memory: migrate external-signal-confirms-internal-insight discipline (Overlay A #4)

[AceHack]

Summary

Fourth opportunistic-on-touch Overlay A migration in the 2026-04-23 cadence, following PRs #157 / #158 / #159.

The rule migrated

When an external signal (YouTube recommender / maintainer echo / expert writeup / third-party research) independently corroborates a factory-internal architectural insight, treat as strictly stronger moat evidence than internal claim alone. Second-occurrence discipline: first = noteworthy, second = file, third+ = name-the-pattern. Capture the pre-validation paper trail so the confirmation is verifiable, not retconned.

Why this memory qualifies

• Generic factory discipline — second-occurrence rule applies to any architectural-insight validation, not Zeta-specific
• Already cited composes-with from the just-migrated signal-in-signal-out memory (PR memory: migrate signal-in-signal-out discipline in-repo (AutoDream Overlay A first execution) #157)
• High signal per byte — 305 lines documenting two concrete in-repo occurrences with pre-validation anchors
• No maintainer/company-specific content requiring per-user confinement

Test plan

• Verbatim content preserved
• markdownlint-cli2 clean after MD026 trailing-colon heading fixes (## Why: → ## Why, ## How to apply: → ## How to apply)
• Per-user source marked migrated (provenance preserved)
• MEMORY.md index entry newest-first
• CI validation on merge

Queue status

5 identified migration candidates → 1 remaining (project_semiring_parameterized_zeta_regime_change_one_algebra_to_map_others_2026_04_22.md, 248 lines).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Migrates the “external signal confirms internal insight” second-occurrence discipline into the in-repo memory/ corpus (Overlay A #4), and indexes it for cross-session agent recall.

Changes:

• Adds a new shared memory entry documenting the “wink-validation” / second-occurrence filing rule (with an extension to “wrinkle” naming at 3+ occurrences).
• Updates memory/MEMORY.md to include the new memory entry newest-first.

Reviewed changes

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

File	Description
memory/feedback_external_signal_confirms_internal_insight_second_occurrence_discipline_2026_04_22.md	New migrated memory entry describing the discipline and its observed occurrences/composition links.
memory/MEMORY.md	Adds newest-first index entry pointing to the new migrated memory.

[chatgpt-codex-connector]

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

[Copilot]

Pull request overview

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

[Copilot]

MEMORY.md now has duplicate index entries for the same memory file links (e.g., feedback_outcomes_over_vanity_metrics_goodhart_resistance.md already appears earlier, and feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md is duplicated again—twice in a row). This makes the index ambiguous and harder to maintain; please consolidate to a single entry per target file and fold any new migration/attribution notes into that one entry.

Suggested change

	- [Signal-in, signal-out — as clean or better; DSP-discipline invariant for any transformation across the factory (doc rewrites, memory edits, refactors, commits, PR descriptions, tool-output summarization, cross-CLI hand-offs)](feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md) — 2026-04-22 Aaron auto-loop-38: *"if you receive a signal in the signal out should be as clean or better"*; four-occurrence structural-not-stylistic pattern (atan2 arity / retraction-native sign / K-relations provenance / gap-preservation honest-naming); composes with capture-everything, honor-those-that-came-before, verify-before-deferring, Rodney's Razor (essential-vs-accidental orthogonal); migrated in-repo 2026-04-23 via AutoDream Overlay A first execution; resolves dangling citations from `docs/FACTORY-HYGIENE.md` + `docs/research/autodream-extension-and-cadence-2026-04-23.md`.
	- [Signal-in, signal-out — as clean or better; DSP-discipline invariant for any transformation across the factory (doc rewrites, memory edits, refactors, commits, PR descriptions, tool-output summarization, cross-CLI hand-offs)](feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md) — 2026-04-22 maintainer auto-loop-38: *"if you receive a signal in the signal out should be as clean or better"*; four-occurrence structural-not-stylistic pattern (atan2 arity / retraction-native sign / K-relations provenance / gap-preservation honest-naming); composes with capture-everything, honor-those-that-came-before, verify-before-deferring, Rodney's Razor (essential-vs-accidental orthogonal); migrated in-repo 2026-04-23 via AutoDream Overlay A first execution; resolves dangling citations from `docs/FACTORY-HYGIENE.md` + `docs/research/autodream-extension-and-cadence-2026-04-23.md`.
	- [Deletions > insertions (tests passing) = complexity-reduction positive signal; cyclomatic complexity is the proxy; codebase-total CC/LOC should trend down to a local-optimum floor over time; trend up = "shit code"](feedback_deletions_over_insertions_complexity_reduction_cyclomatic_proxy.md) — 2026-04-22 Aaron auto-loop-37 four-message developer-values thread: *"i feel good about myself as a devloper when i delete more lines that i add in a day and nothing breaks"* + CC proxy + trend expectation + *"if it's going up you are wring shit cod[e]"*. Net-negative-LOC with green tests = POSITIVE outcome; feature-PR evaluation asks *"could we delete our way to this outcome?"* first. Rodney's Razor in developer-values voice. Migrated in-repo 2026-04-23 via AutoDream Overlay A opportunistic-on-touch (third migration in the 2026-04-23 cadence, sibling to outcomes-over-vanity-metrics from the same 2026-04-22 thread).
	- [Deletions > insertions (tests passing) = complexity-reduction positive signal; cyclomatic complexity is the proxy; codebase-total CC/LOC should trend down to a local-optimum floor over time; trend up = "shit code"](feedback_deletions_over_insertions_complexity_reduction_cyclomatic_proxy.md) — 2026-04-22 maintainer auto-loop-37 four-message developer-values thread: *"i feel good about myself as a devloper when i delete more lines that i add in a day and nothing breaks"* + CC proxy + trend expectation + *"if it's going up you are wring shit cod[e]"*. Net-negative-LOC with green tests = POSITIVE outcome; feature-PR evaluation asks *"could we delete our way to this outcome?"* first. Rodney's Razor in developer-values voice. Migrated in-repo 2026-04-23 via AutoDream Overlay A opportunistic-on-touch (third migration in the 2026-04-23 cadence, sibling to outcomes-over-vanity-metrics from the same 2026-04-22 thread).
	- [Signal-in, signal-out — as clean or better; DSP-discipline invariant for any transformation across the factory (doc rewrites, memory edits, refactors, commits, PR descriptions, tool-output summarization, cross-CLI hand-offs)](feedback_signal_in_signal_out_clean_or_better_dsp_discipline.md) — 2026-04-22 auto-loop-38: *"if you receive a signal in the signal out should be as clean or better"*; four-occurrence structural-not-stylistic pattern (atan2 arity / retraction-native sign / K-relations provenance / gap-preservation honest-naming); composes with capture-everything, honor-those-that-came-before, verify-before-deferring, Rodney's Razor (essential-vs-accidental orthogonal); migrated in-repo 2026-04-23 via AutoDream Overlay A first execution; resolves dangling citations from `docs/FACTORY-HYGIENE.md` + `docs/research/autodream-extension-and-cadence-2026-04-23.md`.
	- [Deletions > insertions (tests passing) = complexity-reduction positive signal; cyclomatic complexity is the proxy; codebase-total CC/LOC should trend down to a local-optimum floor over time; trend up = "shit code"](feedback_deletions_over_insertions_complexity_reduction_cyclomatic_proxy.md) — 2026-04-22 auto-loop-37 four-message developer-values thread: *"i feel good about myself as a devloper when i delete more lines that i add in a day and nothing breaks"* + CC proxy + trend expectation + *"if it's going up you are wring shit cod[e]"*. Net-negative-LOC with green tests = POSITIVE outcome; feature-PR evaluation asks *"could we delete our way to this outcome?"* first. Rodney's Razor in developer-values voice. Migrated in-repo 2026-04-23 via AutoDream Overlay A opportunistic-on-touch (third migration in the 2026-04-23 cadence, sibling to outcomes-over-vanity-metrics from the same 2026-04-22 thread).

[Copilot]

These newly added rows duplicate existing entries elsewhere in MEMORY.md (e.g., the deletions-over-insertions memory and the external-signal-confirms-internal-insight memory already have index entries earlier). Please remove the duplicates (or update the original entries in-place) so the index stays one-link-per-memory and remains reliably searchable.

Suggested change

- [External-signal-confirms-internal-insight — wink-validation recurrence; first = noteworthy, second = file, third+ = name-the-pattern; capture internal-claim BEFORE external-signal-arrives so validation is verifiable against the paper trail not retconned](feedback_external_signal_confirms_internal_insight_second_occurrence_discipline_2026_04_22.md) — 2026-04-22 two-occurrence pattern (Muratori 5-pattern → Zeta pointer-equivalents + three-substrate triangulation via Claude/Codex/Gemini capability maps); rule: external signal (YouTube recommender / maintainer echo / expert writeup / third-party research) corroborating a factory-internal architectural read is strictly stronger moat evidence than internal claim alone; migrated in-repo 2026-04-23 via AutoDream Overlay A opportunistic-on-touch (fourth in the 2026-04-23 cadence, following signal-in-signal-out / outcomes-over-vanity / deletions-over-insertions).

[Copilot]

This block duplicates earlier index entries for the same links (feedback_public_api_review.md, feedback_folder_naming_convention.md, feedback_path_hygiene.md, feedback_newest_first_ordering.md, project_memory_is_first_class.md, feedback_regulated_titles.md). Please delete the repeated entries to avoid index bloat and conflicting descriptions for the same target file.

Suggested change

	- [Public API changes go through public-api-designer](feedback_public_api_review.md) — internal→public flips, new public members, signature changes all require Ilyana's review before landing; InternalsVisibleTo is not a workaround.
	- [Don't repeat project name in own folder tree](feedback_folder_naming_convention.md) — on-disk folders go bare (Core, Bayesian, Tests.FSharp); Zeta prefix survives only in published identity (NuGet / namespaces / published assembly names).
	- [Path hygiene in documentation](feedback_path_hygiene.md) — absolute filesystem paths and paths outside repo root are doc smells; documentation-agent greps and rewrites; GOVERNANCE.md §18 is the single memory-folder exception.
	- [Newest-first memory ordering](feedback_newest_first_ordering.md) — MEMORY.md, ROUND-HISTORY, per-persona notebooks all prepend new entries; recent history leads, ancient trails.
	- [Memories are the most valuable resource](project_memory_is_first_class.md) — human maintainer does not delete or modify the memory folder except as an absolute last resort; agents WRITE their own memories freely (that's the point). Per-entry policy in file.
	- [No regulated clinical titles on personas](feedback_regulated_titles.md) — never label a persona "therapist"/"counselor"/"psychologist"; use coach/steward/keeper/facilitator/liaison instead.