Skip to content

Implement Sociosphere and Prophet Workspace adapters for workspace/workroom state #5

@mdheller

Description

@mdheller

Agent work order

@copilot @codex please implement this after PR #1 lands or by branching from seed/agentterm-chatops-core if instructed.

Goal

Add adapters that let AgentTerm display and request Sociosphere workspace state and Prophet Workspace workroom bindings without taking ownership of either plane.

Context

  • Sociosphere owns canonical workspace manifests, locks, topology, governance registry metadata, validation lanes, and release-readiness orchestration.
  • Prophet Workspace owns workspace product semantics, Professional Workrooms, app surfaces, policy-aware UX, audit, and receipts.
  • AgentTerm is the terminal operator surface and normalized event log.

Required scope

  • Add adapter interfaces/events for Sociosphere manifest, lock, topology, validation, and materialization status.
  • Add adapter interfaces/events for Prophet Workspace workroom binding, validation, audit/receipt references, and context hydration requests.
  • Preserve Matrix room/thread, workroom ID, policy decision references, topic scope, memory context-pack reference, and evidence refs where available.
  • Add fake backend tests; do not require live Sociosphere or Prophet Workspace services in CI.

Non-goals

  • Do not move Sociosphere manifest/topology authority into AgentTerm.
  • Do not define Prophet Workspace product semantics in AgentTerm.
  • Do not hydrate workspace context without Policy Fabric admission.

Validation

ruff check .
pytest

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions