Skip to main content

Page Type View

Use this view when the question is what kind of page you need.

Page type names the job. Section path names the terrain.

hub

123 pages

  • First Principles
  • Meetings
  • Principles
  • Onboarding
  • Modalities
  • 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.
  • CountriesCountry platforms ranked and scored — where individual agency, business trust, and community bonds compound.
  • CountriesDomain entry for country platforms, scorecards, regulation, and coordination context.

playbook

1 pages

  • PlaybooksReusable ways to act from the Dreamineering mental model.

glossary

1 pages

  • GlossaryPublic entry point for canonical Dreamineering language.

decision-record

0 pages

    Preflight Choice​

    Before a /docs edit, choose and record:

    • change_class: maintenance, content, new-page, or rewrite
    • route: the public /docs/... destination
    • page_type: the job the page performs
    • template: the shape that governs the edit
    • language_expected: whether DDL/DML updates are likely

    New pages and material rewrites must declare page_type and template before editing. Maintenance edits still need a preflight reason so the close record can distinguish a formatting fix from a content decision.

    Hub pages orient and route. They do not teach. Use the Hub Index Template for the full migration process.

    Enforcement​

    Touched /docs pages now close through two local gates:

    • wiki-flow-guard.mjs blocks edits that skipped Map-First preflight or close receipts.
    • docs-content-check.mjs --strict blocks touched docs whose type, template shape, or inner/outer boundary fails.

    Legacy untouched pages remain backlog. Once a page is touched, it must carry frontmatter type and match its page job before Stop, commit, pre-push, or npm run docs:quality can pass. Emergency bypasses use the auditable WIKI_FLOW_OVERRIDE=1 receipt path.

    Failure Modes​

    • Type drift: The frontmatter says hub, but the body teaches. Change the type or move teaching into child pages.
    • Template drift: The page records a template in preflight but closes without the sections that template requires.
    • Advisory drift: The post-edit warning fires, but no blocking gate catches the same failure at commit time.

    Story Surfaces​

    src/pages pages sell the Dream, frame the journey, and point toward reusable charts. They may carry the narrative spine, current offer, or product story. They should not become knowledge buckets.

    /docs pages teach reusable know-how. Community, games, systems, agency, AI, and crypto belong here when the reader can apply the pattern without knowing this repo.

    Context​