The Orchestration Policy

The Orchestration Policy enforces deterministic routing for every inbound intent.

Through a series of prioritized Rules, the Orchestrator evaluates the metadata of a request—method, origin, and headers—to select the optimal path for settlement.

Policy Hierarchy (9-0)

Backpac evaluates rules in a strict descending sequence from Priority 9 (Highest) to Priority 0 (Floor Invariant). The first rule that matches the intent terminates the search and executes its action.

Rules 1–9: Conditional Overrides

These rules are used to surgically steer traffic based on specific technical criteria.

• Priority 9: Emergency intercepts or forensic isolation.
• Priority 5-8: High-value optimization (e.g., steering sendTransaction to premium pools).
• Priority 1-4: General traffic shaping and deprecation handling.

Rule 0: The Floor Invariant (Default)

The Default Rule is the physical floor of the policy. It handles any request that survives higher-priority filters.

• Match Condition: Absolute. Rule 0 matches all intents.
• Mandate: Must always be assigned to a valid Reliability Pool. It cannot have filters.

Universal Condition Logic

A Rule is only triggered if every configured condition is met (Logical AND).

1. RPC Method: Match by Exact String or Wildcard (*).
2. Source IP: Enforce perimeter access for specific infrastructure ranges.
3. HTTP Headers: Verify internal tags or user-tier markers (e.g., x-user-tier: institutional).

Deterministic Actions

When a rule triggers, it executes one of two atomic actions:

1. Signal Hand-off (Forward)

Dispatches the intent to a specific Reliability Pool. This is the standard path for settlement.

2. Deterministic Intercept (Fixed Response)

Terminates the request at the edge and returns a predefined JSON payload.

• Use Case: Blocking deprecated methods, rate-limiting aggressive actors, or providing simulated responses for air-gapped testing.

---

Policy ensures that no intent is left to chance.