Client Delivery › C6 spec: Data config
C6 spec: Data config
C6 / L6 Data & Documents: where this client's data lives, how it is classified, and how it ages.
REQ-D-00, isolated by default: per-tenant isolation, derived-copy status, and the estate's system-of-record role are platform invariants, not client options. Clients configure residency, taxonomy, and lifecycle; never the walls.
REQ-D-00, isolated by default: per-tenant isolation, derived-copy status, and the estate's system-of-record role are platform invariants, not client options. Clients configure residency, taxonomy, and lifecycle; never the walls.
The ground rules and artifact-placement conventions on the C1 specification apply to every band: values enter once in the binding, everything downstream is generated, nothing is hand-edited. Columns: discovery section, binding key, the exact artifact the value materializes into, when it takes effect, and the check that verifies it.
The configuration map
| ID | Client input | Disc. | Binding key | Materializes as | Takes effect | Verified by |
|---|---|---|---|---|---|---|
| D-01 | Tenant store provisioning parameters | Setup | data.stores{} | Infrastructure-as-code variables per tenant; stores stamped from platform templates | At provisioning | The automated cross-tenant read-path test; red blocks deploys |
| D-02 | Source estate inventory, including restricted stores | D | data.estate[] | The source catalog's content: systems, locations, access classes; the C5 rows consume it, this row owns it | Updated as found | Restricted stores carry the entitlement-only flag; shared-index exclusion tested |
| D-03 | Document taxonomy mapping | C, D | data.taxonomy_map{} | Taxonomy map consumed by indexing and classification jobs | Next ingestion | Classification coverage report; unmapped document types are triaged, never dropped silently |
| D-04 | Data residency and regions | E | data.residency | Region parameters in infrastructure-as-code; store and managed-ingestion regions derive from this one value | At provisioning | Residency audit: every store, index, and knowledge base region matches the value |
| D-05 | Retention and legal hold | E | data.retention{} | Lifecycle rules executed by nightly jobs; hold flags immediate; scoped index lifecycle follows case events | Nightly; holds immediate | Lifecycle dry-run, a hold-override test, and the per-tenant deletion drill |
Acceptance
- Isolation and residency audits are green across every store and index.
- The deletion drill completes: one test tenant fully purged, verified empty.
- Taxonomy coverage meets threshold with all unmapped types triaged.