Skip to content

feat(roadmap): bind edge-ai-android feasibility spike to a device-resident loop - #192

Merged
mashkovd merged 1 commit into
mainfrom
feat/edge-ai-android-bind-feasibility-spike
Oct 16, 2026
Merged

mashkovd merged 1 commit into
mainfrom
feat/edge-ai-android-bind-feasibility-spike

Conversation

@mashkovd

Copy link
Copy Markdown
Member

What

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 PASS
  • python -m unittest discover -s roadmap/tests -p 'test_*.py': 318 tests OK

Refs #34, mctlhq/mctl-agents#652

🤖 Generated with Claude Code

https://claude.ai/code/session_01JfH3dqZvkmRuM4EeYVaJHw

…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

claude Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Claude finished @mashkovd's task in 15s —— View job


Review complete

Approved commit 23b7105. The change only edits roadmap/epics/edge-ai-android.yaml. It binds feasibility-spike to mctl-agents#652, using the same issue: {repository, number} shape as agent-commerce.yaml. It also rewords the goal and the work-item title, and leaves lifecycle: paused as it was. I found no P1, P2 or P3 issues.

I couldn't run validate.py or the unit tests in this environment because the command needed approval. I relied on the PR's reported results (20 PASS, 318 tests OK).

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Roadmap manifest-only change: binds work item to mctl-agents#652 using the same issue schema as other epics; lifecycle unchanged.

@github-actions

Copy link
Copy Markdown

Antigravity (agy) review

agy returned a result this workflow could not use; see the workflow log. Treated as a failed review.

@mashkovd
mashkovd merged commit 33af5ff into main Oct 16, 2026
7 checks passed
@mashkovd
mashkovd deleted the feat/edge-ai-android-bind-feasibility-spike branch October 16, 2026 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant