Morphism Foundational Framework Governance Prompt V2

assetactive

Morphism Foundational Framework Governance Prompt V2

Source: morphism-foundational-framework-governance-prompt-v2.md (ingested 2026-03-28)

Develop a comprehensive foundational framework document that meticulously defines the core tenets, operational rules, guided workflows, agent behaviors, system states, and drift detection mechanisms for the entire system. This document is critical as all subsequent system components and functionalities will depend directly on these definitions.

Specific Requirements:

  1. Core Tenets/Principles:

    • Clearly articulate the fundamental principles and architectural pillars that govern the system's design, behavior, and evolution.
    • Provide detailed explanations for each tenet, outlining its significance, implications, and how it influences system decisions.
    • Physics-Based Analogies: For each core tenet, formulate a sensible and provable analogy drawn from physics or natural sciences. These analogies must effectively illustrate the tenet's concept, behavior, or impact within the system, enhancing understanding and providing a robust mental model.

  2. Rules and Guides (Policies & Constraints):

    • Define all governing rules, policies, constraints, and best practices that dictate system behavior, data integrity, security, and operational procedures.
    • Categorize rules (e.g., business logic, technical constraints, security policies, compliance requirements).
    • Specify the enforcement mechanisms and monitoring strategies for each rule.

  3. Workflows:

    • Document all critical system workflows, illustrating the precise sequence of operations, decision points, and interactions between different components or agents.
    • Utilize clear diagrams (e.g., flowcharts, BPMN diagrams) accompanied by detailed textual descriptions.
    • Identify all inputs, outputs, preconditions, postconditions, and potential error paths for each workflow.

  4. Agents and States:

    • Agents: Identify and define all active entities or "agents" within the system (e.g., user roles, automated services, microservices, specific modules). Describe their roles, responsibilities, capabilities, and interaction patterns.
    • States: Define all significant system states and the states of key entities or data. Document the transitions between these states, the events that trigger state changes, and the conditions under which these transitions occur. Employ state diagrams where beneficial.

  5. Drift Detection and Management:

    • Establish clear definitions and mechanisms for identifying "drift," which refers to any deviation from the defined tenets, rules, workflows, or expected states.
    • Specify how drift will be detected, measured, reported, and remediated.
    • Address both configuration drift (deviation from intended configuration) and behavioral drift (deviation from expected operational behavior).

Deliverables:

  • A comprehensive "Foundational Framework Document" (e.g., a structured Markdown document, Confluence page, or dedicated architectural specification).
  • Detailed definitions and explanations for each component listed above.
  • Clearly articulated physics-based analogies for each core tenet, including justification for their sensibility and provability.
  • All necessary diagrams (workflow diagrams, state diagrams, agent interaction diagrams) to visually represent the defined concepts.

Quality Standards:

  • Clarity and Precision: All definitions, descriptions, and analogies must be unambiguous, precise, and easily understandable by both technical and non-technical stakeholders.
  • Completeness: The document must comprehensively cover all foundational aspects, leaving no critical element undefined or underspecified.
  • Consistency: Maintain absolute consistency in terminology, definitions, and analogies throughout the entire document.
  • Verifiability: Physics-based analogies must be logically sound, demonstrably relevant to the system concept, and withstand rigorous scrutiny.
  • Actionability: The document must provide a clear, unambiguous, and actionable basis for all subsequent design, development, testing, and operational activities.
  • Maintainability: The document structure must facilitate easy updates, revisions, and version control as the system evolves.