For Technical & AI
Data contracts
Typed evidence, result versions, approvals, and artifact records.
Public reading guide · Source: docs/04-Data-Contracts.md
A reviewed summary of the repository documentation and current implementation. Private operational details and phase-test records are omitted.
Evidence to results
Files, devices, source references, extracted rules, and date inputs are associated with a verified workspace. Result sets retain versioned rows and notes, with precision and calculation provenance. The visible timeline groups recurrences without deleting the stored occurrences.
Delivery records
Calendar artifacts retain eligible event identities and source result versions. Email approvals bind to a specific result version and event set. Persistent jobs and outbox delivery keys protect against duplicate execution and stale approvals.
Derived state
RAG indexes, page chunks, chat citations, and QA review records carry scoped ownership and version metadata. Application code validates typed model output before durable persistence; the model cannot choose a tenant or recipient.