The directory methodology defines how ARuntime classifies and verifies runtime products without turning a category map into a leaderboard.
Record model
Records use a versioned JSON Schema and support primary/secondary categories, stack layers, formats, targets, capabilities, sources, status, version scope, review date, and caveats. Unknown values remain unknown.
Source hierarchy
Prefer specifications, official documentation, official repositories, and release notes. Vendor-specific capability claims require vendor primary material. Independent research can evaluate performance or limitations but does not replace product documentation for current feature status.
Classification process
- Identify primary execution unit and lifecycle.
- Assign primary category by dominant responsibility.
- Add secondary categories only for directly implemented responsibilities.
- Map covered layers.
- Record caveats and ambiguous boundaries.
- Validate internal links and source IDs.
Verification and cadence
Record the UTC date and version/documentation scope. Re-review after major releases, category changes, reported corrections, or at the editorial cadence. Metadata modification alone does not change the reviewed date.
Status handling
Active, archived, discontinued, preview, and research status are distinct from open-source/commercial and from maturity. Archived entries remain when they support historical understanding and are clearly labeled.
Corrections
Submit the record, field, proposed correction, authoritative source, and version. Accepted changes update the record, review date when materially reverified, and changelog.