Transparency log guide

Core concepts#

• Each published report contributes a content hash leaf.
• The service signs and exposes a latest root checkpoint.
• Anyone can verify inclusion and append-only growth without tenant credentials.

Public transparency endpoints#

• Current root: GET /pqc/transparency/root
• Key history: GET /pqc/transparency/keys
• Inclusion proof: GET /pqc/transparency/{content_hash}
• Consistency proof: GET /pqc/transparency/consistency?from_size=A&to_size=B

Operational use#

Embed root snapshots into release records. During incident response, compare historic checkpoints to current roots and validate no fork or silent rewrite occurred.

Related guides#

Continue with witness onboarding and verify for external assurance workflows.