ksamaschke/implementation-skills-codex
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Mechanical harness routing: native Codex is the home engine #4

Merged
ksamaschke merged 1 commit from feat/mechanical-harness-routing into main 2026-08-19 09:10:01 +00:00
Conversation 0 Commits 1 Files changed 9 +636 -262
ksamaschke commented 2026-08-19 09:10:00 +00:00
Owner
Copy link

Fixes the reported behavior of a Codex agent invoking PI although configured for local Codex: the skill itself said 'Prefer PI' and treated native execution as a fallback. Native Codex is now the home engine for every implementation duty; PI and Claude CLI serve only where config routes them or the cross-family review rule requires. isc route returns ENGINE/MODEL/EFFORT/DISPATCH/WHY (availability-aware, WARN+exit 1 on invariant violations) and isc lanes prints the full ladder; every dispatch point calls it instead of re-deriving routing from prose. The dispatcher returns a duty only, and the delegation skills (pi-delegate, use-pi, codex-worker) were resynced to that contract. 92/92 smoke bash+dash, 25/25 renderer tests.

Fixes the reported behavior of a Codex agent invoking PI although configured for local Codex: the skill itself said 'Prefer PI' and treated native execution as a fallback. Native Codex is now the home engine for every implementation duty; PI and Claude CLI serve only where config routes them or the cross-family review rule requires. isc route <duty> returns ENGINE/MODEL/EFFORT/DISPATCH/WHY (availability-aware, WARN+exit 1 on invariant violations) and isc lanes prints the full ladder; every dispatch point calls it instead of re-deriving routing from prose. The dispatcher returns a duty only, and the delegation skills (pi-delegate, use-pi, codex-worker) were resynced to that contract. 92/92 smoke bash+dash, 25/25 renderer tests.
The skill told this harness to prefer PI for routine implementation and
treated its own native execution as a fallback, so a Codex agent routed work
to PI although configured for local Codex. Native Codex is now the home
engine for every implementation duty; PI/Claude serve only where config or
the cross-family review rule sends them. isc route <duty> returns
ENGINE/MODEL/EFFORT/DISPATCH/WHY mechanically, isc lanes prints the ladder,
and the dispatcher returns a duty rather than an engine/model string.
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
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-codex!4
No description provided.