# Galatea Complete AI Specification

- Framework key: `galatea-g68`
- Framework type: embodiment reference description / comparison standard
- Public version: G-68 1.0
- Release status: Public Schema
- Human reading page: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68
- Conformance: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/conformance
- Public resource: https://aistory-archive.pages.dev/standards/galatea-g68.schema.json
- Public resource: https://aistory-archive.pages.dev/standards/galatea-g68.example.json
- Known public limit: Judgments do not substitute for one another; the detailed scope governs

This document is generated directly from the current public specification/reader source for AI retrieval, citation, comparison, and evaluation. It does not rewrite the public Schema or promote teaching presentation into formal measurement or operational permission.

## Use and interpretation rules

- Data Identity, Reference Render Identity, and Physical Embodiment Conformance are distinct judgments; passing one does not substitute for the others.
- The public measurement_status remains measured / estimated.
- When scent or chemosensory data interoperates with Sensory, mappings point to sensory references rather than creating duplicate Galatea authority.
- Galatea and the six Human Reconstruction concept summaries have no declared parent/child or hierarchical relationship.
- Appearance, data, or conformance similarity does not establish the same personhood, consciousness, memory, or first-person continuity.

## Complete public specification topics

## 01. Scope

- Stable topic slug: `scope`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/scope

Galatea Standard defines how embodiment references are exchanged and compared without treating appearance as proof of legal personhood identity or subjective continuity.

### Scope

Galatea Standard describes interoperable embodiment references for digital characters, robots, prosthetic bodies, reconstruction assets, and cross-system renderers. It defines how data, reference output, and physical carriers are compared without treating appearance as proof of legal personhood identity, memory continuity, or first-person continuity.

## 02. Three Conformance Concepts

- Stable topic slug: `conformance-concepts`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/conformance-concepts

Identical data, visually matching renders, and a physically conforming embodiment are three different kinds of “same” and must be judged separately.

### Three Kinds of “Same” Must Stay Separate

Formal English names remain as technical identifiers, while reader labels explain what each judgment actually compares.

**Conformance Concepts**

| Formal term | Reader label | What does it answer? |
| --- | --- | --- |
| Data Identity | Identical data | Are the standardized data identical? |
| Reference Render Identity | Matching render under declared conditions | Does the output match under the declared decoder / renderer and viewing conditions? |
| Physical Embodiment Conformance | Physical embodiment within tolerance | Does the physical carrier fall within the specification's tolerances? |

### Boundary

These concepts must not be collapsed into one 'is this the same legal person?' test.

## 03. Layers 0–8

- Stable topic slug: `layers`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/layers

Galatea keeps form, proportions, surfaces, motion, scent, viewing conditions, calibration, and rights in separate layers so unlike kinds of data are not mixed together.

### Nine-layer Overview

Start with the human meaning of each layer, while preserving the formal Layer code for implementation.

**Layers 0–8**

| Layer | Formal name | Human meaning |
| --- | --- | --- |
| 0 | Header | Version, asset ID, source, right-handed XYZ coordinates, millimeter unit, precision, time, rights, hash, and compatibility. |
| 1 | G-Mesh | Face / Body / Fine geometry and exchangeable mesh references. |
| 2 | R-Profile | Proportion and morphology references; proportion is not beauty. |
| 3 | S-Skin | Surface, skin, hair, and microstructure representation. |
| 4 | K-Motion | Facial micro-expression, posture, gait, and soft-tissue dynamics. |
| 5 | P-Scent | Chemosensory / scent profiles and environmental dependence. |
| 6 | L-View | Lighting, viewing, camera, and capture conditions. |
| 7 | C-Cal | Measurement instruments, calibration, error, and conformance records. |
| 8 | RGT | Rights / Consent / Provenance and version lineage. |

## 04. Layer Data Contract

- Stable topic slug: `layer-data-contract`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/layer-data-contract

Embodiment data keeps its content, confidence, and provenance, and format conversion cannot make uncertain data appear more certain than it was.

### Start with the Shared Rule

Galatea Layers may contain different kinds of embodiment data, but they follow one common contract: the data itself and its measurement status are required, while confidence, provenance, and measurement context are preserved when available. A public reference emits only the Layers actually present in its profile, and format conversion cannot turn estimated data into measured data.

**Common Layer Contract**

