embraion 0.1.0__tar.gz

embraion-0.1.0/AGENTS.md

@@ -0,0 +1,87 @@
+# EmbrAIon Agent Instructions
+
+EmbrAIon is the upstream source of truth for reusable AI-First engineering behavior.
+
+## Repository ownership
+
+- Put vendor-neutral behavior in `core/`.
+- Put host/provider-specific representation in `adapters/`.
+- Put deterministic executable operations in `tools/`.
+- Put machine-readable contracts in `schemas/`.
+- Put project bootstrap material in `templates/`.
+- Keep product/domain-specific semantics in consuming-project overlays.
+
+## Capability loading
+
+- `core/catalog.yaml` is the canonical discovery index.
+- Prefer conditional capability loading over injecting the entire Core into every task.
+- Every catalog path must resolve to exactly one canonical capability.
+- Skills use one directory per skill with `SKILL.md` as the entry point.
+
+## Agent naming
+
+Canonical Core agents are job-like roles: `lead`, `worker`, `reviewer`, `architect`, `analyst`, `validator`, `researcher`, and `steward`.
+
+## Separation of concerns
+
+Agent role, access profile, model route, provider, and external integration state are independent dimensions.
+
+A role never implies broader permissions or a more expensive model. Model choice never expands access.
+
+## Data classes
+
+Use exactly three canonical data classes: `PUBLIC`, `PRIVATE`, and `CONFIDENTIAL`. Unknown classification fails closed.
+
+## Learning
+
+Learning output is advisory until explicitly promoted. Runtime evidence may create candidates, but no learning tool may directly mutate Core. Promotion uses review, validation, applicable evals, and explicit approval.
+
+## Security and integrations
+
+- External integrations must be inventoried.
+- Inventories store metadata and environment-variable names, never secret values.
+- Unknown integration state, access expansion, provider/privacy mismatch, and embedded credentials fail closed according to policy.
+- Security scanners report findings; they do not weaken policy to pass.
+
+## Worktrees
+
+Worktree cleanup is evidence-driven and fail-closed. Preserve ambiguous, dirty, locked, active, divergent, or unproven state. Salvage recoverable work before destructive cleanup.
+
+## Evals
+
+Use deterministic tests for schemas, code, references, and generated output. Use `evals/` for behavioral properties and baseline comparison.
+
+## Spec Kit
+
+Spec Kit is a recommended external capability for substantial specification-driven work. It remains independently managed and never overrides EmbrAIon Core or project truth.
+
+## File naming
+
+- Use lowercase kebab-case for repository-owned files.
+- Prefer one or two words when practical.
+- Standard ecosystem filenames are exceptions, including `README.md`, `AGENTS.md`, and `SKILL.md`.
+- Python modules use standard `snake_case` where required by the Python import system.
+
+## Brand terminology
+
+- Use **AI-First Engineering System** in normal prose and title case.
+- Use **AI-FIRST ENGINEERING SYSTEM** for the canonical all-caps brand category.
+- The lowercase-F spelling is forbidden.
+
+## README timestamps
+
+- Every `README*.md` ends with a last-updated timestamp.
+- Any README edit updates its timestamp in the same change.
+- Canonical format: `YYYY-MM-DD HH:mm UTC`.
+
+## Change discipline
+
+- Prefer the minimum justified change.
+- Preserve compatibility unless a breaking change is explicit.
+- Keep Core independent from any single host, provider, platform, or consuming project.
+- Do not weaken Core hard rules from a project overlay.
+- Do not silently duplicate canonical policy.
+
+## Completion reporting
+
+For substantial work report: Changed, Architecture, Validation, Risks, and Workers.

embraion-0.1.0/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+## Unreleased
+
+### Added
+
+- PyPI Trusted Publishing release path through GitHub Actions and the protected `pypi` environment.
+- Standalone wheel/sdist release artifacts for installation without cloning the repository.
+
+- Full Hindi and Spanish localization for the main README, documentation, and trademark policy.
+- Localization completeness validation now covers Russian, Simplified Chinese, Hindi, and Spanish.
+
+- Standard MIT License for EmbrAIon source code and documentation.
+- Canonical trademark and brand-assets policy.
+- Russian and Simplified Chinese informational translations of the brand policy.
+- Localized licensing documentation.
+
+### Changed
+
+- Package version prepared for the first public `v0.1.0` release.
+
+- Framework and Python package metadata now declare MIT licensing.
+- Main and brand README files now make the brand-assets exclusion explicit.

embraion-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 GORYNED and Egor Tomashin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

embraion-0.1.0/PKG-INFO

@@ -0,0 +1,388 @@
+Metadata-Version: 2.4
+Name: embraion
+Version: 0.1.0
+Summary: Portable AI-First Engineering System
+License-Expression: MIT
+Project-URL: Homepage, https://goryned.com
+Project-URL: Repository, https://github.com/GORYNED/EmbrAIon
+Project-URL: Documentation, https://github.com/GORYNED/EmbrAIon/tree/main/docs
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML<7,>=6.0
+Requires-Dist: jsonschema<5,>=4.22
+Dynamic: license-file
+
+<p align="center">
+  <img src="brand/assets/readme/hero-dark.png" alt="EmbrAIon — AI-First Engineering System by GORYNED" width="100%">
+</p>
+
+<p align="center">
+  <strong>English</strong> ·
+  <a href="localization/README.ru.md">Русский</a> ·
+  <a href="localization/README.zh-CN.md">简体中文</a> ·
+  <a href="localization/README.es.md">Español</a> ·
+  <a href="localization/README.hi.md">हिन्दी</a>
+</p>
+
+# EmbrAIon
+
+**AI-First Engineering System [by GORYNED](https://goryned.com)**
+
+> 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+
+- `pipx` is 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:
+
+```bash
+pipx install "git+https://github.com/GORYNED/EmbrAIon.git"
+```
+
+If `pipx` is not installed yet:
+
+```bash
+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:
+
+```bash
+pipx install embraion
+```
+
+A regular `pip` installation is also supported:
+
+```bash
+python -m pip install "git+https://github.com/GORYNED/EmbrAIon.git"
+```
+
+### 2. Verify the installation
+
+```bash
+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:
+
+```bash
+cd /path/to/your/project
+embraion init --name MyProject
+```
+
+This creates:
+
+```text
+.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:
+
+```bash
+embraion install --host codex --destination .
+```
+
+GitHub Copilot:
+
+```bash
+embraion install --host copilot --destination .
+```
+
+Claude Code:
+
+```bash
+embraion install --host claude-code --destination .
+```
+
+Portable bundle:
+
+```bash
+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:
+
+```text
+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
+
+```text
+embraion init
+embraion install
+embraion update
+embraion sync
+embraion validate
+embraion doctor
+```
+
+### Routing and runtime state
+
+Resolve a route:
+
+```bash
+embraion route --host codex --route-class strong --data PRIVATE
+```
+
+Create a bounded dispatch plan:
+
+```bash
+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:
+
+```bash
+embraion session start \
+  --session-id task-001 \
+  --task "Implement feature" \
+  --role lead \
+  --host codex \
+  --access plan
+```
+
+Inspect or update it:
+
+```bash
+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
+
+```bash
+embraion security scan --path .
+```
+
+The scanner checks for high-risk configuration problems such as possible embedded credentials and policy drift.
+
+### MCP inventory
+
+```bash
+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
+
+```bash
+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:
+
+```bash
+embraion learning observe \
+  --id repeated-review-gap \
+  --kind repeated-failure \
+  --target-type skill \
+  --target-id review \
+  --summary "Repeated review gap"
+```
+
+Promotion is gated:
+
+```text
+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:
+
+```bash
+embraion eval run \
+  --case reviewer-readonly \
+  --record path/to/execution-record.json
+```
+
+Create and compare baselines:
+
+```bash
+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:
+
+```bash
+embraion sync --host all --output build/generated --force
+```
+
+Generated outputs are disposable projections. Canonical policy always remains in `core/`.
+
+## Repository layout
+
+```text
+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/](docs/README.md)
+
+Translations:
+
+- [Русский](localization/docs/ru/README.md)
+- [简体中文](localization/docs/zh-CN/README.md)
+- [Español](localization/docs/es/README.md)
+- [हिन्दी](localization/docs/hi/README.md)
+
+## License and brand
+
+EmbrAIon source code and documentation are licensed under the [MIT License](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](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](https://goryned.com)**
+
+<sub>Last updated: 2026-09-23 21:13 UTC</sub>