Reference

Move directly to lookup material when the task is already clear.

Reference is the operational map for command syntax, APIs, developer internals, and the adjacent materials that support concrete execution.

Open reference

CLI

Find exact command behavior

Jump into flags, subcommands, and workflow fragments when you already know which execution detail you need.

Open CLI reference

API

Inspect public interfaces

Move from command usage into API surface and module-level boundaries when library integration matters.

Open API overview

Internals

Trace developer-facing design

Use developer architecture material when the task requires build, testing, or implementation-level reasoning.

Open developer architecture

Reference

Reference is the lookup surface for readers who already know the question they need to answer. The whitepaper establishes the system story; reference tells you where to verify exact behavior, exact interfaces, and exact maintenance material without forcing you through the whole narrative again.

Use the deep-content layers intentionally

The content stack works best when each layer keeps one job:

• Whitepaper frames scope, constraints, and adoption logic.
• Architecture explains why the layers and boundaries exist.
• Algorithms explains filtering, statistics, execution, and memory behavior in maintained terms.
• Performance explains how to interpret throughput evidence.
• Research appendix adds bibliography, related-project comparison, and evolution notes once the core story is clear.

Reference begins after that point.

Implementation lanes

Use this page when the task is no longer “understand the story” but “land on the exact maintained interface.” The reference layer therefore routes readers into command, API, build, and contributor surfaces instead of repeating narrative prose.

Operator reference

• CLI Reference
• Getting Started
• Configuration
• Deployment

CLI and API lookup

• API Overview
• IO Module
• Processing
• Statistics

Contributor surfaces

• Developer Guide
• Developer Architecture
• Build
• Testing
• Benchmark Guide

Research and comparison entry points

• Research appendix
• Bibliography
• Related projects
• Evolution notes
• Archive Overview

Internal anchors from the whitepaper redesign

Internal documentation anchors

These entries come from the site-wide reference catalog created in the IA foundation. Use them as the canonical internal reading trail before you jump to external context.

1. DocWhitepaper overview

   Primary narrative entry that ties positioning, architecture, and evidence together.

   Theme concept: whitepaper

2. DocArchitecture rationale

   Trace zero-copy I/O, parallel pipelines, and maintainable boundaries.

   Theme concept: architecture

3. DocAlgorithm and workflow entry

   Keeps learning paths, workflows, and execution pages in one navigation skeleton.

   Theme concept: algorithms

4. DocBenchmark methodology

   Explains environment, caveats, and how to read throughput numbers.

   Theme concept: performance

5. DocReference hub

   Shared entry for CLI, API, build, and testing material.

   Theme concept: referenceNav

6. DocResearch appendix

   Collects bibliography, adjacent-project comparison, and design evolution history.

   Theme concept: researchNav

How to use this page

• Want to execute commands right now? Start from Operator reference.
• Want to understand public interfaces and library integration? Start from CLI and API lookup.
• Want to inspect internals, build, or test practice? Start from Contributor surfaces.
• Want project background, external reading, or comparison material? Move to the Research appendix.