Public SEC filings (Form 10) and press releases at the time of each spinoff are the canonical sources. Most teams seed the dataset from a structured pull and then layer in curated commentary, post-split performance summaries, and cross-references over time.

Yes. Add a transaction-type field to each row, and the base page can render a small label distinguishing pure spinoffs from carve-outs and split-offs. Most researchers find the combined cluster more useful than separate page groups by transaction type.

Add a reacquisition field to the row and conditionally render a note on the base page. The URL stays addressable, which is useful because reacquisition outcomes are part of the long-term spinoff record and attract their own ongoing research queries.

Yes. The spinoff row references parent and new-entity slugs that align with brand cluster URLs. The base page renders the links inline, and the brand pages in turn can reference the spinoff slug to complete the bidirectional link graph.

Leave incomplete fields empty on the row. The base page renders the available fields and skips the missing ones gracefully. A spinoff page with only date, parent, entity, and a short summary is still more useful than burying the event in a generic timeline.

Each page carries unique fields like parent, new entity, date, distribution mechanics, and post-spinoff summary. Even minor events meet the threshold for unique content. Pages without enough substance can be skipped rather than published as stubs.

Yes. Field mappings can target chart container elements on the base page. The chart library reads a per-row data URL or symbol pair and renders the dual time series, which is one of the most common visualizations on spinoff reference pages.

Each row can carry an array of resulting entities rather than a single new-entity slug. The base page renders the array as a list of links into the brand cluster. The slug for the routed page can name the parent and the headline split for the title.