Crafting Desktop Companion Pets

Crafting DesktopCompanion Pets

Start

Record the exact target/run root, task type, identity route, detected or proposed format, immutable comparison set, and separate install/integrate/ commit/push/publish authority.

Route the task as new pet, identity/proportion repair, action work, deterministic frame/atlas repair, format migration, runtime/scheduler repair, or validation/handoff. A narrow deterministic repair may enter at its nearest gate only when identity, action meaning, format, and behavior are already selected.

Read only the applicable references

• Model capability, approvals, or resuming production: execution-and-models.md.
• Identity or evidence: identity-and-evidence.md.
• Morphology, proportion, or likeness: canonical-identity-and-proportions.md.
• Actions, motion, props, or effects: actions-and-motion.md.
• Generation batches or retries: generation-job-graph.md and repair-and-convergence.md.
• Visual/technical review: visual-qa.md.
• Scheduling, movement, or long use: behavior-and-soak.md.
• Format/package/runtime: exactly one or more applicable format-v2.md, format-v3.md, or format-v4.md references, based on detected/confirmed capability needs.
• Nangong Wan: nangong-wan-calibration-case.md only for process/desktop calibration; never use its geometry or numbers as another target's rule.

Hard gates

1. Select canonical identity at actual runtime size before dependent visual jobs. Source-faithful work uses target evidence; original/brand work uses an approved brief.
2. Generated images are candidates. Deterministic tools own extraction, registration, order, atlases, previews, hashes, and reports.
3. Builder self-review and independent internal visual review must pass before user acceptance handoff. The user is not fallback QA; present only internally passing candidates or a genuinely irreducible choice/authority decision.
4. Technical, visual, package, runtime, behavior, user acceptance, and authority statuses remain independent. Metrics cannot award visual pass.
5. Use semantic phases and target-specific action contracts; never fill fixed quotas or slide standing art for locomotion.
6. Preserve canonical body occupancy when effects expand. Change composition/layers/format rather than shrinking the character.
7. Invalidate only downstream claims affected by an upstream hash change. Repair the causal layer and change strategy after the same root condition recurs.
8. Creation or packaging never authorizes installation, integration, commit, push, publication, account use, or global configuration.

Retained result

Existing approval persists for its stated scope. Internal gate passage permits the next already-authorized production step; it does not require another user confirmation unless the user reserved that decision. Record final user acceptance separately. A blocked dependency does not block unrelated safe preparation.

Keep the project brief/evidence, identity and action contracts, canonical hash, jobs, generated and deterministic artifacts, actual-size sheets, true-duration previews, per-gate verdicts, commands/exit codes, unverified checks, authority state, run summary, and local keep/archive/cleanup/ uncertain inventory. Stop with the exact blocker when a required gate or authority cannot be established.