Auth Patterns — Following Astro Knots Conventions in a Rsbuild + Module-Federation Shell

Augment-it isn't a pure Astro site — the shell is Rsbuild + Svelte + Module Federation, and the backend is NATS-fronted microservices with a workspace-service holding session tokens. But the Astro Knots auth conventions (session cookie, middleware gate, public allowlist, never-prerender-a-gated-route) still encode the right discipline. This blueprint translates each rule into the augment-it architecture so the audit-trail and the failure modes stay legible across the two stacks.

Path

blueprints/Auth-Patterns-following-Astro-Knots-Patterns.md

Authors

Michael Staton

Augmented with

Claude Code on Claude Opus 4.7 (1M context)

Auth Patterns — Following Astro Knots Conventions

[[../specs/Initial-User-Experience]] — the auth gate is the first surface the new user touches
[[Augment-It-as-Working-App-and-Architecture-Demo]] — the auth pattern is itself one of the things the architecture-demo identity should make legible
[[Module-Federation-Rsbuild-Dev-Loop-Gotchas]] — federation mechanics the workspace-token discipline rides on
[[../specs/Shell-and-Micro-Frontend-UX-Coherence]] — auth affordances belong to the same coherence audit (no Hidden/Dead/Misnamed gates)
The astro-knots skill’s Auth-gated routes must not be prerendered section is the canonical Astro Knots reference; once a referenceable blueprint exists in the parent monorepo, link it from here

Auth Patterns — Following Astro Knots Conventions

Related