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.
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.
A complete case at Kearney Funeral Services, from first call to closure. Scrub the timeline to watch the pipeline execute — compliance gates, conditional pass-throughs, and system cascades.
RequiemOS handles per-tenant variation with a module pipeline: a library of reusable workflow building blocks, assembled into tenant-specific templates by platform staff.
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. Nine numbered stages from intake through S3 storage, 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.
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.
Where the General Price List, the contract, and the case workflow meet. Step through each lifecycle stage — GPL administration, arrangement, mid-case amendment, reconciliation at close — to see what data crosses each seam and what deliberately stays put. Interactive drill-down on every stage. Reflects pre-ADR-036 doctrine; rewrite queued for ratification.
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.