OpsHistory control plane for adaptive multi-chat agentic operations

[mdheller]

Mission

Codify the CloudHistory lesson into AgentTerm as an explicit OpsHistory control plane: local-first event history, adaptive sync, policy-gated replication, redaction priority, context-pack export, and deterministic replay for multi-chat human/agent operations.

AgentTerm already treats every meaningful action as an event and states that the event log is the control plane. This issue makes that control plane first-class instead of implicit.

Core concept

OpsHistory is the local-first operational memory fabric for AgentTerm rooms, threads, agents, tools, browser sessions, shell sessions, GitHub/CI events, Memory Mesh recall/writeback, Policy Fabric decisions, AgentPlane runs, and handoffs.

The CloudHistory lesson to preserve:

• local state first;
• replication controlled by policy, not ambient transport;
• cadence changes with topology;
• deletion/redaction propagates faster than normal writes;
• payloads and sync windows are bounded;
• shutdown/termination behavior is bounded;
• policy can change without rebuilding the operator UI.

Scope

Add docs/specs and implementation seams for:

1. ops-historyd or equivalent AgentTerm-local event history service/library.
2. Event classes for chat, slash command, agent reply, tool call, browser event, terminal event, memory recall/writeback, policy decision, AgentPlane run, GitHub/CI event, artifact ref, redaction, revocation, and handoff.
3. Adaptive sync profile schema:
   • solo local;
   • active multi-agent room;
   • multi-room workroom;
   • enterprise bridge;
   • offline/fog mode.
4. Redaction/tombstone priority lane.
5. Context-pack export boundary for Memory Mesh and AgentPlane.
6. explain surfaces for why an event synced, did not sync, entered memory, was denied, or was redacted.
7. Deterministic replay dry-run for a room/thread/workroom.

Acceptance criteria

• AgentTerm docs define OpsHistory as the shared control-plane event fabric.
• A machine-readable OpsHistory event schema exists or is stubbed with clear extension points.
• A machine-readable sync policy example exists with bounded windows, payload caps, topology-aware cadence, and redaction priority.
• Matrix event IDs, thread roots, bridge metadata, and encryption posture remain preserved.
• Agent Registry remains the authority for non-human participants.
• Policy Fabric remains the authority for replication, hydration, writeback, bridge, export, and redaction decisions.
• Memory Mesh receives context-pack requests rather than raw unbounded transcripts.
• AgentPlane consumes context packs and emits evidence refs rather than scraping AgentTerm state directly.

Non-goals

• Do not replace Matrix.
• Do not move Memory Mesh, Agent Registry, Policy Fabric, or AgentPlane authority into AgentTerm.
• Do not make every chat message permanent memory.
• Do not replicate raw sensitive payloads by default.

Initial commands to validate when implemented

ruff check .
pytest
agent-term ops-history policy explain --profile active-multi-agent-room --dry-run
agent-term ops-history replay --thread demo-search --dry-run
agent-term ops-history context-pack --workroom pi-demo --topic professional-intelligence --dry-run

Agent note

@copilot @codex This is cross-plane architecture. Keep implementation bounded. Prefer docs, schemas, examples, validators, and fake-backend tests before live networking.

[mdheller]

Addendum: service-runtime lesson from SafariBookmarksSyncAgent

The second Apple plist adds a runtime/service lesson on top of the CloudHistory policy lesson. OpsHistory should not be only a library inside the AgentTerm UI. It needs a local-first service boundary.

Required additions to issue scope

Add Linux equivalents for the launchd/XPC shape:

• ops-historyd as a user-scoped, activatable local service.
• Named IPC endpoints, likely D-Bus names and/or Unix sockets:
  • org.sourceos.OpsHistory
  • org.sourceos.OpsHistory.Push
  • org.sourceos.OpsHistory.Redaction
  • org.sourceos.OpsHistory.ContextPack
• A subscription-registration activity for Matrix/workroom/topic/context-pack/policy-update notifications.
• Background maintenance priority for ordinary sync.
• Higher-priority redaction/tombstone propagation lane.
• Network-aware posture: offline queue, bidirectional sync when online, metered-network policy gate.
• Idle-safe / pressure-exitable behavior: service can stop when inactive and recover from durable local state.
• Transaction/receipt semantics so shutdown does not corrupt event state.

Linux mapping

launchd Label                -> systemd user unit name
MachServices                 -> D-Bus well-known names / Unix sockets
LaunchEvents xpc.activity    -> systemd timers/socket activation/subscription task
EnablePressuredExit          -> idle-stop + durable local state + restartable service
ProcessType Standard         -> maintenance/background cgroup/resource posture
RequireNetworkConnectivity   -> network-aware queue and retry policy
NetworkTransferDirection     -> ingress/egress policy
Priority Maintenance         -> background QoS unless governance-critical

Acceptance criteria addition

The first implementation pass should include at least one machine-readable service manifest or example showing the OpsHistory endpoints, activation posture, durable store, network requirements, redaction priority lane, and context-pack endpoint.