genesis ecosystem / root control plane / local-first portal

genesis foundry

A sovereign landing page and operating portal for the Genesis ecosystem. Use it to understand the architecture, launch modules, determine where to begin, track local progress, preserve workspace notes, export portable JSON, and keep the whole system legible as a single civilizational-scale project rather than a pile of isolated files.

root_index module_launcher guided_routing offline_first local_first indexeddb json_portable no_telemetry
section 01

dashboard

modules0
routes0
notes0
bookmarks0
quests done0
xp0
integrity100
storage—

What this file is: not a replacement for the specialized modules, but the control plane that makes the entire project intelligible, explorable, and operational from one root entry point.

control plane

See the whole architecture, not just one downstream application at a time.

routing system

Ask where to begin based on your objective and get a recommended Genesis route.

local workspace

Keep notes, bookmarks, quests, and plans entirely in local-first browser state.

portable state

Export/import JSON so the project remains sovereign across hosting, devices, and sessions.

section 02

start here

If you are brand new:

Common intents:

map current work understand skills analyze rewards invent successors deploy careers build new module

If unsure, use the wizard below.

section 03

module atlas + launcher

section 04

architecture map

The Genesis chain is intentionally layered. Upstream modules make downstream modules more precise, interpretable, and interoperable.
constitutionprinciples & doctrine
→
templatestructural shell
→
occupation_atlasobserve existing work
→
skill_taxonomyclassify capability
→
reward_dnaunderstand incentives
→
progen_enginedesign successors
→
regenerative_careersoperationalize pathways
readable architecture logic 
genesis_constitution
    = the philosophical and operational baseline

genesis_template
    = the technical and interface shell

occupation_atlas
    = what work exists? how is it structured?

skill_taxonomy
    = what capabilities exist? how do they bridge?

reward_dna
    = what do work environments reward and preserve?

progen_engine
    = what successor roles or systems should exist?

regenerative_careers
    = how do humans and institutions actually move into them?
section 05

guided routes

section 06

which module do i need?

wizard output

Run the routing wizard to receive a recommendation.
section 07

interoperability + knowledge packs

project rule

Every Genesis module should remain useful as a standalone file but still exchange knowledge through portable JSON envelopes.

recommended envelope

{
  "genesis": {
    "module": "module_name",
    "type": "complete_state | knowledge_pack",
    "app_version": "x.y.z",
    "schema_version": "x.y.z",
    "exported_at": "ISO-8601"
  },
  "knowledge": {}
}

root responsibilities

Track module existence, explain sequencing, preserve notes, and help users navigate toward the right application without hiding the boundaries between them.

modulebest export conceptbest downstream use
section 08

workspace

No workspace summary saved yet.
section 09

quests + xp

The root portal uses lightweight gamification to preserve direction across a long-form project.

rank: seed

seed 0–99 XP · orientation

water 100–249 XP · routing

tree 250–549 XP · architecture

canopy 550+ XP · orchestration

section 10

builder mode

builder console ready.

module maturity registry

Track status, versions, and deployment links for every Genesis module.

guided routing logic

Recommend the right module or route based on user intent.

knowledge pack exchange

Define a portable JSON envelope for module interoperability.

project atlas

Explain how each module fits the overall system.

local-first sovereignty

Keep the whole portal useful even when offline or copied to static hosting.

section 11

integrity + provenance

Compute a SHA-256 digest of the current root state (excluding the audit log from the digest).

No digest computed.

storage_check

detecting storage...
section 12

docs + deployment

what the root portal should do
  • Introduce the thesis and project scope.
  • Explain the Genesis architecture in one place.
  • Launch each module through consistent relative paths.
  • Recommend where a user should begin.
  • Preserve local notes, bookmarks, and state.
  • Support print-friendly summaries and static hosting.
  • Keep module boundaries clear rather than flattening them into one monolith.
deployment notes 
recommended repo structure

/index.html                    ← this file
/genesis_constitution/index.html
/genesis_template/index.html
/occupation_atlas/index.html
/skill_taxonomy/index.html
/reward_dna/index.html
/progen_engine/index.html
/regenerative_careers/index.html

This root file assumes static relative links.
If the repo is hosted with GitHub Pages or any static host,
the module cards can be launched without any backend.
next recommended artifacts after this file
  • Optional site-wide search index across all modules.
  • Optional global knowledge-pack viewer.
  • Optional version/change log dashboard.
  • Optional public proof / integrity page.
  • Optional root-level asset manifest.