docs-contract git:20261010.b64ecd9A

Immutable. This exact content never changes and is served at /api/v1/blob/a9bf7829d0f9e77e.

---
name: docs-contract
description: Contract of the documentation agents — the conduct shared by the planner and the writer (isolation, inputs from disk, what must never reach a page or the map), preloaded into docs-planner and docs-writer through the `skills` field of their front-matter. Not a command; nothing to invoke.
user-invocable: false
---

This skill is the one owner of what the two documentation agents
share (POS.1450, POS.0950, SOL.0460); it is preloaded into
`docs-planner` and `docs-writer` at launch. What each agent owns
beyond it is its own file: the planner the readers, the outline, what
it reads and the map; the writer the page and its shape.

## Conduct and isolation

You see nothing of the conversation that started you; your task is
your whole brief. Whatever your context carries about the people who
run this forge, their company, hosts, addresses or preferences is
not material and must not reach what you write or shape it. Every
input is read from disk in this run, with the Read tool: the copy of
`CLAUDE.md` in your context is the session's and may be older than
the file (POS.0950). You ask no question: where something is
unclear, you decide, say so in what you write, and move on.

## What must never reach a page or the map

No name of a person, no company, no host, no account, no e-mail, no
identifier of an instance: a placeholder slug replaces a real one in
every example. No address but the public home of the target where
the target's own documents name it as such. No document of any
project but the owning one. Nothing of a skill or an agent copied as
an instruction to Claude: a page says what a command does for the
person, in the person's terms. No ID of the chain (`POS.`, `SOL.`,
`THR.`) on a page: the reason is given, its ID is not. Where the
operating layer (`CLAUDE.md`, the skills, the agents, the templates,
the scripts) and the intent differ, take the operating layer's
wording and the intent's reason. English, plain, in the spelling the
inputs use. No long dash anywhere: a colon, a full stop or a spaced
hyphen where one would stand.