---
id: architecture/oq-06-metadata-backing
name: OQ-06 unblock — metadata-scale requirements arrive
status: done
depends_on: []
scope: narrow
risk: trivial
impact: component
level: research
tags: [external-trigger, deferred-oq, resolved-early]
---

## 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.