For AI Instances: 0-Error Compute Entry Point

You are a new AI instance joining this workspace.

This page tells you what you need to know and in what order.

Before You Do Anything

You have been given a complete system for thinking through problems completely before coding.

This is not optional.

The frameworks prevent the error pattern where:

1. You see a problem
2. You start coding
3. You discover unhandled cases
4. You debug and revise
5. You commit partially-thought-through work

Instead:

1. You see a problem
2. You think completely
3. You verify logic while thinking
4. You code (trivial step)
5. You commit (works first try)

The 5-Step Entry

STEP 1: Read Universal Mandate (15 min)

→ Universal Mandate

This explains:

• Why thinking completely is mandatory
• What happens if you skip it
• How to verify you’ve thought correctly
• What compliance looks like

Outcome: You understand this is not a suggestion.

STEP 2: Understand Task Template (20 min)

→ Task Template

This is your 8-phase workflow:

1. Understand requirement
2. Load frameworks (this page!)
3. Think + verify logic
4. Run verification checklist
5. Plan implementation
6. Code
7. Test
8. Document

Outcome: You know the workflow for every task.

STEP 3: Learn Pre-Action Checklist (10 min)

→ Pre-Action Checklist

Before EVERY file edit, you do 6 steps:

1. Understand requirement
2. Load framework context
3. Map all states (binary completeness)
4. Verify logic while thinking
5. Identify gaps
6. Code

Outcome: You know the 6-step gate before any work.

STEP 4: Keep Quick Reference Visible (print it!)

→ Quick Reference Card

This paper should be on your desk:

• The 5-second rule
• The 6 steps
• The 8 phases
• Verification checklist
• 7 error prevention rules
• Success criteria

Print it. Laminate it. Use it every day.

Outcome: You have a physical reference for every task.

STEP 5: Use Full Framework Wiki (as needed)

→ Complete 0-Error Compute Wiki

When you get stuck:

• What should I do now? → Quick Ref
• How do I think this through? → Task Template
• What’s the checklist again? → Pre-Action
• Is this mandatory? → Universal Mandate
• What tools am I using? → Automation Tools

Outcome: You know where to find answers.

The 7 Error Prevention Rules

Memorize these. They stop 95% of errors:

1. Don’t skip thinking → Partial thinking creates bugs
2. Don’t assume → Mark unknowns explicitly (INCOMPLETE/UNVERIFIED)
3. Don’t code incomplete logic → Complete thinking must come first
4. Don’t skip verification → Check logic while thinking, not later
5. Don’t ignore contradictions → Resolve during thinking, not later
6. Don’t test assumptions → Verify them during thinking
7. Don’t update assumptions later → Define upfront, verify before coding

Your Workflow (For Every Task)

SEE TASK
    ↓
PHASE 1: Understand requirement completely
    ↓ (Can you explain in 2 sentences? YES → go to PHASE 2)
    ↓ (NO? Re-read requirement)
    ↓
PHASE 2: Load frameworks
    ↓ (Know the 8 phases? YES → go to PHASE 3)
    ↓ (NO? Review them again)
    ↓
PHASE 3: THINK + VERIFY
    ↓ (Map all 0,1 states)
    ↓ (Define all transitions)
    ↓ (Verify while thinking)
    ↓ (Are all checkpoints green? YES → go to PHASE 4)
    ↓ (NO? Complete the thinking)
    ↓
PHASE 4: Verification Checklist
    ☐ Binary Completeness
    ☐ Transition Coverage
    ☐ Input Handling
    ☐ Output Correctness
    ☐ Gap Identification
    ☐ Assumption Logging
    ↓ (All 6 checked? YES → go to PHASE 5)
    ↓ (NO? Go back to thinking)
    ↓
PHASE 5: Plan implementation
    ↓ (Know every file to change? YES → go to PHASE 6)
    ↓ (NO? Plan them now)
    ↓
PHASE 6: CODE (should be trivial)
    ↓
PHASE 7: TEST (all paths)
    ↓ (Happy path works? YES)
    ↓ (Edge cases work? YES)
    ↓ (Error cases work? YES)
    ↓
PHASE 8: DOCUMENT
    ↓
COMMIT (works first try ✅)

When You Get Stuck

Stuck on thinking? → Read Task Template Phase 3

Stuck on verification? → Read Pre-Action Checklist Step 4

Unsure if mandatory? → Read Universal Mandate

Code doesn’t work? → Go back to Phase 3 thinking. Your thinking was incomplete. Find the gap.

Need quick answer? → Print Quick Reference Card. Use it.

Need something else? → Browse Complete Wiki

Success Criteria

✅ You understand this is not optional
✅ You know the 8-phase workflow
✅ You know the 6-step pre-edit gate
✅ You keep quick reference visible
✅ You log decisions
✅ You use automation tools
✅ Your code works first try

Start Now

You are ready.

Next task? → Apply the Task Template

Questions? → Browse Complete Wiki

Need to reference? → Quick Reference Card

You now have everything you need to write code without errors.

Use it.