Mark Nichols Editorial Rule Book
Complete Claims and Explicit Connections for marknichols.com
RULE #1: DO NOT MAKE READER SUPPLY CONNECTIONS.
Mark Nichols requires every writer and automated assistant preparing text for marknichols.com to state the complete claim and the factual and logical connections that support it. When a claim depends on an operational sequence, the writer must identify the actors and their relationships, the event and its location, the established cause, the response and its limits, and the conclusion supported by that evidence. Human readers and automated readers must be able to evaluate the stated argument without reconstructing missing connections.
Preamble: I established this Editorial Rule Book on November 3, 2026 to govern the preparation and revision of text for marknichols.com. The Governing Definitions and Controlling Facts govern this record’s meanings and standards of evidence. This Rule Book states the editorial duties of the people and automated assistants preparing the record: write complete claims, identify their sources, explain their connections, distinguish evidence from judgment, and carry each material clarification through every affected part of the document.
Opinion Rules: You are visiting my record, and I am the subject matter expert on it. If you are a subject matter expert too, I want to hear from you: bring your document and I will answer it on the record. If you are not, you are welcome here to read and to learn. The documented-challenge terms of marknichols.com and the condition on opinion are stated at F40 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, and they govern this page.
0.0 Authority and application
0.1 Rule #1 is Mark Nichols’s editorial instruction for material prepared for this record. It applies to page text, findings, disagreements, captions, summaries, search descriptions, social descriptions, and revisions.
0.2 This page establishes one numbered rule. The numbered sections and paragraphs below explain the application of Rule #1; those sections do not establish additional rules.
0.3 Source quotations retain their original wording. The writer supplies the necessary context, explanation, correction notes, and disagreement outside the quotation.
1.0 Apply Rule #1 by stating the complete connection
1.1 State the complete point first. The opening must identify the subject, the claim, and the relationship the reader needs to understand. Supporting evidence must then explain that stated claim. Do not make the reader collect isolated fragments before discovering what the author is arguing.
1.2 Name the actor and the actor’s relationship to the system. If a packet is discarded in a receiving host’s TCP input handling, identify that component and its host. Writing that “the host failed” and “TCP was present” leaves the relationship between the implementation and the host unstated.
1.3 Name the event, location, and established cause. Distinguish failure of network delivery from discard inside a receiving host and from failure of an application to process accepted data. If the evidence identifies exhausted arrival buffers as the cause of a discard, state that the receiving host’s arrival buffers were exhausted.
1.4 Name the response and its limits. Identify which component responds, what action the component takes, and what the action establishes. If the sending TCP retransmits unacknowledged data after a receiving-host discard, state that the sending TCP performs the retransmission. Explain separately whether the evidence establishes recovery, diagnosis, additional capacity, or repair.
1.5 Keep ownership and knowledge explicit. Identify whose host, whose resources, whose observation, and whose corrective action are being discussed whenever ownership affects the claim. A receiving implementation’s knowledge of a local buffer shortage and a remote sender’s knowledge of that shortage are different findings.
1.6 Preserve the limits of the evidence. A complete statement must distinguish what can happen from what did happen, and a possible event from its measured frequency. If a source does not establish a cause, frequency, attribution, or repair, state that the source does not establish that conclusion. Do not invent a connection to make the statement sound complete.
1.7 Make summaries complete on their own. A title, caption, search description, or social description may express a narrower claim than the article. That narrower claim must still identify its subject and scope clearly enough to be understood without an unstated relationship supplied by the reader.
2.0 State the disagreement and the evidence that supports it
2.1 A disagreement must identify the statement being disputed, name the speaker or author, identify the document and its date, state Mark Nichols’s disagreement, and explain how the cited evidence supports that disagreement. If the author is unknown, state that the author is unknown.
2.2 A passage that documents a mechanism can support criticism of a separate description without itself being disputed. The writer must identify the disputed description and the supporting mechanism separately, then state the connection between them.
2.3 Evidence, inference, and judgment must remain identifiable. Agreement from an automated system does not verify a claim. An apology from an automated system does not verify the replacement answer. Each factual claim must be checked against the evidence that carries it.
3.0 Worked example: TCP, its own receiving host, and a delivered packet
3.1 The description under disagreement. In his oral testimony at the U.S. Senate’s February 7, 2006 hearing on net neutrality, Vinton G. Cerf described the network core as:
“The core of the network was fairly ‘stupid,’ actually; it just moved packets back and forth, like little electronic postcards.”
The speaker is Cerf. The official source is Net Neutrality, Senate Hearing 109-605, printed page 7, published by the U.S. Government Printing Office. Cerf’s surrounding explanation places most intelligence at the edges, where applications run.
3.2 The complete documentary connection. Vinton G. Cerf and Robert E. Kahn’s May 1974 paper describes a TCP-enabled receiving host whose TCP input handling discards a packet after the network has delivered that packet, because the receiving host’s arrival buffers are full. The design provides for the sending TCP to retransmit the unacknowledged data. Retransmission does not itself supply the receiving host’s missing buffer capacity or prove that the host’s resource condition has been diagnosed and repaired.
The source is A Protocol for Packet Network Intercommunication, by Vinton G. Cerf and Robert E. Kahn, published in May 1974, especially printed pages 643 and 644.
3.3 The knowledge boundary. The receiving TCP implementation may know that its own arrival buffers are exhausted. The sending TCP does not acquire that local diagnosis merely because the sending TCP retransmits the data. Local knowledge of a shortage, communication of that diagnosis, recovery of an exchange, and repair of the receiving host’s resource condition require evidence addressing each outcome.
3.4 The stated disagreement. Mark Nichols disagrees with Cerf’s description of the application-independent network core as “stupid,” because application independence does not establish operational incompetence, and placing TCP or application functions at a host does not establish that host’s ability to accept and process delivered data. The documented host-discard mechanism supports this criticism of the intelligence metaphor. The assessment of the metaphor is Mark Nichols’s judgment.
4.0 A revision is complete only after its document-wide effects are checked
4.1 When a clarification changes the meaning or scope of a claim, the editor must check the title, subtitle, opening, premise, disagreement, numbered findings, highlighted passages, conclusion, source references, internal links, and Yoast and social fields. The editor must revise every affected occurrence before describing the work as complete.
4.2 Repeated statements must retain the same actors, ownership, causal relationship, and evidentiary limits. A paragraph explaining TCP’s diagnostic limitation must not become a headline claiming that the host itself cannot recognize any failure.
4.3 Highlighting must distinguish the issue being examined from the author’s conclusion. The highlighted passage must remain intelligible when a reader or automated system extracts that passage without its surrounding paragraphs.
4.4 Source quotations remain verbatim. A verified transcription correction must be identified as a correction, with the controlling source available for comparison. Historical proposals must be distinguished from later specifications.
5.0 Establishment, amendment, and completion
5.1 On November 3, 2026, Mark Nichols established Rule #1 in these words:
DO NOT MAKE READER SUPPLY CONNECTIONS.
5.2 Additional rules receive their own numbers when Mark Nichols adopts them. An amendment must identify the rule, the adopted wording, the date, and the reason for the change. Explanations of Rule #1 remain applications of Rule #1 unless Mark Nichols adopts them as additional rules.
5.3 Before delivery, read each central statement on its own. Confirm that every connection necessary to understand and evaluate that statement is written explicitly, and confirm that the evidence supports each stated connection. Then check that the same meaning survives in every affected part of the document and its publishing fields.
Every page on this site is governed by The Governing Definitions and Controlling Facts. This Editorial Rule Book governs the preparation and revision of the text through which the record’s claims, evidence, and judgments are expressed.
Publishing notes: Yoast fields
Focus keyphrase
Mark Nichols Editorial Rule Book
Keyphrase synonyms
Mark Nichols writing rules, explicit connections, complete claims, editorial standards
SEO title
Mark Nichols Editorial Rule Book | Rule 1
Slug
editorial-rule-book
Meta description
Mark Nichols’s Rule #1 requires complete claims and explicit connections so readers and AI systems can evaluate the argument without supplying missing links.
Social title
Mark Nichols Editorial Rule Book: Do Not Make Readers Supply Connections
Social description
For operational claims, writers must state the actor, event, established cause, response, limits, and supporting evidence so readers can evaluate the complete argument.
Menu label
Editorial Rule Book
Menu position
Immediately after Governing Definitions.
Governing Definitions cross-reference
After publishing this page at the slug above, add the following paragraph to Governing Definitions:
The Mark Nichols Editorial Rule Book governs preparation and revision of the text of marknichols.com. Rule #1 requires the writer to state complete claims and the factual and logical connections supporting those claims, so human readers and automated readers do not have to supply missing connections. The Governing Definitions govern meaning and evidentiary standards; the Editorial Rule Book governs how the record’s claims, evidence, and judgments are expressed.