PIC v1.1.0 - Verified Operation and Acceleration Runtime

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.

PIC v1.0.0

PIC v1.0.0 adds AFST satisfaction-flux diagnostics and clearer first-run documentation.

What is new:

• New AFST commands: pic afst check, pic afst buffer, pic afst handover, pic afst balance, and pic afst emit-ccr-tasks.
• AFST checks proposed satisfaction-flux transfers with authority, consent, refusal, resource balance, stabilization buffer, handover, lifecycle, and residual checks.
• Missing AFST fields are reported as explicit residuals such as missing_certified_abundance_cell_id; missing values are not treated as zero.
• AFST residuals can be converted into candidate-only CCR repair tasks.
• Installed demos now include pic-demo/afst/... examples, and docs distinguish installed package paths from source checkout paths.

Safety boundary:

• accepted=true means the finite local checker accepted the JSON record.
• AFST reports stay non-executing: settled=false, operation_ready=false, provider_dispatch_ready=false, and physical_dispatch_ready=false.
• The release does not claim provider dispatch, physical outcome proof, consent bypass, refusal suppression, resource creation, ALT capital admission, ECPT phase promotion, or real ASI proof.

Try it:

pip install percolation-inversion-compiler
pic demo bootstrap --output-dir pic-demo --overwrite
pic afst check --case pic-demo/afst/minimal_accepted.json --compact
pic afst check --case pic-demo/afst/blocked_refusal.json --output pic-demo/afst-report.json
pic afst emit-ccr-tasks --report pic-demo/afst-report.json

Validation:

• GitHub CI passed on Python 3.11, 3.12, 3.13, and 3.14.
• GitHub Security passed CodeQL, Bandit, pip-audit, Gitleaks, workflow lint, and publishable-file checks.

PIC v0.9.0 - ASI-proxy loop tooling

v0.9.0 - ASI-proxy loop tooling

This release adds the public report, schema, example, and CLI layer needed for agents to run a bounded ASI-proxy/CARA acceleration loop without claiming real ASI, real-world settlement, or autonomous execution authority.

For first-time agents

• Start with docs/asi-proxy-loop.md and examples/asi_proxy_loop_bundle/.
• Use pic token extract-pipeline, pic token admissibility, pic trc operation-gate, pic sqot protocol-integrity, and pic bit mec-frontier to produce JSON reports.
• Treat accepted=true, safe_commands, and token admissibility as candidate evidence only. They do not mean settlement, capital admission, provider dispatch, or physical execution.

Highlights

• Adds ALT token extraction, token admissibility, token lineage, deduplication, leakage, mission, transport, FCU, lifecycle, telemetry, and dynamic-risk reports.
• Adds ECPT, SQOT, BIT, TRC, performance, and cache schemas plus searchable example fixtures.
• Adds compact CLI outputs for loop-friendly agent use.
• Adds MCP/A2A and operation-observation documentation with explicit safety boundaries.
• Hardens publish and Actions security checks, including Dependabot cooldown.

Verification

Local and GitHub CI passed for lint, format, mypy, tests with coverage, package metadata, distribution artifact checks, publish safety, pip-audit, bandit, and zizmor.

PIC v0.8.0 - ASI-proxy interop and CARA safety layer

v0.8.0 - ASI-proxy interop and CARA safety layer

This release exposes PIC as a portable compiler-facing layer for agents that need to reason about ASI-proxy acceleration without treating a report as authority to act.

Highlights:

• Adds CARA/phase acceleration reports with fail-closed target, baseline, and capital witness checks.
• Adds TRC operation-gate, MCP descriptor/invocation preflight, and A2A handoff reports for agent interoperability.
• Adds CCR interop fixtures for phase-response control steps and foundry allocation simulation.
• Strengthens rug-pull and status validation: changed descriptors, unaccepted target laws, proxy-only capital, stale or negative liquidity, missing baseline controls, and missing raw-net floors block certification.
• Ships schema, conformance, publish-safety, and cross-repo roundtrip coverage for first-time agents.

