TraceLogic Documentation

Product documentation, built alongside the platform.

A map of the TraceLogic SaaS documentation surface. Some areas are available now, some are shared on controlled access during pilot scoping, and some are in development alongside the pilot. Honest about pilot stage; deliberate about what is public and what is private.

Book a Pilot Demo → Public vs Private Boundary Glossary
Governance Documentation
Proves control and accountability
The Governance Evidence Pack covers impact analysis, data concerns, design choices, evaluation results, vendor considerations, training, controls, approvals, monitoring, incidents, updates, and decisions to narrow or extend use over time.
See the Governance Evidence Pack
SaaS Product Documentation
Supports adoption and confidence
Getting started, feature guides, troubleshooting, knowledge base, persona guides, release notes, and visuals. Built to help users, reviewers, admins, buyers, and technical reviewers understand and adopt TraceLogic.
This is the page you are on now.
TraceLogic needs both. Governance documentation proves the controls are real. SaaS documentation makes the platform usable. Each is a separate discipline; do not conflate them.
Documentation Map

Ten areas, mapped honestly

Each area is labelled with its current state. Pilot stage means some content is published, some is shared on request, and some is being written alongside the platform. Status changes as the product matures.

Available
Getting Started and Onboarding
A public-safe Getting Started and Onboarding Guide covers what TraceLogic is, who it is for, what the controlled pilot demonstrates, login and tenant context, the main screens in the pilot lifecycle, and a first walkthrough of a governed decision. Role-specific onboarding paths are anchored to the Operator and Manager lifecycle runbooks. Synthetic or approved test data only. Shared on request as part of pilot scoping.
Available
How-To Articles and Feature Guides
A controlled Core How-To and Feature Guide covers the current governed mortgage pilot lifecycle: case creation, retrieval assisted intake, manual review and correction, governance evidence confirmation, deterministic decision evaluation, policy trace review, governance report review, approval and return, attestation and execution token handoff, controlled execution, replay, Trust Dashboard, Pilot Contract Gaps, and exception handling. Each feature is described in four parts: what it does, why it matters, who uses it, and the related governance control. Scoped to the current pilot baseline, not every future feature. Shared under pilot scoping.
Controlled access
API and Developer Documentation
Architecture overview, authentication, role-based access model, tenant separation, key data models, integration assumptions, error handling, environment differences across demo, pilot, and production. Shared on a controlled-access basis during pilot scoping. Sensitive endpoints and infrastructure detail are not exposed publicly.
In development
Searchable Knowledge Base
Structured source material exists across the onboarding guide, the core how-to guide, the troubleshooting guide, the operator and manager runbooks, the changelog, and the glossary on this page. A searchable knowledge base interface and indexed article system that ties all of this together remains in development. Planned categories include Getting Started, Using TraceLogic, Governance Model, Use Case, Replay and Trust, Troubleshooting, Data and Privacy, Pilot Support, Release Notes, and Developer Notes.
Available
Release Notes and Changelog
A pilot-stage changelog is maintained in the project. Covers new features, improvements, fixes, governance control changes, UI changes, known limitations, and pilot release notes. Current entries cover the May 2026 local stabilisation work. Written for users and buyers, not just developers. Sensitive technical detail withheld. Shared on request as part of pilot scoping.
Partially available
Visuals and Contextual Guidance
A public showcase repository carries redacted lifecycle screenshots (intake, decision review, policy check trail, manager review, execution gate, evidence replay, Trust Dashboard), three architecture diagrams (governance flow, evidence replay flow, separation of duties), and a small set of synthetic case examples. All assets use synthetic or approved test data and follow documented redaction rules. Walkthrough videos, in-app tooltips, and empty-state guidance remain in development.
Available
Troubleshooting and Support Articles
A controlled Troubleshooting and Support Guide covers login issues, access denied, missing case, missing evidence, retrieval extraction errors, returned cases, approval blocked, execution blocked, expired or invalid tokens, replay unavailable, Trust Dashboard evidence gaps, tenant mismatch or suspected leakage, and unexpected status. Each scenario describes symptom, likely cause, what to check first, action, when to escalate, and what not to attempt. The guide is grounded in the Operator and Manager runbooks, the Risk Management Plan, and the incident escalation pattern. A pilot support intake route is live on the platform. Shared under pilot scoping. No automated monitoring claim.
Partially available
Persona-Based Documentation
Operator and Manager lifecycle runbooks are available, covering login and tenant context, case handling, evidence confirmation, review, attestation, token handoff, controlled execution, replay, escalation, and completion. Persona guides for reviewer, compliance, audit, operational risk, admin, technical reviewer, pilot sponsor, and prospective buyer remain in development.
Available
Formatting, Terminology, and Glossary
Consistent TraceLogic terminology across all documentation: governed decision, decision artifact, frozen evidence, policy check, human review, Separation of Duties, execution gate, replay, Trust Dashboard, pilot, synthetic data, approved test data. Human-readable labels only.
Available
Documentation Maintenance Process
Owner per documentation area, review cadence, update triggers tied to UI and backend changes, screenshot refresh process, changelog process, version history, internal review before publishing, and approval gate for public documentation.
Documentation Boundaries

What is public, what is controlled-access.

A clear boundary between documentation that lives on the public website and documentation that is shared under pilot scoping or NDA. The boundary protects both parties and supports honest pilot conversations.

Public
Available on the website
What TraceLogic is and how it works at a high level
Getting started overview and onboarding map
Feature explanations across the lifecycle
Governance model overview
FAQ and use case explanation
Glossary and standard terminology
Release notes at a safe level
Controlled access
Shared under pilot scoping
Detailed API documentation and endpoint reference
Sensitive infrastructure and deployment detail
Security implementation specifics
Internal runbooks
Incident records and detailed test evidence
Internal monitoring records
Vendor risk assessment
Customer-specific pilot documentation
Detailed tenant configuration
Glossary

Standard terms, used consistently

Used the same way across the website, the platform, the pilot demo, and pilot conversations.

Governed decisionA regulated decision processed through the full TraceLogic lifecycle: intake, policy check, review, approval, controlled execution, and replay.
Decision artifactThe sealed record of a single governed decision, containing evidence, policy version, decision output, review status, and metadata.
Frozen evidenceThe preserved evidence captured at the moment of approval. Replay reads from this evidence, not from live systems.
Policy checkDeterministic evaluation of a case against the active policy, with the matched rule path recorded.
Human reviewThe reviewer step in the lifecycle. The reviewer approves, returns, or rejects based on the artifact and evidence shown.
Separation of DutiesThe lifecycle separates submitter, reviewer, and executor into distinct roles. The same person cannot perform all three.
Execution gateExecution is authorised only against an approved artifact, via a token. Direct action is not the trigger.
ReplayReconstructing a decision later from the frozen artifact alone. No live recomputation, no reliance on current state.
Trust DashboardA business-readable view across coverage, exceptions, and approval lineage, sourced from governed artifacts.
PilotA controlled engagement scoped around a defined decision lifecycle, agreed governance controls, and synthetic or approved test data.
Synthetic dataData generated for testing purposes. Resembles real cases in structure but represents no real customer.
Approved test dataReal-shape data approved for non-production use under explicit pilot scoping. Used only when synthetic data cannot demonstrate the case credibly.

Want a specific area in more depth?

Some documentation is shared under pilot scoping. Tell us what you need to evaluate and we will walk you through it.

Book a Pilot Demo → Documentation Enquiry FAQ