-
-
Notifications
You must be signed in to change notification settings - Fork 1
Define cross-zome interface types for governance-as-operator protocol #41
Copy link
Copy link
Open
Labels
P2-highHigh priority - important for milestone completionHigh priority - important for milestone completioncross-zomeCross-zome integration and coordinationCross-zome integration and coordinationphase-2-governancePhase 2 - Enhanced governance & process integration (current)Phase 2 - Enhanced governance & process integration (current)valueflowsValueFlows ontology compliance and integrationValueFlows ontology compliance and integrationzome-governanceGovernance zome - validation, economic events, commitmentsGovernance zome - validation, economic events, commitments
Milestone
Metadata
Metadata
Assignees
Labels
P2-highHigh priority - important for milestone completionHigh priority - important for milestone completioncross-zomeCross-zome integration and coordinationCross-zome integration and coordinationphase-2-governancePhase 2 - Enhanced governance & process integration (current)Phase 2 - Enhanced governance & process integration (current)valueflowsValueFlows ontology compliance and integrationValueFlows ontology compliance and integrationzome-governanceGovernance zome - validation, economic events, commitmentsGovernance zome - validation, economic events, commitments
Type
Projects
Status
Backlog
Summary
Define the shared data structures that enable the governance-as-operator pattern: the Resource Zome requests state transitions, the Governance Zome evaluates and decides, and the Resource Zome applies approved changes.
These types form the communication contract between the resource and governance zomes.
Context
The governance-as-operator architecture (see
documentation/specifications/governance/governance-operator-architecture.md) establishes a clear separation where:This issue creates the foundational types that both zomes depend on.
Technical Implementation
1. Core Request/Result Types
Define in a shared location (e.g.,
nondominium_utilsor a new shared types crate):2. Governance Decision Tracking
3. Error Types
4. Placement Decision
Decide whether to:
nondominium_utilscrate with these typesnondominium_typesshared crateAcceptance Criteria
GovernanceTransitionRequestandTransitionContextdefined and serializableGovernanceTransitionResultdefined with all fieldsGovernanceDecisionandResourceStateChangedefinedGovernanceOperatorErrorenum covers cross-zome failure modesDependencies
Definition of Done