adopt-repo-standardslisted

# Adopt Repo Standards When you need to **bring a concrete repository onto the engineering baseline** (constitution, project facts, fences, conformance entrypoints), run **one adoption** cycle—not a permanent dual instruction stack. ## When to use - New or existing product repo needs Skills-aligned engineering baseline - Predecessor instruction layouts / dual standards must be retired - Manifest, fences, and conformance entrypoints are missing or stale ## Method **Required surfaces → wire entrypoints → verify → hard-cut predecessor layouts.** ### 1. Frame - Target repo and delivery terminal - Required surfaces (constitution projection, project.manifest, fences, checks) - Predecessor instruction sources to retire ### 2. Research - What is already present vs missing (read repo; do not invent authority) - Depth: [references/full-standard.md](references/full-standard.md) - When wiring project facts: open [references/project-manifest-standard/](references/project-manifest-standard/) - When choosing stack/profile fences: open [references/enterprise-profile-standard/](references/enterprise-profile-standard/) and [references/enterprise-control-plane-standard/](references/enterprise-control-plane-standard/) as needed - For implementation shape constraints applied *while adopting*, open sibling depth under other workflows only if this adoption must implement product code: - `../build-product/references/engineering-standard/` - `../select-dependency-versions/references/techno