Waymark · Spatial · Model 01 / 03

Waymark

Sketch-to-layout language model for viewer-relative scene answers

Give it a written sketch of a photo and ask where something is; it answers in one short sentence.

For apps that describe a scene to someone who cannot see it, or need to check what is where.

Released 1.1.0 since 2026-09-20: one model for street and indoor scenes Default Spatial v1.1.0

Waymark reads a text sketch of a scene and answers one layout question — left or right, closer or farther, in front or behind — in one short sentence.

Overview #

Waymark answers questions about where things are in a photographed scene. You give it a written sketch of the scene — the list of objects and where they sit, which a vision model produces from the image — and one question; it gives back a single short sentence in everyday words such as left, right, closer or behind. Use it when you need a quick layout answer rather than a route.

Waymark is a 124M-parameter decoder-only language model that answers layout questions about a scene it has never seen. It reads a structured text sketch — the kind of scene, where the viewer stands, a list of objects with viewer-relative positions, pairwise relations and anything uncertain — together with one short question, and returns a single sentence: what is on the left or right, what is closer or farther, what is in front of or behind what, and what is blocking what.

The input is text and the output is text. A vision model that emits the Falcon scene sketch does the seeing; Waymark does the reasoning about the sketch and keeps to its vocabulary of relative positions. It never reports metres, GPS coordinates or compass bearings, and it does not invent objects, doors or paths that the sketch does not mention. Answers are sampled from the model at a low temperature, so they are short, plain and slightly variable from call to call.

Since version 1.1.0 (2026-09-20) Waymark is one model for street and indoor scenes — homes, offices, schools, shops, restaurants, hotels, station concourses and garages as well as streets, paths and plazas. It was reached through an intermediate indoor finetune (published for one day as “Waymark Indoor”, now withdrawn) and then retrained on a balanced mix of street and indoor sketches; the request value "model": "waymark-indoor" still works on /v1/spatial as an alias for these weights.

Waymark is the default model of the Waymark series. Its sibling, Waymark Extra, reads the same sketch grammar and keeps Waymark's layout question-and-answer task, but adds movement: given a sketch and a goal it emits a timed, viewer-relative trace of a person moving through the scene. Waymark Extra is a larger model — 355M parameters with a 1,024-token window, trained from scratch — and the Falcon API binds it to /v1/move; Waymark is the model behind /v1/spatial.

Intended use #

  • Answering “which side”, “what is closer”, “what is in front” and “is my view blocked” questions over a sketch produced by a vision model from a street-level scene.
  • Turning a sketch of sidewalks, roadways, crossings, plants, stairs, ramps and overpasses into a one-line layout read that a responder can fold into a longer reply.
  • Acting as the fallback answer when a larger responder cannot finish, since the sketch is already grounded and the answer is short.

Out of scope #

  • Reading pixels: Waymark only ever sees the text sketch.
  • Anything metric — distances in metres, heights, headings, sizes in real units.
  • Documents, maps, receipts and other non-scene material; sketches of kind document are rejected before they reach the model.
  • Navigation, accessibility or safety decisions, such as when to cross a road.

Choose Waymark when #

  • The sketch is a plain street-level scene with objects, relations and a viewer line, and you want the smallest model that answers in the trained vocabulary.
  • You need a layout answer in about a second, rather than a multi-second trace.
  • You need a movement trace rather than a layout sentence — a goal such as “walk to the doorway” turned into timed, viewer-relative steps — or your sketches are long or busy, with a second person, two-leg routes or prompts past 512 tokens: choose Waymark Extra instead, with its 24 layers and 1,024-token window, on /v1/move.

Specification #

Parameters123,999,744
KindDecoder-only language model (GPT-style)
Layers12 pre-LayerNorm transformer blocks
Attention12 causal self-attention heads, head dimension 64
Width768 (MLP hidden 3,072, GELU)
Context512 tokens (learned absolute position embeddings)
Vocabulary50,304 (GPT-2 BPE, padded); output head tied to the token embedding
BiasesNone on linear layers; LayerNorm keeps its affine bias
Checkpointmodel.pt, 496.0 MB, float32 PyTorch checkpoint with a JSON sidecar
DecodingTop-k 40; temperature 0.3 on the Falcon API route (greedy at or below 0.25); at most 96 new tokens
Training1.1.0: 1,500 steps from an indoor finetune of 1.0.0, loss on answer tokens only, 45 % street rows
Training platformVertex AI, 1× NVIDIA L4 (1.0.0) and 1× NVIDIA A100 (1.1.0)

Try it #

You send
A sketch with a doorway and a retaining wall, and the question “what’s in front”.
You get back
One sentence: the doorway is on your right, in the foreground.

The same exchange as the API sees it:

json
{
  "sketch": "kind: scene\nviewer: eye-level on sidewalk\nobjects: doorway (right foreground); retaining wall (center background)\nrelations: doorway in front of retaining wall; doorway right of center; retaining wall behind doorway\nrelative: doorway closer than retaining wall",
  "question": "what's in front"
}
json
{
  "ok": true,
  "engine": "waymark",
  "model": "waymark",
  "text": "doorway on your right foreground.",
  "from": "sketch"
}

Limits & safety #

It does not see the image; it reads the sketch. Everything Waymark can say about a scene is bounded by what the sketching model wrote down, and anything the sketch omits or gets wrong, Waymark inherits.

  • No true distances or sizes: answers are relative — closer, farther, in front, behind — never metres, GPS coordinates or compass bearings. Estimates, never measurements.
  • No pixels and no capture details: Waymark's training rows contain no capture, colour, size or ground attributes, so questions about shot type, colour, size or height off the ground are not backed by its training data even when the sketch carries those fields.
  • Narrow vocabulary: 45 street-level object names, 10 viewer phrases and 32 question templates. Document, map or unknown sketch kinds, and objects outside the vocabulary, are out of distribution and can draw generic or wrong sentences.
  • No guarantee against invention: the model was trained not to name objects, doors or paths absent from the sketch, but this is a property of the data, not a checked constraint on the output. On busy hospital sketches of eight to twelve objects, version 1.1.0 still substitutes a familiar name for an unfamiliar one in about four answers in ten.
  • No confidence score: the answer is a single sample at temperature 0.3, so repeated calls can differ in wording and occasionally in substance.
  • Context of 512 tokens: a prompt longer than 511 tokens is truncated from the front, silently dropping the sketch header and earliest lines.
  • Not a navigation, accessibility or safety aid, and not a substitute for looking: it must not be used to decide when to cross a road or whether a passage is clear.
Spatial Released

Give it a sketch of a scene and a goal like “walk to the door”, and it describes the walk step by step.

Movement traces from a scene sketch and a goal, with a plain-words summary

v1.0.0
Intention Released

The more careful version of the movement reader: it looks at every object and every step before it answers.

Attention over every object and every step of an observed motion

v1.0.0

Latest versions #

VersionDateStatusNote
1.1.0ReleasedRetrained on a balanced street-and-indoor mix, via an indoor finetune of 1.0.0 (answer-only loss, 1,500 steps, 1× A100). Same contract; one model now covers street and indoor scenes.
1.0.0ReleasedFirst documented version. Served weights are the step-250 checkpoint (validation loss 0.1505); a refine run warm-started from it completed on 2026-09-09.

Read the full documentation

Nine chapters: architecture, inputs and outputs, training, evaluation, API, runtime, limits and versions.

Full documentation