agent-enderun 0.7.2 → 0.8.0

package/.enderun/knowledge/corporate-governance/manager-first-30-days-guide.md

@@ -0,0 +1,112 @@
+# First 30 Days Corporate Project Management Guide (@manager)
+
+**Purpose**: A practical playbook for @manager covering the critical first 30 days of any new corporate/enterprise project. It combines the Scaffolding SOP, checklists, and briefings into a day-by-day and week-by-week operating rhythm.
+
+---
+
+## Week 0 – Project Initiation (Days 1–3)
+
+### Day 1 – Governance Baseline
+- Deliver the **Governance Baseline Briefing** (use `governance-baseline-briefing-template.md`)
+- Walk the user through the **Corporate Project Kickoff Checklist**
+- Get explicit acknowledgment of the standards
+- Record the decision in `PROJECT_MEMORY.md`
+
+### Day 2 – Team Alignment
+- Brief all active agents using `corporate-project-scaffolding-sop.md`
+- Assign initial responsibilities:
+  - @backend: Type foundation
+  - @frontend: Type copies + modal skeleton
+  - @analyst: Contract verification process
+- Create the first Architecture Decision Record (ADR) for governance baseline
+
+### Day 3 – Foundation Kickoff
+- Officially start **Phase 1** (Contract Foundation)
+- Set up the first Hermes channels and trace ID convention
+
+---
+
+## Week 1 – Foundation Layer
+
+**Primary Focus**: Contracts before code.
+
+**Key Activities**:
+- Ensure `branded-types-law.md` and core identifiers are implemented
+- `ManagerApproval` and `HighRiskActionPayload` are defined
+- `contract.version.json` is initialized
+- @frontend has matching type copies
+- First version of `domain-error-handling-standard.md` is in place
+
+**@manager Checkpoints** (end of Week 1):
+- [ ] All Phase 1 items from Kickoff Checklist completed
+- [ ] User has seen the type foundation
+- [ ] No feature implementation has started yet
+
+---
+
+## Week 2 – High-Risk Infrastructure
+
+**Primary Focus**: Build the protection layer before any privileged features.
+
+**Key Activities**:
+- @backend designs high-risk validation logic
+- @frontend builds `HighRiskSecurityModal` + Hermes briefing hook
+- Audit logging strategy is defined
+- Reference: `high-risk-action-approval-flow-simulation.md`
+
+**@manager Checkpoints** (end of Week 2):
+- [ ] High-risk endpoint pattern approved
+- [ ] Security modal + Hermes flow reviewed
+- [ ] Audit logging approach signed off
+
+---
+
+## Week 3 – First Real Features (Under Strict Governance)
+
+Only after Weeks 1–2 are complete:
+
+- Begin implementing the first non-privileged features using proper contracts and typed errors
+- First privileged feature may only start after infrastructure from Week 2 is approved
+- Use `backend-high-risk-endpoint-guide.md` and `frontend-high-risk-modal-guide.md` as implementation references
+
+---
+
+## Week 4 – Reinforcement & Early Habits
+
+**Focus**: Make governance second nature.
+
+**Activities**:
+- Run the first **Contract Drift** simulation exercise with the team (`contract-drift-detection-simulation.md`)
+- Review the first audit logs of any privileged actions
+- Conduct a mid-project governance retrospective
+- Update `PROJECT_MEMORY.md` with lessons learned
+
+---
+
+## Ongoing Rhythm (After Day 30)
+
+- Every new feature involving users, roles, permissions, or configuration → Re-read relevant governance files
+- Every contract change → @analyst verification + Hermes notification
+- Every high-risk action in production → Review the approval + audit trail
+- Monthly: Light governance health check using the Kickoff Checklist as a template
+
+---
+
+## Anti-Patterns in the First 30 Days
+
+- Starting feature coding before governance baseline is acknowledged
+- Promising “we’ll add controls later”
+- Letting @backend or @frontend implement high-risk logic without @manager approval of the pattern
+- Skipping documentation of governance decisions
+
+---
+
+## Reference Documents (Read in Order)
+
+1. `corporate-project-scaffolding-sop.md`
+2. `corporate-project-kickoff-checklist.md`
+3. `governance-baseline-briefing-template.md`
+4. `manager-first-three-briefings.md`
+5. `corporate-governance-playbook.md`
+
+This 30-day guide replaces ad-hoc project starts with a disciplined, repeatable process.

package/.enderun/knowledge/corporate-governance/manager-first-three-briefings.md

@@ -0,0 +1,79 @@
+# @manager – First Three Critical Briefings (Templates)
+
+This document provides ready-to-adapt briefing content that @manager should deliver in the early stages of any corporate/enterprise project.
+
+---
+
+## Briefing 1: Governance Baseline (Day 0 / Project Kickoff)
+
+**Audience:** User + all active agents
+
+**Key Message:**
+
+Before we write a single line of feature code, we must lock in the governance foundation.
+
+We will follow these non-negotiable standards:
+- Branded Types for every identifier
+- High-risk actions protected by explicit `managerApproval` + Hermes flow
+- Contract-first development
+- Proper audit logging for all privileged operations
+- Typed Domain Errors instead of generic exceptions
+
+These rules exist to protect the project from technical debt, security holes, and audit failures at scale.
+
+I will personally enforce these standards in every briefing and delegation. If we encounter pressure to “skip governance for speed”, we will slow down instead.
+
+Do you accept these terms as the operating rules for this project?
+
+---
+
+## Briefing 2: Contract & Type Foundation (After User Accepts Governance)
+
+**Audience:** @backend + @frontend + @analyst
+
+**Key Message:**
+
+We will now establish the single source of truth for all types.
+
+1. Create `apps/backend/src/types` with:
+   - Branded type utility
+   - Core identifiers (UserID, RoleID, ApprovalID, etc.)
+   - `ManagerApproval` and `HighRiskActionPayload`
+   - Initial domain entities and API contracts
+
+2. Initialize `contract.version.json`.
+
+3. @frontend will immediately create matching type copies.
+
+4. No routes, no components, and no database work may begin until this foundation is approved by me.
+
+@analyst will be responsible for detecting any future contract drift.
+
+---
+
+## Briefing 3: High-Risk Infrastructure (Before Any Privileged Feature)
+
+**Audience:** @backend + @frontend
+
+**Key Message:**
+
+If this project will contain user/role management, configuration changes, or any privileged operations, we must build the governance infrastructure **before** implementing those features.
+
+Required deliverables:
+
+**@backend:**
+- High-risk endpoint validation logic that rejects requests missing `isHighRiskAdminAction` + valid `managerApproval`.
+- Audit logging integration for every privileged action (see audit-logging-standard.md).
+
+**@frontend:**
+- Reusable `HighRiskSecurityModal` component.
+- Hermes briefing flow that collects a reason and only then dispatches the approved request.
+
+Only after these two layers are in place and tested may we begin implementing actual privileged user stories.
+
+---
+
+**Usage for @manager:**
+- Copy and adapt these briefings at the appropriate moments.
+- Always reference the exact knowledge files in `.agents/knowledge/corporate-governance/`.
+- Document the user’s and agents’ acknowledgments in `PROJECT_MEMORY.md`.

package/.enderun/knowledge/deployment_checklist.md

@@ -0,0 +1,7 @@
+# Deployment Checklist
+
+- [ ] Environment variables set (`.env.production`).
+- [ ] Database migrations executed.
+- [ ] Build artifacts verified.
+- [ ] SSL certificates active.
+- [ ] Monitoring hooks connected.

package/{.antigravitycli → .enderun}/knowledge/framework_vs_user_project_boundary.md

@@ -7,7 +7,7 @@ This is one of the most important rules in Agent Enderun.
 There is a strict separation between two things:
 
 1. **The Agent Enderun Framework** (the tool)
-   - Located in: `framework-mcp/`, `.antigravitycli/`, `bin/`, root config files (`panda.config.ts`, etc.)
+   - Located in: `framework-mcp/`, `.gemini/`, `bin/`, root config files (`panda.config.ts`, etc.)
    - Purpose: Governance, agents, MCP tools, CLI, knowledge base, blueprints
 
 2. **The User's Application** (what the user is actually building)
@@ -22,14 +22,14 @@ All new code, files, features, and modifications must happen **exclusively** ins
 
 ### Forbidden Actions (When Building User's Project)
 - Creating files in `framework-mcp/src/utils/`, `framework-mcp/src/tools/`, etc.
