The loop

Finding the owner

How AppThentic works out who can explain a rule, and follows answers to the person who actually knows.

The person who wrote a rule is not always the person who decided it, and the most senior person is not always the one who knows. AppThentic looks for whoever can actually explain it.

Signals

  • Who wrote, reviewed and last changed the code behind the rule.
  • Who is named in the tickets, documents and conversations around it.
  • What your organization tells AppThentic about its members: their projects and roles.
  • What people say in earlier answers.

Following the answer

When the person asked doesn’t know, their answer still counts. AppThentic records it exactly as given.

“I don’t know. Priya told me this came from the partner agreement.”

AppThentic does not turn that into a fact. It records that this person does not know the original reason, and that they attribute the rule to Priya and the partner agreement. Then it asks Priya.

It keeps following until it reaches someone who can answer, or it records the reason as Unknown, along with every step it took.

Anyone asked can say “not mine” and name someone else. Every change of owner is recorded with who made it and when.

More than one owner

No single person owns every flow. A refund rule might be explained by Finance, implemented by Payments and operated by Support. AppThentic keeps each person’s part, with their name.

See Owners and approvals.

Was this page helpful?
Esc