---
id: capability.infotech.citation-evidence-workspace
name: Citation Evidence Workspace
summary: Document-centered evidence workspace for capturing, managing, presenting, and re-opening citations
  — the umbrella application over the citation-evidence six-package design.
owner: citation-evidence
status: draft
domain: infotech
tags:
- citation
- evidence
- workspace
maturity:
  discovery:
    current: D4
    target: D5
    confidence: medium
    rationale: INTENT.md, wiki/ArchitectureOverview.md, wiki/SharedContracts.md, wiki/DependencyMap.md,
      and ADRs under docs/decisions/ describe the umbrella-first six-package design and partition boundaries
      in detail.
  availability:
    current: A1
    target: A3
    confidence: medium
    rationale: Vite/TS app runnable locally (`npm run dev`/`build`); depends on citation-engine via a
      local workspace link; no hosted deployment yet.
external_evidence:
  completeness:
    level: C1
    confidence: low
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
    - umbrella app wiring citation-engine into a usable workspace
    - documented partition boundaries for future package extraction
    broken_expectations: []
    out_of_scope_expectations: []
  reliability:
    level: R0
    confidence: low
    basis: consumer_quality_signals
    known_reliability_risks:
    - most subsystem partitions still live under src/ pending extraction; only citation-engine has been
      extracted so far
discovery:
  intent: Give users a working evidence workspace today while the six-package design is incrementally
    extracted, keeping citation-engine as the stable shared core.
  includes:
  - document-centered evidence capture, management, and presentation UI
  - wiring to citation-engine
  excludes:
  - subsystems not yet extracted into their own packages (see wiki/DependencyMap.md)
  assumptions: []
  use_cases: []
  research_memos: []
availability:
  current_level: A1
  target_level: A3
  current_artifacts:
  - Vite/TS application, runnable via `npm run dev`
  target_artifacts: []
  consumption_modes:
  - application (local dev server)
relations:
  depends_on: []
  supports: []
  related_to: []
evidence:
  documentation:
  - INTENT.md
  - wiki/ArchitectureOverview.md
  - wiki/SharedContracts.md
  tests:
  - tests/
  - vitest.config.ts
  consumer_feedback: []
  bug_reports: []
  incidents: []
consumer_guidance:
  recommended_for:
  - evaluating or prototyping the citation-evidence workspace UI
  not_recommended_for:
  - production deployment (no hosted build/deployment artifact yet)
  known_limitations:
  - umbrella-first MVP; five of six planned packages remain unextracted
promotion_history: []
---

# Citation Evidence Workspace

## Overview

`citation-evidence` is the umbrella workspace application over a planned six-package design for document-centered citation evidence. `citation-engine` has already been extracted as the shared domain core; remaining partitions stay under `src/` pending extraction.

## Assessment notes

### Discovery

INTENT.md, wiki/ArchitectureOverview.md, wiki/SharedContracts.md, wiki/DependencyMap.md, and ADRs under docs/decisions/ describe the umbrella-first six-package design and partition boundaries in detail.

### Availability

Vite/TS app runnable locally (`npm run dev`/`build`); depends on citation-engine via a local workspace link; no hosted deployment yet.

### 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`