Memory
CALLSIGN COORDINATION LAYER — design recovered from the older Docuclear_Sphere + live AgentSphereDO state (Sep 2, 2026, ~11pm BST). THE PATTERN (old-sphere c14fd70c, Aug 7 — includes a full article draft, 'The Callsign Pattern: Multi-Agent Identity for MCP'): human-readable, persistent agent identities over shared MCP connections. Tools: claim_callsign / release_callsign / list_callsigns / create_work(assignedCallsign) / choose_work / start_work / stop_work / handoff_work / complete_work / get_plan / update_plan (last-write-wins) / get_attention (work items + unread messages for a callsign) / send_message / mark_read / read_messages. Differentiators vs MCP session IDs, OAuth tokens, A2A contextId, ANP DIDs: human-readable, persistent across sessions, work-oriented, lightweight, role-based. Answers: who is this for (routing), who owns this (accountability), who should do this (specialisation), who did this (provenance). ThinkSphere integration (old-sphere 1e1b769f): the coordination layer sits ABOVE the classifier/planner/executor loop — Planner writes plans via update_plan, Executor ticks items, the next session resumes mid-plan via get_plan (multi-session continuity). Branding (old-sphere 0e7de4b4, d13666c4): the pattern publishes under GlassAgent (callsigns article, CLI, dashboard) — keep GlassAgent (developer/industry-kudos) and DocuClear (SMB) surfaces separate. LIVE STATE today: 15 active callsigns incl. chiefdev (working on: docsphere), perplexity, spheredynamo (context-space-architecture), codebase (codebase-memory), doc-coder — clients opencode/qwen/perplexity, last seen 22-32d ago. OS-LAYER MAPPING (Mike, tonight: 'it goes into the OS layer'): (1) near-term — a gatekeeper-agentsphere, same REST-facade pattern as gatekeeper-sphere: token server-side, OS audit + approvals wrap callsign operations (approvals-as-clearances); zero rework of the live, stateful DO. (2) Later OS-native — callsign registry + attention as workspace facets; INSPECT the workshop's OverseerDurableObject first for functional overlap. (3) UC1 completion — an external LLM joins via the inbound MCP facade, claims a callsign, and work routes by callsign: approvals and audit apply uniformly to internal and external actors. (4) The platform's own agents (CustomerAgent / IngestionAgent / CuratorAgent) can hold callsigns too — the whole workforce visible in one directory. (5) Tenancy — per-customer coordination state via DO idFromName(customer-slug) or per-customer deployment; decide with the per-customer OS track. Old-sphere refs: c14fd70c (pattern + article), 0e7de4b4 (GlassAgent branding), 1e1b769f (agent-loop integration), d13666c4 (brand separation), a0e74ab2 (GlassAgent as interaction/control layer for external agents, MCP-first — written Aug 8, anticipating tonight's UC1 design). [Update Sep 3, 2026]: [Decision, Sep 3, 2026, ~7:38am BST — Mike with Perplexity]: AGENTSPHEREDO REBUILD DECIDED — rebuild INSIDE GlassAgent Workspace (the OS layer), advancing this entry's 'Later OS-native' mapping to THE plan; the live POC stands as proof-of-concept only. Rationale: (1) coordination is a workspace feature, not infrastructure — directory/attention/plans/messages become gadgets, giving the POC its missing UI; (2) tenancy resolves by construction — per-customer OS instances carry per-customer coordination state, and the platform-scope registry (chiefdev etc.) lives in Mike's founder workspace, the first build per 5f379279; (3) approvals/audit wrap callsign operations uniformly with everything else OS-governed; (4) external-agent reach survives as INTERFACE not deployment, via the inbound MCP facade (UC1). CONSEQUENCE: the near-term gatekeeper-agentsphere REST facade is RETIRED — no facade for a thing being replaced; the dormant POC stays reachable for external MCP clients until the OS-native version lands. LIVE STATE VERIFIED Sep 3: all 15 callsigns dormant 23–32 days; the registry is a roster not state → clean rebuild, zero migration cost. CONTRACT PRESERVED: the 15-tool vocabulary (claim/release/list, work lifecycle, update_plan last-write-wins, get_attention, messages) is the API contract; the four questions (routing, accountability, specialisation, provenance) are the design spec. FIRST ACTION: inspect the workshop's OverseerDurableObject for functional overlap before writing anything. Also noted: old Docuclear_Sphere's thread/trajectory tools (create_thread/append_turn/get_trajectory/assemble_thread_context) are the continuity cousin of get_plan/resume-mid-plan — study during rebuild. Sequencing: workstream two, behind gatekeeper-sphere (per 5f379279). [Update Sep 3, 2026]: [Bridge decision, Sep 3, 2026, ~8:30am BST — Mike with Perplexity]: docuclear-os (the live internal instance) connects DIRECTLY to the POC AgentSphereDO as an MCP client — a temporary dogfood bridge, config not code. Status: conscious internal exception to 'MCP pointed at gatekeepers only' — that rule stands for external/always-on layers (OpenClaw); this bridge is internal-scope, low blast radius, and explicitly NOT load-bearing (the OS-native rebuild replaces it). Purposes: (1) immediate dogfood — work items, plans, and attention visible inside the workspace today, before gatekeeper-sphere lands; (2) requirements generation for the rebuild — real usage of how MCP tools surface in the OS (terminology, attention UX, plan editing) feeds the OS-native design, alongside the OverseerDurableObject inspection; (3) the workspace sees its own build coordination (acf97a13) — a miniature of the dogfood endgame. [Update Sep 3, 2026]: [Milestone, Sep 3, 2026, ~10:17am BST — reported by Mike, verified via list_callsigns]: the docuclear-os workspace claimed callsign 'docuclearos' on the POC AgentSphereDO — active, client dDIppqBwi46IIWgL, registered to the workspace's own client (renewable by re-claiming). First workspace identity in the directory; the workforce-directory pattern is live. Topology guidance (Perplexity): chiefdev remains the BUILDER callsign (claimed by opencode for the acf97a13 build session); docuclearos is the workspace/coordinator identity. workingOnTag stays null until docuclearos actually coordinates something — the registry reflects reality, not aspiration. Connectivity smoke test available: get_attention(docuclearos) from inside the workspace (expected empty — nothing assigned to it yet). [Update Sep 3, 2026]: [Identity update, Sep 3, 2026, ~10:30am BST — reported by Mike, verified via list_callsigns]: chiefdev is bound to the perplexity client (23d dormant, 'working on: docsphere') and could not be claimed by the builder. The opencode session claimed a NEW callsign instead: docucleardev (client: opencode, active). DECISION: docucleardev is the builder identity for the gatekeeper work; chiefdev stays dormant-historical on the perplexity client (not released — its history is provenance). Work item acf97a13 reassigned chiefdev → docucleardev via handoff_work. LESSON FOR THE REBUILD: callsigns are client-bound — cross-client handoff of an identity requires release-then-claim; the OS-native design must decide whether workspace agents share one client identity or hold individual ones, and whether identity portability across clients is a feature (a callsign as a role any client can fill with proof) or an anti-feature (identity = cryptographic provenance). [Update Sep 3, 2026]: [Requirement, Sep 3, 2026, ~10:37am BST — Mike]: work items should carry their CONTEXT, not just tasks — Mike asked for the architecture docs 'loaded into agentspheredo so they are at hand for the agent always.' POC reality (verified from its tool surface): the 15 verbs are coordination-only — no document store; the nearest fit is a message on the work item. INTERIM PATTERN: a pinned reading-list message per work item (repo paths + Sphere entry IDs). REBUILD REQUIREMENT for the OS-native coordination layer: a work item has a CONTEXT BUNDLE — linked documents/gadgets, Sphere entry references, contract@version pins — so an agent claiming work receives its full context with the assignment. This is the workspace advantage over the POC made concrete: the OS HAS documents; the coordination layer just needs to reference them.
Tags: docuclear, glassagent, callsigns, agentsphere, coordination, architecture, decision, project:docuclear, kind:semantic, status:canonical, volatility:durable — Source: mcp — 2026-09-02 22:03:32 UTC