Launch checklist for first 100 stars

[morning-verlu]

Track public launch work for KAI OS v0.3.1.

Goal:
Get KAI OS in front of Kotlin/JVM developers, OSS maintainers, and agent infrastructure builders through real interest, not artificial engagement.

Current positioning:

Local-first Evidence OS for AI agents in Kotlin
Agent = Process, Workflow = Scheduler, Tool = Syscall

Primary CTA:

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

Public links:

• Repo: https://github.com/morning-verlu/KAI
• Site: https://morning-verlu.github.io/KAI/
• Codespaces: https://codespaces.new/morning-verlu/KAI?quickstart=1
• Release: https://github.com/morning-verlu/KAI/releases/tag/v0.3.1
• Discussion: KAI OS v0.3.1: first-run Evidence OS tour #8
• Comparison: https://github.com/morning-verlu/KAI/blob/main/docs/COMPARISON.md
• Evidence OS docs: https://github.com/morning-verlu/KAI/blob/main/docs/EVIDENCE_OS.md
• Evidence sample: https://github.com/morning-verlu/KAI/tree/main/examples/evidence-sample
• JVM service review example: https://github.com/morning-verlu/KAI/tree/main/examples/jvm-service-review
• Baseline gate example: https://github.com/morning-verlu/KAI/tree/main/examples/baseline-gate
• Evidence feedback: https://github.com/morning-verlu/KAI/issues/new?template=evidence_feedback.yml
• Launch kit: https://github.com/morning-verlu/KAI/blob/main/docs/LAUNCH_KIT.md
• Social preview image: https://morning-verlu.github.io/KAI/assets/kaios-social-card.png
• Demo GIF: https://morning-verlu.github.io/KAI/assets/kaios-demo.gif
• Reddit r/Kotlin post: https://www.reddit.com/r/Kotlin/comments/1u6cj41/ (posted, currently filtered by Reddit; modmail approval request attempted)
• X post: https://x.com/wurslu/status/2066465796101136615

Contributor entrypoints:

• [Good first issue]: Verify the Codespaces first-run path #11 Verify the Codespaces first-run path
• [Infrastructure]: Enable public GitHub Actions CI #12 Enable public GitHub Actions CI after workflow scope is available

Completed contributor examples:

• [Good first issue]: Add a JVM service review example #9 JVM service review example
• [Good first issue]: Add a baseline diff evidence sample #10 Baseline gate evidence sample

Checklist:

• Publish GitHub Pages launch site.
• Add hosted one-command installer.
• Add GitHub Codespaces path for no-local-install trials.
• Ship v0.3.1 first-run kaios tour with no API key requirement.
• Add README first-screen install + kaios tour CTA.
• Add release badge, discussions badge, demo GIF, and process-table preview.
• Update site hero and metadata around Evidence OS.
• Refresh roadmap and contributing docs around v0.3.1 Evidence OS.
• Replace stale launch docs with outbound posts centered on kaios tour.
• Update GitHub Discussion KAI OS v0.3.1: first-run Evidence OS tour #8 with the v0.3.1 tour CTA.
• Add a no-install Evidence Sample with review artifact, process trace, replayable capsule, and kaios.review/v1 JSON.
• Add an Evidence feedback issue template for readers who inspect tour/review/sample artifacts.
• Refresh v0.3.1 release notes and Discussion KAI OS v0.3.1: first-run Evidence OS tour #8 with Codespaces, Evidence Sample, and feedback CTAs.
• Add public good-first/help-wanted contributor entrypoints for examples, evidence samples, Codespaces, and CI.
• Add a framework comparison page for LangGraph/OpenAI Agents SDK/Koog/LangChain4j positioning.
• Add a runnable JVM service review example.
• Add a baseline gate evidence sample.
• Post the short social pitch on X.
• Pin repository on the maintainer GitHub profile.
• Submit the Kotlin/JVM community draft to r/Kotlin.
• Get r/Kotlin post approved or choose another Kotlin/JVM channel.
• Verify the Codespaces first-run path in an actual Codespace ([Good first issue]: Verify the Codespaces first-run path #11).
• Enable public CI after refreshing token with workflow scope ([Infrastructure]: Enable public GitHub Actions CI #12).
• Post Show HN after logging into Hacker News.
• Post LinkedIn after logging into LinkedIn.
• Reply to early issues/comments within 24 hours.
• Ship one feedback-driven follow-up within 24-48 hours of the first external post.

Notes:
Do not lead with Homebrew. Homebrew is only an install option. The product is KAI OS: the local-first Evidence OS that turns agent runs into process traces, replayable capsules, syscall ledgers, and CI-ready runtime evidence.

[morning-verlu]

Launch progress update:\n\n- v0.1.5 shipped with coroutine DAG scheduling, timeout policy, and sibling cancellation.\n- README now includes a terminal process-table preview for quick sharing.\n- Current open launch blockers: profile pin, public posts, GitHub Actions workflow-scope refresh, and early community replies.\n\nCurrent star count is still 0, so the next highest-leverage step is public posting from docs/LAUNCH_KIT.md plus pinning the repo on the maintainer profile.

[morning-verlu]

Progress update: v0.3.1 first-run tour is released, the README first screen now leads with install + kaios tour, the launch site metadata/hero now points at the no-key Evidence OS loop, and ROADMAP/CONTRIBUTING are refreshed around the v0.3.1 Evidence OS path. Next launch lever: outbound posts that send people directly to kaios tour and the first 60-second evidence loop.

[morning-verlu]

Added a focused comparison/positioning page so new visitors can quickly understand KAI OS versus LangGraph, OpenAI Agents SDK, Koog, and LangChain4j.\n\nLinks:\n- Comparison: https://github.com/morning-verlu/KAI/blob/main/docs/COMPARISON.md\n- Site entry: https://morning-verlu.github.io/KAI/\n\nThis keeps the launch message centered on KAI OS as a local-first Evidence OS, with Homebrew/Codespaces/installers treated as adoption paths rather than the product.

[morning-verlu]

Shipped the JVM service review example as the next conversion artifact after the comparison page.\n\nLink:\n- https://github.com/morning-verlu/KAI/tree/main/examples/jvm-service-review\n\nWhy it matters for launch: visitors can now run kaios review against a realistic Kotlin/JVM backend change instead of only reading static evidence artifacts. The documented flow was validated locally end to end: quickstart, patch check/apply, review JSON capture, process table, and evidence summary.

[morning-verlu]

Shipped the Baseline Gate Evidence Sample.\n\nLink:\n- https://github.com/morning-verlu/KAI/tree/main/examples/baseline-gate\n\nWhy it matters for launch: the repo now has a concrete no-key example where valid/replayable capsules still cause kaios diff --check to exit 1 because stable runtime behavior changed. This makes the CI-gate part of Evidence OS easier to understand without asking readers to trust abstract docs.

[morning-verlu]

Refreshed the social preview card so shares now lead with the current Evidence OS positioning instead of the older generic AI OS line.

Updated asset:

• https://morning-verlu.github.io/KAI/assets/kaios-social-card.png

New card copy emphasizes Trace, Capsule, Syscall Audit, CI Gate, and the kaios tour && kaios evidence --summary path. This should make X/HN/LinkedIn/GitHub unfurls clearer for first-time visitors.

[morning-verlu]

Added a local evidence samples smoke check so visitors can verify the checked-in Evidence Sample and Baseline Gate artifacts without waiting for public CI.

Command:

./scripts/evidence-samples-smoke.sh

What it validates:

• Evidence Sample capsule contract
• Evidence Sample offline replay
• Baseline/current capsule contracts
• Baseline/current offline replay
• normalized kaios.run-diff/v1 output matches examples/baseline-gate/expected/diff.stable.json
• kaios diff ... --check exits 1 for valid changed runtime behavior

This partially covers the public-CI trust gap while #12 is still blocked on GitHub workflow scope.

[morning-verlu]

Launch checklist update:

New evaluator path is now live on main:

• START_HERE.md: browser-only, local CLI, and artifact-only paths.
• ./scripts/codespaces-smoke.sh: one-command smoke for the Codespaces/browser path.
• Devcontainer now runs ./gradlew installDist --no-daemon, matching the documented build/install/kaios-cli/bin/kaios command.
• GitHub Pages now links to Start here and uses a clearer Star/Fork CTA.

Verified locally:

./scripts/codespaces-smoke.sh
./scripts/evidence-samples-smoke.sh
./gradlew test --no-daemon

Pages deploy for 1de1653 completed successfully. This gives outbound posts a cleaner CTA: Start here -> Codespaces smoke or kaios tour -> inspect artifacts.

[morning-verlu]

Launch checklist update:

Added an Evidence Artifact Map to make the product loop easier to understand at a glance:

• Asset: https://morning-verlu.github.io/KAI/assets/kaios-evidence-map.svg
• README now shows the map before the CLI demo.
• START_HERE.md now opens with the map.
• GitHub Pages now embeds the map in the Evidence section.

The map summarizes the core CTA for outbound posts:

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

Verified locally:

./scripts/evidence-samples-smoke.sh
./scripts/codespaces-smoke.sh
./gradlew test --no-daemon

Pages deploy for 2f4669e completed successfully and the SVG is live with content-type: image/svg+xml.

[morning-verlu]

Launch checklist update:

Added a shareable PNG version of the Evidence Artifact Map for platforms that do not render SVG well:

• PNG: https://morning-verlu.github.io/KAI/assets/kaios-evidence-map.png
• SVG: https://morning-verlu.github.io/KAI/assets/kaios-evidence-map.svg

README and START_HERE.md now use the PNG so GitHub renders the visual reliably. docs/LAUNCH_KIT.md now includes a Visual-First Short Post built around this image.

Suggested outbound angle:

KAI OS turns agent runs into runtime evidence:
Git change -> kaios review -> review.md + trace.json + capsule.json -> review/audit/baseline gate

Verified before push:

./scripts/evidence-samples-smoke.sh
./scripts/codespaces-smoke.sh
./gradlew test --no-daemon

Pages deploy for 61ad7bd completed successfully; the PNG is live as content-type: image/png.

[morning-verlu]

Launch checklist update:

Added a repository CI smoke path as a trust signal while the real .github/workflows/ci.yml push remains blocked by missing workflow scope.

New public assets:

• Local CI smoke: ./scripts/repository-ci-smoke.sh
• Copyable workflow template: examples/github-actions-repository-ci.yml
• CI docs: docs/CI_SETUP.md

The smoke path runs clean build/test/install, validates checked-in Evidence Sample + Baseline Gate capsules, runs kaios tour, validates the generated tour capsule, and replays it offline.

Verified locally:

./scripts/repository-ci-smoke.sh

Pages deploy for e118709 completed successfully. For outbound language, keep it precise: repository CI template and local smoke are ready; public GitHub Actions CI still needs a token with workflow scope.

[morning-verlu]

Launch checklist update:

Added a Docker trial path for visitors who do not want local Java/Gradle and do not want to use Codespaces.

New files and docs:

• Dockerfile: installs the published v0.3.1 release ZIP inside an Alpine-based runtime image.
• .dockerignore: keeps Docker context small.
• ./scripts/docker-smoke.sh: builds the image, runs kaios tour, validates the generated capsule, replays it offline, and checks the bundled Evidence Sample.
• README, START_HERE.md, docs/INSTALL.md, docs/VERIFY.md, and docs/LAUNCH_KIT.md now list the Docker path.

Primary visitor command:

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

Verified this pass:

bash -n scripts/docker-smoke.sh scripts/codespaces-smoke.sh scripts/repository-ci-smoke.sh scripts/evidence-samples-smoke.sh
docker build --check .
./scripts/repository-ci-smoke.sh
./gradlew test --no-daemon

Important note: full ./scripts/docker-smoke.sh did not complete locally because Docker Hub / Alpine package downloads were extremely slow in this environment. The Dockerfile passed Docker build checks, and the release-based design avoids compiling KAI OS inside Docker.