A living library of architecture decisions, system walkthroughs, and concept overviews for the RequiemOS platform.
Every page below is a self-contained static document. Pick a card to open it. New documents are added as the platform evolves — see the README in this folder for how to contribute one.
Three operational aggregates — Contract Management, Chain of Custody, Case Workflow — sitting over a two-layer substrate of durable Person identity and operational Case state.
One case generates four different kinds of record. Each has its own purpose, its own consumer, its own retention policy — and they never merge.
Login screen to persona-complete MVP, in eleven steps. The “shell out, fill in” principle, the midpoint workflow-engine reveal, four rejected alternatives, and the checkpoints where the arc itself is re-examined.
What the substrate means when you sit down to wire it. Two real cards in app-core — NextStepsCard and TransferCard — are “still mostly blank on purpose” because the service that would populate them is still being designed. This is that service, shown as one API call, one structured answer, and the questions the UI actually wants to ask.
One model for three morgue scenarios — an in-house branch morgue, Megan’s firewalled coroner section, and the provincial morgues Kearney operates. Built to kill the recurring model/semantic confusion: tenant boundaries, the scan→write fork, the one-nullable-column delta on storage_occupancies, and a “say this, not that” vocabulary panel. A design reference for Zareef (schema) and Matt (surface); the ADR stays authoritative.
Document 2 of 3, picking up where the arrangement deck stops. The Care Centre side of a case: the prep document arriving by email, intake and cooler assignment, preparation, attendant and vehicle scheduling, and the two-person identification check before the decedent leaves the building. Six steps on two parallel tracks, no system-enforced gate anywhere in the stretch, and a shared attendant / hearse-driver pool that turns out to be the real constraint. Reconstructed from the full raw transcript of the Aug 19 session with Stephanie and the Care Centre prep staff.
How Kearney runs the arrangement today, first call through contract signing and handoff to transfer. Twenty-one slides: a gate-by-gate breakdown of all ten steps, cross-cutting friction themes, and the open questions — three now resolved, between an unplanned live walkthrough at the Aug 5 discovery session and a follow-up email from Jaycee. Reconstructed from discovery sessions, checked against the raw transcript and correspondence where it mattered most.
Full calendar CRUD is backend-ready on the step-3-5-calendar-backend branch — read/filter, create, edit, soft-cancel, and a buffer-aware conflict check, plus the audit trail each of those writes automatically. A map of the API surface and the demo-ready seed data for Matt and Zareef ahead of the July demo.
Four peer PRDs — Resources, Staff Availability, Automatic Scheduling, Calendar — that together cover the operational scheduling surface. Cross-PRD explainer with diagrams, end-to-end scenarios, and a wayfinding grid.
Every document a direct cremation touches at Kearney — 23 forms across seven phases, first call to urn pickup — placed in the order the case actually needs them. Validated form-by-form against the Aug 28 funeral-director session, with the irreversible-cremation gate and the four remaining ambiguities called out.
Burial as cremation’s list minus the cremation-specific forms, plus a permit — the rule the Aug 28 Kearney session confirmed. Colour-coded by what that session resolved (the shared disposition authorization), what it verified (permit, casket order), what is handled off-system (cemetery coordination), and what stays a blind spot (headstone, pallbearer, procession).
How Kearney’s paper forms become catalogued data. A six-step alternating-AI-and-human pipeline that ingests each form, maps its fields to the database, and maps them again to workflow modules — with a human review gating every AI step.
Step-by-step slide deck explaining how a tenant PDF becomes a form the platform can read and write. Ten numbered stages from intake through the app-core fixture and blank to checking and going live in the platform console, with the duplicate-detection step (canonical synthesis) called out. Keyboard-navigable; print to PDF with P.
How the D3 fill engine plugs into the RequiemOS form strategy. The five-step fill pipeline (persist, fill, stamp QR, flatten, hand to DocuSign), the pre-fill read path, three verification gotchas the fill service must honour, and the Cloudflare-plus-private-network deployment posture on Railway.
The platform’s primary regulatory differentiator made tangible. Three lanes (remains, personal effects, implanted devices), the append-only ledger with supersession, the terminal-state gate at closure, and the medical-device hard gate before cremation.
How RequiemOS comes into Kearney after Garden Hill. The options considered, why Narrow wins on expectations, support and safety, and one cremation case walked top to bottom: who does what, where, and in which system, under Wide and under Narrow.
One at-need contract followed from the GPL through arrangement, a mid-case amendment, and reconciliation at close. Package selection, removable toggles, the discount approval flow, services-rendered resolution — eight tableaux on a paper-receipt visual. Reflects pre-ADR-036 doctrine; rewrite queued for ratification.
Staff already scan and email filled forms today. How that same habit feeds RequiemOS instead of a SharePoint folder — three ways a form can come back filled, a seven-step pipeline split across code, vision-LLM, and human confirmation, and what a form needs to carry to skip straight to its case.
A vision model reads a scanned page and names its form type — not its case — and splits scanner-concatenated bundles, as a triage shortcut on the Unfiled queue. The spike results on a real upside-down Canon scan (~95%), the cost of cheap vs. expensive recognition, and the key finding: a one-time onboarding fingerprint, injected only for a form's own look-alike family, fixes variant confusion with no confident-wrong misfiles — and lets a cheap model match an expensive one.
Every paper form operated across the business’s brands — grouped by brand, each with its blank and filled reference and compliance status. Backed by the canonical inventory at docs/discovery/forms-registry/forms-catalog.json and machine-readable for Claude.
Captured screens from the systems and internal sheets the firm runs today — SRS, Mortware, and the internal sheets & boards — gathered as source material for building Requiem.OS. Click any shot for full size; add notes inline. Backed by screenshots-catalog.json and machine-readable for Claude.