docs: consolidate canonical specs and preserve PBS reference IDs
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Packer Specs
|
||||
|
||||
Owner: `packer`. Canonical source: `docs/specs/packer`.
|
||||
|
||||
This directory contains the normative packer specification set.
|
||||
|
||||
## Purpose
|
||||
@@ -47,7 +49,7 @@ Specs should normally be fed by:
|
||||
|
||||
1. agendas that frame the open topic,
|
||||
2. decisions that close the architectural question,
|
||||
3. pull-request plans that define propagation,
|
||||
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.
|
||||
@@ -77,3 +79,6 @@ Recommended order:
|
||||
4. build artifacts;
|
||||
5. diagnostics and Studio operation model;
|
||||
6. versioning and trust.
|
||||
|
||||
|
||||
See the [specification guide](../README.md) for compiler, language and provider boundaries.
|
||||
|
||||
Reference in New Issue
Block a user