Cas orchestration flow
sequenceDiagram
participant U as Ingestion Layer
participant RC as Rule Context Loader
participant AW as Architecture Work Generator
participant AEMG as AEM Generator
participant AE as Alignment Engine
participant AID as AID Generator
participant KL as Knowledge Layer
participant OI as Operational Intelligence
U->>RC: Provide context input
Note over U: Business requirements / Code changes / Conversation
RC->>RC: Load global rules + project rules
Note over RC: Governance-aware operational participation boundaries loaded into execution context
RC-->>KL: Persist rule_context
Note over KL: rule_context (in-memory / passed downstream)<br/>from knowledge/global/rules/ + knowledge/projects/<project>/rules/
RC->>AW: Pass context + rule_context
AW->>AW: Extract architecture_work + operational governance signals from context
AW-->>KL: Persist architecture_work
Note over KL: knowledge/projects/<project>/work/aw-*.md
AW->>AEMG: Provide architecture_work + rule_context
AEMG->>AEMG: Update AEM
Note over AEMG: Execution-driven governance evolution and operational participation signals continuously refine architectural state
AEMG-->>KL: Persist AEM
Note over KL: knowledge/global/maps/aem-*.md
AEMG->>AE: Provide updated AEM + rule_context
AE->>AE: Analyse AEM + ADR + rules + diagrams + operational participation alignment
AE-->>KL: Persist alignment findings + new architecture_work proposals
AE->>OI: Emit governance drift + operational intelligence signals
OI->>OI: Synthesize participation, capability evolution, and governance intelligence
OI-->>KL: Persist operational intelligence insights
Note over KL: knowledge/projects/<project>/alignment/alignment-report-*.md
AE->>AID: Provide updated AEM + findings
AID->>AID: Align intent with updated AEM
Note over AID: Architecture intent continuously operationalized through governance-aware participation loops
AID-->>KL: Persist AID
Note over KL: knowledge/projects/<project>/intent/architecture-intent-document*.md
participant GOV as Governance Forum
AW->>GOV: Submit accepted decisions
Note over GOV: Governance participation evolves through execution feedback, operational learning, and lightweight refinement
Note over GOV: Triggers pattern-evolution-flow (ADR, decision lifecycle, pattern sync)
Note over GOV: See pattern-evolution-flow for decision lifecycle (ADR, governance, pattern sync)
Note over GOV,KL: Governance Foundation v1 stabilized. Future evolution prioritizes operational experimentation over governance abstraction expansion
GOV-->>KL: Update ADRs and patterns
Note over KL: knowledge/global/decisions/ and knowledge/global/patterns/
See Also