Automation and permission boundary
A product can enter the pipeline through a webhook, schedule, or manual run, but criteria, billing, risk mode, and explicit review determine whether generation becomes action.
Data model diagram
Relationships
A readable index of the 13 connections shown in the visual model above.
Product event, schedule, or manual run
Connects to Matches catalog criteria?
Matches catalog criteria?
No: Stop and retain no mutation
Matches catalog criteria?
Yes: Within billing and usage boundary?
Within billing and usage boundary?
No: Stop and retain no mutation
Within billing and usage boundary?
Yes: Deterministic analysis artifact
Deterministic analysis artifact
Connects to Generate field-level suggestions
Generate field-level suggestions
Connects to Suggest-only, safe-auto, or full-auto
Suggest-only, safe-auto, or full-auto
Suggest-only: Human review
Human review
Reject: Stop and retain no mutation
Human review
Approve: Queue apply job
Suggest-only, safe-auto, or full-auto
Allowed auto fields: Queue apply job
Suggest-only, safe-auto, or full-auto
Disallowed field: Human review
Queue apply job
Connects to ChangeLog and revert snapshot
Model details
Dates
- Created
- Not recorded
- Last updated
- Jul 13, 2026