gtmesh seal
Validates a drafted page and, only if it’s clean, moves it from writing to review and stamps its provenance hashes.
gtmesh seal <slug> # validate, then writing → review
gtmesh seal slug-a slug-b # seal several pages at onceWhat it does
seal is the checkpoint at the end of writing. It runs schema validation (ajv) plus the deterministic editorial lints, and only succeeds if the page is schema-valid AND lint-clean — a page that fails either cannot seal. On success it moves the page to review and stamps the three provenance hashes (built_content_hash / built_projection_hash / built_schema_hash) that make later registry-to-registry diffs precise.
It’s the same validation gtmesh validate runs as the writer’s self-check — seal just adds the status move and the hash stamp.
After image placement, a page re-enters a light re-seal: the image-director skill runs gtmesh amend <slug> (→ needs_update), then you seal again to re-validate with assets present and re-stamp the body hash.
Arguments & flags
| Argument | Description |
|---|---|
<slugs...> | Page slugs to seal (one or more) |
No command-specific options.
Reads & writes
- Reads: the page, its schema, and the editorial rules.
- Writes: status →
review; the three built hashes (built_content_hash/built_projection_hash/built_schema_hash) in the registry.
Examples
gtmesh validate /glossary/idempotency # the writer's self-check (no status move)
gtmesh seal /glossary/idempotency # only if valid AND lint-clean → reviewRelated
- Platform: The writer & quality gate, Page Registry
- Guide: Lifecycle & reconcile, Walkthrough
- CLI:
gtmesh validate,gtmesh publish