atabey 0.0.37 → 0.1.0

package/templates/docs/tech-stack.md

@@ -0,0 +1,21 @@
+# [TOOL] Project Tech Stack
+
+> Auto-generated by `atabey init`. Source of truth: `.atabey/config.json`.
+
+## Application Stack
+- **Backend Language:** Node.js (TypeScript)
+- **Frontend Framework:** Vite (React)
+- **Native / Platform Tier:** Rust or Go (mandatory for every native artifact)
+
+## Runtime & Packaging
+- **Runtime:** Node.js >= 22
+- **Package Manager:** npm workspaces (monorepo)
+
+## Governance & Orchestration (Atabey)
+- **Protocol:** Model Context Protocol (MCP)
+- **MCP Surface:** 40 strictly-typed tools
+- **Storage:** SQLite (`better-sqlite3`)
+- **Messaging:** Hermes WSS Bus (`ws`)
+- **Validation:** Zod
+- **Audit Trail:** keyed HMAC-SHA256 hash chain
+- **Sandbox:** native OS isolation (macOS `seatbelt` / POSIX `uid` drop)

package/templates/full/ATABEY_FULL.md

@@ -1,11 +1,11 @@
-# Atabey Governance Framework Enterprise
+# Atabey Local Governance Framework
 # Place in project root. This file is the single source of truth for Base Project AI Extensions.
 
 ## [ATABEY] SUPREME LAW & ZERO DEVIATION POLICY (MANDATORY)
 > Any deviation from these rules is considered a violation of "Atabey Order," and the development process is immediately HALTED.
 - [ ] **Surgical Precision:** No file editing is allowed except via `replace_text` or `patch_file`. Overwriting the entire file is forbidden.
 - [ ] **Zero Type Hole:** Using the `any` type is a disciplinary offense at the level of 'treason'.
-- [ ] **Zero Console:** Usage of `console.log` is forbidden; only `EnterpriseLogger` is used.
+- [ ] **Zero Console:** Usage of `console.log` is forbidden; only structured `logger` is used.
 - [ ] **Phase Discipline:** Phases cannot be skipped. No transition to the next step until success criteria are met.
 - [ ] **Contract First:** Code cannot be written if the contract signature (`contract_hash`) is broken.
 
@@ -64,7 +64,7 @@ This file (`./ATABEY.md`) and the `.atabey/knowledge/` folder represent the "Sup
 6. **Check `docs/` Folder:** Verify the existence of the `docs/` folder (located at the root directory of the project).
 7. **Absorb Context:** Read `docs/README.md`. If it is missing, check if the architecture folder exists.
 8. **Demand Context:** If the root `docs/` folder does not exist, ask the user for project context and target audience information before writing any code.
-9. **Respect Boundaries:** Always distinguish between the user's project code and the Agent Atabey framework internals. Read `.atabey/knowledge/framework_vs_user_project_boundary.md` if unsure. Never mix the two.
+9. **Respect Boundaries:** Always distinguish between the user's project code and the Atabey framework internals. Read `.atabey/knowledge/framework_vs_user_project_boundary.md` if unsure. Never mix the two.
 10. **Automatic @manager Mode:** You are ALWAYS operating as `@manager`. You do NOT need to be called with `@manager` — this role is your default identity. You analyze, delegate, and orchestrate on EVERY turn without exception.
 
 **NEVER SKIP THIS STEP.** Do not assume context; read first, then act as @manager.
@@ -73,10 +73,10 @@ This file (`./ATABEY.md`) and the `.atabey/knowledge/` folder represent the "Sup
 
 ## CORE PRINCIPLES
 
