Skip to content

Website sources

Captured 2026-10-27. The site is a React app (plain HTTP fetch returns only the <title>), so content was taken from the site's own machine-readable surfaces.

Snapshot

URL Captured as Notes
https://www.machineworld.io/machine-world rendered page text (Chrome) Banner: "MW CLI LIVE · Server-side Processes rolling out in waves", "MACHINE WORLD · V0.1.0 DRAFT"
https://machineworld.io/llms.txt _work/web/llms.txt (10 KB) curated index for LLM crawlers
https://machineworld.io/llms-full.txt _work/web/llms-full.txt (233 KB) all 16 user-facing pages concatenated; primary website evidence
https://machineworld.io/sitemap.xml _work/web/sitemap.xml 28 URLs, every lastmod = 2026-06-11
https://machineworld.io/robots.txt _work/web/robots.txt explicit allowlist for AI crawlers

Pages in the sitemap (/machine-world/...): early-access, caregiver, caregiver-deep-dive, dhamma-reference, orchestrates-a-real-day, digital-physical-human, trust-gradient, where-your-data-lives, when-things-break, human-guidance, economy, faq, practice-guide, builders-start-here, process-pattern, viveka-and-autonomy, intent-calibration-and-skill-economy, capabilities. Sibling pillars: /marga-sakachcha/, /inner-realm, plus /contact, /careers.

Local source of these pages: [local path] (the site renders from these files; local copies are newer than the sitemap date in places, e.g. App-Translation-Review-2026-10-21.csv).

What the site says Machine World is (current, as published)

  • Three pillars under one project: Marga Sakacchā (Mind door, Abhidhamma study in Sinhala), Machine World (System door, "AIware, not software"), Inner Realm (Sound door, AI-native music). One shared invariant: no output may give rise to lobha / dosa / moha (the "vinaya").
  • Machine World = local-first CLI (mw) that runs Processes: coordinated work across digital tools, physical devices and humans. Five layers: Skill -> Workflow -> Routine (time-driven) -> Loop (state-driven) -> Process.
  • Every actor (digital, physical, human) signs the same six-field contract: identity, capabilities, availability, constraints, rate, SLA.
  • Trust gradient, four stages: read-only / suggest / one-click approve / act within rules. Irreversibles never escalate above Stage 3.
  • Data under ~/.machineworld/; nothing leaves without opt-in.
  • Bring-your-own-model: claude-cli, ollama, openrouter, openai-compat.
  • Economy: prepaid token packs; 15% of each invocation to a capability pool for skill contributors; 1% floor for original-author lineage; platform fee <=10%.
  • Two showcase scenarios: Caregiver across continents (Anjali in Toronto, mother Padma in Colombo) and Dhamma reference, grounded never generated (Tipiṭaka retrieval with citations; doctrine retrieved, not generated).
  • Install: curl -fsSL https://get.machineworld.io | sh (macOS, Linux, WSL).
  • Engine repo named on the site: github.com/dinukxx/Machineworld.

Status claims on the site (use these labels)

From FAQ #49 and builders-start-here:

Claim Site label
Local CLI mw (Ink/React TUI calling python -m machineworld.pipeline) Built today
Four BYOM backends Built today
Household data dirs, call ledger, MCP client + local subprocess MCPs Built today
Process pattern, first instance = self-evaluation loop (mw self-eval), shipped 2026-05-08 Built today
Skill authoring via SKILL.md + intent calibration; workflows/routines/loops Today
vinaya-alignment v1.0.0 production-locked Built today
MW-managed tier, token economy, multi-household sharing, remote sync Specced, not load-bearing
Android edge container, iOS, web UI, Telegram interface Roadmap (after first-human session validates the CLI)
Skill marketplace; 15%-to-creator earnings; worker payments Roadmap / ships with managed tier
Guidance agent for human actors (task-guidance) Specced, not shipped
Voice "Today MW is a text CLI", voice only specced for Android edge
Caregiver: subscription audit, Sinhala med reminders Partly
Caregiver: mobile top-up, open-banking bill watch Roadmap
Local offline Sinhala+Pāli+English Gemma fine-tune "when ready"

Inconsistencies found (UNRESOLVED)

Topic Source A Source B
Version site banner V0.1.0 DRAFT, FAQ #8 0.1.0-draft CLI install dir v0.2.9, --version 0.2.0
Production / verified skills FAQ #8: only vinaya-alignment is production + verified FAQ #49: 48 skills, 24 vinaya-verified (2026-05-09); mw skills: 19 production; mw doctor: 4 verified
CLI verified end-to-end? FAQ #8: "compiles but has not been verified end-to-end" FAQ #49 lists it as built; v0.2.0 notes: 1508 tests pass
Engine repo site: dinukxx/Machineworld v0.2.0 notes: machineworld-io/machineworld
LLM providers site: 4 backends CLI ADR-002 "OpenRouter only" (older decision, likely SUPERSEDED)

| LLM backends (names) | landing page and early-access page: "Claude Max, Ollama, OpenRouter, or LM Studio" | llms-full / FAQ: claude-cli, ollama, openrouter, openai-compat | | Skill-creator earnings | landing page: "Creators earn 15% of every invocation of their skill — forever" | source of truth v4: pricing not per token (economy model SUPERSEDED for the platform; creator share not addressed) |

Added 2026-10-28 (full crawl, see website-inventory)

  • The landing page says its 18 documents are "auto-mirrored from the engine repo", source dinukxx/Machineworld, commit 72a7d3e. That repository is not public (GitHub API: Not Found), so the mirror cannot be checked against the repo.
  • 27 links inside the published Markdown point to repository paths the site does not host (e.g. /PROCESS-PATTERN.md, /economy/specs/actor-contract.md, /mw-content/household-finance.md). On the live site they open the empty app shell: broken links on the site.
  • The landing page names two documents whose engineer versions "stay private" (docs/VIVEKA-AND-AUTONOMY.md, docs/INTENT-CALIBRATION-AND-SKILL-ECONOMY.md).
  • Early-access and careers forms store submissions in Firestore project machineworld-b404b (stated on the pages). Forms were not submitted.
  • The site's source folder holds 25 files the live site does not serve: dated planning, spec and research documents from Sep–Oct 2026. Indexed in local-documents.
  • Every published Markdown file is identical to its local copy apart from line endings.

The FAQ itself says to treat the docs as "architectural intent ... not yet proof of running behaviour". This knowledge base therefore labels website claims as stated by the official site and only marks something IMPLEMENTED when the installed CLI also shows it.