# MVC-Starter Project Structure

**Date:** 2026-03-11T11:59:39Z
**Repository Type:** monolith
**Detected Project Type:** web
**Specific Runtime Shape:** Classic ASP server-rendered MVC starter on Windows IIS
**Primary Technologies:** Classic ASP, VBScript, IIS, Microsoft Access

## Classification Summary

This repository is a single deployable web application, not a multi-part client/server system. It is a server-rendered Classic ASP MVC starter with:

- `public/` as the IIS web root and deploy entrypoint
- `core/` as shared framework/runtime code
- `app/` as the application extension surface for controllers, views, models, and repositories
- `db/` as database and migration support
- `scripts/` as scaffolding and operational tooling

## Detected Part

### MVC-Starter

- **Root Path:** `/workspace/MVC-Starter`
- **Project Type:** web
- **Runtime Shape:** Server-rendered MVC monolith
- **Hosting Assumption:** Windows IIS with URL Rewrite
- **Deploy Entry Point:** `public/Default.asp`
- **Framework Runtime:** `core/`
- **Application Extension Surface:** `app/`
- **Operational Support Directories:** `db/`, `scripts/`

## Why This Classification Fits

- The repository exposes a single web entrypoint through `public/Default.asp` and IIS rewrite config in `public/web.config`.
- Request handling flows through `public/` into framework code in `core/`, while application behavior is implemented in `app/`.
- Request handling, view rendering, routing, data access, and framework runtime are all contained in one application tree.
- There are no separate client/server packages, independent deployables, or service boundaries that would justify multi-part classification.
- The repo structure matches a classic server-rendered MVC application rather than a frontend/backend split web stack.
