Record a Claim with Evidence
Add identifiers, systems, and supply ties to the entity ledger, each citing a public observation with an honest verification state
Use this when a public page tells you something about a company, person, or system: a domain it uses, its SEC CIK, the host that serves its portal, or a supplier it depends on.
You need an owner, admin, or member role in the workspace. In the API, use a workspace-bound key with
ledger:write.
Record an identifier in the app
-
Open the company from FININT → Markets → Companies. If Entity ledger has no subject, choose Open ledger subject.
-
In Record an identifier with its source, choose the kind and enter the value as the page shows it. Y2 stores the canonical form: lowercase email and hosts,
ASplus the number for an ASN, a CIK padded to ten digits, and an uppercase ticker. -
Set the namespace when the kind needs one:
Kind Namespace handleThe platform or host, such as github.comexternal-idsec-cik,lei,wikidata, orattack-grouptickerThe exchange's ISO 10383 MIC, such as XNASpublic-keyThe algorithm, such as ssh-ed25519 -
Enter the public source URL, the method, and a short excerpt (the quote that shows the identifier). The excerpt is capped at 500 characters; the ledger keeps a quote and its SHA-256, never a page body.
-
Choose the verification state the evidence supports, and a confidence from 0 to 100.
-
Choose Record claim.
Record a supply or ownership tie in the app
In Record a supply or ownership tie, search the shared catalog for the other company, pick its role (supplier, customer, parent, or subsidiary), cite the page that states the tie, and choose Record tie. Y2 opens a ledger subject for the other company if your workspace has none and anchors it to the catalog entity.
Record through the API
Append the observation first, then the designator, then the claim that cites the observation:
curl https://api.y2.dev/api/v2/ledger/records \
--header "Authorization: Bearer $Y2_API_KEY" \
--header "Idempotency-Key: dns-portal-2026-06-01" \
--json '{"kind":"observation","observation":{"method":"public-dns","sourceGrade":"primary","sourceUrl":"https://dns.example/lookup?name=portal.northwind.example","retrievedAt":"2026-06-01T11:50:00Z","excerpt":"portal.northwind.example A 192.0.2.10 (AS64500)","collector":"dns-sync"}}'A designator with the same kind, namespace, and normalized value is reused: the response is 200
with created: false and the existing dsg_… ID. A claim that repeats a claim key must supersede the
current head (see Correct, supersede, or retract a claim).
Choose the verification state
Pick the lowest state that is true. The ledger rejects states the cited evidence cannot support.
| If the evidence is | Use |
|---|---|
| One public page that ties the identifier to the subject | located |
| The subject's own page stating it | self-asserted |
| Two retrieved pages at different URLs that each identify it | cross-linked |
| A further independent source that agrees | corroborated |
| Only an analyst note connecting other observations | analytic |
| A page where the string appears without a tie | mentioned |
cross-linked and corroborated need at least two retrievals of different pages among the cited
observations. analytic means every cited observation is an analyst note.
Control is a separate, weaker claim
A public profile shows that a handle exists and what it displays. It does not show who can sign in
to it. Record designated-by for the handle, and record controls only when a public source speaks
to control, usually at low confidence.
Related
- Vocabulary for every kind, method, and predicate.
- Ledger record format for the rules and their error codes.