Developer portal

Make every release easier to diagnose

Publish verifiable metadata, describe the expected install layout, and give users precise recovery guidance without shipping executable rules.

Diagnostics-ready checklist

Package symbols, version metadata, support links, and deterministic file hashes users can verify.

Read the checklist

Install-layout language

Declare required, optional, misplaced, and obsolete files using a bounded data format that never executes code.

View the specification

Public read-only APIs

Responses are bounded, versioned, and backed by fixture-validated JSON Schemas. These endpoints require no secret and must not be used for private or administrative data.

  • GEThttps://share.rphlogs.dev/functions/v1/health

    Versioned platform and service health, including public incident history.

  • GEThttps://share.rphlogs.dev/functions/v1/directory?q=plugin

    Search the verified plugin directory with bounded, sanitized results.

  • GEThttps://share.rphlogs.dev/functions/v1/release?channel=stable

    Read signed desktop release-channel metadata.

Trust boundary

Diagnostic capsules contain signed data only. They cannot load assemblies, execute scripts, make network requests, or replace the analyzer's built-in safety rules. Release registration is performed through the desktop wizard with Discord ownership verification; there is no public write API or reusable developer secret.

Browse verified releases