Skip to main content

AI Copyright Registration

Scenario Description​

You need to apply for software copyright (Software Copyright) for your company's software product, for high-tech enterprise certification or intellectual property protection. The traditional method requires preparing a lot of materials: source code identification materials, software description, user operation manual, interface screenshots...... Having an agency do a set costs at least two to three thousand yuan, and doing it yourself requires familiarity with the process.

DesireCore's Software Copyright Writer agent can fully automate this process: you only need to describe the software's functions in natural language, and it will automatically develop a demo application in an isolated sandbox environment, automatically take screenshots, and then generate the complete set of application materials.

Involved Agents​

  • Software Copyright Writer -- Core agent, responsible for requirement understanding, automatic development, screenshots, and material generation
  • Code Assistant -- Optional collaboration to ensure the quality and standardization of generated code

Complete Process​

Step 1: Describe Software Functions​

You: I developed a Markdown editor supporting real-time preview, PDF export,
    and cloud sync. Software name is "MoXie", version V1.0.

Software Copyright Writer: Okay, I'll generate copyright application materials for "MoXie V1.0".

         Based on your description, I've planned the following functional modules:

         1. Editor Page -- Markdown editing area + real-time preview
         2. File Management -- Document list, new/open/delete
         3. Export Function -- PDF export settings and progress
         4. Cloud Sync -- Login/registration, sync status, version history
         5. Settings -- Theme switching, shortcut configuration

         Confirm to start automatic development. Estimated time: 15-20 minutes.

Step 2: Automatic Development and Screenshots​

After confirming the function planning, the agent will automatically in the sandbox environment:

  • Generate complete frontend application code
  • Take screenshots page by page
  • Ensure screenshots contain software name identification

Step 3: Generate Complete Materials​

Software Copyright Writer: All completed!

         Copyright Materials List:
         1. source_code_identification_materials.txt (first 30 pages + last 30 pages)
         2. software_description.txt (detailed function description)
         3. user_operation_manual.txt (operation guide based on screenshots)
         4. screenshots/ (5 interface screenshots, 1920x1080)
         5. softreg_materials.zip (all packaged)

         You can directly download the ZIP package and submit to the Copyright Protection Center.

Step 4: Submission and Correction​

If the Copyright Center requires corrections, just tell the agent the correction comments, and it will modify the materials accordingly:

You: The copyright was returned, saying screenshots are unclear and description is too simple.

Software Copyright Writer: I'll help you fix it:
         1. Regenerate 1920x1080 HD screenshots
         2. Expand description from 500 words to 2000+ words
         3. Supplement functional flowchart description

         Updated, can resubmit.

Key Steps​

  1. Describe Functions -- Describe your software functions and name in natural language
  2. Confirm Planning -- The agent generates functional module planning, you confirm or adjust
  3. Auto Generate -- The agent automatically develops, takes screenshots, generates complete materials
  4. Download and Submit -- Download the packaged ZIP file and submit to the Copyright Protection Center

Final Deliverable​

A complete set of copyright application materials, including source code identification materials, software description, user operation manual, and interface screenshots, ready to be submitted to the National Copyright Protection Center.

Notes​

  • Software name suggested format "XX Software" or "XX System"
  • Version number for first application starts from V1.0
  • Screenshots must contain software name or identification
  • Source code identification materials need first 30 pages + last 30 pages totaling 60 pages
  • For enterprise batch applications, supports parallel generation of multiple materials
Best Practices
  • The more detailed the function description, the more the generated materials match reality. Including specific functional points (e.g., "supports Markdown syntax highlighting") is much better than vague descriptions (e.g., "an editor")
  • If your software has specific industry background (e.g., "smart agriculture", "education platform"), tell the agent, and it will reflect industry characteristics in screenshots and descriptions
  • Before application, you can have the Legal Advisor agent review material compliance together
  • Teach your style preferences upfront: If you have specific requirements for description style or module naming conventions (e.g., "use four-character phrases for all module names"), teach them to the Software Copyright Writer first — no need to adjust every time when batch-generating materials