Source Forms Library

These working forms preserve source identity, location, and version. Complete brackets from the actual source. Select a form only after identifying the material and the receiving requirements. A source-form pattern does not establish citation permission, precedential weight, admissibility, or support for a proposition. The check and common error accompanying each form explain how to use it.

Forms have permanent F-numbers for lookup across the book and online reference. Grouping does not imply that every source in a group has the same legal force. See the house style for editorial defaults and receiving-rule profiles for selected court instructions.

Opinions

F001. Reported judicial opinion

Working form: [Case name], [volume] [reporter] [first page], [pinpoint] ([court] [year]).

Capture: Issued name; reporter identity; deciding court; date; writing; supporting page.

Check: Open the opinion and distinguish the reporter's first page from the page supporting your sentence.

Common error: A correct first page identifies the case but does not locate the proposition.

Source packet: Fictional packet TRAIN-O01 contains the training opinion Harbor Lantern Company v. Oriole Workshop, issued by the fictional Northmere Court of Appeals on February 12, 2025. The fictional TRAIN Reporter prints the opinion in volume 8 beginning on page 120. Page 126 discusses the notice that the parties exchanged; page 127 discusses a different issue. The viewer labels the document's cover as page 1, making printed page 126 the viewer's page 9. The training assignment asks for a citation to the discussion of notice, not for a summary of the decision's outcome.

Completed construction: Harbor Lantern Company v. Oriole Workshop, 8 TRAIN Rep. 120, 126 (Northmere Ct. App. 2025).

Why this construction works: Keep both page numbers because they perform different jobs. The first identifies where the opinion begins in the reporter; the second locates the discussion used by the writer. The fictional court designation remains necessary because the TRAIN Reporter alone does not identify that court. The year comes from the decision, not from the date the researcher downloaded the training packet. A citation ending at page 120 would identify the right document while leaving the reader to search for the supporting passage. A pinpoint to page 9 would use the viewer's numbering system instead of the reporter's printed pagination.

Variation: If the sentence relies on the notice discussion continuing from printed page 126 through printed page 127, use 126–127 only after reading both pages. If page 127 instead concerns an unrelated issue, retain 126. When moving from this fictional reporter version to a slip opinion, locate the passage again and use that version's own page numbers; do not transfer 126 mechanically.

Example scope: Constructed training facts only. TRAIN Rep., Northmere Court of Appeals, the parties, pagination, and discussion are fictional. This example teaches source identity and locator construction; it supplies no real legal authority or holding.

F002. Court-assigned neutral citation

Working form: [Case name], [assigned decision identifier], ¶ [paragraph].

Capture: Exact assigned identifier; court; decision date; numbered paragraph; publication status.

Check: Copy the court's identifier and assigned paragraph, including meaningful suffixes.

Common error: A docket number or OCR paragraph count is not automatically a neutral citation.

Source packet: Fictional packet TRAIN-O02 contains Vale Orchard v. Inland Mill. Its heading gives the fictional Northmere Supreme Court's assigned identifier as 2025 TRAIN-NMSC 14-R. A separate docket line reads TRAIN-24-208. The court has numbered the opinion's paragraphs, and paragraph 32 contains the passage assigned for discussion. The suffix R identifies a replacement decision in this exercise. A text-processing export splits paragraph 32 into three blocks and calls the relevant block paragraph 47. The assignment supplies no rule allowing the exporter to renumber the court's paragraphs.

Completed construction: Vale Orchard v. Inland Mill, 2025 TRAIN-NMSC 14-R, ¶ 32.

Why this construction works: The assigned decision identifier and the docket number are different identifiers. Use the identifier displayed by the fictional court for citation and preserve its meaningful replacement suffix. The paragraph locator comes from the court's numbering, so the exporter's forty-seventh block does not become paragraph 47 of the opinion. A neutral citation allows the reader to identify the decision without choosing a commercial reporter. It does not eliminate the need to verify the correct document, the publication designation, or the passage supporting the proposition. Record the docket and decision date in the source card even when the selected display form does not repeat them.

Variation: If the passage spans the court's paragraphs 32 and 33, change the locator to ¶¶ 32–33. If only an unnumbered PDF is available and it lacks a court-assigned citation, do not manufacture a neutral identifier from its docket. Use an appropriate slip-opinion form and the printed page, while retaining the docket as a docket number.

Example scope: The court, assigned identifier, docket, replacement suffix, and paragraph text are all stipulated fictional training facts. No actual jurisdiction's neutral-citation or publication rules are represented.

F003. Slip opinion

Working form: [Case name], No. [docket], slip op. at [page] ([court] [full date]).

Capture: Issued PDF; docket; date; amendment status; printed slip page.

Check: Confirm that the cited slip version remains the relevant version and the locator is printed on it.

Common error: A later reporter page cannot be substituted without locating the passage again.

Source packet: Fictional packet TRAIN-O03 supplies an issued PDF of Beacon Studio v. Cinder Gallery, docket TRAIN-25-031, dated March 18, 2025, from the fictional Northmere Court of Appeals. The passage to be cited appears on the page printed 7. The PDF has two preliminary sheets, so its viewer calls that page 9. The supplied docket log contains no replacement entry through the exercise's March 20 research cutoff. A separate training reporter proof lists the same decision as starting on page 410, but its typesetting is unfinished and the relevant passage has not been mapped.

Completed construction: Beacon Studio v. Cinder Gallery, No. TRAIN-25-031, slip op. at 7 (Northmere Ct. App. Mar. 18, 2025).

Why this construction works: The docket, deciding court, and full decision date identify this issued document without relying on a finished reporter citation. The phrase slip op. describes the version being cited; 7 is its printed page. Preserve the issued PDF with the source card so another editor can reproduce the location. The docket check is limited to the cutoff supplied by the exercise. It is not a promise that the decision will never be amended. An unverified reporter proof does not justify replacing the slip locator with a guessed reporter pinpoint.

Variation: Suppose a March 24 replacement appears before the assignment is submitted. Read the replacement and determine whether the passage survives; if it moves to printed page 8, update the date, locator, quotation, and version note together. If the original passage was removed, changing only the citation's date would conceal a substantive problem. The original may still be discussed as historical text if that purpose is made explicit.

Example scope: All case and docket facts are fictional. The absence of a replacement is a stipulated exercise fact through March 20, 2025, not a real docket search or current-treatment finding.

F004. Electronic database opinion

Working form: [Case name], No. [docket], [database identifier], at *[star page] ([court] [date]).

Capture: Database name and identifier; docket; court/date; actual star pagination.

Check: Inspect the database version and verify that the asterisk locator exists there.

Common error: A star page from one service may not identify the same location in another.

Source packet: Fictional packet TRAIN-O04 includes two database renditions of Quay Tools v. Meadow Fabricators, docket TRAIN-25-044, decided April 9, 2025, by the fictional Northmere Trial Court. TRAIN Database A assigns the record 2025 TRAIN-DBA 804 and marks the relevant passage 6. TRAIN Database B assigns the same decision 2025 TRAIN-DBB 112 and places the passage at 4. A browser printout from Database A has physical page numbers 1 through 10; those printout pages are not its star pagination. The assignment permits either identified database rendition.

Completed construction: Quay Tools v. Meadow Fabricators, No. TRAIN-25-044, 2025 TRAIN-DBA 804, at *6 (Northmere Trial Ct. Apr. 9, 2025).

Why this construction works: The database identifier and star-page locator belong to one rendition and must travel together. The docket and court/date fields provide additional identity checks. Preserve the star symbol because it tells the reader which locator system the citation uses. A citation to TRAIN-DBB 112 at *6 would combine Database B's identity with Database A's location. The resulting string might look polished while directing the reader to another passage. Store the database name, retrieved version, and passage text in the source card; a bare record number is not enough for later repair.

Variation: To cite the supplied Database B version, use Quay Tools v. Meadow Fabricators, No. TRAIN-25-044, 2025 TRAIN-DBB 112, at *4 (Northmere Trial Ct. Apr. 9, 2025). If the database supplies no star pages, do not invent them from screenfuls or browser pages. Select a verified locator that the source actually supports and check the receiving document's requirements.

Example scope: Both databases, identifiers, case details, and pagination are fictional training facts. This exercise establishes no acceptance rule for a real database or tribunal.

F005. Unpublished disposition

Working form: [Case name], [source identifier], [pinpoint] ([court/date]) ([required status notation]).

Capture: Disposition; date; issuing court; receiving rule; permission purpose; copy requirement.

Check: Determine citation permission and required status wording before choosing the display form.

Common error: Online availability does not establish permission or precedential force.

Source packet: Fictional packet TRAIN-O05 contains Aster Transit v. Pebble Depot, identified as 2025 TRAIN-NMCA 21-U, issued May 6, 2025. Paragraph 9 is the requested passage. The document says unpublished. For this exercise only, the receiving tribunal's supplied Rule TRAIN-12 permits unpublished decisions for persuasive use, requires the parenthetical unpublished, and requires a copy to accompany the submission. The packet also states that unpublished decisions have no precedential force in that fictional tribunal. The writer intends to compare reasoning, not to establish a controlling rule.

Completed construction: Aster Transit v. Pebble Depot, 2025 TRAIN-NMCA 21-U, ¶ 9 (unpublished).

Why this construction works: The display form answers only part of the problem. Before using it, record the permitted purpose under the supplied receiving rule, describe the decision's role accurately in the sentence, and prepare the required copy. Here an appropriate introduction would identify the discussion as persuasive reasoning from an unpublished training decision. The letter U remains part of the assigned identifier, and the required status parenthetical remains visible even though the identifier also carries that suffix. Finding a decision on an accessible website would not answer either the permission question or the separate question of its legal weight.

Variation: If the receiving packet instead permits unpublished decisions solely to establish a specified procedural relationship, this proposed persuasive use would fail. No punctuation change could cure that failure. Either identify a permitted purpose supported by the facts or choose another authority. If a permitted use remains, retain the precise status description and complete any copy or service step required by the receiving rule.

Example scope: Case, court, identifier, Rule TRAIN-12, permission conditions, and status are fictional. They illustrate a decision process and must not be treated as any real court's unpublished-opinion rule.

F006. Summary order

Working form: [Case name], [permitted reporter or database citation], [pinpoint] ([court/date]) (summary order).

Capture: Order; issuing court; date; local rule; required service.

Check: Check whether the receiving rule requires a database or reporter form and service of a copy.

Common error: Calling the document an opinion can obscure the court's own designation.

Source packet: Fictional packet TRAIN-O06 supplies a document titled Summary Order in Cypress Instruments v. Birch Signal, docket TRAIN-25-052, dated June 2, 2025, from the fictional Northmere Review Court. The allowed training database citation is 2025 TRAIN-DBA 920, and the relevant discussion begins at *2. The supplied receiving rule requires an identified database citation, the notation summary order, and service of a copy on a self-represented party. The exercise includes one self-represented party and a service checklist. No document in the packet calls the order a published opinion.

Completed construction: Cypress Instruments v. Birch Signal, No. TRAIN-25-052, 2025 TRAIN-DBA 920, at *2 (Northmere Review Ct. June 2, 2025) (summary order).

Why this construction works: Use the court's document designation and the source form permitted by the supplied receiving rule. The status parenthetical helps the reader distinguish this disposition from other writings in the same case. The citation cannot record that a copy was actually served; that operational step belongs in the filing and service workflow. Link the source card to the attached copy and record who checked service, rather than treating the presence of the parenthetical as proof of compliance. Describe only what the order says, and do not supply a precedential label that the exercise has not authorized.

Variation: If the proposed supporting passage is in a party's motion quoted by the order, rewrite the sentence to distinguish the party's position from the court's resolution. If the receiving rule changes the required reporter or database source, locate the passage in that permitted source before revising the citation. The order's title remains Summary Order regardless of which permitted rendition is used.

Example scope: This is a fictional court, case, database entry, and service rule. The completed citation and checklist logic do not state the rules of a real federal circuit.

F007. Concurring opinion

Working form: [Case name], [full citation], [pinpoint] ([author], concurring).

Capture: Case; writing author; exact concurrence type; page; proposition.

Check: Verify whether the author concurs in the opinion, judgment, or only part of the result.

Common error: A concurrence's reasoning is not automatically the majority's reasoning.

Source packet: Fictional packet TRAIN-O07 presents Moss Survey v. Ridge Cartography in 9 TRAIN Rep. 200, decided by the fictional Northmere Supreme Court in 2025. The majority writing occupies pages 200–211. Judge Vale's separate writing begins on page 212 and is expressly titled Concurring in the Judgment. Its discussion of the survey protocol appears at page 214. Judge Vale agrees with the disposition but declines to join the majority's analysis of that protocol. The writer wants to discuss the narrower approach proposed by Judge Vale.

Completed construction: Judge Vale proposed a narrower treatment of the survey protocol. Moss Survey v. Ridge Cartography, 9 TRAIN Rep. 200, 214 (Northmere Sup. Ct. 2025) (Vale, J., concurring in the judgment).

Why this construction works: The sentence attributes the proposition to its actual author, and the parenthetical preserves the type of concurrence. The reporter's first page still identifies the case as a whole; page 214 locates the particular separate writing. Calling this simply the court's reasoning would erase a material difference between agreement with the result and agreement with the majority's explanation. Read the separate writing's heading and the vote description rather than inferring its status from where it appears in the PDF. Attribution and pinpointing work together: a correct page does not repair an incorrect claim about whose reasoning it contains.

Variation: If another passage at page 207 expresses the majority's analysis, cite that passage separately and frame the comparison explicitly. Do not use one citation at page 214 for both positions. If Judge Vale joins Parts I and II but concurs only in the judgment as to Part III, identify the part relevant to the sentence before selecting the descriptive parenthetical.

Example scope: The reporter, court, judges, case, vote alignment, and positions are invented for training. The example illustrates attribution without implying that a real concurrence carries a particular doctrinal effect.

F008. Dissenting opinion

Working form: [Case name], [full citation], [pinpoint] ([author], dissenting).

Capture: Case; dissent author; page; scope of disagreement.

Check: Frame the sentence as the dissent's position and explain why it matters.

Common error: A forceful dissent quotation cannot be presented as the holding.

Source packet: Fictional packet TRAIN-O08 contains Stonebridge Archive v. Lumen Records, 9 TRAIN Rep. 300, decided by the fictional Northmere Supreme Court in 2025. The majority rejects the archive's requested remedy. Judge Reed dissents beginning at page 318; page 321 gives the dissent's concern about incomplete catalog records. The research assignment asks the writer to explain that concern as an alternative view. The packet contains no later decision adopting it. A draft sentence currently says that the court held incomplete catalogs necessarily require the requested remedy.

Completed construction: Judge Reed's dissent emphasized the problem of incomplete catalog records. Stonebridge Archive v. Lumen Records, 9 TRAIN Rep. 300, 321 (Northmere Sup. Ct. 2025) (Reed, J., dissenting).

Why this construction works: Repair the proposition before polishing its citation. The supplied draft turns a dissenting position into the court's holding and adds a categorical consequence the source facts do not establish. The completed sentence makes the limited attribution explicit. The parenthetical then identifies the writing that the pinpoint reaches. A separate opinion can be relevant to criticism, historical development, or a comparison of approaches, but those purposes should be apparent from the surrounding analysis. The vividness of a passage does not determine whether the court adopted it. Keep the majority's disposition and the dissent's proposed approach as separate fields in the research note.

Variation: If later research locates a decision adopting Judge Reed's approach, read that later decision and cite its own supporting passage. The earlier dissent remains a dissent; it does not retroactively become the earlier court's holding. A discussion of development may cite both writings, with the historical relationship explained accurately and each proposition attached to the right source.

Example scope: All authorities and judicial positions in this packet are fictional. No real case history, dissent, subsequent adoption, or current legal rule has been verified or asserted.

F009. Plurality passage

Working form: [Case name], [full citation], [pinpoint] (plurality opinion).

Capture: Writing; vote alignment; relevant part; separate writings.

Check: Identify the votes supporting the particular passage and analyze its doctrinal role separately.

Common error: The lead opinion is not necessarily a majority opinion on every issue.

Source packet: Fictional packet TRAIN-O09 supplies Ember Harbor v. Meridian Works, 10 TRAIN Rep. 10, decided by a seven-member fictional Northmere Supreme Court in 2025. The vote sheet shows five judges joining Part I, three joining Part II, and two concurring in the judgment on a separate rationale. Two judges dissent. The assigned passage is on page 22 in Part II. The lead writing's introductory page says only Opinion of Judge Rowan. The assignment requires an accurate description of the writing, leaving the controlling-rule analysis for a separate memorandum.

Completed construction: The plurality's Part II discussion focused on the inspection sequence. Ember Harbor v. Meridian Works, 10 TRAIN Rep. 10, 22 (Northmere Sup. Ct. 2025) (plurality opinion).

Why this construction works: Count support for the particular part rather than assigning one vote label to the entire document. The three judges joining Part II do not form a majority of this seven-member court. Agreement by other judges with the judgment does not, on the stipulated facts, show agreement with that reasoning. The parenthetical identifies the passage's status but does not itself decide which rationale governs future cases. Keep a part-by-part vote map alongside the citation so an editor can check the characterization without reconstructing all separate writings. The lead author's name or position at the front of the PDF is not a substitute for that map.

Variation: A sentence about Part I at page 15 would require a different description because five judges join that part. Remove the plurality characterization for that passage if the packet supports describing it as majority reasoning. If a sentence compares Part II with a concurrence, cite both passages and explain their points of agreement and difference before drawing any doctrinal conclusion.

Example scope: The seven-member court, case, report, parts, and vote counts are fictional. This is an attribution exercise; it does not apply any real jurisdiction's test for extracting a controlling rule from fractured decisions.

F010. Amended or superseding opinion

Working form: [Case name], [current source identifier], [pinpoint] ([court/date]) ([version description if material]).

Capture: Original and replacement documents; dates; docket; changed passage.

Check: Compare the relied-on text between versions and update both locator and analysis.

Common error: Retaining an old quotation after changing the citation creates a false match.

Source packet: Fictional packet TRAIN-O10 provides two versions of Alder Harbor v. Quartz Marine, docket TRAIN-25-071. The fictional Northmere Court of Appeals issued an original on July 3, 2025, and a superseding opinion on July 17. Original printed page 8 described three inspection dates. The superseding opinion removes that description and places a more limited discussion on printed page 9. The docket entry expressly states that the July 17 opinion replaces the July 3 opinion. The draft still quotes the removed three-date description but now displays the later date.

Completed construction: The superseding opinion addresses the inspection record more narrowly. Alder Harbor v. Quartz Marine, No. TRAIN-25-071, slip op. at 9 (Northmere Ct. App. July 17, 2025) (superseding opinion).

Why this construction works: The citation and proposition must refer to the same version. Replacing July 3 with July 17 while retaining the deleted wording would make the citation falsely appear to verify that quotation. Compare the relied-on passage, surrounding qualifications, disposition, and pagination before updating the source card. Preserve both files in the research record, but mark which one is superseded and which one supports the final sentence. Here the repair requires revising the prose, not merely the date and page. The version parenthetical is useful because replacement is material to the discussion being written.

Variation: If the assignment instead examines how the court revised its explanation, the original may be cited explicitly as the superseded July 3 version, followed by the July 17 version and a precise description of the change. Give each its own locator. Do not imply that a retained historical copy remains the operative decision or that the replacement adopted text it actually removed.

Example scope: The case, docket entries, versions, dates, and textual changes are fictional training facts. No actual replacement opinion or current docket status is represented.

F011. Order without published opinion

Working form: [Proceeding], No. [docket], [order title] at [page] ([court] [date]).

Capture: Order title; case; docket; entry; issuing court; page.

Check: Read the operative language and distinguish the order from the parties' requested relief.

Common error: A motion title does not establish what the court ordered.

Source packet: Fictional packet TRAIN-O11 includes three documents in Willow Freight v. Copper Yard, docket TRAIN-25-088, before the fictional Northmere Trial Court. Entry 17 is a motion titled Motion to Compel All Inspection Records. Entry 23, dated August 4, 2025, is titled Order on Motion to Compel and has three printed pages. Page 2 requires production of a defined inspection log; page 3 denies the remaining requests. Entry 24 is counsel's proposed order, which sought broader relief but bears no judicial signature. The requested citation supports a statement about what the court actually ordered.

Completed construction: Willow Freight v. Copper Yard, No. TRAIN-25-088, Order on Motion to Compel at 2 (Northmere Trial Ct. Aug. 4, 2025), docket entry 23.

Why this construction works: Identify the entered judicial order and its operative page. The motion title describes requested relief, while the proposed order describes language a party wanted the court to adopt. Neither proves the scope of the ruling. Adding the docket entry disambiguates these nearby documents and assists retrieval. The sentence should specify the defined inspection log rather than saying all inspection records were ordered produced. Record the signed document's identity and entry date, and distinguish a document's printed page from a docket-system attachment number or combined-PDF page.

Variation: For a sentence about the denied requests, cite printed page 3 of entry 23. If a later order modifies the production obligation, read the later order and describe the relationship rather than leaving the earlier order to support a present-tense claim. If the cited order is unpaginated, use a verified numbered paragraph or another locator accepted for that submission instead of inventing a page.

Example scope: All case documents, court details, docket entries, and relief are fictional. This exercise teaches document-role verification and does not establish a real discovery obligation.

F012. Procedural history

Working form: [Primary case], [citation], [accurate history phrase], [later decision citation].

Capture: Both decisions; docket relationship; disposition; relevant issue.

Check: Read the later disposition and verify that it concerns the decision cited.

Common error: An affirmance on another ground does not endorse every earlier rationale.

