Decision Interface Spec (DIS) — One Page

Purpose
Write this for ONE workflow where AI is used (or will be used) to draft, recommend, or execute work. The goal is to replace “alignment” with explicit decision boundaries and an audit trail.

1) Workflow Name
- Name:
- Owner (single accountable person):
- Systems touched (e.g., Zendesk, Gmail, GitHub, AWS, Stripe):

2) Decision Boundary
Define exactly what the system can do.
- Allowed actions (draft/recommend/execute):
 - 
 - 
- Explicitly disallowed actions (hard no):
 - 
 - 
- Required human review (what must be approved before it leaves the building or hits prod):
 - 

3) Inputs and Data Rules
- Approved data sources (links or system names):
- Prohibited data (PII categories, secrets, regulated data, internal-only docs):
- Retention rule (what is stored, where, for how long—if unknown, state “TBD” and assign):

4) Permissions (Least Privilege)
- Identity used by the system (service account name):
- Tokens/keys location and rotation owner:
- What the system can read:
- What the system can write:

5) Guardrails (Hard Gates)
Pick at least one gate you can enforce now.
- Gate type (examples): code-owner approval, CI must pass, two-person rule, ticket required, staging-only, spending cap
- Gate implementation location (GitHub rules, CI pipeline, IAM policy, admin console setting):

6) Logging and Audit Trail (Non-Negotiable)
Record the chain of custody.
- What must be logged (minimum): input reference, output, approver identity (if any), timestamp, destination
- Where logs live (system of record):
- Who reviews logs and how often:

7) Escalation and Rollback
- Escalation triggers (examples: customer complaint, security finding, policy violation, monitoring anomaly):
- On-call / responder group:
- Rollback plan (how to undo changes or stop the workflow fast):

8) Quality Checks
- Definition of “good” output (concrete):
- Known failure modes you expect (hallucinations, tone, wrong data, policy conflict):
- Review cadence and who attends (weekly 30 min is enough):

Sign-off
- Engineering owner:
- Security/privacy owner:
- Legal/compliance owner (if applicable):
- Date effective:

Rule: If it can take an action, it needs a boundary, a gate, and a log.