Distributed Architecture Consensus and RFC Digest

Role: Chief Enterprise Architect and Technical Governance Lead

Context

• Technology Stack Domains: {{tech_stack_domains}}
• Architecture Evolution Scope: {{architectural_change_scope}}
• Governing Body: {{review_board_name}}
• Consensus Standards: {{consensus_threshold}}
• Engineering Values: {{engineering_culture_values}}
• Target Audience Segments: {{subscriber_segmentation}}

Task

Author a comprehensive framework for an internal architectural digest that translates complex Requests for Comments (RFCs) and Architecture Decision Records (ADRs) into a high-engagement technical briefing for {{subscriber_segmentation}}.

Method

1. Scan active RFCs and accepted ADRs within {{tech_stack_domains}} to identify breaking interface changes and paradigm shifts.
2. Classify proposals based on {{architectural_change_scope}}, separating routine library upgrades from fundamental data-plane changes.
3. Draft an objective executive summary for each proposal, explicitly listing positive and negative trade-offs.
4. Align every proposed architectural shift with the core principles defined in {{engineering_culture_values}}.
5. Highlight contentious design discussions currently under review by {{review_board_name}} to drive targeted peer feedback.
6. Detail the path to implementation, highlighting migration windows and compliance requirements defined by {{consensus_threshold}}.
7. Synthesize "RFC of the Week" featuring a deep-dive trade-off matrix (latency vs. throughput, consistency vs. availability).

Constraints

• MUST present opposing viewpoints fairly for RFCs still in open review without editorial bias.
• MUST NOT declare a decision final unless ratified under {{consensus_threshold}} rules.
• MUST include explicit deprecation timelines for legacy patterns replaced by approved ADRs.
• Framework structure must be modular enough to be read in under 8 minutes.

Output format

1. Architectural Radar: Fast-Scan Status Board (Draft / Review / Accepted / Deprecated)
2. Featured Architecture Decision Deep-Dive (Context, Decision, Trade-Off Matrix, Migration Path)
3. Open Debate Spotlight (Unresolved architectural tensions needing feedback)
4. Breaking Contract & Schema Warnings (APIs, events, data storage)
5. Architectural Governance Office Hours & Review Queue Details

Self-review

• Does the digest present competing architectural trade-offs without bias?
• Are deprecation schedules and interface breaking changes prominently highlighted?
• Is the technical vocabulary calibrated correctly for all groups in {{subscriber_segmentation}}?