[inventory] Build executable Emacs-to-Lem parity probes #13

Open
opened 2026-09-16 04:13:23 +00:00 by nsaspy · 0 comments
Owner

Parent: #1

RAGE contract

Consume only this issue on rage/<issue>-<slug>. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical rage and adadr skills from lost-rob0t/skills before architecture or implementation. Blocked by the control-plane decision in #2.

Queue blockers: #3

Analyze

  • Inventory explicit active/disabled packages, implicit Doom modules, custom autoloads, snippets, profiles, Home Manager dependencies, external commands, keybindings, and startup behavior from the pinned dotfiles commit.
  • Distinguish package presence from user-visible behavior and record confidence/provenance per capability.

Gate

  • Every discovered active capability must map to exactly one owner issue or an explicit approved rejection.
  • Generated/tangled files never outrank their Org source.

Execute

  • Expand .prolog/kb/lem_migration.pl into a complete machine-readable manifest.
  • Add black-box probes that capture current Emacs behavior without mutating user state, plus corresponding target probes for Lem.

Evaluate

  • Prove the verifier fails on an unmapped package/module/custom component and passes only when ownership is total.
  • Publish the inventory counts and unresolved mappings in the issue.

Recurse

  • Newly discovered behavior reopens inventory coverage and blocks final cutover until owned.

Acceptance

  • All active packages and Doom modules are represented.
  • All custom autoloads and snippet families are represented.
  • Every capability has provenance, owner, status, and an executable or explicitly manual probe.

Durable evidence

  • Update the relevant facts in .prolog/kb/lem_migration.pl and .prolog/kb/issues.pl in the same change.
  • Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status.
  • Keep failed iterations and architecture contradictions visible.

Stop conditions

  • Source baseline moved without recording a new SHA.
  • A capability cannot be assigned without a design decision.
  • Inventory would read secrets or private runtime state into Git.
Parent: #1 ## RAGE contract Consume only this issue on `rage/<issue>-<slug>`. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical `rage` and `adadr` skills from `lost-rob0t/skills` before architecture or implementation. Blocked by the control-plane decision in #2. Queue blockers: #3 ## Analyze - Inventory explicit active/disabled packages, implicit Doom modules, custom autoloads, snippets, profiles, Home Manager dependencies, external commands, keybindings, and startup behavior from the pinned dotfiles commit. - Distinguish package presence from user-visible behavior and record confidence/provenance per capability. ## Gate - Every discovered active capability must map to exactly one owner issue or an explicit approved rejection. - Generated/tangled files never outrank their Org source. ## Execute - Expand `.prolog/kb/lem_migration.pl` into a complete machine-readable manifest. - Add black-box probes that capture current Emacs behavior without mutating user state, plus corresponding target probes for Lem. ## Evaluate - Prove the verifier fails on an unmapped package/module/custom component and passes only when ownership is total. - Publish the inventory counts and unresolved mappings in the issue. ## Recurse - Newly discovered behavior reopens inventory coverage and blocks final cutover until owned. ## Acceptance - [ ] All active packages and Doom modules are represented. - [ ] All custom autoloads and snippet families are represented. - [ ] Every capability has provenance, owner, status, and an executable or explicitly manual probe. ## Durable evidence - Update the relevant facts in `.prolog/kb/lem_migration.pl` and `.prolog/kb/issues.pl` in the same change. - Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status. - Keep failed iterations and architecture contradictions visible. ## Stop conditions - Source baseline moved without recording a new SHA. - A capability cannot be assigned without a design decision. - Inventory would read secrets or private runtime state into Git.
Sign in to join this conversation.
No description provided.