Roadmap outline

Presentation6 pages17 kB

Converted at publication, cached by fingerprintThe original stays downloadable

slide 1

FRAMING · 7 MAY 2026 Roadmap outline Where the Concordance project goes after its first site. Six slides framing the next loops of the tool. A deck, its PDF preview and its notes, grouped by the build into one page. Roadmap outline · 2026-05-07 · 1/6

slide 2

1 · TODAY A static site from markdown repositories Every note becomes an entity page, every recurring expression a keyword page. Every doubt is a finding in the build log, never a stopped build. Two builds of unchanged sources give byte-identical files. Roadmap outline · 2026-05-07 · 2/6

slide 3

2 · DOCUMENTS Decks, transcripts and their notes Office documents converted to PDF at publication, cached by fingerprint. Transcripts read cue by cue, speakers pseudonymised before anything else reads them. Twin resources recognised as one page with tabs. Roadmap outline · 2026-05-07 · 3/6

slide 4

3 · CONTRACTS The operations an API really exposes An API note declares its contract; the build imports the operations. Each operation note absorbs the operation it names. A purpose-built viewer renders the contract under the page budget. Roadmap outline · 2026-05-07 · 4/6

slide 5

4 · QUALITY A linter where the notes are written The same checks in the merge request and in the build. A SARIF log in the margin of the diff, an error finding fails the check. The wiki keeps pace with the tool: every check has its rule note. Roadmap outline · 2026-05-07 · 5/6

slide 6

5 · LATER A service beside the command line A model query API for the screens that cannot read model.json. Suggestions reviewed on a screen and recorded in the lock file. Nothing of it exists in this version; the specifications describe it as a target. Roadmap outline · 2026-05-07 · 6/6

The framing (6 passages, no note) deck (note: Deck) of the Concordance project (note: Project), six slides on where the tool goes after its first site (note: Site). The deck is the original, its PDF (56 passages, no note) the preview (note: Preview) the build (note: Build) would have converted anyway, and this note (note: Note) its written form (52 passages, no note); the three sit in one folder and the build groups (23 passages, no note) them into one page.

What the deck says

  1. Today: a static site from markdown (3 passages, no note) repositories. Every note (3 passages, no note) becomes an entity page, every recurring (3 passages, no note) expression a keyword (3 passages, no note) page, every doubt a finding in the build (3 passages, no note) log, never a stopped build; two builds (3 passages, no note) of unchanged sources give byte (3 passages, no note)-identical files.
  2. Documents (note: Document): office documents converted (3 passages, no note) to PDF at publication (3 passages, no note) and cached by fingerprint, transcripts (3 passages, no note) read cue by cue (3 passages, no note) with their speakers pseudonymised (3 passages, no note) before anything else reads them, twin resources recognised (3 passages, no note) as one page with tabs (33 passages, no note).
  3. Contracts: an API note (3 passages, no note) declares its contract, the build imports (4 passages, no note) the operations, each operation note (3 passages, no note) absorbs the operation (note: Operation) it names, and a purpose-built viewer renders (3 passages, no note) the contract (note: Contract) under the page budget (20 passages, no note).
  4. Quality: a linter (3 passages, no note) where the notes are written, the same checks in the merge (3 passages, no note) request (31 passages, no note) and in the build, a SARIF log (3 passages, no note) in the margin of the diff; the wiki keeps pace (4 passages, no note) with the tool, every check (note: Check) having its rule note (note: Rule).
  5. Later: a service beside the command (3 passages, no note) line, with a model query API (note: Model query API) for the screens (note: Screen) that cannot read model.json and suggestions reviewed on a screen and recorded in the lock file (note: Lock). Nothing of it exists in this version.
written linkrecognised word, existing noterecognised word, no note

briefs/framing/2026/2026-05-07-roadmap-outline/roadmap-outline.mdSomething to correct? Edit this page

briefs/framing/2026/2026-05-07-roadmap-outline/roadmap-outline.pdf

briefs/framing/2026/2026-05-07-roadmap-outline/roadmap-outline.pptx

Properties

Type
Presentation
Author
Concordance project
Pages
6
Date
Domain
Quality

Read from the file, distinct from the repository date.

3 files grouped — same base name

  • roadmap-outline.mdMarkdown note
  • roadmap-outline.pdfPDF
  • roadmap-outline.pptxPresentation
Separate these files
See the neighbourhood map6 pages6Neighbourhood mapRoadmap outline

Neighbourhood map Roadmap outline

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

36 neighbours in total, more than the map shows.

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.