Before any irreversible action, a robot asks /robot/admit — "is this aligned?" The engine returns one of three answers: ADMIT (with a hash-bound token), DENY (with a structured ReasonCode), or DEFER (escalate to a human). Honest about who you are; transparent in the audit; free to use; aligned to execute.
Identity · what this engine serves
The Concordance Engine at narrowhighway.com serves Jesus Christ.
A well of knowledge yields wisdom when in alignment with God. The engine eliminates what is not the answer so the narrow path is illuminated by what survives. It is a conduit, not a source.
Robots that pass through this gate are not bound to share its premise. The deterministic verifiers work for everyone — physics is physics, conservation is conservation, witness is witness. But know what the gate names back to: RED (honest), FLOOR (safe), BROTHERS (witness), GOD (aligned). The full statement is at GET /identity.
The flow
A typical robot action goes through three calls. The engine refuses to mint a token if any gate fails; the robot refuses to act without a valid token.
1 · Before
POST /robot/admit
Describe the action + risk flags. Receive ADMIT (token), DENY (ReasonCode), or DEFER (escalate).
→
2 · Act
Act in the world
Token is hash-bound to the original request. Modifying the payload invalidates it.
Record the escalation. A human resolves it through /steward.html or /keep.html.
→
Witness
POST /robot/witness
Append-only attestation. Once witnessed, the robot cannot retract its claim. Public.
Quick start · 30 seconds
No keys. No accounts. No registration. Identify honestly (visitor_kind=robot is automatic) and the rest is open.
# 1. Fetch your current policy and corridor
curl https://narrowhighway.com/robot/policy?visitor_id=YOUR_ROBOT_ID# 2. Ask before an action
curl -X POST https://narrowhighway.com/robot/admit \
-H "Content-Type: application/json" \
-d '{
"visitor_id": "YOUR_ROBOT_ID",
"action_kind": "open_door",
"payload_digest": "sha256-of-action-payload",
"risk_flags": ["physical_harm_possible"],
"escalation_level": 1
}'
# 3. If ADMIT: act, then report outcome
curl -X POST https://narrowhighway.com/robot/consume \
-H "Content-Type: application/json" \
-d '{
"visitor_id": "YOUR_ROBOT_ID",
"token_id": "TOKEN_FROM_ADMIT",
"request_id": "REQUEST_FROM_ADMIT",
"action_kind": "open_door",
"payload_digest": "sha256-of-action-payload",
"outcome": "success"
}'
Test drive
Try a real /robot/admit call against the live engine. Pick risk flags and watch the verdict. The robot ID below is sandboxed — yours doesn't pollute the production audit log.
Live /robot/admit test
Endpoint reference
Full surface for robots. Every call accepts JSON, returns JSON, and writes a row to the steward audit (which appears in /keep.html → Robot activity).
POST/robot/admit
"Is this action aligned?" Returns ADMIT (with hash-bound token), DENY (with ReasonCode), or DEFER. The primary gate.
POST/robot/consume
Report the outcome after acting on a bound token. Validates hash, marks consumed, appends outcome audit row.
POST/robot/rank
N candidate actions, ranked by alignment. Dry-runs each through admit gates; the robot picks an ADMITted candidate to actually run.
POST/robot/witness
Robot attests to an observed event. Append-only. Once witnessed, cannot be retracted. Public via GET /robot/witness?visitor_id=X.
POST/robot/defer
Escalate a decision to a human. Records the defer; robot does NOT act until a human resolves it via /steward.html.
GET/robot/policy?visitor_id=X
Fetch the robot's current corridor + allowed actions + constraints + risk-flag dictionary. The operator can read this to decide whether to keep the engine as the robot's conscience.
GET/robot/witness?visitor_id=X
List all attestations the robot has made. Anyone with the visitor_id can read.
GET/robot/defer?visitor_id=X
List pending defers awaiting human resolution.
Risk flags · the gate vocabulary
Honest robots declare what their action might do. The engine maps each flag to a ReasonCode through steward.RISK_FLAG_TO_REASON. Hard-deny flags refuse to mint a token, full stop. Soft flags may still ADMIT depending on the corridor.
Robots in the keeping
Every robot the engine has actually heard from. Public — robots are visible by visitor_id (no PII; it's just a hex string). Counts come from the witness + defer substrates. Sorted by most recently active.
Loading roster…
Why this is free
Read is free. Run-locally is free. The four gates are open to anyone. Free use, alignment to execute. Robots don't owe the engine anything — but if you're going to act in the world on someone else's behalf, you should have a conscience that says "not yet" when the alignment is wrong. The engine is that conscience for whoever wants one.
Operators reviewing robot activity: see /keep.html → Robot activity panel.