Each app accepts only the facts needed before the workflow moves. It does not ask an LLM to freeball the business decision.
Workflow App Examples
Workflow app examples
Krafthaus turns consequential software-company workflows into focused app surfaces. Three live apps prove the pattern: quote approval, AI agent action, and customer onboarding readiness.
Live app surfaces
Three proofs of the same delivery layer.
Each app has a public surface, a closed intake, a pinned Application Manifest v1, a direct_declarative_rulebook binding, a Decision Record, and an execution handoff before the customer workflow moves.
Enterprise quote approval before sales sends pricing, discount, or nonstandard terms. Governed action: send_enterprise_quote.
AI agent action boundary before customer-facing autonomous software acts. Governed action: execute_ai_agent_action.
Customer onboarding readiness before implementation moves to go-live. Governed action: launch_customer_go_live.
What repeats
The app changes. The contract stays stable.
All three live examples use direct_declarative_rulebook and reject customer executable rulebooks in production.
Decide returns required binding material: runtime binding, rulebook contract, application verdict, input hash, and rulebook attestation.
Krafthaus turns the verdict into a next action: send, route, block, execute, or review.
More workflow categories
Start with the workflow your team already repeats.
Choose a category to see the intake, rulebook, record, and handoff before scoping a company-specific app.
Pricing exceptions, discounts, custom terms, legal review, and owner routing before a quote goes out.
Category AI agent actionConfidence, consent, approval, reversibility, risk, and human review before agent execution.
Category Support routingEvidence, policy context, SLA risk, queue routing, and owner assignment for support actions.
Category Onboarding readinessGo-live blockers, implementation status, launch readiness, and customer-success handoff.
Category Compliance document reviewReview-ready documents, evidence packets, owner routing, and case advancement.
Category Procurement exceptionsVendor, invoice, AP, mismatch, approval, and payment exception workflows.
Category wrapper
This is the system, not three disconnected demos.
The examples make Krafthaus legible as the workflow app layer. Start with one consequential workflow, package the operating surface, and use Decide underneath when the workflow needs deterministic verdicts, records, replay, and verification.