
The Core
The micro game is routing water through a network you grow. Like Factorio's belts, but with timed gates instead of conveyors, palms instead of factories, and other families instead of biters. Everything in this document serves one design principle:
The Three Controls — the spine
Water. Trade. People. Three skill panels the player gets good at over hours. The micro skill lives in water. The middle in trade. The macro in people. Mastery is the integration — closing a gate this hour to fund the trade this week to fund the welcome this month. The three feed each other.
The Warcraft Layout — borrowed grammar, not borrowed feel
You control only the father. The wife, son, visitors, animals are the world reacting to your work — not units to direct. No battles, no commanding, no unit panel. The Warcraft borrowing is the screen grammar: a strong top zone for the world-state (sun, season, time), a large central viewport for the oasis itself, a thin bottom strip for the few essential controls. Less UI, more world.
~75–80% of screen · falaj running, palms, family, the network you've built
Closer reference than Warcraft for the actual feel: Pentiment, Eastward, Sea of Stars — pixel games that put the world at centre and let the UI breathe.
The Falaj Game — Control 1 in detail
What the player does, every minute, that gets better with skill
Your falaj is a network of channels, junctions, and gates. Water enters from the spring at a fixed rate. It flows downhill. At each junction sits a dallah-stone gate — historically real: water in a falaj was shared by time, not volume. Tap a gate to cycle it: open → half → closed.
Every node downstream has a thirst meter that drains continuously. Palms need water to fruit. Garden beds to grow. Animals to live. The cookfire to be filled at dawn. You decide which gate opens for which hour.
This is the loop the player gets good at: read the network, predict the bottleneck, route the water before anything goes dry. Like chess, each move is small. Like Factorio, the whole network is the game. Like real Bedouin life, the rhythm is timed and shared.
The depth comes from change. A sandstorm clogs a segment — you reroute. Dates ripen and need extra water for a week — you sacrifice the goat trough. A new family arrives — their palms become new nodes on your network. Can the network absorb them without anyone going thirsty?
The Chain of Progression — water → dates → silver → expand → welcome
No spaceship-scale macro. The whole demo is one oasis. The win condition isn't "automate everything" — it's "build a network strong enough to absorb another family without anyone going thirsty." Realistic, weather-vulnerable, human-scale.
The Three Cycles
Tap a gate. Watch water reroute. Read the network. One small decision repeated, that adds up to expertise.
Chess: moving a piece.
Restore this falaj segment. Plant this row of dates. Build this basin. A multi-step goal with visible result. The middle is where silver gets spent.
Chess: an exchange.
Become the oasis another family chooses. The network that absorbs strangers without breaking. The macro reward is people, not points.
Chess: the won game.
Factorio's belts feel good because placing one belt creates a chain reaction you can see. Our falaj gates do the same — closing a gate visibly stops water downstream and redirects it. The network is legible. The mistake is legible. The fix is legible. That's what makes a real micro game.
Unlike Factorio, there's no spaceship to escape to. The macro is human-scale: a stranger arrives, can your network absorb them. If yes, you have more characters, more activity, more silver flowing. If no, the oasis stays small. Every action serves this — water keeps the palms alive that produce the surplus that pays for the network that absorbs the welcome that grows the family. That's the chain. It's why one click feels like ten clicks.
The World
Narrative before mechanics. Anchor the setting, the time, the tone — and define the antagonist that all systems will push against.

