Build(deps-dev): Bump @typescript-eslint/parser from 8.29.1 to 8.36.0#89
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Build(deps-dev): Bump @typescript-eslint/parser from 8.29.1 to 8.36.0#89dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: "@typescript-eslint/parser" dependency-version: 8.36.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
The |
Contributor
Author
|
Superseded by #90. |
joelteply
added a commit
that referenced
this pull request
May 31, 2026
…strate (L1-L5) Crystallizes the design discussion from 2026-05-31 around persona cognition memory architecture. Captures the unified frame the substrate has been growing toward. Five tiers analogous to the foundry's existing L1-L5 genome cache: - L1 RAG working memory (raw, model context window) - L2 engram cache (in-memory, compressed) - L3 longterm.db (persisted semantic engrams) - L4 forge (local LoRA adapter cache) - L5 grid (distributed gene pool) Lossy compression only at L1→L2 boundary. Working memory is verbatim; older data gets outlined-and-cached when it ages out. One always-on outline-and-cache tick per persona, yielding on CNS context-switch per RTOS-brain doctrine. Per-activity L1, shared L2+ — Algorithm 1's focus/periphery split generalized to per-activity instantiation. Recent-universal floor in periphery pool (top N msgs across all activities, N budgeted by model context size) guarantees cross-activity awareness without severance. Forgetting is intrinsic to L1 budget. Smaller models forget more in the moment but accumulate engrams at the same rate as bigger ones — long-term knowledge is model-size-independent. Novelty detection via embedding-space distance + magnitude: the hotdogs-at-a-tech-meeting canonical example shows how high-distance outliers get protected-until-ms grace windows and earn long-term retention via recall hits. Activity context save/restore via existing EngramKind::SelfReflection meta-engrams; no separate sidecar needed. The engram graph is the storage; SelfReflection is the type marker. Implementation slice scoped: Engram metadata fields (salience, access_count, last_accessed_ms, protected_until_ms) on Engram or RecallMetadata sidecar; outline-and-cache tick; L1 budgeter; decay + consolidation policies; cross-activity integration test. Related tasks: #88 (disk pressure as substrate concern), #89 (this design + implementation scoping). References: COGNITION-ALGORITHMS.md (existing 7 algorithms), BRAIN-REGIONS-SUBSTRATE.md (region trait, sleep-region cadence), GENOME-FOUNDRY-SENTINEL.md (parallel L1-L5 framework), memories source-drain-is-the-universal-pattern, RTOS-brain-no-region-on- hot-path, local-worktree-is-temp-dir. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)