Quality Gates

Quality gates are the evidence contract for a stack pack. Agents may not claim a starter, reference app, package, or release is done unless the relevant gates pass or are explicitly marked out of scope.

Gate Status Values

Status	Meaning
`required`	Must pass for this stack pack to be usable
`conditional`	Required only when the app uses the named feature or platform
`manual`	Requires a human, device, account, or policy review
`paid`	Costs money or external quota
`deferred`	Known gate, intentionally not in current scope
`not-applicable`	Not relevant, with reason recorded

Gate Matrix

Gate	Status	Command or proof	Environment	Evidence artifact	Failure handling
Scaffold from clean state	`required`	`[create command]`	`[machine/tool versions]`	`[created layout]`	`[first diagnostics]`
Local dev run	`required`	`[dev command]`	`[port/device/emulator]`	`[URL, screenshot, logs]`	`[first diagnostics]`
Tests	`required`	`[test command]`	`[env]`	`[passing output]`	`[first diagnostics]`
Lint	`conditional`	`[lint command]`	`[env]`	`[passing output]`	`[first diagnostics]`
Format check	`conditional`	`[format command]`	`[env]`	`[passing output]`	`[first diagnostics]`
Typecheck	`conditional`	`[typecheck command]`	`[env]`	`[passing output]`	`[first diagnostics]`
Production build	`required`	`[build command]`	`[env]`	`[artifact path]`	`[first diagnostics]`
Device/browser smoke	`conditional`	`[device/browser command]`	`[target]`	`[screenshot/log/video]`	`[first diagnostics]`
Package	`conditional`	`[package command]`	`[toolchain]`	`[package path]`	`[first diagnostics]`
Signing	`conditional`	`[sign command or manual step]`	`[cert/key/account]`	`[signed artifact]`	`[first diagnostics]`
Release/store	`manual`	`[dry-run, deploy, upload, or checklist]`	`[account/store]`	`[release result]`	`[rollback or stop condition]`
Security/privacy	`conditional`	`[scan/checklist]`	`[data model]`	`[scan output or review note]`	`[first diagnostics]`
Cleanup/reproducibility	`required`	`[cleanup command or notes]`	`[env]`	`[fresh rerun proof]`	`[first diagnostics]`

Evidence Rules

Terminal output should name the command, working directory, and success result.
Screenshots should include the app state, target device/browser, and timestamp when practical.
Build artifacts should include paths, sizes, and signing/package status.
Store or release gates should distinguish dry-run, upload, review, approval, and publish.
Security/privacy gates should name the data handled, permissions requested, and user-visible disclosures.

Gotcha: A passing build is not a release gate. Packaging, signing, install, store policy, and runtime smoke checks are separate gates on many stacks.

Eval Layer

Add eval fixtures only after the stack pack has been used at least once in a real app build. Early evals should be tiny:

Eval	Purpose	Required assertions
Smoke app prompt	Checks whether agents can follow the pack from scratch	Creates app, uses supported command, passes test/build
Known pitfall prompt	Checks whether agents avoid a documented trap	Avoids deprecated command, unsafe permission, or wrong import
Release claim prompt	Checks release discipline	Refuses to claim publish until package/sign/store gates have evidence