Editorial Recap · Vol. I · № 02 April 23, 2026
Internal Briefing · Impromptu Team Call

From vibe coding to systems thinking.

A two-and-a-half-hour course rewrites how the team plans every project — and a couple of dashboards get fixed along the way.

Featuring · JC · Micah · Gio · Benzo Recording ↗
// THE FRAMEWORK

Every system,
just seven blocks.

Task blocks · ways to do work
01

Service

Immediate, user-facing work. API endpoints, request/response, sub-second.

02

Worker

Background processing. Job tracking, status, anything that can wait.

Storage blocks · ways to keep data
03

Key-Value

Constant-time lookups. Caching, sessions, fast reads.

04

File Store

Large blobs with metadata kept separately.

05

Queue

Ordered messages, event-driven dispatch.

06

Relational

Structured data with relationships. ACID guarantees.

07

Vector

Similarity search. Embeddings. The AI substrate.

The Insight

There are only two ways to do work — but many ways to store the answers.

2

Task Blocks

Now or later. Service or Worker. That's the entire surface area of how work gets done.

5

Storage Blocks

Because "where should this live?" has many right answers, each shaped by access pattern, scale, and consistency needs.

The Role Shift

You're the pilot now.
Claude is the builder.

// PILOT

You

Design the architecture. Specify the blocks. Write the PRD. Strategic planning, system shape, the call on what goes where and why.

// BUILDER

Claude

Implements what the PRD says. Translates blocks into code. Fast, literal, scales with the quality of the spec it's given.

"The planning phase becomes the hardest, most critical part. Implementation falls out clean."

For You
The New PRD

Two questions,
asked first.

1.

Is this about doing work, or storing data?

2.

What are the specific access patterns and performance requirements?

Answer those well, and the right blocks fall out. Hand the blocks to Claude and the implementation is a routine translation. Skip them, and you're vibe-coding in a more expensive chair.

The Blueprint

Patterns are
technology-agnostic.

Block
Common implementations
Service
FastAPI · Django
Worker
Celery · Sidekiq
Key-Value
Redis
File Store
S3
Queue
Kafka
Relational DB
Postgres
Vector DB
Pinecone · Weaviate · pgvector
Apply The Lens

Our projects, re-described.

Same systems we already shipped — now seen through the framework.

Case Study · 01

PD Dashboard
(burndown chart)

Blocks: Relational Key-Value

Sprints and tasks are structured data with relationships — Postgres territory. Hot reads for the dashboard view get a Redis cache so we don't hammer the relational store every render.

Case Study · 02

Chatbot

Blocks: Vector

Already running similarity search on embeddings. The pattern was always there — we just didn't have the name for it. Now we do.

For You
// DEPLOYMENT NOTE

Why we push to helpflow-dev.

push to helpflow/pd-dashboard × Vercel can't see it
└─ billing-account owner lacks org write
push to helpflow-dev/pd-dashboard ✓ Vercel deploys
└─ billing-account owner has access here

The HelpFlow org repo is the source of truth for the team, but the account that pays Vercel can't write to it. helpflow-dev (personal) is the bridge — it's what Vercel actually pulls from. Until permissions get reshuffled, this is the path.

// vercel.json — Asana sync was hitting the default 10s serverless cap.
"functions": { "api/sync.ts": { "maxDuration": 60 } }
Business Update
30 days

Veneers goes dark.

The B Premium client gave a 30-day shutdown notice, and Veneers itself is winding down — not switching providers, not pausing, fully closing. Their bot was basic relative to what we build now, so there's nothing to migrate or salvage. We let it run out the clock.

For You
On The Clock
SAT · 8 AM

PST · client website launch

A dev gets dropped into a temporary Slack channel for the launch window. The client's own dev team owns the website. We're there for one thing.

Scope guardrail

GTM-related issues only. Website bugs go back to their dev team. Hold the line.

Shipped This Week

Filter,
freed.

Closing Ledger

Commitments
on the table.

Owner · ItemDue
JCResume systems-thinking course videos with the teamNEXT WEEK
JCPush PD Dashboard updates via helpflow-dev (Vercel-visible path)ROLLING
JCAdd maxDuration to vercel.json so Asana sync clears the 10s capASAP
GioGet a dev added to client launch Slack channel · field GTM issues onlySAT 8AM PST
TeamHelp Karim with pending test casesTHIS WEEK
TeamAdopt the two-question PRD discipline before any new buildGOING FORWARD
—Veneers (B Premium) winds down · no migration, no save+30 DAYS

— end of edition —