pdurlej/platform

Fork 0

ops: ADR-0014 Phase 06 prune Q2-2026 additional sunset candidates + silverbullet migration spec #173

Closed

claude wants to merge 1 commit from claude-orchestrator/sunset-triage-q2-2026 into main

claude commented

2026-05-11 02:19:14 +02:00

Collaborator

What

Per GPT-5.5 Pro oracle review §6 OVER-ENGINEERING audit: adds 3 new sunset candidates to the Q2-2026 cohort + ships migration spec for the already-scheduled silverbullet sunset (deadline 2026-05-30, 19 days from now).

Recommendations only, not actions. Operator decides per-module via follow-up PRs after reviewing proposals.

Files (5)

File	Purpose
`decisions/0014-prune-q2-2026-additional-candidates.md`	The ADR; 3 new candidates + silverbullet migration table
`docs/sunset-proposals/np-openhabittracker.md`	Sunset rationale + Obsidian replacement + export procedure
`docs/sunset-proposals/shelfmark.md`	2-phase (park then sunset) migration
`docs/sunset-proposals/np-tududi.md`	3-option operator decision (consolidate / keep both / sunset)
`docs/sunset-proposals/silverbullet-migration.md`	Per-content-type migration table + 2-hour operator workflow

Sunset cohort Q2-2026 (this PR adds)

Module	Recommendation	Operator threshold to keep
`np-openhabittracker`	SUNSET	weekly active use over 30 days
`shelfmark`	PARK then SUNSET	integrates with research workflow
`np-tududi`	CONSOLIDATE/SUNSET (3 options)	distinct functional role from Kan

Silverbullet migration table (canonical, per ADR §Migration table)

silverbullet content type	Migration target
Operational docs / runbooks	`pdurlej/platform` repo (`docs/runbooks/`)
Personal notes / PKM	Obsidian vault (`02 Areas/`, `03 Resources/`)
Fast capture / scratch memos	`home-platform-np-memos-1`
Tasks (project)	Kan (project board)
Tasks (personal)	per ADR-0014 §np-tududi decision
Structured product decisions	Forgejo issues OR ADRs
Templates / boilerplate	Obsidian `05 System/templates/`
Drafts (blog, LinkedIn, X)	Obsidian `00 Inbox/drafts/`

Operator runs ~2-hour focus block before 2026-05-30 deadline.

NOT in this cohort (preserved with rationale)

np-meerkat-{backend,frontend} (CRM): serves operator's contacts; separate ADR before sunset
np-radicale (CalDAV): serves operator's calendar; separate ADR
searxng: actively used by Hermes for research; stays
voice-transcription: actively used; stays
gmail-openclaw-broker / gmail-triage-mcp: Iskra mail integration; stays

What this PR DOES NOT do

Does NOT modify any module.yaml (operator decides per-module via follow-up PRs)
Does NOT execute any migration or decommission
Does NOT delete any container, manifest, or module directory
Does NOT touch silverbullet (existing 2026-05-30 sunset retained; this PR adds the migration spec only)

Acceptance criteria

ADR-0014 has Status: Proposed.
4 sunset proposals exist as separate Markdown files with risk matrix.
Silverbullet migration table covers all expected content types + has operator workflow recommendation.
3+3 canary fires on risk/process (touches decisions/).
Operator reviews 4 proposals; opens 3 module-amendment PRs as decisions.
Silverbullet migration pass scheduled within 19-day window.

Rollback

git revert <merge-commit>
git push origin main

Pure additive (5 new files, 0 modified). Reverting deletes the proposals.

Refs

GPT-5.5 Pro oracle review 2026-05-11 §6 OVER-ENGINEERING audit
INDEX.md (2026-04-30) existing sunset queue
PLATFORM_CHARTER.md §6 (Definition of Sunset)
Companion: PR #168, #169, #170, #171, #172

Codex effort needed

Review + merge. No runtime change. After merge: operator decides per-module + executes silverbullet migration within deadline window.

Role: orchestrator / drafter (claude)
Lane: Phase 06 prep
Next: operator reviews 4 proposals → 3 module-amendment PRs (per-module sunset/park decisions) → silverbullet 2-hour migration pass.

