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>
This commit is contained in:
2026-07-06 19:03:42 +02:00
parent 854b8492af
commit 821289b37a
2 changed files with 135 additions and 2 deletions

View File

@@ -0,0 +1,118 @@
---
id: capability.infotech.email-connector
name: Mailbox Evidence Scanner (email-connect)
summary: Headless, provider-neutral email communication and evidence service; first slice scans a mailbox
or fixture directory and produces timestamped CSV evidence reports.
owner: email-connect
status: draft
domain: infotech
tags:
- email
- evidence
- coordination
maturity:
discovery:
current: D2
target: D4
confidence: medium
rationale: README documents the Mailbox Evidence Scanner MVP slice and explicitly disclaims overclaiming
delivery/awareness/coordination success; a coordination-engine adapter contract exists (spec/).
availability:
current: A1
target: A3
confidence: medium
rationale: Runnable today via `PYTHONPATH=src python3 -m email_connect.cli`; local SQLite state and
CSV report output; no packaged distribution or hosted service.
external_evidence:
completeness:
level: C1
confidence: low
basis: scope_vs_intent_and_consumer_expectations
satisfied_expectations:
- mailbox/fixture scanning with classification and CSV report generation
- expected-recipient diffing with known_recipient/undef.no_signal diagnostics
broken_expectations: []
out_of_scope_expectations: []
reliability:
level: R0
confidence: low
basis: consumer_quality_signals
known_reliability_risks:
- first implementation slice only; broader email-connector scope from INTENT not yet built
discovery:
intent: Provide provider-neutral email-channel evidence (has this address been reached? what signal
exists?) without overclaiming delivery or awareness.
includes:
- mailbox/fixture scanning and classification
- CSV evidence report generation
- coordination-engine adapter contract
excludes:
- actually sending email (evidence/scanning only in this slice)
- delivery or awareness guarantees
assumptions: []
use_cases: []
research_memos: []
availability:
current_level: A1
target_level: A3
current_artifacts:
- Python CLI module (`email_connect.cli`)
target_artifacts: []
consumption_modes:
- cli
relations:
depends_on: []
supports: []
related_to: []
evidence:
documentation:
- README.md
tests:
- tests/
consumer_feedback: []
bug_reports: []
incidents: []
consumer_guidance:
recommended_for:
- needs for email-channel evidence scanning without delivery guarantees
not_recommended_for:
- needs requiring actual outbound email sending (not in this slice)
known_limitations:
- MVP slice; state is local SQLite, not shared/service-backed yet
promotion_history: []
---
# Mailbox Evidence Scanner (email-connect)
## Overview
`email-connect` is a headless, provider-neutral email evidence service. Its first slice, the Mailbox Evidence Scanner, scans a mailbox or fixture directory, classifies inbound evidence, and produces timestamped CSV reports without overclaiming delivery or coordination success.
## Assessment notes
### Discovery
README documents the Mailbox Evidence Scanner MVP slice and explicitly disclaims overclaiming delivery/awareness/coordination success; a coordination-engine adapter contract exists (spec/).
### Availability
Runnable today via `PYTHONPATH=src python3 -m email_connect.cli`; local SQLite state and CSV report output; no packaged distribution or hosted service.
### 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`

View File

@@ -1,4 +1,19 @@
version: 1
updated: '2026-06-16'
updated: '2026-07-06'
domain: helix_forge
capabilities: []
capabilities:
- id: capability.infotech.email-connector
name: Mailbox Evidence Scanner (email-connect)
summary: Headless, provider-neutral email communication and evidence service; first slice scans a mailbox
or fixture directory and produces timestamped CSV evidence reports.
vector: D2 / A1 / C1 / R0
domain: infotech
status: draft
owner: email-connect
path: registry/capabilities/capability.infotech.email-connector.md
tags:
- email
- evidence
- coordination
consumption_modes:
- cli