Skip to main content

Clean Copy / Pasting Guide

This guide explains how to copy LMR site content from ChatGPT into project files without accidentally copying instruction labels, broken formatting, or partial update fragments.

It is a practical workflow page. It does not define LMR theory.

Core Rule​

Only paste the actual file content.

Do not paste labels, explanations, or ChatGPT instructions unless they are clearly part of the file.

What to Paste​

When a response says:

FULL FILE:

content/example.md

Copy the content inside the block that follows.

The file content usually begins with a Markdown heading such as:

# Page Title

or:

Section Title​

If the file is a full page, it should usually begin with a single # heading.

What Not to Paste​

Do not paste labels such as:

  • FULL FILE
  • FULL FILE REPLACEMENT
  • FULL FILE UPDATE
  • START FILE CONTENT
  • END FILE CONTENT
  • Copy everything inside the block
  • Replace this section with
  • Add this line
  • Next, we should

Those are instructions, not file content.

Markdown Headings​

Markdown headings use number signs.

Use them exactly as shown.

# means page title

## means main section

### means subsection

#### means smaller subsection

Do not remove the number signs.

They are part of the Markdown file.

Full File Replacement​

If the instruction says:

FULL FILE REPLACEMENT

then replace the entire existing file with the new content.

Do not keep old sections unless they are also included in the replacement file.

New File​

If the instruction says:

FULL FILE

and gives a file path that does not exist yet, create that file and paste the content into it.

Example:

content/reference/clean-copy-pasting-guide.md

Section Update​

If the instruction says:

replace only this section

then do not replace the whole file.

Find the named section and replace only that section.

Because section updates are easier to miss, full file replacements are preferred for this project whenever possible.

Code Fences​

Triple backticks are usually ChatGPT formatting.

Do not paste triple backticks into Markdown files unless the file intentionally needs to display a code block.

For this project, most file content should be pasted without triple backticks.

Inline Code​

Single backticks are usually part of the file.

Examples:

content/site-map.md

public/pdfs/

M′ = 1/λ

Single backticks may remain when they are used to mark file paths, symbols, or inline examples.

Tables​

Markdown tables should be pasted exactly as shown.

Example:

DocumentStatus
Paper IPublished Paper

Do not remove the vertical bars.

Markdown links should be pasted exactly as shown.

Example:

Release Registry

The text inside brackets is the visible link text.

The path inside parentheses is the target.

Public PDF File Names​

Public PDF assets should use lowercase names with underscores.

Example:

lmr_paper_i_codex_v1.0.pdf

Use underscores for public PDF assets.

Do not use spaces in public PDF filenames.

Markdown Page File Names​

Markdown page files may use hyphens.

Example:

clean-copy-pasting-guide.md

For Markdown pages, preserve the site-map convention unless Codex later performs a full link-safe cleanup.

When Unsure​

If a response contains both instructions and content, paste only the content that belongs inside the target file.

If a file update is unclear, do not guess.

Ask for a full file replacement.

Codex Cleanup Rule​

Codex may later scan the project for accidental instruction fragments.

It should flag or remove lines such as:

  • FULL FILE
  • FULL FILE REPLACEMENT
  • START FILE CONTENT
  • END FILE CONTENT
  • Copy everything inside the block
  • Replace only this section
  • Next, we should

Codex should not rewrite LMR theory during this cleanup.