v2.0.0 — EAAO → EADOS: the delivery operating system #71
danielPoloWork
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
EAAO → EADOS: the delivery operating system
The language-agnostic factory becomes a phase-based delivery operating system —
init → design → plan → scaffold → audit → refactor, with the classic factory as thescaffoldphase. State-driven, role-owned, every phase mechanically gated; humans hold the terminal gates.Repository
pgs-eaao→pgs-eados, factory folder.eaao-core/→.eados-core/, self-linteados_lint.py, dev sentinel.eados-dev, distribution bundlepgs-eados-bundle.*, command surface/eados. Consumers who vendored the bundle must update their.eados-core/path and re-download the new asset. Old GitHub URLs auto-redirect.Added — the delivery OS (M1–M5)
orchestrator/os/(workflow, authority, git, rfc, plan, risk), each_schema.md+ reference instance + aneados_lintgate.orchestrator/domains/{software,game,mobile}.yamlparallel to the language profiles (PRD vs GDD, NFR hard-budgets, SemVer vs Alpha/Beta/RC).phase_runner,rfc_check,authority_check,traceability,risk_score,brownfield,migration_planner,sandbox;/eados {init,design,plan,scaffold,audit,refactor}command surfaces.cross-spec-consistencygate (feat(lint): cross-spec-consistency gate — referential integrity across the OS specs #62) — referential integrity across the OS specs (anti-fragmentation).Fixed / Security
roadmap-covers-rfcsmatched RFC ids by raw substring (false coverage); now matched on a word boundary..gitonly at the top level; now refused at any depth (a nested/submodule.git/).The full, itemized changelog is in CHANGELOG.md → 2.0.0. On publish,
release.ymlattaches thepgs-eados-bundle.{tar.gz,zip}factory bundle automatically.This discussion was created from the release v2.0.0 — EAAO → EADOS: the delivery operating system.
Beta Was this translation helpful? Give feedback.
All reactions