Skip to main content

Partners · Identity, collaboration, permissions

BUILT

Partners · Identity, collaboration, permissions

Fides. What may cross a boundary, and nothing more.

Two companies argue about one number and neither will open its books, so the question is never the number. It is what may cross. Fides is the disclosure layer: a relationship, a category, a rung on the ladder, a grant made by a named person, and a refusal by name when the answer is no.

It shares. It never acts. A fact that arrives through Fides does not become truth in your record: it becomes a source, with its origin visible, so the moment it disagrees with your own record the ordinary discrepancy machinery fires and your own Honos routes it to a person.

See Fides on the platformRequest an assessment

The ladder

Never share the number when less answers the question.

A category is granted at a rung, never as a boolean. Degrading happens on the sending side, before anything leaves. Most of the value in a supply chain sits between rungs one and three, which is also where the legal exposure disappears.

RungWhat crossesInventory on hand, as an example
0Nothingrefused
1A thresholdabove your agreed minimum: yes
2A directionfalling for three weeks
3A bandbetween four and six weeks of cover
4A derived figurecoverage 5.2 weeks, DERIVED, rule named
5The observed value184,200 units, OBSERVED, SAP, September 12, 2026

What it refuses, by name

Six rules, each one a test.

ClauseWhat it means
relationship.unclassifiedEvery relationship is classified internal, vertical or horizontal before a grant can exist. Two operating units of one company, a distribution center to a distribution center or a store to a store, are internal and are not screened for sensitivity.
horizontal.sensitivePrice, discount, cost, capacity, forecast or wages, across a horizontal relationship, is refused. An exception needs counsel, a purpose, an expiry, an aggregation floor of five, and it may not exceed the band rung.
grant.personOnly a named person grants, delegates or revokes. An agent principal never may.
delegation.upgradeA delegation to a further tier re-degrades and never upgrades.
delegation.depthDelegation stops at the granted depth, which is zero by default.
opportunity.nofinancialsAn opportunity carries no money. Each side computes its own value on its own data.

Most grants take effect when you make them, because offering your own information is your own decision. Three need the other side to accept first: a horizontal exception, a grant carrying delegation, and the observed rung. A refusal is written to the organization's chain with the clause that refused it, so the compliance file assembles itself rather than being reconstructed later.

Mutual benefit without disclosure

Both sides gain, and neither sees the other's number.

StepWhat happens
1A change is proposed as a statement with no money in it, plus the horizon and how value will be measured afterward.
2Each side computes its own projected value locally, on its own data. Neither number leaves.
3Each side publishes one hash of its decision and a private salt. The decision itself stays local.
4Only when both commitments exist does either side reveal, and each chain verifies the reveal against the commitment.
5Both accepted: the statement is disclosed to both for confirmation, and any action goes through each side's own Honos.
6Either declined: no match, and no value, threshold or reasoning is revealed.

Stated plainly because it is the only leakage: with exactly two parties, a decline is visible as the absence of a match. Both chains record the commitments, the reveals and the verification, so an auditor can prove afterward that no financial information crossed.

Where it sits

Four names, one record.

ProductWhat it does
NerioReads. Serves your AI the state of your systems as evidence, and changes nothing.
MinervaActs. Executes only what a person authorized, reversibly, on the chain.
HonosDecides who may authorize what, and keeps the decision with its evidence.
FidesSays what may cross a boundary, at which rung, under whose grant.

Multi-tier is delegated grants with a depth limit and a re-degrade at every hop, never a shared pool. A delegation travels along the delegating organization's own classified relationship with the next tier, and passes the same competition-law screen as a first-hand grant, so a supplier cannot forward a sensitive fact to its own competitor. Tested three tiers deep. A pool would be both the antitrust artifact a regulator asks about first and the most attractive target on the network.

NerioMinervaHonos

Film · under two minutes

What may cross a boundary.

The ladder, the refusals by name, the commit and reveal protocol, and why a counterparty is another source rather than a new truth.

Forculus: the door between the record and the machine →

The EOS family

NerioAssessAwareness, insight and resilienceMinervaActionExecute, reverse, recordHonosGovernCompliance, audit, policyFidesPartnersIdentity, collaboration, permissionsForculusIntegrateAPIs, gateways, interoperability, digital and physical, roboticsPortunusTraceIdentity, custody, carbon, end of life

Also from AssetShop

Fourteen other products, none of them part of EOS. Separate products, no shared runtime, tenancy or credential path. Nothing below is included in an EOS evaluation or an EOS contract. Each carries its status, and nothing is called built until it is.

Enter the consumer layer at assetshop.eth EOS is the Enterprise Operating System. The brand layer it belongs to is name-native. Past that line the rules are different, and it is built by Shadow Key.

✓
Privacy notice · no tracking
This site uses no third-party tracking, no advertising cookies, no analytics beacons.
A single first-party cookie remembers your preference for dismissing this notice. We follow GDPR + CCPA + state-equivalent privacy laws by default. Full detail in our Privacy Policy and Cookies Policy.