How Pathrule proves hard claims
The technical contracts behind Pathrule knowledge quality: how knowledge enters, what waits for a person, how relevance bounds delivery, and how non-delivery is recorded.
Pathrule's technical standard is simple: a product claim needs a bounded input, defined behavior when evidence is missing, and a result that can be tested independently.
This page collects those contracts for how knowledge enters Pathrule, how it is selected and how it is delivered. A Remote MCP connection has a different delivery boundary: it installs no hooks, so knowledge arrives when the agent calls Pathrule's tools.
Knowledge quality has several gates
Pathrule does not put every markdown file into every prompt. Knowledge moves through independent controls:
-
Selective discovery. When your agent runs the project scan, active instruction files, their import chain, tool rules and decision records are distinguished from general documentation. Broad documentation is offered for review instead of being imported as live instruction by default.
-
Review before persistence, with the exceptions named. Inferred knowledge waits for a person: project scan candidates are added only when approved, Team Intelligence suggestions reach agents only once a person verifies them, fixes for stale knowledge change nothing until a refresh task is resolved, and an executable constraint an agent proposes for a rule is stored as a proposal and is not enforced until a person approves it. An assistant's own writes go through Pathrule's write tools and are marked as an assistant's, versioned and reversible. Project learning findings are shared without a review step, as advice to verify and never as rules. Two things are written without asking, only on a cloud workspace and only the first time an agent asks for deep context: the file path pairs read from recent git history that seed which files change together, and short technology memories at the workspace root recognised from file names. No file contents, diffs or commit messages are read for either. See How knowledge compounds.
-
Path ownership. An entry belongs to the narrowest workspace path that owns it. Work outside that path does not receive it merely because it exists in the same repository.
-
Relevance to the request. An entry still has to qualify for the current request, every time. Eligibility and order are decided separately and never trade places: one decides whether an entry is eligible, the other decides the order among those already eligible. Learning affects only the order. It can move a proven memory from fourth place to first; it cannot move anything from ineligible to present. Volume is bounded too: delivery fits a per-prompt budget, so the amount delivered does not grow with the size of the knowledge base.
This is why disciplined authoring is not a precondition for a quiet prompt. A vague or badly written entry does not become noise; it simply never qualifies for a request it has nothing to do with. The visible cost of a weak memory is that it does not show up.
-
Measured delivery and use. Pathrule records what it delivered and what the assistant consulted. Derived layers report when they last received data, so a quiet system can be distinguished from a disconnected one.
The same discipline applies to why an entry was not delivered. "Nothing qualified", "the ranking call timed out", "the response was malformed" and "there was nothing to rank" are recorded as distinct outcomes rather than one word, because they are different situations with different fixes. A slow moment is reported as one, so it is never mistaken for an empty knowledge base.
When relevant knowledge does not fit the budget, or its body is not already on the machine, it is offered by title rather than dropped, so the assistant can fetch it deliberately. Discarding a correct answer for being inconveniently placed is the outcome this is designed to avoid.
-
Reviewable maintenance. Knowledge an agent finds stale, contradicted by the code, duplicated or unclear is raised for review as a refresh task, and nothing is changed until that task is resolved. Writes are versioned, conflicts are explicit and deletion is reversible.
These gates turn shared knowledge into a small, inspectable operating system for a repository. They are why a project can compound decisions without turning its entire documentation archive into default context. See How knowledge compounds and Suggestions and self-audit.
Dated verification
On August 23, 2026, focused automated checks for these contracts passed in the main Pathrule product repository, among them knowledge discovery, import ordering and the exclusion of noisy sources.
PathruleBench is separately reproducible at github.com/pathrule/benchmark: fixtures, scenarios, hidden checks, the harness and every chain with each turn's token usage. How we measure publishes its method, its numbers and the conditions where the gap closes. Measured results describe the setups they were measured on; they are not guarantees for your repository.
A useful evaluation rule
For any Pathrule claim, ask three questions:
- What evidence enters the decision?
- What happens when that evidence is missing or ambiguous?
- Which result is allowed to change or block the work?
The contracts above answer all three. That is the difference between a feature description and an engineering claim.