The fold is real — but the story changed

Your fold math was right — and exactly-180° really exists as a legal Penrose object. It folds to exactly 60.00°, the seam seals, and once folded it is RIGID — a trihedral corner that holds its bowl shape with no flex.

But it is not five petals. Five evenly-spaced 36° petals would force the parent vertex to ten thin tips — the engine's own named-invalid Star, "a leaderless circle cannot close." Five separate tiles can never carry exactly 180° (zero hits across every system). And "one tile deliberately left out" never leaves 180° — no Penrose corner is a straight angle.

The real object is the HALF-NOOK: one thin rhomb (36°) + two thick rhombs (72° + 72°) = exactly half the circle, mounted over five open slices. It is literally half of the legal Nook gathering — and its other half is its own mirror. Socially: 2 stewards + 1 newcomer close the bowl together.

Also proven: kite/dart can't do this at all — its seam edges are length 1 vs φ and can never seal. The jewel is a rhomb object. Evidence: apps/tessacraft/tools/fold_vertex_verify.mjs, rerun anytime.

💶 Marketplace fee — ✅ RULED. Nothing waiting on you here.

You answered this in-session (2026-07-18): "Small flat fee, 5 euro per transaction total for now." Small and flat, exactly the non-extractive shape the council recommended — the same for every payer, no friction a payer avoids. "For now" is recorded, so it's revisitable without ceremony. Nothing is built against it yet (no marketplace checkout exists); the number waits, ruled, for whenever the marketplace lands. · source: RULED_marketplace-fee-5-flat-wax-is-knowledge-transfer…2026-07-18.md

🎲 Odds — ✅ FULLY SPECIFIED (your "to be clear" + midday confirms, 2026-07-18)

One jewel always powers the token; TOKENS stack on it — N earned tokens ⇒ √N draw odds (five ⇒ √5). Boost recipe = the six non-thread resources; thread is exempt because it needs other people — the door back in is always work you can do alone. Nothing purchasable boosts odds; money never reaches the draw. Scarcity self-corrects through more hosting. Recorded in canon (memory + lexicon); no build yet (prod frozen).

✅ Both confirms answered ("Keep wax and cap of 5 confirmed, streak realized not separate"): CAP = 5 is law — the stack hard-caps at five, max odds √5 ≈ 2.236 · streak = REALIZED — no separate rejection-streak mechanism exists or will ever be specced; rejection → time at home → resources → tokens IS the boost. And WAX stays wax — the name council is resolved. Nothing in this card waits on you.

📼 Recordings — ✅ your standing order is in force

You ruled it plainly: no recording gets transcribed — #64, #63, any of them — unless you name it and say so. A file landing in import/ is not a flag by itself; we flag-and-rename only. Recording 63's staged routing is held accordingly. When you want one read, name it anywhere and it moves.