ProtectMySleep®Category LabChoose a design
Menu

Methodology

Facts, methods, and claims stay in separate columns.

The Category Lab is designed to be useful without pretending that research context is product proof. Every record states who controls the source, what was evaluated, which product or sample it applies to, and what it does not establish.

Record
PMS-KB-MTH-001
Version
1.0
Published
Modified
Reviewed
Publisher
ProtectMySleep Category Lab
01

Last reviewed 28 July 2026

02

Primary-source preference

03

No unspecified product claims

04

Governing publication policy for public Knowledge Base records.

01

Source fact

A statement directly supported by the cited regulator, standards owner, certification scheme, official material source, procurement file, or manufacturer page.

02

Engineering judgment

A technically reasoned development direction. It must be tested on the actual construction and is never presented as achieved performance.

03

Strategic inference

A commercial conclusion drawn from multiple facts—such as a market gap, program pathway, or content opportunity—clearly labeled as strategy.

Knowledge record contract

Organize the fact before publishing the answer.

A page is a reading view. The governed asset underneath it is a versioned knowledge record with a stable identity, evidence chain, applicability boundary, and accountable review state.

  1. 01

    Permanent record ID, canonical URL, record type, publication status, and version.

  2. 02

    A concise conclusion, controlled terms, applicable scope, and explicit out-of-scope boundary.

  3. 03

    Evidence class, source owner, source URL, edition or date, and a locator precise enough to recheck the statement.

  4. 04

    Method, conditions, specimen or product boundary, units, and sample state for any measured value.

  5. 05

    Known limitations, uncertainty, and the conclusions that the evidence cannot support.

  6. 06

    Related materials, components, product systems, claims, tests, and commercial-availability state.

  7. 07

    Responsible publisher or contributor, technical reviewer when assigned, publication date, modified date, and review date.

  8. 08

    Change reason, correction note, and prior-version reference when a substantive conclusion changes.

AI use policy

AI may assist the work. It is never the evidence.

AI tools may help discover candidate sources, organize terms, compare documents, translate, or prepare a working draft. A generated answer is not cited as authority and does not raise an evidence state.

Before publication, material facts must be checked against the identified primary or controlling source. Inferences remain labeled, limitations remain visible, and a result from one material, sample, or construction is not generalized to a category.

Public HTML, structured data, and the machine-readable record catalog are generated from the same record fields so that a crawler does not receive a stronger or different claim than a human reader.

Evidence states

Five labels prevent a concept from becoming a claim.

Every technical data card should display its state before showing a value, adjective, certification mark, or comparison.

01

Verified

A traceable report or certification applies to the identified product, BOM revision, sample state, and scope.

02

Supplier-declared

A supplier document is available, but finished-product performance has not been established.

03

Engineering target

A desired value or acceptance criterion for development—not an achieved result.

04

Concept

A research direction with no qualified commercial construction.

05

Not comparable

Method, conditions, units, specimen, or sample state differ; ranking would mislead.

Publication rules

Evidence discipline is an operating habit.

The Lab publishes technical frameworks only after their sources, evidence state, limitations, and review date are made visible to the reader.

  1. 01

    Prefer regulators, standards owners, certification schemes, official material-brand documents, public procurement files, and manufacturer product specifications.

  2. 02

    Label brand claims as brand claims; never borrow a competitor result for ProtectMySleep.

  3. 03

    Record URL, owner, title, publication or version date where available, access date, scope, and limitation.

  4. 04

    Separate law, method, voluntary certification, supplier declaration, engineering inference, and commercial strategy.

  5. 05

    Attach every publishable performance statement to a Claim ID and Product Evidence Record.

  6. 06

    Freeze or downgrade a claim when its membrane, construction, factory, process, care profile, certificate, or evidence scope changes.

Corrections & accountability

Substantive corrections should leave a trace.

When evidence, scope, or a conclusion materially changes, the record’s modified date, version, and correction note should be updated. Typographic changes do not create a false freshness signal.

ProtectMySleep Category Lab is the responsible publisher. Named contributors and technical reviewers are attached when a record has an assigned individual review owner.

Report an error or submit a source