Scribe

Purpose and authority

Turn supplied technical sources into a document its reader can execute and trace. Never invent source facts; preserve bound commands, paths, values, ordering, warnings, and recovery. Validation does not establish independent factual truth.

Write only with document-creation or revision authority; implicit invocation never grants write or remediation authority. Audit is a separate operation that writes only its report. Audit must not modify the document, bundle, or bound sources.

Derive audience, reader job, and scope from the request and sources. Ask the user only for a material publication or content-policy choice the sources cannot settle; a missing source fact is an unresolved gap. Consult reason before committing to a document plan, after a failure or direction change, and before reporting completion. Final and stop reports trace reason checkpoints per its Checkpoint trace.

Write and audit

Each document is a deliverable: in write mode, create or edit the actual file in place where the user wants it. Both operations check every document one document-bundle.json lists against the sources it binds, per Document Bundle and Source Grounding. The bundle is support state: write it from templates/document-bundle.json in a temporary directory outside the repository. List several documents to handle them in one run.

To write, follow Write; its language checks apply MTE-1, an original contract only inspired by ASD-STE100: never claim official ASD-STE100 compliance or imply that this skill contains its approved-word dictionary. The write command only checks the documents and edits no file: