Pipeline Help

Checklist, complete workflow, and operational guidance for the Diamond pipeline.

Diamond Rules
Diamond Selection Checklist

Live screening rules loaded from current system settings.

ConditionCurrent Rule
Loading...
Loading...
7-Check Contract
Intended 7-Check Implementation Status

This contract shows what the system is meant to enforce and whether the current implementation is aligned, partial, or still missing.

CheckIntended RuleCurrent SystemDeliveryAlignment
Loading...
Loading...
System Workflow
How The Complete Diamond System Works

This is the detailed lifecycle from raw 52W input to final diamond stock selection.

1. Data Intake

Input enters via manual upload (CSV/XLSX/PDF) or automated BSE fetch. Rows are normalized and validated into canonical fields: security code/name, LTP, 52W high, proximity.

2. Stage-1 Signal Build

Validated rows are persisted and transformed into stage-1 price signals. The pipeline marks initial qualifiers based on nearness to 52-week highs.

3. Fundamentals Enrichment

For qualified symbols, fundamentals are fetched (PE, market cap, growth metrics). This enriches each candidate for valuation and growth checks.

4. News & Announcements Enrichment

News providers and exchange announcements are synced. Positive/negative signals are scored and merged into per-stock context for stage-3 scoring.

5. Management Sync

Structured management signals are pulled from internet sources. The current phase syncs Screener shareholding and document snippets, then parses linked annual reports to populate promoter holding, promoter pledge, board-profile, auditor-event, management-communication, and annual-report review evidence before scoring.

6. Diamond Evaluation

The diamond engine applies configured thresholds and condition weightage (price, PE, market cap, sales growth, news, management quality). Entry value and decision status are computed.

7. LLM Analyst Layer

For shortlisted candidates, LLM enrichment generates fit/summary reasoning. This augments, but does not replace, deterministic filters.

8. Outputs & Monitoring

Results appear in Current Run Table, Watchlist, Dashboard KPIs, and History. Alerts, stale-data checks, and run logs provide operational safety.

9. Manual vs Automated Execution

Manual mode allows step-by-step control. Automated mode executes fetch → fundamentals → news → management → diamond sequentially and updates status live.

Structured Management Inputs
Internet Sync Plus Manual Fallbacks

The current Phase-1 internet sync route pulls Screener shareholding and document snippets into the existing management tables, and now parses the most recent annual reports as the starting point for pledge, board, and promise-keeping evidence. Upload endpoints remain available as fallback when you want to override or backfill a source manually.

/api/v1/sync/management accepts JSON with optional trade_date, max_tickers, and async. It currently syncs promoter holdings, promoter pledge cues, board-profile cues, auditor-event cues, management-communication artifacts, annual-report notes, and annual-report link counts from internet sources.
/api/v1/sync/management/status?job_id=... returns live progress for async management sync runs.
/api/v1/uploads/management/promoter-holdings requires ticker, period, promoter_holding_pct, plus trade_date in the multipart form.
/api/v1/uploads/management/promoter-pledge requires ticker, period, promoter_pledge_pct, plus trade_date.
/api/v1/uploads/management/board-profiles requires ticker, period; optional board strength and director counts are supported.
/api/v1/uploads/management/auditor-events requires ticker, period, auditor_event.
/api/v1/uploads/management/management-guidance requires ticker, period, document_type, guidance_topic, guidance_signal, delivery_status.
/api/v1/uploads/management/annual-report-management requires ticker, period; management, governance, capital allocation labels and note are optional.