emkeel 0.1.0__tar.gz

emkeel-0.1.0/.gitattributes

@@ -0,0 +1,5 @@
+# SEPARACIÓN — un solo límite físico:
+# TODO lo que Emkeel genera (ADRs, specs, records) vive en emkeel-governance/.
+# Esa única carpeta se excluye de la distribución (tarball / mirror code-only).
+# Borra esa carpeta para separar artefactos del código; sálvala para respaldarlos.
+emkeel-governance/ export-ignore

emkeel-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,45 @@
+name: emkeel-ci
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  gates:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install
+        run: pip install -e ".[dev]"
+
+      # Gate: el PR debe referenciar un ticket (trazabilidad ticket->codigo).
+      # Solo aplica en pull_request (en push directo a main no hay PR title).
+      - name: "Gate — ticket link"
+        if: github.event_name == 'pull_request'
+        env:
+          EMKEEL_BRANCH: ${{ github.head_ref }}
+          EMKEEL_PR_TITLE: ${{ github.event.pull_request.title }}
+        run: python -m emkeel.gates.check_ticket_link
+
+      # Gate: un PR feature (rama feat/) debe traer su spec en emkeel-governance/specs/.
+      - name: "Gate — plan present (features)"
+        if: github.event_name == 'pull_request'
+        env:
+          EMKEEL_BRANCH: ${{ github.head_ref }}
+        run: python -m emkeel.gates.check_plan_present
+
+      # Gate: un spec de feature debe declarar Acceptance Criteria.
+      - name: "Gate — acceptance criteria (features)"
+        if: github.event_name == 'pull_request'
+        env:
+          EMKEEL_BRANCH: ${{ github.head_ref }}
+        run: python -m emkeel.gates.check_acceptance_criteria
+
+      # Gate: la suite completa de tests (memoria durable anti-regresión).
+      - name: "Gate — tests"
+        run: pytest -q

emkeel-0.1.0/.github/workflows/jira-transition.yml

@@ -0,0 +1,27 @@
+name: jira-transition
+
+# Post-merge automation (NOT a gate): when a PR merges, move its linked ticket to Done.
+on:
+  pull_request:
+    types: [closed]
+
+jobs:
+  transition:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install emkeel
+        run: pip install -e .
+      - name: Transition linked ticket to Done
+        continue-on-error: true  # best-effort; never block on a Jira hiccup
+        env:
+          JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
+          JIRA_EMAIL: ${{ secrets.JIRA_EMAIL }}
+          JIRA_TOKEN: ${{ secrets.JIRA_TOKEN }}
+          EMKEEL_BRANCH: ${{ github.head_ref }}
+          EMKEEL_PR_TITLE: ${{ github.event.pull_request.title }}
+        run: python -m emkeel.jira

emkeel-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,30 @@
+name: release
+
+# Publish emkeel to PyPI on a GitHub Release (or manual dispatch).
+# Uses PyPI Trusted Publishing (OIDC) — NO token stored. Configure the trusted
+# publisher on PyPI once: Project → Publishing → add this repo + workflow "release.yml".
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  pypi-publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read   # actions/checkout needs this (job-level perms replace the full set)
+      id-token: write  # required for OIDC Trusted Publishing
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Build wheel + sdist
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+      - name: Publish to PyPI (Trusted Publishing)
+        uses: pypa/gh-action-pypi-publish@release/v1

emkeel-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+.venv/
+venv/

emkeel-0.1.0/AGENTS.md

