templates/data-app/examples/acme-workflow/README.md

# Acme Cloud automation usage

Golden lifecycle reference. See the [catalog](../manifest.json) for revision-specific approval and eligibility.

## Question and fit

Where does adoption move from installation to activation, repeat usage and retention?

Adapt this reference when evidence supports an adoption lifecycle or cohort and aggregate flow investigation. Borrow only relevant sections when the whole composition does not fit. An explicitly requested layout takes precedence.

## Preservation and adaptation

Acme Cloud is a fictional workflow product. The canonical content, fixture and semantic tests live here. The dashboard follows installation, activation, first-conversation flow, activity and retention, with independently scoped controls and shared section navigation.

Replace the synthetic fixture with reviewed evidence. Preserve units, population eligibility, weighting, maturity and missing values. Read the [evidence contract](data-contract.md); remove unsupported analyses rather than invent entity-level records from aggregates. Vocabulary belongs in authored content, not the shared component library.

Cards use the shared editable canvas within each analytical section: drag from card-header whitespace, resize adjacent-card boundaries, and use the Move control with keyboard arrows. Section boundaries retain their filter and source scope.

Prepare privately from the plugin root with `node scripts/prepare-data-app.mjs --surface dashboard --example acme-workflow --output /absolute/new-directory`. Gallery launchers and prepared projects share this canonical implementation. Build, rendered review and fresh-generation acceptance are separate checks.