super-solid-system 1.0.0__tar.gz

super_solid_system-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 [2026] [Doth-J]
+
+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.

super_solid_system-1.0.0/PKG-INFO

@@ -0,0 +1,494 @@
+Metadata-Version: 2.4
+Name: super-solid-system
+Version: 1.0.0
+Summary: A lightweight, type-safe microkernel & plug-and-play framework for Python.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: microkernel,plugin,registry,modular,framework,dependency-injection,type-safe
+Author: Doth-J
+Author-email: theodjoan@gmail.com
+Requires-Python: >=3.10
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Typing :: Typed
+Requires-Dist: pydantic (>=2.0.0)
+Project-URL: Homepage, https://github.com/Doth-J/super-solid-system
+Project-URL: Issues, https://github.com/Doth-J/super-solid-system/issues
+Project-URL: Repository, https://github.com/Doth-J/super-solid-system
+Description-Content-Type: text/markdown
+
+# Super-Solid System (`supersolid`)
+
+<p align="center">
+  <img src="docs/logo.png" alt="Super-Solid" width="250"/>
+</p>
+
+<h1 align="center">Super-Solid System</h1>
+
+<p align="center">
+  <strong>A robust, generic infrastructure for building modular software systems with plug-and-play engines, dynamic plugin discovery, thread-safe component registries, and fault-tolerant system lifecycle management.</strong><br/>
+</p>
+
+<p align="center">
+  <img alt="Python" src="https://img.shields.io/badge/python-%3E%3D3.10-blue?logo=python&logoColor=white"/>
+  <img alt="License" src="https://img.shields.io/badge/license-Apache%202.0-green"/>
+  <img alt="Tests" src="https://img.shields.io/badge/tests-43%2F43%20passing-brightgreen"/>
+  <img alt="Coverage" src="https://img.shields.io/badge/coverage-100%25-brightgreen"/>
+  <img alt="Status" src="https://img.shields.io/badge/status-v1.0.0-brightgreen"/>
+</p>
+
+> A lightweight, type-safe microkernel & plug-and-play framework for Python.
+
+## What is Super-Solid System?
+
+Super-Solid System (`S³`) gives you a small set of building blocks for assembling modular applications:
+
+- **Registries** hold your components — type-checked, thread-safe, and cached.
+- **Engines** group registries together and handle boot/shutdown logic.
+- **Systems** orchestrate engines in dependency order with automatic rollback.
+- **Events** let everything talk to each other through a reactive signal bus.
+- **Security** controls who can load what and from where.
+- **Health** provides a standard way for components to report their status.
+
+No magic, no hidden state, no framework lock-in. Just clean abstractions you subclass and wire up.
+
+## Architecture
+
+```mermaid
+graph TD
+    S["SuperSolidSystem"]
+    EB["SuperSolidEventBus"]
+    E1["SuperSolidEngine A"]
+    E2["SuperSolidEngine B"]
+    R1["SuperSolidRegistry 1"]
+    R2["SuperSolidRegistry 2"]
+    R3["SuperSolidRegistry 3"]
+    D["DiscoveryStrategy Chain"]
+    SP["SecurityPolicy"]
+    H["HealthCheckable"]
+
+    S -->|starts / stops| E1
+    S -->|starts / stops| E2
+    S -->|publishes signals| EB
+    E1 -->|routes loads to| R1
+    E1 -->|routes loads to| R2
+    E2 -->|routes loads to| R3
+    R1 -->|discovers plugins via| D
+    R1 -.->|enforced by| SP
+    R2 -.->|enforced by| SP
+    E1 -.->|implements| H
+    E2 -.->|implements| H
+```
+
+The core loop is simple:
+
+1. **Register** component classes into typed registries (or let discovery find them).
+2. **Load** components on demand — the registry instantiates, caches, and returns them.
+3. **Wire** registries into engines, engines into a system, and call `start()`.
+
+## Installation
+
+### Pip (editable, for development)
+
+```bash
+pip install -e /path/to/super-solid-system
+```
+
+### Poetry (as a local dependency)
+
+```bash
+poetry add --editable /path/to/super-solid-system
+```
+
+### Docker (Multi-stage build)
+
+```bash
+# Build the production Docker image
+docker build -t super-solid-system:latest .
+
+# Run container & verify installation
+docker run --rm super-solid-system:latest
+```
+
+## Quickstart
+
+### 1. Define a base interface and a registry
+
+```python
+from abc import ABC, abstractmethod
+from supersolid.core import super_solid_registry, SuperSolidRegistry
+
+class BaseAdapter(ABC):
+    @abstractmethod
+    def connect(self) -> None: ...
+
+# [QUICK] Create a typed component registry using super_solid_registry
+Adapters = super_solid_registry(name="adapters", component_class=BaseAdapter)
+
+# [ALTERNATIVE] Create a class component registry by subclassing SuperSolidRegistry
+class AdapterRegistry(SuperSolidRegistry[BaseAdapter]):
+    def __init__(self):
+        super().__init__(name="adapters", component_class=BaseAdapter)
+
+Adapters = AdapterRegistry()
+```
+
+`SuperSolidRegistry` is generic — it enforces that only `BaseAdapter` subclasses can be registered here. Anything else raises a `TypeError` at registration time.
+
+### 2. Register components
+
+You can register manually:
+
+```python
+Adapters.register("database", "sqlite", SqliteAdapter)
+```
+
+Or use the `@super_solid_component` decorator for a more declarative style:
+
+```python
+from supersolid.core import super_solid_component
+
+@super_solid_component(Adapters, namespace="database", name="postgres", version="1.0.0")
+class PostgresAdapter(BaseAdapter):
+    def __init__(self, dsn: str = "postgresql://localhost/db"):
+        self.dsn = dsn
+
+    def connect(self) -> None:
+        print(f"Connected to {self.dsn}")
+
+    def disconnect(self) -> None:
+        print("Disconnected.")
+```
+
+The decorator registers the class and attaches a `ComponentMetadata` model you can inspect later:
+
+```python
+PostgresAdapter._metadata.version   # "1.0.0"
+PostgresAdapter._metadata.namespace # "database"
+```
+
+### 3. Load components
+
+```python
+db = Adapters.load("database", "postgres", dsn="postgresql://prod/mydb")
+db.connect()  # Connected to postgresql://prod/mydb
+```
+
+What happens under the hood:
+
+1. Checks the cache — if already loaded with the same parameters, returns the cached instance.
+2. If not registered, runs the **discovery chain** (more on that below).
+3. Introspects the constructor signature and filters keyword arguments automatically.
+4. Calls lifecycle hooks (`initialize()` or `boot()`) if the component defines them.
+5. Caches and returns the instance.
+
+When you're done:
+
+```python
+Adapters.unload("database", "postgres")
+# Calls disconnect() or stop() automatically if the component defines them
+```
+
+### 4. Build an engine
+
+A `SuperSolidEngine` groups registries and provides a unified loading interface:
+
+```python
+from supersolid.core import SuperSolidEngine
+
+class CoreEngine(SuperSolidEngine):
+    def __init__(self):
+        super().__init__()
+        self.connect(Adapters)  # attach registries
+
+    def boot(self, **kwargs) -> None:
+        self._running = True
+        db = self.load("adapters", "database", "postgres")
+        db.connect()
+
+    def mount(self, app, **kwargs) -> None:
+        pass  # hook for attaching to a web framework, etc.
+
+    def shutdown(self, **kwargs) -> None:
+        self._running = False
+```
+
+Need async? Subclass `SuperSolidAsyncEngine` instead — it provides `boot_async()`, `mount_async()`, and `shutdown_async()` that automatically bridge to the sync interface via `asyncio.run()`.
+
+### 5. Orchestrate with a system
+
+```python
+from supersolid.core import SuperSolidSystem
+
+class MyApp(SuperSolidSystem):
+    pass
+
+app = MyApp()
+app.add_engine("core", CoreEngine())
+app.start()  # boots engines in dependency order
+# ... your app runs ...
+app.stop()   # shuts down in reverse order
+```
+
+If any engine fails during `start()`, all previously booted engines are shut down in reverse (LIFO) order automatically.
+
+## Engine Dependencies (Dependency Resolution)
+
+Engines can declare dependencies on other engines:
+
+```python
+class ConsensusEngine(SuperSolidEngine):
+    depends_on = ["network"]  # boot network engine first
+    # ...
+
+class NetworkEngine(SuperSolidEngine):
+    depends_on = []
+    # ...
+
+system = MyApp()
+system.add_engine("consensus", ConsensusEngine())
+system.add_engine("network", NetworkEngine())
+system.start()
+# Boot order: network → consensus (resolved via topological sort)
+```
+
+The system uses the internal `graphlibs` `TopologicalSorter` so circular dependencies raise a `CycleError` immediately.
+
+## Events
+
+`SuperSolidSystem` comes with a built-in `SuperSolidEventBus` that publishes lifecycle signals automatically:
+
+| Event                 | When it fires                      |
+| :-------------------- | :--------------------------------- |
+| `EngineBootingEvent`  | Right before an engine boots       |
+| `EngineBootedEvent`   | After an engine boots successfully |
+| `EngineShutdownEvent` | After an engine shuts down         |
+| `SystemErrorEvent`    | On boot failure or shutdown error  |
+| `PluginLoadedEvent`   | When a plugin is loaded            |
+
+### Subscribing to events
+
+```python
+from supersolid.core import SuperSolidEventBus, EngineBootedEvent, super_solid_subscriber
+
+bus = SuperSolidEventBus()
+
+@super_solid_subscriber(bus)
+def on_boot(event: EngineBootedEvent):
+    print(f"Engine '{event.engine_name}' is up!")
+```
+
+The decorator infers the event type from the parameter annotation. You can also be explicit:
+
+```python
+@super_solid_subscriber(bus, event_type=EngineBootedEvent)
+def on_boot(event):
+    print(f"Engine '{event.engine_name}' is up!")
+```
+
+### Publishing events
+
+The `@super_solid_publisher` decorator auto-publishes a function's return value if it's a `SystemEvent`:
+
+```python
+from supersolid.core import super_solid_publisher, EngineBootedEvent
+
+@super_solid_publisher(bus)
+def finish_boot(name: str) -> EngineBootedEvent:
+    # ... do boot work ...
+    return EngineBootedEvent(engine_name=name)
+
+finish_boot("consensus")  # automatically published to bus
+```
+
+Works with both sync and async functions.
+
+### Custom events
+
+All events are Pydantic models with `extra = "allow"`, so you can add any fields:
+
+```python
+from supersolid.core import SystemEvent
+
+class NodeSyncEvent(SystemEvent):
+    node_id: str
+    epoch: int
+
+# Extra fields work too — they serialize to JSON just fine
+event = NodeSyncEvent(node_id="node_01", epoch=42, custom_field="whatever")
+event.model_dump_json()
+```
+
+## Plugin Discovery
+
+When you call `registry.load()` for something that isn't registered yet, the registry runs a **discovery chain** to try to find it automatically. The default chain has three strategies:
+
+```mermaid
+graph LR
+    A["InternalLib"] -->|not found| B["EntryPoints"]
+    B -->|not found| C["PluginDirectory"]
+    style A fill:#4a9,stroke:#333,color:#fff
+    style B fill:#49a,stroke:#333,color:#fff
+    style C fill:#a94,stroke:#333,color:#fff
+```
+
+| Strategy          | Where it looks                                                            |
+| :---------------- | :------------------------------------------------------------------------ |
+| `InternalLib`     | `{root_pkg}.lib.{registry_name}.{namespace}_{name}` (trusted imports)     |
+| `EntryPoints`     | Setuptools entry points in group `{root_pkg}.{registry_name}.{namespace}` |
+| `PluginDirectory` | `plugins.{registry_name}.{namespace}_{name}` (local files)                |
+
+### Writing a custom discovery strategy
+
+```python
+from supersolid.core import DiscoveryStrategy
+
+class RemoteDiscovery(DiscoveryStrategy):
+    def discover(self, registry, item_namespace, item_name) -> bool:
+        # fetch plugin from remote source, register it
+        return registry.is_registered(item_namespace, item_name)
+
+Adapters.add_discovery(RemoteDiscovery())
+```
+
+## Security
+
+### SecurityPolicy
+
+Attach a `SecurityPolicy` to any registry to control access:
+
+```python
+from supersolid.core import SecurityPolicy
+
+policy = SecurityPolicy(
+    allowed_namespaces={"database", "cache"},  # only these namespaces can be loaded
+    allowed_callers={"core_engine"},            # only these caller IDs are authorized
+    allow_internal_lib=True,                    # trusted internal imports still work
+    allow_dynamic_discovery=False,              # block external plugins (EntryPoints, PluginDirectory)
+)
+
+Adapters.set_policy(policy)
+```
+
+Now `Adapters.load("auth", "oauth")` raises `PermissionError` because `"auth"` isn't in the allowed set. And external discovery strategies are skipped entirely, while `InternalLib` still runs as a trusted fallback.
+
+### Plugin verification
+
+Before importing a plugin file, you can verify its checksum:
+
+```python
+from supersolid.core import PluginVerifier
+
+if PluginVerifier.verify_sha256("plugins/consensus/my_plugin.py", expected_hash):
+    import plugins.consensus.my_plugin
+```
+
+## Health Checks
+
+Any component can implement health reporting by defining a `health_check()` method:
+
+```python
+from supersolid.core import HealthStatus, HealthState, HealthCheckable
+
+class DatabaseAdapter:
+    def health_check(self) -> HealthStatus:
+        return HealthStatus(
+            state=HealthState.HEALTHY,
+            details={"connections": 42, "pool_size": 100}
+        )
+
+db = DatabaseAdapter()
+isinstance(db, HealthCheckable)  # True — structural typing via Protocol
+db.health_check().model_dump_json()
+# {"state": "healthy", "details": {"connections": 42, "pool_size": 100}, "timestamp": ...}
+```
+
+`HealthCheckable` is a `@runtime_checkable` Protocol — no need to inherit from anything.
+
+The three states are `HEALTHY`, `DEGRADED`, and `UNHEALTHY`.
+
+## Project Structure
+
+```
+super-solid-system/
+├── supersolid/
+│   └── core/
+│       ├── __init__.py       # Public API exports
+│       ├── registry.py       # SuperSolidRegistry, super_solid_component, ComponentMetadata
+│       ├── engine.py         # SuperSolidEngine, AsyncSuperSolidEngine
+│       ├── system.py         # SuperSolidSystem (orchestrator)
+│       ├── events.py         # SuperSolidEventBus, SystemEvent, super_solid_subscriber, super_solid_publisher
+│       ├── discovery.py      # DiscoveryStrategy, InternalLib, EntryPoints, PluginDirectory
+│       ├── security.py       # SecurityPolicy, PluginVerifier
+│       └── health.py         # HealthStatus, HealthState, HealthCheckable
+├── tests/
+│   ├── test_registry.py      # Registration, loading, type enforcement, thread safety, unload
+│   ├── test_events.py        # Event bus pub/sub, @open_subscriber, @open_publisher
+│   ├── test_security.py      # Namespace ACL, caller auth, discovery fallbacks, SHA-256
+│   ├── test_health.py        # Health models, Protocol duck typing
+│   └── test_system.py        # DAG resolution, start/stop, rollback on failure
+├── pyproject.toml
+├── LICENSE
+└── README.md
+```
+
+---
+
+## API Reference
+
+| Export                   | Module           | What it does                                                                                     |
+| :----------------------- | :--------------- | :----------------------------------------------------------------------------------------------- |
+| `SuperSolidSystem`       | `core.system`    | Orchestrator — boots/stops engines in dependency order (`SolidSystem`, `OpenSystem`)             |
+| `SuperSolidEngine`       | `core.engine`    | Domain hub — groups registries, handles boot/mount/shutdown (`SolidEngine`, `OpenEngine`)        |
+| `SuperSolidAsyncEngine`  | `core.engine`    | Async variant supporting `boot_async()`, `mount_async()` (`SolidAsyncEngine`, `AsyncOpenEngine`) |
+| `SuperSolidRegistry`     | `core.registry`  | Generic registry — type checks, caching, discovery (`SolidRegistry`, `OpenRegistry`)             |
+| `super_solid_registry`   | `core.registry`  | Factory function — instantiates a `SuperSolidRegistry` (`solid_registry`, `open_registry`)       |
+| `super_solid_component`  | `core.registry`  | Decorator — registers a class with metadata (`solid_component`, `open_component`)                |
+| `ComponentMetadata`      | `core.registry`  | Pydantic model — name, namespace, version, and extras                                            |
+| `SuperSolidEventBus`     | `core.events`    | In-memory pub/sub signal bus (`SolidEventBus`, `OpenEventBus`)                                   |
+| `SystemEvent`            | `core.events`    | Base event model (Pydantic, extra fields allowed)                                                |
+| `super_solid_subscriber` | `core.events`    | Decorator — subscribes handler with type inference (`solid_subscriber`, `open_subscriber`)       |
+| `super_solid_publisher`  | `core.events`    | Decorator — auto-publishes return values (`solid_publisher`, `open_publisher`)                   |
+| `DiscoveryStrategy`      | `core.discovery` | Abstract base — subclass to write custom plugin discovery                                        |
+| `SecurityPolicy`         | `core.security`  | Pydantic model — namespace/caller ACL, discovery toggles                                         |
+| `PluginVerifier`         | `core.security`  | SHA-256 file checksum verification                                                               |
+| `HealthStatus`           | `core.health`    | Pydantic model — state, details, timestamp                                                       |
+| `HealthState`            | `core.health`    | Enum — `HEALTHY`, `DEGRADED`, `UNHEALTHY`                                                        |
+| `HealthCheckable`        | `core.health`    | Protocol — any class with `health_check()` satisfies it                                          |
+
+## Running Tests
+
+Run the test suite with coverage report:
+
+```bash
+poetry run python -m pytest --cov=supersolid --cov-report=term-missing
+```
+
+```text
+Name                           Stmts   Miss  Cover
+--------------------------------------------------
+supersolid/__init__.py             2      0   100%
+supersolid/core/__init__.py        8      0   100%
+supersolid/core/discovery.py      43      0   100%
+supersolid/core/engine.py         49      0   100%
+supersolid/core/events.py         85      0   100%
+supersolid/core/health.py         14      0   100%
+supersolid/core/registry.py      154      0   100%
+supersolid/core/security.py       24      0   100%
+supersolid/core/system.py         59      0   100%
+--------------------------------------------------
+TOTAL                            438      0   100%
+
+============================= 43 passed in 1.12s ==============================
+```
+
+## License
+
+[Apache-2.0](LICENSE)
+