Summary
RFC 0001 (Preponderous-Software/rfcs, rfcs/rfc_0001_modular_architecture.md) says Viron should "Define and store 2D grids with metadata", but Grid stores only dimensions.
src/main/java/preponderous/viron/models/Grid.java:10-12 — fields are gridId, rows, columns only. No name/description/tags/properties. The DTO and create_tables.sql grid table mirror this.
Why it matters
Metadata (name, type, arbitrary properties) lets a game distinguish and configure grids (board vs. menu, biome, etc.) without external bookkeeping.
Suggested direction
Add an optional metadata field to Grid (e.g. a name plus a JSON/properties column), thread it through the DTO, repository, and schema, and expose it on the grid endpoints.
Filed by Claude on behalf of Daniel Stephenson during an RFC↔implementation alignment audit; claims verified against the Viron source.
Summary
RFC 0001 (Preponderous-Software/rfcs,
rfcs/rfc_0001_modular_architecture.md) says Viron should "Define and store 2D grids with metadata", butGridstores only dimensions.src/main/java/preponderous/viron/models/Grid.java:10-12— fields aregridId,rows,columnsonly. No name/description/tags/properties. The DTO andcreate_tables.sqlgrid table mirror this.Why it matters
Metadata (name, type, arbitrary properties) lets a game distinguish and configure grids (board vs. menu, biome, etc.) without external bookkeeping.
Suggested direction
Add an optional metadata field to
Grid(e.g. a name plus a JSON/properties column), thread it through the DTO, repository, and schema, and expose it on the grid endpoints.Filed by Claude on behalf of Daniel Stephenson during an RFC↔implementation alignment audit; claims verified against the Viron source.