Skip to content

Add topology-scoped Space prompts - #168

Open
Yuqing (mydmdm) wants to merge 1 commit into
mainfrom
fix/issue-166
Open

Add topology-scoped Space prompts#168
Yuqing (mydmdm) wants to merge 1 commit into
mainfrom
fix/issue-166

Conversation

@mydmdm

Copy link
Copy Markdown
Contributor

Summary

  • derive Prompt Frame scope from direct Agent Node connections
  • keep unconnected Prompt Frames Space-global and freeze scope at first explicit interaction
  • display the derived scope in the Prompt badge and document the lifecycle contract

Behavior

A Prompt Frame with no direct Agent neighbours applies to every Agent in the Space. Once it has direct Agent connections, it applies only to those Agents. Edge direction and style are ignored, non-Agent connections do not change global scope, and traversal remains direct-only.

Create-only and edge edits do not realize an Agent. The first message or external ACP control reads one current topology snapshot and persists the compiled Prompt in the immutable WorkloadSpec. Create-and-start realizes only after Agent creation completes.

Validation

  • pnpm typecheck
  • pnpm format
  • pnpm lint:fix
  • focused shared, server, RFS lifecycle, and Web badge tests
  • full shared and Web test suites

Fixes #166

Derive Prompt applicability from direct Agent connections while preserving first-interaction workload freezing, expose the derived scope in Frame badges, and document the lifecycle contract.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

Add scoping modes for Space prompts

1 participant