Plan the policy alignment work
This commit is contained in:
@@ -221,19 +221,10 @@ copying an additional documentation tree. Do not copy unused license texts,
|
||||
example projects, or placeholder documents. Root Notarius `AGENTS.md` is based
|
||||
on upstream `agents/AGENTS.md`, not upstream's own contributor instructions.
|
||||
|
||||
## Recommended Work Sequence
|
||||
## Implementation Ownership
|
||||
|
||||
1. Adopt the policy set and orientation changes together with copied-policy
|
||||
attribution, its local license text, and the COPYRIGHT scope statement.
|
||||
Keep cross-links valid at this boundary.
|
||||
2. Complete incorporated-component attribution and applicable license texts;
|
||||
connect README, integration guidance, and prospective release navigation.
|
||||
3. Compare the result directly with the selected upstream files, verify that
|
||||
remaining variations have the stated local justification, and check notices,
|
||||
metadata, and links.
|
||||
|
||||
These are coherent work boundaries, not authorization to execute them during
|
||||
roadmap preparation. A later implementation plan may subdivide them.
|
||||
[Implementation Plan](implementation.md) owns the ordered work stages and their
|
||||
validation. This document owns the target end state, scope, and policy choices.
|
||||
|
||||
## Scope Boundaries And Acceptance
|
||||
|
||||
|
||||
Reference in New Issue
Block a user