Skip to main content
Pinega
Use dark themeMenu

Explanation

Pinega programme model

Pinega is intentionally broader than one repository, storage engine, or research paper. The hierarchy keeps research evidence, reusable engineering, technology programmes, and future commercial offerings connected without pretending that they are the same thing.

Four connected layers

  1. Research: concurrency, transactions, distributed systems, database architecture, verification, optimisation/AI, and performance engineering.
  2. Engineering platform: libraries, benchmarks, semantic models, build/test infrastructure, documentation, design tokens, diagrams, and reproducible workflows.
  3. Technology and products: engine, optimiser, verification, observability, and developer-tool directions that graduate only when implementation evidence exists.
  4. Company and brand: Pinega as master brand; Pinega Labs as the working research/engineering and possible future company identity.

Why the names stay distinct

Pinega Engine can adopt work from the research and engineering layers without becoming the identity of the whole programme. Likewise, an optimiser or verification tool can share Pinega infrastructure without being forced into the Engine executable or roadmap.

This separation also protects public claims: a research result can be real and valuable before it becomes a product capability, while a technology programme can have accepted architecture before its production implementation exists.

Pinega Labs boundary

Pinega Labs is currently a working research and engineering identity and a plausible future company identity. The public site must not imply registration, customer contracts, support availability, or a shipped commercial product unless those facts later become true and visible.

What documentation should mirror

Documentation follows user needs rather than repository directories. A contributor should be able to find a task procedure without first understanding internal file layout; a researcher should be able to trace evidence without navigating product marketing; a future user should eventually find product instructions without being sent through contributor tooling.