Mechanical harness routing: isc route/lanes, no silent inherit #5

Merged

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

Conversation 0 Commits 1 Files changed 7 +474 -75

ksamaschke commented 2026-08-19 09:09:36 +00:00

Owner

Copy link

isc route returns ENGINE/MODEL/EFFORT/DISPATCH/WHY for the current harness — availability-aware, invariant-aware, refusing (exit 1) when a lane is UNCONFIGURED (inherit), the duty is unknown, or the frontier guard is violated. isc lanes prints the full ladder once at Phase 0. Every dispatch point in implement-issues calls isc route instead of re-deriving routing from prose; the dispatcher returns a duty only. 93/93 smoke under bash and dash.

isc route <duty> returns ENGINE/MODEL/EFFORT/DISPATCH/WHY for the current harness — availability-aware, invariant-aware, refusing (exit 1) when a lane is UNCONFIGURED (inherit), the duty is unknown, or the frontier guard is violated. isc lanes prints the full ladder once at Phase 0. Every dispatch point in implement-issues calls isc route instead of re-deriving routing from prose; the dispatcher returns a duty only. 93/93 smoke under bash and dash.

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

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

Routing was re-inferred from prose at every dispatch, so an unconfigured lane
silently inherited the main agent's model (typically Claude), defeating lane
routing and the cross-family review invariant. isc route <duty> now returns
ENGINE/MODEL/EFFORT/DISPATCH/WHY for this harness, refusing (exit 1) on
inherit, unknown duties and frontier-guard violations; isc lanes prints the
whole ladder once. The dispatcher returns a duty; isc route owns the mapping.

ksamaschke merged commit 4c76796922 into main 2026-08-19 09:09:38 +00:00

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

Mechanical harness routing: isc route/lanes, no silent inherit (#5)

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-cursor!5

No description provided.