On this page
A program name does not identify the claim
The U.S. Copyright Office’s Circular 61 explains that copyright covers copyrightable expression in code, rather than the program’s functional ideas or logic. New-version registration principally concerns the new authorship, with stated limits on earlier and third-party material.
Identify the release, source archive, author/claimant and material being claimed before deciding what to deposit. An old release screenshot cannot establish which code belongs in the new application.
The trade-secret question changes the preparation
Circular 61 offers specific deposit routes for code containing trade secrets. One uses the first and last ten pages without redaction. Another uses the first and last 25 pages with secret portions blocked out under the stated limits, including less than half blocked and appreciable copyrightable expression left visible. These are selected alternatives, not permission to black out anything management prefers.
Have the actual notice page, short-program or derivative-version conditions and other applicable options checked. Do not choose a route from page count alone or assume a deposit preserves secrecy of everything submitted.
The correct page count can still come from the wrong release
Fictional example: the U.S. product uses version 4.2, but management’s proposed deposit was exported from 4.0. The package has the expected number of pages. That does not cure the version mismatch.
| Before submission | Evidence to verify |
|---|---|
| Release identity | Exact version and controlled source archive. |
| Claimed material | New code, earlier code and third-party components distinguished. |
| Secrets and option | Actual secret sections and the conforming deposit route. |
| Completeness | Required pages/notices and the authorised filing review. |
Budget the preparation without exposing the code here
Assign the engineering export, rights assessment and registration review as separate jobs. Keep code, secret markings and application material in the company’s approved systems. ELN’s worksheet only needs the dependency and responsible person.
If the required source is unavailable, the circular describes written special-relief requests under conditions. That is a question for actual filing preparation, not a reason to substitute an unrelated version or promise acceptance.
Scope
- Selected Circular 61 teaching examples only, not a complete deposit instruction, confidentiality assurance, accepted registration or ruling on code ownership/copyrightability.
Next step
Use Launch dependencies to assign the version, ownership, secret-material and filing checks before submission. Keep all code and deposit files outside the ELN worksheet.
Sources & review notes
U.S. Copyright Office
Passage, dates and research notes
official-guidance · Printed pages1–4 and6: version scope, source deposits, trade secrets and special relief
March 2021 revision; full circular read. Selected deposit options are teaching examples, not a completed application or blanket secrecy assurance.
Detailed rule records (1)
The deposit must identify the version being registered. Circular 61 distinguishes ordinary source deposits from specified trade-secret options, including first/last ten pages unredacted and a conditional first/last 25-page redaction route.
Circular 61: Copyright Registration of Computer ProgramsBookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.