guide-board/registry/capabilities/capability.communication.compliance-evidence-framework.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.communication.compliance-evidence-framework	Certification And Compliance Evidence Framework	Framework that turns standards, conformance, regulatory, and repository-quality claims into structured, reviewable, repeatable, comparable evidence via a pluggable extension architecture.	guide-board	draft	communication	compliance certification evidence extensions	discovery availability current target confidence rationale D2 D4 medium README documents the framework/extension split and a working local baseline (extensions list/validate, profile validate-target/validate-assessment, plan, run); no separate INTENT/SCOPE found. current target confidence rationale A2 A3 medium Dependency-light and runnable today via `PYTHONPATH=src python3 -m guide_board ...`; ships sample profiles and a working plan/run pipeline.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations extension listing/validation target/assessment profile validation plan and run pipeline with sample profiles level confidence basis known_reliability_risks R0 low consumer_quality_signals domain-specific extensions are described as living separately; core repo scope stops at contracts	intent includes excludes assumptions use_cases research_memos Turn certification/compliance claims into structured, repeatable evidence that can be reviewed and compared across assessments, with domain specifics delegated to extensions. framework contracts (targets, assessments, plans, runs) extension listing and validation sample profiles domain-specific compliance extensions themselves (live in separate extension packages)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 Python package (`guide_board`), runnable via `PYTHONPATH=src` cli	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md tests/	recommended_for not_recommended_for known_limitations repos needing a structured compliance/certification evidence pipeline needs where no extension exists yet for the target domain core is intentionally dependency-light; domain coverage depends on which extensions exist

Certification And Compliance Evidence Framework

Overview

guide-board is a certification and compliance preparation framework. The root project owns framework contracts (targets, assessments, plans, runs); domain-specific compliance logic lives in extensions.

Assessment notes

Discovery

README documents the framework/extension split and a working local baseline (extensions list/validate, profile validate-target/validate-assessment, plan, run); no separate INTENT/SCOPE found.

Availability

Dependency-light and runnable today via PYTHONPATH=src python3 -m guide_board ...; ships sample profiles and a working plan/run pipeline.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml