documentation.pointsav.com goes live — 2026-04-27

@@ -8,22 +8,27 @@ type: topic
content_type: topic
index_group: knowledge-and-editorial-applications
status: active
quality: complete
audience: vendor-public
bcsc_class: public-disclosure-safe
last_edited: 2026-08-24
language_protocol: PROSE-TOPIC
last_edited: 2026-09-05
editor: pointsav-engineering
paired_with: documentation-pointsav-com-launch-2026-04-27.es.md
cites: [ni-51-102, np-51-201]
---

`https://documentation.pointsav.com` went live with TLS at 16:25 UTC on 2026-04-27. The deployment serves the PointSav engineering wiki over a Let's Encrypt certificate valid through 2026-07-26, with automatic renewal enabled.
`https://documentation.pointsav.com` went live with TLS at 16:25 UTC on 2026-04-27. The deployment served the PointSav engineering wiki over a Let's Encrypt certificate, with automatic renewal enabled. This article is the historical record of that launch day; it does not describe the wiki's current content.

---

## What serves today
## What launched on 2026-04-27

Four placeholder TOPIC pages render at the public URL. `/wiki/welcome` is the landing topic, explaining the public-preview status. `/wiki/sample-article` exercises the rendering chrome — table of contents, per-section edit pencils, footer block with categories, masthead band, collapsible left-rail table of contents, language switcher, and the [[wikipedia-leapfrog-design|Wikipedia layout conventions]]. `/wiki/sample-forward-looking` exercises the forward-looking-information cautionary banner and cites both [ni-51-102] and [np-51-201]. `/wiki/sample-citations` exercises inline citation references including the clause-reference form.
At launch, four placeholder TOPIC pages rendered at the public URL — a deliberate placeholder posture (see below), not the corpus in its current form. `/wiki/welcome` was the landing topic, explaining the public-preview status. `/wiki/sample-article` exercised the rendering chrome — table of contents, per-section edit pencils, footer block with categories, masthead band, collapsible left-rail table of contents, language switcher, and the [[wikipedia-leapfrog-design|Wikipedia layout conventions]]. `/wiki/sample-forward-looking` exercised the forward-looking-information cautionary banner and cited both [ni-51-102] and [np-51-201]. `/wiki/sample-citations` exercised inline citation references including the clause-reference form.

Beyond article-rendering paths, the wiki serves: `/healthz` (liveness check); `/` (index page listing all articles); `/search?q=` (full-text search over the on-disk Tantivy index); `/feed.atom` (RFC 4287 syndication feed); `/sitemap.xml`; `/robots.txt`; and `/llms.txt`. There is no edit route and no collaborative-editing feature — the engine has no write surface at all; every article is edited in its source git repository and picked up on the next render.
Beyond article-rendering paths, the wiki served the same operational routes it serves today: `/healthz` (liveness check); `/` (index page listing all articles); `/search?q=` (full-text search over the on-disk Tantivy index); `/feed.atom` (RFC 4287 syndication feed); `/sitemap.xml`; `/robots.txt`; and `/llms.txt`. There was no edit route and no collaborative-editing feature at launch — the engine has no write surface at all; every article is edited in its source git repository and picked up on the next render.

The corpus has since grown substantially: a 2026-09-04 baseline recorded 644 documents across 15 categories on this same wiki, including the `applications` category this article itself belongs to. What follows describes the launch-day placeholder state, not the wiki's current content.

---

@@ -33,7 +38,7 @@ Beyond article-rendering paths, the wiki serves: `/healthz` (liveness check); `/

**systemd unit.** The unit runs the binary as a dedicated unprivileged system user (`local-knowledge:local-knowledge`) on port 9090. Hardening flags include `NoNewPrivileges=true`, `ProtectSystem=strict`, `ProtectHome=true`, and `PrivateTmp=true`, with `ReadWritePaths` scoped to the service's own state directory and `ReadOnlyPaths` scoped to its configuration and content sources.

**Content directory.** The production `--content-dir` flag points at a four-file placeholder subdirectory. The legacy 30+ TOPIC corpus is held in the parent directory pending editorial refinement.
**Content directory.** At launch, the production `--content-dir` flag pointed at a four-file placeholder subdirectory, with the then-30+-article legacy TOPIC corpus held in the parent directory pending editorial refinement. That refinement has since completed and the flag now points at the ratified, substantially larger corpus described above.

**nginx.** Port 443 terminates TLS and reverse-proxies to the loopback service on port 9090. Port 80 serves only the Let's Encrypt HTTP-01 challenge and issues a 301 redirect to HTTPS.

@@ -45,9 +50,9 @@ Beyond article-rendering paths, the wiki serves: `/healthz` (liveness check); `/

