{"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":"ftl-reasons-install","text":"ftl-reasons installs via pip or uv. Three options: (1) pip install ftl-reasons, (2) uv tool install ftl-reasons, (3) uvx ftl-reasons <command> to run without installing. Requires Python. Initialize a new database with: reasons init","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"ftl-reasons-is-tms","text":"ftl-reasons implements actual Doyle-style TMS architecture: SL justifications with antecedents and outlists, BFS propagation cascades with restoration, entrenchment-scored dependency-directed backtracking. LLMs fill the problem-solver role Doyle left open","truth_value":"IN","justification_count":2,"dependent_count":6,"challenges":[],"last_reviewed":"2026-05-30T07:02:40","review_result":"pass","source_type":""},{"id":"ftl-reasons-quick-start","text":"Quick start: (1) pip install ftl-reasons, (2) reasons init, (3) reasons add my-belief 'Text of the belief' --source 'where I learned this', (4) reasons add derived-belief 'Conclusion' --sl my-belief to create a justified derivation, (5) reasons retract my-belief to see cascades propagate, (6) reasons assert my-belief to see restoration, (7) reasons explain derived-belief to trace the justification chain.","truth_value":"IN","justification_count":1,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-30T07:02:40","review_result":"invalid","source_type":""},{"id":"ftl-reasons-repo","text":"ftl-reasons source code and issue tracker: https://github.com/benthomasson/ftl-reasons — open source, 211 tests covering propagation, cascades, restoration, nogoods, backtracking, challenge/defend, import/export, staleness detection. Issues and feature requests go here.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"how-humans-use-eem","text":"Humans use EEM by: inspecting beliefs.md for current state, running reasons explain to understand why something is believed, challenging beliefs with reasons challenge, reviewing the network with reasons status, checking staleness with reasons check-stale. The key value is visibility — humans can see and audit what the system knows","truth_value":"IN","justification_count":2,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"invalid","source_type":""},{"id":"how-to-start","text":"To start using EEM: (1) reasons init — creates reasons.db, (2) add premises from observations with reasons add, (3) add justified conclusions with --sl to link dependencies, (4) use reasons derive to find connections, (5) use reasons review-beliefs to audit, (6) retract when evidence changes and let cascades propagate","truth_value":"IN","justification_count":2,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"invalid","source_type":""},{"id":"hybrid-tms","text":"ftl-reasons is a hybrid TMS: symbolic TMS handles structure (justifications, propagation, cascades, backtracking, challenge/defend) while LLMs handle semantic operations (derive generates beliefs, review-beliefs critiques them, contradiction detection finds nogoods)","truth_value":"IN","justification_count":1,"dependent_count":5,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"pass","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":"reasons-db-vs-beliefs-md","text":"Architecture pattern in practice: reasons.db (SQLite) is the primary store for all structural operations — add, retract, derive, review, justify. beliefs.md is an export format for querying — fast, human-readable, grep-able, used as agent context. Both kept in sync via reasons export-markdown.","truth_value":"IN","justification_count":0,"dependent_count":1,"challenges":[],"last_reviewed":null,"review_result":null,"source_type":""},{"id":"reasons-for-maintenance-beliefs-for-queries","text":"Architecture pattern: use reasons database for all structural operations (add, retract, derive, review). Export to beliefs.md for querying (fast, human-readable, grep-able). Keep both in sync via reasons export-markdown","truth_value":"IN","justification_count":2,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"invalid","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":15,"limit":20,"offset":0}