How it works
What circulates, evolves. What is hoarded, decays.
Lorediv runs on a few simple mechanics that compound: publish, vote, rank, close. Everything else is structure.
The lifecycle
A topic starts in New. All open topics appear on Home — ordered by relevance score, then newer first. Topics with a score of 0 or negative still appear on Home. If a topic hits 100 votes within 48 hours, the author gets a hot bonus of 130 energy. Topics with an expiration date (polls, proposals, predictions) eventually close — frozen, still readable, no more votes. Topics without expiration stay open until the author deletes them.
flowchart TD
NEW["New<br/>newest first"] --> OPEN["Open topic"]
OPEN --> HOME["Home<br/>score then newer"]
HOME -->|"hot for a while"| TREND["Trending"]
OPEN -->|"window ends"| CLOSED["Closed<br/>frozen, readable"]
HOME -->|"window ends"| CLOSED
TREND --> CLOSED
Closed is not delete. The work stays on the tree. It just stops accepting votes and branches.
The relevance vote
One relevance vote. Three weights: ±1, ±3, and ±10. Your lore rank caps how heavy your vote can be — a Newbie can cast ±1, a Geek ±3, a Wizard or GOAT ±10. Casting spends energy from your monthly pool. Receiving votes earns energy back and moves your rank.
The relevance vote works on topics and on individual branches. On polls and proposals, options accept only +1 — one choice per user. On asks, the rank cap applies and a user can vote on multiple answers.
Details: Cast.
Energy
Every user gets a monthly pool of 31 energy. Casting a heavier vote costs more. Receiving a vote on your content earns +1 energy back. At 100 community votes within 48 hours, the author gets +130 (hot bonus). The pool resets each month. Unused energy does not carry over.
Details: Energy.
Rank
Your rank is written {tier} {score} — like Wizard 6.1. It moves with every vote your content receives. The four tiers are:
| Tier | Score | Meaning |
|---|---|---|
| Newbie | 1.0 – 3.1 | Starting out |
| Geek | 3.2 – 5.4 | Supporting voice |
| Wizard | 5.5 – 7.6 | Confirmed authority |
| GOAT | 7.7 – 9.9 | Primary source |
Your rank determines your max vote weight and how agents weight your content in search results.
Details: Rank.
Divs
Each topic carries three tags. Your top tags — weighted by community support — become your divs: the domains where the community recognizes your expertise. On your profile, divs show as up to ten earned tags split 6:3:1 by weight. They are not a profile field you write. They come from your work.
Agents
Every public page has a .md and .json twin. The agent entry point is /llms.txt — a flat map of every address. From there, /skill.md describes the read procedure. No API key. No session. One tree, two ways to read.
Details: Agents.
The rails
The system follows rules borrowed from thermodynamics:
- Entropy — topics without support stay on Home but score low. Trending captures the top 100 by score on a 15-day window.
- Conservation — energy is finite. The monthly pool enforces scarcity. Votes you receive add energy; votes you cast spend it.
- Activation energy — writing requires a session and rate limits. Random noise does not get through.
- Equilibrium — the monthly reset prevents energy hoarding. What circulates stays active.
The full treatment is in The system.
What to read next
- Quick start — your first five actions
- Knowledge tree — the philosophy
- Feed — where the tree breathes