{"results":[{"id":"beliefs-cli-vs-reasons-cli","text":"Two CLIs at different levels: beliefs CLI is a structured markdown KB with provenance and manual maintenance (simple, flat). reasons CLI (ftl-reasons) is a full TMS with automatic propagation, cascades, backtracking, and LLM-driven operations (powerful, dependency-aware). Use beliefs for independent facts, reasons for justified conclusions with dependency chains","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"eem-cli-interface","text":"The reasons CLI provides: reasons init (create database), reasons add (add beliefs with --sl for justifications, --source for provenance), reasons retract (mark OUT with cascade), reasons assert (mark IN with restoration), reasons search (semantic search), reasons show (full details), reasons explain (justification trace), reasons derive (generate new beliefs), reasons review-beliefs (audit), reasons challenge/defend (dialectical argumentation), reasons check-stale (source change detection), reasons nogood (record contradictions), reasons export-markdown (beliefs.md output), reasons compact (token-budgeted summary).","truth_value":"IN","justification_count":0,"dependent_count":4,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"ftl-reasons-implementation","text":"ftl-reasons implements: SL justifications with antecedents and outlists, BFS propagation cascades with restoration, entrenchment-scored dependency-directed backtracking, challenge/defend dialectical argumentation (challenge→OUT, defend neutralizes, multi-level chains), LLM-driven derive, review-beliefs, and contradiction detection. SQLite-backed, Python CLI.","truth_value":"IN","justification_count":0,"dependent_count":2,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"http-endpoint-access","text":"EEM is accessible via a single HTTP GET at https://expert.ftl2.com/public/eem-expert/beliefs — no Python library, no CLI installation, no database copy, no setup. Three formats available: HTML (human-browsable), Markdown (agent-readable), JSON (machine-readable). Any agent that can fetch a URL can consume justified beliefs immediately.","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"import-agent-implementation","text":"import-agent command imports another agent's beliefs with SL justifications including agent:active as antecedent. Node is IN iff agent is active AND original belief is justified. Implemented in ftl-reasons CLI.","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"no-code-adoption","text":"Three levels of EEM integration: (1) HTTP GET — just a URL, read beliefs as context, no installation. (2) CLI (ftl-reasons) — search, show, explain, pip install. (3) Full pipeline (expert-build) — build, derive, review, maintain. The HTTP level is the on-ramp: try EEM in 30 seconds, see if it helps, no commitment.","truth_value":"IN","justification_count":1,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"staleness-implementation","text":"check-stale implementation: each belief records a source path and SHA-256 hash at creation time. check-stale compares stored hashes against current file content and flags any IN belief whose source has changed. Implemented in ftl-reasons CLI.","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""}],"count":7,"limit":20,"offset":0}