Developer Docs
Developer Overview
Start at the main docs hub.
Verification Lifecycle
Artifact submission, receipts, and later comparison.
API Overview
Public request and response model.
Security Model
Claims boundary and public-safe controls.
Architecture
Workflow fit and trust-boundary framing.
Threat Model
Threat assumptions and review posture.
TrustSignal Documentation
Professional evaluator-facing documentation for the verification lifecycle, public API contract, security model, and architecture fit inside existing workflows.
Problem / Context
High-loss workflows need a durable way to detect artifact tampering, provenance drift, and stale evidence after collection.
- Evidence tampering after collection
- Artifact substitution attacks in workflow handoffs
- Provenance loss across compliance and audit systems
- Stale evidence during later review
- Documentation chains that cannot be verified later
Integrity Model
TrustSignal operates as an integrity layer for existing workflow integration. It returns signed verification receipts, verification signals, verifiable provenance, and later verification capability.
How It Works
The evaluator path should be understandable in one scan before you open the API example pages.
Developer Journey Flow
Problem
Verification Lifecycle
Try The API
API Example
Developer Docs
Example / Diagram
This lifecycle view mirrors the public contract and the repo-side evaluator start path.
Verification Lifecycle
Submit artifact material, receive verification signals and a signed verification receipt, store the receipt with your workflow record, and run later verification when trust conditions matter.
Submit Artifact
The external workflow sends an artifact-derived verification request through the TrustSignal API boundary.
Verification Result
TrustSignal returns verification signals that summarize the verification outcome for downstream workflow logic.
Signed Receipt
The system issues a signed verification receipt that binds the verification outcome and verifiable provenance.
Store Receipt
The workflow stores the receipt with its own record so the system of record retains the integrity-layer output.
Later Verification
Before audit review or another high-trust step, the workflow can request later verification against stored receipt state.
Tamper Detection
If the artifact or stored state has drifted, later verification returns a mismatch signal instead of silently reusing the earlier result.
Production Considerations
The evaluator path is intentionally narrow. Production integration still requires explicit authentication, environment configuration, and lifecycle monitoring.
Security and Claims Boundary
Evaluators should understand the public contract and the explicit claims boundary before relying on the output model.
Claims Boundary
- • TrustSignal provides signed verification receipts.
- • Returns verification signals and lifecycle status.
- • Enables later verification of previously checked artifacts.
- • Integrates with existing compliance workflows.
Not Provided
- • Legal determinations
- • Fraud guarantees
- • Compliance certification
- • Replacement for system-of-record platforms