Brand architecture
The portfolio should read as a system, not a collection
The goal is not to make every project look identical. The goal is to make its relationship to the company legible.
Architecture
One parent, two signals
- Point Zero SystemsParent company; corporate identity; ownership and portfolio coherence.
- PointEngineering, developer systems, infrastructure, AI, and machine-facing software.
- OriginShared development stack: tools, systems, capabilities, internal platforms, and reusable developer infrastructure.
- ZeroGames, entertainment, interactive experiences, and publishing.
- Zero DigitalFormal expansion of the Zero entertainment identity when collision avoidance or legal clarity is required.
- PointEngineering, developer systems, infrastructure, AI, and machine-facing software.
Membership
Relationship model
A project can belong to the portfolio in one of three ways:
| Relationship | Role |
|---|---|
| Native umbrella component | A tool, capability, package, or system that primarily exists as part of Origin or Zero. |
| Named system / product | A substantial application or platform with a durable user-facing purpose and its own identity, while still carrying its umbrella affiliation. |
| Adjacent ecosystem product | A product large enough to stand on its own, but designed to integrate with or be built by the relevant umbrella stack. |
Naming
Identity should correspond to a real boundary
Capabilities can exist, mature, and be reused without immediately becoming separate brands.
| Decision | When |
|---|---|
| Keep inside Origin | The work is primarily a capability, internal utility, library, script, CLI, workflow, or composable subsystem. |
| Give it a tool name | A concise name materially improves invocation, documentation, discoverability, or open-source distribution. |
| Give it a system identity | It has a distinct surface, durable architecture, independent lifecycle, and clear user mental model. |
| Let it stand alone | It has its own audience, ecosystem, roadmap, or commercial potential that would be constrained by being treated only as an Origin component. |
In one paragraph
Operating principle
Point Zero Systems is the parent. Point is where systems are built. Zero is where interactive experiences live. Origin provides the shared development substrate; Zero Digital provides the entertainment identity.