Asking the right questions
What om asks owners, how often, and why it asks so few questions.
The scarce resource is not storage or compute. It is the attention of the people who decided. AppThentic is designed to ask them as little as possible, and to make every question worth answering.
Ask less
Before asking anything, om uses what already exists: PR descriptions, commit messages, tickets, docs and earlier answers. It then ranks the remaining gaps by value: how often the rule changes, how much money or risk it touches, and how many people depend on it. Owners see the highest-value questions first, a few at a time.
Ask better
Questions are specific and anchored in what the system really does.
Why 30 days for consumer orders, rather than 60 as for B2B?
Where does this rule stop applying?
What happened the last time this limit was changed?
A contrastive question (“why 30 rather than 60?”) gets a real reason. A generic one (“please document the refund policy”) gets a paragraph nobody reads.
What om does not do
- It does not send long questionnaires.
- It does not offer a menu of reasons to pick from. A busy person picks one anyway, and an invented reason gets recorded as approved.
- It does not reward volume with points or badges.
“Still checking” is an answer
Owners can say they need to check. The rule stays Unknown until they answer, and is never guessed into Approved.