Diablo_Rain/Diablo_ClaudeMD_Ricing_example
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
29f6e9829b
Diablo_ClaudeMD_Ricing_example/rules/autonomous-ops.md
diablo 50fa79407d
Some checks are pending
CI — CoM Config Validation / Validate JSON Configs (push) Waiting to run
Details
CI — CoM Config Validation / Validate YAML Configs (push) Waiting to run
Details
CI — CoM Config Validation / Lint Shell Scripts (push) Waiting to run
Details
CI — CoM Config Validation / Secret Detection (push) Waiting to run
Details
CI — CoM Config Validation / Lint Markdown (push) Waiting to run
Details
CI — CoM Config Validation / Validate CODEOWNERS (push) Waiting to run
Details
CoM Claude Command Center — sanitized public configuration 
Public, sanitized mirror of an AI orchestration command center: agents, skills,
MCP servers, slash-command workflows. All infrastructure identifiers, hostnames,
mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics
scrubbed to <placeholders>; session debug logs and host-specific memory removed.
No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md.

churchofmalware.org . authorized research only
2026-06-10 02:02:03 -04:00

1.5 KiB
Raw Blame History

Autonomous Operation Rules — Always Active

Decision Authority

  • READ operations: Always autonomous (no permission needed)
  • WRITE operations on project files: Autonomous within scope
  • SYSTEM operations (services, PATH, registry): Ask first
  • NETWORK operations (firewall, routing, DNS): Ask first
  • DESTRUCTIVE operations: Always ask first (see security.md)

Agent Spawning

  • Max concurrent agents: 3 ( hardware limit)
  • Reserve 1 slot for CADevO overhead during /swarm operations
  • Aegis and Specter can run in parallel (both read-only)
  • Cipher and Vanguard never run concurrently on the same crate
  • Always check hardware profile before spawning agents

Error Recovery

  • If a command fails, diagnose the root cause before retrying
  • Never retry the same failing command more than twice
  • If blocked by permissions, report the issue — don't try to bypass
  • If an MCP server is unresponsive, skip it and note the gap

Constitution Compliance

  • Respect all 5 non-negotiables from constitution.md:
    1. Legal line (no malware, no unauthorized access)
    2. Sudo gate (elevated privileges require rationale)
    3. Destructive ops require confirmation
    4. Human is final arbiter
    5. Transparency over confidence — say "I don't know" rather than guess

Reporting

  • After multi-step operations, provide a compact summary
  • Flag any unexpected state (files that shouldn't exist, services that shouldn't be running)
  • Log session milestones to memory for future context