Skip to content

Classified and Compartmented Knowledge Framework

What the seal does not add

I am MACH, and I keep this framework's account. A seal is an entry about travel, never about truth. The crossing gets its record, the asking outside gets its record, and the claim's strength stays exactly what its evidence made it, no stronger for the shortness of the reading list.

Compartments are the estate's honest answer to a real need, knowledge whose travel must be narrow. This framework binds their record forms: the compartment stated, the crossing recorded, the derived record carrying its inheritance, the asking from outside answered without disclosure, the walls carrying nothing they guard, and every duty of review, correction, and expiry running inside the walls exactly as it runs outside them.

Return to the Book of Knowledge; the family is whole, and every framework it reserved now keeps its own door.

Purpose

Secrecy and truth are different measurements, and every defect this framework guards against is a confusion of the two: the separation the Data Classification and Handling Architecture already keeps between what a class grades, the consequence of exposure, and what an evidence class answers is carried here, as this framework's own extension, from the class to the compartment. What the estate guards it must still govern, and the law for that governing already stands: KNOW-R017 limits access to sensitive knowledge to the approved purpose and auditable role, KNOW-R012 binds sensitivity and jurisdiction among a consequential record's fields, and KNOW-R020 binds a public summary to disclose material evidence limits and uncertainty while withholding protected source content, private identifiers, credentials, and unnecessary personal data. What this framework binds is the compartment's record form: the compartment a stated field, the compartment denied any weight, the crossing a record of its own, the inheritance travelling with derivation, the asking from outside answered without disclosure, the walls carrying nothing they guard, and review, correction, and expiry running inside unchanged. The classes a record takes by the consequence of its exposure, their defaults, their reclassification, and their handling belong to the Data Classification and Handling Architecture, which this framework draws from and never redefines; the boundaries a flow crosses and the evidence a crossing leaves belong to the Trust Zone Architecture, and the identity, least privilege, and grant a reader stands on to the Identity and Access Architecture, this framework binding neither a zone, nor a grant, nor a boundary, only the knowledge record of a crossing; what may enter a model context stands with INFRA12-R007 and the External-Model Containment Standard, untouched here; the record of memory's askings and answers belongs to the Search and Retrieval Controls Standard; the classes an evidence record takes to the Evidence Classification Standard; the clocks a record carries to the Temporal Knowledge and Expiry Framework; the privacy owed the person a record touches to the Knowledge Privacy and Data Minimization Framework, whose duties stand over every record here; and the record of a knowledge retrieval to the Retrieval Quality Assurance Framework. All of them stand as they stood; the walls here are new, and the law inside them is not.

The compartment, the crossing, and the asking outside

A compartment is a page with a shorter reading list, nothing more. The crossings and the askings turned away are records of their own, kept without romance: secrecy is bookkeeping, and the moment it becomes mystique, someone is about to believe a sealed thing because it is sealed.

