Blueprint Core

Blueprint Core is the canonical knowledge repository for the HubZero Blueprint ecosystem.

It captures the engineering philosophy, design direction, architectural thinking, and AI guidance that define how HubZero builds production-ready software.

Unlike a traditional template repository, Blueprint Core contains no production code.

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

Repository Purpose

Blueprint Core exists to answer one question:

How should HubZero think when building software?

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

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

• How HubZero engineers software.
• How HubZero approaches design.
• How HubZero structures different types of websites.
• How HubZero evaluates quality.
• How HubZero maintains consistency while preserving originality.

Repository Structure

blueprint-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 blueprint repositories.

engineering/

Internal documentation describing how Blueprint Core itself evolves.

These documents define engineering workflows, blueprint lifecycle management, and long-term platform maintenance.

They are maintained only within Blueprint Core.

.hubzero/

The published knowledge layer.

This directory is synchronized into every HubZero Blueprint.

It contains only documentation that is directly useful during blueprint development.

It never contains production code.

Relationship Between Repositories

The Blueprint ecosystem consists of three repositories.

Blueprint Core
        │
        │ publishes
        ▼
Blueprint Base
        │
        │ cloned to create
        ▼
Blueprint Repositories

Blueprint Core

Owns the engineering knowledge.

Blueprint Base

Owns the project foundation.

Blueprint Repositories

Own the actual implementation.

The Role of .hubzero

Every Blueprint contains an identical copy of .hubzero.

Developers working inside blueprints should never edit its contents directly.

Changes must always originate from Blueprint Core.

This guarantees that every blueprint shares the same engineering philosophy while remaining visually and functionally unique.

Philosophy

Blueprint 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 Blueprint Core.

Every document should answer one question:

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

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

Versioning

Blueprint Core evolves continuously.

As new blueprints are built, recurring engineering patterns should be extracted into Blueprint Core.

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

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

Guiding Principle

Blueprint 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 Blueprint remains thoughtful, elegant, production-ready, and unmistakably original.