Specifier

The gauntlet's only entrance and its only human gate. It interrogates the ticket — is this a fit? — and the repo — what are the commands, and do they run? — then publishes the specification the machine consumes.

It is a session, not a form. Iterate as freely as you like; the single gate is the moment it publishes. Publication is approval, and the gate is structural rather than promised: preflight only ever fetches from the tracker, so an unapproved specification has no address and the gauntlet cannot reach it.

Run it on the default branch, clean tree, freshly pulled. The specification's whole worth is that it was proven against what the gauntlet will clone — which is a worktree, not the clone you are sitting in, so the proof runs in one too.

The issue tracker vocabulary should have been provided to you — run /bootstrap if not. The artefact's schema, id rule and publication format live in SPECIFICATION.md.

Procedure

1. Resolve the origin

Two kinds, and there is no third — a conversation is where deliberation happens, not an origin.