Data Classification Settings Block for React

Add a label to LEVELS (with its rung), a rule to RULES and a document to DOCS with its sharing, whether it is encrypted, audited and needs MFA. The matrix, the phone chips, the lock list and the checks all read from those lists. A rule that a label can never drop goes in LOCKED; a new rule also needs a line in conflictsOf, which is the one place that says what a conflict looks like.

It is a small pure function. For a document and its label it asks, in order: does the label forbid sharing outside while the document is public or shared outside; does it require encryption while the document isn't encrypted; does it require audited access while it isn't; does it require MFA while the document opens without. The first conflict is shown with how many more there are, and a document with none says its label fits. Change a switch or a label and every row is checked again.

All of it. The facts about the documents are typed samples and nothing is encrypted, audited or enforced; Save keeps the choices in this page only. To make it real, read the facts from your storage layer, run the same check when a document is labelled or its sharing changes, and enforce the label's rules where files are served, not only here.

Some rules follow from the label itself: a Restricted document is always encrypted and audited, and a Public one can always be shared, so those cells are on, disabled and say so in their name. They are drawn on the page, never hidden, so the matrix reads as a complete ladder.

They are always there and always answer. Save counts what changed (switches, labels and the default) and keeps it in this page, saying "Saved 3 changes in this demo.", or "No changes to save."; it saves even when conflicts remain, because the conflicts are a report, not a block. Discard puts the last saved state back.

Below the medium breakpoint each rule is a card: its name, its hint and a two-by-two grid of toggle chips named for the label and the rule ("Restricted for Require MFA"). The documents stack with their check under the select, and the Save and Discard foot stays pinned to the bottom of the screen. Every switch, chip and select takes the keyboard in the usual way.