Is TraceLogic a workflow tool?
No. Workflow tools track that a task moved from one step to another. TraceLogic governs the decision itself: evidence, policy version, reviewer, approval, controlled execution, and replay. The two can coexist; they solve different problems.
Does TraceLogic replace human reviewers?
No. TraceLogic is designed around human-in-the-loop control. Review, approval, and execution responsibility remain with the people in the lifecycle. The platform makes those steps clearer, not absent.
Does TraceLogic use AI?
The current demonstration uses AI-assisted document intake to help structure evidence and case information. Consequential decision checks are deterministic, and required review and approval remain human-controlled. TraceLogic is not an AI decision-maker or AI-agent governance platform.
Does TraceLogic autonomously approve or execute decisions?
No. TraceLogic does not independently approve, override or execute regulated business decisions. Required approval and execution-control responsibilities are assigned to authorised users according to the configured implementation.
How does TraceLogic handle controlled override?
Where an implementation permits an exception to the normal policy path, the override can require a recorded reason, supporting rationale, evidence and explicit approval. The approved override becomes part of the governed decision record so reviewers can see what changed, why it changed and who authorised it. The exact approval and separation-of-duties requirements are configured for each implementation.
What data does the demo use?
Synthetic or approved test data only. No real customer data, no real bank or vendor branding, no certification marks. Real data use would only be considered as part of a scoped implementation engagement, with handling agreed in writing first.
Is TraceLogic certified?
TraceLogic does not currently claim ISO 27001, ISO 42001, SOC 2 or regulatory certification. Customer implementations would be assessed against the organisation's own security, risk, compliance and procurement requirements. TraceLogic provides governance controls and decision evidence, but it does not replace legal, regulatory or compliance judgement.
Is TraceLogic only for mortgages?
No. Mortgage servicing is the first complete reference implementation because it is regulator-watched, evidence-heavy, and reviewable. Insurance claims have already been exercised on the same governance core using a synthetic decision source, demonstrating that the core is not mortgage-specific. The same governance model may be configured for other high-stakes regulated decisions where policy enforcement, approval control, execution assurance and decision evidence are required.
Can TraceLogic support other regulated decisions?
Yes, in principle. The lifecycle (intake, policy check, review, approval, controlled execution, replay) is decision-type-agnostic. Extending to a new decision type is part of implementation scoping, not assumed by default.
How is TraceLogic different from case management tools?
Case management tracks the case as it moves through people. TraceLogic governs the decision itself: it brings evidence, the policy applied, approval and execution control into a single record that can be revisited and replayed later. Case management can sit alongside TraceLogic; the two answer different questions.
Does TraceLogic replace my existing systems?
No. TraceLogic is designed to sit between your upstream decision sources, your human governance, and your downstream controlled execution, without requiring you to replace the systems you already run. A customer implementation is configured around your existing processes, policies, roles, and evidence sources.
Can TraceLogic govern a decision produced by another system?
Yes. A decision can be produced by an external source; TraceLogic preserves that source's full response as protected evidence and governs it from there: review, approval, controlled execution, and replay — without needing to call back to the external system to replay it later.
What prevents a different decision from being executed than the one that was approved?
Authorisation to execute is created for one specific approved decision only. Before execution proceeds, the decision record is checked against what was approved, and the authorisation is time-limited and single-use. If anything no longer matches, execution is blocked. TraceLogic records the authorised execution against the governed decision; it does not itself move funds or change external systems of record.
What does a customer implementation involve?
The core governance engine is complete. A customer implementation configures it around your organisation's decision processes, policies, decision sources, systems, roles, approval structures, controls, and evidence requirements. The public demonstration shows the governed lifecycle on synthetic data; it is not a customer's production workflow.
How does replay work?
Replay uses the evidence frozen when the decision was governed. A decision can be revisited later and shown to match what was approved, without depending on live systems still being in the same state they were at the time.
What is a frozen decision artifact?
A single, complete record of one governed decision that can't be altered after approval. It contains the evidence used, the policy version applied, the decision output, the reviewer identity, the approval status, and the execution record. It is the basis for replay and for audit reconstruction.
What does an implementation engagement involve?
A controlled engagement scoped around a defined decision lifecycle, agreed governance controls, synthetic or approved test data, and agreed success criteria. See the Implementation Scope page for what is and isn't included.