Статическое представление свидетельств контракта и корпуса соответствия. Эта страница является производной навигацией и не является источником семантики МТС.
Схема индекса
mts-contract-observatory-index/v0.1
Приёмка
cutover/typescript-c1-acceptance-v0.8.json
Текущий контракт
contracts/mts-contract-v0.15.json
Предыдущий контракт
contracts/mts-contract-v0.14.json
Живая проекция проверенного семантического IR
Проверяемые требования · mts-contract/v0.15
Иерархия определяется путями классификации контракта, а не порядком Markdown-разделов. Формулировки и свидетельства поступают из того же проверенного семантического IR, который компилирует MD-проекции.
A compact Author-gated Boolean AND source ANet contains only the exact local T/F truth-table semantics expressed as zero-role Rules; legacy RoleDictionary/index/Scope/interpreter scaffolding is not canonical source.
Boolean AND executes through the shared matcher/Γ-compatible path and frozen compatibility adapter with zero AND-specific host dispatch; operands outside the local T/F domain are NO_MATCH rather than pass-through.
MTS has one canonical semantic Boolean AND source/model. Frozen or future A-memory backends may use generated compatibility or optimized AND lowerings only when they are semantics-preserving with respect to the exact T/F-domain truth table and NO_MATCH boundary, remain generic/backend-owned, and stay outside canonical AND semantic authority.
One v0.15 execution-core semantic authority path: universal FORMAL and canonical JSON converge to the same native source ANet, then shared resolution/denotation/compiler/Γ execution/projection; no consumer-specific host semantic path is authoritative.
Every new canonical logical/executable JSON artifact in v0.15 stops at AUTHOR_REVIEW_PENDING before completion. Proof/aprover artifacts are separately Author-gated in v0.16.
Program-specific host semantic injection budget is exactly zero. Generic orchestration and backend compatibility/optimization lowerings may exist but have no MTS semantic authority.
Theory, Context/currentness, interpreter/meta-program, entry and result execution roles are represented by Links and semantic ANet membership. Host package/launch code may perform only generic selection/orchestration allowed by the machine contract and cannot supply semantic role authority.
The same Link may have different execution roles under different selected ANet contexts only because the corresponding contextual Link memberships differ; host names, manifests or pointers cannot create those roles.
The canonical «Формальная нотация МТС.md» is a deterministic generated projection of the current v0.15 execution-core FORMAL/JSON model, machine registries, selected Gamma/context profiles and Author-approved executable corpus; hand-maintained semantic prose and stale v0.14-only projection are forbidden.
Every semantic capability has positive, structural mutation, missing authority, context, identity, JSON mutation and fresh-memory falsifiers as applicable.
Lean4 and Rocq independently formalize the supported v0.15 FORMAL mathematical core and classify exact premises/domain/exclusions for contextual names, source denotation, DAS and ExactSequence; those proof models must not introduce proof-specific Grammar opcodes.
Paired external assurance proves/cross-checks semantic preservation of FORMAL/JSON convergence and canonical recursive 8/9/6/1 metacompilation for the declared fragment; corpus GREEN alone is not proof of soundness.
One repeated universal Γ is the shared v0.15 semantic execution operation for ordinary executable ANets and self-hosted meta/interpreter ANets: reaction-start snapshot; J0 structural-unary applicability over one explicit current endpoint; S1 read-only structural match/bind; S2 substitution/canonical Link construction during synthesis; 0/1/N ordered image contribution; complete staged successor and atomic publication. Exact grounded MP is the zero-role refinement. J1 cross-current-member join, external semantic grounder commands, consumer-specific opcodes and a second semantic runtime are not required/permitted by the selected profile.
Normal MTS merge paths cannot bypass required CI/repo-guard enforcement: broad always-bypass repository roles are removed or contained to an explicitly audited emergency actor/process, and an intentional RED repo-guard pull request is mechanically blocked from merging until restored GREEN.
FORMAL text and direct JSON converge to the same native source ANet roles, resolver and DAS denotation path before semantics. In direct JSON, object-member null denotes a bare source entry, a string RHS denotes a binding, a nested object denotes an anchored source bundle, and a structured bare key denotes resolved semantic membership. A root binding alone does not publish semantic membership. A non-empty role bundle publishes its resolved role members plus its Theory-to-Rule admission, while a grounded empty role bundle publishes only its Theory-to-Rule admission.
Semantic JSON mutations must predictably change or reject source/denotation/execution behavior; transport-only mutations must not create semantic authority. JSON is invalid and must fail closed for duplicate object keys, including keys that become equal after JSON escape decoding; duplicate local names; unsupported profile/schema identifiers; unknown fields; top-level null; null inside arrays; and structured binding heads outside the supported bounded fragment.
JSON arrays lower canonically to ExactSequence of already-denoted element Links; []=R. R-rooted fold F_R is a separate derived projection, not the positional/execution carrier.
Every FORMAL name is contextual. Absolute name :A is shorthand for R:A; no host-global atom namespace is semantic authority. Structured expressions resolve their endpoint names through the same contextual-name resolver before Link construction.
The accepted v0.15 fragment uses ordinary Link + ExactSequence + self-reference topology; proof-specific Grammar forms must not be introduced as MTS semantic authority.
Every FORMAL/model/JSON/metacompiler/recursive/execution change that can affect v0.15 executable semantics replays the complete Author-approved executable JSON corpus.
The v0.15 direct FORMAL/JSON source path preserves the already accepted ROOT/START/END/PAIR structural aspect constructors and lowers them to native Link topology / recursive 8/9/6/1 without enabling arbitrary cyclic bindings.
Normative English term for «асеть / асеть связей» is ANet. Aset is not an MTS English term; legacy Aset/aset code identifiers have no terminology or semantic authority.
Основное объясняющее представление · производная методология
Карта методологии и жизненного цикла версий
Две координированные, но не тождественные структуры: метод разработки и состояние жизненного цикла версии.
Теория
Контракт
Соответствие
Проверка
Модель / воспроизведение
Приёмка
Текущая
Связь метода и жизненного цикла: производная связь представленияСвязь трассируемости и свидетельств: ссылка из исходных данныхСемантические Связи МТС: в этом представлении не отображаются
ПРИНЯТА
Исследование—
Проблема—
Кандидат—
Проверка—
Модель / воспроизведение—
Принято2 свидетельств
Выпущено—
ПРИНЯТА
Исследование—
Проблема—
Кандидат—
Проверка—
Модель / воспроизведение—
Принято2 свидетельств
Выпущено—
ПРИНЯТА
Исследование—
Проблема—
Кандидат—
Проверка—
Модель / воспроизведение—
Принято2 свидетельств
Выпущено—
ПРЕДЫДУЩАЯ
Исследование—
Проблема—
Кандидат—
Проверка—
Модель / воспроизведение—
Принято2 свидетельств
Выпущено1 свидетельств
ТЕКУЩАЯ
Исследование—
Проблема—
Кандидат—
Проверка—
Модель / воспроизведение—
Принято2 свидетельств
Выпущено1 свидетельств
Анатомия инвариантов · mts-contract/v0.11
Производное представление происхождения данных. Манифест трассируемости: traceability/mts-v0.11.json. Отсутствующие связи показаны явно.
consumer source-to-result replay requires fixed Theory authority, selected finite Act attachments, matching Dictionary/Grammar/Theory, and equality between the source-selected Use and the selected Rule-role binding; candidate self-admission and late unselected ambient attachments do not gain authority
Q and v0.12 STRING/source operations require a structurally valid declared R/O/C/L/U basis with proper O/C relative to R; invalid, collapsed, forged or foreign basis evidence fails closed and write operations perform zero writes
exact STRING source is replayed only against an independently selected V012SourceAuthority: exact Dictionary identity plus exact Grammar/Theory membership Links; raw membership shape is not semantic authority
MATERIALIZE_TARGET removes exactly one leading R hierarchy-wide, preserves remaining indirection and fails closed before target writes on invalid exact evidence
Pure recursive dependency without finite ROOT-grounded distinguishing evidence does not establish semantic Link identity; the current canonical 1/6/8/9 tree carrier is complete only for well-founded ROOT-decomposable Links, while rooted cyclic graphs are not rejected ontologically.
Производное представление происхождения данных. Манифест трассируемости: traceability/mts-v0.14.json. Отсутствующие связи показаны явно.
Путь контракта
contracts/mts-contract-v0.14.json
JSON Pointer контракта
/requiredSemanticLaws/V14-L1
Закон контракта
One Link ontology and one abstract Link-forming primitive induce exactly four self-incidence structural cases 11/10/01/00; after Context orientation these are named ROOT/START_K/END_K/PAIR and encoded by recursive 8/9/6/1, which is not the Anum/Q alphabet.
Generalized modus ponens/reaction is preserved from accepted v0.13 through the explicit A14 -> A16 -> A17 -> A72w witness chain covering 1->0, 1->1, 1->N, N->1 and N->M without host function/cardinality opcodes.
A4': objective chirality Ω={W,J(W)} exists before any observer and J²=Id; an oriented Context K carries one of two Link-native one-sided self-incidence markers, deriving χ(K) and local START_K/END_K roles. Relative frame transport g_AB lies in {Id,J}, composes as Z2, and semantic laws are covariant; no Foundation-global selected W, ExactSequence, host boolean, or four primitive opcodes are orientation authority.
Anum is a rooted compact representation/coding of a sequence of Links; ExactSequence preserves exact positional sequence identity distinct from fold denotation, the recursive Link codec is not Anum, Q is a versioned sequence codec/interpreter, and every local sequence origin is R.
MTS representation layers are explicit and non-ontological above Link: recursive structure, representations/codecs, byte-text and symbolic metanotation introduce no second ontology entity.
Производное представление происхождения данных. Манифест трассируемости: traceability/mts-v0.15.json. Отсутствующие связи показаны явно.
Текущее нормативное требование
A compact Author-gated Boolean AND source ANet contains only the exact local T/F truth-table semantics expressed as zero-role Rules; legacy RoleDictionary/index/Scope/interpreter scaffolding is not canonical source.
A compact Author-gated Boolean AND source ANet contains only the exact local T/F truth-table semantics expressed as zero-role Rules; legacy RoleDictionary/index/Scope/interpreter scaffolding is not canonical source.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Boolean AND executes through the shared matcher/Γ-compatible path and frozen compatibility adapter with zero AND-specific host dispatch; operands outside the local T/F domain are NO_MATCH rather than pass-through.
Boolean AND executes through the shared matcher/Γ-compatible path and frozen compatibility adapter with zero AND-specific host dispatch; operands outside the local T/F domain are NO_MATCH rather than pass-through.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
MTS has one canonical semantic Boolean AND source/model. Frozen or future A-memory backends may use generated compatibility or optimized AND lowerings only when they are semantics-preserving with respect to the exact T/F-domain truth table and NO_MATCH boundary, remain generic/backend-owned, and stay outside canonical AND semantic authority.
MTS has one canonical semantic Boolean AND source/model. Frozen or future A-memory backends may use generated compatibility or optimized AND lowerings only when they are semantics-preserving with respect to the exact T/F-domain truth table and NO_MATCH boundary, remain generic/backend-owned, and stay outside canonical AND semantic authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Author-gated strict Boolean NOT/OR/XOR reuse the exact same FORMAL/JSON source model, semantic Theory->Rule discovery, zero-role Rule topology, generic Γ-compatible execution path and generic frozen-backend lowering as approved AND; no operator-specific semantic/runtime path is permitted.
Author-gated strict Boolean NOT/OR/XOR reuse the exact same FORMAL/JSON source model, semantic Theory->Rule discovery, zero-role Rule topology, generic Γ-compatible execution path and generic frozen-backend lowering as approved AND; no operator-specific semantic/runtime path is permitted.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
One v0.15 execution-core semantic authority path: universal FORMAL and canonical JSON converge to the same native source ANet, then shared resolution/denotation/compiler/Γ execution/projection; no consumer-specific host semantic path is authoritative.
One v0.15 execution-core semantic authority path: universal FORMAL and canonical JSON converge to the same native source ANet, then shared resolution/denotation/compiler/Γ execution/projection; no consumer-specific host semantic path is authoritative.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
FORMAL_MIGRATED or VERTICAL_GREEN requires tracked canonical FORMAL artifact, entry, digest, profile and evidence.
FORMAL_MIGRATED or VERTICAL_GREEN requires tracked canonical FORMAL artifact, entry, digest, profile and evidence.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Every new canonical logical/executable JSON artifact in v0.15 stops at AUTHOR_REVIEW_PENDING before completion. Proof/aprover artifacts are separately Author-gated in v0.16.
Every new canonical logical/executable JSON artifact in v0.15 stops at AUTHOR_REVIEW_PENDING before completion. Proof/aprover artifacts are separately Author-gated in v0.16.
Статус legacy-текста
только provenance; не текущий нормативный источник
Every dependency outside the artifact is explicitly classified and versioned.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Program-specific host semantic injection budget is exactly zero. Generic orchestration and backend compatibility/optimization lowerings may exist but have no MTS semantic authority.
Program-specific host semantic injection budget is exactly zero. Generic orchestration and backend compatibility/optimization lowerings may exist but have no MTS semantic authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Every Author-approved v0.15 executable artifact is pinned and replayed through FORMAL/JSON -> native source ANet -> semantic ANet -> recursive 8/9/6/1 -> generic compatibility lowering where required -> frozen A-memory 0.175.0, with zero semantic backend patches.
Every Author-approved v0.15 executable artifact is pinned and replayed through FORMAL/JSON -> native source ANet -> semantic ANet -> recursive 8/9/6/1 -> generic compatibility lowering where required -> frozen A-memory 0.175.0, with zero semantic backend patches.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Theory, Context/currentness, interpreter/meta-program, entry and result execution roles are represented by Links and semantic ANet membership. Host package/launch code may perform only generic selection/orchestration allowed by the machine contract and cannot supply semantic role authority.
Theory, Context/currentness, interpreter/meta-program, entry and result execution roles are represented by Links and semantic ANet membership. Host package/launch code may perform only generic selection/orchestration allowed by the machine contract and cannot supply semantic role authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
The same Link may have different execution roles under different selected ANet contexts only because the corresponding contextual Link memberships differ; host names, manifests or pointers cannot create those roles.
The same Link may have different execution roles under different selected ANet contexts only because the corresponding contextual Link memberships differ; host names, manifests or pointers cannot create those roles.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
The canonical «Формальная нотация МТС.md» is a deterministic generated projection of the current v0.15 execution-core FORMAL/JSON model, machine registries, selected Gamma/context profiles and Author-approved executable corpus; hand-maintained semantic prose and stale v0.14-only projection are forbidden.
The canonical «Формальная нотация МТС.md» is a deterministic generated projection of the current v0.15 execution-core FORMAL/JSON model, machine registries, selected Gamma/context profiles and Author-approved executable corpus; hand-maintained semantic prose and stale v0.14-only projection are forbidden.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Every semantic capability has positive, structural mutation, missing authority, context, identity, JSON mutation and fresh-memory falsifiers as applicable.
Every semantic capability has positive, structural mutation, missing authority, context, identity, JSON mutation and fresh-memory falsifiers as applicable.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Lean4 and Rocq independently formalize the supported v0.15 FORMAL mathematical core and classify exact premises/domain/exclusions for contextual names, source denotation, DAS and ExactSequence; those proof models must not introduce proof-specific Grammar opcodes.
Lean4 and Rocq independently formalize the supported v0.15 FORMAL mathematical core and classify exact premises/domain/exclusions for contextual names, source denotation, DAS and ExactSequence.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Paired external assurance proves/cross-checks semantic preservation of FORMAL/JSON convergence and canonical recursive 8/9/6/1 metacompilation for the declared fragment; corpus GREEN alone is not proof of soundness.
Paired external assurance proves/cross-checks semantic preservation of FORMAL/JSON convergence and canonical recursive 8/9/6/1 metacompilation for the declared fragment; corpus GREEN alone is not proof of soundness.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
A canonical FORMAL executable artifact reconstructs its executable package in fresh Memory using only fixed generic authorities.
Two fresh Memories with unrelated allocation noise preserve canonical recursive representation and behavior.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
One repeated universal Γ is the shared v0.15 semantic execution operation for ordinary executable ANets and self-hosted meta/interpreter ANets: reaction-start snapshot; J0 structural-unary applicability over one explicit current endpoint; S1 read-only structural match/bind; S2 substitution/canonical Link construction during synthesis; 0/1/N ordered image contribution; complete staged successor and atomic publication. Exact grounded MP is the zero-role refinement. J1 cross-current-member join, external semantic grounder commands, consumer-specific opcodes and a second semantic runtime are not required/permitted by the selected profile.
One repeated universal Γ is the shared v0.15 semantic execution operation for ordinary executable ANets and self-hosted meta/interpreter ANets: reaction-start snapshot; J0 structural-unary applicability over one explicit current endpoint; S1 read-only structural match/bind; S2 substitution/canonical Link construction during synthesis; 0/1/N ordered image contribution; complete staged successor and atomic publication. Exact grounded MP is the zero-role refinement. J1 cross-current-member join, external semantic grounder commands, consumer-specific opcodes and a second semantic runtime are not required/permitted by the selected profile.
Статус legacy-текста
только provenance; не текущий нормативный источник
Roadmap/status projections derive completion from registry/evidence rather than hand-maintained prose.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Normal MTS merge paths cannot bypass required CI/repo-guard enforcement: broad always-bypass repository roles are removed or contained to an explicitly audited emergency actor/process, and an intentional RED repo-guard pull request is mechanically blocked from merging until restored GREEN.
Normal MTS merge paths cannot bypass required CI/repo-guard enforcement: broad always-bypass repository roles are removed or contained to an explicitly audited emergency actor/process, and an intentional RED repo-guard pull request is mechanically blocked from merging until restored GREEN.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
JSON losslessly projects the complete supported canonical source ANet/model, not only passive carriers.
JSON losslessly projects the complete supported canonical source ANet/model, not only passive carriers.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
FORMAL text and direct JSON converge to the same native source ANet roles, resolver and DAS denotation path before semantics. In direct JSON, object-member null denotes a bare source entry, a string RHS denotes a binding, a nested object denotes an anchored source bundle, and a structured bare key denotes resolved semantic membership. A root binding alone does not publish semantic membership. A non-empty role bundle publishes its resolved role members plus its Theory-to-Rule admission, while a grounded empty role bundle publishes only its Theory-to-Rule admission.
FORMAL text and direct JSON converge to the same native source ANet roles, resolver and DAS denotation path before semantics.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Semantic JSON mutations must predictably change or reject source/denotation/execution behavior; transport-only mutations must not create semantic authority. JSON is invalid and must fail closed for duplicate object keys, including keys that become equal after JSON escape decoding; duplicate local names; unsupported profile/schema identifiers; unknown fields; top-level null; null inside arrays; and structured binding heads outside the supported bounded fragment.
Semantic JSON mutations must predictably change or reject source/denotation/execution behavior; transport-only mutations must not create semantic authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
JSON arrays lower canonically to ExactSequence of already-denoted element Links; []=R. R-rooted fold F_R is a separate derived projection, not the positional/execution carrier.
JSON arrays lower canonically to ExactSequence of already-denoted element Links; []=R. R-rooted fold F_R is a separate derived projection, not the positional/execution carrier.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Every FORMAL name is contextual. Absolute name :A is shorthand for R:A; no host-global atom namespace is semantic authority. Structured expressions resolve their endpoint names through the same contextual-name resolver before Link construction.
Every FORMAL name is contextual. Absolute name :A is shorthand for R:A; no host-global atom namespace is semantic authority. Structured expressions resolve their endpoint names through the same contextual-name resolver before Link construction.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
One-Link ontology: host kinds do not acquire MTS semantic authority.
One-Link ontology: host kinds do not acquire MTS semantic authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
The accepted v0.15 fragment uses ordinary Link + ExactSequence + self-reference topology; proof-specific Grammar forms must not be introduced as MTS semantic authority.
Every Author-approved JSON enters the permanent executable regression corpus.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Every FORMAL/model/JSON/metacompiler/recursive/execution change that can affect v0.15 executable semantics replays the complete Author-approved executable JSON corpus.
Every FORMAL/model/JSON/metacompiler/recursive/execution change that can affect v0.15 executable semantics replays the complete Author-approved executable JSON corpus.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Approved JSON/evidence is never silently regenerated; incompatible changes use explicit migration and renewed Author approval.
Read/find/validation are read-only; materialization/publication is explicit and failure-safe.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
The v0.15 direct FORMAL/JSON source path preserves the already accepted ROOT/START/END/PAIR structural aspect constructors and lowers them to native Link topology / recursive 8/9/6/1 without enabling arbitrary cyclic bindings.
The v0.15 direct FORMAL/JSON source path preserves the already accepted ROOT/START/END/PAIR structural aspect constructors and lowers them to native Link topology / recursive 8/9/6/1 without enabling arbitrary cyclic bindings.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
Normative English term for «асеть / асеть связей» is ANet. Aset is not an MTS English term; legacy Aset/aset code identifiers have no terminology or semantic authority.
Normative English term for «асеть / асеть связей» is ANet. Aset is not an MTS English term; legacy Aset/aset code identifiers have no terminology or semantic authority.
Статус legacy-текста
только provenance; не текущий нормативный источник
Источник корпуса соответствия
contracts/mts-conformance-v0.15.json
Текущее нормативное требование
VERTICAL_GREEN requires the complete mandatory evidence bundle and zero semantic injection.