Define the rule
Describe the function’s inputs and outputs around a specific business decision.
Use the same business rule across your tools.
Forge. Define a function once and use it from the applications, agents, and workflows that depend on it.
Product walkthrough. Press Space or Enter to pause or play.
Forge. A function the team can test and reuse.
Test representative cases
Check both ordinary cases and the exceptions that could change the result.
Publish a reviewed version
Make the function available to the tools that need it and keep the version identifiable.
One guard. Every caller gets the same rule.
Inspect evaluateTenderReadiness, its three expected outcomes, and the reviewed activation of version 0.4.0 for two draft consumers.
The function accepts a shipment, telemetry, and Compliance evidence. It returns a readiness decision with reason codes; missing approval produces a hold.
Approved, Stale telemetry, and Missing approval all match their expected results. Inspect the immutable build and the tests behind version 0.4.0.
After review of the exact plan, version 0.4.0 is activated for the Workflow and Ontology action previews. The function evaluates readiness; the running tendering process remains v12.
In practice
The Workflow draft and the Shipment action preview need the same tendering rule. Both use evaluateTenderReadiness 0.4.0 after its three behavior checks and activation review. A passing missing-approval test confirms the expected hold. The function supplies the decision; it does not book a carrier or tender a shipment.
Explore the solutionDiscuss a shared business rule.
Bring a rule or calculation repeated across your tools. We’ll discuss its inputs, outputs, tests, and access requirements.