Documentation

The winning precedence layer for a resolved profile source. This travels with the source so inspection never has to reconstruct resolution later.

JSON wire format for okf bundles --json. An empty prefix list means no evidence was observed, so the optional field is absent rather than empty.

The lines okf computations prints, as data. Pure and separate from runComputations so a test can assert the whole report rather than only the accessors behind it; renderProfileDetail is exported for the same reason.

Concepts arrive in walkBundle order and keep it. Column widths are computed over the selected rows only, so one unrelated long concept ID elsewhere in the bundle cannot pad this report.

The lines okf concepts prints, as data: concept ID, type, one column per key requested with --show, and title last. The --show option affects this text report only; JSON output always carries complete stored frontmatter. Pure and separate from runConcepts so a test can assert the whole report rather than only the accessors behind it, as computationReport and renderProfileDetail already are.

The three default columns are the ones conceptCandidates shows in the interactive concept picker, so the two listings agree.

title comes last and is never padded, so a long title cannot push anything off the right edge and a concept with no title simply ends the line. Column widths are computed over the rows actually printed, so one unrelated long concept ID elsewhere in the bundle cannot pad a filtered listing.

The rows okf concepts --json emits.

Each row is the complete stored frontmatter object. File-derived identity, source paths, Markdown bodies, derived readings, and a CLI-owned envelope are deliberately absent. Filters choose the rows before this renderer runs, and --show is not an input because it controls text columns only.

Every profile diagnostic for an okf concepts command line, in a stable order: the legacy filters first — --type, legacy --where equalities, --has, --missing, as they always have been — then each explicit condition in flag order, then each --sort key. A predicate or sort-key error repeated across flags is reported once.

A sort key is checked for declaration only, as has(KEY) would be: there is no value to check. It is worth checking at all because a misspelled sort key leaves the listing in concept-ID order, which looks entirely plausible.

The two kinds render differently on purpose. A legacy equality outside a vocabulary really can match nothing, and its message has always said so. A predicate's out-of-vocabulary value may sit under != or not, where the condition can still match plenty; it is still a typo worth stopping for, but "no concept can match" would be false.

Why a profile says a filter can never select anything.

The message quotes the filter, status=acepted, and not the flag the user typed. --type Reqest desugars into a filter on the type key before any checking happens, so by the time an error exists there is no flag left to quote and guessing one would sometimes name a flag the user did not use.

Why a profile rejects an explicit --where condition. Neutral about matching, since the offending value may be one the condition excludes.

Sorted, duplicate-free strict handle prefixes observed anywhere in the top-level string frontmatter of the supplied concepts.

Decode the plural environment value. Aeson decodes directly to [Text], so a non-array or non-string member is rejected rather than coerced. Blank elements are discarded and exact duplicates keep their first occurrence.

Plural environment override. JSON is used because registry references may themselves contain colons in URLs and integrity hashes.

Legacy singular environment override for the registry okf profile reads.

JSON wire format for one discovered descriptor. Optional prose is omitted rather than rendered as null, matching the bundle-listing convention.

Resolve the winning registry layer and append network-silent local descriptors unless the caller explicitly requested registry-only behavior.

Resolve a descriptor with an already-detected picker configuration. This is exported so tests can prove the explicit branch ignores availability.

Profile source precedence: repeated --registry flags, then the plural JSON environment value, then the legacy singular environment value, then the effective configuration. Only the winning layer contributes sources. Configuration is read only when needed, so a broken file cannot stop an explicit invocation.

One profile's complete rule set. Every optional field prints as (none) rather than being omitted, so the output shape does not change between profiles and stays reliable to eyeball or grep. Type rules print in the order the profile declares them, since that order is the author's.

One deviation as one line. The ProfileSpec is here only so a missing required field can carry the profile's own explanation of what that field is for; every other case ignores it.

Exported so a test can assert a whole diagnostic line rather than only the accessors behind it, as computationReport and renderProfileDetail already are. The constructors that quote a frontmatter value back to the author ignore both the CompiledProfile and the concept list, so such a test can pass any compiled profile and an empty list.

A deterministic two-line row per profile. Compact mode uses fixed column budgets whose separators sum to 100 Unicode code points, then caps the indented description to 98. Wide mode derives widths from the full identity values and keeps the complete normalized description. Unicode code points are intentionally used instead of terminal display cells so rendering stays pure and terminal-independent; combining and double-width glyphs may not visually occupy exactly one cell.

The source inspection table and its precedence legend are pure so the command can be pinned without evaluating Dhall or consulting the network.

Resolve one profile from a complete, successfully loaded source set. The pure result keeps ambiguity behavior directly testable; command policy turns the Left into exit status 1.