The reading room
Understand the ideas.
Put them to work.
Practical guides to signed records, AI accountability, and evidence your team can check. Find an explanation, follow a real workflow, and choose your next step.
27 articles
How to choose your first Truthlocks use case across 40 industries
Explore banking, telecom, IT, government, healthcare, and education examples, then use four questions to choose a practical first workflow.
Truthlocks operational workflows: finance, procurement, claims, and review
Understand how the operational modules organize work, what needs configuration, and where human approval remains essential.
Action receipts and application logs: how they work together
Learn what to capture in a signed action receipt, how it differs from a log, and why both sources matter when investigating a workflow.
Compliance evidence workflows: collection, exceptions, and human review
Connect evidence sources to a review process without treating automation, a completed checklist, or an AI summary as an assurance conclusion.
How to interpret an AI agent trust score
Use trust signals as review context, distinguish missing history from good performance, and avoid turning a score into automatic permission.
The identity gap between an AI answer and a business action
Follow the handoff from model output to tool execution and identify which identities, permissions, and review records your application needs.
Reviewing AI-to-AI transactions: identity, intent, and evidence
Design review controls for exchanges between software agents without assuming signatures or trust scores can guarantee fraud prevention.
MAIP and machine identity: evaluating an integration
Separate the identity model, API implementation, SDK version, and receiving system’s enforcement when connecting an agent platform.
Adding identity and review gates to an AI workflow
Connect task inputs, permitted tools, human decisions, and action receipts so an orchestrated workflow can be understood after it runs.
Machine identity for AI agents: ownership, permissions, and action history
Give each agent a distinguishable identity so teams can understand its purpose, inspect its access, and review the actions it reports.
Machine identity as evidence for governance reviews
Use agent identities and recorded actions to answer governance questions without treating activity records as automatic regulatory compliance.
Engineering a trust registry: identity, storage, and tenant boundaries
A practical architecture discussion grounded in the Truthlocks registry: separate identity from access, validate scope, and preserve reviewable changes.
An enterprise inventory for AI agents: what to record and review
Build an actionable inventory of agent owners, tools, permissions, credentials, and recorded activity before expanding automation.
Your first machine-identity workflow: a practical setup checklist
Register one agent, define a narrow task, connect an approved tool, and inspect the result before expanding access.
Responding to an unexpected AI agent action
A practical response sequence: contain access, preserve evidence, investigate scope, and validate the workflow before resuming it.
Transparency logs explained: records, checkpoints, and inclusion proofs
Understand what an inclusion proof establishes, why checkpoints need verification keys, and how to read a transparency result without overstating it.
Evaluating verification infrastructure: questions about SOC 2 and evidence
Separate a vendor’s assurance report from your own operational evidence, and ask concrete questions about scope, controls, and access.
Enterprise verification: separate identity checks from document checks
Design an onboarding review that distinguishes a person’s identity, a document’s integrity, and your organization’s approval decision.
Selective disclosure and zero-knowledge proofs: what to evaluate
Understand why sharing less data needs a defined proof format and threat model—not just a promise that a document is private.
Using the Truthlocks Python SDK: configuration and error handling
A practical integration guide to the Python client, keeping credentials on the server, checking API compatibility, and handling failed verification safely.
Supplier evidence and shipment records: a practical verification workflow
Keep supplier statements, document versions, and recorded handoffs connected while leaving physical inspection and assurance visible.
Digital signatures explained: what a verified record tells you
Learn the difference between a document fingerprint, a digital signature, and a trustworthy claim—with a practical certificate example.
What a trust registry does—and what an issuer profile cannot prove
Learn how issuer identities, public keys, and status help recipients check a signed record while keeping trust decisions explicit.
Understanding Truthlocks: records, identities, workflows, and evidence
A plain-language guide to how the Truthlocks system fits together and how people, organizations, and developers can choose a starting point.
The attestation lifecycle: issue, check, share, and revoke
Plan a reliable signed-record integration, including key selection, exact payloads, retries, status checks, and revocation behavior.
Privacy in verification workflows: data, access, and retention questions
Plan what a verification process records, what recipients can see, and how privacy responsibilities are reviewed before deployment.
Healthcare credential reviews: source, status, and responsibility
Organize staff training and qualification evidence without confusing signature verification with licensing, competency, or appointment decisions.