Al Ain (Buraimi Oasis) is the right answer historically — and a locked principle of the game's storytelling is we never name it on screen. The setting is unmistakable to anyone who knows the UAE: the falaj architecture, the date palms, the proximity to Jebel Hafeet, the specific shade of sand, the Bedouin family names that drift through dialogue. An Emirati will recognize it in the first thirty seconds. A foreign player will simply experience "a desert oasis at the start of the 20th century."
Why this matters. Naming Al Ain explicitly turns the game into a documentary; leaving it unnamed turns it into a feeling. The Emirati player gets the pleasure of recognition — the small, private joy of "I know this place, this is mine" — which is far stronger than being told. The foreign player gets a beautiful Arabian setting that doesn't require prior knowledge. Both audiences win, because we trusted them to read the world.
The historical reality (for production reference only — never said in-game): the falaj has flowed for 3,000 years, UNESCO World Heritage. In 1898, Sheikh Zayed bin Khalifa Al Nahyan ("Zayed the Great") was 63 years old and had ruled Abu Dhabi for 43 years (1855–1909). Abu Dhabi island was the political capital; Al Ain was the Al Nahyan family's interior heartland — date orchards, summer retreat, power base in the desert. His eldest son Khalifa built Qasr Al Muwaiji here in the early 1900s. When Zayed died in 1909, Khalifa was offered succession and refused — preferring his advisory role from Al Ain. His brother Tahnoun ruled instead. (None of this is ever stated in-game. The player feels it through the falaj, the architecture, the rhythm.)
Your family's arc — start in the interior, eventually send a son to the coast — mirrors the actual founding journey of the Al Nahyan family. Same desert. Same falaj. Same dream. The game isn't about historical figures, but it walks the same road.
You're right to start before the Iranian traders raise taxes. That moment is your Chapter 1 ending — the news arrives, history begins to move, and the player feels the macro cycle for the first time. Starting in ~1898 gives you four quiet years of family life before the world tilts.
The demo ends with that single line of news — "Word has come from Lingah. The taxes have risen." — and the player understands without being told: my son will leave home.
You've identified the exact creative spine: tender heart, deep systems. Stardew Valley, Spiritfarer, and Dwarf Fortress all do this — the art and writing carry the warmth while the systems carry the depth. The player is solving a logistics puzzle, but the people being fed are their family. The clicks are sharp; the meaning is soft.
The player approaches the game as the father of the clan. Not a commander, not a god — a father. You don't issue orders, you set example. Your wife observes what you do. Your son mirrors what he sees. When the player doesn't know what to do next, the answer is always: what would the father do? That is the emotional anchor inside the deep system.
You found the spine. Unlike Legacy Roots where the government was the antagonist, here it's the desert itself — and the desert is both opponent and teacher. Heat, sandstorms, drought, distance. But also: water under the rock, dates from palms, cool nights, stars to navigate by. The desert doesn't help anyone. But the desert taught the people to help each other.
This is the central design truth: in a place this hard, generosity is the only survival strategy that scales. Hoard, and one bad season ends you. Share, and the network of generosity catches you when your turn comes. Karam isn't a virtue. It's an algorithm.
The antagonist evolves chapter by chapter — see the Beats & Chapters expander below. Desert → Distance → Ambition → History → Modernity. Each beat changes what the family is up against.
Each chapter is a phase marked by an external beat the family doesn't choose. Both the protagonist and antagonist evolve. The micro and middle cycles transform; the macro cycle restarts at a higher scale. Mektub.
The Dilogy — locked
Dilogy = a two-part work. Game 1 is the complete Bedouin saga ending at the moment oil is struck. Game 2 is the complete modern saga from oil-strike to present day. Each ~70 years of in-world time. Each playable as a standalone, together telling the full Mirath. Game 2 only proceeds if Game 1's demo earns approvals — sequel is hypothetical until Game 1 ships and finds its audience.
Game 1 · Mirath: A Saga of Legacy, Trade, and the Desert · ~25 hours
1898 → 1958. The Bedouin saga. Full arc: build → crash → recovery → oil discovered. One generational handoff. Demo is the first 25 minutes of Chapter I. Game 1 ends with the cinematic of oil struck at Bab — the family gathered, watching the rig.
Game 2 · Mirath 2 · ~30–40 hours · sequel
1958 → present day (2026/2027 — releases when the game does). The modern saga. Dubai becomes a trade centre, oil replaces water as the central resource, building-simulator feel with the same Falaj Game mechanics — but routing oil through pipelines instead of water through channels. Money is no longer the question. The new constraints are alliances, civic identity, what kind of city you let it become. Two generational handoffs. Possible climax: the construction of Burj Khalifa as the symbolic completion of the Mirath — the family's name on the tallest building in the world. Iran war material, federation moment, the dilogy threads as candidates for narrative beats.
A third game is open — future-set, only if the dilogy lands. If we get there, it would be the children's children deciding what survives of the family's tradition into whatever the UAE becomes next. Speculative. Not designed.
Why a dilogy, not a single game
Two excellent games > one bloated game. Game 1 ships smaller, tighter, focused on the Bedouin saga ending at oil discovery. The sequel ships when the audience exists, with full Dubai scope and the long generational sweep. This is the Stardew Valley → sequel pattern, the Hades → Hades 2 pattern. Each game complete in itself; together they tell the full Mirath. The shape of Game 1 is a long slow inhale (build the life, Ch I-II, ~10h) → catastrophic crash (lose it, Ch III-IV, ~11h) → slow rebuild (survive, Ch V early) → oil moment (the world changes, Ch V late). That's a real arc, shipping at viable scope.
On generations
Father starts at age 30 in 1898. Game 1 covers ~60 years, ending in 1958 — by then the family is three generations deep. One voluntary handoff happens during Game 1 (Chapter II's Crossing — father to son around 1910, son becomes lead). The crash is endured by the whole family. The oil cinematic is witnessed by everyone alive. No forced death. Game 2 begins a generation later: the son is now the elder, his children are the protagonists.
The arc
Physical antagonist (desert) → social antagonist (distance, ambition) → historical antagonist (depression, modernity) → existential antagonist (forgetting). The player goes from fighting nature to fighting forces no individual can fight — and learns that the only weapon against history is family.
This is the deepest theme, the one we never name aloud: karam is how families survive history. Hoard, and one bad season ends you. Share, and the network you built catches you. That's why Chapter IV's antagonist is "history itself" — by then, every act of welcome from Chapter I matters.
What this gives the demo: the player completes the first 25 minutes of Chapter I and ends with news from Lingah arriving. They haven't met what comes after. But they understand the road continues. That's why they want the full game.
The water that built a country
The Al Ain / Buraimi oasis system is the largest in the region — six interconnected oases watered by the falaj system, an underground irrigation network at least 3,000 years old. The oldest known falaj in the UAE was discovered at Hili, in Al Ain, and is a UNESCO World Heritage site. By 1898, the falaj here had been working continuously for three millennia. This is not legend. This is engineering.
How the falaj actually works
Wells were dug at the foot of Jebel Hafeet, sometimes 30 kilometres away. Underground tunnels channelled water from those wells down to the date orchards. Each plot received water for a fixed time, controlled by a solar frame, then was dammed off and the water diverted elsewhere. The system was shared and timed — your slot, my slot, the neighbour's slot. The falaj was the original communal infrastructure.
Who lived there in 1898
Al Ain was the interior heartland of the Al Nahyan family in 1898 — though Abu Dhabi island remained the formal political capital. The ruler was Sheikh Zayed bin Khalifa Al Nahyan ("Zayed the Great"), who reigned from 1855 until his death on 19 May 1909. His eldest son Khalifa built Qasr Al Muwaiji here in the early 1900s. When Zayed the Great died in 1909, Khalifa was offered succession and refused — preferring an advisory role from his Al Ain headquarters. His brother Tahnoun (1857–1912) became ruler instead. Other Bedouin families — Bani Yas, Al Bu Falah, Dhawahir — lived in and around the oasis, farming dates, raising camels, trading inland.
What our family is
A Bedouin family arriving at one of the smaller, abandoned plots at the edge of the Buraimi oasis system. Not famous. Not noble. The same people who actually built this place — and from whom the future leaders of the country eventually came.
The Journey
The demo is Chapter I only. The dynasty mechanic doesn't appear — that's the surprise of Chapter II. Shape the player's first 25 minutes carefully: each scene runs the three cycles at a different scale.
25 minutes is the right size to make the player feel all three cycles at least once. Less than 20, the macro cycle never lands. More than 30, you start losing the Dubai playtester's attention. The arc fits: 8 min survival (micro dominant) → 10 min building (middle takes over) → 7 min welcoming (macro becomes visible) → news from Lingah (macro arrow points to Chapter II).
Your instinct is exactly right. The dynasty mechanic does not appear in the demo. The player thinks they finished a great oasis-building game. Then in the final frame, the son — now nine — hauls water in his small hands with the same animation as the father, slightly smaller. A line of text: "To be continued."
The full game reveals: he was the protagonist all along. You were just teaching him. Every choice you made in front of him is now part of who he is. That moment of recognition is the hook for the full game.
The cinematic budget: 2 cinematics × 30 seconds = 60 seconds total
Two cinematics carry the whole emotional arc. Everything else is interactive gameplay. No zoom-ins on facial expressions, no described emotional behaviour — just the player playing.
Cinematic 1 · The Arrival · 30 seconds · opens the demo
Pixel-art wide shot. Family — father, wife, son, one camel — walking behind a gazelle across a dune. Gazelle leads them down to a cluster of wild palms. Family stops. Gazelle drinks at a hidden pool. Family stares. Cut to gameplay.
(This is historically accurate to the founding of Abu Dhabi — hunters followed a gazelle to water and settled. Same desert, same story.)
Scene 1 · Survive · ~5–7 minutes of gameplay · The first gate
You are at the wild palms. The camel kneels and won't get up — it needs water. Your wife sits in shade with your son. The tutorial happens through her voice — 3–4 short lines: "The wild palms grow there. There is water under them." → "Dig where the ground darkens." → "The camel needs to drink before it can stand again."
The micro game starts immediately: dig at the palms, find water, place your first dallah-stone gate to route the trickle to the camel trough. One gate. One basin. One palm. You learn the mechanic in 90 seconds. Camel stands. Wife stands. Son follows you.
Heat appears as gameplay: the Heat Bar enters across the top of the screen. A sun-icon slides through dawn-yellow → noon-red → dusk-yellow. In the red zone, your walk speed drops by half. Carrying anything drops you to 30%. You learn within one in-game day: do heavy work at dawn, rest in shade at noon, work again at dusk. Shade is cast by palms — visible darker pixel patches that move with the sun. Standing in shade restores work-energy. The game teaches this without text.
Scene 2 · Build & Sell · ~10–12 minutes · The chain unlocks
Camera pulls back. You see the whole plot. The build menu opens. The chain begins:
- Restore the falaj segment — your network grows from 1 to 3 gates. You schedule water across three palms.
- Plant the date garden — a new node on the network. Garden bed needs water for a week to mature.
- Build the shelter — gives you a shade node where the wife and son can rest. (Stone frame + palm-frond walls — historically real arish/barasti architecture.)
- First sandstorm — clogs one segment of the falaj. You reroute. The shelter holds.
- First caravan arrives. A trader stops. "Three sacks of dates for one silver." You trade. Silver is now a visible resource.
- Silver buys upgrades — more palms, more gates, a second basin. Your network grows from 3 to ~8 gates.
Cold returns: winter night drops the Heat Bar to freezing blue. The family huddles around the cookfire. The cookfire burns palm fronds. Let it die and the next day's work is slow. Fronds are now a resource you keep stocked.
Scene 3 · Welcome · ~5–7 minutes · The macro arrives
A second family appears on the horizon and walks toward the oasis. Pour qahwa or don't. One decision, one tap. (Walk to the dallah hanging by the fire, pick it up, walk to the visitor, tap.)
If you pour: the family stays. Their two palms become new nodes on your network. Two extra gates appear. The visiting man helps clear a clogged falaj segment you couldn't reach — water flow increases by 20%. Days pass in seconds. Dates fruit. More silver.
If you don't pour: they walk on. Network stays small. Days pass anyway. Nothing changes except nothing changes. The reward of welcoming is not abstract — it is more nodes, more flow, more options on screen.
Cinematic 2 · The News · 30 seconds · closes the demo
Pixel-art wide shot of the thriving oasis. A runner appears on the horizon, sprints in. Hands the father a folded letter. The father reads. Cut to the son's silhouette from behind, watching the horizon — three years older, slightly taller, holding two waterskins. Fade to black. "To be continued."
Total: 25 minutes. Sixty seconds cinematic, twenty-four minutes interactive. No facial-expression close-ups. Hi-bit pixel characters communicate through silhouette, posture, and position — not faces. This is a game, not a TV series.

You said it: "the traders arrive, and this is out of our control. It's God's will." That framing is exactly right and it's how the game should feel throughout. The player controls preparation, character, generosity — but not the weather, not the news, not when other families arrive. Mektub. The arrival is the universe acting, and your test is how you receive it.
So the demo's final beat isn't a player choice between Triumph and Choice — it's both. You build successfully (triumph), then a family arrives unbidden (choice), then news of Lingah arrives unbidden (history). Three things happen to you. The player only controls the middle one: do you welcome them? That single choice carries everything.

The coast is Chapter III (Pearl), not the demo. The coast appears after the son crosses to Dubai in Chapter II and grows up there. In the demo, the coast doesn't exist on screen — but the player should feel it just over the horizon when the news arrives.

Forced handoffs feel cheap. The dynasty mechanic must be voluntary, prepared by the world, and refusable forever. This is how it works:
The father visibly slows
Around year 15 of Game 1 (father is roughly age 45), his sprite animations slow by 20%. Walks slower. Digs slower. Work-energy drains 30% faster in red-zone sun. He needs Rest Mode in shade more often. The player feels this without being told. "It used to take me one day to clean the falaj. Now it takes me two."
The son matures into capability
Year 0–6: a small sprite who follows you everywhere. He watches. He catches things heart-to-heart. This is the silsila concept preserved as a mechanic, even though it's not the game's title.
Year 8: can fetch fronds and small loads. Half-worker.
Year 12: can man a falaj gate when assigned. Full half-worker.
Year 18: can do everything the father can do — at full speed. The player starts noticing: he's the faster one now.
The opt-in moment
Around year 15–20, a new option appears in the cookfire-rest menu (only when the son is age 18+): "Let your son lead." Tapping it switches the player's primary controlled character to the son. The father remains in the world — sitting more in shade, advising at the cookfire, available for occasional dialogue. He does not die. He steps back.
Refusing forever is valid
If the player doesn't want to hand off, they don't have to. The father keeps slowing — at age 60, he walks at 40% speed and can no longer dig. But he doesn't die. The son just stays a worker, never becomes leader. The game observes; the game does not judge. Same principle as the closed-family playstyle: another valid way to play the saga.
Why this design
This maps onto real Bedouin family transitions — elders gradually became advisors, never deposed. It respects the player's choice. And it gives the player a moment of recognition: "I've been him for fifteen years. Now I am ready to be the son."
The handoff is the most emotional moment in Game 1 because the player earned it. Every interaction the son witnessed shaped who he becomes when the player steps into him.
The Systems
The mechanical truth of the game. Resources, world state, failure, what the player sees and what they only feel.
You asked: "Palm fronds — is it really building material in real life?" Yes, historically confirmed. In the UAE, Bedouins built two types of houses, both real:
- Arish / Barasti (عريش) — palm-frond shelters. Mangrove pole frame imported from East Africa, walls and roof woven from date-palm fronds. Used heavily in summer for ventilation; the fronds let the breeze through, more closely woven in winter to keep wind out. The standard Bedouin summer home.
- Gus / mud-block houses — for more permanent inland dwellings, especially in Al Ain. Gus is a mud mixture formed into blocks like bricks. Lower courses reinforced with stones bonded by red clay.
So fronds + stone + dried mud are all real building materials. The question is how many to track in the demo.
Candidate resources for the demo
Water (الماء) — LOCKED. The lifeblood. The spine of the Falaj Game itself. Can't be cut.
Dates (التمر) — LOCKED. Food, gift, trade good. Surplus dates pay for everything. Second spine.
Palm fronds (الجريد). Historically real building material. Renewable (cut sustainably from mature palms). Also fuel for the cookfire — which loops into the cold-night mechanic. Most tactile of the construction options.
Stone. Falaj repair, perimeter walls, lower courses of mud-block houses. Less renewable — found, gathered, hauled. The "heavy work at dawn" resource.
Dried mud (gus). Historically the dominant Al Ain building material. Visually similar to stone — risk of being confused if both are tracked.
Salt, coffee beans — defer. Salt belongs to Chapter II caravan trade. Coffee folds into the hidden karam system.
Two configurations worth choosing between
Option A · Water + Dates + Fronds (3 visible). Fronds do double duty as building material AND cookfire fuel — which makes them part of the winter-night mechanic too. Lean, tactile. Stone and mud are abstracted into the "build the falaj" or "build the shelter" project actions, not separately tracked.
Option B · Water + Dates + Fronds + Stone (4 visible). Adds stone for falaj/wall building. More historically grounded. Trade-off: one extra UI slot, slightly slower onboarding. If demo players seem to grasp 3 fast, we add stone in production builds.
My recommendation: start with A. Three resources is the magic number for a 25-minute demo, and fronds-as-fuel gives the winter mechanic a real consequence.
The hidden resources
Karam (كرم) — goodwill. Never displayed. Visible only as consequence: travellers stop, caravans bring rare goods. The diyafa system.
What the son saw — the dynasty seed. Logged silently. Revealed only in Game 2 when the son acts based on what he witnessed.
Across the full saga
Each chapter adds one resource and lets one fade. Water always stays. Game 1 Ch. II adds silver (the silver expands the falaj). Ch. III adds stone (the oasis becomes permanent — mud-block houses, walled gardens, stone-lined wells; visual signal of generational time passing). Ch. IV (Crash) demands you draw on stored karam — no new resource. Ch. V adds oil. Mirath 2 carries oil forward as the central resource and adds concrete as the new construction material of the city era.
The Heat is the one antagonist that walks with you through every chapter of every game in the dilogy. You can't get rid of it, defeat it, or control it. You can only build infrastructure that lets you live with it. The infrastructure is shade. The mechanic is rhythm.
"Noon is when you stop building the world and start tending it."
The meditative principle · for the player who chooses to listen
1. The Sun — large, central, upper
Per the Warcraft layout: the sun sits at the top, in the middle, big. Not a thin pixel bar — a real graphic element with the day-arc visible as a soft band. The sun's position IS the time-of-day reading. The eye learns to glance up the way a driver glances at a fuel gauge. In the red zone, heat haze shimmers around the sun itself, then bleeds into a subtle warm filter over the world below.
2. The screen filter — the heat is visual, not just numeric
When the sun crosses into the red zone, the screen takes on a warm filter — colors shift slightly amber, contrast lifts, the air visibly thickens with shimmer. The visual feel of being in sun is uncomfortable. Step into shade and the filter softens, colors settle, the air clears. The player feels the temperature change before reading any number, because the world itself looks different.
3. Shade is built, not found
This is the locked rule, important: Shade is everything the player created. In real Arabian desert there are not many natural rocks or trees. Maybe a few wild palms, maybe a single boulder. Mostly there is sand and sun. So in the game, shade is infrastructure — palms you planted, shelters you built, awnings you wove, the cookfire-shade your wife sits under. Wild palms exist (Scene 1 — the gazelle leads you to them) but they're the starter cooling, not the destination. You build your own oasis of shade. The desert provides almost nothing.
4. Showing the character in shade — the visual rule
Important you raised this. When the character moves under shade, we still see them clearly — shade is not occlusion. The rendering is: a darker pixel patch on the ground where the shade falls, and the character sprite tinted slightly cooler (blue-shifted, ~10% darker) when standing on that patch. The patch moves with the sun. The character is always visible — we just see them differently: cooler, calmer, restoring. Same sprite, different palette tint. Cheap to build, perfectly readable.
5. Rest Mode — time accelerates in shade
This is the click-movie mechanic, refined. You can enter Rest Mode only in shade you've built. Tap to enter. Time accelerates to roughly 3×–5×. The character is visible sitting under the palm or in the shelter. The falaj keeps running. The palms keep growing. The sun keeps moving. The game keeps playing without you for a while.
You exit Rest the moment anything important happens: a caravan approaches, a sandstorm forms on the horizon, your wife calls you to eat, the cookfire dips low, the son needs you. The game pulls you out. You also exit by tapping anywhere.
This means shade is more valuable than just cooling. Built shade lets you skip the boring parts of the day on your own terms, while letting the world continue. The desert wins by being hot — not by being boring. And the more shade you've built, the more places you have to rest. More water → more palms → more shade → more rest stations → more efficient days. The loop closes back into the falaj game.
6. Shade-zone gameplay — what you DO when noon comes
Noon is not dead time. Noon is when you switch rhythms. Things that belong to the shade:
- Weaving — palm fronds into baskets, mats, rope. Cheap micro task. Produces craft items for trade.
- Repairing — tools dull from use, waterskins patch. Done in shade.
- Eating — yes, eating belongs here. Dates with the family. The wife brings food. Simple animations. A small thing the player will love because the game is letting them be, not do.
- Conversation — the wife, the visiting elder, a passing trader sits with you. Short dialogue beats. Lore. Light hints. Not tutorial — a thing that happens when two people share shade.
- Watching the falaj — the camera tilts slightly to show the network you built running. The animation continues; the player just sees their work. Satisfying the way watching Factorio belts is satisfying.
- Teaching the son — when the son is old enough, sharing shade with him advances his capability. He catches it from being near you. Heart-to-heart — the silsila concept preserved as a mechanic.
7. Cold nights — winter threatens the cookfire
Night blue deepens to freezing blue in winter months. Family huddles around the cookfire. Cookfire burns palm fronds. Let it die in a winter night and the next day's work-energy starts low. Keep fronds stocked. Same loop: water → palms → fronds → fire → warmth → work.
8. Sandstorms — the rare big event
Hot months. Storm appears on the horizon. ~90 seconds of in-game warning before it hits. Close gates so wind-blown sand doesn't clog the channels, herd the camel into shelter, douse the cookfire. After: clogged falaj segments to clear, repairs to make. Not failure — a project that pulls you back to the network.
9. Reputation (الصيت) — the hidden third world-state
As karam accumulates from welcomes, more caravans stop, more travellers appear, a family arrives asking to stay. Never numbered. Only felt as more characters on screen, more activity, more silver flowing. Closed-family playstyle: reputation stays low; the world stays quiet; this is valid.
Three sprites you already need, recombined to tell the whole failure story. No new art for failure.
The Warmth Meter — one icon, only visible when low
A small icon at bottom-left appears only when something is wrong. It's the sum of: water flowing, dates fruiting, cookfire burning, family fed. When all is well, it doesn't appear. The meter triggers only on provision failures (water, fronds, fire) — never on social-isolation failures. The closed-family playstyle is fully valid; refusing welcomes does not trigger the warmth meter.
State changes show through three sprite combinations already in the asset list:
- The cookfire — three states: roaring / ember / cold
- The wife at the cookfire — two states: working (full meal) / sitting (idle)
- The palms — two states: fruiting / bare
Karam as shape-signal, not quality-signal
Karam is not good=success, low=failure. It is a shape signal. Closed-family karam shapes one game; open-family karam shapes a different game. Neither is wrong. The game observes; the game does not judge.
The Closed Oasis playstyle. You refuse most welcomes. Network stays small (3–4 gates). Your dates feed your own. Days pass quietly. Sandstorms come; you weather them with your own. Slower, more contemplative — closer to Stardew Valley solo farm. Game 2 inherits a son raised in privacy and quiet — different strengths, not lesser.
The Open Oasis playstyle. You welcome travellers. Network grows to 10+ gates. Multiple families coexist. Busier, noisier — closer to Rimworld settlement. Game 2 inherits a son who knows crowds — different strengths.
Karam still exists as a hidden value, but it shapes what kind of events arrive, not whether events arrive at all. Low karam: caravans that come are tougher negotiators. High karam: caravans bring gifts and friendlier prices. The world responds to who you are; it does not punish who you choose to be.
The Wife and the Men — two different withdrawal mechanics
If the father stops doing his job (provision-failures, not social ones), two pressures act on him — from different sources:
The wife withdraws warmth. Culturally honest for traditional Muslim Bedouin life: a wife does not openly disrespect or scold her husband in public. Her power is withdrawal of warmth and effort. She serves him the same meals as the children — no extra portion, no sweetened qahwa. She sits at the cookfire facing away when he approaches. She stops greeting him at the shelter door. The son, mirroring her, stops following him. Same sprites — different positions, different timing. No new art.
The men withdraw respect. Public male shame is the real enforcement mechanism in Bedouin culture. The visiting elder notices. The caravan trader notices. "Your dates are bare. The talk in the wadi is that your falaj runs slow." Caravan prices worsen. Travellers don't stop. Reputation among other Bedouin men erodes faster than the wife's silence.
Two different signals from two different sources. Both reversible by becoming the man your family deserves. The wife's withdrawal is private and personal; the men's withdrawal is public and economic. The game models both because real Bedouin life works both ways.
What if the father walks away and the player stops playing?
The family survives without you. The maternal principle is the floor. If the player stops moving, the wife eventually walks to where the father stands, takes the waterskin from his hand, walks to the falaj. She does the bare minimum — fills the basin, returns to the cookfire. Sprites you already have, repositioned. The world continues: sun rises, sun sets, night comes. Nothing breaks.
Auto-save every minute. Come back tomorrow, the world is dim but alive. Cookfire ember, palms bare, wife at the fire sitting. Resume from where you left. Within five minutes of playing, warmth returns.
The mother keeps everyone alive. The father decides whether they thrive. The game observes both.
Time scale mirrors the cycle shift. Scene 1 (micro dominant) is real-time-feeling — you walk, you dig, the sun arcs slowly. Scene 2 (middle dominant) starts compressing — a day passes in 30 seconds, a season in five minutes. Scene 3 (macro becoming visible) compresses further — months pass while you host. Time speeds up as your horizon widens. This is the engine that makes 25 minutes feel like a generation of work.
The Craft
The buildable layer. Lock the name, the art direction, the AI tools, and grab the Gemini prompts your artists will work from.
Locked across four sessions of naming work. Arabic word that means exactly what the game is about. English subtitle that does both genre signal and SEO. The first English word — Legacy — directly explains what Mirath means in Arabic. A bilingual title that teaches itself.
Why Mirath (ميراث)
Mee-RAATH. Two syllables. In Arabic: legacy, inheritance, heritage, patrimony — what one generation hands to the next. The same root (و-ر-ث) as tourath (heritage), mawrooth (that which is inherited), irth (legacy). In Islamic legal scholarship Mirath is the formal term for the science of inheritance — the framework by which a father's wealth, land, and obligations pass to his children under Quranic law. The word IS the mechanic of the game.
For English speakers: sounds like mirage (desert, illusion, distance — and the game has all three) and like myth (the family saga the player is building). Nirvana-class English rhythm — a foreign word that English speakers cannot help saying with reverence. Same family as karma, dharma, nirvana, kismet — words that crossed into English carrying weight.
Why this subtitle
Legacy — the English translation of Mirath itself. The first English word explains the first Arabic word. Anyone, anywhere, opens the Steam page and reads what the game is about in three seconds.
Trade — names the middle control (caravans, dates, silver). Strong SEO word — players searching trade/economy/management games find us.
The Desert — names the antagonist that walks with the player through the entire game (you can't get rid of it, can't defeat it, can't control it). Also a top-tier Steam search word. Anyone scrolling Steam who sees Desert in a title pictures the right thing: harsh environment, resource scarcity, historical setting, building/management.
The article "the" before Desert gives the word weight — the desert is a specific thing in the game, not desert-as-aesthetic. It's the constant. Everything else is what you do against it.
Reference set — games we share shelf space with
The Steam neighbourhood: Dynasty of the Sands, Roman Triumph, Ancient Cities, Dubai Builder, My Time at Sandrock, Pentiment, Disco Elysium. Subtitle pattern echoes the prestige indie subtitle pattern — Pentiment doesn't need a subtitle, Disco Elysium: The Final Cut does, ours does. Three nouns of weight, all concrete, all describing the game truthfully.
Why we rejected Wasl
Beautiful word, beautiful meaning (Dubai's historical name, "the connection"), but: Wasl Properties is a major Dubai real-estate developer with established brand recognition. Al Wasl is a Dubai neighbourhood and a Dubai football club. The keyword is already occupied in the Dubai cultural space — too much competition for any new entrant. Cleaner field exists. Take it.
Why we rejected Silsila
The meaning is gorgeous — the Sufi spiritual chain, knowledge transmitted heart-to-heart from master to disciple. This is the dynasty mechanic of the game named precisely. But prior usage is heavy: the 1981 Yash Chopra film Silsila (Amitabh Bachchan, Rekha) has cult status in India/Pakistan; an existing iOS app called Silsila on the App Store; a Russian women-safety mobile app SILSILA; an Indian fashion brand Sil-Sila. South Asian Steam search returns the film first, not the game. The word is the mechanic, but the mechanic doesn't need the word — it lives in the game itself regardless of what the box says.
The game uses a small lexicon of untranslated Arabic words as mechanics named in the language they came from. Players learn them naturally through use. The Sufi heart-to-heart silsila concept lives inside the game's mechanics even though the title isn't Silsila.
Mirath (ميراث) — legacy, inheritance. The title. The whole point.
Falaj (فلج) — the irrigation channel. The micro-cycle infrastructure.
Karam (كرم) — generosity. The hidden resource that shapes what events arrive.
Diyafa (ضيافة) — hospitality. The act of welcoming a stranger.
Qahwa (قهوة) — the coffee ceremony. The mechanic of welcome.
Arish / Barasti (عريش) — the palm-frond shelter. Historically real.
Gus — mud-block house. The permanent dwelling.
Dallah (دلة) — the brass coffee pot. The prop of welcome.
Sabr (صبر) — patience. The virtue the player learns by playing.
Mektub (مكتوب) — "it is written." Beats outside the family's control.
Silsila (سلسلة) — the chain. The Sufi heart-to-heart transmission. Not the title, but the mechanic of the father–son handoff.
You asked: "what is only allowed in this, but pixel art anyway?" The register is pixel art with modern lighting. Reference list: Punch Club, Eastward, Sea of Stars, Octopath Traveler, Stardew Valley HD, Owlboy. Pixel art that has absorbed three decades of design progress.
✓ Allowed (and required)
- Crisp pixel grid — every pixel placed deliberately, visible at the intended scale
- Limited palette per asset (8–20 colors typically)
- Subtle dithering for shading transitions
- Modern lighting — rim lights, ambient glow, soft shadows, particle effects
- Sub-pixel motion via tween (a sprite slides smoothly even at 64×64)
- Bloom and post-processing on the final render (this is how Sea of Stars looks "modern")
- HD UI overlaid on pixel game (clean fonts, sharp icons)
✗ Not allowed
- Anti-aliasing on character outlines (kills the pixel feel)
- Ink line art on sprites (this was the previous direction — different game)
- Cel-shading on character bodies (the pixel is the line)
- Photorealism or painted textures on pixel sprites
- Vector graphics anywhere in the gameplay layer
Pipeline
Aseprite is the standard tool. Gemini scouts compositions (it makes "pixel-look" images, not true pixels). Fiverr pixel artist — search term: "Aseprite character animation" — repaints the Gemini reference in true pixels at the locked resolution. Unity renders with Sprite Renderer set to Point filter (no smoothing) and a pixel-perfect camera component. Bloom and color grading applied as post-process.
Your existing sprite sheet would need to be re-rendered as pixel art, or used only as a pose reference. The atmosphere of Punch Club's grimy beauty translates directly to Al Ain's golden grime.

You said: "cinematics are the way, we should know which tools to use." Here's the stack:
The cinematic style
Pixel-art cinematic panels (think Sea of Stars, Eastward, CrossCode story moments) — composed as still pixel paintings with subtle motion layers: a few frames of breath, flickering fire, an eye blinking, smoke rising, a hand twitching. Cheaper than full animation. More atmospheric than stills. Matches the gameplay register — no jarring shift to painted illustration.
The tool stack
- Aseprite — the cinematic painter does the base panel here. Industry standard for pixel art. Native frame-by-frame and layered animation.
- Gemini — composition scouting. Generate 5–10 painted "pixel-look" references per scene. Pick the strongest; send to Fiverr as brief.
- Unity Sprite Animator (or Animator Controller) — the subtle motion layers play inside the engine. Breath, fire flicker, eye blink, ambient pixel-rain. State machine per panel.
- Spine or DragonBones (optional) — if a panel needs more complex character motion, rig the pixel character with bones for fluid sub-pixel movement.
- FFmpeg / Adobe After Effects — only for the final trailer cut. Not for in-game cinematics, which always run live in Unity.
The economics
10–15 panels for the demo. ~$150–300 per panel from a skilled Fiverr pixel artist (3–5 day delivery each). Subtle motion adds ~$50/panel. Total cinematic budget: roughly $2,500–5,000 for the demo. Saturn returns the exact number after Fiverr quotes in Week 2.
Same reasoning as before — Gemini's image-to-image consistency matters more than Midjourney's atmosphere when you're producing 50+ matching assets. The prompts below have all been rewritten for hi-bit pixel art (specifying pixel grid, palette limits, no anti-aliasing, the green chroma-key background convention pixel artists use).
Important note about AI + pixel art: Gemini and other AI generators produce painted images that look like pixel art — they're not true pixel art with a clean grid. Use these for reference and brief, not as final assets. The Fiverr pixel artist will repaint them properly in Aseprite at the locked resolution. This is true of all AI image tools as of 2026.
All prompts updated for hi-bit pixel art. Generate 5–10 variants per prompt in Gemini. Pick the strongest as reference. Send to your Fiverr pixel artist (search term: "Aseprite pixel art character commission" — different from illustrators) with the variant + prompt + locked palette + sprite resolution spec. Gemini scouts; Fiverr commits in true pixels.
Character Sprites · Emirati Bedouin family
Pixel-Art Cinematics · story beats
Environments & Buildings · isometric
Props & UI
Core principle: animate what the player does mechanically — walk, dig, build, pour. Story moments are pixel-art cinematic panels with subtle motion, not full animations. Roughly halves the animation budget.
Scene 1 · First Water · Micro dominant
Sprite animations · 8-dir gameplay
- Father — walk (4 frames × 8 dir)
- Father — idle standing
- Father — idle exhausted, hands on knees
- Father — kneel & dig (water-search)
- Father — drink from waterskin
- Father — look around (camera prompt)
- Father — stumble in heat (failure-warmth feedback)
- Mother — walk, idle, drink
- Son — walk (4-dir), idle, sit, drink
- Camel — walk, idle, kneel, get up, drink
Pixel cinematics · subtle-motion panels
- Family arrival at the dune crest (opening)
- Camel kneeling, pack dropped
- Failed first dig, hands in dust
- Water trickle close-up — success
- Family drinking at dusk together
Scene 2 · First Roots · Middle dominant
Sprite animations · new in Scene 2
- Father — repair / lay stones in falaj
- Father — plant date seedling
- Father — weave palm fronds for shelter
- Father — carry water pot from falaj
- Father — chop palm frond from mature palm
- Father — gather stones
- Father — brace against sandstorm (shield eyes)
- Mother — cook at fire, carry water, tend garden, weave, brace
- Son — follow father, play with stones, mimic dig, hide with mother in storm
- Camel — graze, drink at falaj
Building & growth animations
- Barasti — 4 construction states transition
- Falaj — dry → trickle → full flow loop
- Date palm — 4 growth stages over time
- Garden bed — empty → planted → growing → harvest
- Cookfire — unlit → lit → embers
Pixel cinematics · panels
- Father kneeling at the dry falaj stones
- First seedling pressed into earth
- Sandstorm wall on the horizon
- Family huddled in shelter (warm interior)
- Clear morning, shelter survived
Scene 3 · Wider Roots · Macro becomes visible
Sprite animations · new in Scene 3
- Visiting elder — walk-in (slow arrival)
- Elder — gesture (request water/shelter)
- Elder — bow (accept welcome)
- Elder — turn away (refusal)
- Elder — drink qahwa cross-legged
- Visiting woman & children — walk, idle
- Father — pour qahwa from dallah
- Father — welcome gesture (open hand)
- Father — refusal gesture (palm down)
- Father — sit cross-legged at fire
- Son — watch from doorway (this is the silent log)
- Visiting camels — heavy laden walk, kneel with bundles
Pixel cinematics · the emotional load
- Visiting family on the horizon at dusk
- Qahwa ceremony at the fire (your Image 5 ref, re-rendered in pixel)
- Welcome ending — shared meal, lantern light
- The runner from the coast with news
- FINAL: the son hauls water — three years older
The Build
The last layer. Decide who builds it, where it launches, how fast.
Apple regional editorial in MENA cares deeply about cultural authenticity and champions games from the region. TestFlight is the natural delivery vehicle for Dubai authorities. Validation flows region → world, never the reverse.
Now that we're committed to hi-bit pixel art, the Fiverr search terms change: pixel artist, Aseprite character animation, hi-bit sprite artist. Different talent pool from illustrators. Each artist owns one category completely — splitting a category between two artists kills consistency.
Denis keeps
| Domain | Specifically |
|---|---|
| Soul of the game | Story, dialogue, emotional arc, the father's voice. You write this. |
| Lock decisions | Name, art direction, demo climax, year — the choices on this page. |
| Aesthetic approval | Sign-off on every hero pixel asset before the artist proceeds. |
| Gemini generation | You run the prompts personally. Your scouting. |
| Dubai outreach | Personal notes, 15-min conversations. Yours alone. |
| Audio direction | Final approval on oud, drum, and the closing note. |
Delegated
| Who | Owns |
|---|---|
| Pixel Artist #1 — Characters | All sprite sheets, walk cycles, action animations. Father first as hero asset. |
| Pixel Artist #2 — Environment | Buildings, construction states, terrain tiles, props, particle FX. |
| Pixel Artist #3 — Cinematics | 10–15 pixel-art cinematic panels with subtle motion. Hired after sprites flowing. |
| Dhakaa | Unity setup, camera state machine, animation state machines, build pipeline, iPad optimisation. |
| Saturn | Budget after Fiverr quotes and locked asset list. |
| Najm | Brand consistency review of trailer + press materials. |
| Fath | Inactive until Steam release strategy begins. |
The technical pipeline lives in the Unity tutorial doc — a separate companion page. It steps Dhakaa (and you, when you want to follow along) through the entire production workflow in Unity: project setup, Aseprite import, animation state machines via Animator Controllers, Tilemap scene assembly, and the testing loop where you watch the animations move as they come in.
How to use it. Open it as a separate browser tab. Keep this design doc open in one tab; the tutorial in another. As animations arrive from your pixel artists, the tutorial shows you how to drop them into the engine and watch them play. The two pages together are the full production guide.
Tutorial sections:
- Engine setup — Unity fresh project, folder structure, 2D pixel-perfect settings
- Aseprite → Unity pipeline — Aseprite importer plugin, naming conventions, sprite atlas
- The first sprite — drop in the father, see him walk in 8 directions
- Animation state machines — idle / walk / dig / drink transitions
- Scene assembly — putting the oasis together tile by tile
- The Falaj system — gates, water flow, the timed dallah-stone mechanic
- Sun & Shade renderer — warm filter, shade patches, Rest Mode
- Testing loop — playtest harness, save/load, builds for iPad TestFlight
Each section opens as you reach that week of the 12-week plan. As animations come in, you can drop them into the corresponding step and see the work move.
You don't market this in Dubai — you introduce it. A short personal note from you, founder of Golden Kapp, with a private TestFlight link and a request for 15 minutes of honest feedback.
The framing isn't "please endorse my game." It's: "I'm building something rooted in this region's history — set in Al Ain in 1898, honouring the same desert where the UAE began — and I want to make sure I'm getting it right. Will you tell me what I got wrong?" That earns response.
Who to engage privately
- Al Ain–specific — Al Ain Museum, Sheikh Zayed Palace Museum, Qasr Al Muwaiji curators. These are the people who know the falaj system intimately.
- Cultural authorities — Dubai Culture & Arts Authority, Mohammed bin Rashid Library, Etihad Museum.
- Heritage scholars — NYU Abu Dhabi / Zayed University historians on pre-oil Trucial States.
- Emirati cultural voices — writers on Bedouin identity and Khaleeji heritage.
- Women's heritage groups — Sheikha Manal, Sharjah projects. Women's role in oasis life is central.
- Gaming layer — UAE Game Developer Alliance, GameExpo Dubai.
The Golden Kapp connection
Never inside the game. It lives in the booth, the trailer credits, the press kit. "Prism is a creative studio under Golden Kapp." Both carry cultural depth; neither carries the other's logo. Red Bull model.