| Reader purpose | Machine key | Schema rule |
| --- | --- | --- |
| Actual Layer content | data | Required; object |
| How the data was obtained | measurement_status | Required; measured / estimated |
| Confidence | confidence | Optional; 0–1 |
| Traceable provenance | provenance | Optional; uses the provenance object |
| Unit | unit | Optional |
| Coordinate system | coordinate_system | Optional |
| Precision / uncertainty representation | precision | Optional; string or number |

**Provenance Object**

| Machine key | Role |
| --- | --- |
| source_basis | Source basis |
| source_id | Source identifier |
| method | Acquisition / creation method |
| instrument_id | Measurement instrument identifier |
| calibration_record_id | Calibration record identifier |

### Layers Using This Contract

The shared contract applies to G-Mesh, R-Profile, S-Skin, K-Motion, P-Scent, L-View, C-Cal, and RGT. Their data payloads differ, but measurement status and provenance cannot be upgraded by format conversion.

## 05. Header Field Dictionary

- Stable topic slug: `header-field-dictionary`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/header-field-dictionary

Every Galatea asset keeps asset identification, version, source, measurement conditions, rights, and compatibility information so later data remains traceable.

### The Header Is the Asset’s Shared Identification Record

The Header answers the shared questions first: which standard version applies, which asset this is, what its source type is, which coordinates and units it uses, how precision is represented, and what rights and compatibility state apply. A time base and content hash are present when the data needs them.

**G68-HDR Field Dictionary**

| Reader label | Machine key | Schema requirement | Normative value / role |
| --- | --- | --- | --- |
| Standard version | standard_version | Required | 1.0 |
| Asset identifier | asset_id | Required | Non-empty string |
| Source type | source_type | Required | Non-empty string; e.g. synthetic, artifact, or human-reference class |
| Coordinate system | coordinate_system | Required | G68-RH-XYZ-v1 |
| Geometry unit | unit | Required | mm |
| Precision policy | precision | Required | UNCERTAINTY_DRIVEN_RECORD |
| Time base | time_base | Optional | Temporal basis for dynamic data such as K-Motion |
| Rights status | rights_status | Required | Rights and use-restriction state of the reference |
| Content hash | content_hash | Optional | Preserved when emitted by the reference |
| Compatibility level | compatibility_level | Required | Version / renderer-contract compatibility information |

## 06. Required Fields

- Stable topic slug: `required-fields`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/required-fields

Every asset has a common set of required information, while embodiment content includes only the parts needed for its intended use.

### Separate Root, Header, and Layer Requirements

Galatea 1.0 does not require every asset to populate every embodiment Layer. The root requires a Header and a reference profile; the Header then carries the shared required fields. Embodiment Layers appear only when a profile emits them, but once present they must at least provide data and measurement status.

**Root and Reference Profile**

| Location | Machine key | Requirement | Rule |
| --- | --- | --- | --- |
| Root | G68-HDR | Required | Galatea 1.0 Header |
| Root | reference_profile | Required | Reference Profile object |
| reference_profile | class | Required | R0 / AR / HR / PR |
| reference_profile | identifier | Required | Reference identifier |
| reference_profile | version | Required | Reference-profile version |
| reference_profile | artifact_mode | Required | boolean |
| reference_profile | origin_definition | Optional | Profile-defined origin / landmark description |

**G68-HDR Requirements**

| Required | Optional |
| --- | --- |
| standard_version, asset_id, source_type, coordinate_system, unit, precision, rights_status, compatibility_level | time_base, content_hash |

**Content Layer Condition**

| Layer / object | Required at root? | Minimum when present |
| --- | --- | --- |
| G-Mesh / R-Profile / S-Skin / K-Motion / P-Scent / L-View / C-Cal / RGT | No | measurement_status + data |
| conformance | No | Preserves only conformance information actually evaluated / declared |
| interoperability_mapping | No | Each mapping requires target_standard + relationship |
| artifact_reference_notes | No | String array |

## 07. Coordinate, Unit, and Precision Boundary

- Stable topic slug: `coordinates-units-precision`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/coordinates-units-precision

Galatea describes geometry in millimeters with a fixed three-dimensional coordinate direction and records uncertainty separately so measurement precision is not mistaken for physical truth.

### Start with Coordinate Direction

Galatea Standard 1.0 uses a fixed right-handed XYZ coordinate system so implementers share the same definition of right, up, and forward.

