# Atlas Kit

> Unofficial, public `0.x` non-custodial TypeScript SDK for validated Star
> Atlas SAGE C4 reads, signer-free Plan simulation, and explicitly configured
> Plan execution. It is ESM-only and uses `@solana/kit` addresses and external
> signers.

## Documentation

- [Full consumer context](https://atlas-kit-docs.pages.dev/llms-full.txt): the reviewed consumer
  documentation in one file — the README, the public API review, the consumer
  agent guide, and the generated-binding upgrade procedure
- [What is this?](https://atlas-kit-docs.pages.dev/start-here/what-is-this/): SAGE, the z.ink test
  realm, and what the SDK does and refuses to do
- [Your first read](https://atlas-kit-docs.pages.dev/start-here/first-read/): install, connect an
  RPC, and read a fleet in five minutes
- [Guides](https://atlas-kit-docs.pages.dev/guides/): one guide per capability, each with a
  runnable, parameterised example
- [Concepts](https://atlas-kit-docs.pages.dev/concepts/): caching, discovery, errors,
  subscriptions, and the bindings escape hatch
- [API reference](https://atlas-kit-docs.pages.dev/reference/): generated for every public entry
  point from the package `exports` map
- [Glossary](https://atlas-kit-docs.pages.dev/glossary/): Star Atlas terms used across the
  documentation
- [Agent skill](https://atlas-kit-docs.pages.dev/skill/SKILL.md): a compact briefing an assistant can
  install directly — entry-point map, the conventions that a reasonable guess
  gets wrong, and the Plan execution contract

## Repository

The source repository is private; every consumer-facing document above is
served by the site, and the four repository documents are inlined in the
full consumer context. Agents working inside the repository itself should
additionally read `TEST_PLAN.md` (verification contract) and the fixture
registries under `fixtures/` (captured-account provenance and dated PTR
anchors).

Use `createSageClient` for loaded Profile → Character → Fleet traversal or
capability functions for focused imports. Start from a known Profile address.
Never infer wallet-to-Profile derivation. For writes, use only inspectable Plans,
signer-free `simulatePlan`, and explicitly configured `executePlan`; never
blindly retry an unknown outcome. Do not use previous-generation Star Atlas SDK
packages.