Source packet: Fictional packet TRAIN-O12 contains Mapletide Studio v. Solstice Press, 11 TRAIN Rep. 40, decided by the fictional Northmere Trial Court in 2024, and its appeal at 12 TRAIN Rep. 90 in the fictional Northmere Court of Appeals in 2025. The appellate caption and docket cross-reference match the trial proceeding. The appellate disposition affirms the judgment on a timeliness ground while expressly declining to consider the trial court's interpretation of the delivery clause. The draft cites trial page 46 for that interpretation and labels the appeal a complete endorsement.

Completed construction: Mapletide Studio v. Solstice Press, 11 TRAIN Rep. 40, 46 (Northmere Trial Ct. 2024), affirmed on other grounds, 12 TRAIN Rep. 90 (Northmere Ct. App. 2025).

Why this construction works: The history phrase describes the relationship shown by the supplied appellate disposition. It does not turn the trial court's contract analysis into an appellate holding. Correct the surrounding prose to acknowledge the limitation: the appellate court affirmed the judgment on a different ground and left that interpretation unaddressed. Verify the relationship from the docket and opinion, because similar party names can occur in separate proceedings. Preserve the later decision's disposition and the issue it reached as distinct research fields. A history abbreviation is a compact description of an event, not a substitute for analyzing what survived review.

Variation: If the later disposition instead vacated only a fee award while leaving the merits judgment intact, a blanket vacated label would be misleading. Identify the affected part and, when necessary, describe the limited disposition in prose. If a later proceeding involves a different order in the same litigation, explain that connection rather than attaching it as though it reviewed the decision cited.

Example scope: Both courts, reports, decisions, issues, and docket relationships are fictional. No real appellate treatment or current validity determination is supplied by this example.

F013. Short case citation

Working form: [Distinctive short name], [volume] [reporter] at [pinpoint].

Capture: Full antecedent; collision-free short name; new locator.

Check: Check the antecedent after every significant rearrangement of text or notes.

Common error: A short name shared by multiple cases is not a reliable reference.

Source packet: Fictional packet TRAIN-O13 contains a paragraph that first cites Juniper Solar v. Crown Storage, 12 TRAIN Rep. 150, 158 (Northmere Ct. App. 2025), in full. Three sentences later, the writer returns to the same opinion's printed page 161. Between those sentences the writer cites a second fictional case, Juniper Solar v. Delta Carriers, 12 TRAIN Rep. 240, 245 (Northmere Ct. App. 2025). The editorial convention supplied for the exercise allows a distinctive party-based short name with the reporter and pinpoint. Both full citations remain within the reader's immediate context.

Completed construction: Crown Storage, 12 TRAIN Rep. at 161.

Why this construction works: The selected short name distinguishes the intended case from the other Juniper Solar decision. Using Juniper Solar alone would leave the reader to infer which of the two cases the writer means, even though the reporter volume happens to be the same. The new pinpoint is 161; repeating the first citation's 158 would mislocate the newly discussed passage. Keep the reporter component because the supplied short-form convention requires it. The convenience of a short form depends on an accessible full antecedent and a name that remains unambiguous after editing.

Variation: If an editor moves the full Juniper Solar v. Crown Storage citation into another chapter, restore a full citation when introducing the case in this chapter. If another Crown Storage case is added nearby, reassess the short name rather than assuming the earlier choice remains distinctive. A document-level search can find competing names, but an editor still needs to read the local context and confirm the intended antecedent.

Example scope: Case names, reporter entries, court, pages, and the supplied short-form convention are fictional. This exercise does not prescribe the short-form rules of any particular real court or journal.

F014. Immediate reference

Working form: Id. at [new pinpoint].

Capture: Immediately preceding source; intervening references; current locator.

Check: Use only when one unmistakable source supplies the antecedent under the receiving convention.

Common error: An inserted footnote can silently change what the reference appears to mean.

Source packet: Fictional packet TRAIN-O14 begins with a single-source citation: Dawn Kiln v. Violet Ceramic, 13 TRAIN Rep. 20, 26 (Northmere Ct. App. 2025). The next citation concerns printed page 28 of that same opinion. Nothing intervenes. For this exercise, the supplied receiving convention permits Id. when the immediately preceding citation identifies one unmistakable source. A later revision inserts a citation to the fictional TRAIN Materials Code § 8 between the two case citations. The intended supporting opinion does not change, but the immediate reference context does.

Completed construction: Original uninterrupted sequence: Dawn Kiln v. Violet Ceramic, 13 TRAIN Rep. 20, 26 (Northmere Ct. App. 2025). Id. at 28.

Why this construction works: In the original sequence, Id. points to one identifiable source, and the added page directs the reader to a different passage within it. After the code citation is inserted, the same words would appear to point to the code. The correct repair is a source-identifying case citation, such as Dawn Kiln, 13 TRAIN Rep. at 28, assuming its full antecedent remains clear under the supplied convention. Check immediate references after additions, deletions, footnote moves, and citation consolidations. Their meaning depends on surrounding text, so they can break without any character inside the reference changing.

Variation: If the preceding citation lists both Dawn Kiln and another source, do not rely on Id. merely because the intended opinion appears last. Use a clear short or full citation unless the receiving convention and context make the reference unmistakable. If the same page is intended, confirm whether the receiving convention permits the bare immediate reference; that formatting choice never excuses an ambiguous antecedent.

Example scope: All cited sources and pagination are fictional; the immediate-reference convention is supplied for this exercise. The example illustrates dependency on context, not a universal rule for every publication.

Enactments

F015. United States Constitution

Working form: U.S. Const. art. [article], § [section], cl. [clause].

Capture: Instrument; article or amendment; actual subdivisions; relevant version.

Check: Use the Constitution's own subdivision structure rather than adding nonexistent levels.

Common error: A clause locator that belongs to another section can look formally plausible.

Source packet: The National Archives transcription places the commerce language in Article I, Section 8, after the taxing and borrowing provisions. The Library of Congress's Constitution Annotated identifies that passage as Article I, Section 8, Clause 3. The exercise asks only for a citation locating the constitutional text concerning commerce with foreign nations, among the states, and with Indian Tribes. It does not ask whether a particular statute falls within congressional authority. The web page's interface also has headings, navigation links, and explanatory notes that are separate from the constitutional text.

Completed construction: U.S. Const. art. I, § 8, cl. 3.

Why this construction works: The instrument, article, section, and clause together supply a durable locator. The Roman numeral I identifies the article; 8 and 3 identify the section and clause. Do not replace these subdivisions with the position of a search result or a paragraph number created by a browser export. The citation points to constitutional text, while an essay interpreting that text would be a different source requiring its own attribution. A discussion of the reach of congressional power would require appropriate interpretive authorities and analysis beyond this citation-construction exercise.

Variation: For the adjacent borrowing provision, the terminal locator changes to cl. 2. For an article that is not divided into numbered sections, do not add a section solely to make its citation resemble this one. If a historical argument concerns text later changed by amendment, identify the historical version and relevant amendment in the discussion so that the reader understands which text is being used.

Example scope: Real primary-source transcription and official constitutional locator inspected October 8, 2026. Verification covers the text's location and subdivision structure; no application of the Commerce Clause or current case-law treatment was researched for this example.

Example sources: Official source 1 · Official source 2.

F016. Constitutional amendment

Working form: [Jurisdiction] Const. amend. [number], § [section].

Capture: Amendment; section if present; adoption/status material when relevant.

Check: Confirm whether the amendment contains numbered sections and which passage supports the claim.

Common error: Do not invent a section number for an unsectioned amendment.

Source packet: The National Archives transcription of Amendments 11–27 prints five numbered sections under Amendment XIV. Its Section 1 contains citizenship language and restrictions directed to states, including due process and equal protection language. The same institution's Bill of Rights transcription prints Amendment I as an unsectioned paragraph. The exercise requires two accurate locators: one for the first section of the Fourteenth Amendment and one for the First Amendment's text. It does not call for a conclusion about a litigant's rights or about how a clause applies to any government action.

Completed construction: U.S. Const. amend. XIV, § 1.

Why this construction works: The amendment number identifies which change to the Constitution is being cited, and the section identifies a real subdivision within that amendment. Do not use art. XIV, which would describe a constitutional article rather than an amendment. The selected locator reaches several related textual propositions; when the surrounding sentence concerns only one, name that proposition accurately and avoid implying that the whole section says only that. An amendment's adoption date, a proposed amendment's status, and a web page's review date are different facts and should not be substituted for one another.

Variation: The completed locator for the second assigned source is U.S. Const. amend. I. There is no need to append § 1 to an amendment printed without numbered sections. If discussing an originally proposed article in a historical document, distinguish its proposal number from the number of the amendment ultimately ratified; the National Archives page presents both the proposal and the ratified Bill of Rights transcription.

Example scope: The National Archives' Fourteenth and First Amendment transcriptions were directly inspected October 8, 2026. This example verifies their displayed structure and identity, not constitutional doctrine, litigation outcomes, or every historical ratification question.

Example sources: Official source 1 · Official source 2.

F017. Current federal code section

Working form: [Title] U.S.C. § [section] ([identified edition or version]).

Capture: Title; section; subdivisions; edition; amendments; applicability date.

Check: Inspect the applicable text and record why that version governs the question.

Common error: Today's compilation is not necessarily the law governing earlier conduct.

Source packet: GovInfo's official United States Code, 2024 Edition, supplies title 17, section 107, headed Limitations on exclusive rights: Fair use. The exercise asks the researcher to prepare a version-specific citation to that verified edition while beginning a present-day research task. The page presents the statutory text separately from historical and revision notes. The researcher has not completed a check for enactments after the edition's coverage. A preliminary-code search result appeared during research, but opening the current House site returned a maintenance page, so it does not establish a freshly verified current text.

Completed construction: 17 U.S.C. § 107 (2024).

Why this construction works: This is a complete citation to the edition actually inspected. The date identifies that edition, not the year of retrieval or an assertion that every current-law check is complete. The source card should therefore record both the 2024 version and the outstanding currency task. When the assignment concerns current law, verify subsequent amendments, effective dates, and applicable text before presenting the research as current. The formatting can be finished while the legal research remains incomplete. Also distinguish the enacted section from explanatory material displayed beneath it; a quotation from a historical note is not automatically a quotation from section 107 itself.

Variation: If the assignment concerns a transaction on an earlier date, retrieve the relevant historical text and trace changes instead of replacing 2024 with the transaction year by assumption. If an inspected online compilation later supplies a newer explicit coverage date, record that coverage and apply the receiving document's version convention. Do not print a bare 2026 parenthetical merely because the source was visited in 2026.

Example scope: Official 2024 edition text and metadata directly inspected October 8, 2026. This example deliberately marks current-through-2026 verification incomplete and does not decide whether a proposed use is fair use.

Example sources: Official source 1.

F018. Multiple statutory provisions

Working form: [Title] [Code] §§ [first section], [other section] ([version]).

Capture: Every cited section; intended range or nonconsecutive list; version.

Check: Verify each provision and use a range only when the intervening provisions are intended.

Common error: A dash can imply provisions the writer did not mean to include.

Source packet: The official 2024 edition of title 17 contains section 106, headed Exclusive rights in copyrighted works, and section 109, headed Limitations on exclusive rights: Effect of transfer of particular copy or phonorecord. The exercise asks for a combined citation identifying those two sections as separate research subjects. Sections 107 and 108 fall numerically between them, but the assigned citation is not intended to identify every section in that interval. Both cited sections were inspected in the same edition. The assignment is about listing sources, not about resolving a copyright dispute.

Completed construction: 17 U.S.C. §§ 106, 109 (2024).

Why this construction works: The doubled section symbol and comma-separated numbers communicate that more than one section is cited and that the selection is nonconsecutive. A range of 106–109 would also sweep in the intervening sections, changing the stated scope of the citation. The common title and edition can be stated once because they apply to both selected sources. If the sentence advances distinct propositions, separate citations placed beside the respective propositions may be clearer than a combined citation at the end. A compact list should not make the reader guess which source supports which claim.

Variation: For a passage comparing only section 106's distribution provision with section 109's opening subsection, the more precise form is 17 U.S.C. §§ 106(3), 109(a) (2024). Use that version only after reading the identified subdivisions and their qualifications. If two sections are consulted in different editions, separate their citations and state each edition so the combined typography does not imply matching versions.

Example scope: Official 2024 edition identifiers, headings, and named subdivisions inspected October 8, 2026. Subsequent amendments and application to any actual copying, sale, license, or transaction were not resolved.

Example sources: Official source 1 · Official source 2.

F019. Nested statutory subdivision

Working form: [Title] [Code] § [section](a)(2)(B)(iii) ([version]).

Capture: Every subdivision level; redesignation history; exact passage.

Check: Walk the hierarchy from the section heading to the terminal subdivision.

Common error: Dropping one level can redirect the reader to a different rule.

Source packet: GovInfo's official 2024 edition of 5 U.S.C. § 552 includes a sequence within subsection (a), paragraph (4), subparagraph (E), clause (ii), and subclause (I). That terminal provision lists specified forms of relief in the definition of substantially prevailing for the subparagraph. The neighboring subclause (II) addresses a different route. The exercise asks for the locator to subclause (I), while leaving any entitlement to attorney fees for separate analysis. The page's indentation and successive labels make the full hierarchy visible when read upward from the target passage.

Completed construction: 5 U.S.C. § 552(a)(4)(E)(ii)(I) (2024).

Why this construction works: Read the hierarchy from the section down and copy every level in order. Uppercase E, lowercase ii, and uppercase I are meaningful labels, not typography that can be freely normalized. Omitting (4) would break the path from subsection (a) to the selected subparagraph. Ending at (E) would identify a broader unit than the specific route assigned. The pinpoint also should not be made to bear more weight than its text supports: locating one definition does not establish every condition for a fee award. Keep the parent text and neighboring alternative available while drafting the proposition.

Variation: To identify both routes in the definition, cite § 552(a)(4)(E)(ii) rather than manufacturing a compressed range of dissimilar labels. To discuss only the neighboring alternative, change the terminal component to (II). When using a historical edition, verify that the same hierarchy existed at the relevant time; a terminal label cannot be carried backward across amendments or redesignations without checking.

Example scope: The hierarchy and neighboring alternatives in the official 2024 text were directly inspected October 8, 2026. No current fee entitlement, litigation outcome, later amendment, or controlling interpretation was determined.

Example sources: Official source 1.

F020. Public law and Statutes at Large

Working form: [Act title], Pub. L. No. [Congress-law], § [section], [volume] Stat. [first page], [pinpoint] ([year]).

Capture: Enactment identifier; act section; Statutes page; date; codification.

Check: Use the act section for enactment language and trace any separate codified location.

Common error: Act section numbers and code section numbers need not match.

Source packet: GovInfo's enacted-law PDF identifies the American Rescue Plan Act of 2021 as Public Law 117–2, approved March 11, 2021. The Act begins at 135 Stat. 4. Its section 9601(a), printed at 135 Stat. 138, instructs insertion of a new Internal Revenue Code section numbered 6428B. In the downloaded document, the viewer's numbering includes a preliminary cover, so the PDF page position differs from the printed Statutes at Large page. The exercise asks for the enactment location that introduced the new code section, not a current tax-eligibility conclusion.

Completed construction: American Rescue Plan Act of 2021, Pub. L. No. 117–2, § 9601(a), 135 Stat. 4, 138 (2021).

Why this construction works: The public-law number identifies the enactment, section 9601(a) identifies the part of that enactment, and 138 locates the printed passage. The number 4 remains the enactment's starting page. Do not substitute code section 6428B for act section 9601(a): one identifies the destination of the inserted text and the other identifies Congress's amending instruction. A citation to the codified provision would answer a different retrieval question. Read the actual printed header rather than translating the viewer's page count by memory; inserted cover sheets and other preliminary material can change that relationship.

Variation: If discussing the codified provision's later text, retrieve the relevant version of 26 U.S.C. § 6428B and cite that inspected version. If discussing a later amendment to the original enactment, identify the later law and its precise instruction rather than assuming the original public-law PDF incorporates all subsequent changes. Maintain separate entries for enactment, codification, and any later amendment in the version record.

Example scope: GovInfo's enacted-law PDF, title, law number, date, and printed pages 4 and 138 were directly inspected October 8, 2026. Current tax law, benefits, individual eligibility, and later amendments were not evaluated.

Example sources: Official source 1.

F021. Uncodified statutory provision

Working form: [Act identifier], § [section], [official publication and pinpoint] ([date]).

Capture: Enacted text; uncodified provision; effective terms; related code notes.

Check: Read the actual enacted provision even when discovered through a code note.

Common error: A provision can remain legally important without appearing in the main code text.

Source packet: The enacted-law PDF for Public Law 117–2 places its short-title provision in section 1 on printed page 135 Stat. 4. The printed margin associates that provision with a note to 15 U.S.C. § 9001, rather than assigning it a new main-text code section numbered 1. The exercise asks the writer to identify where the Act's short title was enacted. The title is discoverable through summaries and code notes, but the enacted section itself is available and has been inspected. No question about program eligibility or the continuing operation of another provision is presented.

Completed construction: American Rescue Plan Act of 2021, Pub. L. No. 117–2, § 1, 135 Stat. 4, 4 (2021).

Why this construction works: Cite the enacted provision when the proposition concerns its enactment. The first 4 identifies the Act's starting page and the second 4 expressly pinpoints the same page under the expanded form used here; a receiving style may consolidate the repeated page. Discovery through a code note does not turn the short-title provision into the main text of 15 U.S.C. § 9001. Preserve the act section and the printed publication location so a reader can retrieve the actual words adopted. Also distinguish the provision's placement from its practical role: being carried in a note is not a reason to replace enacted text with a database summary.

Variation: For an uncodified effective-date or transition provision, cite its own act section and page after reading its terms. Do not use this short-title section as a template that supplies missing substantive facts. If citing the code note as encountered in a particular edition, identify the note and edition accurately and retain a link to the underlying enactment for verification.

Example scope: The enacted short-title text and its printed marginal note reference were directly inspected October 8, 2026. No independent current classification-table audit or broader claim about uncodified provisions' legal operation was performed.

Example sources: Official source 1.

F022. Historical code provision

Working form: [Title] [Code] § [section] ([historical edition]).

Capture: Historical edition; amendments; relevant event date; source copy.

Check: Preserve the historical numbering and explain a current successor separately if useful.

Common error: Replacing a historical identifier with today's section can change the source.

Source packet: GovInfo provides a United States Code, 2023 Edition, page for 17 U.S.C. § 107. Its page heading explicitly identifies the edition. The exercise is a historical research note reporting what that archived compilation printed, with particular attention to its numbered factor (3). A separate 2024 edition page is also available. The task does not stipulate that the 2023 edition alone proves the law applicable to every event during calendar year 2023, and the researcher has not reconstructed all enactments and effective dates for a specific event.

Completed construction: 17 U.S.C. § 107(3) (2023).

Why this construction works: The parenthetical preserves the identity of the historical compilation actually consulted. Do not silently replace it with a current edition just because the relevant words appear similar. The selected subdivision locates the factor assigned for discussion; it does not state the result of a fair-use analysis. A historical source card should distinguish the event date, edition date, source coverage, and any amendment's effective date. Those dates can differ. When the proposition is narrowly that the archived edition contains particular wording, the archived text verifies that proposition without requiring a claim about every later version.

Variation: If the assignment changes to whether section 107 governed conduct on a specified day, inspect the law in force on that date and investigate amendments or transition terms. If comparing 2023 and 2024 compilations, cite each edition beside the relevant comparison and record whether the selected text actually changed. A different edition label alone is not evidence of a substantive amendment, and identical wording alone does not resolve every temporal issue.

Example scope: The official 2023 edition identifier and section 107's numbered text were directly inspected October 8, 2026. This is an archived-text locator example, not a complete effective-date reconstruction or current copyright opinion.

Example sources: Official source 1 · Official source 2.

F023. State code provision

Working form: [State code title] § [section/subdivision] ([version]).

Capture: State; official title; source status; version; current and historical text.

Check: Check the state's own publication system and the receiving court's prescribed form.

Common error: A commercial title abbreviation does not establish official publication status.

Source packet: Fictional packet TRAIN-E23 contains the Northmere Records Code, official 2025 compilation, published by the fictional Northmere Legislative Office. Section 18-204(b) addresses the training register's indexing requirement. A separate commercial training service reproduces the provision under the label N.R.C. Annotated and adds explanatory notes. The supplied fictional receiving rule requires the name Northmere Records Code and a version parenthetical; it does not authorize the commercial service's abbreviation as the official title. A version sheet states that the official compilation incorporates enactments through June 30, 2025.

Completed construction: Northmere Records Code § 18-204(b) (official 2025 compilation; through June 30, 2025) [TRAIN-E23].

Why this construction works: Use the code title and subdivision shown by the official training source, preserving the hyphen inside the section number. The bracketed packet marker keeps this invented authority visibly within the training environment. The source card should name the publisher and record the coverage statement so an editor can distinguish source identity from update status. The commercial copy may aid discovery, but its annotation is a separate item and should not be passed off as enacted text. The supplied receiving rule controls the display choice for this exercise; the book's general pattern cannot replace a specific instruction from the destination.

Variation: Suppose an enactment after June 30 amends subsection (b) but the official compilation has not incorporated it. Cite the verified enactment alongside the compilation as needed to show the change, and revise any claim that the displayed subsection is fully current. If researching earlier conduct, retrieve the earlier text rather than assuming that today's section number has always contained the same provision.

Example scope: Northmere, its legislative office, code, publisher, receiving rule, and update statement are fictional. This example demonstrates source-status and version checks without representing the statutory system of any actual state.

F024. State session law

Working form: [Act title], [year] [state session-law designation] ch. [chapter], § [section], [page].

Capture: Enacting jurisdiction; session; chapter or act number; section; date.

Check: Trace the enactment to the provision used and check subsequent amendments.

