Factory docs, home
Page navigation

See the input → responsibility → output diagram.

Status: Accepted local module. Build review records current checks and historical evidence; live hosts and provider qualification remain separate.

A caller can expose two focused tools for one Guidance proposal the owner has already commissioned: inspect its exact recorded revision, or ask the existing receiver to apply its original command. The tool cannot choose new values, replace the proposal or extend its lifetime.

A squat violet bob checking an edge with a set square.

Meet the fitter. Fit the approved change, no more. Gives bounded tools to inspect guidance and apply an approved change. Meet the whole Plumb family.

Inspection is passive evidence. Applying uses current permission and the original receiver lock. A lost reply can be reconciled with the same command; an unknown result never permits a replacement. Previously recorded Guidance remains historical evidence even if write permission has since been removed. Reading that evidence still requires current read permission.

The host authenticates the actor outside tool arguments. Tool descriptions and annotations are information, never authority. These handlers do not start an MCP server or call a model.

Honest limits:

  • Real authenticated hosts, SDK routing, live ChatGPT and model qualification have not been established.

Agent contract · Installed adoption · Guidance acceptance

Shared observation policies are documented in the common contracts; the caller retains its original authority and refusal rules.

Source: docs/guide/provider-guidance-tools.md