Block a user
As the archive owner I want the importer rebuilt as modular loaders over the normalizer's canonical exports, so dates/people/tags import correctly and re-runs are idempotent
Tobias Wendt — DevOps & Platform Engineer
Observations
- The async runner +
ImportStatusstate machine (IDLE/RUNNING/DONE/FAILED) is being kept verbatim — good, that is the…
As a reader I want undated and imprecisely-dated letters to be honestly labelled in browse views so I always understand a document's date position
Elicit — Requirements Engineer & Business Analyst (Brownfield)
Observations
- The issue is spec-dense and INVEST-clean: a clear user story, nine Gherkin scenarios with observable…
As a reader I want a clean persons directory so I'm not overwhelmed by unconfirmed import entries
DevOps / Platform — Tobias Wendt (@tobiwendt)
Observations
- This issue adds no new Docker service, no infra component, no env var, and no new external integration. From a platform-topolog…
As the archive owner I want one Flyway migration and domain model carrying all import/precision/attribution/identity fields so downstream phases compile against a single, collision-free schema
Decision Queue — Action Required
2 decisions need your input before implementation starts. Everything else is a concrete recommendation the team will apply directly.
Data model /…
As a reader I want imprecise and unknown dates rendered honestly (e.g. "Juni 1916", "ca. 1916", "Datum unbekannt") so a document never shows a precision the data doesn't have
Tobias Wendt — DevOps & Platform Engineer
Observations
- This is a frontend formatter + one Java helper change. No infrastructure surface: no new Docker service, no Compose change, no…
As the archive owner I want the normalizer's canonical exports to carry every field the importer needs (file, date-range end, person ids in the tree) so the loaders have a complete, joinable contract
Leonie Voss — UX & Accessibility
No concerns from my angle. This is a Python normalizer that produces offline canonical exports (xlsx/JSON) consumed by later import phases — there is no UI,…
As a reader I want a clean persons directory so I'm not overwhelmed by unconfirmed import entries
UX / Accessibility — Leonie Voss (@leonievoss)
Observations
- This issue is designing for the hardest constraint correctly: the 60+ transcriber on a laptop/tablet doing destructive…
As the archive owner I want the importer rebuilt as modular loaders over the normalizer's canonical exports, so dates/people/tags import correctly and re-runs are idempotent
Elicit — Requirements Engineer & Business Analyst
I am in Brownfield mode. This is a well-specified issue — INVEST-compliant, 11 Gherkin scenarios, explicit dependencies and out-of-scope. My…
As the archive owner I want one Flyway migration and domain model carrying all import/precision/attribution/identity fields so downstream phases compile against a single, collision-free schema
Leonie Voss — UX & Accessibility Lead
This is a schema + domain-model phase with explicitly no UI ("no rendering, no UI here"). So I have no surface to audit today. I checked one thing that…
As a reader I want undated and imprecisely-dated letters to be honestly labelled in browse views so I always understand a document's date position
Tobias Wendt — DevOps & Platform Engineer
Observations
- Zero infrastructure delta. No new Docker service, no new env var, no Compose change, no new port, no migration. This rides the…
As the archive owner I want the normalizer's canonical exports to carry every field the importer needs (file, date-range end, person ids in the tree) so the loaders have a complete, joinable contract
Elicit — Requirements Engineer
The issue is well-structured (verb-noun title, file-level breakdown, Gherkin AC, explicit out-of-scope, dependency stated) — this is the spec-density bar I…
As a reader I want imprecise and unknown dates rendered honestly (e.g. "Juni 1916", "ca. 1916", "Datum unbekannt") so a document never shows a precision the data doesn't have
Leonie Voss — UX Designer & Accessibility Strategist
Observations
- This issue is unusually a11y-literate already: visible raw secondary line (not tooltip-only, correctly citing **WCAG…
As the archive owner I want one Flyway migration and domain model carrying all import/precision/attribution/identity fields so downstream phases compile against a single, collision-free schema
Elicit — Requirements Engineer & Business Analyst
I'm in Brownfield mode. This issue is unusually well-formed for a schema phase: it has Gherkin acceptance criteria, an explicit out-of-scope…
As a reader I want undated and imprecisely-dated letters to be honestly labelled in browse views so I always understand a document's date position
Leonie Voss — Senior UX Designer & Accessibility Strategist
Observations
- The core accessibility win here is replacing the bare em-dash. I confirmed
DocumentRow.svelte:167and…
As a reader I want a clean persons directory so I'm not overwhelmed by unconfirmed import entries
QA / Test Strategy — Sara Holt (@saraholt)
Observations
- The test plan is genuinely strong: integration-first for query logic, Testcontainers
postgres:16-alpine(never H2), and the…
As the archive owner I want the normalizer's canonical exports to carry every field the importer needs (file, date-range end, person ids in the tree) so the loaders have a complete, joinable contract
Tobias Wendt — DevOps & Platform Engineer
This is a local developer tool (Python venv, run by hand to regenerate out/), so there's no Compose/CI infra to size. My angle is reproducibility…
As the archive owner I want the importer rebuilt as modular loaders over the normalizer's canonical exports, so dates/people/tags import correctly and re-runs are idempotent
Sara Holt — Senior QA Engineer
Observations
- The Gherkin is unusually complete — 11 scenarios covering ordering, id-resolution, raw retention, pair-split, prose/noise, collective/institu…
As the archive owner I want one Flyway migration and domain model carrying all import/precision/attribution/identity fields so downstream phases compile against a single, collision-free schema
Tobias Wendt — DevOps & Platform Engineer
The headline of this issue is a DevOps concern: three competing V69 migrations would be a boot failure on the next deploy. Consolidating to one…
As a reader I want imprecise and unknown dates rendered honestly (e.g. "Juni 1916", "ca. 1916", "Datum unbekannt") so a document never shows a precision the data doesn't have
Sara Holt — Senior QA Engineer
Observations
- The Gherkin is strong: one scenario per precision branch, plus RANGE same-month collapse, RANGE cross-month, SEASON null-raw fallback,…
As a reader I want a clean persons directory so I'm not overwhelmed by unconfirmed import entries
Security — Nora Steiner / "NullX" (@nullx)
Observations
- The
PATCH /{id}/confirmdecision correctly closes a mass-assignment vector (CWE-915). Ifprovisionalwere a settable…