# Specification and documentation completion TODO

This document tracked work required to make the version 1 specification and its binding supporting
material complete enough for deterministic implementation and verification.

Every tracked item is resolved and removed per the removal rule below. The decisions live in the
authoritative documents, the requirement manifest in [`REQUIREMENTS.md`](REQUIREMENTS.md), and the
structured registries under `spec/model/`; removed work items remain in repository history. In
summary:

- Requirement authority, traceability, and document ownership are established
  (TJ-GOV, TJ-CONCEPT, TJ-TEST-01 through TJ-TEST-05, and the manifest registry).
- Every version 1 requirement range in the acceptance criteria of
  [`PRODUCT.md#15-acceptance-criteria`](PRODUCT.md#15-acceptance-criteria) has an identifier,
  invariant mapping, suites, evidence status, and recorded limitation reference.
- Negative-space coverage is named in the requirement manifest and
  [`TESTING.md`](TESTING.md#negative-space-coverage), including cancellation, queue, byte, process,
  logging, plan, revalidation-drift, set-shape, terminal-lifecycle, and input-decoder cases.
- Documentation quality work is complete: semantic compression into owner references, the canonical
  state-model and effect-boundary diagrams, testable normative language, recorded platform
  limitations ([`PRODUCT.md#151-recorded-platform-limitations`](PRODUCT.md#151-recorded-platform-limitations)),
  and the performance model in [`PERFORMANCE.md`](PERFORMANCE.md).
- Exploration topics are dispositioned: Kitty keyboard and graphics protocols remain future work
  ([`UI_GUIDELINES.md`](UI_GUIDELINES.md#input-and-mouse)); responsive layout is normative in
  TJ-TERM-02 and TJ-TERM-03; agent-driven QA, native fuzzing, and sanitizer runtimes are deferred
  ([`TESTING.md#deferred-verification-directions`](TESTING.md#deferred-verification-directions));
  prior-art performance lessons are evaluated
  ([`PERFORMANCE.md#prior-art-evaluation`](PERFORMANCE.md#prior-art-evaluation)); data-oriented
  design and SIMD are gated on profiling evidence
  ([`CODING_STYLE.md#data-layout-and-vectorization`](CODING_STYLE.md#data-layout-and-vectorization)).

New unresolved specification or documentation work adds a fresh item here and is removed only after
the authoritative document and requirement manifest contain the decision.

## Definition of documentation complete

The specification and binding documentation are complete when:

1. Every product, safety, interaction, platform, and repository obligation has one stable
   identifier.
2. Every requirement has deterministic terms, bounds, state transitions, and failure behavior.
3. Every requirement maps to an invariant, required test suites, evidence, and platform limitation.
4. Every experiment conclusion is either incorporated normatively or explicitly rejected with
   rationale.
5. No acceptance criterion can pass through a warning-only placeholder unless the requirement
   explicitly permits that degraded capability.
6. No unresolved ambiguity can widen selection, authorization, mutation, accounting, or claims of
   completeness.
7. `PRODUCT.md`, `UI_GUIDELINES.md`, `TESTING.md`, and `CODING_STYLE.md` contain no conflicting or
   drifting formulations.