asap

Citations and references for the notes

Status: preparatory notes. Companion to Notes for The Architect and the Agent. This is the citations record for the analytical groundwork document. The corresponding citations for the eventual concept paper will be derived from this fuller list.

This document organizes the source material the notes draw on. The references are grouped by their relationship to the argument: parent works in the Realization Engine sequence, the body of knowledge that organizes architecture practice, the companion artifacts that ground the platform’s design, and the adjacent practice references the platform design document draws on.

Parent works

The concept doc is the architectural-practice instantiation of The Multiplier and the Mirror’s general framework, extended through the defense pattern named in the Enquiry. M&M’s framework is explicit that its subject is human capability under LLM amplification across any knowledge profession, with software engineering as its primary worked example; this paper is another such instantiation.

[P1] Landi, Dennis. The Multiplier and the Mirror. The Realization Engine, 2026. https://realizationengine.net/fstar/docs/The_Multiplier_and_the_Mirror.html

The foundational framework. Establishes that human capability (FORCE) scales through collaborative systems, and that those systems reshape the practitioners working inside them. The concept doc draws on the framework at unusual breadth; the M&M sections most load-bearing for this paper are listed below in M&M’s own section order.

Part One — The Framework

Beyond the Force Multiplier and Mirror — the twin-channel asymmetry (substance vs. presentation) and the studio-mirror / Narcissus’s-pool bifurcation. Carries §6 (the Mirror at two scales).
Force is Not a Number — the multiplicative (Cobb-Douglas) composition of FORCE and the three-layer decomposition (surface / middle / deep). Carries §4 (mapping to BTABoK pillars and proficiency levels).
The Atrophy Problem — the four pressures on FORCE (struggle gains, deliberate-engagement gains, passive-reliance decay, organizational disinvestment). Carries §7 (commitments derived per pressure).
The Layered Decay — surface decays without growth term; middle is the battleground; deep cannot be substituted; presentation projection masks limitations at depth. Carries §6 (institutional self-deception).
The Tipping Point and Hysteresis — F* as a rising bifurcation point with asymmetric recovery cost. Carries the tier-relative analysis in §4 and the early-warning posture in §10.
The Cohort Discontinuity — the step-function distribution at cohort boundaries and the bidirectional collapse of tacit transmission. Carries §5.
The Transfer: When FORCE Flows Into the Model — F→M transfer efficiency by FORCE-layer, the transfer ceiling, the bus-factor illusion. Carries §9 (Knowledge Layer as deliberate, controlled F→M transfer).
The Paradox of Successful Transfer and The Multiplier is Growing — the data-quality spiral and the policy trap of nonlinearly compounding harms under linearly rising output. Carries §3 (urgency framing) and §19 (Global Corp as substance-preserved corpus).
The Phase Portrait (with Separatrix, Fixed Points, Irreversibility Frontier) — the (F, M) coupled-system geometry. Carries the framing of §3 and §14 (act before the irreversibility frontier).

Part Two — Ramifications