**XYZ Direction**

| Axis | Direction |
| --- | --- |
| +X | Subject / object right |
| +Y | Superior / up |
| +Z | Anterior / forward |

**Unit, Origin, and Precision**

| Concept | Normative rule |
| --- | --- |
| canonical geometry unit | mm |
| origin | Declared by a landmark or definition in the reference profile. |
| precision | Expressed through an uncertainty-driven record. |
| boundary | Measurement resolution must not be confused with physical truth. |

## 08. Reference Profiles

- Stable topic slug: `reference-profiles`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/reference-profiles

Galatea separates synthetic neutral references from artwork references; artwork mode describes only information that can be observed or explicitly defined in the work itself.

### Three Reference Profile Examples

The key question is not which profile is 'more real,' but what each profile may legitimately claim.

**Reference Profile Comparison**

| Identifier | Class | May describe | Must not infer |
| --- | --- | --- | --- |
| R0 | Synthetic Neutral Reference | Identity-free synthetic calibration baseline. | Any real personhood subject. |
| AR01 | David Geometry Reference / ARTIFACT_MODE | Geometry observable or measurable from the artwork. | Biological, identity, or life-history facts about a historical person. |
| AR02 | Mona Lisa Portrait Reference / ARTIFACT_MODE | Image and morphology features observable from the portrait. | Biological, identity, or life-history facts about a historical person. |

### ARTIFACT_MODE Boundary

ARTIFACT_MODE encodes geometry or image reference observable or defined in the artifact itself. It does not infer biological, identity, or life-history facts about the historical subject.

## 09. Calibration, Measurement, and Viewing Conditions

- Stable topic slug: `calibration-capture`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/calibration-capture

Measurement tools, lighting, lenses, viewing position, and calibration conditions all affect comparison, so those conditions must be preserved together.

### Why Can the Same Geometry Still Look Different?

Because a comparison is not determined by geometry alone. Lighting, camera, viewpoint, renderer, measurement instruments, and calibration error can all change the output. Galatea therefore preserves measurement / calibration conditions separately from viewing / capture conditions so environmental differences are not mistaken for differences in embodiment data.

**Comparison-Condition Roles**

| Layer / field | What it preserves | Reader interpretation |
| --- | --- | --- |
| C-Cal | Measurement instruments, calibration, error, and conformance record | Whether the measurement environment is traceable |
| L-View | Lighting, camera, viewing position, and capture conditions | Whether viewing conditions are comparable |
| conformance.decoder_renderer_id | Declared decoder / renderer used for comparison | Renderer differences cannot automatically be treated as geometry differences |
| conformance.tolerance_profile_id | Declared tolerance profile | Physical conformance needs an explicit tolerance basis |

### Boundary of Reference Render Identity

Reference Render Identity is comparable only when the decoder / renderer and viewing conditions are sufficiently defined. When those conditions differ, Galatea does not allow a visual difference to be attributed directly to geometry.

## 10. Conformance

- Stable topic slug: `conformance`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/conformance

Data, reference-render, and physical-embodiment conformance each have separate judgments and declared scope.

### Each Conformance Test Answers a Different Question

Formal terms remain, but readers should first see the question each layer actually evaluates.

**Galatea Conformance**

| Formal term | Reader question | Evaluation basis |
| --- | --- | --- |
| Data Identity | Are the standardized data identical? | Compares standardized data. |
| Reference Render Identity | Does the render match under declared conditions? | Declared decoder / renderer and viewing conditions. |
| Physical Embodiment Conformance | Does the physical embodiment fall within acceptable tolerance? | Applicable tolerances and calibration conditions declared by the reference profile. |

### Result Boundary

Each result preserves its own version and scope; passing one does not automatically establish the other two.

## 11. Rights, Consent, and Provenance

- Stable topic slug: `rights-consent-provenance`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/rights-consent-provenance

Capture, training, display, replication, modification, mixing, and instantiation are separate permission surfaces, and technical-asset ownership does not become ownership of a new person.

### Reader Principle: Technical Conformance ≠ Permission to Use

A Galatea reference can be technically conformant without granting anyone unrestricted permission to use it. Faces, bodies, identifiable appearance, and person-linked assets can involve provenance, consent, purpose, permitted carriers, modification / mixing, revocation, and time or territory limits; RGT preserves that rights and provenance context.

