The graph. Every layer of the record.
The whole record,on one map.
Every person, organization, fund, work, model, topic, event and post in the Verum record, and every projected relation between them, drawn from five sources into one graph. A row the projection cannot draw (an end missing from the record, a retired or non-public row) is left out and counted, with its reason, in the coverage panel and the public JSON. Each relation shows its source and date where the record has them, and says plainly when it has none.
The interactive map needs JavaScript. With it on, you can search the graph, filter it by kind, family and layer, replay the record over time, and open any node to read each of its relations, with its source and date where the record has them.
Three kinds of evidence, never mixed.
Every line on the map belongs to one layer, and the layer decides how it is drawn. Nothing is inferred from who sits near whom: a position on the map is a layout, not a relationship.
- Facts
- The public ledger and the steward twin, admitted through the gate. Each carries its source URL and the date its source gives where the record has them, said for what it is: when a source listed or observed it, when it was recorded, or when it began or ended. Drawn as solid lines; a relation the source implies rather than states is marked inferred and drawn dashed.
- Observations
- The Cosign capture and X. A Cosign line is what a public profile showed when it was captured, dated by the capture, not by the relationship; an X row is dated by the time of its post. Never read as an established fact. Drawn as dashed lines.
- Derived
- Semantic co-mention and similarity. Derived links come from co-occurrence in sources; they are not facts. Drawn dotted and faint, and off until you turn them on.
Relations come in families.
Relation words come from Verum's ontology (role at, funded by, cosigned by, lists it as company), chosen to say no more than the source shows, and each relation belongs to one family. A role a source lists is not verified employment. A Cosign profile listing is an affiliation, not employment. An investing announcement is not a personal check.
- AffiliationRoles sources list in the ledger, seats and memberships from the twin, and the companies a Cosign profile lists.
- CapitalFunding rounds and round leads, and investing announcements seen on Cosign.
- StructureSubsidiaries, venture arms, one organization under two names, and listings.
- GovernanceBoards and the people who govern an organization.
- ProductionWho produced, contributed to, documented or co-authored a work or a model.
- EndorsementCosigns, invitations, nominations and acknowledgements.
- DiscourseWhat was said and about whom: interviews, posts, quotes and replies on X.
- MarketRankings, markets served and compute supplied.
- CollaborationPartnerships, collaborations, contracts and awards.
- MentionA name in someone's career text or a link on their profile.
- DerivedCo-mention and similarity, computed from sources.
- EventThe people and organizations an event in the ledger is about.
Five sources, one projection.
People, organizations, funds, works, models, topics, ideas, events and posts. A node seen in two sources is one node only when a strong identifier proves it: a shared id, a Cosign alias, a ledger id, a proven X handle or an exact official domain. A matching name alone never merges anything.
The projection is public JSON at /graph/api/v1/graph.json, and agents can ask the same record over MCP: connect your agent.
- Person
- Organization
- Fund
- Work
- Model
- Topic
- Idea
- Event
- Post
- Public ledger
- 6,250
- Steward twin
- 6,531
- Cosign capture
- 16,854
- Semantic terms
- 452
- X posts
- 1,257
Rows in each source as measured on Oct 11, 2026. The map reads them live.