Reference
Use this section when you need the public commitments that sit behind the README and tutorial pages. It is the contract layer of the docs, not the default first-run reading path.What Stays Public
- Why: the project’s public rationale, stance, and positioning
- Direction: the public roadmap and stage-based priorities
- Product contract: user-facing product sense and first-run journey
- Reliability: build, runtime, and architecture invariants
- Security: disclosure expectations and hardening boundaries
- Releases: release notes and changelog-style public history
- Architecture: the public system map and crate boundaries
Choose A Reference Track
| If you want to understand… | Start here | Why |
|---|---|---|
| why the project exists and what stance shapes it | Why Loong | the public rationale and product posture live there |
| current product direction and first-run contract | Roadmap And Product | roadmap milestones and public product sense stay together |
| where public docs should live and how they should be written | Documentation Policy | this is the repo and Mintlify boundary contract |
| non-negotiable safety and stability expectations | Security And Reliability | invariants, disclosure, and trust boundaries live here |
| public release trail and shipped change history | Releases | this is the public release history, not a planning backlog |
Reference Boundary
Reference stays focused on public commitments, published invariants, release history, and the repo-native source material that supports those commitments. Use setup and tutorial pages first when you still need a runnable path; come here when you need the contract behind that path.Continue Reading
- Go to Why Loong for the public rationale, positioning, and product stance behind the rest of the docs.
- Go to Roadmap And Product for roadmap milestones, product sense, and the current MVP journey.
- Go to Documentation Policy for docs placement, language scope, and publishing model.
- Go to Security And Reliability for invariants, disclosure, and trust boundaries.
- Go to Releases for release notes and changelog-style public history.
- Go back to Build On Loong if you are evaluating extension seams and contribution boundaries.