{"results":[{"id":"ai-loop-host-accessor-syntax","text":"AI-loop action functions use the `ftl[\"hostname\"].module()` accessor pattern with `await` for sequential module calls (e.g., `await ftl[\"stargate\"].user(name=\"admin\")`).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ai-loop-modules-are-idempotent","text":"Module calls in AI-loop actions (user, file, copy, lineinfile, service) are idempotent — safe to re-run even if the condition gate fails to prevent unnecessary executions.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ansible-drops-hosts-25-ftl2-handles","text":"Ansible drops hosts as \"unreachable\" at 25+ hosts; FTL2's persistent gate connections handle them without issues.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ansible-migration-with-full-speedup","text":"Teams migrating from Ansible gain FTL2's full compound speed advantage (3-21x: in-process execution, gate caching, default parallelism) while retaining access to their existing module ecosystem through FQCN dot-notation and Ansible-compatible bundled execution — migration preserves investment in existing modules without sacrificing performance.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"autonomous-self-healing-infrastructure-apps","text":"FTL2 enables autonomous self-healing infrastructure applications: durable AI-loop remediation (observe/condition/action with fail-open, persistent state for crash recovery) operates within a full application framework (long-lived daemons, real-time monitoring via htop, event/gate/SSH pipeline).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"compiled-deps-cannot-bundle-in-gate-pyz","text":"Compiled dependencies (C extensions like psutil) cannot be bundled in the gate `.pyz` package; they must be pre-installed on the remote host via `dnf`/`apt`. Pure-Python deps go in the `.pyz` bundle.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"comprehensive-operational-observability","text":"FTL2 provides comprehensive operational observability across automation and infrastructure: the event streaming subsystem captures structured module execution data (progress/log/status events always in results), while ftl2-htop delivers real-time system metrics (CPU, memory, network) via SSH-gate-psutil pipeline — together covering both application-level task tracking and system-level resource monitoring.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"deployment-secrets-are-manual","text":"In FTL2 deployments (e.g., ftl2-stargate), secrets such as Google OAuth credentials are entered interactively at startup and are not handled by the deployment automation.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"diverse-application-hosting-platform","text":"FTL2 serves as a hosting platform for diverse application types: long-lived daemon contexts with event/gate/SSH infrastructure support game server lifecycle management (servercraft with watchdog, TUI, backup), while the same provisioning pipeline supports hot-reload web applications (catbeez arcade) where publishing is purely file upload with no restart.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"edge-to-application-security-perimeter","text":"FTL2 deployments can implement a layered edge-to-application security perimeter. In observed patterns, Cloudflare DNS-only mode delegates TLS to Caddy (enabling Let's Encrypt ACME), Caddy terminates HTTPS and reverse-proxies to a localhost-only application, firewalld's drop zone silently discards uninvited traffic, SSH is restricted to source IP ranges, and SELinux enforces network connect policies. This pattern has been documented in catbeez deployments and the Cloudflare+Caddy TLS approach is used consistently across FTL2 deployments.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"end-to-end-remote-execution-optimization","text":"FTL2 optimizes remote execution end-to-end from connection to result: the SSH layer pools and reuses connections via asyncssh for async non-blocking I/O, while the gate layer pre-builds modules into cached zipapps that communicate via length-prefixed JSON — eliminating overhead at both the transport and module delivery layers.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"fast-resilient-fleet-execution","text":"FTL2 fleet operations are simultaneously fast and resilient: SSH connection pooling with async I/O and gate caching minimize per-host overhead, default parallelism bounds execution to the slowest host, and failure isolation ensures fleet execution continues and collects structured errors even when individual hosts fail.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl-modules-sent-by-name-ansible-as-bundles","text":"FTL modules are sent to the gate by name (gate already has them); Ansible modules are sent as bundles.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-application-framework-beyond-automation","text":"FTL2 serves as a full application framework beyond one-shot automation: long-lived daemon contexts support persistent services, the event/gate/SSH pipeline enables real-time TUIs, and persistent state orchestrates multi-run workflows — demonstrated by servercraft (game lifecycle manager with watchdog and TUI dashboard) and ftl2-htop (real-time infrastructure monitoring).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-full-performance-stack","text":"FTL2's speed advantage derives from three independent optimization sources: in-process native module execution (up to 250x per-call speedup for native modules), gate-based remote delivery (pre-built zipapps cached on remote hosts, JSON-only parameter protocol), and default parallel host targeting (asyncio.gather fan-out, total time bounded by slowest host).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-gate-zipapp-built-once-shared","text":"The gate zipapp is built once and uploaded to all targeted hosts, not rebuilt per host.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-htop-data-flow-pipeline","text":"ftl2-htop data flow: SSH connection → gate process → SystemMonitor (psutil) → SystemMetrics events → SSH channel → TUI rendering.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-htop-debug-prints-raw-events","text":"The `--debug` flag in ftl2-htop bypasses the TUI and prints raw gate events to stderr, useful for understanding the event protocol.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-htop-only-remote-dep-psutil","text":"ftl2-htop requires only `python3-psutil` installed on remote hosts; FTL2's gate handles everything else via SSH.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"ftl2-htop-real-time-monitoring-stack","text":"ftl2-htop is a complete real-time infrastructure monitoring stack: SSH→gate→psutil data pipeline, dual-thread architecture (Textual UI + FTL2 daemon), 30-sample sparkline history, group-based host filtering, and browser accessibility via textual-serve — all reusing standard FTL2 inventory and gate subsystems.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null}],"count":52,"limit":20,"offset":0}