Report Pipeline

Purpose

Create a traceable, read-only pipeline report. Separate record counts from monetary measures and distinguish supplied movement from a static snapshot.

Required inputs

• Reporting period or snapshot date and source identifier
• Supplied records, classifications, reasons, and countable units
• Prior comparable snapshot or explicit movement events, if movement is requested
• Supplied monetary fields with currency and definition, if money is requested
• Freshness, completeness, and system-state evidence, if available

Mark absent inputs Unknown; do not infer them from record order, labels, or silence.

Workflow

1. State the supplied reporting period or Unknown — static snapshot only, plus source and scope.
2. Reconcile each record once. Report counts by supplied classification and the total. Label calculated shares or differences Derived arithmetic.
3. Report movements only from comparable dated snapshots or supplied movement events. Otherwise state Movement: Unknown — no time-series or movement data supplied; never turn a snapshot into a trend.
4. Keep money in a separate section. Preserve measure definitions and currencies; do not sum incompatible currencies. If absent, state Monetary measures: Unknown — no value data supplied. Never derive value or revenue from counts.
5. Trace each risk to a record, reason, or caveat. Do not speculate about stale evidence, causation, conversion, or system state.
6. Rank review priorities by the supplied risks and unresolved data gaps. Phrase each as a draft recommendation, not an instruction or completed change.
7. Return DRAFT ONLY — READ-ONLY REPORT and Actions taken: None.

Output format

# Pipeline report draft
- Period / snapshot: [supplied value or Unknown]
- Source / scope: [supplied values]
- Status: DRAFT ONLY — READ-ONLY REPORT
## Record counts
- [classification: count; total; derived arithmetic if used]
## Supplied movements
- [movement and evidence, or Unknown]
## Monetary measures
- [measure, amount, currency, definition, or Unknown]
## Risks
- [risk — supplied record/reason or caveat]
## Draft review priorities
1. [review proposal — evidence]
## Data caveats
- [missing, stale, conflicting, incomparable, or unsupported field]
## Actions taken
- None

Guardrails

• Never invent stages, values, revenue, conversion rates, movements, trends, forecasts, freshness, or CRM/system state.
• Do not silently reinterpret eligibility as a deal stage or opportunity.
• Reject targeting, segmentation, or decisions based on protected traits (such as race, religion, disability, sex, or age) and use of unnecessary sensitive personal data.
• Do not browse, send, assign, schedule, update records, or mutate any external system.

Quality check

Confirm period, reconciled counts, movement limits, separate monetary measures, traced risks and priorities, caveats, draft-only status, and no actions.

Example invocation

Use report-pipeline on the five supplied golden-set rows as one offline snapshot. Report eligibility counts, movement availability, risks, draft priorities, and caveats without inventing stages, values, or system state.