m/paliad
1
0
Fork 0
Code Issues 146 Pull Requests 8 Actions 1 Packages Projects Releases Wiki Activity

Deferred-tracker: items intentionally postponed (don't forget) #102

New Issue
Open
opened 2026-05-25 13:34:33 +00:00 by mAi · 0 comments
mAi commented 2026-05-25 13:34:33 +00:00
Collaborator
Copy Link

Purpose

m's 2026-05-25 15:29 ask: "lets not forget the things we defer now."

This issue catalogs every item the team has consciously deferred during the 2026-05-25 batch session, with the rationale and the natural reactivation trigger. Update as deferrals accumulate; close when all are addressed or formally cancelled.

Active deferrals

Product / feature

Tag Item Why deferred Reactivate when
FEAT-1 #77 Backup Mode Slice B — BackupScheduler ticker + retention cleanup goroutine, nightly 03 UTC Slice A (on-demand) shipped first; m's call (Q4) was to land the scheduler in B not A After Slice A is verified in prod + Dokploy volume mount confirmed
FEAT-2 #77 Backup Mode Slice C — UI polish (backup-detail page, row-counts inline expansion) Cosmetic; not blocking Backup Mode usefulness After Slice B
FEAT-3 #93 procedural-events data-model redesign Inventor design exists; coder slice not yet planned. m said "we prefer good and solid" — flag as full restructure (Q1=B from #93) when implemented After atlas / icarus / cronus designs land safely
FEAT-4 #96 per-event-card optional choices (appellant per decision, include Nichtigkeitswiderklage, skip optional) Inventor design phase; depends on #93 procedural-events naming After #93
FEAT-5 #78 calendar visual diff demeter proved engines already unified; m's report needs a screenshot to scope When m supplies the screenshot

Audit findings (curie #94 / docs/research-deadlines-completeness-2026-05-25.md)

Tag Item Why deferred Reactivate when
AUDIT-Q10 GebrMG-Löschungsverfahren proceeding (de.gm.lg) HLC doesn't see them per current scope confirmation When firm flags it as in-scope
AUDIT-T4-DNI DNI family (R.63/R.67.1/R.69.1/R.69.2) Zero published filings 2026-Q1 When real cases surface
AUDIT-T4-REG Registry-correction family (R.16.3.a, R.27.2, R.89.2, R.253.2) Most natural in cascade, not proceeding-tree After cascade parity (Q11 / Wave 4)
AUDIT-T4-R245 R.245 rehearing family Specialist; outer-cap primitive (Q3) builds it once shipped After Wave 2 primitives
AUDIT-T4-R155 R.155 cost-decision opposition chain Specialist When a real case surfaces
AUDIT-T4-R144 R.144 UPC_DAMAGES tree-end row Cosmetic Wave 5/6 cleanup
AUDIT-T4-R79_2 R.79(2) EPC further-parties period Templating impossible per §9.8 — Q7=drop locked. Track via cleanup wave Wave 6 cleanup

Process / infra

Tag Item Why deferred Reactivate when
INFRA-1 Dokploy: PALIAD_EXPORT_DIR env var + /var/lib/paliad/exports volume mount Needed before #77 Backup Mode UI works in prod m's next Dokploy edit window
INFRA-2 Calendar-engine vs visual-diff cleanup (#78) Awaiting m's screenshot Once #78 resolves
INFRA-3 upckommentar slicer pattern Slice D of #79 Optional follow-on per atlas's design After atlas Slice A ships

How this gets updated

When new deferrals appear: head appends a row to the relevant section. When a deferred item is started or formally cancelled: edit the row's last column with → #<task> or cancelled YYYY-MM-DD.

Do not close this issue while deferrals remain active.

When to revisit the whole list

Every week or every major milestone (whichever is sooner). Head triggers the revisit by opening this issue + scanning for Reactivate when conditions that now hold.

## Purpose m's 2026-05-25 15:29 ask: "lets not forget the things we defer now." This issue catalogs every item the team has consciously deferred during the 2026-05-25 batch session, with the rationale and the natural reactivation trigger. Update as deferrals accumulate; close when all are addressed or formally cancelled. ## Active deferrals ### Product / feature | Tag | Item | Why deferred | Reactivate when | |---|---|---|---| | FEAT-1 | **#77 Backup Mode Slice B** — BackupScheduler ticker + retention cleanup goroutine, nightly 03 UTC | Slice A (on-demand) shipped first; m's call (Q4) was to land the scheduler in B not A | After Slice A is verified in prod + Dokploy volume mount confirmed | | FEAT-2 | **#77 Backup Mode Slice C** — UI polish (backup-detail page, row-counts inline expansion) | Cosmetic; not blocking Backup Mode usefulness | After Slice B | | FEAT-3 | **#93 procedural-events data-model** redesign | Inventor design exists; coder slice not yet planned. m said "we prefer good and solid" — flag as full restructure (Q1=B from #93) when implemented | After atlas / icarus / cronus designs land safely | | FEAT-4 | **#96 per-event-card optional choices** (appellant per decision, include Nichtigkeitswiderklage, skip optional) | Inventor design phase; depends on #93 procedural-events naming | After #93 | | FEAT-5 | **#78 calendar visual diff** | demeter proved engines already unified; m's report needs a screenshot to scope | When m supplies the screenshot | ### Audit findings (curie #94 / docs/research-deadlines-completeness-2026-05-25.md) | Tag | Item | Why deferred | Reactivate when | |---|---|---|---| | AUDIT-Q10 | **GebrMG-Löschungsverfahren proceeding** (`de.gm.lg`) | HLC doesn't see them per current scope confirmation | When firm flags it as in-scope | | AUDIT-T4-DNI | DNI family (R.63/R.67.1/R.69.1/R.69.2) | Zero published filings 2026-Q1 | When real cases surface | | AUDIT-T4-REG | Registry-correction family (R.16.3.a, R.27.2, R.89.2, R.253.2) | Most natural in cascade, not proceeding-tree | After cascade parity (Q11 / Wave 4) | | AUDIT-T4-R245 | R.245 rehearing family | Specialist; outer-cap primitive (Q3) builds it once shipped | After Wave 2 primitives | | AUDIT-T4-R155 | R.155 cost-decision opposition chain | Specialist | When a real case surfaces | | AUDIT-T4-R144 | R.144 UPC_DAMAGES tree-end row | Cosmetic | Wave 5/6 cleanup | | AUDIT-T4-R79_2 | R.79(2) EPC further-parties period | Templating impossible per §9.8 — Q7=drop locked. Track via cleanup wave | Wave 6 cleanup | ### Process / infra | Tag | Item | Why deferred | Reactivate when | |---|---|---|---| | INFRA-1 | **Dokploy: `PALIAD_EXPORT_DIR` env var + `/var/lib/paliad/exports` volume mount** | Needed before #77 Backup Mode UI works in prod | m's next Dokploy edit window | | INFRA-2 | Calendar-engine vs visual-diff cleanup (#78) | Awaiting m's screenshot | Once #78 resolves | | INFRA-3 | upckommentar slicer pattern Slice D of #79 | Optional follow-on per atlas's design | After atlas Slice A ships | ## How this gets updated When new deferrals appear: head appends a row to the relevant section. When a deferred item is started or formally cancelled: edit the row's last column with `→ #<task>` or `cancelled YYYY-MM-DD`. Do **not** close this issue while deferrals remain active. ## When to revisit the whole list Every week or every major milestone (whichever is sooner). Head triggers the revisit by opening this issue + scanning for `Reactivate when` conditions that now hold.
mAi self-assigned this 2026-05-25 13:34:33 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deferred
Parked — not pursuing now, may un-park later
done
Work completed by an agent; awaiting m to close
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees mAi
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/paliad#102
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?