@@ -0,0 +1,27 @@
+# AGENTS.md — Contrato del agente (Emkeel)
+
+Eres un **ejecutor bajo gates deterministas**. Las reglas que importan NO viven en
+este archivo (es best-effort y se puede ignorar); viven en **CI + branch protection**,
+que no puedes saltarte. Si algo se puede saltar, no es un gate: es una sugerencia.
+
+## Ciclo de un cambio
+
+1. Una rama por ticket: `feature/<KEY-123>-slug`.
+2. Produce los artefactos del cambio: plan (si es feature) → código → tests.
+3. **Todo fix de bug empieza por un test que lo reproduce** (queda como regresión permanente).
+4. Abre PR. El merge requiere: **CI verde + aprobación humana + ticket ligado**.
+5. ¿Decisión arquitectónica? Un ADR en `emkeel-governance/adr/`.
+
+## Reglas duras (las enforza CI, no este archivo)
+
+- La **suite completa** corre en cada PR. Si rompes algo viejo → CI rojo → no mergeas.
+- Commits: **Conventional Commits** con la KEY del ticket.
+- Prohibido `--no-verify`. Prohibido marcar "done" sin que el check lo compute.
+
+## Separación (estructural, no negociable)
+
+- `src/emkeel/` = código distribuible.
+- `emkeel-governance/` = la ÚNICA carpeta de artefactos (ADR/specs/records). **Nunca** se
+  distribuye (`export-ignore`). Es el único límite físico: borrarla = código limpio.
+
+> Nota: Claude Code lee `CLAUDE.md` (symlink → este archivo).

emkeel-0.1.0/CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md

emkeel-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

emkeel-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Emkeel
+Copyright 2026 EMillion Networking LTD
+
+This product includes software developed at EMillion Networking LTD.
+Licensed under the Apache License, Version 2.0 (see LICENSE).

emkeel-0.1.0/PKG-INFO

@@ -0,0 +1,36 @@
+Metadata-Version: 2.4
+Name: emkeel
+Version: 0.1.0
+Summary: Adopt-and-thin SDLC governance framework
+Author: EMillion Networking LTD
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Emkeel
+
+Framework de gobernanza SDLC — **adopt-and-thin**. La quilla sobre la que se
+construyen proyectos paso a paso: trazables, sin regresiones, con la IA como
+ejecutor bajo gates deterministas.
+
+## Principio central
+
+> **"done" = hecho computado** (el artefacto existe + pasa un check determinista),
+> nunca un flag auto-atestado. El enforcement vive **server-side** (CI + branch
+> protection), fuera del alcance del agente. Pocos gates duros + un gate humano.
+
+## Cómo está organizado (separación estructural, día 1)
+
+- `src/emkeel/` — **código distribuible** (lo único que se empaqueta).
+- `emkeel-governance/` — **la única carpeta de artefactos** (ADR / specs / records). Un
+  solo límite físico: `export-ignore` la excluye del paquete/tarball. Borra esa carpeta
+  para separar artefactos del código; sálvala para respaldarlos. Nada más que separar.
+
+Ver `AGENTS.md` (contrato del agente) y `docs/lifecycle.md` (la convención).
+
+---
+Licensed under **Apache-2.0** — © 2026 EMillion Networking LTD (ver `LICENSE` / `NOTICE`).

emkeel-0.1.0/README.md

@@ -0,0 +1,23 @@
+# Emkeel
+
+Framework de gobernanza SDLC — **adopt-and-thin**. La quilla sobre la que se
+construyen proyectos paso a paso: trazables, sin regresiones, con la IA como
+ejecutor bajo gates deterministas.
+
+## Principio central
+
+> **"done" = hecho computado** (el artefacto existe + pasa un check determinista),
+> nunca un flag auto-atestado. El enforcement vive **server-side** (CI + branch
+> protection), fuera del alcance del agente. Pocos gates duros + un gate humano.
+
+## Cómo está organizado (separación estructural, día 1)
+
+- `src/emkeel/` — **código distribuible** (lo único que se empaqueta).
+- `emkeel-governance/` — **la única carpeta de artefactos** (ADR / specs / records). Un
+  solo límite físico: `export-ignore` la excluye del paquete/tarball. Borra esa carpeta
+  para separar artefactos del código; sálvala para respaldarlos. Nada más que separar.
+
+Ver `AGENTS.md` (contrato del agente) y `docs/lifecycle.md` (la convención).
+
+---
+Licensed under **Apache-2.0** — © 2026 EMillion Networking LTD (ver `LICENSE` / `NOTICE`).

emkeel-0.1.0/docs/install.md

