Dr Plan Exists + Compliance Documentation Collector
Enforce Dr Plan Exists using data collected by Compliance Documentation Collector. Automatically check operational readiness standards on every PR.
How Compliance Documentation Collector Powers This Guardrail
The Compliance Documentation Collector gathers metadata from your documentation, security systems. This data flows into Lunar's Component JSON, where the Dr Plan Exists guardrail evaluates it against your standards.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement with actionable feedback.
Quick Start Configuration
Add both the collector and policy to your lunar-config.yml to enable this guardrail.
# Step 1: Enable the Compliance Documentation Collector
collectors:
- uses: github://earthly/lunar-lib/collectors/compliance-docs@v1.0.5
# with: ...
# Step 2: Enable the Compliance Documentation Guardrails
policies:
- uses: github://earthly/lunar-lib/policies/compliance-docs@v1.0.5
include: [dr-plan-exists]
# with: ...
What Compliance Documentation Collector Collects
This collector gathers the following data that the Dr Plan Exists guardrail evaluates.
pentest
Collects penetration-test records from a directory (default: docs/pentests/).
Each record is a Markdown file named for the report date (e.g. 2026-03-14.md
or 2026-03-14-external.md), with optional YAML frontmatter for the provider,
scope and a link to the report. Writes an empty list when there are no records.
Example Data Flow
Here's an example of the data that Compliance Documentation Collector writes to the Component JSON, which Dr Plan Exists then evaluates.
{
"compliance": {
"penetration_testing": {
"reports": [
{
"date": "2026-03-14",
"path": "docs/pentests/2026-03-14.md",
"provider": "Example Security Ltd",
"scope": "Public API, customer web app",
"report_url": "https://grc.example.com/reports/pentest-2026-03-14"
},
{
"date": "2025-03-02",
"path": "docs/pentests/2025-03-02-external.md",
"provider": "Example Security Ltd",
"scope": "External network"
}
]
}
}
}
Configuration Options
Compliance Documentation Collector Inputs
| Input | Required | Default | Description |
|---|---|---|---|
pentest_dir_paths |
Optional |
docs/pentests
|
Comma-separated list of candidate directories for pen-test records (first match wins) |
Compliance Documentation Guardrails Inputs
| Input | Required | Default | Description |
|---|---|---|---|
max_days_since_exercise |
Optional |
365
|
Maximum number of days allowed since the last DR exercise |
plan_required_sections |
Optional |
Overview,Recovery Steps,Contact List
|
Comma-separated list of required sections in the DR plan |
exercise_required_sections |
Optional |
Scenario,Recovery Steps Tested,Participants
|
Comma-separated list of required sections in the DR exercise record |
exercises_check_all |
Optional |
false
|
Check required sections on all exercises (true) or only the latest (false) |
max_days_since_pentest |
Optional |
365
|
Maximum number of days allowed since the latest penetration-test report |
Ready to Automate Your Standards?
See how Lunar can turn your AGENTS.md, engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 300+ built-in guardrails.