Section 13 of 440

PART 1: FOUNDATION

1.4 BOUNDED PLAN, REVIEW & RETEST SCHEDULE

A ninety-day cycle is an administrative option, not a biological law. Use the duration appropriate to the task, intervention, risk and evidence. Some questions resolve in days; others require months or should not be self-tested at all.

STEP 1: DEFINE THE BOUNDED PLAN

Declared outcome

Selected route

Actor or configuration

Context and supports

What success will mean

What success will not mean

Baseline date

Direct measure

Measurement uncertainty or detectable-change boundary, where available

Person-defined importance threshold, where appropriate

Safety gate

Stop condition

Fallback

STEP 2: PRESERVE UNAIDED AND SUPPORTED PERFORMANCE SEPARATELY

Where support, another person, assistive technology or AI contributes materially, record separate true statements:

Unaided baseline

Supported baseline

Support or tool identity and version

Combined result

Verification burden

Tool-loss or support-loss fallback

Do not subtract support from the result or attribute configured performance to an unaided person.

STEP 3: USE THE SMALLEST USEFUL PRACTICE OR INTERVENTION

Choose no more than three repeatable actions or supports. They must be feasible, reversible where possible and compatible with safety, disability, work, care and access constraints.

Action or support

Missed actions are information. They do not become a compliance score or moral failure.

STEP 4: SCHEDULE OBSERVATION, REVIEW AND RETEST

Record separately:

Direct assessment date

Delayed-retention date, where justified

Predeclared transfer task and date, where justified

Ordinary maintenance or currency review

Burden and adverse-event review

Professional follow-up, where required

The retest queue uses these states:

CURRENT — qualifying evidence remains inside its declared review window.

DUE — the review date has arrived.

OVERDUE / CURRENCY LAPSED — the review window has passed.

NEVER RETESTED — acquisition or baseline exists without a delayed comparable result.

HISTORICAL — the result is retained but is no longer current.

NOT ASSESSED — accompanied by a valid reason code.

Lapsed currency does not prove lost capability. It means current evidence is absent.

STEP 5: INTERPRET CHANGE HONESTLY

Criterion attainment and longitudinal change are separate. A person may meet the present criterion without proving improvement from baseline. A difference inside the declared measurement noise is recorded as change not detected at the stated confidence under that instrument and protocol—not as proof that nothing changed.

STEP 6: MAKE THE NEXT DECISION

At the declared review point, choose:

KEEP

ADAPT

PAUSE

RECOVER

SUBSTITUTE

RETEST

RETIRE

SEEK QUALIFIED REVIEW

Record the result, uncertainty, support, burden, symptoms, adverse events and rationale. Do not produce a weekly, monthly, layer or whole-person composite.

LONGER-HORIZON DIRECTION

Longer planning remains useful without projecting an idealised score or “fully optimised self.”

Functions or relationships I want to preserve

Capabilities I may need to acquire

Supports I may need to secure

Responsibilities I expect to change

Capabilities that may require maintenance

Dependencies or single points of failure

Conditions under which I would redesign or stop

Person- or community-defined outcome that makes this work worthwhile

The plan is complete when it states a bounded purpose, preserves the baseline, compares routes, names support and authority, schedules review and allows a legitimate stop.