The methodology defines how ARuntime selects, classifies, verifies, and maintains technical sources and product records.
Research question
Every page begins with a distinct reader question and scope. Sources are selected to define responsibilities, boundaries, mechanisms, failure modes, and implementation—not to maximize citation count.
Search and source selection
Prefer formal specifications, government/public guidance, peer-reviewed or original papers, official documentation, maintainer repositories, and release notes. Secondary analysis is used only when primary material is insufficient and is labeled accordingly.
Inclusion and exclusion
Include sources that directly support a page’s scope and can be linked. Exclude generic SEO summaries, unattributed claims, inaccessible evidence that cannot be verified, unresolved report artifacts, and future assertions represented as current fact.
Product categorization
Classify by execution unit, owned responsibilities, state, lifecycle, and failure boundary. Assign primary/secondary categories and layer coverage. Record ambiguity and caveats instead of forcing a product into one category.
Version handling
Product and protocol claims name a release, specification date, or current documentation scope and a UTC verification date. Archived or discontinued products remain only when useful and clearly labeled.
Benchmark evidence
Require model, version, hardware, runtime, precision, quantization, lengths, concurrency, batch behavior, cache state, warm/cold state, metrics, quality, and method. Do not combine incomparable vendor numbers into a ranking.
Fact and synthesis
Facts are directly supported. Editorial synthesis connects sources and is labeled. Proposed terminology is labeled emerging proposal. Forecasts state assumptions and uncertainty. Generated assistance is reviewed against sources and project constraints before publication.
Review cadence
Review material changes, security/protocol releases, reported corrections, and scheduled audits. A page-level review date changes only after substantive content and sources are checked.
Corrections
Submissions include page URL, section or quoted claim, issue, proposed correction, supporting source, and optional contact. Accepted corrections update content, references, change notes, and review dates where appropriate.