Build a team decision log

What you will build

A decision log where a team records context, ownership, status, and outcomes.

What you will learn

You will shape a data model, add a status workflow, improve the interface, test persistence, and deploy.

Before you begin

Part 1: Plan the application

Use one Decision record with title, owner, date, context, status, and outcome. Use proposed, decided, and revisited as statuses.

Part 2: Create the data model

Describe the application and ask for a form, table, owner and status filters, and five clearly labeled sample records. Select Build for me.

At this point, you can create a decision and see it in the decision table.

Part 3: Build the main workflow

Ask Codex to add actions for marking a proposal decided and revisiting a decision. Require an outcome before decided and preserve the transition time.

At this point, invalid transitions show an error and valid transitions persist after reload.

Part 4: Design the interface

Ask for a compact working table, strong status indicators, an obvious create action, and an empty state that explains the first decision to record.

Part 5: Test and debug

Create, decide, filter, and revisit one record. Check Dev logs after each action and repair any first failure.

Part 6: Deploy the application

Select Deploy app, open the deployed URL, and repeat the create-and-decide workflow.

Review what you learned

The application uses one focused record model, validated state transitions, and views organized around team tasks.

Extend the application

Add related meeting notes, record who changed each status, or create a view for decisions due for review.