gtmesh explain

Prints a human-readable Markdown view of the mesh structure — what it ranks for, its sections, domain axes, the page-type → section/role/intent table, and markets — computed from gtmesh.config.yaml so it can never drift out of sync.

gtmesh explain [--json]

What it does

explain renders the structural half of what a hand-written strategy doc used to hold — but because it’s generated from the config, it’s always current. It prints Markdown to stdout; pipe it to a file when you want an artifact:

gtmesh explain > strategy.md

The business why (intent shapes, why an apex is source-less, dual-parent rationale) is judgement, not derivable — that lives in foundation/brand.md. explain covers the structure; brand.md holds the why.

It’s read-only and deterministic — the same config always renders byte-identical output.

Arguments & flags

The global options (--project, --quiet) also apply.

Reads & writes

• Consumes: gtmesh.config.yaml (optionally registry/plan context).
• Produces: Markdown on stdout. Read-only — writes nothing unless you pipe it yourself.
• Commits: nothing.

Examples

gtmesh explain                 # print the structural view
gtmesh explain > strategy.md   # keep an artifact (regenerate any time)
gtmesh explain --json          # { markdown: "…" } for a tool or the operator skill

Related

• config — edit the structure this view renders.
• doctor — lint whether that structure is healthy.
• Reference — the version-exact behaviour.