Using the Schemas

1. Purpose of the Schemas#

Schemas ensure:

• consistent field definitions
• reproducible simulation configurations
• standardized experiment metadata
• compatibility across layers and modules

2. Loading Schemas#

Schemas are typically stored as JSON or YAML files and can be loaded using standard parsing libraries.

Example workflow:

1. load schema file
2. validate configuration against schema
3. construct substrate objects from validated data

3. Validation#

Validation ensures:

• required fields are present
• field types match expectations
• operator parameters fall within allowed ranges

Validation errors should be treated as configuration issues rather than runtime failures.

4. Extending Schemas#

Schemas can be extended to support:

• new operators
• custom experiment types
• additional metadata fields
• domain-specific configurations

Extensions should maintain backward compatibility whenever possible.

Quicklinks#

• docs api integration examples
• docs api README
• docs api schema overview
• docs experiments faraday paradox experiment
• docs experiments README
• docs experiments replication checklist
• docs experiments resonance alignment tests
• docs experiments rotating conductor tests
• docs methods dimensional layers
• docs methods field equations
• docs methods operator definitions
• docs methods README
• docs methods substrate dynamics
• docs methods triadic fields
• docs onboarding model map
• docs onboarding reading guide
• docs onboarding triadic quickstart
• docs onboarding verification tests
• docs overview comparison to gr models
• docs overview glossary
• docs overview introduction
• docs overview README
• docs overview resonance primitives
• docs overview theoretical background
• docs simulations boundary conditions
• docs simulations numerical methods
• docs simulations README
• docs simulations solver_architecture
• docs simulations validation metrics
• docs simulations core README
• previous folder