Demo data and release scope

The original fictional investor profiles in profiles/, startup scenarios in startups/, and illustrative material in EXAMPLES.md and its generated docs/examples.html and templates/ are provided under the MIT license in LICENSE, to the extent copyright or similar rights are held by the project contributors. The code, documentation and project assets are also distributed under that license, except the separately licensed included research pack and its notices under packs/.

These are invented software examples, not renamed or anonymized real profiles. Their names, preferences, dates, quantities and scenarios do not establish any real investment mandate, offer, historical event, survival outcome or endorsement. Any resemblance to an actual organization is unintended. Illustrative metrics are not benchmarks or targets. Unknown fields remain unknown.

The schema retains retrieved_date and published_date for compatibility. In fictional records these identify the scenario authoring date; they do not claim that external research was retrieved or independently published. Source links point to the included scenario specifications, not fabricated external sources.

No license or permission is granted for third-party articles, scraped material, real-world research records, names, trademarks, or user-supplied data. No ownership is claimed over facts or material outside the contributors' rights. A project license cannot supply rights held by others.

Locally configured Guide Packs retain their publisher's terms. Configuring a package does not apply this project's MIT licence to it. See the user guide for local configuration and browser storage behavior. The pack format is maintained in Guide Pack Kit.

The included reviewed package at packs/guide-pack.json is a convenience copy maintained in the separate research repository. It retains its editorial licence, source bases and third-party notices. Its browser wrapper is the configured local pack. Replacing it changes the active pack; previous pack workspaces remain stored separately. Fictional demo data stays separate. No private archives or raw source material are included. Merely adding attribution or marking a record reviewed does not establish permission.

Build checks validate the included research package and enforce fictional metadata, local provenance links and indexed files for the separate demo. They check release composition; they cannot establish legal rights or detect every instance of copied content. Contributions must be original or accompanied by a documented compatible reuse basis.