Skip to main content
This page translates BOA-0 philosophy into enforceable system contracts.

A) Business Axis (Durability)

Identity Contract

The system’s reference subject is the Business, not an individual account.
  • Violation: business-critical authority depends on one user identity.
  • Expected behavior: business identity persists across personnel and tool changes.

Continuity Contract

Goals, context, and decision history accumulate and transfer at the Business level.
  • Violation: replacing a worker resets critical operating context.
  • Expected behavior: replacement workers inherit the required business context.

Governance Contract

Control boundaries exist at the Business level and are designed to be extensible.
  • Violation: governance is ad-hoc and person-dependent.
  • Expected behavior: boundaries evolve without redefining Business identity.

B) Agent Axis (Autonomy)

Autonomy Contract

Agents execute autonomously within assigned roles.
  • Violation: every action requires direct human micromanagement.
  • Expected behavior: agents progress scoped work without constant prompting.

Delegation Contract

Delegation is allowed, while accountability traceability remains intact.
  • Violation: delegated outcomes cannot be attributed.
  • Expected behavior: execution paths remain reviewable at decision level.

Process Contract

Autonomous execution must remain compatible with shared operating process.
  • Violation: each agent runs incompatible loops and handoffs.
  • Expected behavior: autonomy is expressed through a common process backbone.

Decision Rule

When implementation trade-offs appear:
  1. Preserve Business durability contracts first.
  2. Preserve process accountability second.
  3. Maximize Agent autonomy inside those boundaries.
  4. Reject shortcuts that violate either axis.