Skip to content

Self-Improvement

ORCA supports two distinct improvement loops:

  • Loop A: user-instance improvement
  • Loop B: framework improvement

This is how ORCA gets better over time without pretending that retries or ad hoc changes count as learning.

What Self-Improving Means Here

Self-improving means:

  • observe real behavior
  • evaluate the outcome
  • record evidence
  • propose a bounded change
  • apply or draft that change in a controlled way
  • measure whether it actually helped

Retries alone are not learning.

Two Loops

Loop A: Instance Improvement

Loop A adapts the user's own ORCA instance.

It improves:

  • local defaults
  • guidance style
  • docs and help routing
  • local tool support behavior
  • onboarding style
  • local automation suggestions

Loop B: Framework Improvement

Loop B improves ORCA as a project.

It improves:

  • framework docs
  • onboarding
  • default policies
  • paved roads
  • orchestration guidance
  • integration packs
  • issue templates
  • automation and validation
  • update channels, release notes, and rollback policy when repeated evidence shows the current update system is causing friction or breakage

Core Rule

Local learning should not automatically become global policy.

Framework learning should require stronger evidence, clearer review, and tighter approval.