gc-consult

Invoke the consult with your question and jurisdictions; it establishes forum, posture, and controlling dates from same-day statute or rule text, then routes through the legal_consult service or specialist agents. The output is a verdict-first memo with verified authorities and next actions.

Every load-bearing authority is re-verified against a live primary source before delivery, and anything unverifiable is labeled an unverified assumption rather than asserted. The memo opens with a method line reporting real counts of verified findings and corrected claims.

On a 503 or GC_BACKEND_UNAVAILABLE response, the workflow falls back to dispatching the in-session general-counsel orchestrator agent, which fans out to 3-5 specialist lenses and synthesizes the same memo structure. Unknown-tool errors stop the run and surface the staleness.

Use gc-redteam when a consult memo already exists and needs adversarial attack before anyone acts on it. gc-consult produces the initial strategy memo; gc-redteam runs afterward as the only adversarial check in the matter lifecycle chain.

Yes, but matter artifacts are out of scope outside the repo with the privileged matters tree. In that case the memo is delivered in the response or to a user-named path instead of being written to a matter workspace and rendered as a document package.