Workflow App Sprint Category
Procurement Exception Gate
For finance, procurement, and operations teams that need one governed exception path before spend or payment moves.
The workflow
Where this breaks today.
Current failure mode
Invoices, vendor choices, purchase requests, mismatch reviews, and exception approvals move through email, Slack, and spreadsheets.
Focused app surface
An exception intake, approval rulebook, Decision Record, and finance handoff that returns approve, block, review, or missing evidence.
Runtime or record layer
Binding mode: trusted_adapter_facts_then_declarative_rulebook. Customer executable rulebooks are outside the current production contract.
Example boundary
What the app decides or hands off.
Request includes vendor, amount, budget owner, PO or invoice state, mismatch type, urgency, policy exception, and missing evidence.
Approve, block, request evidence, or route to finance, procurement, legal, or budget owner before payment or spend advances.
One bad payment exception, unsupported vendor term, or missed mismatch can cost more than the sprint.
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 spend metadata first. Full accounting exports, contracts, and private bank data are not required for the first sprint.
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 Procurement Exception Gate.
Use this category as the public pattern. The company-specific artifact comes after the workflow is real enough to review.