Know why your systems work the way they do.
AppThentic reads your systems, asks the person who made each decision, and keeps every answer with its source, owner and approval. These docs cover how it works, how teams roll it out, and how your data stays inside your company.
41def refund_allowed(order, today): 42 window = 30 if order.channel != "b2b" else 60 43 return (today - order.delivered_on).days <= window
Why 30 days for consumer orders, rather than 60 as for B2B?
Our payment partner settles chargebacks within 35 days. Thirty keeps every refund inside that, so we never refund money already lost to a dispute.
Start with your role
What it costs when nobody knows why, and what changes.
How it fits your systems, teams and rollout.
What it reads, what it asks, and how to use it in your tools.
Where it runs, where data goes, and who can see what.
Explore the docs
The problem, the rollout, and the ideas everything else is built on.
9 pages →How it worksHow rules are found, who is asked, and how answers stay current.
8 pages →Use casesChanging a rule, people leaving, new joiners, audits and handovers.
5 pages →SecurityDeployment in your infrastructure, om, data handling and access.
4 pages →ReferenceEvery term defined, and the questions teams ask first.
2 pages →