# Codex App: From Task to Verified Change

**Author** Aklman · **Published** June 6, 2026 · **Language** English
**Canonical** https://aklman.com/sessions/codex-app-demo/
**Site** Aklman · aklman.com

> This session is from Aklman. AI reading, quoting, and Q&A are welcome; keep the author attribution and canonical link when quoting.

---

## Summary

A product demo script for showing how goal, context, execution, and verification fit into one development flow.

## Context

- Format: Demo
- Platform: Web Demo
- Duration: 18 min
- Topics: Codex / AI Native Development / Developer Experience
- Slides: https://aklman.com/sessions/codex-app-demo/slides
- Slides PDF: https://aklman.com/sessions/codex-app-demo/slides/print
- Print: https://aklman.com/sessions/codex-app-demo/print

## Outline

1. **State the task clearly** — Begin with goal, constraints, and acceptance criteria before asking for code.
2. **Make context traceable** — Files, terminals, browsers, and tests become evidence in one workflow.
3. **Close with verification** — Every handoff should say what changed, what was tested, and what risk remains.

## Notes

This demo explains how an agentic development product should present its value.

The point is not to perform AI writes code quickly. The point is engineering flow: task input, context reading, change execution, verification feedback, and a clear handoff.

## Slides

1. **A task is not one prompt**
   - 01 / Goal
   - A good development task names the goal, boundaries, acceptance checks, and places the agent should not touch.
2. **Context should be replayable**
   - 02 / Context
   - When an agent reads code, runs tests, and inspects the browser, it should leave understandable evidence.
3. **Delivery ends with proof**
   - 03 / Verification
   - Not 'I changed it', but 'I changed these parts, tested these paths, and this risk remains'.

## Resources

- [Works index](/works)

---

*Aklman · aklman.com · Latest version: https://aklman.com/sessions/codex-app-demo/*