Governance Events
Governance events distilled from company 8-K filings and tagged by type: executive changes, auditor changes, restatements, delistings, bankruptcies, shareholder votes and completed mergers.
governance_events — the dataset name to pass to the Obscura API.
What one row means
One governance event disclosed on a company 8-K — a read-only VIEW over `edgar_8k_items` that keeps only the governance-bearing item codes and names each one (executive transition, auditor change, restatement, delisting notice, bankruptcy, shareholder vote, completed merger, charter/bylaw change). The Boardroom-Alpha timeline the console and `/v1/query` read. Derived entirely from public SEC filings — no vendor data.
One row per One row per (accn, item_code) — one governance item on one 8-K accession..
Derived in-database from edgar_8k_items.
Point-in-time availability
Every Obscura dataset carries available_date: the calendar day the publisher made the row
available, day-of, with no session rounding. It is the one column a backtest filters on, and it means the
same thing on every dataset in the catalog.
For governance_events: published: available_date = filed = the 8-K's SEC filing (dissemination) date, inherited from edgar_8k_items. The event is public the moment the filing is.
Schema — 8 columns
The full public column list for governance_events, with the meaning of every field. The same
schema is served unauthenticated at https://api.obscura.trade/v1/catalog/governance_events.
| Column | Type | Description |
|---|---|---|
| cik | bigint · not null | SEC Central Index Key of the filing company; the join key to `edgar_filings`, `edgar_tickers` and the rest of the EDGAR family. |
| display_name | text | Company name as it appears on the filing. |
| filed | date | The 8-K's SEC filing date — when the disclosure reached the public. Equal to `available_date`; kept under its filing-domain name for readability. |
| accn | text · not null | EDGAR accession number of the source 8-K; the provenance key back to the filing itself. |
| item_code | text · not null | The 8-K item number disclosed (e.g. `5.02`, `4.01`, `1.03`). One filing can report several items, so this completes the grain. |
| event_type | text | Plain-language event kind mapped from `item_code`: `executive_transition` (5.02), `auditor_change` (4.01), `restatement` (4.02), `delisting_notice` (3.01), `bankruptcy` (1.03), `shareholder_vote` (5.07), `ma_completed` (2.01), `charter_bylaw_change` (5.03). |
| is_red_flag | boolean | True for the distress-signalling items — auditor change, restatement, delisting notice and bankruptcy — so the red-flag timeline is one filter. |
| available_date | date | PUBLIC-availability date = the 8-K's filing date. The point-in-time column to filter, order and join on. |
Access governance_events
Two delivery paths, one identifier. Both require an Obscura account and an active subscription; the catalog entry and the schema above are public.
import obscura
client = obscura.Client("obs_live_…")
df = client.query(
dataset="governance_events",
symbols=["NVDA", "AAPL"],
start="2024-01-01",
)
Create a free account Browse all 95 datasets
Frequently asked questions
What is in the governance_events dataset?
Governance events distilled from company 8-K filings and tagged by type: executive changes, auditor changes, restatements, delistings, bankruptcies, shareholder votes and completed mergers. One governance event disclosed on a company 8-K — a read-only VIEW over `edgar_8k_items` that keeps only the governance-bearing item codes and names each one (executive transition, auditor change, restatement, delisting notice, bankruptcy, shareholder vote, completed merger, charter/bylaw change). The Boardroom-Alpha timeline the console and `/v1/query` read. Derived entirely from public SEC filings — no vendor data.
How do I avoid look-ahead bias with governance_events?
Filter on governance_events.available_date, the day the publisher made the row public. For this dataset that date is derived as follows — published: available_date = filed = the 8-K's SEC filing (dissemination) date, inherited from edgar_8k_items. The event is public the moment the filing is. A query of the form WHERE available_date <= '<as-of date>' never sees a row before it existed.
In what formats can I get governance_events?
As a Parquet bulk export (POST https://api.obscura.trade/v1/download) or as JSON from the typed query API (POST https://api.obscura.trade/v1/query), both with dataset="governance_events". The column schema is public at https://api.obscura.trade/v1/catalog/governance_events.
Can I filter governance_events by company or symbol?
Yes. governance_events carries cik, the column the API's symbols filter resolves against.