RDSRPM Decisioning System

Consequential action must earn the right to move.

RDS brings evidence, authority, provenance, policy, and trust into the decision itself. It helps Wellzai distinguish between a pathway that should stop, one that needs redesign, one that can proceed, and one that is ready to accelerate.

Target-state Wellzai trust runtime architecture showing identity, authority, policy, evidence and an immutable audit trail around action
RDSTarget-state trust architecture

Trust before action

A credible pathway is more than a plausible recommendation.

When institutions, capital, or intelligent agents are involved, a recommendation is not enough. RDS is designed to make the basis for action inspectable by keeping identity, evidence, authority, policy, and accountability attached to the move. The trust runtime shown here is the end-state architecture Wellzai is building toward.

01

Decision gates

Use a richer answer than yes or no.

Classify consequential moves as Stop, Redesign, Proceed, or Accelerate so judgment remains explicit and actionable.

02

Proof

Know what must be true before movement.

Specify the evidence, authority, provenance, alignment, and policy conditions a pathway must satisfy.

03

Governance

Keep accountability in the runtime.

Support enterprise and agentic workflows without separating execution from the trust conditions that make execution legitimate.

Decision gates

Four decision states, not a binary approval.

As AI agents and automated workflows begin to initiate consequential actions, approval cannot be an afterthought. RDS gives every move an explicit, inspectable state so people, institutions, and intelligent systems share the same basis for acting.

  1. 01

    Stop

    The move should not proceed because the pathway is misaligned, unsupported, or likely to cause harm.

  2. 02

    Redesign

    The intention may be sound, but the current structure, evidence, or authority is insufficient.

  3. 03

    Proceed

    The pathway is credible enough to move with appropriate stewardship, controls, and monitoring.

  4. 04

    Accelerate

    The pathway is working and the evidence supports additional support, scale, or replication.

RDS in a formation

A possible path is not a credible one.

See how evidence, constraints, trust, and decision readiness distinguish a merely possible path from a credible one, and why the result is Proceed with conditions rather than a simple approval.

See the Credible Path

Where it becomes useful

Designed to change the quality of a formation, not add another dashboard.

capital deploymentclaims governanceagentic workflowspartner approvalsimpact-linked programsevidence gates
RPMDefine good
RPTUnderstand the system
RDSGovern action
FORMATIONCoordinate the path

The intelligence stack

See how RPM, RPT, and RDS work together underneath Outcome Formation.