The system locks down. Background pulses red, navigation is disabled with blur + lock icon, and only conflicting items are visible. You must go through the Resolution Ritual: Lockdown (visual hostility) → Weigh-In (force-rank conflicting items) → Cost of Admission (hold to confirm for 3 seconds or type 'I SACRIFICE [label]').

Through the Capacity Audit during onboarding: Start with 168 hours (one week), subtract your biological tax (sleep, hygiene, eating), subtract spoken-for time (commute, meetings, fixed obligations), apply the chaos margin (default 20% reality buffer). The result is your weekly capacity. This number doesn't stretch.

Zombies are commitments punted 2+ times OR stagnant for 7+ days. They represent 'punt debt' — the lie that you'll 'get to it later.' Each punt adds a 50% weight penalty (actual weight = original × (1 + 0.5 × puntCount)), making them physically heavier in your stack. The weekly burial ritual forces you to confront them.

A trusted person who holds you accountable. They pair with you via code and can be required for overriding critical failure or excessive punts. If you exceed punt thresholds, they receive 'Liar Alerts' via push notification. Think of them as an external governor on your tendency to overcommit.

Yes. HADAL is offline-first by design. Your capacity contract and commitments are stored locally (Hive/SharedPreferences). Firestore sync happens when connected, but the core constraint enforcement — morning calibration, critical failure detection, load calculation — works entirely locally without internet.

Morning Calibration accounts for this. Triggered by scheduled notification at your configured time, you rate your energy: 100% (full capacity), 60% (reduced), or 20% (survival mode). The container visually shrinks based on your input, and tasks move toward the Red Zone. If the shrunken capacity creates an overload, you must sacrifice commitments before your stack is visible.

Your data is stored locally by default, with optional Firestore sync for backup and cross-device access. The Capacity Mirror feature lets you optionally share only your load percentage (e.g., '87% full') without revealing commitment details. Witnesses see punt counts and thresholds for accountability, not your commitment content.

The core constraint enforcement — capacity contracts, load calculation, critical failure detection, and hostile UI — will remain accessible to all users. Premium features may include witness pairing, capacity buckets, advanced analytics, and data export. Both tiers enforce the same mathematical rules.

You can. HADAL doesn't lock your phone or prevent uninstallation. The constraint is psychological, not technical. The system is designed for people who want to stop lying to themselves about their capacity. If you delete apps when they tell you hard truths, you might not be ready for HADAL.