# GEARM 0.1 Canonical Example Set — GEARM-A9

These files are **informative, non-normative** examples of GEARM 0.1 machine-readable usage. They illustrate how the established A1–A8 artifacts can be used together; they are not reference implementations and do not create additional GEARM semantics.

A JSON Schema, JSON-LD, or SHACL pass for an example does **not** establish complete GEARM conformance. Applicable semantic-assessment and Profile requirements remain independently applicable. Where an example uses an external identity (for example an AI Product URN), GEARM records the analytical relationship but does not re-own the external semantics.

## Examples

| File | Illustration | Primary semantic point |
|---|---|---|
| `01-metric-observation.example.jsonld` | Metric definition and observation | Definition and occurrence remain distinct; a concrete Metric Observation refers to its governed definition. |
| `02-threshold-evaluation.example.jsonld` | Threshold evaluation | Threshold Definition is distinct from Threshold Evaluation; the evaluation is formed from concrete evidence. |
| `03-ai-assisted-prediction.example.jsonld` | AI-assisted Prediction | An Analytical Execution may invoke an externally governed AI Product while the GEARM result is classified by what it represents: Prediction. |
| `04-recommendation-decision-action-outcome.example.jsonld` | Recommendation → Decision → Action → Outcome | Recommendation, Decision, Action, Outcome and their actors/events remain separately identifiable. |
| `05-information-proposition-direct-consumption.example.jsonld` | Information Proposition without Productization | Information Proposition may remain non-productized and be used directly; Productization is not mandatory. |
| `06-analytical-chaining.example.jsonld` | Analytical chaining | An intermediate analytical output may be consumed by another analytical process without implying Productization, ownership transfer, or ontology inheritance. |
| `07-terminology-mapping.example.json` | Local terminology mapping | A local domain term may explicitly specialize a canonical GEARM concept without claiming equivalence. |
| `08-governed-profile.example.json` | GEARM Profile | A Profile may select, tighten and contextualize GEARM while preserving mandatory core semantics and independent external authority. |

## Validation boundary

The first six files are structural GEARM Semantic Graph documents validated against `../gearm-0.1.schema.json`. The terminology mapping is validated against the same A7 schema. The Profile is validated against `../gearm-0.1.profile.schema.json`.

The JSON-LD examples use `../gearm-0.1.context.jsonld`. The structural `GEARMSemanticGraph` wrapper is an A7 document construct; the resources in each `@graph` use canonical A1 concepts and A2 predicates.

These examples intentionally avoid asserting complete semantic conformance. GEARM-A10 turns selected patterns into explicit expected-PASS positive test cases; GEARM-A11 remains the planned negative-test stage.