English · Русский · 简体中文 · Español · हिन्दी

EmbrAIon

AI-First Engineering System by GORYNED

Where sparks become AI-built products

EmbrAIon is a portable engineering layer for teams that use AI to build software. It gives Codex, GitHub Copilot, Claude Code, and other integrations a consistent project contract: roles, reusable skills, project knowledge, routing, permissions, validation, review, security, and evidence.

EmbrAIon does not sit inside your application runtime. Your Unity game, Python service, web app, or library remains a normal project. EmbrAIon organizes how humans and AI engineer it.

Why use it?

• One reusable engineering system across different repositories and technology stacks.
• Project-owned configuration under .embraion/ instead of hidden framework assumptions.
• Native AI-client projections for Codex, GitHub Copilot, Claude Code, and a Portable bundle.
• Model-agnostic routing: the AI client owns model availability unless your project explicitly overrides it.
• Executable validation profiles with structured evidence.
• Project-specific agents without copying project semantics into reusable Core.
• Fail-closed safety boundaries for privacy, protected paths, configuration, review, and enforcement.
• Explicit automation: EmbrAIon does not silently install executable hooks or CI gates.

Quick start

Install the launcher once:

pipx install embraion

Add EmbrAIon to a repository:

cd MyProject
embraion init
embraion install --host codex --destination .
embraion doctor
embraion status

Use copilot or claude-code instead of codex when that is the AI client you use.

embraion init creates the project-owned configuration surface:

.embraion/
├── .gitignore
├── project.yaml
├── knowledge.yaml
├── policy.yaml
├── routing.yaml
├── validation.yaml
└── agents.yaml

The generated host files are projections. The .embraion/ files remain the canonical project configuration.

How it fits together

Your repository
     │
     ├── .embraion/ configuration + project knowledge
     │
EmbrAIon Core
     │
     ├── roles / skills / workflows / safety policy
     │
     ▼
Codex / Copilot / Claude Code / Portable
     │
     ▼
AI-assisted engineering work
     │
     ▼
validation → review → evidence → human merge

By default EmbrAIon does not pin a specific AI model. The selected host uses its own default or automatic choice. Optional project overrides belong only in .embraion/routing.yaml.

Validation and enforcement

Projects declare real commands in .embraion/validation.yaml and run them explicitly:

embraion validation run affected

Enforcement is opt-in. When a project wants a GitHub Actions gate:

embraion enforcement install \
  --surface github-actions \
  --validation-profile affected

EmbrAIon never installs that workflow silently. Repository branch rules decide whether its status check is mandatory for merge.

Updating

Upgrade the launcher first, then intentionally update a project:

pipx upgrade embraion
cd MyProject
embraion update
embraion doctor

Safe configuration normalization targets the installed launcher version. Existing project-owned values are preserved, missing compatible defaults may be added, and incompatible configuration fails before mutation.

Documentation

Start here: goryned.github.io/EmbrAIon

Recommended path:

1. What is EmbrAIon?
2. Installation
3. Add EmbrAIon to a project
4. Adopt an existing repository
5. Run your first AI task
6. Configure your project
7. Daily workflow

Full command details live in the CLI reference.

Examples

The repository includes executable reference projects for:

• Minimal — the smallest complete EmbrAIon consumer.
• Python — ordinary application code and tests with EmbrAIon layered around them.
• Unity — a runnable Unity 6 project showing that EmbrAIon remains outside the game runtime.

CI exercises the real consuming-project lifecycle across Windows, macOS, and Linux.

Status

EmbrAIon is pre-1.0. Patch releases are intended for compatible fixes and improvements; minor releases may evolve public framework contracts. Projects pin exact published versions so upgrades remain intentional.

License and brand

Source code and documentation are licensed under the MIT License except where explicitly stated otherwise. The EmbrAIon and GORYNED names, logos, wordmarks, visual marks, and files under brand/assets/ are governed separately by TRADEMARKS.md.

_{Last updated: 2026-09-24 18:49 UTC}