JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 115
  • Score
    100M100P100Q90131F

Package Exports

  • @femtomc/mu-control-plane

Readme

@femtomc/mu-control-plane

Control-plane command pipeline for messaging ingress, policy/confirmation safety, idempotency, outbox delivery, and the dedicated messaging meta-agent runtime.

First-platform messaging adapters (v1)

  • Slack
  • Discord
  • Telegram

All three adapters normalize inbound commands into the same control-plane pipeline and preserve correlation across command journal and outbox delivery.

Messaging meta-agent + safe CLI triggers

MessagingMetaAgentRuntime is a dedicated user-facing runtime that sits outside orchestration execution dispatch. It can translate conversational channel input into an approved command proposal and routes that through the same policy/idempotency/confirmation pipeline.

CLI execution is constrained through an explicit allowlist (MuCliCommandSurface) and a non-shell runner (MuCliRunner). Mutating run triggers (run start, run resume) still require confirmation and are correlated end-to-end via:

  • meta_session_id
  • meta_turn_id
  • cli_invocation_id
  • cli_command_kind
  • run_root_id

Unsafe or ambiguous requests are rejected with explicit reasons (context_missing, context_ambiguous, context_unauthorized, cli_validation_failed, etc.).

iMessage status

iMessage is explicitly de-scoped from first-platform runtime support in v1. Legacy iMessage identity rows are quarantined as channel_deprecated during replay and are not treated as active bindings.