Files
citation-evidence/registry/capabilities/capability.infotech.citation-evidence-workspace.md
tegwick c292afff6d Draft capability entry (reuse-surface REUSE-WP-0017-T04, cohort 1)
Honest first-pass maturity vector grounded in README/docs/tests present
in this repo; no invented evidence. Flagged for human review before
publish. See reuse-surface history/2026-07-06-coverage-classification.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-06 19:03:42 +02:00

4.0 KiB

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

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

  • 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