SymID

User-owned portable cognitive identity and permission routing.

PROTOTYPEIdentity / permissions

The Problem

AI systems lack portable, user-controlled identity that carries operating principles, communication preferences, active projects, permission rules, memory-store pointers, and activation profiles across sessions and platforms.

The Approach

SymID acts as a keychain and routing map—carrying user identity, operating principles, communication preferences, active projects, permission rules, memory-store pointers, and activation profile. A local-first companion extension stores identity packets and performs handshake/disclosure with compatibility evaluation. SessionGlyph carries the work; SymID carries the identity.

What Exists Today

  • ✓Protocol specification complete (v0.1 / v0.3.2)
  • ✓Local-first companion extension prototype stores identity packets
  • ✓Handshake and disclosure protocol defined
  • ✓Compatibility evaluation and scope clarification specified
  • ✓Automation plan documented

//What It Does Not Prove

What this project does not prove.

  • ✗Local-first prototype only
  • ✗Client-side encrypted synchronization not built
  • ✗No deployment or independent audit
  • ✗Cross-platform integration not demonstrated

Evidence

Portable cognitive identity protocol and local-first companion extension (handshake, disclosure, compatibility evaluation)

symid

PROTOTYPE
Artifact: symid-companion-extension
Version: v0.1
Environment: Local development (unpacked extension)
Date: 2026-08

Result:

Protocol specified (v0.1 / v0.3.2). Companion extension prototype stores identity packets locally and implements handshake/disclosure with compatibility evaluation.

//Verification Boundary

Local-first prototype only. Client-side encrypted synchronization not built. No deployment or independent audit. Cross-platform integration not demonstrated.

Source Artifacts

  • 📄SymID / SessionGlyph Automation Plan
  • 📄symid-companion-extension (local-first, v0.1)
  • 📄SymID white papers