Publish a decision page

Give a decision a public page anyone with the link can read, and take it down again.

A published decision has a page on eevo.io that opens without signing in: the context, the options with their consequences, the stakeholders and the result, laid out as the console shows them, with a link preview for X, Slack and the like. Nothing that names your organization is on it: no metadata (the page is named after the context's first sentence, not the issue's title), key, person, usage or cost. Search engines may index the page.

Publish

Publish the decision by its id, with the key it was made with:

curl https://eevo.io/api/v1/decisions/dec_…/publication \
  -H "Authorization: Bearer $EEVO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

The answer is the decision record with its publication: url is the page, which you can post anywhere. In the console, the same switch is on the decision's panel in the log, for the person who made it (or created its key).

Only a finished decision with its result stored can be published: a request under retention "Not stored", or whose retention period has ended, has nothing to show (400). Publishing a published decision changes nothing.

What a published decision keeps

While a decision is published its request and result are kept past the key's retention, so the page does not go blank. The rest follows the retention as before: the metadata, the chosen-decision note, revision notes and assessment details are deleted on schedule, since the page does not show them. Taking the page down puts the request and result back under the retention: if it has already ended, they are deleted at the next daily sweep.

Take the page down

DELETE the same address with the same key, or turn the switch off in the console. The link stops working for good: publishing again gives a new one.

curl -X DELETE https://eevo.io/api/v1/decisions/dec_…/publication \\
  -H "Authorization: Bearer $EEVO_API_KEY"

What the page shows

The page is the decision as the request framed it, so write the context and the options with a reader in mind: the page quotes them as they are. Stakeholders are shown by their descriptions; see Write good stakeholders and consequences.