Who creates this material
The byline “Ask Two Questions editorial desk” identifies the site’s publishing operation. It is not a claim that a named academic, therapist or certified trainer reviewed the material. The guides are checked for case arithmetic, information boundaries, internal consistency and working links.
Technical and editorial checks do not establish real-world effectiveness. We avoid invented studies, testimonials, search volumes, results and professional qualifications.
How we check an exercise
We record the fixed facts, missing information, available resources and person who may authorize a change. A counterfactual is labeled as a changed condition rather than silently added to the original scene.
For example, Fixed Deadline has five available hours and a seven-hour full request. Core plus mandatory handoff takes four hours. A seven-hour promise becomes arithmetically feasible only when two additional hours are explicitly authorized and actually available.
For two-role exercises we check what each person can see. The outcome holder should not see the capacity holder’s private estimates in advance. Otherwise there is no meaningful information exchange.
Sources and evidence
Most guides are original practice frameworks built around authored fictional examples. Where no external research finding is used, the page says so. Where an external factual claim is needed, it should link to a source that directly supports that claim.
We distinguish factual constraints within an exercise, suggested actions, plausible consequences and measured observations. At this stage we have technical prototype evidence, not participant outcome evidence.
Updates and corrections
Each guide shows its actual publication date. Future edits should change the modification date when the substance changes, preserve the canonical URL and document a material correction here.
No public corrections form or monitored inbox is currently connected. Readers can check the stated assumptions and compare a guide with its linked practice case. A contact route must be established before a support response is promised.