Stage344 extends Stage343 by verifying GitHub Actions run evidence and preparing artifact download verification.
Stage343 verified the external anchor layer:
hash binding
↓
checkpoint witness
↓
Ed25519 witness
↓
GPG
↓
Sigstore
↓
GitHub Actions anchor intent
↓
independent verification report
Stage344 adds:
GitHub Actions Run
↓
Artifact Download preparation
↓
SHA256 verification
↓
Session Manifest verification
↓
GitHub Artifact Verification Report
What Stage344 Adds
GitHub Actions run verification
Latest workflow run inspection
SHA256 binding check against external_anchor_receipt.json
Connection to Stage343 independent verification report
Artifact download command preparation
github_artifact_verification_report.json
github_artifact_verification_summary.txt
Public Files
docs/artifacts/github_artifact_verification_report.json
docs/artifacts/github_artifact_verification_summary.txt
docs/verification/independent_verification_report.json
docs/anchors/external_anchor_receipt.json
docs/session/session_manifest.json
Artifact Download
After a GitHub Actions run completes:
gh run list --workflow "Stage342 External Anchor"
Download the artifact:
gh run download <RUN_ID> \
-n stage342-external-anchor-artifacts \
-D downloaded_stage344_github_artifact
The downloaded directory is intentionally excluded from GitHub.
Safety Boundary
Stage344 does not publish:
private keys
attack code
dangerous prompts
exploit payloads
bypass procedures
automated attack logic
Meaning
Stage344 moves REMEDA/QSP from:
independent external anchor verification
to:
GitHub Actions artifact verification readiness
This continues the Stage254 direction:
GitHub Actions run
↓
artifact download
↓
independent verification
License
MIT License
Copyright (c) 2025 Motohiro Suzuki