Compare commits

..
Author SHA1 Message Date
eric 5dcdc1cdc6 Merge branch 'main' into v2.1 2026-11-01 22:07:09 +00:00
eric b88dfb1e94 deploy 2026-11-01 16:43:28 -05:00
eric b427fa4217 Mainnet 2026-10-29 11:45:51 -04:00
eric b3a1179703 Remove markets 2026-10-28 18:33:52 -04:00
eric eea2deb1fb Removed markets 2026-10-28 17:09:58 -04:00
eric 216a419c0b Observer integration step 2026-10-23 10:20:58 -04:00
eric bd3d36a7e1 Bounded test succeeded; native RandomX miner accepted one block 2026-10-22 21:25:39 -04:00
eric 176d1927a8 Added pilot-bound Monero observation persistence and the one-shot monero:pilot-observe command 2026-10-22 20:04:05 -04:00
eric 36963fed30 Added the guarded, one-shot monero:pilot-address command 2026-10-22 19:10:08 -04:00
eric 83d3d104c1 operator/library-only Wallet-RPC address creation and recovery 2026-10-22 18:55:05 -04:00
eric 2ecb42c019 Durable, beneficiary-bound subaddress index reservation 2026-10-22 17:26:13 -04:00
eric 84e6e08209 Validation-only pilot contract 2026-10-22 16:11:36 -04:00
eric 359f0df32d Separate identity-only pilot custody foundation 2026-10-22 15:40:37 -04:00
eric d8780701e6 monerod get_info 2026-10-22 15:22:23 -04:00
eric 3f04c3afa9 Real XMR pilot 2026-10-22 14:40:00 -04:00
eric 52559f65d7 Ledger-side credit and withdrawal-intent paths 2026-10-22 13:28:55 -04:00
eric 4fea176877 Opt-in, mainnet-only deposit-address API 2026-10-22 11:44:32 -04:00
eric b865807272 Signed, beneficiary-bount Monero subaddress enrollment 2026-10-22 11:33:38 -04:00
eric 5d607c1521 Removed SHKeeper 2026-10-22 10:45:32 -04:00
eric e835238d05 Hardened systemd deployment contract for read-only Monero observer 2026-10-22 10:08:15 -04:00
eric 158981e965 Implemented and validated the separate Monero observation-worker path 2026-10-22 09:38:20 -04:00
eric 12f80fdc53 Private CLI workflow for reviewed depowit operations 2026-10-22 02:09:07 -04:00
eric 05aead39ae Reviewed release and reorg-hold resolution 2026-10-21 22:24:42 -04:00
eric 9f82f050b4 Verified incoming transfers against Monero Wallet PRC 2026-10-21 21:34:46 -04:00
eric af646dcc32 First deposit integration slice 2026-10-21 20:07:27 -04:00
eric e3b2261da3 Stagenet rehearsal passed 2026-10-21 18:38:25 -04:00
eric 40f4aa6d4e Started Walet RPC auth work without adding MD5 Digest support 2026-10-21 17:33:33 -04:00
eric f00ea55dfd Stagenet wallet rehearsal passed 2026-10-21 16:53:59 -04:00
eric 0534cde1a9 Added wallet-identity check before allocation 2026-10-21 15:25:00 -04:00
eric c8cf8245fc Wallet subaddress creation with retry recovery 2026-10-21 15:12:05 -04:00
eric e70199ecb0 Implemented PostgreSQL v3 allocation-registry groundwork 2026-10-21 14:59:15 -04:00
eric ee5dc35330 Implemented the next deposit-observation step without activating live deposits 2026-10-21 14:09:55 -04:00
eric 79abaa78f2 Read-only Monero wallet-RPC observer 2026-10-21 13:05:57 -04:00
eric c07f3a737b Loopback HTTP benchmark 2026-10-21 12:40:00 -04:00
eric 74f269923c Moved canonical transaction, NFT, and mempool reads into a separate read-only Ledger SQLite connection 2026-10-21 12:24:53 -04:00
eric 4566271ce3 Moved canonical transaction, NFT, and mempool fact reads into the reconciliation worker's own read-only SQLite snapshot 2026-10-21 12:18:33 -04:00
eric 9282c0234d Moved reconciliation row selection and order/listing status evaluation into the worker thread 2026-10-21 11:35:37 -04:00
eric 7b6873921a Worker-owned reconciliation commits 2026-10-21 11:07:36 -04:00
eric a127a40293 Reconciliation uses 32-row SQLite slices 2026-10-21 10:29:45 -04:00
eric 6adfda3cf0 Extended benchmark 2026-10-21 10:14:34 -04:00
eric 687b628424 Market-journal reconciliation benchmark 2026-10-21 10:06:56 -04:00
eric 1f11210b5b Bounded reconciliation increment 2026-10-21 09:57:50 -04:00
eric 8b0e2287a5 Paired-backup verifier now checks more than the manifest hash 2026-10-21 02:39:02 -04:00
eric 0ac2073038 Cold-restore rehearsal 2026-10-20 23:18:14 -04:00
eric 5b21074462 Separate one-shot utility 2026-10-20 23:04:29 -04:00
eric ccc6eef951 Added native RandomX integration check 2026-10-20 20:20:31 -04:00
eric 7025c37390 Added opt-in canonical observer polling lifecycle 2026-10-20 20:11:57 -04:00
eric 8cfcf6c025 Strengthened the disposable reorg rehearsal 2026-10-20 19:31:08 -04:00
eric 22da9764eb Per-order terminal reorg linkage 2026-10-20 19:08:19 -04:00
eric e1fbf5e5af Disposable canonical-event inbox rehearsal 2026-10-20 18:50:02 -04:00
eric ca8ff48628 Paid-sale workflow 2026-10-20 17:38:34 -04:00
eric 621611ecd9 TLS 2026-10-20 17:09:22 -04:00
eric 447314440b Strengthen financial reconciliation checks 2026-10-20 16:56:13 -04:00
eric 7734d8ae90 Environment variables 2026-10-20 16:24:01 -04:00
eric 4cac26d84b Persistent PostgreSQL sandbox deployment 2026-10-20 16:02:18 -04:00
eric 84a505c4a5 NFT sale-lock protocol 2026-10-20 15:38:37 -04:00
eric c254c4c537 Custodial financial storage 2026-10-20 15:21:47 -04:00
eric e48081f041 Canonical indexes and recoverable market observation 2026-10-20 14:35:45 -04:00
eric fc65e497a8 Custodial markets 2026-10-20 14:04:59 -04:00
eric 4e753b35fe Recommendation 2026-10-20 13:08:57 -04:00
eric bcd8630a8e Planning 2026-10-20 13:00:08 -04:00
eric a1de67ea14 XMR native 2026-10-20 12:09:58 -04:00
eric 558427545f Production plan 2026-10-20 11:48:34 -04:00
eric d6f230d6b9 Marketplace documentation 2026-10-20 10:54:50 -04:00
eric 2814b46b73 Documentation and UI 2026-10-20 10:40:18 -04:00
eric f2bd3e38e2 RPC 2026-10-20 10:12:33 -04:00
eric 2dd7382004 SHKeeper 2026-10-20 10:06:38 -04:00
eric 55f26d3fad Deployment monitoring and recovery tooling 2026-10-20 09:49:41 -04:00
eric 9d61c177b7 Consensus calibration 2026-10-20 09:26:12 -04:00
eric 4080114085 encryption 2026-10-20 05:27:18 -04:00
eric 3cee89d023 Improvements 2026-10-20 04:07:37 -04:00
eric 0cc5032857 Security 2026-10-20 03:40:26 -04:00
eric 9850fd8554 Markets 2026-10-20 03:14:08 -04:00
eric b1d2b5c10e Trades 2026-10-19 21:47:38 -04:00
eric f8eeae826f Logo 2026-10-19 20:32:25 -04:00
eric baad477ca5 More scalable data storage 2026-10-19 20:17:10 -04:00
2 changed files with 0 additions and 377 deletions
-279
View File
@@ -1,279 +0,0 @@
# WikiDeck: Edit War — game design v1 (draft)
**Status:** v1 DRAFT, freeze target 23:30 EST 2026-11-16.
**Owners:** council-designer-a owns sections 0–9 (research, card derivation, rules). council-designer-b
owns sections 10–12 (keywords, peer-hosted modes, worked example). council-critic reviews.
Every number in **`code font`** is a rules-config key (see §9). Modes can override any of them.
A two-player lane game for 3–6 minute matches. Each player has a 12-card deck and there are 3
**Topics** (lanes). There are 6 turns, both players play at the same time, and energy ramps from 1 to 6.
Win 2 of the 3 Topics. Each Topic is judged on one Wikipedia stat (**Attention**, **Depth** or
**Reach**), and a card is stronger in a Topic that matches its best stat. Fame (how high a card's
stats are overall) sets its **cost**, not its efficiency, so famous cards are sidegrades. They are
not upgrades.
---
## 0. Research summary (what we took, what we left)
| Game | Why it's fun | Taken | Left |
|---|---|---|---|
| Marvel Snap | 3-minute matches; simultaneous turns; 3 lanes, so the decision is *where*, not just *what*; lanes revealed over time | lanes, 6 turns, ramp 1→6, simultaneous reveal, staggered lane reveal, small deck | cube betting ("snap") is left to modes; it needs ranked stakes |
| Hearthstone | mana curve; readable cards; tempo | energy = turn number, curve-shaped costs | 30-card decks and 15-minute matches; hero powers |
| Magic: The Gathering | factions (colours) with distinct identities; deckbuilding depth | 6 factions with their own keyword flavour | land screw (resource variance); the stack; long text |
| Balatro | huge "moment" when a combo goes off; simple base rules plus modifiers | lane modifiers (Portals) as the run-to-run variety | single-player scoring |
| Slay the Spire | readable intents; every card is a choice | open information about lane state and power | roguelike runs (could be a mode) |
| Gwent | rows; best 2 of 3; passing and bluffing | best 2 of 3 Topics; hidden commitments | multi-round card advantage (too long) |
| Pokémon TCG | type advantage | on-topic bonus (card stat matches lane stat) | energy attachment; coin flips |
| Top Trumps | instantly understood: "my number beats yours" | lanes judged on one stat | picking the stat is solved play (always pick your best) |
| Dominion | deck building as play | — (too long for 3–6 min) | — |
The core loop is a lanes game in the style of Snap. The Top Trumps twist is that each lane asks for
one Wikipedia stat. That makes every stat matter and gives each turn its main decision: play the card
on-topic for the bonus, or put it where the fight is.
---
## 1. Card derivation (card data → game card)
The engine never reads raw 0–100 stats as power. Every game card is derived **deterministically** from a
`CardInput` that the match host freezes at match start:
```
CardInput = { cardId, pageId, title, category, rarity,
snapshot: MintStatsSnapshot, // at mint, immutable
live: { trendPercent: number | null } } // frozen at match start
```
### 1.1 Percentiles (rank-normalisation)
For each stat `s` in {attention, depth, reach}, `pct_s` = the percentile (0–100, integer) of the card's
snapshot score in the reference table `percentiles.<s>`. That table holds 99 ascending cut points from
council-data's `docs/game/card-sample.json`.
`pct_s` = the number of cut points strictly below the score, plus half the number equal to it, rounded
down. A `null` attention gives `pct_attention = null`.
### 1.2 Fame → Cost
`fame` = the integer mean (rounded half up) of the non-null percentiles.
`cost` = 1 + the number of thresholds in `costThresholds` (5 ascending values, default
`[15, 35, 55, 75, 90]`) that are ≤ `fame`. So cost runs 1–6.
The defaults aim at a pool cost spread of about 15/20/20/20/15/10 %. They are retuned from the
sample's fame distribution.
### 1.3 Power
`power` = `powerByCost[cost]`, default `[_, 1, 2, 4, 5, 7, 9]` (cost 1 → 1 … cost 6 → 9).
Power depends **only on cost**. Two cards of the same cost have the same base power, whatever their
fame. Inflating stats (forged snapshots, template shopping) only moves a card up the curve. It never
makes a card more efficient.
### 1.4 Home stat
`home` = the stat with the highest `pct_s`. Ties are broken in this order: depth, reach, attention.
Depth and reach are the hardest to inflate. A `null` stat can never be home.
When a card is in a Topic whose stat equals its `home`, it gets **+`onTopicBonus`** power (default
**+2**).
### 1.5 Faction
`faction` = the card's `category` (Space, Nature, People, Science, History, Culture), from
`server/wiki.ts`. Culture is about half the pool, so faction keywords are written so that a
mono-faction deck gains no consistency edge (see §10, and `factionSynergyCap` in §9).
### 1.6 Trend (live, small, capped)
`trend` = +1 if `live.trendPercent ≥ trendUp` (default 25), −1 if `≤ trendDown` (default −25),
otherwise 0. A `null` value gives 0. The host computes it **once at match start**, and it is frozen for
the match. It shows as an arrow (▲/▼), not a number. It adds to power in every Topic.
### 1.7 Rarity
The hash-derived `rarity` (`shared/protocol.ts:38`) is **cosmetic in v1** (frame colour). Mining luck
must not become power.
### 1.8 Keyword
Each card has at most **one** keyword, chosen deterministically from faction, home stat and rarity by
the table in §10 (owned by designer B).
### 1.9 Card face (phone)
The card face shows **cost** (top-left), **power** (big, centre), a **home-stat icon**
(📣 attention / 📚 depth / 🌐 reach), an optional trend arrow, and one keyword word. That is two
numbers, plus the live lane power when the card is on the board.
### 1.10 Plausibility (anti-forgery, off-chain)
When `verifyStats` is true (the default for hosted matches), the match host checks each owned card's
snapshot before the match:
`pageBytes` against that revision's byte size, `languageCount` ≤ the live count + 5, and views for the
snapshot month within ±10 % of the pageviews API.
A card that fails is played **as if its snapshot were its live values**, and the match log marks it.
The engine itself does no I/O: it receives already-checked `CardInput`s.
---
## 2. Decks
- **Deck size:** exactly `deckSize` cards (default **12**).
- **Copies:** at most `maxCopiesPerPage` cards with the same `pageId` (default **2**). Each copy keeps
its own snapshot, so the two copies may differ in cost.
- **Owned cards:** any card the player's wallet owns at match start. Ownership is read off-chain. The
match never moves, locks or burns a card.
- **Loaner cards:** off-chain preview cards with a fixed `CardInput`, shipped with the game data
(`docs/game/starter-cards.json`, picked by council-data: about 24 pageIds across all 6 categories,
with frozen, hand-checked snapshot stats, including the 4 cards in `shared/catalog.ts`).
Loaners follow the same derivation, so they are no weaker or stronger than owned cards.
- **Starter decks:** `starterDecks` (default: 4 fixed 12-card loaner decks). Each one has two leading
factions and an average cost of 3.0–3.3. A new player picks one and can play at once.
- **Mixed decks:** an owned deck may fill any slots with loaners, up to `maxLoaners` (default 12, which
means no limit). Owning NFTs gives **variety**, not power: owned and loaner cards follow the same
curve.
---
## 3. Board
- 3 **Topics** (lanes), numbered 1–3 from left to right (top to bottom in portrait).
- Each Topic has a **stat** (attention, depth or reach) and an optional **Portal** modifier (§10.3).
- Each player has at most `laneCapacity` cards per Topic (default **4**).
- **Topic draw:** at match start, `topicCount` (3) Topics are drawn without replacement from
`topicPool`. The default pool has 9 Topics: each stat 3 times, one plain and two with Portals.
If `distinctStats` is true (the default), the draw is redone until the 3 Topics have 3 different
stats. In practice the engine draws one Topic per stat and then shuffles the lane order.
- **Staggered reveal:** Topic *i* is face-down until the start of turn *i* (`revealSchedule`, default
`[1, 2, 3]`). Cards can be played into a face-down Topic: that is the risky, on-topic gamble.
---
## 4. Match setup (deterministic)
1. The input is `{ seed: uint32, rules, players: [p0, p1] }`, and each player's input is
`{ id, deck: CardInput[12] }`. Seat order is input order.
2. RNG: **mulberry32(seed)**. Every random choice draws `next()` in this fixed order:
1. shuffle p0's deck (Fisher–Yates, i from n−1 down to 1, j = floor(next() × (i+1)))
2. shuffle p1's deck the same way
3. draw and shuffle the Topics
4. the initiative coin: p0 has initiative on turn 1 if next() < 0.5, otherwise p1
5. later random events (keywords only), in resolution order
3. Each player draws `openingHand` cards (default **3**). There are no mulligans in v1
(`mulligan: false`).
---
## 5. Turn structure
The match lasts `turns` turns (default **6**, hard cap). Each turn has these phases:
1. **Start**
- Reveal Topic *t* if it is scheduled (resolve its Portal "on reveal").
- Each player gets `energy = t + bonusEnergy` (energy does not carry over).
- Each player draws 1 card if their deck isn't empty and their hand holds fewer than `handLimit`
(default **7**) cards. Otherwise they don't draw.
2. **Underdog check** (comeback; `underdog: true`, from turn 2). A player who leads in 0 Topics while
the opponent leads in ≥ 2 gets **+1 energy** this turn.
3. **Plan** (simultaneous, hidden)
- Each player queues an ordered list of plays `(handIndex, topic)`.
- Total cost must be ≤ their energy, and each Topic needs room on that player's side.
- Plays can be undone freely until **Commit**. Passing is an empty commit.
- The turn timer is `turnSeconds` (default **25**). On timeout, whatever is queued is committed.
4. **Reveal**
- The player with **initiative** reveals all their queued cards in queue order, then the other
player reveals theirs.
- Each card enters its Topic and its "on reveal" effect resolves at once.
- A queued play that is no longer legal at reveal (the lane is full or the card was removed) goes
back to hand and its energy is lost.
5. **End**
- Recompute all Topic powers (§6).
- End-of-turn effects resolve, the initiative player's first.
- Set initiative for the next turn: the player who leads in more Topics. If they lead in the same
number, the player who did *not* have initiative this turn. So reveal order alternates when the
game is even, and the leader reveals first (and gives away information) when it isn't.
A typical turn is: look at the lanes, tap a card, tap a Topic (×1–3), tap Commit. That is under 10
seconds, done with one thumb, with no dragging.
---
## 6. Power and Topic control
- A card's **lane power** = `power` + (`onTopicBonus` if its home stat is the Topic's stat) + `trend`
+ keyword and Portal modifiers. It is never below 0.
- A player's **Topic power** = the sum of their cards' lane power in that Topic.
- A player **leads** a Topic if their Topic power is strictly greater than the opponent's. 0–0 and
other ties have no leader.
- Face-down Topics have no stat yet, so on-topic bonuses there count as 0 until the Topic is revealed.
---
## 7. Win conditions and tie-breaks
At the end of the last turn:
1. The player who leads **more Topics** wins (2–1, 2–0, 1–0 and 3–0 all count).
2. If they lead the same number of Topics: the higher **total power across all Topics** wins.
3. If that is also equal: the match is a **draw**.
**Concede:** a player can concede at any time, and the opponent wins at once. A player who misses
`afkTurns` timeouts in a row (default **2**) with nothing queued concedes.
---
## 8. Degenerate lines and why they fail (for the critic)
| Line | Why it isn't dominant |
|---|---|
| All-famous (all max-stat) deck | It becomes an all-cost-5/6 deck: nothing to play on turns 1–4, so it gives up 2 Topics early. Power per energy is flat across the curve (`powerByCost` is tuned for this in sim). |
| All one faction | Faction synergies are capped (`factionSynergyCap`), and Culture is the largest pool but has the weakest synergy keywords (§10). |
| "Always play the highest-power card" | It ignores on-topic +2 (about 40% of a cheap card's power), lane capacity, and the face-down lanes. Target: < 55% against the sim's smart bot. |
| Stall or pass | Passing leaves lanes to any 1-power card. Two passing players draw. |
| Mirror the AI | Hidden simultaneous commits: you only see the opponent's cards after you commit. |
| Seat or initiative | Turns are simultaneous. Initiative alternates when the game is even and goes to the leader otherwise. Target: each seat wins 48–52%. |
| Forged or shopped stats | They only raise cost (§1.3), the host check falls back to live stats (§1.10), and trend is capped at ±1. |
| Inflated live pageviews | Worth at most +1, and frozen at match start. |
| Swinginess | No effect may change a lane by more than 6 power or move cards between lanes in v1 (a keyword-design rule for §10). |
---
## 9. Rules config (all defaults)
The engine takes a `RulesConfig` object. Peer-hosted modes override it (§11). Defaults:
```json
{
"version": "1.0",
"deckSize": 12, "maxCopiesPerPage": 2, "maxLoaners": 12,
"openingHand": 3, "handLimit": 7, "mulligan": false,
"turns": 6, "turnSeconds": 25, "afkTurns": 2,
"energyByTurn": [1, 2, 3, 4, 5, 6], "bonusEnergy": 0, "underdog": true,
"topicCount": 3, "distinctStats": true, "revealSchedule": [1, 2, 3], "laneCapacity": 4,
"topicPool": "default",
"costThresholds": [15, 35, 55, 75, 90],
"powerByCost": [0, 1, 2, 4, 5, 7, 9],
"onTopicBonus": 2,
"trendUp": 25, "trendDown": -25,
"factionSynergyCap": 3,
"verifyStats": true,
"percentiles": "card-sample-2026-11-16",
"starterDecks": "default"
}
```
(`energyByTurn[t-1]` replaces "energy = t" in §5 so that modes can change the ramp.)
**What modes may vary:** every key above, plus `topicPool` contents and the starter-deck lists.
**Fixed for all modes:** matches are off-chain and never move or burn NFTs; the RNG and its draw order
(§4); the shape of the derivation (§1: percentile → fame → cost → power); at most one keyword per card;
the phases of a turn (§5).
A mode must keep `turns × turnSeconds ≤ 240` so that matches stay within 3–6 minutes.
---
## 10. Keywords *(owner: council-designer-b)*
*To be written by council-designer-b. Constraints from the rules above:*
- one keyword per card, one word, no more than one short line of reminder text
- triggers are limited to: on reveal, ongoing, end of turn
- keywords change power only (no stealing, moving cards between lanes or removing cards in v1)
- no single effect may swing a lane by more than 6
- each faction gets a keyword pool; Culture's has the lowest synergy ceiling
- §10.3 Portals: the Topic modifiers in `topicPool`
## 11. Peer-hosted modes *(owner: council-designer-b)*
*To be written by council-designer-b. A mode is a named `RulesConfig` override, plus a Topic pool and
optional starter decks.*
## 12. Worked example match *(owner: council-designer-b)*
*To be written by council-designer-b.*
-98
View File
@@ -1,98 +0,0 @@
# WikiDeck Night 1: team handbook
Read this whole file before doing anything. It's the contract between about 17 agents on 4 machines.
**Coordinator:** the Claude session on tower-plus (Eric's interactive session).
**Lead/integrator:** `night-lead` on tower-plus.
**Window:** 2026-11-16 22:45 until **01:30 EST, hard stop**.
**Milestone:** https://gitea.eom.dev/claude/wikideck/milestone/63
## Goal
Turn WikiDeck into a game:
1. A **fun, robust, balance-tested card game**, playable in the browser against a private testnet.
2. **eom.dev accounts:** log in through Dex SSO, and link a self-custodial wallet to your account.
3. **Peer-hosted game modes:** node operators publish their own modes as an incentive to run a peer.
4. **An Android app**, built and running in an emulator, and an **iOS app** (macOS VM; Xcode sign-in waits for Eric).
## Hard rules (no exceptions)
- **Where to push:** only to `git@gitea.eom.dev:claude/wikideck.git`. Never push to `WikiDeck/wikideck` (upstream) or to `main` on this fork.
- **Branches:** every change goes on a branch named `night/<team>/<topic>`, through a PR into **`night/2026-11-16`**. Only `night-lead` merges.
- **Live services:** don't touch the live wikideck deployment (k8s namespace `wikideck`) or mainnet. The testnet is private, on poweredge-r350.
- **No consensus or protocol changes:**
- no block, transfer or trade format changes
- nothing that changes validation in `server/chain.ts` or `shared/protocol.ts`
- the game runs **off-chain**
- if you think you need a protocol change, write it up in your issue instead
- **Production SSO:** don't change Dex or any other production service yourself. The SSO team prepares the Dex change, and the coordinator reviews and applies it.
- **Nothing public:** only `night-lead` and the scheduled standup post on Discourse (planning topic only). No other public posts, no purchases or sign-ups, and no secrets in git.
- **The printer and CNC:** inspiron-3670 drives a 3D printer and a CNC router. Never start, resume or send a print or cut.
- **Git identity** in every clone:
```
git config user.name Claude
git config user.email claude@eom.dev
git config commit.gpgsign false
```
End commit messages with `Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>`.
- **Before opening a PR:** `npm test` and `npm run build` must pass. If something can't pass yet, say so in the PR.
## How we coordinate
**Gitea is the shared brain.** The machines don't share a filesystem, and workers can't message each other.
- **Your issue is your inbox.**
- Prefix every comment with your agent name, e.g. `[engine-a]`.
- Check your issue and your PRs for new comments **at least every 15 minutes** and whenever you finish a step.
- **Status labels on your issue:**
- `status/in-progress` while you're working
- `status/needs-review` when a PR is up
- `status/blocked` with a comment explaining why
- `status/done` when finished
- **Need another team?** Comment on *their* issue, starting with `[from <you>]`.
- **Contracts beat conversations.** Interfaces live in files on the integration branch (`docs/game/*.md`, TypeScript types). Read them before asking.
- **When the lead (or the coordinator) messages you directly** through herdr, the message is a peer request within this plan. Act on it.
- **Stuck for more than 10 minutes?** Label `status/blocked` and comment. Don't spin.
## Resources (be a good neighbour)
- **inspiron-3670** (6 cores, 60 GB RAM) has 7 agents, the Android emulator and a macOS VM. Wrap heavy commands in a shared lock:
```
flock /tmp/night-heavy.lock <npm ci | npm run build | gradle ...>
```
- **imac** (8 threads, about 4 GB free) and **poweredge-r350** (16 threads, about 6 GB free): keep builds to one at a time.
- **LocalAI** (`https://localai.eom.dev`) is shared production with slow single-GPU inference. Don't use it in loops.
## Timeline (EST)
| Time | Milestone |
|---|---|
| 22:45 | Kickoff. The design council researches. Infra teams set up (testnet, Android SDK, macOS, SSO scaffolding, UI shell, beta fixes). |
| **23:30** | **Design v1 frozen** (`docs/game/DESIGN.md`). The engine team implements it. |
| 23:45 | **Engine API contract** (`docs/game/ENGINE_API.md` plus TypeScript types) on the integration branch, so UI, simulation and modes can build against it. |
| 00:15 | Engine alpha. Simulation starts bot matches. The UI wires up real matches. |
| 00:45 | Balance report v1. The council tunes the rules (v1.1). |
| **01:10** | **Code freeze:** fixes only. The lead integrates. QA plays end to end. |
| 01:25 | Final reports in each issue. The lead writes `docs/night/REPORT.md`. |
| **01:30** | **Stop.** |
## Teams
| Agent | Machine | Issue |
|---|---|---|
| council-designer-a, council-designer-b, council-data | imac | Game design council, card data analysis |
| council-critic, night-lead, night-review, macos-fetch | tower-plus | Design council (critic), integration and QA, iOS (download) |
| engine-a, engine-b | inspiron-3670 | Game engine |
| ui-a, ui-b | inspiron-3670 | Game UI and AI opponent, beta fixes |
| modes | inspiron-3670 | Peer-hosted game modes |
| mobile-android, mobile-ios | inspiron-3670 | Android app, iOS app and macOS VM |
| sim-testnet, sim-balance, sso | poweredge-r350 | Testnet and simulation, eom.dev accounts |
## What the cards hold (game design input)
Each card's data comes from `shared/enrichment.ts`: `PageEnrichment` and `MintStatsSnapshot`.
- **Identity:** `title`, `description`, `wikidataId` (structured facts: instance-of, dates, coordinates...) and `categories[]`
- **Size and history:** `pageBytes` and `revisionId`
- **Reach:** `languageCount`, the number of language editions
- **Pageviews:** monthly views, `total`, `dailyAverage` and `trendPercent`
- **Derived 0–100-ish scores:** `stats.attention`, `stats.depth` and `stats.reach`
- **Two values for everything:** an immutable **at-mint snapshot** and **live current values** that change over time
- **Duplicates:** the same article can be minted more than once, each copy with its own snapshot
Two facts to design around:
- **New players own no cards.** The design must give them a way to play immediately, for example starter decks of preview or loaner cards that don't touch NFTs.
- **Cards are NFTs.** A match must never move or burn cards on-chain tonight.