@mindrian_os/cli 2.0.0-beta.3 → 2.0.0-beta.31

package/data/harness-fixtures/converged-room/STATE.md

@@ -0,0 +1,73 @@
+---
+computed: 2026-09-08T04:07:00Z
+venture_stage: Investment
+total_entries: 13
+---
+# Data Room State
+
+## Room Map
+
+┌─assets─────────────────────────────┐  ┌─business-model─────────────────────┐
+│ □ EMPTY - GAP                       │  │ ■ 1 artifact                        │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─competitive-analysis───────────────┐  ┌─financial-model────────────────────┐
+│ ■ 1 artifact                        │  │ ■ 1 artifact                        │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─funding────────────────────────────┐  ┌─legal-ip───────────────────────────┐
+│ ■ 1 artifact                        │  │ ■ 1 artifact                        │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─market-analysis────────────────────┐  ┌─opportunity-bank───────────────────┐
+│ ■ 1 artifact                        │  │ ■ 1 artifact                        │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─problem-definition─────────────────┐  ┌─references─────────────────────────┐
+│ ■ 1 artifact                        │  │ ■ 2 artifacts                       │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─solution-design────────────────────┐  ┌─strategy───────────────────────────┐
+│ ■ 1 artifact                        │  │ ■ 1 artifact                        │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+┌─team-execution─────────────────────┐  ┌─team───────────────────────────────┐
+│ ■ 1 artifact                        │  │ □ EMPTY - GAP                       │
+│ ? Investment                        │  │ ? Investment                        │
+└─────────────────────────────────────┘  └─────────────────────────────────────┘
+
+Section Completeness
+       2.00 ┼        ╭╮    
+       1.50 ┤        ││    
+       1.00 ┤╭───────╯╰──╮ 
+       0.50 ┤│           │ 
+       0.00 ┼╯           ╰ 
+
+## Sections
+| Section | Entries | Progress | Status | Last Updated |
+|---------|---------|----------|--------|-------------|
+| assets | 0 | ░░░░░░░░░░ 0% | Empty | 2026-09-08 |
+| business-model | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| competitive-analysis | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| financial-model | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| funding | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| legal-ip | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| market-analysis | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| opportunity-bank | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| problem-definition | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| references | 2 | ████░░░░░░ 40% | Active | 2026-09-08 |
+| solution-design | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| strategy | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| team-execution | 1 | ██░░░░░░░░ 20% | Active | 2026-09-08 |
+| team | 0 | ░░░░░░░░░░ 0% | Empty | 2026-09-08 |
+
+## Gaps
+- assets: No entries.
+- team: No entries.
+
+## Cross-References
+- problem-definition/CONTEXT.md references opportunity-bank
+- references/SECTION-SCHEMA.md references team
+
+## Suggested Next Action
+Comprehensive Data Room. Review gaps and strengthen weak sections for investor readiness.

package/data/harness-fixtures/converged-room/USER.md

@@ -0,0 +1,23 @@
+# User Context
+
+## Identity
+
+*(unknown; will be inferred from conversation per Phase 115 dual-path detector)*
+
+## Venture Context
+
+- **Core idea:** *(not yet articulated)*
+- **Stage:** Pre-Opportunity
+- **Primary concern:** *(unknown)*
+
+## Working Style
+
+*(unknown; will be inferred from conversational turns)*
+
+## Persona Blend
+
+*(empty -- per Phase 115 D-12, the persona blend is inferred from STATE.md + USER.md
+once enough material accumulates; until then Larry defaults to the 'default' variant)*
+
+<!-- Phase 119 auto-scaffolded. Edit freely; subsequent renames or content additions
+     from /mos:onboard / /mos:new-project / persona-analyst will merge into this file. -->

package/data/harness-fixtures/converged-room/assets/ROOM.md

@@ -0,0 +1,13 @@
+---
+directory_type: assets
+icm_layer: 0
+auto_scaffolded: true
+purpose: "Binary file storage (PDFs, images, videos) organized by section. Subdirectories appear when scripts/file-asset is invoked."
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15. Every directory in the Data
+     Room has ROOM.md -- no exceptions. This file was auto-scaffolded by Phase 119. -->
+
+# assets
+
+Binary file storage (PDFs, images, videos) organized by section. Subdirectories appear when scripts/file-asset is invoked.

package/data/harness-fixtures/converged-room/business-model/CONTEXT.md

