Migrate development commands to the Model Intelligence owner-authorized loop workflow #64
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/creatidy-kernel#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Replace the Kernel development command system with the current local Model Intelligence repository's coherent owner-authorized /loop workflow, without redesigning the product model.
Why
The owner explicitly mandates this migration. Existing single-issue delivery commands and Scarcity Router development-review dispatch rules conflict with the requested same-checkout native-review loop. Narrow canonical duplicate search found no matching Kernel migration issue.
Scope
Out of scope: product runtime/model redesign; executing the new loop for this migration; other repositories; worktrees/alternate checkouts; direct develop pushes; main, release or deployment.
Acceptance Criteria
Constraints
Use the owner's complete 2026-10-05 migration request and current local Model Intelligence contents as workflow authority. Keep adapters -> ports -> core and accepted architecture/ADRs unchanged except conflicting development-authority wording. Preserve unrelated owner work and existing excluded ledger history. No private state/secrets. No new loop authority may authorize its own migration delivery. Current pre-migration delivery bound is ten remediation cycles, not the new ten-review bound.
Links
Migration Delivery Ledger
PR: #65
Branch: issue-64-model-intelligence-workflow
Recorded base:
c1ad28a517Final HEAD:
1f9172b7ccCommits:
c1c3ce6(migration),1f9172b(preserve source wording). Both authored/committed as Adrian Tkacz adrian.tkacz@creatidy.com.Before: create-follow-up-issue, deliver-issue, implement-issue, review-pr.
After: implement-issue, review-pr, finish-pr, loop. No duplicate legacy controller remains. Authorized follow-up quality/deduplication/trigger safeguards stay in task rules; no automatic issue registration.
Current local Model Intelligence reference files were inspected and copied/adapted; their checkout HEAD is 013cbb43e11d7f698d359db5a456d26d8075e34e and the inspected local contents match that HEAD. Identity/architecture/gate/permission-command adaptations and attribution are documented in PR/NOTICE/reuse record. Reviewer isolation/model/denials and source loop semantics preserved. No product runtime/dependency/lock changes.
Final validation:
Pre-Migration Review Status
Terminal: REVIEW_INFRASTRUCTURE_BLOCKED.
Independent substantive verdict: NOT_RUN; no APPROVE obtained and no valid review dispatch claimed.
max_remediation_cycles=10; remediation_used=0; valid_completed_review_count=0.
The pre-migration /deliver-issue contract requires a fresh Scarcity Router repository_review selection and Router-eligible Agent Manager dispatch with verified model resolution. This session exposes no Router selection tool. A non-routed reviewer or the newly copied /finish-pr semantics cannot substitute under the owner's migration instructions. Missing capability has no corrected-input retry; it was not bypassed by REST, private state or self-review.
The native CLI discovery probe also failed: kilo debug agent pr-reviewer -> kilo: command not found. Native agent/runtime discovery and actual loop execution are unverified; a workspace reload may be required after integration. Local ledger .task_progress.md remains Git-locally excluded with earlier history preserved.
No Scarcity Router calls, worktrees/alternate checkouts, external-repository mutations, unrelated stash/reset, direct develop pushes, main changes, releases or deployments. New /loop was never invoked. Leave #64 open and PR #65 unmerged; implementation/validation is complete but delivery acceptance awaits a valid pre-migration independent review.