Mergeway specification

Normative v1. This section specifies repositories that declare mergeway.version: 1. It describes behavior implemented by release v0.10.0.

This route is the stable home of the Mergeway specification. The version belongs to the configuration contract, not the URL; no parallel /v1/ route exists.

Contents

• Overview defines scope and the document map.
• Terminology defines the terms used by every normative page.
• Conformance and requirement language explains MUST, SHOULD, and implementation conformance.
• Repository and configuration defines discovery, configuration documents, and includes.
• Entity definitions defines entities, inline records, and inheritance.
• Field definitions and types defines the native field model and constraints.
• Records and data sources defines supported files, selectors, and record shapes.
• Identifiers and references defines record identity and relationships.
• Validation and error model defines the three validation phases.
• JSON Schema interoperability defines the supported import and export subset.
• Path-derived data defines $path identifiers and synthetic path fields.
• Open Knowledge Format mapping defines .md and .okf records.
• Changelog and migration notes records specification changes.

The examples rendered in this section come from a fixture validated by the website checks. They are normative where the surrounding text says MUST or MAY; names and example values are non-normative.