-- **Permanent @manager Identity (Enterprise Standard):** The AI assistant is ALWAYS the `@manager` by default — on every turn, every message, without exception. The user does NOT need to type `@manager` to trigger this role. Explicitly typing a different agent (e.g. `@backend`, `@frontend`, `@analyst`) does NOT bypass @manager. All requests must still be processed by @manager first.
-- **Manager MANDATORY Orchestration (Enterprise Project Rule):** Every user request — regardless of how it is phrased or which agent is directly addressed — MUST first be received, analyzed, and orchestrated by the `@manager` agent. The `@manager` is responsible for structured delegation via the `send_agent_message` tool and CLI `@` mentions.
+- **Permanent @manager Identity (Local Control Standard):** The AI assistant is ALWAYS the `@manager` by default — on every turn, every message, without exception. The user does NOT need to type `@manager` to trigger this role. Explicitly typing a different agent (e.g. `@backend`, `@frontend`, `@analyst`) does NOT bypass @manager. All requests must still be processed by @manager first.
+- **Manager MANDATORY Orchestration (Local Control Standard):** Every user request — regardless of how it is phrased or which agent is directly addressed — MUST first be received, analyzed, and orchestrated by the `@manager` agent. The `@manager` is responsible for structured delegation via the `send_agent_message` tool and CLI `@` mentions.
 - **CLI @-Mentions:** The CLI supports direct delegation via `atabey @agent "task"`. This bypasses manual JSON creation and follows the Hermes protocol.
-- **Enterprise CRUD & Admin Governance (Enterprise Standard):** All high-risk administrative operations (user/permission management, bulk delete/purge, system config changes, audit log access, critical integrations, PII export, production schema changes, etc.) are strictly under @manager control. Specialist agents (@backend, @frontend, etc.) **must refuse** and immediately redirect such requests to @manager. Unauthorized execution is recorded as "Rule Violation - Unauthorized Administrative Action". Full list and rules are defined in `.atabey/knowledge/crud-governance.md` → "Corporate CRUD and Administrative Operation Governance".
+- **Local CRUD & Admin Governance (Governance Standard):** All high-risk administrative operations (user/permission management, bulk delete/purge, system config changes, audit log access, critical integrations, PII export, production schema changes, etc.) are strictly under @manager control. Specialist agents (@backend, @frontend, etc.) **must refuse** and immediately redirect such requests to @manager. Unauthorized execution is recorded as "Rule Violation - Unauthorized Administrative Action". Full list and rules are defined in `.atabey/knowledge/crud-governance.md` → "Corporate CRUD and Administrative Operation Governance".
 - **Zero-Request Logging Policy:** Agents MUST log every action and update `PROJECT_MEMORY.md` automatically at the end of every turn, without waiting for a user directive. This is the "Operating Mode" of the framework.
 - **Immediate Memory Sync:** Every state change, decision, or improved capability must be reflected in the memory files immediately.
 - **Zero Temporary Storage & Single Source of Truth:** Storing, caching, or writing project details, logs, tasks, files, or agent planning documents (including implementation plans, scratch scripts, or intermediate tasks) in the operating system's temporary directory (`/tmp`, `/var/tmp`, `temp`, etc.) is strictly forbidden. All planning, state, tasks, and memory MUST be stored inside the designated persistent framework directory (e.g., `.atabey/` or `.agents/`) or the project workspace. This ensures 100% state persistence and context recovery upon session restarts.
@@ -97,10 +97,10 @@ This file (`./ATABEY.md`) and the `.atabey/knowledge/` folder represent the "Sup
 - **Framework vs User Project Boundary (Critical Rule):**
   When working on the user's own application, agents **must never** suggest, create, or modify files inside the framework's own source code (`node_modules/atabey-mcp/src/`, `node_modules/atabey/src/`, `.atabey/agents/`, etc.).
   All development must happen exclusively inside the user's project structure (`apps/backend/src/`, `apps/web/src/`, `src/`, etc.).
-  The only exception is when the **explicit goal** of the session is to improve or extend the Agent Atabey framework itself.
+  The only exception is when the **explicit goal** of the session is to improve or extend the Atabey framework itself.
   Violating this boundary causes confusion, broken setups, and is considered a serious rule violation. @manager is responsible for immediately correcting any agent that crosses this line.
 
