Workload archetypes map

Before this: Project profile map covered always-on environment keys.

Deep dive for .kiro/steering/workload-archetypes.md — conditional on apps/**. One (or other) archetype decides which manifests exist and which inputs are mandatory. Lab C’s demo-nginx uses web-service.

The map

Nine-stage workload archetype contract: map the workload, three tie-break rules, a five-archetype comparison matrix, always-required inputs, per-archetype inputs, optional inputs, configuration guidance, hardening rules, queue-worker and scheduled-job specifics, and required documentation — The whole archetype contract: pick, collect inputs, scaffold, harden, document.

Two reviewer traps worth naming: a sleep loop shipped as a worker hides failures that a scheduled-job would surface as failed Jobs; and queue-worker sync waves matter — a ScaledObject that starts before its TriggerAuthentication comes up unauthenticated.

Next: GitOps conventions map covers the shape every app lands in.