Remodel elicitation_backlog into elicitation_gaps obligation register#197
Draft
lunelson wants to merge 3 commits into
Draft
Remodel elicitation_backlog into elicitation_gaps obligation register#197lunelson wants to merge 3 commits into
lunelson wants to merge 3 commits into
Conversation
Replace the FE-823 question-instance / open|closed backlog with the D65-L typed coverage-obligation model: ElicitationGap carries name + rationale, the presence|field|coverage|manual predicate union, importance + derived coverage, and a disposition enum. Seed the 8-typology grounding catalog at createSpec, add createElicitationGap / setElicitationGapDisposition mutations through CommandExecutor, and derive presence coverage/answered live from the graph at read-back (anti-shadowing: no stored structural state). Regenerate migration + Drizzle snapshot; reconcile SPEC/PLAN and graph/db topology READMEs. field/coverage derivation and manual satisficiency remain downstream.
Introduce the D74-L gate (src/projections/session/capability-readiness.ts): an explicit capability -> relevant-gaps map and evaluateCapabilityReadiness returning proceed / proceed_low_epistemic / negotiate(EstablishmentOffer), driven by live gap coverage with no stored readiness grade. Read-only judgment; never refuses outright (I31-L). Coexists with the existing grade gating for now. Reconcile SPEC/PLAN and projections README. Deferred follow-ons (capability-readiness frontier): readiness-estimate projection, MIN_GRADE consumer rewire, stored-grade deletion, and chrome.phase/chatMode removal.
This was referenced Jun 10, 2026
Contributor
Author
This was referenced Jun 10, 2026
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.
Remodel elicitation_backlog into elicitation_gaps obligation register
Replace the FE-823 question-instance / open|closed backlog with the D65-L
typed coverage-obligation model: ElicitationGap carries name + rationale,
the presence|field|coverage|manual predicate union, importance + derived
coverage, and a disposition enum. Seed the 8-typology grounding catalog at
createSpec, add createElicitationGap / setElicitationGapDisposition
mutations through CommandExecutor, and derive presence coverage/answered
live from the graph at read-back (anti-shadowing: no stored structural
state). Regenerate migration + Drizzle snapshot; reconcile SPEC/PLAN and
graph/db topology READMEs. field/coverage derivation and manual
satisficiency remain downstream.
Add JIT capability-readiness gate over elicitation gaps
Introduce the D74-L gate (src/projections/session/capability-readiness.ts):
an explicit capability -> relevant-gaps map and evaluateCapabilityReadiness
returning proceed / proceed_low_epistemic / negotiate(EstablishmentOffer),
driven by live gap coverage with no stored readiness grade. Read-only
judgment; never refuses outright (I31-L). Coexists with the existing grade
gating for now. Reconcile SPEC/PLAN and projections README.
Deferred follow-ons (capability-readiness frontier): readiness-estimate
projection, MIN_GRADE consumer rewire, stored-grade deletion, and
chrome.phase/chatMode removal.
question catalog re-discussion