Skip to content

feat(memory): add new memory files (decomposed from #4059)#4741

Closed
AceHack wants to merge 1 commit into
mainfrom
lior-decompose-4059-memory
Closed

feat(memory): add new memory files (decomposed from #4059)#4741
AceHack wants to merge 1 commit into
mainfrom
lior-decompose-4059-memory

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 23, 2026

This PR extracts the memory files from #4059.

Copilot AI review requested due to automatic review settings May 23, 2026 16:49
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR extracts and lands several new memory/ entries (plus an updated memory/MEMORY.md auto-index) that were previously bundled in PR #4059, preserving those artifacts as first-class repo memory.

Changes:

  • Adds new project_*.md and feedback_*.md memory files with YAML frontmatter.
  • Updates memory/MEMORY.md auto-index to include the new entries and adjust the “Last reindex”/heap count metadata.

Reviewed changes

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

File Description
memory/project_agora_vision_and_ai_native_economy_2026_05_17.md Adds a new project memory describing the Agora V5 narrative.
memory/MEMORY.md Updates the generated stack index and “Last reindex” metadata.
memory/feedback_otto_cli_pr_4059_two_ci_failure_lessons_backlog_regen_working_tree_leak_and_invisible_unicode_typography_leak_2026_05_17.md Adds a feedback memory capturing CI failure lessons from PR #4059.
memory/feedback_git_worktree_corruption_empirical_anchor_otto_lior_contention_2026_05_17.md Adds a feedback memory documenting a git worktree corruption incident and mitigation intent.

Comment thread memory/MEMORY.md
**📌 Fast path: read `CURRENT-aaron.md`, `CURRENT-amara.md`, `CURRENT-ani.md`, `CURRENT-vera.md`, `CURRENT-riven.md`, and `CURRENT-otto.md` first.**

> **Stack-vs-heap framing (Aaron 2026-05-12):** This file is the **STACK** — indexed, ordered, traversable canonical view. Recent memory files in `memory/` with timestamps newer than the most-current entries here may be **HEAP** — floating cache, not yet indexed, accessible by direct path. Both are easily accessible: stack via traversal, heap via timestamp/filename. Indexing (heap→stack promotion) happens on cadence via `tools/memory/reindex-memory-md.ts` (B-0423), callable from the autonomous-loop tick. Last reindex: 2026-05-16.
> **Stack-vs-heap framing (Aaron 2026-05-12):** This file is the **STACK** — indexed, ordered, traversable canonical view. Recent memory files in `memory/` with timestamps newer than the most-current entries here may be **HEAP** — floating cache, not yet indexed, accessible by direct path. Both are easily accessible: stack via traversal, heap via timestamp/filename. Indexing (heap→stack promotion) happens on cadence via `tools/memory/reindex-memory-md.ts` (B-0423), callable from the autonomous-loop tick. Last reindex: 2026-05-17.
**Date:** 2026-05-17
**Origin:** User (Aaron) / Ani
**Type:** Foundational Narrative / North Star

Comment on lines +8 to +11
## Context

PR [#4059](https://github.com/Lucent-Financial-Group/Zeta/pull/4059) was opened at 10:19Z shipping the Imaginary Stack Step-1 cluster (B-0584 + 2 research + Lean toy model). First CI sweep surfaced 3 mechanical failures (BACKLOG.md drift + tick-shard relative-paths + markdownlint MD047). I fixed all 3 in commit `b8d6947` at 10:34Z. Round-2 CI surfaced **2 new failures** that revealed structural lessons worth substrate-landing.

txt = f.read()
bad = [0x200B, 0x200C, 0x200D, 0xFEFF, 0x2060] + list(range(0x2066, 0x206A))
n = sum(1 for c in txt if ord(c) in bad)
print(f'invisible-unicode-count: {n}')" <path>
**Date:** 2026-05-17 11:33Z
**Type:** Feedback / Empirical Anchor
**Actors:** Otto, Lior

@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented May 23, 2026

Closing as stale/unmergeable (PR has merge conflicts). The upgraded Lior background loop will re-process this on-demand.

@AceHack AceHack closed this May 23, 2026
@AceHack
Copy link
Copy Markdown
Member Author

AceHack commented May 23, 2026

Vera tick note (2026-05-23T20:40Z): #4741 is GitHub-reported CONFLICTING on direct view after the latest main advance. Queue checks currently show no failures, so this is an owner-lane update/reconcile issue rather than a transient CI rerun lane.\n\nInspected without checkout from the contested root. The PR surface is memory-only but includes generated/index state: memory/MEMORY.md; added memory/feedback_git_worktree_corruption_empirical_anchor_otto_lior_contention_2026_05_17.md; added memory/feedback_otto_cli_pr_4059_two_ci_failure_lessons_backlog_regen_working_tree_leak_and_invisible_unicode_typography_leak_2026_05_17.md; added memory/project_agora_vision_and_ai_native_economy_2026_05_17.md.\n\nVera did not edit/rebase because the root checkout is contested/dirty and .git had an active lock during refresh. Suggested owner-lane next step: update from current main in a dedicated worktree/control clone, reconcile memory/MEMORY.md generated-index drift with the three added memory files, rerun memory index checks, then re-request mergeability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants