English · Русский · 简体中文 · Español · हिन्दी
EmbrAIon
AI-First Engineering System by GORYNED
Where sparks become AI-built products
EmbrAIon is a portable AI-First Engineering System for organizing AI-assisted software engineering around explicit roles, reusable skills, workflow orchestration, model routing, access control, validation, review, security, learning, and project overlays.
It is designed to sit above individual languages and frameworks. A Unity/C# project, a Python service, a web application, or another software repository can use the same Core and add only project-specific knowledge and rules.
What EmbrAIon does
EmbrAIon separates the engineering system into independent dimensions:
- Agent — who is responsible: Lead, Worker, Reviewer, Architect, Analyst, Validator, Researcher, Steward.
- Skill — how a repeatable class of work is performed.
- Rule — what is required, forbidden, or protected.
- Workflow — in what order capabilities are composed.
- Routing — which access profile, model tier, host, and provider may execute the work.
- Adapter — how canonical capabilities are represented in Codex, Copilot, Claude Code, providers, or a host-neutral Portable bundle.
- Tool — deterministic executable behavior such as validation, security scanning, worktree management, synchronization, and diagnostics.
- Eval — whether AI behavior actually follows the intended engineering contract.
core/catalog.yaml is the discovery index. Instead of loading the entire framework for every task, EmbrAIon can load only capabilities whose triggers match the current work.
Data classes
EmbrAIon uses three canonical data classes:
| Class | Meaning |
|---|---|
PUBLIC |
Public information that may be sent to eligible external systems |
PRIVATE |
Proprietary/internal project information; external use requires an explicit eligible route |
CONFIDENTIAL |
Highest protection level; denied externally unless a route explicitly allows it |
Unknown or ambiguous classification fails closed. Model choice never expands access or privacy eligibility.
Supported host adapters
Current adapters:
- Codex — native model catalog, model/effort route mapping, generated project agents and config.
- GitHub Copilot — advisory model catalog and generated custom-agent projection.
- Claude Code — Claude model catalog and generated subagent projection.
- Portable — host-neutral installable capability bundle.
- Providers — direct API model catalogs for OpenAI, Anthropic, Google, DeepSeek, plus transport metadata.
Core remains model-neutral. Current model identities and host selectors live only in adapters.
Installation
A local clone of the EmbrAIon repository is not required.
Requirements
- Python 3.11+
pipxis recommended for an isolated CLI installation- Git is only needed while installing directly from the GitHub repository before the PyPI release
1. Install EmbrAIon
Recommended:
pipx install "git+https://github.com/GORYNED/EmbrAIon.git"
If pipx is not installed yet:
python -m pip install --user pipx
python -m pipx ensurepath
Then open a new terminal and run the install command above.
After EmbrAIon is published to PyPI, the normal installation will become:
pipx install embraion
A regular pip installation is also supported:
python -m pip install "git+https://github.com/GORYNED/EmbrAIon.git"
2. Verify the installation
embraion --version
embraion validate
embraion doctor
The installed package contains the canonical Core, adapters, schemas, templates, policies, documentation, and other framework data required by the CLI. EmbrAIon does not depend on a checked-out repository after installation.
Add EmbrAIon to a project
Create the project overlay:
cd /path/to/your/project
embraion init --name MyProject
This creates:
.embraion/
└── project.yaml
The project overlay pins the framework version and is where project-specific capabilities can be declared without modifying Core.
Install a host projection
Codex:
embraion install --host codex --destination .
GitHub Copilot:
embraion install --host copilot --destination .
Claude Code:
embraion install --host claude-code --destination .
Portable bundle:
embraion install --host portable --destination ./vendor/embraion
Use --force only when intentionally replacing an existing generated projection.
How a task flows through EmbrAIon
A substantial task conceptually follows this path:
User goal
↓
Project overlay + Core catalog
↓
Relevant rules / agents / skills / workflows
↓
Data class + access profile + complexity
↓
Host adapter + model route
↓
Implementation
↓
Validation
↓
Independent review
↓
Verification
↓
Delivery / human merge gate
For substantial specification-driven work, Spec Kit is recommended as an independent companion. It refines planning and specification but does not replace Core rules, project truth, compatibility contracts, or validation evidence.
CLI
Framework and project
embraion init
embraion install
embraion update
embraion sync
embraion validate
embraion doctor
Routing and runtime state
Resolve a route:
embraion route --host codex --route-class strong --data PRIVATE
Create a bounded dispatch plan:
embraion dispatch \
--task "Implement feature" \
--role worker \
--host codex \
--route-class economy-write \
--data PRIVATE \
--access write \
--owned-path "src/**"
Writable dispatch planning requires explicit owned paths and refuses the stable main/master branch. The plan and privacy-safe routing telemetry are written under .embraion/state/.
Start normalized session state:
embraion session start \
--session-id task-001 \
--task "Implement feature" \
--role lead \
--host codex \
--access plan
Inspect or update it:
embraion session show
embraion session set --state review --validation passed
The host adapter performs actual AI execution; EmbrAIon owns canonical routing, generated agent definitions, access/ownership boundaries, dispatch plans, normalized state, and privacy-safe operational telemetry.
Security
embraion security scan --path .
The scanner checks for high-risk configuration problems such as possible embedded credentials and policy drift.
MCP inventory
embraion mcp inventory
This creates a normalized privacy-safe inventory under .embraion/state/. Environment-variable names may be recorded; secret values are never intentionally persisted.
Worktrees
embraion worktree list
embraion worktree create ai/my-task
embraion worktree gc
embraion worktree salvage /path/to/worktree
gc is dry-run by default and only considers directly proven, clean, unlocked worktrees. Use --apply explicitly to remove safe candidates.
Learning
Record repeated evidence:
embraion learning observe \
--id repeated-review-gap \
--kind repeated-failure \
--target-type skill \
--target-id review \
--summary "Repeated review gap"
Promotion is gated:
observe → accumulate evidence → propose → approve → promote
Promotion never edits Core automatically. A promoted candidate still requires an ordinary reviewed engineering change.
Behavioral evals
Run an eval case:
embraion eval run \
--case reviewer-readonly \
--record path/to/execution-record.json
Create and compare baselines:
embraion eval baseline --reports build/evals --output baseline.json
embraion eval compare --baseline baseline.json --reports build/evals
Generate adapter projections
Generate all supported projections without installing them into a project:
embraion sync --host all --output build/generated --force
Generated outputs are disposable projections. Canonical policy always remains in core/.
Repository layout
brand/ Brand specification and README assets
core/ Canonical rules, agents, skills, workflows, routing, knowledge
adapters/ Codex, Copilot, Claude Code, Portable, provider integrations
tools/ CLI, runtime, learning, security, MCP, worktree, validation, sync
schemas/ Machine-readable contracts
templates/ Project overlay templates
docs/ Canonical English documentation
localization/ Russian, Simplified Chinese, Hindi, and Spanish translations
tests/ Deterministic unit/integration tests
evals/ Behavioral cases, baselines, graders, fixtures, reports
examples/ Reference integrations
Validation and CI
Every push and pull request is intended to run:
- schema and catalog validation;
- localization parity;
- unit and integration tests;
- security scanning;
- generation of all host projections;
- behavioral eval smoke tests.
Tagged releases generate source, Codex, Copilot, Claude Code, and Portable archives.
Documentation
Canonical documentation: docs/
Translations:
License and brand
EmbrAIon source code and documentation are licensed under the MIT License, except where a file or directory explicitly states otherwise.
The EmbrAIon and GORYNED names, logos, wordmarks, visual marks, and the files under brand/assets/ are not licensed under MIT. The MIT License does not grant trademark or brand-identity rights. See TRADEMARKS.md for the canonical policy.
Current status
EmbrAIon is pre-stable. The architecture and first executable CLI are in place, but the public compatibility contract is not frozen yet.
Before the first stable release, model catalogs, generated host projections, validation coverage, security rules, installation behavior, and release packaging may still evolve.
EmbrAIon · AI-FIRST ENGINEERING SYSTEM · by GORYNED
Last updated: 2026-09-23 21:13 UTC
Release files for embraion 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| embraion-0.1.0.tar.gz | 212.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embraion-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 496.8 kB
Release files / embraion-0.1.0.tar.gz
| Download URL | embraion-0.1.0.tar.gz |
|---|---|
| Size | 212.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62b30399375dc258c3f5490b2c8e8c0bbcf6accb90c569ddbe5a2beedc08062b
|
|
BLAKE2b-256 checksum How to use checksums |
93cabe91b4c362a1a80608d4d5eb31b3d100e09c9421cbd6d5481e21cd042a5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logRelease files / embraion-0.1.0-py3-none-any.whl
| Download URL | embraion-0.1.0-py3-none-any.whl |
|---|---|
| Size | 284.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
debf9c3ecd966e96fe01ba83ba37e27b6b6aac70fad4c8dfd45291e0b8997a09
|
|
BLAKE2b-256 checksum How to use checksums |
344d2a5580155f9216cca6261277bc1817e6234006efb6f95cc47aa202b63fd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency log