02.1 / Lab notebook
← Lab indexUniversal Reduction Plane
How much work can a system skip while preserving the result you need?
Storing, moving and computing the same thing twice costs money. I built URP to test when a system can skip that work. First you specify what the result has to preserve. Then URP checks the reduced result and returns the baseline if the check fails.
Scope and limits
By default, URP accepts exact reductions. Changes in meaning, loss of data or deletion require policy approval. The Docker, Helm and Terraform artifacts pass CI checks. Deployment and production savings remain untested.
Read the paperURP / Workflow
When can URP use a reduced result?
- Plan
Read the work unit’s preservation contract and policy to choose an eligible reduction.
- Execute
Produce a candidate result, for example with exact caching.
- Verify
Check whether the candidate meets the preservation contract.
Worked explanationFollow an exact-cache candidate
- Input
- A work unit defines what must be preserved, and policy allows exact caching.
- Decision / rule
- Treat the cached result as a candidate. Verify it against the preservation contract before accepting it.
- Outcome
- Pass returns the candidate; failure returns the baseline. Either outcome enters the manifest and ledger.
Scope of this exampleA conceptual example of the local proof. Selecting an outcome in this diagram does not perform a cache lookup or verification.
Try it locally.
Run these commands from a checkout of the project. The repository includes setup details and prerequisites.
python3 -m venv .venv
.venv/bin/python -m pip install -e ".[dev]"
.venv/bin/urp --state-dir .urp-demo execute --kind byte_object --input "hello hello hello"