agentic-proofkit

Reusable CLI and JSON proof infrastructure for spec-to-proof workflows in software repositories.

agentic-proofkit helps repositories validate structured requirements, bind requirements to proof routes, plan selective checks, admit receipt-shaped evidence, render human views, and give coding agents bounded next-action packets without copying verifier logic between projects.

Current Repository State

| Surface | State | |---|---| | Source visibility | Public-source release provenance is not claimed until a release is produced from public source | | Current layer | Staged public source import | | Runtime implementation | Source present; release readiness still requires release evidence | | Package release | Not claimed by this repository state | | Public-source provenance | Not claimed until a reviewed release is produced from public source | | License | MIT |

Project Boundary

agentic-proofkit is intended to provide reusable proof-workflow mechanics for repositories that want explicit requirements, proof bindings, deterministic reports, and bounded guidance for coding agents.

Proofkit does not own a consuming repository's product requirements, native witness execution, receipt authenticity, proof freshness, merge admission, rollout, deployment, or production readiness.

Start Here

| Need | Owner | |---|---| | Human orientation | This README | | Coding-agent startup | AGENTS.md | | Adoption and release-channel model | ADOPTION.md | | Completion criteria and remaining work | BACKLOG.md | | Contribution rules | CONTRIBUTING.md | | Vulnerability reporting boundary | SECURITY.md | | Explicit boundary denials | NON_CLAIMS.md | | LICENSE | MIT license |

Non-Claims

This README is a human landing page. It is not a CLI contract, release proof, package publication claim, security audit, or consumer readiness claim. CLI and package behavior are owned by their source, tests, machine-readable contracts, and release evidence, not by this overview.