FieldRules is the rule library your humans already confirmed. IF / THEN / BECAUSE, attributed and versioned. Your agent calls it the same way a PM or an engineer would — and inherits the same reasoning layer.
We shipped the agent. It handles the easy 60%. The other 40% is exactly the stuff our lead ops person used to decide — and now it’s being decided by the model’s defaults.
Each rule is a structured record. IF and THEN describe the operational action. BECAUSE carries the reasoning — in the author’s own words.
Every field is either authored by a named person or derived from their confirmation. The rule is versioned. The author stays on the record. The BECAUSE is never machine-generated.
Your agent reads this record the same way a human queries it. When the library can’t match, the gap is structured context — not a 404 — and it routes back to the human who’d carry that judgment.
because_clause is null until a domain expert authors it.
{
"rule_id": "82a96174-8080-4a60-bd45-af81cd12bf68",
"revision_id": 3,
"when_clause": "enterprise customer has completed kickoff AND first activity data upload spans ≥2 business units",
"then_clause": "schedule a Week 2 data-quality review before any calculation is surfaced in the customer-facing dashboard",
"because_clause": "Mixed-BU uploads in week one routinely mis-map activity categories. Catching it before the first readout is what preserves methodology defensibility — and the customer's trust.",
"domain": "onboarding",
"scope": "workflow",
"hedge_tag": "usually",
"status": "confirmed",
"author_id": "jordan.chen@acme.co",
"confirmed_at": "2026-04-21T09:48:47Z"
}
get_rule or search_rules for the cases that apply, and the BECAUSE travels with the IF/THEN. If MCP isn’t your path, the same records are reachable over a plain JSON endpoint — tool call or context injection, your choice.Documentation produces compliance. FieldRules elicits reasoning — because it asks “what would go wrong if this rule didn't exist?” instead of “why does this rule exist?”
That single design choice is the difference between an agent that covers the easy cases and an agent that handles the ones that would have gone to your best human.
FieldRules is not an agent, not an agent framework, and not a tool-calling runtime. It sits upstream of all three — the human-authored reasoning layer that your agent, your framework, and your runtime all call the same way.
MCP is the canonical caller — list the resources, call what applies, the BECAUSE travels with the record. A plain JSON endpoint is there if you’re not on MCP yet. Same library. Same reasoning. Different transport.
We're onboarding teams with an agent in production or in pilot. If that's you, let's talk about the integration shape. No deck. No demo-ware.
We start with a conversation.