@crvouga/atlas 0.3.0 → 0.5.0

package/docs/reference/server.md

@@ -0,0 +1,685 @@
+# Reference: server
+
+The Atlas server: the API results are uploaded to, the live report, and the viewer on one host. Import path `@crvouga/atlas/server`.
+
+> Generated from the doc comments of `packages/server/src` by `bun run docs`. Do not edit: change the comment next to the code.
+
+### The Atlas server application
+
+Source: `packages/server/src/app.ts`
+
+`createAtlasServer` is the whole of a project's Atlas as one `fetch` handler: the API results are uploaded to, the live
+report every viewer is shown, the gate, the server-sent event stream, the specs and runs the viewer reads, the viewer
+itself, and the server's own description (`/api/openapi.json`, `/llms.txt`). What it knows lives in its backends (by
+default a folder on its own disk), so replacing it loses nothing. Every error leaves as an RFC 9457 problem document; every
+route is described in `openapi.ts` (a test holds the two together).
+
+See docs/server.md
+
+#### `AtlasServerOptions`
+
+```ts
+export type AtlasServerOptions = {
+  /** Every backend, read together. */
+  readonly backends: readonly BackendInput[];
+  /** The id of the backend uploads go to. */
+  readonly write: string;
+  readonly tokens?: readonly ResolvedToken[];
+  readonly anonymousRead?: boolean;
+  /** The built viewer. Without it, only the API is served. */
+  readonly site?: string;
+  readonly outlineBranch?: string;
+  readonly include?: (layer: LayerHeader) => boolean;
+  readonly refreshMs?: number;
+  readonly limits?: { readonly maxObjectMiB?: number; readonly maxJsonMiB?: number; readonly maxStreams?: number };
+  readonly heartbeatMs?: number;
+  readonly log?: (line: Record<string, unknown>) => void;
+  readonly now?: () => number;
+  readonly version?: string;
+  /** Extra runtime configuration written into the page. */
+  readonly page?: Record<string, unknown>;
+};
+```
+
+What the server is built from: its `backends` (read together) and which one takes uploads (`write`), `tokens`, the built `site`, the report's filters (`include`, `outlineBranch`), `limits`, timings, `log`, and `now` for tests.
+
+#### `AtlasServer`
+
+```ts
+export type AtlasServer = {
+  readonly fetch: (request: Request) => Promise<Response>;
+  readonly index: ReportIndex;
+  readonly events: EventHub;
+  /** The routes the server answers, as registered: what the OpenAPI document must describe (a test holds the two together). */
+  readonly routes: readonly { readonly method: string; readonly path: string }[];
+  /** Resolves when the first pass over the backends is done. */
+  readonly ready: Promise<void>;
+  /** Stop refreshing and end every live connection. */
+  close(): void;
+};
+```
+
+A running server application: `fetch` (serve requests), `index` (the live report), `events` (the viewers), `routes` (what it answers), `ready` (the first pass over the backends is done) and `close`.
+
+#### `createAtlasServer`
+
+```ts
+export function createAtlasServer(options: AtlasServerOptions): AtlasServer
+```
+
+The whole of a project's Atlas on one process: the API that results are uploaded to, the live report every
+viewer is shown, and the viewer itself. All of it is under one host, `/api` for the API and `/` for the page.
+What it knows lives in its backends (by default a folder on its own disk), so replacing it loses nothing.
+
+### Authentication and roles
+
+Source: `packages/server/src/auth.ts`
+
+Who is asking, and may they. Tokens have a role (`read` < `publish` < `admin`) and are compared in constant time. Reading
+accepts a Bearer token or the browser's sign-in box (any user name, the token as the password); changing anything needs
+the Bearer header, because a browser sends the sign-in box's credentials to any page that asks, which would let another
+site upload with them. A server with no tokens is open, and refuses to listen beyond this machine unless told it may.
+
+#### `Identity`
+
+```ts
+export type Identity = {
+  readonly name: string;
+  readonly role: ServerRole;
+  /** `bearer` for a token in a header, `basic` for the browser's sign-in box, `none` for a server with no tokens. */
+  readonly via: 'bearer' | 'basic' | 'none';
+};
+```
+
+Who a request is: the token's `name` (never the token), its `role`, and how it was presented (`bearer`, `basic`, or `none` for an open server or an anonymous reader).
+
+#### `Verdict`
+
+```ts
+export type Verdict =
+  | { readonly ok: true; readonly identity: Identity }
+  | { readonly ok: false; readonly status: 401 | 403; readonly message: string };
+```
+
+The answer to "may this request do that": allowed with the identity, or refused with the status to answer (`401` no or unknown token, `403` a known token that may not) and a message that says what to do.
+
+#### `createAuth`
+
+```ts
+export function createAuth(tokens: readonly ResolvedToken[], anonymousRead: boolean)
+```
+
+Who is asking, and may they. A server with no tokens is open (and refuses to listen beyond this machine
+unless told it may). With tokens, every request must carry one, except where `anonymousRead` lets anyone look.
+
+Changing anything needs a token in an `Authorization: Bearer` header, never the browser's sign-in box: the
+browser sends that box's credentials on its own to any page that asks, which would let another site upload
+with them.
+
+#### `Auth`
+
+```ts
+export type Auth = ReturnType<typeof createAuth>;
+```
+
+The authentication of one server: `identify` (who is this), `check` (may they, for a needed role) and `open` (the server has no tokens).
+
+### Server configuration
+
+Source: `packages/server/src/config.ts`
+
+Loads how the server runs: `atlas.server.json`, then environment variables, then flags, each overriding the last, checked
+against `ServerConfigSchema` and resolved (paths made absolute, backends named, tokens read). Every mistake is a
+`ConfigError` that says what to change, and a server that would listen beyond this machine with no tokens refuses to
+start. `SERVER_SETTINGS` documents every setting once; the table in docs/server.md is generated from it and a test proves
+each row.
+
+See docs/server.md#configuration
+
+#### `ResolvedToken`
+
+```ts
+export type ResolvedToken = { readonly name: string; readonly role: ServerRole; readonly token: string };
+```
+
+A token as the server holds it: the `name` it is shown under in logs, its `role`, and the secret `token`.
+
+#### `BackendSpec`
+
+```ts
+export type BackendSpec = { readonly id: string; readonly label: string; readonly url: string };
+```
+
+A backend as configured: its `id`, the `label` people see, and the `url` (a folder, `s3://…`, or another server) to open.
+
+#### `ResolvedServerConfig`
+
+```ts
+export type ResolvedServerConfig = Omit<ServerConfig, 'backends' | 'auth' | 'write'> & {
+  /** The folder that is the default backend, absolute. */
+  readonly data: string;
+  /** Every backend, the data folder first. All are read; uploads go to `writeId`. */
+  readonly backends: readonly BackendSpec[];
+  readonly writeId: string;
+  readonly tokens: readonly ResolvedToken[];
+  readonly anonymousRead: boolean;
+  readonly insecure: boolean;
+  /** Where the config came from, for the first line of the log. */
+  readonly configFile: string | null;
+};
+```
+
+The configuration the server runs with: the file, then the environment, then the flags, checked and resolved.
+
+#### `ConfigError`
+
+```ts
+export class ConfigError extends Error {}
+```
+
+A configuration that cannot be used. The message says what to change; `atlas serve` prints it and exits 2.
+
+#### `SERVER_FLAGS`
+
+```ts
+export const SERVER_FLAGS: readonly string[]
+```
+
+Every flag `atlas serve` accepts, with its `--`.
+
+#### `ServerSetting`
+
+```ts
+export type ServerSetting = {
+  /** What it sets, in words. */
+  readonly summary: string;
+  /** The key in `atlas.server.json` (dotted for nested keys). */
+  readonly key: string;
+  /** The command-line flag, with its value placeholder, or null when there is none. */
+  readonly flag: string | null;
+  /** The environment variables, the first that is set wins; empty when there are none. */
+  readonly env: readonly string[];
+  /** What it is when nothing sets it. */
+  readonly default: string;
+  /**
+   * How the documentation is held to the code: giving `value` through the environment variable (or the flag) must make
+   * `read` of the resolved configuration equal `expected`. A test runs every setting's example both ways.
+   */
+  readonly example: { readonly value: string; readonly read: (config: ResolvedServerConfig) => unknown; readonly expected: unknown };
+};
+```
+
+One setting of the server as an operator meets it: the config key, the flag, the environment variables, and what it does.
+
+#### `SERVER_SETTINGS`
+
+```ts
+export const SERVER_SETTINGS: readonly ServerSetting[]
+```
+
+Every setting that can be given by flag or environment, documented once. `docs/server.md` renders its table from
+this list, and a test proves each row: its example, through the flag and through the environment, changes the
+configuration as the row says. A setting added to the loader without a row here is therefore not documented in the
+table; one documented here that the loader ignores fails the test.
+
+#### `SERVER_USAGE`
+
+```ts
+export const SERVER_USAGE = …
+```
+
+The text `atlas serve --help` prints. Also the source of the `atlas serve` section of `docs/reference/cli.md`.
+
+#### `loadServerConfig`
+
+```ts
+export function loadServerConfig(argv: readonly string[], env: Env, cwd: string, read: (file: string) => string = file => readFileSync(file, 'utf8')): ResolvedServerConfig
+```
+
+Read the file named by `--config`/`ATLAS_CONFIG`, or `atlas.server.json` in the folder if there is one, lay the
+environment and then the flags over it, and check the result. Every problem is a {@link ConfigError} that says
+what to change.
+
+#### `assertSafeToListen`
+
+```ts
+export function assertSafeToListen(config: Pick<ResolvedServerConfig, 'host' | 'tokens' | 'insecure'>): void
+```
+
+A server that anyone on the network can upload to must say who may.
+
+### `atlas dev`
+
+Source: `packages/server/src/dev.ts`
+
+Runs the same server as `atlas serve` on a port of its own, with the viewer's Vite dev server in front of it. Vite proxies
+`/api` (server-sent events included) to the server and writes the same address book into the page, so the browser, the
+uploaders and the viewer all use one host, exactly as in production, and a change to the viewer shows at once.
+
+#### `DEV_USAGE`
+
+```ts
+export const DEV_USAGE = …
+```
+
+The text `atlas dev --help` prints. Also the source of the `atlas dev` section of `docs/reference/cli.md`.
+
+#### `devMain`
+
+```ts
+export async function devMain(argv: readonly string[], io: ServeIo): Promise<number>
+```
+
+`atlas dev`.
+
+### Server-sent events
+
+Source: `packages/server/src/events.ts`
+
+What the server tells every connected viewer the moment it happens. A viewer that misses some (a dropped connection, a
+laptop that slept) loses nothing: events say "something changed", the state is always fetched, and a viewer reads again
+when it reconnects. `EventHub` encodes each event once for all viewers, sends a named `ping` every heartbeat so proxies
+keep the connection and a quiet server is told apart from a dead one, refuses past a maximum number of viewers (they poll
+instead), and lets go of a viewer that has stopped reading rather than hold its backlog.
+
+See docs/server.md#streaming
+
+#### `EventName`
+
+```ts
+export type EventName = 'hello' | 'report' | 'atlas:change';
+```
+
+The events the server publishes: `hello` (sent first to a new viewer), `report` (layers arrived) and `atlas:change` (specs or runs changed). `ping` is the heartbeat, sent by the hub itself.
+
+#### `EventHub`
+
+```ts
+export class EventHub
+```
+
+The viewers connected to `/api/events` and how to reach them all. One hub per server.
+
+- `get count(): number { return this.#subscribers.size; }` — How many viewers are connected right now.
+- `publish(name: EventName, data: unknown): void` — Tell every viewer. `data` is JSON.
+- `stream(request: Request, greeting: () => unknown): Response` — A stream for one viewer, starting with `hello` (what `greeting` returns). It ends when the viewer goes.
+- `close(): void` — End every stream, for shutting down.
+
+### HTTP host for a fetch handler
+
+Source: `packages/server/src/host.ts`
+
+`listen` serves any `(Request) => Promise<Response>` over HTTP: with `Bun.serve` when running on Bun, with a `node:http`
+bridge (streaming bodies in and out, so server-sent events work) everywhere else. The server's behaviour is the same on
+both; `bun run release:smoke` proves it under each. Bodies over `maxBodyBytes` are refused by the runtime before the
+handler sees them.
+
+#### `RunningServer`
+
+```ts
+export type RunningServer = {
+  readonly port: number;
+  readonly url: string;
+  /** Stop accepting, let requests in flight finish for up to `graceMs`, then end what is left. */
+  close(graceMs?: number): Promise<void>;
+};
+```
+
+A server that is listening: the `port` it got (useful when asked for `0`), its `url`, and `close`.
+
+#### `ListenOptions`
+
+```ts
+export type ListenOptions = {
+  readonly port: number;
+  readonly host: string;
+  /** The largest request body to read, in bytes. */
+  readonly maxBodyBytes: number;
+};
+```
+
+Where to listen (`port`, `host`) and the largest request body the runtime will accept.
+
+#### `listen`
+
+```ts
+export async function listen(handler: Handler, options: ListenOptions): Promise<RunningServer>
+```
+
+Serve a fetch handler. On Bun, which is what Atlas is made for, that is `Bun.serve`: one native server for the
+API, the live streams and the page. On Node it is the same handler behind `node:http`, so the package still runs
+where Bun is not installed.
+
+### Server package entry point (`@crvouga/atlas/server`)
+
+Source: `packages/server/src/index.ts`. Import: `@crvouga/atlas/server`
+
+Everything needed to run the Atlas server from code: `createAtlasServer` (a `fetch` handler with the live report, uploads
+and the viewer), `listen` (serve it over HTTP on Bun or Node), `loadServerConfig` (the file, the environment and the flags
+as one checked configuration), `serveMain` (what `atlas serve` runs), `EventHub`, `createAuth`, and the upload checks.
+
+See docs/server.md
+
+### llms.txt of a running server
+
+Source: `packages/server/src/llms.ts`
+
+The plain-text guide ([llms.txt](https://llmstxt.org)) a server serves about itself at `GET /llms.txt`, for an AI
+agent that was handed nothing but the server's address. It is written from this server's own settings (its
+address, whether it needs a token), so what it says is true of the server that says it, and it points at the
+machine-readable description (`/api/openapi.json`) rather than repeating it.
+
+#### `LlmsContext`
+
+```ts
+export type LlmsContext = {
+  /** The address clients use, such as `https://atlas.example.com`, no trailing slash. */
+  readonly url: string;
+  /** True when the server has no tokens: anyone who can reach it may upload. */
+  readonly open: boolean;
+  /** The id of the backend uploads go to. */
+  readonly write: string;
+};
+```
+
+What the guide says about the server that serves it.
+
+#### `llmsTxt`
+
+```ts
+export function llmsTxt(context: LlmsContext): string
+```
+
+The guide for one server, Markdown. Stable in structure: an agent may read it by its headings.
+
+### `atlas serve`
+
+Source: `packages/server/src/main.ts`
+
+Starts the Atlas server from its configuration: opens every backend (creating the data folder), proves the upload
+backend can be written to before listening, finds or builds the viewer, listens at once (so a liveness probe finds the
+process while a large backend is still being read), and stops cleanly on SIGTERM or SIGINT. `serverOptionsOf` is shared
+with `atlas dev`, so the two run the same server.
+
+See docs/server.md#run-it
+
+#### `ServeIo`
+
+```ts
+export type ServeIo = { readonly out: (text: string) => void; readonly env?: Env; readonly cwd?: string; readonly signal?: AbortSignal };
+```
+
+What `serveMain` and `devMain` are given besides arguments: where output goes, and, for tests and embedding, the environment, working directory and an `AbortSignal` that stops the server (otherwise SIGTERM and SIGINT do).
+
+#### `openConfiguredBackends`
+
+```ts
+export function openConfiguredBackends(config: ResolvedServerConfig, env: Env, cwd: string): (BackendInput & { readonly writable: boolean })[]
+```
+
+Open every backend of a configuration. The data folder is made if it is not there.
+
+#### `serverOptionsOf`
+
+```ts
+export function serverOptionsOf(config: ResolvedServerConfig, backends: ReturnType<typeof openConfiguredBackends>, log?: (line: Record<string, unknown>) => void): AtlasServerOptions
+```
+
+What `createAtlasServer` is given for a configuration: `atlas serve` and `atlas dev` run the same server.
+
+#### `serveMain`
+
+```ts
+export async function serveMain(argv: readonly string[], io: ServeIo): Promise<number>
+```
+
+`atlas serve`. Runs until it is told to stop; returns the exit code.
+
+### OpenAPI document of the Atlas server
+
+Source: `packages/server/src/openapi.ts`
+
+The server's HTTP API described as an OpenAPI 3.1 document (JSON Schema 2020-12 inside), generated from the
+operation table below and the Zod schemas of `packages/schema/src/api.ts`. It is served at `GET /api/openapi.json`,
+shipped as `@crvouga/atlas/openapi.json`, and committed as `packages/server/openapi.json` (`bun run docs` rewrites
+it; a test fails when it differs). Any OpenAPI tool can generate a client, a mock or a test suite from it.
+
+The table is held to the code by a test: every route the server registers must have an operation here and every
+operation here must be a route the server registers. Adding a route without describing it fails the build.
+
+Stability: this API only grows within `API_VERSION`: optional parameters, optional response fields, new
+operations and new events. See AGENTS.md ("The server is a living application").
+
+#### `API_VERSION`
+
+```ts
+export const API_VERSION = …
+```
+
+The version of the API described, `major.minor.patch`: the minor grows when an operation or field is added, the major never within `/api`.
+
+#### `Role`
+
+```ts
+export type Role = 'none' | 'read' | 'publish' | 'admin';
+```
+
+Who may call an operation: `none` (anyone), or the least role that may (`read` < `publish` < `admin`).
+
+#### `Operation`
+
+```ts
+export type Operation = {
+  /** The route as Hono registers it, `METHOD /path` (`:name` for a parameter, `*` for the rest of the path). */
+  readonly route: string;
+  /** The same route as OpenAPI writes it, `/path/{name}`. */
+  readonly path: string;
+  readonly operationId: string;
+  readonly tag: string;
+  readonly summary: string;
+  /** What it does and how to use it, written for a client that has read nothing else (Markdown). */
+  readonly description: string;
+  readonly role: Role;
+  readonly parameters?: readonly Param[];
+  readonly body?: Body;
+  readonly responses: Readonly<Record<string, Response>>;
+};
+```
+
+One operation of the API, and the route the server registers for it.
+
+#### `OPERATIONS`
+
+```ts
+export const OPERATIONS: readonly Operation[]
+```
+
+Every operation of the API. The order is the order of the document. The descriptions are the documentation an
+agent reads, so they say what to send, what comes back, and what to do when it does not work.
+
+#### `NOT_OPERATIONS`
+
+```ts
+export const NOT_OPERATIONS: ReadonlyMap<string, string>
+```
+
+Routes the server registers that are not operations of this API, each with the reason. The coverage test skips
+these and only these.
+
+#### `openApiDocument`
+
+```ts
+export function openApiDocument(options: { readonly serverUrl?: string } = {}): Record<string, unknown>
+```
+
+The OpenAPI 3.1 document of the API. `serverUrl` (such as `https://atlas.example.com`) is written into `servers` when given.
+
+### Problem documents
+
+Source: `packages/server/src/problem.ts`
+
+Every error the server answers is an [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) problem document
+(`application/problem+json`): `type`, `title`, `status`, `detail`, and `error`, a copy of `detail` for clients
+written before the standard was adopted. Handlers answer however is natural (`{ error }`); one place,
+{@link asProblem}, makes every error response a problem document, so none can differ.
+
+#### `problemResponse`
+
+```ts
+export function problemResponse(status: number, detail: string, headers: Record<string, string> = {}): Response
+```
+
+A response for a problem, built directly (used where no handler is involved, such as authentication).
+
+#### `asProblem`
+
+```ts
+export async function asProblem(response: Response): Promise<Response>
+```
+
+The response made into a problem document when it is an error (status 400 or more) with a JSON body naming an
+`error`. Headers (`WWW-Authenticate`, `Retry-After`, `Allow`) and any other body fields are kept. Anything else,
+including every success, is returned as it is.
+
+### Finding the viewer
+
+Source: `packages/server/src/site.ts`
+
+Locates the built viewer a server serves: the folder named by `--site`, `./atlas-site`, or one built once into the user's
+cache from the viewer source shipped in the package (`atlas-visualizer build --no-data`). The build is the same for every
+project because the server writes its own address book into the page, so it is built at most once per installed version.
+
+#### `visualizerRoot`
+
+```ts
+export function visualizerRoot(): string | null
+```
+
+Where the viewer's source is, in this repository and in an installed package.
+
+#### `buildSite`
+
+```ts
+export async function buildSite(out: string, log: (text: string) => void): Promise<boolean>
+```
+
+Build the viewer once into a folder, for a server that was not given a prebuilt one.
+
+#### `findSite`
+
+```ts
+export async function findSite(named: string | undefined, cwd: string, log: (text: string) => void): Promise<string | null>
+```
+
+The viewer to serve: the one named, a build beside the project, or one built into the user's cache.
+
+### Store protocol routes
+
+Source: `packages/server/src/store-api.ts`
+
+The `ObjectStore` interface over HTTP at `/api/store`: list keys under `layers/`, read and probe an object, upload one
+(checked by `validateUpload`, immutable once stored) and remove a scratch object. This is what `httpStore` talks to. An
+upload is told to the report only after it is stored, and a layer's manifest, parsed while it was checked, is handed on so
+it is not read again. Everything read is served as untrusted bytes (never sniffed, never run).
+
+See docs/server.md#the-store-protocol
+
+#### `StoreApiOptions`
+
+```ts
+export type StoreApiOptions = {
+  readonly store: ObjectStore;
+  readonly auth: Auth;
+  readonly maxObjectBytes: number;
+  /** Told after something was uploaded: its key, and what kind of thing it is. */
+  readonly onStored: (key: string, kind: string, layer?: ReportLayer) => void | Promise<void>;
+};
+```
+
+What the store routes need: the `store` they read and write, the `auth` that decides who may, the largest object accepted, and `onStored`, told after each upload with its key, its kind and (for a layer catalog entry) the layer already parsed.
+
+#### `readLimited`
+
+```ts
+export async function readLimited(request: Request, limit: number): Promise<Uint8Array>
+```
+
+Read a request body, refusing as soon as it is over the limit rather than after holding it all.
+
+#### `storeApi`
+
+```ts
+export function storeApi(options: StoreApiOptions)
+```
+
+The Hono app of the store protocol, to be mounted at `/api/store`. Reads need role `read`; writes need `publish` through a Bearer token.
+
+### Upload validation
+
+Source: `packages/server/src/validate.ts`
+
+What the server checks before it stores an object, so one bad upload cannot corrupt the report for everyone: the key is
+one Atlas writes (`classify`), a layer's content hashes to its id, blobs and spec files are what their names say, a
+document's files and a catalog entry's document are already there (so nothing half-uploaded is visible), and a run
+passed its privacy scan. Refusals are `Refusal`s carrying the HTTP status to answer. Layers are immutable: the same
+bytes again are fine, other bytes under the same key are not.
+
+See docs/server.md#what-the-server-refuses
+
+#### `Refusal`
+
+```ts
+export class Refusal extends Error
+```
+
+Why an upload was not accepted. The status is what to answer.
+
+#### `UploadKind`
+
+```ts
+export type UploadKind = (typeof KINDS)[number]['kind'];
+```
+
+What a key names: `layer`, `layer-catalog`, `blob`, `spec-body`, `spec-set`, `spec-catalog`, `run-manifest`, `run-catalog`, `run-file` or `scratch` (what `doctor` writes to try the store).
+
+#### `validKey`
+
+```ts
+export function validKey(key: string): boolean
+```
+
+Is this a key a client may name? No traversal, no odd characters, and under `layers/`.
+
+#### `classify`
+
+```ts
+export function classify(key: string): { kind: UploadKind; id: string | null } | null
+```
+
+What kind of object a key names and the id inside it (the layer id, the digest…), or null when it is not a key Atlas writes.
+
+#### `isCatalog`
+
+```ts
+export const isCatalog = …
+```
+
+Catalog entries are what makes something visible, so they are the last thing a client writes.
+
+#### `validateUpload`
+
+```ts
+export async function validateUpload(key: string, bytes: Uint8Array, store: ObjectStore, parsedLayer?: (layer: ReportLayer) => void): Promise<UploadKind>
+```
+
+Check an object before it is stored. What is checked is what would otherwise corrupt the report for everyone:
+a layer whose content is not its name, a catalog entry for something not there yet, a run that failed its
+privacy scan. Everything that is checked is checked cheaply, from the bytes in hand.
+
+#### `sameBytes`
+
+```ts
+export async function sameBytes(store: ObjectStore, key: string, bytes: Uint8Array): Promise<'absent' | 'same' | 'different'>
+```
+
+Is this the same object already? Layers are immutable: the same bytes again is fine, other bytes under the same key is not.