Mission Control

Artifacts

K
← Back to artifactsOpen JAM-31 →

Post-Bianca Cleanup Audit

AuditDoneJAM-31Created Apr 8, 20264 min readFull screen ↗

Findings Summary

The live steering surfaces were partially stale. USER.md was still telling Vinny to prioritize AMRT, Cal Air, and EMT work. TOOLS.md was still presenting some held or personal channels as active project surfaces, and it still treated the AMRT Telegram group as a normal active surface. Mission Control dashboard mock data still surfaced a volunteer-style UAS highlight.

I cleaned the obvious live guidance drift in the workspace guidance surfaces. Since the first audit pass, Pete explicitly chose the stricter cleanup path: the personal-project Discord channels for biking, AMRT/UAS, and EMT recert were deleted. The remaining live guidance now reflects that those channels are gone and should not be treated as active surfaces.

Ready for review: yes

Active Surfaces Audited

  • /Users/vinny/.openclaw/workspace/USER.md
  • /Users/vinny/.openclaw/workspace/TOOLS.md
  • /Users/vinny/.openclaw/workspace/AGENTS.md
  • /Users/vinny/.openclaw/workspace/MEMORY.md
  • /Users/vinny/.openclaw/workspace/mission-control/data/tasks.json
  • /Users/vinny/.openclaw/workspace/mission-control/data/projects.json
  • /Users/vinny/.openclaw/workspace/mission-control/lib/mock-data.ts
  • Live Discord channel list for guild 1482433153858535656
  • Live OpenClaw config audit for handoff-adjacent channel/group references, audit only, no mutation

Edits Made

1. USER.md

Removed active-profile steering that no longer belongs in Vinny's default scope:

  • removed the volunteer email from active email accounts
  • replaced Current Goals with Current Operating Priorities
  • removed AMRT / Cal Air / EMT priority framing
  • added explicit scope guardrails so Vinny does not proactively steer into AMRT, Cal Air, EMT, biking, or similar personal-project tracks unless Pete explicitly reopens them

2. TOOLS.md

Tightened live operating notes to match current reality:

  • split Discord channels into ACTIVE PROJECTS, HOLD / NOT DEFAULT, and AUTOMATED FEEDS
  • initially moved job-search, amrt-uas, emt-recert, and biking into HOLD / NOT DEFAULT
  • after Pete chose stricter cleanup, removed the deleted personal-project channels amrt-uas, emt-recert, and biking from live channel guidance
  • added an explicit note not to route routine Vinny work into Hold channels unless Pete reopens them
  • removed stale wendy agent-line reference from the active cheat sheet because it is not in the current guild channel list
  • moved openclaw-releases into automated feeds where it actually belongs
  • tightened Telegram notes so the AMRT group is marked as present in live config but no longer a default Vinny surface

3. mission-control/lib/mock-data.ts

Removed volunteer-style dashboard framing from active Mission Control UI mock data:

  • replaced the UAS readiness / AMRT / Cal Air mission highlight
  • replaced the old Job search ops highlight, which no longer matches the current paused state
  • current dashboard mock highlights now emphasize First Ascent Labs, AI experiment work, and Mission Control reliability

What Was Intentionally Left Alone

AGENTS.md

No Bianca-handoff cleanup was needed. The active automation instructions there are still work-aligned. I left them unchanged.

MEMORY.md

No live steering issue required edits. Left intact.

Mission Control data

  • tasks.json: no AMRT / EMT / biking / Bianca tasks were found in the active board data
  • projects.json: current projects are business/workflow aligned
  • no cleanup needed there

Historical and non-steering materials

Left alone by design:

  • emt-study/
  • old research and artifacts
  • Mission Control README example text
  • skill example invocations mentioning EMT or AMRT
  • tasks-store.ts guardrail logic that avoids auto-assigning AMRT / Cal Air / EMT tasks to a business project

These are historical, example, or guardrail surfaces, not default runtime steering.

Discord Audit and Recommendation

Current channel state

The relevant personal-project channels have now been handled explicitly:

  • job-search remains in Hold, not in the active PROJECTS category, and Pete explicitly paused the job-search flow on 2026-04-06
  • amrt-uas was deleted on 2026-04-08
  • emt-recert was deleted on 2026-04-08
  • biking was deleted on 2026-04-08

Recommendation

No further Discord channel cleanup is needed for this task.

Reason:

  • the handoff-related personal-project channels were removed entirely
  • job-search remains intentionally held rather than active
  • the remaining cleanup surface is config-adjacent, not Discord-channel clutter

If Pete wants stricter cleanup later, the next safe step is:

  1. decide whether job-search should stay held or eventually be archived if the pause becomes long-term
  2. decide whether the AMRT Telegram group should be removed from live config or transferred to Bianca-owned handling

Remaining Follow-up

One config-adjacent item remains intentionally untouched:

  • the AMRT Telegram group is still present in live OpenClaw config as an allowed group surface

I did not change config, per scope. That should be a separate explicit confirmation step because it affects live runtime behavior.

Validation

Code-adjacent validation completed:

  • cd /Users/vinny/.openclaw/workspace/mission-control && npm run build
  • result: success, exit code 0

Artifact URL