CC-DSG.1 Situation first | A cold reader sees the working situation, practical question, useful answer or blocker, exact contributions, and stop or return before internal apparatus. |
CC-DSG.2 Reference and Suite return | The Reference identifies its edition and returns to the Suite collection, the decisions that establish which product series belong, and each product, edition, result, state, or source that changes the answer. An optional configuration description is named only when the use needs it. |
CC-DSG.3 Separate product and use boundaries | Reference product series, Reference edition, Suite collection, DPF product series and editions, lookup Work, answer, publication, carrier, belongs-to occurrences, availability, and Reference use remain distinct. |
CC-DSG.4 Progressive detail | Date and actionable status are visible; author, evidence, relation, product-series state, warning, and reopen detail appears only when it changes reader action, truth, or named reliance. |
CC-DSG.5 Answer discipline | Each returned item is classified and stated separately as an available result of its actual kind and supplying product, a MethodDescription reference, direct-source evidence, or a named unavailable result. Its readable contribution or blocker is explicit; maintenance appears only when it changes use, and recommendation, alternative, dependency, compatibility, and co-listing create none of those relations. |
CC-DSG.6 Sufficiency and necessity tested | The combination satisfies the declared sufficiency rule and removing any returned item makes the required result insufficient within the stated candidate boundary. A “smallest” claim additionally states a size criterion and establishes that no smaller in-scope combination is sufficient; otherwise retain the narrower necessity claim or call the answer bounded and plausible. |
CC-DSG.7 Change and return honesty | Edition admission to a product series, product-series inclusion in a Suite, qualification warning, removal, product or Suite ending and reidentification, past belonging, availability, Reference route, temporary empty state, and retirement follow their separate rules. A known DPF result remains directly usable without a Reference detour. |
CC-DSG.8 Derivative boundary | Expression, translation or other derivative, an established edition-continuity relation, language-specific product, and carrier are distinguished by their actual identity, source, scheme, reader-use, and maintenance facts. |
CC-DSG.9 Plain-language whole passage | The complete changed passage can be read by an engineer or manager without reconstructing ontology notation; exact triples and relation terms appear only where they change identification or a stronger claim. |
CC-DSG.10 Current problem-led entry fit | Each entry starts from a real working question, supports necessary branches or honest stops, links out distracting detail, and reflects the intended readers’ information need, presentation, availability, and any separately established maintenance fact that changes use. The Reference records what was adopted, adapted, and rejected from current task-guide practice and when to recheck it. |