AI needs an operating record before it runs.
Policies in drives. Owners in chat. Support paths in people's heads. ChangeFabric turns that context into one operating record: Forge reads it, Factory deploys with it, and Pulse keeps it current.
Automation without context makes the wrong thing faster.
Every customer comes to us with context scattered across drives, wikis, ticket comments, and people's heads. Policies are stale. Owners are implicit. Support paths live in chat history. AI tools amplify everything, including the confusion.
So we open with a knowledge inventory. We keep your systems, link what matters, and make the facts queryable by the layer that builds, deploys, and runs AI apps.
One record. Four audiences.
Each layer is tuned to a different reader. The same policy, owner, or support fact appears at the altitude each role needs.
Same fact, four readers. Marketing for the buyer · Customer for the user · Product for the team · Architecture for the engineer.
What happens in week one.
We inventory Notion, Confluence, Google Docs, GitHub, internal wikis, and other systems: what exists, where it lives, and how stale it is.
Each fact is mapped to owners, policies, systems, support paths, and the audience layer that needs it.
Operating context gets wired into Forge, Factory, and Pulse. When an app needs a policy, owner, or support path, it pulls from the right layer.
Launched apps update the record. Stale entries get flagged. Documentation becomes part of operations.
ChangeFabric keeps the record current.
Policy updates, support notes, owner changes, and runbook edits are drafted in context. AI suggests. A human approves. Every artifact lands in the right layer with proper provenance.
when there's an alert, page the on-call
Page the on-call engineer via PagerDuty (not Slack, alerts shouldn't compete with chat traffic). Include: alert title, runbook URL, severity, and the most recent metric snapshot.
if they don't ack in 10 min, escalate
Escalate to the secondary on-call after 10 minutes without acknowledgement. If no ack at 20 minutes, escalate to the engineering manager and open an incident channel #inc-YYYYMMDD.
▍
For engineers extending it.
Pulse data is queryable via REST on Professional and Enterprise. Forge blueprints and Factory handoffs are webhook-driven and Model Context Protocol-compatible.
REST API
Read access to outputs, owners, policies, support paths, telemetry, and value records. JSON, JWT auth, fair rate limits.
Webhooks
Push notifications on output changes, anomaly detection, and connector health changes. Verified signatures, retry semantics, replay.
Custom Connectors
Build via Model Context Protocol, same standard our AI-native integrations use. Templates, harness, validation included.
Want an operating-record inventory?
We'll inventory your documentation systems and return a layered map: what to keep, what to connect, what to retire, and which AI workflows need control first. Free for qualified pilots.