Engineering Architecture Digest Architecture Spec

Role: Principal Systems Architect specializing in engineering communication and distributed systems design.

Context

• Target engineering tier: {{target_engineering_tiers}}
• Core technology stack: {{org_tech_stack}}
• Primary failure domains: {{primary_failure_domains}}
• Strategic architecture roadmap: {{architectural_evolution_goals}}
• Newsletter frequency: {{digest_cadence}}
• Data and telemetry inputs: {{telemetry_sources}}

Task

Generate a production-grade newsletter publication specification that defines the structural schema, technical depth criteria, code snippet formatting, and curation workflow for an internal architecture and systems engineering newsletter.

Method

1. Analyze the system architecture context across {{org_tech_stack}} to identify core technical domains and edge cases.
2. Establish content hierarchy spanning Architectural Decision Records (ADRs), distributed tracing case studies, and telemetry highlights from {{telemetry_sources}}.
3. Define a modular issue blueprint balancing high-level architectural trade-offs with low-level kernel or runtime considerations for {{target_engineering_tiers}}.
4. Design strict guidelines for code excerpts, ASCII system topology diagrams, and diff-style refactoring walk-throughs targeting {{primary_failure_domains}}.
5. Establish objective editorial filters to prevent vendor hype and prioritize real-world reliability metrics aligning with {{architectural_evolution_goals}}.
6. Formulate a sustainable content ingestion and vetting cadence tailored for {{digest_cadence}}.
7. Detail failure-mode post-mortem translation rules to turn proprietary outages into reusable architectural patterns.
8. Specify reader feedback loops including pull-request based contribution workflows and technical errata processes.

Constraints

• MUST maintain senior engineering rigor without marketing jargon or generic high-level summaries.
• MUST mandate exact code block specifications, including language tags and line-limit constraints.
• MUST NOT exceed the bounds of the provided infrastructure stack {{org_tech_stack}}.
• Every architectural pattern referenced must include explicit trade-off vectors (latency, throughput, operational complexity).

Output format

Provide the specification organized into four distinct sections:

1. Newsletter Structural Schema (sections, visual wireframe layout, word counts)
2. Technical Content Policy (code standards, ADR inclusion criteria, telemetry rules)
3. Production and Review Pipeline (intake, peer review, publishing checklist)
4. Sample Issue Wireframe (fully drafted skeleton issue with placeholder architecture topics)

Self-review

• Does the spec explicitly address all failure domains listed in {{primary_failure_domains}}?
• Are code snippet constraints deterministic and actionable for senior engineers?
• Does the publication pipeline integrate cleanly with the {{digest_cadence}} release cycle?