## Placeholder posture — disclosure rationale

The four-file placeholder subtree was authored specifically to enable the public TLS launch without exposing the legacy TOPIC corpus. The legacy corpus carries known editorial debt: forward-looking framings without cautionary-banner discipline per [ni-51-102], and vocabulary items not compliant with the [[compliance-and-continuous-disclosure|continuous-disclosure posture]] for each substantive edit.
The four-file placeholder subtree was authored specifically to enable the public TLS launch without exposing the legacy TOPIC corpus. At the time, the legacy corpus carried known editorial debt: forward-looking framings without cautionary-banner discipline per [ni-51-102], and vocabulary items not yet compliant with the [[compliance-and-continuous-disclosure|continuous-disclosure posture]] for each substantive edit.

The placeholder posture collapses that surface. Four files, written to be clean from the first line, expose only structural prose (no business-outcome claims), only verified facts, and forward-looking framings only inside the explicit demonstration topic where the cautionary-banner pattern is the point of the page. The eventual publication of the refined corpus becomes one material-change event rather than many.
The placeholder posture collapsed that surface. Four files, written to be clean from the first line, exposed only structural prose (no business-outcome claims), only verified facts, and forward-looking framings only inside the explicit demonstration topic where the cautionary-banner pattern is the point of the page. The intent was for the eventual publication of the refined corpus to land as one material-change event rather than many.

This pattern is generalizable. Any deployment that depends on a corpus being editorially ready can launch with a placeholder content tree, swap `--content-dir` once the corpus is ratified, and avoid an all-or-nothing flip. The [[source-of-truth-inversion|source-of-truth inversion]] — the Markdown tree is canonical; the running binary is a view — makes this swap a single service reload.

@@ -57,7 +62,7 @@ This pattern is generalizable. Any deployment that depends on a corpus being edi

The following are planned or intended, not committed. Cautionary language applies per [ni-51-102] and [np-51-201]. Material assumptions include the continued availability of the workspace VM and sustained editorial-pipeline activity.

The editorial pipeline is intended to refine the legacy TOPIC corpus in a separate pass. The expected outcome is a ratified content tree to which `--content-dir` may be swapped, producing a single material-change disclosure event.
The editorial-pipeline refinement this article originally anticipated has since occurred: the ratified corpus described above replaced the placeholder tree via a `--content-dir` swap, consistent with the single-swap pattern this article describes below.

The wiki engine is planned for further development through phases covering git2 commit-on-edit, a wikilink graph, a content-addressed federation layer, an MCP server, and a linter that hardens disclosure-class invariants.

@@ -65,7 +70,7 @@ The wiki engine is planned for further development through phases covering git2 

## Verification

The following checks are reproducible from any external host with TCP/443 connectivity:
The following checks were reproducible from any external host with TCP/443 connectivity at launch, and the routes remain live today (only the certificate dates below are launch-day snapshots, not a current, reproducible result — see the note beneath the block):

```
$ curl -I https://documentation.pointsav.com/healthz
@@ -87,6 +92,8 @@ notBefore=Apr 27 16:24:00 2026 GMT
notAfter=Jul 26 16:24:00 2026 GMT
```

The certificate dates above are the original launch-day issuance window, kept as the historical record. Let's Encrypt certificates renew automatically on a 90-day cycle (per the automatic renewal noted in the opening paragraph); a live check today will show a materially later `notAfter` date, not the one printed here.

---

## See Also