Add profile-based APCP context workflows

Author: AybarsBarut

.github/repository-metadata.yml

@@ -2,7 +2,7 @@
 # Apply these values in GitHub repository settings or with the GitHub CLI.
 
 name: Nexus-APCP
-description: "AI Project Context Protocol for context engineering, AI-assisted development, local code intelligence, AI tool compatibility, agent skills, ADRs, and token optimization."
+description: "AI Project Context Protocol for profile-based context engineering, AI-assisted development, local code intelligence, AI tool compatibility, agent skills, ADRs, and token optimization."
 homepage: "https://github.com/AybarsBarut/Nexus-APCP"
 social_preview: "assets/nexus-apcp-social-preview.svg"
 topics:

.github/workflows/validate.yml

@@ -28,7 +28,10 @@ jobs:
         run: python -m pip install --upgrade pip PyYAML
 
       - name: Check Python syntax
-        run: python -m py_compile scripts/apcp_core_files.py scripts/apcp-gather.py scripts/validate-repo.py
+        run: python -m py_compile scripts/apcp_core_files.py scripts/apcp-gather.py scripts/apcp-install.py scripts/validate-repo.py
+
+      - name: Run unit tests
+        run: python -m unittest discover -s tests
 
       - name: Check PowerShell syntax
         shell: pwsh

.gitignore

@@ -17,6 +17,8 @@ PROMPT_READY.txt
 PROMPT_READY.tmp
 PROMPT_READY*.txt
 PROMPT_READY*.tmp
+apcp-profile.json
+.apcp-profile.json
 .checkpoint
 .apcp-cache/
 .codegraph/

AGENTS.md

@@ -26,6 +26,9 @@ The public repository should remain safe to share. Real project context files, p
 | `CODEGRAPH_INTEGRATION_PROTOCOL.md` | Optional local CodeGraph-compatible code knowledge graph workflow and generated-index hygiene. |
 | `FILE_STRUCTURE_REFACTOR_PROTOCOL.md` | Safe iterative file and folder restructuring protocol for existing projects. |
 | `DEBLOAT_APPLICATION_GUIDE.md` | Lean application guidance for reducing ads, hidden tracking, heavy dependencies, optional feature load, and resource usage. |
+| `DISCOVER_ALGORITHM_DESIGN_GUIDE.md` | Optional problem-discovery and algorithm design guide for projects that need deeper exploration. |
+| `FRONTEND_APPLICATION_DESIGN_PROTOCOL.md` | Optional frontend application design protocol for UI-heavy projects. |
+| `UNIVERSAL_APPLICATION_SECURITY_PROTOCOL.md` | Optional baseline application security protocol for API, web, AI, and service projects. |
 | `AI_ASSISTANT_PROMPT_TEMPLATES.md` | Reusable prompts for common AI-assisted development scenarios. |
 | `WORKSPACE_SPECIFIC_DELIVERY_PROTOCOLS.md` | Domain-specific delivery gates and release expectations. |
 | `DOMAIN_SPECIFIC_GITIGNORE_PROTOCOLS.md` | Safe publishing patterns for different project domains. |
@@ -34,6 +37,7 @@ The public repository should remain safe to share. Real project context files, p
 | `CHANGELOG.md` | Release history and SemVer notes for public protocol-kit versions. |
 | `scripts/apcp_core_files.py` | Canonical core and install file lists used by scripts and validation. |
 | `scripts/apcp-gather.py` | Generates an AI-ready context bundle from core protocol files. |
+| `scripts/apcp-install.py` | Profile-aware installer for copying selected Nexus-APCP files into downstream projects. |
 | `scripts/validate-repo.py` | Repository integrity, metadata, and link validation script. |
 | `scripts/install-local-excludes.sh` / `scripts/install-local-excludes.ps1` | Local Git exclude installers for downstream repositories. |
 | `docs/SEO_CHECKLIST.md` | Repository SEO metadata and keyword source of truth. |
@@ -44,7 +48,8 @@ Run these from the repository root.
 
 ```bash
 python scripts/apcp-gather.py --caveman
-python -m py_compile scripts/apcp_core_files.py scripts/apcp-gather.py scripts/validate-repo.py
+python -m py_compile scripts/apcp_core_files.py scripts/apcp-gather.py scripts/apcp-install.py scripts/validate-repo.py
+python -m unittest discover -s tests
 python scripts/validate-repo.py
 ```
 

AI_MAIN.md

