# LaunchLayer Release Command Center

Canonical guide: https://launch-layers.cloud/help/release-command-center
Product: https://launch-layers.cloud/

The Release Command Center is the project-wide release preflight in LaunchLayer. It is designed to reduce tab hunting and make the next release action understandable without hiding the underlying Apple, Google, build, signing, asset, metadata, privacy, and deployment evidence.

## Status language

The Command Center summarizes the current project as Ready, Working, Needs you, or Blocked. Its readiness percentage is a LaunchLayer progress signal derived from deterministic checks. It is not an Apple App Review or Google Play approval score and does not predict provider policy decisions.

## Check everything

Check everything runs a server-side project-scoped preflight. Depending on the project path and target platform, it can evaluate:
- project and app identity;
- iOS Bundle ID or Android package identity;
- native build-configuration identity alignment;
- exact App Store app binding;
- Apple or Google store/deployment connections;
- signing-readiness evidence;
- app icon and screenshot evidence;
- store name, description, category, privacy URL, and support URL;
- explicit privacy-declaration confirmation;
- latest signed artifact identity;
- unresolved store rejections;
- active screenshot, cloud-build, and deployment work.

The checks use recorded LaunchLayer evidence. Provider state remains authoritative when LaunchLayer has not observed a newer provider-side change.

## Next safe build number

LaunchLayer calculates a suggested next build number from recorded project, configuration, artifact, and deployment build numbers. This reduces accidental reuse of a recorded number. It is guidance rather than a guarantee that the provider has no newer unseen build.

## Smart Fix Center

The Smart Fix Center groups unresolved checks. Take me there opens the relevant project section. Ask AI opens the same project's scoped Project Agent. Routing an issue to AI does not grant the model extra authority: guarded proposal, approval, access-control, and mutation boundaries remain in force.

## Reconcile status

Reconcile status is intended for stale workflow evidence. It asks existing provider-aware screenshot capture, cloud-build, and deployment status workflows to refresh their recorded state and then reloads the project.

Reconcile status does not start a paid build, upload a binary, change signing material or credentials, answer legal/privacy declarations, submit an app for review, or declare provider approval.

## Recommended workflow

1. Open the project and read the Release Command Center.
2. Run Check everything after meaningful setup changes.
3. Follow Do this next before opening every individual tool.
4. Use Smart Fix Center for the remaining issues.
5. Use Reconcile status when external work appears complete but LaunchLayer looks stale.
6. Run Check everything again before a build, upload, or review submission.
7. Use the project timeline to confirm that preflight or reconciliation was recorded.

## Safety boundary

LaunchLayer fails closed on deterministic identity mismatches. Signing, credentials, legal/privacy accuracy, paid build starts, binary uploads, review submissions, and other high-impact provider mutations remain behind their existing explicit workflows. Apple and Google control processing, policy review, approval, and publication.