ProofPath v0.1 is a CI-verifiable action-boundary evidence gate for AI-agent/API audit logs.
ProofPath turns action-boundary audit logs into CI-verifiable evidence.
AI agents and automated systems may hold valid credentials while still needing a separate check before a high-impact action is executed.
ProofPath adds a pre-execution action boundary:
valid credential
!= valid action
!= valid scope
!= valid reversibility
!= valid approval
ProofPath v0.1 now has two practical surfaces:
| Surface | Path | What it gives you |
|---|---|---|
| CI evidence gate | action.yml, docs/GITHUB_ACTION_QUICKSTART.md, examples/github-action-adoption/ |
Turn audit logs into CI-verifiable metrics and pass/fail checks. |
| Personal Agent Guard | examples/personal-agent-guard/ |
Add a local approval boundary and audit log around Claude Code / Codex-style AI coding tools. |
live demo
-> audit log
-> metrics collector
-> CI verification
-> reusable GitHub Action
-> downstream-style adoption example
-> Personal Agent Guard local workflow
- Read the v0.1 landing page:
docs/LANDING_V0_1.md
- Read the v0.1 milestone:
docs/RELEASE_V0_1.md
- Read the GitHub Action quickstart:
docs/GITHUB_ACTION_QUICKSTART.md
- Inspect the reusable action:
action.yml
- Inspect the metrics tools:
scripts/collect_action_boundary_metrics.py
scripts/assert_action_boundary_metrics.py
- Inspect the downstream-style adoption example:
examples/github-action-adoption/
- Inspect the Personal Agent Guard example:
examples/personal-agent-guard/
- Inspect the reports:
reports/action-boundary-fixture-2026-05-17.md
reports/evidence-metrics-2026-05-17-ci-baseline.md
The Rust workflow currently verifies:
formatting
clippy
Rust tests
Compute Witness Rust CLI fixture
live action-boundary metrics
reusable ProofPath GitHub Action self-test
Personal Agent Guard demo self-test
The key repository product loop is:
ProofPath audit JSONL
-> metrics JSON
-> expected-value assertions
-> CI pass / fail
The key personal workflow loop is:
AI coding tool command
-> local policy
-> scoped approval boundary
-> local audit log
- name: Verify ProofPath action-boundary metrics
uses: safal207/ProofPath@main
with:
audit-log: proofpath-audit.jsonl
metrics-output: proofpath-action-boundary-metrics.json
expected-actions-total: "2"
expected-actions-blocked: "1"
expected-actions-accepted: "1"bash examples/personal-agent-guard/run_demo_check.shExpected path:
first guarded command -> BLOCK
approval token written
second guarded command -> ALLOW
audit log contains both decisions
Safe claim:
ProofPath v0.1 demonstrates reusable CI and local evidence-gate patterns for action-boundary audit metrics.
Stronger but still bounded claim:
ProofPath v0.1 shows that an AI-agent/API action boundary can be expressed as audit logs, measured as metrics, and enforced as CI or local pass/fail evidence.
ProofPath v0.1 does not claim:
production security certification
complete prevention coverage
formal verification
regulatory compliance
external production adoption
large-scenario benchmark coverage
latency benchmark coverage
full sandboxing
ProofPath is a CI evidence gate for AI-agent actions.
ProofPath Personal Agent Guard is a local seatbelt for AI coding tools.
v0.2 = versioned release/tag + larger scenario suite + artifact uploads + latency metrics + richer local guard policies
ProofPath v0.1 is no longer only a protocol idea or local demo.
It now has two working product paths:
audit log in
-> metrics out
-> CI pass/fail
and:
AI tool command
-> local guard
-> approval boundary
-> audit trail