Dreamineering Wiki
This is the public compiled know-how layer: reusable mental models, playbooks, domain maps, language, and evidence for humans and agents.
Operating rule: public reusable knowledge belongs in /playbook; story surfaces that sell the Dream belong in src/pages; private project state belongs in the operating system; unresolved ideas route internally; canonical language lives in /agents.
The central model is attention. The wiki directs attention through the Tight Five: clarify Problem/Purpose, ground Principles, choose the Platform/Product, widen Perspective/Potential, then measure Performance/Progress.
Five Doors
Use intelligent systems to extend agency, prove capability, and compound learning.
AI
Use intelligent systems to extend agency, prove capability, and compound learning.
The reader can name the AI chart, instrument, or proof surface to use next.
Best Next Five
Other Ways In
Clarify what matters
- CountriesCountry platforms ranked and scored — where individual agency, business trust, and community bonds compound.
- CultureCulture is rules in action: the shared beliefs, standards, and social glue that coordinate people when intelligence is abundant.
- GamesGames are volunteered feedback loops that teach flow, coordination, and better decision-making before the stakes become life-scale.
- Productivity
- StrategyPositioning is the perceive that builds capital - finding where your unique value meets high demand
- CommunityCommunity is coordination of goodwill: the social glue that lets people hold shape, learn together, and compound trust.
- Mental ModelsReusable lenses for situational wisdom and better judgment.
- ProblemsProblem identification is the highest-leverage skill in the game
Act, ship, solve
- First Principles
- Actuators
- AgencyCharacter plus capability, multiplied by AI — the compound formula for irreplaceable value.
- AgentsPublic agent-facing concepts, language, and collaboration context.
- Amplify AgencyHow to navigate the AI section — seven ordered waypoints from first principles to shipping working AI systems.
- InstrumentsThe control loops every business needs — fill them in, act on them, update them, or they're just documents.
- CountriesDomain entry for country platforms, scorecards, regulation, and coordination context.
- NavigationThe three interlocking systems — Value, Belief, Control — that keep any voyage on course toward the dream.
Measure, learn, improve
- Information ArchitectureThe rules that decide where knowledge-base content goes, how each folder is shaped, and — by job-to-be-done — what format and authoring action to use. Built for human readers and answer engines alike.
- Standards
- Systems
- Naming StandardsAgent-first naming rules for paths, files, terms, and handoffs across Dreamineering
- Science
- Scoreboard
Start Paths
| If you are... | Start with... | Why |
|---|---|---|
| New to the system | Start Here | Orient to the map before the territory |
| Learning agency | Agency | Understand how human and phygital beings become capable |
| Following the story | Intention | See why the journey, loop, and game matter before depth |
| Growing collective agency | Community | Learn culture, archetypes, players, and shared agency |
| Designing better games | Games | Use mechanics, incentives, and simulations intentionally |
| Looking for situational wisdom | Mental Models | Use lenses that help decide what matters now |
| Learning how AI fits work | AI | Understand models, agents, tools, instruments, and work |
| Trying to act | Playbooks | Turn a model into a repeatable move |
| Building or guiding agents | Agents | Align language, instructions, and collaboration |
| Researching a domain | Domains | Find public domain maps and reference libraries |
| Checking claims | Evidence | Trace reasoning to sources, scoreboards, and benchmarks |
| Naming something | Glossary | Use canonical language instead of inventing aliases |
System Map
| Layer | Durable home | Job |
|---|---|---|
| Idea processing | internal routing | Move raw ideas toward publication, demand, or deletion |
| Public know-how | /playbook | Explain reusable mental models, playbooks, domains, and evidence |
| Public story | src/pages | Sell the Dream, frame the journey, and point readers to charts |
| Private/project state | operating system | Store plans, demand stories, decisions, traces, and delivery state |
| Canonical language | /agents | Maintain DDL terms and DML agent notation |
Wiki Contract
- A page earns its place by helping a named reader act or understand faster.
- A public page should not depend on private project state to make sense.
- A concept that becomes canonical should be represented in DDL and, when useful, linked to a
/playbookhome. - A repeatable private process should become a CLI capability or demand story, not a public doc.
- A raw idea should not stay in limbo; it should publish, route, or die.
Maintenance
- Wiki Schema defines page types and routing rules.
- Wiki Index lists the first public spine.