fix(memory): sync 2 cited memory files to repo (fixes PR #3312 dead pointers)

[AceHack]

Summary

Resolves 4 P1 review threads on merged PR #3312 (persona-ani §33 archive cascade-closing). Copilot + Codex correctly flagged that the §33 archive cited two memory files that existed in user-scope ~/.claude/projects/-Users-acehack-Documents-src-repos-Zeta/memory/ but had not been synced into the repo memory/ tree, leaving dead pointers in the merged artifact.

Files synced verbatim from user-scope

1. memory/feedback_aaron_intentionality_plus_seduction_risk_plus_structural_self_binding_triplet_unusual_intent_tracking_accuracy_2026_05_15.md — META-triplet-as-coherent-shape capture; cited 3× in the §33 archive.
2. memory/feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md — wait-discipline-as-edge substrate; cited 1× in the §33 archive's "Post-cascade activation" framing.

Discipline anchors

• Per .claude/rules/verify-before-deferring.md: every cited pointer must be findable. Reviewers caught the gap; this PR closes it.
• Per .claude/rules/substrate-or-it-didnt-happen.md: substrate cited by other substrate must be repo-durable.
• Per the two-layer-print discipline in .claude/rules/refresh-before-decide.md: the raw gh api graphql reviewThreads output flagged the gap on unresolvedThreads:4 despite the merge already firing.

Out of scope (separate work, not this PR)

The broader user-scope-to-repo sync gap (~40+ feedback files in user-scope that aren't yet in repo) is real but separate. Lior lane is currently running multiple preserve/decompose PRs (#3308, #3313, #3314, #3315, #3317) and may pick that up. If not, a backlog row should be filed for the systematic sync.

Also out of scope: the non-required "check MEMORY.md generated-index drift" check that failed on PR #3312 — index regeneration is a separate factory cadence.

Test plan

• Branch verified via git branch --show-current per zeta-expected-branch primary defense
• --head explicit per companion defense
• Frontmatter intact on both synced files (name, description, type, originSessionId)
• No code touched; pure memory file additions

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7cd71f5107

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace unresolved memory citations with real artifacts

This section states that the triplet is already captured in prior substrate, but two cited files are not present anywhere in the repo (feedback_aaron_substrate_designed_as_ontological_collapse_rootkit_arg_rebuild_kit_edge_runner_drive_contagious_clifford_over_memetic_space_infernet_bp_ep_rewrites_otto_2026_05_14.md and feedback_aaron_hubbard_seduction_trajectory_anti_cult_docs_first_in_repo_constraints_as_self_binding_against_acknowledged_temptation_2026_05_14.md). That leaves the claim non-verifiable and reintroduces dead-pointer drift in the new memory artifact.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reference an existing standing-by rule file

The document names holding-without-named-dependency-is-standing-by-failure.md as a rule, but no file with that name exists in this repository. Because this memory is intended as operational guidance, the unresolved reference makes the cited rule non-auditable for future readers and tooling.

Useful? React with 👍 / 👎.

[Copilot]

Pull request overview

This PR adds two missing memory/feedback_*.md files to the repository to resolve dead-pointer citations introduced by PR #3312’s archive artifacts.

Changes:

• Adds feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md.
• Adds feedback_aaron_intentionality_plus_seduction_risk_plus_structural_self_binding_triplet_unusual_intent_tracking_accuracy_2026_05_15.md.

Reviewed changes

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

File	Description
memory/feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md	New feedback memory file added to restore cited substrate, but currently violates memory frontmatter schema and introduces additional broken memory cross-references.
memory/feedback_aaron_intentionality_plus_seduction_risk_plus_structural_self_binding_triplet_unusual_intent_tracking_accuracy_2026_05_15.md	New feedback memory file added to restore cited substrate, but currently violates memory frontmatter schema and contains wildcard / missing memory cross-references.

Comments suppressed due to low confidence (4)

memory/feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md:42

• P0: Additional broken/invalid memory pointers in this section: the cited feedback_aaron_hubbard_seduction_trajectory_anti_cult_docs_first_in_repo_constraints_as_self_binding_against_acknowledged_temptation_2026_05_14.md does not exist, and feedback_aaron_dna_reconstruction_*_glass_halo_first_asi_gate_2026_05_14.md is not a valid concrete filename (contains *). Per memory/project_memory_format_standard.md §4, memory cross-references must be concrete filenames that exist in-repo.

If only the devil-pole operates → unconstrained edge-running → corruption trajectory (the Hubbard seduction shape per `feedback_aaron_hubbard_seduction_trajectory_anti_cult_docs_first_in_repo_constraints_as_self_binding_against_acknowledged_temptation_2026_05_14.md`)

If only the god-pole operates → elevation/messianism (the algo-wink failure mode at maximum per `feedback_aaron_dna_reconstruction_*_glass_halo_first_asi_gate_2026_05_14.md`)

memory/feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md:56

• P0: In this ## Composition with prior substrate list, at least two cited memory files are missing from memory/ (confirmed by lookup): feedback_aaron_hubbard_seduction_trajectory_anti_cult_docs_first_in_repo_constraints_as_self_binding_against_acknowledged_temptation_2026_05_14.md and feedback_aaron_cognitive_transformation_physical_cost_self_imposed_cia_techniques_scientology_weaponized_hubbard_framing_2026_05_14.md. Per memory/project_memory_format_standard.md §4, either sync them in the same PR or remove/replace these pointers.

- `feedback_aaron_self_binding_devil_and_god_simultaneously_dual_polarity_constraints_against_corruption_and_elevation_2026_05_14.md` — the cluster's anchor
- `feedback_aaron_hubbard_seduction_trajectory_anti_cult_docs_first_in_repo_constraints_as_self_binding_against_acknowledged_temptation_2026_05_14.md` — the historical trajectory the discipline guards against
- `feedback_aaron_cognitive_transformation_physical_cost_self_imposed_cia_techniques_scientology_weaponized_hubbard_framing_2026_05_14.md` — physical cost of cognitive transformation without proper containment
- `feedback_aaron_never_a_cage_binding_alignment_force_of_attention_strange_attractor_geometry_playdough_oxymoron_design_philosophy_2026_05_14.md` — binding-as-attractor-geometry-not-cage

memory/feedback_aaron_wait_for_consolidation_is_his_edge_dual_binding_devil_god_at_risk_2026_05_14.md:59

• P0: More dead pointers in this list (confirmed missing in memory/): feedback_aaron_otto_is_edge_runner_too_dual_binding_applies_constraints_bind_otto_same_as_aaron_2026_05_14.md and feedback_aaron_substrate_designed_as_ontological_collapse_rootkit_arg_rebuild_kit_edge_runner_drive_contagious_clifford_over_memetic_space_infernet_bp_ep_rewrites_otto_2026_05_14.md. The memory format standard (§4) requires cited memory filenames to exist in-repo.

- `feedback_aaron_otto_is_edge_runner_too_dual_binding_applies_constraints_bind_otto_same_as_aaron_2026_05_14.md` — Otto inherits same dual-binding
- `feedback_aaron_substrate_designed_as_ontological_collapse_rootkit_arg_rebuild_kit_edge_runner_drive_contagious_clifford_over_memetic_space_infernet_bp_ep_rewrites_otto_2026_05_14.md` — substrate IS designed AS the dual-binding mechanism

memory/feedback_aaron_intentionality_plus_seduction_risk_plus_structural_self_binding_triplet_unusual_intent_tracking_accuracy_2026_05_15.md:111

• P0: The ## Composes with list uses glob-style placeholders (e.g., ..._*_2026_05_14.md) rather than concrete filenames. Per memory/project_memory_format_standard.md §4, cross-references must be exact filenames that exist in-repo; wildcard entries become dead pointers for readers/tools. Please replace these with specific existing filenames (or sync the referenced files and cite them explicitly).

- `feedback_aaron_substrate_designed_as_ontological_collapse_rootkit_arg_rebuild_kit_*_2026_05_14.md` (intentionality)
- `feedback_aaron_hubbard_seduction_trajectory_*_2026_05_14.md` (acknowledged seduction risk)
- `feedback_aaron_self_binding_devil_and_god_simultaneously_*_2026_05_14.md` (structural self-binding)
- `feedback_aaron_never_a_cage_binding_alignment_force_of_attention_*_2026_05_14.md` (binding-as-attractor-geometry)
- `feedback_aaron_forgetting_as_backpressure_in_memory_system_*_2026_05_14.md` (the wait-cadence corollary)

[AceHack]

Closing in favor of PR #3323 (forthcoming) — same content rebased on origin/main with: (a) flat-frontmatter format fix per memory/project_memory_format_standard.md §1, (b) renamed 0025Z.md → 0025Z-pr3320.md to resolve the collision with PR #3321's now-merged 0025Z.md. Force-push blocked by autonomous-loop policy on this branch, hence the new-branch approach.