The Variable Multiplier — domain-varying substance multiplier. Carries §8 (the authority gradient as a deduction from variable M_s across architectural work types).
The Variance Amplifier — variance growing as the multiplier squared, equal access amplifying spread. Carries §6 (Mirror exposure) and §7 (Accelerating Gap framing).
The Barbell Effect — labor-market bifurcation; structural risk to the middle tier. Carries §7 (commitment 1).
Creation Becomes Free. Evaluation Does Not. — cost inversion and optimal-allocation paradox. Carries §9 (why Engagement Model receives the heaviest platform investment) and §12 (decision bottleneck).
When Force Goes Negative — damage scaling once the typing governor is removed. Carries §8 (Enforce tier as negative-FORCE damage limiter).
The Epistemic Corruption Problem — gap between apparent and actual competence; atrophy invisible from inside. Carries §6.
Tacit Knowledge: The Invisible Loss — apprenticeship pipeline collapse via shared-work narrowing. Carries §10 (mentor-as-AI-backstage, AI-excluded judgment).
The Accelerating Gap — Matthew Effect; gap widens AND accelerates over time. Carries §7 (commitment 3 honest framing) and §11 (loop 5).
The Cascade — seven reinforcing feedback loops; few natural brakes. Carries §11 (architecture-practice form of each loop and the platform’s brakes at each intersection).
The ROI Paradox — marginal gain proportional to existing FORCE; collides with evaluation requirement. Carries §11 (tension the platform reveals but cannot resolve).
The Legibility Crisis — organizations lose ability to distinguish substantive from polished hollow output; assessment must shift from output to process observation. Carries §6, §8 (legibility-restoration framing), §10 (HITL band visibility).
Goodhart’s Trap — once a measure becomes a target, gameable via the presentation channel. Carries §6 (assessment-via-process-observation) and §8 (audit trail makes the gameable channel structurally separable from substance).
The Decision Bottleneck — decision speed as the new binding constraint after the Creation/Evaluation inversion. Carries §12 (architecture as the firm’s decision-making discipline).
The Erosion of Competitive Moats — execution moats erode, judgment moats are amplified, decision-speed moats become decisive. Carries §12 (architecture practice as the firm’s only durable moat substrate).
The Meaning Problem — motivation enters FORCE multiplicatively; autonomy loss accelerates motivation decay, which accelerates FORCE decay. Carries §10 (HITL bands as motivation-preservation, AI-excluded preserves agency).
The Sovereignty Question — workforce that has atrophied while relying on a foreign multiplier fails the resilience test (capability without M); three dependency channels (access, training-priority, talent-formation). Carries §13 (sovereignty at enterprise and profession levels).
The Counter-Argument: LLMs as Floor-Raisers — snapshot-vs-trajectory framing; floor-raising real on well-covered tasks at t=0; divergence on novel tasks and over time. Carries §3 (engaging the counter-argument fairly).
The Inequality Accelerant — same divergent dynamic at every scale: individuals, teams, firms, nations. Carries §11 (fractal scaling property; cascade loops have analogues at every level above the practitioner).
Terminal Dynamics — three regimes for the coupled (F, M) system: virtuous, managed decline, collapse spiral. Carries §14 (architecture-profession form of each).

Part Three — Response

So What Do We Do? — the framework’s eight prescriptions for organizations and practitioners. Carries §15, where the platform is read as the architecture-practice operationalization of each prescription.
The Future of the Software Engineer (scope note explicitly applies to any apprenticeship-bearing profession) and The Ladder With No Lower Rungs / What Is a Junior Software Engineer? / What Does It Mean to Be a Software Engineer? — the role-redefinition argument. Carries §5 (architecture-profession cohort discontinuity) and §16 (four futures).
Four Futures (Pilot model / Permanent bifurcation / Role dissolves / Return to specification) — the trajectories. Carries §16, including the platform’s explicit bet on Future 1 plus Future 4.
The Convergence — S_available as the determining variable; window for choosing is finite. Carries §14 (act now framing).

Open Questions and Testable Predictions

Mirror Distortion and Conformity Pressure — practitioners drift toward well-covered training domains. Carries §17.
FORCE as a Commons — supply-side competition vs demand-side commons problem; Ostrom-style institutional analysis as open question. Carries §13 and §17.
Competitive Dynamics of Inter-Firm Transfer — high-FORCE firms internalize the F→M loop. Carries §17.
Mirror Dimensions and Atrophy — diagnostic vs authoring use as testable hypothesis. Carries §17.
The Education System Redesign Problem — post-LLM curricular constraints. Carries §17.
Team Composition Optimization — Cobb-Douglas complementarity. Carries §17.
Empirical Predictions — seven falsifiable predictions; the platform creates measurement opportunity in the architecture domain. Carries §17.

[P2] Landi, Dennis. Enquiry Into Specification as Meaningful Struggle. The Realization Engine, 2026. https://realizationengine.net/spec-chat/docs/theory/Enquiry-Into-Specification-as-Meaningful-Struggle.html

