Finding
The canonical stellar-protocol repository contains six Stellar Limits
Proposals under limits/, but its root README describes the repository as home
to CAPs and SEPs and exposes badges only for those two families. The
limits/README.md process document does not index the individual SLPs, titles,
or statuses. Downstream discovery consequently has no canonical SLP family index
to link or crawl.
Evidence
On 2026-07-14 the canonical tree contained slp-0001.md through
slp-0006.md, while the root overview still named only CAPs and SEPs and the
limits overview had no proposal list. Read-only Docs Algolia queries for
SLP-0004 and SLP-0006 returned the SEP overview rather than an SLP family
page, demonstrating the practical ambiguity without treating search absence
alone as the source defect.
Additional recorded evidence:
- the P4 N2 YieldBlox reconciliation relies on SLP-0006 for the affected-account/quarantine context, showing practical retrieval impact
- live recheck 2026-07-14: stellar-protocol root README describes only CAPs and SEPs and has badges only for those families; limits/ contains SLP-0001 through SLP-0006 but limits/README.md has no proposal index
- live Algolia recheck 2026-07-14: SLP-0004 and SLP-0006 queries route to the SEP overview rather than a canonical SLP family page
Recommendation
Recognize SLPs alongside CAPs and SEPs in the root repository overview, link the
limits/ family directly, and add a maintained index of SLP identifiers, titles,
and statuses to limits/README.md. That canonical index can then be linked from
Docs and surfaced by search without inventing SEP/CAP labels for SLP material.
Source Record
This was found by the downstream Raven eval/improvements loop and recorded as sd-037 (stellar-docs, discovered 2026-07-11).
Public source record: improvements/stellar-docs/sd-037-limits-slps-discoverability.md
Immutable source snapshot: a4608d080232
Resolution Handoff
When a fix is deployed, please link the resolving issue or PR to the source record above and notify Raven through:
https://github.com/kalepail/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sd-037%3A%20
Include the finding id, resolving issue/PR, deployed version or timestamp, and the smallest live recheck. Raven independently verifies the upstream surface before changing the finding to fixed-upstream; issue closure or a merged PR alone is not treated as proof. After a distinct reviewer repeats the live check, the active finding is retired to Raven's resolved ledger; a commit-pinned snapshot is preserved when available.
Finding
The canonical
stellar-protocolrepository contains six Stellar LimitsProposals under
limits/, but its root README describes the repository as hometo CAPs and SEPs and exposes badges only for those two families. The
limits/README.mdprocess document does not index the individual SLPs, titles,or statuses. Downstream discovery consequently has no canonical SLP family index
to link or crawl.
Evidence
On 2026-07-14 the canonical tree contained
slp-0001.mdthroughslp-0006.md, while the root overview still named only CAPs and SEPs and thelimits overview had no proposal list. Read-only Docs Algolia queries for
SLP-0004andSLP-0006returned the SEP overview rather than an SLP familypage, demonstrating the practical ambiguity without treating search absence
alone as the source defect.
Additional recorded evidence:
Recommendation
Recognize SLPs alongside CAPs and SEPs in the root repository overview, link the
limits/family directly, and add a maintained index of SLP identifiers, titles,and statuses to
limits/README.md. That canonical index can then be linked fromDocs and surfaced by search without inventing SEP/CAP labels for SLP material.
Source Record
This was found by the downstream Raven eval/improvements loop and recorded as sd-037 (stellar-docs, discovered 2026-07-11).
Public source record: improvements/stellar-docs/sd-037-limits-slps-discoverability.md
Immutable source snapshot: a4608d080232
Resolution Handoff
When a fix is deployed, please link the resolving issue or PR to the source record above and notify Raven through:
https://github.com/kalepail/stellar-raven/issues/new?template=upstream-improvement-ready.yml&title=%5Bupstream-ready%5D%20sd-037%3A%20
Include the finding id, resolving issue/PR, deployed version or timestamp, and the smallest live recheck. Raven independently verifies the upstream surface before changing the finding to
fixed-upstream; issue closure or a merged PR alone is not treated as proof. After a distinct reviewer repeats the live check, the active finding is retired to Raven's resolved ledger; a commit-pinned snapshot is preserved when available.