Persists the branding/commercial/infrastructure work (previously only in chat and
on the live site) into version control.
What changed:
- docs/naming.md: due-diligence and the decision to brand the product Nightjar
(OpenScribe domain/GitHub/trademark collisions; alternatives screened; why Nightjar).
- docs/hosted-service.md: the commercial model - plan tiers (Self-host / Cloud
Starter / Cloud Pro / Private), indicative pricing, backend mapping, and the
build-to-sell roadmap (metering, billing, provisioning, DPA).
- docs/infrastructure.md: backend infra plan. Primary option = self-host on the
3x Minisforum MS-02 cluster (one with an RTX 3050 6GB) fronted by a Cloudflare
Tunnel, with node roles, the 3050 capacity reality, caveats, and a Hetzner cloud
fallback. Provision-later.
- site/: reproducible marketing-site source - block content for all 11 pages
(rebranded to Nightjar), the navigation, the Contact Form 7 config (honeypot),
the ApisCP SOAP helper (tools/apiscp.php, no secret), and a README on how the
WordPress site is built and managed via the API.
- state/: DECISIONS (Nightjar rebrand, hosted service, MS-02 backend), PROJECT
(brand + commercial section), TODO (rename decision, trademark, mailbox, pricing,
hosted-service build, infra provisioning).
Why:
- User asked to save everything to the repo. Captures the product rebrand, the
commercialisation plan, and the infrastructure decision so a cold session has the
full picture.
Notes:
- The repo is still named `openscribe`; the product/brand is Nightjar. A full
codebase rename is deferred (tracked in TODO + docs/naming.md).
- No secrets committed: the ApisCP API key is read from a local scratch file, never
the repo.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
