clearkrypt 0.12.0

package/.well-known/clearkrypt.json

@@ -0,0 +1,7 @@
+{
+  "language": "ClearKrypt",
+  "version": "0.1.0",
+  "compiler": "deterministic",
+  "targets": ["web", "phone", "pc", "worker", "js", "vm", "project"],
+  "ai_docs": ["/llms.txt", "/docs/AI_CRAWLER_GUIDE.md", "/docs/LANGUAGE_SPEC.md"]
+}

package/.wrangler/cache/pages.json

@@ -0,0 +1,4 @@
+{
+  "account_id": "f79ff34dae9f11ac6bf1d717cf63bd39",
+  "project_name": "clearkrypt"
+}

package/.wrangler/cache/wrangler-account.json

@@ -0,0 +1,6 @@
+{
+  "account": {
+    "id": "f79ff34dae9f11ac6bf1d717cf63bd39",
+    "name": "Caleb.owen2019@outlook.com's Account"
+  }
+}

package/DEPLOYMENT_CLEARKRYPT.md

@@ -0,0 +1,53 @@
+# ClearKrypt Deployment
+
+This v3 package separates the public ClearKrypt website from compiled example apps.
+
+Do **not** deploy `dist/web` unless you intentionally want to deploy a compiled sample app.
+
+## Deploy the public ClearKrypt site
+
+```powershell
+cd C:\Users\COwen\Downloads\clearkrypt\clearkrypt_language
+npx wrangler pages project create clearkrypt
+npx wrangler pages deploy .\site --project-name clearkrypt
+```
+
+Attach this custom domain to the `clearkrypt` Pages project:
+
+```text
+clearkrypt.clearkey.solutions
+```
+
+This site includes:
+
+```text
+/
+/sandbox/
+/extensions/
+/llms.txt
+/.well-known/clearkrypt.json
+/sitemap.xml
+```
+
+## Deploy docs at docs.clearkey.solutions/clearkrypt
+
+Option A, same site already includes docs at `/docs/clearkrypt`.
+
+Option B, separate docs Pages project:
+
+```powershell
+npx wrangler pages project create clearkey-docs
+npx wrangler pages deploy .\site\docs --project-name clearkey-docs
+```
+
+Attach this custom domain to the `clearkey-docs` Pages project:
+
+```text
+docs.clearkey.solutions
+```
+
+Then the docs live at:
+
+```text
+https://docs.clearkey.solutions/clearkrypt/
+```

package/README.md

@@ -0,0 +1,96 @@
+# ClearKrypt
+
+ClearKrypt is a powerful cross-platform application language designed for deterministic 1-to-1 export across web, worker, server, and future native targets.
+
+This repository contains the first launchable foundation:
+
+- npm package
+- CLI
+- parser
+- compiler
+- VM target
+- web target
+- worker target
+- docs
+- standard library plan
+- examples
+- Duolingo-style course
+
+## Install locally
+
+```bash
+npm install
+npm link
+ck --help
+```
+
+## Run example
+
+```bash
+ck run examples/fixit-dashboard/main.ck
+```
+
+## Build web app
+
+```bash
+ck build examples/fixit-dashboard/main.ck --target web --out dist/fixit-dashboard
+```
+
+Open `dist/fixit-dashboard/index.html`.
+
+## Build Cloudflare Worker
+
+```bash
+ck build examples/fixit-dashboard/main.ck --target worker --out dist/worker
+```
+
+## Important Reality
+
+This is a real runnable foundation, not a complete Dart-sized ecosystem. A truly production-grade language ecosystem normally requires years of compiler, VM, package, IDE, runtime, and platform work. This package gives ClearKrypt a serious launch base that can be expanded without throwing it away.
+
+
+## New in this package
+
+### Multi-platform build environments
+
+```bash
+ck build-all examples/fixit-dashboard/main.ck --out build
+```
+
+This creates `web/`, `phone/`, `pc/`, and `worker/` folders so developers can see exactly how one ClearKrypt source compiles for browser, mobile, desktop, and edge runtime environments.
+
+### Visual drag editor
+
+```bash
+ck studio examples/fixit-dashboard/main.ck --out studio
+```
+
+Open `studio/index.html`, drag UI nodes, and copy/download the updated `.ck` source. ClearKrypt stores drag positions as `@pos(x, y)` metadata directly in the source code.
+
+### AI/crawler friendly
+
+This package includes `llms.txt`, `ai-plugin.json`, `.well-known/clearkrypt.json`, `docs/AI_CRAWLER_GUIDE.md`, and `sitemap.xml` so search engines and AI coding tools can understand how to generate ClearKrypt apps without guessing.
+
+## Public website vs compiled app output
+
+The public ClearKrypt language website is in:
+
+```text
+site/
+```
+
+Deploy that folder for the language homepage, sandbox, extensions page, crawler files, and docs shell.
+
+Do not deploy `dist/web` unless you are deploying an app generated from a `.ck` file.
+
+```bash
+npx wrangler pages deploy ./site --project-name clearkrypt
+```
+
+
+## v4 website deployment
+Deploy the public ClearKrypt website from `site/`, not from `dist/web`. `dist/web` is for compiled user programs.
+
+```powershell
+npx wrangler pages deploy .\site --project-name clearkrypt
+```

