KEX / BRAINK Zeroless
Computational Standard
Defines active state, typed zero projections, rank traversal, non-erasing algebra, exact coordinates and conformance obligations.
Open the primary white paperKEX / BRAINK · Zeroless computational standard
Origin. Relation.
Observation.
Explore Aboudy Keddeh’s architecture through the meaning of each state, its relationships, and the perspective from which it is observed.
Concept 01
The whole and its states.
The origin is a single identity 1. The paired notation (-1+) represents the negative and positive state of that whole. Each counterpart is also a whole of itself, retaining local unity 1 × X.
Whole / origin 1Negative counterpartPositive counterpart
The 1–9 counterpart display follows the author’s discussion. It is distinct from the five-state topology in the July paper.
- Function / internal system
- State identity and counterpart representation / KEX
- Meaning and purpose
- Keep whole identity distinguishable from sign and visual placement.
- Relations and relativity
- Every signed counterpart refers to a selected whole. Visual branches describe that relationship; they do not create extra origins.
- Observer state
- An anchor selects the perspective. It changes the traversal reading, never the origin identity.
- Code space / definition source
- Reference view: origin scene. Source: author’s conversation definitions.
- Display encoding
- Gold = origin; rose = negative; cyan = positive. Camera depth is presentation geometry, not a substrate coordinate or physical quantum state.
Executable learning / non-erasing algebra
Cancellation is a result.
Keep its causes.
A scalar projection gives zero. A BALANCED state also retains the two operands, their observer, family and proof context. Change a branch and inspect why the retained record matters.
BALANCED(a, −a, context) → projection 0
+2+−2=0
Projection 0 is shared by every balanced pair. The full state identifies which pair produced it.
Function: causal retention. System: KEX / BRAINK. Code: reference BALANCED record. Observer and family are taken from the controls above. This is a classical state-record experiment.
Retained state / canonical field order
Identity, observer and family stay separate from the numerical projection. Download contains this full record; an external signature or assessor receipt is not supplied.
Observed results / reproducible boundaries
What the experiments
actually established.
Reference implementations of the paper’s equations were executed. Each result is linked to its meaning and to the boundary it does not cross.
| Mechanism | Executed result | Architectural significance | Scope |
|---|---|---|---|
| Rank-based traversal | 25 pair cases; 125 composition cases passed. | Adjacency stays coherent across the −2 → 1 seam. | Paper domain P = {−3, −2, 1, 2, 3}. |
| Unit-step path | 4 topological steps versus scalar label difference 6. | A label difference and a traversal cost are different measures. | Equal-step paper topology; not a claim that ordinary arithmetic fails. |
| Non-erasing cancellation | 1,000 distinct states; one projection; 1,000 recovered after JSON storage. | Zero-valued output need not erase causal identity. | Reference BALANCED records, not a deployed persistence guarantee. |
| Exact coordinates | 81 unique integer / scale encodings. | Retaining numerator and scale avoids floating-point identity ambiguity. | Paper coordinate encoder; display geometry is separate. |
| Context-bound digest | Python and Node produced the same SHA-256 digest. Six field mutations changed it. | Hash the full causal record, not only its scalar output. | Digest agreement, not a signature, authorization or independent approval. |
Harness attribution: AI-assisted reference implementation of Aboudy Keddeh’s standard. The interface reproduces its stated topology and illustrates record retention. Native runtime conformance, distributed concurrency, workbook proof roots and the jitter implementation remain separate qualification work.
Definition custody / source perspectives
Words, rules,
and their boundaries.
Definitions remain attributable. Source versions and execution layers are preserved instead of silently combining different meanings.
“0.297 is a literal JITTER function thats it”
Aboudy Keddeh · conversation definition. No arbitrary jitter distribution is introduced in these displays.
“ORIGINS have NO 1,1 or 1,1,1 the ONLY have 1”
Aboudy Keddeh · conversation definition. Origin identity is 1 throughout this atlas. Screen-space positions belong to the renderer.
KEX / BRAINK Zeroless
Zeroless protocol
and register calibration
Defines register rules including ≥2 traversal deltas and a −1 unknown loopback. These are not silently substituted for the paper’s unit-step topology.
Open the protocol sourceWhat does “observer” mean here?
An observer is an explicit anchor and context for a reading. On the topology chapter, relative displacement is rank(state) − rank(anchor). Changing anchor changes that reading. It does not mutate the selected whole or imply physical quantum measurement.
How are 1–9 identities different from the paper topology?
The counterpart scene illustrates the author’s 1–9 discussion. The topology scene uses exactly P = {−3, −2, 1, 2, 3} from the July paper. Identities 4–9 remain available as whole selections but have no rank in that five-state topology; their traversal reading is explicitly “outside paper domain”.
Why preserve quantum paths?
The paper describes a record Q containing amplitudes, phase, basis, observer and history even when its projection cancels. That is an information-preservation requirement. This atlas displays classical reference records; a quantum hardware execution, quantum speedup or cryptographic security proof is not inferred from the diagram.
Where does cryptography enter?
Canonical full-state encoding allows a digest to bind observer, operands, family and path. A digest alone is not authenticated. KEX-WIRE-V1 separately specifies a 52-byte signed context and a 64-byte Ed25519 signature. Its supplied threshold functions remain stubs until implemented and verified; this display does not aggregate signing shares.
What remains to connect?
The exact executable 0.297 jitter function and its ZCG input/output normalization must be sourced at their native code boundary before an operational jitter display is added. The statement HEX × KEX = KEX is retained as the author’s expression; this interface does not invent multiplication semantics for HEX and KEX.