Skip to main content

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.

Playbook

Five Doors

Use intelligent systems to extend agency, prove capability, and compound learning.

Active door

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 mattersPurpose, principles, people, and the frames that decide what is worth doing.50 pages · intentionAct, ship, solvePlaybooks, tools, product systems, protocols, and repeatable moves.1367 pages · actionMeasure, learn, improveScoreboards, systems, standards, evidence, and feedback loops.136 pages · evolutionCrypto payment railsTokenization, protocols, settlement, countries, governance, and commerce paths.Crypto · Payments · RailsPage type viewAgent-readable grouping by hub, concept, playbook, evidence, and reference type.Agents · IndexDomain matrixPower-user intersections such as AI, crypto, commerce, agents, and systems.Matrix · Domains

Clarify what matters

Act, ship, solve

Measure, learn, improve

Start Paths

If you are...Start with...Why
New to the systemStart HereOrient to the map before the territory
Learning agencyAgencyUnderstand how human and phygital beings become capable
Following the storyIntentionSee why the journey, loop, and game matter before depth
Growing collective agencyCommunityLearn culture, archetypes, players, and shared agency
Designing better gamesGamesUse mechanics, incentives, and simulations intentionally
Looking for situational wisdomMental ModelsUse lenses that help decide what matters now
Learning how AI fits workAIUnderstand models, agents, tools, instruments, and work
Trying to actPlaybooksTurn a model into a repeatable move
Building or guiding agentsAgentsAlign language, instructions, and collaboration
Researching a domainDomainsFind public domain maps and reference libraries
Checking claimsEvidenceTrace reasoning to sources, scoreboards, and benchmarks
Naming somethingGlossaryUse canonical language instead of inventing aliases

System Map

LayerDurable homeJob
Idea processinginternal routingMove raw ideas toward publication, demand, or deletion
Public know-how/playbookExplain reusable mental models, playbooks, domains, and evidence
Public storysrc/pagesSell the Dream, frame the journey, and point readers to charts
Private/project stateoperating systemStore plans, demand stories, decisions, traces, and delivery state
Canonical language/agentsMaintain 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 /playbook home.
  • 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