02 · Test before teaching
Preview the pattern, then decide whether it should persist.
A dry run shows what a rule would catch. Batch application groups work by the winning rule, fills only blank fields, and rechecks every match at write time.
Rules, knowledge & playbooks
Teach Zeno once. Keep the decision.
A useful system should make the twentieth familiar transaction easier than the first. Zeno separates exact rules from judgment-bearing knowledge, turns procedures into playbooks, and keeps every retained instruction inspectable and owned by the organization.
DeterministicExact mappings run without AI and give the same answer every time.
Human-confirmedJudgment enters future context only after acceptance.
Shared engineThe same rule can prepare bank-feed items and parsed documents.
Institutional memory
What the organization learns should outlive the session.
Rules run deterministically at ingest. Confirmed knowledge supplies relevant judgment only where anchored. Playbooks preserve multi-step procedures. Work logs and audit trails show how those instructions affected real work.
03 · One matcher, two directions
The same decision reaches documents and bank activity.
A vendor mapping is not relearned separately by the parser and bank queue. Rules fire at both entry points; nuanced quirks are retrieved as anchored knowledge only when relevant.
04 · Provenance survives
Know whether a person, rule, or agent caused the result.
Rule-provided values retain their source until changed. Work logs describe the reason for a job, and the audit log preserves the exact writes and actor behind resulting records.
Direct captures from the public Parkview Property Management sandbox on August 22, 2026. Sample names and financial data are synthetic; the product interface has not been recreated.
Three layers, three jobs
Do not ask AI to improvise what the company knows exactly.
Keep cheap, certain decisions deterministic and reserve model judgment for the places that need it.
01
Observe a correction
Resolve a vendor, category, route, document type, or procedure.
02
Choose the layer
Use a rule for exact mapping, knowledge for judgment, or a playbook for process.
03
Test the scope
Dry-run patterns and anchor knowledge to the records it concerns.
04
Confirm retention
Knowledge and playbooks remain drafts until a human accepts them.
05
Apply with provenance
Run rules at ingest and retrieve only bounded, relevant context.
06
Correct without mystery
Edit, disable, export, or delete retained instructions.
Owned by the organization
Institutional memory should be a controlled asset, not a black box.
Exact things stay exact
Deterministic mappings run without model cost or interpretive variation.
Judgment stays reviewable
Knowledge is plain language, relevant-record anchored, and human-confirmed.
Learning can be undone
The organization can inspect, edit, disable, export, and delete what it owns.
The rest of the system
Explore the platform →