跳到主要内容Skip to main content

学习路径Learning path · 第 4 阶段Stage 4

怎么做一份素材与许可台账How to build an asset and licence ledger

How to build an asset and licence ledger

这一步决定什么What this stage decides:台账的最小可用列设计,和每张素材从进项目到发布清零的走法:每个文件记来源、许可、核验日、商用与署名状态。: The smallest useful set of columns, and the path each asset takes from entering the project to being cleared: source, licence, verification date, commercial and attribution status.

本站的判断Our judgement:台账的价值在「每行都有下一步」—— 待确认不可怕,没有出处才可怕。: A ledger earns its keep when every row has a next step — unconfirmed is fine, sourceless is not.

性质:本站的判断,未经实测Nature: the site's judgement, not measured

这篇解决什么:AI 资产台账 讲了为什么要建表;这篇讲表长什么样、每一行怎么走完。适用于素材(图像、音频、字体、第三方代码库)从哪来都要记的项目。

What this guide solves: the AI asset ledger entry explains why the table exists; this one gives the columns and walks a row to its end. It fits any project where assets (images, audio, fonts, third-party code) come from somewhere.

适用条件

  • ✅ 项目里的素材来自两个以上渠道(自己做的、下载的、AI 生成的都算渠道)
  • ✅ 存在「以后要商用/发布」的可能 —— 哪怕只是 itch 页面挂个下载
  • ⚠ 不适用:一次性练习、确定永远不外发的文件(可以不进表,但目录里要能分清)
  • 什么时候开始:第一个文件进项目那天。事后补记基本补不回来(理由见 AI 资产台账)。

When this applies

  • ✅ Assets arrive from more than one channel (made by you, downloaded, AI-generated — all channels)
  • ✅ There is any chance of commercial use or release later — even just a download link on an itch page
  • Not for throwaway practice files you are certain will never leave the machine (skip the row, but keep them in a separate folder)
  • When to start: the day the first file lands. Backfilling mostly fails (reasons: AI asset ledger).

台账的列

最小可用版本,七列(表头示例):

列记什么例子(虚构)
路径文件在项目里的位置assets/bgm_loop.ogg
来源哪个站点/工具/人,附获取时的 URLFreesound 用户 X 的条目(示例)
许可类型页面标注的原文,如 CC0 / CC-BY 4.0 / 个人免费CC-BY 3.0(示例)
许可页 URL能点开看到条款的那一页条目页的 license 链接
核验日你当天看到该条款文本的日期2026-11-06(示例)
可商用是 / 否 / 待确认是
署名要求需不需要、写在哪需要,进 credits 页

第三方代码库同样进表:来源换成仓库地址,许可类型记 LICENSE 文件的标识。

The columns

The smallest useful version, seven columns (headers shown):

ColumnWhat goes in itExample (fictitious)
Pathwhere the file livesassets/bgm_loop.ogg
Sourcesite / tool / person, with the URL at retrieval timea Freesound entry by user X (example)
Licence typethe label as the page states it — CC0, CC-BY 4.0, personal-use-onlyCC-BY 3.0 (example)
Licence URLthe page you can open and read the terms onthe entry's licence link
Verified onthe date you actually saw that text2026-11-06 (example)
Commercialyes / no / unconfirmedyes
Attributionrequired or not, and where the credit goesrequired — on the credits page

Third-party code libraries go in the same table: the source becomes the repository URL, the licence type comes from its LICENSE file.

步骤

1. 建表。 一个 assets-ledger.md(或表格文件)放进仓库,用上表七列。

2. 进一文件记一行。 每次把素材放进项目目录的同一动作里,顺手记前两列 —— 来源和 URL 当时不记,一周后就找不回来了。

3. 把许可分成四类。 CC0:无需署名 —— CC0 官方页写明「可以复制、修改、分发、表演,包括商用用途,无需请求许可」(见文末核验表)。CC-BY:可商用但必须按规范署名 —— CC BY 4.0 官方页写明必须给出合理署名、链接到许可、说明是否修改(核验表)。NC / 个人免费:按标注不能商用。条款含糊或搜不到:标待确认,不许默认可用。

4. CC-BY 当场写署名文案。 决定用这个素材时,把署名句一并写进 credits 草稿 —— 攒到发布前统一补是最容易漏的环节。

5. 发布前清零。 「可商用 = 待确认」的行数必须为零。清不掉就把素材移出导出包(这一步属于发布检查,见 怎么做一次发布前检查)。

6. 留证据。 许可页截图或存档(带日期)放到台账目录旁边 —— 条款会变,截图是当时判断的依据。

The steps

1. Create the table. One assets-ledger.md (or spreadsheet) in the repository, with the seven columns above.

2. One file in, one row written. Record source and URL inside the same action that puts the asset into the project — skipped at retrieval time, unfindable a week later.

3. Sort licences into four buckets. CC0: no attribution — the CC0 page states you may "copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission" (table at the end). CC-BY: commercial is fine with attribution as specified — the CC BY 4.0 page requires appropriate credit, a licence link, and indicating changes (see the table). NC / personal-use-only: not commercial, as labelled. Vague or unfindable terms: unconfirmed — never silently treated as usable.

4. Write the attribution line on the spot. When you accept a CC-BY asset, put its credit into the credits draft immediately; batching this to ship-week is where it gets lost.

5. Clear before release. The count of "commercial = unconfirmed" rows must hit zero. Anything you cannot clear leaves the export package — that step belongs to How to run a pre-release check.

6. Keep evidence. A screenshot or dated snapshot of the licence page next to the ledger — terms change, and the screenshot is what your call rested on.

一个可走查的例子

⚠ 文件名、条目与时序是虚构示例。

  • 输入:音乐工具生成的循环曲 bgm_loop.ogg 准备进包;台账行:来源「生成服务 X 免费档」、许可页 URL 未记、可商用「待确认」。
  • 处理:打开该服务当前条款页 → 免费档条款没有写明商用授予(虚构情况)→ 按规则不许标「应该可以」。
  • 结果判断:失败 —— 该行维持「待确认」,bgm_loop.ogg 移出本次导出包。
  • 失败后下一步:两条路:① 换成明确 CC0 的曲包(台账新增一行,来源+许可页+核验日当场记全);② 升级该服务档位、条款页写明商用后,把条款文本截图存档,行状态改「是 · 附截图」。选 ① 更快,选 ② 保留这首曲子。

A walk-through example

⚠ The filenames, the situation and the timeline are a fictitious example.

  • Input: a generated loop bgm_loop.ogg is about to be packaged; the ledger row reads: source "generation service X, free tier", no licence-page URL recorded, commercial "unconfirmed".
  • Processing: open the service's current terms page → the free-tier text does not grant commercial use (invented situation) → by the rules you may not write "probably fine".
  • Result: fail — the row stays "unconfirmed" and bgm_loop.ogg leaves this export.
  • After the failure: two routes — ① swap in an explicitly CC0 music pack (new ledger row with source, licence page and verification date recorded on the spot); ② upgrade the tier, and once the terms state commercial use, archive a dated screenshot and flip the row to "yes — screenshot attached". Route ① is faster; route ② keeps the track.

失败分支

失败形态下一步
许可页打不开或已改版该行降级为「待确认」;发布包等不到就换素材
忘了素材是谁给的隔离该文件(不进导出包),能找回来源再解禁
CC-BY 署名攒到最后没写把整包署名句放进 credits;下次在台账第 4 步当场写
字体没有可商用标注按「不可商用」处理,见 字体的授权陷阱

Failure branches

Shape of failureNext step
The licence page is gone or has changedDemote the row to "unconfirmed"; if the release cannot wait, replace the asset
You forgot which file came from whomQuarantine it (out of the export) until the source is re-established
CC-BY credits postponed and never writtenPut the full attribution block into the credits page now; next time write it at step 4
A font carries no commercial-use statementTreat as not usable commercially — The font licensing trap

下一步

Next steps

来源与核验日

CC0 lets you copy, modify, distribute and perform the work, commercially, without asking permission — CC0 1.0 Universal official page · 2026-11-06

  • CC BY 4.0:必须给出合理署名、链接到许可、说明是否修改 — CC BY 4.0 官方页 · 2026-11-06

CC BY 4.0 requires reasonable attribution, a link to the licence and a note of any changes — CC BY 4.0 official page · 2026-11-06

  • 七列设计、「当场写署名」等取舍 — 本站的判断,无实测数据 · —

The seven-column design and "write the credit while you still remember it" are our own engineering judgement, not measured data — our judgement, no measurements · —