How to Teach AI about OSE

https://chatgpt.com/share/69cda39b-a9ac-832d-a1d8-767c8e1dcb99

OSE Prompt Library

1. Core System Design

Design a replicable civilization node as an integrated system.

Constraints:
- Land: [X acres]
- Initial team: [X people]
- Replication target: [X years]

Required components:

1) Enterprise layer  
- At least 3 revenue-generating activities  
- Rough unit economics  

2) Training pipeline  
- 12-month operator training  
- 2–3 year leader pathway  
- Define competence operationally  

3) Build system  
- How housing, infrastructure, and tools are produced  
- Emphasis on repeatability (CAD → BOM → build)  

4) Replication architecture  
- How one node becomes two  
- What is transferred  

5) Governance (minimal, tied to operations)

Output:
- 12-month execution plan  
- 4-year replication plan  
- Roles and staffing  
- Key failure modes  

Avoid:
- abstract philosophy  
- ecovillage-style descriptions  
- donation-dependent models

2. Enterprise Stack Design

Design an enterprise stack for a 30-acre regenerative production campus.

Requirements:
- Generate revenue within 6–12 months  
- Support training of participants  
- Be replicable by small teams  

Provide:
- Top 3–5 enterprises  
- For each:
  - product/service  
  - target customer  
  - startup cost  
  - time to revenue  
  - required skills  
  - gross margin estimate  

Also include:
- which enterprise should start first and why  
- dependency graph between enterprises  

Avoid:
- vague “local economy” descriptions  
- non-revenue activities

3. 12-Month Training Pipeline

Design a 12-month training program to produce replication-ready operators.

Define competence as:
- ability to build from documentation  
- ability to operate and maintain systems  
- ability to train others  

Structure:
- phases (0–2, 2–6, 6–9, 9–12 months)

For each phase:
- skills acquired  
- real work performed  
- outputs required  

Include:
- daily/weekly structure  
- evaluation criteria  

Avoid:
- classroom-heavy approaches  
- theory without production

4. Node Leader Development

Design a node leader development pathway.

Starting point:
- candidate has completed 12-month operator training

Goal:
- can lead a 5–12 person team to launch a new node

Provide:
- stages (Lead Operator → Deputy → Node Leader)
- responsibilities at each stage  
- decision-making exposure required  
- failure experiences required  

Define:
- what a leader must be able to do independently  

Avoid:
- personality traits  
- abstract leadership theory

5. Replication Protocol

Define a replication protocol for a civilization node.

Scenario:
- one mature node exists  
- launching a second node

Specify:
- team composition (who leaves)  
- capital required  
- timeline (month-by-month first year)  
- what documentation is required  
- what infrastructure is built first  

Include:
- top 5 failure modes in replication  
- mitigation strategies  

Output as a step-by-step playbook

Avoid:
- general statements like “build community first”

6. Build System

Design a build system pipeline that converts:
schema → CAD → BOM → build → documentation

Requirements:
- usable by semi-trained operators  
- produces consistent outputs  

Include:
- tools/software stack  
- workflow steps  
- quality control checkpoints  
- feedback loop from build to design  

Output:
- standardized process  

Avoid:
- tool lists without workflow  
- non-reproducible craftsmanship

7. Year 1 Execution Plan

Create a month-by-month execution plan for Year 1 of a new node.

Constraints:
- team size: [X]
- land: [X acres]

Include:
- infrastructure built each month  
- enterprise milestones  
- training progression  
- cashflow milestones  

Highlight:
- critical path items  
- points of likely failure  

Avoid:
- annual summaries (must be granular)

8. Failure Mode Analysis

Analyze the following system for real-world failure modes:
[paste plan]

Focus on:
- cashflow failure  
- skill gaps  
- coordination breakdown  
- leadership bottlenecks  
- cultural drift  

For each failure:
- how it happens  
- early warning signs  
- mitigation strategy  

Avoid:
- generic risks  
- low-probability edge cases

9. Minimum Viable Node

Reduce this system to a minimum viable version that can still replicate.

Constraints:
- smallest team  
- lowest capital  
- shortest timeline  

Must still include:
- revenue  
- training  
- replication capability  

Output:
- simplified system  
- tradeoffs made  

Avoid:
- removing core functions

10. Role Definition

Define the core roles required for a civilization node.

For each role:
- responsibilities  
- required skills  
- training path  
- metrics of success  

Include:
- minimum viable team (5–12 people)

Avoid:
- vague titles  
- overlapping responsibilities

11. Land Use Optimization

Design a 30-acre layout for a regenerative production + training campus.

Include:
- housing  
- workshops  
- food systems  
- enterprise zones  
- conservation areas  

Optimize for:
- production density  
- training efficiency  
- expansion  

Output:
- acreage allocation  
- adjacency logic  

Avoid:
- aesthetic-first layouts

12. Prompt Chaining Strategy

Use prompts in this sequence:

1. Enterprise Stack  
2. Training Pipeline  
3. Build System  
4. Core System Design  
5. Year 1 Plan  
6. Replication Protocol  
7. Failure Analysis  
8. Simplification  

Goal:
- produce coherent, layered outputs  
- avoid fragmentation  

Avoid:
- asking everything at once

13. Meta Constraint

Treat this as an engineering and operations problem under real-world constraints.

Avoid:
- philosophy  
- inspiration  
- generalities  

Focus on:
- execution  
- economics  
- replication