Methodology
A public article should show how it was built, not just sound confident after it is published.
This page explains article types, source framing, sample language, and human review before a story asks for trust.
Public proof
Method, source, sample status, and scope should be visible before a story asks for the next click.
The goal is not to make every page heavy. It is to let readers see what kind of confidence the page has earned.
Article types
One public template works only when the story type stays visible.
These labels tell the reader what kind of answer the page is trying to give.
Desk explainer
Used when ingredient language, category terms, or shelf claims need translation before a product decision makes sense.
Primary proof: source note + scope line + visible query frame.
Routine guide
Used when the problem is order, repeatability, or where a step belongs inside a calmer routine.
Primary proof: sequence logic + practical use boundaries.
Comparison note
Used when two category ideas are routinely confused and the reader needs one cleaner distinction.
Primary proof: role differences + label cleanup + decision tension.
Trend shortlist
Used when launch noise, shelf movement, or category drift matters enough to deserve a filtered public note.
Primary proof: signal-over-noise framing, not a fake full-market census.
Sample and disclosure language
The page should not imply testing, gifting, or commerce that did not happen.
Purchased / gifted / loaned
If the body depends on hands-on use, the page should say how the product was obtained and what kind of use actually happened.
Not tested
If the page is source-led only, the sample line should clearly say that a purchased, gifted, or loaned wear test is not being implied.
No hidden commerce
Disclosure should state when a page is independent desk guidance and when sponsored, paid-placement, or affiliate mechanics are not present.
Human review gate
A draft is not a publish decision.
01
Define the reader question and article type before writing the answer.
02
Check claims, labels, and category language against source material or clearly stated testing.
03
Review the next step, disclosure, and correction route before publish.
Where this sits
Methodology explains how pages are built. Standards explain the public rules around them.
Use this page for mechanics. Use Standards for the public principles, disclosures, and correction policy around the archive.
Trust routes
The trust pages should connect like one public system.
A reader should not have to guess whether to open About, Methodology, Standards, Corrections, or Contact next. These pages should behave like one visible route.
AboutWho runs the deskOwnership, editorial scope, and why the public site stays reader-first.StandardsHow the public rules stay visibleBylines, dates, disclosures, correction policy, and editorial boundaries in public.CorrectionsHow a page gets challengedUse the correction route when wording, sourcing, or public meaning needs review.ContactHow messages are routedReader feedback, corrections, and business inquiries stay in separate public lanes.