markitect-quarkdown/registry/capabilities/capability.communication.markitect-quarkdown-adapter.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.markitect-quarkdown-adapter	Markitect Quarkdown Render Adapter	Concrete Quarkdown render/export adapter for Markitect, mapping Markitect profiles to Quarkdown profiles and running controlled Quarkdown CLI execution plans without forking or reimplementing Quarkdown.	markitect-quarkdown	draft	communication	markitect quarkdown adapter	discovery availability current target confidence rationale D3 D4 medium README documents a precise scope list (adapter descriptor/entry point, profile mapping, controlled CLI execution plans, permission/runtime dependency mapping, generated-artifact validation and checksums, open-reuse integration metadata) and an explicit non-goal (does not reimplement or fork Quarkdown). current target confidence rationale A1 A3 medium Python package (`markitect-quarkdown`) satisfying the Markitect render adapter contract; consumed by markitect-tool as a renderer plugin.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations render.quarkdown adapter descriptor and entry point Quarkdown CLI execution plans with permission/runtime dependency mapping generated artifact validation and checksums level confidence basis known_reliability_risks R0 low consumer_quality_signals tightly coupled to markitect-tool's render adapter contract version	intent includes excludes assumptions use_cases research_memos Let Markitect render/export documents via Quarkdown through a controlled, checksum-validated adapter boundary, keeping Quarkdown-specific runtime assumptions out of markitect-tool itself. Quarkdown render/export adapter Markitect-to-Quarkdown profile mapping controlled CLI execution with permission mapping and artifact checksums Quarkdown itself (not reimplemented or forked) source-format ingestion (see markitect-filter)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Python package (`markitect-quarkdown`) registering the render adapter entry point library import (plugin/entry-point)	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md tests/	recommended_for not_recommended_for known_limitations markitect-tool consumers needing Quarkdown-based rendering/export needs for source-format ingestion (see markitect-filter) or non-Quarkdown renderers tightly coupled to markitect-tool's render adapter contract version

Markitect Quarkdown Render Adapter

Overview

markitect-quarkdown is the concrete Quarkdown render/export adapter for Markitect: it owns profile mapping, controlled CLI execution, and artifact validation, while explicitly not reimplementing or forking Quarkdown itself.

Assessment notes

Discovery

README documents a precise scope list (adapter descriptor/entry point, profile mapping, controlled CLI execution plans, permission/runtime dependency mapping, generated-artifact validation and checksums, open-reuse integration metadata) and an explicit non-goal (does not reimplement or fork Quarkdown).

Availability

Python package (markitect-quarkdown) satisfying the Markitect render adapter contract; consumed by markitect-tool as a renderer plugin.

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