# Activity reporting app — proposed demonstration brief

Status: proposed scope for a roundtable-to-spec demonstration; not approved implementation.

## User and outcome

A person reviewing project activity wants to inspect the records a simulated user may see, narrow that selection, and export it to a spreadsheet without copying rows.

## Smallest first version

Use the existing local command-line activity-reporting example as the application context. Specify its list, filter and CSV-export workflow using synthetic data. A command-line first version keeps this demonstration focused on specification quality; the user may choose a different interface before consultation approval.

Include project membership and row restrictions as explicit simulated data rules. They are not production authentication. Reuse the established CSV contract rather than deciding a new file format.

## Exclusions

No web interface, server, production authentication, remote data, billing feature, cloud sync, production integration, implementation, publication or deployment. The host will write spec documents only. Model consultation is a separate proposed action requiring explicit authority and an agreed billing route.

## Roundtable objective

Assess whether SPEC-INITIAL.md is coherent enough to guide this small project. Find material ambiguities, conflicting requirements, missing observable checks and unsuitable task dependencies. Cite the supplied sources. Recommend revisions only when they improve this stated goal; do not invent new features or deliberately manufacture disagreement.

## Success for the demonstration

Preserve the initial spec and actual consultation evidence. Inspect citation support, record which recommendations the human accepts or rejects, and produce a revised spec with a traceable comparison. A useful supported change is evidence of assistance. If the review justifies no material change, report that outcome; a completed consultation alone does not establish an improved spec.