SUBSTELLAR — integrate the expanded creative direction into the website work

Please revisit your current website plan using the attached SUBSTELLAR_Overview_Edition.zip. This is a complete, usable snapshot of SUBSTELLAR's creative and product direction: Illustrated Overview 03, with Reader Update 04. It may materially change assumptions in your existing plan, including the roadmap and the rest of the website.

The documentation agent is maintaining this material in a separate workstream. Further review tools, editorial consolidation, and selected visual detail may follow. You do not need to wait for those refinements: there is already enough content and artwork here to inform the website's structure, content, presentation, and next build slices. Make your integration easy to update when a newer snapshot arrives.

INPUT AND READING ORDER

Extract the attached ZIP. Start with substellar/WEBSITE_AGENT_HANDOFF.md, then substellar/README.txt and substellar/index.html. The complete text is also available in substellar/sources/complete-direction.txt. Use substellar/sources/edition-manifest.json for the edition, source identities, scope, and status distinctions. The handoff guide maps the other registers and asset folders.

This snapshot contains 90,735 source words across 45 chapters, all ten completed document slices at illustrated-overview depth, and 50 distinct visuals, including 15 confirmed artwork sheets and 19 editable SVG diagrams/interface sheets. The original artwork, lightweight display images, original approved DOCX, full text sources, structured catalogues, planning registers, and website rebuild files are included.

Do not limit your reading to the overview or treat this as a file to add to a download page. Work through the full source material in manageable sections, and record anything you have not yet reviewed before drawing broad conclusions.

WHAT I WANT YOU TO DO

1. Inspect your actual website repository, current implementation, and existing plan. Establish what is built, what is only planned, and which assumptions this direction changes. Do not assume a feature is implemented because it appears in the document or in concept art.

2. Reconcile the direction across the whole website. Assess its implications for the homepage and project explanation; information architecture and navigation; worlds, layers, exploration, and progression; industry, machines, materials, and equipment; settlements, creatures, and encounters; Tier 1 space systems; the roadmap; the documentation/reference experience; and the visual library. Recommend the pages, relationships, and interactive explanations that help visitors understand SUBSTELLAR. Avoid creating a separate page for every catalogue entry without a clear reason.

3. Produce a source-to-website mapping. For each proposed page or feature, identify the relevant source chapters/IDs and artwork IDs, its purpose and audience, its status in the existing website, and what work remains. Distinguish the game/product direction, the document-production backlog, and the website-build backlog. Keep speculative features and concept imagery clearly labelled in visitor-facing content.

4. Revise the website plan and roadmap presentation. Show which previous assumptions should be kept, changed, deferred, or removed, and why. Prioritise small, coherent website slices with dependencies and concrete completion criteria. Recommend what can be built immediately from the supplied content and what depends on an unresolved decision. Do not invent release dates or convert planned game features into delivery promises.

5. Set up a maintainable integration in your existing repository. Preserve the supplied snapshot, original assets, identifiers, and relative references in a versioned source area appropriate to the project's conventions. Derive website content from it, and document how a later snapshot can be compared and incorporated. Keep the full reference material accessible even where visitor-facing pages use shorter explanations.

6. Record findings for the documentation maintainer. Save the source mapping, changed assumptions, unresolved decisions, proposed source corrections, and website backlog in the repository, using its existing reporting conventions where possible. Cite source paths, section IDs, and artwork IDs so the documentation agent can reconcile your findings precisely. Report your actual saved paths and commit/branch if applicable; do not assume another agent can access your workspace automatically.

AUTHORITY AND WORK BOUNDARIES

The documentation agent remains the maintainer of the creative-direction source. Use this material as the current design reference while preserving its approval distinctions: the original text and supplied artwork are confirmed, while some later specifications and numerical choices remain proposals or expansions for review. Where sources conflict or leave a material choice open, identify the conflict, recommend a resolution, and retain traceable evidence. Do not silently overwrite the approved source or turn a proposed dimension, recipe, or balance value into a confirmed decision.

Preserve and reuse the supplied artwork. Use current_visual_coverage.json together with the historical artwork register: the twelve interface layouts and two opening boards now have delivered coverage. Overview boards are representative concepts, not final views of every model or operating state. Do not generate more images in this pass; report targeted gaps instead.

This task concerns the website and its planning/content integration. Actual mod development still requires my explicit BUILD approval. Inspect the website directly, and keep game implementation status unverified unless you have evidence from the actual mod project. Work within the website-building and publishing permissions already established in our conversation.

START NOW

Begin with the source and repository audit, then deliver a concise account of what changes for the website, the proposed structure, and the prioritised integration plan. Continue with reversible website work that is already authorised. Do not wait for every future document illustration, and do not stop at acknowledging the attachment. Ask me only for the few choices that materially affect the outcome. Before reporting website interaction as verified, test navigation, responsive layouts, and artwork presentation in your supported browser environment; this snapshot includes static and logic checks but no browser-interaction verification.