security: remove sensitive pitch deck materials from public repo

[Copilot]

datacendia-core is public, but docs/pitch-decks/ and public/pitch-decks/ contain investor targeting databases, fundraising terms, personalized outreach templates, and ~1.6 GB of generated decks — none of which belong in an open-source repo.

Changes

• Deleted docs/pitch-decks/ — all generators (CJS/Python), _firms_database.py, email templates, audit/fix scripts, PPTX/HTML/PDF output, screenshots, and all subdirectories (investor/, investor-50/, investor-100/, investor-500/, sales/, design-partner/, gamma/, enterprise/, regional/, pptx/)
• Deleted public/pitch-decks/ — all statically served generated HTML decks and assets
• Added docs/pitch-decks/README.md — placeholder noting materials moved to a private repo
• Updated .gitignore — prevents accidental re-addition:

  # Pitch deck materials (maintained in private repo)
  docs/pitch-decks/**
  !docs/pitch-decks/README.md
  public/pitch-decks/

Retained (platform features, not removed)

• src/pages/pitch/PitchDeck.tsx — interactive React viewer
• src/pages/admin/PitchDeckManagerPage.tsx — admin UI

Note: These files remain in git history. If the fundraising data is considered highly sensitive, a history rewrite (BFG / git filter-repo) should be considered after merge.

Original prompt

Context

datacendia/datacendia-core is a public open-source repository (354 MB) that currently contains sensitive business development materials — pitch decks, investor targeting databases, fundraising details, email outreach templates, and generator scripts. These need to be moved to a new private repository to protect competitive and fundraising information while keeping the platform open source.

What to do

1. Create the migration

Remove the following directories and their contents from datacendia-core, replacing them with a clear README explaining they've moved:

Directories to remove:

• docs/pitch-decks/ — All pitch deck generators (CJS, Python), firm databases (_firms_database.py), email templates (EMAIL-TEMPLATES.md), fix/audit scripts, scaling plans, engine files, screenshots, HTML index, CSS, and all subdirectories (investor/, investor-50/, investor-100/, investor-500/, sales/, design-partner/, gamma/, enterprise/, regional/, pptx/ folders, etc.)
• public/pitch-decks/ — All generated static HTML pitch decks and assets served publicly

Files/components to KEEP in datacendia-core (do NOT remove these):

• src/pages/pitch/PitchDeck.tsx — The interactive React pitch deck viewer (it's a platform feature)
• src/pages/admin/PitchDeckManagerPage.tsx — The admin UI component for managing decks (it's a platform feature)

2. Add a README placeholder

Create docs/pitch-decks/README.md with content like:

# Pitch Decks

Pitch deck materials (generators, templates, investor decks, and sales collateral) are maintained in a separate private repository.

This separation keeps the Datacendia platform fully open source while protecting business development materials.

The interactive pitch deck viewer remains part of the platform at `src/pages/pitch/PitchDeck.tsx`.

3. Add to .gitignore

Add these entries to .gitignore to prevent accidental re-addition:

# Pitch deck materials (maintained in private repo)
docs/pitch-decks/**
!docs/pitch-decks/README.md
public/pitch-decks/

4. Update any references

If the main README.md or other documentation references the pitch decks directory, update those references to note they've been moved to a private repository.

Important notes

• This is a large deletion PR — the pitch deck materials are the dominant contributor to the repo's 354 MB size
• Do NOT remove the React components (PitchDeck.tsx, PitchDeckManagerPage.tsx) — those are platform features
• The commit message should clearly explain WHY materials were removed (security/business sensitivity), not just what was removed

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Should i move the demos to another repo?

Assistant: That's a good question! Let me first look at your repository structure to understand what demos exist and how they relate to the rest of the project.

Assistant: Short answer: No, keep them here. Here's my reasoning:

Why the demos/examples should stay in this repo

1. The repo is a framework/spec, not a large application. Your decision-governance-infrastructure repo is a vendor-neutral governance framework — it's primarily documentation (DGI-Framework-v1.0.md), schemas, API specs, and examples. The examples/ directory is a natural and expected part of a specification repo. Separating it would make the framework harder to understand and adopt.

2. The examples are small and tightly coupled. The examples/ folder contains just 4 files (a sample decision JSON, a decision packet JSON, an integration guide, and a court-admissible PDF) — all directly illustrating how the framework works. They reference the schemas and API definitions in the same repo, so splitting them would create cross-repo dependencies for no real benefit.

3. The overall repo is tiny (~175 KB). There's no bloat concern. Mono-repo separation makes sense when repos become large or have distinct CI/release cycles — neither applies here.

When it would make sense to split

You might consider a separate repo later if you build:

• A runnable demo application (e.g., a web UI or CLI tool that implements the DGI framework end-to-end) — that has its own dependencies, CI pipeline, and release cadence.
• Language-specific SDKs/clients (e.g., dgi-python-sdk, dgi-dotnet-sdk) — those deserve their own repos with their own package publishing workflows.
• A reference implementation with a real database, API server, etc. — that's a separate product from the spec.

Recommended structure going forward

Your current layout is clean and follows the conventions of successful spec/framework repos (like JSON Schema, OpenAPI Spec, etc.):

├── schemas/        ← canonical schema definitions
├── api/            ← API specifications
├── docs/           ← extended documentation
├── examples/       ← usage examples (keep here ✅)
├── DGI-Framework-v1.0.md
└── ...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

*This pull request was created from Copilot chat.*
>