Playbook › Track 2: Business & logic layer
Track 2: Business & logic layer
Track 2: business discovery and the logic layer. Led by the business forward-deployed engineer,
working directly with business stakeholders. This track decides what is worth building, proves what good looks like before anything is built,
and produces the knowledge assets that make the build reusable rather than bespoke.
Step by step
Discover and prioritize
- Stakeholder discovery. Run Discovery sections A, B, and F: workflows and pain, the client's own lifecycle language, and where humans must review no matter what.
- Capability prioritization. Score candidate capabilities on volume, pain, and feasibility; produce the capability heatmap and the shortlist for the first ninety days.
Triage against the ontology
- Ontology triage, three ways. Every finding is classified: consistent with the industry ontology (truth: adopt as is, pin the release), varies by firm (an overlay candidate, domain-specific or function-specific), or contradicts the ontology (recorded as a conscious business-model decision on the Decision Register; a contradiction is never a silent fork).
- Build the ontology overlay. The overlay layers on top of the industry ontology without modifying it: domain-specific and function-specific extensions, cut as a versioned release and selected on the plane through the C3 overlay value.
Define good before building
- Roadmap plan. Sequence the heatmap by value and dependency; each roadmap item names its pattern (P1 to P7) and its determination-rule split.
- PRDs written as evals. Every product requirement is stated as a measurable evaluation: golden exemplars, target metrics, and pass thresholds. A requirement that cannot be evaluated is not yet a requirement.
- Capability maturity benchmarks. Baseline today's numbers per capability (time, cost, quality, cycle) and set the target maturity; these become the ninety-day comparison and the operate-phase scorecard.
Execution-phase documentation
- Document workflows, processes, and business logic for each capability entering the build: step sequences, decision points, exception paths, approval semantics. Each element is passed through the determination rule and labeled: deterministic code (to the domain rule library) or judgment (to an agent skill). This documentation is the direct input to agent development in the build phase.
Deliverables
| Deliverable | Lands as |
|---|---|
| Capability heatmap and roadmap | Engagement record; drives C2 use-case activation order |
| Ontology triage record | Truth adoptions, overlay candidates, and register-recorded contradictions |
| Ontology overlay release | Versioned Knowledge release, selected via C3 |
| PRD-evals with golden exemplars | The eval suites that gate every build |
| Maturity benchmarks | Baseline and target per capability |
| Workflow and business-logic documentation | Skill and rule-library inputs for the build phase |
This track uses: Discovery sections A, B, F, and I, the C2 and C3 bands, and the Decision Register for contradictions.