Meta-Page
Process architecture is the discipline of treating how you work with AI as a first-class artifact — not the prompts you write, but the sequencing, grounding, depth control, capture habits, and configuration files around them. The claim that named this discipline: process is a more reliable carrier of judgment than individual prompts, because process compounds across invocations while prompts reset on every one. This insight was itself extracted from Insight - Codify Your Judgment Into Skills, Not Just Prompts in April 2026, then grew to 16 inbound references of its own and was split again on 2026-05-22 into three sub-insights:
Sub-Insights
- Insight - Process Mechanics — Sequencing, Grounding, and Depth Are the Concrete Moves That Make Process Beat Prompts — the moves. The specific techniques operating at the process layer: sequencing, grounding, depth control, multi-pass retrieval, multi-model synthesis, prompt-length calibration, PRD-first workflows.
- Insight - Process as Configuration — The Behavior Layer Belongs in Process Files, Not Prompt Bodies — the architecture. The principle: behavior is configuration; configuration belongs in process files that are versioned, inspectable, and transferable. Prompts are runtime parameters, not the behavior layer.
- Insight - Process Compounding — Turn Every Session Into a Reusable Asset, Not a One-Off Output — the outcome. What happens when you do this consistently: each session produces reusable assets (skills, content, captured patterns) that compound. The capture-codify-compound loop.
Read all three for the full picture. Each sub-insight stands on its own; together they describe what it means to operate with process discipline as a knowledge entrepreneur.
Original Core Claim
Durable, consistent AI output requires multi-level process design where judgment about sequencing, depth, and grounding is embedded in how you work — not in what you ask each time. Individual prompts are unreliable carriers of judgment because they reset on every invocation. Process is the carrier that compounds.
Why This Was Split
The hub accumulated 16 inbound related-insights references — over the >15 hub-overload threshold defined in core-principles.md. It had been doing three distinct jobs: cataloguing the mechanics of process discipline, naming the architectural principle behind why process beats prompts, and describing the compounding outcome of consistent practice. Three separate theses bundled into one hub. The split lets each one stand on its own with fresh link capacity, and lets inbound insights point at the facet they actually lean on rather than at a meta-concept. Executed via /mastermind-hub-split on 2026-05-22. The hub was itself extracted from Insight - Codify Your Judgment Into Skills, Not Just Prompts in an earlier split (2026-04-08) — this is the second-generation split in the same lineage.
Lineage
- Meta-parent: Insight - Codify Your Judgment Into Skills, Not Just Prompts (the original concept from which Process Architecture was extracted in April 2026).
- This page: the process-discipline facet of that parent concept, now itself a meta-page.
- Sub-insights: the three facets above, named on 2026-05-22.