Skip to content

feat: expose Prophet workspace hook RPC methods#4

Draft
mdheller wants to merge 1 commit intomainfrom
feat/prophet-workspace-plugin-skeleton-v1
Draft

feat: expose Prophet workspace hook RPC methods#4
mdheller wants to merge 1 commit intomainfrom
feat/prophet-workspace-plugin-skeleton-v1

Conversation

@mdheller
Copy link
Copy Markdown

@mdheller mdheller commented May 7, 2026

Summary

This PR wires the existing Prophet workspace no-op hooks into callable Gateway RPC methods.

It updates extensions/prophet-workspace/index.ts to expose:

  • prophetWorkspace.emitCarrier
  • prophetWorkspace.evaluateMembraneDecision
  • prophetWorkspace.appendLedgerEvent
  • prophetWorkspace.resolveConnectedAppGrant

Why

The merged skeleton added the Prophet workspace plugin and hook contracts. This PR makes those hook points callable through OpenClaw's existing Gateway RPC extension model, still without mutating Prophet state.

What this does

  • imports createNoopProphetWorkspaceHooks
  • instantiates no-op hook implementations in the plugin register path
  • exposes dry-run Gateway RPC methods for each hook class
  • updates the status payload to report the hook RPC phase

What this does not do yet

  • call a real Prophet service
  • emit a real PPS carrier
  • append a real ledger event
  • resolve a real connected-app grant
  • mutate workspace state

Upstream alignment

This follows OpenClaw's existing plugin model instead of adding a parallel runtime boundary.

Follow-up

  1. Replace one no-op hook with a local Prophet endpoint call.
  2. Add a smoke test fixture or CLI call for prophetWorkspace.status and one hook RPC.
  3. Route one narrow action through the hook path and render the returned receipt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant