# Release overview beside live evidence

For a release-oriented brief with tracked work, use a restrained two-column
composition: interpretation on the left, measured state on the right. For a pure
engineering wiki, retain the topic-library pattern in design.md; do not invent a release.

## First screen

Use a full-width home with a meaningful colored system icon. The first body row
pairs a concise release summary (about 44%) with a native database chart (56%).
The summary states the current decision or blocker, links its issue, and shows
the known next checkpoint. A live count by actual work status is useful when
those records exist; title it to describe counts, not an invented readiness
percentage. Static prose beside it is a dated snapshot, not a synchronized metric.

Keep the palette restrained and use color to distinguish actual states. Put the
summary and chart before the issue table, source links, and tabbed library. A
large cover, ornamental cards, or every technical detail above the fold obscures
the release state. With too little data for a meaningful chart, use a compact state summary.
Create a live chart when the records provide meaningful counts.

## Work and technical library

Below the overview, provide native Open work and Specs & runbooks tabs, keeping
the summary/chart outside and above the tab group. The primary issue view shows
title, status, priority and engineer when known. Use full page width, deliberate
column widths and wrapped titles so these fields remain readable together.
Choose visible properties for the engineering workflow. Completed work remains reachable separately. A blocked item must remain
visible. Technical records distinguish current behavior, proposed specs, accepted
decisions and runbooks; bodies carry real context, acceptance criteria or
operational steps. Link issues to relevant documents without creating a competing
tracker when another system owns them.

## Acceptance walk

On the first screen, a reader can state what blocks the release and see the
actual work distribution without opening a table. Check chart counts against
records, including completed work; do not conflate counts with release readiness.
Open the blocker, its technical context, and the docs tab. Inspect chart labels,
long issue titles and code at the actual width. A renamed marketing board fails.

## Render and inspect the saved result

Build records and views first, then compose their existing blocks into the home.
Read the connection's current Markdown and view/layout documentation. For native
toggles and tabs, separate their label from child blocks with a blank line.
Preserve exact child-page/database tags during edits. A tool's success response
does not establish that moved blocks retained the intended order: inspect the
saved page and correct misplaced sections while preserving existing objects.
If moving existing database blocks into a new tab/column container changes sibling
order, fetch the saved hierarchy, then reapply the intended complete composition
using those same object IDs. Verify the saved layout and preserve the working tabs.

Set width, card size, wrapped content and property visibility deliberately.
Configure database-record layouts through the data source. For `page_layout`, read
`notion://docs/database-page-layouts`: pinned properties, sidebar details and
record full width can be configured there before UI inspection.

Hide duplicate database titles when the tab already names the destination.
Use the connected tools and authorized UI editing to configure presentation settings.
A tab intended as a working table must contain an inline database/view, not merely
a link to its full-page source. In Notion Markdown, verify `inline="true"` for
embedded work surfaces; reserve `inline="false"` for navigation destinations.
Use semantic colored page icons so mentions are recognizable, not a repeated
colored dot. Keep original assets and long detail accessible without dominating
the working first screen.

Verify home → record → related work → home, actual view filters and counts, and
at least one alternate view. Set the intended everyday default so reopening the home restores the useful
working view.
Inspect the rendered result at normal zoom with the
sidebar visible. Check that hierarchy, density and navigation make the release
state and technical details easy to find. Check useful work is visible above the fold, long titles wrap, and
essential columns do not overflow. Accessibility text can include off-screen
properties: confirm essential columns in the screenshot before claiming they
are visible. Correct clipped fields and excessive whitespace before delivery.

During skill evaluation, preserve the first result and the run's evidence. If
review finds a miss, change the reusable instructions and rerun or resume the
skill with only that revised guidance. Reviewer hand-polishing is not a passing
skill test. Equivalent layout and workflow matter more than identical wording,
page IDs, image pixels, or arbitrary record counts.
