| containers | OK |
| gitea | OK |
| local_clones | OK |
| opt_deployments | OK |
| vault_pages | OK |
Tracks archive/delete decisions for projects the [[projects/_index|project controller]]
flags as drop candidates. States: proposed -> approved -> archived -> delete-ready -> deleted.
Nothing here moves itself. The controller only ever proposes (writes a judgment file) and,
at most, surfaces "archived N days ago, now delete-ready" once 30 days pass. A human approves
every archive and every delete, separately, every time — see ORCHESTRATOR.md's standing-
schedule exception (added 2026-08-25) for the narrow, non-destructive authority the daily job
actually has.
Archiving a Gitea repo uses Gitea's native archived flag (reversible, read-only afterward).
For vault-only projects with no repo, "archive" means the vault page's status: frontmatter
flips to archived and gets a dated note — there's nothing else to flag. Either way, delete
is always a distinct, separately-approved action; nothing in this repo or the dashboard can
call a delete endpoint (verified — see project-control's README).
| Project | Proposed | Proposed by | Approved | Action | Delete-eligible | State |
|---|---|---|---|---|---|---|
apu-assistant |
2026-08-25 | project controller (agy-suro1, first judgment pass) — evidenced staleness: seed status unchanged for 3.5 months, zero artifacts beyond the vault page |
2026-08-25 (user) | Archived — vault page status: seed → archived |
2026-09-24 | archived |
finance-bot |
2026-08-25 | project controller (agy-suro1, first judgment pass) — flagged as a drop candidate, reasoning: "redundant with sms-finance" | 2026-08-25 (user) — reasoning rejected, not the project: user identified the redundancy claim as wrong (finance-bot is a personal/household WhatsApp tracker; sms-finance is SMS's business project financial-control app — no actual domain overlap) | Recategorized — vault page status: developing → idea, moved from Active to Ideas/Backlog in projects/_index.md |
n/a — not on an archive/delete track | recategorized, not archived |
finance-bot's prior mis-flagging is a real, logged accuracy miss for agy-suro1 in this
category — worth a mention next time [[Dispatch Decision Ledger]]'s bulk-reasoning-report
row gets updated with a second data point. The census JSON gave agy the right raw facts
(finance-bot's own vault page describes it as a WhatsApp household tracker); the redundancy
conclusion was an inference error, not a bad data read. Future judgment prompts could ask
agy to state why two projects are "redundant" rather than just asserting it, so a claim
like this is checkable at a glance instead of needing the user to catch it after the fact.apu-assistant's archive is vault-only bookkeeping — there was never a repo or deployment to
touch, so this row exists mostly so the controller stops proposing the same drop every day
once it's already been decided. Any future collector pass should skip status: archived
pages when generating new drop proposals (not yet implemented — collector doesn't currently
read this ledger back to suppress repeat proposals; flagged as a real gap, not fixed here).sms-finance (spectado/pocketbase:latest, Up 2 hours, port 0.0.0.0:3003->8090/tcp), sms-finance-dev (spectado/pocketbase:latest, Up 8 hours, port 0.0.0.0:3103->8090/tcp), ts-sms-finance (tailscale/tailscale:latest, Up 2 hours)./opt/sms-finance (last_touched_iso: 2026-08-25T03:01:20.502323+00:00, active file: pb_data/auxiliary.db-wal).SINERGI/project-fin-control (212 KB, updated_at: 2026-08-19T18:46:09Z). Local working clone at /home/ubuntu/agents-switching/docker/data/project/project-fin-control is 19 commits ahead of remote, with last_commit_date: 2026-08-25T02:55:54+00:00 (289f934a4ad4: "sms-finance: mobile responsiveness fixes"), clean working tree on branch main.sms-finance.md (status: phase2-in-progress, updated 2026-08-24), sms-finance-prd.md (status: approved, updated 2026-08-18).Validation and testing of Phase 2 UI and mobile responsiveness fixes committed today, pushing the 19 unpushed local commits from /data/project/project-fin-control to upstream Gitea SINERGI/project-fin-control, synchronizing the production deployment at /opt/sms-finance, and preparing for Phase 3 (M2 pre-award bid analysis / promote-to-budget and seeding real project budget data from CCTV Bendung / PJT Cawang).
Continue — Intense daily development velocity evidenced by 19 unpushed local commits today, an active dev sandbox container, and same-day database WAL writes in production.
doc-control (spectado/pocketbase:latest, Up 6 days, port 0.0.0.0:3002->8090/tcp), doc-control-rclone (rclone/rclone:latest, Up 6 days), ts-doc-control (tailscale/tailscale:latest, Up 2 hours)./opt/doc-control (last_touched_iso: 2026-08-25T03:00:01.206594+00:00, active file: data/data.db-wal).SINERGI/doc-control-clean (1,277 KB, updated_at: 2026-08-19T18:45:52Z). No local clone on VM101 shared disk.doc-control.md (status: active, updated 2026-08-25).Ongoing production operation of document approval workflows, maintaining automated OneDrive synchronization via Microsoft Graph device-code flow and rclone rcd sidecar, and preparing for future decoupled Phase 4 project registry integration with sms-finance. Specific feature backlog cannot be observed from commits due to absence of a local git tracking clone on VM101.
Continue — Stable production deployment in active daily operational use with same-day database WAL activity, healthy cloud sync containers, and updated documentation.
agents-switching (docker-middleware, Up 17 hours, healthy, port 127.0.0.1:3100->3100/tcp), 9router (docker-9router, Up 18 hours, port 0.0.0.0:20128->20128/tcp), filebrowser (filebrowser/filebrowser:s6, Up 4 days, healthy, port 0.0.0.0:3004->80/tcp), plus 5 agent sandbox containers: sbx-hermes (Up 17 hours), sbx-claude-max (Up 19 hours), sbx-agy-2 (Up 19 hours), sbx-claude-2 (Up 19 hours), sbx-agy-suro1 (Up 19 hours).dimas/agents-switching (305 KB, updated_at: 2026-08-25T00:00:03Z).agents-switching.md (status: active, updated 2026-08-24), agents-switching-v0.8.5-to-v0.8.11.md (status: developing, updated 2026-08-11), agents-switching-v0.8-steel-frame.md (status: active, updated 2026-07-14), agents-switching-v0.7.1-portable.md (status: superseded), agents-switching-v0.7.2-remote.md (status: superseded).Implementing and stabilizing roadmap items for v0.8.5→v0.8.11 (RAM-floor dispatch guard in src/core/dispatch/, dashboard $ cost view on React 19 UI, native MCP dispatch interface evaluation for Gemini-style orchestrators, and hermes agent endpoint probe hardening).
Continue — Core fleet switching and orchestration infrastructure under active daily execution with 8 running containers and commits pushed today to Gitea.
scada-admin (iiot_scada-admin, Up 6 days, healthy, port 0.0.0.0:8081->8081/tcp), grafana (grafana/grafana:latest, Up 6 days, healthy, port 0.0.0.0:3000->3000/tcp), influxdb (influxdb:2.7, Up 6 days, healthy, port 0.0.0.0:8086->8086/tcp), postgres (postgres:16-alpine, Up 6 days, healthy, port 0.0.0.0:5432->5432/tcp), nodered (nodered/node-red:latest, Up 6 days, healthy, port 0.0.0.0:1880->1880/tcp), scada-hmi (nginx:alpine, Up 6 days, port 0.0.0.0:8080->80/tcp), mosquitto (eclipse-mosquitto:latest, Up 6 days, ports 0.0.0.0:1883->1883/tcp, 0.0.0.0:9001->9001/tcp), scada-simulator (python:3-slim, Up 6 days), runtime-tracker (python:3-slim, Up 6 days)./opt/iiot (last_touched_iso: 2026-08-25T02:00:01.958221+00:00, active file: /opt/iiot/backups/scada_2026-08-25.sql.gz).SINERGI/PJT2-W4-SCADA (24 KB, updated_at: 2026-07-14T10:13:56Z).pjt2-scada.md (status: active, updated 2026-07-14).Continuous telemetry ingestion and operational health monitoring for 17 pump stations at Perum Jasa Tirta II RG1, maintaining automated daily PostgreSQL backups, and executing scheduled backlog enhancements (Telegram alarm notifications for critical pump threshold events, HMI Sinoptik diagram integration, and aligning deployment with SINERGI/Proxmox IaC templates).
Continue — Mission-critical industrial telemetry and operational control stack with 9 healthy containers and verified automated daily SQL backups.
SINERGI/Proxmox (472 KB, updated_at: 2026-08-19T18:21:44Z).Proxmox.md (title: Proxmox (SINERGI) — infra-as-code for the pjt2-scada stack, status: seed, created/updated 2026-08-25).Cataloging and validating infrastructure-as-code automation templates (docker-compose.yml, provisioning scripts, PostgreSQL initialization routines) for the pjt2-scada stack, expanding documentation on the newly created Proxmox.md vault page, and establishing reproducible provisioning workflows.
Continue — Active infrastructure-as-code codebase updated 6 days ago in Gitea and newly documented in the Obsidian vault today.
gitea (gitea/gitea:latest, Up 6 days, ports 0.0.0.0:2222->22/tcp, 0.0.0.0:3001->3000/tcp)./opt/gitea (last_touched_iso: null).SINERGI/PJT2-W4-SCADA, SINERGI/Proxmox, dimas/agents-switching, SINERGI/doc-control-clean, dimas/dv-obsidian-vault, dimas/project-control, SINERGI/project-fin-control).gitea.md (status: active, updated 2026-07-16).Routine core service operation, periodic container version upgrades, and regular backup verification. No pending application development features observable.
Continue — Indispensable fleet infrastructure service hosting all internal git repositories.
ts-project-control (tailscale/tailscale:latest, Up 10 minutes), project-control-nginx (nginx:alpine, Up 10 minutes, port 0.0.0.0:3005->80/tcp)./data/project/project-control.dimas/project-control (49 KB, updated_at: 2026-08-25T02:59:16Z).Refining daily census collector routines (v0.2 collector enhancements), expanding judgment synthesis heuristics, polishing the dashboard UI on port 3005, and creating a dedicated vault documentation page for fleet governance.
Continue — Active development and daily execution occurring today (2026-08-25) with recent container rollouts and fresh Gitea commits.
dimas/dv-obsidian-vault (6,872 KB, updated_at: 2026-08-25T00:00:02Z)._index.md (status: seed, updated 2026-07-14).Continuous documentation synchronization across all active projects, updating obsolete project statuses in frontmatter, logging decision ledger entries, and refreshing _index.md to match current fleet topology.
Continue — Primary knowledge base repository with continuous daily updates across all active projects and architectural records.
claude-obsidian.md (title: claude-obsidian, type: concept, status: developing, created 2026-04-08, updated 2026-08-25).Conceptual synthesis and workflow specification for AI assistant integration with Obsidian knowledge bases. As a pure concept note without backing code or runtime containers on VM101, tangible deliverables cannot be observed through system telemetry.
Continue — Concept note actively refreshed in the Obsidian vault today (2026-08-25).
portainer (portainer/portainer-ce:latest, Up 6 days, ports 8000/tcp, 9443/tcp, 0.0.0.0:9000->9000/tcp).infra (unowned by any project page).Operational container management UI. Outstanding work is undocumented; requires assigning project ownership and creating an infrastructure wiki page.
Continue — Healthy operational container supporting Docker container management across the VM101 fleet.
pjt-cawang.md (title: PJT Cawang (family), status: developing, updated 2026-08-11).Cannot observe off-VM deliverables directly. On-VM tracking is limited to recording weekly reporting cycle outputs and project milestones in the wiki.
Continue — Vault page updated 14 days ago (2026-08-11), consistent with bi-weekly reporting rhythms.
cctv-bendung.md (title: CCTV Bendungan Pelana, status: developing, updated 2026-08-11).pjt-cawang for Pelana Dam CCTV installation. Work product generated off-VM. Evaluated strictly on vault-page freshness; actual progress cannot be observed on this VM.Cannot observe off-VM deliverables directly. Outstanding work on-VM includes obtaining historical HPP vs RAB workbooks for sms-finance calibration and synchronizing field status reports in the wiki.
Continue — Updated on 2026-08-11 in tandem with pjt-cawang.
rekon-odc-odp.md (title: Rekon ODC-ODP, status: developing, updated 2026-08-11).Cannot observe external spreadsheet edits. Outstanding work on-VM is logging reconciliation batch milestones and data summaries into the vault.
Continue — Vault page active within the past two weeks (2026-08-11).
project-monitoring.md (title: project-monitoring, status: active, updated 2026-04-26), project-monitoring-ftth.md (title: project-monitoring — FTTH Pinggir Rel (real data), status: developing, updated 2026-08-11).binyo32/project-monitoring outside VM101 reach. Evaluated strictly on vault-page freshness; silence on VM101 does not imply project staleness.Cannot inspect external GitHub repository directly. Outstanding work documented in the wiki includes ongoing FTTH Pinggir Rel dataset integration updated on 2026-08-11.
Continue — Active external project with sub-project documentation updated 14 days ago (silence on VM is expected).
finance-bot.md (title: Finance Bot, type: meta, status: idea, created 2026-04-11, updated 2026-08-25), finance-bot-patterns.md (title: finance-bot patterns, type: project-patterns, status: seed, created 2026-05-06, updated 2026-05-07).status: developing to status: idea and moved to Ideas/Backlog in projects/_index.md. Entirely distinct domain from sms-finance (household WhatsApp expense logging vs. corporate/business project financial control). Evaluated strictly as an off-VM idea backlog item.Preserved in the Ideas/Backlog for personal and household WhatsApp expense tracking. Outstanding work includes formulating initial requirement specifications or prototyping the 3-lane n8n clarification loop when prioritized.
Continue (in Backlog/Ideas) — Formally retained as an active backlog idea per user decision on 2026-08-25; there is zero functional redundancy with sms-finance (personal WhatsApp expense logging vs. business project financial control).
The following vault documentation pages exhibit status: fields or metadata that are contradicted by observed census data:
Proxmox.md (Vault Status: seed vs. Substantial Git Repository):Proxmox.md is marked status: seed (created/updated 2026-08-25), yet Gitea repository SINERGI/Proxmox contains 472 KB of committed infrastructure-as-code scripts (last updated 2026-08-19).Recommendation: Upgrade vault status from seed to active or developing.
pjt2-scada.md (Vault Status: active vs. Maintenance Runtime):
pjt2-scada.md is marked status: active with last update on 2026-07-14. Gitea repo SINERGI/PJT2-W4-SCADA has had no commits since 2026-07-14 (6+ weeks). However, production runtime is fully operational with 9 containers up and daily SQL backups running (2026-08-25).Recommendation: Update vault documentation to reflect operational/maintenance mode rather than active feature development.
project-fin-control (Gitea Remote vs. Local Clone State):
SINERGI/project-fin-control was last updated on 2026-08-19 (appears stale remotely), but the local working clone has 19 unpushed commits with intense development activity today (2026-08-25T02:55:54Z).Recommendation: Push local commits to upstream Gitea to synchronize remote status.
project-monitoring.md (Vault Status: active with 4-Month Dormancy vs. Active Sub-page):
project-monitoring.md has status: active but was last updated on 2026-04-26 (4 months ago), while sub-project page project-monitoring-ftth.md was actively updated on 2026-08-11 with status: developing.Recommendation: Synchronize main page frontmatter to reflect sub-project activity.
_index.md (Projects Index Outdated):
_index.md has status: seed and was last updated on 2026-07-14, omitting recently active projects such as project-control and Proxmox._index.md catalog to include all current fleet projects and their up-to-date statuses.The following projects or infrastructure components exist in only a single data source:
project-control (Gitea Repo / Containers Only — No Vault Page):dimas/project-control (49 KB, updated 2026-08-25) and running containers (ts-project-control, project-control-nginx), but has no vault page in the Obsidian wiki.portainer (Container Only):portainer/portainer-ce:latest), explicitly noted in census as infra (unowned by any project page) with no repository, deployment record, or vault page.claude-obsidian (Vault Only):claude-obsidian.md) in the Obsidian vault without any git repository, deployment directory, or container.pjt-cawang (Vault Only):pjt-cawang.md), representing an off-VM reporting workflow.cctv-bendung (Vault Only):cctv-bendung.md), representing an off-VM reporting workflow.rekon-odc-odp (Vault Only):rekon-odc-odp.md), representing an off-VM Excel workbook.finance-bot (Vault Only):finance-bot.md, finance-bot-patterns.md), representing an off-VM idea on the backlog.| Project | Type | Primary Signal | Status Assessment | Action | Next Milestone Window | Confidence |
|---|---|---|---|---|---|---|
| sms-finance | On-VM App | 19 unpushed commits, dev env up, live DB touched today | Highly Active (Phase 2) | Continue | 1–3 days (by 2026-08-28) | High |
| doc-control | On-VM App | Live DB touched today, 3 containers up, vault updated | Active (Production) | Continue | 1–2 weeks (early Sept) | Medium |
| agents-switching | Fleet Infra | 8 containers up, Gitea updated today, vault active | Highly Active | Continue | 3–7 days (by 2026-08-31) | High |
| pjt2-scada | On-VM SCADA | 9 containers up healthy, daily SQL backup today | Active (Maintenance/Ops) | Continue | 2–4 weeks (late Sept) | Medium |
| Proxmox | Infra / IaC | 472 KB repo updated Aug 19, vault page added today | Active (IaC Initial) | Continue | 1–2 weeks (by 2026-09-05) | Medium |
| gitea | Fleet Infra | Container up 6 days, hosts all internal git repos | Active (Core Service) | Continue | 2–4 weeks | Low |
| project-control | Automation | Gitea repo updated today (census/judgment), containers up | Highly Active | Continue | 1–3 days (by 2026-08-28) | High |
| dv-obsidian-vault | Wiki Repo | 6.8 MB repo updated today, 21 vault pages | Highly Active | Continue | 1–3 days | High |
| claude-obsidian | Concept Note | Vault page updated today (concept doc) | Active (Concept) | Continue | 1–2 weeks | Low |
| portainer | Fleet Infra | Container up 6 days (unowned in vault) | Active (Utility) | Continue | n/a | Low |
| pjt-cawang | Invisible | Vault page updated 2026-08-11 (weekly report cycle) | Active (Off-VM) | Continue | 1–2 weeks (early Sept) | Low |
| cctv-bendung | Invisible | Vault page updated 2026-08-11 (sibling project) | Active (Off-VM) | Continue | 2–3 weeks (mid-Sept) | Low |
| rekon-odc-odp | Invisible | Vault page updated 2026-08-11 (FTTH workbook) | Active (Off-VM) | Continue | 2–3 weeks (mid-Sept) | Low |
| project-monitoring | Invisible | Sub-page updated 2026-08-11, GitHub repo external | Active (External GitHub) | Continue | 2–4 weeks (Sept 2026) | Low |
| finance-bot | Invisible | Recategorized to idea (2026-08-25), personal WhatsApp bot | Backlog / Idea | Continue | n/a | Low |
(All milestone windows formulated as controller estimate, revised 2026-08-25)