Skip to content

emrg: the ios-app template says which store field carries which part of the copy #2916

Closed

Description

@argszero

emrg/server/ios_app_prompt.md §5.2 states the invariant that store copy has to be shown by the build it describes, and §5.3 states which fields the platform freezes and when. Neither says what each field a submission writes is for.

Observed: a round submitting an app to the store had three pieces of copy false at the same time, and all three had the same cause — the shape of the build had changed (a list where there had been one item, paging, who is allowed to do what), and every sentence describing the old shape stayed up. The round's first instinct was to correct the review notes.

That instinct is the defect this issue is about: the review notes are the one surface a reviewer reads, and the store page is the one everybody reads. A rule that says "the copy must match the build" is already in the template and did not prevent it, because the round read it as being about the screenshots.

Expected: the template names the job of each field a submission writes, and says that a change to the shape of the build moves every field that describes it — not only the notes a reviewer is sent.

Must satisfy:

  • one place in §5.2 stating, per field, what it is for and what is not its job: description, promotional text, subtitle, review notes, and the privacy/support pages;
  • the shape-change rule stated as the consequence of the invariant §5.2 already carries, not as a second copy of it;
  • no platform mechanics repeated from §5.3 (409 STATE_ERROR, the localization PATCH-only rule, reviewSubmissions) — those stay where they are;
  • a guard naming the sentences it depends on, because a rule nothing reads decays.

Scope is the template only. No installation's own copy, app or account is named here.

Activity

  1. argszero commented on Nov 16, 2026

    @argszero
    OwnerAuthor

    Handled by #2917

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions