---
technique_id: Hypergraph.AnchorNameLedger@v1
pattern: Pattern.Naming.ProvenancedTermBinding
version: 1
channel: djat-poc-hypergraph-20260716
authors:
  - { order: 1, name: DJ Thomson, did: did:placeholder:dj-thomson-pathways, role: technique-originator }
---

# Anchor Name Ledger

The attribution-ledger analogue for **branded unique names**. The Anchor Name Ledger
tracks **every mention of every trademark-like anchor** (a `tm:` name in the
[Standards Anchor Registry](../registry/external-names.yaml)) and the specific
individual and entity associations with it, across every indexed context and Pathway
dimension.

## Why

Any unique name representing a specific protocol, acronym, standard, community, or
entity is a **specific, independently discernible, almost trademark-like proper name**
in the registry. This gives two things at once:

1. **A mark to track across.** Every place a name is used cites its `tm:` slug, so a
   mention anywhere in the bundle (a control, a pathway, a gap-matrix row, a CALM node,
   a portal card) is discoverable and countable.
2. **An authenticated entry point.** Each anchor carries a steward and an
   `authenticated_entry_point` (a DID) for engagement - a front door for every other
   standard to collaborate through.

## Ledger entry shape

```yaml
mention:
  id: mention_<hash>
  anchor: tm:soc2
  cited_in: calm/architecture/incident-response-fabric.calm.json#poc-evidence-layer
  context_dimensions:
    sdg_domain: security
    standard_anchor: tm:soc2
  associated_entities:
    - { name: "AICPA & CIMA", role: steward, did: did:web:aicpa-cima.com }
  associated_individuals: []          # e.g. a named contributor, when applicable
  recorded_at: <ISO-8601>
  trust_key_deep_link: "poc-hypergraph://context/{ctx}?standard_anchor=tm:soc2"
```

## Cryptographic linking

Each mention is bindable into a [Trust Key](../../trust-key/techniques/TRUST_KEY_TECHNIQUE.v1.md)
dimensional deep link on the `standard_anchor` dimension. That makes the association
between a branded name and its individuals/entities:

- **deep-linkable** - resolve `standard_anchor=tm:...` to every mention and association;
- **offline-verifiable** - the relying party checks the mention against the trust card;
- **substrate-agnostic** - both ends are registry-anchored ids, not URLs (the same
  property the [Right to Follow](../../hypergraph-pathways/terms/Term.RightToFollow.v1.yaml) relies on).

## Named engagements recorded here

- **FINOS** (`tm:finos`) and **Karl Moll** (Technical Project Advocate, FINOS) - the
  open-invitation targets; Karl's engagement on the AIGF x CCC x CALM convergence is
  recorded against `tm:finos-calm`, `tm:finos-aigf`, `tm:finos-ccc`. See
  [`OPEN_INVITATION.md`](../../finos-invitation/OPEN_INVITATION.md).
- **Jim Manico** - recorded against `tm:owasp-aivss` (AISVS follow-up from the Gap Analysis).
- **Ken Huang** and **Tricia Wang** - co-chairs, recorded against `tm:poc-cv-standard`.
- **DJ Thomson** - technique-originator, recorded against `tm:pathways` (Pathways RIS v1.2.0; shared orchestration and encoding language for this bundle).

## Pathway

Opened by [`Hypergraph.Standard.AnchorRegister@v1`](../../hypergraph-pathways/pathways/Hypergraph.Standard.AnchorRegister@v1.yaml)
(step 4) and appended to on every honored contribution and every portal engagement.