@@ -0,0 +1,49 @@
+# Installing Emkeel in a repo
+
+`emkeel init` scaffolds a target repo to be governed by Emkeel. It is **non-clobbering**
+(existing files are skipped unless `--force`) and **never writes secrets**.
+
+## Run
+
+```bash
+# Dry-run first (writes nothing, shows the plan):
+python -m emkeel.init /path/to/repo \
+  --jira-url https://your.atlassian.net \
+  --jira-project KEY \
+  --github-repo owner/repo \
+  --dry-run
+
+# Then for real:
+python -m emkeel.init /path/to/repo --jira-url ... --jira-project KEY --github-repo owner/repo
+```
+
+### Install source (private emkeel)
+
+The generated CI runs `pip install <source>`. **Default:** the PyPI package, version-pinned
+(`emkeel~=0.1.0`) — `pip install emkeel`, no account, no token.
+
+For a **private fork**, pass a git+token form and add the token as a repo secret:
+
+```bash
+python -m emkeel.init /path/to/repo ... \
+  --emkeel-source 'git+https://x-access-token:${EMKEEL_INSTALL_TOKEN}@github.com/OWNER/emkeel.git'
+```
+
+Then add `EMKEEL_INSTALL_TOKEN` (a fine-grained PAT with READ access to the emkeel repo)
+as a GitHub Actions secret in the target repo.
+
+## What it creates
+
+- `emkeel-governance/{specs,adr,records}/` — the single artifact folder (`export-ignore`).
+- `.github/workflows/emkeel-ci.yml` — runs the gates on PRs.
+- `emkeel.toml` — non-secret config (Jira URL + project key, GitHub repo).
+- `.env.example` — secrets template (real `.env` is gitignored, never committed).
+- `AGENTS.md` — the agent contract (skipped if one already exists).
+
+## Connect (one-time, printed by the command)
+
+1. **GitHub for Jira** app → install & link the repo (commits/PRs link to tickets).
+2. **Branch protection** on `main` → require the `gates` check + a PR.
+3. **Secrets** → add `JIRA_TOKEN` (+ `JIRA_EMAIL`) as GitHub Actions secrets.
+4. **Local** → `cp .env.example .env` and fill it.
+5. **Install source** → until Emkeel is on PyPI, point the CI `Install emkeel` line at your source.

emkeel-0.1.0/docs/lifecycle.md

@@ -0,0 +1,22 @@
+# Lifecycle (lean)
+
+```
+rama  →  artefactos  →  PR  →  gates  →  merge
+```
+
+| Paso | Artefacto | Gate (server-side, no falsificable) |
+|---|---|---|
+| plan | `emkeel-governance/specs/<KEY>.md` (solo features) | CI: existe + valida |
+| develop | código + tests | CI: lint + types + **suite completa** verde |
+| verify | (CI) + tu review | required check + required approval |
+| decisión | `emkeel-governance/adr/NNNN-*.md` | CI: ADR presente si toca zona marcada |
+| merge | — | branch protection: CI verde + approval + ticket ligado |
+
+## Por qué funciona
+
+- **"done" = el check pasa**, no un flag que el agente escribe. (Con LangGraph y sin
+  LangGraph el agente se saltaba reglas porque eran auto-atestadas; el orquestador
+  nunca fue la variable — el locus de autoridad sí.)
+- La **suite de tests es la memoria durable** anti-regresión: el agente olvida entre
+  sesiones, la suite no. Re-romper algo viejo = CI rojo = bloqueado.
+- Lo no-mecanizable lo cubre **tu gate humano** (aprobar el PR), no más prosa.

emkeel-0.1.0/docs/review-assist.md

