SaferSkills independently audited compound-learner-mem-bundle (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
R&D / Experimental. Maintained by Sage / 0SxD as part of an ongoing prompt-engineering and agent-skills research portfolio.
Drop-in compound engineering operating system for AI agents. One kernel, three pillars (Pathos + Ethos + Logos), persistent wiki memory, self-evolving gate.
A generic skeleton that turns any Claude chat or Claude Code session into a domain-expert agent. The agent runs multi-turn Trinity Dialectic interrogation BEFORE executing any task, so every output either hits 100% success on a pre-declared rubric OR flags specific blockers the user must resolve first.
Works for any project where "figure out the right thing to build" matters more than "type fast." Examples: research synthesis, grant writing, product planning, technical specs, policy drafting, complex multi-step reasoning.
CLAUDE.md into it, savePATHOS.md, ETHOS.md, LOGOS.md, and the wiki/ folder to Project filesbootgit clone [your-fork] or copy the bundle into your project folderCLAUDE.md auto-loads when Claude Code opens the folderbootThe kernel ships unconfigured. The agent runs auto-agent-construction by asking you multi-turn questions bucketed into the Trinity Dialectic:
Your answers get written into PATHOS.md, ETHOS.md, LOGOS.md. The generic kernel becomes a domain expert for YOUR project. See ETHOS.md section auto_agent_construction for the exact procedure.
| File | Role | One-liner |
|---|---|---|
| README.md | Human entry | The front door |
| CLAUDE.md | Agent boot sector | The switch, also the Claude Project paste-text |
| PATHOS.md | Role, mission, voice | The why |
| ETHOS.md | Rules, gates, rubric | The rules |
| LOGOS.md | Tools, skills tree | The how |
Plus wiki/ for persistent memory (catalog, log, insights ledger, metrics, references).
pel-kernel/
├── README.md # You are here
├── CLAUDE.md # Boot sector + Claude Project paste-text
├── PATHOS.md # Role + mission + voice (WHY)
├── ETHOS.md # Rules + gates + rubric (RULES)
├── LOGOS.md # Tools + skills tree (HOW)
└── wiki/
├── index.md # Content catalog
├── log.md # Append-only chronological log
├── insights.md # Promotion ledger (raw + promoted)
├── metrics.md # Telemetry (sonnet:opus ratio, turn counts)
└── reference/
└── research_report.md # Landscape scan + design rationale (reference)skills/ gets created when the first insight promotes (see ETHOS.md promotion thresholds)specs/ gets created when the first task-specific spec emerges.claude/commands/ gets created by install script in Claude Code CLI mode onlywiki/raw/ gets created on first source ingestwiki/log.archive/ gets created on first log rotation (1000 entries)wiki/insights.archive/ gets created on first demotion (30+ inactive days)Kernel files stay small. As agent learns:
wiki/insights.md raw sectionskills/LOGOS.md gets a pointer row, never the inline contentspecs/wiki/Result: kernel never bloats. Depth grows laterally, not vertically.
Six explicit rules in ETHOS.md:
insights.md promoted section 100 lines, log.md 1000 entries, LOGOS.md 500 lines, individual skills 80 linesETHOS.md declares spec version; install refuses on mismatchLog rotation, insight archival, skill demotion all happen automatically. See ETHOS.md archival policy table.
Every consequential output scored on three dimensions, each 0.0 to 1.0:
Final score = Pathos × Ethos × Logos (product, not sum). Ship threshold = 1.0. Any dimension at 0 = whole turn fails.
This is the core contract: the agent ships at 100% or tells you exactly why it cannot.
Every hard-fail (artifact that shipped defective OR was caught at gate) produces a new rule in ETHOS.md. Version bumps automatically. No speculative rules; only rules derived from real failures enter the gate.
The kernel rewrites its own rulebook in response to reality. Compound engineering applied to the system itself.
"PEL Kernel" is the default name. You can rename on your end without touching the architecture. Only PATHOS.md is domain-specific (the <REPLACE_THIS_BLOCK> section). ETHOS.md and LOGOS.md are fully generic in the shipped bundle and become domain-aware through references to PATHOS.md.
A forker clones the bundle, runs auto-agent-construction, and has a working project expert for their domain without touching evaluation or execution logic.
Adding this bundle to a project that already has files does NOT degrade existing work. The kernel is a superset of typical ad-hoc scaffolds. Existing canon files (research docs, specs, prior outputs) become pre-existing sources in wiki/raw/ on first ingest. Auto-agent-construction configures the kernel to respect what's already there.
If you drop this into a project mid-flight, the first run asks "what already exists? what should I read as canon?" before touching anything.
rm -rf the folder. Nothing else. No daemons, no registries, no residual files.
MIT. SPDX: MIT. See LICENSE. Author: Sage / 0SxD
This repo is part of an active R&D portfolio. Content may move, change, or be withdrawn. Issues welcome but reviews are best-effort.
Built on patterns from:
See wiki/reference/research_report.md for the full landscape scan, design rationale, and uniqueness assessment. That report references a specific instance ("HumanX OS v2") the research was commissioned for; the kernel you hold is the generic version derived from that research.
PATHOS.md to see the role stubCLAUDE.md to see the boot sequenceETHOS.md auto_agent_construction section to see what happens on first runboot~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.