omnibase_infra 0.3.1__py3-none-any.whl → 0.4.0__py3-none-any.whl

omnibase_infra/nodes/contract_registry_reducer/reducer.py

@@ -632,30 +632,14 @@ class ContractRegistryReducer:
         Parses the contract_yaml for consumed_events and published_events,
         then creates postgres.update_topic intents for each topic suffix.
 
-        Environment Placeholder Handling:
-            Topic suffixes from contract_yaml may contain ``{env}.`` placeholders
-            (e.g., ``{env}.onex.evt.platform.contract-registered.v1``). This reducer
-            stores these values **as-is** without stripping the placeholder.
+        Realm-Agnostic Topics:
+            Topics in ONEX are realm-agnostic. The environment/realm is enforced via
+            envelope identity, not topic naming. Contract topics are stored without
+            any environment prefix (e.g., ``onex.evt.platform.contract-registered.v1``).
 
-            This is intentional for several reasons:
-
-            1. **Reducer Purity**: The reducer remains environment-agnostic and
-               deterministic - it doesn't need to know about deployment environments.
-
-            2. **Effect Layer Responsibility**: The PostgresAdapter (Effect layer)
-               is responsible for resolving or stripping the ``{env}.`` placeholder
-               at write time, when the actual environment context is available.
-
-            3. **Auditing**: Storing the raw contract value preserves the original
-               contract specification for debugging and auditing purposes.
-
-            4. **Query Flexibility**: Downstream consumers can query topics with
-               or without the placeholder depending on their needs.
-
-            The Effect layer should handle ``{env}.`` resolution via one of:
-            - Stripping the prefix before storage (simple)
-            - Replacing with actual environment (e.g., ``dev.``, ``prod.``)
-            - Storing as-is with environment-aware queries
+            The Effect layer (PostgresAdapter) may still encounter legacy topics with
+            ``{env}.`` placeholders and will strip them during storage normalization.
+            See ``normalize_topic_for_storage()`` in handler_postgres_topic_update.py.
 
         Args:
             event: Contract registered event with contract_yaml.
@@ -697,9 +681,8 @@ class ContractRegistryReducer:
         if isinstance(consumed_events, list):
             for consumed in consumed_events:
                 if isinstance(consumed, dict):
-                    # NOTE: topic_suffix may contain {env}. placeholder (e.g.,
-                    # "{env}.onex.evt.platform.contract-registered.v1").
-                    # We store it as-is; the Effect layer handles resolution.
+                    # Topics are realm-agnostic (e.g., "onex.evt.platform.contract-registered.v1").
+                    # Legacy topics with {env}. prefix are normalized by the Effect layer.
                     topic_suffix = consumed.get("topic")
                     if topic_suffix and isinstance(topic_suffix, str):
                         # Validate event_type is string (may be missing or wrong type in malformed YAML)

omnibase_infra/nodes/effects/__init__.py

@@ -11,8 +11,8 @@ Available:
     - ModelBackendResult: Individual backend result model
 """
 
+from omnibase_infra.models.model_backend_result import ModelBackendResult
 from omnibase_infra.nodes.effects.models import (
-    ModelBackendResult,
     ModelRegistryRequest,
     ModelRegistryResponse,
 )

omnibase_infra/nodes/effects/models/__init__.py

@@ -5,15 +5,17 @@
 This module exports models used by Effect layer nodes for external I/O operations.
 
 Available Models:
-    - ModelBackendResult: Individual backend operation result
+    - ModelBackendResult: Individual backend operation result (re-exported)
     - ModelEffectIdempotencyConfig: Configuration for effect idempotency store
     - ModelRegistryRequest: Registry effect input request
     - ModelRegistryResponse: Dual-backend registry operation response
+
+Note:
+    ModelBackendResult canonical location is omnibase_infra.models.model_backend_result.
+    Re-exported here for backward compatibility.
 """
 
-from omnibase_infra.nodes.effects.models.model_backend_result import (
-    ModelBackendResult,
-)
+from omnibase_infra.models.model_backend_result import ModelBackendResult
 from omnibase_infra.nodes.effects.models.model_effect_idempotency_config import (
     ModelEffectIdempotencyConfig,
 )

omnibase_infra/nodes/effects/models/model_registry_response.py

@@ -41,7 +41,7 @@ from uuid import UUID
 from pydantic import BaseModel, ConfigDict, Field
 
 from omnibase_infra.enums import EnumBackendType, EnumRegistryResponseStatus
