Context

How this system works, recorded one scope per file. Each one splits into AS IS — what is built and running — and TO BE, what is designed and not built yet, with the issue that will build it.

$count
scopes
${kilowords}k
words
$issues_cited
issues cited
$to_be_total
designs not built

Press / to search every word of it, or pick a group:

Groups

$cards

Designed, not built

$to_be_total TO BE entries across $to_be_count scopes — designed, with the issue that will build it, and not running yet.

$to_be_list

Overdue a look

Ordered by how long since updated was bumped. A scope file rots quietly: nothing about a stale one looks stale.

$old_list

The conventions

One file per scope; everything else deep-links to it rather than restating it. Anything designed but not built goes under TO BE with its issue. No history — overwrite the fact and bump updated; git log is the history. The rules in full are in $context_dir/README.md, and this site checks them on every build: a deep link whose anchor names no heading, a reference to a scope that has moved, a missing updated, a TO BE entry with no issue behind it.