L19: Almanac pages for Hermes, node MCP, skills, personas and fleet wizard (HUP-S11.4) - #31
Merged
SaulBuilds merged 7 commits intoOct 5, 2026
Conversation
…the fleet wizard (HUP-S11.4) Five member-facing pages under content/core for the Citrate Core 0.5.0 release: Hermes, the node MCP server, skills and verified learning, the six personas and five tracks (owner-approved names, Operator ships as Crew), and the fleet wizard. Each page follows the STYLE_GUIDE template, carries Rule-12 frontmatter (created, branch, author, status), and links to the technical pages in citrate-core docs/ and the runtime PERSONAS.md instead of copying them (Rule 9). Status labels say Implemented (pre-audit), arriving with 0.5.0, and name what is still pending (owner sign-off defaults, packaged-app and two-machine runs). Publish after the 0.5.0 stacks merge so the linked core docs exist on main. Gates: truth-lint (--no-fetch) OK; content-lint --strict OK (0 em-dashes, 0 word findings); build-content indexes all five pages (104 pages). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
…cet (L19 review) The deploy-gate row pointed at FAUCET_IN_APP and "the deploy gate notes in the core repo". It now links the DeployGate section of src-tauri/formal/README.md and names the faucet link for what it is (deploy gas, off by default). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
…tack Stack order: main -> L04 (contracts/models precompile corrections, F-1) -> L19 (Almanac core pages, HUP-S11.4). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
The stack merge brought in L04's regenerated content.ts, which predates the five content/core pages. npm run build regenerates it anyway (prebuild); committing the regenerated file keeps the tracked copy in step with content/ (2 lines, generated by scripts/build-content.mjs). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
This was referenced Oct 5, 2026
…o (CI fix) Carries the next 16.3.8 bump and the regenerated address page up the docs stack so npm audit and truth-lint pass here too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
SaulBuilds
added a commit
that referenced
this pull request
Oct 5, 2026
Brings in the next 16.3.8 bump (clears the npm audit gate in build) and the address page regenerated from the current book. content.ts conflict resolved by regenerating it with npm run content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
SaulBuilds
added a commit
that referenced
this pull request
Oct 5, 2026
After the merge of #31 the committed page was built by the base generator and lacked the pointer to the generated precompile page. gen-addresses --check is now up to date against citrate-chain main (book 0aab474b). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
…o (genesis activation) Carries the 40204 agent precompile genesis-activation wording up the docs stack. content.ts is regenerated from the merged content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H
Matr0xshka
pushed a commit
that referenced
this pull request
Oct 5, 2026
* docs(contracts/models): corrected precompile addresses and fail-closed calls (F-1) Federation item F-1, the doc half. The model contracts no longer call the unserved 0x1000 / 0x1001 / 0x1002 addresses (citrate-chain PR 273, HUP-S7.2): - ModelRegistry registration is a record only; requestInference calls 0x0101 MODEL_INFERENCE in its native layout. - LoRAFactory training and merges run off chain and are recorded by the operator (TrainingStarted, MergeRequested, completeTraining, completeMerge); inferWithLoRA calls 0x0101 with the adapter id; on-chain LoRA arithmetic is 0x0112 LORA_APPLY / 0x0113 LORA_MERGE. - Every call goes through CitratePrecompiles, which reverts with PrecompileUnavailable instead of reading "no answer" as a result. New "Precompile calls" section: the addresses these contracts use (0x0101, 0x0106, 0x0108, 0x0112, 0x0113, 0x0121, 0x0122), what each does on 40204 today, and the behaviour before the agent precompile activation height (every call reverts; nothing changes until H, which is not scheduled). Byte layouts and gas are not copied: the section links the chain's docs/precompiles/AGENT_PRECOMPILES.md (Rule 9). Failure modes updated. Frontmatter: branch and updated added, audited_against_sha moved to the stack head fa7c913. Merge after the chain stack reaches main: until then the deployed contracts and main still carry the old constants, which the Source section says. content-lint --strict: green. truth-lint: one failure that is already on main (content/chain/_generated/addresses.md behind the 40204 book). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * fix(ci): bump next to 16.3.8 and regenerate the address page from the current book The build job failed at npm audit: next 16.3.3 is inside the range of the critical next/og ImageResponse advisory (GHSA-vcvr-r3jv-pc5j, 16.2.0 to 16.3.5). Behind it, truth-lint fails because addresses.md was generated from the 2026-09-12 book while citrate-chain main holds the 2026-09-30 book (0aab474b). Both also fail on main. package.json and package-lock.json match security/next-16.3.8 byte for byte, and addresses.md is the gen-addresses output for book 0aab474b, so a later merge of that branch adds nothing here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * docs(contracts/models): agent precompiles are active from genesis on 40204 The chain lane pinned the 40204 agent precompile activation at genesis, (40204, Some(0)), for the 2026-10-05 reroll (citrate-chain PR #273, ADR status accepted, gas schedule owner-signed). The page still said the fork height H was unscheduled and that 0x0112, 0x0113, 0x0121 and 0x0122 were not active. The table, the activation paragraph and the failure-mode bullet now say they are live from the first block of the rerolled 40204, and keep the fail-closed revert guidance for networks where the height is not reached. content.ts is regenerated to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * L19: Almanac pages for Hermes, node MCP, skills, personas and fleet wizard (HUP-S11.4) (#31) * docs(core): Almanac pages for Hermes, node MCP, skills, personas and the fleet wizard (HUP-S11.4) Five member-facing pages under content/core for the Citrate Core 0.5.0 release: Hermes, the node MCP server, skills and verified learning, the six personas and five tracks (owner-approved names, Operator ships as Crew), and the fleet wizard. Each page follows the STYLE_GUIDE template, carries Rule-12 frontmatter (created, branch, author, status), and links to the technical pages in citrate-core docs/ and the runtime PERSONAS.md instead of copying them (Rule 9). Status labels say Implemented (pre-audit), arriving with 0.5.0, and name what is still pending (owner sign-off defaults, packaged-app and two-machine runs). Publish after the 0.5.0 stacks merge so the linked core docs exist on main. Gates: truth-lint (--no-fetch) OK; content-lint --strict OK (0 em-dashes, 0 word findings); build-content indexes all five pages (104 pages). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * docs(core): Hermes page links the deploy gate model, not only the faucet (L19 review) The deploy-gate row pointed at FAUCET_IN_APP and "the deploy gate notes in the core repo". It now links the DeployGate section of src-tauri/formal/README.md and names the faucet link for what it is (deploy gas, off by default). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * chore(content): regenerate content.ts with the core Almanac pages The stack merge brought in L04's regenerated content.ts, which predates the five content/core pages. npm run build regenerates it anyway (prebuild); committing the regenerated file keeps the tracked copy in step with content/ (2 lines, generated by scripts/build-content.mjs). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H * chore(content): regenerate content.ts with the current address page Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <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
1 participant
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.
What
Five member-facing Almanac pages under
content/core/:hermes.md,node-mcp.md,skills.md,personas.md,fleet-wizard.md.docs/instead of copying them.content/_generated/content.tsthat now indexes the five pages (prebuild regenerates it anyway; the tracked copy is kept in step).Why
HUP-S11.4 (Almanac + retro): members need pages for the 0.5.0 Hermes features. The core side (g0-formal evidence, A17 amendment draft, retro draft, essay) is on citrate-core
hup/n7-docs-almanac-retro.Evidence
npm run typecheckclean;npm test110 passed / 4 skipped;npm run buildgreen includingverify:bundle;content-lint --strict0 em-dashes / 0 word findings;truth-lint --no-fetchOK; build-content indexes all pages and regenerating is a no-op after the commit.origin/main..HEAD: no leaks. No compliance-claim phrases in the new pages (disclaimer gate).Pre-existing CI blockers (not from this PR, also failing on main)
npm audit --audit-level=high: criticalnextadvisory; fixed by security: bump next to 16.3.8 (next/og ImageResponse RCE) #27.truth-lintwith fetch: generated addresses page behind the 40204 book (npm run docs:addresses).NOT done
docs/point at core main and will not resolve until the core stack merges.Owner decisions (pending owner sign-off)
docs/adr/ADR-2026-10-04-rule3-amendment-1-budget-ambiguities.md), recommended default: accept all eight readings. A-1 (nonce uniqueness vs pruning) and A-2 (taint snapshot at request build) are real choices; A-3..A-8 record what the code already does. No code change either way.External asks
None.
Playbook items
Stack (merge in this order)
hup/n7-chain-precompile-followups->main(L04, M5), L04: contract docs use the corrected agent precompiles (F-1) #30hup/n7-docs-almanac-retro->hup/n7-chain-precompile-followups(L19, M7)Prerequisites: #27 (next bump), the citrate-chain stack #270..#274 (for #30), and the citrate-core stack #190..#212 (for the links here). Main is squash-only with linear history; squash each PR in order and retarget this one to
mainafter #30 lands.🤖 Generated with Claude Code
https://claude.ai/code/session_01Lqmrq4rH9YBGCDmmemAG8H