[org] Port Org, Org-roam, agenda, capture, Babel, alerts, and publishing #11

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. Blocked by the control-plane decision in #2.

Queue blockers: #5

Analyze

Cover Org/roam2 plus org-roam-ui, org-ql, org-timed-alerts, org-alert, org-download, org-modern, writeroom-mode, ob-http, org-recoll, project-tasks, org-drill, dslide, org-contrib, capture templates, agenda, Babel, encryption, publishing, and TODO workflows.
Identify which behaviors require an Org parser/runtime versus an external Emacs compatibility service.

Gate

Org files remain canonical data; no migration may rewrite or lossy-convert the user's notes.
Open/current TODOs stay first-class; older completed TODO history remains durable but compact/paginated.

Execute

Implement native Lem Common Lisp functionality where feasible and explicit adapters where not.
Add project-scoped Org-roam/navigation and safe capture/write semantics.

Evaluate

Use fixture copies to test parsing, edits, agenda queries, captures, links, Babel dispatch, alerts, exports, and rollback without touching live notes.
Prove round-trip preservation.

Recurse

Any lossy write or unsupported syntax returns to ADADR and blocks the affected write path.

Acceptance

Core Org editing and navigation are safe.
Agenda/capture/TODO behavior matches probes.
No live Org data is used as a destructive test fixture.

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

Parser or writer loses content.
Encryption boundary is unclear.
An adapter would make Emacs a hidden mandatory backend without an approved decision.

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: #5 ## Analyze - Cover Org/roam2 plus org-roam-ui, org-ql, org-timed-alerts, org-alert, org-download, org-modern, writeroom-mode, ob-http, org-recoll, project-tasks, org-drill, dslide, org-contrib, capture templates, agenda, Babel, encryption, publishing, and TODO workflows. - Identify which behaviors require an Org parser/runtime versus an external Emacs compatibility service. ## Gate - Org files remain canonical data; no migration may rewrite or lossy-convert the user's notes. - Open/current TODOs stay first-class; older completed TODO history remains durable but compact/paginated. ## Execute - Implement native Lem Common Lisp functionality where feasible and explicit adapters where not. - Add project-scoped Org-roam/navigation and safe capture/write semantics. ## Evaluate - Use fixture copies to test parsing, edits, agenda queries, captures, links, Babel dispatch, alerts, exports, and rollback without touching live notes. - Prove round-trip preservation. ## Recurse - Any lossy write or unsupported syntax returns to ADADR and blocks the affected write path. ## Acceptance - [ ] Core Org editing and navigation are safe. - [ ] Agenda/capture/TODO behavior matches probes. - [ ] No live Org data is used as a destructive test fixture. ## 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 - Parser or writer loses content. - Encryption boundary is unclear. - An adapter would make Emacs a hidden mandatory backend without an approved decision.

nsaspy referenced this issue

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

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

nsaspy referenced this issue

2026-09-19 02:57:04 +00:00

[starintel-ide] Compose Lem SDL2, Quasar, A2A, STAR-KB/spec IDE, Git and LLM UX #17