EDGE-02: Android local Common Lisp/ABCL runtime library and diagnostic APK #3

New issue

Open

opened 2026-09-23 05:57:45 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-09-23 05:57:45 +00:00

(Migrated from github.com)

Canonical source belongs here; Android field-client/Zara product UIs and ROM overlays consume upstream artifacts rather than duplicate runtime implementation. Foundation #1; common extraction #2.

Implement the real backend behind AndroidRuntimeHost/CommonLispPort: ABCL remains the selected Android Common Lisp target. Kotlin/Java are platform/lifecycle bridges, never replacements for Lisp actor semantics or StarLang compilation. Prove Android ART compatibility rather than assuming desktop JVM success implies it.

Deliverables

Android library/AAR, diagnostic host APK and reproducible versioned build metadata.
Direct typed Lisp entry points with data arguments; never build Lisp eval strings from requests.
Start/stop, foreground/while-in-use permission handling, process-death recovery and bounded app-private durable outbox.
Local/offline runtime without mandatory cloud account; remote/phone/mesh routing explicit in status and configuration.
Permission/capability revocation at the actual effect boundary; capture indicators; bounded resource usage and redacted diagnostics.
Dependency boundary reusable by watch and glasses hosts in this repository.

Acceptance

Actual Common Lisp expressions/API calls execute on Android ART through ABCL.
Diagnostic APK proves backend startup, lifecycle and unavailable/failure states honestly.
Offline restart, process kill, permission denial/revocation and foreground transition tests pass.
Supported architecture/device matrix, minimum/target SDK and dependency pins documented from verified builds.
Runtime policy/lifecycle semantics remain in shared Lisp; no second actor engine in Kotlin.
Downstream can consume a pinned AAR/source revision and run conformance tests.

Current code is only a JVM-compilable forwarding facade, not an Android service or APK. Do not close this issue on facade tests alone.

Primary platform reference checked 2026-09-23: https://developer.android.com/develop/background-work/services/fgs/restrictions-bg-start

Canonical source belongs here; Android field-client/Zara product UIs and ROM overlays consume upstream artifacts rather than duplicate runtime implementation. Foundation #1; common extraction #2. Implement the real backend behind `AndroidRuntimeHost`/`CommonLispPort`: ABCL remains the selected Android Common Lisp target. Kotlin/Java are platform/lifecycle bridges, never replacements for Lisp actor semantics or StarLang compilation. Prove Android ART compatibility rather than assuming desktop JVM success implies it. ## Deliverables - Android library/AAR, diagnostic host APK and reproducible versioned build metadata. - Direct typed Lisp entry points with data arguments; never build Lisp eval strings from requests. - Start/stop, foreground/while-in-use permission handling, process-death recovery and bounded app-private durable outbox. - Local/offline runtime without mandatory cloud account; remote/phone/mesh routing explicit in status and configuration. - Permission/capability revocation at the actual effect boundary; capture indicators; bounded resource usage and redacted diagnostics. - Dependency boundary reusable by watch and glasses hosts in this repository. ## Acceptance - [ ] Actual Common Lisp expressions/API calls execute on Android ART through ABCL. - [ ] Diagnostic APK proves backend startup, lifecycle and unavailable/failure states honestly. - [ ] Offline restart, process kill, permission denial/revocation and foreground transition tests pass. - [ ] Supported architecture/device matrix, minimum/target SDK and dependency pins documented from verified builds. - [ ] Runtime policy/lifecycle semantics remain in shared Lisp; no second actor engine in Kotlin. - [ ] Downstream can consume a pinned AAR/source revision and run conformance tests. Current code is only a JVM-compilable forwarding facade, not an Android service or APK. Do not close this issue on facade tests alone. Primary platform reference checked 2026-09-23: https://developer.android.com/develop/background-work/services/fgs/restrictions-bg-start