Skip to content

OpsHistory context-pack contract for governed multi-chat agent memory #17

Description

@mdheller

Mission

Codify OpsHistory into Memory Mesh as a governed context-pack input contract for multi-chat agentic operations.

Memory Mesh should receive scoped, policy-admitted context packs from AgentTerm/BearBrowser/TurtleTerm/AgentPlane rather than raw unbounded transcripts or opaque browser/session logs.

Scope

  1. Define an ops-history-context-pack schema for:
    • room/thread/workroom/topic scope;
    • actor and agent refs;
    • policy decision refs;
    • event refs;
    • artifact refs;
    • redaction/tombstone refs;
    • retention and promotion rules;
    • allowed recall/writeback behavior;
    • source plane refs: AgentTerm, BearBrowser, TurtleTerm, AgentPlane, GitHub/CI.
  2. Add examples:
    • active multi-agent Matrix room context;
    • BearBrowser agent-runtime browsing trace context;
    • cloud-fog/TurtleTerm shell session context;
    • redacted sensitive-context case.
  3. Preserve existing Memory Mesh posture:
    • no raw sensitive payloads by default;
    • dry-run mode must perform no writeback;
    • scoped recall/writeback through policy admission.
  4. Define how context packs are promoted into durable memory versus kept as ephemeral task context.
  5. Add validation scripts/tests following repo conventions.

Acceptance criteria

  • Schema and examples are machine-readable and validated locally.
  • Docs clearly state that Memory Mesh does not own Agent Registry authority, Policy Fabric decisions, AgentPlane execution, AgentTerm chat authority, or BearBrowser profile separation.
  • Examples include redaction/tombstone handling and bounded sync windows.
  • Context-pack examples use refs/hashes for large artifacts instead of embedding raw artifact payloads.
  • Dry-run behavior prohibits memory writeback.

Non-goals

  • Do not store browser human-profile history in Memory Mesh by default.
  • Do not ingest raw unbounded chat transcripts.
  • Do not implement Matrix, browser, or shell adapters here.

Suggested files

  • schemas/ops-history-context-pack.schema.json
  • examples/ops-history/context-pack.multi-agent-room.example.json
  • examples/ops-history/context-pack.bearbrowser-agent-runtime.example.json
  • examples/ops-history/context-pack.shell-session.example.json
  • examples/ops-history/context-pack.redacted.example.json
  • specs/ops-history-context-pack.v1.yaml
  • scripts/validate_ops_history_context_pack.py

Agent note

@copilot @codex This should extend the existing scoped context-pack work, not replace it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions