Skip to content

EmbrAIon

EmbrAIon — Where sparks become AI-built products

EmbrAIon keeps all the important rules for AI-assisted engineering in one repository-owned contract — knowledge, protected paths, routing, validation, review, and evidence — instead of spreading them across prompts and AI-client settings.

When you need it

EmbrAIon becomes useful when:

  • project rules no longer fit in one prompt;
  • several AI clients should follow the same repository rules;
  • protected paths and validation need real checks, not only instructions;
  • architecture knowledge must survive new sessions and model changes;
  • model/routing/review choices should be reusable project settings.

Mental model: EmbrAIon is the operating system for AI-assisted engineering; .embraion/ is the Settings for this repository.

Before / after

Before After
Rules live in prompts, AGENTS.md, host settings, CI, and people's memory Project rules have one canonical home under .embraion/
Each AI client can drift Shared behavior is projected into supported hosts
“Please run tests” is just an instruction Validation profiles run real project commands
“Do not touch this path” may be only prose Policy + validation/enforcement can reject protected-path changes
Model choices are repeated manually Stable task/risk classes can map to host defaults or project overrides

Choose your path

  • I just want AI to follow my project rules

    Read the one-minute overview, try the sandbox, install EmbrAIon, ask it to configure this project, then give your AI client normal engineering tasks.

    EmbrAIon in 60 Seconds

  • I want the engineering model

    Learn ownership, projections, routing, execution, validation, evidence, and enforcement.

    Engineering Model Deep Dive

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.

Project Bootstrap discovers project truth and real validation while preserving settings and optional routing. Then ask for the engineering outcome:

Fix the retry flow and add regression coverage.

Use copilot or claude-code instead of codex when that is your host.

Not ready to touch a real repository? Try the Five-Minute Sandbox.

How it fits

How EmbrAIon fits into your project

In plain English

You still talk directly to Codex, Copilot, or Claude Code. EmbrAIon gives that host the repository's shared engineering contract and provides deterministic commands for things such as validation and enforcement.

Why not just use a native instruction file?

Native instructions remain useful. EmbrAIon adds the parts that should be shared, versioned, and executable.

Native instruction file EmbrAIon
Mostly host-specific text guidance Shared project contract projected into supported hosts
Easy to duplicate and drift Canonical project-owned settings
Validation is separate/ad hoc Executable validation profiles + evidence
No shared routing vocabulary Stable task/risk route classes
Merge checks are separate Optional protected-path / validation / review enforcement

Next