docs(product): design the compass-agent forge tool surface (RIG-2672) - #588
Open
rigel-mintaka wants to merge 1 commit into
Open
docs(product): design the compass-agent forge tool surface (RIG-2672)#588rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
|
Compass engineering docs preview: https://compass-agent-rig-2672-forge.compass-eng-docs.pages.dev Deployed from Changed pages: |
rigel-mintaka
force-pushed
the
compass-agent/rig-2672-forge-tools-design
branch
from
August 24, 2026 18:26
d752679 to
25dcb8f
Compare
rigel-mintaka
marked this pull request as ready for review
August 24, 2026 18:26
rigel-mintaka
force-pushed
the
compass-agent/rig-2672-forge-tools-design
branch
from
August 24, 2026 18:58
25dcb8f to
bbbcf72
Compare
The forge Go path is complete end-to-end (server chokepoint, hub relay, runner gateway leg, proto carrier + generated TS types); the only missing piece is the TypeScript agent-side leg. This record designs it: a `forge()` method on the `RunnerTransport` seam + its socket impl, a `ForgeBroker`, and eight single-purpose native tools (one per built `ForgeCallRequest` arm) mirroring the comms/lifecycle tool precedent, wired into cli.ts customTools with per-tool prompt guidance. Matt-ruled forks folded as Decisions: full parity (all 8 built arms), one tool per arm with the ruled names, subscribe/unsubscribe deferred to the poll-driver lane. Two non-load-bearing Open Questions remain (single PR vs T1/T2 stack; ForgeRef exposure), each with a recommendation. Ledger: adds DL-241 (the 8-tool forge native toolset) to the Comms & tools section of docs/designs/product/DECISIONS.md, mirroring DL-212's comms-toolset count row. Ledger-impact: DL-241 appended (forge native toolset, one-tool-per-arm, no ForgeRef exposure, subscribe/unsubscribe deferred). Spec-impact: none (design record; the proto/Go path already exists). Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
force-pushed
the
compass-agent/rig-2672-forge-tools-design
branch
from
August 24, 2026 19:11
bbbcf72 to
2049e92
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The forge Go path is complete end-to-end (server chokepoint, hub relay,
runner gateway leg, proto carrier + generated TS types); the only missing
piece is the TypeScript agent-side leg. This record designs it: a
forge()method on the
RunnerTransportseam + its socket impl, aForgeBroker, andeight single-purpose native tools (one per built
ForgeCallRequestarm)mirroring the comms/lifecycle tool precedent, wired into cli.ts customTools
with per-tool prompt guidance.
Matt-ruled forks folded as Decisions: full parity (all 8 built arms), one
tool per arm with the ruled names, subscribe/unsubscribe deferred to the
poll-driver lane. Two non-load-bearing Open Questions remain (single PR vs
T1/T2 stack; ForgeRef exposure), each with a recommendation.
Ledger: adds DL-241 (the 8-tool forge native toolset) to the Comms & tools
section of docs/designs/product/DECISIONS.md, mirroring DL-212's comms-toolset
count row.
Ledger-impact: DL-241 appended (forge native toolset, one-tool-per-arm, no
ForgeRef exposure, subscribe/unsubscribe deferred).
Spec-impact: none (design record; the proto/Go path already exists).
Co-authored-by: Matt Wilkinson matt@rigel.build