This repository now has a direct operational tool:
python -m omnia_limit_detector.cli --input examples/sample_trajectory.jsonl --out-dir report
It solves a concrete problem:
given a sequence of measurement steps,
detect when additional processing stops producing useful structural gain,
compute stop/continue signals,
produce JSON/CSV/HTML reports,
and optionally fail CI when the trajectory crosses the limit boundary.
In short:
trajectory -> marginal gain analysis -> STOP / CONTINUE / WATCH certificate
Many pipelines continue running after useful structure has already saturated.
OMNIA-LIMIT turns this into a reproducible measurement problem.
It answers:
Is the trajectory still gaining structure?
Is marginal improvement collapsing?
Has SEI crossed the exhaustion boundary?
Is residual instability still present?
Should the process continue, watch, or stop?
Which step first crossed the limit boundary?
The rest of this repository explains the OMNIA-LIMIT idea.
The detector is the practical entrypoint.
Clone the repository:
git clone https://github.com/Tuttotorna/omnia-limit.git
cd omnia-limit
Install locally:
pip install -e .
The detector only uses the Python standard library.
Run the sample trajectory:
python -m omnia_limit_detector.cli --input examples/sample_trajectory.jsonl --out-dir report
Run and fail if STOP is detected:
python -m omnia_limit_detector.cli --input examples/sample_trajectory.jsonl --out-dir report --fail-on-stop
Run with custom thresholds:
python -m omnia_limit_detector.cli --input examples/sample_trajectory.jsonl --out-dir report --sei-threshold 0.05 --omega-stability-threshold 0.02 --iri-threshold 0.01
The detector accepts JSONL.
Required field:
step
At least one structural signal should be present:
omega
residual
iri
gain
Optional fields:
note
source
cost
Example:
{"step":1,"omega":0.41,"residual":0.31,"iri":0.10,"cost":1}
{"step":2,"omega":0.55,"residual":0.22,"iri":0.08,"cost":1}
{"step":3,"omega":0.60,"residual":0.18,"iri":0.05,"cost":1}
The detector writes:
report.json
report.csv
report.html
stop_events.jsonl
certificate.json
Meaning:
report.json
Full structured limit analysis.
report.csv
Spreadsheet-friendly step summary.
report.html
Human-readable limit report.
stop_events.jsonl
One JSON object per detected STOP boundary.
certificate.json
Reproducibility certificate with thresholds, first stop step, and final decision.
The detector can fail automatically when STOP is detected:
python -m omnia_limit_detector.cli --input examples/sample_trajectory.jsonl --out-dir report --fail-on-stop
Exit codes:
0 = analysis completed, no blocking STOP condition
2 = STOP boundary detected
3 = invalid input or measurement error
This is not a decision engine.
It does not decide truth.
It does not infer meaning.
It does not claim that a process must stop in the real world.
It provides one concrete, reproducible operation:
read a structural trajectory
measure marginal gain and exhaustion
detect limit boundary candidates
produce reports
optionally fail CI
The rest of the repository documents the OMNIA-LIMIT concept:
stop condition
structural saturation
SEI
residual gain
irreversibility
continue/watch/stop boundary
The code above is the entrypoint.
The repository below is the derivation path.
Repository: Tuttotorna/omnia-limit Release tag: v2026.05.21 Release commit: 4998b6c Release DOI: 10.5281/zenodo.20322684
Boundary:
measurement != validation validation != orchestration orchestration != decision decision != measurement
Zenodo DOI badge for this repository.
Repository: Tuttotorna/omnia-limit GitHub repository id: 1128461964 Release tag: v2026.05.21 Latest release DOI: 10.5281/zenodo.20322684
Release DOI: 10.5281/zenodo.18362097
GitHub release: omnia-limit v1.0.0 release
From a clean environment:
git clone [omnia-limit.git](https://github.com/Tuttotorna/omnia-limit.git)
cd omnia-limit
python -m pip install -e .
pytest
If example scripts are available, run the smallest demonstration after tests pass.
The goal is to see the limit path:
measurement sequence
-> marginal structural gain
-> saturation / irreversibility
-> stop-or-continue boundary
-> external decision
omnia-limit observes a sequence of structural measurements and asks whether continuing still adds useful structural discrimination.
It can support stop / continue signals when a measurement process appears saturated, exhausted, irreversible, unstable, or no longer structurally productive under declared conditions.
Public compression:
OMNIA measures.
omnia-limit asks whether more measurement still helps.
omnia-limit does not:
- infer semantic truth;
- decide correctness;
- replace external judgment;
- prove final truth;
- prove physical truth;
- perform security scanning;
- perform cryptographic attacks;
- convert stop / continue signals into final decisions.
The final decision remains external.
More measurement is not always more knowledge.
At some point, additional transformation may stop adding structure.
omnia-limit makes that boundary explicit.
Every serious omnia-limit result should make clear:
| Component | Meaning |
|---|---|
| sequence | The measurement sequence being observed |
| marginal gain | What additional structure is gained by continuing |
| saturation | Whether the sequence is approaching exhaustion |
| irreversibility | Whether structural loss becomes non-recoverable |
| boundary signal | stop, continue, flag, or inconclusive |
| limitation | What the signal does not prove |
| external decision | Who or what acts after the boundary signal |
Recommended result vocabulary:
continue
stop
flag
inconclusive
Meaning:
- continue: more measurement may still add useful structural discrimination;
- stop: further measurement is unlikely to add useful structural discrimination under the declared protocol;
- flag: instability, irreversibility, or saturation requires inspection;
- inconclusive: the sequence is insufficient or ambiguous.
- docs/QUICKSTART_LIMIT.md
- docs/LIMIT_OVERVIEW.md
- docs/STOP_CONTINUE_CONTRACT.md
- docs/SATURATION_AND_IRREVERSIBILITY.md
- docs/BOUNDARY.md
- docs/LIMIT_MANIFEST.json
For the full ecosystem map, start here:
For public validation artifacts, start here:
For core structural measurement, start here:
| Repository | Role |
|---|---|
| lon-mirror | Canonical public entry point |
| OMNIA-VALIDATION | Public validation showroom |
| OMNIA | Core structural measurement engine |
| OMNIABASE | Representation invariance foundation |
| omnia-limit | Stop / continue boundary layer |
| OMNIA-RADAR | Structural signal detection layer |
| OMNIA-INVARIANCE | Structural invariance layer |
| OMNIA-CONSTANT | Structural constant candidate layer |
| OMNIAMIND | Structural cognition orchestration layer |
| OMNIA-THREE-BODY | Dynamic divergence stress test |
| OMNIA-SECURITY | Bounded structural security diagnostics |
| OMNIA-CRYPTO | Bounded structural crypto diagnostics |
measurement != inference != decision
Decision remains external
MIT.
measurement != inference != decision
This repository is part of the MB-X.01 / OMNIA ecosystem. Its outputs must be read as structural measurement, validation, detection, orchestration or adapter artifacts according to the repository role. They are not autonomous semantic truth claims and they do not make external decisions.
This repository is one bounded measurement role inside Structural Observability.
Role:
saturation and structural stop-boundary detector
Boundary:
STOP is a measured structural boundary. It is not a semantic decision.
Structural Observability foundation:
- lon-mirror: https://github.com/Tuttotorna/lon-mirror
- Foundation release: https://github.com/Tuttotorna/lon-mirror/releases/tag/v0.2.2
- DOI: https://doi.org/10.5281/zenodo.20379374
Role document: