memory(substrate-is-product): Aaron 2026-04-30 reframe — substrate IS one of our products

[AceHack]

Summary

Lands the durable memory file for task #353 distilling Aaron's three corrections in this session that reframe what counts as factory work.

The framing shift: substrate IS one of our products, not infrastructure that supports the products. Initial split is four products in flight:

1. Factory substrate as product/project
2. Package manager
3. Database
4. Aurora

And the set is an evolving trajectory — count + composition shift as the factory learns and as the environment responds.

Why this matters

Under substrate-IS-infra: governance / doctrine / memory protocol / multi-AI orchestration time is overhead. Under substrate-IS-product: that time ships product. Different framings produce different prioritization.

Aaron's third correction ("this always has been substrate work, this is what it means to map out best practices for new domains") further sharpens — substrate-quality work isn't a promotion event. It's the default for new-domain factory work.

What lands

• memory/feedback_substrate_is_product_four_products_evolving_trajectory_aaron_2026_04_30.md — new memory file with rule + Why + 5 How-to-apply rules + Composes-with chain
• memory/MEMORY.md — paired-edit index entry (per memory-index-integrity rule)

Verbatim source

All three Aaron quotes preserved in docs/research/2026-04-30-multi-ai-feedback-packets-this-session.md (Otto-363 substrate-or-it-didn't-happen). This memory file is the durable distillation; the research doc is the verbatim archive.

Composes with

• feedback_internal_direction_from_project_survival_aaron_2026_04_30.md — per-product survival surfaces extend internal-direction per product
• feedback_otto_363_substrate_or_it_didnt_happen_no_invisible_directives_aaron_amara_2026_04_29.md — substrate discipline
• docs/research/2026-04-30-identity-of-project-and-agent-under-multi-repo-fork-competition.md — sharper identity question with four-products framing

Test plan

• memory file passes ASCII-clean lint (BP-10)
• MEMORY.md paired-edit included
• Composes-with chain verified — all linked files exist on main

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds a new durable memory entry capturing the “substrate is product” framing (with an initial four-product split and an explicitly evolving product trajectory), and indexes it in the memory catalog.

Changes:

• Added memory/feedback_substrate_is_product_four_products_evolving_trajectory_aaron_2026_04_30.md with the rule, rationale, application guidance, and compose-with links.
• Updated memory/MEMORY.md to include the new memory entry in the index.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
memory/feedback_substrate_is_product_four_products_evolving_trajectory_aaron_2026_04_30.md	New memory file describing the “substrate is product” framing + how-to-apply guidance and related links.
memory/MEMORY.md	Adds an index entry pointing at the new memory file.

[Copilot]

This memory introduces the term “doctrine” as the umbrella for the factory’s operating rules (“the doctrine” in the product list). The repo recently standardized on “canon” as the umbrella term replacing “doctrine” in new prose; consider switching this usage to “canon” (or “rule/protocol/discipline” as appropriate) to avoid vocabulary drift and contradictions.

[Copilot]

Naming/capitalization is inconsistent here: other repo docs refer to the “Ace package manager” as a proper name, but this line uses “ace package manager”. Consider capitalizing consistently to match existing references and avoid treating it as a generic noun phrase.

Suggested change

	2. **Package manager** — `../scratch` → ace package manager
	2. **Package manager** — `../scratch` → Ace package manager