TEKIN METHOD
03

Documentation is not traceability

One says what should happen. The other shows what did, and under whose decision.

The number is right.
But who decided
the records under it?

1

Two different things

D
DocumentationThe design, the policy, the wiki page.
T
TraceabilityFor each record: which decision, which rule, which person.
2

Why "last modified by" is not enough

When an agent or an integration writes a record, the audit fields often show a technical user. You can see what changed. You can't see whose decision it was.

3

Three honest answers

Every record behind a number gets one.

✓
OwnedPassed a limit someone owns.
×
UnownedWritten by a path with no limit.
?
UnknownThere is no evidence either way.
4

What the answer sounds like

One sentence instead of a score.

// refunds this quarter 412 records behind the number 251 passed a limit someone owns 138 written by a path nobody owns 23 we cannot see
The 23 matter too.
5

Unknown is never owned

If you can't see how a record got its value, it doesn't count as safe. Missing evidence stays visible as missing.

6

Check one number this week

1
Pick one dashboard numberOne that someone acts on.
2
Find what writes itPeople, Flows, agents, integrations.
3
Ask of each pathIs there an owner and a limit?
7

Why it matters now

Before agents, most writes came from a person you could ask. Now more of them come from paths that cannot explain themselves.

From number
to decision

Numberon the dashboard
Recordsbehind it
Writesthat set the value
Pathsthat made the writes
Owner?yes, no, or unknown
← Objects and linksAll cardsTry the 3-question test →