[control] Select and record the ADADR control-plane mode #15

New issue

Open

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

nsaspy commented

2026-09-16 04:13:23 +00:00

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. This issue is the control-plane gate.

Queue blockers: none

Analyze

Read the canonical rage and adadr skills from lost-rob0t/skills and inspect this repository's durable control-plane evidence.
Present the exact choice required by RAGE: human-gated ADADR or self-recording Auto-RAGE. Do not silently infer a mode.

Gate

No port implementation is authorized by this issue.
Stop until the user explicitly selects ADADR or Auto-RAGE.

Execute

Record the selected mode in AGENTS.md, .prolog/kb/lem_migration.pl, and the roadmap.
Define the approved research/design evidence locations without inventing parallel control planes.

Evaluate

Run .prolog/verify.pl and prove exactly one valid mode is selected.
Confirm all implementation issues reference this gate.

Recurse

If the user changes modes later, open a new decision issue; do not rewrite historical run evidence.

Acceptance

One explicit mode is selected and Git-tracked.
The evidence locations and approval semantics are unambiguous.
The Prolog verifier rejects unselected for implementation work.

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

Ambiguous user choice.
Conflicting project instruction.
Any attempt to cross a human approval gate automatically.

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. This issue is the control-plane gate. Queue blockers: none ## Analyze - Read the canonical `rage` and `adadr` skills from `lost-rob0t/skills` and inspect this repository's durable control-plane evidence. - Present the exact choice required by RAGE: human-gated **ADADR** or self-recording **Auto-RAGE**. Do not silently infer a mode. ## Gate - No port implementation is authorized by this issue. - Stop until the user explicitly selects ADADR or Auto-RAGE. ## Execute - Record the selected mode in `AGENTS.md`, `.prolog/kb/lem_migration.pl`, and the roadmap. - Define the approved research/design evidence locations without inventing parallel control planes. ## Evaluate - Run `.prolog/verify.pl` and prove exactly one valid mode is selected. - Confirm all implementation issues reference this gate. ## Recurse - If the user changes modes later, open a new decision issue; do not rewrite historical run evidence. ## Acceptance - [ ] One explicit mode is selected and Git-tracked. - [ ] The evidence locations and approval semantics are unambiguous. - [ ] The Prolog verifier rejects `unselected` for implementation work. ## 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 - Ambiguous user choice. - Conflicting project instruction. - Any attempt to cross a human approval gate automatically.

nsaspy referenced this issue

2026-09-16 04:13:23 +00:00

[epic] Port the complete active Emacs environment to Lem #16