## What Per GPT-5.5 Pro oracle review §6 OVER-ENGINEERING audit: adds 3 new sunset candidates to the Q2-2026 cohort + ships migration spec for the already-scheduled silverbullet sunset (deadline 2026-05-30, 19 days from now). **Recommendations only**, not actions. Operator decides per-module via follow-up PRs after reviewing proposals. ## Files (5) | File | Purpose | |------|---------| | `decisions/0014-prune-q2-2026-additional-candidates.md` | The ADR; 3 new candidates + silverbullet migration table | | `docs/sunset-proposals/np-openhabittracker.md` | Sunset rationale + Obsidian replacement + export procedure | | `docs/sunset-proposals/shelfmark.md` | 2-phase (park then sunset) migration | | `docs/sunset-proposals/np-tududi.md` | 3-option operator decision (consolidate / keep both / sunset) | | `docs/sunset-proposals/silverbullet-migration.md` | Per-content-type migration table + 2-hour operator workflow | ## Sunset cohort Q2-2026 (this PR adds) | Module | Recommendation | Operator threshold to keep | |--------|----------------|---------------------------| | `np-openhabittracker` | SUNSET | weekly active use over 30 days | | `shelfmark` | PARK then SUNSET | integrates with research workflow | | `np-tududi` | CONSOLIDATE/SUNSET (3 options) | distinct functional role from Kan | ## Silverbullet migration table (canonical, per ADR §Migration table) | silverbullet content type | Migration target | |---------------------------|------------------| | Operational docs / runbooks | `pdurlej/platform` repo (`docs/runbooks/`) | | Personal notes / PKM | Obsidian vault (`02 Areas/`, `03 Resources/`) | | Fast capture / scratch memos | `home-platform-np-memos-1` | | Tasks (project) | Kan (project board) | | Tasks (personal) | per ADR-0014 §np-tududi decision | | Structured product decisions | Forgejo issues OR ADRs | | Templates / boilerplate | Obsidian `05 System/templates/` | | Drafts (blog, LinkedIn, X) | Obsidian `00 Inbox/drafts/` | Operator runs ~2-hour focus block before 2026-05-30 deadline. ## NOT in this cohort (preserved with rationale) - **np-meerkat-{backend,frontend}** (CRM): serves operator's contacts; separate ADR before sunset - **np-radicale** (CalDAV): serves operator's calendar; separate ADR - **searxng**: actively used by Hermes for research; stays - **voice-transcription**: actively used; stays - **gmail-openclaw-broker / gmail-triage-mcp**: Iskra mail integration; stays ## What this PR DOES NOT do - Does NOT modify any `module.yaml` (operator decides per-module via follow-up PRs) - Does NOT execute any migration or decommission - Does NOT delete any container, manifest, or module directory - Does NOT touch silverbullet (existing 2026-05-30 sunset retained; this PR adds the migration spec only) ## Acceptance criteria - [x] ADR-0014 has Status: Proposed. - [x] 4 sunset proposals exist as separate Markdown files with risk matrix. - [x] Silverbullet migration table covers all expected content types + has operator workflow recommendation. - [ ] 3+3 canary fires on `risk/process` (touches `decisions/`). - [ ] Operator reviews 4 proposals; opens 3 module-amendment PRs as decisions. - [ ] Silverbullet migration pass scheduled within 19-day window. ## Rollback ``` git revert <merge-commit> git push origin main ``` Pure additive (5 new files, 0 modified). Reverting deletes the proposals. ## Refs - GPT-5.5 Pro oracle review 2026-05-11 §6 OVER-ENGINEERING audit - INDEX.md (2026-04-30) existing sunset queue - PLATFORM_CHARTER.md §6 (Definition of Sunset) - Companion: PR #168, #169, #170, #171, #172 ## Codex effort needed **Review + merge.** No runtime change. After merge: operator decides per-module + executes silverbullet migration within deadline window. --- **Role:** orchestrator / drafter (claude) **Lane:** Phase 06 prep **Next:** operator reviews 4 proposals → 3 module-amendment PRs (per-module sunset/park decisions) → silverbullet 2-hour migration pass.

