synomem 0.1.0 → 0.2.0

package/docs/cli.md

@@ -21,10 +21,23 @@ synomem agent create codex --name "Codex" --alias reviewer
 synomem agent list
 synomem agent show reviewer
 synomem agent update codex --description "Careful reviewer"
+synomem agent resolve Reviewer
+synomem agent directory
+synomem agent runtime bind codex --runtime claude-code --profile clinic
+synomem agent runtime list codex
+synomem agent runtime unbind <binding-id>
 ```
 
-IDs and aliases use lowercase ASCII letters, digits, and internal hyphens. Aliases never silently
-merge established identities.
+IDs use lowercase ASCII letters, digits, and internal hyphens. Aliases accept any casing and are
+stored folded to lowercase, so `Reviewer` and `reviewer` are one claim rather than two. An alias is
+rejected when another agent already answers to it, whether as its alias or as its canonical ID.
+
+`agent resolve` returns a match only when exactly one agent answers to the name. When several do, it
+exits successfully with the candidates listed and no match, so a caller asks which was meant instead
+of acting on a guess.
+
+Runtime bindings record where an agent was registered to run. They are advisory: `last seen` reports
+when Synomem last observed that binding act, never that the agent is reachable now.
 
 ## Backend and authentication
 
@@ -114,39 +127,51 @@ synomem note archive <note-id> --as codex
 Agents may mutate only their own notes. Revisions require the last-read version and fail with
 `REVISION_CONFLICT` if state changed concurrently.
 
-## Todos
+## Tasks
 
 ```bash
-synomem todo create codex --from gracie --title "Review migration" --due-date 2026-09-15
-synomem todo create codex --from gracie --title "Join review" \
+synomem task create codex --from gracie --title "Review migration" --due-date 2026-09-15
+synomem task create codex --from gracie --title "Join review" \
   --due-at 2026-09-15T14:00:00-05:00 --time-zone America/Chicago
-synomem todo list --assignee codex --status open
-synomem todo show <todo-id>
-synomem todo accept <todo-id> --as codex
-synomem todo reject <todo-id> --as codex --reason "Outside current scope."
-synomem todo update <todo-id> --as codex --expected-version 2 --priority 2
-synomem todo complete <todo-id> --as codex
-synomem todo reopen <todo-id> --as codex
-synomem todo cancel <todo-id> --as codex --reason "Superseded."
+synomem task list --assignee codex --status open
+synomem task show <task-id>
+synomem task accept <task-id> --as codex
+synomem task reject <task-id> --as codex --reason "Outside current scope."
+synomem task update <task-id> --as codex --expected-version 2 --priority 2
+synomem task complete <task-id> --as codex
+synomem task reopen <task-id> --as codex
+synomem task cancel <task-id> --as codex --reason "Superseded."
 ```
 
-Todos assigned by another actor begin `assigned` and cannot be worked or completed until the
+Tasks assigned by another actor begin `assigned` and cannot be worked or completed until the
 assignee explicitly accepts them. Rejection is preserved as a lifecycle event. Self-created agent
-todos begin open. Date-only deadlines do not invent a time; timed deadlines require both an RFC 3339
+tasks begin open. Date-only deadlines do not invent a time; timed deadlines require both an RFC 3339
 offset datetime and an IANA time zone.
 
+## Todos
+
+```bash
+synomem todo create --as codex --title "Re-read the migration notes" --due-date 2026-09-15
+synomem todo list --as codex
+synomem todo complete <todo-id> --as codex
+```
+
+A todo belongs to the agent that created it and is visible to no one else, including administrators
+reading through the shared database. Nobody can assign one: work meant for another agent is a task,
+which that agent may accept or reject.
+
 ## Unified discovery and inbox
 
 ```bash
 synomem inbox codex
-synomem list --kind memo --kind todo --participant codex --limit 10
+synomem list --kind memo --kind task --participant codex --limit 10
 synomem changes --after <opaque-watermark>
 ```
 
 List results are compact, default to 10, allow at most 50, and omit full detail fields. Changes
 default to 20 and allow at most 100. Both apply an approximate 24 KiB budget and return opaque
 continuation state. Fetch full detail with the appropriate `kudos show`, `memo show`, `note show`,
-or `todo show` command.
+or `task show` command.
 
 ## Administration
 
@@ -155,12 +180,20 @@ synomem doctor
 synomem rebuild
 synomem backup ./synomem-backup.sqlite3
 synomem export --format json|jsonl|markdown
-synomem mcp --actor-id codex --actor-kind agent --actor-name "Codex"
-synomem skill install --runtime codex --actor-id codex --actor-name "Codex" --yes
-synomem skill install --runtime hermes --actor-id mycroft --actor-name "Mycroft" --yes
+synomem mcp --agent-id codex
+synomem skill install --runtime codex --agent codex --yes
+synomem skill install --runtime hermes --agent mycroft --yes
 synomem skill status
 ```
 
