← All projects
19

Document contracts · architecture research

Structured Document

An editor-independent document model and conformance contract in an architecture incubation repository.

INC-004 architecture complete · core unimplemented
Period
2026 — present
Role
Document contract designer

PROJECT / DECISION RECORD

From the problem to the implementation

  1. 01Problem

    Coupling document meaning to one editor limits portable storage, rendering and backend consumption.

  2. 02Design decision

    Define a Document V1 JSON Schema and valid/invalid fixtures before runtime implementation.

  3. 03Implementation

    Schema, contract and conformance design exist; no editor or renderer is implemented.

Structured from project notes; not a live product screen or an execution test.

Problem

19

Coupling document meaning to one editor limits portable storage, rendering and backend consumption.

Constraints

  • Lexical and React are optional adapters, not owners of canonical document semantics.
  • Document meaning must not depend on Lexical or React internal editor state.
  • Schema/conformance design is not proof of an editor or renderer implementation.

Engineering decisions

  • Define a Document V1 JSON Schema and valid/invalid fixtures before runtime implementation.
  • Define Document V1 independently through JSON Schema and valid/invalid fixtures.
  • Treat editors and frontends as optional adapters to the contract.

Implementation

  • Schema, contract and conformance design exist; no editor or renderer is implemented.
  • Identity, schema and cross-language conformance review order are documented.
  • INC-004 covers architecture only; runtime core/editor/renderer are unimplemented.

Verification / evidence

Source evidenceObserved

README records INC-004, a Document V1 JSON Schema and conformance fixtures.

Result / current state

Architecture incubation is complete; no runtime or public package release is claimed.

Current statusINC-004 architecture complete · core unimplemented