Audit access

Each LayerQu chain score is built from a packet of foundation specifications, source commits, and third-party analyses held in our internal audit repository. The public chain card carries the substantive claim and the source category, not the underlying URL list. A single broken or stale link in a public scorecard does more damage to the reader than the link adds in transparency.

Reviewers who need the underlying packet for verification can request it below. We grant access on a case-by-case basis to chain foundations, regulators, standards bodies, researchers, and institutional reviewers with a stated verification need.

Request audit packet

What is in a packet

A LayerQu audit packet for a single chain contains:

• The structured scorecard JSON (all seven dimensions, sub-scores, gates, caps, source-disagreement disclosure, X+Y vs Z timing block).
• The evidence URL list per sub-score (foundation specifications, governance proposals, code commits, audit reports, peer-reviewed papers, foundation blog posts).
• The audit trail markdown for the chain, with primary-source citations and our internal evaluation notes.
• Methodology v3.1.0 reference and the change log against v3.0 and v2.

Why public chain cards do not carry the URLs

A single broken or stale link in a public scorecard does more damage to the reader than the link adds in transparency. URLs decay, get redirected, or point at content that has been silently edited. The public chain card therefore carries the substantive claim and the source category. Reviewers who need to reconstruct the score from primary sources receive the audit packet on request, where every link is paired with the date we evaluated it and a hash of the artifact at evaluation time.