77 lines
2.9 KiB
Markdown
77 lines
2.9 KiB
Markdown
# Packer Pull Requests
|
|
|
|
This directory contains self-contained packer change proposals for review.
|
|
|
|
## Purpose
|
|
|
|
A pull request document packages a packer change as an executable plan before final integration.
|
|
|
|
Use this directory when a change:
|
|
|
|
- touches multiple documents or code paths,
|
|
- changes packer architecture or semantics,
|
|
- needs explicit acceptance criteria,
|
|
- affects diagnostics, build outputs, registry rules, or shipper boundaries,
|
|
- should be reviewed before editing the final normative corpus or implementation.
|
|
|
|
## Required Properties
|
|
|
|
Every pull request document must be self-contained.
|
|
|
|
A reviewer should be able to understand:
|
|
|
|
- the problem,
|
|
- the target state,
|
|
- the execution method,
|
|
- the acceptance bar,
|
|
- and the validation surface.
|
|
|
|
## Required Sections
|
|
|
|
Each packer pull request should include, at minimum:
|
|
|
|
1. Briefing
|
|
2. Target
|
|
3. Method
|
|
4. Acceptance Criteria
|
|
5. Tests or Validation
|
|
|
|
Recommended additional sections:
|
|
|
|
6. Motivation
|
|
7. Scope
|
|
8. Non-Goals
|
|
9. Affected Documents
|
|
10. Open Questions
|
|
|
|
## Writing Rules
|
|
|
|
- Keep the proposal self-contained and reviewable.
|
|
- Separate architectural reasoning from implementation detail.
|
|
- Make packer outputs and contracts explicit.
|
|
- Do not smuggle unresolved product or architecture choices into implementation steps.
|
|
- If a required decision is missing, stop and raise it instead of guessing.
|
|
|
|
## Review Rule
|
|
|
|
A pull request may plan code and spec consequences, but it must not replace a missing decision record.
|
|
|
|
## Production Sequence
|
|
|
|
The current production track for the standalone `prometeu-packer` project is:
|
|
|
|
1. [`PR-01-packer-project-bootstrap-and-module-boundaries.md`](./PR-01-packer-project-bootstrap-and-module-boundaries.md)
|
|
2. [`PR-02-workspace-init-registry-and-identity-foundation.md`](./PR-02-workspace-init-registry-and-identity-foundation.md)
|
|
3. [`PR-03-asset-declaration-parsing-validation-and-details-contract.md`](./PR-03-asset-declaration-parsing-validation-and-details-contract.md)
|
|
4. [`PR-04-workspace-scan-list-assets-and-studio-read-adapter.md`](./PR-04-workspace-scan-list-assets-and-studio-read-adapter.md)
|
|
5. [`PR-05-sensitive-mutations-preview-apply-and-studio-write-adapter.md`](./PR-05-sensitive-mutations-preview-apply-and-studio-write-adapter.md)
|
|
6. [`PR-06-doctor-diagnostics-and-safe-fix-baseline.md`](./PR-06-doctor-diagnostics-and-safe-fix-baseline.md)
|
|
7. [`PR-07-build-plan-determinism-and-cache-key-foundation.md`](./PR-07-build-plan-determinism-and-cache-key-foundation.md)
|
|
8. [`PR-08-assets-pa-and-companion-artifact-emission.md`](./PR-08-assets-pa-and-companion-artifact-emission.md)
|
|
9. [`PR-09-event-lane-progress-and-studio-operational-integration.md`](./PR-09-event-lane-progress-and-studio-operational-integration.md)
|
|
10. [`PR-10-versioning-migration-trust-and-production-gates.md`](./PR-10-versioning-migration-trust-and-production-gates.md)
|
|
|
|
Recommended dependency chain:
|
|
|
|
`PR-01 -> PR-02 -> PR-03 -> PR-04 -> PR-05 -> PR-06 -> PR-07 -> PR-08 -> PR-09 -> PR-10`
|