Common error: A session-law chapter is not necessarily a code chapter.

Source packet: Fictional packet TRAIN-E24 contains the Northmere Register Access Act, chapter 42 of the fictional 2025 Northmere TRAIN Session Laws. The enactment begins at printed page 310. Section 3, printed at page 312, amends Northmere Records Code § 18-204. Section 7 on page 315 supplies the effective-date terms. The packet's chapter number identifies the law within the legislative session; the code destination has a different chapter and section structure. The exercise asks for the enactment location of the amendment, while requiring the writer to keep the separate effective-date issue visible.

Completed construction: Northmere Register Access Act, 2025 Northmere TRAIN Session Laws ch. 42, § 3, at 312.

Why this construction works: The year and session-law title identify the publication series, chapter 42 identifies the enactment, and section 3 plus page 312 identify the amendment instruction. The page is a printed session-law page, not an electronic viewer count. Do not substitute code chapter 18 for session-law chapter 42 or call the code destination section 3. The source card should map enactment section 3 to code section 18-204 while preserving both identities. It should also flag section 7 for temporal analysis before a sentence describes the amendment as operative on a particular date.

Variation: A citation to the effective-date provision would end ch. 42, § 7, at 315. A present-tense statement about the resulting code text requires inspection of the code and any intervening enactments, not merely this session law's title. If a second enactment changes the first before its effective date, trace both instructions and describe the sequence explicitly rather than assuming the newest publication page resolves it.

Example scope: The jurisdiction, act, session-law series, sections, pages, amendment, and effective-date provision are fictional training facts. No actual state enactment, codification, or date of legal operation is asserted.

F025. Municipal ordinance

Working form: [Municipality and state], Ordinance No. [number], § [section] ([adoption date]).

Capture: Municipality; ordinance; adoption/effective dates; amendment; code destination.

Check: Confirm the municipality's identity and the ordinance's operative version.

Common error: A code publisher's website date does not establish the ordinance's effective date.

Source packet: Fictional packet TRAIN-E25 contains an ordinance adopted by the Town of Bellhaven, Northmere, on February 11, 2025. Ordinance TRAIN-2025-07 has five sections. Section 2 changes an inspection-register requirement; section 5 makes that change effective April 1. A commercial code site's footer says updated March 15, and a neighboring municipality also named Bellhaven has an ordinance numbered 2025-07 concerning parks. The assignment asks for the adopting instrument behind the register change. The packet supplies the signed ordinance and its adoption certificate, but no later amendment.

Completed construction: Town of Bellhaven, Northmere, Ordinance No. TRAIN-2025-07, § 2 (adopted Feb. 11, 2025).

Why this construction works: The municipality and fictional state distinguish the enactment from a similarly named government's ordinance. The ordinance number identifies the whole instrument, and section 2 locates the amendment being discussed. The date is expressly identified as the adoption date. It should not be replaced by April 1, which serves a different role, or by the publisher's March 15 update date. Record all three dates with their labels in the source card. For a statement about when the change operated, read and cite section 5 separately; the display of an adoption date does not answer that temporal question.

Variation: If the proposed sentence says the inspection requirement governed a March 20 event, this packet does not support that conclusion: its effective-date provision points to April 1. Research the earlier rule and any transition language. If the ordinance is later incorporated into a local code, use the inspected code provision for the codified text while preserving the ordinance citation when explaining the amendment's origin.

Example scope: Bellhaven, Northmere, the ordinance, dates, publisher, and competing municipality are fictional. No real municipal enactment or operative requirement is asserted.

F026. Local code provision

Working form: [Municipality], [Code title] § [section] ([version]).

Capture: Government; code; chapter/section; update coverage; related ordinance.

Check: Check whether recent enacted ordinances have been incorporated into the displayed code.

Common error: A current-looking website can lag the latest enactment.

Source packet: Fictional packet TRAIN-E26 provides the City of Ternbridge's Municipal Code § 6.12.040(C). The displayed compilation states that it includes ordinances through TRAIN-2025-09, adopted May 12, 2025. A separate June 3 enactment, TRAIN-2025-14, replaces subsection (C), with an effective date of July 1. The website header shows today's date, but the coverage notice still ends at ordinance 09. The assignment concerns the text applicable to a July 8 register submission. Both the stale compilation and the later signed ordinance are included in the packet. Section 2 of Ordinance TRAIN-2025-14 contains the replacement.

Completed construction: City of Ternbridge, Municipal Code § 6.12.040(C) (compilation through Ordinance TRAIN-2025-09, May 12, 2025), as amended by Ordinance TRAIN-2025-14, § 2 (June 3, 2025).

Why this construction works: This form exposes the mismatch between the code site's coverage and the later enactment instead of disguising it with a current access date. The particular subsection and amendment section are separate locators. Read the amendment instruction together with the old text to reconstruct the relevant provision, and retain the effective-date term in the research note. The site's header date tells when the page was presented, not which ordinances were incorporated. A clean code citation alone would be incomplete support for a July 8 claim if it still points to the superseded subsection.

Variation: If the city later publishes a compilation explicitly incorporating ordinance 14, inspect subsection (C) in that compilation and update the version description. Do not assume every later compilation correctly incorporates the amendment. If the research instead concerns a June 20 submission, investigate whether the old text still applied and whether the amendment contains any special transition provision.

Example scope: City, code, enactments, dates, and amendment instructions are fictional training facts. The combined citation illustrates version reconstruction rather than a real local-law conclusion.

Legislative materials

F027. Federal bill

Working form: [Bill title], [chamber designation] [number], [Congress], § [section] ([version/date]).

Capture: Chamber; number; Congress; version; document date; section.

Check: Compare the cited version with later versions or enacted text when making a historical claim.

Common error: Bill numbers recur and introduced text may never become law.

Source packet: Fictional packet TRAIN-L27 comes from an invented Federal Assembly of Northmere used only for drafting exercises. Its sixth Training Congress has a lower-chamber bill styled TRAIN H.R. 18, the Archive Access Proposal. The introduced version is dated January 14, 2025; section 4 proposes a monthly index. A committee-reported version dated March 7 replaces monthly with quarterly and renumbers the provision as section 5. A prior Training Congress also used bill number 18 for unrelated text. The packet does not include an enacted version or a record of final passage.

Completed construction: Archive Access Proposal, TRAIN H.R. 18, 6th Training Cong., § 4 (introduced Jan. 14, 2025).

Why this construction works: The chamber designation, bill number, legislative term, version, date, and section identify the particular proposal used. The sentence supported by this citation should say that the introduced bill proposed a monthly index. It should not say that the legislature required one. A recurring bill number without the legislative term would not reliably identify the source. Comparing later language requires a second source card because the reported version changes both substance and numbering. Preserve the exact version label displayed by the training document rather than translating every stage into a generic publication date.

Variation: To discuss the reported proposal, cite TRAIN H.R. 18, 6th Training Cong., § 5 (reported Mar. 7, 2025), and describe the quarterly interval. A historical comparison may place both citations beside the respective texts. If later research finds an enactment, locate its adopted language independently; neither a bill's popularity nor its presence on a legislature's website establishes enactment.

Example scope: Assembly, legislative term, bill, stages, and wording are fictional. TRAIN H.R. is a teaching identifier and does not identify a United States congressional bill.

F028. Joint or concurrent resolution

Working form: [Resolution designation and number], [Congress/session], § [section] ([version/date]).

Capture: Resolution type; chamber; number; session; version; legal status.

Check: Identify the resolution type and actual procedural status before characterizing its effect.

Common error: Different resolution types should not be treated as interchangeable enactments.

Source packet: Fictional packet TRAIN-L28 includes two documents from Northmere's invented Federal Assembly: TRAIN H. Con. Res. 6 and TRAIN H.J. Res. 6, both in its sixth Training Congress. The concurrent resolution's agreed text, dated February 20, 2025, concerns assembly scheduling and has paragraph 3. The joint resolution's introduced text concerns a different subject and has section 3. The assignment asks what the agreed concurrent resolution says about scheduling. The packet supplies the official training status sheet but contains no instruction equating the legal effects of the two document types.

Completed construction: TRAIN H. Con. Res. 6, 6th Training Cong., ¶ 3 (agreed text Feb. 20, 2025).

Why this construction works: Preserve the resolution type because the shared numeral does not make these the same instrument. The locator is paragraph 3, the subdivision actually used by the selected document, rather than section 3 copied from the neighboring resolution. Agreed text identifies the supplied stage; it does not, without further governing material, establish every possible legal consequence. The source card should record the adopting bodies and procedural event shown in the status sheet. Describe the scheduling statement within those verified limits instead of automatically calling every resolution a statute or every introduced document an adopted measure.

Variation: If the writer needs to discuss the joint resolution's proposal, use its own full designation, version date, and section. If an amended concurrent resolution later changes paragraph 3, compare the agreed versions before describing the operative schedule. A search hit returning the right number but the wrong resolution type is an identity failure, even if the year and sponsoring chamber happen to match.

Example scope: The legislative body, resolutions, procedures, and dates are fictional. This packet does not prescribe or characterize the legal effects of actual United States resolutions.

F029. Committee report

Working form: [Chamber] Rep. No. [number], at [page] ([year]).

Capture: Reporting committee; report identifier; Congress; page; section or views.

Check: Check whether the passage is in the main report, minority views, or appended material.

Common error: A statement in minority views is not automatically the committee's adopted explanation.

Source packet: Fictional packet TRAIN-L29 contains report TRAIN H. Rep. No. 6-22 from the Northmere Assembly's Records Committee, dated April 16, 2025. The majority discussion ends at printed page 18. Pages 19–23 are expressly headed Minority Views, signed by three named members. Page 21 questions the projected cost of an index system. An appendix reproduces a consultant's estimate at page 30. The writer wants to describe the minority members' cost concern, but a draft currently introduces it as the committee's unanimous finding. The report's cover lists the committee as the submitting body.

Completed construction: TRAIN H. Rep. No. 6-22, at 21 (2025) (minority views).

Why this construction works: The report number identifies the publication; the page and parenthetical identify the relevant component within it. Correct the prose to attribute the concern to the minority members who signed those views. The committee's name on the cover does not convert every appended statement into a position adopted by the whole committee. If naming the members matters to the argument, identify them in the sentence or explanatory parenthetical after checking the signature block. Keep the majority discussion, minority views, and consultant appendix as distinct source components in the research record.

Variation: A sentence about the consultant's numerical estimate should cite page 30 and identify it as the reproduced consultant material. A sentence contrasting majority and minority explanations should give separate locators for each. If the report is reprinted with different pagination, confirm the passage in that edition rather than transferring page 21 unchanged or citing a search-result excerpt as though it were the report itself.

Example scope: Report, committee, legislative numbering, members, and cost discussion are fictional training facts. No real legislative finding or inference about legislative intent is supplied.

F030. Congressional hearing

Working form: [Hearing title] Before [committee], [Congress] [page] ([year]) ([speaker and role if material]).

Capture: Hearing; committee; date; publication; page; speaker.

Check: Read the surrounding testimony and identify whether the source is oral or submitted testimony.

Common error: Witness testimony is not a congressional finding simply because it appears in a hearing.

Source packet: Fictional packet TRAIN-L30 presents a published hearing titled Reliable Public Registers Before the Records Subcommittee of Northmere's invented Federal Assembly, sixth Training Congress. The hearing occurred May 8, 2025. Witness Lena Vale's oral answer appears at printed page 47, while her prepared written statement appears at pages 88–92. At page 47 she says the sample covered three offices; the prepared statement reports a preliminary five-office plan. The assignment asks for the testimony actually describing the completed sample. The chair's question appears immediately before the answer and narrows it to the pilot phase.

Completed construction: Reliable Public Registers: Hearing Before the Records Subcommittee, 6th Training Cong. 47 (2025) (oral testimony of Lena Vale, pilot coordinator) [TRAIN-L30].

Why this construction works: Identify the hearing publication and the speaker whose testimony supports the sentence. The oral answer and submitted statement are different components even though they share an author and hearing date. The surrounding question explains the scope of the answer, so the prose should refer to the pilot sample rather than all office operations. Testimony printed in an assembly hearing is still testimony by the witness; its inclusion does not make it a legislative finding. Preserve the printed page, publication identity, speaker role, and hearing date so another researcher can distinguish the oral record from supplemental submissions.

Variation: If discussing the proposed five-office plan, cite the prepared statement at its actual page and identify its preliminary status. If the witness later submits corrected testimony, retain the correction and explain which version supplies the cited figure. A hearing calendar or press notice may verify that a hearing was scheduled, but it cannot replace the transcript when quoting an answer.

Example scope: Hearing, assembly, witness, sample, and publication are fictional. The example concerns source attribution and does not establish findings by any actual legislative body.

F031. Congressional Record

Working form: [volume] Cong. Rec. [edition-specific page] ([date]) ([speaker if material]).

Capture: Daily or bound edition; volume; page designation; date; speaker.

Check: Verify the page in the edition actually used and attribute the statement accurately.

Common error: Mixing daily-edition pages with bound-edition data impairs retrieval.

Source packet: Fictional packet TRAIN-L31 supplies the Northmere Assembly Record in two editions. The daily edition for June 10, 2025, is volume 6 and prints Delegate Rowan's floor remarks at H214–H215. The later bound volume prints the same remarks at pages 803–804. The assigned passage is on daily page H215, and the writer inspected that edition. An adjacent item is an inserted statement by a different delegate, clearly labeled as submitted for the record. The exercise asks for a citation to Rowan's remarks, not for an inference about the views of the entire assembly.

Completed construction: 6 TRAIN Assembly Rec. H215 (daily ed. June 10, 2025) (remarks of Delegate Rowan).

Why this construction works: The daily-edition label and chamber-prefixed page number preserve the locator system actually used. Do not pair H215 with the bound edition's publication information or replace it with page 804 without inspecting that rendition. The speaker parenthetical attributes the remarks to Rowan. A publication compiling floor proceedings can contain speeches, inserted statements, procedural entries, and other material; the source role must be identified from the item itself. Store the date of the session separately from the date a bound volume was produced so later editors can choose a consistent edition without changing historical facts.

Variation: If the receiving convention requires the bound edition, locate the same passage there and use its verified page. If the relied-on language belongs to the inserted statement, attribute it to the submitting delegate and describe its status. Do not silently convert an inserted statement into words spoken on the floor merely because both appear in the same publication issue.

Example scope: The legislature, record series, volume, pages, delegates, and remarks are fictional. TRAIN Assembly Rec. is not a citation to the actual Congressional Record.

F032. Committee print

Working form: [Committee], [Print title], [print identifier] at [page] ([date]).

Capture: Committee; print title/number; Congress; date; page.

Check: Use the document's own designation and identify authorship where stated.

Common error: A committee print is not automatically a committee report.

Source packet: Fictional packet TRAIN-L32 includes the Records Committee's publication Register Systems: A Staff Survey, identified on its cover as Committee Print TRAIN-6-04, September 2025. The title page attributes the survey to the committee's research staff and expressly states that it is staff work prepared for discussion. Printed page 36 describes a comparison method; an unnumbered cover and two preliminary pages precede it in the PDF. The assignment asks how the staff organized that comparison. A library catalog mistakenly groups the publication under committee reports, but the document itself retains its print designation.

Completed construction: Northmere Assembly Records Committee, Register Systems: A Staff Survey, Committee Print TRAIN-6-04, at 36 (Sept. 2025).

Why this construction works: Use the publication's own type and identifier. The catalog's broad category helps discovery but does not change a committee print into a committee report. In the sentence, attribute the method to the research staff because the title page identifies them as its authors and limits the publication's role. Printed page 36 locates the discussion; the PDF viewer's offset is irrelevant to that pagination. Keep the committee, staff attribution, series identifier, and publication date together in the source card so the citation can be expanded if another similarly titled survey appears.

Variation: If the committee later adopts a formal report relying on the survey, read and cite the report for the committee's adopted explanation, and cite the print for its underlying method when useful. Adoption should not be inferred solely from distribution at a committee meeting. If a revised staff print replaces the method, identify the revised identifier or date and compare the affected passage before reusing an earlier summary.

Example scope: Committee, staff, publication, identifiers, and catalog facts are fictional training materials. No actual legislative endorsement or institutional practice is asserted.

F033. Presidential document

Working form: [Document type and number], [publication identifier], [pinpoint] ([date]).

Capture: Executive order/proclamation or other type; number; publication; dates.

Check: Distinguish signing, publication, and effective terms in the source record.

Common error: A presidential speech and an executive order serve different source roles.

Source packet: Fictional packet TRAIN-L33 contains Executive Order TRAIN-101, signed by the President of the fictional Northmere Federation on July 9, 2025. It is published in volume 6 of the TRAIN Executive Register beginning at page 700 on July 12. Section 4, on page 702, specifies an August 1 implementation date. A July 9 speech announces the policy in broader terms, and a press summary omits section 4's qualifications. The assignment concerns the text of section 4. The packet includes the signed order and official training publication, but no later modifying order.

Completed construction: Exec. Order No. TRAIN-101, 6 TRAIN Executive Reg. 700, 702 (published July 12, 2025) (signed July 9, 2025).

Why this construction works: The document type and number distinguish the order from the speech and press summary. The publication citation identifies the inspected rendition, while the separately labeled signing date prevents the two dates from being collapsed. A sentence about implementation should describe section 4's terms and identify August 1 accurately; neither signing nor publication alone establishes that date. Read the operative language rather than borrowing a summary's broader wording. The source card should retain the section number, printed page, issuing official, and any amendment status known from the packet.

Variation: If the assignment quotes the President's explanation in the speech, cite the speech as a speech with its own recording or transcript locator. Do not use the executive-order citation to support words found only in the announcement. If a later order modifies section 4 before August 1, trace that modification and revise the proposition, not merely the displayed date on the original citation.

Example scope: President, federation, order, register, dates, speech, and policy are fictional. The example supplies no actual executive authority or rule about an actual order's effect.

Administrative materials

F034. Annual CFR provision

Working form: [Title] C.F.R. § [section/subdivision] ([edition year]).

Capture: Title; section; annual revision date; amendments; relevant event.

Check: Confirm the annual edition's coverage and any later changes relevant to the question.

Common error: The year alone does not describe every amendment after the revision date.

Source packet: Fictional packet TRAIN-A34 provides title 8 of the Northmere Federation's TRAIN Code of Regulations, annual 2025 edition, revised as of January 1. Section 22.16(b) contains a register-format provision. A separate final amendment published March 14 changes subsection (b) effective May 1. The assignment concerns a June 10 event. The annual volume's cover says 2025, and an inexperienced researcher assumes that this year label means it includes every change made during 2025. The packet includes both the annual text and the amending publication, allowing the version problem to be identified.

Completed construction: 8 TRAIN C.F.R. § 22.16(b) (2025 annual ed., revised Jan. 1, 2025).

Why this construction works: The completed citation accurately identifies the annual source, but it does not alone establish the rule governing the June event. The revision date describes the annual edition's cutoff and must be considered alongside the later amendment and its effective terms. The source card should connect section 22.16(b) to the March amendment, preserving both documents. If the proposition concerns June, reconstruct and cite the applicable amended text using the receiving convention. A properly formatted annual citation can still support the wrong version if the researcher treats the cover year as a rolling update guarantee.

Variation: For a February event, investigate whether the January text remained applicable then rather than automatically choosing the newest wording. For a historical discussion of the annual compilation itself, the displayed citation may be sufficient with an explicit description of that scope. If an amendment affects only subsection (c), verify that fact before deciding whether the subsection (b) discussion needs revision.

Example scope: Federation, regulatory code, section, dates, and amendment are fictional. TRAIN C.F.R. is not the United States Code of Federal Regulations and establishes no actual regulatory requirement.

F035. eCFR historical version

Working form: [Title] C.F.R. § [section] (electronic version as of [date]).

Capture: Selected version date; title; section; downloaded text; source URL.

Check: Preserve the date-specific text rather than a link that returns the current version later.

Common error: An access date is not necessarily the version date.

Source packet: Fictional packet TRAIN-A35 includes a date-selected electronic version of Northmere's TRAIN Code of Regulations, title 8, section 22.16, as of February 15, 2025. The researcher retrieved it on September 4. The supplied interface distinguishes the selected version date from the retrieval date. A generic section URL now opens wording effective May 1, whereas the preserved date-specific export contains the February text. The exercise asks for the source used to describe the February version. The export's heading and metadata both confirm the selected date, and the relevant passage is subsection (b).

Completed construction: 8 TRAIN C.F.R. § 22.16(b) (electronic version as of Feb. 15, 2025), TRAIN-A35 preserved export.

Why this construction works: The parenthetical identifies the version date, which is the important temporal locator here. September 4 belongs in the retrieval log and should not replace February 15. Preserve the date-selected content as well as the link, because a generic current-section link may later display different language. The reader should be able to reproduce the historical text without guessing which interface settings the researcher used. Keep the export title, selected date, source URL, and relevant subsection in one source card, and compare them before relying on a downloaded file's name alone.

Variation: If a date-specific link redirects to the current version, do not describe the current display as the February source. Use the preserved export and explain the retrieval problem, or reacquire the historical text from a reliable source. If the assignment asks which rule governed a February event, separately investigate effective and transition terms; a historical display date is evidence of a selected text version, not a complete applicability analysis.

Example scope: Electronic system, regulatory text, dates, export, and behavior are fictional training facts. This example makes no claim about the functionality or legal status of the actual eCFR.

F036. Final rule publication

Working form: [Rule title], [volume] Fed. Reg. [first page], [pinpoint] ([date]) ([codification if useful]).

Capture: Agency; final-rule status; document number; pages; effective/compliance terms.

Check: Distinguish preamble explanation, amendment instructions, and codified text.

Common error: A final rule's publication date need not be its effective date.

