P1 gate — prove Prolog-defined cross-component commands without APK rebuild #204

New issue

Open

opened 2026-08-24 06:24:56 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-24 06:24:56 +00:00

(Migrated from github.com)

Parent: #194
Depends on: #177, #198, #199, #200, #201, #202
Integrates with: #150, #151, #159

Goal

Prove new semantic functions composed solely from registered capability primitives are definable, versioned and hot-reloaded through the canonical Prolog/user-command model without an APK rebuild.

Required matrix

At minimum add fixtures for:

a new verb alias selecting an existing capability;
provider preference/fallback changes;
a composed work-mode command spanning multiple device/server capabilities;
confirmation-required side effects;
parameterized user-authored commands;
unavailable provider/capability and partial-failure behavior;
atomic rollback of an invalid update;
restart persistence and revocation.

No second macro interpreter, raw goal execution, arbitrary Intent or shell escape.

Tests

Exercise the same semantic fixtures on Linux and Android, compare typed IntentFrame/ExecutionPlan/capability behavior, and prove unchanged APK identity before/after loading the new definition.

Acceptance

A genuinely new composition and verb run on Android from updated Prolog configuration while the APK hash remains unchanged.

Parent: #194 Depends on: #177, #198, #199, #200, #201, #202 Integrates with: #150, #151, #159 ## Goal Prove new semantic functions composed solely from registered capability primitives are definable, versioned and hot-reloaded through the canonical Prolog/user-command model without an APK rebuild. ## Required matrix At minimum add fixtures for: - a new verb alias selecting an existing capability; - provider preference/fallback changes; - a composed work-mode command spanning multiple device/server capabilities; - confirmation-required side effects; - parameterized user-authored commands; - unavailable provider/capability and partial-failure behavior; - atomic rollback of an invalid update; - restart persistence and revocation. No second macro interpreter, raw goal execution, arbitrary Intent or shell escape. ## Tests Exercise the same semantic fixtures on Linux and Android, compare typed IntentFrame/ExecutionPlan/capability behavior, and prove unchanged APK identity before/after loading the new definition. ## Acceptance A genuinely new composition and verb run on Android from updated Prolog configuration while the APK hash remains unchanged.