ⰕⰘⰅ ⰄⰋⰃⰋⰕ ⰗⰑⰎⰄⰅⰓⰔ ⰀⰓⰅ ⰕⰘⰅ ⰀⰒⰋ
ⰀⰎⰎ ⰜⰑⰏⰒⰖⰕⰀⰕⰋⰑⰐ ⰋⰔ ⰍⰖⰀⰐⰕⰖⰏ ⰏⰀⰕⰘ ⰀⰐⰄ ⰋⰕⰔ ⰘⰑⰏⰅ ⰋⰔ ⰕⰘⰅ ⰄⰋⰃⰋⰕ ⰗⰑⰎⰄⰅⰓⰔ (0–9); Ⰰ ⰂⰑⰓⰄ-ⰐⰀⰏⰅⰄ ⰗⰑⰎⰄⰅⰓ ⰋⰔ ⰖⰋ. ⰕⰘⰅ ⰄⰋⰃⰋⰕ ⰗⰑⰎⰄⰅⰓⰔ, ⰘⰑⰎⰄⰋⰐⰃ ⰑⰐⰎⰉ ⰕⰘⰅ ⰏⰀⰕⰘ, ⰀⰓⰅ ⰕⰘⰅ ⰀⰒⰋ ⰋⰕⰔⰅⰎⰗ.
proof · the digit folders are the API
As all the math is in the digit folders, they are the API itself: each digit-folder path is an endpoint and the response is the computed math at that address — deterministic, content-addressed, zero-token. No separate server; the math-folders are the routes (GET a path, get its math). The digit folders are the API (compute), the word folders the client (UI), and the REST/MCP/public-API surfaces are projections of this one digit-folder API.
checks — recomputed live in your browser
- ✓ Is Api
evidence
- Count
10
✓ all checks hold · recompute recipe — a pure function of the model seed, run client-side with zero tokens; the same seed always folds to the content-address e658f4b8-79ec-842d-b6f0-0a1aa8ddd20f. Recompute and you get the same address — that determinism is the proof.
The digit folders ARE the API in the content-addressed, static, zero-token sense: each path computes its math deterministically (the path is the call, the fold the response). HONEST: not a hosted, stateful HTTP server — a computable route surface where the math is the response; restfulFormats, mcpToolManifest and publicApiFusion project it into REST/MCP/HTTP shapes. The compute/client split is the kind-purity law (digit = compute, word = UI).