Skip to content
ArtlessDev Docs

Home

Scenarios are behavioral facts, authored directly in the app — not tickets, not markdown, not ornate PRDs.
Getting StartedWhat is a Scenario?

Less art, more evidence

Section titled “Less art, more evidence”

ArtlessDev’s core object is the Scenario: a durable, evidence-grounded behavioral fact about a piece of software. Teams author Scenarios directly in the app as structured entities, and track two independent overlays on top of them — lifecycle (Draft, Published, Deprecated) and verification (Not attempted, Fit, Gap).

Scenarios

Every Scenario declares an explicit boundary: one ordered path of Conditions and Results, each backed by concrete evidence. Read Scenarios.

Status

Lifecycle and verification are two independent overlays — never confused with the Scenario’s content itself. Read Scenario Status.

Relationships

Scenarios nest, chain, and share cross-cutting concerns along three independent axes. Read Scenario Relationships.

MCP and the API

Agents, CI and scripts reach Scenarios with a project-scoped API key — over MCP or the REST API.