{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "isaachinman-encephalon--resolve-knowledge-conflicts-after-merge",
 "repo": "isaachinman/encephalon",
 "repo_url": "https://github.com/isaachinman/encephalon",
 "repo_slug": "isaachinman-encephalon",
 "title": "Resolve conflicting knowledge records after a merge",
 "page_title": "How to resolve conflicting knowledge records after a merge with Encephalon",
 "summary": "Validate merged records and add one record that supersedes every conflicting head.",
 "who": "A developer merging a branch where two people recorded different decisions for the same subject.",
 "problem": "Conflicting active heads make reads return both answers, and deleting history to fix it is not allowed.",
 "outcome": "A resolving record supersedes all conflicting heads, and validation passes again.",
 "steps": [
  "Merge the other branch with your usual Git workflow. (inferred, check the README)",
  "Run `npx --no-install encephalon validate` to list the conflicting active heads.",
  "Run `npx --no-install encephalon add --id <resolved-id> --kind <kind> --subject <subject> --source agent --supersedes <head-a> --supersedes <head-b> --data '<resolved summary as JSON>' --text '<search terms>'`, repeating --supersedes for each conflicting head. (inferred, check the README)",
  "Run `npx --no-install encephalon validate` again to confirm no conflicts remain."
 ],
 "agent_prompt": "In the repository <repo-path>, after a merge, run validate, then add one resolving record for subject <subject> that supersedes all conflicting heads. Expected output: validation errors before the fix and a clean validation after it. Verify that no old record file was deleted or edited.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Until a conflict is resolved, reads return every conflicting head as active, and history must never be deleted to repair it.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "Node.js 24.22.1 or later on Linux, macOS or Windows",
  "A Git repository, with a package-manager layout that exposes node_modules/encephalon at the repository root",
  "npm to install the package",
  "A terminal or agent with shell access to the repository"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/isaachinman-encephalon/resolve-knowledge-conflicts-after-merge/",
 "md": "https://dedupedai.com/use-cases/isaachinman-encephalon/resolve-knowledge-conflicts-after-merge/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/isaachinman-encephalon--resolve-knowledge-conflicts-after-merge.json",
 "api_version": "v1"
}