Skip to content

Framework Principles

ORCA Framework is opinionated about how orchestration systems should feel in practice.

Core Principles

  1. Reduce friction before adding capability.
  2. Teach through use, not through a prerequisite lecture.
  3. Prefer one clear default path over broad option menus.
  4. Keep advanced features available without forcing them into the first-run path.
  5. Support user-chosen tools respectfully when they are compatible.
  6. Use existing user context and artifacts before asking for more input.
  7. Make runs inspectable, reviewable, and resumable.
  8. Keep recommendation separate from setup assistance.
  9. Treat docs, onboarding, and automation as workflow surfaces, not side material.
  10. Promote only what has evidence behind it.
  11. Help the user improve without turning the workflow into school.
  12. Use orchestration only when it creates real leverage.
  13. Improve through evidence, not through random drift.
  14. Installation should be clear enough that a new user can reach first success without insider help.
  15. Updates should lower maintenance burden without creating surprise breakage or forced complexity.
  16. The README should describe the project as a whole, not whichever subsystem was edited most recently.
  17. Top-level positioning should follow live operating evidence before generic category language.
  18. Solve with the strongest safe assumption before escalating to the user.

First Principle

The first principle is the anchor for the rest:

The goal is to reduce friction, not create more setup work.

Read friction-reduction-principle.md.

Practical Reading