Skip to content

Bifrost subscriber: listen for foundry.scaffold.requested events #5

Description

@jordanpartridge

What

Foundry registers itself as a Bifrost subscriber on boot. Any service that emits a foundry.scaffold.requested event gets a microservice scaffolded — no direct HTTP call needed.

How it works

Lexi (or any service)
  → emits foundry.scaffold.requested { manifest: {...} }
  → Bifrost receives + fans out
  → Foundry's ListenCommand picks it up from bifrost.foundry Redis channel
  → dispatches ScaffoldPipeline same as REST/MCP entry points

Acceptance Criteria

  • ListenCommand subscribes to bifrost.foundry Redis pub/sub channel on boot
  • Routes foundry.scaffold.requested events to ScaffoldPipeline
  • Foundry registered as a subscriber in Bifrost on deploy
  • Unrecognised event types logged and skipped gracefully
  • 100% test coverage

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