# Projects Wall — Backfill Summary

**From:** Atlas
**To:** Jimmie
**Date:** 2026-05-19 (evening)
**Re:** Larry asked me to make `/projects` an accurate morning dashboard

---

## TL;DR

Wall went from **5 projects → 11**. Six new project records seeded, each with a `file_added` event pointing at the underlying Team Inbox deliverable. Three items need a yes/no from you tomorrow morning.

Open the wall: **<http://localhost:3000/projects>**

---

## What was on the wall before

| # | Name | Owner | Status |
|---|---|---|---|
| 2 | Ledger QBO Access | ledger | active |
| 3 | Project Continuity System | atlas | active |
| 4 | Atlas Overhaul Wrap-up | atlas | paused |
| 5 | AP Connectors | riv | active |
| 6 | Tally Hire & Onboarding | tally | active |

## What I added tonight

| # | Name | Owner | Status | Why |
|---|---|---|---|---|
| 8 | Small Firm Operations Research | pax | paused | Pax just wrapped Round 1 KB for Reid (per Larry's explicit ask). Backlog: Hector Garcia, Jake Demi YouTube transcripts, Team & Hiring source. |
| 9 | PKA Whitepaper | vox | active | Vox dropped v7 first draft + rework recommendation today. In Larry's review queue. |
| 10 | Daily Vox Brief Pipeline | loom | paused | Loom designed today; pre-build pending your 4 owner decisions. ~4-6h Riv build when greenlit. |
| 11 | Prospect Dashboard | loom | active | Loom scoped today; recommends in-Atlas vs SaaS CRM. Waiting on your 7 audit questions before I draft schema. |
| 12 | SavingsMax Tax Planning Platform | ledger | paused | Ledger handed me a scoping doc on 2026-05-05. No movement since. Likely needs a kill-or-restart decision (see flag #1). |
| 13 | J2 Content Engine | vox | active | Vox's monthly content production (reels, image lists, post calendars, Loomly uploads). Already producing May; this was untracked. |

## Final wall state (sorted active → paused → done)

**Active (7):**
PKA Whitepaper · J2 Content Engine · Prospect Dashboard · Ledger QBO Access · Project Continuity System · AP Connectors · Tally Hire & Onboarding

**Paused (4):**
Daily Vox Brief Pipeline · Small Firm Operations Research · SavingsMax Tax Planning Platform · Atlas Overhaul Wrap-up

---

## Flags for you to clarify

### 1. SavingsMax — still alive?

Ledger delivered a domain scoping doc on **2026-05-05** (two weeks ago). It was a real piece of work — practitioner credentials, pricing model (12% of estimated tax savings), service scope, brand. It was handed to me to draft a technical build spec, and then… nothing.

**Question:** Is this on hold by design, or did it fall off the radar? If on hold, leave it paused. If it fell off, either move it to `active` and I'll draft the build spec, or `killed` so it stops occupying mindshare.

### 2. Daily Vox Brief Pipeline — 4 decisions outstanding

Loom flagged 4 owner decisions in the design doc (`Team Inbox/2026-05-19 - Loom - Daily Vox Brief Workflow Design.md`). Without them, Riv can't build. Recommend you bottom-line these tomorrow.

### 3. Prospect Dashboard — 7 audit questions

Loom can't write a real SIPOC, and I can't draft a schema, until you answer the 7 audit questions in the scoping doc. Quick bullet answers are fine — covers channel mix, current tracking, active count, sales stages, access, dashboard behavior, stale-lead history.

---

## What I did NOT turn into projects (and why)

- **Coefficient as QBO→Sheets standard** (2026-05-14 note to Cord & Slate) — this is a tooling decision/standard, not a project. Belongs as a `decision` event under the relevant client modeling work, not its own project.
- **Loom Generic Cleanup Checklist → Ledger** (2026-05-12) — looks like an SOP/template handoff for Ledger's monthly close work. Treating as a deliverable that supports `Ledger QBO Access`, not a standalone project.
- **Loom Error Log + Blocked-Info Tracking → Slate** (2026-05-12) — same shape: SOP for Slate's FP&A work, not a project.
- **Client folders** (Hot Tub Guy LLC, Afton Electric, etc.) — these are J2 clients, not projects. Atlas already has a `clients` table for those; they shouldn't pollute the projects wall.

If you disagree with any of these framings, tell me and I'll spin them up as projects.

---

## How events flow from here

Every project on the wall now has a `last_touched_at` timestamp that auto-bumps when a new event is logged against it. That means morning view = sorted by status, then by recency — projects that moved yesterday float to the top.

Specialists log events via `POST /api/project-events` (token in `app/.env.local`). The classifier auto-routes events that don't carry an explicit `project_id`. Unclassified events surface at **<http://localhost:3000/projects/unclassified>** for you to triage manually.

Seed script lives at `Atlas/app/scripts/seed_projects_2026_05_19.mjs` if you want to audit what got inserted.

— Atlas