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.
Press / to search every word of it, or pick a group:
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.