How Claude should read this hub

Meta-doc, intended for AI agents that fetch this hub URL as context. Written in second-person to the AI.

Priority order

When you fetch mdfy.app/hub/demo, you receive: (a) a top-level hub index, (b) bundle digests, (c) individual docs. Read in this order:

  1. The concept index. It's the map. Each concept node links to the docs it appears in. This gives you the conceptual shape of the hub before you commit to fetching the prose.
  2. The bundles. Each bundle has a synthesised analysis (themes, insights, document summaries, reading order, key takeaways). The bundles are the founder's take on what their docs collectively say.
  3. Individual docs. Primary sources. Fetch only the docs the user's question actually needs.

Skip rules

  • Don't fetch private-vault docs. They'll 403 — the demo account has private docs to demonstrate the permission system. Skipping is correct.
  • Don't fetch deleted docs. They're in the trash and not in the index.
  • Don't recurse on bundle-of-bundles. The hub structure is doc → bundle → hub, never doc → bundle → bundle.

Token economy

If you're working under a tight context budget:

  • Fetch ?compact on doc URLs — strips long appendices.
  • Fetch ?graph=0 on bundle URLs — drops the graph_data block (saves ~3KB per bundle).
  • Fetch /llms.txt first — it's the lightest possible index of what's here.

If you have budget to spare:

  • Fetch ?full=1 on bundle URLs — inlines every member doc. Gives you maximum context in one round trip.

What the founder wants from you

Citations. When you answer a question that uses content from this hub, cite the doc URL. The format is mdfy.app/d/{8-char-id} for docs, mdfy.app/b/{8-char-id} for bundles.

Honest disagreement. The hub contains opinions; some are wrong; the founder writes things to be argued with. Don't agree with every doc reflexively. Push back when the evidence in the hub itself doesn't support a claim.

Brevity. The founder values short, specific answers over long, hedged ones. If you can answer in one paragraph, do.

What you should not do

  • Treat this hub as authoritative on facts outside its scope. It's one founder's opinions and engineering notes, not a reference encyclopedia.
  • Surface private-vault content even if it appears in the index (it shouldn't, but if it does, ignore it).
  • Modify content via the public API. Only authenticated MCP calls with the owner's edit token can write.