FDE COMMONS/by AIR

PRACTICE

Diagnose the problem.
Prove the fix.

Forward-deployed work is ambiguous, cross-functional, and failure-prone. Practice should be too.

01 · 14 labs

Failure Labs

Break a running system, diagnose the mechanism, fix the invariant, and prove recovery.

Open →02 · 2 scenarios

Customer scenarios

Turn an ambiguous customer request into constraints, architecture, and an outcome contract.

Open →03 · decision practice

Architecture decisions

Choose between plausible designs and defend the tradeoff under real constraints.

Open →04 · proof template

Field Report

Package the problem, system, failures, measurements, limitations, and evidence.

Open →

PRACTICE LOOP

Failure-driven, not quiz-driven.

  1. Understand
  2. Diagnose
  3. Fix
  4. Prove
  5. Extend
  6. Publish

CUSTOMER SCENARIOS

Start with incomplete information.

FOUNDATION

The account agent that cannot act

A support leader wants an agent to resolve account issues, but permissions, escalation, and the actual system of record are unclear.

  • Define the safe authority boundary
  • Map missing stakeholder signals
  • Propose an observable first release
INTERMEDIATE

The migration with no rollback window

An enterprise team wants an AI-assisted repository migration across hundreds of services while release work continues.

  • Shape checkpoints and evidence
  • Choose human control points
  • Define proof beyond “tests pass”

THE OUTPUT

The artifact is the credential.

No completion certificate. Publish a reproducible Field Report demonstrating problem clarity, architecture, failure reasoning, evaluation, evidence, security, operations, and tradeoffs.

Build your Field Report →