Workflow App Sprint Category
Compliance Document Review Gate
For operations, compliance, security, legal ops, and customer teams that need a clearer review-ready handoff.
The workflow
Where this breaks today.
Current failure mode
Cases, questionnaires, evidence packets, and policy reviews advance before owner, missing evidence, deadline, and risk state are clear.
Focused app surface
A review intake, readiness rulebook, Decision Record, and owner handoff that returns ready, missing evidence, escalation, or blocked.
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.
Request includes document type, evidence packet, policy or risk notes, missing fields, reviewer owner, deadline, and current stage.
Ready for review, missing evidence, reviewer escalation, or blocked before the document or case advances.
Missing evidence, unclear reviewer ownership, or a bad readiness call creates rework, delays, and audit risk.
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 review metadata first. Sensitive documents can stay in the existing system while Krafthaus models readiness, owner, evidence state, and handoff.
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 Compliance Document Review Gate.
Use this category as the public pattern. The company-specific artifact comes after the workflow is real enough to review.