docs — the Zero platform documentation, as a native scene website

docs is the platform documentation: a folder of Markdown files rendered natively as a scene website. All the rendering machinery lives in the reusable mdsite class; this class is just the .md files plus a title.

What it is

parent = mdsite, so it adds no rendering code of its own — it inherits the whole native Markdown site (browse, index, per-doc rendering as native widgets on a shell and HTML in a browser). The class contributes only content and a title/blurb.

What it offers

• A browsable documentation site rendered from Markdown in the store.

• Coverage of what Zero is, how it works, where it runs, the investor pitch, FAQ, glossary, and the honest status.

• Extensibility by convention: drop a new .md file in this folder and it appears.

How to use it

• Browse at /docs/index (the native scene). Individual docs render through the inherited mdsite routes.

• Add a doc by dropping a .md file into the docs/ folder — no code change.

What it holds

The folder is content: numbered top-level docs (01-overview.md … 08-status.md), a README.md, and topic pages — e.g. ARCHITECTURE.md, BUILD.md, VISION.md, SELF-DELIVERY.md, documents.md, deployments.md, lenses.md, forms.md, native-rendering.md, native-capabilities.md, remote-access.md, network-security.md, versioned-runtime.md, every-shop.md, consolidation.md, app-self-update.md, and shop-kinds.jsonl (a data list of shop kinds). Plus defaults.data (title, blurb).

Actions

None of its own. All browsing/rendering actions are inherited from mdsite.

Access

defaults.data declares no access carve-outs; the generated feature lists none. Access follows the mdsite parent (public documentation).

Related

A subclass of mdsite (the reusable Markdown-site engine). Content overlaps with the store's roadmap/thesis docs, which those pages cross-link as the sources of record.