Applies the Multiplier and Mirror thesis to software engineering. Names meaningful struggle as synapse-engraving activity as the defense pattern that protects FORCE from absorption into the model. Names the Collapse of Execution: implementation effort no longer governs output. The concept doc adopts both moves and re-instantiates them for the architect’s working surface, where typing was the implicit governor on documentation throughput and meaningful struggle takes one form per FORCE-form.

Body of knowledge

The platform takes its working surface, vocabulary, and named cadences from the IASA Body of Knowledge. The references below are direct sources for the practice ASAP supports.

[B1] IASA Global. Business Technology Architecture Body of Knowledge (BTABoK), version 3.x. IASA Global, ongoing. https://btabok.iasaglobal.org/

The corpus that organizes architecture practice into the four models (Engagement, Value, People, Competency), the Architecture Development Life Cycle, the canvas catalog, and the certification structure the concept doc references. The platform’s model-coverage decision in §9 is grounded in BTABoK’s own framing, including its statements that “the engagement model is the how, the value model is the why” and “architects should be governed, not doing the governing.”

[B2] IASA Global. BTABoK Competency Model: nine pillars. IASA Global.

Business Technology Strategy, Human Dynamics, Design, IT Environment, Quality Attributes, Business Architecture, Information Architecture, Infrastructure Architecture, Software Architecture. The pillar decomposition the concept doc maps onto M&M’s Cobb-Douglas FORCE composition in §4. The mapping is the structural claim that BTABoK is the operationalized FORCE taxonomy for the architect.

[B3] IASA Global. BTABoK Competency Model: five proficiency levels. IASA Global.

Awareness, Basic, Delivery, Experienced, Shaping. Bloom-aligned proficiency levels per competency area. The concept doc maps these onto M&M’s three-layer FORCE decomposition (surface / middle / deep) in §4. The mapping carries the claim that the LLM substitutes most effectively for surface FORCE (Awareness/Basic), partially for middle FORCE (Delivery/Experienced), and not at all for deep FORCE (Shaping).

[B4] IASA Global. Concept Definition Language (CoDL) and Canvas Definition Language (CaDL). BTABoK 3.2 Education Portal, IASA Global, 2026.

Companion to BTABoK 3.x. Defines the structured concept and canvas languages the SpecChat profile mirrors and the platform’s preview layer renders.

[B5] IASA Global. CITA Certification: Foundation, Associate, Professional, Distinguished. IASA Global. https://iasaglobal.org/architect-training/cita/

The four-level certification structure mapped in §4 to M&M’s tipping point F* as F*-relative tiers. With Aspiring at the entry side and Chief on the People Model side, the structure implies a developmental trajectory the concept doc argues is now broken under the cohort discontinuity (§5).

[B6] IASA Global. Architect Skills Framework: BIISS specializations. IASA Global.

The Business / Information / Infrastructure / Software / Solution specialization taxonomy used in the platform’s role and team-coverage features.

[B7] IASA Global. BTABoK mentoring engagement structure. IASA Global.

The 3-to-6-month mentoring engagement for Foundation and Associate progression and the 1-to-3-year mentoring relationship for Professional progression. The concept doc treats this structure in §5 as the primary tacit-FORCE transmission channel that the post-LLM cohort discontinuity threatens.

Companion artifacts

The concept doc points to three companion artifacts in the Realization Engine corpus. They make the platform’s design concrete.

[C1] Architect Support Agentic Platform: Platform Design. This repository. https://github.com/Realization-Engine/asap/blob/main/WIP/Architect-Support-Agentic-Platform.md

The full platform design. Covers ten components (deterministic core, enforcement, automation, integration, specialist workers, human entry points, advisory, rendering, knowledge, infrastructure), eight cross-cutting concerns, a lifecycle-by-primitive matrix, model-by-model agentic coverage, the human-in-the-loop role architecture across all three out-of-profile models, and a six-wave delivery plan with a fork point at SpecChat GA exit. The concept doc’s §3, §4, §5, and §6 each summarize a layer of this document.

