Releases: Leryk1981/MOVA
MOVA 4.1.1 – Core Spec Patch Release
Summary
MOVA 4.1.1 is a patch release over 4.1.0.
There are no breaking JSON-schema changes (ds., env., global.*).
The release clarifies the core spec, security layer, text/UI rules, and layers/namespaces, and introduces the operator frame.
Highlights
-
Core catalog cleanup
- Core catalog examples contain only red-core artefacts (no Smartlink or other domain schemas).
ds.mova4_core_catalog_v1andenv.mova4_core_catalog_publish_v1updated to 4.1.1 and aligned with the red-core inventory.
-
Security layer as mandatory red core
mova_4.1.1_security_layerpromoted the security layer to a required part of the core.ds.security_event_episode_core_v1andds.instruction_profile_core_v1are now explicitly aligned withglobal.security_catalog_v1.- Updated instruction profile and security event examples (no domain-specific tails).
-
Text & UI layer alignment
mova_4.1.1_text_and_ui_layerdefines clear text channels (human_ui,model_instruction,system_log,mixed_legacy).ds.ui_text_bundle_core_v1is aligned withglobal.text_channel_catalog_v1and forbids mixing human UI text with model instructions.
-
Layers & namespaces clarified
red_coreis strictly language-only (ds/env/global, plus security/text/episodes/catalogs).- Domain schemas (Smartlink, social, e-commerce, etc.) are explicitly scoped to the skills layer.
- Infra (runtimes, tools, vendors) is described as execution, not part of the language.
-
Operator frame
- New document
mova_4.1.1_operator_frame.mdintroduces a 12-axis operator frame (what/how/where/when/why/...). - Constitution, episodes/genetic-layer, and security docs now reference the operator frame as the official audit lens.
- New document
Migration notes (4.1.0 → 4.1.1)
- No schema migrations are required if you already conform to MOVA 4.1.0.
- Recommended:
- Update documentation references to 4.1.1.
- Ensure your core catalog does not include domain schemas.
- Align security events and instruction profiles with
global.security_catalog_v1. - Check that text bundles use the correct text channels and do not mix human UI text with model instructions.
MOVA 4.1.0 — Core Spec, Security Layer and Runtime Contracts
Overview
This release promotes MOVA 4.1.0 to the canonical core specification.
Version 4.1.0 stabilises:
- the red core (data schemas, envelopes, global catalogs),
- the episode & genetic layer,
- the security layer (instruction profiles + security events),
- the text/UI layer (text channels + UI bundles),
- the runtime & connector core.
All 4.0.0 text documents are archived; 4.1.0 is the new single source of truth.
What’s new
1. Core schemas (red layer)
New and updated core schemas under schemas/:
ds.mova_schema_core_v1.schema.jsonds.mova_episode_core_v1.schema.jsonds.security_event_episode_core_v1.schema.jsonds.instruction_profile_core_v1.schema.jsonds.runtime_binding_core_v1.schema.jsonds.connector_core_v1.schema.jsonds.ui_text_bundle_core_v1.schema.jsonds.mova4_core_catalog_v1.schema.json
Core envelopes:
env.mova4_core_catalog_publish_v1.schema.jsonenv.instruction_profile_publish_v1.schema.jsonenv.security_event_store_v1.schema.json
Global catalogs:
global.episode_type_catalog_v1.jsonglobal.security_catalog_v1.jsonglobal.layers_and_namespaces_v1.jsonglobal.text_channel_catalog_v1.json
All schemas now use JSON Schema draft 2020-12.
2. Text specifications (docs/)
New 4.1.0 documentation:
docs/mova_4.1.0_core.mddocs/mova_4.1.0_global_and_verbs.mddocs/mova_4.1.0_episodes_and_genetic_layer.mddocs/mova_4.1.0_layers_and_namespaces.mddocs/mova_4.1.0_security_layer.mddocs/mova_4.1.0_text_and_ui_layer.mddocs/mova_4.1.0_runtime_and_connectors.md
These documents describe how the red core, episodes, security, text/UI and runtime/connector contracts fit together.
3. Security layer
The security layer is now part of the red core:
- instruction profiles:
ds.instruction_profile_core_v1 - security event episodes:
ds.security_event_episode_core_v1 - security catalogs:
global.security_catalog_v1 - storage envelope:
env.security_event_store_v1
Security events are first-class episodes with episode_type = "security_event/…", linked to instruction profiles and security_model_version.
4. Text & UI layer
A dedicated text/UI layer is introduced:
global.text_channel_catalog_v1(channels:human_ui,model_instruction,system_log,mixed_legacy)ds.ui_text_bundle_core_v1for structured UI text bundles
The spec formalises separation of:
- human-facing UI copy,
- model instructions,
- system logs.
5. Runtime & connectors
Runtime and connector contracts are now explicitly defined:
ds.runtime_binding_core_v1— runtime binding coreds.connector_core_v1— connector core
These schemas are vendor-neutral red core artefacts; concrete runtimes and connectors must extend them in the infra layer.
6. Validator and tooling
The validation tool has been updated:
tools/validate_all.jsnow uses Ajv 2020 (ajv/dist/2020) and validates all schemas as draft 2020-12.- All schemas in
schemas/are registered first, then validated, so$refby$id(including the core schema) resolve correctly.
Run:
npm test
to validate all core schemas.
Migration notes
All previous 4.0.0 text documents are moved to:
text
Копировать код
docs/archive/4.0.0/
For any new work, use only the mova_4.1.0_*.md documents and 4.1.0 schemas as the authoritative specification.
Schema consumers must support JSON Schema draft 2020-12.
MOVA 4.1.0 is now the canonical contract for data, envelopes, episodes and security in the MOVA ecosystem.MOVA 4.0.0 — core specification
First public publication of the MOVA 4.0.0 core specification.
Includes:
- Core language documents in
docs/ - JSON Schemas in
schemas/(draft 2020-12) - Basic examples in
examples/ - Schema validator (
npm test→ Ajv 2020-12)
License: Apache-2.0
Author: Sergii Miasoiedov