M-PM-2 (superseded): pm-observer profile — abandoned, phantom #28
Labels
No labels
blocked:needs-decision
bug
chore
cron
design
in-progress
infra
milestone
module-o
needs-decompose
needs-research
ops-task
pm
quickfix
security/medium
triage-approved
vikunja
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/org_mode#28
Loading…
Add table
Add a link
Reference in a new issue
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?
CLOSED — SUPERSEDED (2026-08-21)
This issue proposed building a
pm-observerprofile that reads Vikunja andproduces drift/rollup/stale/weekly review reports. That was a phantom invention.
Ground truth: the substrate already processes Vikunja work correctly through
tasker-workeron thetaskerboard (~/.hermes/profiles/tasker-worker/SOUL.md):it classifies each Vikunja-backed card, does whatever support it can for
human-op work, and writes back to Vikunja on complete/block. No observer
profile, no cadence trigger layer, no sync middle-man is needed.
The user confirmed the current substrate is the correct implementation. This
issue and the phm
pm-observermachinery have been purged fromdocs/vikunja-pm-system.md(§9 "What's NOT in this system").Superseded by: the existing
tasker-workerdriver. No work required.M-PM-3: PM observation crons — drift / rollup / stale / weeklyto M-PM-3: PM observer agent + lane — drift / rollup / stale / weekly reviewM-PM-3: PM observer agent + lane — drift / rollup / stale / weekly reviewto M-PM-2: the pm-observer profile — new agent, not a laneM-PM-2: the pm-observer profile — new agent, not a laneto M-PM-2 (superseded): pm-observer profile — abandoned, phantom