docs: diagram operations — fold cascade/trace/restrict derivation into the specs (WIP)#234
Draft
dimitri-yatsenko wants to merge 2 commits into
Draft
docs: diagram operations — fold cascade/trace/restrict derivation into the specs (WIP)#234dimitri-yatsenko wants to merge 2 commits into
dimitri-yatsenko wants to merge 2 commits into
Conversation
…Diagram.cascade; fix list formatting - Transitive completeness: a FK to a master is a dependency on the whole composite (master + all parts); downstream tables reference the master alone. - Delete Operations expressed through the cascade engine (Diagram.cascade): master->part is a downstream edge; part_integrity=cascade does the upward walk (U1-U3) + materialize + forward re-cascade. Cross-links cascade.md. - Fix §7.1 and §4.4 bold-label lists (blank line before list for MkDocs).
…nale section Move the first-principles derivation of cascade/trace/restrict (one engine; OR-vs-AND; part->master walk only when mutating; materialization; conformance + open items #1496/#1501/#1481) from the explanation doc into the Diagram spec, so the low-level design lives with the normative spec and implementation is re-derived from it. Reduce explanation/diagram-operations.md to a short conceptual pointer. Fix '-> Master' -> '-> master' in the moved text.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Status: WIP / draft.
Reorganizes the diagram-operations documentation on one principle: low-level technical definitions belong in the specs (with implementation re-derived from the spec), and explanation stays conceptual.
Changes
reference/specs/master-part.md— sharpen the transitive-dependency definition (a foreign key to a master is, in effect, a dependency on the whole composite — master + all parts; downstream tables reference the master alone). Express the Delete Operations rules through the cascade engine (Diagram.cascade: master→part is an ordinary downstream edge;part_integrity="cascade"= upward U1–U3 walk + materialize + forward re-cascade), cross-linkingcascade.md. Fix §7.1/§4.4 bold-label list rendering.reference/specs/diagram.md— new Design Rationale section: the first-principles derivation thatcascade/trace/restrictare one propagation engine (OR-vs-AND, part→master walk only when mutating, materialization), plus Conformance and open items (#1496 / #1501 / #1481). Moved here from the explanation doc so the design lives with the normative spec.explanation/diagram-operations.md— reduced to a short conceptual pointer that redirects to the Diagram spec's Design Rationale and the cascade/trace/master-part specs.Still to do (WIP)
mkdocs.yamlnav entry for the reduced explanation pointer is not in this PR yet.cascade.mdstill describes the dependency graph asnetworkx.DiGraph; should readnx.MultiDiGraph(2.4 line) to match the derivation.