An access token and an application session are related security objects with separate lifecycles. A token can expire while the relying-party session continues through a refresh or new assertion. A session can terminate while a token remains cryptographically within its validity period. Token presence also does not prove that the subscriber is still present.
This guide develops one focused reader question within the Zero Trust subject guide. It adds a complete mechanism, original worked decisions, changed-context transfer checks and explicit limits. Read it with The Gold Standard of Education | Learning That Transfers into Life and the How X Works.
All numerical examples are invented teaching cases. They are not operational measurements, production records, financial advice, conservation findings or compliance results.
In a fictional system, an access token issued at 09:00 expires at 09:15, a refresh token is valid until 17:00 and the relying-party session has an inactivity timeout at 09:30 plus an overall timeout at 13:00. At 09:16, recent activity permits a refresh and the session continues with a new access token. At 09:20, the user logs out: the relying-party session terminates even though the new access token’s exp value lies in the future; enforcement now depends on revocation and resource-server policy. NIST SP 800-63B-4 session management states that access tokens can remain valid after an authentication session ends and that relying-party and identity-provider sessions are independently managed.
Continue with Separating Session Re-Evaluation from Credential Reauthentication, Resolving Effective Permissions Across Overlapping Roles and Scoped Exceptions and the Zero Trust root.
The short answer is to keep the target quantity, observation and reporting rule separate. Name what the system intends to estimate, what was actually observed, how the summary was formed and which conditions make the inference defensible. If one field is missing, keep the ambiguity visible.
eduKateSG · Zero Trust
Find your next learning step
An access token and an application session are related security objects with separate lifecycles. A token can expire while the relying-party session continues through a refresh or new assertion. A session can terminate while a token remains cryptographically within its validity period. Token presence also does not prove that the subscriber is still present.
Chapter contents
Frame the question · Chapters 1–5
2. Separate the two target quantities
Work the example · Chapters 6–10
6. Work the central calculation
7. Check units before interpretation
Check the evidence · Chapters 11–14
11. Use controls that can fail differently
12. Carry uncertainty into the claim
Transfer the method · Chapters 15–18
16. Change one consequential condition
Audit and continue · Chapters 19–22
19. State what it cannot establish
20. Repair an overconfident sentence
Ask which object expired or ended: access token, refresh token, browser session, relying-party session, identity-provider session or policy grant.
Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “define the reader question”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
A token carries an authorization artifact; a session tracks continuing interaction. Their boundaries and authorities can differ.
Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “separate the two target quantities”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Name issuer, audience, resource server, relying party, session host, token type and revocation mechanism.
Keep the comparison fair by holding the specimen, interval, protocol and denominator constant. If one changes, state that the new number answers a different question even when the label looks familiar.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “name the observation rule”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Record issue, expiry, refresh, activity, logout, termination and enforcement timestamps with clock source.
Use two checks that can fail differently: reconstruct a total, test a limiting case, repeat the result from definitions or inspect a shared control. Two calculations that reuse one assumption are only one check.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “protect the denominator and boundary”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Build the 09:00 access token, 09:15 expiry, 09:30 inactivity limit, 13:00 overall limit and 17:00 refresh expiry.
Separate measurement from decision. A correct number can still be too local, uncertain or method-dependent for the intended action. Report it with its conditions and say what stronger evidence would be needed.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “build the fictional evidence ledger”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
At 09:16 a permitted refresh can continue the session; at 09:20 logout terminates it before token expiry.
| Object | Fictional limit | Governs |
|---|---|---|
| access token | 09:15 | token acceptance window |
| inactivity timeout | 09:30 | RP session activity |
| overall timeout | 13:00 | RP session age |
| refresh token | 17:00 | ability to request another token |
Preserve identity and order. Equal totals can hide different mechanisms when records come from different specimens, resources, homes or viewing geometries. Aggregate only after the question no longer depends on that identity.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “work the central calculation”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Seconds since epoch, local wall time and monotonic duration are not interchangeable. Account for clock skew explicitly.
Run a changed-context transfer check. Change one consequential condition while holding the remaining basis fixed, calculate again and explain why the result moves or stays stable.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “check units before interpretation”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
A token exp claim does not revoke the token early, prove user presence or define the application’s session cookie lifetime.
Put the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name the nearest tempting conclusion the evidence does not establish.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “keep method settings visible”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
A usable trace follows the request from session state through token acquisition to resource-server enforcement.
Use uncertainty as structure. Vary the input most capable of changing the conclusion over a defensible range and show whether the ranking or interpretation changes.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “locate the usable range”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Offline validation can accept a token until expiry even after logout unless revocation or short lifetime policy changes the result.
Finish with a reproducible evidence package: source records, definitions, exclusions, calculations, validation result and revision rule.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “recognise saturation and censoring”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Check RP logs, issuer logs, resource-server decisions and the token claims as evidence that can fail differently.
Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “use controls that can fail differently”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Carry network delay and clock skew into boundary tests; 09:15 on one host may not be identical on another.
Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “carry uncertainty into the claim”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
A 401 response can reflect expiry, audience mismatch, signature failure, revocation or policy; do not diagnose from status alone.
Keep the comparison fair by holding the specimen, interval, protocol and denominator constant. If one changes, state that the new number answers a different question even when the label looks familiar.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “separate mechanism from appearance”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Compare systems only with aligned token model, federation topology, session policy and revocation capability.
Use two checks that can fail differently: reconstruct a total, test a limiting case, repeat the result from definitions or inspect a shared control. Two calculations that reuse one assumption are only one check.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “compare like with like”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Test the rival explanation that the application refreshed silently while the analyst thought one long-lived token remained.
Separate measurement from decision. A correct number can still be too local, uncertain or method-dependent for the intended action. Report it with its conditions and say what stronger evidence would be needed.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “test a rival explanation”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Change the inactivity timeout to 09:10. The RP session ends before the first access token expires at 09:15.
Preserve identity and order. Equal totals can hide different mechanisms when records come from different specimens, resources, homes or viewing geometries. Aggregate only after the question no longer depends on that identity.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “change one consequential condition”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Change logout behavior to revoke refresh but not current access tokens. Resource-server acceptance still depends on its validation path.
Run a changed-context transfer check. Change one consequential condition while holding the remaining basis fixed, calculate again and explain why the result moves or stays stable.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “recalculate the changed case”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
The example establishes independent timelines and authorities for token and session state.
Put the boundary of inference beside the answer. Name the system, representation and interval to which the result applies, then name the nearest tempting conclusion the evidence does not establish.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “state what the result establishes”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
It does not prescribe token lifetimes, guarantee immediate logout everywhere or validate a real deployment.
Use uncertainty as structure. Vary the input most capable of changing the conclusion over a defensible range and show whether the ranking or interpretation changes.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “state what it cannot establish”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Replace “the session ends when the JWT expires” with the actual session, token, refresh and enforcement events.
Finish with a reproducible evidence package: source records, definitions, exclusions, calculations, validation result and revision rule.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “repair an overconfident sentence”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Can an expired token coexist with an active session? Yes, if the session obtains another token.
Can a valid token outlive logout? It can without effective early revocation.
Does token presence prove the user is present? No.
Write an evidence ledger before calculating: target quantity, object, unit, boundary, observation rule, transformation and decision limit. Mark every input as observed, stipulated, fitted or assumed.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “answer focused reader questions”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.
Use NIST session guidance, minimize token lifetime appropriately and preserve an end-to-end enforcement ledger.
Draw the mechanism in order. Separate the underlying state, the measurement, the mathematical summary and the claim. Then name one rival explanation and the additional observation that could distinguish it.
Apply the rule to the central fictional case with unrounded inputs, then label the result with its object, unit and protocol. Name one alternative explanation and the observation that would distinguish it.
For Zero Trust, complete seven fields: target, object, unit, boundary, protocol, result and limit. For “continue through verified routes”, a plausible number can otherwise hide a changed definition or undocumented condition.
Change one condition that matters while holding the remaining basis fixed. Recalculate or re-inspect the evidence, state what stays comparable and name the stronger conclusion that still does not follow.
Close with two lines. The first states what the evidence establishes under the named conditions. The second states the nearest tempting conclusion that remains unsupported. Ask another reader to identify the condition that would make the first line false.
Evidence check: preserve the raw observation, the transformation, the comparison rule and the failed alternatives in one audit note. A future reader should be able to reproduce the narrow result without guessing which conditions were held constant.