{
  "title": "About — Cred-spec coherence notes — first-person / DTG credential terminology",
  "story": [
    {
      "type": "markdown",
      "id": "d218bbdfc48e0427",
      "text": "# Cred-spec coherence notes — first-person / DTG credential terminology"
    },
    {
      "type": "markdown",
      "id": "ee8454b68af44f6b",
      "text": "**What this is:** a coherence review of where agentprivacy-docs references DTG credential terminology, against\nthe **DTG Credentials Core Specification** (ToIP DTGWG, Working Draft v1.0,\n<https://trustoverip.github.io/dtgwg-cred-spec/>), with ready-to-apply reconciliations. Prompted by reading\nthat spec as DTG ZKP Task Force co-chair.\n\n**Governance / routing — READ FIRST.** The two richest targets live under `papers/`, which the V6 Rehydration\nPipeline (`papers/Programme/pipeline/CLAUDE.md`) declares **READ-ONLY canon**, and `E7-identity-vrc.md` is a\n**generated extraction** (\"generated artifacts are never hand-edited; fix inputs, rebuild\"). So this doc does\n**not** hand-edit any canon. Each gap below is routed:\n- **Canon (`papers/…`)** → fix the *input source* and rebuild the extraction, or raise with role A0 / SOURCES.md;\n  never a direct edit to the extraction or whitepaper.\n- **Non-canon (`specs/`, `research/` letters)** → editable, but flagged here for your call given the gated\n  private-repo rollout + FROZEN public `origin` (project_docs_publishing_flow). Nothing here is pushed.\n\nSibling map for the ZK side lives in `~/dtgwg-zkp-tf-mage/runtimes/CRED-SPEC-COHERENCE.md`.\n\n---"
    },
    {
      "type": "markdown",
      "id": "679034d624b6962a",
      "text": "## Gap 1 — five of six DTG credential acronyms are asserted but never defined  *(canon; route via pipeline)*\n\n`papers/Programme/pipeline/extractions/E7-identity-vrc.md`, **E7-C26 (L199)** lists the set bare:\n> \"…a decentralised-trust-graph credential set of six credential types plus a relationship card (VRC among\n> **VMC, VIC, VPC, VEC, VWC**, plus RCard)…\"\n\nOnly VRC is expanded anywhere in the corpus. The other five never get an expansion (grep confirms zero hits for\nany expansion form). **Reconciliation (cred-spec expansions):**\n\n| Acronym | Cred-spec expansion | One-line role |\n|---|---|---|\n| VMC | **Verifiable Membership Credential** | membership in a VTC/VTN community |\n| VIC | **Verifiable Invitation Credential** | authorises a prospective member to join |\n| VPC | **Verifiable Persona Credential** | links a persona (P-DID) to a relationship |\n| VEC | **Verifiable Endorsement Credential** | skills / reputation assertion on an edge |\n| VWC | **Verifiable Witness Credential** | third-party attestation of a relationship (requires `taskContext`) |\n| RCard | relationship card (**r-card**) | self-updating vCard analog carrying a VRC (planned DTG VDS) |\n\n**Route:** add these expansions to the *source* the E7 extraction is built from (hearthold-build README /\ntome-x), then rebuild — so the extraction stops asserting \"six types\" without defining five of them."
    },
    {
      "type": "markdown",
      "id": "87b10a4db54f24e4",
      "text": "## Gap 2 — VRC concept drift: richer than the spec  *(NOT a defect — a contribution surface; flag only)*\n\nThe name is coherent everywhere (VRC = **Verifiable Relationship Credential**, incl.\n`specs/vrc_promise_protocol_v3_3.md:1325`, `papers/whitepapers/swordsman_mage_whitepaper_v6_3.md:405`). But the\n*concept* is broader than the spec's:\n- Corpus: \"Bilateral trust object proving **mutual comprehension**. **Promise bundle.**\" (vrc_promise L1325);\n  \"VRCs are *promise bundles* — coordinated bilateral promises grouped for reuse\" (whitepaper L411).\n- Cred-spec: VRC is a bare **relationship attestation** (a signed edge; ZK proves possession + selective\n  disclosure), with no economic/promise-theoretic semantics.\n\n**Do not erase your richer definition to \"match.\"** This is opportunity #9 in the ZKP-TF register: propose the\npromise-bundle economics as an *extension the spec's minimal VRC schema can carry*. **Action:** add a one-line\nreconciliation note where VRC is defined (\"same acronym as the DTG cred-spec's VRC; agentprivacy extends it with\npromise-theoretic / ERC-7812 economics\") rather than a rewrite. Canon copies route via pipeline; the `specs/`\ncopy is directly editable if you approve."
    },
    {
      "type": "markdown",
      "id": "0cb1790e70f09369",
      "text": "## Gap 3 — four-DID taxonomy: mis-ordered and unexpanded  *(non-canon; `research/`)*\n\n`research/privacymage-response-fpp-zkp-progress.md:103`:\n> \"The four-DID taxonomy **(R-DID, M-DID, P-DID, C-DID)** maps onto the pseudonym derivation…\"\n\nOrder differs from the spec and the letters are never expanded (latent collision — an implied \"Principal/Context\"\nreading would be wrong). **Reconciliation (cred-spec):** canonical order **R/M/C/P-DID** =\n**R**elationship / **M**embership / **C**ommunity / **P**ersona DID. Suggested edit: \"the four-DID taxonomy\n(R-DID relationship, M-DID membership, C-DID community, P-DID persona)\". Directly editable (non-canon) on your OK."
    },
    {
      "type": "markdown",
      "id": "e35c88ae24e3f66f",
      "text": "## Gap 4 — \"First Person credential\" conflates PHC and IDVC; IDVC absent entirely  *(mixed)*\n\n\"First Person credential\" is used two ways in `research/privacymage-response-fpp-zkp-progress.md`:\n- L23 as the personhood credential specifically: \"two credential types: **personhood credentials (PHCs)**… and\n  verifiable relationship credentials (VRCs)…\" ✅ coheres.\n- L27 as the whole sovereignty stack: \"the next question the **First Person credential** must answer…\" — loose.\n- `grimoires/spellbook_v5_0_canonical.md:82` / `reference/GLOSSARY_MASTER_v4_0.md:2182` flatly equate\n  👤✓ \"First Person credential\" = \"Verified personhood.\"\n\nThe cred-spec now gives these **distinct** names: **PHC** (a governed VMC: real-human + one-per-person) and\n**IDVC** (Identity Verification Credential — the identity-proofing input, e.g. Veriff/Jumio; *not* a DTG\nsubtype). **IDVC appears nowhere in the corpus** — a pure gap. **Reconciliation:** where \"First Person\ncredential\" means personhood, keep it tied to **PHC**; add at least a pointer to **IDVC** as the distinct\nidentity-proofing carrier so the two aren't collapsed. Glossary lives under `reference/` (check pipeline status\nbefore editing); the letter is non-canon."
    },
    {
      "type": "markdown",
      "id": "6721ec55d86a17ad",
      "text": "## Gap 5 — VTA load-bearing but unexpanded; VTC / VTN absent  *(mixed)*\n\n`research/privacymage-response…:103` uses \"each **VTA**\", \"the **VTA** separation theorem\", \"**OpenVTC**\ninfrastructure\" without expansion; VTC/VTN never appear as standalone terms. **Reconciliation (cred-spec):**\n- **VTA** = **Verifiable Trust Agent** (a DTG node's digital agent; local VTA on edge, cloud VTA on servers).\n- **VTC** = **Verifiable Trust Community** (a DTG node, C-DID-identified).\n- **VTN** = **Verifiable Trust Network** (a set of VTCs under a governance framework).\nAdd expansions at first use. (Note: our ZKP-TF README already aligns VTA capitalization to the spec.)\n\n---"
    },
    {
      "type": "markdown",
      "id": "91e7b934283e91d4",
      "text": "## Summary of routing\n\n| Gap | Where | Kind | Route |\n|---|---|---|---|\n| 1 five acronyms | E7-C26 (canon) | definition-absent | fix input → rebuild extraction |\n| 2 VRC drift | specs + canon | substantive (contribution) | reconciliation note, not rewrite; your call |\n| 3 four-DID | research letter | cosmetic + correctness | direct edit on approval |\n| 4 First-Person/PHC/IDVC | research + reference | conflation + gap | direct edit (letter) / pipeline (glossary) |\n| 5 VTA/VTC/VTN | research letter | definition-absent | direct edit on approval |\n\n**Nothing has been edited in the corpus.** Confirm which non-canon edits (Gaps 3–5 in `research/` + the `specs/`\nnote in Gap 2) you want applied, and how you want the canon gaps (1, and the canon side of 2/4) routed through\nthe pipeline. The spec-side expansions above are ready to drop in."
    },
    {
      "type": "markdown",
      "id": "f434d3a47bbf3cec",
      "text": "# Assets"
    },
    {
      "id": "a618862485a102eb",
      "type": "assets",
      "text": "about-cred-spec-coherence-notes-first-person-dtg-credential-terminology"
    },
    {
      "type": "markdown",
      "id": "1c0a6ac98bfe07e8",
      "text": "## Navigation\n\n← [[Welcome Visitors]] · [[About Agentprivacy]]"
    }
  ],
  "journal": [
    {
      "type": "create",
      "item": {
        "title": "About — Cred-spec coherence notes — first-person / DTG credential terminology",
        "story": [
          {
            "type": "markdown",
            "id": "d218bbdfc48e0427",
            "text": "# Cred-spec coherence notes — first-person / DTG credential terminology"
          },
          {
            "type": "markdown",
            "id": "ee8454b68af44f6b",
            "text": "**What this is:** a coherence review of where agentprivacy-docs references DTG credential terminology, against\nthe **DTG Credentials Core Specification** (ToIP DTGWG, Working Draft v1.0,\n<https://trustoverip.github.io/dtgwg-cred-spec/>), with ready-to-apply reconciliations. Prompted by reading\nthat spec as DTG ZKP Task Force co-chair.\n\n**Governance / routing — READ FIRST.** The two richest targets live under `papers/`, which the V6 Rehydration\nPipeline (`papers/Programme/pipeline/CLAUDE.md`) declares **READ-ONLY canon**, and `E7-identity-vrc.md` is a\n**generated extraction** (\"generated artifacts are never hand-edited; fix inputs, rebuild\"). So this doc does\n**not** hand-edit any canon. Each gap below is routed:\n- **Canon (`papers/…`)** → fix the *input source* and rebuild the extraction, or raise with role A0 / SOURCES.md;\n  never a direct edit to the extraction or whitepaper.\n- **Non-canon (`specs/`, `research/` letters)** → editable, but flagged here for your call given the gated\n  private-repo rollout + FROZEN public `origin` (project_docs_publishing_flow). Nothing here is pushed.\n\nSibling map for the ZK side lives in `~/dtgwg-zkp-tf-mage/runtimes/CRED-SPEC-COHERENCE.md`.\n\n---"
          },
          {
            "type": "markdown",
            "id": "679034d624b6962a",
            "text": "## Gap 1 — five of six DTG credential acronyms are asserted but never defined  *(canon; route via pipeline)*\n\n`papers/Programme/pipeline/extractions/E7-identity-vrc.md`, **E7-C26 (L199)** lists the set bare:\n> \"…a decentralised-trust-graph credential set of six credential types plus a relationship card (VRC among\n> **VMC, VIC, VPC, VEC, VWC**, plus RCard)…\"\n\nOnly VRC is expanded anywhere in the corpus. The other five never get an expansion (grep confirms zero hits for\nany expansion form). **Reconciliation (cred-spec expansions):**\n\n| Acronym | Cred-spec expansion | One-line role |\n|---|---|---|\n| VMC | **Verifiable Membership Credential** | membership in a VTC/VTN community |\n| VIC | **Verifiable Invitation Credential** | authorises a prospective member to join |\n| VPC | **Verifiable Persona Credential** | links a persona (P-DID) to a relationship |\n| VEC | **Verifiable Endorsement Credential** | skills / reputation assertion on an edge |\n| VWC | **Verifiable Witness Credential** | third-party attestation of a relationship (requires `taskContext`) |\n| RCard | relationship card (**r-card**) | self-updating vCard analog carrying a VRC (planned DTG VDS) |\n\n**Route:** add these expansions to the *source* the E7 extraction is built from (hearthold-build README /\ntome-x), then rebuild — so the extraction stops asserting \"six types\" without defining five of them."
          },
          {
            "type": "markdown",
            "id": "87b10a4db54f24e4",
            "text": "## Gap 2 — VRC concept drift: richer than the spec  *(NOT a defect — a contribution surface; flag only)*\n\nThe name is coherent everywhere (VRC = **Verifiable Relationship Credential**, incl.\n`specs/vrc_promise_protocol_v3_3.md:1325`, `papers/whitepapers/swordsman_mage_whitepaper_v6_3.md:405`). But the\n*concept* is broader than the spec's:\n- Corpus: \"Bilateral trust object proving **mutual comprehension**. **Promise bundle.**\" (vrc_promise L1325);\n  \"VRCs are *promise bundles* — coordinated bilateral promises grouped for reuse\" (whitepaper L411).\n- Cred-spec: VRC is a bare **relationship attestation** (a signed edge; ZK proves possession + selective\n  disclosure), with no economic/promise-theoretic semantics.\n\n**Do not erase your richer definition to \"match.\"** This is opportunity #9 in the ZKP-TF register: propose the\npromise-bundle economics as an *extension the spec's minimal VRC schema can carry*. **Action:** add a one-line\nreconciliation note where VRC is defined (\"same acronym as the DTG cred-spec's VRC; agentprivacy extends it with\npromise-theoretic / ERC-7812 economics\") rather than a rewrite. Canon copies route via pipeline; the `specs/`\ncopy is directly editable if you approve."
          },
          {
            "type": "markdown",
            "id": "0cb1790e70f09369",
            "text": "## Gap 3 — four-DID taxonomy: mis-ordered and unexpanded  *(non-canon; `research/`)*\n\n`research/privacymage-response-fpp-zkp-progress.md:103`:\n> \"The four-DID taxonomy **(R-DID, M-DID, P-DID, C-DID)** maps onto the pseudonym derivation…\"\n\nOrder differs from the spec and the letters are never expanded (latent collision — an implied \"Principal/Context\"\nreading would be wrong). **Reconciliation (cred-spec):** canonical order **R/M/C/P-DID** =\n**R**elationship / **M**embership / **C**ommunity / **P**ersona DID. Suggested edit: \"the four-DID taxonomy\n(R-DID relationship, M-DID membership, C-DID community, P-DID persona)\". Directly editable (non-canon) on your OK."
          },
          {
            "type": "markdown",
            "id": "e35c88ae24e3f66f",
            "text": "## Gap 4 — \"First Person credential\" conflates PHC and IDVC; IDVC absent entirely  *(mixed)*\n\n\"First Person credential\" is used two ways in `research/privacymage-response-fpp-zkp-progress.md`:\n- L23 as the personhood credential specifically: \"two credential types: **personhood credentials (PHCs)**… and\n  verifiable relationship credentials (VRCs)…\" ✅ coheres.\n- L27 as the whole sovereignty stack: \"the next question the **First Person credential** must answer…\" — loose.\n- `grimoires/spellbook_v5_0_canonical.md:82` / `reference/GLOSSARY_MASTER_v4_0.md:2182` flatly equate\n  👤✓ \"First Person credential\" = \"Verified personhood.\"\n\nThe cred-spec now gives these **distinct** names: **PHC** (a governed VMC: real-human + one-per-person) and\n**IDVC** (Identity Verification Credential — the identity-proofing input, e.g. Veriff/Jumio; *not* a DTG\nsubtype). **IDVC appears nowhere in the corpus** — a pure gap. **Reconciliation:** where \"First Person\ncredential\" means personhood, keep it tied to **PHC**; add at least a pointer to **IDVC** as the distinct\nidentity-proofing carrier so the two aren't collapsed. Glossary lives under `reference/` (check pipeline status\nbefore editing); the letter is non-canon."
          },
          {
            "type": "markdown",
            "id": "6721ec55d86a17ad",
            "text": "## Gap 5 — VTA load-bearing but unexpanded; VTC / VTN absent  *(mixed)*\n\n`research/privacymage-response…:103` uses \"each **VTA**\", \"the **VTA** separation theorem\", \"**OpenVTC**\ninfrastructure\" without expansion; VTC/VTN never appear as standalone terms. **Reconciliation (cred-spec):**\n- **VTA** = **Verifiable Trust Agent** (a DTG node's digital agent; local VTA on edge, cloud VTA on servers).\n- **VTC** = **Verifiable Trust Community** (a DTG node, C-DID-identified).\n- **VTN** = **Verifiable Trust Network** (a set of VTCs under a governance framework).\nAdd expansions at first use. (Note: our ZKP-TF README already aligns VTA capitalization to the spec.)\n\n---"
          },
          {
            "type": "markdown",
            "id": "91e7b934283e91d4",
            "text": "## Summary of routing\n\n| Gap | Where | Kind | Route |\n|---|---|---|---|\n| 1 five acronyms | E7-C26 (canon) | definition-absent | fix input → rebuild extraction |\n| 2 VRC drift | specs + canon | substantive (contribution) | reconciliation note, not rewrite; your call |\n| 3 four-DID | research letter | cosmetic + correctness | direct edit on approval |\n| 4 First-Person/PHC/IDVC | research + reference | conflation + gap | direct edit (letter) / pipeline (glossary) |\n| 5 VTA/VTC/VTN | research letter | definition-absent | direct edit on approval |\n\n**Nothing has been edited in the corpus.** Confirm which non-canon edits (Gaps 3–5 in `research/` + the `specs/`\nnote in Gap 2) you want applied, and how you want the canon gaps (1, and the canon side of 2/4) routed through\nthe pipeline. The spec-side expansions above are ready to drop in."
          },
          {
            "type": "markdown",
            "id": "f434d3a47bbf3cec",
            "text": "# Assets"
          },
          {
            "id": "a618862485a102eb",
            "type": "assets",
            "text": "about-cred-spec-coherence-notes-first-person-dtg-credential-terminology"
          },
          {
            "type": "markdown",
            "id": "1c0a6ac98bfe07e8",
            "text": "## Navigation\n\n← [[Welcome Visitors]] · [[About Agentprivacy]]"
          }
        ]
      },
      "date": 1787079756409
    }
  ]
}