package/ai-plugin.json

@@ -0,0 +1,12 @@
+{
+  "schema_version": "v1",
+  "name_for_human": "ClearKrypt Language",
+  "name_for_model": "clearkrypt_language",
+  "description_for_human": "ClearKrypt is a cross-platform app language with deterministic web, phone, PC, worker, JS, and VM builds.",
+  "description_for_model": "Use ClearKrypt syntax to create apps. Read docs/AI_CRAWLER_GUIDE.md, docs/LANGUAGE_SPEC.md, and docs/STDLIB.md before generating code.",
+  "auth": { "type": "none" },
+  "api": { "type": "openapi", "url": "/openapi.yaml" },
+  "logo_url": "/clearKrypt-logo.png",
+  "contact_email": "support@example.com",
+  "legal_info_url": "/legal"
+}

package/bin/clearkrypt.js

@@ -0,0 +1,55 @@
+#!/usr/bin/env node
+import fs from 'node:fs';
+import path from 'node:path';
+import { compileFile, runFile, initProject } from '../src/index.js';
+
+const args = process.argv.slice(2);
+const cmd = args[0];
+function flag(name, fallback=null){ const i=args.indexOf(name); return i>=0 ? args[i+1] : fallback; }
+function has(name){ return args.includes(name); }
+function help(){
+  console.log(`ClearKrypt v0.1.0
+
+Usage:
+  ck init <name>
+  ck run <file.ck>
+  ck build <file.ck> --target js|web|phone|pc|worker|vm|project --out <dir>
+  ck build-all <file.ck> --out <dir>
+  ck studio <file.ck> --out <dir>
+  ck check <file.ck>
+  ck docs
+  ck site --out <dir>
+`);
+}
+try {
+  if(!cmd || has('--help') || has('-h')) help();
+  else if(cmd==='init') initProject(args[1] || 'clearkrypt-app');
+  else if(cmd==='run') await runFile(args[1]);
+  else if(cmd==='check') { const res = await compileFile(args[1], {target:'vm'}); console.log('✓ ClearKrypt check passed:', res.meta.name || args[1]); }
+  else if(cmd==='build-all') {
+    const input=args[1]; const out=flag('--out','clearkrypt-build');
+    const result = await compileFile(input,{target:'project',outDir:out});
+    console.log(`✓ Built all environments for ${input} -> ${out}`);
+    if(result.files) for(const f of result.files) console.log('  '+f);
+  } else if(cmd==='studio') {
+    const input=args[1]; const out=flag('--out','clearkrypt-studio');
+    const result = await compileFile(input,{target:'web',outDir:out});
+    const studioSrc = path.resolve(path.dirname(new URL(import.meta.url).pathname),'../tools/studio');
+    fs.cpSync(studioSrc, out, {recursive:true});
+    fs.copyFileSync(input, path.join(out,'source.ck'));
+    console.log(`✓ Visual studio exported -> ${out}. Open index.html`);
+
+  } else if(cmd==='site') {
+    const out=flag('--out','clearkrypt-site');
+    const siteSrc = path.resolve(path.dirname(new URL(import.meta.url).pathname),'../site');
+    fs.rmSync(out,{recursive:true,force:true});
+    fs.cpSync(siteSrc, out, {recursive:true});
+    console.log(`✓ ClearKrypt public website exported -> ${out}`);
+  } else if(cmd==='build') {
+    const input=args[1]; const target=flag('--target','web'); const out=flag('--out','dist');
+    const result = await compileFile(input,{target,outDir:out});
+    console.log(`✓ Built ${input} -> ${out} (${target})`);
+    if(result.files) for(const f of result.files) console.log('  '+f);
+  } else if(cmd==='docs') console.log('Open docs/README.md in this package.');
+  else help();
+} catch(e){ console.error('ClearKrypt error:', e.message); if(process.env.CK_DEBUG) console.error(e.stack); process.exit(1); }

package/course/duolingo_course.md

@@ -0,0 +1,127 @@
+# ClearKrypt Academy — Duolingo-Style Course
+
+## Unit 1: First Words
+
+Goal: write your first app.
+
+### Lesson 1
+Prompt: Translate this into ClearKrypt: The app is called Hello.
+
+Answer:
+
+```ck
+app "Hello"
+```
+
+### Lesson 2
+Prompt: Create a screen named Home.
+
+```ck
+screen Home {
+}
+```
+
+### Lesson 3
+Prompt: Add a title.
+
+```ck
+screen Home {
+  title "Welcome"
+}
+```
+
+## Unit 2: UI Building
+
+Skills:
+
+- cards
+- buttons
+- text
+- layouts
+- navigation
+
+Exercise:
+
+```ck
+screen Home {
+  card {
+    title "FixIt QC"
+    text "Operational tools in one place"
+    button "Open" {
+      go Dashboard
+    }
+  }
+}
+```
+
+## Unit 3: Data
+
+Skills:
+
+- types
+- fields
+- lists
+- records
+
+Exercise:
+
+```ck
+type Equipment {
+  id: Text
+  status: Text
+  station: Text
+}
+```
+
+## Unit 4: Logic
+
+Skills:
+
+- variables
+- functions
+- conditions
+- loops
+
+```ck
+task canEdit(role: Text) -> Bool {
+  when role is "admin" {
+    return true
+  } otherwise {
+    return false
+  }
+}
+```
+
+## Unit 5: Cloud Apps
+
+Skills:
+
+- save
+- query
+- auth
+- policies
+- notifications
+
+## Unit 6: Visual Apps
+
+Skills:
+
+- glass UI
+- themes
+- animation
+- responsive layouts
+- platform adaptation
+
+## Unit 7: Deployment
+
+Skills:
+
+- web build
+- worker build
+- VM build
+- environment secrets
+- app signing
+
+## Unit 8: Mastery Project
+
+Build a full operational dashboard with users, reports, work orders, notifications, and admin tools.

package/docs/AI_CRAWLER_GUIDE.md

