fix(telos): read Context Filter from TELOS.md instead of a hardcoded value - #1808
Open
0bsolescence wants to merge 1 commit into
Open
fix(telos): read Context Filter from TELOS.md instead of a hardcoded value#18080bsolescence wants to merge 1 commit into
0bsolescence wants to merge 1 commit into
Conversation
…value
GenerateTelosSummary emitted a hardcoded Context Filter string into
PRINCIPAL_TELOS.md, which is @-imported at every session start. The literal
carried one specific person's values ('human flourishing, Human 3.0 transition,
...'), so every install silently overwrote the user's own Context Filter with
someone else's, no matter what TELOS.md said.
Reads the '## Context Filter' section from unified TELOS.md, falling back to a
neutral prompt when absent.
Verified: with the user's own filter in TELOS.md, PRINCIPAL_TELOS.md now renders
that filter rather than the literal.
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
1 participant
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.
Problem
GenerateTelosSummary.tsemits a hardcoded string as the Context Filter section ofPRINCIPAL_TELOS.md:PRINCIPAL_TELOS.mdis@-imported at every session start, and the Context Filter is the field that steers prioritisation. Because the literal is unconditional, every install renders the same filter regardless of what the user wrote in their ownTELOS.md, silently replacing their steering criteria with someone else's.Fix
Read the
## Context Filtersection from unifiedTELOS.md, falling back to a neutral prompt when the section is absent.Verification
On a live 7.28.3 install with a populated Context Filter,
PRINCIPAL_TELOS.mdnow renders the user's own text. With the section absent, it renders the fallback prompt rather than an unrelated value.Scope: one function plus its call site. No behaviour change for any other section.
Found and fixed with AI assistance while installing 7.28.3; verified on a live install rather than by inspection.