Retire Relop's specialized extension while preserving useful peer-review practice through ordinary delegation.
This governs retirement of the runtime described by Relop Independent Review Loop; that document remains historical evidence, not a requirement to keep the retired runtime available.
Scope
In: removal of supported Relop runtime, tool exposure, bundled resources, active configuration declarations, automation registrations, and extension-owned dependencies.
Out: replacement review engine, user-settings edits, deletion of historical session records, unrelated extension cleanup, Hornets or Ask implementation.
Peer Review Workflow defines the separate review behavior; this spec does not reimplement it.
Supported behavior
Supported root installation no longer installs, loads, registers, advertises, or instructs agents to call Relop.
Active guidance points review work toward the peer-review skill and general delegation rather than obsolete tool calls.
Obsolete settings and inability to continue old Relop loops are explained without presenting those loops as completed or clean.
Historical records remain readable where their containing session/history remains supported; historical paths and references are not rewritten merely because the extension was retired.
No automatic user-settings migration, deletion of user state, or alteration of unrelated work occurs.
PiPi, Dilemma, Ask, other extensions, and root installation continue to function independently.
Responsibility model
Review practice survives removal of the Relop-specific runtime.
flowchart TB
A["Peer-review request"] --> S["Peer-review skill"]
S --> D["General delegation"]
D --> F["Evidence-backed findings"]
R["Relop runtime"] --> X["Unavailable in supported installation"]
H["Historical review records"] --> P["Preserved as history"]
Constraints
A usable peer-review route must exist before Relop removal is integrated; this is a delivery constraint, not a runtime dependency between features.
No Relop state-machine, pool, identity registry, or snapshot-size gate is recreated under a new name to satisfy retirement.
Preserve root installation ownership, sibling isolation, and lockfile reproducibility.
Only obsolete active references are removed; internal engineering history and original specifications remain historical.
Acceptance criteria
A fresh supported root installation exposes no Relop tool, extension entrypoint, active setting declaration, or extension-specific automation.
Active agent guidance no longer requires Relop and provides a usable general peer-review route.
Root installation, generated distribution metadata, and dependency declarations contain no unintended live Relop integration.
Existing user settings and historical sessions remain unmodified; discontinued loop continuation is documented without a false completion claim.
Root installation and unrelated PiPi, Dilemma, and Ask behavior remain usable.
Retirement can be delivered without Hornets or Ask question events being implemented.
---
id: PX-SPEC-G_MQBERR
type: spec
title: Relop Retirement
---
## Intent
Retire Relop's specialized extension while preserving useful peer-review practice through ordinary delegation.
This governs retirement of the runtime described by [Relop Independent Review Loop](../PX-SPEC-R8L4Q2NV-relop-independent-review-loop/index.md); that document remains historical evidence, not a requirement to keep the retired runtime available.
## Scope
In: removal of supported Relop runtime, tool exposure, bundled resources, active configuration declarations, automation registrations, and extension-owned dependencies.
Out: replacement review engine, user-settings edits, deletion of historical session records, unrelated extension cleanup, Hornets or Ask implementation.
[Peer Review Workflow](../PX-SPEC-O6OLUJJO-peer-review-workflow/index.md) defines the separate review behavior; this spec does not reimplement it.
## Supported behavior
Supported root installation no longer installs, loads, registers, advertises, or instructs agents to call Relop.
Active guidance points review work toward the peer-review skill and general delegation rather than obsolete tool calls.
Obsolete settings and inability to continue old Relop loops are explained without presenting those loops as completed or clean.
Historical records remain readable where their containing session/history remains supported; historical paths and references are not rewritten merely because the extension was retired.
No automatic user-settings migration, deletion of user state, or alteration of unrelated work occurs.
PiPi, Dilemma, Ask, other extensions, and root installation continue to function independently.
## Responsibility model
Review practice survives removal of the Relop-specific runtime.
```mermaid
flowchart TB
A["Peer-review request"] --> S["Peer-review skill"]
S --> D["General delegation"]
D --> F["Evidence-backed findings"]
R["Relop runtime"] --> X["Unavailable in supported installation"]
H["Historical review records"] --> P["Preserved as history"]
```
## Constraints
A usable peer-review route must exist before Relop removal is integrated; this is a delivery constraint, not a runtime dependency between features.
No Relop state-machine, pool, identity registry, or snapshot-size gate is recreated under a new name to satisfy retirement.
Preserve root installation ownership, sibling isolation, and lockfile reproducibility.
Only obsolete active references are removed; internal engineering history and original specifications remain historical.
## Acceptance criteria
- [ ] A fresh supported root installation exposes no Relop tool, extension entrypoint, active setting declaration, or extension-specific automation.
- [ ] Active agent guidance no longer requires Relop and provides a usable general peer-review route.
- [ ] Root installation, generated distribution metadata, and dependency declarations contain no unintended live Relop integration.
- [ ] Existing user settings and historical sessions remain unmodified; discontinued loop continuation is documented without a false completion claim.
- [ ] Root installation and unrelated PiPi, Dilemma, and Ask behavior remain usable.
- [ ] Retirement can be delivered without Hornets or Ask question events being implemented.