Lance Amundsen Research
GitHub Repository ↗
Public Beta · Runtime Interface Freeze 1

PV-PP Runtime API

A runtime API for building applications with the Productive Value–Productive Power (PV-PP) framework. Runtime v0.70 provides a frozen common interface for application registration, decision evaluation, action licensing, bounded execution, and explicit host-owned state transition.

View Source on GitHub Developer Start
Current Runtime v0.70
Interface Status Runtime Interface Freeze 1
Documentation Public Beta

What this project is

The PV-PP Runtime API is the common application interface for the Productive Value–Productive Power framework. It separates generic PV-PP decision architecture from application-specific world semantics. The host application remains authoritative for the actual world and Layer-1 state transition; the runtime evaluates the represented decision state and determines what action is selected and licensed.

PPP → Φ → H → G → R → graph/seed substrate → Π → Π completeness → Constraints → Domain Framing → Restoration Adequacy → Σ → ε
Shared policy projection Q is used during candidate evaluation. Developers normally call the integrated runtime interfaces rather than reproduce the operator sequence manually.

Validation before interface freeze

Runtime v0.70 was frozen after regression and external integration testing. The freeze is intended to prevent unnecessary architectural churn while preserving a clear path for correction if a reproducible application or benchmark failure reveals a genuine defect.

496 / 496

Internal regression suite

Passed against the frozen runtime.
77 / 77

External Small Economy integration suite

Passed unchanged against v0.70.
≈ 50

Subsequent simulation builds

No additional framework/runtime defects exposed.
Freeze rule: v0.70 should not be changed merely because another design appears cleaner or more convenient. Runtime changes should be considered only when reproducible application or benchmark evidence demonstrates a genuine implementation or architectural defect that cannot reasonably be handled compatibly.

Host/runtime boundary

The runtime owns

  • the common PV-PP decision architecture;
  • registered governance and recovery structure;
  • candidate evaluation and shared projection interfaces;
  • Σ selection and execution licensing; and
  • bounded execution through epsilon.

The host owns

  • authoritative actual state;
  • application-specific world semantics;
  • external persistence and effects;
  • world projections supplied through runtime boundaries; and
  • the authoritative Layer-1 state transition.

Selection by the runtime does not itself mutate the actual world. That separation is deliberate.

Developer starting point

New integrations should begin with the current v0.70 common API, not older custom PV-PP applications. The recommended first example is examples/minimal_battery_service/.

Core interfaces

  • PVPPRegistry
  • WorldAdapter
  • PVPPRuntime
  • canonical decision-cycle interface
  • execution licensing and epsilon
  • explicit Layer-1 transition and transition provenance

Quick test

python3 -m pip install pytest
python3 -m pytest -q

The frozen v0.70 regression suite should report 496 passed.

Run the first native example

python3 -m pytest -q examples/minimal_battery_service/test_minimal_battery_service.py
PYTHONPATH=. python3 examples/minimal_battery_service/minimal_battery_service.py

The example demonstrates registry construction, Productive Power and domain registration, action and recovery registration, graph-native Π structure, shared projection Q, canonical decision-cycle evaluation, Σ selection, execution licensing, epsilon, explicit host-owned Layer-1 transition, transition validation, and provenance.

Important implementation notes

Runtime v0.70 requires every registry to contain an action whose identifier is exactly steady. It represents the baseline or no-intervention continuation used by the canonical runtime. Applications may assign application-specific semantics to that action, but the registered ID must remain steady.

The repository also contains historical example worlds and benchmark support modules because the frozen regression suite depends on them. They are retained for regression reproducibility and should not be treated as the recommended architecture for new applications.

What v0.70 does not attempt to provide

The frozen interface does not claim to provide a universal persistent database or RuntimeStore, autonomous scheduler, LLM semantic adapter, learning rule, memory storage algorithm, unrestricted graph search mechanism, or universal arbitration rule for jointly impossible recovery obligations.

Those concerns remain host-owned, application-specific, or outside the present runtime interface.

Project links

Source repository

Frozen Runtime v0.70 source, regression suite, public example, benchmark support fixtures, and beta developer materials.

github.com/AmundsenLance/PV-PP-Runtime-API ↗

Developer reference

PV-PP Volume Six — Runtime API Reference
Beta Developer Documentation for Runtime v0.70.

The runtime implementation itself remains the ultimate authority for callable behavior.

About PV-PP

Productive Value–Productive Power (PV-PP) is an economic and decision framework centered on Productive Value, Productive Power, represented and perceived productive state, governing domains, recovery structure, and viability-aware action selection.

This project page concerns the runtime API specifically. It is not intended to reproduce the complete theoretical, mathematical, benchmark, or research record of the PV-PP framework.