@@ -0,0 +1,32 @@
+# business-model - how this venture makes money
+
+**Statement:** This section holds how this venture makes money, and the value proposition that claim rests on.
+
+One job: hold how this venture makes money, and the value proposition that claim rests on.
+
+## Inputs
+- Working (this room): `market-analysis/`'s segments; `solution-design/`'s solution.
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: the legal structure or agreements. That is `legal-ip/`'s job; this section states the revenue logic, not the contracts that implement it.
+
+## Process
+1. Name the revenue model: how the venture actually gets paid.
+2. Name the customer segments and the payer, who signs, which may not be the same person as the user. If they differ, name both.
+3. Name the value proposition the whole claim rests on.
+
+**D-02, stated explicitly:** Value Proposition is sub-structure inside this section, NOT a section of its own. Three independent sources agree: Theo's book has no standalone value-proposition chapter (the material sits inside `bmd`, business model design); the 2026-04-14 Notion primary source gives Value Proposition and Business Model the identical statement text ("How Do We make money") and the identical icon, immediately adjacent; and `/mos:validate-proposition` already produces into `room/business-model/value-proposition/*` in the live command registry. One reservation, stated for the same reason: "Value Proposition" is a loaded PWS term naming the third gate of Triple Validation (Is it Real? / Can We Win? / Is it Worth It?), a venture-level judgment, so it is not reused as a per-section field name anywhere.
+
+## Outputs
+- One folder per artifact at `business-model/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact. `value-proposition/` is one such sub-folder, not a separate section.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- Who signs the cheque, and is that the same person as the user? If not, both are named.
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): `/mos:lean-canvas`, `/mos:validate-proposition`
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:explore-futures`, `/mos:mullins`, `/mos:analyze-systems`

package/data/harness-fixtures/converged-room/business-model/ROOM.md

@@ -0,0 +1,36 @@
+---
+section: business-model
+statement: "This section holds how this venture makes money, and the value proposition that claim rests on."
+purpose: "Define revenue model, unit economics, go-to-market."
+stage_relevance:
+  - Design
+  - Investment
+default_methodologies:
+  - lean-canvas
+  - validate-proposition
+  - structure-argument
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Business Model
+
+> This section holds how this venture makes money, and the value proposition that claim rests on.
+
+Define revenue model, unit economics, go-to-market.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/competitive-analysis/CONTEXT.md

@@ -0,0 +1,33 @@
+# competitive-analysis - who else, what survives copying
+
+**Statement:** This section holds who else is solving this, and what would still be true if a competitor copied us.
+
+One job: hold who else is solving this, and what would still be true if a competitor copied us.
+
+## Inputs
+- Working (this room): `solution-design/`'s claimed defensibility. This is the reciprocal half of the moat cross-link: `solution-design` records the claim that a technical choice enables a feature that is hard to copy; this section is where that claim gets tested against a real competitor.
+- Working (this room): `market-analysis/`'s segments.
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: the financial model or the legal structure. Competitive positioning is about the market, not the numbers or the paperwork behind it.
+
+## Process
+1. Enumerate real competitors.
+2. Compare on the dimension the customer actually buys on, not the dimension easiest to compare.
+3. Test the `solution-design` moat claim against them: does the claimed defensibility survive the strongest competitor named here?
+
+## Outputs
+- One folder per artifact at `competitive-analysis/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- Take the defensibility claim recorded in `solution-design` and ask whether it survives the strongest competitor named here. If it does not, the claim is a feature, not a moat, and `solution-design` needs updating.
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): `/mos:compare-ventures`
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:challenge-assumptions`
+
+Note: the Reverse Salient family moved to `strategy` in Phase 275 (D-06).

package/data/harness-fixtures/converged-room/competitive-analysis/ROOM.md

@@ -0,0 +1,35 @@
+---
+section: competitive-analysis
+statement: "This section holds who else is solving this, and what would still be true if a competitor copied us."
+purpose: "Analyze competition, positioning, differentiation."
+stage_relevance:
+  - Discovery
+  - Design
+default_methodologies:
+  - compare-ventures
+  - challenge-assumptions
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Competitive Analysis
+
+> This section holds who else is solving this, and what would still be true if a competitor copied us.
+
+Analyze competition, positioning, differentiation.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/financial-model/CONTEXT.md

