Files
prometeu-studio/docs/specs/packer
bquarkz bf31184d4d feat(pbs): add sprite animation and shared Studio authoring
Implement DEC-0084 with factory-only Sprite/Animator structs, complete result
lowering, validated animation sidecars, generated PBS factories and JavaFX/MCP
authoring through shared services.

Qualify native dev/release with ordinary and optimized producers, zero-allocation
playback, private-cycle reclamation, canonical Composer pixels, installed JARs
and JavaFX lifecycle. Preserve the runtime checkout and existing host ABI.
2026-11-05 15:16:07 +00:00
..

Packer Specs

Owner: packer. Canonical source: docs/specs/packer.

This directory contains the normative packer specification set.

Purpose

Specs define the official packer contract.

They exist to make behavior, constraints, interfaces, and artifact guarantees stable across implementation and review.

The packer normative content is maintained directly in this specs/ corpus.

Expected Format

The exact structure may vary by document, but a packer spec should usually contain:

  1. Title
  2. Status
  3. Scope or Applies To
  4. Purpose
  5. Authority and Precedence
  6. Normative Inputs
  7. Core Rules
  8. Non-Goals
  9. Exit Criteria

Some specs may also include:

  • artifact schemas,
  • invariants,
  • diagnostic contracts,
  • examples,
  • migration notes,
  • explicit TODO sections for tracked unresolved items.

Writing Rules

  • Write in normative language.
  • Integrate only decisions that have already been closed.
  • Keep debate history and option analysis out of the spec body.
  • Preserve clear boundaries between adjacent packer specs.
  • Use TODO only for explicitly tracked unresolved items, not as a substitute for agenda work.

Upstream Rule

Specs should normally be fed by:

  1. agendas that frame the open topic,
  2. decisions that close the architectural question,
  3. plans that define propagation,
  4. then spec integration.

If a spec edit would require guessing an unresolved design choice, stop and surface the missing decision first.

Integration Boundary

The Packer package root is p.packer, and Packer remains autonomous from Studio. Studio consumes stable public Packer APIs directly and introduces a narrow consumer-owned gateway only for concrete, static, unstable, or infrastructure-specific integration. Packer never depends on p.studio.

Current Corpus

The current packer core corpus is:

  1. 1. Domain and Artifact Boundary Specification.md
  2. 2. Workspace, Registry, and Asset Identity Specification.md
  3. 3. Asset Declaration and Virtual Asset Contract Specification.md
  4. 4. Build Artifacts and Deterministic Packing Specification.md
  5. 5. Diagnostics, Operations, and Studio Integration Specification.md
  6. 6. Versioning, Migration, and Trust Model Specification.md

Reading Order

Recommended order:

  1. domain and artifact boundary;
  2. workspace and identity;
  3. asset declaration;
  4. build artifacts;
  5. diagnostics and Studio operation model;
  6. versioning and trust.

See the specification guide for compiler, language and provider boundaries.