🧪Lesson 03AI Engineer Loopcraft Workshop 2026

Show issue events in Lakebed

Read the same local event file from Lesson 02 and show matching issue cards in Lakebed.

Read the same local event file from Lesson 02 and show issue cards in Lakebed. The cards should match the check command output. If the view disagrees with the local check, fix the view code, not the event file.

Your next move

You already have

A local event file and parser from Lesson 02.
A check command whose output is the source of truth for issue status.

Add now

A small endpoint or module that reads the same event file and returns issue cards for Lakebed.
List, board, and event views that show status, stop reason, and next action.
A comparison receipt between check output and the Lakebed route.

Stop before

Changing event data just to make the page look right.
Adding writes, schedulers, external trackers, or background workers.

Tiny projection receipt shape

eventFile: data/issue-events.jsonl
checkCommand: pnpm run check:issues
checkCounts: ready 1, approval-required 1, input-required 1
lakebedRoute: /lakebed
lakebedCounts: ready 1, approval-required 1, input-required 1
mismatch: none
nextAction: keep the view path wired to the same event file

Starter prompt

Use the local events and check command from Lesson 02. Add the smallest endpoint or module that reads the same event file and returns issue cards for Lakebed. Show list, board, and event views with status, stop reason, and next action. Run the local check, open the Lakebed route, compare the results, and save a receipt. If the view disagrees with the check output, fix the view path, not the event file. Do not add writes, schedulers, external trackers, or background workers yet.

Build checklist

0/4 done

Keep the file in charge

Reuse the Lesson 02 event loader or wrap it with one small module. Do not move decisions into the UI.

Return issue cards

Add the smallest endpoint or module Lakebed needs to read issue id, title, status, stop reason, next action, and recent events.

Render useful views

Show a list, board columns, and event history that explain why each card landed in its current state.

Compare and save proof

Run the local check, open the Lakebed view, compare counts and statuses, then save a receipt for the comparison.

Proof to save

Save proof that the screen shows the same facts as the command.

The local event parser and check command still run without Lakebed.
A small endpoint or module reads the same event file and returns issue cards.
List, board, and event views show status, stop reason, and next action for each issue.
A receipt records the event file, check command output, Lakebed route opened, and any mismatch found.

file: local event file read
command: local check command and result
output: local counts and Lakebed card counts
stop condition: any mismatch means fix the view path before moving on
receipt: route opened, screenshot or log, and comparison result

Done when

One ready, one approval-required, and one input-required issue appear in the correct Lakebed lanes and match the local check output.

Why it matters

Risk reduced: the view cannot quietly invent a different issue state.
Temptation avoided: treating a pretty card as proof when it does not match the command.
Do not automate yet: writes from the UI, claim actions, external tracker calls, or background updates.

Try this 🔨

Pick one card, find the event that created its status, and say the next allowed action out loud.

Exploration prompts

Use these when you want to ask an agent for a narrower pass instead of handing it the whole lesson.

Trace file to card

Compare the local event file, check command output, and Lakebed cards. List any mismatch between the command output and what the page shows, then suggest the smallest fix.

Choose the read path

Inspect the current Lakebed code. Recommend the smallest endpoint or module for returning issue cards from the local event file without moving decisions into the UI.

Write comparison proof

Draft a receipt that proves one ready, one approval-required, and one input-required issue appear in Lakebed and still match the local check.