You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Or supply an immutable released revision explicitly with `--revision <40-hex-sha>`. Initialization creates the manifest and lock, compact `AGENTS.md`/`CLAUDE.md`, portable Skills, and a validation workflow. Add repository differences—validation commands, protected path hints, UX triggers—to `.engineering/process.yaml`, then re-render/re-lock using a reviewed process upgrade.
31
+
Or supply an immutable released revision explicitly with `--revision <40-hex-sha>`. Initialization creates the manifest and lock, compact `AGENTS.md`/`CLAUDE.md`, portable Skills, and a validation workflow. Existing assistant context is never silently overwritten; follow the [mature repository migration](docs/adoption.md#mature-repository-migration) and use the explicit `--adopt-existing-context` flow. Add repository differences—validation commands, protected path hints, UX triggers—to `.engineering/process.yaml`, then re-render/re-lock using a reviewed process upgrade.
Copy file name to clipboardExpand all lines: docs/adoption.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,5 +9,34 @@
9
9
10
10
Repository-local technology is deliberately opaque to policy. Put commands under `overrides.validation.commands`; add sensitive paths/characteristics and domain triggers when they strengthen classification. Never copy the canonical policy into the manifest.
11
11
12
-
For upgrades, run `engineering-process upgrade --version X --revision SHA --dry-run`, review inherited/profile/generated-file changes and conflicts, then apply from the reviewed target process checkout. A central update never mutates an active repository automatically.
12
+
## Mature repository migration
13
13
14
+
Initialization is non-destructive. If `AGENTS.md`, `CLAUDE.md`, or the process validation workflow is repository-owned, normal `init` stops before creating `.engineering/process.yaml`. Do not use `--force` to bypass this boundary.
15
+
16
+
Use this reviewed workflow:
17
+
18
+
1. Inventory existing assistant, architecture, branch/release, validation, security, product/UX, and deployment guidance. Identify copied generic policy versus genuine repository-specific context.
19
+
2. Keep canonical requirements in this process. Keep local mechanics and stronger constraints in repository-owned documents. Existing `overrides` remain the only mechanism for validation commands, classification additions, UX triggers, controls, and native enforcement.
20
+
3. Commit or otherwise preserve a baseline so the migration can be reviewed.
21
+
4. Run `engineering-process --root <repo> init --profile frontend --adopt-existing-context`. The command moves existing `AGENTS.md` and/or `CLAUDE.md` verbatim into `docs/engineering/local-context/`, declares them in `local_context`, and writes compact generated bootstraps. It refuses to replace a repository-owned workflow.
22
+
5. Split or rename the preserved documents as useful, then update `local_context`. Each entry has a category, repository-relative path, and optional contextual `load_when` instruction:
23
+
24
+
```yaml
25
+
local_context:
26
+
- category: operating_contract
27
+
path: docs/engineering/operating-contract.md
28
+
load_when: load before branch, issue, or release workflow changes
29
+
- category: architecture
30
+
path: docs/architecture/
31
+
load_when: load for changes affecting component boundaries
32
+
- category: ux_product_design
33
+
path: docs/ux/ux-gates.md
34
+
load_when: load for user-visible changes
35
+
```
36
+
37
+
6. Review the full diff. Confirm branch responsibilities, issue-first workflow, agent roles, architecture/deployment rules, Senior UX Designer responsibilities, UX Gates A-D, and local implementation/review conventions remain referenced and readable.
38
+
7. Run `engineering-process validate`. Missing paths, invalid context structure, stale generated bootstraps, modified generated files, and locked-control override attempts fail validation.
39
+
40
+
Local-context documents add detail and mechanics; they do not override the Effective Obligation Set. Progressive `load_when` hints keep the bootstraps compact and avoid loading every document for every change.
41
+
42
+
For upgrades, run `engineering-process upgrade --version X --revision SHA --dry-run`, review inherited/profile/generated-file changes, preserved local-context paths, and conflicts, then apply from the reviewed target process checkout. Upgrade verifies generated-file hashes before replacement and refuses modified or repository-owned targets. It never rewrites files referenced by `local_context`. A central update never mutates an active repository automatically.
0 commit comments