Pumpkin executes. QuietLens BI investigates. Both run through the same operating model — intake, scope, plan or investigate, validate, approve, execute or answer, audit.
Step 01
Pumpkin reads a scoped ticket from Jira. QuietLens BI reads a plain-language question from a business user. Both arrive with the requester, workspace, and access context attached.
Outputs: parsed scope, requester + workspace, access policy
pumpkin.intake: JIRA · DATA-2074 lens.intake: "Why didn't finance get the daily revenue report?" actor: finance lead · workspace: revenue-ops
Step 02
Each run is bound to approved sources, repositories, semantic metrics, and short-lived credentials. Nothing outside the approved surface is reachable.
Outputs: repo + path scope, metric + source scope, least-privilege creds
pumpkin.scope: warehouse-models/billing/* lens.scope: vw_revenue_daily · Airflow · dbt creds: sts · 15 min · read-write fact_invoice
Step 03
Pumpkin produces a step-by-step execution plan with risks and validation. QuietLens BI runs the investigation across connected systems and assembles an answer with lineage.
Outputs: execution plan, investigation trace, risk signals
pumpkin.plan: 6 steps · risk=medium lens.trace: Airflow → dbt → Snowflake → Power BI lens.lineage: raw.invoices → fact_invoice → vw_revenue_daily
Step 04
Validators run before anything is exposed. Pumpkin checks schema, row counts, and policy. QuietLens BI verifies sources, freshness, ownership, and confidence.
Outputs: validation log, confidence + freshness, ownership map
pumpkin.validate: schema · row_count · referential lens.confidence: high · 4 corroborating sources lens.ownership: data-platform · on-call J. Patel
Step 05
Production changes wait for a reviewer. Business actions like raising a ticket or escalating to engineering require explicit confirmation with the evidence pack attached.
Outputs: approval record, evidence pack, reviewer assignment
pumpkin.approval: pending · data-platform-on-call lens.action: raise INC-4421 · confirm evidence_pack: scope · trace · validators
Step 06
Pumpkin opens the PR or applies the controlled change. QuietLens BI returns the answer and creates the ticket. Both record the run end-to-end for audit.
Outputs: PR or ticket, audit timeline, rollback path
pumpkin.pr: qn/data-2074 → #318 opened lens.ticket: INC-4421 created · assigned audit: scope · plan · validators · approval · output