Smart Init

What Smart Init detects

• Single-project repositories and monorepos
• Common stack signals such as Node.js / TypeScript, NestJS, Express.js, Java, Spring / Spring Boot, Kotlin, FastAPI, Django, Flask, PHP, Laravel, Go, .NET, Ruby on Rails, React, Next.js, Angular, Vue, Terraform, Ansible, and other practical repository patterns
• Likely components such as apps, services, libraries, workers, frontends, backends, CLIs, and infrastructure units
• Probable module or bounded-context structure from repository layout
• Resource hints such as APIs, databases, queues, storage, and infrastructure from local configuration and source patterns

Components, modules, and resources

A component is a logical unit of the repository, such as a frontend app, backend service, worker, shared library, or infrastructure package.

A module is a code-level grouping inside a component. A resource is an external or system dependency such as an API, database, queue, storage bucket, or infrastructure service.

How detection works

Smart Init is evidence-based and deterministic. It uses local repository structure, dependency markers, and practical framework signals, including FastAPI, Django, and Flask evidence, rather than a hosted scan or guesswork that changes from run to run.

The result is a proposed architecture configuration preview that the user can review before anything is applied.

Why this matters

Teams often want architecture-as-code without a heavy setup ceremony. Smart Init gets them to a workable first model faster while keeping the model explicit and editable.

It also helps ArchPilot use more relevant defaults for architecture validation, dependency validation, and future governance workflows.

What users control

• Users can review the detection summary before initialization is finalized.
• Detected values can be adjusted when the repository shape is unusual or intentionally custom.
• ArchPilot asks for unresolved fields instead of forcing the user through every possible setting.