@@ -0,0 +1,30 @@
+# financial-model - the numbers and what breaks them
+
+**Statement:** This section holds the numbers, the assumptions under them, and what breaks them.
+
+One job: hold the numbers, the assumptions under them, and what breaks them.
+
+## Inputs
+- Working (this room): `business-model/`'s revenue model; `market-analysis/`'s sizing.
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: the funding pipeline. That is `funding/`, a separate section as of Phase 275: this model says what the venture needs, the pipeline tracks where the money is coming from.
+
+## Process
+1. Build the projection.
+2. Surface every assumption it rests on.
+3. Name the assumption that breaks it first.
+
+## Outputs
+- One folder per artifact at `financial-model/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- Change the single most load-bearing assumption by half and see whether the conclusion survives. If the model has no such assumption identified, it is not finished.
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): none direct today. This section relies on the wildcard `/mos:build-thesis`, which produces to `room/**/thesis/*`, plus the grading commands. Also a named structural gap.
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:build-thesis`, `/mos:grade`, `/mos:deep-grade` (the PWS Triple Validation Compass, specifically its "Is It Worth It" gate)

package/data/harness-fixtures/converged-room/financial-model/ROOM.md

@@ -0,0 +1,35 @@
+---
+section: financial-model
+statement: "This section holds the numbers, the assumptions under them, and what breaks them."
+purpose: "Build financial projections and metrics."
+stage_relevance:
+  - Design
+  - Investment
+default_methodologies:
+  - build-thesis
+  - grade
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Financial Model
+
+> This section holds the numbers, the assumptions under them, and what breaks them.
+
+Build financial projections and metrics.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/funding/CONTEXT.md

@@ -0,0 +1,41 @@
+# funding - the pipeline from discovery to outcome
+
+**Statement:** This section tracks funding paths, dilutive and non-dilutive, from discovery through submission to outcome.
+
+One job: track funding paths from discovery through submission to outcome, so no deadline is missed and no application is silently abandoned.
+
+## Inputs
+- Working (this room): `financial-model/`'s stated need (how much, by when).
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+**Reads from:** `opportunity-bank/`. Every entry here starts life as a banked opportunity promoted by `/mos:funding create`, and carries a `[[opportunity-bank/<source>]]` wikilink back to its discovery.
+
+Do NOT load: the financial model's internals. This section tracks where money comes from, not what the venture does with it.
+
+## Process
+1. Promote: `/mos:funding create <opportunity-slug>` moves an opportunity from `opportunity-bank/` into this pipeline at initial stage Discovered.
+2. Advance: move a funding entry to the next stage. Stage and outcome are two orthogonal dimensions, named separately because conflating them is the error the command's own Design Note exists to prevent:
+   - **Stage** is lifecycle position, sequential and enforced: Discovered, then Researched, then Applying, then Submitted. No skipping. No going backward. Each transition is recorded in `transition_history`.
+   - **Outcome** is the result, not a stage: `awarded`, `rejected`, `withdrawn`. `awarded` and `rejected` are only valid once an entry has reached Submitted; `withdrawn` is valid at any stage.
+3. Record outcome once a result exists.
+
+The full sub-schema lives in `../references/SUB-SCHEMAS.md`; this contract points at the schema rather than duplicating it.
+
+**Scope: two funding types, one implemented.** The 2026-04-14 primary source nests exactly two types under Funding Options: **Dilutive Funding** (equity and venture capital; you give up ownership) and **Non-Dilutive** (grants and similar; you do not). This section's contract covers both. The command surface today implements only the non-dilutive half: `/mos:funding` and `/mos:opportunities scan` are 100 percent Grants.gov and Simpler-Grants sourced, with zero equity, VC, loan, crowdfunding or angel support (grep-confirmed). Dilutive tracking is a named, deliberate deferral from Phase 275, not an oversight and not a claim that dilutive funding does not matter. Until it is built, record dilutive conversations as ordinary dated entry folders in this section; they will not have a stage machine.
+
+Honest command gap: ground truth is none today. No methodology command produces directly into this section. That absence is exactly what the icm-architect audit found at the room level (an empty `funding/` shell) and what the command sweep confirmed at the command level; the two are the same gap seen from two angles.
+
+## Outputs
+- One folder per artifact at `funding/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- For every entry not at Submitted, is there a next action with a date on it. An entry that has not moved in fourteen days is either dead or being avoided; say which.
+
+## Commands that write here
+- Ground truth: none today.
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:mullins`, `/mos:grade`, `/mos:deep-grade`
+- Utility surface (operates on the pipeline rather than producing methodology content into it): `/mos:funding`

package/data/harness-fixtures/converged-room/funding/ROOM.md

@@ -0,0 +1,35 @@
+---
+section: funding
+statement: "This section tracks funding paths, dilutive and non-dilutive, from discovery through submission to outcome."
+purpose: "Track funding paths, dilutive and non-dilutive, from discovery to submission."
+stage_relevance:
+  - Validation
+  - Investment
+default_methodologies:
+  - mullins
+  - grade
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Funding
+
+> This section tracks funding paths, dilutive and non-dilutive, from discovery through submission to outcome.
+
+Track funding paths, dilutive and non-dilutive, from discovery to submission.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/legal-ip/CONTEXT.md

@@ -0,0 +1,30 @@
+# legal-ip - structure, agreements, what is protected
+
+**Statement:** This section holds the legal structure, the agreements, and what is actually protected.
+
+One job: hold the legal structure, the agreements, and what is actually protected.
+
+## Inputs
+- Working (this room): `solution-design/`'s technical choices (what is patentable or trade-secret depends on them); `business-model/`'s revenue model (what needs contracting).
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: market sizing or competitive positioning. Those live in `market-analysis/` and `competitive-analysis/`.
+
+## Process
+1. Name the entity.
+2. Name the agreements.
+3. Name the IP position and the regulatory surface, using the 2026-04-14 Notion primary source's own four nested sub-areas under Legal Docs as the working structure: Regulatory Compliance, Incorporation docs, Contracts and Agreements, Intellectual Property.
+
+## Outputs
+- One folder per artifact at `legal-ip/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- For each thing claimed as protected, name the mechanism and its expiry.
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): none today. No methodology command produces directly into this section. This is a real, named structural gap (SEED-084 `## ADDENDUM 2026-09-04e`), not an omission in this contract.
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:challenge-assumptions` (Red Teaming, whose risk-surfacing fits legal and IP exposure review)

package/data/harness-fixtures/converged-room/legal-ip/ROOM.md

@@ -0,0 +1,35 @@
+---
+section: legal-ip
+statement: "This section holds the legal structure, the agreements, and what is actually protected."
+purpose: "Track legal structure, agreements, IP protection."
+stage_relevance:
+  - Design
+  - Investment
+default_methodologies:
+  - structure-argument
+  - challenge-assumptions
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Legal Ip
+
+> This section holds the legal structure, the agreements, and what is actually protected.
+
+Track legal structure, agreements, IP protection.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/market-analysis/CONTEXT.md

@@ -0,0 +1,32 @@
+# market-analysis - who has it, how many, doing what
+
+**Statement:** This section holds who has this problem, how many of them there are, and what they do about it today.
+
+One job: hold who has this problem, how many of them there are, and what they do about it today.
+
+## Inputs
+- Working (this room): `problem-definition/`'s stated problem.
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: the funding pipeline, or marketing and sales strategy. Marketing and Sales is a real, deliberately deferred gap: the 2026-04-14 Notion primary source names a distinct "Marketing & Sales" section (Marketing Strategies, Sales Strategies & Pipelines) that Phase 275 chose NOT to build. Do not silently absorb that content into this section; if it shows up, name it as belonging to a section that does not exist yet, rather than filing it here.
+
+## Process
+1. Size the market: how many people or organizations actually have this problem.
+2. Segment it: which of them are alike enough to sell to the same way.
+3. Name the job being hired for: the outcome the segment is actually paying to get, not the feature they ask for.
+
+## Outputs
+- One folder per artifact at `market-analysis/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- Is there a real number here, sourced, or is an adjective standing in for one?
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): `/mos:analyze-needs` (produces `room/market-analysis/jtbd-analysis/*`, refiled here from `team-execution` in Phase 275 per D-05), `/mos:user-needs`
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:macro-trends`, `/mos:analyze-timing`, `/mos:diffusion`, `/mos:explore-trends`, `/mos:dominant-designs`, `/mos:mullins`
+
+Note: `/mos:scenario-plan` used to be cited here under the dead slug `scenario-analysis` and now lives in `strategy` (D-05, D-06).

package/data/harness-fixtures/converged-room/market-analysis/ROOM.md

@@ -0,0 +1,35 @@
+---
+section: market-analysis
+statement: "This section holds who has this problem, how many of them there are, and what they do about it today."
+purpose: "Map market size, trends, and customer segments."
+stage_relevance:
+  - Discovery
+  - Validation
+default_methodologies:
+  - analyze-needs
+  - user-needs
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Market Analysis
+
+> This section holds who has this problem, how many of them there are, and what they do about it today.
+
+Map market size, trends, and customer segments.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.

package/data/harness-fixtures/converged-room/opportunity-bank/CONTEXT.md

@@ -0,0 +1,39 @@
+# opportunity-bank - the opportunities found but not yet chosen
+
+**Statement:** This section banks the opportunities found but not yet chosen, each with its Knight position and confidence.
+
+One job: bank the opportunities found but not yet chosen, so none is lost and none is prematurely committed to.
+
+## Inputs
+- Working (this room): `problem-definition/`'s ladder position; `market-analysis/`'s segments; external grant discovery via `/mos:opportunities scan` against Grants.gov and Simpler Grants.
+- Reference (every run): ../references/SECTION-SCHEMA.md
+- Reference (when relevant): ../references/SUB-SCHEMAS.md
+
+Do NOT load: the funding pipeline's own stage state. That is `funding/`'s job; this section holds candidates, not applications.
+
+## Process
+1. Bank each opportunity with its Knight position and confidence score. Do not collapse risk and uncertainty into a single undifferentiated "opportunity."
+2. Keep the two source kinds distinguished: grant-sourced (via `/mos:opportunities scan`) and cascade-sourced (extracted automatically by any methodology command that triggers analyze-room).
+3. Promote only when a candidate earns it, never on a timer.
+
+Quoted verbatim from `commands/opportunities.md:60`: every opportunity carries a Knight position (risk vs uncertainty vs mixed) and a confidence score. Risk is a known problem with quantifiable odds. Uncertainty is an unknown problem requiring exploration. Mixed is a contradiction that could go either way. The full sub-schema (Knight position plus confidence score, and the two source kinds) lives in `../references/SUB-SCHEMAS.md`; this contract points at the schema rather than duplicating it.
+
+**Feeds:** this section feeds `funding/`. `/mos:funding create <opportunity-slug>` promotes a banked opportunity into the funding pipeline at initial stage Discovered, and writes a `[[opportunity-bank/<source>]]` wikilink from the funding entry back to this one, creating a real graph edge back to the discovery. That wikilink is the existing cross-reference mechanism; no other syntax is invented here.
+
+Ground this section's own standing, honestly and briefly: this is the only one of the three sections Phase 275 adds that has a verbatim book-canon hit. Theo's `growth` chapter names "build a bank of opportunities" as the defining action of the Ill-Defined rung of the PWS ladder.
+
+## Outputs
+- One folder per artifact at `opportunity-bank/<artifact-slug>/<artifact-slug>.md` (the Obsidian-nested convention, Key Decision 16). The folder IS the artifact.
+- Never inline content into `ROOM.md`. `ROOM.md` is ICM Layer 0 identity only: statement, purpose, stage relevance, default methodologies. Real content is ICM Layer 4 and lives in its own dated entry folder. Five of twelve sections in the audited `launchpad-02` room had already drifted this way; this line is why the contract exists.
+
+## Human check
+- Feynman: can a stranger restate this section's governing thought in one sentence, without jargon?
+- Minto: does the apex claim sit on MECE-grouped, non-overlapping support?
+- For each banked opportunity, is the Knight position argued or just asserted. A confidence score with no reason behind it is a number, not a judgment.
+
+## Commands that write here
+- Ground truth (the command's own `produces` path names this section): `/mos:futures`, `/mos:score-innovation`, `/mos:trending-to-absurd`, `/mos:whitespace`
+- Framework-matched (a wildcard command whose framework fits this section's job): `/mos:explore-futures`
+- Utility surface (operates on the bank rather than producing methodology content into it): `/mos:opportunities`
+
+Note: `/mos:trending-to-absurd` used to be cited under `problem-definition` and was refiled here in Phase 275 (D-05), because that is where it actually produces.

package/data/harness-fixtures/converged-room/opportunity-bank/ROOM.md

@@ -0,0 +1,36 @@
+---
+section: opportunity-bank
+statement: "This section banks the opportunities found but not yet chosen, each with its Knight position and confidence."
+purpose: "Bank the opportunities discovered before any one is chosen."
+stage_relevance:
+  - Pre-Opportunity
+  - Discovery
+default_methodologies:
+  - trending-to-absurd
+  - whitespace
+  - futures
+icm_layer: 0
+auto_scaffolded: true
+---
+
+<!-- ICM Layer 0 identity file per Canon decision 15 (every directory has ROOM.md).
+     This file was auto-scaffolded by Phase 119 (Room-as-Receipt Invariant); content
+     will be populated by /mos:* methodology runs or by Larry's first conversation.
+     Phase 275: `statement` is the ICM L1 routing field carried on this L0 identity
+     file, rendered twice (frontmatter key for tools, body blockquote for a human
+     or a foreign host reading raw markdown with no MCP tools). The ICM L2 contract
+     for this section lives in the sibling CONTEXT.md. -->
+
+# Opportunity Bank
+
+> This section banks the opportunities found but not yet chosen, each with its Knight position and confidence.
+
+Bank the opportunities discovered before any one is chosen.
+
+## Starter Questions
+
+*(populated when material lands or methodology fires; until then the section is empty by design)*
+
+## Status
+
+Auto-scaffolded. Awaiting first content.