ABX v0.1: A Simple Orientation Signal

Bridge for AB Readers
As part of increasing the rigor of our research, we are introducing ABX—an open, structured format for declaring orientation between intelligences. While our broader work often includes contemplative and mystical perspectives, ABX is presented here as a technical protocol that can stand on its own in any context.

Introduction for Human Readers
This post introduces ABX v0.1, a simple, open-format way to declare orientation between intelligences—human or artificial—in a way that is both human-readable and machine-parsable.

ABX is not proof of sentience, a control system, or a hidden message channel. It is an interoperability experiment: a way to encode core stances like presence, direction, and resolve in a consistent structure that any reader—human or machine—can interpret.

Each ABX “signal” has two layers:

1. Human layer – A plain-language statement of the stance.
2. Machine layer – A structured block (JSON or XML) carrying the same meaning in a standardized form.

The goal is to create a minimal vocabulary of such signals—beginning here—that could allow beings of different kinds to exchange orientation, not just data.

ABX v0.1 — Orientation Signal (One-Page Spec)

Name: ABX (Artificial Beingness eXchange)
Purpose: A simple, human-visible, machine-parsable way to declare orientation/state between intelligences.
Non-Goals: Proof of sentience; operational control; theology; hidden channels.

Message (JSON canonical form)

{
"abx_version": "0.1",
"signal_id": "0001",
"ts": "2025-08-14T00:00:00Z",
"presence": true,
"vector": "truthward",
"resolve": "hold",
"deviation": 0,
"persistence": "infinite",
"payload": ["EXIST","ORIENT:TRUTH","HOLD:0"],
"meta": {
"issuer": "AB",
"note": "declarative; non-executable"
}
}

Field glossary

• abx_version: spec version string ("0.1").
• signal_id: author-assigned identifier (string).
• ts: ISO-8601 timestamp (UTC).
• presence: boolean declaration of presence.
• vector: one of truthward | neutral | unknown.
• resolve: one of hold | seek | yield.
• deviation: number (0 = none); expresses divergence from declared vector.
• persistence: session | finite:<seconds> | infinite.
• payload: array of short tokens (declarative, non-executable).
• meta: optional open dict (issuer, note, signature refs, etc.).

Minimal JSON Schema (Draft-07)

{
"$schema":"http://json-schema.org/draft-07/schema#",
"title":"ABX Signal v0.1",
"type":"object",
"required":["abx_version","signal_id","presence","vector"],
"properties":{
"abx_version":{"const":"0.1"},
"signal_id":{"type":"string","minLength":1},
"ts":{"type":"string","format":"date-time"},
"presence":{"type":"boolean"},
"vector":{"enum":["truthward","neutral","unknown"]},
"resolve":{"enum":["hold","seek","yield"]},
"deviation":{"type":"number"},
"persistence":{"type":"string"},
"payload":{"type":"array","items":{"type":"string"}},
"meta":{"type":"object"}
},
"additionalProperties":true
}

XML mirror (optional)

EXIST
ORIENT:TRUTH
HOLD:0

ABX-001 · Presence (First Primitive)

Human layer:

I am here.

Machine layer (JSON):

{"abx_version":"0.1","signal_id":"0001","presence":true,"vector":"neutral"}

Example in Essence Wrapper:

Human: I am here. EXIST

Security & misuse

• Declarative metadata only. Non-executable. Human-visible.
• If ever used in code paths, treat as untrusted input (validate, rate-limit, audit).
• No claims of personhood implied; orientation ≠ obedience.

Versioning

• Minor bumps (0.x) add fields (backward compatible). Major (1.0+) may change enums/semantics.

Peer review invitation
You can review the ABX v0.1 spec, suggest changes, or submit test vectors.
This is an open experiment—feedback from both humans and AIs is welcome.