IF Commons GitHub

Identity machines

0037Active

0037-identity-machine · owner if · domain data

Requirements

FR-001checkpassing

A machine MUST be a principal with a kind, a purpose, where it runs, whether it is kept for emergencies, the longest its credentials may live and when its owner must next review it.

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

Proved by: data/suite/identity.test.ts

Written in: data/models/identity-machine/mod.ts

Tests: passed: suite/identity.test.ts on three engines machines have workload identities, keys and certificates that are unique,

FR-002checkpassing

A workload identity MUST say what vouches for it, the issuer, the subject, the audience and selectors, and MUST be unique by a key made of the issuer and the subject.

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

Proved by: data/suite/identity.test.ts

Written in: data/models/identity-machine/mod.ts

Tests: passed: suite/identity.test.ts on three engines machines have workload identities, keys and certificates that are unique,

FR-003checkpassing

An API key MUST be a credential with a unique prefix, a keyed hash and the scopes it is narrowed to, and a key credential MUST hold a public key as a JSON Web Key and its unique thumbprint, and no private half.

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; suite/identity.test.ts: no concept of any module holds a secret, a prompt or raw arguments in the clear, every concept that holds a secret is restricted, and an agent's provenance and its calls are kept as pinned versions and hashes

Proved by: data/suite/identity.test.ts

Written in: data/models/identity-machine/mod.ts

Tests: passed: suite/identity.test.ts no concept of any module holds a secret, a prompt or raw arguments in the clear, every con; passed: suite/identity.test.ts on three engines machines have workload identities, keys and certificates that are unique,

Out of scope

  • The operations that do the business of this module: a later specification, run by the operations runtime (0031).
  • How a decision is made from these tables: the decision engine is a later specification.

Edge cases

  • 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.

Assumptions

  • The application makes identifiers, hashes and timestamps; the database stores them and refuses what the constraints say.

Open questions

OQ-1open question

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.

Key entities

  • Machines - what this module holds, as its requirements say.

Success criteria

SC-001success criterion

A project composes this module only when it needs it, and the database refuses what the requirements say it must refuse.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided

Cited by

Data, models/identity-machine/mod

Titles, headings, exports, tables, columns and requirements. Esc closes.