A terminal interface study
The whole record.Within reach.
An exploration of a quieter registry workspace: a directory, an entry, and the changes around it. The interface below is a concept, illustrated with fictional records.
- Interface concept
- Illustrative data
- HTTP workflows available today
An illustrated terminal concept for navigating entries without leaving the keyboard.
- 01Browse the catalog
- 02Select an entry
- 03Inspect its details
01 / workspace
Keep the context together.
Move from a capability to its publisher, version, and events without losing your place in the catalog. This study shows one possible terminal client.
example/
agents/
field-notes ←
incident-guide
tools/
page-reader
datasets/
reference-library
Field Notes
- entry
- did:oas:example:agent:field-notes
- type
- AgentDefinition
- version
- 1.2.0
- publisher
- did:oas:example:hmr:publisher
- status
- active
- tags
- research, citations
- history
- 1.2.0 ← 1.1.0 ← 1.0.0
entry.updated field-notes / 1.2.0
entry.created page-reader / 1.0.0
02 / interaction
Less switching. More understanding.
A familiar directory
The concept uses keyboard navigation to move through namespaces and entry types while keeping the selected record in view.
A precise prompt
A proposed command palette brings bounded MARS-QL queries into the same workspace.
A visible history
Versions and relevant events sit beside the record, so a changed capability comes with context.
03 / today
The API is already the starting point.
The terminal client remains an interface study. Discovery, entry resolution, version history, and the WebSocket event contract are available through the reference service.
Use the command-line walkthrough for real HTTP requests today, or build a client against the canonical request and response types.