Skip to content

History / Development and Testing

Revisions

  • Publish the repository wiki, edited for a reader rather than a generator 73 pages generated from the source tree at f852051, plus a landing page and a sidebar. Three changes were needed before any of it was fit to publish. 5,591 citation links pointed at `file://` paths, which resolve to nothing on a wiki. Repointed at the repository, line ranges intact, so every claim on a generated page can be checked against the code it came from. That turns the densest thing about these pages into the most useful. 124 placeholder lines reading "[No sources needed since this section provides general guidance]" are generator scaffolding and are gone. One claim was misleading rather than wrong: System Overview said payment scanning is off by default, which is true of the shipped default and not of this deployment, where it has been on since 3 October. Now says both. Flattened from nine nested sections into page names, since wiki pages are addressed by name. No collisions, and the generator never cross-linked pages, so nothing broke: 75 pages, zero broken internal links. The landing page is written rather than generated. It leads with what the protocol is, the six factors and their caps, what has actually been proven on a live deployment, and what has not — no audit, admin rights still on a deployer EOA, both operators run by the same party. It also says these pages are derived and that the code and `docs/` win where they disagree, because a generated wiki drifts and readers should know which half to trust. The `.qoder/repowiki/knowledge` tree is deliberately not published: ten pages of tool-internal notes carrying `kind:` and `scope:` frontmatter and source paths prefixed `Sigvara-main/`, written for a machine rather than a reader.

    @RunTimeAdmin RunTimeAdmin committed Oct 7, 2026