Kiro

Quadrant distribution

Jev `choice` — not a hard 0.5 cut. Confidence 0.65.

• Operational8.0%
• Anchored14.0%
• Forming4.0%
• Directed74.0%

Evidence ledger

Recency half-life 180 days. Weight = 2^(-age/180).

1. announcement · accessed 2026-09-24 · w=0.996

   Amazon Q Developer end-of-support; migrate to Kiro

   AWS announced Amazon Q Developer IDE plugins and paid subscriptions reach end of support on 30 April 2027 and directed customers to Kiro, described as a spec-driven agentic IDE/CLI with agentic coding, inline chat, terminal integration, and MCP. New Q signups closed; Opus 4.6 left Q Developer Pro on 29 May 2026.

2. announcement · published 2026-06-25 · w=0.702

   Kiro FedRAMP High and DoD IL-4/5 in GovCloud

   AWS announced Kiro is FedRAMP High and DoD CC SRG IL-4/5 authorized in AWS GovCloud (US), describing Kiro as an agentic AI with IDE and CLI for spec-driven development and native MCP support.

Reproducibility

resolved model: jev-1.13.0

requested model: jev-latest

request id: req_01a0d5de8d2c7c97a48af2c648debc46

timestamp: 2026-09-25T00:02:01.331Z

request hash: e5f3ce3c7fd695071cd944d3ad8e648c2698336acde59e44ebf124aa3cf0a5c1

{
  "model": "jev-latest",
  "state": {
    "goal": "Score this entity on the Jev Quadrant rubric using only the supplied evidence.",
    "framework": "jev-quadrant-v1",
    "topic": {
      "id": "ai-coding-agents",
      "title": "AI coding agents",
      "x_axis": "Proven Execution",
      "y_axis": "Validated Direction"
    },
    "entity": {
      "id": "kiro",
      "name": "Kiro",
      "website": "https://kiro.dev",
      "description": "AWS’s spec-driven agentic IDE and CLI; successor path for Amazon Q Developer IDE plugins."
    },
    "evidence": [
      {
        "id": "q-eos",
        "kind": "announcement",
        "url": "https://aws.amazon.com/blogs/devops/amazon-q-developer-end-of-support-announcement/",
        "date": "2026-09-24",
        "date_kind": "accessed",
        "recency_weight": 0.9962,
        "summary": "AWS announced Amazon Q Developer IDE plugins and paid subscriptions reach end of support on 30 April 2027 and directed customers to Kiro, described as a spec-driven agentic IDE/CLI with agentic coding, inline chat, terminal integration, and MCP. New Q signups closed; Opus 4.6 left Q Developer Pro on 29 May 2026.",
        "title": "Amazon Q Developer end-of-support; migrate to Kiro"
      },
      {
        "id": "kiro-fedramp",
        "kind": "announcement",
        "url": "https://aws.amazon.com/about-aws/whats-new/2026/06/kiro-fedramp-high-dod-il-4-5-govcloud-us/",
        "date": "2026-06-25",
        "date_kind": "published",
        "recency_weight": 0.7017,
        "summary": "AWS announced Kiro is FedRAMP High and DoD CC SRG IL-4/5 authorized in AWS GovCloud (US), describing Kiro as an agentic AI with IDE and CLI for spec-driven development and native MCP support.",
        "title": "Kiro FedRAMP High and DoD IL-4/5 in GovCloud"
      }
    ],
    "claims": [],
    "independent_checks": [],
    "recency": {
      "half_life_days": 180,
      "as_of": "2026-09-25",
      "mass": 1.6978
    }
  },
  "questions": {
    "exec_shipped": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Has this entity shipped a generally available product used by third parties?",
      "criteria": {
        "true": "Independent public evidence shows a generally available product used by third parties.",
        "false": "The product is announced, preview-only, or evidenced only by unsourced vendor marketing with no third-party use."
      }
    },
    "exec_adoption": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is there credible adoption evidence?",
      "criteria": {
        "true": "Credible adoption evidence exists: named customers, published user or download counts, case studies, or equivalent.",
        "false": "Adoption claims are absent, purely anecdotal, or unsourced."
      }
    },
    "exec_reliability": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is there evidence of reliability, quality, security/compliance, or operational maturity?",
      "criteria": {
        "true": "Evidence of reliability, quality, security/compliance, or operational maturity (uptime, incidents handled, certifications, long-running open-source project).",
        "false": "No reliability or quality evidence is present."
      }
    },
    "exec_cadence": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is there evidence of continued delivery after launch?",
      "criteria": {
        "true": "Evidence of continued delivery after launch (dated releases, changelog, subsequent features).",
        "false": "Delivery appears one-shot or stalled."
      }
    },
    "dir_strategy": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is there a specific, consistent, dated public strategy or roadmap?",
      "criteria": {
        "true": "A public strategy or roadmap is specific, consistent, and dated.",
        "false": "Direction is vague, contradictory, or only implied."
      }
    },
    "dir_backed": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Are strategy or roadmap claims backed by shipped artifacts in the evidence pack?",
      "criteria": {
        "true": "Roadmap or strategy claims are backed by shipped artifacts in the evidence pack.",
        "false": "Direction is promised without corresponding delivery evidence."
      }
    },
    "dir_distinct": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is the evidenced direction distinct from generic category copy?",
      "criteria": {
        "true": "The evidenced direction is distinct from generic category copy.",
        "false": "Positioning is interchangeable with peers."
      }
    },
    "dir_invested": {
      "type": "noul",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Is there evidence of sustained investment in this product?",
      "criteria": {
        "true": "Evidence of sustained investment (funding used for the product, research, open-source velocity, or platform expansion).",
        "false": "No evidence of continued investment."
      }
    },
    "quadrant": {
      "type": "choice",
      "instructions": "Use only the supplied state. Do not use prior knowledge that is not represented as evidence items. If evidence is thin, return a probability near 0.5 with the understanding that uncertainty is handled separately. Assign the entity to one Jev Quadrant cell. Do not use a hard 0.5 cut. Weigh the full evidence pack.",
      "criteria": {
        "ANCHORED": "Both delivery (proven execution) and evidenced direction (validated direction) are strong.",
        "DIRECTED": "Validated direction is better evidenced than proven execution.",
        "OPERATIONAL": "Proven execution is better evidenced than validated direction.",
        "FORMING": "Both axes are thin, early, or contradicted."
      }
    }
  }
}

Challenges

Anyone can submit a source. Payment never affects review.

No pending or accepted challenges yet.