Create a factorization

Build, validate, and download a hierarchy file, then prepare the repository commands needed to compile it.

Guided module · based on docs/factorizations.md and schema/factorization-hierarchy.schema.json

Step 01 · Scaffold

Create the required files

Factorization IDVersion directoryStable version code

Generated pathfactorizations/my-factorization/v1/V10abc_hierarchy.yaml

The same directory also requires a `README.md` describing scope, source, version, and status.

Continue to metadata →

Step 02 · Metadata

Write a complete meta block

Human-readable labelStatusdraftactivedeprecatedCreated byCreated at

Continue to hierarchy →

Step 03 · Hierarchy

Compose the complete hierarchy

Select a node to edit it. Add children at any depth to build the complete tree; siblings are created by selecting their parent and adding another child.

Hierarchy

Selected node

Node kindconceptpartialcollection Partial node IDRequired for partial: stable local identity, independent of the core code. Partial mapping noteOptional: describe the overlap and differences. Level Label Ontology code · search by code or label Concept or partial: select an ontology code. Partial also requires a unique local ID. Collection: enter a unique local code. Provisional placementOptional for any node kind; marks this placement as tentative. Bridge · search by label Select unique labels of other nodes in this hierarchy, including partial and collection nodes. Each selection appears below as a removable chip; bridges document cross-loading and do not create hierarchy edges.

A concept code must reference an existing code from the core ontology.

Add child Remove selected

Continue to validation →

Step 04 · Validate and download

Validate the complete hierarchy file

Validation has not been run.

Validate file Download YAML Download RDF Download diagram JSON Open diagram in viewer

Validation boundaryThe browser validates the generated hierarchy and derived artifacts against the rules available in this website build. Domain review is still required before changing `status` from `draft` to `active`.

Node meaning

Choose concept for the same core concept, including equivalent local wording. Choose partial for partial overlap with an existing core code; it does not assert equivalence, narrower/broader direction, or a reversed pole. Choose collection to group concepts using a local code. The label is the wording shown in this factorization; the core ontology remains unchanged.

For partial, supply a stable alphanumeric id. It identifies the local node independently of its core code. Multiple partial nodes may reference the same core code using different IDs. An optional mapping_note explains which contents overlap and how they differ. IDs must not collide with collection codes. Labels and bridges do not determine identity.