Localize ParkNudge from territory and search-intent evidence

[lightcloud00]

Outcome

Expand beyond English-US only where App Store and web evidence identifies a market that can justify complete, supported localization.

Dependencies

• Baseline territory and Search Console data in Establish the privacy-preserving launch revenue scorecard #14
• Final English source copy and screenshots in Finalize legal, privacy, App Store metadata, and screenshots #8

Plan

• Rank candidate locales using downloads, proceeds, product-page conversion, support demand, and search impressions.
• Select one locale at a time and record why it won.
• Localize the app binary, permission strings, notifications, paywall, App Store metadata, screenshots, support, privacy, terms, and key website pages as one coherent release.
• Use qualified human review for safety-sensitive, legal, commerce, and permission copy.
• Test locale decimal parsing, currency minor units, truncation, VoiceOver, and screenshots.
• Compare the localized territory baseline after release.

Guardrails

• App Store metadata localization alone is not a localized product.
• Do not auto-publish machine-translated legal or purchase copy.
• Preserve StoreKit localized displayPrice and each parking record currency.

Acceptance

• One complete locale passes the app/site/localization checklist.
• Store and public website readback match the committed source.
• The decision record includes pre/post metrics and support readiness.

Apple guidance: https://developer.apple.com/localization/

---

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Evidence and closure

Close only from exact current-source evidence plus the applicable independent readback. Keep local, GitHub/CI, provider, deployment, device, store, commerce, indexing, traffic, and revenue evidence distinct; one does not imply another.

Owner / lane

The repository delivery lane owns ordinary implementation and verification. The operator owns only actions explicitly marked as operator-only or protected.

Resolution plan

• Verified: 2026-08-25T05:34:22Z against main@04a6cd5e808720983471ee9595fd40bc94e1f0fe (commit time 2026-08-25T00:53:29Z).
• Source basis: Original issue body, all 0 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
• Disposition: Operator or external gate - execute only the bounded proof steps and stop at protected actions.
• Outcome: Expand beyond English-US only where App Store and web evidence identifies a market that can justify complete, supported localization.

Current evidence and corrected premise

The issue remains open and requires the resolution steps below.
All 0 issue comment(s) were read. There are no comments.

Resolution steps

1. Refresh the authoritative external state and bind it to the exact account, app, build, deployment, or provider identity.
2. Reconcile that readback with the issue-authored work below and identify the smallest remaining action.
3. Prepare the protected action, rollback, and failure receipt without exposing credentials or inferring authority.
4. Stop for the required operator decision or action, then execute it once through the owning workflow.
5. Validate the official readback and map it to every acceptance item before closure.

Grounded issue-authored detail

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Tests and acceptance

Acceptance

• One complete locale passes the app/site/localization checklist.
• Store and public website readback match the committed source.
• The decision record includes pre/post metrics and support readiness.

Apple guidance: https://developer.apple.com/localization/

---

Dependencies and stop gates

Dependencies

• Baseline territory and Search Console data in Establish the privacy-preserving launch revenue scorecard #14
• Final English source copy and screenshots in Finalize legal, privacy, App Store metadata, and screenshots #8
• Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

[lightcloud00]

Verified issue disposition — blocked_external

This is the current managed disposition for lightcloud00/parknudge#19 at default-branch 5c3d185143a2.

Current evidence

• Current stable snapshot for Localize ParkNudge from territory and search-intent evidence #19 at 5c3d185143a2 keeps the issue open with body hash 8a7a8477ea0a; the validated grounded planner classified it as blocked_external.

Files or owner actions

• For Localize ParkNudge from territory and search-intent evidence #19, bind the issue title 'Localize ParkNudge from territory and search-intent evidence' to one existing source path or named owner action before implementation.

Bounded plan

• For Localize ParkNudge from territory and search-intent evidence #19: Resolve the recorded targeted-source diagnostic or bind a canonical checkout before any implementation attempt.
• For Localize ParkNudge from territory and search-intent evidence #19: Complete every read-only and local source check that does not require the external owner or protected system.
• For Localize ParkNudge from territory and search-intent evidence #19: Bind the remaining decision to the exact issue surfaces: Localize, ParkNudge, territory, search-intent, evidence.
• For Localize ParkNudge from territory and search-intent evidence #19: Record the required owner input as one explicit question with a recommended default and impact of deferral.
• For Localize ParkNudge from territory and search-intent evidence #19: Continue the portfolio queue; resume this issue only when the named external proof or decision arrives.

