Agentprivacy Wiki Sync

agentprivacy-wiki-sync

Project the agentprivacy canon (many git repos) into a federated, forkable wiki: a guide hub (guide.agentprivacy.ai) that rosters one sibling subdomain wiki per canon source. Built local-first as ~/.wiki/<host>/ farm hosts; going public is just forking the host up (or DNS-mapping the farm) — localhost → the agentprivacy domain, no structural change.

Golden rule: the git repo is always the source of truth. The wiki is a projection that carries lineage. The Librarian forks; the Archivist never copies.

The model

guide.localhost  ← the hub (build-guide-host.js): index · federation-map · distribution-gates · contribute
   ├─ skill.localhost     ← agentprivacy-skills-v5
   ├─ tomes.localhost     ← cityofmages/tomes
   ├─ research.localhost  ← agentprivacy-docs
   ├─ atlas.localhost     ← spellweb/src/data  (the graph — the hyperlink backbone)
   └─ library.localhost   ← agentprivacy_master/public  (the 5 narrative spellbooks)

Serve all hosts: "$HOME/AppData/Roaming/npm/wiki" --data ~/.wiki --port 3030 --farm (use the ABSOLUTE wiki path — a bare wiki exits 127). Log: ~/.wiki/_farm.log. Each host = pages/<slug> + assets/<slug>/<file> + status/owner.json ({name:"<owner>",friend:{secret:"<friend-secret — never commit the live value>"}}).

The area registry — everything to sync (NAME ALL AREAS HERE)

Status: ✅ done · ◻️ gap (public canon not yet federated) · 🔒 sealed (never federate) · ♻️ dup (never double-federate).

When adding an area: append a row here first, then build it. Naming a thing in this table is step zero of syncing it.

The distribution gates (G0–G7)

