RuleRoster methodology

1. Admit the source before the fact

RuleRoster starts with official or otherwise authoritative sources whose ownership and reuse terms have been reviewed. A public web page is not automatically an admitted source.

When an official source is maintained in a versioned repository, RuleRoster pins the exact commit, path, byte length, content hash, and Git blob identity used for extraction.

• Source ownership and authority are recorded explicitly.
• License, attribution, and notice obligations are retained.
• Ambiguous, conflicting, mutable-only, or unsupported statements remain unpublished.

2. Preserve scope and uncertainty

Facts are converted into strict typed fields that preserve units, applicability, exceptions, consequences, and source-stated qualifiers. RuleRoster does not turn examples into defaults or recommendations into hard limits.

A not-stated marker means the bounded admitted source did not state that field. It is an uncertainty marker, not an affirmative platform behavior.

3. Separate evidence, review, and publication

Evidence snapshots, extracted facts, rule-content packets, approvals, verifications, and publications have separate immutable identities. Changes invalidate later stages instead of silently rewriting history.

Exact compiled repository releases remain permanently noindex. Index promotion is a separate authenticated human decision after the live record and all current quality gates have been rechecked.

4. Recheck every public read

Public pages fail closed unless the current rule version, verification, source links, publication revision, quality result, freshness window, and compiled department module still agree.

Stale or changed evidence is never repaired by guesswork. The record is removed from discovery, marked for review, or retired until a new evidence-backed version is approved.

5. Corrections and independence

RuleRoster is an independent reference. It does not speak for the organizations whose rules it summarizes, and project names are used only to identify the relevant source and scope.

A correction can challenge a claim with a source URL. Accepted corrections create a new reviewed version or an explicit retirement; they do not rewrite the historical record.