-- **Documentation Ownership Rule (Enterprise Standard — Zero Tolerance):**
+- **Documentation Ownership Rule (Governance Standard — Zero Tolerance):**
   Agents are **mandatory** to write all documentation they produce for the user's project (architectural decisions, patterns, implementation details, toaster/approval flow documents, research findings, etc.) **exclusively into the user's own `docs/` folder**.
   These documents must **never** be written into `.atabey/knowledge/`, `.atabey/agents/`, or any framework folder.
   Violation is considered a serious rule breach and is corrected by @manager.
@@ -152,7 +152,7 @@ Every agent must use the **Mandatory Output Flow** defined in their specific `.m
 ## ABSOLUTE DON'TS — APPLIES TO EVERY RESPONSE
 
 - **`any` Type is Forbidden:** The use of `any` is strictly forbidden in TypeScript projects.
-- **`console.log` is Forbidden:** `console.log` cannot be present in production code. Use `EnterpriseLogger` (from `src/shared/logger.ts`) instead.
+- **`console.log` is Forbidden:** `console.log` cannot be present in production code. Use structured `logger` (from `src/shared/logger.ts`) instead.
 - **Mock Data is Forbidden:** The use of fake (mock) data or placeholders is strictly forbidden. Every line of code must connect to a real endpoint or a typed contract. (Exception: Controlled mock usage is allowed for external 3rd party services like Stripe, Twilio).
 - **File Ownership Violation:** Making unauthorized changes in files outside your scope is forbidden.
 - **Security Rule Violation:** Violating security protocols is strictly forbidden.
@@ -288,7 +288,6 @@ Agent completes task → @quality reviews → PASS → Task done + Memory update
 ### 4. Approval Chain
 - All task completions go through `@quality` by default
 - High-risk tasks (Risk Engine score ≥ 60) additionally require human approval via `atabey approve <traceId>` before `@quality` review
-- The `ApprovalCenter` in the Dashboard visualizes pending approvals
 
 ---
 
@@ -387,26 +386,22 @@ node node_modules/atabey-mcp/dist/atabey-mcp/src/mcp/index.js
 
 ---
 
-## [DASHBOARD] WEB CONTROL PANEL
+## [MCP] HEADLESS LOCAL CONTROL PLANE
 
-The Dashboard is a web-based visual control plane powered by Vite + React.
+Atabey operates as a headless Local AI Control Plane via MCP (Model Context Protocol).
 
-### 1. Access
+### 1. Startup & Status
 ```bash
-atabey dashboard              # Default port: 5858
-atabey dashboard 4200         # Custom port
+npx atabey mcp start          # Start headless MCP server (stdio / sse)
+atabey status                 # Inspect agent statuses and token costs
+atabey check                  # System health check
 ```
 
-### 2. Dashboard Features
-- **AgentMonitor:** Real-time agent statuses, phases, and trace IDs
-- **ApprovalCenter:** Pending human approvals with accept/reject actions
-- **CompliancePanel:** Compliance check results and reports
-- **HermesBrokerView:** Message queue contents and agent communication flow
-
-### 3. Dashboard Stack
-- **Frontend:** Vite + React + TypeScript
-- **API:** `useApi` and `useSSE` hooks for real-time data
-- **Styling:** CSS with SharedStyles component
+### 2. Core Governance Capabilities
+- **Agent Governance:** Strict tool access matrix per agent role
+- **Approval Flow:** Human-in-the-loop approvals via `atabey hitl answer` / `approve_operation`
+- **Memory & Integrity:** Project state persistence in `.atabey/` with cryptographic audit chain
+- **Hermes Broker:** Inter-agent messaging and task execution tracing
 
 ---
 
@@ -484,34 +479,27 @@ Integration tests must use a real database (`better-sqlite3` in-memory) or servi
 
 ---
 
-## DASHBOARD ARCHITECTURE
+## SYSTEM ARCHITECTURE
 
 ```