Source packet: Fictional packet TRAIN-A36 contains the Northmere Register Agency's final rule titled Electronic Index Formats. It appears in volume 6 of the TRAIN Federal Register at pages 810–822 on March 14, 2025. Page 814 discusses comments in the preamble; page 820 gives amendment instructions; page 821 contains the replacement regulatory text. The document specifies a May 1 effective date and a later August 1 compliance date for a defined category. The writer wants to cite the agency's explanation for choosing a format, which appears on page 814, not the regulatory command.

Completed construction: Electronic Index Formats, 6 TRAIN Fed. Reg. 810, 814 (Mar. 14, 2025) (final rule; preamble discussion).

Why this construction works: The first page identifies the publication and the pinpoint locates the explanatory passage actually used. The parenthetical makes the source component clear where that distinction matters. Do not present the preamble's explanation as though it were the exact words inserted into the regulatory code. Record the amendment instruction and replacement text separately so the eventual code provision can be traced. Publication, effectiveness, and the category-specific compliance date answer different questions. A sentence about what a regulated party had to do on a particular date needs those terms and the applicable text, not merely this citation to the explanation.

Variation: To quote the replacement wording, move the pinpoint to 821 after comparing the actual text. To explain which code section was amended, cite the instruction at 820 and preserve its destination. If the agency later corrects a typographical error, inspect the correction and determine whether the relied-on explanation, instruction, or regulatory text changed before updating the manuscript.

Example scope: Agency, rule, register series, pages, dates, and compliance categories are fictional. TRAIN Fed. Reg. is a teaching publication and supplies no actual final rule.

F037. Proposed rule

Working form: [Proposal title], [volume] Fed. Reg. [page], [pinpoint] (proposed [date]).

Capture: Agency; proposal status; docket; pages; comment details; later action.

Check: Describe the text as proposed unless a later action establishes adoption.

Common error: A proposal's future-tense language is not evidence of an operative requirement.

Source packet: Fictional packet TRAIN-A37 supplies a proposal titled Searchable Register Fields from the Northmere Register Agency, docket TRAIN-REG-25-6. It appears in volume 6 of the TRAIN Federal Register beginning at page 930 on April 2, 2025. Proposed paragraph (c) appears at page 937 and would add a field to the register. The proposal invites comments through May 20. A later status sheet says the matter remains under consideration through the exercise's June 1 cutoff. The writer's draft incorrectly says that the agency now requires the proposed field.

Completed construction: Searchable Register Fields, 6 TRAIN Fed. Reg. 930, 937 (proposed Apr. 2, 2025), docket TRAIN-REG-25-6.

Why this construction works: The proposal label is essential to the source's role. Revise the sentence to say that the agency proposed adding the field, identifying any conditions in proposed paragraph (c). The comment deadline is neither an adoption date nor an effective date. The docket helps locate later activity, but the source cited remains the April proposal. A current-looking agency page or a passed comment deadline does not convert proposed text into operative text. Record the status cutoff and any known later action separately from the proposal's publication date so the research does not imply an unlimited currency check.

Variation: If a later final rule adopts a narrower field requirement, cite the final rule for the adopted text and the proposal only when explaining the change. If the proposal is withdrawn, describe that event accurately and avoid leaving the proposal as support for a present-tense obligation. A comparison should show the actual language in each document rather than assuming that the final version follows the proposal unchanged.

Example scope: Proposal, agency, docket, dates, status, and text are fictional training facts. No actual regulatory proposal or requirement is represented.

F038. Agency notice

Working form: [Agency], [Notice title], [volume] Fed. Reg. [page], [pinpoint] ([date]).

Capture: Notice type; agency; docket; date; operative content.

Check: Read the document classification and the specific action announced.

Common error: A notice can inform readers without promulgating a regulation.

Source packet: Fictional packet TRAIN-A38 includes the Northmere Register Agency's Notice of Public Workshop on Archive Search. It appears at 6 TRAIN Federal Register 1010–1012, dated April 28, 2025, under the publication's Notices heading. Page 1011 gives the workshop topics and registration instructions. The notice says that the agency seeks information about possible future improvements; it contains no instruction amending the regulatory code. A blog calls the announcement a new search regulation. The assignment asks what process the agency announced, using the notice itself as the source.

Completed construction: Northmere Register Agency, Notice of Public Workshop on Archive Search, 6 TRAIN Fed. Reg. 1010, 1011 (Apr. 28, 2025).

Why this construction works: The title, agency, and publication classification identify an announcement about a workshop. Describe those announced actions precisely rather than adopting the blog's regulatory label. The source may support statements about the scheduled workshop and the topics identified for discussion, subject to any later change. It does not, on the supplied facts, establish a new substantive code requirement. Capture the document number or docket if shown, and distinguish registration instructions for attending the event from rules governing ordinary regulated conduct. The specificity of a notice's instructions does not remove the need to determine their actual subject and scope.

Variation: If a later notice postpones the workshop, cite that notice for the revised date and retain the original only for historical context. If an attachment contains a discussion draft, identify it as that attachment and preserve its draft status. If the research concerns an actual code amendment, locate the amending instrument rather than inferring one from an information-gathering notice.

Example scope: Agency, workshop, register, dates, blog description, and notice contents are fictional. This example teaches source classification without making claims about any actual administrative action.

F039. Agency guidance or manual

Working form: [Agency], [Document title] § [section] ([version/date]), [URL].

Capture: Agency; title; section; version; stated status; URL.

Check: Identify the source's legal role and check whether the chapter has been updated separately.

Common error: A guidance manual should not be labeled a regulation without a basis.

Source packet: Fictional packet TRAIN-A39 contains the Northmere Register Agency's Intake Handbook, edition 3. Its cover is dated January 2025, but chapter 4 carries a separate revision date of June 12. Section 4.3 explains how staff review missing index fields. The handbook's introductory page describes it as internal operational guidance and says that the governing regulation controls if the two conflict. A downloaded chapter from the previous edition uses different escalation steps. The assignment asks how the June handbook directs staff to process an incomplete submission, not what duties the regulation imposes on outsiders.

Completed construction: Northmere Register Agency, Intake Handbook § 4.3 (ed. 3, ch. 4 rev. June 12, 2025), https://training.example/agency/handbook/ch4.

Why this construction works: Identify the chapter's specific revision because the cover date does not describe its latest text. The sentence should attribute the process to the handbook and its staff audience. Calling the handbook a regulation would misstate the source designation supplied by the packet. Retain the introduction's description of legal role and the relevant regulatory cross-reference for later research. The completed citation points to the June chapter, while the source card should preserve the downloaded content in case the link later serves another revision. A generic handbook title without its chapter version would make competing instructions difficult to distinguish.

Variation: If the client-facing obligation is the actual question, read and cite the governing regulation, then explain the handbook's separate relevance if useful. If only section 4.3 is updated in a later release, inspect that section's revision notice before attributing the entire manual to the newer date. Do not resolve a conflict by assuming that whichever document was downloaded last has greater authority.

Example scope: Agency, handbook, regulation reference, revision history, and instructions are fictional. The .example address is illustrative and is not a retrieved source.

F040. Administrative decision

Working form: [Proceeding], [decision or docket number], [publication and pinpoint] ([body/date]).

Capture: Body; decision maker; proceeding; number; date; finality/designation.

Check: Verify the decision's classification at the issuing institution.

Common error: Initial decisions and designated precedents are not interchangeable.

Source packet: Fictional packet TRAIN-A40 includes an initial decision in In re Rowan Register Services, proceeding TRAIN-AD-25-11, issued August 6, 2025, by an administrative adjudicator of the Northmere Register Commission. Paragraph 28 discusses the recordkeeping evidence. A cover notice labels the document Initial Decision and states that commission review remains pending under the exercise's procedure. The commission's separate publication index has a category for designated precedents, but this decision is absent from it. The assignment asks what the adjudicator concluded at this stage, not whether the commission has adopted a binding precedent.

