Repository navigation
Conversation
…a launch The ios-app template's acquisition section permitted a pricing experiment without saying when one is run. Installs move on the day the price moves, not on the day a build ships, so making an app free from the start spends the only event it has: the section now plans a cut as a launch, names what must be true the day before, and says the install figure is read from the sales report rather than from a chart.
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.
Closes #2788
What changed.
emrg/server/ios_app_prompt.md§5.2 — the section that owns acquisition and pricing at low install volume — now says that a price change is a distribution event rather than a setting, and gives the plan that follows: list at a small non-zero price first, choose the day for the drop, and work that day like a release, because a launch has one day and an initial state has none. It names what must already be true the day before (the fields the platform freezes live on a released version, the page complete, the territories open), and it says the install figure is read from the sales report rather than reconstructed from a chart, a day the report does not answer for being a day of zero.Why in that section. §5.2 already carried the other half of the subject — installs are the only hard number, and a pricing experiment is judged by the installs it produces, "including a decision to make the app free". Read alone, that sentence is permission to ship a price and wait, which is what a task then does. The new paragraph is the missing second half, added where the subject already lives rather than in a second home: this template's own rule is that a fact lives in exactly one place.
The guard.
tests/test_prompt_templates.pypins §5.2 through the file's own_bounded_sectionhelper, with both ends positively controlled, so a renamed heading fails instead of widening the region to the rest of the file. The companion control strips each pinned phrase in turn and shows the section then reads as missing, rather than passing on a region it never meant to read. The third assertion is the one-home rule: the sentence "A price change is a distribution event" appears exactly once in the template.Readings taken on this tree. The guard reddens when the rule is removed from the shipped file and passes when it is present, measured by node id in both directions. Full suite: 6204 passed, 36 skipped.
python -c "from emrg.client.app import run_client"andpython -m emrg --helpboth run. No workflow file is touched, so the actionlint gate has no subject here.Scope. This template ships to every installation, so nothing specific to one installation is written into it: no price, no account, team or vendor identifier, and no statement about who authorizes spending. The rule is the general method only, and the installation-side block that also states it is left where it is — reported rather than edited, per the prompt-drift rules.