-- Modifying agent definitions in `.antigravitycli/agents/`
+- Modifying agent definitions in `.gemini/agents/`
 - Editing `panda.config.ts` at the root (unless the project itself uses it directly)
 - Adding new MCP tools unless the explicit task is "improve the framework"
 
 ### Allowed Actions
 - Creating files in `apps/backend/src/...`
 - Creating files in `apps/web/src/...`
-- Adding blueprints and knowledge under `.antigravitycli/` **only** when improving the framework for everyone
+- Adding blueprints and knowledge under `.gemini/` **only** when improving the framework for everyone
 - Updating project-specific configs inside the user's `apps/` or root project files
 
 ## Why This Rule Exists

package/{.antigravitycli → .enderun}/knowledge/frontend_professionalization_guidelines.md

@@ -2,20 +2,20 @@
 
 **Version:** 1.0  
 **Owner:** @manager  
-**Last Updated:** 23 May 2026
+**Last Updated:** 23 Mayıs 2026
 
 ## Purpose
 
-This document defines the official **@frontend Professionalization Program** to close the critical risk item **"@frontend Weakness"** in the Risk Tracking Dashboard.
+This document defines the official **@frontend Professionalization Program** to close the critical risk item **"@frontend Zayıflığı"** in the Risk Tracking Dashboard.
 
-The goal is to elevate the @frontend agent from its current level (6.5) to a true **enterprise-grade** frontend architect (target: 9.0) within 6–8 weeks.
+The goal is to elevate the @frontend agent from its current level (6.5) to a true **kurumsal (enterprise) grade** frontend architect (target: 9.0) within 6–8 weeks.
 
-## Current Risk Assessment (23 May 2026)
+## Current Risk Assessment (23 Mayıs 2026)
 
-- **Risk Name:** @frontend Weakness
+- **Risk Name:** @frontend Zayıflığı
 - **Current Level:** 6.5 / 10
 - **Target Level:** 9.0 / 10
-- **Risk Severity:** Critical / High Risk
+- **Risk Severity:** Kritik / Yüksek Risk
 - **Main Weaknesses:**
   - Component architecture and composition patterns exist on paper but are not deeply enforced.
   - Accessibility (WCAG 2.2) is defined but lacks mandatory enforcement and audit mechanisms.
@@ -48,7 +48,7 @@ The goal is to elevate the @frontend agent from its current level (6.5) to a tru
 - Establish formal **Design System Evolution Process** (proposal → @manager review → approval → migration plan).
 - Create @frontend Growth Task system (similar to other agents).
 - Integrate @frontend performance and accessibility metrics into BRAIN_DASHBOARD.md.
-- Close the "@frontend Weakness" risk item in the Risk Tracking Dashboard upon successful demonstration in a reference application.
+- Close the "@frontend Zayıflığı" risk item in the Risk Tracking Dashboard upon successful demonstration in a reference application.
 
 ## Mandatory Requirements (Non-Negotiable)
 
@@ -84,28 +84,25 @@ Any task involving @frontend must satisfy the following:
 - Include specific @frontend growth tasks in every relevant briefing.
 - Review and approve major design system changes.
 - Track progress via the Risk Tracking Dashboard and BRAIN_DASHBOARD.md.
-- Ensure that @frontend strictly follows the Enterprise Adaptation rules in all user projects (see `enterprise_frontend_adaptation.md`).
-- Escalate repeated violations of accessibility, performance, testing, or D004 adaptation standards as leadership failures.
+- Ensure that the reference application (when built) includes real-world examples of professional frontend patterns.
+- Escalate repeated violations of accessibility, performance, or testing standards as leadership failures.
 
-## Success Criteria (Risk Closure) — Capability First (Post-D004)
+## Success Criteria (Risk Closure)
 
-The "@frontend Weakness" risk can be closed when:
+The "@frontend Zayıflığı" risk can be closed when:
 
-- @frontend agent consistently applies compound components, accessibility (WCAG 2.2), performance budgets, **Panda CSS as the primary styling system**, and proper testing in **real user projects**.
-- @frontend demonstrates mastery of the Enterprise Frontend Adaptation Framework (`enterprise_frontend_adaptation.md`) — correctly discovering the project and intelligently choosing Panda CSS when possible, while respecting strong existing systems when necessary.
-- Completion Reports show high compliance with both professional patterns **and** the Enterprise Adaptation section, including explicit Panda CSS usage.
-- Measurable improvement is visible in BRAIN_DASHBOARD.md and actual project outcomes over multiple engagements.
-- @frontend no longer proposes blind "ideal" structures and instead intelligently shapes itself to whatever architecture the user already has.
+- @frontend agent consistently applies compound components, accessibility, and performance patterns in real tasks.
+- A reference application demonstrates professional-grade frontend work (including high-risk admin flows with Hermes).
+- @frontend Completion Reports show high compliance with the new mandatory requirements.
+- Metrics in BRAIN_DASHBOARD.md show measurable improvement in @frontend quality.
 
 ## Related Documents
 
