VibeGeometry/state/map.yaml
2026-05-04 20:06:14 +01:00

99 lines
6.2 KiB
YAML

experiment:
name: VibeGeometry
status: incubation
phase: phase_0_scaffold
premise: >
Build a durable research and implementation home for agent-authored
Blender 5.0+ scenes that use Python to construct complex geometry-node
graphs for procedural geometry matching reference images and instructions.
mission:
primary: >
Enable Codex and other agents to generate inspectable, reusable Blender
geometry-node graphs that produce specific visual results from reference
images, text instructions, and iterative render review.
near_term: >
Define the scene brief, node graph manifest, Python builder, render runner,
and review loop before building a large library of graph idioms.
hard_boundaries:
- Blender 5.0+ is the target runtime unless a task explicitly chooses another version.
- Geometry nodes are the primary procedural modeling surface.
- Python scripts should construct and orchestrate node graphs, not hide the design in uninspectable imperative mesh code.
- Python is the authoring and orchestration layer; Geometry Script is the inspectable node-graph emission surface, not the whole toolchain.
- Visual targets must preserve reference-image evidence and explicit instructions.
- A graph that runs is not accepted until rendered output is inspected against the target.
- Node groups must be named, parameterized, and legible enough for future agents to modify.
- Attribute creation, transformation, and consumption must be explicit.
- Prefer established Blender node idioms and current API guidance over bespoke graph inventions.
- Keep failed experiments only when they change future belief.
- Do not let proxy checks replace visual review.
live_architecture:
pipeline:
- Ingest reference images and instructions into a scene brief.
- Extract target visual traits: silhouette, repetition, distribution, material response, surface breakup, camera, lighting, palette, and scale cues.
- Plan a geometry strategy in plain language before scripting.
- Emit a node graph manifest describing groups, sockets, attributes, fields, modifiers, materials, and exposed controls.
- Generate Blender Python that builds the scene and node graphs from the manifest.
- Run Blender headlessly or interactively to produce `.blend` files and render evidence.
- Review renders against the visual target and record accepted, rejected, or revised hypotheses.
authoring_stack:
- Python structures intent, repetition, data tables, variants, cleanup, validation, documentation, and scene/render orchestration.
- Geometry Script emits inspectable reusable Geometry Nodes groups.
- bpy handles Blender objects, modifiers, materials, cameras, lights, files, renders, and evaluated-geometry checks.
- External Python tools inspect source blends, generate converter drafts, compare outputs, and maintain corpus evidence.
persistence:
- `state/map.yaml` stores canonical mission, boundaries, architecture, artifacts, and next action.
- `state/scratch.md` stores one bounded active thought surface.
- `state/evidence.jsonl` stores distilled belief-changing records.
- `notes/fresh-workspace-handoff.md` stores compact re-entry instructions.
- `notes/vibegeometry-current-system-map.md` explains the live repo machinery.
- `notes/vibegeometry-implementation-plan.md` stores the near-term build sequence.
active_subgoals:
- Keep the pipeline legible from visual target to graph strategy to Python builder to render review.
- Build a graded Geometry Nodes translation corpus before hardening schemas or builder abstractions.
- Define artifact schemas after enough translated examples expose the real contract pressure.
- Build a minimal Blender runner only after the scene brief and graph manifest contracts are clear.
- Collect Blender 5.0+ geometry-node API and best-practice evidence before hardening graph builders.
- Preserve one-hypothesis iteration when visual results miss the target.
current_artifacts:
canonical_docs:
- notes/architecture-rationale.md
- notes/fresh-workspace-handoff.md
- notes/vibegeometry-current-system-map.md
- notes/vibegeometry-implementation-plan.md
- docs/architecture/pipeline-overview.md
- docs/research/procedural-doctrine.md
- docs/research/geometry-script-fork-notes.md
tools:
- tools/vibegeometry_state.py
- tools/vibegeometry_prepare_compaction.py
- tools/inspect_blend_node_groups.py
- tools/verify_cartesian_translations.py
- tools/verify_piechart_translations.py
- tools/verify_fieldvalue_translations.py
- tools/geometry_script_loader.py
- tools/smoke_nodes_to_script_converter.py
pending_contracts:
- schemas/scene-brief.schema.json
- schemas/node-graph-manifest.schema.json
- schemas/render-review.schema.json
data_flow:
- Rehydrate from map, handoff, system map, implementation plan, and `npm run state:status`.
- Work one bounded pipeline organ.
- Verify the seam that matters.
- Add distilled evidence only when future belief changes.
- Commit completed work.
- If state grows faster than understanding, cut it back.
current_status:
summary: VibeGeometry has an initial persistence scaffold plus verified Geometry Script translations for local math/utility samples, a first official Blender demo tranche, and two IRCSS French Houses city-scale footholds. The IRCSS pass verified MakeSpiral as an architectural spine and PointyGothicCone as ornament grown from a structural host, while mapping blockers in larger systems: repeat-zone feedback, repeat Top outputs, foreach zones, and gizmo nodes. The repo-local Geometry Script fork includes a Blender 5.1 nodes_to_script converter port plus nested-group, menu-socket, and duplicate-key fixes needed by these translations.
next_action: Continue IRCSS French Houses by using the newly compiling GenerateArc/MakeStairs converter drafts as candidates for the next city-organ translation, or select another non-zone architectural helper with a non-empty behavioral harness.
remotes:
vibegeometry: https://github.com/GameCult/VibeGeometry
geometry_script_fork: https://github.com/GameCult/geometry-script
geometry_script_upstream_pr: https://github.com/carson-katri/geometry-script/pull/69