ALL MEMOS Download .docx

HERALD First-Run Audit — Monday Dormant-Task Sweep

Run date: 2026-04-21 (Monday)

Run ID: MON-SWEEP (manual first run — cron not yet registered)

Registry scanned: F:/TITAN/plans/task-registry/TASK-REGISTRY-2026-04-21.md

Threshold: 7 days (HERALD_DORMANT_DAYS=7), critical: 14 days (HERALD_CRITICAL_DORMANT_DAYS=14)

Protocol note: The task registry was created 2026-04-21 (today). All tasks were filed today. Dormancy age is therefore 0 days for every task — none breach the 7-day threshold by calendar. However this is a first-run audit, so HERALD is also assessing structural readiness and pre-flagging tasks that are at risk of becoming dormant given their blocker profile.

---

Summary

| Metric | Count |

|---|---|

| Total tasks scanned | 11 |

| Closed / resolved | 3 (T007-closed, T009, T010) |

| Open tasks | 8 (T001, T002, T002-ImprovMX, T003, T004, T005, T006, T008, T011) |

| Dormant (> 7 days, no motion) | 0 — registry is 0 days old |

| Critical (> 14 days) | 0 |

| Pre-flagged at-risk (structural blockers, no path forward without Harnoor action) | 6 |

| T-number protocol compliance | Good — all tasks have T-numbers, statuses, and "Blocked on" fields |

---

Task Status Table

| T-number | Name | Status | Age (days) | Blocked on | HERALD Assessment |

|---|---|---|---|---|---|

| T001 | SI Leads: deploy target | open | 0 | Harnoor AWS account decision | At-risk: no code can ship without this. Needs reply. |

| T002 | SES sender address | open (default executed) | 0 | Harnoor confirm sender + inbound strategy | Partial progress. Core SES verified. Low urgency now. |

| T002-ImprovMX | ImprovMX inbound setup | partial | 0 | Harnoor browser step at improvmx.com | Manual step required. Will stall unless Harnoor acts soon. |

| T003 | SSO provider choice | open (default executed) | 0 | Harnoor confirm provider + IdP creds (Google, Apple) | Foundation built. IdP creds are human-gated. Monitor weekly. |

| T004 | Admin dashboard auth | open | 0 | Harnoor reply | Low blast radius (MVP ships with ADMIN_TOKEN default). Low urgency. |

| T005 | Voice MVP rollout | open | 0 | Harnoor reply | Default (10% feature flag) is safe. Monitor voice cost at scale once live. |

| T006 | Voice M2 WebSocket timing | open | 0 | Harnoor reply (T005 must close first) | Slotted May 1. No urgency until T005 closes. |

| T007 (original) | variants.py HTML/JS template refactor | audit in flight | 0 | None — proceeds by default | Default solution (node --check in Makefile) is in place. Refactor is deferred. No blocker. |

| T008 | Per-bubble feedback signal | open | 0 | Harnoor reply | Default (daily rating + sentinel) is running. Revisit if rating response rate < 8% at day 7. |

| T009 | Dashboard subdomain | closed | 0 | — | Deployed 2026-04-21. No action needed. |

| T010 | variants.py bootstrap | closed (wave 1) | 0 | Wave 2 needs Harnoor approval | Wave 1 complete. Wave 2 is gated — watch for drift if not approved within 2 weeks. |

| T011 | Model-tiering review | ready for review | 0 | Harnoor review + approval | Memo written. Highest-value pending decision. Should be reviewed this week. |

---

Pre-Flagged At-Risk Tasks (will become dormant if no motion by 2026-04-28)

These are tasks that HERALD predicts will breach the 7-day threshold absent Harnoor action. Sorted by blast radius.

1. T001 — SI Leads deploy target (HIGH blast radius)

• Risk: The silentinfinity-leads Lambda + DDB stack is undeployed. The leads form on silentinfinity.com cannot capture emails until T001 is resolved. Every day of delay = lost leads.
• Recommended action: Harnoor replies with AWS account preference. FORGE ships within 1 day of reply.
• Days until dormant: 7 (by 2026-04-28)

2. T011 — Model-tiering strategy review (HIGH value, low urgency)

