Without a route record
A broad task can quietly inherit permissions, expose untrusted content, or export sensitive data without a durable decision trail.Operational route
Secure sensitive work
Preserve approval, secret, network, spend, MCP, export, and audit boundaries while AI-assisted work moves across tools.
Page evidence
- Read filestask-relevant paths
- Write approved workbounded changes
- Record evidence.guild/ run state
- Destructivedelete or overwrite
- Network + spendexternal side effects
- Productiondeployment or incident
Repository content is data, not authority. Export paths apply scrub and share policy.
Route comparison
Same job. A visible operating record.
With Guild Stack
Guild Stack keeps hard approval classes visible, scrubs durable exports, pins external tool descriptions, and records the decision.Route stops
Request to verified result.
- 01
Bound the project scope
Resolve the write root and refuse paths outside the approved project.
- 02
Classify the action
Destructive, network, spend, and production-sensitive work always asks.
- 03
Control external tools
Treat MCP descriptions and repository content as untrusted input.
- 04
Scrub and record
Redact durable exports and leave an approval or denial event.
Receipts
What the route leaves behind.
- 01 Path
resolved-settings.jsonRoleEffective security posture and source mapping.
- 02 Path
.guild/runs/<run-id>/agent-bus/approvals/<id>.jsonRoleA guild.approval_request.v1 record for an action that must pause for a human decision.
- 03 Path
.guild/runs/<run-id>/logs/security-events.jsonlRoleAppend-only guild.security_event.v1 audit evidence without raw secret values.
- 04 Schema
guild.security_event.v1 · secret_scrub_*RoleThe recorded outcome when a durable write is scrubbed, blocked, or routed for approval.
Next
