From vague client mess to a build-ready field pack.
A calmer front door for the FDE idea: capture the hunch, ground it in rb2 context, challenge it from two perspectives, then compile one reviewable handover pack.
fieldpack.rb2.demo
Case: insurance email routing
Two FTE tied up in manual classification, policy lookup, enrichment, and cross-department routing.
1
Capture field evidenceNotes, transcripts, KPIs, screenshots.
ready
2
Ground in rb2 contextPrecedents, delivery patterns, source separation.
mocked
3
Run tension reviewClient ambition vs rb2 delivery realism.
queued
4
Compile handover packSlice, architecture sketch, ADRs, open questions.
draft
The dashboard is not one cramped screen. It is a set of control planes.
Each plane owns one decision layer. Operators move through them in sequence, but can always inspect sources and review generated artifacts before anything leaves the system.
FieldPack should feel less like a chatbot and more like an operating console for the first two weeks of an FDE pod.
Landing job
Explain the concept fast enough to share with the team and make the service model feel tangible.
Dashboard job
Make the workflow feel controllable: sources, choices, guardrails, and artifacts are visible at every step.
FieldPack /Intake plane
Intake plane
Capture just enough field evidence to turn a sales hunch into a concrete case.
FieldPack run mockedThe plane state changed and a demo log entry was updated.