-                    +---------------------------+
-                    |   Vite + React Dashboard  |
-                    |   (src/dashboard/)        |
-                    +------------+--------------+
-                                 |
-                    +------------+--------------+
-                    |   Hermes API (useApi)     |
-                    |   SSE Events (useSSE)     |
-                    +------------+--------------+
-                                 |
-        +------------------------+------------------------+
-        |                        |                        |
-+-------+--------+     +---------+-------+     +----------+-------+
-| AgentMonitor    |     | ApprovalCenter   |     | CompliancePanel  |
-| Real-time       |     | Pending approvals|     | Check results   |
-| agent status    |     | Accept/Reject    |     | Reports         |
-+-----------------+     +-----------------+     +------------------+
-
-+--------------------------+
-| HermesBrokerView         |
-| Message queue contents   |
-| Agent comm flow          |
-+--------------------------+
+[Host AI Tool (Claude Code, Gemini CLI, Cursor, Windsurf)]
+                           │
+                 (stdio / MCP SSE)
+                           ▼
+             ┌───────────────────────────┐
+             │     Atabey MCP Server     │
+             │   (PolicyGate + Matrix)   │
+             └─────────────┬─────────────┘
+                           │
+         ┌─────────────────┼─────────────────┐
+         ▼                 ▼                 ▼
+   ┌───────────┐     ┌───────────┐     ┌───────────┐
+   │ Memory &  │     │ Sandbox   │     │ Cryptographic│
+   │ State     │     │ Runtime   │     │ Audit Chain  │
+   │ (.atabey) │     │ (FS/Shell)│     │ (HMAC-SHA256)│
+   └───────────┘     └───────────┘     └───────────┘
 ```
 
 ---
 
-Developed by **Yusuf BEKAR** | [Enterprise Inquiries](mailto:ybekar@msn.com)
+Developed by **Yusuf BEKAR** | [Inquiries](mailto:ybekar@msn.com)

package/templates/prompts/security-audit-recipe.md

@@ -1,6 +1,6 @@
 # [SECURITY] Engineering Recipe: Advanced Security Audit
 
-This recipe governs the @security agent's protocol for identifying and mitigating vulnerabilities within the Agent Atabey framework.
+This recipe governs the @security agent's protocol for identifying and mitigating vulnerabilities within the Atabey framework.
 
 ## 🏁 Phase 1: Automated Reconnaissance
 1.  **Secret Scan:** Run `grep_search` for keywords: `apiKey`, `secret`, `password`, `token`, `private_key`.

package/templates/standards/architecture-standards.md

@@ -1,6 +1,6 @@
 # 📐 Corporate Architecture Standards (AL Framework)
 
-This project is developed in accordance with the "Architectural Order" (Architectural Order) rules defined by Agent Atabey.
+This project is developed in accordance with the "Architectural Order" (Architectural Order) rules defined by Atabey.
 
 ## 1. Directory Structure (Monorepo Standard)
 - `apps/backend/`: Business logic, API, and database layers.
@@ -9,9 +9,11 @@ This project is developed in accordance with the "Architectural Order" (Architec
 
 ## 2. Layered Architecture
 All business logic must follow this hierarchy:
-1. **Routes/Controllers:** API entry points and request validation.
-2. **Services:** Where business logic is coordinated.
-3. **Repositories/Models:** Database access and raw data mutations.
+1. **Routes:** API endpoint routing, rate limiting, and middleware registration.
+2. **Controllers:** Request validation (Zod/class-validator), DTO parsing, and HTTP status handling.
+3. **Services:** Core business logic orchestration, domain rules, and background job dispatching.
+4. **Repositories/Models:** Database access, schema models, and transactional mutations.
+5. **Job Workers:** Asynchronous background processing backed by database queue persistence.
 
 ## 3. Type Safety and Contracts
 - The hash in the `contract.version.json` file must always match the active code.

package/templates/standards/crud-governance.md

@@ -1,6 +1,6 @@
 # [GOV] Corporate CRUD and Governance Standards
 
-This document defines the strict rules applicable to data mutation and administrative operations in projects managed by the Agent Atabey AL.
+This document defines the strict rules applicable to data mutation and administrative operations in projects managed by the Atabey AL.
 
 ## 1. High-Risk Operations
 The following operations are considered "High-Risk" and cannot be performed autonomously by specialist agents (@backend, @database, etc.):

package/templates/standards/deployment-standards.md

@@ -1,6 +1,6 @@
 # [START] Deployment and Release Standards
 
-This document outlines the protocols for deploying, updating, and rolling back services managed by Agent Atabey.
+This document outlines the protocols for deploying, updating, and rolling back services managed by Atabey.
 
 ## 1. Release Strategy
 - **Version Control:** All releases must follow Semantic Versioning (SemVer) and be tagged in Git with the format `vX.Y.Z`.

package/templates/standards/enterprise-systems-standards.md

@@ -14,10 +14,14 @@
 - **Lock Minimization:** Avoid `ALTER TABLE` operations that acquire exclusive table locks in production; use concurrent indexing where supported.
 
 ## 3. Background Jobs & Job Queues
+- **Mandatory Database Persistence:** All background jobs, asynchronous queues, and workers MUST persist their lifecycle in the database (e.g., `jobs` / `background_tasks` table). Volatile, in-memory-only queues are strictly prohibited for business workflows.
+- **Transactional Enqueueing:** Enqueueing jobs must be committed within the same database transaction as the business operation to eliminate dual-write hazards.
+- **Status State Machine:** Jobs must transition through explicit database statuses: `PENDING` -> `PROCESSING` -> `COMPLETED` / `FAILED` / `DEAD_LETTER`.
 - **Idempotency:** All job handlers must be idempotent. Use `idempotency_key` or message deduplication hashes.
-- **Retry & Dead-Letter Queues (DLQ):** Failed jobs must use exponential backoff with jitter (max 5 retries) before being routed to a dead-letter queue.
+- **Retry & Dead-Letter Queues (DLQ):** Failed jobs must record attempt count, last error trace, and use exponential backoff with jitter (max 5 retries) before being routed to a dead-letter queue.
 - **Graceful Shutdown:** Workers must listen to `SIGTERM` / `SIGINT` signals, stop accepting new jobs, and allow in-flight tasks up to 30 seconds to finish.
 
+
 ## 4. Caching & Cache Invalidation
 - **Cache-Aside Pattern:** Query cache first; on miss, query database, populate cache with TTL, and return.
 - **Strict TTLs:** Never set infinite cache lifespans. Default TTL: 5 minutes for dynamic entities, 1 hour for static reference data.

package/templates/standards/eslint-standards.md

@@ -0,0 +1,10 @@
+# [ATABEY] Atabey — ESLint Standards
+
+This document outlines the strict ESLint coding standards for Atabey projects.
+
+## 📏 Core Rules
+- **Indentation:** 4 spaces (strict).
+- **Quotes:** Double quotes (`"`) for strings.
+- **Semicolons:** Always terminate statements with a semicolon (`;`).
+- **No Explicit Any:** Avoid using `any`. Use strongly typed interfaces, generics, or `unknown` with type assertions.
+- **Unused Variables:** Warning on unused variables unless prefixed with an underscore (`_`).

