Specs Index

Specs Index

The browsable map of general and cross-repo specs. Each project repo's wiki carries the same index for its own repo-level specs.

⚠ This page is a pointer list, not a copy. It records slug, purpose, status and two links. It does not reproduce a spec's content, so it cannot contradict it — the worst it can be is out of date on status, which is why the file link sits next to it. File = truth. Issue = tracking. Wiki = reading room. If this page disagrees with a spec file, the file wins and this page gets fixed.

Convention: agents/rules/spec-locations.md (noetl/ai-meta#337).

Active

Spec	Purpose	Status	Issue
2026-09-11-ehdb-resilient-core	EHDB as a resilient KV core — CockroachDB's layers 5→2, no SQL layer. ⚠ The architecture overview is repo-owned and lives on the EHDB wiki: Architecture — resilient KV core. This ai-meta spec carries the cross-repo framing.	draft	#339
2026-09-11-d3-projection-serve-flip	Let a behind snapshot serve; make an ahead snapshot unserveable	draft	#336

Archived

(none yet)

Per-repo spec indexes

A spec that changes one repo's own surface lives in that repo's specs/active/<slug>/spec.md and is indexed on that repo's wiki. A spec that spans repos or is architectural lives in ai-meta and is indexed here.

Repo	Index
noetl/server	(no repo-level specs yet)
noetl/ehdb	(no repo-level specs yet)
noetl/worker	(no repo-level specs yet)

Adding a spec

1. Write the file in the owning repo under specs/active/<slug>/spec.md.
2. Open one coordination issue on noetl/ai-meta from the spec-coordination template; it links the file and does not restate its acceptance criteria.
3. Add a row here with the slug, a one-line purpose, the status from the file's frontmatter, and the issue link.

Archiving

Move the file to specs/archive/<slug>/ in the owning repo, move its row to Archived above, and close the coordination issue citing the landing PRs.