cambium-permissions-log

Log autonomous Cambium actions and approvals to an append-only AUDIT.log.

Updated Aug 23, 2026

Search Tags:#workflow #security #logging #audit #compliance #ai-actions

Ready to run

npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-permissions-log

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cambium-permissions-log
Source: https://github.com/ecnepsyroc-bot/Dejavara/tree/main/deploy/skills/cambium-permissions-log
Command: npx skills add https://github.com/ecnepsyroc-bot/Dejavara --skill cambium-permissions-log

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Cambium Permissions Log provides an auditable, append-only ledger for all autonomous AI actions and explicit human approvals, ensuring traceability and accountability across sessions.

Core Features & Use Cases

Append-only logging of AI actions to AUDIT.log at the repository root.
Explicit approvals captured as EXPLICIT entries before taking actions.
Session lifecycle tracking with SESSION_START and SESSION_END to bound action spans.
Operational discipline that enforces logging before execution and supports verification sessions.

Quick Start

Start a new Claude Code session and log the session scope and initial actions to AUDIT.log before executing any autonomous action.

Frequently Asked Questions about cambium-permissions-log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain an append-only audit log for autonomous AI actions in Claude Code?▼

To maintain an append-only audit log for autonomous AI actions, you need a system that enforces logging to an AUDIT.log file before execution. This approach captures all file actions and explicit human approvals at the repository root for compliance verification.

What is the best way to track session boundaries for AI workflow compliance?▼

Tracking session boundaries for AI workflow compliance requires explicit SESSION_START and SESSION_END markers in your audit log. These markers bound action spans across Claude Code sessions, ensuring every autonomous action is traceable to a specific operational timeframe.

Can I use Claude Code sessions to enforce explicit logging before taking file actions?▼

Yes, you can enforce explicit logging before taking file actions during Claude Code sessions. The operational discipline requires capturing EXPLICIT entries for human approvals and writing actions to the ledger before any autonomous execution occurs.

Does append-only logging work for tracking human approvals across multiple AI sessions?▼

Append-only logging works for tracking human approvals across multiple AI sessions by preventing modifications to past entries. It captures explicit approvals as EXPLICIT entries and uses session lifecycle markers to maintain accountability across different operational contexts.

What are the limitations of using a repository root AUDIT.log for AI action accountability?▼

A repository root AUDIT.log for AI action accountability is limited to tracking file actions and explicit approvals within that specific repository scope. It does not inherently support actions taken outside the repository directory structure or non-file-based operations.

Why does my AI compliance workflow require immediate logging of approvals and session markers?▼

Your AI compliance workflow requires immediate logging of approvals and session markers to satisfy audit-friendly accountability requirements. Enforcing logging before execution ensures a verifiable, append-only record of autonomous actions and human oversight is always available.