Completed construction: In re Rowan Register Services, No. TRAIN-AD-25-11, Initial Decision, ¶ 28 (Northmere Register Comm'n adjudicator Aug. 6, 2025).

Why this construction works: The decision type and issuing decision maker prevent an initial adjudication from being presented as a final commission ruling. The paragraph locator belongs to the decision itself. Describe the conclusion as the adjudicator's at the initial stage and keep the pending-review status in the research record. An agency's name on the document does not alone settle finality or designation. Inspect the institution's classification and subsequent action when those matters affect the proposed use. The source card should distinguish proceeding number, decision number if any, authoring official, date, and review status rather than collapsing them into one agency label.

Variation: If the commission later adopts part of the initial decision and rejects paragraph 28, cite the commission's final document for its disposition and explain the rejected reasoning only as history. If the final decision incorporates a passage by reference, inspect the incorporation language and retain both documents. Do not add precedent merely because an electronic database assigns the initial decision a searchable identifier.

Example scope: Commission, proceeding, adjudicator, classifications, and review process are fictional. No actual agency's precedential or finality rules are asserted.

F041. Agency opinion letter

Working form: [Agency or official], [Letter identifier or subject], at [page] ([date]).

Capture: Issuing office; addressee if relevant; letter number; date; scope.

Check: Read factual assumptions and limitations before generalizing its conclusion.

Common error: A fact-specific letter may not establish a general rule for different circumstances.

Source packet: Fictional packet TRAIN-A41 contains letter TRAIN-OL-25-8 from the Northmere Register Agency's Interpretive Services Office to Cedar Index Cooperative, dated September 9, 2025. Page 3 addresses the cooperative's proposed filing arrangement. The letter assumes that every submission is reviewed by a named supervisor and that no archival originals leave the facility. Its closing paragraph limits the response to the facts supplied. A draft memorandum applies the letter's conclusion to an unsupervised remote process, although those facts are different. The exercise provides the whole letter, including the request summary and limitations.

Completed construction: Northmere Register Agency, Interpretive Services Office, Opinion Letter TRAIN-OL-25-8, at 3 (Sept. 9, 2025) (addressing Cedar Index Cooperative's stated arrangement).

Why this construction works: Identify the issuing office as well as the agency and letter number. The pinpoint reaches the conclusion, but the surrounding analysis must preserve the assumptions on which it depends. The source card should pair page 3 with the request summary and limitation paragraph. A fact-specific response can be relevant by comparison without establishing that the same conclusion governs a materially different process. Revise the draft to state the actual arrangement considered and explain any analogy separately. The recipient's identity may matter because it helps locate the request and keeps the letter from appearing to be general guidance addressed to all regulated parties.

Variation: If a later letter withdraws this one, update the discussion of its status and identify the withdrawal. If the assignment concerns the unsupervised remote process, seek authority addressing that process instead of deleting the inconvenient assumptions from the summary. A web page collecting letters is a finding aid; cite and preserve the particular letter rather than the collection's home page alone.

Example scope: Agency, office, letter, recipient, assumptions, and limitation are fictional. The example establishes no real interpretive position or degree of deference.

F042. Patent or application publication

Working form: [Title], [country] Patent [or Publication] No. [number], [claim/column/line] ([date]).

Capture: Grant versus application; number; kind code; date; exact locator.

Check: Verify which publication contains the relied-on disclosure or claim language.

Common error: An application publication is not the same instrument as the issued patent.

Source packet: Fictional packet TRAIN-A42 supplies two instruments from the invented Northmere Patent Office for a device titled Modular Index Tray. The application publication is TRAIN-NM-2024-009 A1, dated October 4, 2024, and has numbered paragraphs. The later grant is TRAIN-NM-510 B1, dated July 2, 2025, and contains claims plus column-and-line locators. Application paragraph 37 describes an optional divider. Granted claim 4 has narrower wording than application claim 4. The assignment asks for the language of the granted claim, not for a conclusion about validity, infringement, or patent term.

Completed construction: Modular Index Tray, Northmere TRAIN Patent No. TRAIN-NM-510 B1, claim 4 (issued July 2, 2025).

Why this construction works: The patent number, kind code, issue date, and claim locator identify the granted instrument actually used. The application publication is a related but different source. Do not transfer claim wording from the application while citing the grant, even when the title and inventors match. Record both identifiers and the relationship between them, then inspect the precise claim or disclosure cited. A claim locator and a specification paragraph answer different retrieval questions: one identifies claimed language in this packet, while the other may identify an explanatory embodiment. The citation does not itself decide the legal significance of either passage.

Variation: For the earlier disclosure, cite Modular Index Tray, Northmere TRAIN Publication No. TRAIN-NM-2024-009 A1, ¶ 37 (published Oct. 4, 2024). If relying on a drawing, identify its figure in the correct instrument. If a corrected grant or later proceeding changes the record, verify that document separately rather than assuming the original downloaded grant remains the complete relevant record.

Example scope: Patent office, jurisdiction, numbers, kind codes, claims, and disclosure are fictional. No actual patent, application, inventor, or patent-law conclusion is represented.

Court rules

F043. National procedural rule

Working form: Fed. R. [rule system] [rule](subdivision).

Capture: Rule system; rule number; subdivision; version; scope.

Check: Read the current rule and any amendment transition provisions relevant to the proceeding.

Common error: A proposed amendment is not an effective rule merely because it appears on an official site.

Source packet: Fictional packet TRAIN-R43 contains Northmere's TRAIN National Rules of Civil Procedure effective January 1, 2025. Rule 18(c)(2) concerns a required statement in a specified motion. A separate committee proposal posted on the same official training site would renumber it as rule 18(d) and change the statement, but the proposal is labeled For Comment and has no effective order. The proceeding in the exercise began in February 2025. A search result emphasizes the proposal because it was posted more recently. The assignment asks for the rule in the supplied effective compilation.

Completed construction: TRAIN Nat'l R. Civ. P. 18(c)(2) (effective Jan. 1, 2025).

Why this construction works: Name the correct rule system and preserve the subdivision sequence from the effective text. The newer proposal does not replace that text merely because it is an official publication or appears first in a search. The source card should retain the promulgating order or version notice, the effective date, and the proposal's separate status. If the research question concerns applicability to a pending proceeding, read any transition terms rather than relying only on the proceeding's commencement date. The completed citation identifies a source; the analysis still must connect its scope and temporal operation to the specific motion.

Variation: If a later promulgating order adopts the amendment effective in July with special treatment for pending matters, inspect that order before changing the citation to rule 18(d). If the assigned filing is an appeal, first check whether this civil-trial rule system applies at all. Similar rule numbers in different systems can refer to unrelated subjects, so the system's name is an identity field, not decoration.

Example scope: National rule system, rule, proposal, proceeding dates, and transition scenario are fictional. This is not a statement of any Federal Rule of Civil Procedure.

F044. Statewide court rule

Working form: [State and rule system] [rule/subdivision] ([version if material]).

Capture: Jurisdiction; court level; rule system; subdivision; effective date.

Check: Confirm that the rule governs the receiving court and document type.

Common error: A statewide appellate rule may not govern a trial-court motion.

Source packet: Fictional packet TRAIN-R44 provides the State of Northmere's Appellate Rules, effective March 1, 2025. Rule 9(b)(3) specifies an appendix reference in opening appellate briefs. The separate Northmere Trial Rules also contain a rule 9, concerning a different subject. The assigned document is a motion filed in a trial court before any appeal. A colleague has copied the appellate appendix requirement into the motion checklist because it appears in a statewide rulebook. The exercise includes the scope provisions of both rule systems so the mismatch can be identified.

Completed construction: Northmere TRAIN Appellate R. 9(b)(3) (effective Mar. 1, 2025).

Why this construction works: The citation correctly identifies the appellate rule, but its existence does not establish that it governs the trial-court motion. Read the rule system's scope and the document category named in the provision. Remove an unsupported requirement from the motion checklist and research the trial rule or applicable local instruction. Statewide distribution means the publication is available across the state; it does not erase distinctions among courts and proceedings. Keep the jurisdiction, system, court level, document type, and effective version as separate source-card fields so an editor can see why a rule was selected.

Variation: If the assignment becomes an opening appellate brief, verify that the relevant appellate court and proceeding fall within the supplied rule's scope, then apply the appendix provision. If a special proceeding uses its own rules, inspect those rules and any incorporation of the general appellate system. Do not infer incorporation from a familiar filing title or from the fact that both matters are heard in the same building.

Example scope: State, courts, rule systems, numbering, and scopes are fictional. The example teaches applicability screening without representing any actual state's procedural requirements.

F045. Local court rule

Working form: [Court], Local Rule [number/subdivision] ([version]).

Capture: Court; local rule; current text; effective date; related order.

Check: Check the specific court's official rules page and amendment notices.

Common error: An unidentified Local Rule 7 cannot reliably be located by another reader.

Source packet: Fictional packet TRAIN-R45 includes Local Rule 7.2(a) of the Northmere Eastern Trial Court, revised April 1, 2025. It addresses the format of a particular motion attachment. The Northmere Western Trial Court has a different Local Rule 7.2(a). An archived Eastern Court PDF from 2023 remains reachable through a search engine, while the court's current training rules page links the 2025 revision and a separate amendment notice effective June 15. The assigned motion will be filed June 20. The packet contains the notice and both versions of the affected text.

Completed construction: Northmere Eastern Trial Court, TRAIN Local R. 7.2(a) (rev. Apr. 1, 2025, as amended June 15, 2025).

Why this construction works: Name the specific court so Local Rule 7.2(a) is retrievable and distinguishable from another court's identically numbered rule. The version description should reflect the amendment actually inspected, not just the date on the main compilation's cover. Compare the amendment notice with the rule text and record whether it changes the attachment requirement. An old PDF's continued availability is evidence that a copy exists, not that the court still uses it. Preserve the official training rules-page context and amendment notice with the source so the selected version can be explained to the person preparing the filing.

Variation: If the filing occurs before June 15, examine the amendment's effective and transition terms rather than applying the later wording automatically. If the case is transferred to the Western Court, rebuild the receiving-requirements sheet for that court. Replacing Eastern with Western in the citation without reading the Western rule would preserve a plausible format while changing the claimed authority to an unverified source.

Example scope: Courts, local rules, revisions, notices, and filing dates are fictional. No actual local court rule or filing requirement is stated.

F046. Standing or individual order

Working form: [Court/judge], [Order or practice title] § [section] ([date]), [URL or docket].

Capture: Issuing judge/court; order; version; applicability; section.

Check: Determine whether the order applies to the case and whether a case-specific order modifies it.

Common error: A judge's prior standing order can remain indexed after replacement.

Source packet: Fictional packet TRAIN-R46 supplies Judge Rowan Vale's Standing Order for Civil Hearings in the Northmere Eastern Trial Court, issued January 6, 2025. Section 3 describes exhibit copies. A former 2022 standing order remains on an archive page. In the assigned case, a February 18 case-specific order changes the number of copies for a scheduled hearing and expressly says that its instruction controls for that hearing. The assignment concerns that hearing. The packet includes both standing orders and the case-specific order, allowing the writer to distinguish general practice from the tailored direction. The case-specific docket entry is identified as TRAIN-18.

Completed construction: Judge Rowan Vale, Northmere Eastern Trial Court, Standing Order for Civil Hearings § 3 (Jan. 6, 2025), TRAIN-R46 packet, as modified for the hearing by docket entry TRAIN-18.

Why this construction works: Identify the judge, court, title, section, and version so the instruction can be located. The general standing order remains useful context, but the filing checklist must account for the expressly controlling case-specific modification. A search engine's archived 2022 result cannot establish present practice. The source card should state which case and hearing each instruction reaches, not merely collect all documents carrying the judge's name. Read the modification's scope carefully: changing the number of copies for one hearing does not necessarily replace every other provision of the standing order.

Variation: If the case is reassigned, check the new judge's applicable practices and any reassignment order before carrying forward the old checklist. If a later standing order replaces the January version, inspect its treatment of already scheduled hearings. A citation can name the correct standing order yet still support the wrong instruction when an applicable case order has modified that instruction.

Example scope: Judge, court, orders, exhibit instructions, and docket entry are fictional. This is a source-priority exercise, not a statement of actual chambers practice.

F047. Case-specific scheduling order

Working form: [Order title] at [page], [case/docket/entry] ([court/date]).

Capture: Case; docket entry; order date; deadlines; later amendments.

Check: Check for modifications and distinguish entry date from a deadline stated in the order.

Common error: A superseded scheduling order is not repaired by a correct docket citation.

Source packet: Fictional packet TRAIN-R47 contains a scheduling order entered March 3, 2025, in Oakline Data v. Harbor Index, docket TRAIN-CV-25-16. Entry 12 sets a September 12 disclosure deadline. An amended scheduling order entered June 9 as entry 31 changes that deadline to October 3; printed page 2 contains the revised date. The amended order leaves other listed deadlines unchanged. A calendar entry still cites the March order. The assignment asks the writer to document the revised disclosure deadline, using the order actually entered in the case.

Completed construction: Amended Scheduling Order at 2, Oakline Data v. Harbor Index, No. TRAIN-CV-25-16, docket entry 31 (Northmere Eastern Trial Ct. June 9, 2025).

Why this construction works: The citation's date is the order's entry date; October 3 is the deadline stated in the order and belongs in the accompanying sentence or calendar record. Identify the amended order and its page rather than retaining the superseded March source. Compare the orders provision by provision so the calendar update changes the affected deadline without assuming that every date moved. The source card should connect the calendar item to the precise operative language and record who checked the later docket activity. A valid docket citation does not rescue a calendar built from an earlier, replaced instruction.

Variation: If a minute entry later modifies the deadline orally set at a conference, inspect the entry and any controlling written order or transcript before updating the calendar. If the amended order is proposed but unsigned and unentered, it cannot be treated as the entered amendment on that basis alone. The source's procedural role matters as much as the date printed at its top.

Example scope: Case, court, docket, orders, dates, and deadlines are fictional. The example does not calculate or establish any real litigation deadline.

Litigation records

F048. Complaint allegation

Working form: Compl. ¶ [paragraph], [docket entry if needed].

Capture: Case; pleading version; paragraph; entry; amended status.

Check: Describe the cited matter as an allegation unless another source establishes it.

Common error: An allegation is not proof of the asserted event.

Source packet: Fictional packet TRAIN-D48 includes the original and first amended complaints in Laurel Systems v. Cedar Harbor, docket TRAIN-CV-25-24. The first amended complaint was filed April 7, 2025, as entry 19. Paragraph 42 alleges that a delivery occurred on February 3; the original complaint used a different date in paragraph 35. No admission, finding, or supporting record is included in this exercise. The writer is preparing a procedural summary and wants to state what the plaintiff alleges. A draft currently presents the February 3 delivery as an established event.

Completed construction: The first amended complaint alleges delivery on February 3. First Am. Compl. ¶ 42, docket entry 19, Laurel Systems v. Cedar Harbor, No. TRAIN-CV-25-24 (filed Apr. 7, 2025).

Why this construction works: The pleading version and paragraph identify the allegation actually being summarized. The sentence marks its status as an allegation instead of converting it into proof. Do not retain paragraph 35 from the original complaint after changing the source name to the amended complaint. Read the operative pleading and preserve any qualifications in the alleged facts. The source card should distinguish filing date, alleged event date, and document version. Whether the allegation is admitted, supported, disputed, or treated in a particular procedural posture requires additional material that this packet does not supply.

Variation: For a discussion of how the allegations changed, cite both pleadings with their respective paragraphs and explain the difference. For a statement that delivery actually occurred, find an appropriate evidentiary or adjudicative source and describe what that source establishes. If a later amended pleading changes the paragraph numbering again, verify every moved allegation rather than mechanically replacing First with Second throughout the citations.

Example scope: Parties, court record, pleadings, dates, and alleged delivery are fictional. The example makes no factual finding or conclusion about the legal effect of a real pleading.

F049. Motion or memorandum

Working form: [Party's document title] at [page], [ECF entry] ([filing date]).

Capture: Party; document; case; entry; page system; date.

Check: Distinguish the party's argument from the court's disposition.

Common error: A requested remedy is not a remedy the court granted.

Source packet: Fictional packet TRAIN-D49 contains a defendant's Memorandum in Support of Motion to Exclude Appendix C, filed May 5, 2025, as docket entry 28 in Meridian Archive v. Flint Works, No. TRAIN-CV-25-29. Printed page 11 argues that the appendix should be excluded entirely. The court later enters an order excluding only two identified pages. The PDF's filing-system header uses page 13 for the memorandum's printed page 11 because a cover and contents page precede it. The assignment asks the writer to describe the defendant's argument, not the court's ruling.

Completed construction: Defendant's Memorandum in Support of Motion to Exclude Appendix C at 11, docket entry 28, Meridian Archive v. Flint Works, No. TRAIN-CV-25-29 (filed May 5, 2025) [printed pagination].

Why this construction works: The document title and party attribution identify whose position is being cited. The sentence should say that the defendant argued for complete exclusion, reserving the court's narrower disposition for its own order citation. The explicit pagination note makes the chosen coordinate clear where the record contains two page systems. Use the receiving convention consistently and ensure that another reader can locate the passage in the delivered file. A motion title can describe the requested remedy without proving that the request was granted. Keep the motion, supporting memorandum, exhibits, and order as separate document identities.

Variation: If the receiving court requires filing-system page numbers, inspect the relevant header and revise the locator to that system, rather than applying an assumed offset across every attachment. If the proposed sentence concerns the ruling, cite the later order and its operative passage. A citation to counsel's memorandum cannot be repurposed as the court's disposition merely by removing the words defendant argued.

Example scope: Case, party filings, page systems, and disposition are fictional. This example illustrates argument attribution and does not state any actual evidentiary ruling.

F050. Declaration or affidavit

Working form: [Name] Decl. ¶ [paragraph], [entry/exhibit] ([date]).

Capture: Declarant; date; paragraph; filing/attachment; qualification.

Check: Read qualifications and identify whether the declarant claims personal knowledge.

Common error: A citation does not resolve admissibility or credibility.

Source packet: Fictional packet TRAIN-D50 includes Mara Rowan's declaration dated June 4, 2025, filed as attachment 2 to docket entry 41 in a training case. Paragraph 6 describes records Rowan says she reviewed. Paragraph 7 states that she personally observed the first inspection; paragraph 8 reports what another employee told her about the second. The assignment asks for her account of the first inspection. A draft combines both inspections into one sentence asserting that Rowan witnessed them. The packet includes the declaration's qualifications and signature but no ruling about admissibility or credibility.

Completed construction: Rowan Decl. ¶ 7, docket entry 41-2 (June 4, 2025) [TRAIN-D50].

Why this construction works: The name, document type, paragraph, and attachment identify the relevant statement. Frame the sentence to reflect that Rowan declares she observed the first inspection. Do not extend her asserted personal knowledge to the second event, which the supplied declaration attributes to another person. Read the qualifications and surrounding paragraphs rather than treating the signature as proof that every statement has the same basis. The source card should preserve the declaration date and filing identity, because those can differ. A precise citation facilitates evaluation of the statement; it does not resolve whether the statement is admissible, credible, or sufficient for a particular legal purpose.

Variation: If discussing the second inspection, cite paragraph 8 and accurately identify the reported source of the information. If a corrected declaration changes paragraph 7, inspect the correction and determine which version the argument uses. If the declaration incorporates an exhibit, cite the exhibit's particular locator for its contents and the declaration for any separate authentication statement, keeping those source roles distinct.

Example scope: Declarant, events, declaration, qualifications, docket, and attachments are fictional. No real evidence ruling, credibility judgment, or personal-knowledge determination is asserted.

F051. Deposition transcript

Working form: [Witness] Dep. [page]:[line]–[page]:[line] ([date]).

Capture: Witness; date; volume; certified version; page/line; errata.

Check: Read the question and surrounding answer, and check relevant errata.

Common error: An isolated yes answer can be misleading without its question.

Source packet: Fictional packet TRAIN-D51 contains the certified deposition transcript of Eliot Vale, taken July 15, 2025, volume 1. At page 84, lines 12–16, counsel asks whether Vale saw the register before the May revision; lines 17–22 contain an answer limited to a preview copy. The answer continues at page 85, lines 1–4, explaining that Vale did not inspect the final version. An errata sheet changes an unrelated spelling at page 12 and leaves this passage unchanged. The assignment asks what Vale reviewed, including the limitation about the final version.

Completed construction: Vale Dep. vol. 1, 84:12–85:4 (July 15, 2025) [TRAIN-D51].

Why this construction works: The range includes the question and the qualifying continuation of the answer, allowing the reader to understand what the witness actually addressed. A citation limited to the affirmative words at page 84 would omit the distinction between preview and final versions. Use the transcript's printed pages and lines, not the four-page-per-sheet printout's sheet number. Check the relevant errata and preserve the certified version used. The source card should identify witness, session date, volume, transcript status, and any correction affecting the passage so a later editor can verify the quotation without searching multiple days of testimony.

Variation: If another deposition session on July 22 also has a page 84, include the correct session date and volume rather than relying on the witness's surname alone. If an errata entry changes this answer, retain both the original and correction and describe them accurately; do not silently replace the testimony while leaving a citation that appears to quote the unchanged transcript.

Example scope: Witness, testimony, dates, pagination, certification, and errata are fictional training facts. The example does not determine the legal effect of deposition testimony or corrections.

F052. Hearing or trial transcript

Working form: [Proceeding] Tr. [volume]:[page]:[lines] ([date]).

Capture: Proceeding; session date; volume; speaker; final transcript.

Check: Identify the particular day and speaker and distinguish argument from testimony.

Common error: A lawyer's statement in argument is not a witness's evidence.

Source packet: Fictional packet TRAIN-D52 supplies volume 3 of a trial transcript for August 12, 2025, in the Northmere Eastern Trial Court. Page 217, lines 6–14, contains counsel's argument that an index was complete. Page 218, lines 2–10, records witness Tessa Reed saying that two fields remained blank. The reporter's final certified transcript corrects the rough draft's mistaken speaker label on page 218. The assignment asks for Reed's testimony, and the record includes multiple trial days with repeated local page numbering. No finding resolving the completeness dispute is supplied.

Completed construction: Trial Tr. vol. 3, 218:2–10 (Aug. 12, 2025) (testimony of Tessa Reed) [TRAIN-D52].

Why this construction works: The proceeding, volume, session date, page, and lines identify the testimony in the final transcript. The speaker attribution is material because the nearby statement by counsel plays a different role. Use the corrected speaker label from the certified transcript rather than the rough draft's error. The sentence should report what Reed testified, leaving any credibility assessment or ultimate finding to the appropriate source. A transcript can contain testimony, argument, objections, and rulings in close succession. The citation should lead to the right component, and the prose should accurately describe that component's role.

Variation: For counsel's argument, cite volume 3, 217:6–14 and attribute it to counsel. For an oral ruling later in the session, cite the court's actual words and preserve any qualification or later written order. If the record is repaginated for an appellate appendix, verify the appendix locator separately and maintain a map to the transcript's original page-and-line coordinates.

Example scope: Court, trial, speakers, testimony, transcript versions, and pages are fictional. No actual fact finding, evidentiary status, or appellate record is represented.

F053. Interrogatory response

Working form: [Party's] Resp. to Interrog. No. [number], at [page] ([date]).

Capture: Request set; responding party; number; response/supplement; date.

Check: Check whether the response was amended and retain its qualifications.

Common error: A later supplement can make a first response incomplete as a source.

Source packet: Fictional packet TRAIN-D53 contains Lark Register Company's responses to the first set of interrogatories in a training civil case. Its initial response to Interrogatory 8, served September 2, 2025, identifies two employees and says the investigation continues. A supplemental response dated September 19 adds a third employee and corrects one employment date. The assignment asks which employees the company identified in its latest supplied response. Page 4 of the supplement contains the revised list. A second interrogatory set also has an Interrogatory 8, concerning a different topic.

Completed construction: Lark Register Company's Supplemental Response to First-Set Interrogatory No. 8, at 4 (Sept. 19, 2025) [TRAIN-D53].

Why this construction works: The responding party, set, request number, supplemental status, date, and page distinguish the intended response from several nearby possibilities. Read the original request together with the supplement to understand what the list answers. The sentence should report that the company identified the three employees, preserving any continuing-investigation qualification that remains. The citation does not independently establish that no other employee was involved. Keep initial and supplemental responses linked in the research record, with a note explaining whether the supplement replaces the whole answer or adds to it. Similar numbering across sets makes the set designation especially useful.

Variation: For a history of changing responses, cite the initial response and supplement separately and describe the added employee or corrected date. If the supplement responds only to part of Interrogatory 8, retain the relevant unreplaced original language rather than treating the supplement as a complete standalone answer. If a later response is disputed, accurately identify that dispute instead of assuming that the latest date resolves every evidentiary question.

Example scope: Company, case, interrogatories, responses, dates, employees, and qualifications are fictional. No actual discovery obligation or evidentiary effect is asserted.

F054. Request for admission response

Working form: [Party's] Resp. to Req. for Admis. No. [number] ([date]).

Capture: Request; response; qualification; amendments; case context.

Check: Read the precise request and response together before describing their effect.

Common error: A qualified response is not necessarily an unqualified admission.

Source packet: Fictional packet TRAIN-D54 supplies Request for Admission 12 from the first request set served on Cobalt Index Cooperative. It asks the cooperative to admit that it received and approved the final register on June 1, 2025. The September 10 response admits receipt of a preview copy that day but denies approval and denies that the received copy was final. The assignment asks the writer to summarize the response. The packet contains no amended response, withdrawal order, or ruling about its effect. A draft has shortened the response to an admission that the final register was approved.

Completed construction: Cobalt Index Cooperative's Response to First-Set Request for Admission No. 12 (Sept. 10, 2025) [TRAIN-D54].

Why this construction works: Read the request and response as a pair. The request combines receipt, approval, version, and date; the response treats those components differently. The summary should preserve the admitted preview receipt and the express denials rather than convert a qualified answer into an unqualified admission. The citation identifies the exact response but cannot repair prose that overstates it. Store both documents and any relevant instruction or qualification in the source card. Determining the procedural or evidentiary consequences would require the applicable rules and case context, which are outside the stipulated facts of this construction exercise.

Variation: If the writer needs a source establishing approval of a final register, this response does not supply it. Search the appropriate record rather than extracting the word admits in isolation. If an authorized amended response later changes the answer, identify the amendment and any relevant order. A response number alone is insufficient when several request sets use the same numbering or different parties answered identical requests.

Example scope: Cooperative, requests, response, documents, and factual positions are fictional. The example does not determine the binding effect, amendment, or withdrawal of any real admission.

F055. Bates-stamped exhibit

Working form: [Exhibit designation], [Bates identifier or range].

Capture: Exhibit; document identity; production; exact Bates range; page map.

Check: Confirm the identifier on the actual exhibit in the delivered record.

Common error: A production range can include multiple unrelated documents.

Source packet: Fictional packet TRAIN-D55 includes Exhibit 14, a three-page inspection log produced with Bates identifiers TRAIN-CEDAR-00421 through TRAIN-CEDAR-00423. The relevant entry appears on TRAIN-CEDAR-00422. The wider production range 00400–00480 also includes emails, invoices, and an unrelated draft plan. A working PDF merges the production into one file and places the relevant page at viewer position 57. The delivered exhibit uses the same Bates stamps but starts its own viewer count at 1. The assignment asks for the log entry as it appears in the delivered exhibit.

Completed construction: Ex. 14, Inspection Log, TRAIN-CEDAR-00422.

Why this construction works: The exhibit designation and exact Bates identifier locate the page without relying on a viewer count that changes when files are assembled. Including the document identity helps the reader distinguish the log from other materials in the production. The broad 00400–00480 range would force the reader through unrelated documents and might imply reliance on all of them. Confirm the visible stamp on the actual delivered exhibit, because a production index or draft exhibit list can contain transcription errors. Record the relationship among original production, exhibit number, and final record location so later renumbering can be repaired systematically.

Variation: If the entry continues onto TRAIN-CEDAR-00423, cite the two-page range after reading both pages. If an exhibit is replaced by a clearer copy with different stamps, preserve the mapping and identify the version actually supplied to the reader. If two productions reuse a numeric sequence with different prefixes, retain the full prefix; shortening the identifier to 00422 would erase the distinction between separate documents.

Example scope: Exhibit, log, production, Bates stamps, and page maps are fictional. The example does not authenticate a real record or establish the truth of an entry.

F056. Appellate appendix

Working form: [Required appendix designation] [volume]:[page].

Capture: Receiving convention; final appendix; volume; assigned page.

Check: Recheck the citation after appendix assembly and PDF export.

Common error: PDF viewer counts may shift while assigned record pages remain stable.

Source packet: Fictional packet TRAIN-D56 provides the final two-volume joint appendix in a Northmere training appeal. The supplied receiving convention uses JA followed by volume and assigned page. A declaration's paragraph 9 appears in volume 2 on assigned page 318. Its source filing used printed page 4, and a preliminary appendix draft placed it at assigned page 301. The final PDF viewer calls the page 126 because each volume has covers and preliminary material. The assignment asks for the reference that the receiving appellate panel can use in the final appendix.

Completed construction: JA 2:318 (declaration ¶ 9) [TRAIN-D56].

Why this construction works: The final assigned appendix page and volume are the controlling retrieval coordinates under the supplied convention. The parenthetical identifies the underlying component without substituting its original page for the appendix locator. Do not retain draft page 301 after final assembly or calculate the location from the viewer's offset without checking the actual page label. Open the exported deliverable and verify that assigned page 318 contains the cited paragraph. A reliable record map preserves original filing identity, original locator, appendix volume, assigned page, and final PDF location as different fields rather than treating them as interchangeable page numbers.

Variation: If the appendix is rebuilt after adding material, recheck all affected assigned pages even when the underlying declaration is unchanged. If the receiving convention requires a different designation, adapt the visible form to that instruction while retaining the verified mapping. If a cited document was omitted from the appendix, resolve its availability and permitted citation route instead of inventing an appendix page or assuming that the panel has the source filing.

Example scope: Appeal, receiving convention, appendix, declaration, and all page coordinates are fictional. No actual appellate rule or record sufficiency determination is stated.

F057. Audio or video evidence

Working form: [Exhibit/recording identifier], at [hh:mm:ss–hh:mm:ss] ([version/date]).

Capture: Recording; exhibit; duration; version; timestamp; transcript relation.

Check: Play the identified segment in the exact recording supplied to the reader.

Common error: Edited clips and full recordings usually have different time coordinates.

Source packet: Fictional packet TRAIN-D57 supplies Exhibit 22, a full 48-minute inspection recording dated April 18, 2025. The relevant exchange runs from elapsed time 00:17:42 to 00:18:09. A separately edited three-minute clip begins with that exchange at 00:00:20 and omits an earlier question. The video's displayed wall clock is eleven minutes fast according to the packet's synchronization note. The assignment asks for a citation to the full recording supplied to the reader. An unverified transcript gives slightly different wording for the last sentence of the exchange.

Completed construction: Ex. 22, Full Inspection Recording, at 00:17:42–00:18:09 (Apr. 18, 2025 version) [TRAIN-D57].

Why this construction works: The exhibit and version identify the file, and the timestamp range uses elapsed playback time in that file. The clip's coordinates and the displayed wall clock are separate systems. Play the full segment and enough surrounding material to confirm the speaker, question, and qualifications before quoting it. The synchronization note matters if the argument concerns real-world timing, but it does not require replacing the file's elapsed-time locator. If quoting the words heard in the recording, check them against the audio rather than treating the unverified transcript as a definitive substitute. Preserve the exact file and its duration in the source record.

Variation: If the clip is the actual exhibit delivered, cite its own identifier and timestamps and explain any omission material to the discussion. If the transcript is separately admitted or assigned a record identifier, cite it accurately for its text while keeping the recording reference for comparison. A time range copied from a different edit can be wrong even when both files bear the same event title.

Example scope: Recording, exhibit, timing, synchronization note, transcript, and exchange are fictional. The example makes no actual authentication, admissibility, or event-timing determination.

F058. Docket entry

Working form: [Case], No. [docket], docket entry [number] ([court/date]).

Capture: Court; case; docket; entry; attachment; entry date.

Check: Open the entry and distinguish the docket description from the attached document.

Common error: A docket text summary is not always the operative document itself.

Source packet: Fictional packet TRAIN-D58 contains a docket sheet in Orchard Index v. Slate Harbor, No. TRAIN-CV-25-52, in the Northmere Eastern Trial Court. Entry 44, entered August 11, 2025, has a short docket description saying Motion resolved. Attachment 1 is the signed order granting part of the motion; attachment 2 is an exhibit list. The docket description does not specify which part was granted. The assignment asks for a citation identifying the docket event, while a separate sentence about the scope of relief would require the signed order's text.

Completed construction: Orchard Index v. Slate Harbor, No. TRAIN-CV-25-52, docket entry 44 (Northmere Eastern Trial Ct. Aug. 11, 2025).

Why this construction works: The case, court, docket number, entry number, and entry date identify the event. This form is suitable for referring to the entry as an event, but the summary text cannot establish details it does not state. Open the attachment when the proposition concerns the ruling's contents and cite the particular order and page. Distinguish entry date from any earlier signature date or later service date shown in the files. The source card should record which attachment was inspected and its document role, because entry 44 alone points to more than one item in this packet.

Variation: To identify the signed order, add attachment 1 and the verified page supporting the sentence. To discuss the exhibit list, use attachment 2 and its own locator. If the docket later corrects the entry's description, preserve the correction when discussing procedural history. A database alert that paraphrases the entry is another layer of summary and should not replace inspection of the source when the exact disposition matters.

Example scope: Case, court, docket, entry, attachments, and disposition are fictional. This example does not report actual litigation activity or establish a real order's scope.

Transactions

F059. Executed agreement

Working form: [Agreement title] § [section] ([parties/date]).

Capture: Executed document; parties; execution/effective dates; section; amendments.

Check: Verify the signed version and any amendment affecting the provision.

Common error: A negotiation draft can look identical except for one operative clause.

Source packet: Fictional packet TRAIN-T59 contains an executed Register Hosting Agreement between Finch Data Cooperative and Lantern Archive Company. Both signature pages are dated February 14, 2025, while section 1 specifies a March 1 effective date. Section 6.2 addresses export of archived records. A negotiation draft dated February 10 has a different export interval but an otherwise nearly identical layout. The packet includes a later amendment affecting fees only and expressly leaving section 6.2 unchanged. The assignment asks for the executed agreement's export provision, with the parties and version made clear.

Completed construction: Register Hosting Agreement § 6.2 (Finch Data Cooperative–Lantern Archive Company, executed Feb. 14, 2025; effective Mar. 1, 2025) [TRAIN-T59].

Why this construction works: The title, parties, section, and labeled dates identify the signed instrument and distinguish it from the negotiation draft. Inspect the signature pages and the actual clause instead of trusting the filename final. The source card should retain the amendment and the determination that it affects fees rather than the cited export clause. Execution date and contractual effective date perform different functions and should not be collapsed into one unexplained date. The completed citation makes the intended text retrievable; evaluating enforceability, interpretation, or performance would require analysis beyond the document identity supplied here.

Variation: If a later amendment changes section 6.2, cite the amendment alongside the underlying agreement or use an accurately identified restated instrument after inspecting it. If discussing the negotiation history, label and cite the February 10 draft expressly rather than giving its language the appearance of executed terms. A comparison should quote or summarize the relevant difference from both versions and preserve their dates.

Example scope: Parties, agreement, signatures, dates, clauses, and amendment are fictional. No actual contract, enforceability determination, or transactional obligation is supplied.

F060. Amendment to agreement

Working form: [Amendment title] § [section] ([date]) (amending [agreement]).

Capture: Amendment; underlying instrument; section; operative terms.

Check: Trace how the amendment changes the referenced agreement and effective date.

Common error: The amendment's section number does not necessarily match the amended clause.

Source packet: Fictional packet TRAIN-T60 includes the First Amendment to the Register Hosting Agreement between Finch Data Cooperative and Lantern Archive Company. It is executed June 18, 2025. Amendment section 2 replaces agreement section 6.2, while amendment section 4 makes that replacement effective July 1. Amendment section 3 changes an unrelated notice address. The original agreement's section 2 concerns definitions and is not the provision being amended. The assignment asks for the instrument that changed the export clause. A draft citation incorrectly says that agreement section 2 was replaced because the amendment uses that section number.

Completed construction: First Amendment to Register Hosting Agreement § 2 (June 18, 2025) (replacing agreement § 6.2, effective July 1, 2025) [TRAIN-T60].

Why this construction works: Keep the amendment's internal locator separate from the destination clause in the underlying agreement. Section 2 tells the reader where to find the changing instruction; section 6.2 tells the reader what that instruction changes. Read the effective-date provision as well as the replacement language before describing when the revised clause operates. The source card should map original clause, amendment instruction, replacement text, and effective term. A revised working copy is useful, but its accuracy should be checked against the signed instruments rather than treated as a substitute for the amendment itself.

Variation: If a second amendment modifies only one sentence of the replacement clause, trace the sequence through both amendments. If the parties execute an amended and restated agreement, determine from that instrument how it treats the prior documents before selecting a citation. Do not assume that a later document titled amendment replaces the entire agreement or that its execution date governs every change it contains.

Example scope: Agreement, parties, amendment, numbering, text, and dates are fictional training facts. The example does not determine the legal operation of any real amendment.

F061. Schedule or exhibit to agreement

Working form: [Agreement short name], sched. [label] § [section] ([version]).

Capture: Agreement; exact schedule label; version; incorporation; replacement.

Check: Read incorporation and priority provisions before relying on the schedule.

Common error: A later replacement schedule can supersede the original attachment.

Source packet: Fictional packet TRAIN-T61 supplies a Register Services Agreement dated April 1, 2025, with Schedule B-2 titled Delivery Fields. Section 3 of that schedule lists the required export fields. The agreement's incorporation clause identifies B-2 by exact label, and its priority clause addresses conflicts between the main text and schedules. A July amendment replaces Schedule B-2 with a version dated July 15 while retaining the same label. A draft attachment called Schedule B lists a broader set of fields but was not incorporated. The assignment concerns the replacement B-2 supplied with the amendment.

Completed construction: Register Services Agreement, sched. B-2 § 3 (replacement dated July 15, 2025) [TRAIN-T61].

Why this construction works: The exact schedule label and replacement date distinguish the operative attachment from the draft and the original B-2. Read the incorporation and priority clauses before describing what role the schedule plays. Do not shorten B-2 to B merely because the title seems similar; that alteration points to a different document in this packet. The source card should connect the schedule to the agreement and replacing amendment, preserving all three files. A schedule's content can be accurately quoted while its contractual role remains misunderstood, so citation review must include both identity and the document's relationship to the agreement.

Variation: For a transaction before the replacement's stated operation, examine the original schedule and amendment's temporal terms rather than applying the July attachment retrospectively. If the main text and schedule appear inconsistent, cite both relevant provisions and analyze the priority clause instead of silently choosing the more convenient wording. If an attachment is missing from a public copy, do not reconstruct its fields from a cover-page reference alone.

Example scope: Agreement, schedules, amendment, labels, dates, and incorporation terms are fictional. No real contractual hierarchy or performance requirement is asserted.

F062. Securities filing exhibit

Working form: [Issuer], [filing type], ex. [number], [section/page] (filed [date]), [accession/URL].

Capture: Issuer; filing; accession; exhibit; date; omitted portions.

Check: Inspect the specific exhibit and note missing schedules or redacted portions.

Common error: The filing's cover page does not establish the complete agreement's contents.

Source packet: Fictional packet TRAIN-T62 contains a public filing by Alder Systems Company in an invented Northmere securities registry. The filing is designated TRAIN Form 8-K, filed August 20, 2025, accession TRAIN-ACC-25-062. Exhibit 10.2 is a licensing agreement signed August 12. Section 7 appears on printed page 9 of the exhibit. An exhibit note says Schedule C is omitted and certain pricing terms are redacted. The assignment asks for the publicly available section 7 text, not for the complete transaction economics. The filing cover lists the exhibit but does not reproduce its clauses.

Completed construction: Alder Systems Company, TRAIN Form 8-K, ex. 10.2, § 7, at 9 (filed Aug. 20, 2025), accession TRAIN-ACC-25-062.

Why this construction works: The issuer, filing type, accession, exhibit number, and locator identify the actual public document. The filing date belongs to the submission; the agreement's August 12 signature date is a separate fact that can be stated when relevant. Inspect the exhibit itself and preserve its omission and redaction notices. The citation supports a description of the available section 7 text, but it does not establish the contents of omitted Schedule C or redacted prices. Public availability of a filing does not guarantee that every attachment to the underlying executed agreement has been disclosed.

Variation: If a later filing supplies an amended exhibit, compare the specific clause and identify the later accession. If the argument depends on Schedule C, mark that evidence gap and obtain an appropriate source rather than inferring the schedule's contents from a reference in section 7. If citing incorporation by reference to another filing, follow that reference and identify the exhibit actually containing the text.

Example scope: Issuer, registry, form, accession, agreement, and redactions are fictional. TRAIN Form 8-K is a teaching identifier, not an actual SEC filing or accession.

F063. Corporate resolution or minutes

Working form: [Entity], [Resolution/minutes title] at [page] ([date]).

Capture: Entity; body; meeting/action; signed or approved status; page.

Check: Confirm whether the record is adopted, draft, corrected, or subject to approval.

Common error: A proposed resolution does not establish corporate action.

Source packet: Fictional packet TRAIN-T63 includes board minutes of Birch Harbor Cooperative for a meeting on September 3, 2025. The minutes were approved September 17 and bear an approval notation. Printed page 4 records adoption of Resolution TRAIN-BHC-25-9 authorizing a named officer to negotiate within specified limits. A meeting packet contains a broader proposed resolution that would have authorized execution, but the approved minutes show that wording was changed before adoption. The assignment asks what action the board recorded as adopted, not whether the resulting transaction is legally binding.

Completed construction: Birch Harbor Cooperative, Board Minutes at 4 (meeting Sept. 3, 2025; approved Sept. 17, 2025) (Resolution TRAIN-BHC-25-9).

Why this construction works: The meeting and approval dates distinguish when the action occurred from when the minutes were approved. The resolution identifier assists retrieval, and the pinpoint reaches the adopted action as recorded. Describe the authority to negotiate within the stated limits; do not substitute the proposed authority to execute. Draft resolutions, meeting packets, approved minutes, and signed written consents can be different records with different roles. The source card should state the record's approval or correction status and preserve any adopted text attached to it. Citation precision does not independently resolve corporate authority or the legal effect of later conduct.

Variation: If corrected minutes later change the recorded vote or text, inspect the correction and explain which version is used. If the board acted by written consent, identify that instrument rather than inventing a meeting date. If a subsequent resolution expands the officer's authority, cite the later resolution for that expansion and keep the earlier limited action distinct in the chronology.

Example scope: Cooperative, board, minutes, resolution, dates, and authorized action are fictional. No actual corporate act, authority opinion, or transaction approval is represented.

Secondary works

F064. Authored book

Working form: [Author], [Title] [pinpoint] ([edition] [year]).

Capture: Author; title; edition; year; volume; page/section.

Check: Compare the title page and cited passage to the edition named in the citation.

Common error: A quotation copied from an older edition may not appear at the new page.

Source packet: Fictional packet TRAIN-S64 supplies Lena Rowan's book Mapping Public Records, second edition, published by the fictional Northmere Study Press in 2024. The title page identifies Rowan as author, and page 146 contains the passage assigned for discussion. A first edition from 2018 places a related but differently worded passage at page 119. A bookseller's listing has mistakenly carried the first edition's publication year into the second edition's description. The assignment asks for the passage as it appears in the inspected second edition. The packet includes title, copyright, and relevant text pages.

Completed construction: Lena Rowan, Mapping Public Records 146 (2d ed. 2024) [TRAIN-S64].

Why this construction works: Use the author, title, edition, year, and pinpoint from the book actually inspected. The bookseller's metadata can assist discovery but should not override the title and publication pages. Do not update the edition label while retaining a quotation or page copied from the first edition. Compare the exact passage, including any qualification or revised terminology, before using it. If the work has multiple volumes, add the volume necessary to locate the page. The source card should preserve enough publication information to distinguish editions even when a library catalog groups them under one title record.

Variation: If comparing the author's changing view, cite the 2018 and 2024 passages separately and explain their differences. If an electronic rendition replaces stable pages with locations, inspect whether it preserves print pagination before using page 146. A device-specific location number should be identified as such rather than presented as a printed page. If a passage quotes another work, distinguish Rowan's discussion from the underlying author's words.

Example scope: Author, book, publisher, editions, metadata error, and pages are fictional. No copyrighted text or actual author's position is reproduced or attributed here.

F065. Chapter in edited collection

Working form: [Chapter author], [Chapter title], in [Volume title] [first page], [pinpoint] ([editor], [year]).

Capture: Chapter author/title; editors; volume; edition; pages.

Check: Attribute the chapter to its author while identifying the containing work.

Common error: An editor is not automatically the author of each chapter.

Source packet: Fictional packet TRAIN-S65 contains the edited collection Registers in Practice, edited by Mara Vale and Eliot Reed and published in 2025. Chapter 6, Written Access Paths, is authored by Tessa Rowan and begins at page 101. The assigned discussion appears at page 118. The collection's cover prominently displays the editors' names, while the chapter opening identifies Rowan as its author. An appendix to the chapter reproduces a separately attributed checklist. The assignment concerns Rowan's own explanation in the chapter body, not the editors' introduction or the appended checklist.

Completed construction: Tessa Rowan, Written Access Paths, in Registers in Practice 101, 118 (Mara Vale & Eliot Reed eds., 2025) [TRAIN-S65].

Why this construction works: The chapter author and title identify the contribution, while the containing title and editors identify the larger work. The first page locates the chapter's beginning; the second page locates the passage used. Do not assign authorship to the editors merely because their names appear on the cover. Read the chapter's byline and distinguish its text from attributed material reproduced within it. The source card should record the collection's edition if there is one, the chapter's page range, and the particular component relied on so later checking does not stop at the volume's general catalog record.

Variation: If the proposition comes from the editors' introduction, cite that contribution and its actual authorship rather than this chapter. If quoting the appended checklist, identify its creator and reproduced location, and inspect the original when the claim depends on that source. If a later collection reprints the chapter with revisions, verify which version supplies the quoted language instead of assuming that identical titles mean identical text.

Example scope: Authors, editors, collection, chapter, checklist, and pagination are fictional. The example demonstrates contribution-level attribution without borrowing an actual publication's text.

F066. Journal article

Working form: [Author], [Article title], [volume] [journal] [first page], [pinpoint] ([year]).

Capture: Author; article; journal; volume; final pages; date; DOI.

Check: Use the final publication record and inspect the particular passage.

Common error: An abstract's summary may omit limitations in the article.

Source packet: Fictional packet TRAIN-S66 supplies the final published article Narrow Searches, Wider Records by Omar Vale in volume 7 of the fictional TRAIN Records Review, beginning at page 210 in 2025. Page 228 discusses a study limited to six participating offices. The abstract summarizes the finding broadly, and a prepublication manuscript uses different page numbers and includes an office later excluded from the final analysis. The assignment asks for the final article's qualified finding. The journal record supplies no DOI, so none is assumed or constructed from the article title.

Completed construction: Omar Vale, Narrow Searches, Wider Records, 7 TRAIN Records Rev. 210, 228 (2025).

Why this construction works: The author, title, journal, volume, first page, pinpoint, and year identify the final publication and the passage actually read. Preserve the six-office limitation in the sentence; a polished citation does not justify generalizing the abstract's shorthand to all offices. Compare the final text with any prepublication version used earlier in drafting. A DOI may be useful when one is verified, but inventing one would introduce a false identifier. The source card should record publication status, version, and any correction notice encountered, along with the article's method and relevant limits where the proposition depends on a study result.

Variation: If an erratum changes the sample or reported figure, cite and account for the correction. If the discussion is about the manuscript's earlier approach, identify that version as a manuscript and cite its own locator. If quoting an authority discussed in the article, inspect that authority for a claim about its holding rather than treating the article's summary as a substitute for the primary text.

Example scope: Author, journal, article, study, versions, and pages are fictional. No actual study result, DOI, peer-review status, or legal holding is asserted.

F067. Article-number publication

Working form: [Author], [Title], [journal] [volume], art. [number], § [locator] ([date]).

Capture: Article number; journal/volume; section/paragraph; version.

Check: Preserve the article number as an identifier and use the publication's available locators.

Common error: An article number should not be silently treated as a first page.

Source packet: Fictional packet TRAIN-S67 provides Hana Reed's article Field Labels and Retrieval Errors in volume 4 of the TRAIN Journal of Record Studies. The journal assigns article number e047 and publishes the work on February 6, 2025. Its HTML version has numbered sections and paragraphs; section 3.2, paragraph 4, contains the assigned limitation. The PDF begins its internal pagination at 1, and e047 is printed in the header as an identifier rather than a page. The assignment asks for a citation to the stable numbered HTML passage. No DOI is supplied.

Completed construction: Hana Reed, Field Labels and Retrieval Errors, TRAIN Journal of Record Studies 4, art. e047, § 3.2, ¶ 4 (Feb. 6, 2025).

Why this construction works: Label e047 as an article number so the reader does not mistake it for a first page. The section and paragraph supply a locator within the article, using numbering actually assigned by the publication. Do not transform e047 into page 47 or add a journal page range that the source does not have. Capture the rendition used and check whether its numbering matches another rendition before switching locators. The source card should retain the title, article identifier, volume, version, and relevant passage, allowing a reader to find the work even if the publisher changes the surrounding website layout.

Variation: If the HTML paragraphs are unnumbered but the final PDF has stable printed pages, use an identified PDF page locator after inspection. If a correction is published as a separate article number, cite that correction and explain which statement it changes. If the journal republishes e047 with a version suffix, preserve the suffix rather than assuming that the base article number uniquely identifies unchanged content.

Example scope: Author, journal, article, identifier, numbering, and publication date are fictional. No real article number, DOI, study finding, or publication record is asserted.

F068. Preprint or working paper

Working form: [Author], [Title] [pinpoint] ([series/no., version date]), [repository/DOI].

Capture: Author; title; series; version; repository; publication status.

Check: Check whether a later published version changes the text used.

Common error: A preprint should not be described as peer reviewed without support.

Source packet: Fictional packet TRAIN-S68 contains Iris Vale's working paper Comparing Archive Search Interfaces, TRAIN Research Series No. 25-03, version 2 dated March 4, 2025. The repository labels it a working paper and provides no peer-review claim. Page 17 reports an early sample of 40 tasks. A later journal version in the packet expands the sample to 65 and changes the conclusion about one interface. The assignment asks how the early version described the initial study, so that version remains relevant as a historical research object. Both versions have similar titles.

Completed construction: Iris Vale, Comparing Archive Search Interfaces 17 (TRAIN Research Series No. 25-03, working paper v. 2, Mar. 4, 2025), https://training.example/papers/25-03/v2.

Why this construction works: The series number, version, date, and status distinguish the working paper from the later publication. Describe its result as belonging to the initial 40-task study and preserve any stated uncertainty. A repository's professional appearance does not supply a peer-review status that the record does not state. If the argument instead concerns the author's final published conclusion, inspect and cite the later article rather than using the working paper's convenient locator. The source card should link related versions while retaining their separate dates, text, and sample definitions, so an editor can identify which result each citation actually supports.

Variation: If version 3 silently replaces the repository download, use the preserved version 2 file or a verified version-specific record for the historical comparison. If the paper is withdrawn, identify that status when relevant. A later journal publication does not make every earlier sentence part of the final article, and a citation should not imply such continuity without a textual comparison.

Example scope: Author, paper, series, repository, samples, and later article are fictional. The .example URL is illustrative, and no actual peer-review or research-status claim is made.

F069. Looseleaf or updated treatise

Working form: [Author], [Title] § [section] ([edition/release/update]).

Capture: Section; edition; release; update date; page if stable.

Check: Preserve the particular update information shown for the section used.

Common error: A general website copyright year may not identify the section's version.

Source packet: Fictional packet TRAIN-S69 supplies section 12.4 of Mara Rowan's Register Practice Manual, second edition, maintained through replacement releases. The section's footer identifies Release 18, updated April 2025. The publisher's website has a 2026 copyright footer, while the binder's original title page says 2022. A neighboring section was updated in Release 20 but section 12.4 was not. The assignment asks for the discussion printed in the supplied section 12.4 pages. The release instructions show which pages were replaced and which were retained.

Completed construction: Mara Rowan, Register Practice Manual § 12.4 (2d ed., Release 18, Apr. 2025) [TRAIN-S69].

Why this construction works: The section's own release information identifies the text being used. Neither the binder's original year nor the website's general footer necessarily describes that section's update. Preserve the replacement-page notice with the cited pages so another reader can confirm the version. A maintained work can contain sections updated at different times; assigning the newest release date to every section would falsely suggest uniform currency. Read the cited passage and its underlying authorities when making a legal proposition rather than assuming that a release label proves all references have been independently rechecked. The citation locates commentary, whose role remains distinct from primary law.

Variation: If Release 21 replaces section 12.4, compare the actual passage before changing the date in the manuscript. If the online version gives a section-specific update date instead of a release number, record that date and the retrieval information without inventing a print release. If quoting an older formulation for historical analysis, explicitly identify the earlier release and explain why it is the version being discussed.

Example scope: Author, manual, editions, releases, publisher, and update history are fictional. No actual treatise's currency, commentary, or legal conclusions are represented.

F070. Restatement provision

Working form: Restatement [series/title] § [section] [comment/illustration] ([edition/year]).

Capture: Issuing organization; edition/draft; section; component.

Check: Distinguish black-letter text, comment, illustration, and reporter's note.

Common error: A tentative draft is not the same work as an adopted final edition.

Source packet: Fictional packet TRAIN-S70 includes the TRAIN Restatement of Record Stewardship, issued by the invented Northmere Legal Study Institute in a final 2025 edition. Section 24 has a main proposition, comment b, illustration 3, and a reporter's note. The assigned passage is illustration 3 under comment b. An earlier tentative draft numbered the same subject section 21 and gave the illustration a different outcome. The assignment asks how the final work illustrates a hypothetical, without claiming that any court has adopted the work as governing law.

Completed construction: TRAIN Restatement of Record Stewardship § 24 cmt. b, illus. 3 (Northmere Legal Study Institute, final ed. 2025).

Why this construction works: Identify the component within the section because an illustration is not the same text as the main proposition or reporter's note. The final-edition description distinguishes the adopted publication from the tentative draft. Describe the source as the Institute's illustration, and avoid attributing its conclusion to a court without an independently inspected judicial source. Keep the section, comment, illustration, edition, and issuing body together in the source card. The useful analogy may depend on the hypothetical's facts, so read the entire illustration and its surrounding comment rather than quoting only its concluding sentence.

Variation: If the sentence concerns the reporter's account of cases, cite the reporter's note and inspect the central cases before making claims about their holdings. If discussing the project's development, cite the tentative draft with its actual draft number, date, and section. A later final edition does not retroactively change what the draft said, nor does final publication by an institution establish adoption by a particular jurisdiction.

Example scope: Institute, restatement, subject, sections, illustration, and draft history are fictional. This is not an actual Restatement or a statement about any real issuing organization's adoption process.

F071. Uniform or model act

Working form: [Issuing body], [Act title] § [section] ([version/year]).

Capture: Issuing body; act; draft/final status; section; local enactment if relevant.

Check: Compare the model text with the actual jurisdiction's enactment when claiming local law.

Common error: A model provision does not prove adoption without changes.

Source packet: Fictional packet TRAIN-S71 provides the Model Register Exchange Act, final 2024 text issued by the invented Northmere Drafting Conference. Model section 8 specifies a default delivery interval. A fictional jurisdiction, Alder Province, enacts a differently numbered provision in 2025 that changes the interval and adds an exception. A conference webpage lists Alder as having legislation on the subject but does not reproduce the local modifications. The assignment asks for the model's recommended language and a separate comparison with Alder's enacted text. Both documents are available in the packet.

Completed construction: Northmere Drafting Conference, Model Register Exchange Act § 8 (final text 2024) [TRAIN-S71].

Why this construction works: The issuing body, title, section, and version identify the recommendation. Describe it as model text, reserving statements about Alder's law for the enacted local source. An adoption list can guide research but cannot establish that the jurisdiction copied every word unchanged. Compare definitions, exceptions, numbering, and effective terms as well as the headline interval. The source card should map model section 8 to the actual local provision without replacing either identifier. A citation to the model is useful for explaining the drafting proposal or comparing approaches; it does not independently prove a duty imposed by a jurisdiction.

Variation: For a statement about Alder's interval, cite the local enactment and identify its added exception. If a revised model later changes section 8, distinguish the model revision from any later local amendment; one does not automatically establish the other. If the source is only a discussion draft, preserve that status rather than labeling it final because a conference hosted the file.

Example scope: Conference, model act, jurisdiction, local enactment, and adoption list are fictional. No actual uniform-law organization, adoption, or local legal rule is represented.

F072. Legal encyclopedia or annotation

Working form: [Author if identified], [Entry/annotation title], [publication] § [section] ([version]).

Capture: Entry; author; publication; update; section; underlying authorities.

Check: Read cited primary authorities when the proposition concerns their holdings.

Common error: A secondary summary cannot replace inspection of a central judicial source.

Source packet: Fictional packet TRAIN-S72 supplies an entry titled Register Authentication by Nolan Reed in the TRAIN Encyclopedia of Record Practice, section 16, updated May 2025. The entry summarizes three fictional decisions and places a qualification in its final paragraph. The writer has read the entry but has not yet opened the central decision discussed in paragraph 2. A draft says that the decision conclusively resolves the client's situation, omitting the entry's qualification. The assignment asks for an accurate citation to the secondary discussion and a clear research step before relying on the underlying decision.

Completed construction: Nolan Reed, Register Authentication, TRAIN Encyclopedia of Record Practice § 16 (updated May 2025).

Why this construction works: The author, entry title, publication, section, and update identify the commentary actually consulted. Attribute its synthesis to the entry and preserve the qualification. A claim about the central decision's holding requires inspection of that decision, including its facts, posture, reasoning, and relevant treatment, rather than reliance on this secondary summary alone. The source card can link the entry to the authorities it identifies while marking which have been read. This makes the research gap visible without pretending that citation formatting completes substantive verification. A section-specific update date is more useful than a general website copyright year when the entry supplies one.

Variation: After opening the primary decision, cite its supporting passage for the holding and use the encyclopedia for its broader synthesis if that remains useful. If the entry quotes a dissent or a procedural order, correct the source-role description before adopting its summary. If an annotation is maintained in numbered releases, identify the actual release used rather than assuming the page displays today's complete legal position.

Example scope: Author, encyclopedia, entry, decisions, and update are fictional. The uninspected-primary-source gap is part of the exercise; no real holding or current treatment is asserted.

Digital and data

F073. Web page

Working form: [Author/organization], [Page title] ([publication/update date]), [URL] (accessed [date] if useful).

Capture: Author; page title; visible date; exact URL; archived copy.

Check: Verify that the link opens the actual item and distinguish publication and retrieval dates.

Common error: A footer year is not a reliable publication date.

Source packet: Fictional packet TRAIN-W73 preserves the Northmere Archive Office's page titled How to Request an Index Copy. The page displays a publication date of January 12, 2025, and a section-specific update of June 6. The researcher captures it on October 1. The sitewide footer says 2026, but no page content is assigned that publication year. The exact page URL ends in /requests/index-copy; the agency home page has a different address. The assignment asks for the instructions shown in the preserved June update, not for a claim that the website will remain unchanged. The fictional page was captured on October 1, 2026.

Completed construction: Northmere Archive Office, How to Request an Index Copy (updated June 6, 2025), https://training.example/requests/index-copy (accessed Oct. 1, 2026).

Why this construction works: The organization, item title, displayed update date, exact URL, and access date identify the page and distinguish content timing from retrieval timing. Do not use the footer's year as the page's publication date. Preserve the captured page and any linked attachment actually relied on, because a live link may later return revised instructions. If the page states that a separate rule governs, inspect that rule before characterizing these instructions as a legal requirement. The source card should record visible dates and their labels rather than resolving ambiguous metadata by guessing a convenient year.

Variation: If the page has no publication or update date, omit an invented date and identify retrieval information when useful under the receiving convention. If the instructions appear only in a linked PDF, cite that PDF's own title, version, and locator. If a later capture differs, compare the actual content before describing the difference as a policy change rather than a layout or navigation change.

Example scope: Office, page, dates, instructions, and capture are fictional. The reserved .example URL is a teaching address, not an inspected live website.

F074. News report

Working form: [Author], [Article title], [publication] ([date]), [URL or page].

Capture: Author; publication; date; edition; passage; correction status.

Check: Distinguish what the reporter observed from what a quoted source asserted.

Common error: A report of an allegation does not independently establish the allegation.

Source packet: Fictional packet TRAIN-W74 includes Mira Vale's article Archive Expansion Announced in the TRAIN Civic Ledger, dated February 18, 2025. The reporter personally describes an announcement event but attributes the projected completion date to a contractor. A February 20 correction changes the contractor's quoted month from September to November. The preserved article shows the correction notice, while an earlier screenshot contains the original month. The assignment asks what the corrected report attributes to the contractor. No independent construction schedule or completed-project record is supplied.

Completed construction: Mira Vale, Archive Expansion Announced, TRAIN Civic Ledger (Feb. 18, 2025, corrected Feb. 20, 2025), https://training.example/news/archive-expansion.

Why this construction works: Identify the article and correction status, then attribute the projected date to the contractor as reported. The reporter's presence at the announcement does not independently verify that the project will finish on that date. The sentence should avoid converting a forecast into an accomplished fact or an official commitment. Read the correction notice and preserve the version cited, especially when different captures remain in circulation. The source card should distinguish reporter observation, quoted assertion, editorial correction, and any underlying document linked by the story. Those distinctions matter even when a single news article contains all four.

Variation: If discussing how public reports changed, cite the original capture and corrected article separately, making their dates clear. If the proposition concerns the actual contractual completion term, obtain and cite the appropriate contract or official record. If a later article reports a delay, inspect its sources instead of assuming that its publication date alone makes every assertion more reliable than the earlier report.

Example scope: Reporter, publication, article, contractor, forecast, and correction are fictional. No actual news event or factual allegation about an identifiable person or business is asserted.

F075. Social-media post

Working form: [Display name] ([account]), [post description] ([date/time]), [post URL/identifier].

Capture: Account; post ID; date/time; content; context; capture.

Check: Preserve the individual post and distinguish account identity claims from verified authorship.

Common error: A cropped screenshot can omit replies, edits, or the preceding context.

Source packet: Fictional packet TRAIN-W75 contains a preserved post on the invented TRAIN Social service. The display name is Harbor Archive Updates and the handle is @harbor_index_train. Post identifier TRAIN-POST-7501 bears a timestamp of March 2, 2025, 14:20 UTC. It replies to a question about a pilot office and says that its register will open Monday. A cropped screenshot omits the preceding question and account handle. The account claims an agency affiliation, but the packet supplies no independent verification of who controlled it. The assignment studies the public message itself.

Completed construction: Harbor Archive Updates (@harbor_index_train), reply announcing the pilot register's Monday opening (Mar. 2, 2025, 14:20 UTC), TRAIN Social post TRAIN-POST-7501, https://training.example/posts/TRAIN-POST-7501.

Why this construction works: The account, individual post identifier, timestamp, and contextual description distinguish the message from a profile page or detached screenshot. Preserve the preceding question because it limits the announcement to a pilot office. Attribute the statement to the account unless separate evidence verifies the author's identity or agency authority. Display names can change and handles can be reused, so the preserved post and capture record are useful alongside the visible citation. The post may be an object of study or evidence of a communicated assertion; citing it does not establish that the announced opening occurred or that the account spoke officially.

Variation: If the post is edited, identify the captured version and record any displayed edit information. If a later reply corrects Monday to Tuesday, include that context where material. If a screenshot is the only surviving copy, describe its provenance and omissions rather than presenting the cropped image as a complete verified post history.

Example scope: Service, account, post, affiliation claim, content, and dates are fictional. The .example address is illustrative; no real account identity or event is verified.

F076. Podcast or interview

Working form: [Speaker/creator], [Episode title], [series], at [timestamp] ([date]), [URL].

Capture: Episode; speakers; recording version; timestamp; transcript.

Check: Attribute the statement to the actual speaker and verify transcript accuracy where material.

Common error: Episode descriptions are not necessarily the speaker's words.

Source packet: Fictional packet TRAIN-W76 supplies episode 12 of the podcast Record Work, titled Building a Search Register, released April 8, 2025. Host Lena Reed interviews archivist Omar Rowan. In the full 42-minute recording, Rowan describes a pilot limitation at 00:18:10–00:18:44. The episode description paraphrases that limitation more broadly, and an automated transcript incorrectly assigns one sentence to the host. A later promotional clip begins at a different point and has different elapsed timestamps. The assignment quotes Rowan's statement from the full recording after checking the sound and surrounding exchange.

Completed construction: Omar Rowan, interview in Building a Search Register, Record Work, ep. 12, at 00:18:10–00:18:44 (Apr. 8, 2025), https://training.example/podcasts/record-work/12.

Why this construction works: Attribute the statement to the actual speaker while identifying the episode and series that contain it. The time range refers to the full recording, so a reader should receive or reach that version. Do not treat the episode description as a verbatim statement by the interviewee or reproduce the transcript's incorrect speaker label. Record the host, guest, release date, recording version, and relevant context in the source card. If the claim depends on exact wording, compare the transcript with the audio and disclose material uncertainty rather than allowing a machine transcription error to become a quotation.

Variation: If the promotional clip is cited, use its own title or identifier and verified timestamps, noting any context lost in editing. If quoting the host's question, attribute it to Reed and identify the corresponding segment. If an episode is reissued with corrections or inserted advertisements that shift timestamps, inspect the new version or preserve the original recording used for the citation.

Example scope: Podcast, participants, episode, transcript, recording, and timestamps are fictional. The .example URL is illustrative and no actual interview statement is attributed.

F077. Dataset

Working form: [Creator], [Dataset title] ([version/snapshot]), [repository/identifier], [table/variable].

Capture: Creator; version; unit; date; variables; filters; stable identifier.

Check: State the denominator and transformations when reporting a derived result.

Common error: A dataset citation alone does not disclose filtering or missing-data choices.

Source packet: Fictional packet TRAIN-W77 supplies the Northmere Research Lab's Register Match Study dataset, snapshot TRAIN-DATA-77-v2 dated May 1, 2025. Its tasks table has 120 rows. Twenty rows lack the outcome field, and eight additional rows are duplicate task identifiers; these excluded groups do not overlap. The remaining 92 unique completed tasks include 69 marked matched. The assignment asks for the match rate among unique completed tasks. A dashboard elsewhere reports 69 of 120 without explaining its denominator. The packet defines each variable and supplies the exclusion log and row identifiers.

Completed construction: Northmere Research Lab, Register Match Study (snapshot TRAIN-DATA-77-v2, May 1, 2025), tasks table, fields task_id and matched, https://training.example/data/TRAIN-DATA-77-v2.

Why this construction works: The citation identifies the dataset and snapshot; the prose must also disclose the calculation. Under the supplied exclusions, 120 minus 20 minus 8 leaves 92 tasks, and 69 divided by 92 equals 75%. State that this is a derived rate among unique completed tasks, not a rate among all rows or a result directly reported by the source. Preserve the exclusion criteria, missing-data treatment, and transformation log so another researcher can reproduce the denominator. Dataset identity alone does not explain analytic choices, and the broad dashboard figure answers a different question.

Variation: If missing outcomes are treated as nonmatches, explicitly describe that alternative and recalculate the denominator rather than silently changing the percentage. If duplicates overlap missing rows, the simple subtraction used here would no longer be justified without a row-level reconciliation. If a newer snapshot adds tasks, cite it separately and avoid comparing rates until the inclusion rules and unit of analysis are aligned.

Example scope: Lab, dataset, identifiers, variables, and records are fictional. The arithmetic follows supplied training counts; it is not an empirical finding about actual courts, agencies, or citation systems.

F078. Spreadsheet analysis

Working form: [Analyst], [Workbook title] [sheet/cell or table] ([version/date]) (derived from [input]).

Capture: Workbook; inputs; formulas; settings; output; version.

Check: Reproduce the result from preserved inputs and distinguish calculated from source-reported values.

Common error: A pasted value can survive after the supporting formula or input changes.

Source packet: Fictional packet TRAIN-W78 contains analyst Tessa Vale's workbook Register Review Rates, version TRAIN-XLS-78-v3 dated June 2, 2025. Inputs!B2:B5 holds accepted counts 8, 12, 5, and 15; Inputs!C2:C5 holds eligible counts 10, 15, 10, and 15. Summary!B7 divides the total accepted count by the total eligible count. A separate pasted cell shows 77.5%, the unweighted mean of the four row percentages. The assignment asks for the overall acceptance rate across eligible records. The workbook preserves the source-count table and the formula used in B7.

Completed construction: Tessa Vale, Register Review Rates, Summary!B7 (workbook TRAIN-XLS-78-v3, June 2, 2025) (derived from Inputs!B2:C5, TRAIN-W78).

Why this construction works: The workbook, version, sheet, and cell identify the output, while the input range identifies the calculation's basis. The accepted counts total 40 and eligible counts total 50, producing an overall rate of 80%. The 77.5% figure weights each row equally and answers a different question. Explain that distinction in the prose rather than assuming that all displayed percentages are interchangeable. Preserve formulas and calculation settings as well as visible values; a pasted result can remain after inputs change. The citation should make clear that the rate is the analyst's calculation, not a value directly stated in the source-count table.

Variation: If the question asks for the average office rate with equal weight per office, the unweighted calculation may be the intended measure, but it must be labeled accordingly. If one row is excluded, document the reason and update both numerator and denominator. When exporting the workbook to a static PDF, retain the editable file and formula audit so the cited cell's result remains reproducible.

Example scope: Analyst, workbook, counts, and cells are fictional. The arithmetic is a supplied training calculation and does not report actual institutional performance.

F079. Software release

Working form: [Creator], [Software name] ([version/commit], [date]), [repository/release URL].

Capture: Version; author; repository; module; settings when relevant.

Check: Identify the actual release used and preserve configuration for a reproducible analysis.

Common error: Citing software does not prove that it was configured correctly.

Source packet: Fictional packet TRAIN-W79 documents the invented software RegisterCompare, created by the Northmere Research Lab, release 2.4.1 dated July 7, 2025, build identifier TRAIN-SW-079. The analysis uses its match module with case folding enabled and punctuation normalization disabled. Release 2.5 changes the default punctuation setting, and the repository's main page now describes that newer release. The assignment asks the analyst to identify the software actually used to generate a preserved comparison table. The packet includes the release manifest, configuration file, input snapshot, and run log for the earlier release.

Completed construction: Northmere Research Lab, RegisterCompare (v. 2.4.1, build TRAIN-SW-079, July 7, 2025), https://training.example/software/registercompare/2.4.1.

Why this construction works: The creator, product, version, build, and release address distinguish the used software from the moving main branch or a newer release. State the material settings beside the analysis or in its methods record, because the citation alone does not disclose configuration. Preserve the input snapshot and run log so another reviewer can reproduce the table. A successful program execution is not proof that the chosen normalization matches the research question. Inspect representative outputs and failures, especially where a setting may merge distinct names or split equivalent references. Software identity and analytic validity are separate checks.

Variation: If rerunning under version 2.5, record the actual settings instead of assuming that unchanged command text produces identical behavior. If a local patch changes the module, identify the patched build and preserve the patch rather than citing the unmodified public release alone. If the program only formats a human-verified citation, describe that limited role instead of implying automated verification of every underlying legal claim.

Example scope: Software, lab, versions, settings, build identifier, and run artifacts are fictional. The .example URL is illustrative; no actual repository, commit, or capability is asserted.

F080. AI output as object of study

Working form: [System/model as identified], response to [prompt description] ([date]), [preserved record].

Capture: Prompt; output; available version; settings; date; preserved artifact.

Check: Use this form when the output itself is evidence or the research object, and verify underlying legal claims separately.

Common error: Generated text is not an independent legal authority merely because it contains citations.

Source packet: Fictional packet TRAIN-W80 preserves a research session with the invented system TRAIN-LanguageModel, whose interface displays model label TRAIN-LM-3 but no finer build number. On August 5, 2025, the researcher asks it to summarize a supplied fictional agency letter. The response overstates the letter as binding every tribunal, although the supplied letter limits itself to a specific arrangement. The packet retains the exact prompt, supplied text, output, visible model label, timestamp, and settings available to the researcher. The assignment studies the system's overstatement rather than using its response as legal authority. The letter identifier is TRAIN-OL-80, and the cited output passage is paragraph 3.

Completed construction: TRAIN-LanguageModel (displayed label TRAIN-LM-3), response to prompt requesting a summary of letter TRAIN-OL-80 (Aug. 5, 2025), preserved session TRAIN-W80, output ¶ 3.

Why this construction works: The citation identifies generated output as the object being examined. It should not imply that the output independently establishes the agency letter's effect. Compare the response with the supplied letter and attribute the overstatement to the system's answer. Record only the model information actually visible; inventing an exact backend build would create false precision. Preserve prompt context because different supplied material or instructions could produce a different answer. If the output contains source citations, inspect those sources separately before relying on their legal propositions, and distinguish an output's citation string from a verified supporting authority.

Variation: If a later run gives a different answer, preserve both sessions and identify the changed prompt, settings, or available version information. Do not overwrite the earlier output used in the study. If AI merely assisted drafting and its output is not the research object, document that assistance according to the relevant disclosure requirements rather than citing generated text as though it were primary law.

Example scope: System, model label, session, letter, and generated response are fictional. The example reports no actual model behavior and makes no legal-authority claim for AI output.

F081. Archived web capture

Working form: [Original page identity], archived [capture date], [archive URL] (original [URL]).

Capture: Original identity; capture date; original and archive URLs; captured content.

Check: Open the archive and confirm that the relevant text or attachment was actually saved.

Common error: An archived navigation shell may omit the source document.

Source packet: Fictional packet TRAIN-W81 contains an archived capture of the Northmere Archive Office's page Register Access Hours, captured June 1, 2025, at 09:30 UTC. The original URL now displays different hours. The capture preserves the page text and its date, but a linked PDF schedule was not saved; following that link reaches an error page. The assignment asks what hours appeared in the captured page text. A draft also claims that the capture proves the PDF's holiday schedule, although the packet contains no copy of that attachment. The archive uses a distinct capture-specific address.

Completed construction: Northmere Archive Office, Register Access Hours, archived June 1, 2025, 09:30 UTC, https://archive.training.example/capture/TRAIN-W81 (original https://training.example/access-hours).

Why this construction works: Identify both the original item and the particular archived capture. The capture date is not automatically the page's publication date or the date the announced hours took effect. Inspect the saved content and distinguish it from missing attachments, current redirects, or a navigation shell. Here the preserved text can support a limited statement about what the page displayed, but it cannot establish the absent PDF's holiday schedule. The source card should record the capture's completeness and the exact passage relied on so a working link does not create a false impression that every component of the original page survived.

Variation: If another capture saves the PDF, open that attachment and cite its own title, version, and archived location where useful. If only the site's navigation was captured, do not describe the substantive page as preserved. If comparing changed hours across captures, identify each timestamp and separate the observed textual change from any inference about when the agency actually changed its operations.

Example scope: Office, page, captures, archive behavior, hours, and missing PDF are fictional. Both .example addresses are illustrative and no real archival capture is claimed.

International and Tribal

F082. Treaty text

Working form: [Treaty title], [date], [official series/identifier], art. [article/paragraph].

Capture: Instrument; authentic text; parties; series; article; amendments.

Check: Research participation and temporal status separately from the treaty's wording.

Common error: A text citation alone does not establish that a state was bound at the relevant time.

Source packet: Fictional packet TRAIN-I82 supplies the Convention on Shared Register Descriptions between the invented states Asterfall and Brindle Reach, signed September 12, 2024. The authenticated training text is published in TRAIN Treaty Series volume 3, instrument 18. Article 7(2) describes the exchange format. The packet identifies the text as authentic but supplies no complete record of ratification, reservations, amendments, or entry into force for either state. The assignment asks what article 7(2) says as a textual provision, while a draft incorrectly assumes that signature alone proves both states were bound at a later event date.

Completed construction: Convention on Shared Register Descriptions, Sept. 12, 2024, 3 TRAIN Treaty Series No. 18, art. 7(2).

Why this construction works: The title, date, publication identifier, and article locate the instrument's text. They do not answer every participation or temporal-status question. Limit the sentence to the provision's wording unless the research also establishes the relevant state's status and any qualification affecting the provision. Preserve the authentic-text designation and any language versions identified by the instrument rather than assuming an unofficial translation is equivalent. The source card should separate textual identity from treaty status, including the date relevant to the claim. The missing status information is a research gap, not a formatting defect that an additional parenthetical can cure.

Variation: If the assignment asks whether Asterfall was bound on a specified date, inspect the appropriate depositary or official status records and the instrument's entry-into-force terms. If an amendment changes article 7(2), identify which text is being cited and whether the amendment applies to the relevant state. A current consolidated text should not silently replace the original when discussing historical obligations.

Example scope: States, convention, treaty series, authentication, dates, and article are fictional. No actual country's treaty practice, participation, or international obligation is asserted.

F083. Treaty status record

Working form: [Depositary], [Treaty status record] ([as-of date]), [specific entry/URL].

Capture: Treaty; state; event; date; reservation/declaration; source.

Check: Identify the particular state's status and the date relevant to the claim.

Common error: A present status page may not by itself explain a historical status change.

Source packet: Fictional packet TRAIN-I83 provides a status table maintained by the invented Shared Registers Depositary for the fictional Convention on Shared Register Descriptions. The preserved table is current through June 30, 2025. Asterfall's row separately records signature on September 12, 2024, deposit of ratification on April 6, 2025, and entry into force for that state on May 6, 2025. A linked declaration has its own document identifier TRAIN-DEC-A1. The assignment asks what event occurred on April 6. The exercise supplies no basis for treating every date in the row as the same legal event.

Completed construction: Shared Registers Depositary, Convention on Shared Register Descriptions: Status Table (as of June 30, 2025), Asterfall entry, event ratification deposited Apr. 6, 2025, TRAIN-I83.

Why this construction works: Identify the preserved status record, its as-of date, the state, and the particular event being reported. Describe April 6 as the deposit event shown in the table, not as signature or entry into force. The table's June 30 coverage is another distinct date. If the proposition concerns the effect of Asterfall's declaration, open and inspect the linked declaration rather than assuming the table's short label captures its contents. Keep status events and textual qualifications as connected but separate source records. A current summary can help locate history, but a historical claim may require the underlying notification or event document.

Variation: For a statement about May 1, investigate the instrument's terms and the recorded May 6 entry-into-force date rather than merely noting that ratification had been deposited. If a later status table changes an entry, preserve the earlier capture and inspect the correction or subsequent event. If the table omits a state, do not infer its complete treaty position without checking the scope and completeness of the record.

Example scope: Depositary, states, convention, status events, declaration, and dates are fictional. The example neither calculates nor asserts any actual international-law consequence.

F084. International judgment

Working form: [Proceeding], [tribunal/document identifier], ¶ [paragraph] ([date]).

Capture: Tribunal; proceeding; judgment/order type; identifier; paragraph.

Check: Use the judgment itself and attribute separate writings distinctly.

Common error: A press release is not the judgment it summarizes.

Source packet: Fictional packet TRAIN-I84 contains the International Register Tribunal's judgment in Asterfall v. Brindle Reach, proceeding TRAIN-IRT-12, issued July 14, 2025. Paragraph 86 appears in the tribunal's main judgment. A separate opinion by Member Rowan has its own paragraph 86, and a press release summarizes the result in broader language. The assignment asks for the main judgment's discussion of a defined exchange procedure. The packet includes the judgment cover, document identifier TRAIN-IRT/J/12, and separate-writing labels, but no later proceedings or enforcement record.

Completed construction: Asterfall v. Brindle Reach, International Register Tribunal, Judgment TRAIN-IRT/J/12, ¶ 86 (July 14, 2025).

Why this construction works: The tribunal, judgment identifier, date, and paragraph distinguish the cited document from the separate opinion and press release. Read the actual paragraph and relevant qualifications in the judgment before adopting a summary. The same paragraph number can occur in different writings within a proceeding, so the document type is part of the locator's meaning. The source card should identify the writing, authoring body, language version, and any correction notice encountered. A citation to the judgment establishes where the passage appears; questions about the judgment's legal effect, finality, or implementation require additional research appropriate to the tribunal and issue.

Variation: If relying on Member Rowan's separate reasoning, name that writing and author and use its own identifier or clear parenthetical. If the press release supplies an explanation absent from the judgment, attribute it to the release rather than inserting it into the tribunal's reasoning. If a corrected judgment replaces paragraph 86, compare the text and update the quotation and locator together.

Example scope: Tribunal, parties, judgment, identifiers, separate opinion, and procedure are fictional. No actual international institution, decision, or jurisdictional practice is represented.

F085. International resolution

Working form: [Organization/body] Res. [number], [document symbol], ¶ [paragraph] ([date]).

Capture: Adopting body; resolution; document symbol; date; paragraph.

Check: Confirm the body and document type before analyzing legal effect.

Common error: A similarly numbered draft or meeting record is a different document.

Source packet: Fictional packet TRAIN-I85 supplies Resolution 15 adopted by the Assembly of the invented Register Cooperation Organization on August 22, 2025. The adopted document symbol is TRAIN-RCO/RES/15, and operative paragraph 6 concerns a technical study. A draft circulated as TRAIN-RCO/DRAFT/15 contains broader language in paragraph 6. A meeting record with symbol TRAIN-RCO/MTG/15 describes debate but is a different document. The assignment asks what the adopted assembly resolution requests. The packet does not supply a charter analysis or other basis for a broad conclusion about the resolution's legal effect.

Completed construction: Register Cooperation Organization Assembly Res. 15, TRAIN-RCO/RES/15, operative ¶ 6 (Aug. 22, 2025).

Why this construction works: The organization, adopting body, resolution number, document symbol, date, and paragraph identify the adopted instrument. Preserve the distinction between the assembly and any secretariat or subsidiary body that circulated the draft. Describe the requested technical study in the words and scope of the adopted paragraph, not the broader draft. A meeting record can explain what participants said, but it does not replace the resolution for its final wording. The source card should retain the adoption record and version relationship while treating the legal effect of the instrument as a separate analytical question.

Variation: For a discussion of negotiations, cite the draft and meeting record separately with their actual symbols and speaker or paragraph locators. If a later resolution amends the request, identify the later adopting body and exact operative text. Do not assume that a document called resolution has the same effect as a similarly named instrument from another organization or a different body within the same organization.

Example scope: Organization, assembly, resolution, symbols, draft, and study are fictional. The example states no practice or legal effect of the United Nations or any actual international body.

F086. Foreign judgment

Working form: [Original case title], [jurisdiction's assigned citation], [locator] ([court/date]).

Capture: Original identifier; court; language; date; opinion version.

Check: Preserve the issuing system's identifier and explain translations when needed.

Common error: A familiar US-style label can misidentify the foreign institution.

Source packet: Fictional packet TRAIN-I86 presents a judgment from the invented jurisdiction Alder Republic. Its issuing institution calls itself the Records Review Chamber, and the original case title is Mera Archive v. Leto Board. The chamber assigns identifier TRAIN-AR-RRC-2025-31 and numbered paragraphs. Paragraph 44 contains the assigned discussion. A commercial English-language digest calls the institution a supreme court, but the source packet supplies no basis for that translation of its role. The court-issued text is in English in this fictional exercise. The assignment asks for an accurate source identity, not a comparative hierarchy conclusion. The decision is dated September 9, 2025.

Completed construction: Mera Archive v. Leto Board, TRAIN-AR-RRC-2025-31, ¶ 44 (Alder Republic Records Review Chamber Sept. 9, 2025).

Why this construction works: Preserve the institution's actual designation and its assigned identifier. Do not replace Records Review Chamber with a familiar domestic court label merely to make the citation look conventional. The original title and paragraph numbering provide a retrieval path that remains useful across databases. Record the language and version inspected, and distinguish the court's text from a digest or unofficial translation. If the analysis depends on the tribunal's place in the legal system, research that institutional question separately. Accurate citation identity is a prerequisite to comparing authority, but it does not itself establish hierarchy, precedential force, or citation permission.

Variation: If a translated title is useful to the reader, add it transparently without discarding the original identity. If another rendition uses page numbers instead of assigned paragraphs, inspect the original numbering before choosing the locator. If the document is an interlocutory order rather than a judgment, use its actual designation and research its status rather than importing assumptions from the receiving jurisdiction's terminology.

Example scope: Republic, chamber, case, identifier, language setting, and digest are fictional. No actual foreign country's institutions, citation conventions, or law are described.

F087. Foreign legislation

Working form: [Jurisdiction], [Instrument title/number], [division] ([version/date]).

Capture: Jurisdiction; enactment; official publication; language; version.

Check: Read the official version and identify any translation used.

Common error: An unofficial translation may omit amendments or reflect a different version.

Source packet: Fictional packet TRAIN-I87 contains Alder Republic's Public Register Instrument, numbered TRAIN-AR-2024-8, in an official consolidated edition dated October 1, 2025. Article 12(3) contains the assigned provision. The source's version note lists a June 2025 amendment. An unofficial English translation dated December 2024 predates that amendment and uses a different subdivision arrangement. The assignment asks for a citation identifying the amended official text, while an accompanying working translation is used only to assist reading. The packet identifies the issuing body and original-language title but does not claim the unofficial translation is authoritative.

Completed construction: Alder Republic, Public Register Instrument No. TRAIN-AR-2024-8, art. 12(3) (official consolidated text Oct. 1, 2025) [TRAIN-I87].

Why this construction works: The jurisdiction, instrument number, subdivision, and version identify the official text rather than the older translation. Preserve the original title in the source record and explain any translated title used for readers. Compare the amendment and consolidation notes before assuming that two language versions contain the same law. The citation's year within the instrument number identifies the original enactment; the consolidation date identifies the version consulted. Those functions should remain distinct. If the legal analysis turns on a contested term, obtain appropriate language assistance and document the translation used instead of treating a convenient online rendering as the official text.

Variation: For a historical event before the amendment, retrieve the relevant earlier official version and examine temporal terms. If quoting the December translation as an object of comparison, identify its translator, date, and unofficial status. Do not cite the 2025 official consolidation while silently quoting wording available only in the older translation. A version mismatch can persist even when the section heading appears unchanged.

Example scope: Jurisdiction, instrument, article, language versions, and amendment are fictional. No actual foreign enactment, translation rule, or legal practice is asserted.

F088. Translated legal source

Working form: [Original source citation] ([translator/translation source], [version/date]).

Capture: Original; translation; translator; version; disputed terms.

Check: Keep both texts and identify material translation choices or limitations.

Common error: Machine translation should not silently be presented as an official text.

Source packet: Fictional packet TRAIN-I88 supplies an original-language decision of Alder Republic's Records Review Chamber, identifier TRAIN-AR-RRC-2025-38, dated October 2, 2025. Translator Mira Vale prepares an identified English translation dated October 5. Paragraph 19 contains a term that Vale renders as permitted, while an automated translation renders it as required. Vale's note explains that the choice affects the sentence's apparent force and flags the phrase for specialist review. The assignment asks for a transparent citation to the translation used, preserving the original document and the uncertainty rather than choosing the more helpful English wording silently. The decision caption is Nera Register v. Olin Office.

Completed construction: Nera Register v. Olin Office, TRAIN-AR-RRC-2025-38, ¶ 19 (Alder Republic Records Review Chamber Oct. 2, 2025) (Mira Vale English trans., Oct. 5, 2025) [TRAIN-I88].

Why this construction works: The original citation identifies the legal source; the translation parenthetical identifies the text through which the reader encounters it. Keep both files and Vale's translation note in the source record. If the disputed term matters to the argument, state the limitation and obtain the appropriate review rather than presenting one rendition as an unquestioned official quotation. An automated translation is a separate rendering, not evidence that the original tribunal used the English word required. Preserve original paragraph numbering where it exists so another reviewer can compare the corresponding passage without relying on the translated document's page layout.

Variation: If an official translation later becomes available, inspect the disputed passage and identify that version accurately; official status does not excuse failing to compare the text used. If the translation omits footnotes or separate opinions, disclose those omissions when material. If quoting only the translation, avoid suggesting that the English wording appears verbatim in the original-language decision.

Example scope: Decision, jurisdiction, translator, versions, and disputed rendering are fictional. No actual foreign-language term or translation of a real legal source is supplied.

F089. Tribal code or enactment

Working form: [Nation], [Code/enactment title] § [section] ([version/date]).

Capture: Nation's name; institution; source type; section; version; access status.

Check: Verify the source through the relevant nation or authorized collection and respect access limits.

Common error: A federal directory entry does not establish the nation's current law.

Source packet: Fictional packet TRAIN-I89 uses the deliberately fictional name TRAIN Nation A and does not model a particular real Tribal nation. The packet supplies a public excerpt of its Records Code, section 4-12(b), issued by the nation's identified legislative office and marked revision September 2025. A cover note states that the excerpt is authorized for public distribution and that a separate appendix is restricted and not included. A federal directory entry elsewhere merely lists the nation's contact information. The assignment concerns the public excerpt and does not require the restricted appendix or an inference about its contents.

Completed construction: TRAIN Nation A, Records Code § 4-12(b) (public excerpt, rev. Sept. 2025), authorized source packet TRAIN-I89.

Why this construction works: Use the nation's own name, source title, subdivision, and version, and record the identified issuing institution. The public excerpt's provenance is the relevant source path; a federal directory listing cannot establish the text of the nation's law. Respect the stated access boundary by limiting the discussion to the supplied public material and marking the absent appendix as unavailable. Do not fill that gap from assumptions about another nation's law or a nearby state's code. The source card should retain the distribution note and describe exactly which portion was inspected, so the citation does not imply access to or verification of the complete code.

Variation: If the question requires a restricted provision, use the nation's appropriate authorized process rather than treating public metadata as permission to obtain or reproduce it. If an authorized collection supplies an older version, verify its relationship to the nation's current source before making a present-tense claim. An enacted amendment and a code compilation should be traced separately when the compilation's coverage is uncertain.

Example scope: TRAIN Nation A, office, code, distribution terms, and directory are wholly fictional. No real Tribal nation's law, access policy, governance structure, or cultural practice is represented.

F090. Tribal court decision

Working form: [Proceeding], [court-assigned identifier], [locator] ([nation/court/date]).

Capture: Nation; court; proceeding; identifier; publication/access status.

Check: Use the court's actual designation and determine the receiving forum's requirements.

Common error: A Tribal court is not a state court because it is geographically within a state.

Source packet: Fictional packet TRAIN-I90 concerns the deliberately fictional TRAIN Nation A Court of Appeals. Its decision in Rowan Office v. Vale Records bears assigned identifier TRAIN-NA-CA-2025-6 and is dated June 17, 2025. Paragraph 23 contains the assigned discussion. The court has authorized this decision's public distribution, while a linked filing is marked restricted and is absent from the packet. A geographic database groups the decision under a neighboring fictional state's name, but the issuing court identifies itself as the nation's court. The assignment asks for a citation to the public decision only.

Completed construction: Rowan Office v. Vale Records, TRAIN-NA-CA-2025-6, ¶ 23 (TRAIN Nation A Court of Appeals June 17, 2025).

Why this construction works: The nation's name and court designation identify the actual issuing institution in the exercise. The geographic database category does not transform that institution into a state court. Preserve the assigned identifier and paragraph numbering, and retain the public-distribution statement with the source card. The restricted filing should not be described as inspected or reconstructed from the opinion's references. If the decision will be used in another forum, research that forum's receiving requirements and the decision's relevant status separately. The presence of a public copy supplies access to that copy, not an automatic conclusion about precedential force or permitted uses elsewhere.

Variation: If relying on a separate writing, identify its author and actual locator rather than attributing it to the court's main decision. If a collection reproduces an older or corrected version, compare it with an authorized source and describe the version used. If the court uses a different institutional title in another matter, preserve that title rather than standardizing every Tribal tribunal to a familiar state-court label.

Example scope: Nation, court, case, identifier, access terms, and database grouping are fictional. No actual Tribal decision, institution, citation rule, or legal effect is asserted.

Archives and records

F091. Archival item

Working form: [Creator], [Item description] ([date]), [collection/series/item], [repository].

Capture: Creator; date; item; collection; container; repository; reproduction.

Check: Distinguish facts visible on the item from catalog-supplied or inferred information.

Common error: A repository homepage cannot locate an individual archival record.

Source packet: Fictional packet TRAIN-H91 contains a scanned memorandum headed Register Room Arrangement, signed by Lena Rowan but bearing no visible date. The Northmere Historical Repository catalog assigns an estimated date of circa 1932 and locates it in the Harbor Office Papers, series 4, box 7, folder 2, item TRAIN-H91-6. The reverse side has a handwritten note by an unidentified person. The assignment asks for Rowan's memorandum text, which appears on the first side. A draft treats the catalog's estimated year as a date written on the original and attributes the reverse-side note to Rowan.

Completed construction: Lena Rowan, Register Room Arrangement memorandum (undated; catalog dates circa 1932), Harbor Office Papers, ser. 4, box 7, folder 2, item TRAIN-H91-6, Northmere Historical Repository.

Why this construction works: The creator, description, collection hierarchy, item identifier, and repository give a path to the individual record. Label the estimated date as catalog-supplied rather than silently converting it into an original date. The source card should distinguish visible document facts, catalog metadata, and researcher inference. Do not attribute the reverse-side handwriting to Rowan without supporting evidence. If the argument turns on physical features, record which scan or reproduction was inspected and any missing sides or edges. A repository home page may establish where a collection is held, but it is too broad to locate this memorandum without the item information.

Variation: If another catalog revision changes the estimated date, preserve the metadata version used and investigate the reason before altering a historical claim. If the original is inspected in person, record that access separately from the digital reproduction. If quoting the reverse-side note, identify it as an unattributed annotation and give its side or image locator rather than incorporating it into the memorandum's authored text.

Example scope: Creator, memorandum, repository, collection, identifiers, handwriting, and dates are fictional. No actual archival provenance or historical attribution is asserted.

F092. Public-records production

Working form: [Agency], [Document title] at [locator], production [identifier] ([date]).

Capture: Agency; request/production; item; date; redactions; attachments.

Check: Note missing attachments and identify the particular produced document.

Common error: Agency custody does not guarantee that every statement in the document is true.

Source packet: Fictional packet TRAIN-H92 contains a production from the Northmere Archive Office responding to request TRAIN-PR-25-18. The office produced an Inspection Summary dated March 6, 2025, on July 21, 2025. The relevant text appears at Bates page TRAIN-PR18-00017 and reports a contractor's statement about missing labels. The summary references Attachment B, which is not included; the production letter notes one withheld attachment but does not supply its contents. The assignment asks what the produced summary reports. A draft presents the contractor's assertion as an agency-verified fact and assumes the missing attachment confirms it.

Completed construction: Northmere Archive Office, Inspection Summary at TRAIN-PR18-00017 (document dated Mar. 6, 2025), production TRAIN-PR-25-18 (July 21, 2025).

Why this construction works: The document date and production date identify different events, and the specific page locates the item within the larger release. Attribute the missing-label statement to the contractor as reported in the summary unless another source establishes more. Agency custody does not make every embedded assertion an agency finding. Record the missing attachment and the production letter's actual explanation without inventing its contents. The source card should preserve request identifier, production identifier, document identity, redactions, and attachments inspected, allowing a reviewer to see both the available evidence and its boundaries.

Variation: If a supplemental production later supplies Attachment B, inspect it before revising the claim and cite its own locator. If the attachment contradicts the summary, describe the conflict rather than treating later production as automatic confirmation. If a redaction obscures the speaker's identity, state that limitation and avoid filling the gap from an unrelated document with a similar title.

Example scope: Agency, request, production, document, contractor, and withheld attachment are fictional. The example establishes no actual public-records response, truth determination, or disclosure entitlement.

F093. Historical compilation

Working form: [Compiler/author], [Compilation title] [volume/page] ([edition/year]).

Capture: Original document; compilation; editor; publication; locator.

Check: Distinguish the reproduced original from editorial notes and modernized text.

Common error: A transcription can contain editorial changes absent from the original.

Source packet: Fictional packet TRAIN-H93 supplies volume 2 of Harbor Office Documents, compiled and edited by Mara Vale in a 1984 edition. At page 216 the compilation reproduces a 1911 register notice, while page 217 contains Vale's explanatory note. The editor's introduction says spelling has been modernized and illegible words placed in brackets. A facsimile of the original notice is available in the packet and shows one punctuation difference relevant to the assignment. The writer wants to describe the original notice's instruction, distinguishing it from the editor's later explanation and transcription choices.

Completed construction: Mara Vale ed., Harbor Office Documents vol. 2, at 216 (1984) (transcribing a 1911 register notice) [TRAIN-H93].

Why this construction works: The compiler, volume, page, and edition identify the consulted compilation, while the parenthetical identifies the older document reproduced there. The 1984 publication date does not become the notice's date. Read the editorial conventions before presenting the transcription as an exact reproduction. Where punctuation or a bracketed restoration matters, compare the facsimile and explain the difference instead of silently choosing the version that supports the argument. The source card should keep original-document identity, compilation location, editor's note, and transcription changes distinct. A sentence about Vale's historical interpretation belongs with page 217, not the notice citation at 216.

Variation: If quoting the original facsimile directly, cite its archival identity and locator, adding the compilation as a finding aid if useful. If the original is unavailable, state that the quotation follows the edited transcription and preserve material editorial brackets. If another edition revises the transcription, identify the edition used and compare the changed passage before carrying forward an older quotation.

Example scope: Compiler, collection, edition, notice, facsimile, and editorial changes are fictional. No actual historical document, quotation, or scholarly interpretation is reproduced.

F094. Map or plan

Working form: [Creator], [Map/plan title], [sheet/revision] ([date]), [repository/identifier].

Capture: Creator; scale; sheet; revision; date; legend; source.

Check: Check the legend and revision and identify whether the map shows proposed or existing conditions.

Common error: A proposed site plan does not establish what was actually constructed.

Source packet: Fictional packet TRAIN-H94 provides Finch Design Office's Harbor Archive Access Plan, project TRAIN-PLAN-94, sheet C-3, revision B dated May 14, 2025. The legend distinguishes existing paths with solid lines and proposed paths with dashed lines. The disputed entrance route is dashed. A reduced photocopy makes the line patterns difficult to distinguish and omits the revision block. A later construction photograph shows part of the site but not the entire route. The assignment asks what the plan proposes, not what was ultimately built. The original-resolution sheet and legend are supplied for inspection.

Completed construction: Finch Design Office, Harbor Archive Access Plan, sheet C-3, rev. B (May 14, 2025), project TRAIN-PLAN-94 [TRAIN-H94].

Why this construction works: The creator, plan title, project identifier, sheet, revision, and date distinguish the drawing from earlier designs or neighboring sheets. Read the legend before describing a feature: the dashed route is proposed in this packet, so the plan does not by itself prove construction. Preserve the full-resolution sheet, scale statement, legend, and revision block. A reduced copy can alter apparent measurements and hide source-status information. If a dimension matters, use the drawing's stated dimensions or a validated measurement method appropriate to the task rather than measuring an arbitrarily resized screenshot and treating the result as a surveyed distance.

Variation: If an as-built drawing later records the completed route, inspect its own status, date, and qualifications and cite that version for the completed condition. If the claim concerns actual conditions on a particular day, use appropriate evidence of those conditions in addition to the design record. A photograph showing one segment cannot establish every feature drawn on a multi-sheet plan without a supported connection.

Example scope: Design office, project, drawing, site, revision, legend, and photograph are fictional. The example does not establish actual construction, surveyed dimensions, or professional design compliance.