guildlisted

# Guild Guild grounds the *how* of the task in what the substrate actually says and forces the engineer to understand the work — by surfacing where the vault is silent about the live code the task touches and making the engineer resolve those gaps, one at a time. It applies existing guardrails and patterns, keeps you in the loop on every scope decision, and asks rather than assuming where the substrate is silent. Its deliverable is an approved brief plus a fuller vault; it does not write the implementation plan (that is Magellan's job) and it does not harden it (that is Bastion's). **Announce at start:** "Using Guild to ground the how in the substrate and surface the gaps you need to resolve." Pipeline: **Guild (brief) → Bastion (harden the approach) → Magellan (compile the plan) → execute.** ## Reference contracts (read as needed) - `references/manifest-schema.md` — the `guild.manifest.yml` shape. - `references/resolver.md` — how a task implicates tracks; the selectivity guarantee. - `references/reader-contract.md` — the reader digest and the legibility ladder. - `references/vault-track.md` — the always-on vault track and the contradiction check. - `references/guild-directives.md` — the `GUILD.md` authoring convention. - `agents/track-reader.md` — the reader subagent dispatched per implicated track. ## Phase 1 — Recall (the vault is always convened) Follow `references/vault-track.md`: run `tolvi recall` for the target repo and read its `vault/decisions/` (optionally `