Plan

Fix Plan

Four phases to close the gaps found in the audit. Orange means I need your Y before anything live is written.

✎ Edit the text version
Flowchart
Drawing…
Four phases, left to right

Orange tag = I need your Y before I write to a live system. Grey "G" tags = which gap the step closes (hover for the name).

TodayEach under an hour
Push the 28 unpushed commits to a backup branch
Claude5 minneeds your Y

Removes the one-laptop risk. KPI fixes, plan, prototype and audit are in those commits.

Closes: G2
Security cleanup
Harsh15 minneeds your Y

Details are shared privately with Harsh.

Closes: G3
Fix the 1 Nov clock change
Claude20 minneeds your Y

Only the daily checklist runs on UTC; the other five already use Chicago time. Move it to a Chicago schedule. Deadline: Sun 1 Nov. Then check Automation 2 on Mon 2 Nov.

Closes: G8
Tell me what the hermes-agent server is
Harsh2 minno write

It has run since 9 Aug and is in no doc. If unused I stop it (not delete). Also check when the AWS credits end: $27.80 a month is free only until then.

Closes: G15
→
This weekAbout 2.5 days of Claude time
Read-only morning check
Claude1 dayno write

Every morning one message: Lambda errors, Airtable runs, sheet freshness, deployed code equals repo. Reads only, writes nothing.

Closes: G1 G10
Repair the numbers at the source
Claude + Nakul0.5 dayneeds your Y

Fix the 1,000 cap in the weekly snapshot, pick one Deal Review date (687 vs 111 leads), align call counts to Nakul's method.

Closes: G4
Tighten AWS access
Claude1 hourneeds your Y

Details are shared privately with Harsh. Also add alarms to the 3 Lambdas without one.

Closes: G14
KPI Daily tab: dry run, then live
Claude1 dayneeds your Y

Auto-filled daily KPIs replace the dead Daily Input tabs. Plan: knowledge/plans/kpi-daily-weekly-plan.md.

→
Next 2 weeksAbout 4 days of Claude time
Lead Speed: stamp P0 and Research first
Claude, after Nakul approves2 daysneeds your Y

Permanent dates, never overwritten. Needs Nakul's 4 decisions on the plan page.

Closes: G5
One archive pass
Harsh decides, Claude moves0.5 dayneeds your Y

Move, never delete: 5 off automations, old Tasks A-J, dead tabs, 19 scratch files, the unused public Lambda URL.

Closes: G9
One source for tiers, docs refreshed
Claude1 dayno write

One tier definition plus a test that fails when copies disagree. Docs dated and corrected.

Closes: G6 G11
Cost sheet
Claude + Harsh1 hourno write

AWS bill is read-only. Airtable and GHL plan costs come from you.

Closes: G12
→
Later (blueprint)Only after the morning check exists
Write gateway for Airtable, GHL, Sheets
Claude3-4 daysneeds your Y

Every write passes plan, approve, apply, verify. Today the hooks are the only guard.

Closes: G7
Named owner and backup for each human step
Harsh30 minno write

Dashboard paste, Smart Skip email, EOD typing, merges.

Closes: G13
CI and the rest of the 24x7 layer
Claude1-2 weeksneeds your Y

Needs GitHub Pro (about $4 a month) for branch protection. Blueprint P1.5, P6, P7.

How many gaps close, and when

Bar width = gaps closed in that phase.

4Today
4This week
5Next 2 weeks
2Later (blueprint)

Gaps closed, running total: Today 4/15 → This week 8/15 → Next 2 weeks 13/15 → Later (blueprint) 15/15

Gap by gap

Is it in the blueprint, and where does it land in this plan.

GapWhatIn the blueprint?Closed in
G1Nothing watches the automationsPlannedThis week
G2One laptop holds recent workPartly plannedToday
G3Secrets and keys need cleanupConflicts with a decisionToday
G4The same KPI has four answersPlannedThis week
G5Lead-speed dates are missing or overwrittenNo stepNext 2 weeks
G6Business rules are copied in 4+ placesPartly plannedNext 2 weeks
G7Scripts bypass the write guardPlannedLater (blueprint)
G8Daylight saving on 1 NovPlannedToday
G9Dead and half-built things are not retiredNo stepNext 2 weeks
G10Deploys are by hand, drift goes unseenPartly plannedThis week
G11Docs disagree with each other and with the systemPlannedNext 2 weeks
G12Cost is invisibleNo stepNext 2 weeks
G13Human steps are hidden single pointsPartly plannedLater (blueprint)
G14AWS access needs tighteningPlannedThis week
G15A running server nobody documented, and a credit cliffNo stepToday
Total effort: about 1 hour today, 2.5 days this week, 4 days over the next 2 weeks. The blueprint's full 24x7 layer is weeks more and only makes sense after the morning check proves useful.