AWS Kiro

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Ready

Primary summary from verified readiness

Evidence strength Strong

Decision

Human editorial judgment · 2026-08-20

Wait for stronger evidence

Why: Spec-driven engineering aligns with our IPRP/spec-first rules, but the metered vibe/spec pricing, consumption bugs, and single-agent rigidity make it cost- and throughput-unpredictable for high-volume autonomous use, where we already rely on Codex (ChatGPT plan) and agy.
Next: Trial only via the AWS Startups 1-year Pro+ credit (if still open) to validate spec-driven flow cost vs Codex/agy; do not put Kiro on the per-request metered plan in any autonomous cron loop until consumption-per-request is predictable

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revision 12