Role
Evidence boundary
Draws a clear line between public evidence and private source verification.
Public
Aggregate evidence
Lets readers inspect metric behavior, charts, and method provenance.
Private
Source audit
Keeps protected texts, identities, titles, and reconstructable mappings outside the public site.
Evidence Frame
Public-safe topics
- authorship and condition claims at a structural level
- first-draft and unaided-writing constraints
- versioned outputs and chart-generation records
- platform-side history where relevant
- export records and reproducibility notes
- hash/version discipline where appropriate
- controlled disclosure paths
What public provenance can show
Public provenance can show the chain from method to evidence: which chart assets were generated, what metric families were used, how pages map to outputs, and how aggregate results support the findings.
It can also show exception tracking. A credible public result should not hide every place where the headline segment is not first. Those exceptions define the boundary of the claim instead of weakening it.
What this page proves / does not prove
This page supports an integrity claim: PRM separates public evidence, protected source material, and controlled review materials into distinct layers.
It does not publish source text, private manifests, source-level mappings, or NDA-level audit packets. It shows how the public claim is bounded, where the evidence trail is visible, and where deeper verification should move into controlled review.
Private review topics
- full source manifests
- private mapping tables
- provenance files
- source-level documentation
- protected corpus material
- technical review packets
Review boundary
The boundary is simple: public pages explain method and aggregate results; private review materials support source-level verification.
That keeps the public site useful without exposing raw writing, third-party source mappings, or reconstructable manifests. It also gives serious reviewers a path to inspect provenance without making the website a source dump.
Controlled review path
The next step for technical diligence, research review, or licensing discussion is controlled review rather than public download.
Controlled review can cover source manifests, provenance files, version records, reproducibility notes, audit-supporting materials, and source-level verification materials where appropriate. Training, fine-tuning, benchmark use, or dataset licensing rights are separate discussions and are not implied by the public website.
Why it matters
PRM is strongest when the claim, the evidence, and the review path are visibly separate.
The claim belongs on public pages. The evidence appears as aggregate charts and method notes. The source-level proof belongs in controlled review. Keeping those layers distinct makes the public story cleaner and the technical story more defensible.
How to read the charts
Start with the coverage dashboard. It shows the analysis surface behind the public site: workbooks, metrics, tokenizers, segments, slice sizes, and chart exports.
Then read exception count as a trust signal. It makes visible where the headline result is not first, which is part of honest provenance.
Tokenizer robustness and the metric-slice heatmap show whether the result persists across processing choices and measurement windows. The public-safe gauntlet dashboard ties those outputs back to the main comparison environment without exposing protected text.
Public-safe limits
This page does not publish raw writing, protected excerpts, third-party source text, private file manifests, source-level mappings, artist names, album titles, or song titles.
Public-safe boundary
Public pages show aggregate evidence, metric behavior, method provenance, and corpus structure. Protected text, identities, source titles, and reconstructable mappings stay private.