Change: module-migration-11 - Project And Codebase Ownership Realignment
Parent Feature: #354 Module Migration & CLI Reorganization
Resolves the post-migration ownership ambiguity between specfact-project and specfact-codebase for brownfield import and related analysis internals.
Problem
import from-code was historically moved under the project family during module migration, even though its primary input is a source codebase.
- migration artifacts now disagree about whether brownfield analysis internals (
analyzers, comparators, parsers, related helpers/agents) belong to specfact-project or specfact-codebase.
- active follow-up changes can otherwise keep reinforcing contradictory public paths and ownership assumptions.
Target Direction
- treat code-first brownfield workflows as
specfact code ... ownership
- narrow
specfact project ... to SpecFact bundle/workspace artifact lifecycle
- realign internal subsystem ownership so brownfield analysis internals have one canonical owner
- update pending migration/docs/prompt/runtime validation work so the new ownership model is enforced consistently
Related
Change: module-migration-11 - Project And Codebase Ownership Realignment
Parent Feature: #354 Module Migration & CLI Reorganization
Resolves the post-migration ownership ambiguity between
specfact-projectandspecfact-codebasefor brownfield import and related analysis internals.Problem
import from-codewas historically moved under theprojectfamily during module migration, even though its primary input is a source codebase.analyzers,comparators,parsers, related helpers/agents) belong tospecfact-projectorspecfact-codebase.Target Direction
specfact code ...ownershipspecfact project ...to SpecFact bundle/workspace artifact lifecycleRelated
module-migration-11-project-codebase-ownership-realignment