Docs / Specification

A-corpus — Corpus grammar decisions

Status: accepted

clause-addressed-sentence — A clause is an addressed sentence in a list, not a table row

Cited bycorpus.address.clause-idcorpus.address.clause-idA clause id is three dot-separated segments — contract, operation, subject — each matching [a-z0-9-]+. A clause item writes the subject alone; its file and section supply the rest.corpus.anatomy.ledecorpus.anatomy.ledeAn operation section opens with a lede: one paragraph stating what the operation covers. The lede is the operation's only description; its fragment entry carries no gloss.corpus.anatomy.clause-listcorpus.anatomy.clause-listAfter the lede, one contiguous list holds the section's ungrouped clauses, each item - <subject> — <statement> on one line, optionally followed by its Why on a two-space-indented … line.corpus.anatomy.after-listcorpus.anatomy.after-listProse, diagrams, tables, scenarios and unsettled lines follow the clause list and state no obligation.

The id stays on the sentence, as a margin anchor does, and a reader meets the operation’s purpose before its first rule. The full id still reaches the lock file, the pins and every {{id}}.

teaching-reference-live — Teaching and reference live on separate pages

Cited bycorpus.render.cardcorpus.render.cardcontextful-spec state renders spec/cards/<contract>.md per contract: each operation with its lede and clause count, each refusal as error and gloss, each bound as value, unit and basis, all naming their clause.corpus.guide.filecorpus.guide.fileEach contract has one guide, spec/guide/<contract>.md: front matter contract, one # title equal to the contract's registry title, then prose outside diagrams of at most 400 words plus 20 words per operation its contract's fragment registers.

Contract files are reference; a guide teaches the flow in plain language, and a card gathers operations, error cases and bounds on one page.