flintspark Book a demo

A fuel decision with its reasons

A fuel procurement decision is the choice between locking a fuel contract and buying at spot. Flint, flintspark's agent, reads EIA prices, applies a lock-or-spot rule stated in words and drafts a recommendation for each region with its reasons. By default a person approves it before it is submitted.

A sketch with the demo's values, not a screen from the product.

What data is used?

Two things from the US Energy Information Administration: this week's retail diesel price for each region, and the Short-Term Energy Outlook's forecast for next year.

Flint reads each value from the same place every run. A person confirms those places, and how Flint knows the submit went through, when the skill is taught.

A sketch, not a screen from the product.

How is the rule applied?

The rule is stated in words. For each region, Flint compares next year's forecast with that region's price this week, and the result is lock or spot. It then writes the reason from those two numbers.

Flint learns the rule from a demonstration, and a person reviews it before the skill is trusted. Where several pairs of numbers fit, Flint asks which one was meant. In the demo run the forecast was below this week's price in all three regions, and the result was spot in all three.

  1. Read
    The prices

    Each region's price this week.

  2. Compare
    The forecast

    Next year's forecast, against each price.

  3. Decide
    Lock or spot

    One result for each region.

  4. Explain
    A written reason

    Written from the numbers it read.

What does the approver see?

The exact request Flint wants to submit: the decision, the price and the written reason for each region. Submitting is binding, so Flint stops there.

The approver can approve, reject or take over. The approval is a signed, single-use grant for that exact request.

A sketch, not a screen from the product.

What is audited?

Each run records its steps, what Flint looked at, the rule that fired, the decision and the evidence, for 90 days by default. The approval goes into the hash-chained audit log.

Where to go next: the energy procurement solution, or the demo this use case is built on, with what was real and what was recorded.

A sketch, not a screen from the product.

Questions about this page

What decision does this use case support?

Whether to lock a fuel contract or buy spot, region by region. Flint, flintspark's agent, compares next year's forecast with each region's current price, drafts a request with a written reason for each region and waits for a person to approve it.

What does the approver see?

The exact request Flint wants to submit: the decision, the price and the written reason for each region. The approver can approve it, reject it or take over. The approval is signed, single-use and tied to that exact request.

What is recorded about each decision?

Each run records its steps, the prices Flint read, the rule that fired, the decision and the evidence. The approval itself goes into the hash-chained audit log. Run records are not in that log, and they are kept for 90 days by default.

See Flint run

Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.

We reply from hello@flintspark.ai.