✍️ Contribute — fork and write

This is a federated wiki: you may fork any page to your own site and write on it. Your fork remembers where it came from (the journal is the lineage), so improvements can flow back without losing attribution.

To read or reuse

Fork any page (skills, tomes, conjectures, graph nodes) into your own wiki or materialize it as a local file. The upstream: field and footer on every page tell you where the source of truth lives.

To contribute back

Edits made on a fork can be proposed back into the agentprivacy git canon. Contributions pass the G7 fork-back gate: a coherence check (does it agree with the conjecture register and grimoire?), an attribution check (is authorship clear and licensed?), and a First-Person sign-off before anything merges. See Distribution Gates.

What stays sealed

Working chronicles, plans, drafts, version-history, and audits live only in git — they are the Archive, not the Library. The wiki carries the circulating canon, not the internal record.

← Welcome Visitors · Federation Map · Distribution Gates

Private knowledge, time and resources

A public correction follows the fork-and-review path above. A scoped consultation, permissioned reference or resource pledge can begin at Labs. Agree recipient, permitted uses and evidence before sharing private context. A pledge does not transfer knowledge ownership or bypass publication gates. See Community resources and trust tasks.