Repository navigation
Describe the write-only prune in the paper - #38
Merged
Merged
Conversation
Apply the chore/prune-write-only removals (PR #37): the dynamic threshold controller and its hysteresis, the spike bypass (now CheckCapacityFlush), the 6D mood integrator, the stored source-reliability metadata and per-memory context, and the dead config flags are described as removed. State what the composite score still drives (the peak embedding, working memory admission, uncertainty) and that it is not a write gate, keep the RLS blender, composite score, signal history and emotion projection as live with their packet effects, and describe BiasMid as the clamped quadratic remap it is.
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.
Summary
This follow-up to #36 applies the final
chore/prune-write-onlyremoval list (#37) to the paper. #36 merged before these two commits were pushed, so they come here. It is docs only.Merge after #37. The paper now describes the pruned engine.
What changed
CheckSpikeBypassis nowCheckCapacityFlush, which keeps only the capacity cap;memories.ambient_mood(migration 57);source_reliability,source_contradiction_count,source_last_verified_tsand the per-memory context column (migration 56).c_tstays in memory for boundary detection;affect_retrieval,reinforcement_enabledandsequential_edges_enabledflags;Context::Memoryfields.ComputeCompositeScore(Jaccard 0.08);UpdateSignalHistory, formerlyUpdateThreshold(Jaccard 0.53). It keeps the score window that feeds uncertainty and thedt_emacadence that feeds boundary gaps and pacing.m_ratestays inUpdateRateStatefor the maintenance hints;UpdateSensitivity(171/1986 differ). It feeds the composite score and the interrupt gate.e_peak, which goes into the stored representative embedding and serves as the fallback topic anchor. It also drives working-memory admission throughS_windowand the score-variance term of uncertainty. It is never called a write gate.force_write (Durable retention) ∨ should_flush, and the capacity flush is part ofshould_flush.BiasMid. It is described as the clamped quadratic remap x' = clamp(x − 4b·x(1−x), 0, 1), used at about 300 call sites and not foldable into intercepts. The retrieval biases (−0.175 / 0.325 / −0.25) are listed.PRUNE:markers from Rewrite the paper around the v5 engine and fix its contradictions #36 are resolved.Test plan
QUARTO_DISABLE_GIT=1 QUARTO_DISABLE_GITHUB=1 quarto render docs/papergives no warnings and 0 unresolved cross-references.origin/chore/prune-write-only:CoreStagecomposition insrc/cortext.cpp;capacity_flush.cpp,signal_history.cppandaccumulator_scores.cpp;e_peakuse inboundary.cppandwrite_gate.cpp;InitializeSensitivityPriorsfields.