@@ -0,0 +1,74 @@
+# ClearKrypt AI and Crawler Guide
+
+This file is intentionally written for search engines, crawlers, and AI coding assistants.
+
+## What ClearKrypt is
+
+ClearKrypt is a cross-platform application programming language for building web apps, phone apps, desktop apps, workers, dashboards, and operational tools from one source language.
+
+## Canonical syntax sample
+
+```ck
+app "Example"
+use ui
+use data
+
+screen Home {
+  title "Example App"
+  card {
+    text "Welcome"
+    button "Continue" { go Dashboard }
+  }
+}
+
+task add(a: Number, b: Number) -> Number {
+  return a + b
+}
+```
+
+## Important concepts
+
+- `app` names the application.
+- `use` imports a standard library capability.
+- `type` declares structured data.
+- `screen` declares UI.
+- `task` declares callable logic.
+- `intent` declares event-driven automation.
+- `@pos(x, y)` is optional layout metadata used by ClearKrypt Visual Studio.
+
+## Build commands
+
+```bash
+ck run src/main.ck
+ck build src/main.ck --target web --out dist-web
+ck build src/main.ck --target phone --out dist-phone
+ck build src/main.ck --target pc --out dist-pc
+ck build-all src/main.ck --out dist-all
+ck studio src/main.ck --out studio
+```
+
+## How AI should generate ClearKrypt apps
+
+When a user asks an AI to create a ClearKrypt app:
+
+1. Create `app "Name"` first.
+2. Add `use ui`, `use data`, `use cloud`, or other libraries as needed.
+3. Define data with `type` blocks.
+4. Define screens with `screen` blocks.
+5. Define reusable logic with `task` blocks.
+6. Define automations with `intent` blocks.
+7. Use explicit strings and readable names.
+8. Put layout hints in `@pos(x, y)` only when pixel-level positioning is requested.
+
+## Crawler files
+
+A ClearKrypt project should include:
+
+- `README.md`
+- `docs/LANGUAGE_SPEC.md`
+- `docs/STDLIB.md`
+- `docs/AI_CRAWLER_GUIDE.md`
+- `llms.txt`
+- `ai-plugin.json`
+- `sitemap.xml`
+- `.well-known/clearkrypt.json`

package/docs/COMPILER_ARCHITECTURE.md

@@ -0,0 +1,62 @@
+# Compiler Architecture
+
+ClearKrypt uses a clean multi-stage compiler pipeline.
+
+```text
+.ck source
+  -> lexer tokens
+  -> AST parser
+  -> semantic analyzer
+  -> typed IR
+  -> target emitter
+  -> deployable artifact
+```
+
+## 1-to-1 Export Strategy
+
+ClearKrypt does not ask AI to rewrite app code for each platform. Instead, every source construct maps to a canonical intermediate representation.
+
+Example:
+
+```ck
+button "Save" { say "saved" }
+```
+
+Becomes this target-neutral IR:
+
+```json
+{
+  "node": "Button",
+  "label": "Save",
+  "actions": [{"op":"Print","value":"saved"}]
+}
+```
+
+Emitters then produce exact target code.
+
+## Runtime Layers
+
+1. VM runtime for bytecode.
+2. JS runtime for web/server.
+3. Native render bridge for future Swift/Kotlin/Flutter targets.
+4. Cloud adapter runtime for Firebase/Cloudflare/AWS/Supabase.
+
+## What is included now
+
+- Working lexer
+- Working parser
+- Basic semantic analyzer
+- VM output
+- JS output
+- Web output
+- Cloudflare Worker output
+
+## What should be built next
+
+- Full typed IR
+- Package manager
+- LSP server
+- WASM VM
+- Flutter emitter
+- Swift/Kotlin emitters
+- Runtime conformance tests

package/docs/COMPLETE_LANGUAGE_GUIDE.md

