KAI OS v0.3.1 First-Run Tour

KAI OS v0.3.1 First-Run Tour

KAI OS v0.3.1 is the first public release shaped around a clear product loop:

Git change -> kaios review -> review.md + trace.json + capsule.json -> review/audit/baseline gate

KAI OS is not a chatbot framework or Kotlin LangChain clone. It is a local-first Evidence OS for AI agents in Kotlin: agent runs become process traces, replayable capsules, syscall ledgers, and CI-ready runtime evidence.

Agent    = Process
Workflow = Scheduler
Tool     = Syscall
Memory   = Process state

Try It First

Local install:

curl -fsSL https://morning-verlu.github.io/KAI/install.sh | sh
export PATH="$HOME/.kaios/bin:$PATH"
kaios tour

No local Java or Gradle setup:

https://codespaces.new/morning-verlu/KAI?quickstart=1

Then run:

./scripts/codespaces-smoke.sh

Docker path:

docker build -t kaios:local .
docker run --rm kaios:local tour

No install at all:

• Evidence Viewer: https://morning-verlu.github.io/KAI/evidence-viewer.html
• Start here: https://github.com/morning-verlu/KAI/blob/main/START_HERE.md
• Evidence Sample: https://github.com/morning-verlu/KAI/tree/main/examples/evidence-sample
• Evidence Artifact Map: https://morning-verlu.github.io/KAI/assets/kaios-evidence-map.png
• JVM Service Review: https://github.com/morning-verlu/KAI/tree/main/examples/jvm-service-review
• Baseline Gate: https://github.com/morning-verlu/KAI/tree/main/examples/baseline-gate

Kotlin/JVM runtime library path:

./gradlew -p examples/kotlin-runtime-api run

• Kotlin/JVM evaluation path: https://github.com/morning-verlu/KAI/blob/main/docs/KOTLIN_JVM_EVALUATION.md
• Kotlin Runtime API: https://github.com/morning-verlu/KAI/blob/main/docs/KOTLIN_API.md
• Runnable example: https://github.com/morning-verlu/KAI/tree/main/examples/kotlin-runtime-api

Help In 5 Minutes

If the Evidence OS direction feels useful, the fastest way to help is to make
one public signal or one small verification concrete:

• Star the repo if you want local-first agent evidence to exist in the
  Kotlin/JVM ecosystem: https://github.com/morning-verlu/KAI
• Share the no-install Evidence Viewer with one Kotlin/JVM developer:
  https://morning-verlu.github.io/KAI/evidence-viewer.html
• Pick a small launch task from the Contributor Board:
  https://github.com/morning-verlu/KAI/blob/main/docs/CONTRIBUTOR_BOARD.md
• Add a Kotlin API capability recipe: #14
• Add a denied-syscall evidence walkthrough: #15
• Verify full Docker smoke on a normal network: #16

The shortest rationale is here:

• Why Star KAI OS: https://github.com/morning-verlu/KAI/blob/main/docs/WHY_STAR.md

What The Tour Proves

kaios tour creates a disposable Git workspace, runs the no-key onboarding path, makes a small code change, runs kaios review, and prints pointers to:

• Markdown review artifact.
• process table with PID, state, tokens, memory, syscalls, tool time, and cost.
• kaios.process-trace/v1 JSON.
• replayable kaios.run-capsule/v1.
• kaios.review/v1 output.
• PR-friendly evidence summary.
• recovery dry-run report.

The point is that agent work leaves runtime evidence that can be inspected, copied, replayed offline, and compared in CI without requiring an external model provider.

Highlights

• Added kaios tour, a no-key walkthrough for the full Evidence OS loop.
• Added kaios.tour/v1 JSON output for docs, launch posts, and smoke checks.
• Added kaios try as a friendly alias for the tour.
• Added checked-in evidence examples so visitors can inspect traces, capsules, replay, and baseline drift before installing.
• Added a no-install Evidence Viewer for inspecting a process table, syscall ledger, replayable capsule, and baseline gate from the browser.
• Added Codespaces and Docker trial paths for no-local-Java evaluation.
• Added a Kotlin Runtime API example for teams evaluating KAI OS as an embeddable JVM library.
• Added visual evidence artifacts for launch posts and first-run evaluation.
• Updated README, install docs, launch site, launch kit, and quickstart docs around the tour-first path.

Feedback Wanted

I am looking for feedback from Kotlin/JVM developers, OSS maintainers, and agent infrastructure builders:

• Does the Agent = Process / Workflow = Scheduler / Tool = Syscall model make the project legible?
• Would replayable run capsules help in PR review, support, or CI?
• Is kaios review useful enough to run on a real JVM/Kotlin repo?
• Does the Kotlin Runtime API feel like the right abstraction boundary?

Feedback links:

• Discussion: #8
• Focused Kotlin/JVM feedback discussion: #17
• Kotlin/JVM evaluation path: https://github.com/morning-verlu/KAI/blob/main/docs/KOTLIN_JVM_EVALUATION.md
• Evidence feedback issue: https://github.com/morning-verlu/KAI/issues/new?template=evidence_feedback.yml

Verification

Core release verification:

./gradlew test installDist distZip distTar --no-daemon
./scripts/repository-ci-smoke.sh
./scripts/codespaces-smoke.sh
./scripts/evidence-samples-smoke.sh
build/install/kaios-cli/bin/kaios tour --json

Evidence contract verification:

build/install/kaios-cli/bin/kaios capsule --file examples/evidence-sample/change-review.capsule.json --check
build/install/kaios-cli/bin/kaios replay --file examples/evidence-sample/change-review.capsule.json
build/install/kaios-cli/bin/kaios capsule --file examples/baseline-gate/capsules/baseline.capsule.json --check
build/install/kaios-cli/bin/kaios capsule --file examples/baseline-gate/capsules/current-different.capsule.json --check
build/install/kaios-cli/bin/kaios diff examples/baseline-gate/capsules/baseline.capsule.json examples/baseline-gate/capsules/current-different.capsule.json --check

kaios diff ... --check intentionally exits 1 for the baseline-gate sample because the gate detects valid changed runtime behavior.

Docker note: docker build --check . has been verified locally. Full Docker smoke depends on Docker Hub and Alpine package download speed in the local environment.