glm-5.3-flash
6c583af81a
Root cause of the two taskgraph validate errors: the sdd_process doc never recorded the full frontmatter enum set (impact was entirely undocumented), so agents invented variants. - oq-06: status done → completed; n5-unborn-head-rider: impact wire-claim → component (schema-valid nearest value). - oq-19/oq-21 tracker files had no frontmatter at all (silently skipped by every taskgraph command — validate does not flag them); scaffolded both as proper tasks. oq-19 now depends_on the n5 rider task (rider 1 executes there; the container closes when both done), with a body note explaining the split. - sdd_process.md: added the impact table, the exact enum variant list for all five categorical fields (probed from taskgraph 0.1.3), and the three gotchas agents hit (done ≠ completed; frontmatter-less files silently vanish from the graph; closed status lifecycle). Verification: taskgraph validate ✓ (9 tasks), taskgraph topo shows the n5 → oq-19 edge correctly.
1.3 KiB
1.3 KiB
id, name, status, depends_on, scope, risk, impact, level, tags
| id | name | status | depends_on | scope | risk | impact | level | tags | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| architecture/oq-06-metadata-backing | OQ-06 unblock — metadata-scale requirements arrive | completed | narrow | trivial | component | research |
|
Description
Tracker for OQ-06 (deferred(scope)): registry/metadata backing store.
Resolved early (2026-09-21, ADR-012) before the blocking condition
arrived: the deferral's premise was wrong — the deferred "metadata-scale
requirements" only ever gated a persistence adapter (future, separate,
additive), never the default backing. The default (registry-file
feature: per-repo record files + in-memory index, config-seeded,
op-mutable) is file-scale by design under the alknet repo/adapter
pattern. Marking done closes the tracker.
Work
None. OQ-06 is resolved by
docs/architecture/decisions/012-registry-backing-and-ops.md (§1–2, §4).
Verification
- OQ-06 status matches
docs/architecture/open-questions.md(resolved).
Out of scope
- Building a persistence adapter (gated on a real deployment need — additive, no tracker needed until then).
Summary
Resolved early via ADR-012: the repo/adapter pattern made the default independent of scale requirements; the deferral dissolved.