Venture Book · venturebook

Owner directive (2026-07-10), canonical. "…the Runs with n8n like for the Playbook composed by concated cookbooks … of the Loops and the Schemas, Schematics, Venture Book and EndeavorBook with all the necessary for the Loops be successful in augmenting particles and producing sparks to initiate other Loops." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:534]

Content

The Venture Book is the library's register of ventures — what each venture IS, its divisions, and the parameters a loop needs when its particles touch venture value. It exists so a datan never invents venture facts: slices, PADs and copy pull from this book and from the instance genome-schema. Ownership of the book's guardianship follows the owner's earlier rule for books: "Make one SQUAD to be the guardians of the book" [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:414].

Entry structure

Each venture entry carries:

1. Identity — id, name, one-liner, parent organization (from organizations-identities/<slug>.json, the genome source of truth);
2. Divisions — the operating sub-ventures ("planets");
3. Endeavor dimensions — pointers into endeavorbook (programs, products, professionalization);
4. Spatial expression — which genome-spatial-site slices carry each division;
5. Books-to-loops contract — which playbooks/benchmarks govern work on this venture's particles.

Entry: Royal Orbit Holding Group (the model venture)

"Royal Orbit Holding Group is a Middle Eastern royal-heritage holding company that runs a constellation of subsidiaries — Trade, Gold, Energy, Agro, Management, Atari Petroleum, and CodeLoop — plus an ultra-luxury hospitality program (Wajeeh Guest)…" [src: wiki/organizations/instances/royalorbit/genome.json:36].

Divisions with spatial presence today — the four division pods of the live v1 site, each with its own subpage and splat asset [src: web/royal-orbit/src/division.ts:22]:

Divisions without spatial presence yet — Royal Orbit Agro and Royal Orbit Management (named identity properties in the org dossier [src: organizations-identities/royalorbit.json:1]); they enter the v2 journey via genome-spatial-site slices when their pods are generated. CodeLoop is the technology subsidiary.

Programs of the venture (from the instance genome programs key): Royal Orbit Constellation (venture, active) · Wajeeh Guest Program (endeavor, active) · Royal Orbit Trade & Commodities (venture, building) · Pillars of Development (venture, planned) [src: wiki/organizations/instances/royalorbit/genome.json:232].

Spatial expression (v2) — division-to-slice mapping in the reference strand: district-aerial (Trade) → caravan (Gold) → market (Atari) → falcon-flight (Energy) → world-night (the connected orbit) — see genome-spatial-site.example.json.

Extension rule

One entry per venture of each of the 29 organizations, generated from organizations-identities/*.json and the per-org instance genomes — never hand-invented. New entries are authored per sop-004-library-authoring and reviewed by the cogni-neural-engine accept/refuse rule.

Composition

• uses: genome-schema (programs/market keys), endeavorbook (the endeavor dimensions of each venture), src-royalorbit (live spatial facts), genome-spatial-site (spatial expression)
• used-by: district-spatial-site (slice content), cogni-spatial-site (what the journey must express), squad-instance (builds from it), infograph (Library lane)

See also

• endeavorbook — the companion book
• dwork — the engine converting work entropy into Venture & Endeavor structure
• [Royal Orbit instance genome](../../../wiki/organizations/instances/royalorbit/genome.json)