@@ -9,6 +9,7 @@ This file is a copy-safe starter template. After copying Nexus-APCP into a proje
 
 ## SYSTEM_INIT
 - **Protocol**: CAVEMAN optional. Activate only when requested or when `PROMPT_READY.txt` says `Mode: CAVEMAN`.
+- **Context Profile**: load `apcp-profile.json` when present. If absent, assume `core` and activate specialized protocols only when task-relevant.
 - **Quality**: production-ready, verified, no simulated work.
 - **Safety**: DRY, SOLID, secure, public/private boundary respected.
 - **Checkpoints**: mandatory validation at each gate.
@@ -65,8 +66,21 @@ This file is a copy-safe starter template. After copying Nexus-APCP into a proje
 - Preserve the public/private boundary from `AI_PROJECT_CONTEXT_PROTOCOL.md` and `DOMAIN_SPECIFIC_GITIGNORE_PROTOCOLS.md`.
 - Keep generated prompt bundles such as `PROMPT_READY.txt` out of public commits.
 - Prefer current project evidence over copied template state.
+- Treat selected profile files as active context. Treat non-selected specialized protocols as references, not standing instructions, unless the user or task explicitly invokes them.
 - If context is stale or contradictory, stop and reconcile before implementation.
 
+## RULE_PRIORITY
+
+When rules conflict, use this order:
+
+1. Current user request and explicit approvals.
+2. Security, privacy, secret-handling, and public/private boundary rules.
+3. Project-specific filled context and current task state.
+4. Selected APCP profile files and task-invoked specialized protocols.
+5. General examples, templates, and optional reference protocols.
+
+If two active rules still conflict, choose the narrower task-specific rule, explain the conflict briefly, and ask only when proceeding would create real risk.
+
 ---
 
 *Nexus-APCP: logic first, tokens last.*

AI_PROJECT_CONTEXT_PROTOCOL.md

@@ -11,6 +11,19 @@ This file is the **single source of truth** for AI coding assistants and agents
 - Changes are synchronized automatically
 - The AI takes on the role of project manager
 
+### Active Context Profile
+
+Nexus-APCP supports profile-based context loading through `apcp-profile.json`.
+Use `core` unless the project clearly needs `web`, `backend-api`, `cli`, `game`, `ai-rag`, or `full`.
+Specialized protocols outside the active profile are references, not standing instructions, unless the current user request or task explicitly invokes them.
+
+Rule priority:
+1. Current user request and explicit approvals.
+2. Security, privacy, secret-handling, and public/private boundary rules.
+3. Filled project context and current task state.
+4. Selected APCP profile files and task-invoked specialized protocols.
+5. General examples, templates, and optional reference protocols.
+
 ---
 
 ## SECTION 1: GENERAL PROJECT INFORMATION

CHANGELOG.md

@@ -7,6 +7,8 @@ Nexus-APCP follows SemVer for public protocol-kit releases. A version in `codeme
 ## [Unreleased]
 
 - Centralize the canonical APCP core file list for gather, validation, and documentation consistency.
+- Add profile-based install and context gathering with `apcp-profile.json`, `scripts/apcp-install.py`, and default narrow `core` context.
+- Add unit tests for profile selection, gather error handling, config filtering, and installer dry-run behavior.
 - Harden repository validation with syntax checks, YAML parsing, generated artifact cleanup, Markdown anchor checks, and simple leak-pattern scanning.
 - Add safer local-exclude and checkpoint workflows for downstream public repository hygiene.
 - Add optional CodeGraph-compatible local code knowledge graph guidance for semantic discovery, call tracing, impact analysis, and generated index hygiene.

CONTEXT_OPTIMIZATION.md

@@ -5,6 +5,13 @@ As a software project grows, the codebase and documentation eventually exceed th
 
 ## Modular Context Strategy
 
+### Profile Filter
+**Usage**: Before packaging context for a project.
+- **Default**: `core`, loaded from `apcp-profile.json` when present.
+- **Project profiles**: `web`, `backend-api`, `cli`, `game`, `ai-rag`, and `full`.
+- **Rule**: Use the narrowest profile that matches the project. Add files through `include` only when the current task needs them, and remove unrelated files through `exclude`.
+- **Token Impact**: prevents specialized protocols from entering the model context when they do not match the project.
+
 ### Level 1: Standard (Bootstrap Mode)
 **Usage**: When starting a new session or a new project.
 - **Files**: Full `AI_PROJECT_CONTEXT_PROTOCOL.md` + Full `TASK_PROGRESS.yaml`.