Evergreen public documentation, educator guides, shared learning paths, and
selected examples for PathMX. This repository is intended to become the source
for pathmx.dev; the existing domain is not changed by this scaffold.
Install or update the native PathMX CLI:
bun add -g @fellowhumans/pathmx@latest
pathmx self-update
pathmx play --openThe configured root is paths/index.path.md.
This repository intentionally has no package.json, dependency tree, or
lockfile. PathMX owns the build, Player, and publishing workflow through its
native CLI.
Build into a disposable verification directory:
pathmx build -o .pathmx-check --cleanThe repository configures the Cloudflare provider without a custom domain. Publishing is deliberately split into three actions:
pathmx publish # build and stage a reviewable local snapshot
pathmx publish --dry-run # stage and run provider validation
pathmx publish --deploy # explicit external deploymentDo not use --deploy without maintainer authorization. No command in the
normal build or dry-run workflow changes pathmx.dev or its DNS.
paths/docs/contains current framework and authoring documentation.paths/guides/contains task-oriented educator and learner guides.paths/training/contains reusable, self-paced learning Paths.paths/examples/contains selected examples maintained as evergreen demos..agents/skills/contains the complete managed official PathMX skill set.
The first scaffold curates material from:
- the v1
pathmx.devsite at PathMX v1 revisionff68b7016b4ebb052298ad7cff8aca1ceb661f5e(three methodology patterns, pattern artwork, and the PathMX paper); and - the public Build Week repository at revision
02e701b(the Codex learning-space flow, Chess Opening lesson, and Kepler Orbit demo).
Imported material is adapted for the current v2 vocabulary and command surface. The source repositories remain historical records rather than synchronized copies. Third-party notices are retained beside their assets.
PathMX remains in Labs. Local Play and explicit static Cloudflare publishing are working; hosted multi-user learning spaces and other product boundaries are still evolving.