Core Deployment Readiness

Core Deployment Readiness

Use the agent to decide whether an app, feature, or prototype is ready for deployment, rollback, and operational ownership.

Verified Surface

• Provider lane: core
• Native surface: SKILL.md skill packages
• Harness export: core
• Import mode: techtide-synthesis
• Source evidence: load references/source-evidence.md before promoting third-party material.

Workflow

1. Confirm build, test, lint, smoke, and environment checks are green or explicitly waived.
2. Verify secrets, migrations, feature flags, observability, and rollback steps.
3. Check user-facing flows at the smallest practical production-like boundary.
4. Block deploys with unreviewed auth, payment, destructive data, or external-recipient writes.
5. Produce a go, no-go, or conditional-go recommendation with evidence.

Output Contract

Return:

• provider lane and native surface
• source evidence used
• promotion decision or operating recommendation
• security and privacy notes
• verification still required

Guardrails

• Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
• Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
• Do not install or execute unreviewed external scripts as part of source research.
• Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
• Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.