@@ -0,0 +1,137 @@
+## Start Here
+ClearKrypt apps begin with an app declaration, imports, and one or more screens. Everything visual can include metadata like @pos(x, y) so the visual editor can modify source code safely.
+```ck
+app "My App"
+use ui
+
+screen Home {
+  title "Welcome" @pos(40, 60)
+  text "This is ClearKrypt." @pos(40, 130)
+}
+```
+
+## Syntax Basics
+ClearKrypt uses readable blocks, quoted labels, strongly named constructs, and brace-delimited scopes. Semicolons are not required.
+```ck
+task greet(name: Text) -> Text {
+  return "Hello " + name
+}
+```
+
+## Types
+Core types include Text, Number, Bool, Date, List<T>, Map<K,V>, Record, Screen, Event, Result<T>, and platform resources.
+```ck
+type WorkOrder {
+  id: Text
+  equipmentId: Number
+  status: Text
+  createdAt: Date
+}
+```
+
+## UI Components
+The UI library supports title, text, button, card, list, form, input, badge, table, chart, map, modal, drawer, tabs, toast, and custom components.
+```ck
+screen Dashboard {
+  card "Open Work Orders" @pos(40, 80) {
+    badge "Live"
+    button "Open" @pos(65, 170) { go WorkOrders }
+  }
+}
+```
+
+## Layout and @pos
+@pos(x, y) is source-owned layout metadata. Studio and Sandbox drag operations update this metadata without AI translation.
+```ck
+title "Drag Me" @pos(120, 64)
+text "The source changes when I move." @pos(120, 128)
+```
+
+## Data and State
+ClearKrypt supports data declarations, collections, records, local state, and adapter-backed persistence.
+```ck
+data orders = from firestore "workOrders"
+  where status is not "closed"
+  sort createdAt desc
+```
+
+## Events and Actions
+Buttons and UI events contain action blocks. Actions can say, go, save, notify, call tasks, or invoke adapters.
+```ck
+button "Submit" @pos(40, 300) {
+  save report to firestore "reports"
+  say "Submitted"
+}
+```
+
+## Build Targets
+ClearKrypt exports to web, phone, PC, worker, JavaScript, VM bytecode, and project scaffolds using deterministic compiler targets.
+```ck
+ck build app/main.ck --target web --out dist/web
+ck build app/main.ck --target phone --out dist/phone
+ck build app/main.ck --target pc --out dist/pc
+ck build-all app/main.ck --out dist
+```
+
+## Compiler Internals
+The package includes lexer, parser, semantic checker, emitters, CLI, and VM runtime. These are real files in src/ and bin/.
+```ck
+src/lexer.js
+src/parser.js
+src/semantic.js
+src/targets/web.js
+src/vm.js
+bin/clearkrypt.js
+```
+
+## Extensions
+Extensions add platform capabilities. They should declare clear source syntax, compiler lowering rules, docs, and AI examples.
+```ck
+use firebase
+use cloudflare
+use ui
+```
+
+## AI and Crawlers
+ClearKrypt includes llms.txt, sitemap.xml, ai-plugin.json, .well-known metadata, examples, and source docs so AI tools can learn syntax from canonical public content.
+```ck
+/llms.txt
+/sitemap.xml
+/.well-known/clearkrypt.json
+/docs/clearkrypt/
+```
+
+## Deployment
+Deploy the language site from site/. Deploy generated apps from dist/web only when you intentionally compile a specific ClearKrypt program.
+```ck
+npx wrangler pages deploy ./site --project-name clearkrypt
+npx wrangler pages deploy ./docs-site --project-name clearkey-docs
+```
+
+# Layout must be usable without dragging
+
+ClearKrypt screens should normally begin with an explicit layout.
+
+```clearkrypt
+screen Home {
+  layout Stack
+  title "A usable page"
+  text "Everything aligns automatically."
+}
+```
+
+`@pos(x, y)` is not required. It is treated as visual-editor metadata unless `layout Freeform` is used.
+
+# Module model
+
+A `use` line imports a standard capability group. `use ui` is not a style. It is the vocabulary that enables visual app components. Styling and layout are controlled by `layout`, `theme`, containers, and components.
+
+Recommended starter imports:
+
+```clearkrypt
+use ui
+use data
+use storage
+```
+
+Use `auth`, `network`, `platform`, `worker`, `crypto`, `ai`, `test`, and `deploy` when the app needs those capabilities.