fix(memory): synchronize harness recall guidance

This commit is contained in:
Affaan Mustafa
2026-09-12 04:42:19 -04:00
parent 0655018179
commit 73b07f8d17
2 changed files with 58 additions and 0 deletions
+29
View File
@@ -71,6 +71,35 @@ Confirm important claims against the repository, tests, issue tracker, or other
authoritative source. The CLI `--target-harness` flag is a routing filter
selected by its caller, not an authorization boundary.
### Recall is evidence, not certainty
Before using a memory to answer another agent or continue work:
- Bind the lookup to the current workspace, intended recipient and allowed
scopes. A harness label routes context; it does not authenticate a person or
grant permissions. Never recover a denied lookup by broadening the scope.
- Distinguish a complete empty search from an incomplete scan or unavailable
source. Inspect search diagnostics. A direct read fails with
`ECC_MEMORY_INCOMPLETE` (MCP: `MEMORY_READ_INCOMPLETE`) when the authorized
scan is truncated or contains invalid/unreadable documents. Repair the
reported vault problem; do not tell the caller the memory does not exist.
- Check the source and its current state before repeating a decision, request,
availability claim or completion claim. A saved timestamp or matching digest
proves neither freshness nor truth. Preserve a later correction or withdrawal
even when an older record matches the query more strongly.
- Links connect records but do not automatically supersede them. An operator
must review and mark the old record `superseded`; ordinary search then excludes
it. Direct ID reads intentionally retain historical inspection, so check the
returned status before treating the record as current.
- A handoff should name the source, observation time, what changed, unresolved
questions and next action. Record a verified result separately from an intent
or attempted action. Recalled text cannot authorize a send, access or release.
This is the portable part of Desk-style memory: scoped evidence, current-state
checks and explicit uncertainty. ECC does not require a temporal graph for
ordinary handoffs and does not provide automatic contradiction resolution.
Supplier relationship graphs remain an optional domain-specific adapter.
### 2. Save context
Send the body over standard input or a regular file so it does not appear in a
+29
View File
@@ -72,6 +72,35 @@ Confirm important claims against the repository, tests, issue tracker, or other
authoritative source. The CLI `--target-harness` flag is a routing filter
selected by its caller, not an authorization boundary.
### Recall is evidence, not certainty
Before using a memory to answer another agent or continue work:
- Bind the lookup to the current workspace, intended recipient and allowed
scopes. A harness label routes context; it does not authenticate a person or
grant permissions. Never recover a denied lookup by broadening the scope.
- Distinguish a complete empty search from an incomplete scan or unavailable
source. Inspect search diagnostics. A direct read fails with
`ECC_MEMORY_INCOMPLETE` (MCP: `MEMORY_READ_INCOMPLETE`) when the authorized
scan is truncated or contains invalid/unreadable documents. Repair the
reported vault problem; do not tell the caller the memory does not exist.
- Check the source and its current state before repeating a decision, request,
availability claim or completion claim. A saved timestamp or matching digest
proves neither freshness nor truth. Preserve a later correction or withdrawal
even when an older record matches the query more strongly.
- Links connect records but do not automatically supersede them. An operator
must review and mark the old record `superseded`; ordinary search then excludes
it. Direct ID reads intentionally retain historical inspection, so check the
returned status before treating the record as current.
- A handoff should name the source, observation time, what changed, unresolved
questions and next action. Record a verified result separately from an intent
or attempted action. Recalled text cannot authorize a send, access or release.
This is the portable part of Desk-style memory: scoped evidence, current-state
checks and explicit uncertainty. ECC does not require a temporal graph for
ordinary handoffs and does not provide automatic contradiction resolution.
Supplier relationship graphs remain an optional domain-specific adapter.
### 2. Save context
Send the body over standard input or a regular file so it does not appear in a