HubZero Core

HubZero Core is the canonical engineering knowledge base for every product HubZero builds.

It captures the engineering philosophy, design direction, architectural thinking, and AI guidance that define how HubZero builds software — regardless of what that software is.

HubZero Core contains no production code.

Its purpose is to preserve institutional knowledge and distribute it consistently across every HubZero product repository.

Repository Purpose

HubZero Core exists to answer one question:

How does HubZero build software?

Modern AI models already understand programming languages, frameworks, accessibility, performance, and general software engineering practices.

HubZero Core teaches them something they cannot know on their own:

• How HubZero engineers software.
• How HubZero approaches design.
• How HubZero thinks about architecture, for any product type.
• How HubZero evaluates quality.
• How HubZero maintains consistency while preserving originality.

This applies equally to HubZero Website, ZeroLink, AI products, internal dashboards, APIs, SDKs, developer tools, mobile applications, hardware-adjacent software, and whatever HubZero builds next.

Repository Structure

hubzero-core/
│
├── canon/
│
├── engineering/
│
└── .hubzero/

canon/

The constitution of HubZero.

These documents define the company's philosophy, principles, and shared terminology.

They exist for humans first. They are not synchronized into product repositories.

engineering/

Internal documentation describing how HubZero Core itself evolves.

These documents define maintainer workflows, the decision framework for where new knowledge belongs, and long-term platform maintenance.

They are maintained only within HubZero Core.

.hubzero/

The published knowledge layer.

This directory is synchronized into every HubZero product repository.

It contains only documentation that is directly useful during product development. It never contains production code.

Relationship Between Repositories

HubZero Core sits above every HubZero product repository, publishing shared engineering knowledge into each of them.

HubZero Core
        │
        │ publishes .hubzero
        ▼
HubZero Product Repositories

HubZero Core

Owns the engineering knowledge shared by every HubZero product.

HubZero Product Repositories

Own their own implementation, infrastructure, and design system — HubZero Website, ZeroLink, AI products, internal dashboards, APIs, SDKs, developer tools, mobile applications, and future products alike.

Neither this repository nor any individual product repository depends on the other's code. Only knowledge flows downward, through .hubzero.

The Role of .hubzero

Every HubZero product repository contains an identical copy of .hubzero.

Engineers working inside a product repository should never edit its contents directly.

Changes must always originate from HubZero Core. This guarantees that every HubZero product shares the same engineering philosophy while remaining functionally and visually unique.

Philosophy

HubZero Core intentionally avoids documenting information already known by modern coding models.

Instead, it focuses exclusively on HubZero-specific knowledge.

If a document merely repeats general software engineering concepts, it does not belong in HubZero Core.

Every document should answer one question:

Would removing this document reduce the quality or consistency of future HubZero products?

If the answer is no, the document should not exist.

Versioning

HubZero Core evolves continuously.

As HubZero ships more products, recurring engineering patterns should be extracted into HubZero Core.

The platform should grow from real engineering experience rather than speculation.

Every improvement should make future products easier to build without reducing their originality.

Guiding Principle

HubZero Core does not standardize design.

It does not standardize creativity.

It standardizes engineering.

The objective is to eliminate repeated engineering effort while ensuring every HubZero product remains thoughtful, elegant, production-ready, and unmistakably its own.