Examples
See the method applied to representative project and discovery situations.
Guides in this section
A minimal, non-sending error-report adapterThis example lets you validate an adapter package without a vendor account or network access. It always rejects transport. It must never report a ticket as created when nothing was sent.
Review and promote one meeting statementThis complete example uses fictional notes in a disposable, initialised EWAI project. It demonstrates the file handoff; no meeting platform, model call or real person's approval is involved.…
Install and select a small design-system packUse a disposable initialised project for this exercise. It shows the distinction between a candidate folder, an installed pack and an approved project selection. In a real project, review the guidance with its owner before selecting it.
Complete prototype-review inputsThese are the four CLI input shapes for a prototype plan and one design cycle. They aren't ready-made approval records. Use them with an existing UI delivery whose intent and design-system guidance you've reviewed.
Worked example: reproducible Archaeology and Discovery depthThis example shows how two sessions can produce different explanatory wording while reaching the same material investigation boundary. The project, people, IDs, and digests are illustrative; they are not a claim about a real system.
Record one reviewed test scenarioUse this complete input shape after preparing scenarios for an existing intent. The fictional feature here is customer-access; it isn't a requirement your project inherits.
Worked examplesThese compact scenarios demonstrate how to apply EWAI proportionately. They're illustrative decision patterns, not specifications to copy unchanged or exhaustive phase checklists. A stage omitted from an example isn't waived; follow the cur…