docs: add object placement authoring plan#21
Merged
Conversation
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
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.
Motivation
instance.idcontract, and the minimal engine work (generic spawn + id↔entity mapping) needed before any dev-only placement overlay work proceeds.Description
docs/planning/object-placement-authoring-plan.mdwhich documents the problem statement, current diagnostics, the person↔agent ownership model, theinstance.idcontract, a 0..6 slice implementation plan, verification commands, exclusions, open questions, and next-step recommendations.docs/planning/README.mdto expose the new planning document in the planning index.instance.id↔Entitymapping) and explicitly gates any visual-editor style work behind approval and a dev-only prototype path.Testing
pnpm validate:docs-links, which completed successfully and reported docs/link validation OK.pnpm build:pages, which failed becauseexamples/starter-runtime/distwas missing and the pages build script requires runningpnpm buildfirst.pnpm build, which failed during the wasm build step becausewasm-packis not available in the environment; thebuild:wasmstep therefore exited withwasm-pack: command not found.wasm-packby invokingwasm-pack --version, which is not present; re-running the full site build will succeed once the wasm toolchain dependency (wasm-pack) and example build artifacts are available.Codex Task