Show baseline

Elements of a baseline with their version then and its date, marked changed, superseded, removed or added since (SR-051); with withEvidence the verification status of each requirement per view and the validation status at its version in the baseline, with the records dated after it named (SR-094).

Command baseline.get. Reads the workspace and changes no file.

Input

Field	Type	Required	Description
baseline	string	yes	Name of a baseline, or its file name (with or without .yaml).
withEvidence	boolean	no	Also give, at each entry’s version in the baseline, the verification status of each requirement in every view it applies in (only the variant’s when the stored selection has one) and the validation status: own records up to the baseline’s date and time, records of that version dated after it named apart (SR-094). Like the rest of the output it reads the evidence files on disk, so each repository should be checked out at the commit the baseline names; a baseline.repository-commit-differs warning names each one that is not. Default: false.
limit	integer	no	Elements of the page; total counts all. Default: 200.
offset	integer	no	Default: 0.

Output

Field	Type	Required	Description
name	string	yes
file	string	yes	Relative to the workspace root, / as separator.
repository	string	yes	The repository that holds the file.
date	dateTime	yes	A date and time with time zone (RFC 3339 date-time), for example 2026-10-26T09:30:00Z.
view	viewId	no	The view of the stored selection; left out for the core.
selectionKnown	boolean	yes	The file stores a selection. Without it no element is added or removed (SR-051 AK2/AK3).
repositories	array of object	yes
repositories[].name	string	yes
repositories[].commit	commit	yes	Full Git object ID (SHA-1 or SHA-256).
elements	array of object	yes	One page: the file’s entries in file order, then the added elements in store order. State precedence: missing, superseded, removed, changed, unchanged; added only for elements not in the file.
elements[].id	uuid	yes	Element ID: random UUID version 4, lower case, never changes (D-017, SR-002).
elements[].repository	string	no	The repository of the copy, whenever it is known.
elements[].state	one of "unchanged", "changed", "superseded", "removed", "added", "missing"	yes	missing: not in the store, or in a repository that is not here (incomplete). removed: not superseded and no longer in the stored selection (SR-051 AK3). added: in the stored selection and not in the file.
elements[].version	version	no	The version in the baseline; left out for added.
elements[].versionDate	string or null	no	Date of that version from the Git history (ADR-0005), read for the page only; null when unknown.
elements[].current	version	no	The current version when it differs, also for removed and added.
elements[].verification	array of object	no	With withEvidence, for entries of the file (not added or missing) whose type has the meaning requirement: one row per view it applies in now, the core first, then the variants in store order (SR-094 AK4, SR-047 AK3); with a variant in the stored selection only that variant’s row (AK5). Empty when it applies in no view shown. Own records only, never indirect (AK6). Left out when the stored view cannot be resolved.
elements[].verification[].view	viewId	yes	A view as the tool writes it in outputs: core or the canonical UUID or short ID of a variant (SR-043).
elements[].verification[].status	one of "open", "verified", "failed", "outdated"	yes	From the records of the view that count for the baseline: dated at or before it (AK2); outdated with records of other versions only, open without (AK3).
elements[].verification[].later	array of evidenceRecord	no	The records of the baseline version in this view dated after the baseline, newest first: they do not count (AK2). Left out when there is none.
elements[].validation	validationStatus	no	With withEvidence, for entries of the file (not added or missing) of a type with the meaning need and for any other with a validation record (SR-038, SR-094 AK7): the status at the baseline version from the validation records that count for the baseline, without view. Open without such records.
elements[].validationLater	array of evidenceRecord	no	With validation: the validation records of the baseline version dated after the baseline, newest first; they do not count (AK2). Left out when there is none.
counts	object	yes	Elements per state over all pages.
counts.unchanged	integer	yes
counts.changed	integer	yes
counts.superseded	integer	yes
counts.removed	integer	yes
counts.added	integer	yes
counts.missing	integer	yes
total	integer	yes	Entries of the file plus added elements.
names	array of elementName	yes	The elements of the page, the variant of view and the variants the verification rows name, each once in the order first named (#588).
problems	array of problem	no
incomplete	incomplete	no	True when a result is incomplete because targets are in repositories that are not available locally (SR-006 AK2, SR-036 AK3).

App

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Show baseline.

CLI

reqseq baseline get, with --json for the output as JSON. Its help:

Usage: reqseq baseline get <baseline> [options]

Elements of a baseline with their version then and its date, marked changed,
superseded, removed or added since (SR-051); with withEvidence the verification
status of each requirement per view and the validation status at its version in
the baseline, with the records dated after it named (SR-094).

Arguments:
  baseline                Name of a baseline, or its file name (with or without
                          .yaml).

Options:
  --baseline <value>      instead of the argument <baseline>
  --with-evidence         Also give, at each entry's version in the baseline,
                          the verification status of each requirement in every
                          view it applies in (only the variant's when the stored
                          selection has one) and the validation status: own
                          records up to the baseline's date and time, records of
                          that version dated after it named apart (SR-094). Like
                          the rest of the output it reads the evidence files on
                          disk, so each repository should be checked out at the
                          commit the baseline names; a
                          `baseline.repository-commit-differs` warning names
                          each one that is not. default: false
  --no-with-evidence      set with-evidence to false
  --limit <number>        Elements of the page; total counts all. default: 200
  --offset <number>       default: 0
  --input <json|@file|->  command input as JSON: inline, from a file, or from
                          standard input
  --workspace <path>      workspace root (default: nearest folder upwards with
                          reqseq-workspace.yaml)
  --json                  print exactly the command output as JSON
  --yaml                  print the whole command output as YAML, problems one
                          per line
  -h, --help              show help

API

POST /v1/commands/baseline.get on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

MCP

Tool baseline_get of the MCP server (reqseq mcp), with the input as its arguments.