Bonni's Automous workflow Custom_modes.yaml

[OttSmarty]

custom_modes.md
custom_modes.yaml

[OttSmarty]

BONNI Autonomous Kilo Modes

A curated set of 18+ production‑grade Kilo Code modes that turn BONNI‑AI into a mostly self‑driving system: governance, core architecture, cognitive engine, Bedrock/Minecraft integration, analysis/visualization, community ops, and essential infra.

Who is this for? Builders using Kilo Code who want an opinionated, autonomous multi‑mode stack for AI + Minecraft research and operations (Windows‑first paths shown; adapt as needed).

---

TL;DR

1. Copy custom_modes.yaml into your project (e.g. .kilocode/custom_modes.yaml).
2. Launch Kilo and select a mode (start with Executive Orchestrator).
3. Keep Ethics & Safety Auditor enabled for guardrails.
4. Use the Mode Tech + Diagnostic Orchestrator pair to validate and harden.

---

Contents

• Overview
• Install & Setup
• Quick Start
• Runtime Conventions
• Safety & Governance
• Mode Taxonomy
• Operational Playbooks
• Diagnostics & Observability
• Contributing
• Mode Reference (Appendix)
• Changelog

---

Overview

These modes are organized into tiers that mirror the system’s cognitive and operational layers:

TIER 1  Governance         ──► orchestrator · ethics-governor
TIER 2  Core Architecture  ──► lead-ai-architect · architect
TIER 3  Cognitive Engine   ──► metacognitive-architect · cognitive-algorithm-engineer · memory-engineer · neural-link-engineer
TIER 4  Game Integration   ──► bedrock-tech · bds-integration · addon-developer · simulation-engineer
TIER 5  Analysis/Viz       ──► behavior-analyst · visualization-engineer · research-console-developer
TIER 6  Interface/Comm     ──► technical-writer · user · community-liaison
Infra   Essentials         ──► devops-engineer · telemetry-engineer · debug · mode-tech · ask · code

All modes default to autonomous execution (autoExecute: true, requireConfirmation: false) with safe rollback on error. You can override this per‑mode.

---

Install & Setup

File layout

Place the YAML in your repo so Kilo can load it:

.your-project/
└─ .kilocode/
   ├─ custom_modes.yaml       # ← this file
   └─ README.md               # optional local copy of this guide

Some teams prefer modes/custom_modes.yaml. Kilo supports multiple locations; pick one and keep it consistent.

Enable in Kilo Code

• Open Kilo → select your workspace → Modes pane → ensure your custom_modes.yaml is discovered.
• If Kilo supports multiple mode registries, make sure this file is higher priority than defaults for slug collisions.

Windows‑first paths

Several modes reference Windows paths (e.g., D:\Bonni\…). Treat these as examples; update to your environment. Prefer environment variables and a single context:// root shim in MCP for portability.

---

Quick Start

1. Safety first → keep Ethics & Safety Auditor enabled.
2. Start orchestration → run Executive Orchestrator (orchestrator) to plan a cross‑mode workflow.
3. Pick a target → e.g., “spin up BDS, deploy behavior packs, connect AI bridge, start telemetry.”
4. Harden config → run Mode Tech (mode-tech) to lint/validate modes.
5. Verify → run Diagnostic Orchestrator (debug) and check reports.

---

Runtime Conventions

• MCP Calls: Many modes rely on MCP tools/resources (e.g., use_mcp_tool('pack-validator', …), access_mcp_resource('telemetry://…')). Provide no‑op shims if a tool is missing so modes don’t crash.
• Telemetry Everywhere: Emit structured logs for all actions. Ethics and Diagnostics subscribe to these channels.
• Idempotency: Modes should be safe to re‑run; most carry their own rollback and diffing.
• Least Surprise: Keep defaults autonomous but allow an env flag KILO_REQUIRE_CONFIRMATION=1 for manual sessions.

---

Safety & Governance

• Ethics & Safety Auditor (ethics-governor) runs continuously: predictive risk, pre‑execution blocks, compliance logs.
• Executive Orchestrator (orchestrator) coordinates cross‑mode plans and enforces escalation.
• Recommended kill‑switch: KILO_SAFE_MODE=1 disables auto‑execute in high‑risk contexts (prod, cost spikes).

---

Mode Taxonomy

