Identity & Context · Document 1 of 3

← EarthLinC Overview

Document 1 of 3

Identity & Context

What a person is. What an account is. What a signature actually establishes — and what it does not.

Overview

AI extends what people can explore and make. People's questions, experiences, judgment and choices provide direction. EarthLinC organises that work into four dimensions it can name and keep track of: Identity, Context, Relationship and Knowledge.

This document defines Identity and Context, and defines Knowledge at IC-11. Relationship is defined in Document 2, Relationships & X. Human agency, AI roles and infrastructure are covered in Document 3, Human Agency, AI & Infrastructure.

It is written for a reader who wants to know plainly what the protocol requires, and where it deliberately stops.

  • Identity

    Who or what acted, and on whose authority — kept separate from the account that signed.

    Defined here · IC-01 to IC-03
  • Context

    The question, intention, sources, circumstances and history a Station came from. Often partial.

    Defined here · IC-08 to IC-10
  • Relationship

    How Stations, Realms and contributions connect, and what each connection commits to.

    Defined in Document 2, Relationships & X
  • Knowledge

    Works, observations, learning records, findings and interpretations, with source material, participant interpretation and AI interpretation kept distinguishable.

    Defined here · IC-11

The summaries above restate the clauses; the requirements themselves are set out in full under Full Specification.

Key Scenarios

The two figures below follow one illustrative person with one question. They are explanatory drawings: no wallet is connected, no signature is produced, no membership is granted and no record is written.

Figure 1 · Illustrative example A question becomes Station A Clauses: IC-01, IC-02, IC-03, IC-04, IC-08, IC-09, IC-12, IC-13
A person's question becomes Station A, carrying Identity, Context, Realm and Version annotations A hand-drawn diagram. On the left, a person labelled "A person, real-world identity, IC-01" and a speech bubble labelled "A question, an intention". An arrow leads right into a large box labelled "Station A, an independently identifiable work, IC-04". Inside it are four stacked panels: Identity (IC-01, IC-02), Context (IC-08), Realm (IC-12) and Version (IC-13). Below the person, a separate box labelled "Signing account, key or wallet action, IC-02 and IC-09" is joined to the Identity panel by a dashed line, showing that signing is held apart from real-world identity. A person real-world identity IC-01 A question, an intention Signing account key or wallet action IC-02 · IC-09 Station A an independently identifiable work IC-04 Identity who or what acted, and on whose authority IC-01 · IC-02 Context question, intention, sources, history IC-08 Realm the environment it sits in, with a route back IC-12 Version a fixed version or a changing reference IC-13 A verified signature establishes the signing action (IC-09). On its own it is not evidence of real-world identity (IC-01, IC-02). Nothing here is signed; this is an explanatory drawing. A person's question becomes Station A, carrying Identity, Context, Realm and Version annotations The same hand-drawn diagram redrawn vertically. From top to bottom: a person labelled "A person, real-world identity, IC-01"; a box labelled "A question, an intention, IC-08"; a large box labelled "Station A, an independently identifiable work, IC-04" containing four panels — Identity (IC-01, IC-02), Context (IC-08), Realm (IC-12) and Version (IC-13); and, joined by a dashed line, a box labelled "Signing account, key or wallet action, IC-02 and IC-09" noting that a signature shows the signing action, not who the person is. A person real-world identity IC-01 A question, an intention IC-08 Station A independently identifiable work IC-04 Identity who acted, on whose authority IC-01 · 02 Context question, sources, history IC-08 Realm environment, route back IC-12 Version fixed version or changing reference IC-13 Signing account a signature shows the signing action, not who the person is IC-02 · 09

A person asks a question. The work that follows becomes Station A — independently identifiable thought, work, research, media or interaction (IC-04). A conforming display carries four annotations with it: Identity, who or what acted and on whose authority (IC-01, IC-02); Context, the originating question, intention, sources, circumstances and history, which may be partial (IC-08); Realm, the environment the Station sits in, with a route back to the originating contribution (IC-12); and Version, which states whether a reference is a fixed version or a changing one (IC-13). The signing account is held apart from all of this: a verified signature establishes the relevant signing action (IC-09) and is not by itself evidence of real-world identity, and where authorisation or delegation cannot be established, that is disclosed rather than omitted (IC-03).

