Some checks are pending
CI — CoM Config Validation / Validate JSON Configs (push) Waiting to run
CI — CoM Config Validation / Validate YAML Configs (push) Waiting to run
CI — CoM Config Validation / Lint Shell Scripts (push) Waiting to run
CI — CoM Config Validation / Secret Detection (push) Waiting to run
CI — CoM Config Validation / Lint Markdown (push) Waiting to run
CI — CoM Config Validation / Validate CODEOWNERS (push) Waiting to run
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
1.1 KiB
1.1 KiB
| paths | |
|---|---|
|
Syn_OS Development Rules — Active when working in the repo
Code Standards
- Rust code follows
cargo clippy --workspace --all-targets -- -D warnings - Conventional commits:
type(scope): summary(see /save skill for full spec) - No unsafe blocks without documented justification
- All new crates must have at least basic tests
Build System
- Use
justcommands (justfile has 20+ targets) orcargo xtask - ISO builds go through the 30-stage validation pipeline
- Never modify Cargo.toml workspace members without running
cargo check
Agent Workflow
- The Syn_OS repo has its OWN .claude/ with specialized configs — defer to repo-level agents when working there
- Home agents (Atlas, Sentinel, Ops) handle cross-project admin
- Repo agents (CADevO, Cipher, Aegis, etc.) handle Syn_OS-specific work
Key References
- CLAUDE.md in repo root: 22KB of project context
- FEV.md: 74KB roadmap (v21→v25)
- HostConfigs: config// (security profiles, ansible, firejail, grub, network, ufw)
- ARCANUM ansible inventory: arcanum/ansible/hosts