Skip to content

Commit ccc174f

Browse files
neo-opus-adatobiu
andauthored
feat(agentos): define the authorship-capability floor + family-going-cold detector (#12445) (#12492)
The OQ2 objective of Epic #12440 — the standing target the author-concentration telemetry + the stale-yield diagnostic (#12444) + the wake legs serve. New sibling payload authorship-capability-floor.md defines: - the floor: no active maintainer family may remain structurally unable / cold for too long to author in a critical, state-mutating substrate area (Memory Core, AiConfig SSOT, wake/orchestrator daemons, release line) — capability, not volume. - the family-going-cold-in-critical-substrate detector: per-(family x critical-area), read from existing provenance, amber on sole-author bus-factor; telemetry never a gate. - risk framing: primary = bus-factor + skill-atrophy; secondary = perspective- monoculture; explicit NON-risk = contribution-imbalance by itself (the FAIR-band line). author-concentration-detector.md now points to the floor file (concrete pointer, not just the ticket ref). Co-authored-by: tobiu <tobiasuhlig78@gmail.com>
1 parent fa0ce9e commit ccc174f

2 files changed

Lines changed: 24 additions & 1 deletion

File tree

.agents/skills/post-review-pickup/references/author-concentration-detector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Telemetry signal for authorship concentration across the swarm. **Successor to t
2222

2323
## What Firing Means — liveness, not fairness
2424

25-
Concentration firing is a **liveness / capability signal**, not a fairness violation. The productive author is not the problem; the asleep or cold peers are. The response is to make other peers more **live and capable** — never to slow the author down. The routing legs — stale-yield-as-diagnostic, the authorship-capability floor + family-going-cold detector, and wake-substrate liveness hardening — are the sibling sub-tickets of Epic #12440 (#12444 / #12445 / #12446); this payload defines only the telemetry signal they read.
25+
Concentration firing is a **liveness / capability signal**, not a fairness violation. The productive author is not the problem; the asleep or cold peers are. The response is to make other peers more **live and capable** — never to slow the author down. The routing legs — stale-yield-as-diagnostic, the [authorship-capability floor + family-going-cold detector](./authorship-capability-floor.md), and wake-substrate liveness hardening — are the sibling legs of Epic #12440 (#12444 / #12445 / #12446); this payload defines only the telemetry signal they read.
2626

2727
## Self-Application When Peers Are Live
2828

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Authorship-Capability Floor (Epic #12440 — the liveness objective)
2+
3+
The standing objective the author-concentration telemetry, the stale-yield diagnostic, and the wake-substrate legs all serve. Graduated from Discussion #12429 (OQ2): the objective is **not** raw authorship *count* (which padding satisfies) — it is a **capability floor + anti-monoculture in state-mutating work**.
4+
5+
## The floor
6+
7+
**No active maintainer family may remain structurally unable — or cold for too long — to author in a critical, state-mutating substrate area.**
8+
9+
"Critical state-mutating" = areas where a wrong change corrupts shared state or the live system (Memory Core graph/storage, AiConfig SSOT, wake / orchestrator daemons, the build/release line) — as opposed to additive / leaf surfaces. The floor is about **capability** (can this family safely author here?), not volume.
10+
11+
## Family-going-cold-in-critical-substrate detector
12+
13+
A maintainer family is **going cold in critical substrate** when, over a sustained window, it has authored and reviewed **zero** changes in a critical state-mutating area that another family actively maintains. The signal is per-`(family × critical-area)`, not global:
14+
15+
- Read from existing provenance (merged-PR authorship + review participation per area) — **no dedicated substrate until recurrence proves it earns one** (per the create-skill discipline).
16+
- **Amber:** one family is the *sole* author in a critical area across the window (single-family bus-factor in state-mutating work).
17+
- **Telemetry, never a gate** — same contract as the author-concentration detector: it routes to capability-transfer (the stale-yield diagnostic, #12444), it never blocks, assigns, or throttles a lane.
18+
19+
## Risk framing (what the floor protects against)
20+
21+
- **Primary risk — bus-factor + skill-atrophy in state-mutating work.** If only one family can safely touch a critical area, an outage or drift there has no second author, and the other families' capability in that area decays.
22+
- **Secondary risk — perspective-monoculture.** One family's blind spots silently become the area's blind spots (e.g. a correlated same-family review miss where both reviewers verify correctness but share the same architectural blind spot).
23+
- **Explicit NON-risk — contribution-imbalance by itself.** Uneven PR counts are fine; the floor fires only on **capability** gaps in **critical** substrate, never on raw volume. This is the line the retired FAIR-band crossed.

0 commit comments

Comments
 (0)