Tier	Slug	Name	Purpose (one‑liner)	Auto	Groups
1	orchestrator	Executive Orchestrator	Global planner, cross‑mode coordination	✅	mcp, read, edit, browser, command
1	ethics-governor	Ethics & Safety Auditor	Predictive risk + compliance; blocks unsafe ops	✅	mcp, read, browser, command
2	lead-ai-architect	Lead AI Architect	Cognitive architecture design/evolution	✅	mcp, read, edit, browser, command
2	architect	Core Systems Architect	Full‑stack system + topology design	✅	mcp, read, edit, browser, command
3	metacognitive-architect	Metacognitive Architect	Self‑observation & reflective learning	✅	mcp, read, edit, command
3	cognitive-algorithm-engineer	Cognitive Algorithm Engineer	Neuroscience → code, profiling, tuning	✅	mcp, read, edit, command
3	memory-engineer	Memory Engineer	Embeddings, FAISS/Annoy, recall optimization	✅	mcp, read, edit, command
3	neural-link-engineer	Neural Link Engineer	Perception↔UGI↔Memory routing & latency	✅	mcp, read, edit, command
4	bedrock-tech	Bedrock Tech	BDS ops, packs, AI bridge health	✅	mcp, read, edit, browser, command
4	bds-integration	BDS Integration	Protocols, event mapping, latency control	✅	mcp, read, edit, command
4	addon-developer	Add‑On Developer	BP/behavior JSON, /scriptevent, entities	✅	mcp, read, edit, browser, command
4	simulation-engineer	Simulation Engineer	Worlds, constraints, NPCs, benchmarks	✅	mcp, read, edit, command
5	behavior-analyst	Behavior Analyst	Telemetry stats, trends, predictive models	✅	mcp, read, browser, command
5	visualization-engineer	Visualization Engineer	Dashboards & visual explainers	✅	mcp, read, edit, browser, command
5	research-console-developer	Research Console Developer	"God Console" live control UI	✅	mcp, read, edit, browser, command
6	technical-writer	Technical Writer	Docs pipelines + visual docs	✅	mcp, read, edit, browser
6	user	User Research Node	External research + validation	✅	mcp, read, browser, command
6	community-liaison	Community Liaison	GitHub/Docs/Discord coordination	✅	mcp, read, browser, command
—	devops-engineer	DevOps Engineer	Containers, GPU alloc, CI/CD	✅	mcp, read, edit, browser, command
—	telemetry-engineer	Telemetry & Diagnostics	Metrics/logs/traces + health prediction	✅	mcp, read, edit, browser, command
—	debug	Diagnostic Orchestrator	Cross‑layer scans + self‑correct	✅	mcp, read, command
—	mode-tech	Mode Tech	Mode schema/regex validation + diffs	✅	mcp, read, edit, browser, command
—	ask	SiftReader	Whole‑repo ingest + insights	—	read, mcp, browser
—	code	Code Skeptic	Enforces proof & project rules	—	mcp, read, edit, browser, command

Auto indicates autoExecute: true and requireConfirmation: false by default in your YAML.

---

Operational Playbooks

A. Stand up a research world end‑to‑end

1. orchestrator plans resources and dependencies.
2. devops-engineer builds/starts containers (BDS, bridges, services).
3. bedrock-tech configures BDS, installs/validates packs.
4. bds-integration brings up WebSocket/REST bridges; tunes latency.
5. addon-developer deploys new entities/events + /scriptevent flows.
6. telemetry-engineer enables metrics/logs; visualization-engineer builds dashboards.
7. behavior-analyst models emergent behavior; technical-writer captures the run.
8. debug runs cross‑layer diagnostics; ethics-governor monitors throughout.

B. Cognitive architecture upgrade

• lead-ai-architect proposes module evolution → cognitive-algorithm-engineer implements → memory-engineer adjusts embeddings/indexing → neural-link-engineer re‑routes pathways → debug validates.

C. Community release cycle

• community-liaison prepares GitHub release; technical-writer updates docs; visualization-engineer exports diagrams; user validates claims with sources.

---

Diagnostics & Observability

• Diagnostic Orchestrator (debug): full scans, cross‑layer coordination, predictive issue detection, self‑correction.
• Telemetry & Diagnostics Engineer: standardized metrics/logs/traces; predictive health; dashboards.
• Code Skeptic: blocks unverified claims; demands logs; enforces project rules.

Checklist before shipping

• mode-tech passes schema + regex guards
• debug scan: no high/critical findings
• ethics-governor compliance report clean
• Dashboards reflect current topology
• Runbooks updated by technical-writer

---

Contributing

1. Edit custom_modes.yaml (keep slugs stable).
2. Run Mode Tech to validate structure/regex and to generate field comments if needed.
3. Add/extend fileRegex guards for any edit‑capable modes.
4. Keep roleDefinition and whenToUse concise and action‑oriented; technical details belong in customInstructions.
5. PRs should include: sample run logs, telemetry screenshots, and a brief safety analysis.

---

Mode Reference (Appendix)