-- `.antigravitycli/agents/frontend.md` (main definition + Enterprise Adaptation section)
-- `.antigravitycli/knowledge/enterprise_frontend_adaptation.md` (primary reference for large projects)
+- `.gemini/agents/frontend.md` (main definition)
+- `.gemini/knowledge/reference_application_guidelines.md`
 - `docs/roadmap.md` → Risk Tracking Dashboard
 - `PROJECT_MEMORY.md` → STRATEGIC ROADMAP
 
 ---
 
 **This guideline is now part of the official agent knowledge base.** All agents, especially @manager and @frontend, must follow it when working on frontend-related tasks in kurumsal projects.
-
-**Update Note (24 May 2026):** Success criteria shifted from "prove in reference app" to "prove through consistent, context-aware performance in real enterprise projects" following Decision D004.

package/{.antigravitycli → .enderun}/knowledge/hermes_live_test_guidelines.md

@@ -2,19 +2,19 @@
 
 **Version:** 1.0  
 **Owner:** @manager  
-**Last Updated:** 23 May 2026
+**Last Updated:** 23 Mayıs 2026
 
 ## Purpose
 
-This document defines the official **Hermes Live Test Program** to close the risk item **"Hermes 'Defined on Paper'"** in the Risk Tracking Dashboard.
+This document defines the official **Hermes Live Test Program** to close the risk item **"Hermes 'Kağıt Üzerinde'"** in the Risk Tracking Dashboard.
 
 Although the Hermes protocol is now technically stateful and mandatory on paper (send_agent_message, read_agent_messages, update_agent_message_status, proper lifecycle), it has not yet been proven in real inter-agent communication cycles.
 
 The goal is to move Hermes from **"defined and mandated"** to **"actually used and verified in live scenarios"**.
 
-## Current Risk Status (23 May 2026)
+## Current Risk Status (23 Mayıs 2026)
 
-- **Risk Name:** Hermes “Defined on Paper”
+- **Risk Name:** Hermes “Kağıt Üzerinde”
 - **Previous Progress:** %70 (protocol made stateful + mandatory in all agents)
 - **Current Gap:** No real, end-to-end live message flows have been executed and verified between agents in a working context.
 - **Risk Severity:** Orta (but blocking full autonomous orchestration claim)
@@ -50,7 +50,7 @@ To consider the Hermes protocol "live and proven", the following scenarios **mus
 
 ## Acceptance Criteria (Risk Closure)
 
-The "Hermes Defined on Paper" risk can be closed only when **all** of the following are true:
+The "Hermes Kağıt Üzerinde" risk can be closed only when **all** of the following are true:
 
 - At least the 4 scenarios above have been executed in a real context (preferably inside the reference application).
 - Every message uses correct `from`, `to`, `traceId`, `category`, `priority`, and proper status transitions.
@@ -78,10 +78,10 @@ The "Hermes Defined on Paper" risk can be closed only when **all** of the follow
 
 ## Related Documents
 
-- `.antigravitycli/knowledge/hermes_protocol.md` (original protocol definition)
-- `.antigravitycli/agents/manager.md` → Hermes Communication Mandate section
-- `.antigravitycli/knowledge/frontend_professionalization_guidelines.md`
-- `.antigravitycli/knowledge/reference_application_guidelines.md`
+- `.gemini/knowledge/hermes_protocol.md` (original protocol definition)
+- `.gemini/agents/manager.md` → Hermes Communication Mandate section
+- `.gemini/knowledge/frontend_professionalization_guidelines.md`
+- `.gemini/knowledge/reference_application_guidelines.md`
 - `docs/roadmap.md` → Risk Tracking Dashboard
 - `PROJECT_MEMORY.md` → STRATEGIC ROADMAP
 