Out (git → wiki): G0 source-of-truth (git upstream) · G1 classify circulating vs sealed · G2 coherence (numbers/tiers/versions match register+grimoire) · G3 attribution (upstream/author/license; vendored credited) · G4 projection altitude (link down to source, don't dump) · G5 hyperlink coherence (links resolve; from the graph edges) · G6 distribution topology (right site, canonical slugs, no collisions). Back (wiki → git): G7 fork-back — coherence + attribution + First-Person sign-off (OPEN→SIGNED); propose a diff, never auto-commit.

The process (per area — the 8-step loop)

1. Manifest (G1) — NON-OPTIONAL. Enumerate the source dir; mark every file circulating or sealed. The leak and the gaps both came from skipping this. Default-seal chronicles/plans/drafts/audits/version-history.
2. Map. Slug + title per file; resolve cross-links (intra-site [[ ]], cross-site reference items).
3. ⊥check map. Adversarially verify classification + coherence against the repo + grimoire/register.
4. Generate. Run the converter → page JSONs + staged assets/<slug>/<sourcefile>.
5. Hyperlink. Inject nav footer + hub rosters + cross-links.
6. ⊥check build. Slug-collision + link-integrity + orphan sweep (script below) BEFORE serving.
7. Serve. Write into ~/.wiki/<host>/; the farm rebuilds the sitemap on next request.
8. ⊥check live. Read the live wiki; confirm sitemap count, assets 200 text/markdown, links resolve, and no sealed slug leaked (leak-scan below). For structured data (register, graph) a deterministic re-parse beats an agent; for prose/lore use an Explore agent to map live↔repo. SIGN (chronicle) only when clean.

Conventions (do these every time)

• slug = slugify(title) (t.replace(/\s/g,'-').replace(/[^A-Za-z0-9-]/g,'').replace(/-+/g,'-').toLowerCase()), and choose unique, readable, self-namespacing titles so roster/footer [[title]] links always resolve.
• THE BIJECTION RULE (2026-08-03 ruling, after a fedwiki.club bug report): the page's stored slug MUST equal FedWiki's own asSlug(title) = t.replace(/\s/g,'-').replace(/[^A-Za-z0-9-]/g,'').toLowerCase() — downstream code (share links, <slug>.html static export, forks) assumes title↔slug map to each other. Consequences: titles must be ASCII-clean (no emoji — "Archer 🗡️🎯" slugs to archer- with a trailing dash; put emoji in the story-card heading instead), no title-vs-filename divergence (agentprivacy-guild-efficiency file with title "Guild Efficiency" broke fedwiki.club link-gen). build-all.js now has a bijection lint that fails the build on any violation — never push pages that fail it. Rename map for the 2026-08-03 mass fix: ~/.wiki/skill-fedwiki/rename-map.json; club repair script: club-fix.js.
• Cross-site links = a FedWiki reference item {type:'reference', site:'<host>', slug, title, text} — NOT a bare [[ ]] (those resolve same-site only). Add a cross-site ref ONLY if the target page already exists.
• Neutralise source-body [[ ]] before converting — canon prose (RPP gates etc.) uses [[ ]] as content; it collides with wikilinks. Strip to plain text, then add your own links.
• Assets keep the original source filename (assets/<slug>/01-the-single-button.md), not <slug>.md.
• Attach each page's source file as a # Assets heading + {type:'assets', text:slug} item.

Tooling (~/.wiki/skill-fedwiki/)

• skill-to-fedwiki.js — buildPage({srcPath,slug,title,navText,assetsSlug}) module + frontmatter/section split.
• build-all.js (skills) · build-tomes.js · build-research.js · build-atlas.js — per-source orchestrators.
• build-local-host.js <host> — materialize staged pages+assets into a farm host.
• build-guide-host.js — the hub; flip a site's SITES[].status to LIVE + re-run to roster it (and emit its cross-site tileglyph tile + reference).
• link-tomes-research.js — idempotent post-pass wiring act↔conjecture cross-site links (re-run after a rebuild).
• add-family.js — idempotent post-pass binding all hosts into a family: injects a roster item (categories Hub=guide · Sister sites=the four) into every welcome-visitors, so each site rosters its sisters and can pull the whole family into the neighbourhood. Re-run after a rebuild (welcome-visitors is regenerated).
• log.js <op> <detail> — append a greppable entry to log.md (## [date] op | detail; the LLM-Wiki log).
• file-answer.js "<title>" [content.md] — file a good answer back into the wiki as a synthesis note (notes/<slug>.md + a log.js note entry) so explorations compound (the LLM-Wiki "answers filed back" op).
• build-guide-extras.js — idempotent post-pass: publish log.md → Federation Log, notes/*.md → The Notes, and AUDIT.md → Federation Audit on the guide, + a Log & Notes section on welcome-visitors.
• audit.js — the lint op: reads every host → page counts · broken links · leak-scan · orphans · cross-site refs → writes AUDIT.md + a lint log entry + a PASS/WARN table. Reads only. (Non-zero broken/leaks are usually benign in-content [[ ]] examples or false-positive candidates — the report says so; confirm before acting.)
• resync.js [area...] — one-command auto-sync for a research turn. Runs forkback (report contributions first) → the chosen area builders (default: all) → link-tomes-research → add-family → audit → build-guide-extras. A research turn that touched only research = node resync.js research. Full re-sync = node resync.js. This is the run order; resync.js encodes it.
• make-favicon.js — per-host colour-identity favicon flag.
• forkback.js <host> — the G7 gate: detect external contributions (current story diverges from the create journal snapshot, or post-create journal actions exist) and print each as an [OPEN] proposal for First-Person sign-off. Reads only — never writes to git or the wiki. Run before re-building a host (a rebuild overwrites contributions); fold signed changes into the source repo by hand (page→repo is a lossy projection).
• push.js / push-assets.js — public push (action API / WebDAV) — parked; user pushes to the domain manually.

Verify recipes

# sitemap count for a host
curl -s -H "Host: <host>.localhost" http://localhost:3030/system/sitemap.json | grep -o '"slug"' | wc -l
# link integrity (run in ~/.wiki/<host>): 0 broken expected (in-content example [[ ]] are benign)
node -e 'const fs=require("fs");const S=t=>t.replace(/\s/g,"-").replace(/[^A-Za-z0-9-]/g,"").replace(/-+/g,"-").replace(/^-|-$/g,"").toLowerCase();const F=fs.readdirSync("pages"),X=new Set(F);let b=0;for(const f of F){const p=JSON.parse(fs.readFileSync("pages/"+f));for(const it of p.story){if(it.type==="reference")continue;for(const m of (it.text||"").matchAll(/\[\[([^\]]+)\]\]/g))if(!X.has(S(m[1])))b++;}}console.log("broken:",b)'
# leak scan — sealed content that slipped in (verify hits are false positives like a Chronicler persona)
curl -s -H "Host: <host>.localhost" http://localhost:3030/system/sitemap.json | grep -oE '"slug":"[^"]+"' | grep -iE "chronicle|draft|plan|audit|candidate|presync|\.bak"

Gotchas (learned the hard way)

• Manifest-first or it bites you: firehosing a whole repo/graph leaks internal nodes (3 chronicle nodes rode the spellweb graph into atlas — now sealed by type:chronicle/label:/^Chronicle/). Spine-only passes under-federate (research got 6 of ~100 docs).
• dist/spellweb/nodes.json is a stale 16-node artifact — parse src/data/*.ts.
• Cast sigil may carry a parenthetical note — take the glyph only, or slugs break.
• Leak-scan false positives: chronicler (the persona), spec-vertex-naming-audit (canonical spec), "plan" inside "plane". Always confirm a hit is real before sealing.
• Browser extension is offline here — tileglyph tiles / favicon flags can't be visually verified; check the item JSON, not the render.

Verify: agentprivacy.ai · plan ~/.claude/plans/moonlit-stirring-lagoon.md · coverage audit agentprivacy_master/docs/chronicles/2026-06-27_federation_coverage_audit.md