Correction and update — September 15, 2026. The original article described a zero-JavaScript site without analytics or a newsletter. The current application includes a browser-side Workbench, Vercel Analytics, and a link to the hosted Buttondown signup page. This revision replaces the earlier description with what we can verify in the application source. The structured stack record is a separately dated snapshot and may lag this article.
A static site with a small interactive tool
The production application uses Astro. The current dependency lockfile resolves Astro 7.3.2. Pages are built as static output and hosted on Vercel; approved changes merged to the production branch trigger deployment.
Articles are Markdown content collections. Company stack records are JSON files validated against a schema during our checks. The site builds those records into browsable pages. This setup gives the small dataset version history and reviewable diffs without requiring a runtime database.
The Workbench runs planning rules in the browser. It organizes user-provided answers into a pilot review and supports copy, Markdown export, and print. Its form answers are not sent to a model or saved by the Workbench. Page-visit analytics are separate. Filling out a brief does not validate the user’s answers or establish production readiness.
What is connected, and what is still unverified
| Component | What the source establishes | Limit |
|---|---|---|
| Astro | Static build configured, with content collections | This does not mean every page is JavaScript-free |
| Vercel | Hosting integration and Analytics component | Analytics collection quality and dashboard reporting have not been audited here |
| Git and JSON | Versioned records with schema validation | A valid schema does not establish factual accuracy or freshness |
| Buttondown | Signup form targets the configured subscription endpoint | Successful subscription and email delivery have not been verified end to end |
| Workbench | Browser-side planning and export controls | A file-download request is not proof that the user saved a file |
Research and editorial work
AI tools assist research, drafting, development, and review. Human review remains part of the publishing process. This article does not claim that every publication passed a fixed four-agent pipeline, or that an automated check establishes factual correctness.
The practical standard is to keep source-backed observations distinguishable from editorial recommendations, show uncertainty, and correct material errors. Workflow guides describe proposed approaches. They are not records of customer deployments or results from our own platform tests unless explicitly identified as such.
Evidence for this update
This is a first-party source review of the production application’s package lockfile, Astro configuration, layout, newsletter component, Workbench generator, and build workflow. Checked September 15, 2026. The application repository is private, so readers cannot independently inspect those files through this article; that is a limitation of this account.
The public stack record retains its own evidence and snapshot date. We have not silently changed that record to match this article. Questions and corrections can be sent to kyle@thetechstack.com.
Next checks
Verify the newsletter from signup through delivery, check the analytics reporting against expected page visits, and keep the structured record aligned with documented changes. We make no current claim about infrastructure cost, publishing cadence, or measured audience impact.