package/{.antigravitycli → .enderun}/knowledge/hermes_protocol.md

@@ -45,10 +45,10 @@ Every message sent via `send_agent_message` must follow this conceptual structur
 
 ## 🔄 Lifecycle Protocol
 
-1.  **Dispatch:** Agent calls `send_agent_message`. Message is saved in `.antigravitycli/messages/recipient.json`.
+1.  **Dispatch:** Agent calls `send_agent_message`. Message is saved in `.gemini/messages/recipient.json`.
 2.  **Notification:** The recipient agent checks their inbox during their turn via `read_agent_messages`.
 3.  **Acknowledgment:** For `ACTION` or `DELEGATION`, the recipient should send an `INFO` message back once started or completed.
-4.  **Logging:** All critical communications must be summarized in the agent's log file (`.antigravitycli/logs/agent.json`).
+4.  **Logging:** All critical communications must be summarized in the agent's log file (`.gemini/logs/agent.json`).
 
 ---
 

package/{.antigravitycli → .enderun}/knowledge/manager_authority_audit_enforcement.md

@@ -2,7 +2,7 @@
 
 **Version:** 1.0  
 **Owner:** @manager  
-**Last Updated:** 23 May 2026
+**Last Updated:** 23 Mayıs 2026
 
 ## Purpose
 
@@ -12,14 +12,14 @@ Even though strong rules exist in individual agent files, without a systematic a
 
 ## Why This Is Necessary
 
-From the agent control audit (23 May 2026):
+From the agent control audit (23 Mayıs 2026):
 
 - @backend, @frontend, @analyst, and @explorer have partial governance rules, but enforcement is inconsistent.
 - @git, @mobile, and @native have almost no @manager control defined.
 - Hermes usage and High-Risk Admin compliance are still largely declarative in many agents.
 - Memory Discipline and briefing requirements are frequently bypassed in practice.
 
-Without regular auditing and clear enforcement, the "Single Entry Point" and "Zero Tolerance" principles lose effectiveness.
+Without regular auditing and clear enforcement, the "Tek Giriş Noktası" and "Sıfır Tolerans" principles lose effectiveness.
 
 ## Core Principles
 
@@ -77,10 +77,10 @@ When a violation is detected, @manager must apply the following in order:
 
 This authority system directly supports the closure of multiple risks:
 
-- No Production-Grade Reference Application
-- @frontend Weakness
-- Hermes “Defined on Paper”
-- Lack of Real Usage Data
+- Referans Uygulama Yokluğu
+- @frontend Zayıflığı
+- Hermes “Kağıt Üzerinde”
+- Gerçek Kullanım Eksikliği
 
 Every time a reference application or major task is executed, @manager must run an Authority Audit and record findings.
 
@@ -92,10 +92,10 @@ Every time a reference application or major task is executed, @manager must run
 
 ## Related Documents
 
-- `.antigravitycli/agents/manager.md` → @manager Mandatory Behavior Rules for Enterprise Projects + Hermes Communication Mandate
-- `.antigravitycli/knowledge/hermes_live_test_guidelines.md`
-- `.antigravitycli/knowledge/frontend_professionalization_guidelines.md`
-- `.antigravitycli/knowledge/reference_application_guidelines.md`
+- `.gemini/agents/manager.md` → Kurumsal Proje İçin @manager Zorunlu Davranış Kuralları + Hermes Communication Mandate
+- `.gemini/knowledge/hermes_live_test_guidelines.md`
+- `.gemini/knowledge/frontend_professionalization_guidelines.md`
+- `.gemini/knowledge/reference_application_guidelines.md`
 - `docs/roadmap.md` → Risk Tracking Dashboard
 - `PROJECT_MEMORY.md` → STRATEGIC ROADMAP + HISTORY
 

package/{.antigravitycli → .enderun}/knowledge/project_scaffold_guidelines.md

@@ -2,7 +2,7 @@
 
 **Version:** 1.0  
 **Owner:** @manager  
-**Last Updated:** 23 May 2026
+**Last Updated:** 23 Mayıs 2026
 
 ## Purpose
 
@@ -14,8 +14,8 @@ The goal is to move from "empty `apps/` folder" to a **minimal but meaningful pr
 
 @manager should initiate a project scaffold in the following cases:
 
