pico-ioc 1.2.0__tar.gz → 1.4.0__tar.gz

pico_ioc-1.4.0/.llm/ARCHITECTURE.md

@@ -0,0 +1,428 @@
+# pico-ioc — Architecture
+
+> **Scope:** internal model, wiring algorithm, lifecycle, and design trade-offs.
+> **Non-goals:** tutorials/recipes (see `GUIDE_CREATING_PLUGINS_AND_INTERCEPTORS.md`), product pitch.
+>
+> ⚠️ **Requires Python 3.10+** (uses `typing.Annotated` with `include_extras=True`).
+
+---
+
+## 1\) Design goals & non-goals
+
+### Goals
+
+  - **Tiny, predictable DI** for Python apps (CLIs, Flask/FastAPI, services).
+  - **Fail fast** at bootstrap; deterministic resolution.
+  - **Ergonomic**: typed constructors; minimal reflection; explicit decorators.
+  - **Framework-agnostic**: no hard deps on web frameworks.
+  - **Safe by default**: thread/async-friendly; no global mutable singletons.
+
+### Non-goals
+
+  - Full Spring feature set (complex scopes, bean post-processors).
+  - Hot reload or runtime graph mutation beyond explicit overrides.
+  - Magical filesystem-wide auto-imports.
+
+---
+
+## 2\) High-level model
+
+  - **Component** → class marked with `@component`. Instantiated by the container.
+  - **Config Component** → class marked with `@config_component`. Instantiated and populated from external sources like files or environment variables.
+  - **Factory component** → class marked with `@factory_component`; owns provider methods via `@provides(key=TypeOrToken)`. Providers return *externals* (e.g., `Flask`, DB clients).
+  - **Interceptor** → class or function marked with `@interceptor`. Discovered automatically to apply cross-cutting logic.
+  - **Container** → built by `pico_ioc.init(mod_or_list, ...)`; resolve with `container.get(KeyOrType)`.
+
+### Bootstrap sequence
+
+```mermaid
+sequenceDiagram
+    participant App as Your package(s)
+    participant IOC as pico-ioc Container
+    App->>IOC: init(packages, config, ...)
+    IOC->>IOC: Create ConfigRegistry from sources
+    IOC->>App: scan decorators (@component, @config_component, @interceptor)
+    IOC->>IOC: register providers and collect interceptor declarations
+    IOC->>IOC: build and activate interceptors
+    IOC->>IOC: apply policy (e.g., @primary, @on_missing aliases)
+    IOC->>IOC: apply overrides (replace providers/constants)
+    IOC->>IOC: instantiate eager components
+    App->>IOC: get(Service)
+    IOC->>IOC: resolve dependencies (with interception)
+    IOC-->>App: instance(Service)
+```
+
+---
+
+## 3\) Discovery & registration
+
+1.  **Scan inputs** passed to `init(...)`: module or list of modules/packages.
+2.  **Collect**:
+      * `@component` classes → registered by a **key** (defaults to the class type).
+      * `@config_component` classes → registered as special components whose instances are built from external configuration sources.
+      * `@factory_component` classes → introspected for `@provides(key=...)` methods.
+      * `@interceptor` classes/functions → collected for activation.
+      * `@plugin` classes → if explicitly passed via `init(..., plugins=(...))`.
+3.  **Registry** (frozen after bootstrap):
+      * Map **key → provider**. Keys are typically **types**; string tokens are also supported.
+
+**Precedence:** If multiple providers are active for the same key (e.g., one with `@primary`, another regular), a deterministic policy is applied to choose the winner. Direct overrides are applied last, having the final say.
+
+---
+
+## 4\) Resolution algorithm (deterministic)
+
+When constructing a component `C`:
+
+1.  Inspect `__init__(self, ...)`; collect **type-annotated** parameters (excluding `self`).
+2.  For each parameter `p: T`, resolve by this order:
+    1.  **By name**: if a provider key matches the parameter name `p` (if `prefer_name_first=True`).
+    2.  **Exact type** `T`.
+    3.  **MRO walk**: first registered base class of `T`.
+    4.  **By name (fallback)**: if a provider key matches the parameter name `p`.
+3.  Instantiate dependencies depth-first; cache singletons.
+4.  Construct `C` with resolved instances.
+
+### Failure modes
+
+  * **No provider** for a required key → **bootstrap error** (fail fast) with a full dependency chain.
+  * **Ambiguous/incompatible** registrations → policy resolves to a single provider or raises an error.
+
+### 4b) Collection resolution
+
+If the constructor requests `list[T]` or `list[Annotated[T, Q]]`:
+
+  * Return **all** compatible providers for `T`.
+  * If `Q` (qualifier) is present, filter to matching ones.
+  * Registration order is preserved; no implicit sorting.
+  * Returns an empty list if no matches.
+
+---
+
+## 5\) Lifecycles & scopes
+
+  * **Singleton per container**: a provider is instantiated at most once and cached.
+  * **Lazy proxies (optional)**: `@component(lazy=True)` or `@provides(lazy=True)` defers instantiation until first use via a `ComponentProxy`. Prefer eager to catch errors early.
+
+**Rationale:** Most Python app composition (config, clients, web apps) fits singleton-per-container; it’s simple and fast.
+
+---
+
+## 6\) Factories & providers
+
+Use `@factory_component` for **externals** (framework apps, DB clients, engines).
+
+```python
+from pico_ioc import factory_component, provides
+from flask import Flask
+
+@factory_component
+class AppFactory:
+    @provides(key=Flask)
+    def provide_flask(self) -> Flask:
+        app = Flask(__name__)
+        app.config["JSON_AS_ASCII"] = False
+        return app
+```
+
+Guidelines:
+
+  * Providers should be **pure constructors** (no long-running work).
+  * Prefer **typed keys** (e.g., `Flask`) over strings.
+
+---
+
+## 7\) Concurrency model
+
+  * Container state is **immutable after init**.
+  * Caches & resolution are **thread/async safe** (internal isolation; no global singletons).
+  * Instances you create **must** be safe for your usage patterns; the container cannot fix non-thread-safe libraries.
+
+---
+
+## 8\) Error handling & diagnostics
+
+  * **Bootstrap**:
+      * Missing providers → explicit `NameError` with full dependency chain details.
+      * Duplicate keys → resolved by policy, preferring `@primary`.
+  * **Runtime**:
+      * Exceptions from providers/constructors bubble up. The resolver path is included in the error for easier debugging.
+
+**Tip:** Keep constructors **cheap**; push I/O to explicit start/serve methods.
+
+---
+
+## 9\) Configuration
+
+Configuration is treated as a first-class, type-safe component using a dedicated injection system.
+
+1.  **Define a Config Class**: Create a class (preferably a `dataclass`) and mark it with `@config_component`. An optional `prefix` can be used for environment variables.
+
+    ```python
+    from pico_ioc import config_component
+    from dataclasses import dataclass
+
+    @config_component(prefix="APP_")
+    @dataclass(frozen=True)
+    class Settings:
+        db_url: str
+        timeout: int = 30
+    ```
+
+2.  **Provide Sources**: At bootstrap, pass an ordered tuple of `ConfigSource` objects to the `config` parameter of `init()`. The order defines precedence (first source wins).
+
+    ```python
+    from pico_ioc import init
+    from pico_ioc.config import EnvSource, FileSource
+
+    container = init(
+        "my_app",
+        config=(
+            EnvSource(prefix="APP_"), # Highest priority
+            FileSource("config.prod.yml", optional=True),
+            FileSource("config.yml"), # Lowest priority
+        ),
+    )
+    ```
+
+3.  **Inject and Use**: Inject the config class into other components just like any other dependency.
+
+    ```python
+    from pico_ioc import component
+
+    @component
+    class Database:
+        def __init__(self, settings: Settings):
+            self.connection = connect(settings.db_url)
+    ```
+
+### Resolution Logic
+
+  - **Automatic Binding**: By default, `pico-ioc` binds fields automatically. For a field like `db_url`, it checks for keys like `APP_DB_URL` (in `EnvSource`), `DB_URL`, or `db_url` (in `FileSource`).
+  - **Manual Overrides**: For more complex cases where keys don't align, you can use field-level helpers like `Env["CUSTOM_VAR"]`, `File["key.in.file"]`, or `Path.file["nested.key"]` to specify the exact key to use.
+
+This system ensures that configuration is **type-safe**, **externalized**, and **testable**, while remaining simple for the common cases.
+
+---
+
+## 10\) Overrides & composition
+
+### 10.1 Module-ordered overrides
+
+The policy engine respects definition order. While not a strict "last-wins", providers marked `@primary` will take precedence over others discovered during the scan.
+
+### 10.2 Direct overrides argument
+
+`init()` accepts an `overrides` dictionary for ad-hoc replacement.
+
+```python
+c = init(app, overrides={
+    Repo: FakeRepo(),                      # constant instance
+    "fast_model": lambda: {"mock": True},  # provider
+    "expensive": (lambda: object(), True), # provider with lazy=True
+})
+```
+
+**Semantics:**
+
+  * Applied **after scanning and policy** but before eager instantiation → replaced providers never run.
+  * Accepted forms:
+      * `key: instance`
+      * `key: callable`
+      * `key: (callable, lazy_bool)`
+  * With `reuse=True`, re-calling `init(..., overrides=...)` applies new overrides to the cached container.
+
+---
+
+## 11\) Interceptors (AOP & Lifecycle Hooks)
+
+Interceptors are components that apply cross-cutting logic like logging, metrics, or policy enforcement. They are discovered automatically via the `@interceptor` decorator.
+
+`pico-ioc` supports two kinds of interceptors:
+
+### Method Interceptors
+
+These implement the `MethodInterceptor` protocol and wrap method calls on any component, enabling Aspect-Oriented Programming (AOP). They are ideal for tracing, timing, caching, or feature toggles.
+
+```python
+from pico_ioc import interceptor
+from pico_ioc.interceptors import MethodInterceptor, Invocation
+
+@interceptor(order=-10) # lower order runs first
+class LoggingInterceptor(MethodInterceptor):
+    def __call__(self, inv: Invocation, proceed):
+        print(f"Calling {inv.method_name}...")
+        result = proceed()
+        print(f"Finished {inv.method_name}.")
+        return result
+```
+
+### Container Interceptors
+
+These implement the `ContainerInterceptor` protocol and hook into the container's internal lifecycle events.
+
+**Hook points**:
+
+  * `on_resolve(key, annotation, qualifiers)`
+  * `on_before_create(key)`
+  * `on_after_create(key, instance)` → may return a **wrapped/replaced** instance.
+  * `on_exception(key, exc)`
+
+**Registration:** Interceptors are discovered by the scanner during `init()` or `scope()`. There is no need to pass them manually. Their activation can be controlled with the same `@conditional` decorator and gates (`profiles`, `require_env`) used for other components.
+
+---
+
+## 12\) Profiles & conditional providers
+
+Use `@conditional` to **activate providers based on profiles, environment variables, or a predicate function**.
+
+```python
+from pico_ioc import component, conditional
+
+class Cache: ...
+
+@component
+@conditional(profiles=("prod", "staging"))
+class RedisCache(Cache): ...
+
+@component
+@conditional(require_env=("REDIS_URL",))
+class AnotherRedisCache(Cache): ...
+
+@component
+@conditional(predicate=lambda: os.path.exists("/tmp/use_mem"))
+class InMemoryCache(Cache): ...
+```
+
+**Rules**:
+
+  * `profiles=("A","B")` → active if any profile passed to `init()` or `scope()` matches.
+  * `require_env=("A","B")` → all environment variables must exist and be non-empty.
+  * `predicate=callable` → must return a truthy value to activate.
+  * If no active provider satisfies a required type and something depends on it → **bootstrap error** (fail fast).
+
+---
+
+## 13\) Qualifiers & collection injection
+
+Attach qualifiers to group/select implementations using `@qualifier`.
+
+  * Request `list[T]` → injects all registered implementations of `T`.
+  * Request `list[Annotated[T, Q]]` → injects only those implementations of `T` tagged with qualifier `Q`.
+
+This preserves registration order and returns a stable list.
+
+---
+
+## 14\) Plugins
+
+`@plugin` classes implementing the `PicoPlugin` protocol can observe the **container lifecycle**.
+
+  * `before_scan(package, binder)`
+  * `after_scan(package, binder)`
+  * `after_bind(container, binder)`
+  * `before_eager(container, binder)`
+  * `after_ready(container, binder)`
+
+Plugins are passed **explicitly** via `init(..., plugins=(MyPlugin(),))`. Prefer **interceptors** for fine-grained wiring events; use **plugins** for coarse lifecycle integration.
+
+---
+
+## 15\) Scoped subgraphs (`scope`)
+
+Build a **bounded container** containing only dependencies reachable from selected **roots**.
+
+```python
+from pico_ioc import scope
+from src.runner_service import RunnerService
+from tests.fakes import FakeDocker
+import src
+
+c = scope(
+    modules=[src],
+    roots=[RunnerService],
+    overrides={"docker.DockerClient": FakeDocker()},
+    strict=True, lazy=True,
+)
+svc = c.get(RunnerService)
+```
+
+### Tag-based pruning
+
+Providers may carry `tags` (via `@component(tags=...)` or `@provides(..., tags=...)`). `scope()` can filter the initial set of providers using `include_tags` and `exclude_tags` before traversing the dependency graph.
+
+### Semantics
+
+  * **Limited reach**: only providers transitively reachable from `roots` are included in the final graph.
+  * **Deterministic precedence**: `overrides > scoped providers > base container providers` (if `strict=False`).
+  * **Strict mode**: controls whether missing dependencies raise an error (`True`) or can be resolved from the `base` container (`False`).
+  * **Lifecycle**: still **singleton-per-container**; `scope` does **not** add request/session scopes.
+  * **Context manager**: `with scope(...):` is supported.
+
+**Use cases:** fast unit tests, integration-lite, CLI tools, microbenchmarks.
+
+---
+
+## 16\) Diagnostics & diagrams
+
+### Registry & resolution (class diagram)
+
+```mermaid
+classDiagram
+    class PicoContainer {
+      +get(key) instance
+      +get_all(base_type) sequence
+      +add_method_interceptor(it)
+      +add_container_interceptor(it)
+      - _providers: Map[key, ProviderMeta]
+      - _singletons: Map[key, instance]
+    }
+    class ProviderMeta {
+      + factory: Callable
+      + lazy: bool
+      + tags: tuple
+      + qualifiers: tuple
+    }
+    class MethodInterceptor {
+      +__call__(inv, proceed)
+    }
+    class ContainerInterceptor {
+      +on_resolve()
+      +on_before_create()
+      +on_after_create()
+      +on_exception()
+    }
+    PicoContainer "1" o-- "*" MethodInterceptor
+    PicoContainer "1" o-- "*" ContainerInterceptor
+```
+
+### Resolution flow (activity)
+
+```mermaid
+flowchart TD
+    A[get(Type T)] --> B{Cached?}
+    B -- yes --> Z[Return cached instance]
+    B -- no --> D[Resolve dependencies for T (recurse)]
+    D --> I_BEFORE[ContainerInterceptors: on_before_create]
+    I_BEFORE --> F[Instantiate T]
+    F -- exception --> I_EXC[ContainerInterceptors: on_exception]
+    F -- success --> H[Wrap with MethodInterceptors if needed]
+    H --> I_AFTER[ContainerInterceptors: on_after_create]
+    I_AFTER --> G[Cache instance]
+    G --> Z
+```
+
+---
+
+## 17\) Rationale & trade-offs
+
+  * **Typed keys first**: better IDE support; fewer foot-guns than strings.
+  * **Singleton-per-container**: matches typical Python app composition; simpler mental model.
+  * **Explicit decorators**: determinism and debuggability over magical auto-wiring.
+  * **Fail fast**: configuration and graph issues surface at startup, not mid-request.
+  * **Interceptors over AOP**: precise, opt-in hooks without full-blown aspect weavers.
+
+---
+
+**TL;DR**
+`pico-ioc` builds a **deterministic, typed dependency graph** from decorated components, factories, and interceptors. It resolves by **type** (with qualifiers and collections), memoizes **singletons**, supports **type-safe configuration injection**, **overrides**, **plugins**, **conditionals/profiles**, and **scoped subgraphs**—keeping wiring **predictable, testable, and framework-agnostic**.

