Define GitHub organization architecture for 60+ repository microkernel ecosystem

[Copilot]

Defines complete repository architecture for ObjectStack's transition from monorepo to distributed microkernel ecosystem. Addresses the question: "如何在一个GitHub组织中创建哪些项目" (How to organize projects in a GitHub organization).

Architecture

7 repository categories, 60+ total repositories:

Protocol Layer (1)          Microkernel Layer (6)         Plugin Layer (50+)
└─ spec                     ├─ core, objectql             ├─ Drivers (12+): postgres, mysql, mongodb, redis...
                            ├─ runtime, client            ├─ Connectors (10+): salesforce, slack, stripe...
                            └─ cli, types                 ├─ Plugins (15+): encryption, cache, multitenancy...
                                                          ├─ Server Adapters (8+): hono, express, nextjs...
                                                          ├─ Templates (10+): crm, helpdesk, hr-system...
                                                          └─ Tools (5+): devtools, vscode-extension...

Naming conventions:

• Core: [name] → @objectstack/[name]
• Drivers: driver-[database] → @objectstack/driver-[database]
• Connectors: connector-[service] → @objectstack/connector-[service]
• Plugins: plugin-[feature] → @objectstack/plugin-[feature]
• Templates: template-[domain] → @objectstack/template-[domain]

Migration Strategy

4-phase extraction from monorepo:

Phase	Timeline	Scope	Count
P0	Q1 2026	Core repositories	7
P1	Q2 2026	Essential drivers (PostgreSQL, MySQL, MongoDB, Redis)	4
P2	Q2 2026	Security/performance plugins	4
P3-P6	Q3-Q4 2026	Connectors, templates, tools	20+

Repository Templates

Each category has standardized structure with CI/CD, testing, docs requirements. Example driver template:

driver-postgres/
├── src/
│   ├── driver.ts              # Implements DriverInterface from @objectstack/spec
│   ├── connection.ts          # Connection pooling
│   ├── query-builder.ts       # SQL generation
│   └── __tests__/
│       ├── unit/
│       └── integration/       # With docker-compose.yml for test DB
├── .github/workflows/
│   ├── ci.yml                 # Lint, typecheck, test, build
│   └── integration-test.yml   # Database integration tests
└── docs/
    ├── CONFIGURATION.md
    └── MIGRATION.md

Governance & Quality

Tier-based ownership:

• Tier 1 (spec, core): Core team only, RFC + voting required
• Tier 2 (objectql, runtime, client, cli): Core + trusted contributors
• Tier 3 (drivers, server plugins): Core + community
• Tier 4 (connectors, templates, tools): Community-led

Quality standards:

• Test coverage: 60-90% (tier-dependent)
• TypeScript strict mode required for core/drivers/plugins
• All repos: CodeQL scanning, Dependabot, signed commits (Tier 1-2)

Deliverables

• ARCHITECTURE_QUICK_REFERENCE.md - Visual overview, 5-min read
• GITHUB_ORGANIZATION_STRUCTURE.md / CN - Complete specification, 849 lines
• PROJECT_STRUCTURE_IMPLEMENTATION_SUMMARY.md - Implementation roadmap with benchmarking against Kubernetes, Salesforce, VS Code, Prisma

Rationale

Why multi-repo over monorepo:

• Independent versioning (plugins evolve at different rates)
• Lower contribution barrier (fork single repo, not entire monorepo)
• Isolated CI/CD (faster feedback, parallel builds)
• Clear ownership boundaries (Tier 1-4 governance model)
• Scalable community growth (40+ community-maintained repos planned)

Benchmarked against:

• Kubernetes: Core vs kubernetes-sigs/* separation, CRD pattern
• Salesforce: AppExchange marketplace model, metadata-driven architecture
• VS Code: Extension marketplace, plugin API design
• Prisma: Schema-first approach, driver abstraction pattern

Original prompt

你是企业管理软件领域的顶级开发工程师师，我编写的是全球企业管理软件的基础规范，采用微内核及插件式设计，按照全球最新最优秀软件的最佳实践，扫描目前完成的所有的协议，请从具体开发实现的角度，包括内核的开发， data, ui, system的子项目开发，以及各个插件的开发，评估如何在一个GitHub组织中创建哪些项目每个项目分别负责做哪些开发的内容以及每一个项目的具体结构。

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	Jan 30, 2026 3:28pm