Skip to content

History / Recall Quality

Revisions

  • Audit every claim against the code, and correct what did not survive Not a copy-edit. Each number and name below was measured from the running system, and these are the ones that did not match. **The policy stack was described wrongly, and it is a security page.** The wiki said a single PRE_ACT hook runs seven policies, listing all seven. Four run at PRE_ACT; the other three run at PRE_VALIDATE and PRE_COMMIT. So the page told a reader that seven policies stand between a decision and a side effect on their machine, when four do — and that the fabrication guard fires before the action, when it fires before the commit. Architecture, Security Model, Governance Engine and First Run all carried it, because all four had copied the boot log, which was itself printing a flat list under one hook's name. The log is fixed in the repository; these pages now match it. **Recall Quality invented three of the five validity state names.** The code has VALIDATED, PARTIALLY_VALID, OUTDATED, DISPROVEN, UNKNOWN. The page said Validated, Provisional, Superseded, Disproven, Expired — so a reader seeing PARTIALLY_VALID in an API response would not have found it documented anywhere. The five score fields are now their real names too, with the 270 and 540-day staleness horizons that decide two of the states. **Outcome Tracking was a horizon and a grade out.** There are four horizons, not three — 7/30/90/180 — and exactly three grades: correct, partial, incorrect. "Unverifiable" was listed as a fourth grade; no such grade exists, and the underlying idea deserved better than a wrong row. A judge that cannot observe abstains, the prediction stays pending, and the abstain rate is reported as its own number rather than collapsed into a zero. **Institutional Memory documented a command that crashes.** `migrate.py down` with no version raised IndexError. The runner now says what it wants; the page shows the version. Smaller: the Elite Commander is OPV-000 in the code, not an em dash. Prompt sizes are stated as approximate and install-dependent, because they move with your skills and profile — the old page gave exact figures no install produces. New page: Continuous Integration. Home: dependency count corrected from 5 to 16 plus 2 for tests. Verified: 267 routes, 39 house and 28 council, 56 tools and all 16 named ones present, 22 skills, 14 checks, 5 migrations, 14 council members, 606 tests. All 21 wiki links resolve.

    @noreply noreply committed Jul 24, 2026
  • Add the full wiki (22 pages): getting started, architecture, memory subsystem, operations, security

    @ElmatadorZ ElmatadorZ committed Jul 24, 2026