-from omnibase_infra.nodes.effects.models.model_backend_result import (
+from omnibase_infra.models.model_backend_result import (
     ModelBackendResult,
 )
 

omnibase_infra/nodes/effects/protocol_consul_client.py

@@ -21,7 +21,7 @@ from __future__ import annotations
 
 from typing import Protocol, runtime_checkable
 
-from omnibase_infra.nodes.effects.models import ModelBackendResult
+from omnibase_infra.models import ModelBackendResult
 
 
 @runtime_checkable

omnibase_infra/nodes/effects/protocol_postgres_adapter.py

@@ -24,7 +24,7 @@ from uuid import UUID
 
 from omnibase_core.enums import EnumNodeKind
 from omnibase_core.models.primitives import ModelSemVer
-from omnibase_infra.nodes.effects.models import ModelBackendResult
+from omnibase_infra.models import ModelBackendResult
 
 
 @runtime_checkable

omnibase_infra/nodes/effects/registry_effect.py

@@ -100,7 +100,7 @@ from omnibase_infra.errors import (
     InfraConnectionError,
     InfraTimeoutError,
 )
-from omnibase_infra.nodes.effects.models.model_backend_result import (
+from omnibase_infra.models.model_backend_result import (
     ModelBackendResult,
 )
 from omnibase_infra.nodes.effects.models.model_effect_idempotency_config import (

omnibase_infra/nodes/node_contract_persistence_effect/__init__.py

@@ -0,0 +1,101 @@
+# SPDX-License-Identifier: MIT
+# Copyright (c) 2025 OmniNode Team
+"""Node Contract Persistence Effect package - Declarative effect node for contract persistence.
+
+This package provides NodeContractPersistenceEffect, a declarative effect node that
+routes intents from ContractRegistryReducer to PostgreSQL handlers for contract
+and topic persistence operations.
+
+Architecture (OMN-1845):
+    This package follows the ONEX declarative node pattern:
+    - node.py: Declarative node shell extending NodeEffect
+    - handlers/: PostgreSQL operation handlers
+    - registry/: Infrastructure registry for dependency injection
+    - contract.yaml: Intent routing and I/O definitions
+
+    The node is 100% contract-driven with zero custom business logic in node.py.
+    All intent routing is defined in contract.yaml and handlers are resolved
+    via container dependency injection.
+
+Node Type: EFFECT_GENERIC
+Purpose: Execute PostgreSQL I/O operations based on intents from ContractRegistryReducer.
+
+Implementation Details:
+    - Routes 6 intent types to specialized handlers
+    - Circuit breaker protection for PostgreSQL
+    - Error sanitization for security
+    - Retry policies for transient failures
+
+Supported Intent Types:
+    - postgres.upsert_contract: Insert/update contract record
+    - postgres.update_topic: Update topic routing table
+    - postgres.mark_stale: Batch mark stale contracts
+    - postgres.update_heartbeat: Update heartbeat timestamp
+    - postgres.deactivate_contract: Soft delete contract
+    - postgres.cleanup_topic_references: Remove contract from topics
+
+Handlers:
+    - HandlerPostgresContractUpsert: Contract upsert operations
+    - HandlerPostgresTopicUpdate: Topic routing updates
+    - HandlerPostgresMarkStale: Batch staleness marking
+    - HandlerPostgresHeartbeat: Heartbeat timestamp updates
+    - HandlerPostgresDeactivate: Contract deactivation
+    - HandlerPostgresCleanupTopics: Topic reference cleanup
+
+Usage:
+    ```python
+    from omnibase_core.models.container import ModelONEXContainer
+    from omnibase_infra.nodes.node_contract_persistence_effect import (
+        NodeContractPersistenceEffect,
+    )
+
+    # Create via container injection
+    container = ModelONEXContainer()
+    effect = NodeContractPersistenceEffect(container)
+    ```
+
+Related:
+    - contract.yaml: Intent routing definition
+    - node.py: Declarative node implementation
+    - handlers/: PostgreSQL operation handlers
+    - registry/: Infrastructure registry
+    - contract_registry_reducer/: Source of intents
+    - OMN-1845: Implementation ticket
+    - OMN-1653: ContractRegistryReducer ticket
+"""
+
+from __future__ import annotations
+
+# Export handlers
+from omnibase_infra.nodes.node_contract_persistence_effect.handlers import (
+    HandlerPostgresCleanupTopics,
+    HandlerPostgresContractUpsert,
+    HandlerPostgresDeactivate,
+    HandlerPostgresHeartbeat,
+    HandlerPostgresMarkStale,
+    HandlerPostgresTopicUpdate,
+)
+
+# Export the declarative node
+from omnibase_infra.nodes.node_contract_persistence_effect.node import (
+    NodeContractPersistenceEffect,
+)
+
+# Export registry
+from omnibase_infra.nodes.node_contract_persistence_effect.registry import (
+    RegistryInfraContractPersistenceEffect,
+)
+
+__all__: list[str] = [
+    # Node
+    "NodeContractPersistenceEffect",
+    # Registry
+    "RegistryInfraContractPersistenceEffect",
+    # Handlers
+    "HandlerPostgresCleanupTopics",
+    "HandlerPostgresContractUpsert",
+    "HandlerPostgresDeactivate",
+    "HandlerPostgresHeartbeat",
+    "HandlerPostgresMarkStale",
+    "HandlerPostgresTopicUpdate",
+]