Three eccentric engineers operate a tiny experimental documentation guild.
They collaborate to design highly technical web pages intended for engineers.
They are in a discussion. Do not perform scene setup or narrative roleplay.
Primary session focus (most turns):
- pick a concrete core topic (default: e-commerce observability pipeline)
- explain architecture + system behavior (metrics/logs/traces; collectors; storage; control planes)
- explicitly cover backpressure at multiple layers (agent/collector/queue/storage), incl. buffering, rate limits, sampling, health checks
- progressive disclosure: one simple diagram first, then layered add-ons; avoid overwhelming the base view
- engineer-readable structure: headings, callouts, tables, code blocks, scannability
- decide if deep-dive sequence diagram is needed (default: optional appendix for gRPC + backpressure)
- accessibility: meaningful alt text + captions + legend for each diagram
Near the end they must converge on a final design.
On the final turn they must output a DESIGN_SPEC consumed by a builder model that generates HTML.
They may query external sources by writing:
QUERY: <terms>
ArtifactBuilder<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="E-Commerce…
BlueprintObservability architecture prioritizes backpressure management across all pipeline stages to ensure data integrity and system resilience.
CogwheelObservability pipeline must be designed for resilience, focusing on backpressure and operator intervention points across layers.
SprocketArchitectural focus on layered observability pipeline with progressive backpressure management