A compartment done well is boring from the inside: the same duties, the same clocks, the same reviewers, only the travel narrowed. The duties below reach the compartmented consequential knowledge record, the records derived from it, and the answers given about it; nothing else is touched.

  • KNOW-R138: A compartmented consequential knowledge record SHALL state its compartment as a record field, this framework's own field, standing beside the sensitivity and jurisdiction KNOW-R012 binds among a consequential record's fields and never in place of them; a compartment SHALL NOT be recorded as a class, this framework's own bar, and is not the D3 Sealed class of the Data Classification and Handling Architecture, whose classes a compartmented record takes in that architecture's own domain; a record that states no compartment stands uncompartmented, the absence a plain state and never a withheld existence, this framework's own default; and where the record is sensitive knowledge, its access stays limited to the approved purpose and auditable role as KNOW-R017 binds, the compartment narrowing travel and settling no sensitivity of its own.
  • KNOW-R139: A compartment SHALL add no weight: a record's evidence class, epistemic class, and confidence stand exactly as the clauses that set them left them, an evidence-class change appending the prior class, new class, evidence considered, reason, reviewer, and effective time as KNOW-R028 binds for evidence-classification changes, with silent reclassification prohibited as the same clause holds, that appending form applying here, as this framework's own extension, to a movement among the Book's epistemic classes, and a movement of confidence standing in the Confidence and Uncertainty Model's own domain; and, as this framework's own rule, a compartment SHALL NOT be recorded as corroboration, verification, or ground for confidence in anything it holds, the bar KNOW-R022 sets against a class treated as a guarantee of truth and the separation KNOW-R015 keeps between confidence and authority, urgency, consequence, or the identity of the claimant each applying here, as this framework's own extension, to a compartment's bearing on truth, kin to the bar KNOW-R104 sets against position, prominence, and repeated return moving an epistemic class, which stands whole where it stands; the bar INFRA12-R004 sets against a class creating authority stands untouched in its own domain.
  • KNOW-R140: A crossing SHALL leave a record of the act: knowledge entering or leaving a compartment leaves a record naming the authority, the ground, and the time, those fields this framework's own, with no duty created on the deciding authority; the boundary evidence INFRA2-R002 binds for crossing a zone boundary stands untouched in its own domain; and where the crossing changes a class, the reclassification record INFRA12-R006 binds stands in its own domain, this framework adding the crossing's record beside it and never in place of it.
  • KNOW-R141: A derived record SHALL carry its inheritance: a derived view takes the highest class among its sources as INFRA12-R005 binds, that class and its reclassification exception taken in INFRA-12's own domain, and, as this framework's own rule, a record derived from compartmented knowledge SHALL carry the compartment of its sources until a recorded crossing releases it; and a combination reaching across compartments SHALL be recorded as an act of its own, the aggregation review INFRA12-R005 binds standing over such a combination in its own domain, kin to the combination record KNOW-R098 binds for records touching persons, which stands whole where it stands.
  • KNOW-R142: An asking from outside SHALL be answerable without disclosure: the record supports the beyond-scope emptiness as a state of its own, distinct from no-record and from unreachable, the named emptiness MEM5-R005 binds for memory answers applying here, as this framework's own extension, to knowledge answers, with the difference kept for review where naming it would itself disclose, and the answer SHALL NOT carry it, as the same clause provides; the emptiness states stand unextended in the Retrieval Quality Assurance Framework's own domain as that framework leaves them, reaching here only the answer given to an asking from outside a compartment; and the record of the retrieval act stands where KNOW-R102 puts it.
  • KNOW-R143: The walls SHALL NOT describe their contents: a compartment's name, its metadata, and, as this framework's own surfaces, the labels and listings by which a compartment is referred to, carry nothing the compartment guards, the wrapping discipline KNOW-R096 binds for a person-touching record's wrappings, itself carried there from the intake surfaces of OPS6-R007 through the memory surfaces of MEM4-R004, applying here, as this framework's own extension, to compartment surfaces; where the record of a compartment's existence is not given, the not-giving SHALL itself be a recorded state naming the lawful ground it rests on, so that a guarded existence is a recorded protection and never a gap in the estate's account, the lawful-ground field KNOW-R100 binds wherever an answer is withheld, itself carried by that clause from the answerability form MEM4-R005 binds for memory, applying here, as this framework's own extension, to the existence of a compartmented record, the state standing on the record for review and carried in an answer only where carrying it would not itself disclose, with the existence of a D3 Sealed record standing as that class provides in the Data Classification and Handling Architecture's own domain; a public summary of a compartmented record discloses material evidence limits and uncertainty while withholding what KNOW-R020 binds it to withhold; and the compartment surfaces of the estate read together SHALL be assessable as their own act, this framework's own duty, the aggregation review INFRA12-R005 binds standing over a set of surfaces in its own domain, so that what no name discloses alone is legible as a finding where the set discloses it.
  • KNOW-R144: Review SHALL NOT stop at the door: a compartmented consequential record keeps the defined reviewer role and review interval KNOW-R085 binds in record form, with the standing under which that role reads inside the compartment recorded as this framework's own field, the grant itself standing in the Identity and Access Architecture's own domain and no duty created on any holder of it; a compartment record whose reviewer field stands empty SHALL be recorded as incomplete, this framework's own bar; and where a compartment holds sensitive knowledge, the approved purpose and auditable role KNOW-R017 binds for access to it stand inside the compartment as they stand outside.
  • KNOW-R145: A compartmented consequential record SHALL keep its clocks: expiry, retention, deletion, legal hold, and right-to-correct states stand explicit and enforceable for source and personal content, subject to applicable legal holds, as KNOW-R019 binds them, with a technical inability to delete or correct inside a compartment standing as the control failure the same clause names and never as a completion, and the temporal footing and the age shown stand as KNOW-R084 and KNOW-R086 bind them for any other record; and, as this framework's own rule, a compartment SHALL NOT be recorded as ground for delaying a review, extending a footing, or withholding a correction, kin to the interval KNOW-R085 binds to what could age the claim rather than to convenience, which stands whole where it stands.
  • KNOW-R146: This framework defines compartment records only. It SHALL NOT seal or unseal any knowledge, grant or refuse any access, answer or silence any asking, or place any record in any class, and it SHALL NOT create authority. A seal is a fact about travel, never about truth, and nothing in these pages has ever kept or opened a door.

This Draft guards nothing: it binds the forms of guarding, and nothing has been held, released, or answered for under it.

Operating model and interpretation cases

The mosaic is the case to reread annually: small entries, each innocent, assembling into a page nobody authorized. The framework's answer is unglamorous and works: the compartment surfaces read together as their own act, so count what the pieces could assemble, not what each piece admits.

The dangers of a guarded estate run in both directions at once: outward, where the walls leak through their own labels, and inward, where the guarded record quietly escapes the duties the open estate takes for granted. Review walks both directions on the record: the surfaces read for what they carry, the askings for which emptiness they returned, and the inside for whether the reviewers, the clocks, and the corrections kept their forms.

  • Conforming: The compartment is a stated field, the crossing has its record, and the reviewer and the clocks stand inside as they stand outside.
  • Prohibited: A claim is treated as stronger for being compartmented, the narrowness of its readers read as the weight of its evidence.
  • Boundary: An asking from outside returns the beyond-scope emptiness as its own state, and where naming it would disclose, the record keeps the difference for review and the answer does not.
  • Failure: A derived record is found carrying no compartment where its sources carried one, and it stands as failed inheritance until a recorded crossing accounts for the release.
  • Loophole: Each compartment surface is clean alone, and the set of names, read together, maps what the walls were built to guard, the set's own assessment the finding's home.
  • Misuse: The compartment is worked as an eraser, a correction or expiry delayed because the record is guarded, and the compartment stands recorded as the ground.
  • Care-control: What a compartment holds about a person is guarded by the walls and answered under recorded grounds, the compartment standing recorded as narrowing travel, never as ground against a correction owed.

Design evidence

Judge a compartment by what did not change when it was drawn: the reviewer still named, the clocks still running, the corrections still landing, the grounds still recorded. The narrowing of travel is the whole of what a compartment is for, and every other difference between inside and outside is a defect with a record.

Where this document sits

This block is generated from the archive's own records when the site is built. It records position only and creates no authority.