shoney.arickathil
c0b0dbb846
- README: shipped concurrency/HTTP/WebSockets sat in the roadmap as "not yet available"; "no package manager" contradicted [deps]; the deps example would not have compiled (the key IS the module name) - runtime/README: leads with wovm, wo-rt.c demoted to a historical section; dropped 2 nonexistent recipes, crates/rt, @gc refcounting, 13 suites -> 18 - employee + log-watcher READMEs claimed "does not compile"; both are gates - error catalog: +10 emitted codes incl WO-E250, the only diagnostic the shipped query surface raises; recorded why the sweep rotted - language-surface: group-by parses, then the typechecker refuses it - 00-code-review + 00-link-audit re-run; history kept, not rewritten - 48 dead Rust-era exploration links de-linked rather than re-pointed (their prose names the retired plan by number); successor map -> discarded.md - 08-project-structure: compiler/plan/ never existed; corpus has 9 dirs, 5 empty - releasing.md: dropped a --draft step the workflow never had - new docs/00-doc-audit.md: findings + disposition, incl one row where the audit was wrong and the doc it accused was right - status folders removed: 34 stories flat, status only in frontmatter; 252 links recomputed from resolved paths; board/board-views/structure retaught - story 24 -> in-progress, since frontmatter is now the only truth - new iteration 38: fs mutation verbs + net.connect, the two capability families no iteration owned - new iteration 39: gofiber/fiber v3.5.0 parity study. The ledger called CSRF/sessions unblocked by iteration 34's HMAC, but the runtime has no source of randomness at all - linkcheck skips .dev/.superpowers: 0 broken paths, 0 bad anchors Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
72 lines
2.3 KiB
Markdown
72 lines
2.3 KiB
Markdown
# Live board views (Obsidian Dataview)
|
||
|
||
Every story iteration file carries YAML frontmatter — **the frontmatter
|
||
is the source of truth**:
|
||
|
||
```yaml
|
||
---
|
||
iteration: "8" # immutable id (string: "7b", "9b" exist)
|
||
status: in-progress # done | in-progress | refine | hold — the ONLY place status lives
|
||
chain: 1 # concurrency-chain position, chain stories only (1–6)
|
||
---
|
||
```
|
||
|
||
**Editing `status:` IS the status change.** Story files sit flat in
|
||
`docs/stories/language-runtime-database/`; no directory encodes state, so
|
||
there is nothing to move and nothing that can disagree. This replaced the
|
||
2026-08-20/21 folder scheme on **2026-08-26** — under that scheme a status
|
||
change moved the file, which broke every relative link in and to it, and
|
||
the repo's two link audits were largely the cleanup.
|
||
|
||
The closed set `status:` may take is `done`, `in-progress`, `refine` (needs
|
||
a brainstorm before it can be planned) and `hold`. A value outside it will
|
||
simply not appear in the lanes below, which is the cheapest possible
|
||
validation. The prose board ([`00-status.md`](00-status.md)) stays the
|
||
standup narrative; these queries are the live views over the same facts.
|
||
|
||
Adjust the `FROM` path to your vault root (queries below assume the
|
||
vault opens at the repo root).
|
||
|
||
## Everything not done, chain order first
|
||
|
||
```dataview
|
||
TABLE iteration, status, chain
|
||
FROM "docs/stories/language-runtime-database"
|
||
WHERE status != "done"
|
||
SORT chain ASC, iteration ASC
|
||
```
|
||
|
||
## Grouped by status (the kanban lanes, as data)
|
||
|
||
```dataview
|
||
TABLE rows.file.link AS story, rows.iteration AS iteration
|
||
FROM "docs/stories/language-runtime-database"
|
||
WHERE status != "done"
|
||
GROUP BY status
|
||
```
|
||
|
||
## The concurrency chain, in execution order
|
||
|
||
```dataview
|
||
TABLE iteration, status
|
||
FROM "docs/stories/language-runtime-database"
|
||
WHERE chain
|
||
SORT chain ASC
|
||
```
|
||
|
||
## Active right now
|
||
|
||
```dataview
|
||
LIST
|
||
FROM "docs/stories/language-runtime-database"
|
||
WHERE status = "in-progress"
|
||
```
|
||
|
||
## Kanban caveat
|
||
|
||
The Kanban plugin stores board state in its own markdown file — a
|
||
second copy of status. To keep frontmatter the single source of truth:
|
||
**use Dataview for querying; treat any Kanban board as a VIEW, never
|
||
the place status is edited.** A status change is one edit to one
|
||
`status:` key; a Kanban card drag that only rewrites the Kanban file is a
|
||
lie the next query won't see.
|