GridPlacement 6.0.0

Primary: <a href=https://grid-placement.pages.dev/v6-0/guides/architecture-overview/ rel=external>Architecture Overview
Setup path: <a href=https://grid-placement.pages.dev/v6-0/guides/csharp-project-setup/ rel=external>C# Project Setup
Bootstrap + ordering: <a href=https://grid-placement.pages.dev/v6-0/guides/world-bootstrap-and-system-order/ rel=external>World Bootstrap and System Order
Release gate: <a href=https://grid-placement.pages.dev/v6-0/guides/release-readiness-and-test-gate/ rel=external>Release Readiness and Test Gate

6.0.0: This is the internal development documentation track. The 6.0 runtime is still evolving and features may change.

Welcome to the GridPlacement 6.0.0 development documentation.

Requirements: Godot 4.4 or later • GridPlacement 6.0.0-dev
6.0.0 is under development and may contain breaking changes

What 6.0 is

6.0 is a full architecture redesign centered on explicit boundaries, typed services, and C#-driven placement workflows:

Concept	What it means
Core vs adapter split	`GridPlacement.Core` owns domain rules, while `GridPlacement.Godot` translates Godot scenes, nodes, and resources into that runtime.
C# 6.0 workflow	Placement, occupancy, manipulation, and preview flows are processed through typed C# runtime services instead of legacy node-first orchestration.
Public services first	Consumers should reason about placement services and setup guides first, then drill into lower-level types when they need lower-level control.
Typed diagnostics	6.0 is moving toward clearer result objects, event payloads, and release-gate documentation instead of state-heavy public surfaces.
Internal development scope	The C# build lane is green, but the workflow coverage suite is still under repair and the broader test surface is still being stabilized.

This documentation set is for the 6.0 internal development line. The public runtime story is now aligned to the actual repository state:

6.0 is C#, not GDScript.
the focused workflow coverage suite is the intended proof lane, but it is currently failing on the audited branch.
the legacy all-in-one core test lane is still a blocker for GA.

For the production stable / maintenance release line, see: