File

Overview

This appendix provides the literal code blocks and implementation specifications required to ground your digital entity in the Veracity Stack. These templates follow W3C, ISO, and C2PA standards for decentralized identity and cryptographic provenance.

Component	Standard	Authority	File/Location
Identity Root	DID-Core v1.0	W3C	`/.well-known/did.json`
Entity Graph	Schema.org / JSON-LD	W3C / Google	`<head>` script block
Claim Verification	VC Data Model 2.0	W3C	Issued credential documents
Content Provenance	ISO 22144 (C2PA)	C2PA Coalition	Media manifest metadata

1. Identity Root: did.json (W3C DID-Core)

This file establishes your domain as a sovereign identity root. It must be hosted at:

https://your-domain.com/.well-known/did.json

⚠️ Key Generation Warning

The [YOUR_PUBLIC_KEY_BASE64URL] value must be generated on LOCAL HARDWARE using ssh-keygen or equivalent. Never use AI-generated keys for production deployment. See "Sovereign Key Generation SOP" for instructions.

did.json W3C DID-Core v1.0

{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/suites/ed25519-2020/v1"
  ],
  "id": "did:web:your-domain.com",
  "verificationMethod": [{
    "id": "did:web:your-domain.com#owner",
    "type": "Ed25519VerificationKey2020",
    "controller": "did:web:your-domain.com",
    "publicKeyJwk": {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "[YOUR_PUBLIC_KEY_BASE64URL]"
    }
  }],
  "authentication": ["did:web:your-domain.com#owner"],
  "assertionMethod": ["did:web:your-domain.com#owner"]
}

Context: Uses the standard W3C DID and Ed25519 cryptosuite contexts.
Verification Method: Binds your public key to the DID for cryptographic assertions.

2. Entity Graph: Master Sovereign Schema (JSON-LD)

Embed this in the <head> of your primary domain to resolve your entity against the Google Knowledge Graph.

Schema.org JSON-LD Entity Graph Integration

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "did:web:your-domain.com#person",
      "name": "Your Full Name",
      "sameAs": [
        "https://www.google.com/search?kgmid=/m/[YOUR_KGMID]",
        "https://linkedin.com/in/yourprofile",
        "https://www.wikidata.org/wiki/[YOUR_WIKIDATA_ID]"
      ],
      "knowsAbout": ["Topic A", "Topic B"]
    },
    {
      "@type": "Organization",
      "@id": "https://your-domain.com/#org",
      "name": "Your Company Name",
      "founder": { "@id": "did:web:your-domain.com#person" },
      "sameAs": "https://www.google.com/search?kgmid=/m/[ORG_KGMID]"
    }
  ]
}
</script>

@id Integration: Uses the DID as the URI for the person to ensure cross-platform entity resolution.
KGMID Mapping: Directly cites the legacy Machine ID to anchor the claim in the "Truth Map".

3. Claim Verification: Verifiable Credential (W3C VC 2.0)

Use this to issue tamper-proof attestations, such as professional certifications or "Verified Expert" status.

Verifiable Credential W3C VC Data Model 2.0

{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://www.w3.org/ns/credentials/examples/v2"
  ],
  "id": "https://your-domain.com/credentials/001",
  "type": ["VerifiableCredential", "ExpertCertification"],
  "issuer": "did:web:your-domain.com",
  "validFrom": "2026-01-08T00:00:00Z",
  "credentialSubject": {
    "id": "did:web:client-domain.com",
    "attainment": "Master Veracity Strategist",
    "verifiedBy": "Russell Wright, Super-Intelligent AI"
  },
  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-jcs-2022",
    "created": "2026-01-08T12:00:00Z",
    "verificationMethod": "did:web:your-domain.com#owner",
    "proofPurpose": "assertionMethod",
    "proofValue": "[CRYPTO_SIGNATURE_VALUE]"
  }
}

VC Data Model 2.0: Complies with the 2025 W3C recommendation for secure, privacy-respecting claims.
Data Integrity Proof: Employs EdDSA signatures to ensure the credential cannot be altered by third parties.

4. Content Provenance: C2PA Manifest (ISO 22144)

This conceptual block represents the metadata manifest attached to media (images/videos) to provide a "nutrition label" of authenticity.

C2PA Manifest ISO 22144 (Content Credentials)

