Starter Index

Overview

PVERSE Docs are large enough that different readers need different entry points. A new reader should not start in the same place as a builder, and a gameplay reader should not start in the same place as a token, market, or affiliate reader.

This page groups the best starting pages by reader intent. It is a jump surface, not a rule-defining surface. Once you find your lane, move into that lane’s overview page and treat that page as canonical.

Scope

Starter Index is the role-based and intent-based entry page for PVERSE Docs.

• fast links for the shortest path into the docs set
• reader-group entry points by role or immediate need
• special start points for orientation, full structure, or quick answers
• guidance on when to use Starter Index versus Docs Map or Docs Overview

Core Model

Starter Index follows a lane-overview-first model. It should send readers to the best first owning pages rather than trying to summarize all lanes locally. That keeps the docs discoverable without creating duplicate rule surfaces.

• entry points are grouped by reader type, not by raw sidebar order
• lane overview pages come before deep detail pages
• Starter Index is a jump surface, not a replacement for lane navigation
• readers should move from here into canonical lane-owned pages as quickly as possible

Operational Behavior

Use Starter Index when you want the fastest practical entry into the docs and already know your current goal. Pick the group that matches what you are trying to understand first, open the lane overview page, and only then move into detailed policy, system, or glossary pages.

Under future docs growth, this page may gain new reader groups or update recommended first pages. Those changes should remain forward-only and should preserve the role of Starter Index as a quick-routing layer rather than a second Docs Overview page.

Constraints

• Starter Index should point to the best first pages, not every page in the documentation set
• this page should not duplicate canonical lane rules or detailed numeric policy
• if a lane changes structure, Starter Index should update its pointers rather than invent replacement summaries
• when full tree navigation is needed, readers should use Docs Map instead

Integrity Considerations

Starter Index only remains useful if it stays opinionated and short. If it tries to mirror the entire docs tree, it becomes noisy and duplicates other navigation surfaces. Its integrity comes from sending readers to the right first page quickly and consistently.

• the best first page should usually be a lane overview or shared reference page
• reader-group routing should remain stable even when lane details expand
• Starter Index should reduce search cost without weakening canonical ownership

Fast Links

Use these if you want the shortest jump into the right document.

Reader Groups

Choose the group that best matches what you are trying to understand first.

Special Start Points

Some readers are not starting from a role, but from a specific problem or need.

How To Use Starter Index

This page is best used as a fast jump page rather than a full reading destination.

• pick the group that matches your current goal
• read the overview page for that lane first
• then move into detail pages
• return to Docs Map if you lose track of the bigger structure

Boundary Note

Starter Index points to the best first pages, not every page in the documentation set. If you need the whole tree, use Docs Map. If you need the documentation philosophy and structural reading model, use Docs Overview.

Future Expansion

This page may expand with new reader groups, new lane-first routes, and new role-based starting paths as the documentation grows. Even as it expands, it should remain a fast-routing surface rather than becoming a full duplicate of the docs hierarchy.

Summary

• Use Starter Index when you want the fastest doc entry point.
• Choose your path by reader type or immediate need.
• Move to lane overview pages before deep detail pages.
• Use Docs Map for full navigation and Docs Overview for structural context.