You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`standard`| No automatic expiry | Active until explicitly expired, redacted, or deleted. |
394
+
|`short_lived`| 30 days from `created_at`| Automatically excluded from hosted loads after the default window. |
395
+
|`security`| 90 days from `created_at`| Used for redaction stubs and security-sensitive audit records. |
396
+
|`legal_hold`| No automatic expiry | Never auto-expires; `memory expire` and `memory delete` require `--force`. |
397
+
387
398
Local mode tolerates missing metadata for backward compatibility. Hosted review
388
399
mode treats missing trust as `unknown`, ignores expired memory, and excludes
389
400
memory below the configured trust threshold. Tagged hosted memory is injected
@@ -402,6 +413,20 @@ conflict record is written for operator review instead of overwriting local
402
413
memory. Hosted team-memory sync also sends tenant, installation, repo, and
403
414
domain scope metadata so the server can authorize the full tuple.
404
415
416
+
### Memory lifecycle operator controls
417
+
418
+
Use `coven-code memory` to inspect and administer local and hosted memory
419
+
without exposing redacted or deleted content to the model.
420
+
421
+
| Command | Purpose |
422
+
|---------|---------|
423
+
|`coven-code memory list [--dir <path>] [--tenant <id>] [--repo <id>] [--domain <name>] [--json]`| List memory id, path, retention class, trust, created time, effective expiry, and status. With no `--dir`, scans the project auto-memory directory plus hosted scopes under the Coven Code config directory. |
424
+
|`coven-code memory expire <id-or-path> [--at YYYY-MM-DD] [--force]`| Set `expires_at` in frontmatter. Defaults to today and refuses `legal_hold` entries unless `--force` is present. |
425
+
|`coven-code memory redact <id-or-path> --reason <text>`| Replace the file with a redaction tombstone stub via `redact_memory_file`; the original body is removed. |
426
+
|`coven-code memory delete <id-or-path> --reason <text> [--force]`| Replace the file with a deletion tombstone stub. `legal_hold` entries require `--force`. |
427
+
|`coven-code memory delete --scope tenant=<t>,install=<i>,repo=<r>[,domain=<d>] --reason <text> [--force]`| Remove the hosted memory directory for a scoped tenant/installation/repo/domain. Scope deletion refuses legal-hold files unless forced. |
428
+
|`coven-code memory ledger [--dir <path>] [--json]`| Export tombstoned entries only: id, path, redacted/deleted timestamp, retention class, tombstone reason line, and provenance source. The ledger reads tombstone stubs and never includes original memory body content. |
429
+
405
430
### @include directives
406
431
407
432
AGENTS.md files support `@include` to pull in content from other files:
Copy file name to clipboardExpand all lines: docs/src/content/configuration.js
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,10 @@ export function render() {
92
92
}
93
93
}</code></pre>
94
94
95
+
<h2>Memory Retention</h2>
96
+
<p>AGENTS.md frontmatter supports lifecycle fields for hosted review memory. <code>expires_at</code> uses <code>YYYY-MM-DD</code> and always wins over retention defaults. <code>retention_class</code> can be <code>standard</code> (no automatic expiry), <code>short_lived</code> (30 days from <code>created_at</code>), <code>security</code> (90 days), or <code>legal_hold</code> (no automatic expiry and requires <code>--force</code> for operator expiry/deletion).</p>
97
+
<p>Operators can run <code>coven-code memory list</code>, <code>expire</code>, <code>redact</code>, <code>delete</code>, and <code>ledger --json</code>. Redaction and deletion write tombstone stubs; the audit ledger exports ids, timestamps, reasons, and provenance without original removed content.</p>
0 commit comments