The writer & quality gate

What it is

The single step in the pipeline where a language model runs. The repo-local article-writer skill fills a scaffolded page’s body from its _brief, then hands the draft to two more skills: the humanizer and the independent, blocking review-gate. The gtmesh CLI never calls a model; the writer never touches the registry.

Why it matters

This is the firewall that keeps GoToMesh deterministic. Every networked, non-deterministic, judgment-heavy task lives in a skill — never in the engine. The CLI scaffolds the page and records its status; the writer reads that assignment and writes prose. Because the two communicate only through the page file (_brief plus content) and the registry status, you can swap the model without touching the engine, and a re-run produces the same registry.

How it works

The article-writer works one page at a time. Per page it:

1. reads only that page’s _brief and schema stubs, plus templates/<type>.md, foundation/*, and strategy.md;
2. fills the content fields and the editorial meta;
3. runs the humanizer, then self-checks with gtmesh validate <slug>;
4. invokes the review-gate as its final pre-seal step.

The review-gate scores the draft against the aeo: dimensions and thresholds in gtmesh.config.yaml (answer-block quality, self-containment, structure, specificity, first-party sourcing) and enforces the house voice. A page passes only when every dimension clears its bar, the weighted overall clears overall_threshold, and there are no blockers. On failure the page stays in writing with notes; on pass control returns to the writer.

Key files & flags

Related

• seal — validates and stamps the built hashes
• validate — the writer’s schema + lint self-check
• Page types & schemas — the contract the body fills
• Walkthrough — where this step sits in the flow