Skip to content
System architecture whitepaperRule orchestration algorithmPerformance and evidenceReferences and evolution

System Architecture Whitepaper / Rule Orchestration Algorithm / Evidence Dossier

Turn Cursor Rules into a reviewable engineering research portal

The homepage now behaves like the project thesis: explain the system first, make the orchestration algorithm legible, and back every claim with performance, evidence, and references.

132+Rule assets
32+Domains
4High-density domains
ThesisSystemEvidenceMission → Architecture → Rules → References

Thesis Signals

A system architecture whitepaper needs structure before persuasion

The landing page answers four reviewer questions fast: what the repository organizes, how the publication system works, how the rule orchestration algorithm behaves, and why the evidence is credible.

Rule assets

132+

The repository remains the single source of truth for every metric and figure.

Knowledge coverage

32+

Dense and long-tail domains together frame the corpus as a knowledge system.

Phases

3

Curation, orchestration, and publication stay explicit instead of implied.

System Topology

The system architecture whitepaper translates repository facts into a publication system

Rather than relying on copy alone, the site is organized as asset, snapshot, IA, presentation, and publishing layers that can be reviewed independently.

1Asset Layerrules/ stays canonical so the shell cannot drift from the corpus.2Snapshot Layersync-site-facts.mjs turns repository state into reusable structured data.3IA LayerIntroduction, architecture, algorithms, performance, references, and evidence form the reading path.4Presentation LayerTheme components convert metrics, topology, pipeline, and dossiers into one visual language.5Publishing LayerVitePress and GitHub Pages publish the final whitepaper surface.

Method

The rule orchestration algorithm is a documented pipeline, not a black box

The algorithms chapter explains how the project turns a flat rules corpus into categories, composition patterns, upgrade paths, and publication-ready evidence.

1

Discover

Scan the corpus and normalize the asset set.

2

Classify

Map rules into domains, buckets, and long-tail signals.

3

Compose

Translate rule clusters into composition patterns and review paths.

4

Publish

Expose architecture, performance, and references as an evidence surface.

Performance & Evidence

Performance and evidence are first-class chapters, not footnotes

Performance here includes build stability, navigation efficiency, maintainability, figure reliability, and the density of useful signals available to advanced readers.

High-density domains

4

Dense domains provide fast, strong signals for reviewers.

Mid-density domains

6

The middle layer proves the corpus scales beyond a few headline categories.

Long-tail domains

22

The long tail strengthens the site as a research-grade reference surface.

References & Evolution

References and evolution raise the project above a category index

Instead of decorative links, the dossier maps which framework, project, or reference shaped each layer of the publication system.

Documentation Method

Diátaxis

Absorbed

Separates explanation, guidance, and reference so the shell stays legible.

Advanced

Refines that split into introduction, architecture, algorithms, performance, references, and evidence.

Docs Engineering

MoonshotAI / kimi-cli

Absorbed

Borrowed the build-time docs snapshot idea.

Advanced

Expanded the snapshot into a whitepaper-ready data model for figures and dossiers.

Open Source Framing

AOSA + peer repositories

Absorbed

Treats architecture and boundaries as publishable project assets.

Advanced

Turns the rules index into an evidence layer supported by references and evolution notes.

Reframing 132+ rule assets across 32+ domains as a whitepaper, algorithm dossier, and evidence library