TEREO
AI writes. TEREO proves.
TEREO is a proof layer for AI coding.
keep only if gain > noise
Each kept receipt becomes the next baseline.
It watches one small change, reruns one fixed check, and writes one readable receipt. The check should show one gain and catch the core breakage that would make that gain false. The check can prove a bug fix, a behavior change, or a speedup.
TEREO comes from Ancient Greek τηρέω (tēréō):
to watch over, guard, preserve.
Want the full story? Read the blog post: What Is TEREO?
One loop.
One kept receipt.
Demo
- Install TEREO.
pip install tereo
- Feel the loop.
tereo demo
If you prefer module execution, python3 -m tereo demo is the same runtime.
What it looks like:
Working on this repo itself? See the local setup in runtime/README.md.
The demo should close with something like this:
scorecard: latency: 10.000000 ms -> 8.000000 ms; 2.000000 ms better (20.00%)
verdict: keep
confidence: high
Quick Start
- Install TEREO.
pip install tereo
- Run TEREO locally.
tereo --help
If you prefer module execution, python3 -m tereo --help is the same runtime.
Use your own check. Keep your own workflow. Make it yours.
TEREO is small on purpose. Fork it. Keep it. Make it yours.
Public Commands
tereo demo
tereo prove
tereo show
tereo log
Everything else is there to support this surface, not to replace it.
Why This Is Hard
- one good-looking run can lie
- gains drift
- noise changes verdicts
- checks matter more than vibes
holdis different fromkeep
Narrow By Design
TEREO is strongest when one fixed check can judge one small change. That check should include both what should get better and what must stay true. If a patch hits the promise but breaks the core, that is a false gain, not a keep. That is a feature, not a full replacement for broader product judgment.
Read Next
- START.md Start here.
- runtime/README.md The runtime, advanced commands, receipts, and proofboard.
- skill/README.md The portable rulebook for humans and agents.
- WHY.md Why TEREO stays this small.
If the project is easy to explain, it is easy to trust.
Metadata
Release files for tereo 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tereo-0.1.3.tar.gz | 22.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tereo-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.5 kB
Release files / tereo-0.1.3.tar.gz
| Download URL | tereo-0.1.3.tar.gz |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44b3863f906833bd41c9c62437776b78a5a4e8b404353bf380a9b21c720e2319
|
|
BLAKE2b-256 checksum How to use checksums |
87eb0c925683edf48a48ca44dba6b41dac9e4bc391e361c881f7f0a18bede5ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 5, 2026.
Transparency logRelease files / tereo-0.1.3-py3-none-any.whl
| Download URL | tereo-0.1.3-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
699770b00f0f3dac6c5b153cf9deb2420918b2e68aab1891d942da605b767e1e
|
|
BLAKE2b-256 checksum How to use checksums |
b0cc773ea3e0547f48c6e77ebb6b45e640b5b9192f4fe38a803a860e84c5b7ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 5, 2026.
Transparency log