Figure 2 · Illustrative example Two independently sourced works, shown together Clauses: IC-04, IC-05, IC-06, IC-11, IC-12, IC-13
State one: Station A and Station B as independent works Two hand-drawn boxes side by side and unconnected. Station A lists source, attribution, version v1 fixed, and its own context, with clauses IC-04, IC-05 and IC-13. Station B lists the same fields for a different participant. A note reads that the two works are separate and nothing is connected. Station A IC-04 Source: participant A Attribution: participant A Version: v1, fixed Context: own question, own sources IC-05 · IC-13 Station B IC-04 Source: participant B Attribution: participant B Version: v1, fixed Context: independently sourced IC-05 · IC-13 Two separate works. Nothing is connected, and no record is created. State one: Station A and Station B as independent works The same two hand-drawn boxes, stacked vertically and unconnected. Each lists source, attribution, version v1 fixed and its own context, with clauses IC-04, IC-05 and IC-13. A note reads that the two works are separate and nothing is connected. Station A IC-04 Source: participant A Attribution: participant A Version: v1, fixed Context: own question, own sources IC-05 · IC-13 Station B IC-04 Source: participant B Attribution: participant B Version: v1, fixed Context: independently sourced IC-05 · IC-13 Two separate works. Nothing is connected, and no record is created.
State two: Station A and Station B in a shared presentation The two hand-drawn boxes sit at the top, each noting that source, attribution and version are retained under IC-05. Hand-drawn lines run down from both into a pale teal box labelled "Shared presentation". Inside, five lines state that Station A and Station B each remain identifiable, that constituent attribution is preserved rather than replaced under IC-05, that source, participant and AI interpretation stay distinguishable under IC-11, that presentation grants no copyright, ownership, modification or publication permission under IC-06, and that any further permission effect is pending. Station A source · attribution · version retained IC-05 · IC-13 Station B source · attribution · version retained IC-05 · IC-13 Shared presentation IC-05 · IC-11 · IC-12 Station A — source, attribution and version remain identifiable Station B — source, attribution and version remain identifiable Constituent attribution is preserved, not replaced (IC-05) Source, participant and AI interpretation stay distinguishable (IC-11) No copyright, ownership, modification or publication permission (IC-06) Further permission effects: pending State two: Station A and Station B in a shared presentation The same relationship redrawn vertically. Station A and Station B sit at the top, each noting retained source, attribution and version under IC-05. Lines run down into a pale teal box labelled "Shared presentation", which states that each work remains identifiable, that attribution is preserved rather than replaced under IC-05, that source, participant and AI interpretation stay distinguishable under IC-11, that no copyright, ownership, modification or publication permission is granted under IC-06, and that further permission effects are pending. Station A source · version retained IC-05 · IC-13 Station B source · version retained IC-05 · IC-13 Shared presentation IC-05 · IC-11 · IC-12 Station A — source, attribution and version remain identifiable Station B — source, attribution and version remain identifiable Attribution is preserved, not replaced (IC-05) Source, participant and AI interpretation stay distinguishable (IC-11) No copyright, ownership, modification or publication permission is granted (IC-06) Further permission effects: pending

Independent works. Station A and Station B are separately sourced. Each keeps its own source link, its own attribution, its own context and its own version reference. Nothing is connected in this state, and no record is created.

Combined view. The two are shown together in one presentation. Both constituent sources stay identifiable and neither attribution is replaced (IC-05); source material, participant interpretation and AI interpretation remain distinguishable (IC-11); the route back to each originating contribution is retained (IC-12); and each version reference is still marked as fixed or changing (IC-13). Combining changes presentation only — it grants no copyright, no token ownership, no permission to modify and no permission to publish or redistribute (IC-06). Any further permission effect is marked pending rather than assumed.

Read together, the two states describe one rule: a shared presentation may bring works alongside each other, but it does not absorb them. Sources are preserved explicitly, and the permissions attached to each work are unchanged by the act of showing them side by side.

Full Specification