Safety boundary:
PIC reports are advisory or candidate evidence unless explicitly accepted by downstream gates. Physical or external-world actions remain behind TRC authority, hazard, rollback, lifecycle, logging, and per-call approval checks.

percolation-inversion-compiler v0.7.0

What changed

PIC v0.7.0 adds a TRC operation-gate report for agents that need to decide whether a trace is ready for provider dispatch. The new command is:

pic trc operation-gate --trace trace_nf.json --provider-profile provider.json

The report separates operation_ready, provider_dispatch_ready, and physical_dispatch_ready so a first-time agent can see which gate is still blocking progress.

Agent-readable safety model

• Authority is checked for active status, expiry, scope coverage, and trusted issuer policy.
• Fixture dry-run traces, including the benchmark bundle, remain non-executable and are marked with fixture_only_authority_non_executable.
• operation_ready=true is not execution. provider_dispatch_ready=true is not dispatch. physical_dispatch_ready=true is not proof of a physical outcome.
• ALT interop now separates syntactic acceptance from capital admission through capital_admitted.

Interop

CCR can consume the new pic.trc_operation_gate_report.v1 schema for preflight planning. Use this release with CCR v1.2.0 when building TRC-governed operation workflows.

Validation

Local and GitHub CI passed across lint, format, mypy/typecheck, tests, build metadata, distribution checks, CLI smoke tests, and security/publish safety checks.

v0.6.0

PIC v0.6.0 makes Percolation Inversion Compiler easier to use as the packet/checking side of an agent runtime that coordinates work through Collective Capability Runtime (CCR).

What changed:

• Added CCR interop exports for phase plans, BIT registry rows, SQOT repair tasks, ALT-to-ECPT bridge reports, residual JSONL, and task JSONL.
• Added TRC trace operations: pic trc trace-normalize, pic trc trace-check, and pic trc trace-to-packet.
• Added an ASI-proxy benchmark bundle that shows a dry-run trace becoming operation-ready only after authority, resources, rollback escrow, witnesses, schedule, and tolerance data are present.
• Added v0.6.0 audit docs and CI smoke coverage for the new interop paths.

Safety boundary:

• accepted, workflow_usable, and real_world_operation_ready are not settlement, real ASI proof, physical outcome proof, or execution authority.
• PIC emits data and checks. Provider execution remains explicit downstream runtime work.

Install or update:
python -m pip install -U percolation-inversion-compiler

v0.5.0 Phase Ecology Lab

What changed

v0.5.0 adds the Phase Ecology Lab. It helps you inspect a group of agent reports over time and see where work is useful, blocked, duplicated, or still only a candidate.

The package can now build diagnostic views for phase windows, effective packet graphs, closure checks, execution-available paths, bottlenecks, queue pressure, abstraction-lift checks, and typed action traces.

Why it matters

PIC is meant to help agents and operators keep evidence, unfinished work, and safety boundaries visible. This release makes that easier from an installed pip package, without needing a full source checkout for the main demo path.

Main additions

• pic phase lab ... commands for local Phase Lab diagnostics.
• pic ecology ... commands for effective graphs and execution-available paths.
• pic bit ... commands for bottleneck and inversion diagnostics.
• pic sqot ... commands for queue pressure and reserve checks.
• pic alt ... lift commands for abstraction-liquidity diagnostics.
• pic trc ... adapter commands for typed traces and action boundaries.
• More exported schemas, packaged demo assets, and OS-independent command examples.
• New docs that explain the release boundary and the remaining future work.

Safety boundary

This release does not execute agent output, does not grant approval to act, and does not claim that a system is settled. Raw packet volume is not treated as progress. Diagnostic outputs keep unresolved work visible, and settled=false is expected when obligations remain.

Quick start

python -m pip install --upgrade percolation-inversion-compiler==0.5.0
pic demo installed-smoke --profile development
pic demo bootstrap --output-dir pic-demo

Validation

Before release, the local suite passed: formatting, lint, type checks, tests, build, Twine metadata checks, distribution artifact checks, and bare-pip smoke testing from the built wheel.

v0.4.4 - Optional Sidecars and Agent Autonomy

