mosaicstack/stack
1
0
Fork 0
Code Issues 31 Pull Requests 2 Actions Packages Projects Releases 15 Wiki Activity

Forge<->Fleet bridge: concrete forge TaskExecutor adapter dispatching stages via the fleet (agent-send.sh) #628

New Issue
Open
opened 2026-06-22 19:44:51 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-06-22 19:44:51 +00:00
Owner
Copy Link

Recon (2026-06-22) found @mosaicstack/forge (packages/forge, v0.0.3) is a fully-implemented software-factory PIPELINE engine (brief -> Board-of-Directors review -> 3 planning stages -> coding -> review/remediation -> testing -> deploy; run/resume/status), missing only a concrete TaskExecutor to dispatch tasks to agents. The fleet keeps agents alive (agent-send.sh).

Build the missing bridge: a thin adapter (e.g. packages/forge-exec) implementing forge's TaskExecutor interface that takes a ForgeTask and dispatches it to a named fleet agent via agent-send.sh, returning status/result. This makes forge DRIVE the fleet (delivery orchestration on top of the runtime substrate).

Do NOT rebuild forge's pipeline sequencing / gate logic / brief classification / BOD — reuse runPipeline/resumePipeline. Post-PoC; part of the control-plane / delivery-orchestration workstream. Verdict: forge + fleet are COMPLEMENTARY (forge=orchestration layer, fleet=runtime substrate).

Recon (2026-06-22) found @mosaicstack/forge (packages/forge, v0.0.3) is a fully-implemented software-factory PIPELINE engine (brief -> Board-of-Directors review -> 3 planning stages -> coding -> review/remediation -> testing -> deploy; run/resume/status), missing only a concrete TaskExecutor to dispatch tasks to agents. The fleet keeps agents alive (agent-send.sh). Build the missing bridge: a thin adapter (e.g. packages/forge-exec) implementing forge's TaskExecutor interface that takes a ForgeTask and dispatches it to a named fleet agent via agent-send.sh, returning status/result. This makes forge DRIVE the fleet (delivery orchestration on top of the runtime substrate). Do NOT rebuild forge's pipeline sequencing / gate logic / brief classification / BOD — reuse runPipeline/resumePipeline. Post-PoC; part of the control-plane / delivery-orchestration workstream. Verdict: forge + fleet are COMPLEMENTARY (forge=orchestration layer, fleet=runtime substrate).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#628
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?