Skip to content

labtrust-release

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

labtrust-release

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
RELEASE_FIXTURE_MANIFEST.json
RELEASE_FIXTURE_MANIFEST.json
 
 
formalization_readiness_report.json
formalization_readiness_report.json
 
 
handoff_manifest.bundle_to_verifier.v0.json
handoff_manifest.bundle_to_verifier.v0.json
 
 
handoff_manifest.certificate_to_bundle.v0.json
handoff_manifest.certificate_to_bundle.v0.json
 
 
handoff_manifest.runtime_to_certificate.v0.json
handoff_manifest.runtime_to_certificate.v0.json
 
 
handoff_manifest.signed_bundle_to_memory.v0.json
handoff_manifest.signed_bundle_to_memory.v0.json
 
 
handoff_to_certifyedge.json
handoff_to_certifyedge.json
 
 
handoff_to_pf.json
handoff_to_pf.json
 
 
invalid_mismatched_certifyedge_commit_manifest.json
invalid_mismatched_certifyedge_commit_manifest.json
 
 
invalid_mismatched_labtrust_commit_manifest.json
invalid_mismatched_labtrust_commit_manifest.json
 
 
invalid_mismatched_pf_commit_manifest.json
invalid_mismatched_pf_commit_manifest.json
 
 
invalid_placeholder_commit_manifest.json
invalid_placeholder_commit_manifest.json
 
 
labtrust_release_fragment.json
labtrust_release_fragment.json
 
 
lean_check_result.v0.json
lean_check_result.v0.json
 
 
manifest.json
manifest.json
 
 
proof_obligation.v0.json
proof_obligation.v0.json
 
 
proof_obligation_hints.json
proof_obligation_hints.json
 
 
proof_obligation_identifiers.json
proof_obligation_identifiers.json
 
 
regeneration_report.json
regeneration_report.json
 
 
release_chain_validation_result.v0.json
release_chain_validation_result.v0.json
 
 
release_manifest.v0.json
release_manifest.v0.json
 
 
runtime_receipt.json
runtime_receipt.json
 
 
science_claim_bundle.certified.json
science_claim_bundle.certified.json
 
 
science_claim_bundle.pending.json
science_claim_bundle.pending.json
 
 
scientific_memory_import_report.json
scientific_memory_import_report.json
 
 
signed_science_claim_bundle.json
signed_science_claim_bundle.json
 
 
trace.json
trace.json
 
 
trace_certificate.json
trace_certificate.json
 
 
trace_hash_alignment.json
trace_hash_alignment.json
 
 
verification_result.json
verification_result.json
 
 
workflow_profile.v0.json
workflow_profile.v0.json
 
 

README.md

LabTrust v0.1 release fixtures

Generated PCS v0.1 release evidence for the LabTrust QC workflow comes from one atomic cross-repo chain spanning LabTrust-Gym, CertifyEdge, Provability Fabric, and Scientific Memory, and maintainers refresh the directory through the materialize workflow instead of editing individual files by hand.

Schema-only conformance examples live in ../labtrust/ and serve validation tests separate from release evidence.

Regenerate

From a sibling LabTrust-Gym checkout, run the clean chain.

export PCS_DETERMINISTIC=0
export CERTIFYEDGE_SOURCE_COMMIT="$(git -C ../CertifyEdge rev-parse HEAD)"
export PF_SOURCE_COMMIT="$(git -C ../provability-fabric rev-parse HEAD)"
bash examples/pcs_qc_release/scripts/run_pcs_v01_clean_chain.sh

Import into pcs-core with validation before replacing this directory.

export PCS_CHAIN_WORK=../LabTrust-Gym
just generate-labtrust-release-fixtures

RELEASE_FIXTURE_MANIFEST.json records producer commits and SHA-256 digests for every file.

Protocol artifacts

The digest-signed protocol layer regenerates through just materialize-labtrust-protocol.

File Type
release_manifest.v0.json ReleaseManifest.v0
handoff_manifest.*.v0.json Stage handoffs
handoff_to_pf.json Alias for bundle-to-verifier handoff
release_chain_validation_result.v0.json 30-check attestation
RELEASE_FIXTURE_MANIFEST.json Digest manifest used by pcs validate-release-chain

On Windows run the PowerShell materialize script.

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/materialize-labtrust-protocol.ps1

Formal checks

Optional Lean trust-kernel artifacts include proof_obligation.v0.json and lean_check_result.v0.json as described in docs/lean-trust-kernel.md.

Validate

pcs validate-release-chain examples/labtrust-release/
just validate-labtrust-release-fixtures
cd python && pytest -q tests/test_release_chain.py tests/test_release_fixtures.py

The validator runs 30 checks documented in docs/labtrust-release-fixtures.md.

Negative fixtures live under ../labtrust-release-invalid/.

Authority

Downstream repositories use this directory at a pinned pcs-core tag as PCS v0.1 LabTrust release evidence, with policy in docs/labtrust-release-fixtures.md and profile notes in docs/labtrust-v0.1-profile.md.