Mechanical harness routing: isc route/lanes #9

Merged

ksamaschke merged 1 commit from feat/mechanical-harness-routing into main 2026-08-19 09:11:23 +00:00

Conversation 0 Commits 1 Files changed 5 +408 -18

ksamaschke commented 2026-08-19 09:11:21 +00:00

Owner

Copy link

isc route returns ENGINE/MODEL/EFFORT/DISPATCH/WHY for the current harness, resolved from the lane map, the routing keys in .claude/implement-issues.md, and live CLI availability; WARN + exit 1 on frontier-guard violations, exit 1 on unknown duties. isc lanes prints the full ladder once at Phase 0. Every dispatch point in implement-issues (Phase 2 sizing, Phase 3 implementer, 4.1 checker, 4.2 reviewers) now calls isc route and dispatches exactly what it returns rather than re-deriving routing from prose; the dispatcher consult survives only for tie-breaks and must express its decision as a duty. 91/91 smoke under bash and dash.

isc route <duty> returns ENGINE/MODEL/EFFORT/DISPATCH/WHY for the current harness, resolved from the lane map, the routing keys in .claude/implement-issues.md, and live CLI availability; WARN + exit 1 on frontier-guard violations, exit 1 on unknown duties. isc lanes prints the full ladder once at Phase 0. Every dispatch point in implement-issues (Phase 2 sizing, Phase 3 implementer, 4.1 checker, 4.2 reviewers) now calls isc route and dispatches exactly what it returns rather than re-deriving routing from prose; the dispatcher consult survives only for tie-breaks and must express its decision as a duty. 91/91 smoke under bash and dash.

ksamaschke added 1 commit 2026-08-19 09:11:22 +00:00

feat(isc): mechanical harness routing via isc route/lanes ... 9e66b4521d

Routing was re-inferred from prose at every dispatch point, so lane
assignments drifted from what the config actually says. isc route <duty> now
returns ENGINE/MODEL/EFFORT/DISPATCH/WHY for this harness — reading the lane
map, the routing keys, and live CLI availability — and refuses (exit 1) on
unknown duties or frontier-guard violations; isc lanes prints the whole
ladder once at Phase 0. Every dispatch point calls it instead of reasoning.

ksamaschke merged commit 233f5e6eb2 into main 2026-08-19 09:11:23 +00:00

ksamaschke referenced this pull request from a commit 2026-08-19 09:11:24 +00:00

Mechanical harness routing: isc route/lanes (#9)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ksamaschke/implementation-skills-claude!9

No description provided.