Lexicon

The plain-language glossary of Ark terms.

Ark: The complete family resilience system. Everything below nests inside this frame. The Ark is where the philosophy lives — sovereign, redundant, eternal. It is also the level at which Feeds become visible, because Feeds describe how the whole system works together.
Domain: A major capability area an Ark needs. Domains are self-contained categories that organize knowledge. They don't reference each other directly — that's what Feeds are for. Domains are named as single words, verb-rooted. They work as navigation labels, hashtags, and conversational shorthand.
Rig: A specific, named, buildable configuration that lives inside a domain. A Rig is a complete thing someone can visualize in their space — it's the unit people browse, choose, and build. Rig names are plain-language and evocative. They tell you what the thing is or does. No alphanumeric model numbers. "The Shelf Stack" tells you what it is. "The Gut" tells you what it does. "The Sanctum" gives dignity to an uncomfortable topic.
Manifest: The parts list for a Rig. Every component is listed with its role, a Core recommendation, and available Swaps. A Manifest is what's on board.
Core: The recommended, non-negotiable primary component for a given role in a Manifest. The default path.
Swap: An alternate component that fills the same role as a Core. Swaps exist for preference, local availability, or different trade-offs — never framed as budget fallbacks. Frame as: "if you prefer X" or "if Y is available locally." Never frame as: "if you can't afford the Core."
Sequence: Step-by-step build instructions for a Rig. Numbered, ordered, practical. This is where the tone shifts from philosophy to competent friend — no Ark mythology inside a Sequence.
The Echo: Audio companion content. The theory behind the build — the "why behind the how." The Echos explain principles so users can adapt Rigs to their specific circumstances rather than following instructions blindly. The Echos are titled as statements or questions, not episode numbers. "Why Mesh, Not Cell" — not "Episode 3." This lets them be discovered independently and shared without context.
Footprint: The physical space a Rig requires. Expressed as dimensions with context. Example: 4ft × 2ft floor, 6ft vertical. Fits against a wall in a kitchen or garage.
Yield: What a Rig produces. Quantified output — grams of lettuce per cycle, liters of biogas per day, mesh coverage radius in km. Always concrete.
Cycle: The relevant time unit of a Rig's operation. Growth cycle, digest cycle, charge cycle, harvest rotation. Reinforces closed-loop thinking without belaboring it.
Feed: A directional resource flow between Rigs, usually across domains. Feeds are the only term in the lexicon that doesn't belong to a single domain — they live at the Ark level, describing how the whole system connects. Feeds work for material flows (nutrients, waste, water), energy flows (biogas, electricity), and information flows (sensor data, alerts) without needing separate terms for each. Feeds are always bidirectional in documentation. If Rig A feeds Rig B, then Rig B's page shows that it is fed by Rig A. A person building a single Rig in isolation will never encounter the word Feed. It only appears when systems connect.
Steward: A person building or running an Ark. Replaces "user" in user-facing language. Carries connotations of care, long-term commitment, tending, and responsibility-without-ownership-claim. The work of an Ark is stewardship of resources, knowledge, and living partners — not consumption or extraction.
The Doors: Empathy-led entry pages keyed to specific life situations (job loss, illness, climate grief, etc.). Each Door names the situation honestly, surfaces 1–3 highly-leveraged rigs as immediate practical help, and points to crisis resources where appropriate. Designed to fully serve a visitor who never returns. Stewardship is what some people grow into — never the price of admission.
Pressing: A checksummed offline HTML bundle of the published catalog, cut by The Press. Bytes travel by sneakernet; the public /press ledger lists number, date, counts, and hashes so a Steward can verify a drive.
Dual-lane: A rig pattern with two named sections: Standard Practice (conventional small-scale build) and Stack & Loop (cross-domain integration). Lane 1 is the prerequisite to Lane 2. Common in Tend and Coffer.