mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
Every page now loads /webmcp.js, scripts/webmcp.ts with its types stripped (npm run webmcp). Where the browser has document.modelContext it registers two read-only tools: search_skills over the published skills index, and get_skill, which returns a skill's markdown checked against the index digest. The markdown alternate link moves from build.py to site.py, so CI holds every page to it. The API catalog gains the site itself (llms.txt and the skills index) and hanzo.ai/agents; the live discovery check now fetches every catalog link. tests/site.mjs drives the tools through a recording modelContext, and checks a browser without one loads clean.
614 lines
32 KiB
HTML
614 lines
32 KiB
HTML
<!doctype html>
|
|
<html lang="en"><head>
|
|
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
|
|
<title>engineering-rfc-consensus-building</title>
|
|
<meta name="color-scheme" content="dark">
|
|
<style>
|
|
/* Committed to one visual world: a dark instrument panel. No light variant —
|
|
the dot field and the hairline rules only read on black, and a naive
|
|
inversion would wash both out. Every colour is painted explicitly so the page
|
|
never borrows a host background. */
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
|
|
|
|
:root{
|
|
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
|
|
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
|
|
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
|
|
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
|
|
--font-zen-pixel-square:'Zen Pixel Square',monospace;
|
|
--mono:var(--font-zen-mono);
|
|
--sans:var(--font-zen-sans);
|
|
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
|
|
--r:999px; --r-soft:14px;
|
|
}
|
|
*{box-sizing:border-box}
|
|
html{-webkit-text-size-adjust:100%}
|
|
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
|
|
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
|
|
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
|
|
|
|
/* The dot field. A halftone made of one repeating radial-gradient, faded out
|
|
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
|
|
/* No overflow clip here: the dot field is inset to the box already, and a clip
|
|
would cut off the copy-prompt menu. */
|
|
.hero{position:relative;border-bottom:1px solid var(--line)}
|
|
.hero::before{content:"";position:absolute;inset:0;
|
|
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
|
|
background-size:7px 7px;
|
|
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
pointer-events:none}
|
|
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
|
|
|
|
nav{border-bottom:1px solid var(--line)}
|
|
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
|
|
justify-content:space-between;align-items:center;gap:1rem}
|
|
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--ink);text-decoration:none;
|
|
display:inline-flex;align-items:center;gap:.6rem}
|
|
.brand i{font-style:normal;color:var(--faint)}
|
|
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
|
|
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--soft);text-decoration:none}
|
|
nav a.up:hover{color:var(--ink)}
|
|
|
|
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
|
|
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
|
|
h1 em{font-style:normal;color:var(--faint)}
|
|
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
|
|
|
|
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
|
|
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
|
|
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
|
|
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
|
|
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
|
|
line-height:1.2;font-weight:400}
|
|
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
|
|
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
|
|
.btn.solid:hover{background:#d8d8d4}
|
|
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
|
|
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
|
|
|
|
/* Copy-prompt selector. Each row copies the prompt for its own target. */
|
|
.copy{position:relative;display:inline-flex}
|
|
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
|
|
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
|
|
padding:.4rem;display:flex;flex-direction:column;
|
|
box-shadow:0 12px 32px rgba(0,0,0,.75)}
|
|
.menu[hidden]{display:none}
|
|
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
|
|
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
|
|
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
|
|
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
|
|
white-space:nowrap}
|
|
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
|
|
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
|
|
.mi:hover .mark{color:var(--ink)}
|
|
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
|
|
letter-spacing:.1em;text-transform:uppercase}
|
|
|
|
/* Works-with bar: one scrolling row, name and mark per agent. */
|
|
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
|
|
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
|
|
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
|
|
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
|
|
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
|
|
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
|
|
display:flex;align-items:center}
|
|
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
|
|
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
|
|
-webkit-overflow-scrolling:touch;
|
|
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
|
|
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
|
|
.bar::-webkit-scrollbar{display:none}
|
|
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
|
|
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
|
|
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
|
|
text-decoration:none;background:var(--ground)}
|
|
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
|
|
.agent .mark{width:.95rem;height:.95rem}
|
|
|
|
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
|
|
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
|
|
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
|
|
p{margin:0 0 1rem;max-width:70ch}
|
|
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
|
|
li{margin:.22rem 0}
|
|
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
|
|
text-decoration-color:var(--line-hi)}
|
|
a:hover{text-decoration-color:var(--ink)}
|
|
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
|
|
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
|
|
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
|
|
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
|
|
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
|
|
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
|
|
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
|
|
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
|
|
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
|
|
display:block;overflow-x:auto}
|
|
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
|
|
|
|
.curl{display:block;background:var(--panel);border:1px solid var(--line);
|
|
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
|
|
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
|
|
white-space:pre;line-height:1.9}
|
|
.curl b{color:var(--ink);font-weight:400}
|
|
.curl i{font-style:normal;color:var(--faint)}
|
|
|
|
/* index */
|
|
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
|
|
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
|
|
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
|
|
#q:focus{outline:none;border-color:var(--soft)}
|
|
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
|
|
text-transform:uppercase;margin:0 0 2rem}
|
|
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
|
|
padding-bottom:.45rem}
|
|
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
|
|
border-radius:var(--r-soft);text-decoration:none}
|
|
.row:hover{background:#0a0a0a}
|
|
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
|
|
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
|
|
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
|
|
color:var(--faint);font-size:.85rem}
|
|
footer a{color:var(--soft)}
|
|
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
|
|
margin:0 0 2rem;font-size:.85rem}
|
|
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
|
|
border-bottom:1px solid var(--line);padding-bottom:.4rem}
|
|
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
|
|
.fmap a:hover{text-decoration:underline}
|
|
.fmap div{color:var(--faint);line-height:1.5}
|
|
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
|
|
|
|
@media (max-width:640px){
|
|
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
|
|
.btns{gap:.5rem}
|
|
.btn{padding:.75rem 1.15rem;font-size:.68rem}
|
|
.copy,.copy .btn{width:100%;justify-content:center}
|
|
.menu{left:0;right:0;min-width:0}
|
|
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
|
|
.strip b{border-right:0;padding-right:0}
|
|
.bar{width:100%}
|
|
}
|
|
</style>
|
|
<link rel="icon" href="/favicon.svg">
|
|
<link rel="canonical" href="https://hanzoskills.com/engineering-rfc-consensus-building">
|
|
<link rel="alternate" type="text/markdown" href="/engineering-rfc-consensus-building.md">
|
|
<script type="module" src="/webmcp.js"></script>
|
|
</head>
|
|
<!-- Reading this with a machine? Every page here is also plain markdown.
|
|
This one: https://hanzoskills.com/engineering-rfc-consensus-building.md
|
|
Index: https://hanzoskills.com/llms.txt
|
|
Corpus: https://hanzoskills.com/all.md
|
|
Append .md to any path for the markdown twin. -->
|
|
<body>
|
|
<nav><div class="in">
|
|
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
|
|
<a class="up" href="/">All skills</a>
|
|
</div></nav>
|
|
|
|
<div class="wrap">
|
|
<h1>engineering-rfc-consensus-building</h1><p class="lede">Stakeholder identification, feedback collection, consensus building, and approval processes for RFCs</p><h1>RFC Consensus Building</h1>
|
|
<p><strong>Scope</strong>: Techniques for identifying stakeholders, collecting feedback, building consensus, and driving RFC approval <strong>Lines</strong>: ~280 <strong>Last Updated</strong>: 2025-10-25 <strong>Format Version</strong>: 1.0 (Atomic)</p>
|
|
<hr>
|
|
<h2>When to Use This Skill</h2>
|
|
<p>Activate this skill when:</p>
|
|
<ul><li>Identifying who needs to review and approve your RFC</li><li>Collecting feedback from engineers, architects, and stakeholders</li><li>Addressing concerns and incorporating feedback into RFC</li><li>Facilitating design review meetings and Q&A sessions</li><li>Handling disagreements and driving consensus</li><li>Using decision frameworks (DACI, RACI) to clarify roles</li><li>Escalating decisions when consensus cannot be reached</li><li>Managing the RFC approval process from draft to approved</li></ul>
|
|
<h2>Core Concepts</h2>
|
|
<h3>Concept 1: Stakeholder Identification</h3>
|
|
<p><strong>Categories of Stakeholders</strong>:</p>
|
|
<ul><li><strong>Authors</strong>: Write and own the RFC</li><li><strong>Reviewers</strong>: Provide feedback and expertise (SMEs)</li><li><strong>Approvers</strong>: Have veto power, make final decision</li><li><strong>Implementers</strong>: Engineers who will build the solution</li><li><strong>Informed</strong>: Need to know, but not involved in decision</li></ul>
|
|
<p><strong>Identification Questions</strong>:</p>
|
|
<ul><li>Who is affected by this change? (users, teams, systems)</li><li>Who has expertise needed for review? (security, performance, data)</li><li>Who has authority to approve? (tech lead, architect, director)</li><li>Who will implement this? (frontend, backend, DevOps)</li><li>Who needs to be informed? (adjacent teams, leadership)</li></ul>
|
|
<h3>Concept 2: Feedback Collection Strategies</h3>
|
|
<p><strong>Async Feedback</strong> (Scale to many reviewers):</p>
|
|
<ul><li>Comments in Google Docs or GitHub PR</li><li>Slack threads for quick questions</li><li>Email for formal approvals</li></ul>
|
|
<p><strong>Sync Feedback</strong> (Deep discussions):</p>
|
|
<ul><li>Design review meetings (1 hour, 5-10 people)</li><li>Office hours (open Q&A slots)</li><li>One-on-one walkthroughs (for key stakeholders)</li></ul>
|
|
<p><strong>Structured Feedback</strong>:</p>
|
|
<ul><li>Request specific feedback areas (e.g., "Review security section")</li><li>Set deadlines (e.g., "Please review by Friday")</li><li>Use comment templates (e.g., "Blocking concern" vs "Nice-to-have")</li></ul>
|
|
<h3>Concept 3: DACI Decision Framework</h3>
|
|
<p><strong>Driver</strong>: Owns the RFC and drives to decision</p>
|
|
<ul><li>Responsible for drafting, collecting feedback, updating RFC</li><li>Facilitates meetings and discussions</li><li>Proposes decision to Approver</li></ul>
|
|
<p><strong>Approver</strong>: Makes final decision</p>
|
|
<ul><li>Has veto power</li><li>Accountable for outcome</li><li>Typically tech lead, architect, or engineering manager</li></ul>
|
|
<p><strong>Contributors</strong>: Provide input and feedback</p>
|
|
<ul><li>Subject matter experts (security, performance, data)</li><li>Affected teams (frontend, backend, DevOps)</li><li>No veto power, but concerns must be addressed</li></ul>
|
|
<p><strong>Informed</strong>: Kept in the loop</p>
|
|
<ul><li>Adjacent teams, leadership</li><li>Notified when decision is made</li><li>Can comment but not required</li></ul>
|
|
<hr>
|
|
<h2>Patterns</h2>
|
|
<h3>Pattern 1: Stakeholder Mapping for RFC</h3>
|
|
<p><strong>When to use</strong>:</p>
|
|
<ul><li>Starting RFC process</li><li>Ensuring all affected parties are included</li></ul>
|
|
<pre><code class="lang-markdown">## Stakeholder Map: Real-Time Collaboration RFC
|
|
|
|
### DACI Roles
|
|
|
|
**Driver**: @alex (backend engineer)
|
|
- Owns RFC creation and updates
|
|
- Drives consensus and decision
|
|
|
|
**Approver**: @engineering-lead (CTO)
|
|
- Final decision authority
|
|
- Approves or rejects RFC
|
|
|
|
**Contributors** (Must Review):
|
|
- @jordan (backend): WebSocket server design
|
|
- @taylor (frontend): Client-side editor integration
|
|
- @sam (product): Product requirements alignment
|
|
- @charlie (security): Authentication and rate limiting
|
|
- @dana (DevOps): Infrastructure and scaling plan
|
|
|
|
**Informed** (Notified, Optional Review):
|
|
- [email protected] (all engineers)
|
|
- [email protected] (product team)
|
|
- [email protected] (exec team)
|
|
|
|
### Review Timeline
|
|
- **Draft**: 2025-10-25 (author completes)
|
|
- **Review Start**: 2025-10-26 (invite contributors)
|
|
- **Feedback Deadline**: 2025-11-01 (5 business days)
|
|
- **Design Review Meeting**: 2025-11-02 (1 hour, sync discussion)
|
|
- **Final Decision**: 2025-11-03 (approver decides)
|
|
|
|
### Communication Plan
|
|
- **Draft ready**: Slack #engineering channel, tag contributors
|
|
- **Feedback reminder**: Email 2 days before deadline
|
|
- **Meeting invite**: Calendar invite with RFC link in description
|
|
- **Decision announcement**: Slack + email to "Informed" group</code></pre>
|
|
<h3>Pattern 2: Feedback Collection Template</h3>
|
|
<p><strong>Use case</strong>: Requesting structured feedback from reviewers</p>
|
|
<pre><code class="lang-markdown">## Review Request: RFC-042 Real-Time Collaboration
|
|
|
|
Hi @jordan, @taylor, @charlie,
|
|
|
|
I've completed the draft for **RFC-042: Real-Time Collaboration**.
|
|
Please review by **Friday, Nov 1** and provide feedback.
|
|
|
|
**RFC Link**: [Google Doc / GitHub PR]
|
|
|
|
**Specific Feedback Needed**:
|
|
- @jordan (Backend): Review WebSocket server design (Section 3.2)
|
|
- @taylor (Frontend): Validate client editor integration (Section 3.3)
|
|
- @charlie (Security): Review auth and rate limiting (Section 5)
|
|
|
|
**Feedback Format**:
|
|
- **Blocking Concern**: "This must be addressed before approval"
|
|
- **Strong Suggestion**: "Recommend changing, but not blocking"
|
|
- **Question**: "Need clarification"
|
|
- **Nice-to-Have**: "Optional improvement"
|
|
|
|
**Design Review Meeting**: Tuesday, Nov 2 at 2pm (1 hour)
|
|
- We'll discuss blocking concerns and unresolved questions
|
|
- Please add questions to RFC comments beforehand
|
|
|
|
Thanks!
|
|
@alex</code></pre>
|
|
<h3>Pattern 3: Design Review Meeting Agenda</h3>
|
|
<p><strong>Use case</strong>: Facilitating effective sync discussion</p>
|
|
<pre><code class="lang-markdown">## Design Review: RFC-042 Real-Time Collaboration
|
|
|
|
**Date**: 2025-11-02, 2:00 PM - 3:00 PM
|
|
**Location**: Zoom [link] / Conference Room B
|
|
**Attendees**: @alex (driver), @jordan, @taylor, @charlie, @sam, @engineering-lead
|
|
|
|
### Agenda (60 minutes)
|
|
|
|
**1. Context & Goals (5 min)** - @alex
|
|
- Briefly recap problem statement and proposed solution
|
|
- Clarify goals: real-time editing, <200ms latency, 50 concurrent users
|
|
|
|
**2. Architecture Overview (10 min)** - @alex
|
|
- Walk through architecture diagram (C4 Level 2)
|
|
- Explain WebSocket + OT + Redis approach
|
|
- Q&A on high-level design
|
|
|
|
**3. Blocking Concerns (20 min)** - All
|
|
- **Concern 1** (@charlie): "How do we prevent DoS attacks on WebSocket server?"
|
|
- Proposed mitigation: Rate limiting (100 ops/sec per user)
|
|
- Decision: Add to RFC Section 5.2
|
|
- **Concern 2** (@jordan): "What happens if Redis goes down?"
|
|
- Proposed mitigation: Fallback to Postgres snapshots, auto-reconnect
|
|
- Decision: Add to RFC Section 6.3 (Failure Modes)
|
|
|
|
**4. Alternative Approaches (15 min)** - All
|
|
- Discussion: Why OT over CRDTs?
|
|
- Discussion: Why Redis over in-memory state?
|
|
- Ensure alternatives are adequately documented
|
|
|
|
**5. Open Questions (5 min)** - All
|
|
- Q: Should we support audio/video chat? → Decision: No, defer to Q2
|
|
- Q: Max document size? → Decision: 50k chars, show warning
|
|
|
|
**6. Next Steps & Decision (5 min)** - @engineering-lead
|
|
- @alex: Update RFC with feedback by Nov 3
|
|
- @engineering-lead: Review updated RFC and approve by Nov 4
|
|
- If approved: Start implementation in Sprint 12
|
|
|
|
### Meeting Notes
|
|
[Collaborative doc for notes during meeting]</code></pre>
|
|
<h3>Pattern 4: Handling Disagreements</h3>
|
|
<p><strong>Use case</strong>: Driving consensus when reviewers disagree</p>
|
|
<pre><code class="lang-markdown">## Disagreement: Database Choice (Postgres vs MongoDB)
|
|
|
|
### Positions
|
|
**@alice (Backend Lead)**: Prefers PostgreSQL
|
|
- Rationale: ACID transactions required for billing
|
|
- Concern: MongoDB lacks strong consistency guarantees
|
|
|
|
**@bob (Data Engineer)**: Prefers MongoDB
|
|
- Rationale: Flexible schema for rapidly changing product
|
|
- Concern: Postgres schema migrations are slow and risky
|
|
|
|
### Discussion Framework
|
|
|
|
**Step 1: Clarify Requirements**
|
|
- Q: Do we need ACID for billing? (Legal/compliance requirement?)
|
|
- Answer: Yes, financial regulations require strong consistency
|
|
- Q: How often do we change schema?
|
|
- Answer: ~2-3 times per quarter (moderate frequency)
|
|
|
|
**Step 2: Evaluate Trade-offs**
|
|
| Requirement | Postgres | MongoDB | Winner |
|
|
|-------------|----------|---------|--------|
|
|
| ACID for billing | ✅ Strong | ❌ Weak | Postgres |
|
|
| Schema flexibility | ⚠️ Migrations | ✅ Flexible | MongoDB |
|
|
| Team expertise | ✅ High | ⚠️ Medium | Postgres |
|
|
| Query richness | ✅ SQL | ⚠️ Limited | Postgres |
|
|
|
|
**Step 3: Seek Compromise**
|
|
- Hybrid approach: Postgres for billing, MongoDB for user-generated content?
|
|
- Rejected: Too complex for small team (2 databases to maintain)
|
|
- Use Postgres with JSONB for flexible fields?
|
|
- Accepted: JSONB columns provide schema flexibility where needed
|
|
|
|
**Step 4: Decision**
|
|
- **Chosen**: PostgreSQL with JSONB for flexible fields
|
|
- **Rationale**: ACID is non-negotiable, JSONB solves schema flexibility
|
|
- **Concession**: Invest in migration tooling (Alembic) to reduce risk
|
|
|
|
**Step 5: Document Decision**
|
|
- Update RFC Section 4 (Alternatives Considered)
|
|
- Create ADR-007: "Why Postgres over MongoDB"
|
|
- @bob: Acknowledge concern addressed, approve RFC</code></pre>
|
|
<h3>Pattern 5: Escalation Process</h3>
|
|
<p><strong>Use case</strong>: When consensus cannot be reached</p>
|
|
<pre><code class="lang-markdown">## Escalation: Real-Time Collaboration - Performance Concerns
|
|
|
|
### Deadlock Scenario
|
|
- @jordan (Backend): "OT is too complex, will cause bugs"
|
|
- @alex (Driver): "OT is industry standard, proven by Google Docs"
|
|
- **Cannot reach consensus** after 2 design reviews
|
|
|
|
### Escalation Steps
|
|
|
|
**Step 1: Document Positions**
|
|
- @jordan's concern: OT has steep learning curve, risk of bugs
|
|
- Evidence: 5 similar projects had OT bugs in first 6 months
|
|
- @alex's position: OT is only proven solution for text editing
|
|
- Evidence: Google Docs, Figma, Notion all use OT successfully
|
|
|
|
**Step 2: Identify Decision Criteria**
|
|
- What matters most: correctness, time-to-market, or team expertise?
|
|
- Product says: Time-to-market (ship in Q1)
|
|
- Engineering says: Correctness (no data loss)
|
|
|
|
**Step 3: Escalate to Approver**
|
|
- Present both positions to @engineering-lead (Approver)
|
|
- Include: Trade-off matrix, evidence, recommended decision
|
|
|
|
**Step 4: Approver Decision**
|
|
- @engineering-lead: "Correctness is critical, accept slower time-to-market"
|
|
- **Decision**: Use OT, allocate 2 extra weeks for thorough testing
|
|
- **Mitigation**: Hire consultant with OT expertise (reduce risk)
|
|
|
|
**Step 5: Document and Move Forward**
|
|
- Update RFC with decision rationale
|
|
- @jordan: Acknowledge concern heard, move forward with team
|
|
- Plan: Weekly check-ins on OT implementation progress</code></pre>
|
|
<h3>Pattern 6: Incorporating Feedback</h3>
|
|
<p><strong>Use case</strong>: Updating RFC based on review comments</p>
|
|
<pre><code class="lang-markdown">## Feedback Integration Log
|
|
|
|
### Feedback Received (2025-11-01)
|
|
|
|
**@jordan (Backend)**: "What's the fallback if Redis goes down?"
|
|
- **Type**: Blocking concern
|
|
- **Action**: Added Section 6.3 (Failure Modes)
|
|
- **Resolution**: Fallback to Postgres snapshots, auto-reconnect with backoff
|
|
|
|
**@taylor (Frontend)**: "How do we display cursors for 50 users?"
|
|
- **Type**: Question
|
|
- **Action**: Added Section 3.4 (Client UI Design)
|
|
- **Resolution**: Show top 10 active users, aggregate others as "+40 more"
|
|
|
|
**@charlie (Security)**: "Rate limiting is too low (100 ops/sec)"
|
|
- **Type**: Strong suggestion
|
|
- **Action**: Updated Section 5.2 (Rate Limiting)
|
|
- **Resolution**: Changed to 200 ops/sec (allow burst typing), with burst allowance
|
|
|
|
**@sam (Product)**: "Should we support markdown formatting?"
|
|
- **Type**: Nice-to-have
|
|
- **Action**: Added to "Future Work" section
|
|
- **Resolution**: Defer to v2, focus on plain text for MVP
|
|
|
|
### Changes Made
|
|
- ✅ Section 6.3 added: Failure mode analysis
|
|
- ✅ Section 3.4 added: Cursor display strategy
|
|
- ✅ Section 5.2 updated: Rate limit 100→200 ops/sec
|
|
- ✅ Future Work section: Markdown formatting for v2
|
|
|
|
### Changelog Entry</code></pre>
|
|
<h2>Version 1.2 (2025-11-01)</h2>
|
|
<ul><li>Added failure mode analysis (Redis downtime)</li><li>Clarified cursor display strategy (top 10 users)</li><li>Increased rate limit to 200 ops/sec per feedback</li><li>Moved markdown formatting to future work</li></ul>
|
|
<pre><code>
|
|
### Re-Review Request
|
|
"I've updated the RFC based on your feedback. Please review v1.2 and confirm blocking concerns are addressed."</code></pre>
|
|
<h3>Pattern 7: Approval Checklist</h3>
|
|
<p><strong>Use case</strong>: Ensuring all approval criteria are met</p>
|
|
<pre><code class="lang-markdown">## RFC Approval Checklist
|
|
|
|
### Pre-Approval Requirements
|
|
- [x] All contributors have reviewed RFC
|
|
- [x] Blocking concerns addressed
|
|
- [x] Alternatives documented and evaluated
|
|
- [x] Risks and mitigations identified
|
|
- [x] Design review meeting completed (2025-11-02)
|
|
- [x] RFC updated with feedback (v1.2)
|
|
- [x] Approver has reviewed final version
|
|
|
|
### Contributor Sign-offs
|
|
- [x] @jordan (Backend): Approved (2025-11-01)
|
|
- Comment: "Failure modes addressed, looks good"
|
|
- [x] @taylor (Frontend): Approved (2025-11-01)
|
|
- Comment: "Cursor strategy is clear, ready to implement"
|
|
- [x] @charlie (Security): Approved with caveat (2025-11-01)
|
|
- Comment: "Approved. Monitor rate limit, may need adjustment post-launch"
|
|
- [x] @sam (Product): Approved (2025-11-02)
|
|
- Comment: "Aligned with product goals, ship it!"
|
|
|
|
### Approver Decision
|
|
- [x] @engineering-lead: **APPROVED** (2025-11-03)
|
|
- Comment: "Well-documented, consensus reached, proceed with implementation"
|
|
|
|
### Next Steps
|
|
- [x] Update RFC status: Draft → Approved
|
|
- [x] Announce decision to "Informed" group (Slack #engineering)
|
|
- [ ] Create implementation tasks (Jira/Linear)
|
|
- [ ] Kick off Sprint 12 implementation</code></pre>
|
|
<h3>Pattern 8: Post-Approval Communication</h3>
|
|
<p><strong>Use case</strong>: Announcing decision and next steps</p>
|
|
<pre><code class="lang-markdown">## Announcement: RFC-042 Real-Time Collaboration - APPROVED
|
|
|
|
**To**: [email protected], [email protected]
|
|
**From**: @alex
|
|
**Date**: 2025-11-03
|
|
|
|
Hi team,
|
|
|
|
Great news! **RFC-042: Real-Time Collaboration** has been approved by @engineering-lead.
|
|
|
|
### Summary
|
|
We'll be implementing real-time collaborative editing using WebSocket + Operational Transform (OT) + Redis. This will enable 2-50 users to edit documents simultaneously with <200ms latency.
|
|
|
|
### What's Next
|
|
- **Implementation**: Starts Sprint 12 (Nov 6)
|
|
- **Timeline**: MVP targeted for Q1 2025
|
|
- **Team**: @alex (lead), @jordan (backend), @taylor (frontend)
|
|
|
|
### Key Decisions
|
|
- **Tech Stack**: WebSocket (ws), OT (ot.js), Redis, Postgres
|
|
- **Alternatives Rejected**: CRDTs (larger payloads), polling (high latency)
|
|
- **Risks Mitigated**: Redis failover, rate limiting, OT testing
|
|
|
|
### How You Can Help
|
|
- **Try the alpha** (internal only, Week 3-4 of Sprint 12)
|
|
- **Provide feedback** on UX and performance
|
|
- **Report bugs** in #collab-bugs channel
|
|
|
|
### RFC Document
|
|
Read the full RFC here: [link to Google Doc / GitHub]
|
|
|
|
Questions? Ping me in Slack or join office hours (Fridays 2-3pm).
|
|
|
|
Thanks to everyone who reviewed and provided feedback!
|
|
|
|
@alex</code></pre>
|
|
<hr>
|
|
<h2>Quick Reference</h2>
|
|
<h3>Stakeholder Identification</h3>
|
|
<pre><code>Role | Responsibility | Example
|
|
-----|----------------|--------
|
|
Driver | Owns RFC, drives consensus | RFC author
|
|
Approver | Final decision authority | Tech lead, CTO
|
|
Contributors | Provide feedback, SMEs | Backend lead, security
|
|
Implementers | Build the solution | Frontend/backend engineers
|
|
Informed | Kept in loop | Adjacent teams, leadership</code></pre>
|
|
<h3>Feedback Types</h3>
|
|
<pre><code>Type | Definition | Action Required
|
|
-----|------------|------------------
|
|
Blocking Concern | Must be addressed | Update RFC, re-review
|
|
Strong Suggestion | Recommend changing | Consider, justify if rejected
|
|
Question | Need clarification | Answer in RFC or comments
|
|
Nice-to-Have | Optional improvement | Defer to future work</code></pre>
|
|
<h3>DACI Framework</h3>
|
|
<pre><code>DACI Role | Power | Count
|
|
----------|-------|------
|
|
Driver | Drives process | 1 person
|
|
Approver | Veto power | 1 person (or small group)
|
|
Contributors | Feedback, no veto | 3-10 people
|
|
Informed | Notified | Unlimited</code></pre>
|
|
<h3>Key Guidelines</h3>
|
|
<pre><code>✅ DO: Identify all stakeholders upfront (DACI framework)
|
|
✅ DO: Set clear deadlines for feedback
|
|
✅ DO: Facilitate design review meetings for sync discussion
|
|
✅ DO: Address blocking concerns before seeking approval
|
|
✅ DO: Document disagreements and how they were resolved
|
|
|
|
❌ DON'T: Skip stakeholder identification (surprises later)
|
|
❌ DON'T: Ignore feedback (causes resentment, delays)
|
|
❌ DON'T: Rush to approval (consensus takes time)
|
|
❌ DON'T: Avoid conflict (address disagreements head-on)
|
|
❌ DON'T: Forget to announce decision (inform stakeholders)</code></pre>
|
|
<hr>
|
|
<h2>Anti-Patterns</h2>
|
|
<h3>Critical Violations</h3>
|
|
<p>❌ <strong>Skipping Stakeholder Identification</strong>: Not involving key reviewers</p>
|
|
<pre><code class="lang-markdown"># ❌ NEVER:
|
|
Write RFC → Send to engineering-lead for approval → Skip team review
|
|
|
|
# ✅ CORRECT:
|
|
Write RFC → Identify stakeholders (DACI) → Collect feedback → Address concerns → Seek approval</code></pre>
|
|
<p>❌ <strong>Ignoring Blocking Concerns</strong>: Pushing for approval despite unresolved issues ✅ <strong>Correct approach</strong>: Address all blocking concerns, update RFC, re-review</p>
|
|
<h3>Common Mistakes</h3>
|
|
<p>❌ <strong>No Feedback Deadline</strong>: Open-ended review period</p>
|
|
<pre><code class="lang-markdown"># ❌ Don't:
|
|
"Please review when you have time"
|
|
|
|
# ✅ Correct:
|
|
"Please review by Friday, Nov 1 (5 business days)"</code></pre>
|
|
<p>❌ <strong>Async-Only for Complex RFCs</strong>: No sync discussion for controversial topics ✅ <strong>Better</strong>: Schedule design review meeting for deep discussions</p>
|
|
<p>❌ <strong>Defensive Responses to Feedback</strong>: Arguing instead of listening</p>
|
|
<pre><code class="lang-markdown"># ❌ Don't:
|
|
Reviewer: "This won't scale"
|
|
Author: "You're wrong, it will"
|
|
|
|
# ✅ Correct:
|
|
Reviewer: "This won't scale"
|
|
Author: "Can you elaborate? What scale are you concerned about?"
|
|
[Discuss, update RFC with scaling plan]</code></pre>
|
|
<p>❌ <strong>No Decision Documentation</strong>: Approving without documenting rationale ✅ <strong>Better</strong>: Update RFC with decision, rationale, and next steps</p>
|
|
<hr>
|
|
<h2>Related Skills</h2>
|
|
<ul><li><code>rfc-structure-format.md</code> - RFC document templates and formatting</li><li><code>rfc-technical-design.md</code> - Designing architecture and evaluating alternatives</li><li><code>rfc-decision-documentation.md</code> - Documenting decisions and ADRs</li><li><code>product/prd-requirements-gathering.md</code> - Stakeholder interviews (product side)</li></ul>
|
|
<hr>
|
|
<p><strong>Last Updated</strong>: 2025-10-25 <strong>Format Version</strong>: 1.0 (Atomic)</p>
|
|
<footer>
|
|
<div class="fmap">
|
|
<div><b>Build</b>
|
|
<a href="https://hanzo.app">hanzo.app</a> app builder
|
|
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
|
|
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
|
|
<div><b>Run</b>
|
|
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
|
|
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
|
|
<div><b>Account</b>
|
|
<a href="https://hanzo.id">hanzo.id</a> sign in
|
|
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
|
|
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
|
|
<div><b>Company</b>
|
|
<a href="https://hanzo.ai">hanzo.ai</a> canonical
|
|
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
|
|
</div>
|
|
<div class="fend"><a href="/engineering-rfc-consensus-building.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
|
|
</footer>
|
|
</div></body></html> |