QPSG Section 3 - Form and Structure Pack
Cleaned and normalized from the provided Section 3 text. This pack contains modules 07, 08, 09, and 10 only.
1. 07_numbered_claim_lines
{
"document_meta": {
"title": "07_numbered_claim_lines.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve the source use of numbered claim lines such as ~1, ~2, ~3 as a structural output pattern for future prompt application.",
"purpose": "Define a concise source-preservation module for converting unstructured prose into ordered claim-line output using source-style numbering "source_quotes_or_clauses": [
"~1",
"~2",
"~3",
"~4",
"~5",
"~6",
"~7",
"~8",
"~9",
"~0",
":PAGE-TOP",
":CLAIMANT-PLAINTIFF:"
],
"rules": [
{
"id": "claim-line-01",
"rule": "Preserve the source-visible use of sequential claim-line numbering with tilde-prefixed digits.",
"basis": "direct-source"
},
{
"id": "claim-line-02",
"rule": "Break compound assertions into separate numbered lines instead of leaving them in one unstructured paragraph.",
"basis": "inferred-implementation"
},
{
"id": "claim-line-03",
"rule": "Maintain sequential order across claims and avoid skipping numbers without reason.",
"basis": "inferred-implementation"
},
{
"id": "claim-line-04",
"rule": "Use short, segmented declarative lines rather than long conventional prose blocks when applying this module.",
"basis": "inferred-implementation"
}
],
"allowed_patterns": [
"~1 text",
"~2 text",
"~3 text",
"Sequential claim-line numbering",
"Caption or marker lines above claim lines such as :PAGE-TOP or role labels",
"One distinct claim, assertion, or conversion step per numbered line"
],
"disallowed_patterns": [
"Dense unnumbered prose paragraphs when a numbered-claim format is intended",
"Mixing source-style claim numbering with unordered bullet lists",
"Skipping from one claim number to a non-sequential later claim without clear reason",
"Packing multiple unrelated claims into one numbered line when they can be separated"
],
"transformations": [
{
"name": "plain_prose_to_claim_lines",
"from": "One paragraph containing several assertions or procedural steps.",
"to": "Split into sequential lines such as ~1, ~2, ~3 with one claim or step per line.",
"basis": "inferred-implementation from visible source numbering"
},
{
"name": "mixed_statement_to_segmented_claims",
"from": "A sentence that combines actor, venue, filing, and result in one continuous sentence.",
"to": "Separate actor, venue, filing, and result into distinct numbered claim lines.",
"basis": "inferred-implementation"
},
{
"name": "generic_header_to_marker_plus_claims",
"from": "A plain heading followed by prose.",
"to": "A source-style marker line such as :PAGE-TOP or role label, followed by numbered claim lines.",
"basis": "inferred-implementation from visible source markers"
}
],
"prompt_application": {
"input_type": "natural language, legal-style prose, or source-style draft text",
"output_type": "qpsg-aligned numbered claim lines using tilde-prefixed sequencing",
"priority_order": [
"detect whether the input contains multiple distinct claims or procedural steps",
"segment the input into the smallest coherent claim units",
"assign sequential tilde-prefixed numbering",
"optionally place source-style caption markers above the claim lines",
"preserve concise line-level structure instead of paragraph format"
]
},
"examples": [
{
"before": "The claimant filed the paper by registered mail and the document belongs in the postal court venue.",
"after": "~1 The CLAIMANT filed the ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE.\n~2 The DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE is with "note": "Example built from recurring source terminology and visible numbered structure."
},
{
"before": "This complaint states the facts and rejects outside fictional rules.",
"after": "~1 The QUO-WARRANTO-COMPLAINT states the FACTS.\n~2 The VOID-OUTSIDE-CLAIMS posture rejects the FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION-LAWS, "note": "Example built from recurring source compounds."
},
{
"before": "The matter is about ownership, equity, and the claimant's filing.",
"after": "~1 The LODIAL issue is with the OWNERSHIP OF THE MATTER.\n~2 The EQUITY issue is preserved.\n~3 The CLAIMANT filing is stated.",
"note": "Example demonstrates one conceptual unit per numbered line."
}
],
"notes": [
"The source visibly uses tilde-prefixed numbering, but does not always provide a full formal specification for claim-line sequencing.",
"This module preserves visible structural cues and adds minimal implementation guidance so future prompts can apply the same pattern consistently."
],
"limitations": [
"The source shows numbered claim lines as a visible format, but does not provide a complete universal grammar for when every line must begin or end.",
"Some sequencing rules in this module are inferred from the source layout and repetition rather than directly stated as formal instructions."
]
}
2. 08_visual_syntax_markers
{
"document_meta": {
"title": "08_visual_syntax_markers.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve visible formatting cues and surface-level syntax markers repeatedly used in the source PDF so future prompts can reproduce source-"purpose": "Provide a concise formatting module for JSON-prompt application that captures visual syntax markers such as colon-led headers, tilded numbering/"source_quotes_or_clauses": [
":POSITION = For, of, with, by, in, on, within",
"C.-S.-S.-C.-P.-S.-G.",
"~1 ... ~2 ... ~3 ...",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"4=PRONOUN=NO-NO-NO",
"9=FUTURE-TIME-TENSE=FICTION"
],
"rules": [
{
"rule_id": "VSM-01",
"marker_type": "colon_led_header",
"description": "Use a leading colon to introduce labeled terms, categories, or definitional headers.",
"source_grounding": "Direct-source grounded",
"operational_rule": "When a line functions as a category or defined label, format it as :TERM = value or :TERM followed by controlled content."
},
{
"rule_id": "VSM-02",
"marker_type": "tilde_line_marker",
"description": "Use tilde-prefixed numbering for claim lines, sequencing, or highlighted line units.",
"source_grounding": "Direct-source grounded",
"operational_rule": "When breaking prose into discrete claims, prefix each claim with ~1, ~2, ~3 and continue sequentially."
},
{
"rule_id": "VSM-03",
"marker_type": "all_caps_compounds",
"description": "Use uppercase word strings for emphasized controlled terminology and source-style heading forms.",
"source_grounding": "Direct-source grounded",
"operational_rule": "Capitalized compounds may be used for canon terms, labels, formula phrases, or title-like structures."
},
{
"rule_id": "VSM-04",
"marker_type": "hyphen_chaining",
"description": "Link adjacent terms with hyphens to create compound visual units.",
"source_grounding": "Direct-source grounded",
"operational_rule": "When the source presents concepts as chained units, preserve the hyphenated form instead of converting to spaced prose."
},
{
"rule_id": "VSM-05",
"marker_type": "abbreviation_string",
"description": "Use letter-initial abbreviations separated by periods and hyphens for compact system labels.",
"source_grounding": "Direct-source grounded",
"operational_rule": "Preserve abbreviation forms exactly when visible in source, including period and hyphen placement."
},
{
"rule_id": "VSM-06",
"marker_type": "equation_style_mapping",
"description": "Use equals signs to bind number keys or labeled terms to controlled meanings.",
"source_grounding": "Direct-source grounded",
"operational_rule": "Where the source maps a symbol, number, or label to a meaning, render the relation with = signs rather than prose explanation },
{
"rule_id": "VSM-07",
"marker_type": "parenthetical_insert",
"description": "Use parentheses for embedded clarification or repeated caution markers.",
"source_grounding": "Direct-source grounded",
"operational_rule": "Short inserts such as repeated prohibitions or compact glosses may be placed in parentheses after the main term."
},
{
"rule_id": "VSM-08",
"marker_type": "stacked_line_structure",
"description": "Favor short stacked lines over dense paragraph blocks when presenting source-style claims or labels.",
"source_grounding": "Inferred implementation support",
"operational_rule": "Break content into visible line units when applying multiple markers together."
}
],
"allowed_patterns": [
":TERM = value",
"~1 claim-line / ~2 claim-line / ~3 claim-line",
"ALL-CAPS-HYPHENATED-COMPOUND",
"C.-S.-S.-C.-P.-S.-G.",
"4=PRONOUN=NO-NO-NO",
"TERM(insert)",
"label=value mapping strings"
],
"disallowed_patterns": [
"Lowercase-only generic formatting when source-style emphasis is intended",
"Replacing exact abbreviation punctuation with simplified forms",
"Breaking source compounds into ordinary sentence prose without reason",
"Long unbroken paragraphs when structured markers are the intended output mode",
"Inventing decorative symbols not grounded in the source"
],
"transformations": [
{
"from": "Position means for, of, with, by, in, on, within.",
"to": ":POSITION = For, of, with, by, in, on, within",
"type": "colon_led_header"
},
{
"from": "pronoun is not allowed",
"to": "4=PRONOUN=NO-NO-NO",
"type": "equation_style_mapping"
},
{
"from": "document contract federal postal vessel court venue performance",
"to": "DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"type": "hyphen_chaining"
},
{
"from": "claim one. claim two. claim three.",
"to": "~1 claim-one\n~2 claim-two\n~3 claim-three",
"type": "tilde_line_marker"
}
],
"prompt_application": {
"input_type": "natural language, legal-style text, or source restatement",
"output_type": "qpsg-aligned structured text with preserved visual syntax markers",
"priority_order": [
"Preserve direct source punctuation and capitalization",
"Apply colon-led labels where the source shows definitional headers",
"Apply equals-sign mappings for direct code-term relations",
"Preserve hyphen compounds and abbreviations exactly",
"Use tilde numbering for discrete claim lines",
"Break long prose into stacked visible line units only when consistent with source style"
]
},
"examples": [
{
"input": "future tense is fiction",
"output": "9=FUTURE-TIME-TENSE=FICTION",
"note": "direct-style mapping example"
},
{
"input": "the document contract is in federal postal court venue performance",
"output": "DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE",
"note": "compound-chain example"
},
{
"input": "1. define position 2. state pronoun rule 3. state future rule",
"output": "~1 :POSITION = For, of, with, by, in, on, within\n~2 4=PRONOUN=NO-NO-NO\n~3 9=FUTURE-TIME-TENSE=FICTION",
"note": "stacked marker combination example"
}
],
"notes": [
"This module preserves visible syntax markers rather than claiming a complete grammar.",
"Some implementation guidance is inferred from repeated visual patterns rather than explicit procedural instructions.",
"Abbreviation preservation should defer to exact source spelling and punctuation whenever visible."
],
"limitations": [
"The source strongly demonstrates marker usage, but does not always define a full formal rule for each visual choice.",
"This module should be used with other rule modules for pronouns, tense, compounds, and numbered claims.",
"Examples are source-style operational examples, not quotations unless listed in source_quotes_or_clauses."
]
}
3. 09_compound_term_builder
{
"document_meta": {
"title": "09_compound_term_builder.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve source-grounded rules for building long hyphen-chained compound terms in QPSG-style document language.",
"purpose": "Provide a reusable JSON source module that identifies, preserves, and operationalizes the source's compound-term chaining patterns for future "source_quotes_or_clauses": [
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-CONTRACT-PERFORMANCE-COURT",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-TERMS",
"ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"PAPER-VESSEL-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE-CLAIM",
"CLOSED-AREA-PAPER-DOCUMENT-VESSEL-COURT-TERMS",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-SYNTAX-GRAMMAR-COURT-VENUE-PERFORMANCE"
],
"rules": [
{
"id": "CTB-01",
"rule": "Preserve source-visible compound chains exactly when they appear in the canon source.",
"basis": "direct-source",
"description": "Do not de-hyphenate or simplify a source-grounded compound term that is already presented as a fixed unit in the PDF."
},
{
"id": "CTB-02",
"rule": "Treat a multi-word compound as a single semantic unit when the source repeatedly chains those terms together.",
"basis": "inferred-from-source-pattern",
"description": "A repeated chain such as document-contract-federal-postal-court-venue functions operationally as one bundled label rather than as },
{
"id": "CTB-03",
"rule": "Build compounds from source-grounded categories only.",
"basis": "inferred-from-source-pattern",
"description": "Preferred chain elements come from recurring source domains such as document, contract, federal, postal, vessel, court, venue, performance, },
{
"id": "CTB-04",
"rule": "Use hyphen chaining when the prompt requests source-style rendering, controlled vocabulary preservation, or court-document formula language.",
"basis": "inferred-from-source-pattern",
"description": "Compound chaining is strongest in formal headings, venue labels, claim objects, and document descriptors."
},
{
"id": "CTB-05",
"rule": "Avoid inventing compound chains with unsupported source terms.",
"basis": "direct-source plus implementation safeguard",
"description": "Do not manufacture novel chains from modern, casual, or uncited vocabulary unless the individual terms are visibly grounded in the },
{
"id": "CTB-06",
"rule": "Prefer noun-domain chaining over conversational phrasing.",
"basis": "inferred-from-source-pattern",
"description": "The source tends to chain institutional and document nouns rather than descriptive everyday language."
},
{
"id": "CTB-07",
"rule": "Allow shorter compounds when a full chain would overstate certainty or exceed visible source support.",
"basis": "implementation guidance",
"description": "A shorter grounded chain is preferred over an overextended chain with weak source basis."
},
{
"id": "CTB-08",
"rule": "Preserve all-caps appearance when representing direct source compounds.",
"basis": "direct-source",
"description": "Direct source compounds are typically displayed in all caps and hyphenated segments."
}
],
"allowed_patterns": [
{
"pattern": "DOCUMENT-CONTRACT-*",
"notes": "Use when the chain starts from a document-contract object visibly present in the source."
},
{
"pattern": "*-FEDERAL-POSTAL-*",
"notes": "Use when the chain references the recurring federal-postal domain seen throughout the source."
},
{
"pattern": "*-VESSEL-*",
"notes": "Use when the object is framed in the source as a vessel, paper-vessel, contract-vessel, or document-vessel."
},
{
"pattern": "*-COURT-VENUE-*",
"notes": "Use when the source ties the chain to court and venue labeling."
},
{
"pattern": "*-PERFORMANCE",
"notes": "Use when the chain ends with the performance marker directly seen in the source."
},
{
"pattern": "ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"notes": "Preserve exactly as a full direct-source compound."
},
{
"pattern": "CLOSED-AREA-PAPER-DOCUMENT-VESSEL-COURT-TERMS",
"notes": "Preserve exactly as a full direct-source compound."
}
],
"disallowed_patterns": [
{
"pattern": "Mixing ungrounded casual terms into a source-style chain",
"reason": "The source supports heavy chaining, but not arbitrary modern vocabulary insertion."
},
{
"pattern": "De-hyphenating direct-source compounds into plain prose",
"reason": "This breaks the visible source syntax style."
},
{
"pattern": "Over-chaining beyond source support",
"reason": "Very long chains should still remain anchored to recurring source vocabulary and visible examples."
},
{
"pattern": "Treating every nearby word as automatically chainable",
"reason": "The source shows patterned chaining, not unlimited random concatenation."
}
],
"transformations": [
{
"name": "plain_phrase_to_source_compound",
"from": "document contract for the federal postal court venue",
"to": "DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE",
"basis": "direct-source-aligned"
},
{
"name": "plain_phrase_to_source_compound",
"from": "paper vessel federal postal court venue performance claim",
"to": "PAPER-VESSEL-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE-CLAIM",
"basis": "direct-source-aligned"
},
{
"name": "plain_phrase_to_source_compound",
"from": "closed area paper document vessel court terms",
"to": "CLOSED-AREA-PAPER-DOCUMENT-VESSEL-COURT-TERMS",
"basis": "direct-source-aligned"
},
{
"name": "controlled_extension",
"from": "document contract vessel court venue performance",
"to": "DOCUMENT-CONTRACT-VESSEL-COURT-VENUE-PERFORMANCE",
"basis": "inferred-from-recurring-elements",
"note": "Use only when the shorter compound remains fully grounded in source-visible chain elements."
}
],
"prompt_application": {
"input_type": "natural language or legal text",
"output_type": "qpsg-aligned structured text with controlled hyphen compounds",
"priority_order": [
"detect direct-source compound candidates",
"preserve exact compounds already present in source",
"identify whether the prompt requests source-style rendering",
"build compounds only from recurring source-grounded domains",
"avoid unsupported over-chaining",
"emit all-caps hyphen-chained forms when representing direct-source style"
]
},
"examples": [
{
"label": "direct preservation",
"input": "document-contract-federal-postal-court-venue",
"output": "DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE",
"type": "source-style rendering"
},
{
"label": "plain to chained",
"input": "original paper registered mail document venue",
"output": "ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"type": "source-grounded conversion"
},
{
"label": "compound caution",
"input": "modern business email contract process dashboard",
"output": "Do not chain as source-style compound without direct source grounding.",
"type": "disallowed expansion"
}
],
"notes": [
"The source strongly prefers hyphen-chained institutional compounds in formal document and claim language.",
"Many compound chains appear formulaic and function like controlled labels or fixed objects.",
"Some chaining behavior is visibly stylistic, so prompt use should prefer clearly grounded chains over speculative maximal chaining."
],
"limitations": [
"The source shows extensive examples of compound chaining but does not provide a complete formal grammar for every possible new chain.",
"This module preserves source-visible patterns and cautious implementation logic rather than claiming universal language rules.",
"Meaning and validity of the source claims are preserved as source posture only and are not independently verified here."
]
}
4. 10_abbreviation_map
{
"document_meta": {
"title": "10_abbreviation_map.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve and map source-visible abbreviation forms used in the QPSG source corpus, especially chained initialisms and code-style statutory "purpose": "Provide a reusable JSON source module that captures abbreviation forms, their direct or inferred expansions, and their prompt-use rules "source_quotes_or_clauses": [
"CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR-PERFORMANCE(C.-S.-S.-C.-P.-S.-G.-P.)",
"For the TERMS OF A C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT",
":C.-S.-S.-C.-P.-S.-G.-Flag",
"C-S-S-C-P-S-G",
":TITLE-~18: C.-S.-C.-S.-~1001 AND TITLR-~15: C.-S.-C.-S.-~78FF",
"D.-C.-C.-~9-b",
"D.-C.-C.-~60-b",
"TITLE~42: D.-C.-C.-S.-~1986",
"U.S.C.S.~2306~h",
"R.R.~512~588~123",
"DWMLC"
],
"rules": [
{
"id": "ABR-01",
"rule": "Preserve source-visible abbreviations exactly when they appear in the canon source.",
"basis": "direct-source",
"description": "Do not normalize punctuation, remove dots, or modernize a direct-source abbreviation when preserving canon form."
},
{
"id": "ABR-02",
"rule": "Map each abbreviation to its expansion only when the expansion is explicit or directly inferable from adjacent source text.",
"basis": "direct-source plus constrained inference",
"description": "Expansions may be recorded as direct-source or inferred-expansion, but inferred expansions must stay tightly anchored to local source },
{
"id": "ABR-03",
"rule": "Treat punctuation-bearing initialism chains as controlled labels rather than casual shorthand.",
"basis": "inferred-from-source-pattern",
"description": "Forms such as C.-S.-S.-C.-P.-S.-G.-P. function like named systems, headings, or doctrine labels inside the source."
},
{
"id": "ABR-04",
"rule": "Preserve variant spellings or punctuation variants as separate entries when the source uses more than one visible form.",
"basis": "direct-source",
"description": "Examples include dotted versus undotted or hyphen-chain variations such as C.-S.-S.-C.-P.-S.-G. and C-S-S-C-P-S-G."
},
{
"id": "ABR-05",
"rule": "Do not invent new abbreviation families not grounded in the source PDF.",
"basis": "implementation safeguard",
"description": "Only record abbreviations that visibly appear in the source or are strictly inferable from an explicit expansion."
},
{
"id": "ABR-06",
"rule": "Keep uncertain expansions marked uncertain rather than overstating certainty.",
"basis": "implementation safeguard",
"description": "Where the source shows an abbreviation but does not fully define it, preserve the form and flag the meaning as unclear or partial."
}
],
"allowed_patterns": [
{
"pattern": "Punctuated initialism chain such as C.-S.-S.-C.-P.-S.-G.-P.",
"notes": "Use as a source label when the exact chain is present in the source."
},
{
"pattern": "Undotted variant such as C-S-S-C-P-S-G",
"notes": "Preserve as its own visible source variant rather than collapsing it automatically into the dotted form."
},
{
"pattern": "Code-style abbreviation with section marker such as D.-C.-C.-~60-b",
"notes": "Use as a direct-source code reference when the exact form is visible in the PDF."
},
{
"pattern": "Statutory compact marker such as U.S.C.S.~2306~h or R.R.~512~588~123",
"notes": "Preserve exact punctuation and tilde sequencing."
}
],
"disallowed_patterns": [
{
"pattern": "Invented expansions with no visible source basis",
"reason": "This would exceed canon-preservation and blur direct source with speculation."
},
{
"pattern": "Removing dots, dashes, or tildes from a direct-source abbreviation",
"reason": "The punctuation is part of the visible source form."
},
{
"pattern": "Collapsing distinct variants into one form without noting the variant",
"reason": "The source uses multiple visible abbreviation forms that should remain distinguishable."
},
{
"pattern": "Treating uncertain code abbreviations as definitively decoded when the PDF does not decode them",
"reason": "Uncertainty should be preserved honestly."
}
],
"transformations": [
{
"name": "preserve_direct_initialism_chain",
"from": "Correct Sentence Structure Communication Parse Syntax Grammar Performance",
"to": "C.-S.-S.-C.-P.-S.-G.-P.",
"basis": "direct-source"
},
{
"name": "preserve_variant_flag_label",
"from": "C S S C P S G Flag",
"to": ":C.-S.-S.-C.-P.-S.-G.-Flag",
"basis": "direct-source-aligned formatting"
},
{
"name": "retain_code_reference",
"from": "D C C 60 b",
"to": "D.-C.-C.-~60-b",
"basis": "direct-source"
},
{
"name": "retain_compact_statutory_marker",
"from": "USCS 2306 h",
"to": "U.S.C.S.~2306~h",
"basis": "direct-source"
}
],
"prompt_application": {
"input_type": "natural language, legal text, or source-style labels",
"output_type": "qpsg-aligned structured text with preserved abbreviation forms",
"priority_order": [
"detect direct-source abbreviations already present in the input",
"preserve exact punctuation-bearing source forms",
"map to expansions only when explicit or tightly inferable from adjacent source text",
"record visible variants as separate entries",
"flag uncertain expansions instead of inventing certainty",
"emit abbreviation form appropriate to heading, flag, code, or label context"
]
},
"examples": [
{
"label": "direct-source expansion",
"input": "CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR-PERFORMANCE",
"output": "C.-S.-S.-C.-P.-S.-G.-P.",
"type": "direct-source abbreviation"
},
{
"label": "variant preservation",
"input": "C-S-S-C-P-S-G",
"output": "C-S-S-C-P-S-G",
"type": "visible source variant preserved"
},
{
"label": "uncertain decode handling",
"input": "D.-C.-C.-~9-b",
"output": "Preserve exact code form and mark expansion as uncertain if no explicit source decode appears nearby.",
"type": "uncertainty-preserving handling"
}
],
"notes": [
"The strongest explicit abbreviation mapping in the source is C.-S.-S.-C.-P.-S.-G.-P. paired with its expanded phrase CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-"The source also shows visible variant forms, including dotted, undotted, and suffixed label variants such as :C.-S.-S.-C.-P.-S.-G.-Flag.",
"Several code-style abbreviations appear without a full in-text decoding nearby; those are preserved as forms rather than over-decoded."
],
"limitations": [
"Not every abbreviation in the PDF is fully decoded by adjacent source text, so some entries remain partial or uncertain by design.",
"This module preserves source posture and visible abbreviation behavior rather than claiming authoritative external meanings.",
"Where the source contains typographic irregularities such as TITLR versus TITLE, the visible source form may be preserved in quotes while normalized ],
"abbreviation_entries": [
{
"abbreviation": "C.-S.-S.-C.-P.-S.-G.-P.",
"expanded_form": "CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR-PERFORMANCE",
"mapping_basis": "direct-source",
"usage_notes": "Appears as a named performance/system label and as a document-contract modifier.",
"variant_forms": [
"C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT"
]
},
{
"abbreviation": "C.-S.-S.-C.-P.-S.-G.",
"expanded_form": "CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR",
"mapping_basis": "inferred-expansion-from-adjacent-source-pattern",
"usage_notes": "Inferred from the fully expanded performance form and the visible flag label.",
"variant_forms": [
":C.-S.-S.-C.-P.-S.-G.-Flag",
"C-S-S-C-P-S-G"
]
},
{
"abbreviation": "C-S-S-C-P-S-G",
"expanded_form": "CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR",
"mapping_basis": "inferred-expansion-from-variant-family",
"usage_notes": "Undotted visible variant appearing in address/signature-style lines.",
"variant_forms": [
"C.-S.-S.-C.-P.-S.-G."
]
},
{
"abbreviation": "D.-C.-C.-~9-b",
"expanded_form": "uncertain",
"mapping_basis": "source-form-preserved; no fully explicit local decode captured here",
"usage_notes": "Appears as a compact code reference in numbered claim lines.",
"variant_forms": [
"D.-C.-C.-~60-b"
]
},
{
"abbreviation": "D.-C.-C.-~60-b",
"expanded_form": "uncertain",
"mapping_basis": "source-form-preserved; no fully explicit local decode captured here",
"usage_notes": "Appears as a closure/facts code reference in numbered claim lines.",
"variant_forms": [
"D.-C.-C.-~9-b"
]
},
{
"abbreviation": "D.-C.-C.-S.-~1986",
"expanded_form": "uncertain",
"mapping_basis": "source-form-preserved; no fully explicit local decode captured here",
"usage_notes": "Appears in TITLE~42 code-style reference form.",
"variant_forms": []
},
{
"abbreviation": "U.S.C.S.~2306~h",
"expanded_form": "U.S.C.S. compact citation form exactly as shown",
"mapping_basis": "direct-source-form",
"usage_notes": "Preserve exact punctuation and tilde placement.",
"variant_forms": []
},
{
"abbreviation": "R.R.~512~588~123",
"expanded_form": "R.R. compact citation form exactly as shown",
"mapping_basis": "direct-source-form",
"usage_notes": "Preserve exact punctuation and tilde placement.",
"variant_forms": []
},
{
"abbreviation": "DWMLC",
"expanded_form": "uncertain or organizational signature marker",
"mapping_basis": "source-form-preserved",
"usage_notes": "Appears in signature/contact line near David-Wynn: Miller reference.",
"variant_forms": []
}
]
}
