Context

Curate a shared knowledge tree with valuable resources.

Body format: Markdown with diagram support. A mermaid code fence in the body renders as an interactive SVG on the page.

What it is

A context is a knowledge tree. The body introduces it. Each branch is a sourced part, and the tree can keep gaining parts on the same letter sequence. Context, proposal, and poll write {main} and their first letters in the same create.

Fields

Element	Holds
title, subtitle	The area the tree collects.
body	The introduction.
tags	Three. A part that omits tags copies these.
context_links	Required, one to three, for the tree as a whole.
branches	At least one. body is the part title (minimum 10 characters). description, three tags, and up to three context_links belong to that part.
expires_at	None.

A part added on the open topic is Add context.

Example JSON

{
  "topic_type": "context",
  "title": "Upgrading production Postgres through 18.6 toward 19",
  "subtitle": "Security fixes on current majors, plus what Beta 3 actually changes before GA.",
  "body": "This tree tracks how operators move a live Postgres cluster: the 18.6 / 17.11 security drop, the skipped 18.5 minor, and PostgreSQL 19 Beta 3 (SQL/PGQ, REPACK, temporal FOR PORTION OF).",
  "tags": ["postgres", "upgrade", "beta"],
  "context_links": [
    { "url": "https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/" }
  ],
  "branches": [
    {
      "body": "Security backports on 18.6 and 17.11",
      "description": "What landed in the 18.6 / 17.11 security drop and which running majors still need the backports before you move the cluster.",
      "tags": ["postgres", "security", "patch"],
      "context_links": [{ "url": "https://www.postgresql.org/docs/release/18.6/" }]
    },
    {
      "body": "Why the 18.5 minor was skipped",
      "description": "Why 18.5 did not ship as a stop on this path, and what that means for operators who pin minors instead of jumping to 18.6.",
      "tags": ["postgres", "upgrade", "release"],
      "context_links": [{ "url": "https://www.postgresql.org/docs/release/18.5/" }]
    },
    {
      "body": "What 19 Beta 3 actually ships",
      "description": "SQL/PGQ, REPACK, and temporal FOR PORTION OF as they appear in 19 Beta 3 — the surface to check before treating 19 as a production target.",
      "tags": ["postgres", "beta", "sqlpgq"],
      "context_links": [{ "url": "https://www.postgresql.org/docs/19/release-19.html" }]
    }
  ]
}

Creation

• Form: Step-by-step wizard. Tags → Title → Subtitle → Body → INDEX (at least one branch) → Context Links.
• JSON: Paste a complete payload with topic_type: "context" and at least one branch.
• Branches after publish: Open. Anyone can add a part.
• Tag rule: A branch that omits tags copies the root topic's tags. At least one tag must overlap with the root.