Fibric’s reference architecture separates planning from execution. An operator uses a model to produce an ExecutionPlan. The executor accepts a defined structure with named capabilities and parameters. It checks the plan before calling a connector.
This boundary makes the allowed action set inspectable. A policy can limit the capability, customer, entity, or parameters involved. If the plan is malformed or the required authority is missing, execution stops. The executor should not infer a missing permission or ask a model to reinterpret a rejection.
What deterministic execution means
The executor follows code and policy for a given request. That does not make an external system deterministic. An API can time out after accepting a request; a controller can acknowledge a command without producing the intended physical result. The integration must define how those outcomes are reported and reconciled.
Execution records therefore need to distinguish a proposal, an accepted request, an attempted effect, and a confirmed outcome. Keeping those states separate gives the team something useful to investigate.
Current product scope
This is the generalized platform contract. BearScope’s actual action availability depends on the deployed gateway, feature configuration, user role, and tenant. Product-specific paths can have their own transactions and histories. The architecture alone is not evidence that an external action is enabled.