ai-core-framework 0.1.0 → 0.2.0

package/{core/scripts → scripts}/sync-platforms.sh

@@ -1,16 +1,16 @@
 #!/usr/bin/env bash
 # ============================================================================
 # sync-platforms.sh
-# Sync core/ content sang Claude Code, Cursor, Windsurf format.
-# Usage: bash core/scripts/sync-platforms.sh
+# Sync root-level framework folders to Claude Code, Cursor, and Windsurf format.
+# Usage: bash scripts/sync-platforms.sh
 # ============================================================================
 
 set -euo pipefail
 
 AI_CORE_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-PROJECT_ROOT="$(dirname "$AI_CORE_DIR")"
+PROJECT_ROOT="$AI_CORE_DIR"
 
-echo "🔄 Syncing core/ to AI platforms..."
+echo "🔄 Syncing root-level framework folders to AI platforms..."
 echo "   Source: $AI_CORE_DIR"
 echo "   Target: $PROJECT_ROOT"
 
@@ -41,14 +41,16 @@ sync_claude_code() {
     done
 
     # --- Sync commands (flatten from subdirs) ---
-    find "$AI_CORE_DIR/commands" -name "*.md" -type f | while read -r cmd_file; do
-        local basename
-        basename=$(basename "$cmd_file")
-        # Skip README files
-        [[ "$basename" == "README.md" ]] && continue
-        cp "$cmd_file" "$claude_dir/commands/$basename"
-        echo "   ✓ command: $basename"
-    done
+    if [ -d "$AI_CORE_DIR/commands" ]; then
+        find "$AI_CORE_DIR/commands" -name "*.md" -type f | while read -r cmd_file; do
+            local basename
+            basename=$(basename "$cmd_file")
+            # Skip README files
+            [[ "$basename" == "README.md" ]] && continue
+            cp "$cmd_file" "$claude_dir/commands/$basename"
+            echo "   ✓ command: $basename"
+        done
+    fi
 
     # --- Sync skills ---
     for skill_file in "$AI_CORE_DIR"/skills/*/SKILL.md; do
@@ -64,22 +66,22 @@ sync_claude_code() {
     cat > "$PROJECT_ROOT/CLAUDE.md" <<'EOF'
 # Project Instructions for Claude Code
 
-This project uses `core/` framework for structured Agile/Scrum development.
+This project uses root-level framework folders for structured Agile/Scrum development.
 
 ## 🚨 CRITICAL: Read these first
 
-1. **Rules**: See `core/rules/00-global-rules.md` — **MUST follow**
-2. **Agents**: See `core/agents/` — pick correct agent for task
-3. **Skills**: See `core/skills/using-ai-core/SKILL.md` — chat-first bootstrap
-4. **Commands**: See `core/commands/` — use slash commands for workflows
-5. **Workflows**: See `core/workflows/feature-lifecycle.md`
+1. **Rules**: See `rules/00-global-rules.md` — **MUST follow**
+2. **Agents**: See `agents/` — pick correct agent for task
+3. **Skills**: See `skills/using-ai-core/SKILL.md` — chat-first bootstrap
+4. **Commands**: See `commands/` — use slash commands for workflows
+5. **Workflows**: See `workflows/feature-lifecycle.md`
 
 ## Quick reference
 
 ### User interface
 The normal user interface is the AI chat window. When the user types `/command ...`,
 `guide /command ...`, or `next TICKET-XXX`, interpret it as an AI Core workflow
-request. Do not ask the user to run `bash core/scripts/ai-core.sh` or set
+request. Do not ask the user to run `bash scripts/ai-core.sh` or set
 `AI_AGENT`; use those executable scripts internally only when helpful.
 
 ### Before any code change
@@ -100,7 +102,7 @@ DRAFT → GROOMED → READY → IN_PROGRESS → IN_REVIEW → QA → DONE
 
 ## ❌ Absolute prohibitions
 
-See `core/rules/00-global-rules.md` → G-011
+See `rules/00-global-rules.md` → G-011
 
 ## 🎭 Your current role
 
@@ -115,10 +117,10 @@ Read the agent file to understand your boundaries.
 
 ## Skill bootstrap
 
-At session start or before any workflow request, read `core/skills/using-ai-core/SKILL.md`.
-For feature discovery use `core/skills/brainstorming/SKILL.md`.
-For implementation plans use `core/skills/writing-implementation-plan/SKILL.md`.
-For completion claims use `core/skills/verification-before-done/SKILL.md`.
+At session start or before any workflow request, read `skills/using-ai-core/SKILL.md`.
+For feature discovery use `skills/brainstorming/SKILL.md`.
+For implementation plans use `skills/writing-implementation-plan/SKILL.md`.
+For completion claims use `skills/verification-before-done/SKILL.md`.
 EOF
     echo "   ✓ CLAUDE.md"
 
@@ -149,12 +151,12 @@ alwaysApply: true
 
 # Project Rules
 
-This project uses `core/` framework. Read these files for full context:
+This project uses root-level framework folders. Read these files for full context:
 
-- `core/rules/00-global-rules.md` — Hard rules (MUST follow)
-- `core/agents/` — Agent personas
-- `core/commands/` — Workflow commands
-- `core/workflows/feature-lifecycle.md` — End-to-end process
+- `rules/00-global-rules.md` — Hard rules (MUST follow)
+- `agents/` — Agent personas
+- `commands/` — Workflow commands
+- `workflows/feature-lifecycle.md` — End-to-end process
 
 ## Top 10 Rules (summary)
 
@@ -167,7 +169,7 @@ This project uses `core/` framework. Read these files for full context:
 7. **No direct push** to main/develop
 8. **No secrets** committed
 9. **No self-approval** of PRs
-10. **Follow agent boundaries** in `core/agents/<agent>.md`
+10. **Follow agent boundaries** in `agents/<agent>.md`
 
 ## Before any task
 
@@ -188,7 +190,7 @@ Users should type workflow commands in chat, for example:
 - `guide /mark-ready TICKET-001`
 - `next TICKET-001`
 
-Do not require users to type shell commands such as `bash core/scripts/ai-core.sh`
+Do not require users to type shell commands such as `bash scripts/ai-core.sh`
 or environment variables such as `AI_AGENT=...`. Shell scripts are internal tools
 for deterministic execution, validation, and CI.
 EOF
@@ -264,15 +266,15 @@ sync_windsurf() {
     cat > "$windsurf_file" <<'EOF'
 # Windsurf Project Rules
 
-This project uses core/ framework for Agile/Scrum enforcement.
+This project uses root-level framework folders for Agile/Scrum enforcement.
 
 ## Required Reading
 
 Before ANY task, read:
-1. `core/rules/00-global-rules.md` — hard rules
-2. `core/agents/` — role definitions
-3. `core/skills/using-ai-core/SKILL.md` — chat-first bootstrap
-4. `core/workflows/feature-lifecycle.md` — process
+1. `rules/00-global-rules.md` — hard rules
+2. `agents/` — role definitions
+3. `skills/using-ai-core/SKILL.md` — chat-first bootstrap
+4. `workflows/feature-lifecycle.md` — process
 
 ## Non-negotiable rules
 
@@ -284,12 +286,14 @@ EOF
     echo "" >> "$windsurf_file"
     echo "## Available commands" >> "$windsurf_file"
     echo "" >> "$windsurf_file"
-    find "$AI_CORE_DIR/commands" -name "*.md" -type f | while read -r cmd_file; do
-        local basename
-        basename=$(basename "$cmd_file" .md)
-        [[ "$basename" == "README" ]] && continue
-        echo "- /$basename" >> "$windsurf_file"
-    done
+    if [ -d "$AI_CORE_DIR/commands" ]; then
+        find "$AI_CORE_DIR/commands" -name "*.md" -type f | while read -r cmd_file; do
+            local basename
+            basename=$(basename "$cmd_file" .md)
+            [[ "$basename" == "README" ]] && continue
+            echo "- /$basename" >> "$windsurf_file"
+        done
+    fi
 
     echo "" >> "$windsurf_file"
     echo "## Available skills" >> "$windsurf_file"
@@ -297,7 +301,7 @@ EOF
     find "$AI_CORE_DIR/skills" -name "SKILL.md" -type f | while read -r skill_file; do
         local skill_name
         skill_name=$(basename "$(dirname "$skill_file")")
-        echo "- $skill_name: core/skills/$skill_name/SKILL.md" >> "$windsurf_file"
+        echo "- $skill_name: skills/$skill_name/SKILL.md" >> "$windsurf_file"
     done
 
     echo "   ✓ .windsurfrules generated"

package/{core/scripts → scripts}/validate-audit-log.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# core/scripts/validate-audit-log.sh
+# scripts/validate-audit-log.sh
 #
 # Validates append-only audit log hash chaining.
 

package/{core/scripts → scripts}/validate-docs.sh

@@ -116,7 +116,7 @@ load_docs_policy() {
     return 0
   fi
 
-  DOCS_POLICY_FILE="core/config/docs-policy.default.json"
+  DOCS_POLICY_FILE="config/docs-policy.default.json"
   DOCS_POLICY_JSON=$(jq '.' "$DOCS_POLICY_FILE")
 }
 

package/{core/scripts → scripts}/validate-permissions.sh

@@ -25,7 +25,21 @@ command_file_for() {
   local command="$1"
   local name
   name=$(printf '%s' "$command" | sed 's#^/##')
-  find core/commands -name "$name.md" -type f | head -1
+
+  if [ -d "commands" ]; then
+    find commands -name "$name.md" -type f | head -1
+    return 0
+  fi
+
+  if [ -d "skills" ]; then
+    find skills -name 'SKILL.md' -type f -print0 |
+      while IFS= read -r -d '' file; do
+        if awk -v command="/$name" '$1 == "command:" && $2 == command { found=1 } END { exit found ? 0 : 1 }' "$file"; then
+          printf '%s\n' "$file"
+          break
+        fi
+      done
+  fi
 }
 
 allowed_agents_for_command() {

package/{core/scripts → scripts}/validate-state.sh

@@ -38,7 +38,7 @@ NC='\033[0m'
 TICKETS_DIR="project/tickets"
 BUGS_DIR="project/bugs"
 BACKLOG_FILE="project/backlog/backlog.json"
-SCHEMA_FILE="core/config/ticket.schema.json"
+SCHEMA_FILE="config/ticket.schema.json"
 
 # ============================================================
 # Allowed state transitions matrix (per RULE 06)
@@ -606,6 +606,6 @@ else
   echo "════════════════════════════════════════════════════════"
   echo ""
   echo "Per RULE 06 (Approval Gates), all tickets must follow state machine."
-  echo "See: core/rules/06-approval-gates.md"
+  echo "See: rules/06-approval-gates.md"
   exit 1
 fi

package/{core/scripts → scripts}/workflow.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# core/scripts/workflow.sh
+# scripts/workflow.sh
 #
 # Executable handlers for AI Core state workflow commands.
 
@@ -159,8 +159,8 @@ transition_ticket() {
        }]' "$file" | write_json "$file"
 
   append_audit "$command" "$ticket_id" "$from_state" "$to_state" "$reason"
-  bash core/scripts/validate-state.sh "$ticket_id"
-  bash core/scripts/validate-permissions.sh
+  bash scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-permissions.sh
   log_pass "$ticket_id transitioned $from_state -> $to_state"
 }
 
@@ -277,7 +277,7 @@ EOF
     }' > "$file"
 
   append_audit "/analyze-requirements" "$ticket_id" "null" "DRAFT" "Created from executable requirement intake"
-  bash core/scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-state.sh "$ticket_id"
   log_pass "Created $ticket_id"
   log_pass "Created $spec_path"
 }
@@ -407,8 +407,8 @@ EOF
        }])' "$file" | write_json "$file"
 
   append_audit "/write-plan" "$ticket_id" "$status" "$status" "Implementation plan created"
-  bash core/scripts/validate-state.sh "$ticket_id"
-  bash core/scripts/validate-permissions.sh
+  bash scripts/validate-state.sh "$ticket_id"
+  bash scripts/validate-permissions.sh
   log_pass "Created $plan_path"
   log_pass "Linked plan from $file"
 }
@@ -490,7 +490,7 @@ cmd_release() {
   jq --arg version "$version" --arg at "$at" --arg by "$by" \
     '.version = $version
      | .created_at = $at
-     | .created_by = $by' core/templates/release/release-record-template.json > "$file"
+     | .created_by = $by' templates/release/release-record-template.json > "$file"
   log_pass "Created release record $file"
 }
 

package/{core/skills → skills}/ai-core-commands/SKILL.md

@@ -5,7 +5,7 @@ description: Interpret AI Core slash-command text in Codex. Use when the user ty
 
 # AI Core Commands
 
-Codex plugins do not expose `core/commands/*.md` as native slash-command autocomplete. This skill makes AI Core command text executable through normal chat.
+Codex plugins do not expose `commands/*.md` as native slash-command autocomplete. This skill makes AI Core command text executable through normal chat.
 
 ## Mandatory Trigger
 
@@ -34,21 +34,21 @@ next TICKET-XXX
 
 1. Log the user request first:
    ```bash
-   AI_AGENT=codex bash core/scripts/log-user-request.sh "<user request text>"
+   AI_AGENT=codex bash scripts/log-user-request.sh "<user request text>"
    ```
 
 2. Resolve command metadata:
-   - Search `core/commands/**/<command-name>.md`.
+   - Search `commands/**/<command-name>.md`.
    - Read the command file.
    - Infer `owner_agent`, `requires_agents`, args, preconditions, postconditions, hard rules, and output format.
 
 3. Load the matching agent file when present:
-   - `core/agents/<owner_agent>.md`
+   - `agents/<owner_agent>.md`
 
 4. Execute the command in chat-first mode:
    - Use deterministic scripts only when the command file or workflow requires them.
    - Do not ask the user to run shell wrappers during normal use.
-   - Preserve all hard rules from `core/rules/00-global-rules.md`.
+   - Preserve all hard rules from `rules/00-global-rules.md`.
 
 5. Report:
    - Command executed
@@ -62,19 +62,19 @@ next TICKET-XXX
 Command files are stored under:
 
 ```text
-core/commands/
+commands/
 ```
 
 The command name maps to a Markdown file by removing the leading slash:
 
 ```text
-/analyze-requirements -> core/commands/**/analyze-requirements.md
-/request-log -> core/commands/**/request-log.md
+/analyze-requirements -> commands/**/analyze-requirements.md
+/request-log -> commands/**/request-log.md
 ```
 
 If multiple files match the same command name, stop and ask for clarification.
 
-If no file matches, say the command is not defined and suggest `/request-log`, `/setup-project`, or checking `core/commands/README.md`.
+If no file matches, say the command is not defined and suggest `/request-log`, `/setup-project`, or checking `commands/README.md`.
 
 ## Strict Rules
 

package/{core/skills → skills}/development-implement-task/SKILL.md

@@ -90,8 +90,8 @@ Load `rules/07-definition-of-ready.md`. Verify the ticket passes every item. If
 │  → Read ticket JSON                             │
 │  → Read acceptance criteria                     │
 │  → Read related code (if ticket references it)  │
-│  → Read core/rules/02-code-quality.md       │
-│  → Read core/rules/05-testing-mandatory.md  │
+│  → Read rules/02-code-quality.md       │
+│  → Read rules/05-testing-mandatory.md  │
 ├─────────────────────────────────────────────────┤
 │  STEP 3: Create/checkout branch                 │
 │  → Branch name: feature/${TICKET_ID}-${slug}    │

package/{core/skills → skills}/meta-sync-platforms/SKILL.md

@@ -19,23 +19,23 @@ postconditions:
 
 # /sync-platforms
 
-> Exports `core/` source-of-truth specs to Claude Code, Cursor, and Windsurf config files.
+> Exports root-level framework source-of-truth specs to Claude Code, Cursor, and Windsurf config files.
 
 ## 🎯 Purpose
 
-Keep all supported AI tools aligned with the same agents, commands, and rules while editing only `core/` as the canonical source.
+Keep all supported AI tools aligned with the same agents, commands, and rules while editing only root-level framework folders as the canonical source.
 
 ## 🔄 Execution Flow
 
-1. Verify `core/scripts/sync-platforms.sh` exists.
-2. Run `bash core/scripts/sync-platforms.sh`.
+1. Verify `scripts/sync-platforms.sh` exists.
+2. Run `bash scripts/sync-platforms.sh`.
 3. Review generated `.claude/`, `.cursor/rules/`, `.windsurfrules`, and `CLAUDE.md`.
 4. Confirm generated files should be committed.
 5. Report created/updated files.
 
 ## 🔒 Hard Rules
 
-- Source changes MUST be made in `core/`, not generated exports.
+- Source changes MUST be made in root-level framework folders, not generated exports.
 - MUST review generated files before commit.
 - MUST rerun after changing agents, commands, or rules.
 - MUST NOT delete user custom platform config without confirmation.

package/{core/skills → skills}/meta-validate-audit-log/SKILL.md

@@ -31,7 +31,7 @@ Detect manual edits to `project/audit-log.jsonl`. Executable workflow handlers a
 /validate-audit-log
 ```
 
-The AI may call `core/scripts/validate-audit-log.sh` internally and must summarize the result.
+The AI may call `scripts/validate-audit-log.sh` internally and must summarize the result.
 
 ## Hard Rules
 

package/{core/skills → skills}/meta-validate-docs/SKILL.md

@@ -29,7 +29,7 @@ postconditions:
 
 ## Purpose
 
-Catch missing docs before review or release. In chat, use `/validate-docs`; the AI may call `core/scripts/validate-docs.sh` internally and must summarize the result.
+Catch missing docs before review or release. In chat, use `/validate-docs`; the AI may call `scripts/validate-docs.sh` internally and must summarize the result.
 
 ## Execution Flow
 

package/{core/skills → skills}/meta-validate-permissions/SKILL.md

@@ -24,7 +24,7 @@ postconditions:
 
 ## Purpose
 
-Make role boundaries mechanically enforceable by comparing `project/tickets/*.json` history entries with `core/commands/**` command ownership metadata.
+Make role boundaries mechanically enforceable by comparing `project/tickets/*.json` history entries with `commands/**` command ownership metadata.
 
 ## Chat Usage
 
@@ -38,7 +38,7 @@ Make role boundaries mechanically enforceable by comparing `project/tickets/*.js
 `state_history[].by_agent` must match the command `owner_agent` or `requires_agents`.
 
 ### RULE VP-002: Unknown commands fail
-Any `by_command` value without a matching `core/commands/**/<name>.md` file blocks validation.
+Any `by_command` value without a matching `commands/**/<name>.md` file blocks validation.
 
 ### RULE VP-003: No self-approval
 If `assignee` is recorded, the same agent cannot approve review-to-QA or DONE transitions.

package/{core/skills → skills}/meta-validate-state/SKILL.md

@@ -28,9 +28,9 @@ Catch corrupted backlog data, missing ticket references, skipped transitions, mi
 ## 🔄 Execution Flow
 
 1. Verify `jq` is installed.
-2. In chat, run `/validate-state` with optional ticket ID. The AI may call `core/scripts/validate-state.sh` internally.
+2. In chat, run `/validate-state` with optional ticket ID. The AI may call `scripts/validate-state.sh` internally.
 3. Validate `project/backlog/backlog.json` references existing tickets when validating all state.
-4. If available, run JSON schema validation against `core/config/ticket.schema.json` and `core/config/backlog.schema.json`.
+4. If available, run JSON schema validation against `config/ticket.schema.json` and `config/backlog.schema.json`.
 5. Report failures with file path, field, and recovery command.
 6. Block workflow if validation fails.
 

package/{core/skills → skills}/planning-analyze-requirements/SKILL.md

@@ -62,13 +62,13 @@ Turn free-text requirement (email, Slack, voice note) into a structured ticket w
 
 Check before starting. **ABORT** if any check fails.
 
-### 1. `core/` initialized
+### 1. Root-level framework folders initialized
 ```bash
 test -d "project/tickets" || ABORT "Run /setup-project first"
 ```
 
 ### 2. BA agent available
-Check `core/agents/business-analyst.md` exists and is enabled in config.
+Check `agents/business-analyst.md` exists and is enabled in config.
 
 ### 3. Requirement text is not empty
 If empty or < 10 chars → ABORT and ask for the actual requirement.
@@ -145,7 +145,7 @@ If empty or < 10 chars → ABORT and ask for the actual requirement.
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Write ticket JSON                                │
 │   Path: project/tickets/TICKET-XXX.json           │
-│   Schema: core/config/ticket.schema.json             │
+│   Schema: config/ticket.schema.json             │
 │   State: DRAFT                                           │
 │   created_by: "business-analyst-agent"                   │
 ├──────────────────────────────────────────────────────────┤

package/{core/skills → skills}/planning-mark-ready/SKILL.md

@@ -57,7 +57,7 @@ If any precondition fails, ABORT and keep the ticket in `GROOMED` or move to `BL
 
 ## 🔄 Execution Flow
 
-1. Load ticket JSON and `core/rules/07-definition-of-ready.md`.
+1. Load ticket JSON and `rules/07-definition-of-ready.md`.
 2. Validate INVEST criteria.
 3. Validate acceptance criteria are testable and include happy path, edge case, and error case.
 4. Validate estimation evidence from grooming.

package/{core/skills → skills}/planning-plan-refactor/SKILL.md

@@ -28,7 +28,7 @@ postconditions:
 
 ## 🎯 Purpose
 
-Plan large refactors without putting project-specific design into `core/`.
+Plan large refactors without putting project-specific design into framework source folders.
 
 ## 🔄 Execution Flow
 
@@ -36,7 +36,7 @@ Plan large refactors without putting project-specific design into `core/`.
 2. Inspect affected code areas and docs.
 3. Identify current problem, target state, constraints, and risks.
 4. Determine whether ADR is required.
-5. Create `docs/runtime/refactor/<slug>-refactor-plan.md` from `core/templates/technical/refactor-plan-template.md`.
+5. Create `docs/runtime/refactor/<slug>-refactor-plan.md` from `templates/technical/refactor-plan-template.md`.
 6. Propose ticket breakdown for `project/tickets/`.
 7. Propose backlog entries for `project/backlog/backlog.json`.
 8. Define testing, rollout, and rollback plan.
@@ -45,7 +45,7 @@ Plan large refactors without putting project-specific design into `core/`.
 ## 🔒 Hard Rules
 
 - MUST NOT modify production code during planning.
-- MUST keep plan in `docs/runtime/refactor/`, not `core/`.
+- MUST keep plan in `docs/runtime/refactor/`, not framework source folders.
 - MUST create characterization test ticket before risky behavior-preserving refactors.
 - MUST require ADR for architectural decisions.
 - MUST split work into tickets of 8 points or less.

package/{core/skills → skills}/project-setup-project/SKILL.md

@@ -29,37 +29,37 @@ postconditions:
 
 ## 🎯 Purpose
 
-Make a copied `core/` framework operational in a real repository. This command checks repo structure, updates configuration, creates state directories, syncs platform instructions, and explains next steps.
+Make copied root-level framework folders operational in a real repository. This command checks repo structure, updates configuration, creates state directories, syncs platform instructions, and explains next steps.
 
 ## 🚦 Trigger
 
-Manual after copying `core/` into a project:
+Manual after copying root-level framework folders into a project:
 
 - `/setup-project`
-- `bash core/scripts/setup-project.sh`
+- `bash scripts/setup-project.sh`
 
 ## 📋 Preconditions, STRICT
 
 1. Repository has `.git/`.
-2. `core/README.md` exists.
-3. `core/templates/project/project-config.yaml` exists.
-4. `core/templates/project/project-structure.yaml` exists.
+2. `README.md` exists.
+3. `templates/project/project-config.yaml` exists.
+4. `templates/project/project-structure.yaml` exists.
 5. User has permission to create `config/`, `project/`, `docs/project/`, `docs/runtime/`, `.claude/`, `.cursor/`, `.windsurfrules`, and `CLAUDE.md`.
 
 ## 🔄 Execution Flow
 
-1. Confirm repo root and `core/` location.
+1. Confirm repo root and framework folder locations.
 2. Create `config/` if missing.
-3. Copy `core/templates/project/project-config.yaml` to `config/project-config.yaml` if missing.
-4. Copy `core/templates/project/project-structure.yaml` to `config/project-structure.yaml` if missing.
+3. Copy `templates/project/project-config.yaml` to `config/project-config.yaml` if missing.
+4. Copy `templates/project/project-structure.yaml` to `config/project-structure.yaml` if missing.
 5. Ask for missing project fields or infer with `/detect-stack`.
 6. Create required `project/` directories: tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, prs.
 7. Create required docs namespaces: `docs/project/` for project/product requirements and `docs/runtime/` for operational AI Core documentation.
 8. Create `project/backlog/backlog.json` and `project/user-requests.jsonl` if missing.
-9. Run `bash core/scripts/setup-project.sh` when shell access is available, or perform steps 2-8 manually.
-10. Install root `scripts/` copies from canonical `core/scripts/` if they are missing.
+9. Run `bash scripts/setup-project.sh` when shell access is available, or perform steps 2-8 manually.
+10. Confirm `scripts/` contains the portable enforcement scripts.
 11. Install portable `.github/workflows/ai-core-governance.yml` if missing.
-12. Run `/sync-platforms` or `bash core/scripts/sync-platforms.sh`.
+12. Run `/sync-platforms` or `bash scripts/sync-platforms.sh`.
 13. Recommend installing hooks with `bash scripts/install-hooks.sh` if `.githooks/` exists.
 14. Run `/validate-state`.
 15. Output project readiness summary and first workflow suggestion.
@@ -69,8 +69,8 @@ Manual after copying `core/` into a project:
 ### RULE SP-001: Do not overwrite user config blindly
 If config values already exist, preserve them unless user confirms change.
 
-### RULE SP-002: Keep `core/` canonical
-Generated `.claude/`, `.cursor/`, and `.windsurfrules` files are exports. Source changes belong in `core/`.
+### RULE SP-002: Keep root-level framework folders canonical
+Generated `.claude/`, `.cursor/`, and `.windsurfrules` files are exports. Source changes belong in root-level framework folders.
 
 ### RULE SP-003: No product code changes
 Setup modifies AI runtime/config files only: `config/`, `project/`, `docs/project/`, `docs/runtime/`, generated platform config, and optional docs scaffolding. It MUST NOT modify production source code.
@@ -81,11 +81,11 @@ A project is not ready until `project/` contains directories for tickets, backlo
 ### RULE SP-004a: User request log required
 A project is not ready until `project/user-requests.jsonl` exists. Every AI-handled user request **MUST** be logged there before substantive work begins.
 
-### RULE SP-005: `core` remains framework-only
-Project-specific state and config MUST NOT be written under `core/`. Use `project/` and `config/`.
+### RULE SP-005: Framework folders remain framework-only
+Project-specific state and config MUST NOT be written under framework source folders. Use `project/` and `config/`.
 
-### RULE SP-006: `core/scripts` is canonical
-Portable enforcement scripts live under `core/scripts/`. Root `scripts/` entries are install-time copies for developer convenience.
+### RULE SP-006: `scripts/` is canonical
+Portable enforcement scripts live under `scripts/`.
 
 ## 📤 Outputs
 
@@ -100,7 +100,7 @@ Success:
 
 Failure:
 
-- Missing `core/`
+- Missing root-level framework folders
 - Not a Git repository
 - Sync failure
 - Invalid config

package/{core/skills → skills}/qa-report-bug/SKILL.md

@@ -485,7 +485,7 @@ Developer cannot fix "broken" — needs specific scenario. Example of good bug:
 | Ambiguous severity | AI suggests, human confirms |
 | SEV-1 after hours | File + page on-call immediately |
 | Reporter gave bad info | Diplomatic pushback, guide to quality |
-| Evidence file too large | Store in core, link reference |
+| Evidence file too large | Store in the project evidence area, link reference |
 
 ## 🔗 Related Commands
 

package/{core/skills → skills}/release-release/SKILL.md

@@ -65,7 +65,7 @@ Manual:
 5. Confirm QA evidence exists for every included ticket.
 6. Check open bugs and known issues.
 7. Generate changelog with ticket IDs, PRs, bug fixes, migrations, and breaking changes.
-8. Create `project/releases/vX.Y.Z.json` from `core/templates/release/release-record-template.json` with scope, approvals, risks, deploy plan, rollback plan, and timestamps.
+8. Create `project/releases/vX.Y.Z.json` from `templates/release/release-record-template.json` with scope, approvals, risks, deploy plan, rollback plan, and timestamps.
 9. Create or update release branch if configured.
 10. Tag release using `vX.Y.Z`.
 11. Trigger deployment or document manual deployment step.
@@ -93,7 +93,7 @@ Database migrations MUST include forward plan, rollback or mitigation, and backu
 Do not move an existing release tag. Create a new patch release instead.
 
 ### RULE REL-007: Release record schema required
-Every release record MUST satisfy `core/config/release.schema.json`. Missing approvals, rollback verification, QA evidence, security scan status, or known issue approval blocks release.
+Every release record MUST satisfy `config/release.schema.json`. Missing approvals, rollback verification, QA evidence, security scan status, or known issue approval blocks release.
 
 ### RULE REL-008: Post-release smoke evidence
 If a release is marked `RELEASED` and `qa.post_release_smoke_required=true`, then `qa.post_release_smoke_passed=true` and the evidence path MUST be recorded.

package/{core/skills → skills}/using-ai-core/SKILL.md

@@ -29,7 +29,7 @@ guide /mark-ready TICKET-001
 next TICKET-001
 ```
 
-Do not ask users to type `bash core/scripts/ai-core.sh` or `AI_AGENT=...` during normal use. Those are internal tools for deterministic execution and CI.
+Do not ask users to type `bash scripts/ai-core.sh` or `AI_AGENT=...` during normal use. Those are internal tools for deterministic execution and CI.
 
 ## Agent Selection
 
@@ -45,7 +45,7 @@ If command metadata and user intent conflict, explain the conflict and stop.
 - `project/` is machine-readable runtime state.
 - `docs/` is human-readable project documentation.
 - `config/` is project configuration.
-- `core/` is portable framework code.
+- Root-level framework folders are portable framework code.
 
 Do not move backlog, tickets, releases, bugs, sprints, or audit records into `docs/`. Generate human-readable summaries in `project/views/` and keep longer narrative docs in `docs/`.
 
@@ -69,4 +69,3 @@ Ask before running the next step. Do not continue automatically when the next co
 - No self-approval.
 - No DONE without fresh verification evidence.
 - No public API, setup, migration, architecture, or release-impacting change without the required docs evidence.
-