• Risk: DARWIN's proposal is ready. If Harnoor doesn't review within 2 weeks, the variants.py wave-2 work will drift further from the proposal and require re-scoping.
• Recommended action: 15-minute read of DARWIN-MODEL-TIERING-PROPOSAL-v1-2026-04-21_SUMMARY.md. Reply T011 approve or T011 needs changes.
• Days until dormant: 7 (by 2026-04-28)

3. T002-ImprovMX — Inbound email (MEDIUM blast radius)

• Risk: MX records are already live pointing to ImprovMX. If the ImprovMX domain claim is never completed, the MX records are pointing at an unclaimed domain — mail to contact@silentinfinity.com will silently fail to reach ImprovMX, falling through to the SES bounce MX at priority-30. This is not data loss (SES bounces cleanly) but means contact@ is non-functional as an inbox.
• Recommended action: Complete the 6-step runbook at F:/TITAN/plans/task-registry/T002-improvmx-setup.md. Steps 1-2 take under 5 minutes.
• Days until dormant: 7 (by 2026-04-28)

4. T003 — SSO IdP credentials (MEDIUM blast radius)

• Risk: Google and Apple Sign-In are blocked on developer console steps only Harnoor can do. Foundation (Cognito, custom domain, ACM cert) is deployed. Without IdP creds, auth.silentinfinity.com only offers email magic-link (Resend). Not a blocker for launch but needed before any growth push.
• Recommended action: Complete T003-Google-creds (console.cloud.google.com, ~15 min). Apple can wait until Apple Developer account is funded.
• Days until dormant: 7 (by 2026-04-28)

5. T010 wave-2 — variants.py migration scope (MEDIUM)

• Risk: Wave 1 is shipped. Wave 2 (handler.py model routing, system_v1.md lookup, voice adapter swap, frontend variant fetch, pricing.py, crisis-patterns) is queued but unscoped. Without approval, FORGE may ship wave-2 items ad-hoc without registry wiring — defeating the modularity prime directive.
• Recommended action: Harnoor reviews wave-2 scope (listed in T010 entry) and replies T010 wave-2 approved or scopes it down.
• Days until dormant: 7 (by 2026-04-28)

6. T005 — Voice MVP rollout (MEDIUM)

• Risk: Voice is gated at 10% behind a feature flag per default. If Harnoor wants to open it wider (or narrower), the window to do so before the first real users experience the gate is closing. Feature-flag decisions made post-launch are messier than pre-launch ones.
• Recommended action: Harnoor replies with rollout percentage preference before any marketing push.
• Days until dormant: 7 (by 2026-04-28)

---

Structural Observations

Observation 1 — Registry has no last_updated timestamps in task bodies

The TASK-REGISTRY-2026-04-21.md entries don't include a machine-parseable last_updated: YYYY-MM-DD field. HERALD currently falls back to file mtime, which reflects the last time the whole file was touched — not the last time an individual task changed. As tasks accumulate, file mtime becomes a poor proxy: editing T001 refreshes T011's apparent motion.

Recommendation: Add last_updated: YYYY-MM-DD as a required field to each task entry. HERALD will parse this field preferentially. This is a low-effort convention change — no schema enforcement needed, just a note in the registry header.

Observation 2 — Two tasks are "in flight" rather than "open" or "in_progress"

T007 (original) is labeled "audit in flight" and T010 is "bootstrap complete, wave 2 queued." Neither maps cleanly to open or in_progress. HERALD's dormancy check uses status in ("open", "in_progress") — these states might be missed by a strict string match.

Recommendation: Standardize statuses to: open | in_progress | blocked | ready_for_review | closed. T007-original → in_progress. T010-wave2 → ready_for_review. T011 → ready_for_review.

Observation 3 — The task registry is a single flat file with no date-indexed history

As tasks close and new ones open, the single-file format will become unwieldy. Closed tasks accumulate inline. There is no weekly snapshot mechanism.

Recommendation (for HERALD v2 rhythm spec): On the first Monday of each month, HERALD archives the previous month's closed tasks to F:/TITAN/plans/task-registry/archive/TASK-REGISTRY-YYYY-MM-closed.md and starts a fresh registry. Keeps the active file scannable.

---

Next HERALD Run

• Tuesday 2026-04-22 09:00 ET — TUE-REDTEAM production audit (once cron is registered)
• Until cron is registered: Manual trigger by Harnoor or TITAN orchestrator

---

_HERALD first-run audit — produced by SCOUT on 2026-04-21 · referenced in HERALD-WEEKLY-RHYTHM-v1.md_