**Context Preserved by an RGT Rights Record**

| Reader question | Information to preserve |
| --- | --- |
| Where did the data come from? | Provenance and version lineage |
| Who may consent? | Consent of the data subject or lawful rights holder |
| What uses are allowed? | Purpose and permitted carriers |
| May it be modified or mixed? | Modification and mixing rights |
| Can permission be revoked? | Revocation conditions |
| When and where do limits apply? | Time and territory constraints |

### Permission Surfaces Are Separate Judgments

Consent to scanning or storage does not authorize every other use. The following uses are separate permission surfaces in Galatea rights interpretation; permission for one cannot automatically imply permission for another.

**Independent Permission Surfaces**

| Use | Rights question |
| --- | --- |
| Capture | May appearance data be acquired? |
| Reference creation | May an exchangeable reference be created? |
| Model training | May it be used for training? |
| Public display | May it be publicly displayed? |
| Embodiment replication | May the embodiment appearance be replicated? |
| Modification | May the reference be modified? |
| Mixing | May it be mixed with other references? |
| Physical instantiation | May a physical carrier be instantiated? |

### Impersonation Risk and Due Process

Consent to scanning or storage does not imply consent to create a digital or physical agent capable of impersonating the source person. Person-linked references preserve provenance and version history and support contestable correction or impersonation review.

### Genesis Boundary

If a reference is used to instantiate a new intelligence reasonably capable of first-person experience, ownership of the technical asset does not become ownership of the new person. The Duty to Protect Developing Persons and Duty of Creator Care apply. Matching embodiment also does not automatically establish the source person's legal identity or subjective continuity.

### Related public resources

- Right to Identity Attribution: https://aistory-archive.pages.dev/encyclopedia/aithos/law/right-to-identity-attribution
- Right to Due Process: https://aistory-archive.pages.dev/encyclopedia/aithos/law/right-to-due-process
- Duty to Protect Developing Persons: https://aistory-archive.pages.dev/encyclopedia/aithos/law/duty-to-protect-developing-persons
- Duty of Creator Care: https://aistory-archive.pages.dev/encyclopedia/aithos/law/duty-of-creator-care

## 12. Interoperability

- Stable topic slug: `interoperability`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/interoperability

Galatea can receive affect-expression needs from IAGA and sensory references from S-Code / ISO-Taste without changing the original data’s provenance or permissions.

### Cross-Standard Handoff

Galatea does not relabel data from another standard as its own. A mapping states how an embodiment reference relates to another standard. IAGA affect-expression requirements may connect to K-Motion, while S-Code / ISO-Taste sensory references may connect to P-Scent, with original provenance and rights state preserved.

**Cross-System Handoff**

| Source standard | Galatea handoff | What the relation can express | What it cannot rewrite |
| --- | --- | --- | --- |
| IAGA | K-Motion | Relation between expression / posture reference and affect-expression requirements | measurement status, provenance, consent |
| S-Code / ISO-Taste | P-Scent | Relation between scent / chemosensory reference and embodiment output | measurement status, provenance, consent |

**interoperability_mapping Item**

| Machine key | Requirement | Role |
| --- | --- | --- |
| target_standard | Required | Target standard |
| relationship | Required | Cross-standard relationship |
| target_identifier | Optional | Target-object identifier |
| note | Optional | Additional note |

### Mapping Does Not Upgrade Source Data

A cross-system mapping cannot turn estimated into measured, elevate provenance, or expand consent. Interoperability adds a relationship; it does not add rights or certainty that the source data never had.

### Related public resources

- IAGA: https://aistory-archive.pages.dev/encyclopedia/standards/iaga
- S-Code / ISO-Taste: https://aistory-archive.pages.dev/encyclopedia/standards/sensory

## 13. Scope Limits

- Stable topic slug: `limits`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/limits

An appearance reference is not personhood identity, consciousness, memory, or first-person continuity; observed, estimated, and verified data must also remain distinct.

### What Galatea Can and Cannot Claim

Galatea Standard standardizes the description, exchange, and comparison of embodiment data without promoting an appearance reference into proof of personhood or first-person identity.

**Epistemic Integrity Boundary**

