0-Error Compute - Quick Reference
0-Error Compute - Quick Reference Card
Print this. Keep it visible. Use it for every task.
The Core Rule (5 SECONDS)
THINK → VERIFY → CODE
Don’t skip steps. Don’t think fast. Think completely, verify completely, then code.
Before Every File Edit (6 STEPS - 5 MINUTES)
- Read PRE_ACTION_CHECKLIST.md
- Know what you’re building
- Map all 0,1 states
- Verify logic while thinking
- Mark all unknowns (INCOMPLETE/UNVERIFIED)
- Code only after all verified
The 8 Phases (IN ORDER)
| Phase | What | Time | Done? |
|---|---|---|---|
| 1 | Understand requirement | 5-10 min | ☐ |
| 2 | Load frameworks | 5-10 min | ☐ |
| 3 | Think + verify logic | 15-45 min | ☐ |
| 4 | Verification checklist | 10-20 min | ☐ |
| 5 | Plan implementation | 5-10 min | ☐ |
| 6 | Execute (write code) | 10-30 min | ☐ |
| 7 | Test all paths | 10-20 min | ☐ |
| 8 | Document | 5-10 min | ☐ |
Verification Checklist (BEFORE CODING)
☐ Binary Completeness — All states mapped?
☐ Transition Coverage — Every state has exits?
☐ Input Handling — All inputs covered?
☐ Output Correctness — Output follows from input+state?
☐ Gap Identification — Unknowns marked?
☐ Assumption Logging — Decisions documented?
If ANY are unchecked → GO BACK TO PHASE 3
7 Error Prevention Rules
- Don’t skip thinking — Partial thinking = bugs
- Don’t assume — Mark unknowns explicitly
- Don’t code half-logic — Complete thinking first
- Don’t skip verification — Check while thinking
- Don’t ignore contradictions — Resolve them now
- Don’t test assumptions — Verify them first
- Don’t update assumptions later — Define them upfront
Decision Logging Format
When you make a decision:
DECISION: [What decision]
REASON: [Why you chose this]
ALTERNATIVES: [Other options considered]
VERIFIED: [How you verified this works]
TIMESTAMP: [When decided]
What to Do If You Get Stuck
Stuck on thinking?
- Return to Phase 1 — Do you understand the requirement?
- Write down unknowns explicitly
- Break problem into smaller pieces
- Start with simplest case first
Stuck on verification?
- Draw a state diagram
- Trace through one example input completely
- Check: Did it reach output? Yes/No
- If no → Missing transition (go back to thinking)
Code doesn’t work?
- Reread Phase 3 thinking
- Compare code to thinking
- Is there a mismatch? Yes/No
- If yes → Thinking was incomplete (go back to Phase 3)
Success Criteria
✅ Requirement understood fully
✅ All 0,1 states mapped
✅ All transitions verified
✅ All unknowns marked
✅ Verification checklist all checked
✅ Code written per plan
✅ All tests pass
✅ Documentation complete
If all are checked: TASK COMPLETE
Links to Full Frameworks
- Universal Mandate — Complete requirements
- Task Template — Full 8-phase details
- Pre-Action Checklist — 6-step gate details
Use this card. Every task. No exceptions.