Philosophy

ORCA Framework exists because agentic software work needs more than speed. It needs durable decisions, clean context boundaries, real verification, and a way to preserve the perspective of a first-time user.

Working Beliefs

• Good specs make agents faster because they remove hidden interpretation.
• The first blind QA pass is uniquely valuable and cannot be recreated after briefing.
• Subagents should be used for independence, not theater.
• A review gate is useful only when it can block or change the work.
• A project is not done until another capable agent can understand what happened.
• User-facing work should feel product-specific and intentional, not generic, prompt-shaped, or stylistically interchangeable.

Practical Discipline

ORCA Framework favors written artifacts that are short enough to use and specific enough to test. It avoids ceremonial process. Every artifact must help an agent decide, build, verify, review, test, or ship.