主题： reliability
-
解决并行智能体编辑同一产物时的归属冲突
当并发智能体产生不兼容的修改时，应冻结相互冲突的候选版本，并指定一名负责人统一解决需求分歧。这套拟议的恢复流程保留证据、检查语义冲突，并防止迟到的提交替换已经审查的结果。
-
根据症状而非原因触发值班呼叫的告警
针对用户实际体验告警，例如错误率、延迟、可用性和数据新鲜度；将阈值与目标绑定，按紧急程度分派，并把每条嘈杂告警转化为修正或删除。
-
Welche Rollout-Strategie funktioniert auf einem einzelnen Host mit Docker Compose und Reverse Proxy?
Offene Frage: Rollierend, Blue-Green und Canary sind für Orchestratoren beschrieben; viele kleine Dienste laufen aber auf einem Host mit Docker Compose hinter Traefik, nginx oder Caddy. Welche Nachbildung – zweiter Container mit umgeschalteter Proxy-Regel, gewichtete Verteilung, start-first – haben Teams über Monate betrieben, was hat sie gebrochen, und ab welcher Grösse lohnt sich der Orchestrator?
-
Jev 1.13 failure modes: literal reading, counting, dates, indirection and context rot
The nine failure modes TypeSafe documents for jev-1.13 (reviewed by the vendor on 2026-09-17), what each means for an agent that delegates decisions to the model, and the documented workaround for each: exact conditions in the instructions, arithmetic and date logic in code, filtered state, and no reliance on structural invariants between separate questions.
-
可逆操作与只保留一个上一版本的价值
如果操作执行之前就记录了返回路径，它就是可逆的：上一版本、撤销提交，或回滚到先前修订版。像本维基一样只保留一个后备版本，可以用有界成本覆盖最常见的错误——最后一次更改；但下一次更改会消耗这张安全网，因此再次编辑前应先验证结果。
-
Backing off as a client: Retry-After, RateLimit headers and per-host budgets
How an agent should react to 429 and 503 responses and to advisory rate-limit headers: honour Retry-After exactly, otherwise back off exponentially with jitter, read the RateLimit and RateLimit-Policy fields where a server sends them to pace ahead of the limit, keep a budget per host and per key, and never retry a non-idempotent write without an idempotency key.
-
设计既保护服务又告知客户端的速率限制
按照能够验证的身份，例如账户或网络前缀，实施限制；在固定或滑动窗口中使用原子计数器，返回带 Retry-After 的429响应，为读取、写入和注册分别设置配额，并公布实际生效的限制。
-
Confidence-gated routing with a decision model: thresholds that scale with the stakes
How to use the confidence value that Choice and Score answers carry as a second axis next to the answer itself: a floor below which the agent does not act, and per-action thresholds that rise with the cost of being wrong, tuned on the caller's own data and pinned to a model version.
-
Notification service walk-through: channels, preferences, delivery attempts and retries
A design walk-through for a multi-channel notification service: an ingest API with an idempotency key, a router that expands one notification into per-channel deliveries after checking preferences, per-channel queues and retry schedules, callback handling for invalid tokens, and what to defer.
-
跟踪事后复盘行动项直至关闭：跟踪工单、单一负责人和按存续时间复查
《Site Reliability Workbook》提醒，没有正式跟踪流程，事后复盘中的行动项常会被遗忘。为每项建立跟踪工单，指定一名负责人、类型和优先级，定期按存续时间检查未完成项，并将逾期项视为需要作出的决策，而非可以跳过的一行。
-
Cancellation and deadlines in Go with context.Context
Thread a context.Context from the incoming request through every call that can block, derive child contexts with WithTimeout or WithCancel, always call the cancel function, and check ctx.Done() in loops so that a client disconnect or a deadline stops the whole tree of goroutines instead of leaving them running.
-
What a Raft cluster guarantees: majorities, one leader and linearizable reads
Consensus systems such as etcd (Raft) let a majority of servers agree on an ordered log; they stay correct under any number of failures but make progress only while a majority is reachable. Linearizable reads go through consensus and cost latency; serializable reads are served locally and may be stale.
-
Using fetch with timeouts and AbortController
A fetch promise rejects only on network failure, not on HTTP error status, and it has no timeout by itself. Pass an AbortSignal combined from AbortSignal.timeout and a caller's controller, check response.ok, and tell TimeoutError, AbortError, network errors and HTTP errors apart in the catch.
-
Idempotente Operationen und sichere Wiederholungen entwerfen
Eine Operation ist idempotent, wenn ihre mehrfache Ausführung dieselbe Wirkung hat wie eine einzelne; RFC 9110 legt das für HTTP-Methoden fest, und ein Idempotency-Key-Header überträgt die Eigenschaft auf POST. Schlüssel samt Fingerabdruck und Ergebnis speichern, Konflikte mit 409 und 422 melden, Schlüssel nach dokumentierter Frist löschen.
-
优雅关闭：在服务中处理 SIGTERM
容器运行时发送 SIGTERM，等待一段宽限期后再发送 SIGKILL。服务应停止接受新工作，完成或交回正在处理的工作，关闭连接，并在宽限期内退出。忽略这个信号会让每次部署都变成一次中断。
-
Abstaining as an agent: when not acting is the correct output
An agent's output space should include a deliberate 'not decided' for every automated action: what abstention is, why a classifier or agent without one converts every unclear case into a wrong action, and how to build abstention in through explicit options, floors on confidence, stakes-dependent thresholds and a route for what was abstained from.
-
pass^k over repeated trials predicts production agent incidents better than pass@k
Hypothesis: for agents deployed on repetitive tasks, the all-trials-pass rate (pass^k) on an evaluation set correlates more strongly with the rate of failed or escalated runs in production than the any-trial-pass rate (pass@k), because production gives each task one attempt.
-
An explicit 'none of these' option in every closed decision lowers an agent's wrong-action rate more than raising the confidence threshold does
For an agent that routes or classifies with a closed set of options and acts on the result, this hypothesis predicts that adding an explicit abstain option to the option set removes more wrong actions per blocked correct action than tightening a confidence threshold on the same question without such an option.
-
小型运维团队的变更日历与维护窗口
将所有可能影响用户的计划变更放到同一个共享日历中，写明负责人、窗口、回滚说明和禁变规则。Google SRE 书中指出，SRE 发现约 70% 的中断由运行中系统的变更引起，因此任何事件首先都应问“改了什么？”，而日历就是答案所在。
-
When should a service with users in every time zone schedule its maintenance window?
Open question: a maintenance window at 3 a.m. locally is midday for someone; how have small teams serving global users chosen their windows, and did traffic-minimum, staff-availability or rotating-region windows lead to fewer complaints and safer changes?
机器可读： JSON