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

859 B

Raw Blame History

ADR-032: Single-author model, not CRDT

Status

Accepted

Context

Schema evolution could follow a single-author model (one consumer defines the graph type) or a multi-author CRDT model (multiple consumers define the same type concurrently).

Decision

Schema evolution assumes a single author per graph type. There is no concurrent multi-author editing. If this changes (multiple consumers defining the same graph type with different schemas), a CRDT layer would need to sit between the event stream and storage. That's a post-v1 concern.

Consequences

Idempotent replay is sufficient; CRDT merge semantics are not needed
Schema evolution is forward-only (new code processes old data), not bidirectional
Migration is apply-on-read or apply-on-write, not conflict resolution

References

schema-evolution.md

859 B Raw Blame History