docs(wiki): audience-segmented wiki, FL×DT design docs, and wiki-sync recipe#45
Merged
Conversation
… recipe The GitHub wiki was a one-line stub. This establishes docs/wikis/ as the source of truth (mirrored to the forge wiki, never edited in the wiki UI) following the convention already used by the sibling gossamer project. Wiki (docs/wikis/) — signpost pages that orient each audience and link the canonical docs rather than duplicating them: Home, User, Developer, Maintainer, Lay-Public, Glossary, README.adoc Design docs (docs/design/) — the canonical depth the wiki points at: mind-management-plan.md product + engineering synthesis flyinglogic-devonthink-integration.md the settled FL×DT architecture flyinglogic-devonthink-proofs.md proofs + proof-obligation ledger Justfile: add `just wiki-sync [dry]`, mirroring gossamer's recipe. It clones the wiki remote (NEXIA_WIKI_REMOTE overrides), copies docs/wikis/*.md, and pushes a commit stamped with the code repo's short SHA so every wiki page traces to the revision it came from. README.adoc stays repo-only. Also adds the missing CC-BY-SA-4.0 SPDX header to mind-management-plan.md. All 34 repo paths and 6 internal page links referenced by the wiki verified to resolve; `just must-check` green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🔍 Hypatia Security ScanFindings: 68 issues detected
View findings[
{
"reason": "Issue in scorecard.yml",
"type": "missing_workflow",
"file": "scorecard.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
Verified against the code rather than TOPOLOGY.md, which is stale: claim TOPOLOGY/wiki reality λδ substrate "planned" built (#35, #36, #43 merged) core size ~623 LOC, 12 tests 5,344 LOC, 90 tests green λδ is the largest subsystem in the core (~4,050 LOC, ~76%): reader, value model, evaluator + Budget, hygienic macros, multimethods, prelude, and the notebook host seam. Calling it "planned" materially misrepresents the project to every audience the wiki serves. - Home.md: substrate row planned -> built; status paragraph now cites measured figures and flags that TOPOLOGY.md predates the three LambdaDelta merges. - Developer.md: add the λδ substrate as a first-class stack layer; Track A marked substantially landed, with the outstanding work named (.ld packages, surfacing L2+ through the disclosure ladder). Toolchain verified end-to-end while checking this: `just build-wasm` (with wasm-bindgen-cli 0.2.126, matching Cargo.lock), `just build`, and `just test` all green — 90 Rust + 10 UI tests, including "TEA update delegates to the wasm core". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🔍 Hypatia Security ScanFindings: 68 issues detected
View findings[
{
"reason": "Issue in scorecard.yml",
"type": "missing_workflow",
"file": "scorecard.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in dogfood-gate.yml",
"type": "missing_timeout_minutes",
"file": "dogfood-gate.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
hyperpolymath
marked this pull request as ready for review
July 16, 2026 21:22
hyperpolymath
added a commit
that referenced
this pull request
Jul 17, 2026
…fix the Justfile (#46) ## Why `TOPOLOGY.md` predated the three LambdaDelta merges (#35, #36, #43) and never mentioned λδ. Because it is *the* status source, every downstream doc inherited its stale figures — including the wiki landed in #45. This re-derives the countable facts from the tree and corrects the cascade, then fixes the Justfile gaps found along the way. ## TOPOLOGY was understating the project on six axes | Claim | Reality | |---|---| | λδ absent entirely | **Built, not planned** — reader, value model, evaluator + Budget sandbox, hygienic macros, multimethods, prelude, host seam. ~3,400 LOC excl. tests, **~64% of the core**, its largest subsystem. Now its own dashboard row | | "12 passing unit tests" | **90** (81 unit + 3 exchange + 2 golden + 2 property + 2 doc) | | WASM bridge "40%, in progress" | **Wired and exercised** — `Main.res` loads the wasm at boot, `WasmStore` binds 21 of 31 exports, ui-ci runs a TEA↔WASM contract test against the real bundle | | CI "10%, landing in a parallel workstream" | `rust-ci.yml` + `ui-ci.yml` **load-bearing since #22**, SHA-pinned, green on main | | Web/PWA "no service worker yet (planned)" | Service worker + webmanifest + icon **ship and are registered** (`Main.res:88`, #27) | | UI "no drag-and-drop; GraphView placeholder" | Note drag **implemented** (`View.res:397`); GraphView renders a circular layout | **Overall ~35% → ~65%.** The critical path has **moved off the WASM bridge onto the UI surface**: 10 exports are unbound in ReScript, including both λδ entry points (`lambdadeltaEval`, `evalLambdadelta`) — the substrate is reachable from JS but nothing calls it. Also corrects **a mixed-basis error I introduced in #45**: λδ was reported as "~76% of the core" by dividing 4,049 LOC (*with* tests) by 5,344 (*without*). Like-for-like it is 3,407/5,344 = **~64%**. ## Justfile - **`just test` could not work on a clean checkout** — the UI tests import generated `*.res.js` and the wasm bindings, so type-check failed with 4 `TS2307` errors. Now `test → build → build-wasm`. Warm no-op costs ~0.45s, so it is not a tax on the inner loop; added `test-rust` for the Rust-only loop. - **`just check` was weaker than CI** (no `--all-targets`, no `--features wasm`, ran from `core/`) — it could pass locally while CI failed. Now mirrors `rust-ci.yml` exactly. - **`just doctor` ignored the wasm toolchain** — the one thing that actually blocks the browser build. Now checks the wasm32 target and compares the wasm-bindgen CLI against `Cargo.lock`, printing the exact fix command on drift. - **`crg-grade` and `crg-badge` were dead on arrival** — Make-style `$$(...)` under just/sh expanded `$$` to the shell PID, so `(` was a syntax error. They failed 100% of the time. Rewritten as bash shebang recipes. ## Verification - `just check` — pass (now compiles the `wasm` feature, which the old one never did) - `just test` from a **fully cleaned tree** (no `web/wasm`, no `*.res.js`) — rebuilds and passes **90 Rust + 10 UI** - `just doctor`, `crg-grade` (→ `D`), `crg-badge` — all run; doctor's FAIL path verified by hiding wasm-bindgen from `PATH` - `asciidoctor` renders README/ROADMAP/QUICKSTART-DEV clean; `just wiki-sync dry` still previews correctly ## Deliberately not done — needs your call - **`READINESS.md` grade D is probably stale.** All three *Path to C* criteria now appear met (product CI on every PR ✅, UI tests in CI ✅, WASM bridge built + smoke-tested ✅). The grade is assigned by audit, so I corrected the facts and flagged a re-audit rather than self-promoting. `just crg-badge` publishes that letter, so the badge is currently understating the project. - **`must-spdx-headers` is a broken gate** (pre-existing, untouched here). It runs `find . | head -20`, so it checks an arbitrary, readdir-order-dependent fifth of the tree *and* walks vendored `node_modules/`. It currently fails on `@rescript/react`'s own `.res` files — **every tracked source file does have SPDX**. Worse, `contractile.just` has drifted from its source: `contractiles/must/Mustfile.a2ml` contains no `spdx-headers` rule at all, and its `no-hardcoded-paths` rule (severity: **critical**) is missing from the generated file. The `contractile` tool isn't installed to regenerate, and this is your standards ecosystem — so I left it alone. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



The GitHub wiki was a one-line stub ("Welcome to the nexia-list wiki!"). This establishes
docs/wikis/as the source of truth, mirrored to the forge wiki — the convention the sibling gossamer project already uses. Edit the Markdown here, never in the wiki UI.What is here
Wiki (
docs/wikis/) — signpost pages that orient each audience and link the canonical docs rather than duplicating them:Home,User,Developer,Maintainer,Lay-Public,Glossary, plus a repo-onlyREADME.adoc.Design docs (
docs/design/) — the canonical depth the wiki points at:mind-management-plan.mdflyinglogic-devonthink-integration.mdflyinglogic-devonthink-proofs.mdjust wiki-sync [dry]— mirrors gossamer’s recipe. Clones the wiki remote (NEXIA_WIKI_REMOTEoverrides), copiesdocs/wikis/*.md, and pushes a commit stamped with the code repo’s short SHA, so every wiki page traces back to the revision it came from.README.adocstays repo-only.How it fits the existing repo
The wiki is pinned to what is actually true today rather than to the plan: TOPOLOGY’s ~35% MVP and readiness grade D, the real ADRs, the real Justfile recipes, and the
.machine_readable/contractiles. The architecture spine it documents is the one the code already proves withNotebook::backlinks— a derived, rebuildable index beside the notes, never trusted from disk.Verification
just must-checkgreen;just wiki-sync drypreviews cleanly against the live remote..machine_readable/6a2/, Justfile recipe names, READINESS grade D).mind-management-plan.md.Note
Draft — nothing has been published to the forge wiki. Merging this lands the source of truth; running
just wiki-syncis the separate, deliberate publish step.🤖 Generated with Claude Code