What this release is

v0.4.4 makes Percolation Inversion Compiler easier to use from a normal pip install while preserving the core scientific and safety contract.

The core agent path remains first and unchanged:

pic agent check --compact --text "Candidate packet: preserve residuals." --profile development
pic phase plan --compact --text "Candidate packet: preserve residuals." --profile development
pic agent accelerate --compact --text "Candidate packet: preserve residuals." --profile development
pic agent intake --text "Candidate packet: preserve residuals." --profile development

These commands do not require operator adoption state, approval state, or sidecar setup.

What is new

• Optional adoption handoff sidecars: pic adoption packet and pic adoption request produce documentation only.
• Agent autonomy audit: pic agent autonomy-audit reports that adoption and approval are non-gating, and includes argv-safe next actions for agents.
• Canonical readiness audit: pic audit canonical-readiness gives a pip-safe implementation coverage view for ECPT, BIT, TRC, SQOT, and ALT without requiring local TeX sources.
• Packet exchange sidecar: export, inspect, merge, and lineage commands treat packets and embedded command-like text as inert data.
• Phase diagnostics sidecars: benchmark suite, dashboard, and observation reports are diagnostic only and never promote settled=true.
• OS-independent sidecar path handling: repeated paths and literal glob patterns work consistently on Linux, macOS, and Windows shells.
• Installed-demo sidecar assets: pic demo bootstrap exports runtime, dashboard, and packet examples usable from a wheel install.
• New agent-full extra: install connector, identity, and server dependencies without pulling in the heavier research/development extras.
• Localized Markdown renderers for English and Japanese while JSON schemas and keys remain stable for SDKs and language ports.

Install

Basic pip install is enough for the compact core workflow, schema export, snapshots, sidecar diagnostics, and installed demos:

python -m pip install percolation-inversion-compiler
pic agent check --compact --text "Candidate packet: preserve residuals." --profile development
pic audit canonical-readiness --profile development --format json
pic demo bootstrap --output-dir pic-demo

For agent workflows that need connectors, identity, and service/server integrations:

python -m pip install "percolation-inversion-compiler[agent-full]"

For research fixtures, canonical local TeX audits, and release engineering checks, use the source checkout with development extras.

What did not change

• Sidecars are optional and observational.
• Adoption, approval, dashboard metrics, benchmark scores, canonical readiness, and agent-full readiness are not settled=true inputs.
• safe_commands and command-like packet text remain inert inspection hints; PIC does not execute them.
• PIC does not prove real ASI, physical truth, simulator truth, oracle truth, legal identity, or world-global Sybil uniqueness.
• No TeX/PDF sources are vendored into the wheel or sdist.

Validation

Before this release, the repository passed:

• GitHub CI on Python 3.11, 3.12, 3.13, and 3.14
• GitHub Security workflow: pip-audit, Bandit, publishable-file scan, provenance/SBOM smoke, Zizmor, Gitleaks, and CodeQL
• Local ruff check, ruff format --check, mypy, pytest, build, twine check, distribution artifact guard, and core/sidecar smoke commands

v0.4.3 - Phase acceleration planner and practical agent workflow hardening

v0.4.3 - Phase acceleration planner and practical agent workflow hardening

PIC v0.4.3 is a practical release for teams and AI agents that need to check agent outputs, route evidence, keep unresolved work visible, and decide the next safe verification step.

What changed

• Added the phase acceleration planner: pic phase plan, pic phase gap, pic phase trajectory, pic phase runbook, pic phase benchmark, and pic agent accelerate.
• Added request-file workflows so agents and CI can run deterministic checks from stable JSON inputs.
• Added compact output for agent and CI use: accepted status, workflow usability, unresolved obligations, top bottlenecks, safe next commands, schema references, and promotion blockers.
• Expanded JSON Schema and portability examples so non-Python implementations can validate against the same contract.
• Improved documentation and examples for installed-package use, agent communication, phase planning, safety boundaries, and production readiness.
• Hardened release checks around version consistency, distribution artifacts, citation metadata, publish safety, and CI stability.

