Reina Core Kanban Cleanup Report

Date: 2026-07-04

Scope: Reina Core / Harmony / memory-v2-adjacent Kanban cards that could affect the autonomous loop.

Summary

The board had old pre-C0 cards mixed with the new autonomous-loop clean chain. Some were still `todo`, one implementation card was `scheduled`, and two memory-v2 P2 child cards had just been promoted to `running` by the dispatcher. This was exactly the risk Sir pointed out: stale cards could be mistaken for current authorization.

Cleanup result:

• Kept the canonical clean chain:

- `t_1b975019` C0.1 worker capsule lint checker: done.

- `t_cdf700c9` C0.2 channel-split synthetic evaluator: ready.

- `t_090e0d03` C0.3 sensory gate tabletop cases: ready.

• Kept only one related scheduled watcher:

- `t_fa290b8b` memory-v2 SQLite/FTS5 threshold watcher: scheduled, silent below threshold, creates fresh approval card if threshold reaches 200.

• Archived legacy superseded cards:

- `t_6867d578` Temporal fact graph mock prototype.

- `t_d1e0d103` Hybrid retrieval offline eval.

- `t_1ecccba2` Persona exporter spec/synthetic samples.

- `t_96a853e4` Persona training candidate exporter prototype.

- `t_c64a5554` Eval set 30-question draft.

- `t_f01d85ad` Eval set + rubric draft.

- `t_646c2552` LoRA/MLX tracking/planning.

- `t_7dd0b61a` LoRA training experiment card.

- `t_479ec119` SQLite event store + FTS5 local prototype.

- `t_f1b3af1a` Temporal fact graph v1 local prototype.

- `t_eb87d75b` Hybrid retrieval 10-query eval.

• `t_f1b3af1a` and `t_eb87d75b` had active worker PIDs (`443575`, `443576`) after dispatcher promotion. They were archived and the worker processes were terminated.

• `t_cdf700c9` received a comment warning the heartbeat to reconcile existing archived artifact `t_92414f10` rather than blindly redoing work.

Why the archived cards are stale

They were created before the C0 conflict scan and before Sir established `goals.md` as the authorization truth source. Several comments encoded broad “shadow-only” wording. Under the current rule, archived cards must not be interpreted as live authorization. Future work should be recreated from current `goals.md` and the canonical README.

Current intended flow

C0.1 done → C0.2 ready/reconcile → C0.3 ready → stop and wait for Sir
Anything after C0.3, including Hermes-aware event projector shadow-only, requires Sir approval.
Verification
• Archived 11 stale/superseded cards.
• Kept `t_fa290b8b` scheduled watcher.
• Added cleanup comments to archived cards and active C0.2/C0.3 cards.
• Updated canonical README.
• No deletions or permanent purge were performed.
Updated 2026-07-04 18:23 PDT. 報告 3 天後轉封存,需要時說一聲。