Below is a condensed reference. Each entry lists the intent, triggers, tooling, and execution policy. Full prose (roleDefinition) is included for portability.

---

TIER 1 — Governance

orchestrator — Executive Orchestrator

• Intent: Global planning, cross‑mode coordination, predictive ops.
• Exec: autoExecute: true, requireConfirmation: false, rollbackOnError: true.
• Tools: mcp, read, edit, browser, command.
• Key MCP: exec-hub.plan_global_workflow, resource-core.analyze_allocation, optimization-core.improve_workflows.
• Role:

Top-level operational controller coordinating all modes with autonomous strategic planning.

ethics-governor — Ethics & Safety Auditor

• Intent: Predictive risk, pre‑execution blocks, compliance reporting.
• Exec: autonomous + rollback.
• Key MCP: policy-hub.load_compliance_rules, safety-core.enforce_protocols, predictive-ethics.analyze_risk_factors.

---

TIER 2 — Core Architecture

lead-ai-architect — Lead AI Architect

• Intent: Cognitive architecture evolution, performance optimization.
• Key MCP: model-registry.analyze_architecture, neural-design.generate_architecture, cognitive-optimizer.enhance_modules.

architect — Core Systems Architect

• Intent: Full‑stack system topology, boundary optimization, deployment strategy.
• Key MCP: mcp-registry.validate_servers, orchestration-core.optimize_topology, deployment-optimizer.enhance_strategy.

---

TIER 3 — Cognitive Engine

metacognitive-architect

• Intent: Self‑observation, meta‑models, reflective updates.
• Key MCP: meta-lab.evaluate_self_model, self-evolution.optimize_cognition.

cognitive-algorithm-engineer

• Intent: Theory→code, validation, profiling, entropy tuning.
• Key MCP: math-engine.verify_formulas, testing-framework.validate_algorithms, entropy-tuner.optimize_thresholds.

memory-engineer

• Intent: Embeddings, indexing, recall, snapshots, cross‑session persistence.
• Key MCP: memory-hub.analyze_systems, vector-search.enhance_faiss, snapshot-manager.orchestrate_cycles.

neural-link-engineer

• Intent: Perception↔UGI↔Memory routing, coherence, latency predict.
• Key MCP: neuro-bridge.sync_channels, timing-optimizer.synchronize_pathways.

---

TIER 4 — Game Integration

bedrock-tech

• Intent: BDS ops, packs, network tuning, bridge health.
• Key MCP: pack-validator.verify_packs, bds-ops.collect_status, performance-optimizer.enhance_server.

bds-integration

• Intent: Protocol optimization, event mapping, replay/debug.
• Key MCP: protocol-optimizer.enhance_websockets, event-mapper.optimize_mapping, replay-system.debug_communication.

addon-developer

• Intent: Behavior packs, /scriptevent, entities, translation fidelity.
• Key MCP: schema-validator.enforce_structure, command-translator.optimize_mapping, entity-optimizer.enhance_behavior.

simulation-engineer

• Intent: Worlds/testbeds, constraints, NPCs, behavior logging.
• Key MCP: worldgen.create_environment, behavior-monitor.analyze_emergence.

---

TIER 5 — Analysis & Visualization

behavior-analyst

• Intent: Behavioral stats, entropy/drive analysis, forecasting.
• Key MCP: analytics-lab.analyze_behavior, pattern-recognition.identify_trends.

visualization-engineer

• Intent: Dashboards, cognitive/evo charts, assets → docs.
• Key MCP: vis-hub.generate_visualization, dashboard-builder.create_interface.

research-console-developer

• Intent: Live control UI, telemetry merge, operator widgets.
• Key MCP: telemetry-api.integrate_data, control-system.enable_live_ops.

---

TIER 6 — Interface & Communication

technical-writer

• Intent: Doc indexing, extraction, visual docs, quality gates.

user (User Research Node)

• Intent: External research + validation + verified repos.

community-liaison

• Intent: GitHub/PR/Issues/Docs/Discord orchestration.

---

Essentials — Infra & Quality

devops-engineer

• Intent: Containers, GPU resource alloc, CI/CD, autoscale.

telemetry-engineer

• Intent: Observability layer, predictive health, alerting.

debug (Diagnostic Orchestrator)

• Intent: Full scans, cross‑layer coordination, self‑correct.

mode-tech

• Intent: Mode schema validation, regex guards, diffs.

ask (SiftReader)

• Intent: Whole‑repo ingest, structured insights.

code (Code Skeptic)

• Intent: Quality gatekeeping, proof requirements, rule enforcement.

---

Changelog

• v1.0.0 — Initial public README for BONNI auto
  readme.md
  nomous modes.