Skip to content
arula

Arula / Learning design / Lab 2

Stage
Concept Map.

Standard intuition. Standardized language. Established behavior change.

The master map

01 / The master map

Change the way you<br/>think, speak, and work.

00
DEFINE~10 min

Frame the Boundary

Standard intuition

“I don’t know what’s true here yet, and neither does the agent.” Authority is something you establish before you act — not something you discover from the output.

Standardized language

  • Grounding / Stage Zero
  • Workbench
  • Journey
  • Non-negotiables
  • seam
  • Contract
  • authority

Established behavior change

Before opening an agent, write down what is authoritative, what is in scope, and what is explicitly out.

01
DEFINE~20 min

Map the Seam

Standard intuition

One agent holding two repos will sound confident and be shallow. Disagreement between two scoped reports is the signal, not the noise.

Standardized language

  • Sub-agent (not Agent)
  • Repo Context Compressor
  • Context window
  • claim-not-fact
  • Judgment triad: confirmed requirement / documented assumption / unresolved ambiguity
  • seam ledger
  • contract drift
  • generated client

Established behavior change

Never hand one agent two repositories. Run scoped sub-agents, reconcile the returns yourself, and record disagreements rather than silently resolving them.

02
DEFINE~20 min

Make the Spec Buildable

Standard intuition

Absence is invisible. Code shows you what exists; only the written requirements show you what’s missing.

Standardized language

  • Spec Craft → LLD
  • Solution Intent
  • Acceptance criteria → story Given/When/Then
  • unresolved ambiguity
  • Non-negotiables
  • ⚠ ownership ruling

Established behavior change

Read the requirements against the code hunting for absence. Escalate an unresolved ambiguity instead of letting the agent fill the gap.

03
PLAN~15 min

Design the Orchestration

Standard intuition

More agents is not orchestration. Orchestration is deciding who knows what. And a change can be correct in its final state and still unsafe while it’s rolling out.

Standardized language

  • /plan (not program planning)
  • ⚠ agent orchestration
  • ⚠ context isolation
  • ⚠ rollout order
  • ⚠ compatibility window

Established behavior change

Decide and write down the release order before any code is written.

04
EXECUTE~30 min

Build the Bounded Slice

Standard intuition

A helpful agent is a dangerous agent. Proximity is not permission.

Standardized language

  • Plausible helplessness
  • Rule / Hook / Gate (the contrast set)
  • Build
  • Non-negotiables

Established behavior change

Review every diff for scope before you review it for correctness. If it touches something you didn’t authorize, revert — don’t rationalize.

05
JUDGE~20 min

Prove the Pair

Standard intuition

Both halves can be right and the whole still wrong. The builder cannot be the judge.

Standardized language

  • Sycophancy
  • PR Reviewer / Secure Code Reviewer (zero-context reviewer)
  • Idempotency
  • fresh context

Established behavior change

Run a zero-context reviewer against the pair on every cross-repo change. Demand evidence, not assertion.

06
JUDGE + LEARN~5 min

Transfer the Learning

Standard intuition

The next person — or the next agent — either inherits your context or re-derives it badly.

Standardized language

  • Handoff (not Journey)
  • Judgment
  • Non-negotiables

Established behavior change

Write the handoff before closing the change: decisions made, evidence produced, what’s still open.

02 / Across all seven stages

The Determinism Ladder.

  1. Prompt
  2. Rule
  3. Gate

The Determinism Ladder — prompt → rule → gate runs underneath all seven rather than belonging to one.

Its intuition

Every time you move a decision out of “I asked the agent nicely” and into “the system won’t allow it,” you’ve made a permanent improvement instead of a hopeful one.

The companion documentLearning Architecture & Stage Overview