# CoreAI Technical Specifications

## Purpose

This document defines the technical baseline for CoreAI v1.

## File Formats

- Markdown for human-readable documentation and AI-readable exports.
- YAML for schemas, manifests, bundles, and snapshots.
- JSON may exist for compatibility, but YAML is preferred for authored examples.

## Encoding

All project files should use UTF-8.

## Naming

Official documentation uses uppercase `COREAI_*.md` names under `docs/`.

Example data uses lowercase descriptive filenames under `examples/`.

## Runtime Expectations

A future CoreAI loader should:

- read local files
- validate YAML against schemas
- resolve relative paths
- apply visibility rules
- assemble bundles in priority order
- emit deterministic exports
- capture snapshots when requested

## Versioning

Versioning starts with repository history. Schema versions may be added when runtime compatibility requires them.

## Provider Boundary

No schema field should require a specific AI provider. Provider-specific settings must remain optional and isolated.