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

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

• 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