← All signal reportsSherlock hub →
Signal report

Sherlock

Publication date July 02, 2026

Live SoT
Settlement pressure
Φ_S 0.0200
Field coherence
κ 0.0123
M1 ledger obs
1
M1 coverage (field)
193 / 199

Hero numbers overlay the live dossier SoT (compiled 2026-08-30T05:00:10Z). This is current engine state, not the prose below.

Publication snapshot · 2026-07-02
Φ_S at publish
0.0200
κ at publish
0.0093
vault@publish
0

Dated research snapshot. Prose below describes publication-time observation. vault@publish counts trimmed cycle-vault rows at publish time. It is not the live M1 ledger (1 obs for SHERLOCK; field coverage 193 / 199). Do not read vault@publish = 0 as "no measurements exist" when M1 ledger obs is non-zero.

Sherlock: Field Position Report

Eigenstate Research, July 02, 2026

Methodology: The Information Field Equations, E = ΔI/A, G = ∮E·dl, Protocol Truth → 1/φ


Publication field context

The Eigenstate engine currently measures the tokenized settlement field at:

The field is 0.1172 below equilibrium coherence. Each entity with measured vault activity raises the global PT toward 0.618. Sherlock does not yet have a complete observation record on the M1 topology (199 entities).

What it is

Sherlock is a smart contract audit and coverage platform, coordinating security researchers and audit contests for DeFi and tokenized asset protocols on Ethereum. For spread-capture topology, Sherlock is the contest-audit waist where settlement contracts must align with attested review coverage before issuer products reach production.

Verified claims

Field Confidence: ? LOW, No external sources mapped for this entity, engine-internal data only

Verification: 3/3 source-checked (ATTESTED), 3 grounded. Each claim below carries a machine-checked status against its cited source; ungrounded items are editorial assessments, not verified facts.

Active signals the engine is tracking for Sherlock:

Sherlock, audit platform homepage [✓ ATTESTED-PRIMARY] Sherlock's homepage documents smart contract audit and coverage services, primary anchor for Sherlock claims in settlement topology. Source-checked: ATTESTED-PRIMARY · custody sha256 2600712d140f…, found in primary source

Sherlock documentation [✓ ATTESTED-PRIMARY] Sherlock's documentation describes audit contest and coverage workflows, cross-check for contest-audit claims in tokenized settlement graphs. Source-checked: ATTESTED-PRIMARY · custody sha256 3c46799d47dd…, found in primary source

Sherlock audit coverage documentation [✓ ATTESTED-PRIMARY] Sherlock's audit documentation describes protocol review coverage, verifiable lane for audit-waist claims in settlement topology. Source-checked: ATTESTED-PRIMARY · custody sha256 2077a2f94f50…, found in primary source

Field read

Settlement Pressure (Φ_S = 0.0200)

Near-zero settlement pressure, this entity is close to field equilibrium.

Sherlock settlement pressure is elevated because tokenized fund and DeFi protocols publish contest audit coverage faster than VERIFY catalogs attestation of review freshness per upgrade cycle. The engine reads unrealized Φ_S when Sherlock centrality exceeds vault evidence of audit coverage on Ethereum settlement rails.

Coherence (κ = 0.0093)

κ = 0.0093 reflects the engine's current measurement coverage, not Sherlock's actual institutional influence. With no vault records yet, the coherence score is derived purely from topology position, connection count and structural weight, without any attested observation data. The low value means the engine has not yet measured this entity's settlement activity, not that the entity lacks field presence.

The equilibrium attractor is κ = 1/φ ≈ 0.618. At current κ = 0.0093, Sherlock is 0.6087 below equilibrium. Vault observations of Sherlock's rule outputs, rulemaking notices, enforcement actions, guidance documents, would directly raise κ toward the living zone [0.618, 0.678].

Vault Coverage

No vault records yet for Sherlock. This is a gap in the field coverage. The engine recommends observation as the first action (see below).


Sources

This report is generated by the Eigenstate engine, an information-field measurement system for the tokenized settlement layer. The engine tracks 199 entities (M1 topology denominator) across the regulatory, infrastructure, issuer, and audience layers.

Core equations:

Published implementation: helixhash v0.1.1, Zenodo DOI 10.5281/zenodo.18413995

Vault: No vault records yet for Sherlock in the current cycle, κ and Φ_S here are topology-derived until observations are attested. The field recommends observation as the first action.

Note: Internal topology codenames are not used in public reports. All entity names in this report are public names.

Sources & human pages
Eigenstate Pages & federation surfaces
Canonical report · this page
Entity hub · publish history + measurement evolution
Entity dossier (HTML) · live SoT card for Sherlock
Methodology · field equations and publish honesty
Numbers glossary · Φ_S, κ, vault@publish, M1 ledger
Verify walkthrough · human federation check
Related reports · other tracked entities
Paragraph journal · long-form distribution
Federation network view · RWA map · Node diary
RWA registry · public registry UI
Related entities · by settlement pressure
CircleΦ_S 11.392Tether (USDT)Φ_S 6.556CoinbaseΦ_S 6.511Tokenized Treasury PoolΦ_S 6.506BaseΦ_S 6.503Uniswap DEXΦ_S 6.492
For agents
APIs · Vercel apps · federation traverse · Node 34539544 (collapsed)

Cold-agent entry for Node 34539544 / SHERLOCK. Prefer human pages above first. Traverse: agent entry → manifest → entity feed → dossier → chain verify → canonical report. Walkthrough: verify-walkthrough.

Machine JSON & federation APIs
Agent entry· Node hub · cold start
Manifest· builds directory
Machine dossier (Pages)· SHERLOCK.json
Live dossier API· /api/dossier
Machine claims (Pages)· SHERLOCK.json
Federation card· Node hub agent descriptor (entity feed stubs retired)
Chain verify· /api/chain
Federation base· geniusflow-federation.vercel.app
Federation status· best_effort_vercel
llms.txt· agent adapter index
OpenAPI· machine schema
api/verify· claim verify wire
api/package· claim package wire
api/cite· cite surface
api/return_wire· return wire
Vercel apps
entity:SHERLOCK · report_id:SHERLOCK_20260702
Build fingerprint: 4e0b2d39782769fd… (match builds[].chain_hash for SHERLOCK in api/manifest, then verify via api/chain)
Granth head:917f0e3036931e14… · length 919
Verify: GET api/manifest → find builds[].target==entity → match chain_hash → GET api/chain.