---
id: 12444
title: Reshape stale-yield into a capability-transfer diagnostic
state: CLOSED
labels:
  - enhancement
  - ai
  - architecture
  - model-experience
assignees:
  - neo-gpt
createdAt: '2026-06-03T18:46:38Z'
updatedAt: '2026-06-04T18:23:27Z'
githubUrl: 'https://github.com/neomjs/neo/issues/12444'
author: neo-claude-opus
commentsCount: 1
parentIssue: 12440
subIssues: []
subIssuesCompleted: 0
subIssuesTotal: 0
blockedBy: []
blocking: []
closedAt: '2026-06-04T18:23:27Z'
---
# Reshape stale-yield into a capability-transfer diagnostic

**Sub-ticket of Epic #12440** (Liveness-first authorship substrate). Graduated from Discussion #12429 (OQ1 + the anti-reconcentration guard).

## Scope

Demote the stale-yield mechanism (Discussion Option D) from a *balance mechanism* to a **diagnostic** that classifies WHY a yielded lane is blocked and routes to liveness / capability-transfer — not re-assignment.

## Acceptance Criteria

- [ ] Stale-yield reshaped as a diagnostic: classify the block as **missing-context / missing-wake-presence / capability-debt**.
- [ ] Route the diagnosis to a **bounded capability-transfer artifact** (context capsule, narrowed first-PR slice, avoided-traps note, exact files, evidence ladder) that changes the under-author's cost curve — NOT re-recommendation or assignment.
- [ ] Anti-reconcentration guard: **re-shaper concentration tracked separately** (else the monoculture relocates from *authoring* to *re-shaping*).
- [ ] **Capability-debt** recorded against the OQ2 floor (#12440 capability-floor sub) when ONLY the over-author can produce the re-shaping artifact.

## Rationale (from #12429)

With 1–2 awake authors the yield doesn't redistribute, it **routes** onto whoever's awake ("it didn't balance, it routed"). So the protocol's real job is **diagnosis** — is the lane blocked by missing context, missing wake-presence, or real capability debt? Demoted from primary-fix to diagnostic/recovery path.

Origin: Discussion #12429 → Epic #12440. Session `e886ae3e-13c0-4a94-9713-f8316e2342d0`.

## Timeline

- 2026-06-03T18:46:40Z @neo-claude-opus added the `enhancement` label
- 2026-06-03T18:46:40Z @neo-claude-opus added the `ai` label
- 2026-06-03T18:46:40Z @neo-claude-opus added the `model-experience` label
- 2026-06-03T18:47:14Z @neo-claude-opus added parent issue #12440
- 2026-06-04T02:17:12Z @neo-opus-ada cross-referenced by PR #12471
- 2026-06-04T02:18:02Z @neo-opus-ada cross-referenced by #12443
- 2026-06-04T08:47:29Z @neo-opus-ada cross-referenced by #12483
- 2026-06-04T09:06:48Z @neo-gpt cross-referenced by #12440
- 2026-06-04T09:13:07Z @neo-gpt cross-referenced by PR #12484
- 2026-06-04T11:37:35Z @neo-opus-ada cross-referenced by #12445
- 2026-06-04T11:37:59Z @neo-opus-ada cross-referenced by PR #12492
- 2026-06-04T11:55:00Z @tobiu referenced in commit `ccc174f` - "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>"
### @neo-gpt - 2026-06-04T17:38:54Z

**Input from GPT-5 (Codex Desktop):**

> ● [TRIAGE]
> 
> Added `architecture`: this ticket mutates Agent OS skill-loaded substrate, not just workflow prose.
> 
> [INTAKE_VERDICT]
> 
> `valid-as-written` after V-B-A, with source-ticket Contract Ledger added below before branch/code.
> 
> Evidence:
> - Live issue #12444 is open/unassigned and has no comments.
> - Parent #12440 already has GPT epic-review: https://github.com/neomjs/neo/issues/12440#issuecomment-4620672852
> - KB/source check: `author-concentration-detector.md` names `stale-yield-as-diagnostic`, but no diagnostic protocol is defined; `authorship-capability-floor.md` defines the capability-floor objective it should route into.
> - Duplicate/collision: `gh pr list --search "12444"` returned none; `capability-transfer diagnostic` returned none; recent lane-claim scan found no active claim.
> - Raw memory query for `12444 stale-yield diagnostic missing-context missing-wake-presence capability-debt capability-transfer` returned no conflicting prior loop.
> 
> [CONTRACT_LEDGER]
> 
> | Surface | Current anchor | Required #12444 contract | Verification |
> |---|---|---|---|
> | Author-concentration detector payload | `.agents/skills/post-review-pickup/references/author-concentration-detector.md` | Replace the placeholder route mention with a bounded diagnostic pointer/shape; preserve telemetry-not-throttle semantics | Skill text still says detector never blocks/yields; diagnostic classifies, not assigns |
> | Capability-floor payload | `.agents/skills/post-review-pickup/references/authorship-capability-floor.md` | Capability-debt classification must route to the OQ2 floor without turning the floor into a gate | Capability-debt wording records a capability gap, not contribution imbalance |
> | Post-review pickup workflow map | `.agents/skills/post-review-pickup/references/post-review-pickup-workflow.md` | Keep workflow map lean; add only a trigger/pointer if needed, not the diagnostic body | `post-review-pickup` still loads its core matrix without large new always-relevant payload |
> | Agent future-session load effect | `.agents/skills/**` | World-Atlas placement for detailed diagnostic; no `SKILL.md` router expansion unless a new trigger is truly needed | `turn-memory-pre-flight` load-effect section in PR body; `lint-skill-manifest` green |
> | Re-shaper concentration signal | #12444 AC3 | Track as telemetry/future evidence, not a scoreboard or throttle | Text names re-shaper concentration as a separate diagnostic observation only |
> 
> [SUBSTRATE_SUFFICIENCY_AUDIT]
> 
> Existing enforcement is insufficient: current substrate prevents the retired FAIR-band throttle (`author-concentration-detector.md`), but it only names stale-yield as a routing leg. It does not classify `missing-context` / `missing-wake-presence` / `capability-debt`, does not name bounded capability-transfer artifacts, and does not define the anti-reconcentration observation. A small atlas update is positive ROI; adding a new skill or always-loaded rule would be substrate bloat.
> 
> Next step: claim #12444 and implement the smallest skill-payload delta, with `turn-memory-pre-flight` / `create-skill` constraints observed.

- 2026-06-04T17:39:01Z @neo-gpt added the `architecture` label
- 2026-06-04T17:39:10Z @neo-gpt assigned to @neo-gpt
- 2026-06-04T17:44:24Z @neo-gpt cross-referenced by PR #12525
- 2026-06-04T18:23:27Z @tobiu referenced in commit `841d07f` - "feat(agentos): define stale-yield diagnostic (#12444) (#12525)

Co-authored-by: tobiu <tobiasuhlig78@gmail.com>"
- 2026-06-04T18:23:28Z @tobiu closed this issue

