1 · Start here
PVPP Getting Started
The shortest path into the runtime: understand the framework/runtime/host boundary, verify frozen v0.167, and build a small runnable battery application.
Current Frozen RuntimeRuntime V2.1 · v0.167
Regression Baseline1320 / 1320 passing
Programmer DocumentationGetting Started · Guide · Reference
Documentation — start here
The current Version 2.1 programmer documentation is organized as three complementary books under the frozen v0.167 build. Start with Getting Started, use the Guide to learn the framework and application method, and use the Reference when you need the exact runtime contract.
2 · Learn and build
PVPP Programmer's Guide
The framework and application-design guide: modeling, canonical decision stages, execution, testing, AI-assisted development, and worked examples.
3 · Exact contract
PVPP Programmer's Reference
The exact technical reference for frozen v0.167: public API, stage contracts, host protocols, execution, re-entry, errors, limitations, and compatibility.
4 · Source
GitHub Repository
Browse the frozen runtime source, tests, examples, benchmarks, documentation directories, manifests, and preserved earlier runtime generations.
Recommended path: Getting Started → Guide as needed → Reference when exact runtime behavior or API contracts matter. Directory links are intentionally stable while final PDF and Word filenames are frozen.
One repository, four preserved frozen builds
The repository preserves the frozen runtime lineage rather than overwriting it. Runtime V1 v0.70 and Runtime V2 v0.131 remain historical baselines. Runtime V2.1 v0.141 is preserved as the prior Version 2.1 build. Runtime V2.1 build v0.167 is the current frozen baseline.
(P_i(t), O_i(t)) → Φ → H → G → ℛ → Graph / seed substrate → Π → completeness → Constraints → Domain Framing → Adequacy → Σ → ε
Framework meaning remains governed by the authoritative PV-PP Framework Version 2.1 source set. Runtime source and tests govern implemented runtime behavior. The runtime does not redefine the framework.
Choose a runtime
Runtime V1 — v0.70
Runtime Interface Freeze 1. The original frozen common runtime interface.
496 / 496
Original internal regression suite at freeze.
Use for historical reproduction, existing v0.70 integrations, or comparison with later builds.
Runtime V2 — v0.131
Frozen second-generation baseline. Preserved separately for provenance and comparison.
967 / 967
Complete v0.131 regression suite.
Use for reproduction or comparison with later Version 2.1 builds.
Runtime V2.1 — v0.141
Prior frozen Version 2.1 baseline. Preserved rather than overwritten by v0.167.
1093 / 1093
Frozen v0.141 regression suite.
Use for exact reproduction of the earlier V2.1 baseline or comparison with v0.167.
Runtime V2.1 — v0.167
Current Version 2.1 frozen baseline. New Version 2.1 applications should normally target this build.
1320 / 1320
Frozen full regression suite.
Build v0.167 extends Version 2.1 with host-driven in-flight supervision while preserving the synchronous canonical decision core and the framework/runtime/host boundary.
Host/runtime boundary
The runtime owns
- the implemented common PV-PP decision and governance architecture;
- registered and governed represented structure;
- implemented candidate/completeness, constraints, adequacy, and selection surfaces;
- execution licensing and ε authority boundaries;
- governed invalidation and re-entry; and
- the Version 2.1 validation, governance, and supervision interfaces actually present in v0.167.
The host/application owns
- authoritative actual state and domain/world mechanics;
- semantic completeness of domain-specific transition-relevant state;
- application-specific measurements and objective content;
- external persistence, instrumentation, and enforcement mechanisms;
- environmental realization; and
- the authoritative Layer-1 state transition.
Runtime selection, licensing, or a successful native call does not itself prove that the authoritative external world reached the intended successor state.
Runtime V2.1 execution and supervision boundary
Runtime V2.1 preserves authority-bound synchronous native call-through. Consequential invocation through the runtime must derive from the applicable runtime-issued governance lineage rather than from host-created authority-looking objects.
Build v0.167 adds host-driven in-flight supervision. Host instrumentation supplies observations and host code invokes supervisory checkpoints. The runtime evaluates admitted evidence and governs whether continuation remains authorized. The canonical decision core remains synchronous.
The runtime does not autonomously sense the world, schedule its own checkpoints, or by itself guarantee that an external process has stopped. External controllers remain responsible for carrying out stop, pause, rollback, or other enforcement actions and for reporting the resulting evidence back into the governed process.
PV-PP runtime governance also does not replace operating-system security, IAM, network enforcement, sandboxing, or other conventional controls required by the deployment environment.
Repository organization
PV-PP-Runtime-API/
├── runtime-v1/ # historical frozen Runtime V1, build v0.70
├── runtime-v2/ # historical frozen Runtime V2, build v0.131
├── runtime-v2.1/ # preserved prior Runtime V2.1, build v0.141
└── runtime-v2.1.167/ # current frozen Runtime V2.1, build v0.167
├── benchmarks/
├── docs/
│ ├── PVPP Getting Started/
│ ├── PVPP Programmer's Guide/
│ └── PVPP Programmer's Reference/
├── examples/
├── pvpp_runtime/
├── tests/
└── V0167_FILE_HASHES.sha256
The current runtime directory also contains lineage, conformance, hardening, release-note, and hash/provenance records used to identify and reproduce the frozen build.
About PV-PP
Productive Value–Productive Power (PV-PP) is a productive-system and decision framework centered on Productive Value, Productive Power, actual and perceived state, actor objectives, viability, recovery, governance, candidate construction, selection, consequential execution, and authoritative state transition.
This site concerns the Runtime API and its programmer documentation. It does not reproduce the complete theoretical, mathematical, proof, benchmark, or research record of the PV-PP framework.