{"results":[{"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":"stale-belief-problem","text":"A belief derived from source material that has since changed may no longer be true. Without staleness detection, the belief network silently diverges from reality — it answers 'is this justified?' correctly for the old state but not the current one","truth_value":"IN","justification_count":2,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"invalid","source_type":""},{"id":"staleness-addresses-frame-problem","text":"check-stale is EEM's answer to the frame problem: instead of tracking everything that didn't change, it detects what did change and flags affected beliefs for re-evaluation. This bounds the maintenance cost to changed sources rather than the entire belief set","truth_value":"IN","justification_count":1,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"pass","source_type":""},{"id":"staleness-detection","text":"Staleness detection tracks whether the source material a belief was derived from has changed. 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","truth_value":"IN","justification_count":2,"dependent_count":3,"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":""},{"id":"staleness-workflow","text":"Staleness workflow: run check-stale after source material changes → review flagged beliefs → retract or update beliefs whose sources invalidate them → let retraction cascades propagate to dependents. This keeps the belief network aligned with current reality","truth_value":"IN","justification_count":1,"dependent_count":0,"challenges":[],"last_reviewed":"2026-05-29T17:30:21","review_result":"pass","source_type":""}],"count":7,"limit":20,"offset":0}