Data model

    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.

    1

    Product event, schedule, or manual run

    Connects to Matches catalog criteria?

    2

    Matches catalog criteria?

    No: Stop and retain no mutation

    3

    Matches catalog criteria?

    Yes: Within billing and usage boundary?

    4

    Within billing and usage boundary?

    No: Stop and retain no mutation

    5

    Within billing and usage boundary?

    Yes: Deterministic analysis artifact

    6

    Deterministic analysis artifact

    Connects to Generate field-level suggestions

    7

    Generate field-level suggestions

    Connects to Suggest-only, safe-auto, or full-auto

    8

    Suggest-only, safe-auto, or full-auto

    Suggest-only: Human review

    9

    Human review

    Reject: Stop and retain no mutation

    10

    Human review

    Approve: Queue apply job

    11

    Suggest-only, safe-auto, or full-auto

    Allowed auto fields: Queue apply job

    12

    Suggest-only, safe-auto, or full-auto

    Disallowed field: Human review

    13

    Queue apply job

    Connects to ChangeLog and revert snapshot

    Model details

    Dates

    Created
    Not recorded
    Last updated
    Jul 13, 2026

    Entities

    TriggerAutomationSettingsCatalog criteriaBilling gateSEO analyzerAI generatorModeOperator reviewQueue jobAudit log