deployment-and-hosting-guidance

name	deployment-and-hosting-guidance
description	Use when choosing, auditing, changing, deploying, migrating, or troubleshooting hosting, deployment environments, cloud tiers, preview/staging/production setup, persistent versus ephemeral workloads, infrastructure cost, rollback, scaling, or runtime placement.
activation	Activate when the description trigger applies to the current task.
required_inputs	Task request, relevant repository context, constraints, and authority dependencies.
required_outputs	Skill-specific artifact, verification evidence, canonical verdict, and next action.
authority_dependencies	00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md.
evidence_requirements	Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim.

Deployment And Hosting Guidance

Use this skill to route deployment and hosting decisions through APIVR.

Required Inputs

• APIVR tier and applicable Elite Build Goals.
• Application type, runtime, data/storage needs, traffic expectations, and deployment target if known.
• Current hosting provider, environment layout, build/deploy commands, and rollback path.
• Cost sensitivity and reliability target.

Routing Workflow

1. Read 40_knowledge/DEPLOYMENT_AND_HOSTING_GUIDANCE.md.
2. Classify workload shape:
   • static/edge;
   • server-rendered web app;
   • API/service;
   • background worker;
   • scheduled job;
   • event-driven function;
   • database/storage dependent app;
   • always-on realtime process.
3. Decide whether the workload needs persistent compute, ephemeral execution, managed platform hosting, container hosting, or dedicated infrastructure.
4. Identify environment requirements: local, preview, staging, production, rollback, secrets, logs, monitoring, and domain/DNS.
5. If any deployed route is called by a provider, scheduler, webhook, OAuth/Auth redirect, or external machine caller, load skills/external-integration-launch-gate/SKILL.md and require a route contract before release.
6. Record deployment evidence in the evidence ledger and completion report.

Decision Graph

flowchart TD
  A["Workload needs hosting or runtime choice"] --> B{"Static or content-only?"}
  B -- "Yes" --> C["Static hosting or edge CDN"]
  B -- "No" --> D{"Needs long-running process, sockets, or durable memory?"}
  D -- "Yes" --> E["Persistent service or container"]
  D -- "No" --> F{"Triggered by schedule or event?"}
  F -- "Schedule" --> G["Scheduled job platform"]
  F -- "Event/Webhook" --> H["Event-driven function or queue"]
  F -- "Request/response" --> I["Managed app/API hosting"]
  E --> J["Define rollback, logs, scaling, cost"]
  G --> J
  H --> J
  I --> J
  C --> J
  J --> K["Verify deployed behavior before PASS"]

Guardrails

• Do not deploy without rollback or restoration planning for Standard and above.
• Do not choose always-on infrastructure for work that can safely be event-driven or scheduled.
• Do not choose ephemeral/serverless hosting for workloads that require durable in-memory state, long-running sockets, or local filesystem persistence.
• Do not claim deployment success until the deployed URL or service behavior is verified.
• Do not put provider-facing routes behind human login, route-group auth, middleware redirects, or deployment protection unless the provider has a documented machine bypass.