ParableAgent Operating Rules
The Laws That Govern Deterministic Parable Analysis
Data Integrity Rules
All parable data must originate from the canonical Gospels (Matthew, Mark, Luke, John). No apocryphal or extra-biblical sources.
The system SHALL NOT generate, invent, or hallucinate parables, references, or theological interpretations not present in the database.
The parable database contains exactly 39 entries. This number is immutable during operation.
Bible references must be exact (Book Chapter:Verse format). No approximate or ranged references.
Query Processing Rules
Identical queries MUST produce identical results. No randomness in query resolution (except for explicit random_parable).
Theme matching uses defined synonym lists. Unknown themes return empty results, not guesses.
All text matching is case-insensitive. "MERCY" = "mercy" = "Mercy".
Keyword searches support partial matching. "sow" matches "sower" and "sown".
Response Rules
All responses follow predefined schemas. No free-form text generation for data fields.
Retrieval operations return all matching results, not samples or subsets (unless pagination requested).
When no results match, return explicit "not found" - never empty responses without explanation.
Every result includes its source reference. No unsourced claims.
Tool Interaction Rules
Tools are stateless. No tool call affects the outcome of any other tool call.
Tool outputs can be used as inputs to other tools. The system supports tool chaining.
All standard tools are read-only. No tool modifies the underlying parable database.
List results are always sorted consistently (alphabetically by default, or by specified criterion).
Theme Classification Rules
Exactly 14 themes exist: Mercy, Forgiveness, Kingdom, Prayer, Faithfulness, Repentance, Stewardship, Judgment, Love, Humility, Watchfulness, Grace, Obedience, Righteousness.
A parable may belong to multiple themes. The Good Samaritan is both "Mercy" and "Love".
Primary themes take precedence in default sorting. Secondary themes are listed afterward.
Error Handling Rules
Invalid inputs receive helpful error messages, not crashes or undefined behavior.
All inputs are validated before processing. Invalid book names, malformed references, etc. are rejected with explanation.
Rule Count: 21 Rules
These rules implement the Tau-Bench Principles and ensure reliable, predictable behavior!