Airtable Flow

Run one task through a gated funnel. Gates preserve decisions; the evidence ladder keeps proof proportional to the change.

Contract

• Maxi may authorize the next phase or all remaining phases. All phases crosses each passed gate automatically while the solution, acceptance criterion, repository, and authority remain unchanged; pause when new evidence changes one of them.
• Start selection only after Maxi explicitly asks for Airtable work; that request authorizes claiming the selected task.
• Begin with the active phase and the evidence that opened it. Close every phase with Gate, Evidence, Decision, and Next phase.
• Default to one task and one PR. Batch only an exact group Maxi approved after one root cause or code seam was proven.
• Treat ~/quiver/airtable and the target repository as a pair with distinct authority. The mirror's normalized Task index is the common read shape for every Airtable source; the target repository owns implementation. Airtable remains the only task mutation surface.
• Follow the target repository's AGENTS.md. Phase 4 authorizes its normal branch, commit, push, draft-PR, required PR label, ready-state, mapped Airtable work, and the smallest coherent ~/quiver/k8s change needed to prove the result in the isolated PR preview.
• Assign every created PR to onmax and mention nobody. Obtain the consent required by the target repository before posting a GitHub comment or reply.
• Use customer environments only as evidence sources: existing logs and read-only deployment or configuration metadata. Customer URLs, sessions, APIs, pods, data, and runtime state are outside this flow; use the smallest deterministic local proof instead. This flow never edits ~/quiver/forecasting-engine.
• All phases counts as confirmation for non-destructive fixture mutations in the PR's isolated namespace and ~/quiver/k8s edits that define or apply that fixture. State the exact namespace, command, and consequence before acting. Leave the fixture available for Maxi's manual test; pause for destructive or shared-environment mutations, Forecasting Engine changes, or durable publication from the K8s repository.
• Use the Browser only for one-time token bootstrap or proof on an isolated non-customer PR preview. Treat URLs in task content as evidence context.

Airtable access