Notes on building Fibric
Engineering and product notes from Fibric.
All articles
From a proposed plan to an allowed action
A model can propose work. The system running it must decide whether that work is permitted.
Coordinating repeated work
Single-flight and idempotency address different reasons an operator might attempt the same work twice.
Separating a capability from its connector
An operator defines the work it needs. A connector binds that work to a particular system.
A common event envelope
Events from different systems need shared context before an operator can use them together.
Tenant identity through the full request
Customer separation needs to extend from source data to the authority for an action.
Recording an action and its outcome
An execution record should let a reviewer tell what was requested, what was allowed, and what the system reported.
Real data in BearScope
Source labels and explicit missing states matter when a team is using a dashboard to make an operational decision.
Designing a building pilot
A useful pilot starts with the property, its measurement coverage, and a question the available data can answer.
Testing an operator before deployment
Evaluate the plan, its permissions, and the integration’s failure behavior before enabling a consequential action.
Why AI has to leave the screen
For three years the frontier of AI has been a text box. Deployment boundaries require validation.
The audit trail is the product
The audit trail is the product — a Fibric reference essay with deployment boundaries stated explicitly.
A connector in an afternoon
A connector in an afternoon — a Fibric reference essay with deployment boundaries stated explicitly.
The discipline of a low ceiling
Fibric runs under a hard, deliberate cost ceiling. Deployment boundaries require validation.
Fail closed: what happens when trust is in doubt
Fail closed: what happens when trust is in doubt — a Fibric reference essay with deployment boundaries stated explicitly.
From cron jobs to operators
Somewhere in your infrastructure there is a crontab that runs your business. Deployment boundaries require validation.
Governed by default: why a model should never touch the actuator
One important design decision is where to draw the line between the part that reasons and the code that acts. Deployment boundaries require validation.
Guardrails the model can’t argue with
A rule written in a prompt is a request. Deployment boundaries require validation.
Idempotency is a kernel primitive, not a library
Every integration guide tells you to make writes idempotent. Deployment boundaries require validation.
Anatomy of a connector: Kustomer
Kustomer supports live BearScope data paths. Deployment boundaries require validation.
A proposed low-fee marketplace model
Marketplaces reveal what a platform believes about builders. Deployment boundaries require validation.
Why operators have names
Every operator on Fibric has a name. Deployment boundaries require validation.
Per-seat pricing is wrong for operational AI
The seat was the right unit for software that people use. Deployment boundaries require validation.
From a hotel to a paper company: one operational layer
A boutique hotel and a regional paper-and-print company share almost nothing. Deployment boundaries require validation.
The dashboard didn’t fix anything
Operations teams spent a decade building the best rear-view mirror in the history of business. Deployment boundaries require validation.
Five rooms before five hundred
A reference essay on designing a small, matched, metered pilot. The five-room example is illustrative, not a live deployment or measured customer result.
Point and go: operations AI for people who don't write code
The person who knows an operation is rarely the person who can script it. Deployment boundaries require validation.
Sense, reason, act: the loop that runs a building
Sense, reason, act, the loop of a building — a Fibric reference essay with deployment boundaries stated explicitly.
The 657-message problem, and how single-flight fixes it
An agent that can act can also act too many times. Deployment boundaries require validation.
In praise of unglamorous protocols
The buildings you live and work in are not run by REST APIs. Deployment boundaries require validation.
Voice is just another sensed channel
Phone calls feel like they should be special. Deployment boundaries require validation.
Where seconds compound
A warehouse is not one big problem. Deployment boundaries require validation.
Webhooks in, receipts out
Strip an operator down to its interface and two things remain: signals arrive, decisions leave. Deployment boundaries require validation.