Add shared human/task asset batches with reviewed atomic publication, explicit reference rebinds, ownership inspection and qualified glyph/scene budgets. Expose the same authoring and capacity results through Assets and MCP. Deliver isolated guest test targets, retained visual evidence and immutable runtime lifecycle/control observations. Preserve provider qualification and installed authoring examples alongside the completed discussion lessons. Close AGD-106 coordination and the delivered discussion workflows through housekeeping, updating lesson references and preserving qualification limits. Sound remains outside the asset delivery wave. Validation: 579 module tests and 31 additional desktop, process and installed checks passed; native glyph/scene 16/17 boundaries qualified. Discussion validation passed after housekeeping.
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:
- Title
- Status
- Scope or Applies To
- Purpose
- Authority and Precedence
- Normative Inputs
- Core Rules
- Non-Goals
- 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:
- agendas that frame the open topic,
- decisions that close the architectural question,
- plans that define propagation,
- 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. Domain and Artifact Boundary Specification.md2. Workspace, Registry, and Asset Identity Specification.md3. Asset Declaration and Virtual Asset Contract Specification.md4. Build Artifacts and Deterministic Packing Specification.md5. Diagnostics, Operations, and Studio Integration Specification.md6. Versioning, Migration, and Trust Model Specification.md
Reading Order
Recommended order:
- domain and artifact boundary;
- workspace and identity;
- asset declaration;
- build artifacts;
- diagnostics and Studio operation model;
- versioning and trust.
See the specification guide for compiler, language and provider boundaries.