The why beneath the code

Dates are UTC at rest, viewer-local at render

The canonical spec lives in the ai-labs parent, not here

This repo's context-v/ holds implementation-local docs only. The spec of record — contract, session model, schema, increments — is ai-labs/context-v/specs/Id-Didi-Sh-Identity-Service.md. Read it before changing anything load-bearing.

• Reminder
• Id-Didi-Sh
• Context-Vigilance

What Corpora-Builder Needs From didi.sh — the primitives list, handed over early

corpora-builder wants workspace identity from didi.sh. Two gaps: workspaces aren't a thing here yet, and a CLI has nowhere to put a cookie.

• Exploration
• Id-Didi-Sh
• Corpora-Builder
• Identity
• Workspaces
• Consumer-Requirements

Serving Secrets Server-Side as an MCP Capability Plane

Implementation-local notes on a remote MCP endpoint that holds credentials server-side and hands collaborators capabilities, not secrets.

• Exploration
• Id-Didi-Sh
• Secrets-Management
• MCP
• Capability-Plane
• Elixir
• Implementation-Local

Claude connectors need didi.sh to be an OAuth server

didi.sh knows who a person is. It can't yet tell Claude so, and MemoPop's connector is the first product waiting on that.

• Issue-Resolution
• OAuth
• Model-Context-Protocol
• Claude-Connector
• MemoPop
• Id-Didi-Sh

OAuth Authorization Server for Claude Connectors

Discovery, authorize, token, refresh, and client registration on id.didi.sh, so Claude can sign a partner into MemoPop with one magic link.

• Plan
• Id-Didi-Sh
• OAuth
• Claude-Connector
• Elixir