[C2] ASAP Acronym and Term Glossary. This repository. https://github.com/Realization-Engine/asap/blob/main/WIP/ASAP-Acronym-and-Term-Glossary.md

Working vocabulary across the ASAP corpus. Useful when reading the platform design or the BTABoK source material.

[C3] Global Corp Enterprise Architecture: A Fictional BTABOK-Complete Enterprise Architecture for Global Supply Chain Tracking. SpecChat repository. https://realizationengine.net/spec-chat/docs/examples/global-corp/Global-Corp-Exemplar.html

The narrative architecture document and its companion spec collection. Functions as the fixed point against which the platform’s components are designed and tested. Referenced in §8.

SpecChat design notes

The platform’s design depends on several SpecChat design records. These remain repository-only material, cited here for traceability.

[S1] SpecLang-Design.md. SpecChat repository. https://github.com/Realization-Engine/spec-chat/blob/main/docs/design-notes/SpecLang-Design.md

The consolidated design covering Core SpecLang, the BTABOK profile, CoDL and CaDL alignment, and the Engagement Model scope.

[S2] Spec-Type-System.md. SpecChat repository. https://github.com/Realization-Engine/spec-chat/blob/main/docs/design-notes/Spec-Type-System.md

Spec type taxonomy, rationale, and validation architecture.

[S3] MCP-Server-Integration-Design.md. SpecChat repository. https://github.com/Realization-Engine/spec-chat/blob/main/docs/design-notes/MCP-Server-Integration-Design.md

The MCP server surface ASAP consumes. Integration phases referenced in the platform’s six-wave delivery plan.

[S4] SpecChat-BTABOK-Implementation-Plan.md. SpecChat repository. https://github.com/Realization-Engine/spec-chat/blob/main/docs/design-notes/btabok/SpecChat-BTABOK-Implementation-Plan.md

Phased plan for SpecChat’s BTABOK profile, validators, and canvas rendering. Phases 1 through 4 underwrite the enforcement layer the concept doc’s §4 and §5 describe.

[S5] BTABOK-Out-of-Scope-Models.md. SpecChat repository. https://github.com/Realization-Engine/spec-chat/blob/main/docs/design-notes/btabok/BTABOK-Out-of-Scope-Models.md

The scope discipline that places Value, People, and Competency models out of the SpecLang profile. The model-coverage asymmetry the concept doc defends in §5 traces to this decision.

Adjacent practice references

The platform design draws on practice frameworks and methods adjacent to BTABoK. These are not load-bearing for the concept doc itself but ground the design’s references in §3 and §6.

[A1] Westrum, Ron. “A Typology of Organisational Cultures.” Quality and Safety in Health Care, 2004. The typology underlying the Westrum Culture Diagnostic referenced in the platform’s People Model coverage.

[A2] SFIA: Skills Framework for the Information Age. SFIA Foundation. https://sfia-online.org/. Referenced in the platform’s Competency Model integrations.

[A3] TOGAF Standard, Architecture Skills Framework. The Open Group. Referenced alongside SFIA and BTABoK in the Competency Model index.

[A4] European e-Competence Framework (e-CF). CEN Workshop, European Standard EN 16234-1. Referenced alongside SFIA and TOGAF in the Competency Model index.

[A5] Christensen, Clayton M., et al. “Know Your Customers’ ‘Jobs to Be Done.’” Harvard Business Review, September 2016. The Jobs-to-be-Done method referenced in the stakeholder concern miner subagent and in BTABoK’s own discovery practices.

[A6] Carlson, Curtis R., and William W. Wilmot. Innovation: The Five Disciplines for Creating What Customers Want. Crown Business, 2006. Source of the NABC (Needs / Approach / Benefits / Considerations) framing the platform’s business case drafter uses.

This site is open source. Improve this page.