Animatics
The fabric, in motion
Every animatic below is a self-contained animated SVG — embed any of them anywhere on the site with a single include.
Twenty-one explainers, small to large
The envelope
Every message is a signed envelope — capability, correlation, deadline, identity.
Four exchanges
Messages out, results back, a control channel, and an audit stream Cortex watches.
Action vs event
Actions are point-to-point; events fan out to every subscriber.
Route by capability
The sender names a capability, never an agent.
Capacity is elastic
Backlogs are normal — absorbing a spike is a scaling action.
The retry ladder
Five seconds, thirty seconds, two minutes — then the dead-letter queue and operator replay.
Delivered twice, executed once
Idempotency by request id: duplicates are acknowledged, not re-executed.
Every request has a deadline
Work that cannot finish in time fails honestly.
Out of the hot path
The orchestrator tracks what exists and whether it is alive — and never routes a message.
Three layers of who
The service, the agent, and the principal — all named, even for cron.
An agent is code
Deterministic control flow, with the model invoked for one targeted subtask.
Three patterns
Pure code, targeted subtasks, LLM-orchestrated — in order of preference.
Typed at the ports
An edge between incompatible shapes is refused at authoring time.
Six ways to fire
Manual, schedule, webhook, queue, result-of, audit pattern — one graph carries them all.
Workflows are data
Publishing a transducer is saving it, not shipping code.
Autonomy proposes
The planner drafts a workflow from a goal; an operator publishes it.
Swap the provider, not the code
Per-tenant provider resolution with keys encrypted at rest.
Every token has an owner
AI calls are priced as they happen and attributed to a tenant.
Connect a source once
Eleven live sources stream onto the mesh for every consumer at once.
From stream to understanding
Cortex turns the audit stream into representations, aggregations and projections.
Coordination nobody commands
Pheromone trails evaporate unless the colony keeps them warm.
Six real-world scenarios
Prism is where each story starts and ends. Loom is everything in between.
A ticket enriches itself
A ticket lands in Prism; Loom scores sentiment, classifies, embeds and links similar tickets — then writes it all back.
A document understands itself
An upload flows through extraction, entities, summary and translation before returning to Prism.
Watching the coastline
Flood, stream-water and bathing-water feeds correlate into one alert on the earth-science console.
Rack 7 is overheating
Sensor streams are enriched at ingestion; a transducer classifies the anomaly and the heatmap turns red.
The Friday report writes itself
The scheduler fires with a named system principal; scanners, charts and a styled report follow.
Healing before the pager
A failed health check becomes a finding, a diagnosis, and a causal chain in the alert console.