Skip to content

Keep authority, state, and quality gates explicit as a long-form story grows.

Start with what you need to do. Drop into the exact contracts only when implementation details matter.

Choose a path

Choose a path

You do not need to read the framework from top to bottom. Pick the outcome you need and follow the shortest useful path.

Run, extend, and inspect

Once the product model is clear, these are the practical entry points for execution, inspection, and integration.

Three documentation layers

Product concepts, usage guidance, and exact engineering contracts stay separate so each page can serve the reader who actually needs it.

Tier A

Product concepts

Mental models, positioning, architecture, production flow, and quality. Start here if NovelForge is new to you.

Tier B

Usage guides

Project SDK, integrations, context, learning, corpus, evaluations, quality evolution, and Studio.

Tier C

Contracts & engineering records

Harness, runtime, semantic workers, story and canon mechanics, policies, and historical specifications.