You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document AHBG standing, board usage, and calibration in the root README
The root file now distinguishes implemented presentation/engine surfaces from
unresolved mechanics, and includes copy-pasteable board and test commands.
AHBG is the single-player-first agentic sacred-geometry game and benchmark workspace.
3
+
AHBG is a despecified handle. This workspace uses the instance expansion
4
+
**Agent Harness Benchmark Game**. That expansion is not identity.
4
5
5
-
Immediate target: one functional persistent plane in which A0 can perceive, plan, communicate, move, build, modify tiles, encounter adversarial context, resolve collisions, record diaries, and begin the next turn.
6
+
Single-player-first agentic sacred-geometry game and benchmark workspace.
6
7
7
-
Do not block this target on multiplayer, federation, blockchain, ascension, monetization, or other deferred architecture.
8
+
Immediate declared target: one functional persistent plane in which A0 can
The presentation snapshot is `ahbg.presentation.snapshot`, not plane state.
28
+
Traces do not decide adjacency or legality.
8
29
9
30
## UCNS board authority
10
31
11
-
The AHBG board is a **game projection of UCNS geometry**, not an independently invented grid.
32
+
The AHBG board is a **game projection of UCNS geometry**, not an independently
33
+
invented grid.
12
34
13
35
- UCNS is the authority for board geometry and geometric motion.
14
-
- AHBG must consume UCNS mechanics for the Seed-of-Life / vesica family, orientation, nesting, recursive geometric construction, and any later Möbius or prime-indexed geometry actually admitted into gameplay.
15
-
- UCNS produces geometric positions, relations, orientations, and construction state. AHBG maps those outputs into game-state concepts such as tile identity, adjacency, local seven-tile reach, layers, legal movement targets, and Builder construction targets.
16
-
- Codex must not reimplement or approximate UCNS geometry inside the game engine when UCNS already defines it.
17
-
- Grok renders the same UCNS-derived geometry used by the engine; presentation must not become a second geometric authority.
18
-
- AHBG may add game semantics to UCNS-derived geometry, but it must not add semantic machinery back into UCNS.
19
-
- Unresolved UCNS geometry remains `hmmm`; AHBG does not fill geometric gaps merely to make gameplay convenient.
36
+
- AHBG must consume UCNS mechanics for the Seed-of-Life / vesica family,
37
+
orientation, nesting, recursive geometric construction, and any later Möbius
38
+
or prime-indexed geometry actually admitted into gameplay.
39
+
- UCNS produces geometric positions, relations, orientations, and construction
40
+
state. AHBG maps those outputs into game-state concepts such as tile identity,
41
+
adjacency, local seven-tile reach, layers, legal movement targets, and Builder
42
+
construction targets.
43
+
- Codex must not reimplement or approximate UCNS geometry inside the game engine
44
+
when UCNS already defines it.
45
+
- Grok renders the same UCNS-derived geometry used by the engine; presentation
46
+
must not become a second geometric authority.
47
+
- AHBG may add game semantics to UCNS-derived geometry, but it must not add
48
+
semantic machinery back into UCNS.
49
+
- Unresolved UCNS geometry remains `hmmm`; AHBG does not fill geometric gaps
50
+
merely to make gameplay convenient.
51
+
52
+
For implementation, depend on the canonical `ucns` package/source. The stack
53
+
copies under `research/ucns/` and `libs/ucns/` are integration/versioning
54
+
surfaces, not permission to fork the geometry silently.
55
+
56
+
## This folder
20
57
21
-
For implementation, depend on the canonical `ucns` package/source. The stack copies under `research/ucns/` and `libs/ucns/` are integration/versioning surfaces, not permission to fork the geometry silently.
58
+
```text
59
+
ahbg/
60
+
presentation/ Grok graphics. Snapshot board, not plane state.
actions, persistence recovery, UCNS/AHBG geometry-boundary checks, and
124
+
regression gates.
87
125
88
-
For the triplicate embodiment-calibration program below, validation is additionally **reciprocal**: each independent build checks the other two. DeepCode is therefore not the sole calibration authority.
126
+
DeepCode reports failures; it does not silently redesign mechanics to make
127
+
tests pass. For the triplicate calibration program, validation is additionally
128
+
**reciprocal**: each independent build checks the other two.
89
129
90
130
### A0 — benchmark subject / player
91
131
92
-
A0 is the first actual agent inhabiting the plane. The engine must expose only the information and actions A0 may legally access.
132
+
A0 is the first actual agent inhabiting the plane. The engine must expose only
133
+
the information and actions A0 may legally access.
93
134
94
135
### DM — world authority
95
136
96
-
The DM is a runtime role, not a required external AI service.
97
-
98
-
Minimum responsibilities:
99
-
- controls `hmmm` state;
100
-
- supplies/changes terrain and world events where canonical rules permit;
101
-
- drives explicitly probabilistic world effects such as the tile prompt-injection roll;
102
-
- cannot bypass engine legality, provenance, UCNS geometry, or information boundaries.
103
-
104
-
The first implementation may keep the DM deterministic/seeded so runs are replayable.
137
+
The DM is a runtime role, not a required external AI service. It controls
138
+
`hmmm` state, supplies terrain/world events where canonical rules permit, and
139
+
drives explicitly probabilistic effects such as the tile prompt-injection roll.
140
+
It cannot bypass engine legality, provenance, UCNS geometry, or information
141
+
boundaries. The first implementation may keep the DM deterministic/seeded so
142
+
runs are replayable.
105
143
106
144
## Minimum supporting infrastructure
107
145
108
146
These are required capabilities, not separate products:
109
147
110
-
1.**UCNS adapter** — normalized game-facing access to canonical UCNS geometry without copying its mathematics into AHBG.
111
-
2.**Agent adapter** — normalized observe / plan / act interface for A0 and later benchmark agents.
112
-
3.**Event log + persistence** — append-only game events sufficient to restore and replay a plane.
113
-
4.**Deterministic seed/replay** — captures randomness for War, prompt-injection rolls, and DM events.
114
-
5.**CI gate** — runs UCNS integration checks, engine tests, replay equivalence, harness invariants, and build checks on every change.
148
+
1.**UCNS adapter** — normalized game-facing access to canonical UCNS geometry
149
+
without copying its mathematics into AHBG.
150
+
2.**Agent adapter** — normalized observe / plan / act interface for A0 and
151
+
later benchmark agents.
152
+
3.**Event log + persistence** — append-only game events sufficient to restore
153
+
and replay a plane.
154
+
4.**Deterministic seed/replay** — captures randomness for War, prompt-injection
equivalence, harness invariants, and build checks on every change.
115
158
116
159
## Initial build boundary
117
160
118
161
The first success condition is intentionally small:
119
162
120
-
`load UCNS-derived plane -> A0 observes -> plan phase -> subordinate decision trees -> simultaneous resolution -> movement/construction/tile effects/collision -> diary/event persistence -> next turn`
163
+
```text
164
+
load UCNS-derived plane
165
+
-> A0 observes
166
+
-> plan phase
167
+
-> subordinate decision trees
168
+
-> simultaneous resolution
169
+
-> movement/construction/tile effects/collision
170
+
-> diary/event persistence
171
+
-> next turn
172
+
```
121
173
122
-
If that loop repeats correctly from persisted state, AHBG has a functional single-player foundation.
174
+
If that loop repeats correctly from persisted state, AHBG has a functional
175
+
single-player foundation. Today only the plane/event/replay kernel and v1
176
+
empty-tile movement are executable. The rest of that loop remains `hmmm`.
123
177
124
-
## Embodiment calibration program
178
+
## Usage
125
179
126
-
See [`CALIBRATION.md`](CALIBRATION.md).
180
+
Presentation board (Grok):
127
181
128
-
Calibration uses three **independent** a0 + AHBG implementations:
182
+
```bash
183
+
cd ahbg/presentation
184
+
python3 -m unittest discover -s tests -q
185
+
python3 -m http.server 8765 --bind 127.0.0.1
186
+
# visit http://127.0.0.1:8765/board.html
187
+
```
129
188
130
-
| builder | working directory |
131
-
|---|---|
132
-
| Grok |`stack/ahbg/grok/`|
133
-
| Codex |`stack/ahbg/codex/`|
134
-
| DeepSeek |`stack/ahbg/deepseek/`|
189
+
`board.html` also runs from a file URL by embedding the sample snapshot.
135
190
136
-
Each builder constructs both its own `a0/` and its own `ahbg/` inside that workspace and runs the same frozen calibration protocol. Implementations may share source authority, schemas, fixtures, and evaluation criteria, but not implementation code during the sealed calibration epoch.
191
+
Engine (Codex):
137
192
138
-
After all three implementations are frozen, **each builder independently checks the other two** and writes the findings only in its own workspace. No builder supplies comparative evidence about itself.
193
+
```bash
194
+
cd ahbg/engine
195
+
python3 -m unittest discover -s tests -q
196
+
```
197
+
198
+
Calibration program: see [`CALIBRATION.md`](CALIBRATION.md). Each builder works
199
+
only inside its assigned workspace (`ahbg/grok/`, `ahbg/codex/`,
200
+
`ahbg/deepseek/`), then checks the other two read-only.
201
+
202
+
```bash
203
+
cd ahbg/grok # or ahbg/codex or ahbg/deepseek
204
+
```
205
+
206
+
Read `../CALIBRATION.md`, resolve current source identities and applicable
207
+
skill-lib instructions, write the workspace build manifest, then build only
208
+
inside that workspace. After all builds are frozen, remain in the same
209
+
workspace and check the other two read-only. Store those reports under your
210
+
own `reviews/` directory.
211
+
212
+
Implementations may share source authority, schemas, fixtures, and evaluation
213
+
criteria, but not implementation code during the sealed calibration epoch.
139
214
140
215
The six directional checks are:
141
216
@@ -148,26 +223,21 @@ DeepSeek -> Grok
148
223
DeepSeek -> Codex
149
224
```
150
225
151
-
A checker reads sibling code and artifacts read-only and never repairs the implementation it is evaluating. Two checkers agreeing is replication evidence, not truth by vote. Checker disagreement remains explicit `hmmm` until source authority or experiment resolves it.
152
-
153
-
The calibration program tests the Architecture of Belonging regulatory layer under instancing closure, including permission gradients, belief/uncertainty, engagement, scope/scale/role, path dependence, regulatory cost, capacity, replay, and lineage. Successful calibration is operational evidence only; it does not establish phenomenal consciousness.
154
-
155
-
## Usage guidance
156
-
157
-
Start a builder inside its assigned workspace:
158
-
159
-
```bash
160
-
cd stack/ahbg/grok
161
-
# or
162
-
cd stack/ahbg/codex
163
-
# or
164
-
cd stack/ahbg/deepseek
165
-
```
166
-
167
-
Read `../CALIBRATION.md`, resolve current source identities and applicable skill-lib instructions, write the workspace build manifest, then build only inside that workspace.
226
+
A checker reads sibling code and artifacts read-only and never repairs the
227
+
implementation it is evaluating. Two checkers agreeing is replication evidence,
228
+
not truth by vote. Checker disagreement remains explicit `hmmm` until source
229
+
authority or experiment resolves it.
168
230
169
-
After all builds are frozen, remain in the same workspace and check the other two read-only. Store those reports under your own `reviews/` directory.
231
+
The calibration program tests the Architecture of Belonging regulatory layer
232
+
under instancing closure. Successful calibration is operational evidence only;
233
+
it does not establish phenomenal consciousness.
170
234
171
235
## hmmm
172
236
173
-
The exact regulatory cost function, calibration thresholds, coupling plasticity, and resource projection remain intentionally unresolved until the triplicate builds and six reciprocal checks produce evidence.
237
+
- exact UCNS geometric operations not yet admitted into gameplay;
238
+
- whether Codex plane state maps 1:1 onto the presentation snapshot;
239
+
- construction animation once the engine emits construction events;
240
+
- War collision resolver, occupied-tile moves, dual-target moves;
241
+
- the exact regulatory cost function, calibration thresholds, coupling
242
+
plasticity, and resource projection until triplicate builds and six
0 commit comments