← back to index

Lesson: Lock-In Recognition — Two Use Cases

Curriculum location: curriculum/lessons/lock-in-recognition/

Status: v1 draft, 16 May 2026

Prerequisites: familiarity with eve-glyph-lattice/methodology/14-lock-in-as-darkness.md and eve-glyph-lattice/methodology/17-early-iteration-hyperscaler-commoditization.md

Companion methodology: eve-glyph-lattice/methodology/19-sap-inflection-point-finding.md (named-institution finding)

What this lesson teaches

The methodology classifies all forms of lock-in as darkness (Methodology 14) and names early-iteration commoditization as the structural counter-move at the substrate level (Methodology 17). Both methodologies are abstract until the operator has worked through real cases. This lesson supplies two cases that, together, teach what lock-in recognition looks like in practice.

The two cases are paired deliberately:

• Case 1 — Vertex / Sabrix vs. Avalara (commoditizer won). A mature-institutional incumbent lock-in regime was defeated in the free marketplace by a competitor offering substrate portability the incumbent's posture could not match.
• Case 2 — Canadian SR&ED assessment agent (attempted burial). An assessment agent designed to make a public-subsidy compliance process transparent and quantifiable was perceived as a threat by named institutional actors who benefited from the opacity, and those actors moved to bury the agent rather than compete on merit.

The cases sit at opposite ends of a structural spectrum. Case 1 shows what happens when an incumbent's lock-in is defeated by a market competitor; the lock-in falls and the customer base benefits. Case 2 shows what happens when an incumbent's lock-in is not in a market — it is in a public-program-design surface — and the incumbents have the institutional weight to bury the threat before it can compete. Together they teach the operator to recognize lock-in across both substrates: market-mediated and policy-mediated.

Learning objectives

By the end of this lesson, the operator should be able to:

1. Identify mature institutional lock-in parameters in a vendor or institution's customer-facing posture, even when the lock-in is not labeled as such in the contracting language.
2. Distinguish substrate-portability competitors from feature-competitors. Not every new entrant is a commoditizer. Recognizing which entrants threaten the structural posture (and which only threaten margin) is the analytical skill.
3. Recognize the four phases of the institutional-runaway sequence (Methodology 17) inside concrete institutional behavior — useful start → asymmetric authority accrual → only-path consolidation → resistance to exit.
4. Recognize attempted-burial behavior as a diagnostic signal that the burying institution is in phase 3 or 4 of the runaway sequence. Institutions in earlier phases compete on merit; institutions in late phases bury threats they cannot defeat openly.
5. Apply the recognition to the operator's own working context without flinching — including domains where the operator has personal commercial or institutional exposure.

Lesson structure

• README.md — this file. Lesson overview, learning objectives, structure.
• case-1-vertex-avalara-commoditizer-won.md — the free-marketplace example.
• case-2-sred-assessment-agent-attempted-burial.md — the institutional-burial example.
• comparative-analysis.md — what the two cases together teach. The structural distillation.

The operator is expected to read the two case files in order, then read the comparative analysis. Each case file ends with three classification questions the operator should be able to answer about the case before moving on. The comparative analysis ends with five recognition prompts the operator should be able to apply to their own working environment.

How this lesson is taught in the game

These cases become loss-condition simulations inside the universal adaptive game (/game/). The operator-player walks a digital twin of each scenario:

• Case 1 walk-through: the player operates as a mid-market CFO evaluating tax-engine vendors. The simulation presents the choice in 2017 between an established Vertex deployment and an Avalara migration. The player who reads only the feature comparison signs Vertex. The player who reads the substrate-portability dimension signs Avalara. The simulation runs forward to 2025 and shows both outcomes. The learning is that lock-in dimensions do not surface in the comparison matrix the incumbent provides; they surface in the comparison matrix the operator builds themselves.

• Case 2 walk-through: the player operates as the architect of the SR&ED assessment agent. The simulation presents the moment of disclosure to the institutional actors whose authority the agent threatens. The player who treats the disclosure as a stakeholder-management problem loses the agent. The player who recognizes the disclosure as the moment of institutional-runaway-sequence phase 4 surfacing — and routes the agent's substrate outside the burying institutions' reach before disclosure — saves the agent. The learning is that attempted-burial is predictable from the institutional configuration; recognizing it before disclosure is the operator skill.

Both simulations end with the loss-condition rendering described in /game/loss-conditions/loss-condition-design.md applied at network and civilization scales. The destruction shown is the destruction lock-in produces, and the destruction prevented is what recognition prevents.

Distribution and editing posture

This lesson, like the rest of the education repository, is private. Specific named actors in Case 2 are left as structural roles (with placeholders) so the operator (lead operator) can edit named specifics in or out before any wider distribution. The structural lesson is independent of the specific actor names; the cases are pedagogically useful with names or without them.

Operator decision points for distribution:

1. Whether to name specific institutional actors in Case 2 (currently structural roles only).
2. Whether to add a Case 3 from the operator's own SAP work (the Stage 2 RISE-push pattern from Iteration 1 is structurally a Case 2 cognate — institutional actors moving to bury a customer-favorable finding rather than compete on its merits).
3. Whether the lesson cluster is referenced from the public council page at eveglyphdesign.github.io/eve-hyperloop/council.html, or remains education-internal until further notice.

The lesson stands as v1 pending those decisions.

Cross-references

• eve-glyph-lattice/methodology/14-lock-in-as-darkness.md — the principle.
• eve-glyph-lattice/methodology/17-early-iteration-hyperscaler-commoditization.md — the structural counter-move.
• eve-glyph-lattice/methodology/19-sap-inflection-point-finding.md — the named-institution application.
• eve-glyph-education/game/design/observed-operator-patterns.md — the operator-pattern register these cases extend.
• eve-glyph-education/contributor-pathway.md — the protocol-level commitment to substrate portability the cases illustrate.

Pour le bien-être du peuple.

© 2026 Dany Theriault. EVE “digital stem cell” glyph and glyph-based design principles — all rights reserved. Stewardship of rights of use and assignment for large public and institutional usage rests with the Pacific Utilities Design Council. Published as a time-stamped record of authorship and intent.
pour le bien-être du peuple