Repository navigation
feat(roadmap): bind edge-ai-android feasibility spike to a device-resident loop - #192
Merged
Merged
Conversation
…ident loop The epic has been paused since 2026-09-12 with both work items unbound, so nothing could ever move it out of PARK. The owner decided on 2026-10-16, after the market assessment, to spend a two-day no-Kotlin spike before archiving or activating, and to change the framing: the phone is the execution device. TDLib session, model and policy gate live on the device, there is no Local Bridge and no hosted agent, so the goal now says that instead of describing a generic "local execution surface". feasibility-spike is bound to mctlhq/mctl-agents#652, which carries the scope, the five acceptance criteria and the decision rule. lifecycle stays paused on purpose: the spike is evidence gathering, not activation, and local-execution-contract is untouched until the spike reports. Claude-Session: https://claude.ai/code/session_01JfH3dqZvkmRuM4EeYVaJHw
|
Claude finished @mashkovd's task in 15s —— View job Review completeApproved commit 23b7105. The change only edits I couldn't run |
Antigravity (agy) reviewagy returned a result this workflow could not use; see the workflow log. Treated as a failed review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
roadmap/epics/edge-ai-android.yaml: bind work itemfeasibility-spiketo spike(edge-ai): on-device tool-calling loop over Telegram tool schemas on a Pixel 10 Pro, no Kotlin mctl-agents#652 and retitle it to what the spike actually tests.spec.goalwith the owner's thesis: the phone is the execution device. TDLib session, on-device model and local policy gate live on the device, no Local Bridge, no hosted agent, private chats never leave the phone.lifecyclestayspaused.local-execution-contractis untouched.Why
The epic has been in PARK since 2026-09-12 with both work items unbound, so the roadmap could never report progress on it. On 2026-10-16 the owner read the market assessment and chose a two-day no-Kotlin spike on a Pixel 10 Pro before deciding between archive and a narrowed activation. The spike issue carries the scope, the five acceptance criteria and the decision rule; this PR only makes the manifest point at it and say what question the epic is now asking.
Checks
python roadmap/scripts/validate.py roadmap/epics: 20 PASSpython -m unittest discover -s roadmap/tests -p 'test_*.py': 318 tests OKRefs #34, mctlhq/mctl-agents#652
🤖 Generated with Claude Code
https://claude.ai/code/session_01JfH3dqZvkmRuM4EeYVaJHw