Useful first.
Verifiable always.

Sirrius Atlas is designed as a working reference, not a feed of confident-looking claims. Every collection declares what its sources can—and cannot—support.

How an entry earns its label.

01

Discover broadly

Official documentation and changing public secondary material are reviewed to find commands, changes, and repeatable practices worth investigating.

02

Validate product facts

Current vendor documentation is the source of truth for commands, flags, availability, and version-specific behaviour.

03

Label the boundary

Secondary-only ideas remain patterns or watchlist notes. Corroboration is described as “Both”; it never implies two creators or an endorsement.

04

Keep judgment human

Automated research may produce a report, but it cannot edit a collection, create or merge a pull request, or deploy the website.

Three source descriptions.
No borrowed authority.

Official documentation

The entry is supported by current first-party product documentation.

Secondary web research

The entry is a publicly discovered pattern or watchlist item and is not presented as a product fact.

Official documentation + secondary web research

A practical idea was discovered through secondary material and independently corroborated against current official documentation.

The report may knock.
It cannot let itself in.

Collection audits create human-review reports containing evidence and explicit instructions. A person must authenticate each proposed change before it can be considered for publication.

  1. 1Documentation changes are detected.
  2. 2A review issue is created.
  3. 3Each candidate is authenticated.
  4. 4Approved changes are tested and reviewed.
  5. 5A separate, deliberate deployment is made.

Independent publication. Sirrius Atlas is published by Sirrius Office Inc. Vendor-specific field guides are not affiliated with or endorsed by the vendors they cover. Product names and marks belong to their respective owners.

Open Claude Code Atlas Visit Sirrius Office