Usecases

What happens when platforms meet the mission.

Illustrative composites until named clients publish. Each story is Challenge → Platform → FDE → Outcome—the same thesis as industry pages.

Cases

Challenge → Platform → FDE → Outcome

Game

Align → Prove → Ship · Develop/Review/Fix

FDE role: Owned concept-to-slice delivery, context packs, Plan ceremonies, and review disposition with studio leads.

Challenge: A studio needed a shippable vertical slice—design and engineering under one gated loop—not pitch decks and unreviewed agent dumps into the build pipeline.
FDE method: Embedded FDEs Align on concept and success signals with design and eng leads; Prove a playable thin slice; Ship MLP content and features with Develop / Review / Fix.
Platform: Ask/Explore for systems research; Plan for scope lock; Build with role agents; Design Mode and Browser where UI mattered; Agent Review before every drop.
Outcome: Faster gated content and feature loops, shared review findings for leads, and an agentic cadence the studio could keep after the embed.

Modernization

Discover → Architecture → Sprint → QA · Align→Prove→Ship

FDE role: Led brownfield mapping, PHI-aware context engineering, strangler Plan/Build, and enablement of client eng on review gates.

Challenge: A healthcare company was stuck on a legacy clinical/ops product: compliance-sensitive data paths, brittle releases, and slow feature delivery.
FDE method: FDEs mapped the as-is system in Ask, engineered context with path grants away from PHI stores, Planned strangler cuts, Built thin modern slices, and held Agent Review as the merge gate.
Platform: Local-first agents in the client environment; BYOK under security policy; path grants and run policy; companion for plan/usage admin; Agent Review on every generative cut.
Outcome: A modernized product path with bounded risk, faster evidence-backed releases, and client engineers trained to keep the gated GenAI SDLC.

Product

Brief → Spec → Sprint → Develop/Review/Fix

FDE role: Installed Plan-before-Build discipline, co-owned MLP stories, and transferred review ceremonies to the client squad.

Challenge: A B2B product team shipped assistant-generated PRs that skipped scope lock and created expensive rework.
FDE method: Embedded FDEs Align on success signals with product and eng; Prove a thin slice under Plan and Debug; Ship MLP with story loops and a hard Definition of Done.
Platform: software_dev pack, Plan approvals, multi-model BYOK, companion history for stakeholder plan review, Agent Review before merge.
Outcome: Less rework after Plan approval; clearer evidence at each story gate; client squad kept the Plan → Build → Review loop after the embed.

Modernization

Align → Prove → Ship

FDE role: Owned strangler planning, context engineering, and review disposition with OEM leads.

Challenge: OEM digital services lagged expectations while legacy stacks made big-bang rewrites unacceptable.
FDE method: FDEs Align with product and platform leads, Prove a thin connected-service slice, Ship under Align → Prove → Ship with enablement.
Platform: Ask/Explore mapping; context packs and path grants; Plan strangler cuts; Build thin modern slices; Agent Review before every drop.
Outcome: Modernized service path with bounded risk, faster gated releases, and a cadence the OEM team could keep.