"MarkRight" brand for sale
Markdown is not the right primitive for the LLM era. It isn't streaming-stable, unsemantic, and error-prone. It also lacks first-class syntax for things like
- citations
- tool calls
- reasoning blocks
- addressable spans
- document relationships
The format won only by inertia. Thus, successors are being drafted in public.
- IBM Research published LLMON, a formal LLM-native markup spec, in March 2026.
- Hacker News is debating it openly: “Ask HN: What Comes After Markdown?” and “Markdown Is a Disaster: Why and What to Do Instead” both ran active threads with developers arguing the format is too underspecified to carry serious LLM workflows.
- Stammy's “markdown 2.0” thread and kepano's reply crystallized the debate publicly in April 2026.
The trend is clear. A "TypeScript" for LLMs: a superset of markdown that adds what LLMs need: stable identifiers, semantic types, sidecar metadata, streaming-stable rendering. Whoever standarizes it will basically win the license wars, and own the next .docx.
But you'll need a banger name for that. We're selling MarkRight.
What we're selling
We hold the full asset bundle and the underlying rights of prior use:
- github.com/markright (organization)
- @markright on npm (organization)
- markright.dev
- markright.app
- Underlying rights of prior use on the MarkRight name
Why we're selling, not building
We built some examples, but then other priorities took over. Sitting on a name during the moment it is most relevant feels worse than handing it to someone who will actually lead.
If you are building in this space, agent-native markup, addressable blocks, sidecar metadata, streaming-stable rendering, and you want a name that does the work for you on first impression, the bundle is yours.
One more time, because the wordplay is half the pitch
Markup. Markdown. MarkRight.
It is right there.
Talk to us
Reach out at monster@forsale.monster. Serious inquiries only. We will share diligence materials on request.