How TrustFabric works
Policy documents become draft rules, people approve a bundle, the gateway evaluates requests against it, and each decision becomes evidence.
The policy lane
You import policy documents by uploading or pasting text, recording the source, owner, revision and sensitivity. Requirement extraction is deterministic: it finds obligation sentences (must, shall, required, prohibited and similar) and maps them to control categories as draft proposed rules.
People review the drafts and assemble a policy bundle. A bundle moves from draft to in review to approved, and is later superseded by a newer version. Approval requires a person with the approver permission who is not the bundle's author. Once approved, a bundle is immutable and SHA-256 hashed.
The runtime lane
An agent or CI step sends an authorization request describing who is acting, on what, with which tool, and where data would be processed. The gateway answers ALLOW, DENY, REQUIRE_APPROVAL or INSUFFICIENT_CONTEXT against the approved bundle, with reasons.
Every answer is written as a record in a per-organization hash chain that can be verified and exported.