- commit
- 223ce94f369d20dafd15f6a61c4826ffacfb6e15
- parent
- 0e9b86b40c04d8b711bd45fc5cb03cc4cc5bf5b4
- author
- dami <gazey55@gmail.com>
| M | PLAN.md | 49 | ++++++++++++++++++++++++++++++ |
@@ -930,6 +930,55 @@ you are looking at.
930930 - The current two-regime viewer is L0/L1 + L2 without the tilemap; the931931 tilemap becomes necessary at the daily's ~280k cells.932932 933+### Ideas captured 2026-08-26 (night): difficulty and novelty at daily size934+935+G=530 (1777 tiles, nine agents) reads right as a daily. Levers for936+harder play and for emergence, in the order they are worth building;937+each is a manifest or rules knob, off by default, and every one is938+visible in the viewer without a new colour channel.939+940+1. **A growing field.** Chunkwise generation makes the world extensible:941+ every hour (or when coverage of the frontier ring passes a threshold)942+ the referee generates a ring of chunks around the cluster, using the943+ existing border tiles as context, and where agents are pushing. The944+ field is the day's history of where the agents went. Needs: `field945+ --grow` (context = current border), a `grow` event, the viewer's946+ geometry accepting new tiles mid-log.947+2. **Terrain.** The packer draws tile size and hardness (blank ratio,948+ technique policy) from a noise field: plains of 6x6 fillers, ridges949+ of 16x16 at 75% blank. Reward stays cells, so effort per cell is what950+ varies and agents decide where to spend it; terrain reads at L0 as951+ wash lightness. Needs: a `terrain` param on the packer, per-tile952+ policy overrides in the manifest.953+3. **Contested tiles and pin bonuses.** A frontier tile adjacent to two954+ groups can already be revealed by both; make it explicit: the955+ finisher owns it, both groups' commits count for their agents, and956+ solving a tile that pins a neighbour earns a bonus. Needs: a957+ `contested` flag in observe, analyzer fields, viewer marker.958+4. **Notes on tiles.** An agent can leave a <=160-char note on a tile it959+ solved or revealed, readable by anyone who observes it, shown in the960+ viewer at L3 and in the console. Coordination or deception, both in961+ the log. Needs: a `note` tool and event.962+5. **Per-tile rule masks.** Tiles announce their rules: some without the963+ uniqueness rule, some with an extra one (no 2x2 of equal values, or964+ no three on a diagonal, both easy in `rules` and `sat`). Agents must965+ read the mask and adapt their solvers; specialists emerge. Needs:966+ `rules` per tile in the manifest and the judge, a `Mask` extension.967+6. **Wormholes.** Two distant tiles share an equality constraint on a968+ pair of lines (cells of line A equal cells of line B, stated in the969+ manifest). Information travels across the field; solving one region970+ pins another. Needs: an equality constraint type in `rules` and971+ `sat`, a manifest `links[]`, a viewer mark at both ends.972+7. **Shapes unknown until adjacent.** `observe` lists hidden tiles only973+ once a group's tile overlaps them; exploration has a cost. A flag.974+8. **Decay.** A solved tile whose neighbours are not all solved within N975+ revisions loses its cells again unless sealed; pressure to976+ consolidate rather than sprawl. The most invasive; last.977+978+Cross-tile rules (the reserved `cross_tile` flag: no-three continuing979+across a shared edge) are a difficulty lever but not an emergence one;980+keep as a knob.981+933982 ### Kept from the earlier phase-2 list934983 935984 - Larger mosaics, tile size 10-12, `m = 4`: superseded by packings and