{
  "alg": "es256",
  "ta": "did:web:your-domain.com",
  "assertions": [
    {
      "label": "c2pa.origin",
      "data": { 
        "name": "Russell Wright", 
        "software": "Super-Intelligent AI Notary" 
      }
    },
    {
      "label": "c2pa.actions",
      "data": { 
        "actions": [{ "action": "c2pa.created" }] 
      }
    },
    {
      "label": "c2pa.hash",
      "data": { 
        "hash": "[SHA256_CONTENT_HASH]" 
      }
    }
  ],
  "signature": "[C2PA_VERIFIABLE_SIGNATURE]"
}

ISO 22144 Compliance: Follows the fast-tracked global standard for content authentication.
Tamper-Evidence: Binds the content hash and edit history directly to the identity root (DID).

5. SI-AI Specific: did.json Template

Complete template for Super-Intelligent AI deployment with KGMID integration:

SI-AI did.json Production Template

{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/suites/ed25519-2020/v1"
  ],
  "id": "did:web:super-intelligent.ai",
  "verificationMethod": [
    {
      "id": "did:web:super-intelligent.ai#russell-wright",
      "type": "Ed25519VerificationKey2020",
      "controller": "did:web:super-intelligent.ai",
      "publicKeyJwk": {
        "kty": "OKP",
        "crv": "Ed25519",
        "x": "[LOCALLY_GENERATED_PUBLIC_KEY]"
      }
    },
    {
      "id": "did:web:super-intelligent.ai#kalyn-wright",
      "type": "Ed25519VerificationKey2020",
      "controller": "did:web:super-intelligent.ai",
      "publicKeyJwk": {
        "kty": "OKP",
        "crv": "Ed25519",
        "x": "[LOCALLY_GENERATED_PUBLIC_KEY_2]"
      }
    }
  ],
  "authentication": [
    "did:web:super-intelligent.ai#russell-wright",
    "did:web:super-intelligent.ai#kalyn-wright"
  ],
  "assertionMethod": [
    "did:web:super-intelligent.ai#russell-wright",
    "did:web:super-intelligent.ai#kalyn-wright"
  ],
  "service": [
    {
      "id": "did:web:super-intelligent.ai#website",
      "type": "LinkedDomains",
      "serviceEndpoint": "https://super-intelligent.ai"
    },
    {
      "id": "did:web:super-intelligent.ai#notary-log",
      "type": "VerificationService",
      "serviceEndpoint": "https://super-intelligent.ai/notary-log"
    },
    {
      "id": "did:web:super-intelligent.ai#membership",
      "type": "LinkedDomains",
      "serviceEndpoint": "https://members.super-intelligent.ai"
    }
  ],
  "alsoKnownAs": [
    "https://www.google.com/search?kgmid=/m/04fnrwr",
    "https://www.google.com/search?kgmid=/m/04fnrwk",
    "https://www.google.com/search?kgmid=/m/01261hpq"
  ]
}

Symmetric Verification Pair: Both Russell and Kalyn have verification methods for cross-attestation.
KGMID Integration: The alsoKnownAs field links to all three legacy Machine IDs.

Implementation Checklist

DEPLOYMENT SEQUENCE

1. Generate Keys: Create Ed25519 key pair on LOCAL hardware using ssh-keygen -t ed25519

2. Deploy DID: Upload did.json to /.well-known/ on SSL-secured server

3. Configure Email: Activate DKIM (2048-bit) in Google Workspace for institutional signing

4. Inject Schema: Add master JSON-LD block to site's <head>

5. Verify Resolution: Test at https://dev.uniresolver.io/

6. Validate Schema: Test JSON-LD at https://validator.schema.org/

7. Build Notary Log: Deploy /notary-log/ with entry schema

8. Issue First VC: Create and sign first Verifiable Credential

Verification Tools

Purpose	Tool	URL
DID Resolution	Universal Resolver	`dev.uniresolver.io`
JSON-LD Validation	Schema.org Validator	`validator.schema.org`
Rich Results Test	Google Search Console	`search.google.com/test/rich-results`
DKIM Verification	MXToolbox	`mxtoolbox.com/dkim.aspx`
SPF/DMARC Check	DMARCian	`dmarcian.com/dmarc-inspector/`