A trust anchor MUST say its trust domain, its kind, its public material, when it stops being trusted and whether it is trusted.
Enforced (check): .github: cd commons/data && bun run verify — suite/identity.test.ts: on three engines machines have workload identities, keys and certificates that are unique, and devices have attestations, posture and sessions, all as principals of their kind
A certificate MUST be a credential of its principal, with a unique fingerprint, and MUST hold no private key.
Enforced (check): .github: cd commons/data && bun run verify — suite/identity.test.ts: on three engines machines have workload identities, keys and certificates that are unique, and devices have attestations, posture and sessions, all as principals of their kind
A kind of principal that has no table of its own in this module: it is held by the principal and its roles alone, per FR-001.
DuckDB loads this schema and can read it, and cannot update a row that another row refers to; operations that change principals, runs or delegations are for PostgreSQL and SQLite, per FR-001.
The constraints that governance cannot say (acyclic hierarchies, a subtype row only for a principal of its kind) are checks of the operations and of invariant queries, not of the schema.