Skip to content

PIC v1.1.0 - Verified Operation and Acceleration Runtime

Latest
Latest

Choose a tag to compare

View all tags
@kadubon kadubon released this 11 Jul 07:05
v1.1.0
61c4fa7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PIC v1.1.0 helps agents turn candidate capabilities into evidence-checked, reusable results without treating activity as progress.

Quick start

python -m pip install "percolation-inversion-compiler==1.1.0"
pic agent check --compact

Install the optional operation tools only when you need an explicitly approved adapter:

python -m pip install "percolation-inversion-compiler[operation]==1.1.0"
pic operation adapter-check --manifest adapter.json

What is new

  • Resource-matched acceleration certificates compare a baseline and candidate under the same horizon, stopping rule, evidence, resources, observation protocol, constraints, and receiver family.
  • Direction-aware metrics cover time to verified results, verification yield, residual half-life, receiver reuse, certified capital gain, resource cost, and error correlation.
  • Unknown values remain unknown. They are not replaced with zero or counted as positive progress.
  • BIT gains require a witness; SQOT uses measured attention and verification costs; ALT rechecks admission evidence; TRC uses finite traces and an explicit operation gate.
  • Real-world operations follow adapter-check -> plan -> preflight -> approve -> dispatch -> verify -> reconcile, with approval digests, expiry, nonce replay protection, SSRF defenses, bounded I/O, and independent verification.
  • Strict bounded JSON/YAML readers, UTC freshness checks, deterministic schemas, cross-platform smoke tests, and Python/TypeScript contract fixtures improve deployment reliability.

Safety boundary

PIC does not prove real ASI, consciousness, legal authority, consent, or a physical outcome. Check and AFST commands never dispatch side effects. A provider receipt proves only that a call was attempted. physical_outcome_proven remains false, and physical_outcome_verified requires a separately validated verifier report with matching scope and observation window.

Compatibility

v1.1.0 is additive and keeps the v1 API and CLI. Existing callers can migrate gradually. Strict CLI and interop boundaries now reject coerced numeric strings, string booleans, non-finite values, and ambiguous timestamps.

See the README, docs/migration-v1.1.md, docs/resource-matched-measurement.md, and docs/operation-security.md for complete examples.

Assets 8
Loading