Canonical Source Wins
A missing injected catalog entry does not prove Carmen is absent. Load the canonical ForgeApps skill when the surface can reach it, and state the boundary when it cannot.
Carmen Skill / Evidence Review
What Carmen Usage Has Taught Us
A bounded review of discoverable local Codex invocations and ForgeApps commit history. This draft separates durable operating lessons from unavailable or unverified history.
5local session logs sampled
40candidate user messages reviewed
23skill-history commits
21.83 KiBmain skill before subtraction
Evidence Boundary
What is available: five selected local Codex JSONL logs from August 9–21, 2026, plus the ForgeApps Git trail from the earlier Cora path through Carmen. What is not claimed: deleted sessions, other machines, unavailable services, or a complete count of every invocation.
Durable Learnings
Activation Needs Visible Proof
Valid Codex voice sessions activate without a connectivity ritual. Carmen's dashboard belongs in the current Carmen task's verified right pane.
Identity Is a Role
Adam repeatedly uses the skill to recover Carmen as his coordinator. Preserve that identity, but let the greeting stay natural instead of forcing one sentence.
Stable Owners Beat New Workers
Reuse visible tasks, keep new workers unpinned unless asked, assign one writer per artifact, and route corrections to the existing owner.
Approval Blocks Surface Fast
Name the owner, blocked action, and exact user step. Do not auto-approve or bury the block in polling.
Conversation Should Stay Human
Answer stable discussion from loaded context. Check current state when it matters. Lead with the result and remove routine reassurance.
Conditional Detail Belongs Outside
The history shows repeated protocol growth followed by trims. Keep the main skill as a router and load focused procedures only when needed.
No Forced Goal Statement
Goal tracking remains available when Adam asks for it. Carmen's normal coordination must not depend on a formal daily objective or Oscar gate.
Observed Evolution
Coordinator foundation. Activation, identity versioning, pronunciation, and mirror rules entered the skill.
Operational hardening. Surface classification, worker naming, approval escalation, dashboard proof, queues, and objective mechanics expanded.
Corrections and trims. The AREA51 activation gate was removed, unnecessary checks were narrowed, and ordinary conversation became direct again.
Canonical-path recovery. Voice sessions exposed catalog and access limits; worker-root and communication rules were clarified.
Current direction. Activation moved to a procedure, the rigid greeting was removed, and the main wrapper is now scheduled for a measured subtraction.