Get started, set up Fibric in five steps

Step 1 / About your operation

What are we bringing reason to?

Fibric runs the same way over a building, a campus, a warehouse, or a line of orders. Tell us what you operate so we can set the right defaults.

Name your operation

Give your operation a name to continue.

What kind of operation is it?

A hotelComfort, energy, access, arrivals A campus or buildingHVAC, lighting, sensors, security A warehouse or floorFlow, exceptions, dispatch Orders & fulfillmentCommerce, proofs, shipping, WISMO Something else entirelyFibric doesn't care what you run. If you operate it, it fits.

Pick the closest fit. You can change it later.

Step 2 / Connect a system

Plug Fibric into what you already run.

Connectors are how Fibric senses the real world. Pick one or more to start. Capability over connector means you can swap any of these later without a rewrite. Everything here is built on MCP.

BMS Building controls Hardware HVAC, lighting, and access over BACnet or Modbus. SEN Sensor network Hardware Occupancy, temperature, air, and door state, live. MG Magento Commerce Orders, proofs, and fulfillment state for every line. NS NetSuite ERP Sales orders, inventory, and the at-risk feed. KU Kustomer Support Conversations and customer context, swappable for Zendesk.

Read-only to start. Fibric senses before it ever acts.

Connect at least one system so Fibric has something to sense.

Step 3 / Your first intent

Say what you need. In plain words.

An intent is a standing instruction. Fibric reasons over what it senses and proposes the steps to meet it. Write your own, or start from an example.

Write an intent, or tap an example to start.

Start from an example

Step 4 / Set a guardrail

Draw the line Fibric won't cross alone.

The model proposes, a deterministic executor disposes. This policy is checked before any action ever happens, and it fails closed. Set the spend above which Fibric must ask you first.

Never act above $2,500 without my approval.

$0 pauses everything$10,000+

Single-flight and idempotency keys mean a runaway action, the kind that floods 657 messages, is structurally impossible. Set $0 to require approval for everything until you trust it.

Step 5 / Review

One last look before it goes live.

This is exactly what Fibric will run. Nothing acts until you say go, and every step after will leave a receipt you can read.

Operation ——

Connected

First intent —

Guardrail —Fail-closed, checked before every action

You are live

Fibric is on the floor.

Fibric is sensing now, and it has its first intent and its guardrail. The moment a step is worth taking, it will propose it, check your policy, and act, leaving the receipt below for every move.

Fibric Governed

Operation—

Sensing—

Intent—

Guardrail—

ExecutorDeterministic, fail-closed

StatusArmed & watching

Receipt FBR-000000 —

See how Fibric reasons → Add an operator