Settings
The settings file holds the Settings a Startup sets that its root file does not, inherited nearest-holder first.
settings.mdx holds the Settings a Startup sets that startup.ts does not. A Setting is inherited from its nearest holder, Studio to Startup to Product, unless a file sets its own.
leaseline/startup.tssettings.mdxSettings not set in startup.ts
Reference
MDX, frontmatter only. Each key is a Setting, and its value overrides the inherited one.
| Key | Type | Holds |
|---|---|---|
trial | duration | How long a trial runs before the first charge, such as 14d |
signup | email | workEmail | magicLink | keyless | apiKey | oauth | agentIdentity | How a buyer signs up to the Startup's App |
priceMove | number | The largest Price change, as a share, an Agent makes without an Approval |
delayWindow | map | How long each one-way Verb waits before it runs, by Verb |
locked | list | Settings no Product below may change |
Examples
Minimal
---
trial: 30d
---Leaseline
---
trial: 30d
signup: magicLink
priceMove: 0.1
delayWindow: { refund: 1 business hour }
locked: [signup]
---What it builds
The StartupBuilder compiles each key into one Setting value on the Startup.
- a
Settingper key, withlockedwhere listed - a Change when a value moves, so every Setting has a history
- an Approval when a later Action exceeds a Setting such as
priceMove
Good to know
- A key set in both
startup.tsandsettings.mdxfails the parse check, so every Setting has one home. - A Studio sets defaults for every Startup below it in
studio.ts. - Policies are rulings on how numbers are computed, in the policies file. Settings are choices.