Neuruh

Problems · failure mode

Systems nobody can explain

Services, repositories, scripts, and agents accumulate. Nobody can say which ones are canonical, which are running, or which a decision actually depended on.

Why conventional tools fail

  • Inventories list what exists, not what is authoritative.
  • Documentation describes intent and drifts from what runs.
  • Counts made without published rules cannot be repeated or checked.

The evidence it takes

  1. 01

    What runs, observed rather than remembered

  2. 02

    Counting rules that someone else can repeat

  3. 03

    Contradictions kept, not smoothed over

What Neuruh does

Neuruh counts an estate under published rules and preserves contradictions, producing a truth, state, gap, and recovery report tied to evidence.

Proof · ATTESTED

Neuruh’s own operating estate, counted on one host under published rules.

18 services · Operating estate census · as of · not a live feed

Read it on the proof ledger →

Boundary

What this does not do

A point-in-time report, not live monitoring. Findings name evidence; they are not a certification or a security attestation.

Every boundary →

Start with one scoped piece of work

Forensic System Audit · Scoped in a 90-minute session. Bring a system you already run. Get an evidence-backed report of what is actually true about it, what state it is in, where the gaps are, and how to recover.