| content |
{"Commits":[{"Sha1":"c08e4cf7f {"Commits":[{"Sha1":"c08e4cf7fead5f50e16b1bac74dcca0fb743f68a","Message":"feat: group SLOs that burn together into one Incident candidate (K8.7)\n\nBefore: one real outage burned three SLOs and produced three candidates for one\nHuman to triage. Now the SLOs breached in an episode are one candidate that\nnames them all; the first breached SLO in model order is the group's source\nregistration so existing registrations keep working. A member that joins after\nthe report raises one more candidate for the grown set, a member that recovers\nreports nothing, and SLO_BREACH_GROUP_SETTLE_SECONDS (default 0) lets late\nmembers join the first candidate. The report key carries only the tenant, the\nwindow and the SET of SLOs, nothing per process, so replicas and restarts still\nfold in the Trigger's dedup window. The rule is a default chosen without an\nOwner and is recorded as such (A11). Verified by scripted tests and by two\nconsistent real-fault drills (SIGKILL of a throwaway PG16 under signed traffic):\none candidate naming three SLOs, previously three candidates (kept as the\nbefore-grouping report). Not released or deployed: the live 4310 monitor keeps\nits per-SLO behaviour until a release.\n\nCo-Authored-By: Claude Sonnet 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-10-02T21:30:14-07:00"}],"HeadCommit":{"Sha1":"c08e4cf7fead5f50e16b1bac74dcca0fb743f68a","Message":"feat: group SLOs that burn together into one Incident candidate (K8.7)\n\nBefore: one real outage burned three SLOs and produced three candidates for one\nHuman to triage. Now the SLOs breached in an episode are one candidate that\nnames them all; the first breached SLO in model order is the group's source\nregistration so existing registrations keep working. A member that joins after\nthe report raises one more candidate for the grown set, a member that recovers\nreports nothing, and SLO_BREACH_GROUP_SETTLE_SECONDS (default 0) lets late\nmembers join the first candidate. The report key carries only the tenant, the\nwindow and the SET of SLOs, nothing per process, so replicas and restarts still\nfold in the Trigger's dedup window. The rule is a default chosen without an\nOwner and is recorded as such (A11). Verified by scripted tests and by two\nconsistent real-fault drills (SIGKILL of a throwaway PG16 under signed traffic):\none candidate naming three SLOs, previously three candidates (kept as the\nbefore-grouping report). Not released or deployed: the live 4310 monitor keeps\nits per-SLO behaviour until a release.\n\nCo-Authored-By: Claude Sonnet 5.5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-10-02T21:30:14-07:00"},"CompareURL":"luoanwu/seven-domain-five-dimension-unified-model/compare/cbbb98c21594913f4e5565f7942f8b47c65fa245...c08e4cf7fead5f50e16b1bac74dcca0fb743f68a","Len":1}... |