Executive Brief

Village.

Teaching community before economy.

SAMLLC · Working Theory · 2026

01 — Problem

The wrong lesson

Every educational game teaches either individual skill (math drills, puzzle solving) or competitive economics (tycoon games, trading simulators).

None teach the thing that actually makes civilization work: interdependent systems maintained by a community.

Kids learn to optimize for personal score, not for collective resilience. The games we give them model a world where the smartest individual wins. The real world runs on the village that doesn't fall apart when one person has a bad week.

02 — Concept

Build a village together

Village is a first-person building game where a child manages one plot in a shared world. The game enforces physical reality.

Water flows downhill. Crops need irrigation. Buildings need foundations. Paths connect neighbors.

You can't build a roof without walls. You can't grow food without water infrastructure your neighbor helped build. You can't repair your tools without the smith who needs ore from the miner who needs food from the farmer who needs water from the channel you dug.

The lesson isn't "cooperation is nice." The lesson is "cooperation is the load-bearing structure."

03 — Mechanics

How it teaches

Physics-first: Water flows. Fire spreads. Structures have load limits. Nothing works because the game says so — the physics simulation is the teacher.
Build order: Foundation → walls → roof. Irrigation → soil → crops. The game won't let you skip steps. Skipping steps is how real communities fail.
Shared infra: Water channels, roads, bridges are shared resources. Any player can contribute. No player can monopolize. Maintenance is everyone's job.
Resilience score: Not scored on wealth or growth — scored on resilience. Can it survive a flood? A drought? A player going offline for a week?
AI coach: Socratic guide asks questions: "What does your village need before it can grow?" Never directive. Asks the question that leads to the answer.
No combat: The only adversary is entropy. Things wear out, weather happens. The challenge is maintenance and adaptation, not destruction.

04 — Architecture

Built on Lattice

Village runs on the Lattice stack. The game is a Trojan horse for the entire platform:

Identity: Each child has an NFT-anchored identity. Their plot, their progress, their reputation — cryptographically theirs.
Consensus: Shared world state validated by BFT. No child can cheat their neighbor's resources. Trustless cooperation on a trustless network.
Sovereignty: Data stays on each child's Coop device. Learning profile encrypted — parents own it. COPPA-compliant by architecture, not policy.
Safety: Behavioral lockout → parent notified in <60s → re-auth required. Immutable incident record signed ML-DSA-87 — cannot be deleted by the child.

05 — Why it matters

The product that makes it real

Village is the product that makes the Lattice network tangible to a family.

Not "post-quantum cryptography" — "the game my kid plays where they learn how communities work, on hardware we own, with data nobody else can see."

The market is full of games that teach kids to compete. We don't have one that teaches them to build something together that lasts.

It's also, genuinely, the game we wish existed for our own kids.