Client Delivery › C7 spec: Environment config
C7 spec: Environment config
C7 / L7 Environment: the account boundary, identity, budgets, and the people the gates route to.
REQ-V-00, budgeted and audited by default: every run carries a declared token budget and end state, and the audit trail is append-only. Neither is a client option; clients set the numbers and the names, never the existence of the mechanism.
REQ-V-00, budgeted and audited by default: every run carries a declared token budget and end state, and the audit trail is append-only. Neither is a client option; clients set the numbers and the names, never the existence of the mechanism.
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 |
|---|---|---|---|---|---|---|
| V-01 | Tenancy and account mapping | E, H | environment.tenant | Account or subscription structure + per-tenant key alias, via infrastructure-as-code | At provisioning | Isolation test suite at the account and key level |
| V-02 | Identity provider | E | environment.idp | Identity federation config per tenant (workload identities plus SSO) | On config deploy | SSO login and end-to-end identity-passthrough test: downstream checks act as the person |
| V-03 | Platform access endpoint | G, E | environment.endpoint | North gateway instance stamped from the template (setup step 15); the channels and hosts CONTENT of that config is C1, rows E-01 and E-02 | On config deploy | A sanctioned host lists exactly its own tenant's tools and no other |
| V-04 | Cloud platform | H | environment.cloud | Overlay selection driving the infrastructure module set (AWS, Azure, or GCP) | At setup; later is a migration | Blindness audit: nothing above L7 references the cloud value |
| V-05 | Token budgets per use case | H | environment.budgets{} | Run-contract defaults consumed by loop enforcement every tick | Next run | Over-budget kill test: the run terminates and raises an incident |
| V-06 | Gate approvers and backups | F | environment.approvers{} | Approval matrix consumed by gate mechanics and the review surface | Next transition | Segregation check (the data enterer cannot approve) and the backup-routing test |
| V-07 | Alerts and escalation timers | F, H | environment.escalation{} | Alerting config: recipients, timers, paging routes | Immediately | Timer drill: an unanswered approval escalates to the named backup on schedule |
Acceptance
- The one-click provisioning dry-run is green end to end with these values (playbook Track 1 gate).
- SSO, passthrough, isolation, and blindness audits all pass.
- The budget kill and escalation drills complete with incidents and audit entries recorded.