metaobjects 0.24.1__tar.gz → 0.24.2__tar.gz

{metaobjects-0.24.1 → metaobjects-0.24.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: metaobjects
-Version: 0.24.1
+Version: 0.24.2
 Summary: Cross-language metadata standard: declare typed entities once, generate idiomatic drift-checked code across languages — Python port.
 Project-URL: Homepage, https://metaobjects.dev
 Project-URL: Repository, https://github.com/metaobjectsdev/metaobjects

{metaobjects-0.24.1 → metaobjects-0.24.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "metaobjects"
-version = "0.24.1"
+version = "0.24.2"
 description = "Cross-language metadata standard: declare typed entities once, generate idiomatic drift-checked code across languages — Python port."
 readme = "README.md"
 requires-python = ">=3.11"

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/core_types.py

@@ -69,6 +69,7 @@ from .meta.core.requirement.meta_requirement import MetaRequirement
 from .meta.core.requirement.requirement_constants import (
     REQUIREMENT_ATTR_DISPOSITION,
     REQUIREMENT_ATTR_IMPLEMENTED_BY,
+    REQUIREMENT_ATTR_SUPERSEDED_BY,
     REQUIREMENT_ATTR_LEVEL,
     REQUIREMENT_ATTR_STATEMENT,
     REQUIREMENT_ATTR_STATUS,
@@ -636,6 +637,14 @@ _REQUIREMENT_COMMON_ATTRS = [
     ),
     AttrSchema(name=REQUIREMENT_ATTR_STATEMENT, value_type=ATTR_SUBTYPE_STRING, required=True),
     AttrSchema(name=REQUIREMENT_ATTR_COUNTEREXAMPLE, value_type=ATTR_SUBTYPE_STRING, required=True),
+    # FR-039 -- the requirement that REPLACED a retired one. Declared BEFORE
+    # @implementedBy to match the canonical spec's child order, which the registry
+    # manifest emits verbatim and every port byte-matches.
+    AttrSchema(
+        name=REQUIREMENT_ATTR_SUPERSEDED_BY,
+        value_type=ATTR_SUBTYPE_STRING,
+        required=False,
+    ),
     AttrSchema(
         name=REQUIREMENT_ATTR_IMPLEMENTED_BY,
         value_type=ATTR_SUBTYPE_STRING,

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/errors.py

@@ -94,6 +94,12 @@ class ErrorCode(str, Enum):
     # references / sourceRefField-not-matching / M:N-attr-on-1:N). The symmetric-
     # on-hetero + symmetric+sourceRefField rules emit ERR_BAD_ATTR_VALUE instead.
     ERR_INVALID_INDEX = "ERR_INVALID_INDEX"
+    # FR-039 -- @status: retired declares @implementedBy. Refused rather than exempted:
+    # a retired capability has no implementation BY DEFINITION, so forbidding the
+    # attribute makes the dangling-reference class unreachable instead of tolerated.
+    ERR_REQUIREMENT_RETIRED_HAS_IMPLEMENTORS = "ERR_REQUIREMENT_RETIRED_HAS_IMPLEMENTORS"
+    # FR-039 -- @supersededBy on a requirement whose @status is not `retired`.
+    ERR_REQUIREMENT_SUPERSEDED_BY_NOT_RETIRED = "ERR_REQUIREMENT_SUPERSEDED_BY_NOT_RETIRED"
     ERR_INVALID_RELATIONSHIP = "ERR_INVALID_RELATIONSHIP"
     # identity.reference @references names an FK target object that does not resolve
     # to any object in the loaded tree (a dangling cross-reference between metadata).

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/loader/validation_passes.py

@@ -76,6 +76,7 @@ from ..shared.base_types import (
     TYPE_OBJECT,
     TYPE_ORIGIN,
     TYPE_RELATIONSHIP,
+    TYPE_REQUIREMENT,
     TYPE_SOURCE,
     TYPE_TEMPLATE,
 )
@@ -236,6 +237,9 @@ def run_validations(
     # #335 Half B — @sortable on an array field, or a subtype with no operator band → error.
     _validate_sortable_has_supported_subtype(root, errors)
     _validate_index_lookup_fields(root, errors)
+    # FR-039 -- a retired requirement carries no @implementedBy (refused, not exempted,
+    # so the dangling-ref class is unreachable) and @supersededBy is legal only there.
+    _validate_retired_requirement_links(root, errors)
 
 
 # ---------------------------------------------------------------------------
@@ -3827,3 +3831,75 @@ def _validate_index_lookup_fields(root: MetaData, errors: list[MetaError]) -> No
                         ),
                         envelope=node.source,
                     ))
+
+
+# ---------------------------------------------------------------------------
+# FR-039 -- a retired requirement's link vocabulary
+#
+# Two rules, and the first is the structural point of the FR.
+#
+#   1. `@status: retired` may NOT carry `@implementedBy`. Not exempt from the
+#      dangling-reference check -- REFUSED. 0.24.0 removed the previous retired
+#      vocabulary because `verify` was SILENT on dangling refs for it, hiding 29
+#      unresolvable references across 14 entries in one estate while reporting
+#      zero. Forbidding the attribute makes the bug class UNREACHABLE instead: a
+#      retired capability has no implementation by definition.
+#   2. `@supersededBy` is legal ONLY on `retired`. Resolution of the reference is
+#      `verify`'s job; the loader owns the shape.
+#
+# `requirement.*` gate logic otherwise lives only in the TS CLI, which is exactly
+# why THIS rule belongs in the loader: a Python estate would otherwise be free to
+# author the shape the rule exists to prevent.
+#
+# ADR-0039: attrs() is the RESOLVING accessor in Python (attr() is own-only), so a
+# requirement inheriting its status through `extends` is judged on its EFFECTIVE one.
+# ---------------------------------------------------------------------------
+
+
+def _validate_retired_requirement_links(root: MetaData, errors: list[MetaError]) -> None:
+    from ..meta.core.requirement.requirement_constants import (
+        REQUIREMENT_ATTR_IMPLEMENTED_BY,
+        REQUIREMENT_ATTR_STATUS,
+        REQUIREMENT_ATTR_SUPERSEDED_BY,
+        REQUIREMENT_STATUS_RETIRED,
+    )
+
+    def walk(node: MetaData) -> None:
+        for child in node.children():
+            if child.type == TYPE_REQUIREMENT:
+                attrs = child.attrs()
+                status = attrs.get(REQUIREMENT_ATTR_STATUS)
+                is_retired = status == REQUIREMENT_STATUS_RETIRED
+
+                if is_retired and REQUIREMENT_ATTR_IMPLEMENTED_BY in attrs:
+                    errors.append(MetaError(
+                        code=ErrorCode.ERR_REQUIREMENT_RETIRED_HAS_IMPLEMENTORS,
+                        message=(
+                            f'requirement.{child.sub_type} "{child.name}" is @status: '
+                            f"{REQUIREMENT_STATUS_RETIRED} and declares "
+                            f"@{REQUIREMENT_ATTR_IMPLEMENTED_BY}. A retired capability has no "
+                            f"implementation -- that is what retiring it means. Delete the "
+                            f"attribute; if the nodes are still there, the capability is not "
+                            f"retired. What used to implement it belongs in `notes`, and what "
+                            f"REPLACED it in @{REQUIREMENT_ATTR_SUPERSEDED_BY}."
+                        ),
+                        envelope=child.source,
+                    ))
+
+                if not is_retired and REQUIREMENT_ATTR_SUPERSEDED_BY in attrs:
+                    shown = status if status is not None else "(absent)"
+                    errors.append(MetaError(
+                        code=ErrorCode.ERR_REQUIREMENT_SUPERSEDED_BY_NOT_RETIRED,
+                        message=(
+                            f'requirement.{child.sub_type} "{child.name}" declares '
+                            f"@{REQUIREMENT_ATTR_SUPERSEDED_BY} but its "
+                            f'@{REQUIREMENT_ATTR_STATUS} is "{shown}". That attribute names '
+                            f"the requirement which REPLACED a withdrawn one, so it is legal "
+                            f"only on @{REQUIREMENT_ATTR_STATUS}: {REQUIREMENT_STATUS_RETIRED}."
+                        ),
+                        envelope=child.source,
+                    ))
+            # Hierarchy IS nesting, so a retired requirement can sit at any depth.
+            walk(child)
+
+    walk(root)

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/meta/core/requirement/requirement_constants.py

@@ -26,6 +26,9 @@ REQUIREMENT_SUBTYPES = (
 #: 1 solution · 2 segment (app/library) · 3 service · 4 object · 5 member.
 REQUIREMENT_ATTR_LEVEL = "level"
 REQUIREMENT_ATTR_STATUS = "status"
+# FR-039 -- the requirement that REPLACED a retired one. Resolving reference,
+# legal on `retired` only.
+REQUIREMENT_ATTR_SUPERSEDED_BY = "supersededBy"
 REQUIREMENT_ATTR_DISPOSITION = "disposition"
 REQUIREMENT_ATTR_TRACKED_BY = "trackedBy"
 REQUIREMENT_ATTR_STATEMENT = "statement"
@@ -41,11 +44,15 @@ REQUIREMENT_ATTR_IMPLEMENTED_BY = "implementedBy"
 REQUIREMENT_STATUS_PLANNED = "planned"
 REQUIREMENT_STATUS_LIVE = "live"
 REQUIREMENT_STATUS_PARTIAL = "partial"
+# FR-039 -- built, then deliberately removed; it must NOT be rebuilt. PRESCRIPTIVE:
+# the entry states a prohibition in force, falsifiable by the capability reappearing.
+REQUIREMENT_STATUS_RETIRED = "retired"
 
 REQUIREMENT_STATUSES = (
     REQUIREMENT_STATUS_PLANNED,
     REQUIREMENT_STATUS_LIVE,
     REQUIREMENT_STATUS_PARTIAL,
+    REQUIREMENT_STATUS_RETIRED,
 )
 
 #: Statuses whose implementing nodes are supposed to still exist. A dangling
@@ -63,6 +70,11 @@ REQUIREMENT_STATUSES_REQUIRING_LIVE_NODES = (
 # Statuses with outstanding work, so a @disposition is meaningful on them. On any
 # other status the decision IS the status, and recording a second one can only
 # agree with it or contradict it.
+# Statuses on which `@implementedBy` is REFUSED AT LOAD (FR-039). Forbidding the
+# attribute makes the dangling-reference bug class UNREACHABLE rather than exempt --
+# a retired capability has no implementation by definition.
+REQUIREMENT_STATUSES_FORBIDDING_IMPLEMENTORS = (REQUIREMENT_STATUS_RETIRED,)
+
 REQUIREMENT_STATUSES_WITH_OUTSTANDING_WORK = (
     REQUIREMENT_STATUS_PLANNED,
     REQUIREMENT_STATUS_PARTIAL,

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/registry_manifest.py

@@ -255,7 +255,7 @@ def _sorted_children(definition: TypeDefinition) -> list[dict[str, object]]:
     return children
 
 
-METAMODEL_VERSION = "0.12"
+METAMODEL_VERSION = "0.13"
 """Rolled-up spec-version for the cross-port registry manifest.
 
 ``"0"`` = pre-1.0 / unstable (semver major-0). Flips to ``"1.0"`` at the

{metaobjects-0.24.1 → metaobjects-0.24.2}/src/metaobjects/spec_metamodel/requirement.json

@@ -24,9 +24,10 @@
           "allowedValues": [
             "planned",
             "live",
-            "partial"
+            "partial",
+            "retired"
           ],
-          "description": "planned intended but not built yet; live implemented and in use; partial implemented with known gaps. A requirement is PRESCRIPTIVE — it states what SHOULD happen and is never a journal of what happened — so a capability that no longer applies is DELETED, not annotated as retired; the record of it having existed belongs to version control and to notes on the entries that survive. A dangling @implementedBy is an ERROR on live/partial (the model moved, the requirement is stale) and ALLOWED on planned, where the nodes do not exist YET. A planned requirement also never contributes to object coverage: planning a capability must not silence the warning that nothing implements it."
+          "description": "planned intended but not built yet; live implemented and in use; partial implemented with known gaps; retired BUILT THEN DELIBERATELY REMOVED — it must not be rebuilt. A requirement is PRESCRIPTIVE: it states what SHOULD be true and never journals what happened, and retired satisfies that because it states a prohibition in force, falsifiable by the capability reappearing. On retired, @implementedBy is REFUSED at load (ERR_REQUIREMENT_RETIRED_HAS_IMPLEMENTORS) — a retired capability has no implementation by definition, so its references cannot dangle because they cannot exist; @supersededBy names the requirement that replaced it. A dangling @implementedBy is an ERROR on live/partial (the model moved, the requirement is stale) and ALLOWED on planned, where the nodes do not exist YET. Neither planned nor retired contributes to object coverage: planning a capability must not silence the warning that nothing implements it, and neither must retiring one."
         },
         {
           "type": "attr",
@@ -65,6 +66,14 @@
           "max": 1,
           "description": "What breaking it looks like, in one sentence — a STATIC falsifiability test, authored once, never a state. A requirement MUST be violable: 'every entity has a uuid primary key' is (point at one with a composite string key); 'things are persisted' is not, and is a description rather than a requirement. Renamed from @violation in 0.24.0, which read as a status."
         },
+        {
+          "type": "attr",
+          "subType": "string",
+          "name": "supersededBy",
+          "min": 0,
+          "max": 1,
+          "description": "The requirement that REPLACED this one. Legal on @status: retired only (ERR_REQUIREMENT_SUPERSEDED_BY_NOT_RETIRED otherwise), and RESOLVED like any other reference, so a dangling one is ERR_REQUIREMENT_DANGLING_REF and a supersession chain stays walkable: A names B, and when B is retired in turn it names C. That resolution is the whole point — 0.24.0 deregistered an unresolved string, and the 2026-08-10 ruling had asked for the resolving form (point 4) which was never built. A prose note in @notes points one hop and goes stale; this does not."
+        },
         {
           "type": "attr",
           "subType": "string",
@@ -107,9 +116,10 @@
           "allowedValues": [
             "planned",
             "live",
-            "partial"
+            "partial",
+            "retired"
           ],
-          "description": "As on requirement.functional. A live or partial architectural requirement claimed by NOTHING is an error: a policy declared and applied to nothing. A planned one is exempt from that check — it is not applied yet by definition."
+          "description": "As on requirement.functional. A live or partial architectural requirement claimed by NOTHING is an error: a policy declared and applied to nothing. planned is exempt from that check — it is not applied yet by definition — and retired is exempt because a withdrawn policy governs nothing."
         },
         {
           "type": "attr",
@@ -148,6 +158,14 @@
           "max": 1,
           "description": "What breaking it looks like — the node that would contradict it. A STATIC falsifiability test, not a state. This is what makes universality checkable. Renamed from @violation in 0.24.0, which read as a status."
         },
+        {
+          "type": "attr",
+          "subType": "string",
+          "name": "supersededBy",
+          "min": 0,
+          "max": 1,
+          "description": "The requirement that REPLACED this one. Legal on @status: retired only (ERR_REQUIREMENT_SUPERSEDED_BY_NOT_RETIRED otherwise), and RESOLVED like any other reference, so a dangling one is ERR_REQUIREMENT_DANGLING_REF and a supersession chain stays walkable: A names B, and when B is retired in turn it names C. That resolution is the whole point — 0.24.0 deregistered an unresolved string, and the 2026-08-10 ruling had asked for the resolving form (point 4) which was never built. A prose note in @notes points one hop and goes stale; this does not."
+        },
         {
           "type": "attr",
           "subType": "string",

{metaobjects-0.24.1 → metaobjects-0.24.2}/uv.lock

@@ -250,7 +250,7 @@ wheels = [
 
 [[package]]
 name = "metaobjects"
-version = "0.24.1"
+version = "0.24.2"
 source = { editable = "." }
 dependencies = [
     { name = "pyyaml" },