---
id: capability.communication.markitect-quarkdown-adapter
name: Markitect Quarkdown Render Adapter
summary: 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.
owner: markitect-quarkdown
status: draft
domain: communication
tags:
- markitect
- quarkdown
- adapter
maturity:
  discovery:
    current: D3
    target: D4
    confidence: medium
    rationale: 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:
    current: A1
    target: A3
    confidence: medium
    rationale: Python package (`markitect-quarkdown`) satisfying the Markitect render adapter contract;
      consumed by markitect-tool as a renderer plugin.
external_evidence:
  completeness:
    level: C1
    confidence: low
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
    - render.quarkdown adapter descriptor and entry point
    - Quarkdown CLI execution plans with permission/runtime dependency mapping
    - generated artifact validation and checksums
    broken_expectations: []
    out_of_scope_expectations: []
  reliability:
    level: R0
    confidence: low
    basis: consumer_quality_signals
    known_reliability_risks:
    - tightly coupled to markitect-tool's render adapter contract version
discovery:
  intent: Let Markitect render/export documents via Quarkdown through a controlled, checksum-validated
    adapter boundary, keeping Quarkdown-specific runtime assumptions out of markitect-tool itself.
  includes:
  - Quarkdown render/export adapter
  - Markitect-to-Quarkdown profile mapping
  - controlled CLI execution with permission mapping and artifact checksums
  excludes:
  - Quarkdown itself (not reimplemented or forked)
  - source-format ingestion (see markitect-filter)
  assumptions: []
  use_cases: []
  research_memos: []
availability:
  current_level: A1
  target_level: A3
  current_artifacts:
  - Python package (`markitect-quarkdown`) registering the render adapter entry point
  target_artifacts: []
  consumption_modes:
  - library import (plugin/entry-point)
relations:
  depends_on: []
  supports: []
  related_to: []
evidence:
  documentation:
  - README.md
  tests:
  - tests/
  consumer_feedback: []
  bug_reports: []
  incidents: []
consumer_guidance:
  recommended_for:
  - markitect-tool consumers needing Quarkdown-based rendering/export
  not_recommended_for:
  - needs for source-format ingestion (see markitect-filter) or non-Quarkdown renderers
  known_limitations:
  - tightly coupled to markitect-tool's render adapter contract version
promotion_history: []
---

# 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

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