- Human approval before anything is publishedAvailable now
- A report reaches leadership only through a recorded municipal approval — the requirement is enforced in the database, not by policy alone.
- Source-linked statementsAvailable now
- Every material statement in a drafted report keeps a reference to the submission, photograph, or document behind it.
- Machine-prepared drafts, human-releasedAvailable now
- Report drafts are prepared automatically from the submissions on file — every statement labeled by origin and linked to its source. The system makes no engineering, legal, or financial determinations and never rates contractors; nothing is released without a recorded municipal approval.
- Original submissions preserved verbatimAvailable now
- What a contractor submitted is never edited. Municipal wording is layered on top and always distinguishable.
- Organization-level data isolationAvailable now
- Each municipality's records are separated with database row-level security, not application filters.
- Private evidence storageAvailable now
- Photographs and documents live in private storage; staff view them through short-lived, expiring links.
- Append-only audit trailAvailable now
- Sends, submissions, reviews, edits, and approvals append to an audit record that nothing in the application can rewrite.
- Records-retention configurationPlanned
- A preserve-by-default posture is decided and documented; per-city retention schedules and disposition workflows are scheduled ahead of the first pilot.
- Council-packet exportPlanned
- Export of approved reports to packet formats follows pilot validation — approved content only.