QPSG Section 4 - Document Application Pack
Cleaned and normalized from the provided Section 4 text. This pack contains modules 11, 12, 13, and 14 only.
1. 11_document_contract_templates
{
"document_meta": {
"title": "11_document_contract_templates.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve recurring document-contract formula patterns, fillable source-style templates, and reusable clause skeletons visible in the source PDF.",
"purpose": "Provide a JSON source module that captures named document-contract templates for future prompt use and PDF source uploads, while preserving "source_quotes_or_clauses": [
"For the CORRECT-SENTENCE-STRUCTURE-COMMUNICATION-PARSE-SYNTAX-GRAMMAR-PERFORMANCE(C.-S.-S.-C.-P.-S.-G.-P.) of this DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-"For the DOCUMENT-CONTRACT-PAPER-VESSEL of the QUO-WARRANTO-COMPLAINT",
"PAPER-VESSEL-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE-CLAIM",
"CLOSED-AREA-PAPER-DOCUMENT-VESSEL-COURT-TERMS",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"by an ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE"
],
"rules": [
{
"id": "DCT-01",
"rule": "Preserve recurring document-contract clause skeletons as reusable templates when the same structural pattern appears more than once in the "basis": "direct-source plus constrained template extraction"
},
{
"id": "DCT-02",
"rule": "Keep template names grounded in source-visible compound phrases rather than modern legal labels.",
"basis": "direct-source"
},
{
"id": "DCT-03",
"rule": "Separate direct source phrases from fillable slots added for prompt reuse.",
"basis": "implementation safeguard"
},
{
"id": "DCT-04",
"rule": "Retain compound-term chaining and source-style sequencing inside template patterns.",
"basis": "direct-source"
},
{
"id": "DCT-05",
"rule": "Do not overstate these templates as validated legal forms.",
"basis": "limitation safeguard"
}
],
"allowed_patterns": [
{
"pattern": "For the [compound-source-term] of this DOCUMENT-CONTRACT-[compound-source-term]",
"notes": "Core source formula opener used for template preservation."
},
{
"pattern": "For the DOCUMENT-CONTRACT-PAPER-VESSEL of the QUO-WARRANTO-COMPLAINT",
"notes": "Direct-source complaint template anchor."
},
{
"pattern": "by an ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"notes": "Direct-source filing or service style marker."
},
{
"pattern": "For this AMICUS-CURIE-VESSEL-DOCUMENT of this SERVICE",
"notes": "Direct-source response/service template anchor."
}
],
"disallowed_patterns": [
{
"pattern": "Modernized plain-English contract or lawsuit templates with source compounds removed",
"reason": "This would break canon-preservation and erase source structure."
},
{
"pattern": "Invented document titles not visibly grounded in the source PDF",
"reason": "Template names must remain source-anchored."
},
{
"pattern": "Presenting fillable fields as if they were verbatim source text",
"reason": "Prompt slots are implementation support and must stay distinguishable from the source."
}
],
"transformations": [
{
"name": "plain_complaint_to_source_template",
"from": "Complaint for quo warranto",
"to": "DOCUMENT-CONTRACT-PAPER-VESSEL of the QUO-WARRANTO-COMPLAINT",
"basis": "direct-source-aligned compounding"
},
{
"name": "plain_filing_to_registered_mail_venue",
"from": "filed by registered mail",
"to": "by an ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"basis": "direct-source"
},
{
"name": "plain_service_response_to_amicus_template",
"from": "service document requiring answer back",
"to": "AMICUS-CURIE-VESSEL-DOCUMENT of this SERVICE ... ANSWERING-BACK of the TEN-DAY-TRUST-LAWS",
"basis": "direct-source-aligned extraction"
}
],
"prompt_application": {
"input_type": "natural language or legal text requesting a source-style document shell",
"output_type": "qpsg-aligned source-template entries and fillable document-contract clauses",
"priority_order": [
"identify the closest direct-source template family",
"preserve source compounds and ordering",
"add fillable support slots only where useful",
"mark inferred slots as implementation support",
"avoid modern legal rewrites"
]
},
"examples": [
{
"name": "quo_warranto_template_example",
"type": "source-style example",
"before": "Create a quo warranto complaint template.",
"after": "For the DOCUMENT-CONTRACT-PAPER-VESSEL of the QUO-WARRANTO-COMPLAINT are with the PAPER-VESSEL-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE-CLAIM "note": "Derived from direct-source clause structure."
},
{
"name": "registered_mail_template_example",
"type": "source-style example",
"before": "Create a registered mail filing clause.",
"after": "For the C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT of the FACTS are with these CLAIMS ... by an ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE.",
"note": "Condensed from direct-source wording."
},
{
"name": "service_answer_back_template_example",
"type": "source-style example",
"before": "Create a service document requiring a response.",
"after": "For this AMICUS-CURIE-VESSEL-DOCUMENT of this SERVICE is with an ANSWERING-BACK of the TEN-DAY-TRUST-LAWS or with the QUO-WARRANTO-COMPLAINT-"note": "Direct-source response/service template anchor."
}
],
"notes": [
"Template extraction here is modularized from repeated source formulas rather than copied as a full document.",
"Fillable slots are intentionally conservative because the source gives formula language more clearly than a complete form schema.",
"The source strongly favors document, contract, vessel, venue, performance, claimant, and complaint compounds as reusable building blocks."
],
"limitations": [
"The source provides strong clause patterns but not a complete standardized field list for every document type.",
"Some template boundaries are inferred from repeated phrase families rather than explicitly labeled by the source as templates.",
"This module preserves source posture only and does not provide legal advice or validated court filing guidance."
]
}
2. 12_venue_vessel_court_lexicon
{
"document_meta": {
"title": "12_venue_vessel_court_lexicon.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Controlled vocabulary preservation for venue, vessel, court, postal, federal, port, dry-dock, jurisdiction, performance, and claimant-adjacent "purpose": "Provide a concise lexicon module for future JSON prompts so source-style text can reuse the source’s recurring venue/vessel/court terminology "source_quotes_or_clauses": [
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"IN THE C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-VENUE-PERFORMANCE",
"DOCUMENT-CONTRACT-POSTAL-VESSEL-COURT-VENUE-JURISDICTION OF THE FEDERAL-COURT-BUILDING",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-VESSEL-COURT-TERMS",
"ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE",
"DOCUMENT-CONTRACT-PAPER-VESSEL",
"PAPER-VESSEL-FEDERAL-POSTAL-COURT-VENUE-PERFORMANCE-CLAIM",
"CLOSED-AREA-PAPER-DOCUMENT-VESSEL-COURT-TERMS",
"DRY-DOCK-VESSEL-COURTHOUSE-BUILDING",
"CLERK-PORT-AUTHORITIES"
],
"rules": [
{
"id": "lexicon-01",
"rule": "Prefer the source’s compound venue/vessel/court terms when a prompt needs forum, place, performance, filing, or jurisdiction language.",
"basis": "direct-source"
},
{
"id": "lexicon-02",
"rule": "Preserve multi-part compounds exactly when they appear as recurring fixed expressions in the source.",
"basis": "direct-source"
},
{
"id": "lexicon-03",
"rule": "When implementing prompts, use concise term-level mappings only as support; do not replace direct source compounds when a direct phrase exists.",
"basis": "inferred-operational"
}
],
"allowed_patterns": [
"document-contract-*",
"*-postal-*",
"*-vessel-*",
"*-court-*",
"*-venue-*",
"*-jurisdiction",
"*-performance",
"*-port-authorities"
],
"disallowed_patterns": [
"Replacing source compounds with simplified modern legal paraphrases inside canon-preservation outputs",
"Inventing venue/vessel/court compounds not grounded in the source",
"Treating this lexicon as independent legal advice or universal terminology"
],
"transformations": [
{
"from": "court filing venue",
"to": "document-contract-federal-postal-vessel-court-venue-performance",
"type": "inferred implementation support"
},
{
"from": "mail venue",
"to": "original-paper-registered-mail-document-venue",
"type": "inferred implementation support"
},
{
"from": "paper complaint in court",
"to": "document-contract-paper-vessel with the paper-vessel-federal-postal-court-venue-performance-claim",
"type": "inferred implementation support"
}
],
"prompt_application": {
"input_type": "natural language or legal-style text needing source-aligned venue/court terminology",
"output_type": "qpsg-aligned text using controlled lexicon terms",
"priority_order": [
"detect direct source compounds first",
"select lexicon term by forum/place/performance function",
"preserve exact compound if source phrase exists",
"use inferred mapping only where the source shows a clear pattern"
]
},
"examples": [
{
"input": "File the complaint in the federal court venue.",
"output": "File the complaint with the document-contract-federal-postal-court-venue.",
"basis": "inferred from direct source compounds"
},
{
"input": "Use the original mailed document as the venue paper.",
"output": "Use the original-paper-registered-mail-document-venue.",
"basis": "direct-source phrase"
},
{
"input": "This courthouse building starts the case.",
"output": "This dry-dock-vessel-courthouse-building starts the damage-claim.",
"basis": "inferred from direct source phrase"
}
],
"notes": [
{
"term": "document-contract-federal-postal-vessel-court-venue-performance",
"source_context": "Primary long-form compound tying document, contract, postal, vessel, court, venue, and performance together.",
"concise_meaning_in_source": "A preferred source compound for forum/performance context.",
"related_terms": [
"document-contract-federal-postal-court-venue",
"document-contract-federal-postal-vessel-court-terms"
],
"preferred_usage": "Use when prompts need the source’s fullest venue-performance expression."
},
{
"term": "venue",
"source_context": "Appears in repeated compounds such as court-venue and document-venue.",
"concise_meaning_in_source": "Forum/place component inside source compounds.",
"related_terms": [
"jurisdiction",
"performance",
"court"
],
"preferred_usage": "Prefer inside source compounds rather than alone."
},
{
"term": "vessel",
"source_context": "Appears in postal-vessel-court, paper-vessel, and contract-vessel compounds.",
"concise_meaning_in_source": "Container/document/forum component as used by source wording.",
"related_terms": [
"paper-vessel",
"document-contract-paper-vessel",
"contract-vessel-closed-document"
],
"preferred_usage": "Retain as source vocabulary; do not normalize away."
},
{
"term": "court",
"source_context": "Appears in federal-court-building, vessel-court, courthouse-building, and court-terms compounds.",
"concise_meaning_in_source": "Forum/institution component embedded in compounds.",
"related_terms": [
"federal-court-building",
"courthouse-building",
"court-terms"
],
"preferred_usage": "Prefer compound use."
},
{
"term": "postal",
"source_context": "Repeated in federal-postal-court and postal-vessel forms.",
"concise_meaning_in_source": "Postal qualifier within source court/venue compounds.",
"related_terms": [
"federal-postal",
"registered-mail",
"postmaster"
],
"preferred_usage": "Keep when present in source compound."
},
{
"term": "federal",
"source_context": "Paired with postal and court-building in multiple clauses.",
"concise_meaning_in_source": "Federal qualifier inside venue/court compounds.",
"related_terms": [
"federal-postal-court-venue",
"federal-court-building"
],
"preferred_usage": "Use with source-paired compounds."
},
{
"term": "jurisdiction",
"source_context": "Appears in document-contract-postal-vessel-court-venue-jurisdiction.",
"concise_meaning_in_source": "Jurisdiction component inside a larger venue compound.",
"related_terms": [
"venue",
"court",
"federal-court-building"
],
"preferred_usage": "Prefer the full compound where possible."
},
{
"term": "performance",
"source_context": "Appears in venue-performance and performance-claim compounds.",
"concise_meaning_in_source": "Execution/performance component of source forum language.",
"related_terms": [
"venue-performance",
"performance-claim"
],
"preferred_usage": "Use inside compound expressions."
},
{
"term": "original-paper-registered-mail-document-venue",
"source_context": "Standalone compound in the source.",
"concise_meaning_in_source": "Registered-mail document venue phrase.",
"related_terms": [
"document-venue",
"registered-mail"
],
"preferred_usage": "Use when prompts refer to mailed original paper."
},
{
"term": "document-contract-paper-vessel",
"source_context": "Appears in the quo warranto complaint clause.",
"concise_meaning_in_source": "Paper/document vessel phrase.",
"related_terms": [
"paper-vessel-federal-postal-court-venue-performance-claim"
],
"preferred_usage": "Use when the prompt centers paper-as-vessel wording."
},
{
"term": "paper-vessel-federal-postal-court-venue-performance-claim",
"source_context": "Extended complaint-related compound.",
"concise_meaning_in_source": "Paper-vessel claim phrase tied to court/venue/performance.",
"related_terms": [
"document-contract-paper-vessel",
"closed-area-paper-document-vessel-court-terms"
],
"preferred_usage": "Use for claim-level prompt outputs when source style is desired."
},
{
"term": "closed-area-paper-document-vessel-court-terms",
"source_context": "Appears in complaint/court-terms clause.",
"concise_meaning_in_source": "Closed-area court-terms phrase for paper/document vessel context.",
"related_terms": [
"court-terms",
"paper-vessel"
],
"preferred_usage": "Preserve exactly if used."
},
{
"term": "dry-dock-vessel-courthouse-building",
"source_context": "Appears in the start-date clause.",
"concise_meaning_in_source": "Courthouse-building compound framed as vessel/dry-dock.",
"related_terms": [
"federal-court-building",
"courthouse-building"
],
"preferred_usage": "Use only when directly matching source style."
},
{
"term": "clerk-port-authorities",
"source_context": "Appears in claimant-against clause.",
"concise_meaning_in_source": "Port-authority wording attached to clerk duties.",
"related_terms": [
"postmasters",
"clerk",
"port-authorities"
],
"preferred_usage": "Preserve in clerk/failure/duty contexts."
}
],
"limitations": [
"This module preserves source vocabulary and prompt-use guidance only.",
"Concise meanings are descriptive summaries of source usage, not endorsements or legal definitions.",
"Some mappings in transformations are inferred implementation support because the source gives recurring compounds more clearly than explicit conversion ]
}
3. 13_exclusion_and_void_outside_modes
{
"document_meta": {
"title": "13_exclusion_and_void_outside_modes.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Preserve source claims that exclude, void, or reject outside grammar modes, foreign paper, foreign parse-syntax-grammar fiction laws, rules, codes, "purpose": "Provide a concise JSON source module for future prompts so source-style outputs can identify and filter source-flagged outside modes while clearly "source_quotes_or_clauses": [
"VOID-OUTSIDE-CLAIMS of a FOREIGN-PAPER, FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION-LAWS, RULES, CODES, OR: REGULATIONS",
"MODIFICATION-FICTION-PRONOUN-ADVERB-VERB-SYNTAX-GRAMMAR",
"ADVERB-ADJECTIVE-PRONOUN-SYNTAX-GRAMMAR",
"ADVERB-VERB-ADVERB-VERB-ADVERB-VERB-SYNTAX-GRAMMAR",
"ADJECTIVE-PRONOUN-SYNTAX-GRAMMAR",
"by the FRAUDULENT-SYNTAX-GRAMMAR",
"For the TERMS OF A C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT of the FACTS ARE with the WORD-TERM-CLAIMS",
"future-tense is with the void by a now-time-contract"
],
"rules": [
{
"id": "EXC-01",
"rule": "Preserve the source's direct exclusion posture toward outside claims and foreign paper modes.",
"basis": "direct-source",
"description": "The source expressly frames certain outside claims, foreign paper, and foreign parse-syntax-grammar fiction laws, rules, codes, and },
{
"id": "EXC-02",
"rule": "Treat named modification-fiction grammar clusters as source-flagged disallowed modes.",
"basis": "direct-source",
"description": "The source explicitly lists pronoun/adverb/verb/adjective combinations as modification-fiction or fraudulent syntax-grammar patterns."
},
{
"id": "EXC-03",
"rule": "Keep direct source exclusions separate from implementation filters added for prompt handling.",
"basis": "implementation safeguard",
"description": "Prompt filters may summarize the source's exclusion posture, but they must not be presented as broader universal language laws."
},
{
"id": "EXC-04",
"rule": "When rewriting into source style, prefer source-marked fact, word-term, and document-contract language over excluded outside-mode wording.",
"basis": "direct-source plus constrained implementation",
"description": "Transformations should move text toward the source's fact and word-term posture instead of preserving language the source marks as foreign, },
{
"id": "EXC-05",
"rule": "Do not state these exclusions as validated legal or linguistic truth outside the source corpus.",
"basis": "limitation safeguard",
"description": "This module preserves the source's internal exclusion logic only."
}
],
"allowed_patterns": [
{
"pattern": "WORD-TERM-CLAIMS of the DOCUMENT-CONTRACT-[compound-source-term]",
"notes": "Source-preferred fact/claim posture contrasted with outside claims."
},
{
"pattern": "For the TERMS OF A C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT of the FACTS",
"notes": "Direct-source fact-anchor used alongside the exclusion cluster."
},
{
"pattern": "now-time-contract",
"notes": "Direct-source time anchor used to void future-tense in the source framework."
},
{
"pattern": "VOID-OUTSIDE-CLAIMS of a FOREIGN-PAPER ...",
"notes": "Direct-source exclusion formula."
}
],
"disallowed_patterns": [
{
"pattern": "FOREIGN-PAPER",
"reason": "Directly named by the source as part of the void-outside-claims cluster."
},
{
"pattern": "FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION-LAWS, RULES, CODES, OR: REGULATIONS",
"reason": "Direct-source exclusion phrase."
},
{
"pattern": "MODIFICATION-FICTION-PRONOUN-ADVERB-VERB-SYNTAX-GRAMMAR",
"reason": "Directly listed as a flagged fiction-grammar mode."
},
{
"pattern": "ADVERB-ADJECTIVE-PRONOUN-SYNTAX-GRAMMAR",
"reason": "Directly listed as a flagged fiction-grammar mode."
},
{
"pattern": "ADVERB-VERB-ADVERB-VERB-ADVERB-VERB-SYNTAX-GRAMMAR",
"reason": "Directly listed as a flagged fiction-grammar mode."
},
{
"pattern": "ADJECTIVE-PRONOUN-SYNTAX-GRAMMAR",
"reason": "Directly listed as a flagged fiction-grammar mode."
},
{
"pattern": "future-tense language in a source-style output",
"reason": "The source states that future-tense is with the void by a now-time-contract."
}
],
"transformations": [
{
"name": "outside_claim_to_word_term_claim",
"from": "outside legal or regulatory claim language",
"to": "WORD-TERM-CLAIMS of the DOCUMENT-CONTRACT-[source-compound-term]",
"basis": "direct-source-aligned replacement"
},
{
"name": "future_tense_to_now_time_contract",
"from": "will / shall / future-event phrasing",
"to": "now-time-contract phrasing",
"basis": "direct-source time exclusion"
},
{
"name": "pronoun_modification_cluster_to_named_terms",
"from": "pronoun-adverb-verb or adjective-pronoun clusters",
"to": "named roles, claimant terms, defined word-term chains",
"basis": "source-aligned implementation"
},
{
"name": "foreign_paper_to_document_contract",
"from": "foreign paper language",
"to": "DOCUMENT-CONTRACT / PAPER-VESSEL / ORIGINAL-PAPER-REGISTERED-MAIL-DOCUMENT-VENUE phrasing where supported",
"basis": "source compound preference"
}
],
"prompt_application": {
"input_type": "natural language, legal-style text, or source-style text needing outside-mode filtering",
"output_type": "qpsg-aligned source-preservation text with excluded outside modes flagged or rewritten",
"priority_order": [
"detect direct outside-mode markers named in the source",
"flag fiction-grammar clusters the source lists explicitly",
"replace future-tense with now-time-contract posture where needed",
"replace pronoun-heavy or undefined clusters with named word-term claims",
"re-anchor output to fact/document-contract/source compounds"
]
},
"examples": [
{
"name": "outside_claim_filter_example",
"type": "source-style example",
"before": "Use outside regulatory language to support the claim.",
"after": "For the TERMS OF A C.-S.-S.-C.-P.-S.-G.-P.-DOCUMENT-CONTRACT of the FACTS are with the WORD-TERM-CLAIMS ... with the VOID-OUTSIDE-CLAIMS of "note": "Condensed from the direct exclusion clause."
},
{
"name": "future_tense_void_example",
"type": "source-style example",
"before": "The claimant will provide the proof.",
"after": "The claimant proof is with the now-time-contract.",
"note": "Implementation example derived from the source's future-tense void posture."
},
{
"name": "fiction_cluster_rewrite_example",
"type": "source-style example",
"before": "He quickly argues it unfairly.",
"after": "The claimant argument is with the WORD-TERM-CLAIMS of the FACTS.",
"note": "Implementation example showing movement away from source-flagged pronoun/adverb/verb clusters."
}
],
"notes": [
"The strongest exclusion wording appears inside the fact-terms/document-contract clause cluster rather than as a standalone rule list.",
"This module combines direct-source exclusions with narrowly labeled prompt-handling guidance so later prompts can apply the source posture consistently.",
"Several excluded modes overlap with the separate pronoun, tense, and fact-vs-fiction modules and should be used together rather than treated as independent ],
"limitations": [
"The source gives an exclusion posture and several named disallowed clusters, but it does not define a complete general-purpose filtering grammar for "Some transformation guidance here is inferred for prompt application and is not verbatim source wording.",
"This module preserves source claims only and does not validate them as legal, linguistic, or procedural truth."
]
}
4. 14_transformation_pipeline
{
"document_meta": {
"title": "14_transformation_pipeline.json.pdf",
"version": "1.0",
"source_basis": "Untitled 1.pdf",
"mode": "canon-preservation",
"format": "json-source-for-pdf"
},
"scope": "Create an operational transformation order, derived from source patterns, for applying the separate preserved rule modules in a consistent sequence.",
"purpose": "Provide a concise pipeline for future prompts that transforms plain input into source-aligned structured output while clearly separating direct-"source_quotes_or_clauses": [
"4=PRONOUN=NO-NO-NO",
"5=POSITION = ALPHABET-LETTERS, WORD-SPELLINGS, DEFINITION-TERMS AND OPERATIONS",
"6=LODIAL=OWNERSHIP OF THE MATTER, EQUITY",
"7=FACT-CONTRACT-OPERATIONS",
"8=PAST-TIME-TENSE",
"9=FUTURE-TIME-TENSE=FICTION",
"future-tense is with the void by a now-time-contract",
"VOID-OUTSIDE-CLAIMS",
"FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION-LAWS, RULES, CODES, OR: REGULATIONS",
"DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE",
"~1",
"~2",
"~3"
],
"rules": [
{
"id": "pipeline-01",
"rule": "Apply direct-source exclusion and defect markers before formatting refinements.",
"basis": "inferred-implementation from source priorities"
},
{
"id": "pipeline-02",
"rule": "Resolve pronoun, tense, and undefined-term issues before compound-building or claim-line formatting.",
"basis": "inferred-implementation"
},
{
"id": "pipeline-03",
"rule": "Prefer direct-source terminology and visible source formatting where the source provides it.",
"basis": "direct-source plus inferred sequencing"
},
{
"id": "pipeline-04",
"rule": "Keep every transformation stage labeled as either direct-source grounded or inferred implementation support.",
"basis": "inferred-implementation"
}
],
"allowed_patterns": [
"Stage-by-stage transformation order",
"Direct-source checks before style polishing",
"Use of source-preferred compounds and lexicon",
"Sequential numbered claim-line output at the final formatting stage"
],
"disallowed_patterns": [
"Applying visual formatting before correcting direct-source defect markers",
"Leaving pronouns unresolved when a source-style replacement is available",
"Keeping future-tense fiction markers when converting to source-aligned now-time phrasing",
"Using generic substitutes where a preserved source-preferred term is directly available"
],
"transformations": [
{
"name": "outside_mode_filter",
"from": "Text containing source-flagged outside-mode or foreign fictional language markers.",
"to": "Text filtered or rewritten to remove or isolate source-flagged outside-mode patterns.",
"basis": "direct-source exclusion posture plus inferred sequencing"
},
{
"name": "pronoun_resolution",
"from": "Text containing disallowed or defective pronoun references.",
"to": "Text with repeated names, roles, claimant labels, or object-specific terms.",
"basis": "direct-source pronoun prohibition plus inferred replacement support"
},
{
"name": "tense_normalization",
"from": "Text containing future-tense fiction markers.",
"to": "Text rewritten into present or now-time contract phrasing where possible.",
"basis": "direct-source future-tense posture plus inferred conversion support"
},
{
"name": "definition_and_position_anchoring",
"from": "Text with vague, undefined, or loosely placed terms.",
"to": "Text anchored by exact spellings, titles, positions, and definition terms.",
"basis": "direct-source key-5 wording"
},
{
"name": "source_term_substitution",
"from": "Generic legal or descriptive wording.",
"to": "Source-preferred lexicon such as CLAIMANT, QUO-WARRANTO-COMPLAINT, or DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE when directly supported.",
"basis": "inferred-implementation from recurring source vocabulary"
},
{
"name": "compound_building",
"from": "Separate source-supported terms in ordinary phrase form.",
"to": "Hyphen-chained compounds following visible source patterns.",
"basis": "direct-source visual style plus inferred assembly guidance"
},
{
"name": "claim_line_formatting",
"from": "Plain prose or paragraph-form output.",
"to": "Sequential tilde-numbered claim lines such as ~1, ~2, ~3.",
"basis": "direct visible source numbering plus inferred final formatting stage"
}
],
"prompt_application": {
"input_type": "natural language, legal-style prose, or source-style draft text",
"output_type": "qpsg-aligned structured text using source-preserved terminology and final numbered-claim formatting",
"priority_order": [
"1 detect and isolate source-flagged outside-mode or foreign-fiction patterns",
"2 detect pronouns and replace with repeated names, titles, roles, or exact object terms",
"3 detect tense markers and normalize future-tense fiction into present or now-time phrasing where possible",
"4 anchor wording by position, spelling precision, and definition terms",
"5 substitute generic wording with source-preferred vocabulary when directly supported",
"6 build source-style hyphen compounds from supported term clusters",
"7 apply venue/vessel/court lexicon where relevant",
"8 apply visual syntax markers and caption lines where appropriate",
"9 format the final output into sequential numbered claim lines"
]
},
"pipeline_stages": [
{
"stage": 1,
"name": "detect_outside_mode_patterns",
"type": "direct-source grounded with inferred sequencing",
"description": "Scan for source-flagged outside-mode language such as VOID-OUTSIDE-CLAIMS conflicts or FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION clusters."
},
{
"stage": 2,
"name": "resolve_pronoun_defects",
"type": "direct-source grounded with inferred replacement support",
"description": "Identify pronouns and replace them with repeated names, claimant labels, titles, or exact object terms."
},
{
"stage": 3,
"name": "normalize_tense",
"type": "direct-source grounded with inferred conversion support",
"description": "Identify future-tense fiction markers and convert them to present or now-time contract phrasing where feasible."
},
{
"stage": 4,
"name": "anchor_definition_terms",
"type": "direct-source grounded",
"description": "Strengthen position, spelling, and definition precision using the key-5 position/definition rule set."
},
{
"stage": 5,
"name": "apply_canonical_terms",
"type": "inferred-implementation from recurring source vocabulary",
"description": "Replace generic wording with source-preferred recurring terms when the source directly supports the substitution."
},
{
"stage": 6,
"name": "build_compound_terms",
"type": "direct-source visible style with inferred assembly guidance",
"description": "Chain supported terms into source-style hyphen compounds."
},
{
"stage": 7,
"name": "apply_controlled_lexicon",
"type": "direct-source grounded",
"description": "Insert venue, vessel, court, filing, or ownership lexicon where relevant to the transformed statement."
},
{
"stage": 8,
"name": "apply_visual_markers",
"type": "direct-source visible style with inferred formatting sequence",
"description": "Add source-style markers such as caption lines, colon-led labels, or visible header markers where appropriate."
},
{
"stage": 9,
"name": "format_numbered_claim_lines",
"type": "direct-source visible style with inferred final formatting sequence",
"description": "Render the final transformed content as tilde-numbered claim lines such as ~1, ~2, ~3."
}
],
"examples": [
{
"before": "He will file the complaint in the court and send it by registered mail.",
"after": "~1 The CLAIMANT files the QUO-WARRANTO-COMPLAINT.\n~2 The DOCUMENT-CONTRACT-FEDERAL-POSTAL-COURT-VENUE is with the matter.\n~3 The CLAIMANT
"stage_notes": [
"Pronoun 'He' replaced with CLAIMANT.",
"Future marker 'will' normalized to present-time phrasing.",
"Generic terms replaced with recurring source-preferred compounds.",
"Final output rendered as numbered claim lines."
]
},
{
"before": "The outside rules will control the case later.",
"after": "~1 The VOID-OUTSIDE-CLAIMS posture rejects the FOREIGN-PARSE-SYNTAX-GRAMMAR-FICTION-LAWS, RULES, CODES, OR: REGULATIONS.\n~2 The FACT-CONTRACT-"stage_notes": [
"Outside-mode language flagged and rewritten using source exclusion posture.",
"Future-tense marker normalized away from later-time phrasing.",
"Final output rendered as numbered claim lines."
]
}
],
"notes": [
"The source does not present a single fully ordered transformation algorithm; this module assembles one from repeated source priorities and visible formatting "Direct-source phrasing is preserved wherever clearly present, while stage order is implementation support for future prompt reuse."
],
"limitations": [
"The pipeline order is partly inferred because the source is fragmentary and repetitive rather than laid out as a single formal algorithm.",
"This module is a preservation-and-application aid for source-style prompting and should not be treated as a universal grammar or legal method."
]
}
