Observed
Directly inspectable in a cited artifact, public route, test output, dataset, standard, or dated record.
Trace to the sourcePublic standard
Make the claim as strong as the evidence allows.
This standard governs ARCTURA educational pages, guides, case records, and public institutional claims. It favors traceable sources, explicit boundaries, dated review, and correction over the appearance of certainty.
Claim classes
Readers should know what kind of statement they are reading.
Interpreted
A reasoned reading of observations. Plausible alternatives and material assumptions should be stated.
Separate fact from meaningProposed
An intended design, curriculum outcome, organizational direction, or next action that has not yet been demonstrated.
Do not write plans as resultsSource practice
Prefer the closest authoritative source.
For technical standards, use the issuing standards body, public agency, specification, or original research when available. For ARCTURA status, use the repository, production route, dated case record, or applicable legal record. Secondary explanation can add context but should not replace a primary source for a material claim.
Cite where the claim appears
Place the link close enough that a reader can tell what it supports. Use a direct destination, descriptive link text, and the version or date when change matters.
State the evidence limit
A source may establish publication, implementation, or a standard's language without establishing effectiveness, adoption, safety, or endorsement.
Authorship and generated assistance
Tools may assist; responsibility stays identifiable.
Automated and generative tools may support research organization, drafting, transformation, code, testing, or visual development. Public material must still be reviewed against its sources, checked for unsupported claims, and owned through the repository history. Generated output is not treated as a source.
Material should not imply personal experience, independent testing, partnership, endorsement, learner outcomes, or professional review when no record supports it. Generated images must not contain essential text, false institutional signals, or documentary claims.
Corrections
Make it easy to challenge a specific statement.
Open a public repository issue with the affected URL, exact text or behavior, proposed correction, and source when available. Security issues should follow the security policy rather than a public issue. A correction that should not be public can be sent to signal@arctura.org.
Receive
Record the route, claim, source, reporter, and potential consequence.
Classify
Distinguish factual error, stale status, ambiguity, accessibility defect, or interpretation dispute.
Correct
Change the page and connected metadata, schema, catalogs, or records in the same release.
Preserve
Keep the change in Git history and note a material correction where silent revision would mislead.
Review cadence
Review by consequence and volatility.
Legal, privacy, security, program-status, and ecosystem-boundary pages require review when the underlying state changes. Technical guides should be reviewed when cited standards materially change or a correction reveals a broader issue. Dates signal review, not permanent validity.