Ship Profile A as a reproducible read-only library release #8

New issue

Open

opened 2026-08-03 07:47:57 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-03 07:47:57 +00:00

(Migrated from github.com)

Depends on

#1 through #7

Goal

Turn the implemented kernels into a reproducible, independently usable Profile A release rather than a private StarIntel adapter.

Scope

expose the narrow public session and read-only fetch API
publish capability discovery for the active profile
package libcldiscordcurl and cl-discord-self separately
add Nix checks for native units, Lisp units, replay, compatibility, and integration fixtures
verify production closure excludes Python
document setup, fixture-only validation, lifecycle, checkpoint, limits, and failure semantics
add a controlled opt-in live smoke-test harness that is disabled by default and never runs in CI

Constraints

the released library contains no StarIntel policy or storage dependency
Profile A is read-only
no unsolicited messaging or interaction automation
no automatic transport-profile rotation
no claim of successful validation unless the command was executed and recorded

Exit gate

all 25 design acceptance tests are represented by executable checks or an explicitly linked downstream integration gate
production ASDF and Nix closures contain no Python
shutdown drains or cancels every operation before native unload
logs and conditions contain credential references, never raw credentials
a non-StarIntel Common Lisp program can instantiate the library through the documented public API

## Depends on - #1 through #7 ## Goal Turn the implemented kernels into a reproducible, independently usable Profile A release rather than a private StarIntel adapter. ## Scope - expose the narrow public session and read-only fetch API - publish capability discovery for the active profile - package `libcldiscordcurl` and `cl-discord-self` separately - add Nix checks for native units, Lisp units, replay, compatibility, and integration fixtures - verify production closure excludes Python - document setup, fixture-only validation, lifecycle, checkpoint, limits, and failure semantics - add a controlled opt-in live smoke-test harness that is disabled by default and never runs in CI ## Constraints - the released library contains no StarIntel policy or storage dependency - Profile A is read-only - no unsolicited messaging or interaction automation - no automatic transport-profile rotation - no claim of successful validation unless the command was executed and recorded ## Exit gate - all 25 design acceptance tests are represented by executable checks or an explicitly linked downstream integration gate - production ASDF and Nix closures contain no Python - shutdown drains or cancels every operation before native unload - logs and conditions contain credential references, never raw credentials - a non-StarIntel Common Lisp program can instantiate the library through the documented public API