GitHub - cryptictyrant519/keystone-proof: Deterministic execution and replay-verifiable proof infrastructure. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
cryptictyrant519
keystone-proof
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>6 Commits<br>6 Commits
Keystone_Enterprise_Proof
Keystone_Enterprise_Proof
proof
proof
verify
verify
.gitignore
.gitignore
ARCHITECTURE.md
ARCHITECTURE.md
AUDIT_STATUS.md
AUDIT_STATUS.md
ENTERPRISE_SUMMARY.md
ENTERPRISE_SUMMARY.md
INVARIANTS.md
INVARIANTS.md
README.md
README.md
TRUTH.md
TRUTH.md
WHY_KEYSTONE.md
WHY_KEYSTONE.md
View all files
Repository files navigation
Keystone
Deterministic execution and replay-verifiable proof infrastructure.
Core Proof
same input → same execution path → same canonical artifact chain → same proof hash
What Keystone Demonstrates
Keystone demonstrates a proof model for complex execution pipelines where outputs must be reproducible, replay-verifiable, and tied to canonical artifact integrity.
The public package in this repository contains proof artifacts only. It does not contain Keystone's private source code or internal implementation.
Repository Scope
This repository is Keystone's public proof surface.
It contains:
proof artifacts
verification scripts
public architecture documentation
governance documents
replay demonstration material
validation summaries
It does not contain:
Keystone's private production source code
proprietary execution engine internals
recovery engine internals
sync or merge internals
canonicalization or hashing internals
private test harnesses
private design notes
This repository is intended for:
platform engineering reviewers
DevSecOps teams
software supply-chain reviewers
AI infrastructure teams
governance and audit reviewers
technical evaluators who need to inspect Keystone's public proof surface
Public Governance Documents
Recommended review order:
WHY_KEYSTONE.md — why Keystone exists and why execution claims are not enough
TRUTH.md — what Keystone treats as execution truth
INVARIANTS.md — rules that must remain true for execution records to be trusted
ARCHITECTURE.md — public architecture shape and trust pipeline
AUDIT_STATUS.md — current verification posture and public/private boundary
Proof Package
See:
Keystone_Enterprise_Proof/
Contents include:
technical brief
architecture diagram
deterministic demo video
replay verification artifacts
independent repository verification
Keystone self-verification
SHA256 manifest
replay commands
Scope
Keystone is a deterministic execution vault that stores immutable evidence of every state transition and guarantees replay-verifiable truth, provable recovery, and cross-machine identical state.
This repository publishes Keystone's public proof surface, including governance documentation, architecture documentation, audit and verification status, the enterprise proof package, replay-verification artifacts, verification scripts, and reproducibility evidence.
The purpose of this repository is to enable independent evaluation of Keystone's verifiability, governance model, and proof guarantees. Keystone is intentionally structured so that its guarantees can be independently validated without access to the underlying execution engine.
This repository allows reviewers to inspect Keystone's architectural guarantees, review system invariants and governance commitments, validate proof artifacts and verification outputs, reproduce verification procedures, and independently confirm evidence integrity and replay-verifiable truth.
This repository does not include Keystone's private execution engine, orchestration and scheduling internals, deterministic pipeline implementation, vault internals, vault schemas, vault configurations, proprietary state-transition systems, proprietary recovery systems, proprietary evidence-preservation systems, production deployment infrastructure, or operational vault product...