Capability and Operation Contracts

Capability and Operation Contracts An architecture diagram generated by Archify. RpcCaller · rpc_call(...) Protocol · Web-only dispatch contract · Web capability RpcCaller rpc_call(...) Protocol Web capability RpcExecutor · production satisfier · Web-only dispatch contract · batchexecute owner RpcExecutor production satisfier batchexecute owner Web Feature APIs · narrow collaborators · Web-only dispatch contract · backend adapters Web Feature APIs narrow collaborators backend adapters Namespace ABCs · eleven neutral APIs · Architecture component · abstract operation scope Namespace ABCs eleven neutral APIs abstract operation scope BackendAssembly · transport tuples · root lifecycle contracts · typed handoff BackendAssembly transport tuples typed handoff ClientLifecycle · root coordinator · root lifecycle contracts · root owner ClientLifecycle root coordinator root owner TransportLifecycle · open · close phases · root lifecycle contracts · Protocol TransportLifecycle open · close phases Protocol Concrete Resources · Web / Android · root lifecycle contracts · selected participants Concrete Resources Web / Android selected participants Namespace Workflows · await → settlement · Architecture component · operation_scope Namespace Workflows await → settlement operation_scope CallSupervisor · admission · metrics · qualified operation · LifecycleSupervisor satisfier CallSupervisor admission · metrics LifecycleSupervisor satisfier OperationLease · epoch + context · qualified operation · generation-qualified OperationLease epoch + context generation-qualified OperationContext · deadline · task · journal · qualified operation · task-local carrier OperationContext deadline · task · journal task-local carrier satisfied by injected into implements freezes calls phases satisfied by enters scope yields exposes Web-only dispatch contract root lifecycle contracts qualified operation Legend Frontend Backend Database Cloud Security

Narrow capabilities

  • • Features receive only the collaborators they use; backend assembly records stay at the composition boundary
  • • Transport resources satisfy root lifecycle phases without exposing backend state to namespace contracts

Qualified operation

  • • A context joins only for the same supervisor, task, loop, and generation; nested scopes keep the earlier deadline and journal
  • • Shared producers clear waiter-specific state while root lifecycle still fences owned work