Monolythium/Build/Guides & tutorials

Guides & tutorials.

Public guidance with explicit availability labels. The operator and indexer pages are release-readiness checklists, not currently executable tutorials; SDK work should remain local while the development RPC is stale.

· Conventions

How guides are written.

01

Outcome → steps → verify.

Every guide opens with a single-sentence outcome, lists the numbered steps, and ends with a copy-paste-able verification command. No filler.

02

Public source, public history.

Guides live in the docs repository. Open a PR with a typo fix, an additional verification step, or a new platform — first-time contributors are welcome.

03

Availability is part of verification.

A guide that depends on an unreleased artifact, inactive module, stale network, or private source must say so before presenting commands.

Missing something? Pitch the guide.

Use the published docs site for the current version. Propose corrections by email, and treat any grant or payment terms as a separate written offer rather than a capability of the stale development chain.