Fictional service interruption
The fictional team Alder Offline is planning four rectangular graphics, each one thousand by five hundred millimetres. Its exercise says an optional external AI drafting provider is unavailable. The browser tools and externally hosted static site remain reachable. This constructed outage is not a report of an actual provider incident, service-level guarantee or production monitoring result. It is a test of which parts of a declared workflow genuinely depend on optional assistance.
Complete the deterministic task
The learner enters final width, height, unit and quantity in the area calculator. Multiplying one thousand by five hundred gives five hundred thousand square millimetres per graphic, which is half a square metre. Four graphics therefore have two square metres of rectangular display area. The calculation follows entered dimensions and does not need an AI answer. It excludes bleed, sheet yield, cutting waste and physical suitability; those questions retain their own requirements and checks.
Preserve the useful record
The team can still build a partial brief, record unknown inputs and download structured or readable results from the local workflow. Device saving remains opt-in, and the user should keep an independent export where needed. A provider outage must not silently erase input or turn an earlier draft into accepted work. The selected printer relationship and any real commercial promise remain unchanged unless their actual parties agree a variation. The calculator's successful output does not establish shared-engine availability.
Keep unsupported assistance unavailable
The exercise does not manufacture a source-grounded answer from missing model output. If a task requires summarising a protected report or extracting evidence, the team can review permitted sources manually or wait for the authorised adapter to recover. Arithmetic, permissions and commercial totals should still use tested deterministic processes. Any resumed assistant action needs current permitted context and an attributable result; retries should not duplicate a message or create a contract from stale authority.
Observed result and next action
The observed result is a two-square-metre arithmetic output and a retained local draft while optional drafting remains unavailable. No real uptime percentage, AI accuracy or complete engine resilience is claimed. The mistake avoided is making a model connection a mandatory dependency for every public tool. The next action is to finish independently supported tasks, keep unresolved evidence explicit and verify the actual optional service before resuming assistance, without implying that its recovery approves content or fulfilment.
Take it to the next job
- Keep tested arithmetic independent of optional AI drafting.
- Preserve inputs and usable exports during the unavailable feature.
- Leave unsupported evidence assistance unresolved until its authorised service is verified.
