Data Schema

Each record in the Dilution dataset represents a single S-1 filing, captured at the time it was filed and enriched with lifecycle and market context.

Unless otherwise noted, fields are point-in-time as of the filing date. Lifecycle fields update as filings resolve.

---

Core Filing Fields

Field	Type	Description
date	string	Filing date (YYYY-MM-DD)
filing_timestamp	string	Exact filing timestamp (Eastern Time)
ticker	string	Stock ticker at filing time
company_name	string	Issuer name
root_file_number	string	SEC registration file number
accession_number	string	Unique SEC accession identifier
filing_url	string	Direct link to the filing on EDGAR

---

Market Context (Point-in-Time)

Field	Type	Description
market_cap_at_filing	float	Market capitalization measured one trading day prior to filing
shares_offered	float	Number of shares registered in the filing

Market context fields are constructed using only information available prior to the filing date to avoid look-ahead bias.

---

Dilution Classification

Field	Type	Description
dilutive	integer	Binary indicator (1 = dilutive, 0 = non-dilutive)
resale	integer	Indicates whether the filing is a resale registration

The dilution label reflects the structural impact of the filing, not subsequent price action.

---

Lifecycle Resolution

These fields update over time as filings resolve.

Field	Type	Description
became_effective	integer	Indicates whether the filing became effective
effective_date	string	Date the filing became effective (YYYY-MM-DD)
days_to_effective	float	Days between filing and effectiveness
offering_withdrawn	integer	Indicates whether the filing was withdrawn
withdrawal_date	string	Date the filing was withdrawn
days_to_withdrawal	float	Days between filing and withdrawal

Lifecycle fields are initially unset and populate only when the corresponding event occurs.

---

Metadata

Field	Type	Description
last_updated	string	Timestamp of the most recent lifecycle update

This field reflects dataset maintenance activity and does not affect historical point-in-time integrity.

---

Notes on Data Behavior

• Records are never removed once published

• Point-in-time fields remain fixed

• Only lifecycle fields update as events occur

• All dates are returned as YYYY-MM-DD strings

This structure ensures the dataset is safe for both historical research and live monitoring.