Owner Guide¶
The owner guide is the shortest path to what matters right now.
Use this page for¶
- What is already done
- What is still blocked
- What lies ahead
- Which services need accounts or subscriptions
- Which API keys or secrets need to exist before future work starts
Reading order¶
- Check what is complete.
- Check what is in progress and what comes next.
- Scan the services and keys tables before you plan any new work.
The generated section below is the source-of-truth summary pulled from the status file.
Generated from the Bid Signal owner-wiki registry. Do not edit this section directly.
Plain-language summary¶
If you only read one page, read this one. It tells you what has already shipped, what still blocks progress, and what accounts or secrets you may need later.
What is complete¶
- Status source and registry live in this repo
- Static wiki generation runs from the local repo
- MkDocs builds successfully in strict mode
What is in progress¶
- Bid Signal persistence migration
What comes next¶
- Implement repository-backed actions in bid-signal
- Decide whether any owner-private content will be added behind access protection
What comes later¶
- Bid Signal Stripe verification
- Bid Signal live source adapters
- Deploy automation if the site should publish automatically on commit
Services to sign up for or confirm¶
| Service | Why it matters | Status |
|---|---|---|
| GitHub | Source control, commit history, and repo-connected Pages deployment | already in use |
| Static host | Host the public or private owner wiki site | optional |
API keys and secrets to plan for¶
| Key or secret | Why it matters | Status |
|---|---|---|
| GitHub deploy credential | Only needed if you add a GitHub-based publishing workflow beyond repo-connected hosting | optional |
| Stripe secret key and webhook secret | Needed for Bid Signal backend verification work, not for the owner wiki itself | future product work |
| Upstream source API keys | Needed only when live source adapters are implemented in bid-signal | future product work |
Practical reading¶
The owner wiki itself does not need a runtime API key for the current build-only workflow. Any publishing credential is only needed if you later add a specific hosting workflow.