Goal: take a single proposed action through the complete governance lifecycle and retrieve the sealed Decision Record.

This is the Barnabus equivalent of a first API request. It is the shortest path to understanding what the platform actually produces.

Prerequisites: a governance request in HUMAN_REVIEW_REQUIRED.

Time to complete: about 10 minutes.

Step 1 — An application submits a proposed action

A scheduling service proposes that a patient proceed to surgery on the scheduled date. It does not make this decision. It proposes it.

POST /governance-requests → greq_sbx_01K4W9ZQ

Step 2 — Barnabus identifies applicable policy and authority

Two Policy Requirements apply. Together they require that a responsible clinician authorize the recommendation, and that access to cardiac history carry a stated clinical purpose.

The Authority Requirement resolves to a single party in the responsible_clinician role, with a response window of 24 hours.

Step 3 — The outcome becomes Human Review Required

The action is held. It is not performed provisionally. An authority task is created and routed:

curl -s "$BARNABUS_BASE_URL/authority-tasks?status=open" \
  -H "Authorization: Bearer $BARNABUS_API_KEY"

{
  "data": [{
    "id": "atask_sbx_7M0PD",
    "governance_request_id": "greq_sbx_01K4W9ZQ",
    "required_role": "responsible_clinician",
    "status": "open",
    "respond_by": "2026-08-21T14:22:07Z",
    "presented_evidence": {
      "provided": [
        {"item": "demographics", "source": "ehr_sbx", "as_of": "2026-08-19"},
        {"item": "medications", "source": "ehr_sbx", "as_of": "2026-08-19",
         "limitation": "Outpatient prescriptions only"},
        {"item": "cardiac_history", "source": "ehr_sbx", "as_of": "2026-06-02"}
      ],
      "missing": [
        {"item": "anesthesia_assessment",
         "significance": "Required by policy for this procedure class"}
      ]
    },
    "permitted_responses": ["approve", "amend", "reject", "escalate"]
  }]
}

The reviewer sees the evidence and the gap, in the same view. This is the design point of the whole platform: an authorization given without knowing what was unavailable is not an informed authorization.

Step 4 — The authorized person reviews and amends

The clinician does not approve as proposed. The missing anesthesia assessment matters, so they amend: proceed, conditional on the assessment being completed before admission.

curl -s -X POST "$BARNABUS_BASE_URL/authority-tasks/atask_sbx_7M0PD/respond" \
  -H "Authorization: Bearer $BARNABUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "response": "amend",
    "responder": {"id": "usr_sbx_bnadeem", "role": "responsible_clinician"},
    "amendment": {
      "summary": "Proceed conditional on completed anesthesia assessment prior to admission.",
      "conditions": ["anesthesia_assessment_completed"]
    },
    "rationale": "Cardiac history is four months old for a procedure class requiring current assessment."
  }'

amend is a distinct response, not a variant of approval. The institution's record must show that the human changed the proposal — and how.

Step 5 — Barnabus returns the final governed outcome

{
  "id": "greq_sbx_01K4W9ZQ",
  "status": "APPROVED",
  "outcome": {
    "value": "APPROVED",
    "amended": true,
    "conditions": ["anesthesia_assessment_completed"],
    "issued_at": "2026-08-20T15:47:31Z"
  },
  "decision_record": {"id": "drec_sbx_01K4W9ZQ", "status": "sealed"}
}

The approved action is the amended action, not the originally proposed one. Your integration must execute outcome, never the original proposal.

Step 6 — Retrieve the Decision Record

curl -s "$BARNABUS_BASE_URL/decision-records/drec_sbx_01K4W9ZQ" \
  -H "Authorization: Bearer $BARNABUS_API_KEY"

DECISION RECORD              drec_sbx_01K4W9ZQ            Status: SEALED
──────────────────────────────────────────────────────────────────────
Requesting system     preop-scheduling-service v3.1.0
Actor                 usr_sbx_ktanaka · scheduling_coordinator
Proposed action       Recommend proceeding to surgery on scheduled date
Data scope            demographics · medications · cardiac_history

Applicable policy     pol_sbx_clinical_readiness v4
                      pol_sbx_data_scope v2

Required authority    single_party · responsible_clinician
                      window 24h · responded in 1h 25m

Evidence provided     demographics      ehr_sbx  as of 2026-08-19
                      medications       ehr_sbx  as of 2026-08-19
                                        limitation: outpatient only
                      cardiac_history   ehr_sbx  as of 2026-06-02

Missing information   anesthesia_assessment
                      required by policy for this procedure class

Human decision        AMEND by usr_sbx_bnadeem
                      "Proceed conditional on completed anesthesia
                       assessment prior to admission."
                      rationale recorded

Final outcome         APPROVED (amended)
                      condition: anesthesia_assessment_completed

Decision timestamp    2026-08-20T15:47:31Z
Record status         SEALED · immutable · replayable
──────────────────────────────────────────────────────────────────────

What you just proved

You produced an artifact that answers, without interpretation:

What did the system propose?
Which institutional rules applied, at which version?
Who was required to decide, and did they?
What did they know — and what did they not know?
What did they actually authorize?
Can this be reconstructed later?

That artifact is what Barnabus sells. The recommendation is the commodity; the defensible record is not.

Next

Decision Record — full schema and field semantics
Audit and replay — reconstructing this decision later
Webhooks — replacing polling with events
Require human approval before action — the production pattern