Business goal
Put the paid-validation funnel on a stable public HTTPS URL so the first 20 target users can use it and purchase-intent data survives restarts.
Requirements
- Run the existing Node service on a public HTTPS origin.
- Configure the server to listen on the host and port required by the provider.
- Mount a private persistent volume for lead, event, and sales JSONL files.
- Keep
.data, source code, and Git metadata unreachable over HTTP.
- Add a health check and a documented backup/export procedure.
- Put the public URL in the repository homepage and first-sale outreach script.
- Do not expose deployment tokens or personal lead data in GitHub Actions logs.
Acceptance criteria
- The free analysis and paid-intent flow work on the public URL.
- A test intent survives a service restart and is deleted after verification.
- Sensitive paths return 404 from the public origin.
- GitHub CI and a post-deploy smoke check pass.
- Monthly hosting cost and rollback steps are documented before enabling the service.
Blocker
No deployment-provider account, authenticated CLI, or repository deployment secret is currently available. Provider selection may create an account, accept external terms, and incur recurring cost, so it requires owner authorization.
Business goal
Put the paid-validation funnel on a stable public HTTPS URL so the first 20 target users can use it and purchase-intent data survives restarts.
Requirements
.data, source code, and Git metadata unreachable over HTTP.Acceptance criteria
Blocker
No deployment-provider account, authenticated CLI, or repository deployment secret is currently available. Provider selection may create an account, accept external terms, and incur recurring cost, so it requires owner authorization.