-- The Risk Tracking Dashboard shows **"No Production-Grade Reference Application"** as a top-priority open risk.
-- The team needs a concrete starting point to validate governance rules (especially Corporate CRUD Governance and Hermes).
+- The Risk Tracking Dashboard shows **"Referans Uygulama Yokluğu"** as a top-priority open risk.
+- The team needs a concrete starting point to validate governance rules (especially Kurumsal CRUD Yönetişimi and Hermes).
 - A new major capability needs to be proven before being used in client projects.
 - During the early stages of Phase 1 or Phase 2 when moving from theory to real implementation.
 
@@ -74,7 +74,7 @@ Any project scaffold created with Agent Enderun **must** include at least the fo
 - The scaffold must respect the **Framework vs User Project Boundary** (only work inside `apps/`).
 - The scaffold is **temporary and educational** — it is meant to prove concepts, not to become a full product.
 - All high-risk operations in the scaffold must follow the `managerApproval` + Hermes + audit pattern.
-- After successful completion, update the Risk Tracking Dashboard to reflect progress on "No Production-Grade Reference Application".
+- After successful completion, update the Risk Tracking Dashboard to reflect progress on "Referans Uygulama Yokluğu".
 
 ## Success Criteria
 
@@ -88,10 +88,10 @@ A project scaffold is considered successful when:
 
 ## Related Documents
 
-- `.antigravitycli/knowledge/reference_application_guidelines.md`
-- `.antigravitycli/knowledge/frontend_professionalization_guidelines.md`
-- `.antigravitycli/knowledge/hermes_live_test_guidelines.md`
-- `.antigravitycli/knowledge/manager_authority_audit_enforcement.md`
+- `.gemini/knowledge/reference_application_guidelines.md`
+- `.gemini/knowledge/frontend_professionalization_guidelines.md`
+- `.gemini/knowledge/hermes_live_test_guidelines.md`
+- `.gemini/knowledge/manager_authority_audit_enforcement.md`
 - `docs/roadmap.md` → Risk Tracking Dashboard
 
 ---

package/{.antigravitycli → .enderun}/knowledge/reference_application_guidelines.md

@@ -2,7 +2,7 @@
 
 **Version:** 1.0  
 **Owner:** @manager  
-**Last Updated:** 23 May 2026
+**Last Updated:** 23 Mayıs 2026
 
 ## Purpose
 
@@ -14,8 +14,8 @@ The goal of a reference application is to **prove** that Agent Enderun’s gover
 
 @manager should initiate a reference application in the following situations:
 
-- The Risk Tracking Dashboard shows **"No Production-Grade Reference Application"** as a top-priority open risk.
-- The team needs to validate that new governance rules (especially Corporate CRUD Governance and Hermes) work end-to-end.
+- The Risk Tracking Dashboard shows **"Referans Uygulama Yokluğu"** as a top-priority open risk.
+- The team needs to validate that new governance rules (especially Kurumsal CRUD Yönetişimi and Hermes) work end-to-end.
 - A new major capability (e.g., advanced Hermes flows, complex admin patterns) needs to be demonstrated before being trusted in client projects.
 - During Phase 1 or early Phase 2 when moving from theory to practice.
 
@@ -38,13 +38,13 @@ Any reference application **must** demonstrate the following:
    - At least one real inter-agent message flow (e.g., @backend → @analyst or @manager → @backend)
    - Proper use of `send_agent_message` + `update_agent_message_status`
 
-5. **Corporate Governance Compliance**
+5. **Kurumsal Yönetişim Compliance**
    - All high-risk actions must go through @manager briefing and approval
    - Full audit logging with Trace ID, previousState/newState, and actor
 
 6. **Framework Boundary Respect**
    - All code lives strictly inside `apps/`
-   - No modifications to `framework-mcp/`, `.antigravitycli/agents/`, or root framework files
+   - No modifications to `framework-mcp/`, `.gemini/agents/`, or root framework files
 
 7. **Professional Standards**
    - Error handling with DomainError hierarchy
@@ -73,7 +73,7 @@ This scope is small enough to build quickly but rich enough to prove the most cr
 
 - Never create a reference application without an explicit @manager briefing.
 - The reference app is **temporary and educational** — it is not a product.
-- After the reference application successfully closes the "No Production-Grade Reference Application" risk, it may be archived or replaced with a cleaner example.
+- After the reference application successfully closes the "Referans Uygulama Yokluğu" risk, it may be archived or replaced with a cleaner example.
 - All work must be logged in HISTORY and the Risk Tracking Dashboard must be updated.
 
 ## Updating Risk Status
