Files

glm-5.1 67ccfbf928 docs: restructure architecture docs to flowgraph pattern

- Create decisions/ directory with 32 numbered ADRs (ADR-001 through ADR-032)
  extracted from inline DD/SD/ED/SE decision sections
- Create open-questions.md with 16 OQs organized by theme, cross-referenced
  to ADRs, with status tracking (resolved/open)
- Create README.md as architecture index with doc table, ADR table, and
  lifecycle status definitions (draft/reviewed/stable/deprecated)
- Replace inline decision sections in all spec docs with ADR reference tables
- Replace inline open questions with OQ references to centralized tracker
- Update frontmatter: metagraph-module.md, overview.md, sqlite-host.md → reviewed;
  schema-evolution.md and encrypted-data.md remain draft
- DD1-DD10 → ADR-009 through ADR-018
- D1-D8 → ADR-001 through ADR-008
- SD1-SD5 → ADR-019 through ADR-023 (SD5 folded into ADR-006/008)
- ED1-ED5 → ADR-023 through ADR-027
- SE1-SE5 → ADR-028 through ADR-032

2026-05-29 07:19:03 +00:00

922 B

Raw Blame History

ADR-008: Common columns pattern

Status

Accepted

Context

All tables need auditability (creation/modification timestamps) and extensibility (metadata). Without a common pattern, each table defines these differently.

Decision

All tables share id (text PK, consumer-generated), metadata (JSON text defaulting to {}), createdAt, and updatedAt (integer timestamps in SQLite, timestamptz in PG). The metadata column is an extension namespace following _subsystem.key namespacing — it's for opaque key-value pairs that subsystems add without schema changes, not for queryable data.

Consequences

Every row has auditability and extensibility
Subsystems add metadata without schema changes
Columns that appear in WHERE/JOIN conditions should be proper columns, not metadata
SQLite uses integer timestamps; PG will use timestamptz

References

sqlite-host.md

922 B Raw Blame History