IF Commons GitHub

Identity ReBAC

0035Active

0035-identity-rebac · owner if · domain data

Requirements

FR-001checkpassing

The module MUST hold the definition of an authorization model with its version and status, and relation tuples of an object, a relation and a subject (a kind of principal or of object, with the relation of the subject where a set is meant), a caveat and its values, an expiry and a time, unique by a key made of all of them.

Enforced (check): .github: cd commons/data && bun run verify — suite/identity.test.ts: on three engines any kind of principal holds roles once, roles inherit and are separated, attributes of any principal and resource are one value each, policies and relation tuples and the permissions they grant are unique

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

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

Tests: passed: suite/identity.test.ts on three engines any kind of principal holds roles once, roles inherit and are separated,

FR-002checkpassing

A permission relation MUST say which relation on which type of object grants which permission, once for a permission and a type.

Enforced (check): .github: cd commons/data && bun run verify — suite/identity.test.ts: on three engines any kind of principal holds roles once, roles inherit and are separated, attributes of any principal and resource are one value each, policies and relation tuples and the permissions they grant are unique

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

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

Tests: passed: suite/identity.test.ts on three engines any kind of principal holds roles once, roles inherit and are separated,

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

  • Rebac - 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-rebac/mod

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