> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elata.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Repo Workflows

> Canonical maintainer commands and source-of-truth guidance for the Elata SDK monorepo.

## Canonical Commands

Use `run.sh` from the repo root whenever possible:

```bash theme={null}
./run.sh doctor
./run.sh dev all
./run.sh build all
./run.sh test
./run.sh verify-all
```

## What To Use For Common Jobs

| Job                                                    | Source of truth                                                                         |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| New demo app flow                                      | `@elata-biosciences/create-elata-demo`                                                  |
| Consumer-facing install path and package landing pages | [npm package pages](https://www.npmjs.com/package/@elata-biosciences/create-elata-demo) |
| Consumer-facing package docs                           | package `README.md` files                                                               |
| SDK build, test, release orchestration                 | `run.sh`                                                                                |
| Public app-launch, protocol, and XP context            | `../elata-protocol`                                                                     |
| Release policy and recovery                            | [/sdk/maintainers/releasing](/sdk/maintainers/releasing)                                |
| Repo and package ownership questions                   | `docs/repo-map.md` in `elata-bio-sdk`                                                   |

## Repo Interrogation Order

When you need to confirm whether something is current or canonical:

1. Check the repo `README.md`.
2. Check `run.sh` for command behavior.
3. Check the relevant package `package.json`.
4. Check the nearest package README or docs page.
5. Search the repo with `rg`.

## Verification Rules Of Thumb

* Scaffolder changes: `./run.sh test create-elata-demo`
* Consumer onboarding or packaging changes: `pnpm smoke:consumers`
* `run.sh` changes: run the narrowest affected command, then broaden if release paths changed
* Release tooling changes: `./run.sh verify-all` if feasible
* Docs that mention onboarding: verify the `create-elata-demo` path and the parent-workspace caveat

## Backward Compatibility Notes

* `scripts/dev-link.sh` remains a thin wrapper around `run.sh sync-to`.
* `sync-to` remains useful for local `packages/eeg-web` development.
* Consumer onboarding should still point to `create-elata-demo`, not `sync-to`.

## Related Repos

If you are debugging beyond package boundaries, also use the public protocol repo:

* `../elata-protocol` for contracts, local Anvil deployments, config generation, XP tooling, and simulations

See [Related Repos](/sdk/maintainers/related-repos) for the developer-focused map.