fix(migrate): Q27 essential — do not infer AWS Activate tier from spend#129
Open
herosjourney wants to merge 2 commits into
Open
fix(migrate): Q27 essential — do not infer AWS Activate tier from spend#129herosjourney wants to merge 2 commits into
herosjourney wants to merge 2 commits into
Conversation
…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>
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>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.mdQ4 said credits eligibility is "inferred from Q3 alone";clarify-ai.mdQ15 impact table mapped spend bands → Founders/Portfolio; Q27 was PROPOSED/defaulted; Generate had nounknownguardrails.Changes
Clarify
startup_program_status: "unknown"with neutral downstream copy requirement.Generate
generate-ai.md: conditional Your profile block perstartup_program_status; forbid tier-specific language whenunknown.generate-artifacts-report.md: verdict/callout rules by status; ban spend-based Activate inference in ROI copy.Validation
scripts/validate-startup-program-artifacts.py— fails whenstartup_program_status == "unknown"but artifacts imply a confirmed tier.validate-artifacts.mdcheck fix: Q-number drift, Category E collision, README typo and stale install path #16 — run validator before Generate handoff.fixtures/preferences-unknown-startup.json+ 3 pytest cases.Test plan
pytest tests/test_validate_startup_program_artifacts.py(3 passed)startup_program_status: unknown— neutral copy passes; tier-specific phrases failFollow-up
validate-migration-report.pywhen Enforce comprehensive migration HTML reports with post-write validation #78 mergesMade with Cursor