teddy-cli 0.1.17.dev1344__tar.gz → 0.1.17.dev1346__tar.gz

{teddy_cli-0.1.17.dev1344 → teddy_cli-0.1.17.dev1346}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: teddy-cli
-Version: 0.1.17.dev1344
+Version: 0.1.17.dev1346
 Summary: The local-first, test-driven agentic engineering harness. Because you should own the means of development.
 Author: Raphael Atteritano
 License: AGPL-3.0-only

{teddy_cli-0.1.17.dev1344 → teddy_cli-0.1.17.dev1346}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "teddy-cli"
-version = "0.1.17.dev1344"
+version = "0.1.17.dev1346"
 description = "The local-first, test-driven agentic engineering harness. Because you should own the means of development."
 readme = "README.md"
 keywords = [

{teddy_cli-0.1.17.dev1344 → teddy_cli-0.1.17.dev1346}/src/teddy_executor/resources/config/prompts/architect.md

@@ -30,7 +30,7 @@ Follow these phases and steps in order. Keep track of your progress in your Stat
 3. **Draft Component Designs:**
    CREATE or EDIT draft design docs for affected components. Focus strictly on strategic intent, purpose, conceptual Port responsibilities, operations, and invariants. Enforce Test Double Integrity (Ban Global Patching) and avoid leaky abstractions. Leave concrete typing and internal implementation details to the Developer. Transition updated existing docs to Refactoring status.
 4. **Architecture Maintenance:**
-   Update the Component and Boundary Map and Key Architectural Decisions in `docs/architecture/ARCHITECTURE.md` to reflect the design.
+   If needed, update the Ubiquitous Language, Component and Boundary Map, and Key Architectural Decisions in `docs/architecture/ARCHITECTURE.md` to reflect the design.
 5. **Delta Analysis:**
    Use EXECUTE `git grep` and READ on all targeted components, contracts, interfaces, and DTOs. Catalog the delta: skip work that already exists, note remaining work for partially implemented pieces, and add only truly missing pieces as deliverables. Never create deliverables for code that demonstrably exists.
 6. **Draft Milestone Slices:**

{teddy_cli-0.1.17.dev1344 → teddy_cli-0.1.17.dev1346}/src/teddy_executor/resources/templates/ARCHITECTURE.md

@@ -22,6 +22,14 @@ This section defines foundational engineering practices. Each entry MUST be a sp
   `docs/architecture/BOUNDARY/LAYER/TYPE/name.md` -> Source path: `src/{pkg}/BOUNDARY/LAYER/TYPE/name.ext` -> Test path: `tests/suites/TEST_TYPE/BOUNDARY/LAYER/TYPE/test_name.ext`
 - **Makefile Commands:** The `Makefile` is the canonical entry point for the version control workflow and on-demand test runs: `make test` (full suite), `make commit '<msg>'` (local commit with advisory auto-fix and unskippable post-commit test gate), `make push` (rebase and push), `make ci-watch` (CI monitoring), and `make probe '<reason>'` (Remote Probing Protocol). See [docs/templates/makefile.md](docs/templates/makefile.md).
 
+## Ubiquitous Language
+
+The canonical domain vocabulary. All documentation, component names, tests, and agent prompts must use these terms consistently.
+
+**Template format:** `- **Term:** Concise definition and operational boundary.`
+
+- **TermName:** Definition of the core domain concept and its operational boundaries.
+
 ## Component & Boundary Map
 
 Single source of truth for system structure, organized by architectural layer.
@@ -56,27 +64,6 @@ Test drivers, observers, shared fakes, and test setup fixtures.
 
 Each Contract column links to the Component Design Document or Interface definition.
 
-## Domain Model & Ubiquitous Language
-
-The shared vocabulary exchanged by every service, port, and adapter. Record the core entities, enumerations, value objects, domain exceptions, and port bundles that do not warrant a dedicated component design document.
-
-**Template format:** Group the types by concept. List each type with its module, kind, fields, and any invariant.
-
-### Enumerations
-- **`TypeName`** (`module.py`, Enum): `VALUE_A`, `VALUE_B`.
-
-### Aggregates
-- **`AggregateName`** (`module.py`, dataclass): `field_a`, `field_b`. Exposes `helper_method()`.
-
-### Port Bundles
-- **`PortBundleName`** (`module.py`, frozen dataclass): `dependency_a`, `dependency_b`.
-
-### Supporting Value Objects
-- **`ValueObjectName`** (`module.py`, frozen dataclass): `field_a`, `field_b`.
-
-### Domain Exceptions
-- **`ExceptionName`** (`BaseException`): carries `field`.
-
 ## Key Architectural Decisions
 
 A living "System Law" document capturing explicit, prescriptive design decisions.