Just-In-Time Capability Offer

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

While editing a process explanation, you find approval→remote login and local setup→local build as independent paths. A small diagram may clarify dependency/parallelism, unlike offering every visualization tool before reading.

Mechanism

Do necessary work first, then offer optional capability tied to an observed communication gap and reader benefit. A dependency diagram is optional, not a prerequisite for independent text edits. Continue text while unanswered and add the chosen enhancement within scope. Never classify required permission/accessibility as optional.

Bad example

Before reading, ask the user to choose all visualization, animation and export tools, stopping every edit until answered.

Good example

Revise the supplied process text first. Offer a small dependency graph because the two paths can be mistaken for one fixed sequence; explain its benefit. Keep it optional and continue text if unselected without repeated promotion. Follow explicit existing choices and preserve required authorization as required.

Why the change matters

Observed need makes an offer assessable. Separating optional/required decisions reduces tool-menu burden without blocking settled work on unanswered preferences.

Observable expectation

The illustrative offer identifies the dependency section and independence of paths. Unanswered choice still permits text completion; declining a graph keeps the text solution.

Reject unrelated effects/exports and required access decisions bypassed by defaults.

Limits

Explicit visualization requests can proceed directly without artificial questions. Verify actual capability availability. Provenance remains unconfirmed, and an optional offer grants no external-service/paid-call permission.