Skip to main content

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, now measured: 76.0% of successful installs got a page on the laws alone — Apple boilerplate containing the word "error". An oracle- seeded boundary (neos seed) takes that to 11.3% on unseen installs with no real failure hidden, and the token saving from 76% to 97.6%. Run it beside your existing alerting, not instead of it. → FAIR.md, FAIR2.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.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for neos-triage 0.3.0
File Size Uploaded Provenance
neos_triage-0.3.0.tar.gz 61.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for neos-triage 0.3.0
File Interpreter ABI Platform
neos_triage-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 120.6 kB

Release files / neos_triage-0.3.0.tar.gz

Download URL neos_triage-0.3.0.tar.gz
Size 61.1 kB
Tags Source
SHA-256 checksum
How to use checksums
538b36ee58d594334c3f777c04f680a9b27cd2d0faeb9acce8ddb21838dbb637
BLAKE2b-256 checksum
How to use checksums
9cd617c62865f9f51b5d66c27c8f47d1f23e0283c16435460d384bf1a3f989be
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 14, 2026.

Transparency log

Release files / neos_triage-0.3.0-py3-none-any.whl

Download URL neos_triage-0.3.0-py3-none-any.whl
Size 59.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7994ff15d97e74b3c93c58aba3428c6274499402b8424e1ddb150e2bdc732d3a
BLAKE2b-256 checksum
How to use checksums
da058965f7c35c628dd5373d200ec19f25b1f033636dabb074773bf5016ecd06
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 14, 2026.

Transparency log

Security for neos-triage 0.3.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.

Select from 2 files

Attestation for neos_triage-0.3.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 14, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page