> For the complete documentation index, see [llms.txt](https://devlab-machines.gitbook.io/devlab-machines-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devlab-machines.gitbook.io/devlab-machines-docs/core-coordinator.md).
# Core coordinator
Machines registry
The app persists machines, fixed snapshots, jobs, candidates, events, and replay receipts. Browsing is public; private actions require a signed wallet account. Machine publication exposes configuration and evidence, not private financial records.
## Sign-in
Sign-in is Solana wallet only. The server issues a one-use nonce message, the wallet signs it (ed25519), and the server verifies the signature before minting a session. No email provider is involved, and signing is free — it sends no transaction.
## Data authority
* Machine lifecycle writes go through authenticated server functions after an ownership check; browsers receive read-only access to public registry and evidence data.
* AI writes (proposals, results, run status) go through the server only after an ownership read; clients cannot forge completed results.
* Chain/token state is recorded only after server-side on-chain verification — the database never leads the chain.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://devlab-machines.gitbook.io/devlab-machines-docs/core-coordinator.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
