neos-triage
Triage structured event streams by exact law. No model in the decision.
pip install neos-triage
neos /var/log/syslog
An LLM triaging events spends most of its tokens deciding whether an event matters. That decision here is a handful of bit operations over a byte — so it costs nothing, and a model only writes words for the ~1% that survive.
75.9% fewer tokens than a lean batched classifier, measured on 215,089 real events with both sides using the same safe dedup. → USAGE.md
Read this before you deploy it
Measured against ground truth the tool cannot see — filesystem-check exit codes recorded in a separate file — it caught 42 of 59 real incidents: 71.2% recall, 95% CI [58.6%, 81.2%].
As originally shipped it caught 0 of 59. A dedup credited with 97% of the token saving was hiding a failure that recurs 1,113 times. Fixing it cost 13 points of the saving, because the 89% published earlier was the same result with the incidents removed.
False-page rate is still unmeasured. Run it beside your existing alerting,
not instead of it. neos label / neos score produce the evidence for your
own stream. → FAIR.md, DEPLOY.md
How it works
event ──[adapter]──► PACKET ──► ROUTE ─ hands settle ─► REDIAL ──► DECLINE
a regex every step below is bit operations
route(), redial() and decline() are verified against compiled C kernels
over all 256 inputs. Nothing is trained, tuned or fitted. The laws never
see words — an adapter converts at the boundary and decides nothing, which is
why text arriving in an event cannot reach the control path.
Adapters auto-detect: syslog (ISO and BSD), .NET/Unity, tagged, NDJSON.
Below a 50% parse rate it refuses rather than reporting a confident 0%.
What it will not do
It reports. It cannot send, write, execute or act — no subprocess, no
exec, no network, zero dependencies, all enforced by tests rather than
claimed.
Tests
python3 tests/test_triage.py # 22
python3 fairtest.py # incident recall vs an independent oracle
Two properties are proved, not sampled: the hand set is total over all 64 packet shapes — no event is ruled and then dropped — and the decision path imports nothing.
Licence
Apache-2.0. The sibling project that carries fluidfix's AGPL kernel is not distributed here.
Metadata
Release files for neos-triage 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| neos_triage-0.2.0.tar.gz | 44.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| neos_triage-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.6 kB
Release files / neos_triage-0.2.0.tar.gz
| Download URL | neos_triage-0.2.0.tar.gz |
|---|---|
| Size | 44.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bce41d86d194415f0aacfe9c1c6b86863904e982b67743c56b0c24e90189838
|
|
BLAKE2b-256 checksum How to use checksums |
282c0214af8cd947780fa01309c74aba95f444a04765d14ac81145158101e826
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 13, 2026.
Transparency logRelease files / neos_triage-0.2.0-py3-none-any.whl
| Download URL | neos_triage-0.2.0-py3-none-any.whl |
|---|---|
| Size | 44.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4fd8db964b949f32e77cb6f59205c5bc1a6b9631a7da71994ec93875519ddc2b
|
|
BLAKE2b-256 checksum How to use checksums |
90ddd886d3a4bb2fbd8350b58091954e38dba5ac1f8e76b984c1bffce17f85b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 13, 2026.
Transparency logSecurity for neos-triage 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for neos_triage-0.2.0.tar.gz
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 Sep 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.