Build the evidence chain in order
- 01
Review provenance and rights
Confirm the declared source category, required attribution, and AI-generated status before treating image inputs as publishable.
- 02
Validate the declaration
Require the exact schema, kind, slug, version, fixed token catalog, controlled visual values, asset roles, and compatibility fields.
- 03
Install the final candidate in isolation
This guide targets DeepSeek Harness 0.1.3-alpha.1 at source commit d347e703908d0406b7a7ef80e3a0e594d86b2215. The Alpha installation uses a build from that exact source revision. Check the selected item’s current package, profile, and test results separately; older receipts and screenshots do not establish compatibility with this Alpha.
- 04
Capture real light and dark evidence
Use the DSH Appearance control in the actual Web UI, replace simulated previews with controlled runtime WebP derivatives, and preserve their metadata.
- 05
Rebuild and verify deterministically
Let the trusted generator rebuild from the reviewed declaration and assets, then verify the final complete artifact before publication.
Keep digest scopes separate
| Token | Role | Check |
|---|---|---|
| artifact.sha256 | Final complete tgz bytes | Authorizes the exact downloaded installation artifact |
| payload.sha256 | Canonical tar payload excluding the manifest | Supports deterministic content audit, not download authorization |
| preview asset SHA-256 | One controlled runtime image derivative | Must match its URL, dimensions, byte size, and asset declaration |
- Reject simulated or external publication previews.
- Reject unrecognized, historical, candidate, or mixed compatibility and runtime-attestation fingerprints.
- Reject artifact, integrity, path, MIME, byte-size, or dimension mismatches.
- Reject symlinks, path traversal, untrusted executable author input, and non-deterministic rebuilds.
- Publish only a specific reviewed version whose controlled download is available.
Prepare the release
Prepare a reviewable release
Submit a specific draft version with its source information and both visual modes. Review the produced package and test results before publication, so the published item matches what users actually install.
Review this release draft for completeness: source and license, light and dark assets, package identity, installation, restart, and rollback. Report concrete blockers and prepare the final review package.Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: Full Skin publication gate; Fixed 0.1.3-alpha.1 source and item-level verification; Artifact and payload digest scopes
What should I do first?
Publication is the point where an attractive draft becomes a versioned claim. Every claim must resolve to reviewed declarations, controlled bytes, and evidence from the supported runtime.
Which boundary matters most?
This guide targets DeepSeek Harness 0.1.3-alpha.1 at source commit d347e703908d0406b7a7ef80e3a0e594d86b2215. The Alpha installation uses a build from that exact source revision. Check the selected item’s current package, profile, and test results separately; older receipts and screenshots do not establish compatibility with this Alpha.
Does passing a technical test establish artwork rights?
No. Runtime behavior and rights are separate. A release still needs accurate licenses, attribution, and permission for third-party material.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.