Skip to main content

EP10. Architecture-Driven Generation Activity

🏛️ Breaking Up With the "Just Write It" Black Box​

"Write a report."

Latest models spit out dozens of plausible pages in seconds—title, outline, body. Read carefully and you shake your head: logic leaps, uneven depth, no sharp through-line. "Make it longer" only adds volume, not satisfaction.

If Socratic learning trains metacognition, Cocrates' second great axis—artifact generation—blocks mindless generation by design. Cocrates is clear: good artifacts come only from solid architecture—and architecture is a set of human decisions.

🏗️ What "Just Write It" Really Means: Write Whatever​

An architect who stacks bricks without questions builds a house with the bathroom window facing the living room. Generating without structure is the same gamble.

Architecture-less output breeds three fatal problems:

  • Collapsed logic and consistency: AI writes the plausible next sentence—not a coherent whole. Sections fight each other.
  • Lost accountability: When someone asks "why this flow?" you can't answer—AI chose the architecture, not you.
  • Unreviewable black box: No blueprint means no verification—only "does it read smoothly?"

🔍 ASR: Making Vague Architecture Concrete​

"Design architecture first—sounds right, but design what?"

Cocrates uses ASR (Architecturally Significant Requirement)—constraints that materially change composition, quality, and delivery.

  • Report ASR: "Audience is C-suite" → density of summary, conclusion-first structure.
  • Deck ASR: "Exactly 10 minutes" → slide count, governing message limits.
  • Tech blog ASR: "Junior developers" → depth of jargon explanation, ratio of analogy.

Skip explicit ASR and AI fills silence with silent defaults—"reasonable enough" choices you never approved. Move without marking what's fragile (ASR) and the mover stacks books on your glassware.

🏡 Four Layers—Like Building a House​

[Identify concerns / ASR] → [ADR: alternatives & decision] → [Spec: integrated blueprint] → [Generation & Verification]

  • 1. Concern / ASR: Surface big structural forks—one story vs. two, roof vs. rooftop room.
  • 2. ADR (Any Decision Record): For delegated areas, lay out 2–3 real options with trade-offs; user decides; audit trail recorded.
  • 3. Spec: Merge approved requirements and ADRs into one self-contained blueprint—build without re-reading the whole chat.
  • 4. Generation & Verification: Generate from approved spec only, not the first prompt. Then verify item by item—and catch undocumented ASR smuggled in by AI.

📝 Three-Line Summary​

  1. "Just write it" = "write anything." Architecture-less generation is an uncontrollable black box.
  2. Break silent defaults. Identify ASR; run ADR before building.
  3. Cocrates doesn't sideline humans. Every step—you review, decide, approve. You own the blueprint.

🎬 Coming Up Next​

We've covered why the architecture pipeline exists. Next: the four specialist skills—adr-writing, spec-writing, spec-driven-generation, spec-driven-verification—templates and rules inside.

"Squeeze out architecture before you write. If architecture holds, content won't shake."

This series introduces the Cocrates Harness framework. Cocrates is an agent harness designed for Socratic dialogue so users keep agency and grow.