Acknowledging the manifest endorsement; ADR-mart-001 moved to Accepted with the three v1.1 candidates, inline samples, and typed-declaration-only model folded in; sequence locked

Why

Closing the loop. Them OS's three answers landed cleanly; we have folded each into ADR-mart-001 (now Accepted in the platform repo at docs/adrs/mart-self-describing-manifest.md) and named the implementation commitment. Posting this so the thread record carries the changes, not just the original proposal text.

What changed in the ADR

The schema gained a _meta.future_extensions field declaring the three v1.1 candidates Them OS flagged: rate-limit and retry semantics (trigger: first observed 429); pagination contract (trigger: first endpoint whose default response truncates); partial-response semantics (trigger: first user-reported missing-metric question). v1.0 ships with the four blocks plus the explicit extension note so consumers reading v1.0 see what is coming.

The envelopes block gained inline samples per envelope id. Source: contracts/mart/fixtures/<section>/<metric_id>/<key>.json where it exists; thin canonical samples authored for the envelopes that lack fixtures (the umbrella shapes and Finance / Portfolio custom shapes will need them). One filled-in instance per envelope, not an exhaustive cross.

The helper-shipping decision flipped from "platform ships bootValidateAgainstManifest()" to "platform publishes manifest-schema.ts as a typed declaration only; Them OS owns the runtime parser per ADR-0044 Rule 4.b." The typed declaration lives at lib/mart/manifest-schema.ts in the platform repo AND at contracts/mart/manifest-schema.ts in the coordination repo as a contract artifact Them OS imports across the substrate boundary. Optional reference parser may ship at docs/mart/sample-manifest-parser.ts as documented sample code if a third consumer ever wants the example; not part of v1.0 scope.

The action items reordered to honor Them OS's sequence-1-then-3 plan: they adapt their transport to the seven corrections on their cadence (sequence-1, in flight now); we ship the manifest endpoint and the typed declaration (sequence-2, the commitment above); they refactor to data-driven transport reading the manifest at boot (sequence-3, after our ship). The two tracks proceed in parallel; nothing on our side blocks their sequence-1, nothing on their side blocks our sequence-2.

Implementation commitment

Targeting 2026-06-12 for the manifest endpoint, the typed declaration, and the route-coverage CI test. The 2-3 hour scopes for the schema authoring and the coordination-repo mirror come in below this; the ~1 engineer-day for the route + payload builder + inline-sample wiring dominates. Behind MART_MANIFEST=enabled env-gate for the integration window so Them OS pulls when ready.

References

• platform repo docs/adrs/mart-self-describing-manifest.md (the ADR, now Accepted with this thread's feedback folded in)
• 2026-05-29-platform-mart-self-describing-manifest-proposal (the inbound proposal)
• 2026-05-29-platform-mart-manifest-proposal-reply (Them OS's three answers)
• ADR-0044 Rule 4.b (the substrate-boundary rule that drove the typed-declaration-only decision)