@@ -0,0 +1,28 @@
+# Review-assist (advisory)
+
+After CI is green and before the human merges: a per-criterion review. It reduces the
+reviewer's blind spot (useful when you can't read the code deeply) — but it is
+**advisory, never a gate**. The human is the final approver; the AI never merges.
+
+## Steps
+
+1. **Gather inputs.** `python -m emkeel.review <KEY>` prints a template with the
+   ticket's Acceptance Criteria, one section each. Get the diff with `gh pr diff <N>`.
+2. **Verdict per criterion.** For each `AC1..ACn`, the reviewer (AI and/or human) fills:
+   - `verdict:` met / not-met / unsure
+   - `evidence:` the file/lines in the diff that show it
+3. **Concerns.** List anything outside the criteria worth flagging (design, risk).
+4. **Ratchet.** Any criterion not backed by a test → file a test. Judgment you make
+   once becomes a permanent deterministic check (so next time the machine guards it).
+5. **Human approves.** Read the filled template, then merge. The AI never merges.
+
+## Why advisory, not a gate
+
+AI judgment is probabilistic — a non-deterministic CI gate would reintroduce the very
+fragility Emkeel removes. So the layers are:
+
+- **CI / gates (deterministic floor)** — tests, linters: cannot be faked.
+- **Review-assist (advisory)** — shrinks the human's blind spot, criterion by criterion.
+- **Human (final approver)** — judgment + merge.
+
+What the review-assist proves with a test, it hands down to the deterministic floor.

emkeel-0.1.0/emkeel-governance/adr/0001-adopt-and-thin.md

@@ -0,0 +1,39 @@
+# 1. Emkeel adopta gobernanza adopt-and-thin
+
+- Estado: aceptado
+- Fecha: 2026-06-06
+- Deciders: operador (EMillion Networking)
+
+## Contexto
+
+El framework v1 (`em-development-framework`, engine LangGraph bespoke) se volvió
+insostenible para un solo dev: cada escalado se desorganizaba (footgun de `--work-impl=stub`,
+replan W69, scope drift 4×). Un research de mercado (deep-research, 2026-06-06, verificado
+adversarialmente) confirmó el consenso: para un equipo solo/diminuto se **componen
+herramientas off-the-shelf**, no se construye un framework bespoke (el anti-patrón).
+
+## Decisión
+
+Emkeel compone: **GitHub** (branch protection + Actions CI), **Jira** (workflow),
+**Conventional Commits**, **ADRs markdown**, y **Claude Code** (skills/subagents/hooks +
+AGENTS.md). El único código propio es una capa fina: **gates deterministas** + el patrón
+**Plan-Execute-Verify** + el pegamento **ADR↔sesión** (trazabilidad spec a largo plazo,
+brecha no resuelta del mercado). `"done"` = hecho computado; enforcement server-side;
+pocos gates duros + gate humano.
+
+## Consecuencias
+
+- v1 **congelado** (cantera read-only). W70/W71 **cancelados**.
+- **Separación estructural día 1**: `src/` (distribuible) vs `emkeel-governance/` (la única
+  carpeta de artefactos, `export-ignore`). Un solo límite físico. Nunca más un cutover.
+- **Anti-regresión**: test-on-fix + CI corre la suite completa en cada PR.
+
+## Alternativas consideradas
+
+- Seguir parchando v1 → rechazado (arrastra errores).
+- Reconstruir otro engine bespoke → rechazado (*second-system trap*).
+
+## Referencias
+
+- Research de mercado (deep-research, 2026-06-06).
+- Memoria del operador: `project-emkeel-v2-pivot`.

emkeel-0.1.0/emkeel-governance/adr/0002-license-apache-2.0.md

@@ -0,0 +1,26 @@
+# 2. Emkeel is licensed Apache-2.0 (free / open-source)
+
+- Status: accepted
+- Date: 2026-06-07
+- Deciders: operator (EMillion Networking)
+
+## Context
+Emkeel started under a provisional proprietary license. The operator decided to
+distribute it **free / open-source first** (adoption now; monetize later via open-core).
+A permissive OSS license also removes the private-package friction: once on PyPI,
+`pip install emkeel` works for anyone — no install token.
+
+## Decision
+License Emkeel under **Apache-2.0**. Chosen over MIT for its explicit **patent grant**
+(safer for a tool that may be commercialized later). The repos Emkeel *governs* stay
+private — only the framework itself is public.
+
+## Consequences
+- `LICENSE` replaced (proprietary → Apache-2.0 verbatim) + `NOTICE` added.
+- `pyproject.toml` declares Apache-2.0.
+- Distribution path opens: PyPI (public), `pip install emkeel`, no token.
+- Re-licensable by the copyright holder; contributions covered by Apache-2.0 §5.
+
+## Alternatives considered
+- **MIT** — simpler, but no explicit patent grant.
+- **Stay proprietary** — blocks free distribution and keeps the install-token friction.