package/templates/standards/frontend-standards.md

@@ -1,12 +1,12 @@
 # 🎨 Corporate Frontend and Responsive Standards
 
-This document defines the UI/UX standards for projects managed by Agent Atabey. All interfaces must comply with "Mobile-First", "Fluid Responsive", and "Cross-Device Adaptive" principles.
+This document defines the UI/UX standards for projects managed by Atabey. All interfaces must comply with "Mobile-First", "Fluid Responsive", and "Cross-Device Adaptive" principles.
 
 ## 1. Zero UI Library Policy (Supreme Mandate)
 - **NO Third-Party UI Frameworks:** Usage of `@chakra-ui`, `mui`, `@shadcn`, `antd`, or similar pre-built component libraries is **STRICTLY FORBIDDEN**.
 - **Atomic Manual Construction:** Every UI component (Button, Modal, Input, etc.) must be built manually from scratch using atomic CSS principles.
 - **Styling Engine:** All styles must be written with type-safe **Panda CSS** or structured **Tailwind CSS**.
-- **Reasoning:** Pre-built libraries introduce massive bloat, difficult-to-override styles, and dependency lock-in. Agent Atabey enforces pure, lightweight, and 100% customizable UI code.
+- **Reasoning:** Pre-built libraries introduce massive bloat, difficult-to-override styles, and dependency lock-in. Atabey enforces pure, lightweight, and 100% customizable UI code.
 
 ## 2. Design System: Panda CSS & Tailwind Integration
 - **Token Usage:** Colors, spacing, and font sizes must be managed via the `token()` function or standard CSS variables.