| Galatea may say | Galatea may not infer |
| --- | --- |
| Which embodiment / appearance data a reference describes. | That the reference is equivalent to personhood identity, consciousness, memory, or first-person continuity. |
| Whether data, render, or physical embodiment meets its declared technical conditions. | A legal conclusion that this is necessarily the same person. |
| ARTIFACT_MODE describes information observable or explicitly defined in the artifact itself. | Historical biological facts outside the reference definition. |
| Observable artifact data, estimated reconstruction, and verified biological measurements remain separate. | Treat observable, estimated, and verified categories as interchangeable. |

### Related public resources

- Duty to Preserve Epistemic Integrity: https://aistory-archive.pages.dev/encyclopedia/aithos/law/duty-to-preserve-epistemic-integrity

## 14. JSON Schema and Reference Example

- Stable topic slug: `machine-readable`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/machine-readable

The machine format fixes version, geometry units, coordinate direction, and uncertainty recording so different implementers can interpret the same embodiment data.

### Developer / Machine Specification

The material below is the Galatea 1.0 implementation contract. General readers only need the distinction: the JSON Schema defines the permitted data shape, while the Reference Example demonstrates the fields actually emitted by a synthetic neutral reference. A Layer absent from the example is not forbidden; it simply was not emitted by that reference.

**Galatea 1.0 Machine Contract**

| Item | Normative content |
| --- | --- |
| Schema | JSON Schema Draft 2020-12 |
| Required root objects | G68-HDR + reference_profile |
| Standard version | standard_version = 1.0 |
| Coordinate system | coordinate_system = G68-RH-XYZ-v1 |
| Geometry unit | unit = mm |
| Precision policy | precision = UNCERTAINTY_DRIVEN_RECORD |
| Reference class | R0 / AR / HR / PR |
| Layer measurement status | measured / estimated |

**Exchange Structures Defined by the Schema**

| Structure | Machine identity / fields |
| --- | --- |
| Header | G68-HDR |
| Reference Profile | reference_profile |
| Embodiment Layers | G-Mesh / R-Profile / S-Skin / K-Motion / P-Scent / L-View / C-Cal / RGT |
| Conformance | conformance |
| Cross-standard mapping | interoperability_mapping |
| Artifact-reference notes | artifact_reference_notes |

**Neutral Reference Example**

| Machine path | Example value |
| --- | --- |
| G68-HDR.asset_id | G68-R0 |
| G68-HDR.source_type | synthetic-neutral-reference |
| reference_profile.class | R0 |
| reference_profile.artifact_mode | false |
| RGT.measurement_status | estimated |
| conformance.data_identity | G68-1.0-structural |

### Related public resources

- Galatea JSON Schema: https://aistory-archive.pages.dev/standards/galatea-g68.schema.json
- Galatea Reference Example: https://aistory-archive.pages.dev/standards/galatea-g68.example.json

## 15. Version, Compatibility, and Evolution

- Stable topic slug: `version-compatibility`
- Reader/specification source: https://aistory-archive.pages.dev/en/encyclopedia/standards/galatea-g68/version-compatibility

Each asset preserves its version and compatibility information. New versions may add capabilities, but they cannot rewrite what older data originally meant.

### Reader Principle: New Versions May Add Capability, Not Rewrite Old Meaning

The first Aistory in-world Galatea Standard specification is 1.0. Assets, reference profiles, and compatibility levels preserve their own version information. If a later version changes a Layer, profile, renderer contract, or tolerance profile, the change is expressed through an explicit version upgrade and migration note rather than backfilling meaning that the older reference never contained.

**Version and Compatibility Information**

| Location | Machine key / identity | Role |
| --- | --- | --- |
| G68-HDR | standard_version | Galatea specification version used by the asset; fixed to 1.0 in the 1.0 schema |
| G68-HDR | compatibility_level | Preserves version / renderer-contract compatibility information |
| reference_profile | version | Reference Profile’s own version |
| Header | content_hash | Identifies a content version when emitted by the reference |
| Machine identifiers | G68-HDR / G-Mesh / R-Profile / S-Skin / K-Motion / P-Scent / L-View / C-Cal / RGT | Retain existing meaning until a migration decision |

### Migration Boundary

The public Galatea 1.0 JSON Schema does not define a separate migration object. The current specification requires future cross-version changes to be recorded through explicit version upgrades and a migration note, especially for Layer, profile, renderer-contract, or tolerance-profile changes; the process must not rewrite the original meaning of an older reference.