Reviewer Guidance

Reviewer Guidance is the memory of your IDP Agents. It's a set of durable, organization-wide rules the AI reviewer reads before every review — your team's standards, conventions, and accepted exceptions, captured once and applied everywhere.

Instead of re-explaining the same expectations on pull request after pull request, you teach the reviewer once and it carries that context into every future review, across every workspace in the organization.

How guidance is used

Before the agent reviews a change, InfraDots loads your organization's active guidance into the review context. The agent uses it to decide what to flag, what to let pass, and which conventions to expect — for example:

• Style — "Use for_each instead of count for multi-instance resources."
• Security — "Require encryption at rest on all storage resources."
• Policy — "Production resources must carry a cost-center tag."
• Naming — "Prefix production resource names with prod-."
• False-positive — "Public read on the marketing-assets bucket is intentional; don't flag it."
• Context — "We run all workloads in eu-central-1."

Guidance is advisory. It changes how the agent reviews, but it can never override InfraDots' destructive-change or security guardrails — you cannot teach the agent to approve a resource deletion or bypass a safety gate.

Saving guidance

Guidance is authored in the flow of work, right when you have something to teach. The Implement changes dialog keeps one-shot instructions and durable guidance in two separate fields, so per-change details never leak into a saved rule:

1. On a review that needs changes, open Implement changes.
2. (Optional) In Instructions for this implementation, add anything that should steer only the current change — these are applied now and never saved.
3. In Remember as guidance for future reviews, write the durable rule you want the reviewer to keep, then choose Continue.
4. InfraDots distills that guidance into a single, generalized rule and proposes a category. Review the draft — edit the wording, change the category, or go back.
5. Choose Save & implement. InfraDots saves the rule first, then starts the implementation — so the rule applies to this run as well as every future review.

Because the agent generalizes what you wrote, any remaining one-off specifics (a single resource name, an exact value) are stripped out, leaving a rule that reads cleanly on the next review.

Scope: organization-wide

Every saved rule applies to the entire organization — all workspaces, all teams. This is deliberate: a convention one engineer teaches shouldn't have to be re-taught for the next repository. New workspaces inherit your existing guidance from their very first review.

Managing guidance

All saved guidance lives under Organization → Agents → Reviewer Guidance, listed by category. To stop the agent applying a rule, remove it — it no longer appears in the review context on the next run.

Automation

The same guidance is available over the API for scripted management:

• GET /api/agents/<org>/memory/ — list the organization's guidance.
• POST /api/agents/<org>/memory/ — add a rule (category, content).
• POST /api/agents/<org>/memory/propose/ — distill a free-text instruction (user_prompt) into a draft rule without saving it.
• DELETE /api/agents/<org>/memory/<id>/ — remove a rule.