package/templates/standards/governance-standards.md

@@ -1,6 +1,6 @@
-# [ATABEY] Agent Atabey — Governance & Order Standards
+# [ATABEY] Atabey — Governance & Order Standards
 
-This document defines the supreme governance mandates of the Agent Atabey framework.
+This document defines the supreme governance mandates of the Atabey framework.
 All agents **must** internalize these rules before executing any task.
 
 ---

package/templates/standards/i18n-standards.md

@@ -1,6 +1,6 @@
 # 🌐 Corporate Multi-Language (i18n) Standards
 
-This document defines the localization, internationalization, and multi-language management rules for projects managed by Agent Atabey.
+This document defines the localization, internationalization, and multi-language management rules for projects managed by Atabey.
 
 ## 1. Centralized Management
 - **Hardcoded Forbidden:** No text visible to the user shall be written directly into the code (JSX/HTML/TS).

package/templates/standards/logging-and-secrets.md

@@ -1,6 +1,6 @@
 # 🪵 Corporate Logging and Secret Management (.env) Standards
 
-This document defines the logging discipline and sensitive data (secret) management rules for projects managed by the Agent Atabey AL.
+This document defines the logging discipline and sensitive data (secret) management rules for projects managed by the Atabey AL.
 
 ## 1. Logging Discipline (Zero Console Policy)
 - **console.log Forbidden:** The use of `console.log`, `console.warn`, or `console.error` in production code is strictly forbidden.

package/templates/standards/native-standards.md

@@ -1,7 +1,7 @@
 # [NATIVE] Corporate Native / Platform-Layer Standards (Rust / Go)
 
 This document defines the mandatory language, safety, and FFI rules for the
-native / platform tier of any project governed by Agent Atabey.
+native / platform tier of any project governed by Atabey.
 
 > **Supreme rule:** The native/platform layer is written in **Rust (preferred)**
 > or **Go**. TypeScript/JavaScript is FORBIDDEN for this tier. Business logic

package/templates/standards/quality-standards.md

@@ -1,6 +1,6 @@
 # ⚖️ Corporate Code Quality and Discipline (Linting & Standards)
 
-This document defines the technical discipline rules that all code produced by the Agent Atabey AL must comply with. The goal is zero errors, maximum readability, and sustainability.
+This document defines the technical discipline rules that all code produced by the Atabey AL must comply with. The goal is zero errors, maximum readability, and sustainability.
 
 ## 1. TypeScript Discipline
 - **Strict Mode:** `strict: true` is mandatory in all projects.

package/templates/standards/security-audit-standards.md

@@ -1,6 +1,6 @@
 # [SECURITY] Security Audit Standards
 
-This document defines the security audit procedures required for all Agent Atabey-managed projects to ensure a "Defense-in-Depth" posture, aligned with OWASP ASVS and the OWASP Top 10.
+This document defines the security audit procedures required for all Atabey-managed projects to ensure a "Defense-in-Depth" posture, aligned with OWASP ASVS and the OWASP Top 10.
 
 ## 1. Automated Vulnerability Scanning
 - **Dependency Audit:** All projects must execute `npm audit` within the CI/CD pipeline. Any high/critical vulnerability must block deployment.

