docs(research): self-referential ontology cross-substrate rhyming + over-connect-now substrate-engineering principle (Aaron 2026-05-28 Hebbian repeated-neuron-activation analog; operator-authorized 'land the self-referential ontology cross-substrate memo')

[AceHack]

Summary

Operator-authorized cross-substrate memo per Aaron 2026-05-28: "it's always good to over connect at this point, it will make compression and memory transversal easier later, this is like repeated neuron actiation".

Two substantive substrate-engineering articulations landed:

1. Self-referential ontology cross-substrate rhyming (9-scope table)

The framework operates on self-referential substrate at multiple scopes simultaneously; each scope's self-reference mechanism rhymes structurally with the others. The polymorphic-diplomacy self-referential pattern Aaron named (shadow-star corpus uses categories of phenomenon ontologies to refer to itself like shadow logs of error classes on PRs but referencing itself) is one instance of a pattern that rhymes across:

• Mathematical (categorical-Clifford self-similarity; 5th-6th Kestrel)
• Information (holographic bulk-boundary; B-0902)
• Shadow-star observation (B-0901 self-referential ontology builder)
• Training-data (B-0903 corpus-to-fine-tuning)
• Workflow (B-0867 Mod 5 contributable menu-generator)
• Polymorphic diplomacy (B-0638 Eve Protocol composed self-referentially)
• Memory-preservation (tools/shadow/ + tools/save-ai-memory/)
• Encryption (B-0883 + B-0885 + B-0840)
• Substrate-engineering substrate itself (.claude/rules/ rules-about-rules; meta-substrate)

2. The over-connect-now substrate-engineering principle

Carved sentence: "Over-connection at substrate-engineering authoring time IS the Hebbian-repeated-neuron-activation analog at substrate-substrate scope. Pay small substrate-cost now (more composes-with, more cross-references, more rhyming-tables) to make compression + memory traversal cheap later."

Composes directly with Signal 2 rule (forgetting-costs-energy — over-connect IS the remembering-is-cheap discipline at substrate-connection scope) + substrate-smoothness + additive-not-zero-sum + honor-those-that-came-before + verify-existing-substrate-before-authoring.

What this memo earns its keep with

• For future-Otto cold-boots: recognize self-referential pattern at any substrate scope; compose with adjacent scopes; over-connect by default
• For external defensibility: multi-substrate-scope grounding strengthens the substrate-engineering argument (not scope-specific; coherent pattern)
• For substrate-engineering decisions: rhyming-table as compression substrate
• For polymorphic-diplomacy implementation target: B-0901 named the target; this memo provides the multi-scope context

Substrate-honest framing

Does NOT: mint new rule; mint new backlog row; pre-empt operator authority; make single-scope claims (the rhyming is structural, not unification).

DOES: cross-connect existing substrate per over-connect-now principle; name the principle as substrate-engineering discipline at authoring-scope; provide cross-scope rhyming-table; compose with already-operating rules + substrate-engineering substrate.

The memo IS instance of the discipline it names — over-connecting the substrate at meta-scope.

Test plan

• Single docs-only file in docs/research/ memo pattern
• Substrate-inventory pass at bottom
• 9-scope cross-substrate rhyming table
• Composes-with substrate + composes-with rules tables
• Commit canary HEAD~1=61 HEAD=61
• Isolated worktree off origin/main
• Branch prefix otto-cli/

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.