Published synthetic example · independent checks welcome
Let your examiner
check the work.
A signed package is useful only if someone else can inspect it. Download the sample records, examine each claim against its cited bytes, and use the review instructions to record an independent finding.
ZIP · 0.91 MiB · 116 claims · 66 evidence records · Source commit 0df6fec1f780 ↗
What is ready, and what is not
Ready to examine.
Not externally reviewed.
The toolkit is prepared for an examiner’s own checks. Publishing it does not create an endorsement, prove the source material is authentic, or measure performance on real matters.
- Published material
- Synthetic demonstration only
- Independent human review
- NOT PERFORMED
- Claim review status
- All 116: NOT REVIEWED
- Trusted reviewer reports
- 0
- Empirical field accuracy
- UNMEASURED
- Reference software checks
- PASSED
A review another person can own
Inspect the claim.
Keep your own conclusion.
- 01 / READ
Open the claim list.
The viewer presents the claims and their source references. Treat each statement as a proposition to check, not a conclusion you must accept.
Inspect individual claims ↗ - 02 / CHECK
Use your own process.
Download the examiner kit. Follow its instructions to inspect source bytes, commitments, signatures and the stated computational results.
Get the offline kit ↓ - 03 / RECORD
Return signed findings.
Record what you checked and what you did not. Use an agreed private channel to return a reviewer report; this page is not an upload or intake channel.
Discuss the review process ↗
Inspectable source material
The package, not just the presentation.
The offline archive contains the original portable viewer. Machine-readable records are also available separately below.
Commitments for independent comparison
Keep a reference outside the package.
Hashes identify these exact published bytes. An embedded producer key checks package integrity; independently retained keys and records are needed when signer provenance matters.
- Archive SHA-256
- 2497b69527c883853eed42d6c4c2720656852d696f6b49e05ae9e8c8519c9937
- Manifest BLAKE2b-256
- 2992299a64ca16cd0f893f37180091c14c79a1a8bb6d9d463ff4755ea34160aa
- Case Merkle root
- 0eb899d5528bdcbc845f7a56c05d37484351d41d680a153992b7b68f1b05ebc8
- Producer Ed25519 public key
- b7514cb4d8ba09bc1486d1e8420f4f6e823f440feee423be332a37d4d29bef91
Source execution binding and software-test scope
These are development and reference checks, not a count of external reviews or a field-accuracy benchmark.
704 tests passed; 1 skipped. Scope: Producer-maintained suite passed in source checkout and again from the frozen kit; optional PyTorch skipped. This is not an independent external audit.
{
"observation_stage": "ANALYSIS_START_AND_END_UNCHANGED",
"qualification": "Signed process observations are not independent machine or identity attestation.",
"record_blake2b_256": "9dca10bdddc81446540c6ff8e0609cb9fd8bc7f4d4488aefd6744e36299f0b13",
"recorded_source_commit": "0df6fec1f780c9742ae89ec908e4ce60b1a94d3d",
"source_byte_match": true,
"status": "EXACT_RECORDED_ANALYSIS_SOURCE_BYTES"
}Package scope: SYNTHETIC_SOFTWARE_REVIEW_DEMONSTRATION
The evidence stays inspectable.
The judgment stays independent.
This public kit uses synthetic records. No independent human conclusion or real-world accuracy claim is represented. Actual professional work requires authenticated records, agreed scope and appropriate review.
Back to SUBROSA in plain English ↗