A.6.A:4.4 - Recover details that change the result
Use the following questions where their answer changes the recovered meaning or its use. They are not ten fields that every sentence must populate:
-
Site tuple and site classification. Site tuple members: named EntityOfConcern, scene, interface element or front-end element, Description episteme, episode, control state, or non-claim-bearing site kind - with publication or carrier participation stated separately when live.
-
Invited enactor tuple. Which
U.System, collective system, or role assignment whose holder is aU.Systemis invited to act. -
Candidate action tuple. What action or inquiry the phrase concerns. If the result selects a Method for enactment, identify its exact
U.Method; keep any MethodDescription, WorkPlan and actual Work separate under their direct rules. -
Intended meaning. Which interpretation the context supports, and which consequential rival remains or is excluded. An
AIS.*label is optional. -
Coupling frame. The actual conditions and, where applicable, coupling relation on which the recovered claim depends; recover their rule rather than treating their names as proof. Examples: reach envelope, interface state, incident horizon, control horizon, probe pack, open issue set.
-
Detector, viewpoint reference, and independent view. Who or what detected the cue; which exact viewpoint episteme
viewpointRefresolves to under the effective reference scheme when a viewpoint is selected; and, independently, which already-conformingview : U.Viewis cited when a view itself participates. None follows from another. -
Normal form and
articulationHint. Whether a particular expression form or articulation cue changes what the receiver can recover or do. -
Scope and time when relevant.
U.ScopeandΓ_timeSHALL be explicit when omission changes meaning. -
Representation substrate when relevant. Especially when comparing ecological, embodied, latent-distributed, and symbolic-local treatments.
-
Witness mode and evidence references. Exemplars, sensory traces, probe notes, kinematic data, interface events, controller traces, run logs, or review notes.