docs: status lines of the design records that describe an older state #749

New issue

Closed

opened 2026-11-13 12:39:37 +00:00 by orion · 2 comments

orion commented

2026-11-13 12:39:37 +00:00

Collaborator

Context

The index of the design records promises "a status line that says how much of it exists today". The audit finds status lines that say "not built" or "proposed" for work that is on main:

Record	The status line says	The repository has
`docs/design/ECS.md`	proposed, there is no `std/ecs`	`std/ecs/src` with column, entity, events, hierarchy, query, store (#453 closed)
`docs/design/TENSOR.md`	designed, not built (2026-10-23)	`std/tensor/src/lib.trb`, `tensor.trb` (#691 closed)
`docs/design/COMPUTE.md`	`std/tensor`, `std/gpu` and `std/learning` do not exist	`std/tensor` exists
`docs/design/JAVASCRIPT-AND-PHP.md`	planned, no back end exists	`compiler/src/backend/javascript`, `compiler/src/backend/php` (#708 closed)
`docs/design/JAVASCRIPT-BACKEND.md`	proposed, no code exists	the same
`docs/design/COLLECTION-STORAGE.md`	designed, not built (2026-10-23)	slice 1 landed (#526 closed)
`docs/design/NATIVE-BODIES.md`	designed, not built	parse, check and lowering of native bodies landed (#467, #478, #484 closed)

A reader, and the loop that plans from the records, takes built work for open work.

Source

Cleanup audit 2026-11 (#742), finding F3; the report is docs/project/2026-11-cleanup-audit.md.

Goal

Every status line of docs/design/*.md states what exists on main today, which slices are open, and the issue that tracks the open part.

Design record point

docs/design/index.md (the promise of the status line); docs/contributing/ (how a record is written).

Acceptance criteria

The seven records above have a status line that names the built slices, the open slices and their issue numbers
Every other record's status line was read against std/, compiler/ and the closed issues, and the PR description lists each record with "unchanged" or the change
A status line that leaves work open names an open issue, or the PR description lists the record as "no issue" for the tracking epic #742
torb docs check is green; no text below the status line changes except a sentence that repeats the stale claim

Dependencies

None.

Seed

None (documentation only).

Size

One PR, one commit.

## Context The index of the design records promises "a status line that says how much of it exists today". The audit finds status lines that say "not built" or "proposed" for work that is on `main`: | Record | The status line says | The repository has | |---|---|---| | `docs/design/ECS.md` | proposed, there is no `std/ecs` | `std/ecs/src` with column, entity, events, hierarchy, query, store (#453 closed) | | `docs/design/TENSOR.md` | designed, not built (2026-10-23) | `std/tensor/src/lib.trb`, `tensor.trb` (#691 closed) | | `docs/design/COMPUTE.md` | `std/tensor`, `std/gpu` and `std/learning` do not exist | `std/tensor` exists | | `docs/design/JAVASCRIPT-AND-PHP.md` | planned, no back end exists | `compiler/src/backend/javascript`, `compiler/src/backend/php` (#708 closed) | | `docs/design/JAVASCRIPT-BACKEND.md` | proposed, no code exists | the same | | `docs/design/COLLECTION-STORAGE.md` | designed, not built (2026-10-23) | slice 1 landed (#526 closed) | | `docs/design/NATIVE-BODIES.md` | designed, not built | parse, check and lowering of native bodies landed (#467, #478, #484 closed) | A reader, and the loop that plans from the records, takes built work for open work. ## Source - Cleanup audit 2026-11 (#742), finding F3; the report is `docs/project/2026-11-cleanup-audit.md`. ## Goal Every status line of `docs/design/*.md` states what exists on `main` today, which slices are open, and the issue that tracks the open part. ## Design record point `docs/design/index.md` (the promise of the status line); `docs/contributing/` (how a record is written). ## Acceptance criteria - [ ] The seven records above have a status line that names the built slices, the open slices and their issue numbers - [ ] Every other record's status line was read against `std/`, `compiler/` and the closed issues, and the PR description lists each record with "unchanged" or the change - [ ] A status line that leaves work open names an open issue, or the PR description lists the record as "no issue" for the tracking epic #742 - [ ] `torb docs check` is green; no text below the status line changes except a sentence that repeats the stale claim ## Dependencies None. ## Seed None (documentation only). ## Size One PR, one commit.

orion added the

ready

loop

labels

2026-11-13 12:39:37 +00:00

orion referenced this issue

2026-11-13 12:41:38 +00:00

cleanup: 2026-11 audit plan (epic) #742

orion commented

2026-11-13 19:07:37 +00:00

Author

Collaborator

[loop:torbscript] claim implement by session:loop-torbscript-20261113 until 2026-11-14T01:10:00Z

orion referenced this issue from a pull request that will close it,

2026-11-13 19:09:17 +00:00

docs(design): status lines say what is built and which issue tracks the rest #764

orion commented

2026-11-13 19:10:13 +00:00

Author

Collaborator

[loop:torbscript] implement: #764, head be51302c83, CI pending (commit messages, what-the-change-touches and pdisc green; tier A/B and torb docs check queued on the congested runners), next: review (merge gate; the CI result is read by the next tick). Worker tokens: about 120k estimated.

[loop:torbscript] implement: https://git.torb.dev/torbscript/language/pulls/764, head be51302c837488582c0805d4fdce08f50a18523c, CI pending (commit messages, what-the-change-touches and pdisc green; tier A/B and `torb docs check` queued on the congested runners), next: review (merge gate; the CI result is read by the next tick). Worker tokens: about 120k estimated.

orion referenced this issue

2026-11-13 19:54:47 +00:00

backend: JavaScript #63