Packs
Contents
Plate data
- Pack types
- 02
- Industry Packs
- 05
- Company Packs
- Private
- Spec
- Super Brain
The idea
The architecture is empty until something fills it.
Super Brain describes the shape of an Industry OS. A Pack is what gets loaded into it.
There are two kinds, and the difference between them is who owns the knowledge.
The formula
Where each part comes from.
The formula
Foundation Model
Industry Pack
Company Pack
Agent Role
Enterprise Agent
The model is bought. The Industry Pack is shared. The Company Pack is private. The agent role is chosen.
Industry Pack
What a sector knows.
- Ontology
- Entities, relationships, events, metrics, rules, workflows, decisions and actions for the industry.
- Knowledge graph
- The structure those declarations describe, populated with industry level facts.
- Reference workflows
- The processes the sector actually runs.
- Agent templates
- Starting manifests with sensible approval boundaries.
- Metrics
- Defined once, so agents cannot disagree about definitions.
- Connectors
- The systems this industry runs on.
- Evaluations
- Test sets, including cases that must fail safely.
- Guardrails
- Regulatory and safety rules, enforced before reasoning completes.
Industry Packs contain nothing proprietary to any one company. That is what makes them shareable.
Company Pack
What one company knows.
- Products and brands
- Yours, with your naming and your hierarchy.
- Customers and territories
- Your structure, not a generic one.
- Policies and SOPs
- Including the ones that exist only as documents.
- Contracts and commitments
- Terms that constrain what can be recommended.
- Business definitions
- What your organisation means by growth, margin, risk and priority.
- Historical decisions
- What you chose before, and what happened next.
A Company Pack is private. It stays inside your boundary, it is never pooled with another company's, and it is never used to improve anything outside your tenant.
The privacy line
Where the line sits.
- Shared
- The ontology of an industry. Its regulations, terminology, workflows and benchmarks.
- Private
- Everything specific to one company.
- Never
- Company knowledge used to train, tune or improve anything outside its own tenant.
The architecture is open. The enterprise intelligence is yours.
The ecosystem
Anyone can publish an Industry Pack.
The analogy is Linux and its distributions, or Kubernetes and its operators. The architecture is the thing that creates the ecosystem.
We maintain five Industry Packs. If you know a sector better than we do, you are better placed to publish its pack than we are.
Plate data
- Pack types
- 02
- Industry Packs
- 05
- Company Packs
- Private
- Spec
- Super Brain
Read next.
- Industry Ontology Schema
- How the ontology inside a Pack is declared.
- IndustryOS Hub
- Published Packs, and the six ways to contribute one.
- For enterprises
- How a Company Pack is grounded, and what stays yours.
- The architecture
- Layer 04, which a Pack fills.
One architecture. Twenty pages. Same document.
Most of the value is in the Company Pack.
The industry knowledge is available. What makes an agent useful is your own context, and that is the part worth talking through.
A conversation, not a demo script. We ask what your systems of record are, what they cannot answer, and which decisions actually matter. If an Industry OS is not the right answer for you, we will say so.