feat(002): launch content, docs stubs, registry-derived status ladder#1
Merged
Conversation
Replace the spec-001 placeholders with the real launch copy and docs seed for stagecraft.ing (spec 002-launch-content). - Index: hero, the Specify/Stamp/Operate/Verify loop, the product-family list, a for-agents block, and a live-registry pointer. Every capability claim carries a maturity chip and a receipt link resolved at build time from the spec that governs it, so the copy cannot read louder than the source. - Status ladder (M1-M5): rolled up from the baked registry, not hardcoded. At build time M1 is shipped (the EnRaHiTu chassis), M2 in progress (the template contract; the born-with certificate is still pending, so it is not claimed proven), M3-M5 planned. - Docs: an index over three stubs (What is EnRaHiTu, The template contract, Self-hosting the control plane), each summarizing and linking its source. - Fix spec 002 establishes (Astro-era src/content to real app/ paths) and mark it complete; regenerate the derived shards. app/routes.ts and react-router.config.ts are spec-001 scaffold files, edited only to register and prerender the new docs route; that coupling drift is waived in the PR body rather than by re-authoring complete spec 001.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spec 002: launch content
Implements
002-launch-contentend to end: the real index copy and the docs seed, replacing the spec-001 placeholders. No new build toolchain.What's here
app/routes/_index.tsx): hero, the Specify / Stamp / Operate / Verify loop, the product-family list, a for-agents block, and a live-registry pointer. Every capability claim carries a maturity chip and a receipt link resolved at build time from the spec that governs it, so the copy cannot read louder than the source.app/lib/milestones.ts): rolled up from the baked registry, never hardcoded. At build time: M1 shipped (the EnRaHiTu chassis,enrahitu/001to008), M2 in progress (the template contract; the born-with certificate is still pending, so it is not claimed proven), M3 to M5 planned. The build fails loud if any referenced spec id stops resolving.app/routes/docs.tsx+app/routes/docs.$slug.tsx+app/lib/docs.ts): an index over three stubs (What is EnRaHiTu, The template contract, Self-hosting the control plane), each summarizing and linking its source, with an honest maturity marker.establishescorrected (Astro-erasrc/content/to the realapp/paths) and marked complete; derived shards regenerated.Verification
npm run typecheckandnpm run buildclean; every route prerenders (including the three new docs pages); zero off-origin resource loads in the built output.compile,index check,lint --fail-on-warn, andcouple(with the waiver below).Spec-Drift-Waiver: app/routes.ts and react-router.config.ts are spec-001 scaffold files, edited here only to register and prerender spec 002's new docs stub route (app/routes/docs.$slug.tsx). The changes are route wiring driven entirely by spec 002; spec 001's scaffold design is unchanged, so the complete spec 001 is not re-authored (per .claude/rules/adversarial-prompt-refusal.md).