Fifteen numbered requirements, IC-01 to IC-15, set out in full. Three keywords carry weight; they describe proposed conformance within this specification.

  • MUSTRequired for conformance with this specification.
  • SHOULDRecommended; departures are expected to be explained.
  • MAYOptional, at the implementer's discretion.

All 15 clauses shown.

  1. IC-01

    Person

    Definition

    A Person is a human participant. An account, wallet, token or agent is not sufficient evidence of real-world identity.

  2. IC-02

    Identity references

    Must

    Identity references may identify accounts, addresses or other identifiers. Implementations MUST distinguish verified signatures and account actions from real-world identity claims.

  3. IC-03

    Authorisation and delegation

    Must

    Implementations MUST distinguish human-authorised actions from autonomous or delegated actions where this can be established. Delegation scope MUST be identifiable, and implementations MUST disclose when authorisation cannot be established.

  4. IC-04

    Station

    DefinitionMay

    A Station is independently identifiable thought, work, research, media or interaction. A Station MAY stand alone or combine with others.

  5. IC-05

    Combination and attribution

    Must

    Combining, displaying or referencing Stations MUST preserve identifiable source links, and MUST NOT silently replace constituent attribution.

  6. IC-06

    Distinct rights

    Must

    Implementations MUST distinguish author attribution, account control, token ownership, permission to modify, and permission to publish or redistribute. One is not proof of another. Token ownership alone does not establish copyright.

  7. IC-07

    Navi

    MustShould

    Navi connects AI capabilities to Station development and interaction; its roles SHOULD be understandable to participants. Assistance MUST NOT by itself establish human authorship, nor authorise publication, modification, spending, signing or relationships.

  8. IC-08

    Context

    DefinitionMay

    Context includes the originating question, intention, sources, circumstances and history. Context MAY be partial, private, disputed or evolving.

  9. IC-09

    Statements and records

    Must

    Implementations MUST distinguish participant statements from independently verifiable records. A valid signature establishes the relevant signing action, not the truth of the statement.

  10. IC-10

    Disclosed context

    ShouldMust

    Participants SHOULD understand what context is disclosed. Public attribution MUST NOT imply permission to disclose unrelated personal information.

  11. IC-11

    Knowledge

    Must

    Knowledge includes works, observations, learning records, findings and interpretations. Implementations MUST distinguish source material, participant interpretation and AI interpretation where known. Inclusion MUST NOT imply independent validation of accuracy or research quality.

  12. IC-12

    Realm

    DefinitionMust

    A Realm is an identifiable environment organising Stations and relationships. Association with another Realm or with X MUST retain a route to the originating contribution and its available context.

  13. IC-13

    Version and reference

    Must

    Relationship and verification MUST identify a fixed version versus a changing reference. A changing reference MUST NOT be presented as an immutable commitment to current content.

  14. IC-14

    Web3 records

    Must

    Implemented Web3 records MUST explain what they establish. Identifiers, signatures or tokens MUST NOT be presented as proof of permanent storage, uninterrupted hosting, correct authorship or factual truth.

  15. IC-15

    Provenance and availability

    ShouldMust

    Implementations SHOULD preserve understandable source, version and participation links, and MUST disclose unavailable content or incomplete history when it is material to interpretation.

Specification Boundaries

The technical matters below are not specified in IC-01 to IC-15. This document states no requirement about them, and implementations are not constrained by it on these points.

  • Unspecified

    Identifier formats and identity verification methods.

  • Unspecified

    ERC-6551 Realm implementation, control and recovery mechanisms.

  • Unspecified

    The attribution model used to express constituent sources.

  • Unspecified

    The technical form of Navi delegation and its scope encoding.

  • Unspecified

    How version commitments are recorded and resolved.

  • Unspecified

    Metadata visibility rules and default disclosure settings.

  • Unspecified

    Storage and retrieval guarantees for source and history availability.

Document Information

This specification defines conformance requirements and does not certify implementation. The current website policies remain applicable; this document does not replace them.

One of the three documents in the EarthLinC Protocol set: Identity & Context (this document), Relationships & X, and Human Agency, AI & Infrastructure.

English is the reference version of this document; the 繁體中文, Español and 日本語 texts are full translations of the same text and carry the same status.