RequiemOS · reference

Where the price list, the contract, and the case flow meet

Three domains run alongside a case. The workflow owns the clock and is fixed at first call; the contract is signed once, and any material change after signing voids the row and authors a fresh one (per ADR-036); the GPL is read-only stock the contract copies from. They cross at only two points, and post-signing overages flow to a distinct reconciliation-invoice artifact rather than back into the contract.

Canonical sources: ADR-017 — GPL Structural Model (structural) · ADR-036 — Contract Versioning: Void-and-Recreate Replaces Amendments (lifecycle). This page is a reference rendering, not a system of record.

Case timeline select a stage to drill in

Case
workflow
Template chosenfixed for life
Runs package-selection module
Modules completead-hoc adds · Layer 4 logged
Runs reconciliation module
case_closegates on reconciliation
Contract
pre-need match → convert
snapshotBuilt from GPLdiscount · override · sign
Void & recreateon material change
cross-readLine items vs delivered
Sealedhistory kept
GPL
price list
not read yet
sourcePackages · items · prices
Read for addssnapshot
—
—

The snapshot is one-way

The contract copies GPL prices at arrangement and freezes them on its own rows. Later GPL edits never flow back into a signed contract — which is exactly what makes override, fill-in, and versioning safe.

Workflow is rigid; the contract is versioned by row

The module sequence is fixed at first call and immutable after. The contract is never edited in place — material changes void the current row and author a fresh case_contracts row against the same case (ADR-036 D1). A disposition change — burial to cremation — is close-and-recreate at the case level, not a workflow edit.

One cross-domain read

Reconciliation is the single place delivered services (workflow, Layer 4) meet contract line items. It is the system's most prominent cross-aggregate read.