# Third-Party Review Brief — Cascade × The Game Crafter

**Date:** 2026-07-03
**Reviewer:** ghojualamanchu (third-party)
**Submitter:** tenchi
**Operator (drafting):** Zo
**Status:** Open — pending review

---

## Why you're being asked

We've decided that The Game Crafter (TGC) is a viable print-on-demand host for the Cascade relational substrate, but we want a second opinion before we commit engineering and design resources. Your job is to read the engineering analysis and tell us:

1. **Yes, build it** — and on which substrate
2. **No, don't build it** — and why (what did we miss?)
3. **Conditional yes** — build it if X, otherwise Y

You're not being asked to design the product. You're being asked to **render a verdict on viability and surface the constraints we may have missed**.

## What to read first

- **`SOP-2026-07-03-game-crafter-deep-dive.md`** — the process record (what we did, in order)
- **`cascade-game-crafter-analysis.md`** — the engineering payload (component specs, fit math, distribution paths, cost estimates)

You can skip the v2 source docs unless a question below pulls you in. They're referenced where the analysis depends on them.

## The five questions, ranked by importance

### Question 1 (load-bearing): Substrate choice

The 127-hex map has a **3:2 aspect ratio** (landscape, approximately). TGC boards are square (1:1). The two substrate options:

- **Medium Six-Fold Board** (508×508mm, 6 panels) — arranged 2×3 = 1016×508mm, aspect 2:1. **Closer to 3:2.** Hex size at 80–85mm.
- **Large Quad-Fold Board** (508×508mm, 4 panels) — arranged 2×2 = 1016×1016mm, aspect 1:1. **Clipped at corners** unless hex is shrunk to ~70mm.

**Is Six-Fold the right call, or is there a third option we're not seeing?** Are we miscalculating the hex bounding box? Is there a board product (custom or otherwise) that gives a 3:2 native aspect ratio?

### Question 2: Pattern-type encoding

A Cascade hex can hold a **Cohort** (person), **Location** (place), **Utility** (tool/practice), or **Expression** (artifact). The board is currently designed for Cohort hexes (names, photos, or note cards).

**How should the physical pieces encode the pattern type?** Options:
- A) Tile back stamp (Cohort = blue, Location = green, etc.)
- B) Separate punchout sets per pattern type (4 sets, mixed at use time)
- C) Type stickers applied to blank tiles
- D) Pattern-type printed on the substrate per hex (operator pre-fills)

**Which option is most ergonomically sound for a 3-minute Daily Three practice?** Which scales best when a hex transitions between pattern types over its life?

### Question 3: Digital integration

TGC has a developer API. We may want a future digital Cascade app that mirrors the physical board state.

**Is TGC's API sufficient for a future digital layer, or should we plan for a separate API host (e.g., zo.space route) and treat TGC as print-only?** What does the API actually expose — just cart/order management, or full state APIs?

### Question 4: Cohort distribution model

Three paths:
- **Marketplace:** Self-serve retail on TGC. Slowest scaling, broadest reach.
- **Concierge:** Bulk orders for cohorts. Faster, cohort-specific SKUs, but requires per-cohort negotiation.
- **Hybrid:** Marketplace default + concierge for Cohort Zero and institutional partners.

**Which model is right for a Cohort Zero pilot of, say, 10–20 people, then scaling to subsequent cohorts of 30–50?** Are there TGC-specific constraints we're not aware of (minimum order quantities, IP terms, designer royalties)?

### Question 5: Hex-size tradeoff

The Large Hex Tile is 95×83mm and 2mm thick. 127 tiles = ~2.3kg per Cascade set. Substantial.

**Is this the right tile size for cohort play, or should we look at the Medium Hex Tile (smaller, lighter) on a larger board?** What does actual play ergonomics demand — a heavy set that's stable on a table, or a light one that's easy to rearrange?

## Bonus questions (if you have time)

- **Currency representation:** How should Hearts, Stars, Moons, Hourglasses, Balloons be marked on tiles? Printed icon, sticker, punchout, or chit?
- **Warmth band representation:** The five warmth bands (Blazing/Hot/Warm/Cool/Cold) need to be visible at a glance. Tile color? Back pattern? Substrate coloring?
- **The R0 / You hex:** Should the operator's hex be physically distinct (e.g., a different shape, a name plate, a fixed position), or should it be a regular hex with a "You" marker?
- **Course workbook:** Does TGC's book component (19 variants) make sense for the Practitioner Path, or should the workbook stay digital?
- **Multi-pattern-set support:** If an operator wants to run Cascade on a Location (a city, a building), do they need a separate physical set, or can one set with pattern-agnostic tiles cover both Cohort-centered and Location-centered use cases?

## What we don't want from you

- **Don't re-litigate the Oscillator Model.** The thermodynamic-ceiling framing is settled in v2.
- **Don't redesign the hex grid.** The 127-hex / 7-ring geometry is canonical. If you think it's wrong, that's a separate conversation, not this one.
- **Don't write production specs.** This is a viability review, not a build document. Build specs come after we have a substrate decision.

## What we DO want from you

- **Yes/No/Conditional verdict on Question 1.** With reasoning.
- **Concrete answers on Questions 2–5** (or "I don't know, here's who would").
- **Anything we missed.** Constraints, opportunities, or risks that didn't appear in our analysis.
- **A recommendation on the digital-integration question** (Question 3) — this affects whether we build toward TGC-as-platform or TGC-as-printer.

## How to respond

Reply in the same folder (`Cascade/`) with a file named `third-party-review-response.md` or similar. Use the same verdict taxonomy as the fact-check SOP (OK / FIX / MOVE / CUT) if it helps structure the response, but free-form is also fine.

If you need to read the v2 source docs for context, they're at `anthrocybernetics-foundation-v2/` in the workspace. The Oscillator Model and Cascade Hexgrid Spec are the load-bearing ones.

## Timeline

No hard deadline — but the goal is to commit to a substrate and start design before the Cohort Zero pilot kicks off. If a 2-week turnaround is reasonable, that's the target. If you need more, just say so.

---

*Thanks for the second read. We're trying not to ship a physical product that doesn't hold up under cohort use, and your perspective is the missing piece.*