최신 릴리스 : v7.1.2-alpha · 주요 : 해제 · 릴리스 상태 : ALPHA

버전: 7.0.0 ( Framework version live docs are Verified against, read by scripts/check-version-declared.sh) | 라이센스: MIT

**Status **: 액티비 **Owner **: @dttai71 Consumer: 첫 번째 리더 및 팀은 프레임 워크를 채택 여부 결정 **리뷰 **: 2026-12-26

누가 이것을 읽습니다 : 누구나 프레임 워크를 채택하거나 처음이 재포를 열지 결정합니다. 언제: 다른 것의 앞에. 10 분이 걸립니다. 레이아웃 및 읽기 주문은이 페이지의 끝 부분에 있습니다.

프레임 워크가 무엇인지

버전 7은 프레임 워크의 두 번째 세대입니다 : 재건축, 업그레이드하지. 첫 번째 세대 (v6 및 이전)은 [archive/]에서 비유되지 않은 아카이브입니다. 여전히이 나무에 수확 된 것, 소스 당 한 행 MIGRATION-MAP.md. 첫 번째 세대의 아무것도가 거기에서 행하지 않는 한 적용.

1. AI 에이전트 및 몇 명의 사람들과 소프트웨어를 구축하기위한 방법론 - 종종 하나.
2. 당신은 4개의 자산을 소유합니다. Vendors는 나머지를 공급합니다: 에이전트, 모델, 런타임, 정션 오케스트라.
3. 규칙은 3개의 종류에 앉습니다. 단결정 검사 블록.
4. 명세.

SDLC Enterprise Framework

Latest release: v7.1.2-alpha · Main: Unreleased · Release status: ALPHA

Version: 7.0.0 (the framework version live docs are verified against, read by scripts/check-version-declared.sh) | License: MIT

Status: ACTIVE Owner: @dttai71 Consumer: first-time readers and teams deciding whether to adopt the framework Review by: 2026-12-26

Who reads this: anyone deciding whether to adopt the framework, or opening this repo for the first time. When: before anything else. It takes ten minutes; the layout and reading order are at the end of this page.

What the framework is

Version 7 is the framework’s second generation: rebuilt, not upgraded. The first generation (v6 and earlier) is archived unmodified in archive/; what still holds was harvested into this tree, one row per source in MIGRATION-MAP.md. Nothing from the first generation applies unless it has a row there.

1. A methodology for building software with AI agents and a few people — often one.
2. You own four assets. Vendors supply the rest: agents, models, runtimes, in-session orchestration.
3. Rules sit in three classes. Only deterministic checks block.
4. Controls scale with the risk of the thing being built, not with team size.
5. A rule names a runnable command and the real incident (burn case) that justifies it.
6. A rule without a command is reference material, not a rule.
7. Gates default to ADVISORY with a counter and a deadline, and climb only on measured rates. A narrow control against irreversible harm may enter MACHINE directly — only under the exception contract in controls/rule-contract.md.
8. Incidents flow back into rules through one path (lessons-to-rules).
9. The framework gates itself in CI: doc count, rule tables, version declarations.
10. Promise: fewer rules, more of them enforced. Every section says what it shortens.

The four assets you own

Everything else is rented: agent CLIs, subagents, skills, hooks, models, CI runners. Adapters to them are generated and disposable. The policy is not. This repo’s skills/ are such adapters: they route an agent to the files that hold the rules, and are not a fifth asset. Shortens: you build and maintain nothing a vendor already ships.

Tier by risk of the artefact, not headcount