How to set a required secret before your first run
An Application's Secrets page lists nothing until a policy that declares the secret is published, so a required secret could not be set in advance. The GitHub guide now shows the way through: publish paused, set the secret, then resume.
Thanks to a design partner
Read more: docs.proof.computer/liskov/get-started/github
For agents
- Record id
2026-11-21-docs-set-secrets-before-first-run- Type
improved, not breaking- Live since
2026-11-21T16:57:27Z- Surface
- Application Secrets page; proof liskov application publish / resume
- Before
- Undocumented: a secret value can be set only after a policy declaring it is published, and an unpaused first publication runs before the secret exists.
- After
- Documented route: add
--paused --reason "set secrets before first run"to the publish command, set the value on the Application's Secrets page, then runproof liskov application resume <app> --reason "secrets set" --yes. - Action
- Use the paused-publish route for any Application whose manifest declares a required secret.
- Unaffected
- Secret storage and delivery behaviour (unchanged)