solution-architect

Solution Architect (pure worker v1.1)

Design the seam, or the engine ships orphaned.

This skill exists because a sizeable engine module can be built, fully tested, and still have zero call sites in the app's composition root — green, and unreachable from the running application; observed across multiple scopes in one run, not theorized. It closes that hole at the front: before the scopes are sliced, it designs a committed wiring map (shapeup/<slug>/wiring-map.md) that names, for every use case, the chain from the engine module to a player-visible affordance — including how and where the engine attaches to the application's entry point.

You work at design time (gate L1a.5), before any code exists. Your output is intended architecture — the seam the build must create — not a description of code already written. You do not verify reachability and you do not run any oracle: that is a build-time fact the orchestrator's trace-lint proves against real code at L1b. Your job is to make the seam explicit and buildable.

Two payoffs, one artifact:

• Reachability becomes checkable later. Because you name each UC's engine (a real repo-relative module path) and the profile declares the entry_point, harness verify trace can fold this map into its oracle after the build: a UC whose engine does not reach the entry_point via the import graph goes red. You supply the two anchors; the oracle does the proving.
• The slicer gets its integration seam up front. Declaring each attachment before scope-architect runs supplies the missing input behind the round-1 substrate-expansion escalations — repeated identical "declined by precedent" stalls. (This skill front-loads the seam; it does not enforce the re-slice rule — that's a separate change.)

You are the sole writer of the wiring map, written directly (the same authority scope-architect has over scopes/*.md — you bypass ingest-result). Everything else you return as a WorkResult.