2.3 KiB
Fresh Workspace Handoff
Immediate Re-entry Instruction
Read state/map.yaml, this file, notes/vibegeometry-current-system-map.md,
and notes/vibegeometry-implementation-plan.md, then run:
npm run state:status
Restate the persisted next action before editing.
Do not continue implementation automatically from a rehydrate-only request.
Do not trust this file for the exact live HEAD. Use git for volatile truth:
git status --short --branch
git log --oneline -5
Current State
VibeGeometry is an initial scaffold. It has persistence machinery, project orientation docs, helper tools, and an initial Geometry Nodes translation corpus note, but no Blender builder library or artifact schemas yet.
The current next action is to build the first Geometry Nodes translation corpus
entry by inspecting a small public .blend node group, mapping its graph in
prose, and recreating it with Geometry Script.
Important Invariants
- Target Blender 5.0+ unless the task says otherwise.
- Geometry nodes are the primary procedural geometry surface.
- Python constructs and orchestrates graphs; it should not bury the design in opaque imperative mesh generation.
- Visual target evidence must remain attached to scene briefs and render review.
- A graph is not accepted just because it runs. Render evidence decides.
- Node groups, exposed sockets, and attributes need names clear enough for future agents to inspect and modify.
- Add evidence only when it changes future belief.
Open Questions
- What exact JSON shape should the scene brief use for references, instructions, target traits, and acceptance criteria?
- What should the first node graph manifest schema require versus merely allow?
- What node-group inspection JSON shape is most useful for translating public
.blendexamples into Geometry Script? - Which Blender 5.0+ APIs and node construction helpers should become the first stable builder layer?
- What is the smallest useful render-review artifact?
Compaction Notes
When preparing for imminent compaction, write hot memory first to
state/scratch-compaction-<guid>.md, then run:
npm run state:prepare-compaction
Fold only durable lessons into canonical state and delete the temporary scratch-compaction file after it has served its purpose.