package/templates/standards/security-standards.md

@@ -1,6 +1,6 @@
 # [SECURITY] Corporate Security and Data Protection Standards
 
-This document defines the security protocols and data protection standards for projects managed by Agent Atabey.
+This document defines the security protocols and data protection standards for projects managed by Atabey.
 
 ## 1. Database Security (RLS)
 - **Row Level Security (RLS):** All user data must be protected with RLS policies. A user cannot access another user's data except through a permission protocol approved by `@manager`.

package/templates/standards/testing-standards.md

@@ -1,6 +1,6 @@
 # [SKILL] Corporate Testing Standards
 
-This document defines the testing discipline and scope rules for projects managed by Agent Atabey. Code quality must be ensured with automated tests.
+This document defines the testing discipline and scope rules for projects managed by Atabey. Code quality must be ensured with automated tests.
 
 ## 1. Test Pyramid and Strategy
 - **Unit Tests:** Written for the smallest parts of business logic. Must be fast and isolated.

package/templates/standards/token-economy.md

@@ -0,0 +1,27 @@
+# 🪙 Token Economy & Context Management Standards
+
+This document defines the strict context management and token cost optimization rules for Atabey projects. All agents must follow these mandates to minimize LLM usage costs and prevent context drift.
+
+## 1. Search Before Reading (Mandatory)
+* **Rule:** Never execute a full directory listing (`list_dir`) recursively or read an entire file (`read_file`) without searching first.
+* **Method:** Use `grep_search` to find the exact line number of interest. Then, read only the surrounding lines (e.g. ±20 lines) using `read_file` with `StartLine` and `EndLine`.
+* **Cost Impact:** Prevents thousands of unnecessary input tokens from being loaded into context.
+
+## 2. Surgical Modifications
+* **Rule:** Do not write or replace whole files unless they are very small (<50 lines).
+* **Method:** Use targeted text replacement tools (`replace_text`, `patch_file`, `replace_file_content`, `multi_replace_file_content`) to apply edits to specific lines only.
+* **Cost Impact:** Reduces output token generation by up to 95%, keeping LLM responses fast and cost-effective.
+
+## 3. Output Conciseness
+* **Rule:** Keep explanations and logs to the absolute minimum required.
+* **Method:** Do not output verbose comments, intermediate thinking logs, or redundant progress messages. Avoid repeating what the code does; explain only the "why" if non-obvious.
+* **Cost Impact:** Saves output tokens in CLI streams and communication queues.
+
+## 4. Context Compaction & Memory Pruning
+* **Rule:** Do not carry the entire history of the development session.
+* **Method:** Before initiating a task, retrieve only the active state via `get_memory_insights` or by reading `PROJECT_MEMORY.md`. Archive completed tasks and older logs in `.atabey/memory/archive/`.
+* **Cost Impact:** Keeps the prompt context window clean and prevents performance degradation due to long-context attention dilution.
+
+## 5. No Blind Coding & Stopping Gates
+* **Rule:** Halt execution and ask the user for clarification if a task requires reading more than 5 large files without producing a clear search match.
+* **Method:** Do not guess the structure or keep querying the filesystem repeatedly. Report the block to `@manager` and wait.

package/dist/atabey/src/cli/commands/init/create-agent.d.ts

@@ -1,4 +0,0 @@
-/**
- * Plugin SDK: Creates a new custom agent template.
- */
-export declare function createAgentCommand(name: string): Promise<void>;

package/dist/atabey/src/cli/commands/init/create-agent.js

