← Blog
Week of

Retrospective reconstruction · Published · Weekly archive

Run the awkward version of the demo

A clean example shows possibility. Messy inputs show where the work remains.

Field NotesRetrospective

Retrospective reconstruction of the week beginning 2025-01-20, written on 16 November 2026. This is not a claim of publication at the time.

Cosmos was one of January’s striking announcements. The follow-up question for any impressive demo is fairly ordinary: what happens if we change the input?

Try an empty field. Try a repeated request. Give it two instructions that conflict. Use a value right at the limit. Include something the system should stop and ask about.

Write the expected behaviour down first. Otherwise it is too easy to watch an unexpected result and explain why it was probably fine. A missing input should stay missing until resolved. A second click should not silently create a second order.

Keep the evidence appropriate to the claim. A screenshot shows what was visible. It cannot prove that a record was saved correctly or that a background job finished. Check the stored state as well.

This does not require a huge testing programme before anyone can try a prototype. Start with five awkward cases around its main promise. If two fail, the next work is already obvious. Fix those and rerun the clean example too. There is no need to invent a larger roadmap while the basic path still breaks.

Sources available at the time

NVIDIA CES announcements

All posts Work with me