Stave is the Substrate: Five Reasoning Paradigms on One Snapshot A developer behind Stave, a cloud security tool whose catalog of over 3,000 controls is written in YAML and CEL, ran a trial in which five reasoning engines — Z3 (SMT), Soufflé (Datalog), Clingo (answer-set programming), Prolog, and PRISM (probabilistic model checking) — produced correct answers from Stave's exports without reading Stave's source code. Three of the five passed on the first attempt; the Clingo and Prolog runs failed, were traced to a wrong predicate name and a golden-transcription error respectively, and passed after fixes, with results committed to reasoning-specs/TRIAL-RESULTS.md and re-run by a fresh sub-agent. The developer frames the result as a category split: AWS Compliance Mod is scoped to per-resource checks, while Stave acts as a substrate any reasoning paradigm can target. ✓ Human-authored analysis; AI used for formatting and proofreading. AWS Compliance Mod is the canonical implementation of one reasoning paradigm per-resource SQL benchmarks against framework requirements. Stave is the substrate. Five reasoning engines: SMT, Datalog, answer-set programming, Prolog, probabilistic model checking produce correct answers from Stave's exports without reading a line of Stave's source code. Previous article Stave and the AWS Compliance Mod: why we ship both https://dev.to/bala paranj 059d338e44e7e/stave-and-the-aws-compliance-mod-why-we-ship-both-5kp , makes the per-feature complementarity argument: compound chain detection by Stave covers the compositional risk class that per-resource framework checks AWS Compliance Mod can't see by construction. That framing is still correct. Run both; they cover orthogonal territory. This article makes the bigger claim. The complementarity isn't just "we have compound detection; they have framework coverage." It's "we ship a contract that arbitrary reasoning engines can target; they ship one specific reasoning paradigm." That's a category split. The proof is a trial that already happened, with results committed to the repo, and a fresh-sub-agent re-run that survives the "but maybe the spec author leaked the answer" objection. Every cloud security tool can be located on the reasoning-paradigm × content-coverage grid: | Reasoning paradigm | Content shape | |---|---| | Per-resource attribute checks | "Is this bucket encrypted? Is this role MFA-enforced?" | | Compound / chain composition | "Do these three settings combine into a Capital One path?" | | Transitive closure Datalog | "What is the complete blast radius from this principal?" | | SMT satisfiability | "Does there exist any assignment that violates this invariant? Show me the witness or prove none exists." | | Probabilistic model checking | "Given the observed protection factors, what's the probability of successful exploitation?" | | Proof-tree derivation Prolog | "Trace the proof chain — root, edges, leaves — for this conclusion." | | Game-theoretic adversary modeling | "What's the optimal attacker move given the defender's posture?" | turbot/steampipe-mod-aws-compliance occupies one row in that grid with per-resource attribute checks and covers it exhaustively: 540+ controls across 16+ frameworks. Mature, auditor-recognized, the right tool for "am I CIS-compliant right now?" Stave occupies the row dimension as a substrate: any reasoning paradigm with an engine-agnostic input format can target the same Stave exports. The catalog over 3,000 controls today is written in YAML + CEL; the exports project into SMT-LIB, JSONL, RDF / JSON-LD, and the engine-native formats those paradigms consume. The category split: AWS Compliance Mod is row-scoped. Stave is dimension-scoped. reasoning-specs/TRIAL-RESULTS.md in the Stave repo records the first-round trial. Five reasoning specs and engines. Each spec carries: The trial: hand the spec + input fixture + export-schema documentation to an agent. Withhold the original implementation code and the golden answer. The agent must produce output that matches the golden via the spec's validation rules. Round 1 same-session results: | | Engine | Outcome | |---|---|---| | 1 | Z3 SMT-LIB | PASS — exact match on verdict + witness | | 2 | Soufflé Datalog | PASS — anonymous reachable count: 12 byte-identical | | 3 | Clingo ASP | FAIL → fixed → PASS spec bug: mfa enforced should have been has mfa enforced | | 4 | Prolog | FAIL → fixed → PASS golden transcription bug: spec said 6 proofs, actual file has 12 | | 5 | PRISM probabilistic | PASS — step probabilities exact, aggregate within ±0.005 | Three of five passed straight. Two failures caught real defects and the trial harness distinguished the two failure types. Clingo's failure was the spec author's error wrong predicate name . Prolog's failure was the inventory author's error mis-counted the golden . Same trial format, two distinct bug categories, both surfaced precisely. Trial format did its job. The spec is wrong when the agent can't derive the engine's output from the spec; the golden is wrong when the agent's output matches the engine's actual output but not the golden. The Round 1 trial had one disclosure: the spec author and the trial agent were the same session. Even with the answer withheld from the spec, contextual leak was possible "the author would unconsciously phrase the spec to produce the right answer they already know" . Round 2 was a fully-blind re-run. Two of the five trials Prolog + Clingo had spec changes after Round 1. The Round 2 agent was a fresh sub-agent with no access to: spec.yaml which carried the answer in a comment golden.yaml the answer key examples/