Parts

⚠️ Planned for a future release. The parts system (UPCM — Unified Part Configuration Management) is designed but not yet implemented in v0.1.0. This page describes the intended architecture.

Parts will be first-class entities in Arxyne — every physical component, software module, or firmware image will get stable identity, revision tracking, and dependency analysis.

Planned Part Identity

Every part will be defined by a part.yaml sidecar file:

partId: AHMED-BODY-25DEG
revision: 1
partType: physical
category: research_body

Four required fields — everything else is optional metadata that enriches traceability.

Part Types

Parts will carry two orthogonal classifiers:

Classifier	Values	Meaning
Type	physical, software, firmware	What the part is
Role	leaf, assembly	Structural position (leaf = no children)

Planned Capabilities

• Dependency graph — part tree with cycle detection
• Revision tracking — change history per part
• Impact analysis — downstream effects of a revision change
• Product membership — products declare their parts via a manifest
• USD representation — parts authored as prims with arxyne:part:* attributes

See Also

• Design Intent & Targets — targets that parts will bind to
• Core Concepts — the mental model