feat(occ): Add Optimistic Concurrency Control to NodeOperations (Issue #333)

docs/architecture/business-logic/database-schema.md

@@ -822,6 +822,10 @@ LIMIT 10;
 
 ## Migration Strategy
 
+> **📖 For detailed implementation procedures**, see the [Schema Management Implementation Guide](../development/schema-management-implementation-guide.md).
+
+**Summary**: NodeSpace uses lazy migration with version tracking to handle schema evolution without ALTER TABLE operations. This preserves the Pure JSON architecture while enabling controlled schema evolution.
+
 ### From External Repositories
 When migrating from separate `nodespace-*` repositories:
 
@@ -842,6 +846,8 @@ NodeSpace uses a **lazy migration strategy** for safe schema evolution:
 - **No ALTER TABLE**: Pure JSON schema eliminates SQL migrations on user machines
 - **Protection levels**: core/user/system fields with enforcement at API level
 - **Enum extensibility**: `core_values` (protected) + `user_values` (user-extensible)
+- **Forward compatibility**: Schemas designed for additive changes via protection levels
+- **Rollback capability**: Old schema versions supported indefinitely
 
 See [Issue #106](https://github.com/malibio/nodespace-core/issues/106) for complete 7-phase implementation details including SchemaService, MigrationRegistry, MCP tools, and frontend wrappers.
 

docs/architecture/components/validation-system.md

@@ -4,6 +4,17 @@
 
 The NodeSpace Validation System provides comprehensive business rule enforcement through natural language rule definition, cross-field validation logic, and conversational error handling. Users can define complex validation rules in plain English, which are automatically converted to executable logic and integrated into the AI-native workflow.
 
+### Schema Validation Integration
+
+The validation system integrates with NodeSpace's schema management for type-level validation. When schemas evolve, validation rules automatically apply to the current schema version through lazy migration. See [Schema Management Implementation Guide](../development/schema-management-implementation-guide.md) for details on:
+
+- **Schema version compatibility** - Validation works across schema versions
+- **Lazy migration with validation** - Nodes validated against current schema after migration
+- **Protection level enforcement** - Schema changes respect validation rules
+- **Type validation** - Enum values, field types, and constraints checked against schema
+
+This integration ensures data integrity while allowing schemas to evolve safely.
+
 ## Core Architecture
 
 ### Validation Engine Structure