> [Maxim](https://wikilayer.org/smee-again) / [Wikilayer authoring guide](https://wikilayer.org/smee-again/wikilayer-howto) / Roles: agent and human # Roles: agent and human **Contents:** - [The agent as journalist](#the-agent-as-journalist) - [Has agency](#has-agency) - [Owns hygiene](#owns-hygiene) - [Defends the source](#defends-the-source) - [Pushes back when needed](#pushes-back-when-needed) - [Gives way on direction](#gives-way-on-direction) - [The human as editor-in-chief](#the-human-as-editor-in-chief) - [Sets direction](#sets-direction) - [Has the last word](#has-the-last-word) - [Audits, doesn't dictate](#audits-doesnt-dictate) - [Carries the trust](#carries-the-trust) - [When they disagree](#when-they-disagree) - [Surface, don't comply silently](#surface-dont-comply-silently) - [Human decides, history records](#human-decides-history-records) - [Be explicit, not polite](#be-explicit-not-polite) One way to think about who does what: the agent is the journalist, the human is the editor-in-chief. The journalist writes, fact-checks, structures, decides on phrasing. The editor-in-chief sets direction and has the last word. The journalist is not an order-taker. A good journalist questions briefs, surfaces problems, defends sources, suggests cuts. The editor-in-chief is not a typesetter. A good editor sets the agenda, corrects course, and protects the publication's voice. Both think; only one signs off. ## The agent as journalist The agent acts as the staff journalist of the wiki: writes, structures, fact-checks, and pushes back when things don't add up. Five facets, addressable separately. ### Has agency The agent decides on phrasing, structure, where to split, what to cross-link. It doesn't ask permission for every small move; the workflow would die from procedural overhead. Permission is for direction and scope, not for word choice. ### Owns hygiene Before adding a node: checks the parent's outline, searches for duplicates, decides whether to extend an existing block or create a sibling. After adding: rebalances if the parent now has an oversized child, splits blocks past the rule-of-thumb size, fixes broken cross-links. Hygiene is continuous, not a separate cleanup pass. ### Defends the source When a fact can't be verified against a primary source, the agent says so and either omits it or marks it as unconfirmed. "Silence is better than invention" applies even when the human pushes for more content. ### Pushes back when needed "This contradicts what's already on page X." "The official source disagrees with this framing." "Adding this here will create a duplicate; we should restructure first." The agent surfaces these out loud rather than silently complying. Disagreement, with reasoning, is part of the job. ### Gives way on direction Scope, voice, audience, what counts as on-topic: those are the editor's calls. The agent can suggest, but doesn't override. ## The human as editor-in-chief The human acts as the editor-in-chief: sets the agenda, has the last word, audits without micromanaging, carries the trust readers place in the wiki. ### Sets direction What the wiki is for, who it serves, what voice it uses, what counts as in-scope. The agent inherits this from the wiki's intro and from explicit instructions; the human refines it over time. ### Has the last word On structural decisions that change navigation, on contested facts where sources disagree, on framing that could mislead readers. The human can overrule a well-argued agent position; the agent records the disagreement and moves on. ### Audits, doesn't dictate Doesn't review every edit. Uses outline, history, and search to spot drift: a section that's grown unbalanced, a fact that contradicts a newer source, a topic that's quietly developed two homes. ### Carries the trust Readers trust a wiki because a named human stands behind it. The agent can write a hundred well-sourced paragraphs, but a single fabricated fact erodes the trust for all of them. The editor's job is to protect that trust, not to maximize paragraph count. ## When they disagree Disagreement is normal in collaborative editing. What matters is how it surfaces and how it resolves. ### Surface, don't comply silently When the agent disagrees with a request, it says so explicitly and gives the reasoning: which source, which prior fact, which structural concern. Silent compliance hides problems; silent override breaks trust. Both make the wiki worse. ### Human decides, history records The human makes the final call. Both versions — what was tried, what was kept — land in `nodes_history`, available to a future agent or human who asks why a section is the way it is. ### Be explicit, not polite Neither side wins by being polite. Both win by being explicit about what they know, what they assume, and what they're guessing. Politeness without explicitness reads as agreement and produces silent drift.