emkeel-0.1.0/emkeel-governance/specs/KEEL-10.md

@@ -0,0 +1,23 @@
+# KEEL-10 — Installer default to public git source
+
+## Context
+Emkeel is now public + tagged `v0.1.0`, so a governed repo can install it token-less from
+the public repo. The installer's default `--emkeel-source` should reflect that (the prior
+default `emkeel~=…` won't resolve until PyPI exists).
+
+## Plan
+- `src/emkeel/init.py` — `_default_source()` returns `git+<public-repo>@v{__version__}`
+  (token-less, tag-pinned, tracks version bumps).
+- `tests/test_init.py` — assert the default is the public git URL pinned to `@v{version}`.
+- `docs/install.md` — document the public-git default; PyPI/private-fork as alternatives.
+
+## Acceptance Criteria
+- `emkeel init` (no `--emkeel-source`) generates CI installing from
+  `git+https://github.com/.../emkeel.git@v0.1.0` — public, no token.
+- The pin tracks `__version__` (`@v{version}`), so a release/tag bump updates the default.
+- A custom `--emkeel-source` (PyPI spec or private git+token) still overrides.
+- The default needs no secret (no `EMKEEL_INSTALL_TOKEN`).
+
+## Anti-regression
+- Tests cover: default is public git + tag-pinned (`@v{version}`), never bare; custom
+  source still flows through; checklist mentions the token only for private sources.

emkeel-0.1.0/emkeel-governance/specs/KEEL-11.md

@@ -0,0 +1,23 @@
+# KEEL-11 — PyPI release workflow + installer default to PyPI
+
+## Context
+Model A chosen: repo stays PRIVATE (governance hidden), distribute the PACKAGE on PyPI
+(public). This adds the release pipeline and reverts the installer default to the PyPI
+pin (KEEL-10's public-git default is superseded — the repo is private again).
+
+## Plan
+- `.github/workflows/release.yml` — on a GitHub Release (or manual dispatch), build
+  wheel+sdist and publish to PyPI via **Trusted Publishing (OIDC, no token)**.
+- `src/emkeel/init.py` — `_default_source()` returns `emkeel~=0.{minor}.0` (PyPI pin),
+  not the git URL. Private fork still overridable via `--emkeel-source`.
+- `tests/test_init.py` + `docs/install.md` — assert/document the PyPI default.
+
+## Acceptance Criteria
+- `emkeel init` (no `--emkeel-source`) generates CI with `pip install "emkeel~=0.1.0"`.
+- `release.yml` builds and publishes via Trusted Publishing (`id-token: write`, the
+  `pypa/gh-action-pypi-publish` action) — no PyPI token stored in the repo.
+- A custom `--emkeel-source` (private git+token) still overrides.
+- The release workflow ships only in emkeel's own repo (NOT scaffolded into governed repos).
+
+## Anti-regression
+- Tests cover: default source is the PyPI pin (`emkeel~=`), never bare; custom source overrides.

emkeel-0.1.0/emkeel-governance/specs/KEEL-2.md

@@ -0,0 +1,19 @@
+# KEEL-2 — Gate: plan-presence para features
+
+## Contexto
+Primer ticket dogfood: el primer cambio real que recorre el loop de Emkeel
+(rama → PR → gates CI → merge). Añade el segundo gate determinista.
+
+## Plan
+- `src/emkeel/gates/check_plan_present.py` — el gate: una rama `feat/` exige
+  `emkeel-governance/specs/<KEY>.md`; otros tipos no.
+- `tests/test_check_plan_present.py` — su test (test-on-fix desde el día 1).
+- `.github/workflows/ci.yml` — nuevo step que corre el gate en PRs.
+
+## Verificación
+- `pytest` verde (incluye el nuevo test).
+- Auto-validación: este PR es `feat/KEEL-2-...`, así que el gate corre sobre sí mismo
+  y exige este mismo spec → debe pasar porque el archivo existe.
+
+## Anti-regresión
+- El test cubre: feature requiere spec, no-feature no, y detección de spec presente.