pico_ioc-1.4.0/.llm/DECISIONS.md

@@ -0,0 +1,185 @@
+# DECISIONS.md — pico-ioc
+
+This document records **technical and architectural decisions** for pico-ioc.  
+Each entry includes a rationale and implications. If a decision is later changed, mark it **[REVOKED]** and link to the replacement.
+
+---
+
+## ✅ Current Decisions
+
+### 1) Minimum Python version: **3.10**
+**Decision**: Require Python **3.10+**; drop 3.8/3.9.  
+**Rationale**: `typing.Annotated` + `get_type_hints(..., include_extras=True)` simplify internals and enable qualifiers/collections.  
+**Implications**: Users on older runtimes must upgrade; CI matrix targets 3.10+.
+
+---
+
+### 2) Resolution order: **param name → exact type → MRO → string token**
+**Decision**: Name-first resolution with deterministic fallback.  
+**Rationale**: Ergonomic for common configs by name; still strongly typed.  
+**Implications**: Documented behavior; potential behavior change from older pre-1.0 versions.
+
+---
+
+### 3) Lifecycle model: **singleton per container**
+**Decision**: One instance per key per container.  
+**Rationale**: Matches typical Python app composition (config/clients/services); simple and fast.  
+**Implications**: No request/session scopes at IoC level; use framework facilities if needed. `lazy=True` is available but not default.
+
+---
+
+### 4) Fail-fast bootstrap
+**Decision**: Instantiate eager components after `init()`; surface errors early.  
+**Rationale**: Deterministic startup; no hidden runtime surprises.  
+**Implications**: Keep constructors cheap; push heavy I/O to explicit start/serve phases.
+
+---
+
+### 5) Keys: **typed keys preferred; string tokens allowed but discouraged**
+**Decision**: Prefer class/type keys (e.g., `Flask`) over string tokens.  
+**Rationale**: Better IDE support, fewer collisions, clearer intent.  
+**Implications**: String tokens remain for interop, but are a last resort.
+
+---
+
+### 6) Qualifiers & collection injection are **first-class**
+**Decision**: Support `Annotated[T, Q]` and `list[Annotated[T, Q]]` for filtering.  
+**Rationale**: Enables side-by-side implementations (primary/fallback) without custom registries.  
+**Implications**: Stable registration order is preserved for lists; empty lists are valid.
+
+---
+
+### 7) Plugins are **explicitly registered**
+**Decision**: No magical discovery; pass plugins to `init(..., plugins=(...))`.  
+**Rationale**: Predictability and testability.  
+**Implications**: Slightly more verbose, but boundaries stay explicit.
+
+---
+
+### 8) Public API helper (`export_public_symbols_decorated`)
+**Decision**: Provide a helper to auto-export decorated symbols in a package’s `__init__.py`.  
+**Rationale**: Reduces boilerplate; favors convention over configuration.  
+**Implications**: Dynamic export is opt-in; does not auto-register providers by itself.
+
+---
+
+### 9) Overrides in `init(...)`
+**Decision**: `init(..., overrides={...})` replaces bindings at bootstrap.  
+**Rationale**: Simple unit testing/mocking without extra modules.  
+**Implications**:
+- Applied **before eager instantiation** → replaced providers never run.  
+- Accepted forms:  
+  - `key: instance` (constant)  
+  - `key: callable` (provider, non-lazy)  
+  - `key: (callable, lazy_bool)` (provider with explicit laziness)  
+- With `reuse=True`, subsequent `init(..., overrides=...)` mutates cached bindings.
+
+---
+
+### 10) Scoped subgraphs with `scope(...)`
+**Decision**: Provide `scope(...)` to build a bounded container limited to the dependency subgraph of given roots.  
+**Rationale**: Faster, deterministic unit/integration setups; great for CLIs/benchmarks.  
+**Implications**:
+- **Not** a new lifecycle: still singleton-per-container.  
+- Supports `include_tags`/`exclude_tags` (tags from `@component(..., tags=...)` / `@provides(..., tags=...)`).  
+- `strict=True` fails if deps are outside subgraph.  
+- Works as a context manager to ensure clean teardown.
+
+---
+
+### 11) **Interceptors API** (AOP & Lifecycle Hooks)
+**Decision**: Introduce two types of interceptors, auto-discovered via `@interceptor`, to observe or modify container and component behavior.
+**Kinds & Hooks**:
+- **`MethodInterceptor`**: Implements `__call__(self, inv: Invocation, proceed)`. Wraps method calls on components for Aspect-Oriented Programming (AOP) use cases like logging, tracing, or caching.
+- **`ContainerInterceptor`**: Implements container lifecycle hooks:
+    - `on_resolve(key, annotation, qualifiers)`
+    - `on_before_create(key)`
+    - `on_after_create(key, instance)` (may wrap/replace the instance)
+    - `on_exception(key, exc)`
+**Rationale**: Provides structured extension points for both cross-cutting concerns (AOP) and container lifecycle events without the complexity of full aspect weavers.
+**Implications**:
+- Deterministic ordering via `order` (lower runs first).
+- Auto-registered via `@interceptor(...)` on classes or provider methods.
+- `on_exception` must re-raise if the error is not meant to be suppressed.
+
+---
+
+### 12) **Conditional providers** (profiles, env, predicate)
+**Decision**: `@conditional(profiles=(...), require_env=(...), predicate=callable)` activates providers based on environment vars or logic.  
+**Rationale**: Profile-driven wiring (`PROFILE=test/prod/ci`), optional integrations (Redis/S3) without code changes.  
+**Implications**:
+- If no active provider satisfies a required type → **bootstrap error** (or at resolution if lazy).  
+- Multiple candidates may be active (use qualifiers/collections to select).  
+- Works seamlessly with `scope(...)`; conditionals apply before traversal.
+
+---
+
+### 13) Deterministic Provider Selection: **Policy-driven, preferring @primary**
+**Decision**: When multiple providers implement the same base type, the selection is not a simple "last-wins". Instead, a policy is applied:
+1.  If one or more candidates are decorated with `@primary`, the first one found will be chosen.
+2.  If no candidates are marked as primary, the selection may fall back to providers decorated with `@on_missing`, or other aliasing logic.
+A true "last-wins" only occurs when binding the *exact same key* multiple times, which overwrites the previous provider entry.
+**Rationale**: This provides more explicit control over which implementation is the default, making the dependency graph more predictable than relying solely on scan order.
+**Implications**: To select a default implementation for an interface, use `@primary`. Module ordering is a less reliable mechanism for this purpose.
+
+---
+
+### 14) Concurrency & safety
+**Decision**: Container is immutable after `init()`; caches are isolated and safe across threads/tasks; no global singletons.  
+**Rationale**: Avoid shared mutable state; enable safe parallel use.  
+**Implications**: Make your **own** instances thread/async-safe if they’re shared.
+
+---
+
+### 15) Configuration Injection
+**Decision**: Provide `@config_component` for strongly typed configuration classes, populated from ordered `ConfigSource`s (`EnvSource`, `FileSource`, etc.).  
+**Rationale**: Type-safe configuration with minimal boilerplate, supporting both automatic autowiring by field name and manual overrides (`Env`, `File`, `Path`, `Value`).  
+**Implications**:
+- Precedence is explicit: `overrides` > sources (in order) > field defaults.
+- Missing required fields (no default and not resolvable) raise `NameError`.
+- Supported formats: env vars, JSON, INI, dotenv, YAML (if available).
+- Encourages using `dataclass(frozen=True)` for immutable, validated settings.
+
+---
+
+## ❌ Won’t-Do Decisions
+
+### A) Alternative scopes (request/session)
+**Decision**: No extra lifecycles beyond singleton-per-container.  
+**Rationale**: Keep model simple; delegate per-request/session to frameworks.  
+**Implications**: Avoids ownership ambiguity and complexity.
+
+---
+
+### B) Asynchronous providers (`async def`)
+**Decision**: Not supported inside the container.  
+**Rationale**: Simplicity and determinism; no loop coupling in core.  
+**Implications**: If async init is required, handle it inside your component explicitly.
+
+---
+
+### C) Hot reload / dynamic re-scan
+**Decision**: Not supported.  
+**Rationale**: Conflicts with fail-fast and immutability; complicates debugging.  
+**Implications**: Use framework/dev tools for code reload (e.g., `uvicorn --reload`).
+
+---
+
+## 🗃️ Deprecated / Revoked
+
+_No entries currently._
+
+---
+
+## 📜 Changelog of Decisions
+
+- **2025-08**: Minimum Python 3.10; name-first resolution; fail-fast clarified; typed keys preferred.  
+- **2025-09-08**: Introduced `init(..., overrides)` with defined precedence and laziness semantics.  
+- **2025-09-13**: Added `scope(...)` for bounded containers with tag pruning and strict mode.  
+- **2025-09-14**: Added **Interceptors API** and **Conditional providers** as first-class features; documented last-wins registration and concurrency stance.
+
+---
+
+**Summary**: pico-ioc remains **simple, deterministic, and fail-fast**.  
+We favor typed wiring, explicit registration, and small, composable primitives (overrides, scope, interceptors, conditionals) instead of heavyweight AOP or multi-scope lifecycles.
+