Conformance Cell

A normative requirement from the OCSS Trust Framework conformance contract. Each cell pairs a mono, uppercase keyword — MUST, SHOULD, or MUST-NEVER — with the requirement text, color-coded to the conformance state tokens and led by a signal rule. The keyword is always real text, never communicated by color alone.

The three levels

must → success · should → warning · must-never → danger.

MUSTVerify the outer envelope signature before acting on any payload.
SHOULDCache the Trust List and re-validate entries at least once per hour.
MUST-NEVERTrust an unsigned envelope, or downgrade a stricter inner rule.

Keyword override

The rendered keyword can be overridden (e.g. RFC 2119 synonyms) while level keeps driving the color and signal rule.

RECOMMENDEDPin the accreditation tier in the audit log alongside the decision.
PROHIBITEDSell, broker, or re-share data attributable to a minor.

The MUST / MUST-NEVER contract

The spec page’s two-column contract: the obligations column set against the prohibitions column. Collapses to a single column on narrow viewports.

MUST

  • Verify the outer signature
  • Honor the strictest rule
  • Log the enforcement decision

MUST-NEVER

  • Trust unsigned envelopes
  • Downgrade a stricter rule
  • Sell or re-share minor data

Three-level contract

A layout="stack" contract carrying all three levels in a single column.

MUST

  • Present a valid Trust List entry
  • Pass the conformance test suite

SHOULD

  • Re-validate the Trust List hourly
  • Surface the accreditation tier to operators

MUST-NEVER

  • Display the certification mark without a passing suite
  • Accept an expired or revoked signature