01 Product Overview

01. Product Overview & Vision

PACT OS: Personal Productivity & Accountability System

---

🎯 Mission & Philosophy

PACT OS is designed to solve the Execution Gap—the psychological disconnect between forming ambitious long-term goals and executing immediate daily habits.

Most productivity systems fail because they rely exclusively on motivation or passive task lists. PACT OS replaces passive list-making with Server-Authoritative Commitments:

1. Intention without friction: Commitments are sealed in under 5 seconds with a title and a deadline.
2. Accountability with consequences: Missing a deadline activates a pre-sealed consequence state machine.
3. Financial clarity: Money and budget tracking enforce integer-cent precision to prevent rounding errors.
4. Data privacy: User data remains strictly owned by the user, governed by Row Level Security (RLS).

---

💡 Core Concepts

graph TD
    Goal[Strategic Goal] --> Project[Scoped Project]
    Project --> Task[Actionable Task]
    Task --> Commitment[Sealed Commitment]
    Commitment --> Consequence[Binding Consequence]
    Commitment --> Proof[Proof of Work]

Loading

1. The Commitment Hierarchy

• Goals: High-level strategic objectives with target completion dates.
• Projects: Scoped initiatives containing actionable deliverables.
• Tasks: Specific, time-blocked action items.
• Commitments: Tasks bound to an explicit deadline (deadline_at) and an accountability state machine.
• Consequences: Pre-configured outcomes (reflections, declarations, financial pledges) activated upon deadline breach.

2. Timeblocking & Cadence

PACT OS operates on structured daily and weekly temporal boundaries:

• Daily Cadence: Morning intent setting and evening reflection.
• Weekly Review & Sunday Ritual: A 5-step guided reflection ritual that audits completed tasks, carries over pending items, and plans the upcoming week's top 5 priorities.

3. Financial Discipline

Monetary management is integrated directly into the OS as a discipline ledger:

• Integer Cents: All transactions store amount_cents (bigint) to eliminate IEEE 754 float inaccuracies.
• Budget Envelopes: Monthly and category-based spending limits.

---

🔄 Primary User Workflows

Workflow A: Daily Timeblocking & Speed-Sealing (< 5 Seconds)

1. Open Task Modal (TaskFormModal).
2. Type title and select deadline preset (e.g., "Today 10 PM").
3. Submit commitment. The system records scheduled_start, deadline_at, and initializes the commitment state machine.

Workflow B: Deep Work Focus Session

1. Navigate to Focus Engine (/app/focus).
2. Select target task and duration (e.g., 25 minutes).
3. Start timer. The offline Web Audio soundscape synthesizer (src/lib/focus/sound.ts) generates ambient focus audio.
4. Complete session to log actual_duration_seconds to user analytics.

Workflow C: Deadline Resolution & Proof Verification

1. User submits proof or completes task before deadline.
2. For external proof tasks (GitHub commit, LeetCode submission), the system calls server connectors (src/lib/integrations/).
3. Upon verification, task status transitions to completed and streak multipliers increment.
4. If deadline passes without completion, background cron (/api/cron/sweep-deadlines) marks task missed and activates the consequence payload.

---

🧭 System Integration Summary

sequenceDiagram
    participant User
    participant NextJS as Next.js Server Actions
    participant DB as Supabase PostgreSQL
    participant Cron as Sweeper Cron

    User->>NextJS: Seal Commitment (Title + Deadline)
    NextJS->>DB: INSERT into tasks & commitments
    alt Task Completed on Time
        User->>NextJS: Mark Complete / Submit Proof
        NextJS->>DB: UPDATE status = 'completed'
    else Deadline Expires
        Cron->>DB: Scan expired deadlines (deadline_at < NOW())
        Cron->>DB: UPDATE status = 'missed', activate consequence
    end

Loading

---

📚 Related Documentation Pages

• Features — Comprehensive breakdown of all 14 core OS modules.
• Architecture — Server vs client boundaries and technical design.
• Consequence System — State machine rules and breach handling.