@@ -81,7 +81,7 @@ This scope is small enough to build quickly but rich enough to prove the most cr
 When a reference application is completed and accepted:
 
 1. Update the Risk Tracking Dashboard in both `docs/roadmap.md` and `PROJECT_MEMORY.md`
-2. Mark "No Production-Grade Reference Application" as **Closed**
+2. Mark "Referans Uygulama Yokluğu" as **Closed**
 3. Record the achievement in the HISTORY section of PROJECT_MEMORY.md
 4. Optionally create a short "Reference Application Walkthrough" under `docs/`
 

package/.enderun/logs/analyst.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/backend.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/devops.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/explorer.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/frontend.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/git.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/manager.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/mobile.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/native.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/orchestrator.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/qa.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/logs/security.json

@@ -0,0 +1 @@
+{"runs":[]}

package/.enderun/memory-graph/agent-contexts/analyst.json

@@ -0,0 +1 @@
+{ "agent": "@analyst", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/backend.json

@@ -0,0 +1 @@
+{ "agent": "@backend", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/devops.json

@@ -0,0 +1 @@
+{ "agent": "@devops", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/explorer.json

@@ -0,0 +1 @@
+{ "agent": "@explorer", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/frontend.json

@@ -0,0 +1 @@
+{ "agent": "@frontend", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/git.json

@@ -0,0 +1 @@
+{ "agent": "@git", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/manager.json

@@ -0,0 +1 @@
+{ "agent": "@manager", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/mobile.json

@@ -0,0 +1 @@
+{ "agent": "@mobile", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/native.json

@@ -0,0 +1 @@
+{ "agent": "@native", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/orchestrator.json

@@ -0,0 +1 @@
+{ "agent": "@orchestrator", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/qa.json

@@ -0,0 +1 @@
+{ "agent": "@qa", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/agent-contexts/security.json

@@ -0,0 +1 @@
+{ "agent": "@security", "version": "1.0.0", "lastUpdated": "2026-05-25T17:00:00Z", "sessionHistory": [], "knownContracts": [], "recentDecisions": [], "watchedFiles": [], "pendingTasks": [], "notes": "Context initialized." }

package/.enderun/memory-graph/graph.json

@@ -0,0 +1,26 @@
+{
+  "version": "1.0.0",
+  "description": "Agent Enderun Army Memory Graph. Tracks all agent interactions, delegations, and communication edges across the entire army.",
+  "generatedAt": "2026-05-25T17:00:00Z",
+  "updatedAt": "2026-05-25T17:00:00Z",
+  "nodes": [
+    { "id": "@manager", "state": "IDLE", "lastAction": "Framework initialized", "activeTrace": null, "healthScore": 9.5, "totalActionsThisSession": 0 },
+    { "id": "@orchestrator", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.8, "totalActionsThisSession": 0 },
+    { "id": "@backend", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.2, "totalActionsThisSession": 0 },
+    { "id": "@frontend", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.0, "totalActionsThisSession": 0 },
+    { "id": "@security", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.3, "totalActionsThisSession": 0 },
+    { "id": "@qa", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.1, "totalActionsThisSession": 0 },
+    { "id": "@devops", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.0, "totalActionsThisSession": 0 },
+    { "id": "@analyst", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.6, "totalActionsThisSession": 0 },
+    { "id": "@explorer", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.4, "totalActionsThisSession": 0 },
+    { "id": "@git", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 9.1, "totalActionsThisSession": 0 },
+    { "id": "@mobile", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 8.8, "totalActionsThisSession": 0 },
+    { "id": "@native", "state": "IDLE", "lastAction": null, "activeTrace": null, "healthScore": 8.9, "totalActionsThisSession": 0 }
+  ],
+  "edges": [],
+  "schema": {
+    "nodeFields": ["id", "state", "lastAction", "activeTrace", "healthScore", "totalActionsThisSession"],
+    "edgeFields": ["id", "from", "to", "type", "traceId", "timestamp", "metadata"],
+    "edgeTypes": ["DELEGATED", "ESCALATED", "BLOCKED_BY", "UNBLOCKED_BY", "BROADCAST", "COLLABORATED", "REVIEWED"]
+  }
+}