At this level
com.t0ronto.commons · 3- com.t0ronto.commons.attestation record A single attestation in the t0ronto data commons: one quad asserting that `subject` stands in relation `predicate` to an object. Subject is an at-uri (a project entity, or another attestation in the retracts case). Predicate is an at-uri to a project predicate entity (see scripts/predicate_seed.json). Object is exactly one of `objectRef` (an at-uri reference to another entity — an edge in the graph), `objectLit` (a scalar literal — a property value; external IRIs live here as xsd:anyURI), or `ob
- com.t0ronto.commons.defs defs A social-platform presence, used as a com.t0ronto.commons.statement objectStruct (predicate `social`). The platform list is open — clients should fall back gracefully on unknown values. Per-platform value semantics differ: `bluesky` carries a DID (did:plc:* or did:web:*) so resolution flows through the AT Proto directory; `email` carries an email address; `website` carries a URL; other platforms carry either a URL or a platform-native handle.
- com.t0ronto.commons.entity record An anchor in the t0ronto data commons: a bare, claim-free identity for a thing — an organization, programme, venue, neighbourhood, or a vocabulary concept. The anchor holds NO properties of its own. Everything true of it — name, type, topics, location, prefLabel, broader, alignments — is asserted by separate com.t0ronto.commons.statement records, which may be authored by many different DIDs. The anchor exists only to mint a stable, resolvable identity that statements point at. Whether an anchor