Engram can watch Tightbeam's existing Codex and Claude transcripts. To show which Tightbeam agent, archetype, and delegation produced a code change, it needs the session mappings that Tightbeam already records.
Read-only recon Live 0.1.8 checked Main source checked
Current Tightbeam homes are per host and harness:
~/.tightbeam/homes/gibson/codex ~/.tightbeam/homes/gibson/claude
Multiple archetypes use these homes. Guidance and elected skills are applied per session. Creating one Engram index per archetype would duplicate storage and misrepresent this topology.
Tightbeam's append-only pointer history connects native harness sessions to the stable Tightbeam session key. I verified this join with a real Codex transcript and a real Claude transcript.
A directory, native session ID, archetype name, and Engram tape ID each describe a different thing. Keep those distinctions in the integration.
| User outcome | What is enough | Remaining work |
|---|---|---|
| Search code reads and edits; open surrounding conversations | Existing native adapters and explicit watch roots | Install the selected Engram release, validate actual transcript shapes, and backfill history. |
| See the responsible Tightbeam agent and archetype | A small metadata bridge | Export native-session mappings and enrich results. Engram currently returns tape IDs as its session IDs. |
| Follow one agent through restarts and harness changes | Existing Tightbeam pointer history plus integration | Join every recorded native segment to the stable agent key, including older segments. |
| Trace a work item or delegation through to an edit | Explicit causal-link integration | Use recorded assignments, turns, wakes, and dispatch relationships. Shared homes or similar text cannot establish the link. |
| Know the identity guidance used at a past moment | Historical evidence with a stated scope | A current identity stamp cannot prove what the model read during an earlier turn. Preserve unknowns. |
| Search across hosts | Local indexes and existing additional stores | Arrange immutable tape or consistent snapshot transport, tape availability, and freshness. Additional stores are not a remote-query protocol. |
Keep native transcript ingestion. Export a compact context manifest that relates the host, harness, native session ID, and Engram tape versions to the Tightbeam session key. Include assignment and dispatch references only where records establish them.
A companion tool can prove result enrichment first. A reusable integration should give Engram a supported context import/read interface and expose the mapping through a narrow Tightbeam export. It does not need a new transcript format or a new identity system.
This example is for Gibson and has not been installed. Each host needs its own actual base directory and configured name.
db: ~/.engram/tightbeam/index.sqlite
tapes_dir: ~/.engram/tightbeam/tapes
additional_stores: []
watch:
debounce_secs: 5
ingest_timeout_secs: 120
log: ~/.engram/tightbeam/watch.log
sources:
- path: ~/.tightbeam/homes/gibson/codex/sessions
pattern: "*.jsonl"
- path: ~/.tightbeam/homes/gibson/claude/projects
pattern: "*.jsonl"
The watcher handles new file events. It does not backfill existing history on startup, and it skips absent directories. Inventory archives and older home layouts explicitly. Keep generated tapes outside every watched root.
Engram's existing lineage mechanism needs the same UUID in both the sending tool call and receiving message. Tightbeam's stored IDs do not automatically create those markers. A small producer bridge could support future dispatches, but historical traffic needs explicit relationships from the retained records.
I recommend the metadata and causal-link route for complete attribution. A forward-only marker bridge remains a smaller optional integration. Agent ancestry and native harness subagents need separate treatment from an actual Tightbeam delegation.
I checked the live gateway version, matching source, fetched main, Engram's watcher/adapters/query projection, read-only Tightbeam metadata, and real native-session joins. No index rebuild, integration deployment, or full adapter test was performed.
The recon includes the configuration example, source revisions, proposed mapping fields, and a bounded proof covering shared homes, native session changes, cross-host collisions, real edits, and historical identity gaps.