Logging & Path Privacy controls
Relevant source files
The following files were used as context for generating this wiki page:
Logging and Path Privacy controls in Delano are designed to ensure that the shared runtime and local delivery contracts remain secure and private. These controls prevent the accidental leakage of sensitive information, such as raw agent prompts or local absolute file paths, into the repository's permanent records. The system utilizes privacy-safe defaults for prompt and log handling, which are enforced through various validation scripts and hooks within the .agents/ runtime.
The primary objective is to maintain a "Local Dossier" posture where provenance and evidence are clear, but local environment details and raw model interactions are strictly guarded. This is critical because Delano acts as an agent-agnostic runtime where multiple tools and operators interact with the same file-backed contracts.
Sources: README.md:14-16, README.md:275-277, AGENTS.md:38-42
Privacy-Safe Logging Architecture
The logging architecture focuses on "metadata-only" capture for delivery metrics and gated access for prompt logging. The system distinguishes between public delivery evidence (stored in .project/) and internal runtime logs (stored in .agents/logs/).
Log Safety Enforcement
Delano employs specialized scripts and hooks to monitor and sanitize output before it is committed or displayed.
check-log-safety.sh: A shell script used to verify that committed logs do not contain raw prompts or non-compliant data.check-text-safety.mjs: A utility that scans files for bidirectional (Bidi) control characters (like U+202E) that could be used for malicious text obfuscation or path manipulation.- Prompt Logging: Raw prompts are treated as "opt-in only." By default, logs must be privacy-safe to pass validation gates.
Sources: README.md:275-277, AGENTS.md:38-40, assets/install-manifest.json:84, test/package.test.js:237-251
Delivery Metrics and Events
Delivery metrics are designed to be privacy-safe by being "metadata-only." This ensures that while progress and performance can be tracked, the specific content of the work remains within the appropriate boundaries.
The diagram shows the flow of event data through privacy filters to ensure only metadata is used for metrics.
Sources: assets/install-manifest.json:45-47, test/package.test.js:315-325
Path Privacy Standards
Path privacy controls prevent the leakage of local absolute paths (e.g., /Users/username/repo/...) into documentation, contracts, or hook output. Instead, Delano mandates the use of relative paths anchored to the repository root.
Enforcement Mechanism
Path standards are enforced through automated scripts during the delano validate cycle:
check-path-standards.sh: Scans the project for absolute path patterns.fix-path-standards.sh: Provides automated remediation for identified path leaks.- Path-Output Safety: Validation gates check that command outputs and generated files adhere to relative path standards.
Sources: README.md:275-277, AGENTS.md:41, assets/install-manifest.json:85-87
Component Summary
| Component | File Path | Role |
|---|---|---|
| Path Standards Rule | .agents/rules/path-standards.md | Canonical rules for path formatting. |
| Log Safety Check | .agents/scripts/check-log-safety.sh | Verifies logs are free of raw prompts. |
| Text Safety Check | .agents/scripts/check-text-safety.mjs | Detects dangerous Bidi characters. |
| Path Validator | .agents/scripts/check-path-standards.sh | Identifies absolute path leaks. |
| Metrics Summarizer | .agents/scripts/summarize-project-metrics.mjs | Generates privacy-safe metrics. |
Sources: assets/install-manifest.json:29, assets/install-manifest.json:84-86, test/package.test.js:237, test/package.test.js:321
Validation Flow
The validate command acts as the central gatekeeper for privacy controls. It aggregates multiple specialized checks to ensure the repository state is compliant before it is considered ready for release or sync.
The sequence diagram illustrates how delano validate coordinates multiple privacy and safety scripts.
Sources: README.md:273-282, .agents/scripts/README.md
Conclusion
Logging and Path Privacy controls are integral to Delano's commitment to traceable yet secure delivery. By enforcing relative pathing and strictly managing log content, the system ensures that the "Local Dossier" remains portable and free of sensitive environment-specific leaks. These controls are not merely recommendations but are enforced by the core validate runtime, making compliance a prerequisite for task completion.
Sources: README.md:14-16, AGENTS.md:38-42