App

Everything you have built so far is either invisible (Agents, a case plan, rows in a table) or reached only through a task: the Coded Action App's two screens open one claim at a time, when the Maestro case raises a gate in Action Center. Nobody can go and look. This section builds the surfaces people open on their own, starting with the one PDD.md §11 asks for.

Two apps, two jobs

	Coded Action App (block 3f)	Process App (block 6)
Who opens it	A reviewer, when a task lands	The claims team lead, any time
How it opens	Inside Action Center, from the task	At its own URL, signed in
What it shows	One claim, at one gate	The whole portfolio; every claim; one claim in full
What it decides	That task	The same task, from the claim page, and nothing else
What it writes	Completes its task; the case writes the record	Completes the task; the case writes the record; the app never does

A reviewer's screen with a claims list bolted on is the wrong thing, and so is a dashboard that lets someone edit a claim. This section keeps two apps, one claim view shared between them, and one writer of the record.

In this section

Step	What it covers
1. Build the Process App	Block 6, a standalone Coded Web App: the portfolio dashboard, a searchable claims list, and one claim on the Action App's own screen

This is the section's first lesson. More join it as they are proven.