Add Rhein Finance Featured App reinstatement request

[FarrukhRZ]

Featured App Reinstatement Request

Summary

• Featured App name: Rhein Finance
• Organization: Rhein Finance (Mosaic Lab)
• Current stage:
  • Freshly paused, seeking reinstatement
  • Mid-appeal, disputing the basis of the pause
  • Already reinstated, lock outstanding

Briefly summarize what this PR is requesting: This Pull Request submits Rhein Finance's Featured App reinstatement request following its pause related to excess FeaturedAppActivityMarker claims relative to the Featured App Marker Guidance's 115% tolerance. The request includes the basis of the pause, the technical causes identified, corrective measures undertaken, evidence of continued compliance, and on-chain verification data, formalizing a reinstatement already recommended by the Accountability Committee.

Reinstatement Request File

This PR adds a completed reinstatement request at:

reinstatement/rhein-finance-2026-07-03.md

The request should be prepared using:

templates/featured-app-reinstatement-request.md

Submission Checklist

Before submitting, confirm:

• The completed reinstatement request file is included in the reinstatement/ directory
• The file follows the Featured App Reinstatement Request template
• All PartyIds are listed exactly as they appear on-chain
• Any fields that do not apply are marked N/A with a brief reason
• Supporting figures, sources, and transaction hashes are included where applicable
• CIP-0116 locking status is included
• Any exception request is clearly identified in the reinstatement file, if applicable

Reviewer Notes

• This request formalizes a reinstatement already recommended by the Committee (Ryan Trinkle, Featured App Coordination) following our formal appeal submitted 23 April 2026.
• The reinstatement request includes a supplementary internal review against CIP-47, identifying and correcting two additional non-qualifying marker-generating operations alongside the primary calibration and edge-case fixes.
• CIP-0116 lock verification is included via on-chain update reference in the reinstatement request.