Repository Split: Open Core and Enterprise

Target structure

• Public repo: OpenArca (Open Core engine + public docs)
• Private repo: OpenArca-Enterprise (commercial extensions)

Why split early

• clear licensing boundary,
• safer contributor model,
• easier public roadmap management,
• cleaner release process for Open Core.

Integration model

Open Core can load enterprise/service overrides via:

• EXTENSIONS_DIR
• EXTENSIONS_OVERRIDES_FILE

This keeps runtime integration explicit and auditable.

Guardrails

• RBAC/security checks stay in Open Core middleware.
• Enterprise code must not bypass Open Core validation gates.
• Capabilities API remains the single runtime feature truth.