Working Draft 0.1 Public Decision Systems Engineering

Authority should be inspectable before a consequential decision becomes real.

Authority Circuit Architecture translates declared rules into explicit predicates, deterministic states, replayable proof records, and operational remedy.

Technical working draft. Not legal advice. The demonstrator is illustrative and does not establish conformance or determine any real-world authority.

SourceVersioned authority
EvaluateTyped predicates
ProveReplayable record

ACA-100

A closed-loop authority architecture

Six layers keep authority, evidence, evaluation, proof, and correction distinguishable.

  1. 01Source authority

    Identify source, scope, delegate, jurisdiction, effective period, and revocation status.

  2. 02Formal rule

    Express applicable requirements as declared, typed predicates and dependencies.

  3. 03Evidence

    Reference provenance, integrity metadata, access controls, and unresolved conflicts.

  4. 04Evaluation

    Apply a versioned decision profile without concealing human judgment as computation.

  5. 05Decision proof

    Produce a portable record that supports inspection and lawful replay.

  6. 06Remedy execution

    Detect, notify, preserve, review, correct, propagate, verify, and close.

ACA-120 / ACA-130

Verifiable Authority Cell

Change the synthetic predicate values. The illustrative evaluator preserves uncertainty instead of silently converting it into approval.

ALLOWDENYHOLD CONFLICTREVOKEDESCALATE

Synthetic profile

Eligibility decision example

HOLD
Evaluation note

A mandatory predicate is unknown. ALLOW is blocked pending verification.

ACA-140

The decision travels with its proof.

A Decision Proof Record distinguishes integrity proof from truth proof and preserves the material basis for replay.

01

Identity

Record, profile, rule version, evaluator, and evaluation time.

02

Predicate record

Material value, source, evidence reference, unknown, conflict, expiry, or revocation.

03

State transition

Prior state, resulting state, trigger, actor or service, and reason.

04

Remedy route

Available correction path, responsible authority, deadline, and verification status.

ACA-150

Review is an event. Remedy requires verified correction.

  1. Detect
  2. Notify
  3. Preserve
  4. Review
  5. Correct
  6. Propagate
  7. Verify
  8. Close

Closure requires evidence that corrective action occurred and, where applicable, propagated to dependent records and downstream decisions.

Standards family

One architecture, explicitly versioned components

ACA-000

Program Charter

Scope, commitments, governance, roadmap, and publication model.

ACA-100

Architecture

System layers, invariants, trust boundaries, and interfaces.

ACA-110

Core Terminology

Shared meanings for authority, evidence, predicates, proof, and remedy.

ACA-120

Authority Cell

Canonical inputs, evaluation behavior, and safe handling of uncertainty.

ACA-130

State Machine

Six canonical states and traceable transition requirements.

ACA-140

Decision Proof Record

Portable inspection, audit, challenge, and replay artifact.

ACA-150

Remedy Protocol

Correction lifecycle, propagation, measures, and verified closure.

Candidate reference implementation

Operationalized Remedy Protocol

Bounded ORP materials remain under reconciliation and do not yet define ACA conformance.