Asking AppThentic
Ask om why a rule exists, who owns it, or what depends on it, and get an answer with its sources.
Anyone with access can ask om a question in plain language and get an answer built from Organization Memory, with every source cited.
Where to ask
- In chat: in AppThentic, Slack or Microsoft Teams.
- By phone: leaders call om, and om calls back with a confirmed answer. See Calling om.
- From an AI coding tool, over MCP. See AI coding tools.
Ask anything
Ask the way you would ask a colleague. There is no syntax to learn and no list of allowed questions. For example:
- “Why do we hold payouts above ₹50,000 for a manual check?”
- “Who decided the 24-hour hold on seller payouts, and is it still needed?”
- “What breaks if we extend refunds to 45 days?”
- “Which rules in payouts have no owner?”
- “What changed in refund rules this quarter, and who approved it?”
What an answer contains
- The answer in a few sentences.
- The status of each rule it relies on: Approved, Inferred, Stale and so on.
- The sources: the owner’s answer, the PR, the ticket, the line of code.
- What is unknown, said plainly, instead of filled in.
The same memory, explained for each person
A developer asking why refunds stop at 30 days gets the service, the code path and the config that enforce it. A product manager asking the same thing gets the business rule, the customer impact and the decision behind it. The knowledge is the same; the explanation fits the person.
Who sees what
Authorization happens before retrieval. AppThentic decides what a person may see first, and only that reaches om. Instructions to the model shape how an answer is explained; they are never what keeps restricted information out.
Admins assign who sees what. See Access and audit trail.