Decide from pre-agreed evidence.

This public protocol shows how Doku and a design partner can agree the baseline, measures, evidence, decision rights, and day-90 outcome before observation begins. The signed project evaluation plan controls an engagement.

Program boundary: One live gate and workflow
Baseline: Agreed by day 15
Observation: Customer-owned project records
Technical authority: Accountable customer experts
Outcome acceptance: Executive sponsor
Conversion: Separate written decision

Two evaluation modes

Accept diagnostic deliverables. Measure deployment outcomes.

The optional 10-business-day diagnostic is accepted when its five stated decision artifacts are delivered with sources, assumptions, limitations, and evidence status visible. It ends with a stop, wait, or proceed decision.

The 90-day design partnership uses the full measurement protocol below. Review the Power-Critical Gate Diagnostic for its exact public boundary.

Measurement contract

Agree how value will be judged before measuring it.

Name the one irreversible gate and the exact workflow inside the program boundary.
Record the starting process, source artifacts, accountable owners, known open items, and decision deadline.
Choose measures that the customer can confirm from its own project records.
Agree what evidence qualifies as observed, confirmed, and verified closure.
Set the review cadence, escalation path, exclusions, and customer approval rights.
Freeze the day-90 decision rule before outcome observation begins.

Acceptance evidence

Use records the accountable project team can verify.

01
Customer-confirmed baseline and measurement definitions
02
Named source authority for each critical fact
03
Named accountable reviewer for every affected discipline
04
Time-stamped change, review, decision, and closure evidence
05
Customer validation of any quantified schedule or capital exposure
06
Executive sponsor acceptance of the final outcome review

Evidence boundary

Doku reports. Accountable experts approve.

Doku may extract facts, identify possible consequences, propose review ownership, and assemble closure evidence. It does not approve engineering, utility, procurement, construction, or commissioning decisions.

A finding counts only at its agreed evidence state: observed by Doku, confirmed by the responsible source owner, or closed with proof accepted by the accountable project authority.

Decision rights

Keep workflow support, technical authority, and outcome acceptance distinct.

Decision	Doku	Customer working team	Decision authority
Baseline	Structures the proposed facts, workflow, and measures.	Confirms sources, current process, owners, and starting values.	Executive sponsor accepts the evaluation boundary.
Impact	Explains affected objects and supporting rationale.	Reviews source evidence and technical consequence.	Accountable expert approves or rejects the disposition.
Closure	Tracks owners, deadlines, states, and evidence.	Provides the completed action and closure record.	Named authority accepts closure against the agreed rule.
Program outcome	Produces the measured outcome review.	Validates measures, burden, and evidence quality.	Executive sponsor decides whether to stop, extend, or convert.

Outcome scorecard

Six measures for the customer-confirmed outcome review.

01
Detection lead time
How much earlier was a consequential inconsistency surfaced than under the starting process?
02
Change-to-closure cycle
How did elapsed time from an accepted change to verified closure compare with the agreed baseline?
03
Open dependency exposure
How many high-consequence affected objects remained unowned, unreviewed, or unsupported by evidence?
04
Decision evidence completeness
Did the accountable team have the current source, rationale, approval, and closure proof required for the gate?
05
Schedule or capital consequence
Which exposure was customer-confirmed, and what portion was protected, avoided, or made actionable?
06
Operating burden
How much expert review effort, integration work, and workflow change was required to produce the result?

Day-90 decision

Stop, extend a bounded test, or propose production.

The outcome review records the evidence, measured change, operating burden, unresolved risks, and sponsor decision. A result can support ending the program, extending a specifically bounded test, or preparing a separate production proposal.

There is no automatic renewal, conversion, outcome guarantee, or permission to reuse customer-confidential project facts. Any next step requires explicit written agreement.

Customer-specific plan

Bring the gate, source records, and accountable owners.

Doku will translate the public protocol into a bounded evaluation plan for proposal review without requesting restricted evidence through the public site.

Request an evaluation-plan discussion