Skip to content

Final-system design mirror · Canonical source: docs/target/functional-chains/chains/FC-14-identity-and-policy.md · SHA-256 c28fbd587ba83427b02679d6e6b83084b047e8d89f5261739877746cde7791a2. Design intent is not deployment proof.

FC-14 — Scoped identity, policy and actual enforcement

Classification: TARGET_DESIGN — final-system requirement, not proof of integration or deployment.

Inherits: System model, authority, contracts and receipts, failure rules.

Functional promise

Owner(s): Konfid / Daat / each owner PEP.

Initiator: A workload requests a specific action on a resource within a tenant and purpose.

Expected result: Bound allow/deny decision and separate effect-point enforcement receipt.

Nominal end-to-end behavior

Step Stage Required outcome
1 Authenticate Scoped owner state and evidence receipt; no hidden mutation of other systems
2 bind actor/resource/digest Scoped owner state and evidence receipt; no hidden mutation of other systems
3 decide policy Scoped owner state and evidence receipt; no hidden mutation of other systems
4 enforce at PEP Scoped owner state and evidence receipt; no hidden mutation of other systems
5 journal result. Scoped owner state and evidence receipt; no hidden mutation of other systems

Interfaces and authority gates

Target boundary references: B-SEC-01. These identify candidate or scoped adopted contracts; they do not certify complete multi-owner deployment. Producer disclosure and receiving-owner admission are separate decisions.

Where no exact interface is adopted, keep TBD rather than inventing a protocol ID. All privileged effects must be checked at the actual enforcing owner.

Failure, privacy and forbidden shortcuts

Expired policy, missing identity/audit provider, wrong tenant and substituted digest fail closed.

Owner-specific tenant/actor identity, source classification, integrity checks, replay and correction must be preserved. No debug dashboard or public documentation site may disclose private content.

Definition of done — acceptance and negative tests

Permission/denial and bypass tests prove no effect on a rejected request.

To qualify the full chain, pin both producer and consumer revisions and execute negative fixtures, recovery and idempotency scenarios. An owner code snapshot alone does not demonstrate running behavior.

Required code and contract alignment

Connect Konfid/host-injected Daat rules to actual enforcing products, never a universal root permission.

Source anchors and verification boundary

See the 53-repository portfolio and snapshot reconciliation for source member names, hashes, declared local roots and evidence limitations. Contract boundaries are catalogued in the C0 target ledger. This is intended final behavior, not evidence of a currently operational multi-repository integration.