The evidence contract, programmatically.
The public API is not enabled in this local candidate. No API key, service-level commitment or production integration is offered here.
What an integration must preserve
- Identity & state
- Network, target, analysis run, observation time, block or native state and finality.
- Evidence
- Field, value, provenance, source, fingerprint, limitations and explicit supporting links.
- Assessment
- Risk, Confidence and assessment state are separate fields. A gated assessment must remain gated in downstream interfaces.
- Fresh Deep run
- A paid report requires a new analysis snapshot and a qualified entitlement. A cached Free Scan is insufficient.
Production authentication, quotas and external integration documentation remain unavailable until the service is enabled.
A sell test is a state-bound observation.
How to read a successful transaction without turning one local result into a guarantee.
↗Control is a path, not a label.
Why an owner address is the beginning of a control investigation.
↗Liquidity is more than a number.
Separate pool state, executable depth, custody and withdrawal conditions.
↗Sampled exposure is not global concentration.
Read selected balances with the right denominator and exclusions.
↗Source count is not independence.
Two tools can share one upstream state provider.
↗Verification stops at its boundary.
Runtime code, implementation references and active delegation are distinct claims.
↗Read the record, not just the conclusion.
Search the evidence ledger, select an object, then follow its stored links in Signal Lattice. Calls, token accounting and state changes remain separate views.
Open the archived evidence ledger →