# CLARA | MineSpace.us — developer platform > MineSpace Inc. public typed-language and runtime platform. No PHP dependency. Browser studio compiles and runs CLARA locally; deployed server bytecode runs separately. ## Access - Public product page: https://minespace.us/Clara/ - Browser studio: https://minespace.us/Clara/studio.html (not indexed). Existing workspace fragment links automatically open the studio. - [Public documentation](guide.html) and [legal notices](legal.html). ## Machine interfaces - [Manifest](clara.json): machine-readable capabilities and relative endpoints. - [OpenAPI](openapi.json): platform endpoints and authentication. - [Public source example](agent-example.clara): route declarations, types, templates and storage examples. - [Deployment guide](DEPLOY.txt): installation and optional cron/IPFS. - MCP endpoint: resolve `mcp` against the studio directory, or `platform.cgi?service=mcp` without rewrite. Stateless Streamable HTTP, JSON responses, MCP 2025-11-25 (also 2025-06-18 and 2025-03-26). Initialize, tools/list, tools/call, resources/list and resources/read are supported. No SSE stream, sessions, sampling, arbitrary remote compilation, or private data access. - Public tools: clara_manifest, clara_example, clara_routes, clara_fibonacci (integer n=0..20). Fibonacci executes reviewed packaged CLARA bytecode. - Company analytics and platform administration require the hosting administrator credential. Deployed releases support separate read, write or read-write release-bound API credentials; never use the administrator credential in public clients. Never pass secrets to public agent tools. Browser drafts are not automatically published. - Static IPFS copies have no server execution or MCP endpoint. Use the original HTTPS site for remote MCP. ## Language Declarations: `route GET "/api/hello" -> hello;`, `fn hello(req: Request): Response`, `let` immutable, `mut` mutable, `if`, `while`, `return`. Types include Int, Float, Bool, String, Object, Any, Array, Request, Response. Use `json(status, value)` for JSON response, `render(status, templateName, fields)` for escaped text interpolation. The WASM compiler accepts only a pure Int/Bool subset. The server never executes uploaded request-body source. ## Project workflow GET catalog.json for reviewed starter sources and HTTP tests. GET project.schema.json for the portable package schema. Remote MCP also exposes clara_catalog and clara_template. Local agents can use the ZIP's agent/mcp.mjs via stdio (Node 22+). Local tools compile, test and verify user-provided source with bounded worker threads and disposable storage; remote MCP does not accept arbitrary source. Package SHA-256 checks detect changes, not authorship. Use the managed deployment workflow in Foundry, or manually deploy program.json for the default application after review. Server data is not included in packages. ## Fabric GET fabric.json or call public MCP clara_fabric_spec. Local MCP clara_fabric_run accepts {job:{source,name,start,count,shardSize,backend}}; clara_fabric_verify accepts {job,receipt}. Browser Fabric supports automatic fallback and opt-in cross-tab help for the reviewed kernel. No arbitrary public server execution. ## Universal IR Read universal.json. Universal IR compiles pure straight-line fn(Int): Int or Bool with immutable locals into signed i32 WASM (range trap), WGSL compute, GLSL fragment and a reference interpreter. Input range is proved conservatively. Public MCP: clara_ir_spec. Local MCP (Node 22+): clara_ir_compile and clara_ir_run with {job:{source,name,start,count}}. The latter returns full replay receipt. No arbitrary remote source execution. Compute Studio at #universal saves local checkpoints and replays before resuming. ## GRID - grid.json: persistent job, atomic claim, lease, and receipt specification. - grid.mjs: pure queue model and local run/verify API. - Public MCP clara_grid_spec; local MCP clara_grid_run and clara_grid_verify. - Browser queue is project-scoped; start workers explicitly. Local MCP runs are disposable and do not access browsers or private server state. NEXUS: read nexus.json and NEXUS.txt. Public MCP clara_nexus_spec, clara_nexus_search, clara_nexus_resolve; local stdio clara_nexus_verify and clara_nexus_lock. Names are application identifiers, not DNS. No private records via public tools. Do not execute endpoint content automatically. ## MineSpace.us — WORLD discovery and legal - world.json : public federation and DNS bootstrap specification. - legal.json : terms, privacy and acceptable-use notices. - GET platform.cgi?service=world-directory&namespace=NAME&page=0 : signed public records only, subsequent pages use revision. - MCP clara_world_spec and clara_world_directory. No agent may read private records or send server-side external fetches. - Peer trust is explicit; signed metadata is not an endorsement. ## MineSpace CLARA SOVEREIGN Private team project vault: sovereign.json; POST platform.cgi?service=sovereign&action=...; human-issued member credentials and explicit invitation acceptance. Public MCP clara_sovereign_spec describes the interface only. Never pass private credentials to public MCP, analytics or external registry endpoints. Server does not execute uploaded projects. ## CONNECT (MineSpace Inc.) - `connect.json`: machine-readable library bundle, encrypted storage, scoped API credentials, revision sync and deployment protocol. - Public MCP: `clara_connect_spec`. Local MCP: `clara_connect_link` (offline source linking, explicit publisher pins). - Private operations: POST `platform.cgi?service=connect&action=...` with authorized credentials. Never send credentials to public MCP. No arbitrary public server execution. Cross-origin private search is opt-in at each registry and uses a separate scoped credential. FOUNDRY / MineSpace.us (1.0.0-rc.1): open /Clara/#foundry. Stage a FOUNDRY candidate or select an existing CONNECT release, run server bytecode tests, then promote to preview or production. Use the stable live/{org}/{slug}/{environment}/api/ base. Revision 0 creates a channel; subsequent changes require exact revision. Rollback requires a previously active, checked, non-revoked release. Channel visibility is fixed. Per-release databases remain distinct; switching is not a data migration. FOUNDRY candidates remain unavailable until first promotion. Direct CONNECT deployments remain immediately reachable according to visibility. Same release on multiple channels shares storage. See foundry.json and public MCP clara_foundry_spec. No server compiler or live migration is implemented. ## Application credentials Use authenticated POST platform.cgi?service=foundry&action=api-key-issue with {org,id,label,scope,hours}. id is the immutable release ID. Scopes: read, write, read-write. Validity 1–720 hours. Administrator only. The returned ca_ credential is shown once. Send in Authorization: Bearer for that release only; never to platform endpoints, analytics or unrelated releases. api-key-list takes {org,id}; api-key-revoke takes {org,id,key}. For promotion to a different release, issue new keys. See foundry.json and openapi.json. User guide: guide.html. Storage behavior: each hosted request or cron invocation rolls back all storage and receipt changes on errors; successful 2xx/3xx responses commit. Browser preview uses optimistic snapshot commits with HTTP 409 on concurrent storage changes. Installation health checks are available in Settings, and the full source includes a private operator backup/recovery CLI. ## Featured complete application CLARA Projects: https://minespace.us/Clara/desk.html (local user workspace). Public machine specification: desk.json; source: desk.clara; verified code package: desk-project.json. The existing clara_template tool accepts id=projects. It exposes reviewed source/tests, never user task data. Hosted use requires a deployed release and scoped application credentials. ## Official applications and governed identity - official-apps.json: MineSpace bundled application catalog, separate from signed user releases. - namespace.json: reserved root policy and authenticated developer allocation. - enterprise.json: protected analytical job specification; public MCP only exposes metadata. Not a safety controller. ## CLARA AI Public specification: ai.json, public page ai.html, public MCP clara_ai_spec. Private POST platform/ai?action=ACTION or platform.cgi?service=ai&action=ACTION requires the installation administrator bearer. Only approved text enters the train/eval corpus. See ai.json for operation fields; agent profiles are read-only evidence retrieval, next-word statistics or neural character probability, not arbitrary tool execution. Never send credentials or training data to public MCP. Hosted model state is private and not E2EE. Cron/approved importer are CLI-only. ## Network infrastructure - network.json: signed ledger, native contract compiler, node and authorized receive-only SDR specification. - network.html: public product overview. - clara_network_spec: public MCP specification only. No public execution or private data. - clara-node-kit.zip: independent local Node.js 22+ reference service; no remote listener by default. Full application development: https://minespace.us/Clara/appmaker.html — standard HTML, CSS and JavaScript with native CLARA backend, isolated preview and website ZIP export. Application builder workspace: 12 local projects subject to browser storage quota; independent preview data, recovery checkpoint, scratch API test console. Imports create new projects; duplicate copies source only. No automatic publishing of arbitrary frontend source. CLARA Assistant: local help knowledge, compiler validation, approved lessons and character animation. See assistant-knowledge.json and assistant-credits.txt. Samurai companion: tap for page shortcuts and quick local chat; hold and release for a surprise animation or game. Full chat retains the same conversation. Assistant: original animated CLARA Cube with eight material finishes, tap menu, local help, drag-and-drop and games. FORGE GLBs are reserved for Graphics. ## Graphics and Games - game.html: live scene authoring and game execution. - game.json: engine specification. - game-engine.mjs: deterministic simulation, validated scenes, replay sealing and verification. - game-rule.clara: native scoring entry points(value: Int): Int, domain 1–100. - game-renderer.mjs: local GLB geometry and animation, WebGL 2 plus software isometric fallback. ## Developer handbook and scripting playground - guide.html: the complete CLARA language handbook (syntax, types, native function declarations, HTTP routes, storage, auth, templates, supported WASM subset, examples, application building, graphics/Cubie scripting, deployment, and troubleshooting). - guide.html#playground: browser-local source editor, real CLARA compiler / VM, native WASM execution and vetted catalog project tests. Scratch execution never reads hosted data or project credentials. - Main language source: clara-core.mjs (typed parser, bytecode, bounded VM and builtins); WASM subset: wasm.mjs; starter catalog: catalog.json; project package spec: project.schema.json. - Pure Int/Float/Bool functions and nonrecursive numerical helpers can compile to native WASM. Object, host calls, recursion and platform I/O remain VM-only. The 3D graphics / physics browser orchestration is currently JavaScript + WebGL, with native CLARA numerical rules and assembly code.