Persist governed prompt and response bodies as restricted trajectory content #64
Labels
No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-proxy#64
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Agent Proxy needs prompt and response content as foundational trajectory evidence, not as generic Ollama host telemetry and not only as optional SigNoz span attributes. Implement a durable content-addressed restricted-body store behind content.body_ref, with explicit capture policy, retention class, access tier, hashes, replay semantics, backup coverage, and deletion/expiry authority. Keep hot-path emission bounded and asynchronous. Default operational logs and host Ollama telemetry remain prompt-free. This follows agent-proxy#63.