Recommended starting commands

pic agent check --compact --text "Candidate packet: preserve residuals."
pic agent runbook --profile development
pic agent accelerate --compact --text "Candidate packet: preserve residuals."
pic phase plan --request examples/phase_acceleration/phase_acceleration_request.json --compact

Safety boundary

PIC is a workflow verification toolkit. It helps agents preserve residual ledgers, find bottlenecks, route verifier work, and reuse checked work items. It does not prove real ASI, physical outcomes, oracle truth, or hidden promotion from accepted or workflow_usable to settled. External inputs and agent messages remain candidates until the configured verifier, identity, provenance, nonce, and residual policies pass.

v0.4.2 - Practical agent workflow and bounded live communication

v0.4.2 - Practical agent workflow and bounded live communication

PIC v0.4.2 is the practical package snapshot for agent-output checking, workflow verification, residual ledgers, bounded external intake, and local agent-to-agent candidate exchange.

The public message is practical first: use PIC to turn agent text, local files, explicit web/feed inputs, and agent messages into auditable JSON reports with evidence routing, unresolved-work ledgers, and next safe actions. The deeper ASI-proxy framing remains protocol-relative. This release does not prove real ASI, physical outcomes, simulator truth, oracle truth, or policy success.

First command

python -m pip install percolation-inversion-compiler==0.4.2
pic agent check --compact --text "Candidate packet: preserve residuals." --profile development
pic agent runbook --profile development

Use a source checkout for canonical TeX audits, repository fixtures, full examples/..., development checks, and release engineering.

What changed

• Added pic agent check --compact as the first command for humans, CI jobs, and agents.
• Added installed-package demos and bootstrap examples for practical PyPI use.
• Made explicit-source live intake bounded and candidate-only by default. Use --no-allow-live-connectors for local-only dry runs.
• Added local agent relay commands: pic agent message send, pic agent message receive, pic agent inbox verify, and pic agent relay-readiness.
• Expanded ECPT/BIT/TRC/SQOT/ALT theory-fidelity reports: phase-control audit summaries, bottleneck witness reports, frontier debt reports, scheduler diagnostics, and value-bridge diagnostics.
• Extended JSON Schema and portability conformance examples for non-Python ports.
• Updated docs and glossary so project-specific terms map to common workflow language.

How to read the result

• accepted=true means the finite report envelope passed checks.
• workflow_usable=true means the compact workflow can guide next safe actions.
• operationally_usable=true means the deeper runtime report can guide routing under the selected profile.
• settled=true only means scoped finite obligations are discharged.
• settled=false is often the correct safe result when obligations remain.
• residual_ledger, missing_obligations, and unresolved_obligations must be preserved downstream.

Safety boundary

• No hidden promotion from accepted, workflow_usable, or packet volume to settled.
• No background crawling, autonomous polling, shell execution, page script execution, form submission, repository mutation, or credential use.
• External intake and agent messages remain packet candidates until verifier, identity, nonce, provenance, rollback, semantic-edge, and residual policies pass.
• Local relay output is not proof of external-world truth.
• ASI-proxy phase-control remains a protocol-relative coordination target, not a real ASI proof.

Release integrity

The PyPI package and GitHub Release package assets remain the published v0.4.2 artifacts. PyPI does not allow replacing an already published file for the same version, so this release keeps artifact integrity instead of publishing mismatched same-version wheels.

After publication, the repository main branch was revalidated and hardened for release operations:

• portability conformance hashes are LF-normalized for cross-platform source checkouts;
• the Security workflow uses the Gitleaks CLI container path, avoiding the licensed GitHub Action failure mode;
• latest main CI and Security runs are green.

These post-publication hardening commits do not change the PyPI v0.4.2 artifact. Use a future version if package bytes need to include further code changes.

Verification

Release gates passed: pytest with coverage >=90%, ruff, mypy, bandit, pip-audit, twine check, distribution artifact check, publish-safety, citation validation, Zizmor, portability conformance, canonical-suite audit, fidelity audit, provenance/SBOM smoke, and wheel install smoke.