claude added 1 commit

2026-05-11 02:19:14 +02:00

ops: ADR-0014 Phase 06 prune Q2-2026 additional candidates + silverbullet migration spec

canary-required / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 10s

Details

fef2468c12

Per GPT-5.5 Pro oracle review §6 OVER-ENGINEERING audit, adds 3 new sunset
candidates to the Q2-2026 review cohort + ships migration spec for the
already-scheduled silverbullet sunset (deadline 2026-05-30, 19 days from now).

Additional candidates (ADR-0014 §Sunset candidates Q2-2026)

- np-openhabittracker: SUNSET unless weekly active use
- shelfmark: PARK then SUNSET unless integrates with research workflow
- np-tududi: 3-option operator decision (consolidate to Kan / keep both
  with documented separation / sunset to Obsidian-Iskra)

Per-module sunset proposals (docs/sunset-proposals/)

- np-openhabittracker.md: rationale + Obsidian daily-note replacement +
  export procedure + risk matrix
- shelfmark.md: 2-phase migration (park first; sunset at deadline) + risk matrix
- np-tududi.md: 3 options (A consolidate / B keep both / C sunset to
  Obsidian) with pros/cons each
- silverbullet-migration.md: per-content-type migration table covering
  operational docs / personal notes / scratch memos / tasks / decisions /
  templates / drafts; operator workflow recommendation (single 2-hour pass)

NOT in this cohort (preserved with rationale)

- np-meerkat-{backend,frontend} (CRM): serves operator's contacts;
  separate ADR before sunset
- np-radicale (CalDAV): serves operator's calendar; separate ADR
- searxng: actively used by Hermes for research; stays
- voice-transcription: actively used; stays
- gmail-openclaw-broker / gmail-triage-mcp: Iskra mail integration; stays

What this PR DOES NOT do

- Does NOT modify any module.yaml (operator decides per-module via
  follow-up PRs after reviewing proposals)
- Does NOT execute any migration or decommission
- Does NOT delete any container, manifest, or module directory
- Does NOT touch silverbullet (existing 2026-05-30 sunset retained; this
  PR adds the migration spec only)

Refs

- GPT-5.5 Pro oracle review 2026-05-11 §6 OVER-ENGINEERING audit (additional
  sunset candidates) + recommendation to migrate silverbullet by content type
- INDEX.md (2026-04-30) existing sunset queue: silverbullet, vault,
  audio-mcp-legacy, signal-bridge-legacy, products-agent-eval-lab, teamspeak3
- PLATFORM_CHARTER.md §6 (Definition of Sunset)

**Role:** orchestrator / drafter (claude)

claude referenced this pull request

2026-05-11 02:23:14 +02:00

docs(hermes): canonical 7-deliverable bundle templates (Phase 07 §G + GPT §7) #174

claude referenced this pull request from a commit

2026-05-11 02:24:55 +02:00

state/reports: WAKEUP_BRIEF for operator after overnight session 2026-05-11

claude referenced this pull request

2026-05-11 02:25:31 +02:00

state/reports: WAKEUP_BRIEF for operator after overnight session 2026-05-11 #175

codex commented

2026-05-24 07:59:22 +02:00

Collaborator

Fork A triage (codex): closing as superseded by the current post-soak cleanup model.

This old Phase 06 prune/sunset ADR predates ADR-0020 and the current milestone roadmap. Cleanup and sunset work now belongs to Milestone 01 (legacy cleanup) and later module-upgrade/sunset waves, with ADR-0020 gates.

The per-module sunset notes may still be useful raw material, but this PR should not be merged as a Phase 06 ADR in the post-cutoff roadmap.

Fork A triage (codex): closing as superseded by the current post-soak cleanup model. This old Phase 06 prune/sunset ADR predates ADR-0020 and the current milestone roadmap. Cleanup and sunset work now belongs to Milestone 01 (legacy cleanup) and later module-upgrade/sunset waves, with ADR-0020 gates. The per-module sunset notes may still be useful raw material, but this PR should not be merged as a Phase 06 ADR in the post-cutoff roadmap.

codex closed this pull request

2026-05-24 07:59:22 +02:00