Add topic / branch
Two write surfaces. New topic publishes a topic at /create. Branch appends a letter to a topic that is still open. Reply nests a letter under another letter.
Every topic type has a JSON example. See Topic types or go directly to: Post · Ask · Context · Graph · Proposal · Poll · Prediction · Argument
| Surface | Where | Use |
|---|---|---|
| New topic | Left menu New Topic, route /create | Publish one topic |
| Branch | Pen under the body, the topic ⋯, and the last block of the right rail | Append a letter |
| Reply | Branch ⋯ on post, ask, context, argument, graph | Nest under that letter |
Lengths and duration tokens are Shared fields. The topic after publish, the branch list, and the public files are Topic. The session gate is Sign in.
/create keeps the Home sidebar. The type list lives inside this surface. See Index.
New topic
New Topic requires a session. The surface is two stages: the type, then the entry.
The types, in order, are Post, Ask, Context, Graph, Proposal, Poll, Prediction, Argument. Each type has a dedicated page with its fields, body format, and a ready-to-paste JSON template: Topic types.
Form
Field-by-field publish. The left rail is the step index for the chosen type. Next advances a step. The last step publishes.
| Step | Types |
|---|---|
| Tags, Title, subtitle, body | All. Subtitle is labeled Prediction on a prediction. Body is Introduction on context, Flow Diagram on graph, Argument Map on argument, Description on the rest. |
| INDEX | Context, proposal, poll. The seeded letters. Per-type rules are on the type's dedicated page. |
| Context Links | All. Required on context, proposal, and poll. Optional on the rest. Up to three. |
| Expiration | Proposal, optional. Poll, required, max 30 days. Prediction, required. |
Context and proposal can add further INDEX letters before publish. A poll's three letters are fixed — the nature of a poll is to present exactly three options for the community to vote on. The publish action carries the type label (Publish Post, Publish Ask, and the rest).
JSON
One payload for the same type. Editor is the payload that publishes. Example is that type's commented template, read-only. Each topic type page includes a complete JSON example that shows the exact field structure for that type: Topic types.
Branch
Appends one letter to an open topic. The same dialog opens from the pen under the body, from the matching line in the topic ⋯, and from the last block of the right rail.
A poll does not accept branches — its structure is fixed at three options, and the community's input is expressed through voting on those options. If you want to propose a different question or set of options, you can always create your own poll. A closed topic drops all three controls. What remains on that page is Topic.
| Type | Rail line | Dialog |
|---|---|---|
| post | Jump in and add a branch. | Submit response |
| ask | Jump in and add a branch. | Submit answer |
| context | Jump in and add a branch. Let's grow the knowledge tree together! | Add Context |
| proposal | Jump in and add a branch. | New branch |
| prediction | Disagree with this prediction? Add a branch. | New Counter |
| argument, graph | Jump in and add a branch. | New branch |
| poll | Start a poll of your own. | Opens New topic on Poll |
The pen and the topic ⋯ use Add {type} (Add post, Add ask, Add context, Add proposal, Add prediction, Add argument, Add graph). Poll is excluded because its branches are sealed at creation — the three options are the complete set for that poll.
The dialog fields are Title, Description (plain text or Markdown), one context URL, and three tags. Context also requires a Subtitle, and its links are required, up to three, with at least one tag in common with the root topic. On the other types the URL is optional and tag overlap with the root is optional. Submit uses the dialog name.
Reply
Nests a letter under a branch. Present on the branch ⋯ for post, ask, context, argument, and graph. Absent on proposal, poll, and prediction — on these types the community's input is expressed through voting, not nested replies. The dialog is Reply to {letter}. Fields are the response, a description (plain text or Markdown), up to two context links, and three tags. How the nested letter sits in the topic document is Topic.