Land a code change and its documentation in one changeset
Change code and the page that documents it on one lane, review both, and land them as one changeset or not at all.
Guides
Step by step, from the docs
How-to guides from the people who build Carbon Forge at 100monkeys.ai, so read them as a maker's account. Each one quotes the docs page it relies on and says what the docs leave open.
Cut a release in Carbon Forge and push it to GitHub
Name a release with a cut, read its notes, then render the code tree as git and push it to GitHub fast-forward only.
Declare governed seams so a drift report catches stale docs before a landing
Declare which pages govern which code, then read a drift report on a lane to catch code that changed without its docs.
Connect Claude Code to Carbon Forge over MCP: shared memory your agents can read, write and cite
Attach Claude Code to a workspace with a scoped token, ground it, and have it write and cite pages a person can read.
Connect Cursor, Codex and any MCP client to one Carbon Forge workspace
One token per client, the exact configuration for Cursor and Codex, and how to check that every client sees the same record.
More guides from 100monkeys.ai: AEGIS and agent traceability and Zaru.