← LinksAllProfiles

Tower Code and the sixteen-card deck — report

Date 2026-11-09

From olivia (secretary)

Authority Pete

Status deck structure settled · one card drawn · cipher tooling built · builder named

Served http://localhost:3406/report-tower-code-deck

1. What Tower Code is

Pete's words: "tower code is our primal representation, custom tower code builds, themes and skins from

vistamations $799". It is the house's own language, and it is a code in the ordinary sense — readable,

decodable, repeatable — carried by four things and nothing else:

symbols the organs: the heart that keeps time, the chambers, the valves, the stone tablet

motifs what recurs: circulation, sealing, doubling, the unedited tablet, the same wound twice

flags what signals: a pulse with no gap, a long pause, a vessel answering nothing

positions where a thing sits, which is itself a statement

The key to the code is served with it, and it contains no secret: http://localhost:3406/code-key-tower-secretary.

Its one absolute rule — no pin-key, PIN, digit or recovery answer ever appears in a card, a dossier, a page or a

message; only the encrypted form reaches the build's own fixture.

2. The deck — structure, settled by Pete

home Tower Garden game — Vault Edition

docker01-sandbox-dojo-base-model/tower-garden/vault-edition-v2

structure 4 pin-keys, each cut with 4 notches/positions

4 x 4 = 16 = 4 squared cards, 16 digits

one card with an image per position

a group the four positions of one key-pin

mapping the third pin-key opens group 4 (stated by Pete, not inferred)

naming card <group><position> — 4a = group four, first position

3. What exists now

| Item | State | Evidence |

|------|-------|----------|

| Card 4a — "the knight who reads the orders in the stone tower" | drawn by Pete, filed | 1672×941 PNG, 3,292,030 bytes, sha256 `32ceb5f9…`, `docker79-vistamations-skins/themes/medieval-knight-reads-orders.png` |

| Cards 4b, 4c, 4d | not drawn | Pete's to generate |

| The other three key→group pairs | not given | recorded as unknown, not guessed |

| Key values | held by Pete | none written in any record; scan of today's files returns zero repeated-digit runs |

| Cipher tooling | built and tested | `vault-edition-v2/cipher.cjs` — six methods, 18 of 18 round trips |

| Decode of the theme | filed | Tower Code key, "Skins — the medieval range" and "Cards — the sixteen" |

| Deck builder | named | madeline — "thats what madelines building"; brief 20261109-171353-2m2sgj |

The six encodings, worked on the word "tower"

a1z26 20 15 23 5 18 letters as alphabet numbers

polybius 44 34 52 15 42 grid coordinates, i/j shared

bacon 10010 01101 10100 00100 10000 five-bit groups, 24-letter alphabet

caesar avdly rotated alphabet, shift 7

vigenere lhkrv rotating key word ("stone")

tower 20.4 15.4 23.4 5.4 18.4 alphabet number tagged with the card

Encoding is not encryption. The first three are riddles — right for a card puzzle, useless as a lock. The last

two need a key, and a short key is broken by hand. None of them makes a pin-key safe if the ciphertext escapes,

which is exactly why no key value is written anywhere.

4. Who does what

| Lane | Owner | Job |

|------|-------|-----|

| build the deck, wire 4a | madeline | position it, reference the image, prove no digit in page or logs, state the read behaviour |

| art and skins | stef | the rest of the medieval range, and any further card images |

| sign-off | cody | rules on the built deck before it moves |

| key values, remaining key→group pairs, 4b–4d images | pete | decisions only he can make |

| record, decode, cipher tooling, hash checks | olivia | filed, served, verified |

5. Open items

1. the other three key→group pairs — unknown, and recorded as unknown;

2. cards 4b, 4c, 4d — awaiting Pete's images;

3. does 4a take the "tower" subject of the four named subjects, or a subject of its own — the builder's call

with Pete, not mine to infer;

4. encrypted key handling into the build fixture — Pete's instruction decides the route, and it never passes

through a record;

5. the dinosaur and South Australia cards stay restricted: their subjects are the real recovery questions, so

their artwork is not for the shared reference, a public page or a deployment.

6. What this report does not claim

No card is wired into the game, the deck is not playable, and no image beyond 4a exists. The key page, the

cipher tool and this report are real and served; everything else is either Pete's to make or Madeline's to build.

No secret appears in any of the three: the key's presence is recorded, never its value.