Repository navigation
docs(planning): F1 conflict-aware-drafts — deterministic contradiction heuristics - #25
Merged
Merged
Conversation
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.
Why
claim draftandaskcurrently ignore contradictions — a draft negating an approved claim is stored silently. F1 makes contradictions explicit and visible (status: conflict) without auto-resolution, closing a poisoning vector for local-first memory.Follows
mcp-v2-protocol-upgradebacklog F1 (ranked #1 by fit with trust model) — deterministic, no LLM/embed/network.What
claim drafttime, scan approved claims in workspace, normalizetitle+body+tags, apply 3 heuristics: negation flip, value swap, status changecontradicts: [{claim_id, heuristic}]in draft frontmatter (preserved via Parse/Render + digest)askreturnsreadyapproved +conflictdrafts side-by-sideStatus
docs/plans/active/conflict-aware-drafts.mdlocked (01M0ZAT3BS4GS7X61V4ZZB9GY9, intake01M0ZAYX27CD3EKSN1CWTPT4XE, lanenormal,status: active)planned:contradiction-detection(01M0ZBG7) — heuristics + metadata + draft wiringconflict-surface(01M0ZBGR, dependscontradiction-detection) — query + ask JSONstatus: conflictdocs/planning/CONFLICT-AWARE-DRAFTS.md(this PR) + harness planChecklist
Phase 1: contradiction-detection
DetectContradictionsinclaim.go+ table testsContradictiontype + frontmattercontradicts+ round-trip + digestClaimStore.Draft/claim draftScanWorkspace/RebuildpreservecontradictsChecks:
go test ./...,go vet,CGO_ENABLED=0 go buildPhase 2: conflict-surface
TrustedQueryreturn drafts with conflict signalaskJSONstatus: "conflict"ready+conflictChecks:
go test -race,make smoke,git diff --checkNext Actions
work full phase contradiction-detection(next)work full phase conflict-surfacecheck full→handoff→ squash-mergeHarness
trusted-single-runtimeabandoned (inventory mismatch, superseded by 0.3.x)mcp-v2-protocol-upgradecompleted and moved todocs/plans/completed/conflict-aware-draftsRelated: #19 (brainstorm merged), mcp-v2
0.3.0done.