YAU — The Protocol Coordinator

One-line pitch: YAU sits between the low-level infrastructure and the higher-level game mechanics, keeping state coherent. Plumbing — you don’t call it directly.

What this is

YAU is a coordinator layer. It holds a reference to its parent ZHOU, maintains a Theta Bao and a two-slot Monopole counter, and exposes a React() function that owner contracts call to advance the cryptographic state machine.

Think of it as middleware — the contracts above it (YANG, SIU, and the gameplay contracts) rely on YAU’s state staying consistent.

If you’ve played a web3 game before

• Closest analogy: a network router — moves state between layers without being the endpoint.
• Or: middleware in a web stack — transparent, but essential for request flow.
• Or: a DeFi accounting module — reconciles state across pools.

Dysnomia term	What it maps to
YAU	Coordinator between ZHOU plumbing and higher layers
React()	Owner-called state advance
Theta	YAU’s internal Bao
Monopole[2]	Paired state counters

What you actually do with it

• Nothing directly. Higher contracts call React() as part of their flows.

Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.

YAU0x7e91d862A346659DaEEd93726e733C8C1347a225

YAU.Monopole(uint256)Read

Open this function to load its call form.

Rewards / costs

• Cost: none directly.
• Reward: none — infrastructure.

Requirements & gating

• None for players.

Where it connects

Depends on ZHOU. Feeds into YANG. Referenced throughout the CHATLOG chain.

Quick FAQ

Q: What does React actually change? A: Advances YAU’s internal state by one cryptographic step, producing a new Bao the caller can use.

---

Want the Solidity? The contract reference lives at technical/core/07_YAU.