Type Profiles

Overview

Type profiles layer on top of the base Eidos schema. They define what goes inside the envelope:

• Required and optional properties for this type
• Expected relationships
• ID format conventions
• Type-specific validation rules

Profile Naming

Profiles follow the namespace/type@version convention:

arke/collection@v1
arke/file@v1
arke/folder@v1
arke/user@v1
arke/agent@v1
arke/group@v1
arke/chunk@v1

How Profiles Work

When an entity is created or updated:

1. Base Eidos validation runs first (envelope structure)
2. The entity's type field is used to look up the profile
3. Profile-specific validation runs (required properties, relationship rules)
4. If the type is unknown, only base validation applies

Extensibility

You can create new entity types without modifying the base schema:

1. Define a new profile with its validation rules
2. Register it with the profile system
3. Entities with that type will be validated against your profile

The base schema is open for properties, relationships, and types -- only the envelope structure is fixed.

Available Profiles