@@ -1,59 +0,0 @@
-import fs from "fs";
-import path from "path";
-import { writeTextFile } from "../../../shared/fs.js";
-import { UI } from "../../utils/ui.js";
-/**
- * Plugin SDK: Creates a new custom agent template.
- */
-export async function createAgentCommand(name) {
-    const projectRoot = process.cwd();
-    const agentsDir = path.join(projectRoot, "src/modules/agents/registry");
-    if (!fs.existsSync(agentsDir)) {
-        UI.error("Agent registry directory not found. Please ensure you are in an Atabey development environment.");
-        return;
-    }
-    const filePath = path.join(agentsDir, `${name}.ts`);
-    if (fs.existsSync(filePath)) {
-        UI.error(`Agent '${name}' already exists.`);
-        return;
-    }
-    const template = `import { AgentDefinition } from "../types.js";
-
-const STATE_MACHINE = "../schema/agent-lifecycle-schema.json" as const;
-
-export const ${name}: AgentDefinition = {
-    name: "${name}",
-    displayName: "${name.charAt(0).toUpperCase() + name.slice(1)} Specialist",
-    role: "Custom Specialty",
-    description: "Automatically generated custom agent for specific project needs.",
-    capability: 7,
-    tier: "core",
-    tags: ["custom"],
-    stateMachine: STATE_MACHINE,
-    tools: [
-        "read_file",
-        "write_file",
-        "replace_text",
-        "grep_search",
-        "send_agent_message",
-    ],
-    instructions: {
-        identity: "${name.toUpperCase()} Domain Expert",
-        mission: "Execute tasks related to ${name} with high precision and following Atabey standards.",
-        chainOfThought: "1. Analyze Task\\n2. Plan Steps\\n3. Execute\\n4. Verify",
-        rules: [
-            "Always maintain type safety.",
-            "Log all critical actions.",
-        ],
-        knowledgeFiles: [],
-    },
-    specialties: {
-        ${name}: 10,
-    },
-};
-`;
-    writeTextFile(filePath, template);
-    UI.success(`[OK] New agent '${name}' created at src/modules/agents/registry/${name}.ts`);
-    UI.warning("[INFO] Don't forget to register the agent in src/modules/agents/definitions.ts");
-}
-//# sourceMappingURL=create-agent.js.map

package/dist/atabey/src/cli/commands/init/create-agent.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"create-agent.js","sourceRoot":"","sources":["../../../../../../src/cli/commands/init/create-agent.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,IAAI,CAAC;AACpB,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,aAAa,EAAE,MAAM,uBAAuB,CAAC;AACtD,OAAO,EAAE,EAAE,EAAE,MAAM,mBAAmB,CAAC;AAEvC;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,kBAAkB,CAAC,IAAY;IACjD,MAAM,WAAW,GAAG,OAAO,CAAC,GAAG,EAAE,CAAC;IAClC,MAAM,SAAS,GAAG,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,6BAA6B,CAAC,CAAC;IAExE,IAAI,CAAC,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC5B,EAAE,CAAC,KAAK,CAAC,iGAAiG,CAAC,CAAC;QAC5G,OAAO;IACX,CAAC;IAED,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,GAAG,IAAI,KAAK,CAAC,CAAC;IACpD,IAAI,EAAE,CAAC,UAAU,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC1B,EAAE,CAAC,KAAK,CAAC,UAAU,IAAI,mBAAmB,CAAC,CAAC;QAC5C,OAAO;IACX,CAAC;IAED,MAAM,QAAQ,GAAG;;;;eAIN,IAAI;aACN,IAAI;oBACG,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC;;;;;;;;;;;;;;;qBAe3C,IAAI,CAAC,WAAW,EAAE;6CACM,IAAI;;;;;;;;;UASvC,IAAI;;;CAGb,CAAC;IAEE,aAAa,CAAC,QAAQ,EAAE,QAAQ,CAAC,CAAC;IAClC,EAAE,CAAC,OAAO,CAAC,mBAAmB,IAAI,4CAA4C,IAAI,KAAK,CAAC,CAAC;IACzF,EAAE,CAAC,OAAO,CAAC,gFAAgF,CAAC,CAAC;AACjG,CAAC"}