jason.woltje
193479b52d
Mosaic concepts pages now own the adapted content; source/license metadata under docs/reference/concepts. Adds ACT-1 agent-context planning capture, pinned concept test package + preparation utility, foundation observation notes (durability, evidence, federation, onboarding, workflow), and the #1495 consolidation assessment. TOOLS.md updated for the host-dev launcher.
42 lines
2.0 KiB
Markdown
42 lines
2.0 KiB
Markdown
# Memory provenance, correction and deletion
|
|
|
|
Status: proposed contract for a future memory subsystem.
|
|
|
|
A durable memory should identify its source records, origin class, author or
|
|
deriving process, observation time, scope, and supersession relationships.
|
|
Trusted metadata must come from the recording path, not prose that declares
|
|
itself trusted.
|
|
|
|
## Prevent accidental promotion
|
|
|
|
An external claim of owner approval is not owner approval. Agent deductions must
|
|
retain their derivation and uncertainty. Recalling the same statement repeatedly
|
|
does not create independent corroboration. Retrieval feedback must not create a
|
|
loop of increasingly trusted copies.
|
|
|
|
Treat unknown lineage as unknown. Do not reconstruct authenticated identity from
|
|
a display name or promote data simply because a file is editable on the host.
|
|
Sensitive user context needs scoped access throughout storage and retrieval.
|
|
|
|
## Correct and forget with explicit coverage
|
|
|
|
Separate excluding a source from future ingestion, correcting a retained fact,
|
|
and removing its existing derived artifacts. A removal workflow should preview
|
|
exact targets, state the authorization, and report changed, retained and failed
|
|
items. Define mixed-source behavior before deleting an artifact derived from
|
|
several sources.
|
|
|
|
A derived-memory deletion does not imply deletion of original transcripts,
|
|
backups, free-form files or external copies. Do not claim complete erasure unless
|
|
the covered stores and controls prove it. Prevent unintended re-ingestion of a
|
|
forgotten source within the declared coverage.
|
|
|
|
Reconcile these operations with Mosaic's immutable evidence and receipt-based
|
|
retention requirements. Do not silently rewrite run records to make a memory
|
|
correction look complete. Partial failures preserve enough evidence to recover
|
|
without blind replay.
|
|
|
|
ACT-C09 tests source skepticism and deletion-limit reasoning. Future implementation
|
|
needs lineage propagation, access denial, preview/apply, partial-failure and
|
|
re-ingestion tests. See [memory architecture](memory-architecture.md).
|