How it works
From proposed commitment to decision proof.
Qistas sits between the systems that propose commitments and the people who approve them. It does not change what they propose; it shows what can be supported now — and keeps the basis.
01How it works
From proposed commitment to decision proof.
- 01
Proposed commitment
Qistas receives the commitment proposed by your existing commercial or optimization system.
- 02
Source-bound evidence
Operational evidence is mapped to a canonical decision state.
- 03
Evidence check
Freshness, provenance, availability and contradictions are evaluated.
- 04
Obligations & constraints
Technical limits, duration, customer obligations and existing commitments are applied.
- 05
Assurance envelope
Qistas identifies the portion that is supported under the available evidence.
- 06
Client decision
You remain the commercial decision-maker.
- 07
Boundary monitoring
Decision-relevant changes can require recertification or withdrawal.
- 08
Decision proof
The original basis can be inspected and replayed later.
02Inputs
Qistas works from evidence, not assumptions.
Asset / operational evidence
- Power
- Energy
- Operational state
- Technical limits
- Connection state
- Relevant asset telemetry
Obligations
- Customer requirements
- Contracted constraints
- Existing commitments
- Reserved capability
Policy
- Service duration
- Product rules
- Internal assurance rules
- Applicable operational constraints
Provenance & time
- Source
- Event timestamp
- Availability timestamp, where available
- Evidence version
These inputs allow Qistas to determine what is currently supportable, what is already encumbered, and whether the evidence is sufficient to issue an assurance result.
03Evidence Assurance
A result is only as defensible as its evidence.
A result is only as defensible as its evidence. Qistas distinguishes valid evidence from stale, missing, contradictory or unavailable evidence — and assures accordingly.
- ValidCurrent, attributable and consistent.
- StaleOlder than the decision allows.
- MissingRequired but not received.
- ContradictorySources disagree on the same fact.
- UnavailableThe source cannot currently be read.
Qistas determines what can be assured under the evidence available at the decision point.
04Why this amount?
Every assured amount should be explainable.
Qistas preserves the calculation path behind the assurance result, allowing authorized users to trace material values to their sources and verify the result again.
Why this amount?
Illustrative example- Proposed commitment
- 10.00 MW
- Assured amount
- 8.70 MW
- Unassured
- 1.30 MW
Why?
- Source evidence valid
- Duration requirement satisfied
- 1.30 MW already encumbered
- Policy v3.2 applied
View calculation proof
- 1
Evidence
Source readings at decision time, with provenance and timestamps
- 2
Transformations
Explicit mappings into the canonical decision state
- 3
Obligations
Existing commitments and reserved capability on the same assets
- 4
Constraints
Technical limits and the required duration
- 5
Calculation
Deterministic assurance calculation under policy v3.2
- 6
Result
8.70 MW assured · 1.30 MW unassured
- 7
Verification
Re-run from the preserved inputs: exact match
05Outputs
More than a yes or no.
Each assurance result is a structured record your systems and teams can act on.
Proposed amount
What your system proposed.
Assured amount
What is supported now.
Unassured amount
What is not, and is never described as assured.
Evidence state
Valid, stale, missing, contradictory or unavailable.
Binding constraints
The limits that determined the amount.
Reason codes
Machine-readable reasons for the result.
Validity horizon
How long the result holds under its context.
Recertification requirement
Whether a change requires a new result.
Decision proof
The preserved basis of the result.
Replay result
Whether a re-run reproduces it exactly.
06Deterministic, precisely
Reproducible decisions — not predictions of the future.
With the same evidence, obligations, policy and software version, Qistas produces the same assurance result.
This does not mean that future delivery is guaranteed. It means the assurance decision itself is reproducible and auditable.
07Validity context
Assurance has a validity context.
An assurance result is not permanent. When decision-relevant evidence changes, the previous result may no longer hold.
- Capability
- Obligations
- Connectivity
- Source quality
- Policy
- Duration requirement
Qistas tracks decision-relevant changes and can require recertification when that context changes.
08Where Qistas sits
A distinct question at each layer of the stack.
Enterprise enquiries
Keep your optimizer. Add independent assurance.
Evaluate Qistas against your existing commitments in a read-only Shadow Pilot before making any operational change.