# RAPP Base

> RAPP Base is a public, GitHub-native static collection publisher inspired by
> PocketBase and Firebase. It is not wire-compatible with either project and is
> not a private, low-latency, or realtime database.

Read these resources in order:

1. https://kody-w.github.io/rapp-base/registry.json — protocol and URLs.
2. https://kody-w.github.io/rapp-base/SPEC.md — protocol rules.
3. https://kody-w.github.io/rapp-base/api/v1/status.json — build/event head.
4. https://kody-w.github.io/rapp-base/api/v1/collections.json — collections.
5. https://kody-w.github.io/rapp-base/versions/index.json — immutable versions.
6. https://kody-w.github.io/rapp-base/schemas/command.schema.json — commands.
7. https://kody-w.github.io/rapp-base/SECURITY.md — public-data threat model.

Read transport: CORS-open JSON from `raw.githubusercontent.com` or the optional
Pages explorer. Write transport: one strict command in a public GitHub Issue.
Never submit secrets or personal/private data. Deletion publishes a tombstone;
Git and Issue history remain public.
The Issue Form requires a publication attestation; submitting raw JSON or the
exact legacy v1.0 SDK wrapper programmatically constitutes the same assertion.
The legacy wrapper is not an Issue Form path. This is an assertion, not proof
or moderation.

Status `healthy` means repository-integrity checks passed; GitHub, Actions, and
Pages availability are not measured. Collection capacity distinguishes active
slots from tombstones/lifetime history, while event/request limits are
lifetime bounds. Invalid admissions retain hashes and stable errors, not raw
rejected command text. Admission ordering is first durable observation.

The `.well-known/mcp.json` document advertises static resources only. There is
no live MCP, plugin, websocket, or server-side realtime endpoint.