English · Русский
EmbrAIon
AI-First Engineering System by GORYNED
EmbrAIon keeps the rules for AI-assisted engineering with the repository — project knowledge, protected paths, routing, validation, review, and evidence — instead of scattering them across prompts and AI-client settings.
Use the same project contract with Codex, GitHub Copilot, Claude Code, or a host-neutral Portable bundle.
Why use it?
Use EmbrAIon when:
- important project rules no longer fit in one prompt;
- several AI clients need to follow the same repository contract;
- protected paths and validation need deterministic checks rather than prose alone;
- architecture knowledge and policy must survive model/session changes;
- model selection, review, and evidence should be reusable project settings instead of ad hoc choices.
Mental model: EmbrAIon is the operating system for AI-assisted engineering;
.embraion/is the Settings for this repository.
EmbrAIon does not replace the AI client, intercept every prompt, or run inside the finished product.
Quick start
pipx install embraion
cd MyProject
embraion init
embraion install --host codex --destination .
Open the repository in your AI client and ask:
Configure EmbrAIon for this project.
Lead uses the canonical Core Project Bootstrap skill to inspect existing truth, bind knowledge, preserve safety policy, and discover real validation. Routing stays optional. See Project Bootstrap.
Then work normally:
Fix the retry flow and add regression coverage.
Use copilot or claude-code instead of codex when that is your host.
Lead reads the project contract, selects specialists automatically, classifies each assignment independently, resolves project routing, and applies configured model/effort through supported native host capabilities. It collects proportional validation and review, integrates results, and retains final authority.
Want to experiment first? Use the Five-Minute Sandbox.
Before / after
Before
prompts + AGENTS.md + host settings + CI + tribal knowledge
↓
drift
After
.embraion/
↓
one repository-owned project contract
↓
host projections + validation + review
Documentation
Canonical site: https://embraion.goryned.com/
Recommended onboarding:
- Why EmbrAIon?
- EmbrAIon in 60 Seconds
- Five-Minute Sandbox
- Installation
- Choose the repository path:
- Add EmbrAIon to a Project for a new or simple repository.
- Adopt an Existing Repository for a mature repository with existing AI-client configuration.
- Your First AI Task
- How It Works
Need a term or a direct answer? See the Glossary, FAQ, and Security & Data Flow.
For engineers, see Engineering Model Deep Dive.
Examples
- Minimal — smallest complete project overlay.
- Python — ordinary Python app + EmbrAIon engineering layer.
- Unity — Unity 6 project with EmbrAIon outside the game runtime.
Status
EmbrAIon is pre-1.0. Projects pin exact published framework 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-29 02:30 UTC
Metadata
Release files for embraion 0.17.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.17.0.tar.gz | 630.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embraion-0.17.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / embraion-0.17.0.tar.gz
| Download URL | embraion-0.17.0.tar.gz |
|---|---|
| Size | 630.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e7f6f08427d457fdd9a826ff38825468444bc27941295dab32d85956e4e7c3f
|
|
BLAKE2b-256 checksum How to use checksums |
3b930f2a4da2e33b0a74aa7f91a41a6303e50eb92e1fd1c2725c7afa1f835ec1
|
| 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 29, 2026.
Transparency logRelease files / embraion-0.17.0-py3-none-any.whl
| Download URL | embraion-0.17.0-py3-none-any.whl |
|---|---|
| Size | 864.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd6541f40c62dc77d9490ed2de90d79331e3927506ebbfff2e6b026590aee5af
|
|
BLAKE2b-256 checksum How to use checksums |
f289d3f643de43efce6c6f29e41c3466e9fcb4d83dc43cc976465b2bab6ef906
|
| 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 29, 2026.
Transparency log