| Up: runtime map | Account machine | Protocol primitives |
Extensions add products above the bilateral core. They may submit typed account/entity transactions, but must not bypass account consensus, mutate delta fields directly, or become hidden loop owners.
core/extensions/cross-j/ - cross-j route and fill coordination.core/orderbook/ - deterministic same-j matching and book state.core/pathfinding/ - payment graph and route selection.core/extensions/lending.ts - lending projection pending final folder migration.applyCommand(...) - applies deterministic orderbook commands.buildPreparedCrossJurisdictionRoute(...) - constructs a bound cross-j route.withCanonicalCrossJurisdictionRouteHash(...) - commits route fields canonically.findPaymentRoute(...) - selects a route from advertised capacities.deriveDelta(...) - remains the only economic delta derivation boundary used by extensions.An extension can propose work, never redefine settlement truth. Consensus state remains in E/A/J machines; retry policy, caches, and automation remain private shadow or infrastructure state.