Skip to content

decision(D-J): choose format stewardship #55

Description

@softmarshmallow

Tracks registry decision D-J under #43. The charter's stated default is evidence to test, not a decision already taken. Explicit owner GO is required.

Decision question

Is the engine's canonical durable contract the in-memory model plus operation vocabulary, with binary storage/interchange owned by hosts and supported by engine conversion/packing tooling, or does the engine itself own a durable binary format?

Decision time

At the Phase 5 boundary, together with D-G(b), after real .grida→n0 converter experience and the n0 XML ratification pass.

Evidence bar

  • Converter evidence over the pinned real-document corpus: what preserves, rejects, or needs host policy.
  • The ratified n0 XML contract and its authored-source/resource boundaries.
  • A responsibility matrix for schema/version ownership, unknown-field policy, resource packaging, validation, upgrades, compatibility support, and test ownership under each stewardship option.
  • At least one concrete host-integration sketch, plus the engine tooling/API surface each option requires.

Guardrails

  • Keep D-J distinct from D-G(b): stewardship and representation are coupled, not identical.
  • Do not modify format/grida.fbs, make .grida native to the chassis, or serialize resolved documents.
  • Do not claim host management is free; required tooling and compatibility ownership must be priced.

Context

Done

The converter findings, ratification result, and responsibility matrix are linked; owner GO is recorded; one steward exists for every compatibility obligation; D-G(b) is reconciled without collapsing the two questions; and the verdict is recorded in the charter and #43.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions