This is the fastest accurate path through the current MAPLE repo. It shows three things:
- a pure worldline example with no daemon dependency
- the daemon-backed runtime surface exposed by
maple-cli - the optional Ollama-backed playground path exposed by PALM
git clone https://github.com/mapleaiorg/maple.git
cd maple
cargo build -p maple-cli -p palm-daemon -p palmcargo run --manifest-path examples/mwl-worldline-lifecycle/Cargo.tomlThis is the quickest way to see the repo's core thesis in action: durable identity, lifecycle state, and recorded receipts instead of an ephemeral chat loop.
In a new terminal:
cargo run -p maple-cli -- daemon start --foregroundcargo run -p maple-cli -- kernel status
cargo run -p maple-cli -- worldline create --profile agent --label quickstart-agent
cargo run -p maple-cli -- worldline listThose commands exercise the current public runtime surface directly: kernel status, worldline creation, and daemon-backed control.
If you want the local-model path too:
ollama serve
ollama pull llama3.2:3b
cargo run -p maple-cli -- doctor --model llama3.2:3b
cargo run -p palm -- playground set-backend \
--kind local_llama \
--model llama3.2:3b \
--endpoint http://127.0.0.1:11434
cargo run -p palm -- playground infer "Summarize the current playground status"This is the practical "Ollama-like" MAPLE workflow today: Ollama provides the local backend, PALM provides governed backend selection and inference entry points, and the model crates provide the underlying store, router, server, and benchmark types.
- Worldlines turn actors into durable identities.
- PALM turns the runtime into a controllable daemon rather than a one-off process.
maple-cliexposes current governance and provenance surfaces directly.- Ollama is optional; governance and provenance remain visible without it.
Skip step 5. The worldline, kernel, daemon, provenance, and governance flows are still valid and useful without a local model backend.
- Clean up installation details in Installation
- Author a package contract in Author Your First Agent Package
- Inspect the boundary design in Commitment Boundary