heaven/textmachine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Tell the truth in the ratified contract header: it called itself an unratified S3 draft for three days and pointed at a companion path absent beside the canon

Browse source
This commit is contained in:
heaven 2026-08-07 23:06:13 +03:00
parent ea2867b6c7
commit bc987677e4
1 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/architecture/14-api-contract/openapi.yaml
View file

@ -3,14 +3,19 @@ openapi: 3.1.0
info:
title: TextMachine API
version: 0.1.0-draft
summary: Contract between the frontend and the TextMachine platform (draft, awaiting ratification).
summary: Ratified contract between the frontend and the TextMachine platform (D39.99).
description: |
**DRAFT of frontend session S3 — not a ratified contract.** The ratified copy belongs in
`docs/architecture/14-api-contract/` (orchestrator's zone).
**RATIFIED contract (D39.99, 04.08.2026).** The canonical copy lives in
`docs/architecture/14-api-contract/` (orchestrator's zone); `frontend/docs/api-contract/` is a
byte-mirror of it, and a divergence is a defect of one of the two, never a local edit.
⚠ Text corrected by orchestrator #15 on 07.08: this file called itself an unratified draft of
session S3 for three days after it was ratified, and pointed at a companion path that does not
exist beside the canonical copy. The version string still reads `-draft` — session S3 bumps it
as the first item of its spec work.
Companion document: `../API_CONTRACT_DRAFT.md` — provenance of every decision (derived from
engine code / proposed by the frontend / open), rationale, dependencies and open questions.
This file is normative for the FORM; the companion explains where the form comes from.
Companion document: the `README.md` beside the canonical copy — provenance of every decision
(derived from engine code / proposed by the frontend / open), rationale, dependencies and open
questions. This file is normative for the FORM; the companion explains where the form comes from.
## Boundaries