Workflow App Sprint Category
Onboarding Readiness Gate
For customer success and implementation teams that need one readiness handoff before launch, go-live, or customer expansion.
The workflow
Where this breaks today.
Current failure mode
Launch readiness depends on scattered implementation status, training notes, security review, integration blockers, and owner judgment.
Focused app surface
A readiness intake, review rulebook, Decision Record, and CS handoff that returns ready, blocked, or review required.
Runtime or record layer
Binding mode: decision_record_only. Customer executable rulebooks are outside the current production contract.
Example boundary
What the app decides or hands off.
Account has target launch date, integration status, training state, security review, blockers, owner, urgency, and missing inputs.
Ready, blocked, or review required before implementation moves the account to go-live.
One unclear go-live call can create churn risk, support load, customer-facing confusion, and avoidable implementation rework.
What ships
One useful workflow surface, not a broad project.
Trigger, current path, owner, failure modes, and the boundary where work should proceed, block, review, or route.
Required fields, evidence standard, missing-input states, and examples of acceptable requests.
Direct declarative Rulebook v1, trusted-adapter fact contract, or Decision Record-only path depending on the workflow.
A focused Krafthaus page, notary, packet builder, score, dashboard row, or handoff artifact the team can review.
What gets stored, where the record travels, and who or what receives the next action.
What to automate, measure, or turn into repeat runtime usage after the first workflow proves useful.
Trust boundary
Start with metadata and handoff shape.
Runs on readiness metadata first. Private customer documents can remain in the existing implementation system.
One workflow
The sprint deliberately avoids broad AI transformation, platform rebuilds, or customer executable rulebooks.
Metadata first
The first sprint can use request metadata, policy fields, evidence status, owner, risk, and desired handoff before private-system integration.
15-minute review
The low-friction next step is to confirm the workflow owner, required inputs, Decide binding, and whether a Krafthaus surface is worth scoping.
Workflow App Sprint
Map your version of Onboarding Readiness Gate.
Use this category as the public pattern. The company-specific artifact comes after the workflow is real enough to review.