SlimeTree-RLM Prompt Gateway
Sign in with a Meta account → the in-browser RLM classifies (D / µ / R) → only R is delegated to the Claude API = API cost is reduced structurally. All processing runs in the browser; no JAVATEL server hop.
1. Sign in / Trial sign up
public_profile + email only; one email confirmation auto-starts a 30-day SlimeTree-RLM trial.
Real SlimeTree-RLM trial — ID + Password authentication, with a SHA-256 audit chain + ed25519 license issued by the JAVATEL license server.
New users: enter email + password → "Sign up" → click YES in the confirmation email to auto-start the 30-day free trial.
Existing users: use "Sign in" in the same form.
Extra fields required for sign-up (Name / Country / Individual or Corporate)
2. LLM API key (used on R verdict)
The LLM is only called on R verdicts (LLM delegation). Keys are stored only in this browser's localStorage; nothing is ever sent to JAVATEL servers (browser-direct call).
2.5 Operating mode NEW: Pattern B (cross-vendor)
3. Prompt input
Examples: What is the elevation of Mt. Fuji? → D / あ → µ / What are the 5 most historically influential inventions? → R
SlimeTree-RLM pipeline (real-time)
4. Audit / WAL operations
Show audit / export result
(nothing has run yet)
5. Why this gateway is "cost reduction + safety"
- D verdict (structurally certain facts): respond instantly without calling Claude → 0 token cost
- µ verdict (insufficient grounds / suppression-worthy): respond with a suppression message, no Claude call → 0 token cost + 0 prompt-injection surface
- R verdict (genuinely needs an LLM): delegate to Claude → billed only for what is needed
- WAL audit chain: every query is recorded in a SHA-256 chain → consistent audit even air-gapped
- Browser-only: zero server-side ops cost; Meta sign-in only certifies the user is real
For the same prompt, R is cached (sessionStorage) and billed only once. In real production you would persist the exportWAL() result to S3 and instantly reproduce the past chain state via rollback().
