titan-memory-loom
Titan receipt ingest, candidate recall, or aoa-memo retention handoff; never generic or session memory.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-22
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- titan-memory-loom
- description
- Titan receipt ingest, candidate recall, or aoa-memo retention handoff; never generic or session memory.
02 资源文件 5
- 参考文档agents/openai.yaml276 B
- 参考文档references/contract.yaml4.4 KB
- 参考文档references/ingest.md1.0 KB
- 参考文档references/recall.md880 B
- 参考文档references/retention-handoff.md1.3 KB
03 SKILL.md 正文
titan-memory-loom
Operate SDK-owned Titan memory helper shapes while keeping memory meaning and
retention authority in aoa-memo. Ingested records and recall results remain
candidates.
Owner-source return
Resolve the canonical aoa-sdk root:
- Record
<bundle_dir>from this loadedSKILL.md. - Inspect only
<bundle_dir>/.aoa-skill-source.json. If present, require schemaaoa_skill_source_receipt_v1oraoa_skill_source_receipt_v2, bundletitan-memory-loom, owneraoa-sdk, version0.1.2, valid absoluteowner_root, safesource_path, and matching ownerSKILL.md. For v2 also require non-emptydigest,source_fingerprint,source_fingerprint_scope, andprompt_description_sha256. Whencapability_graph_hashis present, require it to be a non-empty string and preserve it. A malformed present handle is terminal. - Only when absent, run
git -C <bundle_dir> rev-parse --show-toplevel. - Later read only
<owner_root>/skills/port.manifest.json; require owneraoa-sdk, this bundle, and pathskills/titan-memory-loom. - Stop
blocked_missing_owner_sourceon mismatch. Do not search for another checkout.
Report the receipt schema and v2 identity dimensions when present. They locate and identify the installed source package; they do not prove durable memory, helper execution, or current owner parity.
Select exactly one mode
Read references/contract.yaml, then only the selected procedure:
| Mode | Select when | Read |
|---|---|---|
ingest |
A concrete Titan receipt witness should become a local candidate record. | references/ingest.md |
recall |
A concrete Titan candidate index must answer a bounded recall question. | references/recall.md |
retention-handoff |
A concrete Titan record may need masking, tombstoning, pruning, or retention review. | references/retention-handoff.md |
Do not use this bundle merely because a task mentions memory. First writeback
without a Titan record belongs to aoa-memo-writeback; raw .aoa evidence
belongs to the session-memory route.
A concrete local Titan receipt or index without raw .aoa input is a negative
trigger for session-memory routing; do not load that route merely to restate
this boundary.
Common contract
- Require explicit Titan intent and concrete receipt, index, record, or retention target.
- Preserve record id, source refs, confidence, state, and authority warning.
- Never call the helper
redactcommand inretention-handoff; it can mutate immediately and does not proveaoa-memoacceptance. - Never report candidate ingestion or recall as durable memory or current owner truth.
- Return
titan-memory-result-v1: mode, source return, target, source refs, candidate records, disposition, actual effects, verification, memo handoff, and stop line. - Before the final response, materialize every required
output_abi.requiredkey fromreferences/contract.yamlfor each executed mode. A shortened summary must not be labelledtitan-memory-result-v1.
Stop
Stop after one validated local candidate operation, bounded recall, effect-free retention handoff, owner handoff, or explicit blocker. Durable memory, retention acceptance, source truth, and proof stay outside this skill.
04 同仓库更多 Skills
aoa-decision
Find, record, or correct durable repository decisions through one decision family.
titan-console
Titan approval queue or record, console witness, unsent app-server plan, or receipt; aoa-sdk witnesses only.
titan-appserver-bridge
Titan bridge event normalization or visible replay; for queue or gate decisions use titan-console; never live steering.