Skip to content

Future work: unified manifest engine (5 durable-state writers → 1) #415

Description

@TinDang97

Deferred by design from the 2026-07-20 storage-unify campaign (W1–W6, #396–#401): merge the five per-plane durable-state writers (page manifest dual-root, AOF manifest, graph JSON manifest, vector IndexManifest, ShardControlFile) into one manifest engine with per-plane payload sections.

Full RFC: .planning/rfcs/unified-manifest-engine.md (moon-docs@65a6f1a) — M-A/B/C phasing, open questions Q1 boot-bootstrap / Q2 commit-cadence coupling / Q3 no-dual-write, plus the task #48 poison-record policy tie-in (section decoders fail closed with an INFO counter, never skip-and-continue).

Explicitly unscheduled: per the 2026-07-12 'unify contracts, keep engines' decision this needs a measured pain point (a real incident or profiling evidence) before it earns a milestone. Prerequisite naming cleanup (AofShardManifest rename) already shipped in W6 (#401).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions