Resolve unconvertible-character findings in a manuscript-encoding approval ledger before EPUB creation, then treat EPUB output as a separate gate. This article records which manuscript encoding boundary was approved and who approved each wording decision. It does not convert individual files, execute save blocking, or generate an EPUB.
Rune Studio findings belong to the manuscript read/write preflight. They are not proof of Unicode behavior in EPUB 3 content, EPUB package validity, reader rendering, or store acceptance.
Approve the manuscript encoding in the ledger header
Record project ID, manuscript revision, received encoding, editing encoding, planned handoff, approver, and approval date. For example: received as standard SHIFT_JIS, edited as UTF-8, and handed to the EPUB stage as UTF-8.
Do not merge SHIFT_JIS with Windows-31J / CP932. An unknown origin remains unapproved and returns to the observation or conversion owner. A ledger does not turn a guess into approval.
Close each meaning decision in five columns
| Location | Original | Proposed wording | Evidence | Approver |
|---|---|---|---|---|
| chapter, paragraph, context | character and code point | candidate wording | author direction or glossary | name and time |
Use a location that can be found again. Include U+XXXX when known. Apply only rows with both evidence and an approver. Header-level encoding approval is independent from row-level meaning approval.
Accept only finding locations from Rune Studio
Stage 3 materials confirm major Japanese encoding detection, red highlighting of unconvertible characters, and automatic-save blocking while an issue remains. The ledger can accept those locations as intake.
Rune Studio does not approve replacement meaning or prove EPUB rendering. There is also no Stage 4 result showing a two-chapter intake, approved-row application, and zero-finding rescan.
Reconcile zero findings with full approval
Submission requires both conditions:
- every in-scope ledger row is approved; and
- the approved manuscript has zero unresolved findings at the same encoding boundary.
Zero findings cannot hide a pending approval, and full approval cannot hide a remaining finding. This article defines the reconciliation but does not claim it was executed.
Bind one ledger revision to one manuscript revision
Put manuscript filename and SHA-256, ledger revision, and approval deadline in the header. Do not reuse an earlier zero-finding result after the manuscript changes. A cancelled row remains in history with its reason and approver; deleting it merely to make counts agree is not approval.
If the EPUB operator edits the manuscript, return it as a new manuscript revision. Output-stage editing does not overwrite the approval ledger.
Put EPUB output behind a separate gate
| Gate | Evidence | Covered here |
|---|---|---|
| Manuscript encoding and meaning approval | header and five columns | yes |
| EPUB generation | artifact and tool log | no |
| EPUB package validity | structural validation | no |
| Reader rendering | device checks | no |
| Store acceptance | store response | no |
Hand the EPUB stage the approved manuscript revision, encoding declaration, ledger revision, and zero-unresolved record. STUDIO-065 owns save blocking, STUDIO-534 owns reversible conversion, and STUDIO-521 owns BOM observation.
The first action is not conversion. Approve the manuscript encoding in the header and close one five-column row, while keeping that evidence explicitly separate from EPUB output evidence. Repeat both the manuscript and ledger revisions on the boundary sheet.