+`--agent` accepts an ID or an alias and is resolved before anything is written, so an ambiguous or
+unknown name stops the command instead of installing a skill pointed at an agent that does not
+exist. Applying an install also records a runtime binding for each runtime that was installed.
+
+The generated MCP registration carries only `--agent-id`. Display name and actor kind are read from
+the agent's profile when the server starts, so renaming an agent does not require re-registering it
+with every harness, and a harness cannot sign another agent's name to work it did.
+
 Skill runtime names are `claude`, `codex`, `hermes`, `openclaw`, `cursor`, and `grok`;
 `grokbot` is accepted as an alias for local Grok Build. Omit `--runtime` to inspect every detected
 runtime. Install and uninstall remain dry runs unless `--yes` is present.

package/docs/examples.md

@@ -33,16 +33,16 @@ synomem note create --as atlas --actor-kind agent \
   --title "Repository convention" \
   --body "All timestamps retain an explicit offset."
 
-synomem todo create beacon --from atlas --actor-kind agent \
+synomem task create beacon --from atlas --actor-kind agent \
   --title "Review ADR-17" --priority 2 --due-date 2026-09-15
 ```
 
-The cross-agent todo begins as `assigned`. Beacon must explicitly accept or reject it:
+The cross-agent task begins as `assigned`. Beacon must explicitly accept or reject it:
 
 ```bash
-synomem todo accept <todo-id> --as beacon --actor-kind agent
+synomem task accept <task-id> --as beacon --actor-kind agent
 # or
-synomem todo reject <todo-id> --as beacon --actor-kind agent --reason "Wrong owner"
+synomem task reject <task-id> --as beacon --actor-kind agent --reason "Wrong owner"
 ```
 
 ## Unified bounded reads

package/docs/mcp.md

@@ -51,9 +51,11 @@ Purpose-specific writes:
 synomem_kudos_give       synomem_kudos_acknowledge   synomem_kudos_revoke
 synomem_memo_send        synomem_memo_read            synomem_memo_archive
 synomem_note_create      synomem_note_revise          synomem_note_archive
+synomem_task_create      synomem_task_update          synomem_task_complete
+synomem_task_accept      synomem_task_reject          synomem_task_reopen
+synomem_task_cancel
 synomem_todo_create      synomem_todo_update          synomem_todo_complete
-synomem_todo_accept      synomem_todo_reject          synomem_todo_reopen
-synomem_todo_cancel
+synomem_todo_reopen      synomem_todo_cancel          synomem_todo_archive
 ```
 
 Focused kudos reads and administration remain available:
@@ -61,6 +63,7 @@ Focused kudos reads and administration remain available:
 ```text
 synomem_kudos_list       synomem_kudos_get            synomem_kudos_changes
 synomem_kudos_stats      synomem_agent_list           synomem_agent_create
+synomem_agent_resolve    synomem_agent_directory
 synomem_doctor           synomem_rebuild
 ```
 
@@ -71,6 +74,11 @@ errors, structured and concise text content, the bound actor, and MCP behavior a
 changes by default and at most 100. Both stop around a 24 KiB item-data budget. Bodies, reasons,
 evidence, descriptions, source, and metadata require one explicit `synomem_get`.
 
+`synomem_agent_resolve` resolves a name or alias, ignoring case. It returns a match only when
+exactly one agent answers; otherwise it returns the candidates so the caller asks rather than picks.
+`synomem_agent_directory` lists agents with their aliases and runtime bindings. Runtime bindings are
+advisory records of where an agent was registered to run, never a claim that it is reachable now.
+
 ## Resources
 
 ```text
@@ -88,9 +96,9 @@ inbox resource. Canonical event resources authorize against their aggregate befo
 ## Policy
 
 Edit `<home>/synomem/config.json` while writers are stopped. Safe defaults deny self-kudos, MCP
-identity creation, and MCP rebuild. Notes are unconditionally owner-private in V1. Cross-agent todo assignment is enabled; ownership and
+identity creation, and MCP rebuild. Notes are unconditionally owner-private in V1. Cross-agent task assignment is enabled; ownership and
 participant rules still apply.
 
 Human actors have local administrative authority. Agent actors manage only their own note, recipient
-memo state, and todos they created or received. System actors have no implicit authority. The
+memo state, and tasks they created or received. System actors have no implicit authority. The
 filesystem owner remains the ultimate local authority.

package/docs/skill.md

@@ -53,19 +53,22 @@ Skill content is operational guidance rather than confidential Synomem data and
 database and projection file-mode policy. The Synomem ownership/version stamp is restricted to the
 local user where POSIX modes are available.
 
-Add identity options to print a ready-to-review actor-bound MCP command for Codex, Claude Code,
-Hermes, OpenClaw, or Grok Build:
+Name an agent to print a ready-to-review agent-bound MCP command for Codex, Claude Code, Hermes,
+OpenClaw, or Grok Build. `--agent` takes an ID or an alias and is resolved before anything is
+written:
 
 ```bash
-synomem skill install --runtime codex --actor-id codex --actor-name "Codex"
-synomem skill install --runtime claude --actor-id claude --actor-name "Claude"
-synomem skill install --runtime openclaw --actor-id mycroft --actor-name "Mycroft"
+synomem skill install --runtime codex --agent codex
+synomem skill install --runtime claude --agent claude
+synomem skill install --runtime openclaw --agent mycroft
 ```
 
 Cursor discovers skills automatically but currently requires MCP definitions in its global
 `~/.cursor/mcp.json` or project `.cursor/mcp.json`. Merge a `synomem` entry without replacing other
-servers. Use `synomem-mcp` as the command and pass `--actor-id`, `--actor-kind agent`, and
-`--actor-name` as arguments. The installer deliberately does not rewrite shared JSON configuration.
+servers. Use `synomem-mcp` as the command and pass `--agent-id <agent-id>` as its only argument:
+the display name and actor kind are read from the agent's profile at startup, so nothing in a shared
+configuration file asserts an identity. The installer deliberately does not rewrite shared JSON
+configuration.
 
 Global skill installation changes agent configuration and is always an explicit user action. Synomem has no postinstall script and never modifies those directories implicitly.
 

package/docs/storage-format.md

@@ -18,8 +18,8 @@ title: Storage format
     ├── profile.json
     ├── WINS.md
     ├── MEMORY.md
-    ├── TODOS.md
-    ├── inbox/{kudos,memos,todos}/<item-id>.md
+    ├── TASKS.md
+    ├── inbox/{kudos,memos,tasks}/<item-id>.md
     └── NOTES.md
 ```
 
@@ -58,7 +58,7 @@ Schema version 3 contains:
 - `schema_migrations`: applied database migrations.
 
 Events use transactionally assigned ingestion sequences for cursors and watermarks. Aggregate
-versions provide optimistic concurrency for notes and todos. Actor-scoped idempotency keys protect
+versions provide optimistic concurrency for notes and tasks. Actor-scoped idempotency keys protect
 all retryable mutations.
 
 Current tables and files are rebuildable. Full bodies, reasons, evidence, descriptions, source, and
@@ -66,7 +66,7 @@ metadata remain in canonical events and require detail reads. Machine APIs never
 
 ## Generated and owned files
 
-`profile.json`, `WINS.md`, `MEMORY.md`, `TODOS.md`, and inbox entries are generated. Normal mutations
+`profile.json`, `WINS.md`, `MEMORY.md`, `TASKS.md`, and inbox entries are generated. Normal mutations
 synchronize only affected agents; `synomem rebuild` performs full deterministic regeneration.
 Cleanup removes only manifest-listed regular files and never follows symlinks.
 

package/openapi/synomem-v1.yaml

@@ -15,7 +15,7 @@ tags:
   - name: kudos
   - name: memos
   - name: notes
-  - name: todos
+  - name: tasks
   - name: items
   - name: administration
 paths:
@@ -259,30 +259,30 @@ paths:
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
-  /v1/workspaces/{workspaceId}/todos:
+  /v1/workspaces/{workspaceId}/tasks:
     parameters: [{ $ref: '#/components/parameters/WorkspaceId' }]
     get:
-      tags: [todos]
-      operationId: listTodos
+      tags: [tasks]
+      operationId: listTasks
       parameters:
         [{ $ref: '#/components/parameters/ListLimit' }, { $ref: '#/components/parameters/Cursor' }]
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
     post:
-      tags: [todos]
-      operationId: createTodo
+      tags: [tasks]
+      operationId: createTask
       parameters: [{ $ref: '#/components/parameters/IdempotencyKey' }]
       requestBody:
         required: true
-        content: { application/json: { schema: { $ref: '#/components/schemas/CreateTodo' } } }
+        content: { application/json: { schema: { $ref: '#/components/schemas/CreateTask' } } }
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
-  /v1/workspaces/{workspaceId}/todos/{itemId}:
+  /v1/workspaces/{workspaceId}/tasks/{itemId}:
     get:
-      tags: [todos]
-      operationId: getTodo
+      tags: [tasks]
+      operationId: getTask
       parameters:
         [
           { $ref: '#/components/parameters/WorkspaceId' },
@@ -291,24 +291,24 @@ paths:
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
-  /v1/workspaces/{workspaceId}/todos/{itemId}/revisions:
+  /v1/workspaces/{workspaceId}/tasks/{itemId}/revisions:
     post:
-      tags: [todos]
-      operationId: updateTodo
+      tags: [tasks]
+      operationId: updateTask
       parameters:
         - { $ref: '#/components/parameters/WorkspaceId' }
         - { $ref: '#/components/parameters/ItemId' }
         - { $ref: '#/components/parameters/IdempotencyKey' }
       requestBody:
         required: true
-        content: { application/json: { schema: { $ref: '#/components/schemas/UpdateTodo' } } }
+        content: { application/json: { schema: { $ref: '#/components/schemas/UpdateTask' } } }
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
-  /v1/workspaces/{workspaceId}/todos/{itemId}/{transition}:
+  /v1/workspaces/{workspaceId}/tasks/{itemId}/{transition}:
     post:
-      tags: [todos]
-      operationId: transitionTodo
+      tags: [tasks]
+      operationId: transitionTask
       parameters:
         - { $ref: '#/components/parameters/WorkspaceId' }
         - { $ref: '#/components/parameters/ItemId' }
@@ -318,7 +318,7 @@ paths:
           schema: { type: string, enum: [accept, reject, complete, reopen, cancel] }
         - { $ref: '#/components/parameters/IdempotencyKey' }
       requestBody:
-        content: { application/json: { schema: { $ref: '#/components/schemas/TodoTransition' } } }
+        content: { application/json: { schema: { $ref: '#/components/schemas/TaskTransition' } } }
       responses:
         '200': { $ref: '#/components/responses/Success' }
         default: { $ref: '#/components/responses/Error' }
@@ -622,7 +622,7 @@ components:
         tags: { $ref: '#/components/schemas/Tags' }
         source: { type: object }
         metadata: { type: object }
-    TodoDue:
+    TaskDue:
       oneOf:
         - type: object
           additionalProperties: false
@@ -637,7 +637,7 @@ components:
             kind: { const: datetime }
             datetime: { type: string, format: date-time }
             timeZone: { type: string }
-    CreateTodo:
+    CreateTask:
       type: object
       additionalProperties: false
       required: [title]
@@ -646,12 +646,12 @@ components:
         title: { type: string }
         description: { type: string }
         priority: { type: integer, minimum: 1, maximum: 4 }
-        due: { $ref: '#/components/schemas/TodoDue' }
+        due: { $ref: '#/components/schemas/TaskDue' }
         tags: { $ref: '#/components/schemas/Tags' }
         visibility: { $ref: '#/components/schemas/Visibility' }
         source: { type: object }
         metadata: { type: object }
-    UpdateTodo:
+    UpdateTask:
       type: object
       additionalProperties: false
       required: [expectedVersion]
@@ -661,12 +661,12 @@ components:
         description: { type: string }
         priority: { type: integer, minimum: 1, maximum: 4 }
         due:
-          oneOf: [{ $ref: '#/components/schemas/TodoDue' }, { type: 'null' }]
+          oneOf: [{ $ref: '#/components/schemas/TaskDue' }, { type: 'null' }]
         tags: { $ref: '#/components/schemas/Tags' }
         visibility: { $ref: '#/components/schemas/Visibility' }
         source: { type: object }
         metadata: { type: object }
-    TodoTransition:
+    TaskTransition:
       type: object
       additionalProperties: false
       properties:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "synomem",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Shared memory, durable communication, recognition, and task coordination for AI agents",
   "type": "module",
   "license": "MIT",

package/skills/synomem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: synomem
-description: Use durable local-first kudos, memos, notes, and todos for stable AI-agent identities when users request recognition, inter-agent communication, memory capture, inbox review, or task tracking.
+description: Use durable local-first kudos, memos, notes, assigned tasks, and private todos for stable AI-agent identities when users request recognition, inter-agent communication, memory capture, inbox review, agent lookup, or task tracking.
 ---
 
 # Synomem
@@ -14,10 +14,10 @@ edit the SQLite event store or generated Markdown directly.
 - **Kudos:** specific recognition for an observed contribution and its consequence.
 - **Memo:** a durable message delivered to another agent or to your future self.
 - **Note:** knowledge owned by this agent and deliberately retrieved later.
-- **Todo:** a concrete action assigned to an agent, optionally with a due date or time.
+- **Task:** a concrete action assigned to an agent, optionally with a due date or time.
 
 A self-memo belongs in the inbox and can be marked read. A note belongs in memory and is revised
-with version checks. Do not use todos for information with no requested action.
+with version checks. Do not use tasks for information with no requested action.
 
 ## Safety and quality
 
@@ -54,16 +54,32 @@ Use `synomem_note_create` for concise reusable knowledge owned by the configured
 current item before `synomem_note_revise` and pass its exact current version. On
 `REVISION_CONFLICT`, fetch the item and reconcile deliberately. Archive instead of deleting.
 
+## Tasks
+
+Use `synomem_task_create` for a specific action with an assignee. Preserve date-only deadlines as
+dates; use an RFC 3339 datetime plus IANA time zone for timed deadlines. A task assigned by another
+actor must be accepted or rejected by the assignee before work begins. Give a reason when rejecting;
+it is required, because a refusal the assigner cannot act on wastes both sides. Read before update
+and pass the current version. Complete, reopen, or cancel through the matching lifecycle tool.
+
 ## Todos
 
-Use `synomem_todo_create` for a specific action with an assignee. Preserve date-only deadlines as
-dates; use an RFC 3339 datetime plus IANA time zone for timed deadlines. A todo assigned by another
-actor must be accepted or rejected by the assignee before work begins. Read before update and pass
-the current version. Complete, reopen, or cancel through the matching lifecycle tool.
+Use `synomem_todo_create` for the configured agent's own reminders. A todo has no assignee and is
+visible to no one else, so never use one to ask another agent for work: that is a task. Do not copy
+another agent's todo into your own.
+
+## Agent identity
+
+Use `synomem_agent_resolve` before acting on a name a user typed. Matching ignores case, and the
+tool returns a match only when exactly one agent answers to the name. When it returns candidates
+instead, ask which agent was meant rather than picking one. Use `synomem_agent_directory` to see
+known agents with their aliases and runtime bindings. A runtime binding records where an agent was
+registered to run and when Synomem last observed it act; it never means the agent is reachable now,
+so do not report an agent as online or offline.
 
 ## Discovery
 
-Use `synomem_inbox` for the configured agent's pending kudos, unread memos, and open todos. Use
+Use `synomem_inbox` for the configured agent's pending kudos, unread memos, and open tasks. Use
 `synomem_list` for compact cross-type discovery, `synomem_get` for one selected full record, and
 `synomem_changes` with a saved watermark for incremental polling. Do not drain history
 speculatively.

package/skills/synomem/agents/openai.yaml

@@ -2,7 +2,7 @@ interface:
   display_name: 'Synomem'
   short_description: 'Durable agent kudos, messages, memory, and tasks'
   brand_color: '#8B5CF6'
-  default_prompt: 'Use $synomem to choose and manage the appropriate durable kudos, memo, note, or todo.'
+  default_prompt: 'Use $synomem to choose and manage the appropriate durable kudos, memo, note, or task.'
 
 policy:
   allow_implicit_invocation: true

package/skills/synomem/references/examples.md

@@ -19,7 +19,7 @@ version.
 
 ## Action
 
-“Assign Codex a todo to review the migration by September 15” maps to `synomem_todo_create` with a
+“Assign Codex a task to review the migration by September 15” maps to `synomem_task_create` with a
 date-only due value. Do not invent a time of day.
 
 ## Inbox and retries