Commands

• Run git grep -n -F Localize main for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.
• Run git grep -n -F ParkNudge main for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.
• Run git grep -n -F territory main for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.
• Run git grep -n -F search-intent main for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.
• Run git grep -n -F evidence main for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.
• Run python3 -m pytest -q for Localize ParkNudge from territory and search-intent evidence #19 and retain sanitized output.

Acceptance tests

• For Localize ParkNudge from territory and search-intent evidence #19: [ ] One complete locale passes the app/site/localization checklist.
• For Localize ParkNudge from territory and search-intent evidence #19: [ ] Store and public website readback match the committed source.
• For Localize ParkNudge from territory and search-intent evidence #19: [ ] The decision record includes pre/post metrics and support readiness.
• For Localize ParkNudge from territory and search-intent evidence #19: [ ] One complete locale passes the app/site/localization checklist.
• For Localize ParkNudge from territory and search-intent evidence #19: [ ] Store and public website readback match the committed source.
• For Localize ParkNudge from territory and search-intent evidence #19: [ ] The decision record includes pre/post metrics and support readiness.

Risks

• For Localize ParkNudge from territory and search-intent evidence #19, a false source binding could widen the change or invalidate this plan; Revert only the exact task-branch change after capturing source and runtime identity; never reset or restore an owner worktree.

Stop gates

• For Localize ParkNudge from territory and search-intent evidence #19: no issue close, reopen, body edit, pull-request, branch, or merge mutation while implementing this plan
• For Localize ParkNudge from territory and search-intent evidence #19: the managed plan comment and disposition-specific readiness labels are the only authorized issue mutations in the planning lane
• For Localize ParkNudge from territory and search-intent evidence #19: no push, protected-branch update, force-push, or merge
• For Localize ParkNudge from territory and search-intent evidence #19: no deploy, upload, App Store Connect, TestFlight, or public release
• For Localize ParkNudge from territory and search-intent evidence #19: no credential value disclosure, rotation, billing, or provider change
• For Localize ParkNudge from territory and search-intent evidence #19: no owner-worktree restore, reset, checkout, process signal, or queue reorder

Named owner action

• Gus must complete or coordinate the protected action 'Localize ParkNudge from territory and search-intent evidence' for Localize ParkNudge from territory and search-intent evidence #19, then attach sanitized evidence at proof/parknudge-19/acceptance.json.

Proof target

• proof/parknudge-19/acceptance.json

Retry trigger

• Retry Localize ParkNudge from territory and search-intent evidence #19 only after proof/parknudge-19/acceptance.json records the title-specific external action as complete.

---

Ledger schema: aos.github-issue-plan-coverage.v1 · issue body: 8a7a8477ea0a

[lightcloud00]

Evidence-selected international search packet — ParkNudge

• Portfolio order: 23 / 34 (tier_c)
• Surfaces: web, ios_app_store
• Owned Google/Bing readiness: unobserved
• US baseline: evidence_unobserved (28 days required)
• International state: held_for_us_baseline
• Market decision: none — CA / en-CA is only a tie-break candidate; it is not selected.
• Source: lightcloud00/search-intelligence-engine@f3599220140ed9f7840320385afa4951708390b4
• Source checks: full Python test suite; npm lint, typecheck, tests, migration checks, production build, and rendered HTML tests; marker-owned GitHub dry-run before apply and SHA readback after apply
• Owner/retry: this issue owns the next evidence pass; retry country scoring only after its 28-day US baseline reaches 60% coverage.
• Catalog: portfolio-market-research-catalog.v1@2026-08-30.1; as of 2026-08-30T05:14:05Z

Seed intents are research inputs, not validated volume claims or store-listing keywords:

• find my parked car app
• parking meter reminder
• parking garage location tracker

Next evidence gates:

• Verify owned Google Search Console and Bing Webmaster property access, then collect the 28-day US baseline.
• Collect US App Store public rank/review evidence and owned territory analytics when available.
• Cluster seed intents by user job and funnel stage; keep brand, competitor, and problem-language clusters distinct.
• Score up to three countries only after baseline coverage reaches 60%; select at most one market scoring 65 or higher.
• Draft transcreated metadata and materially distinct content only after native-language and legal/safety review.

Stop gate: no paid-provider spend, automatic country redirects, thin country pages, localization publication, deployment, or store submission is authorized by this packet. Unavailable evidence remains unknown, never zero demand.