CP05 Task 39 rulings (release dialog, supersede, document notice, decision entries)
Scan com.kamo.z.shared.cameras so the KamoCameras tables are created
KamoCameras entities and repositories (schema camera)
Sites, device-code enrollments, go2rtc config history, camera systems, cameras, groups, access rules and saved layouts. Tables are created by KamoInitializerSer...
Index owner-less notes, keep SI memory cards out of every search but the SI's own
KamoCollab CP11 Task 6 (spec 5.6, D29). note.rag.upsert names the note's owner, absent for Our Master Note: such a note, or one its label shares, is indexed wit...
Retiring an SI asks what happens to its workstation — Delete now, Delete after N days (default 7, 1-365) or Keep; a retired SI's profile shows the pending deletion date or 'kept' with Delete now and Keep; the Computers tab marks a pending deletion and offers Keep and Delete now
Owner decision 2026-10-11. AiRetireWorkstationChoice sits inside the retire confirmation (ConfirmationDialog gains a content slot and confirmDisabled): hidden f...
Retiring an SI takes the admin's choice for its workstation — Delete now, Delete after N days, or Keep
Owner decision 2026-10-11. POST /members/{id}/ai/retire accepts {workstation: KEEP|DELETE_NOW|DELETE_AFTER, deleteAfterDays: 1-365, default 7}; no body or no wo...
CP12 T36 rulings — the escalation's decision-task link, the charter LIMIT parity guard
A retired SI's workstation carries the admin's choice — retire_disposition (KEEP, DELETE_NOW, DELETE_AFTER) and delete_after, written only by their own UPDATE (updatable = false, like the AI session columns, so a sweep's stale save cannot undo it); RetireChoice parses and validates it (none = KEEP, DELETE_AFTER 1-365 days, default 7); findDueForDeletion reads only due rows through the partial index, oldest first, LIMITed; AccessLogEventType gains AI_WORKSTATION_AUTO_DELETED
Owner decision 2026-10-11: at retire the admin chooses Delete now, Delete after N days or Keep. The columns and ix_hosted_computer_delete_after were applied by ...
SI members' structured task comments — a position as a chip with its stance, a hand-off as a card, an escalation with a link to the decision task — and the charter mirror's daily message cap per SI colleague (KamoCollab CP12 T36)
- TaskCommentsThread: POSITION shows "Position · Proposes|Agrees|Disagrees" above the text; HANDOFF a "Hand-off" card holding the packet; ESCALATION "Escalate...
CP07 Task 39 rulings (requests to share in the Interaction Center, readiness refusal)
A session search can be narrowed to what its audience may read
POST /api/rag/search on the session path takes audienceMembers (at most 50) and audienceExternal and ANDs, per member, the four ways a member may read a point (...
CP12 Task 35 rulings — the Team view's links, blocked-task reads, columns, failures, and the worktree rebase
An SI's charter read is retried on a YugabyteDB conflict instead of answering 503
GET **************** (I1) resolves the charter in one read-only transaction of 15-25 queries. One "Restart read required" (40001) answered 503 CHARTER_UNAVAILAB...
Like what you see shipping?
All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.