Skip to content

kadubon/percolation-inversion-compiler

Repository files navigation

Percolation Inversion Compiler

percolation-inversion-compiler is a production-oriented finite verifier-routing and ECPT collective phase runtime for AI agents. It compiles capability packet candidates, verifier evidence, semantic edge checks, SQOT salience queues, residual ledgers, and runtime events into deterministic JSON so agents can evaluate an ASI-proxy collective phase under declared protocols. ECPT phase progress here is collective packet percolation: it does not require self-rewriting, fine-tuning, or model-weight changes.

Search terms: ECPT, BIT, TRC, SQOT, ASI-proxy collective phase, protocol-relative ASI-proxy phase-control, certificate compiler, proof obligations, residual ledgers, salience queue, packet ecology, semantic edge verification, typed trace normal forms, frontier extraction, AI agent integration, verifier SDK.

What It Does Not Do

  • It does not prove real ASI, physical, simulator, oracle, or policy outcomes.
  • It does not execute unsafe actions or grant authority to mutate repositories, shells, networks, or models.
  • It does not require or model self-rewrite, fine-tuning, or model-weight updates.
  • It does not treat registry metadata, declared status, queue priority, or agent text as evidence.
  • It does not silently promote unresolved external obligations to settled.

Core Workflow

Step Runtime object What the agent gets
1 Fixed agent population A declared population, policy digest, model digest, route allowlist, and no-self-rewrite ledger.
2 Packet candidates Finite capability packets from agent output, local files, fixtures, repositories, or verifier evidence.
3 Evidence + semantic edge checks Hash/provenance checks and typed relations such as theorem-to-code, code-to-test, rollback-support, and execution-path.
4 Verified packet capital Reusable packets promoted only after route, receiver, rollback, authority, edge, and residual policies pass.
5 SQOT salience queue A priority schedule that preserves diagnostic reserve and quarantines stale, unsafe, or hash-invalid packets.
6 Psi dashboard Protocol-relative collective phase components for availability, closure, execution paths, queues, hazards, and basin reachability.
7 Bottleneck / phase tasks Ranked finite tasks for verifier routing, packet repair, edge construction, and phase-control planning.
8 Action results Execution reports and route resolutions that are applied back into the runtime state.
9 Runtime store Persistent event logs, verified packets, route batches, packet lineage, and residual ledgers.
10 Collective phase certificate A fail-closed certificate over fixed population, no self-rewrite, no hidden injection, closure, execution availability, Psi thresholds, and resource-matched baseline.

The runtime is fail-closed: planning can recommend finite ASI-proxy actions, but settled remains false unless scoped verifier rules discharge the required finite obligations. Residual external obligations remain explicit.

Core contract: registry is metadata, not evidence. Use pic doctor and structured checker outputs to distinguish declared status, finite certificate results, proof obligations, and residual ledgers.

Quickstart

Install the development environment:

uv sync --all-extras --dev

1. Inspect Bundled Theory Snapshots

Use this path when you do not have the canonical TeX sources locally.

uv run pic snapshot list
uv run pic snapshot show --artifact ecpt
uv run pic snapshot show --artifact sqot
uv run pic snapshot routes

2. Run One Runtime Step

This produces packet ingestion, SQOT scheduling, Psi components, bottleneck tasks, missing obligations, and residual ledgers.

uv run pic runtime step --state examples/runtime_state.json --input examples/runtime_step_input.json --profile production

3. Certify A Collective Phase Candidate

This checks fixed population, no self-rewrite, no hidden capability injection, accepted closure witnesses, execution-available paths, Psi thresholds, SQOT reserve, hazard/authority checks, and resource-matched baseline conditions.

uv run pic runtime collective-certify --population examples/agent_population.json --state examples/collective_runtime_state.json --basin examples/ecpt_basin_contract.json --baseline examples/runtime_baseline_run.json --threshold examples/runtime_threshold.json

For a complete command inventory, see CLI reference.

Who Should Use This?

  • AI agent integrators who need deterministic JSON for verifier routing, packet promotion, residual-ledger preservation, and fail-closed runtime loops.
  • Researchers studying ECPT, BIT, TRC, SQOT, finite certificate compilers, collective capability percolation, frontier extraction, and protocol-relative phase-control.
  • Tool and runtime maintainers building portable Python, Rust, TypeScript, Go, Julia, or service-based implementations around stable JSON Schemas.

Documentation Map

Canonical Sources

Development Checks

uv run pytest
uv run ruff check .
uv run ruff format --check .
uv run mypy src scripts

License

Code in this repository is licensed under Apache-2.0. The cited Zenodo papers are licensed CC-BY-4.0 by their publisher metadata and are not vendored here.

About

Collective ECPT phase acceleration runtime and finite verifier-routing SDK for ASI-proxy packet percolation, semantic edge verification, SQOT scheduling, fail-closed execution, residual ledgers, provenance, and AI agent integration.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages