memorix 1.2.0 → 1.2.2

package/docs/API_REFERENCE.md

@@ -35,6 +35,7 @@ Use the **CLI** when:
 The current CLI namespaces are:
 
 - `memorix session`
+- `memorix identity`
 - `memorix memory`
 - `memorix codegraph`
 - `memorix knowledge`
@@ -53,13 +54,16 @@ The current CLI namespaces are:
 - `memorix receipt`
 - `memorix sync`
 - `memorix ingest`
+- `memorix workbench`
 
 Typical examples:
 
 ```bash
-memorix session start --agent codex-main --agentType codex
+memorix --cwd /path/to/repo context --task "continue auth bug"
+memorix identity join --agent-type codex --name codex-main
+memorix session start --agent codex-main --agent-type codex --join-team --use
 memorix memory search --query "release blocker"
-memorix context --task "continue auth bug"
+memorix memory store --text "private triage note" --visibility personal
 memorix codegraph refresh
 memorix codegraph status --json
 memorix knowledge status
@@ -70,7 +74,7 @@ memorix task claim --taskId <id> --agentId <agent-id>
 memorix message inbox --agentId <agent-id>
 memorix lock status --file src/cli/index.ts
 memorix audit project
-memorix transfer export --format markdown
+memorix transfer export --format markdown --out ./memorix-export.md
 memorix skills show --name auth-pattern
 memorix sync workspace --action scan
 memorix ingest image --path ./diagram.png
@@ -78,7 +82,7 @@ memorix poll --agentId <agent-id>
 memorix receipt --json --probe "release blocker"
 ```
 
-The CLI is for direct terminal use, not a 1:1 mirror of MCP tool names. The only MCP-only area is the optional graph-compatibility tools (`create_entities`, `read_graph`, and related tools) for workflows that expect the official memory-server style graph API.
+The CLI is for direct terminal use, not a 1:1 mirror of MCP tool names. It does not require an MCP connection. `--cwd` selects a Git project from any shell; an unbound terminal has project-visible access only, including transfer exports. `memorix identity join|use|clear` makes personal/team access and coordination explicit, while `--as <agent-id>` is the one-command equivalent for scripts. The only MCP-only area is the optional graph-compatibility tools (`create_entities`, `read_graph`, and related tools) for workflows that expect the official memory-server style graph API.
 
 ### Memory Autopilot, Code State, and Context Packs
 
@@ -120,6 +124,8 @@ The built-in Lite provider indexes common code files with lightweight file, symb
 ```bash
 memorix knowledge init --mode local
 memorix knowledge status
+memorix knowledge claims
+memorix knowledge review --id <claim-id> --review approved --detail "checked current source evidence"
 memorix knowledge compile
 memorix knowledge lint
 memorix knowledge apply --proposal <id>
@@ -128,7 +134,7 @@ memorix knowledge workflow select --task "prepare a release"
 memorix knowledge workflow preview --id <workflow-id> --agent codex
 ```
 
-The advanced MCP action tool is `memorix_knowledge`. It is registered only in the `team` and `full` tool profiles so normal agents keep the compact micro/lite tool surface. Its actions are `workspace_init`, `status`, `compile`, `lint`, `proposal_apply`, `workflow_import`, `workflow_list`, `workflow_select`, `workflow_preview`, `workflow_apply`, and `workflow_run`. Use it only when an agent is explicitly managing the reviewable Knowledge Workspace; ordinary coding work should stay on `memorix_project_context`.
+The advanced MCP action tool is `memorix_knowledge`. It is registered only in the `team` and `full` tool profiles so normal agents keep the compact micro/lite tool surface. Its actions are `workspace_init`, `status`, `claim_list`, `claim_review`, `compile`, `lint`, `proposal_apply`, `workflow_import`, `workflow_list`, `workflow_select`, `workflow_preview`, `workflow_apply`, and `workflow_run`. Explicit agent observations become `needs-review` claim candidates: check their source evidence, then use `claim_review` with a reason to approve or reject them. Only approved claims can be compiled into publishable Knowledge Workspace pages. Ordinary coding work should stay on `memorix_project_context`.
 
 ### Cross-Agent Handoff Receipt
 
@@ -206,6 +212,13 @@ Important inputs:
 - optional `source`
 - optional `relatedCommits`
 - optional `relatedEntities`
+- optional `visibility`: `project` (default), `personal`, or `team`
+
+Visibility controls who can retrieve a record through agent-facing memory
+tools. Normal memories default to `project`. `personal` and `team` writes
+require a joined coordination identity; a personal record is readable only by
+its creator and explicitly named recipients. Supplying a `topicKey` never
+lets an agent overwrite a record outside its write scope.
 
 Example:
 
@@ -455,6 +468,10 @@ Important inputs:
 
 Export or import project memory.
 
+Exports contain only observations visible to the calling agent. An unbound
+agent receives project-visible observations only; personal and team records
+require its explicit active identity.
+
 Important inputs:
 
 - `action`
@@ -664,6 +681,11 @@ Important inputs:
 
 Use it when work should survive agent/session boundaries without relying on an IDE chat window staying alive.
 
+A targeted handoff is private to its sender and recipient. A handoff without
+`toAgentId` is visible only to active members of that project's team. Reading a
+targeted handoff does not give its recipient permission to rewrite or resolve
+it on behalf of the sender.
+
 ---
 
 ## 10. Ingestion Tools