# TechFabric Platform

> The kernel under an enterprise composable architecture. Capabilities publish once as versioned contracts, every mutation passes one governed pipeline, and surfaces render from view contracts they cannot write behind.

Role: Governed composable framework
Databricks surfaces: Lakebase / Postgres, Unity Catalog, Databricks Apps
Status: Published on npm as @fabricorg/platform. Every other accelerator on this page consumes it.
Documentation: https://platform.techfabric.com
Canonical: https://www.techfabric.com/accelerators/platform

---

## The problem

In most enterprise systems, a row changes and nothing explains why. Audit means reading application logs and guessing. When an AI agent is one of the actors, that gap stops being an inconvenience and becomes a governance failure.

## How it works

Every domain change passes through one mutation pipeline: Actor, Action, Policy, State Machine, Handler, Adapter, Event, Projection. No exceptions and no bypasses. The event log is authoritative and read models are derived from it, so state is replayable.

## What it changes for you

Your auditors get an answer that holds. Every state change carries the actor, the policy that allowed it, and the event that explains it, so an audit becomes a query instead of a reconstruction. Teams adopting it stop building a bespoke approval and audit layer for every application.

## Questions

### Do we have to adopt the whole platform to use it?

No. It is a library you register inside your own application, not a system you migrate onto. You start by routing one domain's mutations through it and expand from there.

### How is this different from an audit log?

An audit log records that something changed. This makes the change impossible unless a policy allowed it, and the event that explains why is emitted as part of the same transaction. You audit by running a query.

### Does it work for AI agents as well as people?

That is the reason it exists. An agent actor passes exactly the same policy and state-machine gates as a human one, with the same audit trail. There is no separate, weaker path for automation.

