AssetShop Nerio
Assess · Awareness, insight and resilience
The read side. Sees everything permitted. Changes nothing.
LIVEThe context service runs on the platform with fourteen tests of its own.
Nerio serves your SI the state of your systems as evidence: every figure labeled with how it is known, every disagreement between sources kept rather than averaged away, and no tool of its own that can act. An agent that reasons over Nerio can be trusted with a decision because Nerio gives it no action of its own; carrying out an approved request is Minerva's, and only an owner can grant it.
What an agent can do here, and what it cannot
A principal is an agent identity your owner or admin creates. Its authority is drawn from read, reasoning, draft and propose, and from execute only where an owner grants it, within a per-action and a daily limit.
| Tool | Authority | What it returns |
|---|---|---|
get_state | read | The current value of an entity's field from every source that holds it, each labeled OBSERVED with its source and time. |
list_discrepancies | read | Where your systems disagree: the sides, the gap, since when, and whether a person has been asked. |
get_evidence | read | The record behind a figure: the observation, its source, its hash on the chain. |
get_timeline | read | How a value moved, observation by observation. |
explain | reasoning | A derivation with its rule named, labeled DERIVED. Never a number without the rule that produced it. |
simulate | reasoning | A what-if, labeled SCENARIO so it can never be mistaken for the record. |
propose_action | propose | A request into Honos, routed by policy to a named person, who decides it. |
execute_action | execute, only where an owner grants it | Minerva's tool, served here, and only once your organization has a signed contract, a verified pilot and your recorded approval: carries out a request a person already approved, within the owner's per-action and daily limits, by sending your own executor a signed, single-use authorization; EOS then verifies the result. Nerio has no tool of its own that can write, act or decide. |
Nerio
Reads every system. Writes to none.
Nerio is the reading side of EOS: observations with their source and time, disagreements kept with their evidence, a graph of what depends on what.
The problem
Three systems hold three versions of the same figure, and the monthly close picks one by hand.
Why it matters
The version that wins by habit is not the version that is right. Keeping the disagreement is what makes the decision auditable.
What you get
Every figure with its system of record and time; disagreements kept with their evidence; a wrong value corrected without losing its history; reads limited to your organization.
- 1ObserveEach source, each value, stamped
- 2CompareDisagreements surfaced, not hidden
- 3ExplainEvidence and derivation shown
- 4Hand offA proposal; a person decides elsewhere
Every figure carries its label
Seven labels, enforced on the way out. OBSERVED: read from a source, with the source and the time. DERIVED: computed by a rule the response names. INFERRED: reasoned, and marked as such. SCENARIO: modeled, never the record. DECISION: the state an approved decision intends. ACTION: what was carried out. OUTCOME: what verification found. A response with an unlabeled number cannot leave the service; the builder refuses it. A report carries only the first two.
Disagreement is kept, not averaged
When two systems hold different values for the same field, Nerio records both sides, the gap, and the moment it opened. It does not pick a winner. A person does, through a request the record keeps, and the resolution is a decision with a name on it.
Tenancy and the chain
A principal belongs to one organization, and every read is bound to it; a read across organizations returns 403. Every call is appended to the organization's chain: the principal, the tool, the labels on what went out, and the cost. An auditor can reconstruct what an agent knew at the moment it proposed what it proposed.
How Nerio and Minerva connect
Nerio reads and never writes. EOS holds no write credential to your systems of record. A change is made only by your own executor, for a request a named person approved, under a signed, single-use authorization from Minerva, and EOS then verifies the result. Nothing is sent to your executor until your organization has a signed contract, a verified pilot and your recorded approval. Nerio evidences, a person authorizes through Honos, and Minerva reads the authorization from the record; Nerio never calls Minerva, and Minerva never writes into Nerio's observations, disagreements or decisions. The join is a request id.
See Nerio on the platform Start an evaluation Read about Minerva
Film · two minutes
Nerio sees.
The Nerio film, two minutes: the read side that sees everything permitted and changes nothing, the labels enforced on the way out, the tools an agent can call, disagreement kept rather than averaged, every call on the organization's chain, and how Nerio, Honos and Minerva connect. Every line was from this page when the film was made; the page now states seven labels, and that an owner can grant an agent execute, within limits, to carry out a request a person approved. Where the film and the page differ, the page is current.
The EOS film, the whole loop from a discrepancy to a reversible action, is on the platform page.
Honos: who may authorize what →
Fides: what may cross a boundary →
The EOS family
Request the two-week EOS assessment: $15,000, read-only, first finding targeted in 14 daysRead-only throughout. If you continue to the $50,000 pilot, the $15,000 assessment fee is credited.
Start with your own data.
Two weeks, fixed price. Read-only, no migration. The first finding comes from your systems, not a demo. Continue only if it is worth it.