Brief: Build The SG/Sentinel Website

Summary

The brief that scoped this site: turn ~57,000 words of design briefs plus a working implementation into a clear, credible, navigable static site. It fixes the narrative spine (problem → idea → architecture → proof → method → what's next), the content rules this site follows — accuracy above all, don't overclaim status, real code only, real commands only, no invented metrics — and the definition of done, including the hand-built architecture SVG and the precise live-AWS caveat. Captured here for the same reason everything else is: the provenance discipline applies to the site itself.

Key concepts

• The six narrative beats — the front page follows the spine in order
• The content rules — precision over marketing — the status language everywhere on this site
• The definition of done — how the site is validated and released

Key ideas

• "Credibility with this audience comes from precision, not marketing."
• "Use real code, never invent snippets" — every excerpt on this site is verbatim from the snapshot.
• "Build the site from the packet, keep it honest, and let the architecture do the talking."

On this site

Became this site; the engineering page documents how its rules are enforced by the validate gate and CI.

Read the document