Capabilities of the governance engine.

Documents and case inputs can be structured with assisted extraction while field provenance is retained so reviewers can trace values to their source evidence.

Decisions are evaluated against configured rules. The check is deterministic, repeatable, and produces an output that is recorded in full alongside the inputs that drove it.

Each decision carries the policy version it was evaluated against and the specific rule path that produced the outcome. Policy logic is visible as part of the evidence, not buried in code.

A reviewer sees the decision output, the supporting evidence, and the policy trace in one view. They approve or return the case based on what is presented, not on a separate spreadsheet.

Where an implementation allows an exception to the normal policy path, the override can require a recorded reason, rationale, supporting evidence and explicit approval. The exact approval and separation-of-duties requirements are configured per implementation.

On approval, the case is stored in an integrity-sealed, tamper-evident decision record: evidence, policy result, decision output, review status, and governance metadata.

Execution authority is tied to the approved artifact and verified before use. The authority is time-limited and single-use, and the authorised execution is recorded against the governed artifact.

Internal policy decisions can be re-run against their frozen inputs and policy snapshot to confirm an exact match or identify drift. Decisions received from an external source are reconstructed and integrity-verified from their frozen record without re-calling the source system.

A business-readable view across coverage, exceptions, approval lineage, and replay evidence. Designed for managers, compliance, risk, and audit, not engineers.

Configuration, policy, evidence, and replay are scoped per tenant. A single deployment can support multiple decision domains without crossing the controls between them.

Authorised responsibilities are assigned according to the configured implementation. TraceLogic enforces supported role boundaries, including preventing a proposal creator from attesting the same approved artifact for controlled execution.

The governed decision record brings together source evidence, intake values, policy trace, review status, approval lineage and execution evidence for later inspection and reconstruction.