Schema constraints

Entities conform to defined types and validation rules. Invalid writes fail at store time so malformed data does not silently enter the memory graph.

Before vs after

Before: one tool stores age: "thirty" while another expects a number. After: schema validation rejects the invalid write and returns a deterministic error.

# Invalid payload example
neotoma store --json='[{"entity_type":"person","name":"Ana Rivera","age":"thirty"}]'

# Valid payload
neotoma store --json='[{"entity_type":"person","name":"Ana Rivera","age":30}]'

This protects deterministic state evolution and reduces silent mutation risk. See conflicting facts risk for conflict handling.