This is a source-to-page map, not a completion receipt or an audit result. It explains where each original section is represented and where the raw structured/image artifacts belong. The ten supplied files remain at the repository root; prose in this wiki reorganizes their meaning instead of duplicating the original documents as pages.
Line ranges in the original maps below refer to the supplied September 6 files. Heading names are normalized to plain text for readability. The separately dated September 10 map follows them; preparing this foundation does not refresh either source’s external claims.
Corpus inventory
| Original file | Type and role | Explanatory destination |
|---|---|---|
CHEATSHEET.md | Dated public-platform research and practical boundaries | platform, workflow, state-and-trust, costs-and-rights, experience-and-acceptance, evidence-and-limits |
PLAN.md | Condensed reusable execution checklist, not a completed app plan | workflow, platform, costs-and-rights, state-and-trust, experience-and-acceptance, evidence-and-limits |
PRD.md | Smallest-sufficient-stack decision and acceptance contract | scopes, three scope pages, experience-and-acceptance, evidence-and-limits |
websim-full-stack-poster.json | Capability inventory, layout decision, generation and inspection record | artifact-atlas > Full-stack record, platform |
scoped-posters.json | Global design rules, three node/edge/copy/check records, provenance | artifact-atlas > Scoped record, scopes, three scope pages |
websim-quickstart-poster-astra.webp | Creator workflow illustration | Embedded in workflow, explained in artifact-atlas > Quickstart illustration |
websim-full-stack-poster-grok.png | Grouped capability inventory without arrows | Embedded in platform, record explained in artifact-atlas |
scope-1-play-now.png | One browser’s local loop | Embedded and given a text equivalent in scope-1-play-now |
scope-2-keep-what-matters.png | Draft/access/records separation | Embedded and given a text equivalent in scope-2-keep-what-matters |
scope-3-play-together.png | Two visitors and shared project | Embedded and given a text equivalent in scope-3-play-together |
CHEATSHEET.md section map
| Lines | Original section | Coverage |
|---|---|---|
| 1–4 | Title, research date, D/O/R/? key | index > How to read claims, evidence-and-limits |
| 5–10 | The 30-second answer | index, platform, workflow: platform model and smallest-useful-loop default |
| 11–22 | What old tutorials miss | evidence-and-limits > Evidence chronology, costs-and-rights > Choose the bill before the build, workflow > Improve and recover: Build, frameworks, roles, reconnects, Merge/group build, credits, /clear |
| 23–40 | The complete publicly knowable stack | platform: all 13 inventory rows, including portability and unknown infrastructure |
| 41–57 | Architecture you actually need to understand | platform > Visitor browser: creator/visitor/community flow and optional capabilities, explicitly not deployment topology |
| 58–72 | Start → ship, without getting lost | workflow: all eight steps and the device-code authorization warning |
| 73–76 | Three copy/paste prompts introduction | workflow > Reusable prompt contracts: specifications, not compliance guarantees |
| 77–89 | First build | workflow > First build |
| 90–101 | Add persistence securely | workflow > Add persistence securely, state-and-trust > Identity is not authorization |
| 102–111 | Fix without wrecking everything | workflow > Repair without a rewrite |
| 112–121 | Pick the right state | state-and-trust > Choose a state lifetime: all five state categories |
| 122–132 | Three costs—not one free badge | costs-and-rights > Choose the bill before the build, workflow > Improve and recover: four cost/reward questions and efficiency order |
| 133–145 | Safety rules that matter | costs-and-rights, state-and-trust: visibility, uploads, license, remix rights, authorization, XSS, untrusted comments, automation restrictions |
| 146–161 | Ship gate | experience-and-acceptance > Release questions: all nine gate categories and source references |
| 162–172 | Stay or migrate? | costs-and-rights > Stay or migrate: four use cases and distinct ownership/rights/export boundaries |
| 173–189 | Triple-check record and remaining unknowns; closing doctrine | evidence-and-limits: provenance, chronology, rejected inferences, auth-gated prices, runtime limits and failed research-agent account; index for operating doctrine |
PLAN.md section map
| Lines | Original section | Coverage |
|---|---|---|
| 1–9 | Fenced request record | workflow: condensation request from CHEATSHEET, reusable checklist purpose; this map retains its accuracy/coverage/structure intent without turning the fence into page metadata |
| 11–18 | Title, checked date, claim key and default | index, platform, workflow |
| 19–45 | The whole stack—only the distinctions that matter; conceptual map | platform: all eight condensed groups and responsibility flow |
| 46–54 | Choose the bill before the build | costs-and-rights > Choose the bill before the build |
| 55–58 | Task-list wrapper and “Build small. Verify honestly. Ship deliberately.” heading | workflow explains the future checklist, not completed work; prose uses ordinary Markdown rather than raw task-list HTML |
| 59–73 | 1. Scope & start | workflow > Scope before implementation, workflow > Start and establish access: 1.1 audience/loop/checks/start and 1.2 budget/access/capability limits |
| 74–95 | 2. Implement the smallest complete experience | workflow > Implement the smallest complete loop, state-and-trust > Choose a state lifetime: 2.1 complete loop and 2.2 earned capabilities; every state-table category |
| 96–110 | 3. Protect people, content, and data | costs-and-rights, state-and-trust: 3.1 visibility/rights and 3.2 authority/untrusted content |
| 111–123 | 4. Improve without breaking the working version | workflow > Improve and recover, state-and-trust > Untrusted content and destructive actions: 4.1 targeted repair/recovery and 4.2 reviewed collaboration/destructive moderation |
| 124–143 | 5. Verify → publish → operate; wrapper close | experience-and-acceptance > Release questions, workflow > Shipping is a decision, not a poster label, costs-and-rights > Stay or migrate: 5.1 applicable release cases and 5.2 critical requirements/exit |
| 145–159 | One reusable prompt contract | workflow > One reusable change contract |
| 160–168 | Three-pass verification boundary and closing doctrine | evidence-and-limits > How the original research handled contradictions, evidence-and-limits > What remains unverified, index |
PRD.md section map
| Lines | Original section | Coverage |
|---|---|---|
| 1–8 | Title, date, recommendation, audience and package boundary | index, scopes: design recommendations, not an implemented product or private architecture |
| 9–22 | 1. Verdict and scope selector | scopes > Decision order and all three scope pages: minima, conditional additions, non-ladder rule and stop conditions |
| 23–49 | 2. Candid review of previous output | evidence-and-limits > Prior artwork rationale, not a new audit: all P0/P1/P2 themes, inferred reader costs and retained qualities; scopes > Product promise and non-goals for brainstorm triage |
| 50–61 | 3. Product contract and non-goals | scopes > Product promise and non-goals, workflow > Scope before implementation: promise, package/future success, exclusions and six future inputs |
| 62–75 | 4. Capability gates | scopes > Capability admission: all seven gates and managed-built-in/trust boundary |
| 76–92 | 5. Funday principles, applied without importing platform machinery | experience-and-acceptance > Experience principles: all eight requirements and numerical targets; external doctrine attribution without inventing wiki targets |
| 93–108 | All nine states considered; no nine-screen mandate | experience-and-acceptance > Nine reachable states: all states and N/A reasoning |
| 109–129 | 6. Acceptance contract for the future build | experience-and-acceptance > Acceptance cases: A1–A12, conditional applicability, no claim of passed checks |
| 130–137 | 7. Evidence and risk boundaries | evidence-and-limits > Evidence chronology, costs-and-rights, state-and-trust: build/runtime funding, multiplayer/data limits, assets/privacy, rights and safety sources |
| 138–146 | 8. Implementation handoff | workflow: six steps from visitor/loop through capability choice, targeted implementation, creator publication and stopping |
| 147–155 | 9. Package verification and limits | evidence-and-limits > Package provenance and limits, artifact-atlas: source deliverables, artwork requirements, unestablished outcomes and failed delegated-writer account |
Structured-record coverage
| Record paths | Human-facing explanation |
|---|---|
Full-stack /title, /source, /scope, /date, /image | artifact-atlas > Full-stack record preserves identity, research date, scope and source/image relationship |
Full-stack /actualProvider, /actualModel, /requestedProvider | Actual xAI/Grok provenance distinguished from requested provider |
Full-stack /zones/*/name, /zones/*/layers/* | artifact-atlas > Five zones plus every layer in platform |
Full-stack /edges, /layoutDecision, /verification, /constraints/* | Empty edges, intentional non-topology layout, attributed inspection/rejected draft and all four constraints in artifact-atlas > Full-stack record |
Scoped /title, /date, /source/*, /kind | artifact-atlas > Scoped record identifies recommendations, not runtime configuration |
Scoped /imageProvenance/*, /verification/* | artifact-atlas > Provenance and inspection fields: requested/actual provider, model, PNG/dimensions/method, three edge counts, S3 copy decision and limits |
Scoped /globalRules/* | artifact-atlas > Six global rules, scopes |
Scoped /scopes/*/id, /title, /filename, /question, /decision, /composition | artifact-atlas > Anatomy of each scope record and the three individual scope pages |
Scoped /scopes/*/nodes/*, /edges/*, /copy/*, /checks/* | Individual scope-page text equivalents and declared-edge tables; exact copy/check arrays retained in the linked JSON |
In the last two rows, fields following /scopes/*/id share the /scopes/*/ prefix. The records can be downloaded from artifact-atlas without interpreting JSON to understand the concepts.
September 10 starter source coverage
Read-only source root: /home/loca/dev/simp-research-starter/websim-starter; supplied commit: d12614a (not independently checked here). Repository-local STARTER_CORPUS_MAP.yaml supplies the machine-readable inventory, section locators, conflict register and fusion map. These are provenance paths, not live public downloads. The September 10 CHEATSHEET.md below is not the September 6 repository-root file and must never overwrite it.
The inventory records 168 files / 34,800,940 bytes: five root research/HTML files; eight source files; one build script; one engine test file; one verification receipt; nine recording files; one narration manifest; 19 media files; 79 vendor files; and 44 dist files. Physical media totals are 101 images (42 PNG, 3 JPG, 4 WebP, 52 SVG) and nine MP3s; embedded slots are not extra files. artifact-atlas > September 10 local demonstration inventory explains media identities, narration and the viewport/chapter matrix; evidence-and-limits > September 10 historical receipts and corrections preserves receipt limitations and corrected backup claims.
| September 10 source and lines | Mined substance | Integrated destination |
|---|---|---|
CHEATSHEET.md:1–49 | Evidence legend, verdict, three product lanes, lean starter/dependency admission | platform, scopes |
CHEATSHEET.md:51–91 | Base responsibilities, smaller alternatives, daisyUI/Bits ownership and composition | platform, experience-and-acceptance |
CHEATSHEET.md:93–133 | Six conceptual starter categories, engine selection, Threlte minimum/optional extras, DOM controls and lifecycle | scopes, scope-1-play-now, experience-and-acceptance |
CHEATSHEET.md:135–168 | Optional storage/content/audio/auth/AI capabilities, multiplayer distinctions, three AI boundaries and OMP loop | state-and-trust, platform, workflow |
CHEATSHEET.md:170–237 | Unexecuted setup/deployment menu, dated registry/peer snapshot, Node recommendation and licenses | workflow, platform, evidence-and-limits, artifact-atlas |
CHEATSHEET.md:239–277 | Reusable OMP brief, future ship checklist, research versus implementation | workflow, experience-and-acceptance, evidence-and-limits |
GAMING-NAKAMA.md:1–32 | Dated full-Nakama/minimal-glue recommendation and ownership diagram | platform, scopes, scope-3-play-together |
GAMING-NAKAMA.md:34–49 | Eight boundaries; authenticate/join/play/reconnect/record first playable loop | state-and-trust, scope-3-play-together, experience-and-acceptance |
GAMING-NAKAMA.md:51–60 | Primary-source references and no-runtime-proof boundary | evidence-and-limits, workflow |
Websim-Stax.html: ws-tour, ws-playground, ws-hood, ws-sources | Eight Darkroom chapters, recorded replay, preview/isolation policies, local save/lineage, same-page relay, transcript/glossary and instructional setup | artifact-atlas > Chapter knowledge, not runtime receipts, workflow, state-and-trust, evidence-and-limits |
Gaming-Stax.html: story-stage, cheat-sheet, boundaries, glossary; embedded chapter/art/provenance scripts | Eight gaming scenes, ownership rules, local referee, engine brief, corrected boundaries and embedded media | artifact-atlas, scope-3-play-together, state-and-trust, evidence-and-limits |
GamingStax_full-txt.bkp.html: hero-arena, conveyor, matrix, boundaries, starter-spec, glossary | Historical six-domain matrix, eight distinctions, playable-loop brief and vocabulary; superseded license/lifecycle/RPC wording and obsolete local links are qualified | evidence-and-limits > September 10 historical receipts and corrections, platform, scope-3-play-together |
websim-stax/src/ (eight files), build.mjs, test/engine.test.mjs, verification.json | Implementation/assembly lineage and historical test/verification scope, not new execution | artifact-atlas, evidence-and-limits |
websim-stax/recordings/{pomodoro,snake,tictactoe}/{meta.json,v1.html,v2.html} | Three prompt/follow-up pairs, six replay HTML artifacts and three metadata records; not the later three approaches | artifact-atlas |
websim-stax/narration/chapters.json, media/ | Eight chapter transcripts, full track/eight clips, cues/provenance and four PNG/WebP artwork pairs | artifact-atlas, evidence-and-limits |
websim-stax/dist/ | Media-stripped audit-projection.html, 41 historical proof images, proof/print.pdf and proof/blueprint.json | artifact-atlas, evidence-and-limits |
websim-stax/vendor/ | 24 daisyUI CSS files, 52 Lucide SVGs, both complete LICENSE files and LICENSES.txt; third-party attribution retained | artifact-atlas > Third-party vendor attribution, evidence-and-limits |
This accounts for all 11 HTML files: three root demonstrations/backup, the source shell, six replay versions and one audit projection. Their readable knowledge is fused into existing themes; no raw HTML/base64 dump, embedded execution, asset-copy claim or new runtime acceptance is implied.
Publication-source arrangement and intentional boundaries
content/ is the repository-local wiki source root. Pages have YAML frontmatter for title, description, writing dates, research date, status and topics; this is separate from PLAN.md’s historical fenced request. content/assets/ holds unchanged image copies, and content/records/ holds unchanged JSON copies. artifact-atlas > Source-preserving copy strategy describes how those copies relate to originals.
No original Markdown section is repurposed as a new audit, strategy/prototype plan, showcase claim, deployment assertion, or completion receipt. Original review statements are dated and attributed. Original future acceptance requirements remain unexecuted requirements. External Funday references are outside this corpus, and the quickstart’s image-provider history is unknown rather than inferred from its filename.