Move Property Intelligence to root solutions

Author: dimitree2k

CLAUDE.md

@@ -54,7 +54,8 @@ aac-forge/
 │   ├── SAD-template.md
 │   └── REVIEW-template.md
 ├── examples/
-│   └── order-management/            # Real-world enterprise domain
+│   └── order-management/            # Tutorial/demo/reference domain only
+├── solutions/                        # Real architecture change packages for root model
 ├── tests/                            # Golden-file tests + smoke test
 └── .github/workflows/                # CI/CD
 ```
@@ -120,6 +121,10 @@ borders, shapes, icons, and relationship styling. Colors and borders must carry
 architecture meaning such as ownership zone, sensitivity, lifecycle status, publication
 path, certainty, or boundary semantics.
 
+Real architecture work belongs in root `solutions/` and root `model/`. The `examples/`
+tree is reserved for tutorial/demo/reference material and must not be auto-selected for
+production architecture generation.
+
 ### Modular Files
 
 All `*.c4` files in a directory tree are **auto-discovered and merged** by LikeC4.

README.md

@@ -91,9 +91,11 @@ aac-forge/
 │   └── REVIEW-template.md            # 5-role review report template
 │
 ├── examples/
-│   └── order-management/             # Real-world enterprise domain
+│   └── order-management/             # Tutorial/demo/reference domain only
 │       ├── model/                    # 3 domains: customer-facing, core-services, integrations
 │       └── solutions/001_.../        # BR + SAD — Automated Order Fulfillment
+├── solutions/                        # Real architecture change packages for the root model
+│   └── 001_.../                      # BR + ADRs + SAD + review output
 │
 ├── tests/
 │   ├── smoke-test.sh                 # End-to-end pipeline validation
@@ -173,6 +175,10 @@ All `*.c4` files in a directory tree are **auto-discovered and merged**. Only on
   filters. Avoid generic `include *` landscape views for SAD deliverables unless they
   are intentionally curated portfolio/workspace views.
 
+Real architecture work belongs in root `solutions/` and root `model/`. The `examples/`
+tree is reserved for tutorial/demo/reference material and should not be auto-selected
+for production architecture generation.
+
 ## CI/CD
 
 On PR: validates all model workspaces + format check + smoke tests.

docs/how-to/create-new-solution.md

@@ -15,7 +15,7 @@ The pipeline: **BR document → LLM generates C4 model changes → validate →
 
 ## 1. Create the Solution Folder
 
-Solutions live in `solutions/` (for the main model) or `examples/<name>/solutions/` (for example models):
+Real architecture solutions live in root `solutions/`:
 
 ```
 solutions/
@@ -28,6 +28,8 @@ solutions/
 ```
 
 `NNN` is a zero-padded sequential number (001, 002, ...). Use the next available.
+The `examples/` tree is reserved for tutorial/demo/reference material. Do not place
+working enterprise architecture packages under `examples/`.
 
 ```bash
 mkdir -p solutions/001_My_Feature/input
@@ -73,6 +75,7 @@ A good BR includes:
 
 See existing BRs for examples:
 
+- `solutions/001_Property Intelligence Platform/input/BR Property Intelligence Platform.md`
 - `examples/order-management/solutions/001_.../input/BR Automated Order Fulfillment.md`
 
 ## 3. Run the Generate Skill

docs/input/specs/ADR-process.md

@@ -147,7 +147,7 @@ BR Document
 
 | Scope | Path | Example |
 | --- | --- | --- |
-| **Solution decisions** | `<solution>/decisions/` | `examples/order-management/solutions/002_.../decisions/ADR-002-0001-kafka-vs-rest.md` |
+| **Solution decisions** | `<solution>/decisions/` | `solutions/002_.../decisions/ADR-002-0001-kafka-vs-rest.md` |
 | **Repo/tooling decisions** | `docs/adr/` | `docs/adr/ADR-0001-use-likec4-over-structurizr.md` |
 
 Solution ADRs are architecture decisions made while designing a solution. They live with

examples/AGENTS.md

@@ -0,0 +1,6 @@
+# Examples Directory
+
+This tree is only for tutorial, demo, and reference material.
+
+Do not create real enterprise architecture solutions here. Use root `solutions/` for
+BR, ADR, SAD, and review artifacts, and root `model/` for the active architecture model.

skills/arch-generate-solution.md

@@ -6,13 +6,19 @@ ADRs Accepted → edits the LikeC4 model → validates → exports diagrams →
 SAD (rev 2) → verifies.
 
 **Argument:** Path to the solution folder, e.g.
-`solutions/001_Forging Runic Diagrams and Covenant Scrolls` or
-`examples/order-management/solutions/002_Automated Order Fulfillment`.
+`solutions/001_Property Intelligence Platform`.
 
-If no argument is provided, iterate through `solutions/NNN_Name/` folders (and
-`examples/*/solutions/NNN_Name/`) from highest number to lowest. Target the first folder
-that has files in `input/` but whose `output/` folder is empty or has only a SAD
-skeleton (rev 1, status: Draft). If none found, ask the user.
+Real architecture work lives under root `solutions/`. The `examples/` tree is only for
+tutorial/demo/reference work.
+
+If no argument is provided, iterate through `solutions/NNN_Name/` folders from highest
+number to lowest. Target the first folder that has files in `input/` but whose `output/`
+folder is empty or has only a SAD skeleton (rev 1, status: Draft). If none found, ask
+the user.
+
+If the user passes a path under `examples/`, confirm that they intentionally want to
+work on tutorial/demo material before creating or modifying artifacts there. Do not
+auto-select `examples/*/solutions/` for normal architecture work.
 
 ---
 
@@ -53,8 +59,11 @@ Use `readFile` to read all files from `<solution>/input/`.
 > `tail`, or `range` options.
 
 **1.2 Read the current architecture model**
-Use `searchFiles` with pattern `*.c4` under `model/` (or the relevant `examples/*/model/`)
-to discover all model files. Use `readFile` to read every discovered `.c4` file.
+Use `searchFiles` with pattern `*.c4` under `model/` to discover all model files. Use
+`readFile` to read every discovered `.c4` file.
+
+Only read an `examples/*/model/` workspace when the user explicitly passed an
+`examples/` solution path and confirmed they are working on tutorial/demo material.
 
 **1.3 Read workspace configuration**
 Use `readFile` to read `aac-forge.config.json` (repo root) for `approvalBackend` and