Skip to content

[P2] Org cleanup — archive 64 legacy repos in batches (per org-cleanup-audit.md) #9

@abhicris

Description

@abhicris

Separate org-management session (do not execute from inside abhicris/CR8).

Scope

Per /Users/abhishekkrishna/internal/create-protocol/org-cleanup-audit.md:

  • KEEP PUBLIC (4): console-contracts, .github, research, research-paper-100x
  • KEEP PRIVATE revive (5): rishi-api, createprotocol-api, createprotocol-frontend, createprotocol_org, erc721Ai
  • ARCHIVE forks (6): comgradio, depilot, snsautobase, consoleV2, operator-filter-registry, create-appchain
  • ARCHIVE legacy console era (~40): console-*, mercado*, foodverse*, fitburn*, etc.
  • ARCHIVE legacy CR8 era (~18): create-token, COM-contracts, fine-tuning-*, etc.

Execution rules

  • Archive only, never delete — irreversible, git history matters.
  • Add DEPRECATED notice in each README pointing to this repo / abhicris/CR8 before archiving.
  • Batches of 5. Pause and review after each batch.
  • Update the org .github/README after — pin: console-contracts, research, research-paper-100x, and whatever ends up being the canonical CR8 repo.

Open questions (must answer before archiving)

  1. Which Vercel project serves createprotocol.org, testnet.createprotocol.org, docs.createprotocol.org? Map domain → project → repo before archiving anything.
  2. Is rishi-api salvageable as the Phase 1 compute backend?
  3. Are any private repos under NDA or contractual restriction?
  4. Token-sale repos — were any tokens sold? Regulatory scan before archive.

Label

documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions