Skip to content

fix(migrate): Q27 essential — do not infer AWS Activate tier from spend#129

Open
herosjourney wants to merge 2 commits into
awslabs:mainfrom
herosjourney:fix/q27-essential-startup-program
Open

fix(migrate): Q27 essential — do not infer AWS Activate tier from spend#129
herosjourney wants to merge 2 commits into
awslabs:mainfrom
herosjourney:fix/q27-essential-startup-program

Conversation

@herosjourney

Copy link
Copy Markdown
Contributor

Summary

Fixes a Clarify/Generate gap where AWS Activate Founders vs Portfolio was treated as inferable from GCP or AI monthly spend, or silently defaulted on the assumption sheet while downstream artifacts still named a specific tier (e.g. "Eligible Founders").

Root cause: clarify-global.md Q4 said credits eligibility is "inferred from Q3 alone"; clarify-ai.md Q15 impact table mapped spend bands → Founders/Portfolio; Q27 was PROPOSED/defaulted; Generate had no unknown guardrails.

Changes

Clarify

  • Q27 → ESSENTIAL when Category H fires (AI workloads detected). Asked in Step 4 after Q15 — not on the assumption sheet.
  • Q4: Remove spend-based inference; point to Q27 for Activate package selection.
  • Q15: Impact table covers cost modeling only — no Activate tier recommendations from spend bands.
  • Wizard skip handling: if Q27 skipped → startup_program_status: "unknown" with neutral downstream copy requirement.

Generate

  • generate-ai.md: conditional Your profile block per startup_program_status; forbid tier-specific language when unknown.
  • generate-artifacts-report.md: verdict/callout rules by status; ban spend-based Activate inference in ROI copy.

Validation

Test plan

  • pytest tests/test_validate_startup_program_artifacts.py (3 passed)
  • Re-run Clarify wizard on Terraform discovery with Vertex AI — confirm Q27 in essentials batch after "looks good"
  • Generate with startup_program_status: unknown — neutral copy passes; tier-specific phrases fail
  • Generate with Q27 answer B (Founders) — tier-specific copy allowed

Follow-up

Made with Cursor

…m spend

Funding stage (self-funded vs VC-backed) cannot be derived from GCP or AI
monthly spend. Promote Q27 to an essential Clarify question when AI workloads
are detected, remove spend-to-Activate mappings from Q15/Q4, and add Generate
rules plus validate-startup-program-artifacts.py to block tier-specific copy
when startup_program_status is unknown.

Co-authored-by: Cursor <cursoragent@cursor.com>
@herosjourney herosjourney requested a review from a team as a code owner July 9, 2026 03:26
Run dprint on Q27 PR markdown tables; extend startup-program validator to
require a clickable link to aws.amazon.com/startups/credits when AWS Activate
is mentioned; document the link requirement in generate-artifacts-report.md.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant