Problems

A problem is a title and a Markdown description; everything else in the Lab belongs to one.

A problem is what is being worked out. It has:

a title;
a description, written in Markdown with GitHub-style tables, task lists and strikethrough. The editor has Write and Preview tabs;
a workbook with its commits;
a dashboard;
any number of artifacts.

Writing a good description

There are no required fields beyond the title. Sections that help readers, and that the outline offers, are:

What the problem is, who has it, and which decision it serves.

## Hypothesis

What you expect the data to show, written before you look.

## What this does not claim

Limits a reader must know, such as what a measure stands in for.

HTML in a description is shown as text, never rendered.

Ownership and access

Who	Sees	Changes
A customer’s editors and admins	their organisation’s problems and Ridgital’s templates	their organisation’s problems
A customer’s viewers	the same	nothing
Ridgital staff	every problem	Ridgital’s own problems (with ARMID write permission)

A problem you can read but not change can be copied with Copy to my problems. Ridgital may offer some of its problems to every customer as templates to start from.

There is no limit on the number of problems.