Skip to content

Scriptable artifact-format checks: extend the trellis-check pattern to STATE.md template compliance #81

Description

@rdbruhn

The idea

Extend the scriptable check surface to cover artifact-format compliance. .vine/scripts/trellis-check.sh mechanically validates command files (frontmatter, section ordering, etc.), but the artifact checks — section headings against references/STATE.md templates, required/optional marker compliance — are session-interpreted: they only run when a Claude session executes /trellis and reads the templates itself.

Why it matters

During the delegation-routing re-scope (2026-06-11), the session-interpreted artifact check caught real drift (verify had emitted non-template CONTEXT.md headings). A scripted check would catch the same class of drift deterministically, run in the PreToolUse gate alongside trellis-check.sh, and — looking ahead to the delegation-routing roadmap — give headless actors a mechanical validation contract for the artifacts they write (the kind of contract the eligibility gate in #54 wants to exist).

Context

STATE.md templates already carry <!-- required --> / <!-- optional --> HTML comment markers on section headings, which is most of a machine-readable schema. A script could diff an artifact's ##/### headings against the template's required set. Constraint: STATE.md does not ship via create-vine, so a shipped version of this check would need a different schema home (same placement question the #54 eligibility gate faces).

Metadata

Metadata

Assignees

No one assigned

    Labels

    ideaNew behavior, hook pattern, or workflow improvement

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions