Database and Identity¶
Overview¶
Where the schema rules, the identity model and the module ownership actually live.
This page is an index. The standards themselves are held in Architecture and Development, and those pages own them. Nothing is duplicated here.
Access¶
No menu. This section is reached from Developer.
Screen¶
No screen.
Main Features¶
The Standards That Govern Stored Data¶
| Standard | What it settles |
|---|---|
| UUID Identity Transition Standard | Row and relation identity, and the coexistence of numeric and UUID keys |
| System Structure Standard | Where files, packages and modules may live, and what owns what |
| Module Registry | Which module owns which capability |
| Dependency And Public API Standard | What may depend on what, and what may be public |
| Source Registry Standard | How a source becomes authoritative for a capability |
| Task Context And Handoff Standard | How a unit of work carries its context across a handoff |
The Identity Decisions Behind Them¶
- ADR 0011 — UUID-First Identity And Dual-Key Coexistence
- ADR 0029 — Bounded Structure And Format Debt Transition For UUID Candidates
The Identity Migration That Was Carried Out¶
- Multica Session Records — UUID Migration — the row and relation constraints applied across Hub and production, and what it did not complete
Fields¶
| Field | What it means |
|---|---|
| Row UUID | The identity of one record |
| Relation UUID | The identity of a parent a row points at |
| Numeric key | The compatibility value that coexists with the UUID |
| Module | The single owner of a capability |
Status¶
There is no status on this page.
A numeric identifier is not a parent reference. Where a column only ends in
_IDit may hold an external identifier or a code value. The identity standard is how you tell them apart.
Notes¶
- Read the identity standard before touching a column's constraints. Adding a uniqueness rule to a live table changes what can be written.
- The migration was preparation, not deployment. No production build, install, restart or reload was performed as part of it, and no release was promoted. See the record above.
- Compatibility values were preserved. Existing UUID values and numeric keys were not rewritten.
- Rows whose parent does not exist were left null rather than given an invented parent.
- A full schema listing is not held here. Read it from the database, not from a document that may be behind.
Related¶
- Architecture — the standards this page indexes
- Development — documentation and knowledge standards
- History — the decisions behind the identity model