OpsHistory context-pack intake and run/evidence emission contract

[mdheller]

Mission

Integrate OpsHistory into AgentPlane as the governed context intake and evidence emission layer for multi-chat agentic operations.

AgentPlane already validates bundles, places execution, runs them, emits evidence artifacts, and supports deterministic replay. OpsHistory should not replace that. It should supply bounded context packs and receive run/evidence references.

Scope

1. Define AgentPlane intake of OpsHistory context packs:
   • room/thread/workroom/topic scope;
   • policy decision refs;
   • agent/session authority refs;
   • memory context-pack refs;
   • browser/shell/GitHub/CI event refs;
   • redaction/tombstone refs;
   • artifact refs by hash/ref, not raw payload.
2. Define emitted OpsHistory events for:
   • validation start/complete;
   • placement decision;
   • run start/complete/fail;
   • replay artifact emitted;
   • evidence artifact emitted;
   • policy denial;
   • revocation/redaction invalidation;
   • agent handoff.
3. Add service/runtime posture for local-first execution:
   • activatable service boundary where appropriate;
   • pressure-exitable/idle-safe behavior;
   • durable evidence refs;
   • no ambient transcript scraping.
4. Add replay semantics:
   • OpsHistory event refs must be sufficient to reconstruct the context intake envelope;
   • full replay must still use AgentPlane artifacts as authority.
5. Add validation/example bundle that consumes an OpsHistory context-pack fixture and emits synthetic OpsHistory event refs in dry-run mode.

Acceptance criteria

• Docs explain AgentPlane's role in the OpsHistory loop: context-pack consumer, evidence producer, replay authority.
• Machine-readable fixture exists for an OpsHistory context-pack intake.
• Machine-readable examples exist for AgentPlane-emitted OpsHistory events.
• Existing evidence-forward execution model remains intact.
• Raw chat transcripts, browser histories, shell outputs, credentials, and large artifacts are not embedded directly.
• Policy Fabric decision refs and Agent Registry authority refs are represented.
• Redaction/tombstone invalidation of context packs and evidence references is modeled.

Non-goals

• Do not move AgentPlane evidence authority into AgentTerm, Memory Mesh, or BearBrowser.
• Do not implement Matrix, browser, or shell adapters here.
• Do not bypass bundle validation, placement, run artifacts, or replay artifacts.

Suggested files

• docs/integration/ops-history.md
• schemas/ops-history-context-intake.schema.json
• schemas/ops-history-agentplane-event.schema.json
• examples/ops-history/context-intake.example.json
• examples/ops-history/agentplane-events.example.json
• validator/test following repo conventions.

Agent note

@copilot @codex Keep the first PR contract-first: docs, schemas, examples, validators, dry-run fixture. Runtime binding follows after the contracts settle.

[mdheller]

Triage — OpsHistory context-pack intake and run/evidence emission contract: Integration. OpsHistory → AgentPlane evidence bridge. Depends on OpsHistory durability decision (Noetica #51).