Internal Briefing

AIDLC Council
Meeting

Screenflow, the 2-Builder Pipeline, & Quality Control.

Kacha HanchanaFriday, June 19, 2026

02The Problem

The Failure of Static Design Docs (Spec Drift)

Design docs promise a shared source of truth, then quietly fall out of sync with the code. The gap between what is written and what runs is where projects start to drift.

01

Ghost documents

Docs that sit outside the dev loop become orphaned - nobody opens them, so they stop describing the system that actually ships.

02

Post-hoc documentation

Specs written after implementation describe what was built, not what to build. They lose all value as a guide for the next change.

03

The post-AI choice problem

AI assistants make architectural choices the spec never anticipated, so the document and the codebase diverge faster than ever.

04

Technical debt accumulation

Every iteration without a living spec adds another truth gap, and the gaps compound until the docs are actively misleading.

03The Problem

Document Theater vs. Living Truth

A document that looks authoritative but no longer matches the system is theater. Real truth lives where the system is defined - in the repo, not the markdown.

01

Static rot

Design diagrams begin rotting the moment production code is written against them. The picture freezes; the system keeps moving.

02

Ambiguity failure

Static specs can't absorb production-level change and ambiguity. The first real edge case the doc didn't foresee breaks its authority.

03

Siloed information

Post-facto documentation is disconnected from system state - a snapshot in a silo, never reconciled against what is live.

04

SSOT failure

When the Single Source of Truth is a markdown file but the actual truth is in the repo, the SSOT is a label, not a fact.

04Experience Architecture

Debunking the Screenflow

A screen is no longer a static destination. We treat the flow as a living surface that reacts to user state and the model's intent, so the path bends to the person, not the wireframe.

Dynamic user state

Every screen reads from a shared state machine - intent, context, and history - so what renders next is decided live, never hard-routed.

Mapping AI interactions

We chart where the model speaks, suggests, or acts, and define the hand-back to the user at each touchpoint so control is always legible.

Fluid experiences

Transitions follow the user's momentum. Loading, branching, and recovery are designed states, not afterthoughts.

05Team Topology

The 2-Builder Pipeline

Two roles, one continuous track. The Product Builder shapes the what; the Tech Builder shapes the how. The value is in a clean, lossless handover between them.

Product Builder

Defines the intent

Owns screenflow, copy, and user states
Specifies AI behavior and guardrails
Validates against the real user job

Tech Builder

Realizes the system

Implements the state machine + data
Wires model calls, tools, and fallbacks
Hardens for performance and edge cases

Seamless handover: a single shared spec - states, contracts, and acceptance checks - travels with the work, so nothing is re-derived and no intent is lost in translation.

06Reliability

Quality Control Framework

Quality is enforced in layers. Machines catch the deterministic failures, humans judge the ambiguous ones, and a consistency pass keeps the whole product speaking with one voice.

Automated verification

Schema, contract, and regression checks run on every change. Failures block the handover before they ever reach a reviewer.

Human-in-the-loop

Reviewers adjudicate the gray areas - tone, judgment, edge cases - and their rulings feed back as new automated checks.

Consistency checks

A cross-flow pass audits naming, states, and behavior so the product feels designed by one team, not stitched together.

07Cadence & Delivery

AIDLC Tracking & Roadmap

We keep the loop tight with a weekly sync and a dated roadmap that carries us through August.

Friday Syncs

Weekly working session to unblock builders, review QC signal, and re-rank the roadmap.

LocationRoom P2

June 2026Now
Screenflow v1 + pipeline live
Shared spec format adopted; first flows shipped through both builders.
July 2026
QC framework rollout
Automated gates enforced on every handover; human review queue established.
August 2026
Scale & scenario coverage
Consistency checks across all flows; roadmap re-baselined for Q4.

08Forward Plan

Strategic Next Steps

Three moves to compound what the pipeline already gives us: cover more of reality, sharpen the build loop, and make quality scale without scaling headcount.

01

Scenario mapping

Inventory the real user journeys and AI branch points, then prioritize the flows with the highest leverage and risk.

02

IDE optimization

Tighten the builder toolchain - spec-aware editors, instant preview, and inline checks - so handover friction trends to zero.

03

Scaling QC

Promote recurring human rulings into automated gates so coverage grows while manual review shrinks.

Owners assigned at the next Friday sync - Room P2.

AIDLC CouncilMeeting

AIDLC Council
Meeting