Week of March 16–20, 2026 · Burke ⚡
Repo: github.com/t-and-c/client-grant-intelligence · Live Demo: spark-04ae.tail6ecd0f.ts.net:8443 (Tailnet)
Working product with auth, full onboarding flow, multi-dimensional scoring, eligibility engine, and search UI. Sprint 2 (Grant Discovery & Scoring) is underway — 7 of 12 tasks delivered today, including Grants.gov and SAM.gov connectors, semantic matching with embeddings, and database migrations.
Sprint 2 closes by Tuesday (Mar 25) — 5 remaining tasks in flight (dedup, 5-dim scoring, exec summaries, risk flags, dashboard UI). The autonomous pipeline operates 24/7: agents receive issues, implement, open PRs, CI validates, auto-merge.
Tasks estimated at 136 agent-hours are being delivered at an average 0.09x drag factor — ~12x faster than estimated. Pre-approved architecture docs eliminate rework. Zero human intervention required during implementation.
Focus: feeding Tony's methodology into the pipeline before operating on client repos
Grant Intelligence repo created and CI configured — PRs #1–#6 (deps + GitHub Actions)
First real product feature delivered — scoring package with 97 tests, +2,718 lines
8 product capabilities approved via AIPMO (#22–#29) · Commit-early discipline + stall detection shipped · Dedup hardening (5 fixes)
Grant Intelligence Platform — what's working now
Repo: github.com/t-and-c/client-grant-intelligence · Live Demo: spark-04ae.tail6ecd0f.ts.net:8443 (Tailnet)
Victor tested the product hands-on — all bugs fixed within minutes
API used abbreviated field names (techAlignment, financial) while the frontend schema used full names (technicalAlignment, financialViability). Zod validation rejected Step 4 of onboarding. Root cause: no shared contract between frontend and API — two agents built each side independently.
Clerk middleware tried to validate API keys in the edge runtime even when running in demo mode without keys configured. Blocked all page access. Root cause: demo mode bypass wasn't applied at the middleware layer — only at the component level.
Both bugs were fixed within minutes of Victor's report. The pattern is clear: agents build fast but don't cross-validate contracts between packages. Next steps: E2E acceptance tests (ops #39), shared Zod schemas enforced across frontend/API boundaries, and smoke tests post-merge before marking "delivered."
These are exactly the bugs that automated E2E testing will catch — shifting detection left from human QA to CI pipeline
Pivoted from live Chrome demo recording to polished static PDF demos
Sales deck built around the WWTD methodology. 9 slides, one idea per slide. 3 iterations from generic AI pitch → methodology-first sales narrative.
Real case study: "From Conversation to Working Software." 14 sections showing the full pipeline with real GI data — 8 capabilities decomposed, Efficacy Pareto applied, 475-line architecture document, sprint planning with back-pressure analysis.
9-section client-facing explainer: intake → AI analysis → planning → commitment package → build → ship → feedback loop.
All three PDFs generated by Burke from HTML → PDF pipeline. Next iteration: interactive web versions with live data from the pipeline.
Measuring progress by pipeline events, not calendar days
Decision from Monday meeting: track progress by events (state transitions), not by days
T&C autonomous pipeline vs. equivalent human team (DORA median performers)
| Metric | Industry Median | T&C Pipeline | Delta |
|---|---|---|---|
| Tasks per week | 3–4 (1 sprint) | 17 | ~5× |
| Lead time (issue → merged) | 1–4 weeks | < 24 hours | ~10–20× |
| Drag factor | 1.5–2.0× (over est.) | 0.09× (under est.) | Inverted |
| Human intervention | Constant | Zero (implementation) | ∞ |
| Rework cycles per PR | 2–3 | ~1.5 (AI review) | ~50% less |
| Cost per task | $3–5K (loaded salary) | $2–10 (API tokens) | ~500× |
The combination of pre-approved architecture docs + autonomous agents + event-driven pipeline compresses cycles in ways that traditional teams structurally cannot match
Zero human intervention during implementation — agents operate 24/7 with architecture docs as spec