Named operators that run an operation.
An operator is a named role with a bounded job. Two run in BearScope today; six are managed early access. The generalized runtime, public SDK, and self-service install path are not yet available.
The reference loop.
Sense
It reads your live systems through connectors and turns what it sees into one clear signal.
Reason
It thinks the call through with a base model, inside the limits you set.
Act
An enabled path uses policy, human approval where required, and duplicate-suppression controls before dispatch.
Record
Supported actions keep the proposal, decision, and reported result. Recovery depends on the connector.
The systems agents run on
Every operator works through connectors. Browse the systems Fibric can sense and act on.
Browse connectors → RecipesCross-domain plays
See clearly labelled reference patterns. Public signals may be live; operational and life-safety actions are illustrative.
Browse recipes → Reference previewThe proposed operator contract
Review the target SDK and runtime shape. Public packages and API endpoints are not available today.
Read the reference docs → Loop builderPreview a loop
Compose an illustrative signal, proposal, action boundary, and record without connecting a production system.
Open the tool →Managed pricing, scoped before launch.
There is no public self-service plan today. The pricing page shows indicative managed early-access assumptions. Connector, operator, action, and deployment rates are confirmed in writing during onboarding.