roboz 0.1.2.dev6__tar.gz → 0.1.2.dev8__tar.gz

{roboz-0.1.2.dev6 → roboz-0.1.2.dev8}/CHANGELOG.md

@@ -2,13 +2,52 @@
 
 ## Unreleased
 
+## 0.1.2.dev8 - 2026-09-20
+
+- Breaking: remove the legacy agent master tool. Model-driven agents run
+  their configured default tools followed by the built-in `prompt_agent` tool;
+  deterministic agents require and run only their configured default tools.
+  Use `default_tools` to configure deterministic steps instead of relying on
+  the removed `master_tool` attribute.
+
+- Show every displayed tool's external dependency IDs and kinds in
+  `Agent.show_agent_info()`.
+
+## 0.1.2.dev7 - 2026-09-20
+
+- Breaking: replace the `is_agentic` boolean with the string-valued
+  `AgentMode.DETERMINISTIC`, `.STEERABLE`, or `.AUTONOMOUS` enum (the default
+  remains steerable). Autonomous agents use model-driven scheduling without a
+  user-input tool or direct user-interaction sidecar; their tools communicate
+  through the event pipe. Remove `interaction_mode` arguments and
+  `set_interaction_mode` calls: invocation uses a bound host channel, defaulting
+  to CLI, and restores the previous binding automatically. Registering a
+  `UserIO` adapter selects `Output.API` for the binding's lifetime.
+  `AgentMode` now lives in `roboz.models`; the existing `roboz.agent` export
+  remains available for compatibility.
+
+- Run each configured default tool exactly once per cycle for deterministic agents.
+  Model-driven agents retain their master-tool step.
+
+- Filter conversation history with `roboz.models.filter_messages` by role,
+  requested action, or result caller while retaining message order and metadata.
+
+- Call `get_completion(endpoint=..., messages=...)` directly without an API
+  callback. `MockLLMEndpoint` now accepts literal text responses as well as JSON
+  objects and exceptions.
+- Breaking: completions without an output model or tool list now return raw text
+  verbatim instead of attempting action validation. Supply `LlmOutputModel=...`
+  or `active_tools=...` to retain structured dictionary results and repair retries.
+  Endpoint and callback arguments are mutually exclusive. See the
+  [completion guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/tool-authoring.md#standalone-llm-backed-tools).
+
 ## 0.1.2.dev6 - 2026-09-15
 
 - Breaking: make the `roboz` root a lazy authoring facade. It now exports only
   `Agent`, `Skill`, `Tool`, `Factory`, `tool`, and `factory` alongside discoverable
   domain namespaces. Import models from `roboz.models`, agent helpers from
   `roboz.agent`, built-in tools from `roboz.tools`, and context protocols from
-  `roboz.tooling`. See [the import migration guide](docs/imports.md).
+  `roboz.tooling`. See [the import migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/imports.md).
 
 ## 0.1.2.dev5 - 2026-09-13
 
@@ -28,7 +67,7 @@
   stay side-effect free. Endpoints support explicit early `materialize()` calls
   while preserving their identity; prompt contexts delegate initialization.
   Breaking: OpenAI-compatible client protocols now require `close() -> None` for
-  typed cleanup. See [the lifecycle contract](docs/dependency-primitives.md).
+  typed cleanup. See [the lifecycle contract](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
 
 - Make resource-inspection declarations explicit: aggregate contexts and agents
   implement the `HasExternalDependencies` protocol, renamed from `Context` with
@@ -44,20 +83,20 @@
   share supplied state. Agent inspection uses live tool methods, and deployment
   builders use the same bindings. Restore top-level agent, skill, and built-in
   tool exports; removed dependency and `Ctx` APIs stay removed. See
-  [the primitive migration](docs/dependency-primitives.md).
+  [the primitive migration](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
 
 - Breaking: core endpoints require synchronous OpenAI-compatible clients instead
   of an untyped client. Client methods and request controls are checked statically;
   the real `openai.OpenAI` client satisfies the protocols without a wrapper or an
   SDK dependency in core. Replace placeholder or incompatible clients with a
-  conforming chat/transcription client. See [the client contract](docs/dependency-primitives.md).
+  conforming chat/transcription client. See [the client contract](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
 
 - Breaking: external resource implementations must provide `check() -> bool` for
   explicit availability checks. Executables check PATH; core endpoints use model
   discovery without generating output. Results are uncached, absent resources
   return `False`, and check errors propagate. Binding, copying, and inspection
   never invoke checks. Plain contexts need no check method. See
-  [resource inspection and availability](docs/dependency-primitives.md).
+  [resource inspection and availability](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
 
 - Accept any concretely typed factory context, including plain objects and lists.
   Contexts without resource inspection are passed through unchanged and their
@@ -67,7 +106,7 @@
   retaining their identity and client for execution and inspection. Endpoint
   request helpers and the selector now use concrete endpoints; lazy construction
   and companion migrations remain deferred. Scripted endpoints report no external
-  resources. See [typed contexts and resource inspection](docs/dependency-primitives.md).
+  resources. See [typed contexts and resource inspection](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md).
 - Fix `@factory()` input inference so parenthesized factories retain the same
   concrete input, output, and context types as bare `@factory` declarations.
 
@@ -78,7 +117,7 @@
   stay in `roboz.dependencies`; the top-level API now exposes only data and
   tool/factory/context primitives. Remove legacy dependency bases, lazy/reference
   helpers, and checker registration. Agent, built-in tool, and companion consumers
-  remain unmigrated; this checkpoint is not release-ready. See [typed contexts and resource inspection](docs/dependency-primitives.md)
+  remain unmigrated; this checkpoint is not release-ready. See [typed contexts and resource inspection](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/dependency-primitives.md)
   for the contract, removed APIs, and migration boundary.
 
 ## 0.1.2.dev4 - 2026-09-12
@@ -106,7 +145,7 @@
   and background agents start through default tools. Construct generic
   definitions directly with `DeployableAgent(...)`.
   Sandbox-aware `Deployment` lives in `roboshed.deployments`, not core.
-  See `docs/agent-factories.md` for migration.
+  See [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md) for migration.
 
 ## 0.1.2.dev2 - 2026-09-09
 
@@ -116,7 +155,7 @@
 
 - Breaking: move dependency primitives from `roboz.tooling.dependencies` and
   `roboz.tooling` to `roboz.dependencies`. Update those imports; the existing
-  top-level `roboz` authoring API remains available. See `docs/context-migration.md`.
+  top-level `roboz` authoring API remains available. See [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md).
 
 - Add `DependencyRoute` for live caller-owned selections. Materialization and discovery delegate to the current target without introducing a separate identity or caching the selection.
 
@@ -124,11 +163,11 @@
   Capabilities own their tool-specific endpoint choices and receive the agent
   endpoint as a fallback, independently of runtime controls. Lazy/live
   references retain identity and deferred resolution. See
-  `docs/agent-factories.md` for builder migration.
+  [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md) for builder migration.
 
-- Breaking: move the Librarian and its memory/summarization tools out of core into `roboshed.agents` and `roboshed.tools`. Use `librarian(sandbox, agent_names, agent_endpoint=...)` instead of `LibrarianConstructor` and its path record; see `docs/agent-factories.md`. Core retains control, interaction, and generic construction primitives.
+- Breaking: move the Librarian and its memory/summarization tools out of core into `roboshed.agents` and `roboshed.tools`. Use `librarian(sandbox, agent_names, agent_endpoint=...)` instead of `LibrarianConstructor` and its path record; see [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md). Core retains control, interaction, and generic construction primitives.
 
-- Add generic `AgentDefinition`, `AgentCapability`, `Capability`, and `SubAgentSpec` in `roboz.deployment`. Configure all tools and skills through capabilities, with fresh agent pipes and explicit sink configuration; definitions select no project, memory, or persistence conventions. See `docs/agent-factories.md`.
+- Add generic `AgentDefinition`, `AgentCapability`, `Capability`, and `SubAgentSpec` in `roboz.deployment`. Configure all tools and skills through capabilities, with fresh agent pipes and explicit sink configuration; definitions select no project, memory, or persistence conventions. See [the archived agent migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/agent-factories.md).
 
 - Breaking: `roboz[shed]` now installs `roboshed` instead of `roboz-shed`. Update direct requirements to `roboshed` and imports from `roboz_shed` to `roboshed`; no compatibility package is provided.
 
@@ -149,7 +188,7 @@
   Contexts implement `ExternalDependencySource`, preserving resource identity
   and reflecting live nested contexts, agents, and catalogs without resolving
   lazy resources. `external_dependencies` is now a reserved context field name;
-  see `docs/context-migration.md`.
+  see [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md).
 
 ### Fixed
 
@@ -161,7 +200,7 @@
 - **Breaking:** Construct tool contexts with `Ctx(**values)` and pass resources
   directly. Remove `FactoryCtx`, specialized context classes, `ToolDependency`,
   and endpoint binding wrappers; `Tool.dependencies` now returns resources.
-  See `docs/context-migration.md` for replacements and state ownership.
+  See [the archived context migration guide](https://github.com/Tachion-Oy/roboz/blob/roboz-v0.1.2.dev7/docs/context-migration.md) for replacements and state ownership.
 
 - Define and enforce Google-style source docstrings, and normalize tool
   docstrings before including them in agent prompts.

roboz-0.1.2.dev8/PKG-INFO

@@ -0,0 +1,283 @@
+Metadata-Version: 2.5
+Name: roboz
+Version: 0.1.2.dev8
+Import-Name: roboz
+Summary: Typed primitives for composable agentic workflows
+Project-URL: Homepage, https://github.com/Tachion-Oy/roboz
+Project-URL: Repository, https://github.com/Tachion-Oy/roboz
+Project-URL: Issues, https://github.com/Tachion-Oy/roboz/issues
+Project-URL: Documentation, https://github.com/Tachion-Oy/roboz#readme
+Author: Tachion Oy
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,llm,tool-calling,typing,workflows
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Requires-Dist: pydantic>=2.12.4
+Requires-Dist: python-dotenv>=1.2.1
+Requires-Dist: rich>=14.2.0
+Provides-Extra: proton-bridge-beta
+Requires-Dist: roboz-proton-bridge<0.2.0,>=0.1.0b1; extra == 'proton-bridge-beta'
+Description-Content-Type: text/markdown
+
+<div align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/roboz-logo-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="docs/assets/roboz-logo-light.svg">
+    <img alt="RoboZ" src="docs/assets/roboz-logo-dark.svg" width="560">
+  </picture>
+
+  <p><strong>Chain tools. Skip calls.</strong></p>
+</div>
+
+RoboZ is a framework for building llm powered agents. The core ingredient is that every tool may be chained conditionally to a subsequent tool thus allowing easy injection of deterministic flows into agentic processes.
+
+[![CI](https://github.com/Tachion-Oy/roboz/actions/workflows/ci.yml/badge.svg)](https://github.com/Tachion-Oy/roboz/actions/workflows/ci.yml)
+[![Python 3.13+](https://img.shields.io/badge/Python-3.13%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+
+> [!WARNING]
+> RoboZ is pre-release software requiring Python 3.13 or newer. APIs may change
+> before 1.0.
+
+## Basic idea
+
+![](docs/assets/tool-chaining.svg)
+
+### Problems to solve: Context bloat and too many llm calls
+Suppose the task we want to achieve is ask our buddy Bob out to lunch and then book a table. For the sake of argument assume that our agent has access to the following MCP servers (Note: this is an example, RoboZ has native Tool primitives):
+
+- Ask Bob what they want
+- Find a restaurant
+- Book a table.
+
+In the usual approach an agent is presented each MCP server separately in their system prompt and it must call them one-by-one to complete the task. When the agent is completing the task, at every turn it must choose the correct tool, formulate its output accordingly and absorb the reply into its context, which already must contain the specific instructions on how to use each tool. In addition, at each turn one has to wait for the llm to reply, each reply costs tokens and each reply risks a mistake from the llm.
+
+### Deterministic chains
+The philosophy in RoboZ is that a workflow is (mostly) deterministic and only on occasion does one need to call an llm. For example in RoboZ an agent would trigger the "ask Bob if they want to have lunch" tool and all subsequent steps come by chaining: each tool can be chained to other tools upstream where their outputs are passed down the chain. Each link/edge may introduce a True/False condition, in our case for example if Bob is interested in having lunch (with us). If he is not, RoboZ allows for the chain to break and returns back to the default tool, which for an agentic process is usually "ask the llm what to do next". The default mode is that chained tools are not presented to the agent, they are thus *passive* or in other words their role is strictly in forming deterministic workflows and they cannot be invoked.
+
+Chaining not only reduces the llm calls, but it also provides a useful way of introducing a fine-grained guard layer for tool calls. This is in fact precisely how the cli tools and their access policies work in Roboz. For a cli command a chained passive tool evaluates the intent and breaks the chain if policies are violated.
+
+
+## Start here: Agent with a tool
+
+```python
+from random import choice
+
+from simpsons_quotes import QUOTES
+
+from roboz import Agent, tool
+from roboz.llm.endpoints import MockLLMEndpoint
+from roboz.models import Empty, Message, Stop
+
+
+@tool
+def get_quote(input: Empty, messages: list[Message]) -> Stop:
+    """Return a random Simpsons quote and then stop."""
+    return Stop(value=choice(QUOTES))
+
+
+mock = MockLLMEndpoint(
+    responses=[{"action": "get_quote", "rationale": "Need Simpsons quote!"}]
+)
+
+agent = Agent(
+    name="demo",
+    system_prompt="You are a Simpsons quote generator",
+    agent_endpoint=mock,
+    tools=[get_quote],
+)
+
+output, messages_ = agent.invoke()
+print(f'"{output.value}"')
+```
+
+The above [simple example](examples/simple.py) uses the accompanying
+[quote file](examples/simpsons_quotes.py) in this repository. Run it from the
+repository root with
+
+```bash
+uv run python examples/simple.py
+```
+It creates an agent that returns a random
+Simpsons quote. **The docstring in the tool is the instruction that the agent sees**. It uses a mock endpoint, with pre-determined replies, so you can run it without API keys.
+The main contracts of RoboZ are already visible:
+
+- `@tool` creates an instance of a usable tool for the agent
+-  A tool's input and output are typed. Tools also receive the entire message stack
+- Callable endpoints are single instances, as a hard rule
+- Different output types impact the dynamics, importantly `Stop` breaks out of the agentic loop
+- `agent.invoke()` runs the agent and returns its output `Stop` and messages.
+
+The above does not show the main idea of tool chaining, for that read the following sections.
+## The central abstraction
+
+An agent is a loop that calls tools. Everything is defined as a tool: Skills,  background agents, prompting the agent, prompting the user, running nested agents, start up hooks etc. Everything.
+
+**A tool can be triggered in three ways:**
+- **Invoked by an agent**: The `prompt_agent` tool asks an LLM what to do next and its `Invoke` output always calls another tool. It is constructed internally for `AgentMode.STEERABLE` and `AgentMode.AUTONOMOUS` agents, but it is still just a tool.
+- **By chaining**. After an invoked tool has fired RoboZ checks if a chained tool with a *true* chain condition exists (for more than one *true* condition for a fork you get a runtime error). If yes, the output is passed on and the process repeats until the first broken chain or all chained tools are exhausted
+- **As default tools**. Once the tool chain is exhausted or the chain breaks due to a *false* condition the loop returns to the freely defined `default_tool` (there actually can be many, they are all called in sequence).
+
+RoboZ then collapses to the traditional agentic approach as a special case if one just has the `prompt_agent` as the default with no chaining. An `AgentMode.DETERMINISTIC` agent has no `prompt_agent`; its default tools perform tasks directly, allowing deterministic branching through chaining. This is useful for a background agent that performs periodic maintenance work. `AgentMode.STEERABLE` agents may ask the user for input, while `AgentMode.AUTONOMOUS` agents cannot.
+
+## Why is this framework useful?
+### Tool Chaining
+This may be used to reduce the number of llm calls, leading to a speed increase, lower cost and fewer AI errors. It also provides a useful way of introducing a guard layer for tool calls, which can be used to restrict agentic actions.
+### Output Truncation
+A tool’s output can be hidden from the llm, also partially, and this can start to apply after the message has been shown N times.
+### Tool outputs are typed
+The contract in RoboZ is that every action in the agentic loop is a tool call and all outputs are typed classes. Raw strings or JSON is never exchanged (unless explicitly opted in) as is and typed classes and validation are present throughout, with designated classes for tasks such as `Invoke` and `Stop`.
+### LLM Endpoints are instances
+As a fundamental design rule in Roboz, everything that depends on an LLM call must be trivially swappable to another provider or model. This makes changing an agent endpoint trivial and furthermore multi-endpoint functionality, where inside a single agent several endpoints are implemented, quite easy.
+
+To see the above in practice see the [complex example](examples/complex.py) example below.
+
+
+
+## Chains, factories, truncation and many endpoints
+![](docs/assets/number-escalation.svg)
+
+In the code example below we illustrate some of the features that make RoboZ different from other frameworks.
+
+**Tool chaining** is usually introduced via the decorator argument `chained_to` which indicates the name of the tool whose output is passed as the input (the tools also possess a `.chain` method). The input/output contract must be Liskov compatible, i.e the upstream output must be a subclass of the downstream input. A possible `chain_condition` can be passed in, which by definition has access to the tool's input argument and returns a boolean. The chain condition must evaluate to at most one true condition, but it can evaluate to `false` on all links, in which case you return to the default tool(s). `AgentMode.STEERABLE` and `AgentMode.AUTONOMOUS` construct a `prompt_agent` tool backed by the agent endpoint; `AgentMode.DETERMINISTIC` uses the configured default tools.
+
+The `escalate` is an example of a **tool factory**, which is a simple concept. It accepts a context parameter which is added to the tool's closure and calling the factory with a context argument returns a tool. A very common use case is a tool with an endpoint as a context. In RoboZ all llm **endpoints are instances**, so it is easy to have a specific endpoint for a tool, that is different from that of the agent, below we construct deterministic mock endpoints so that no API keys are required for the examples. Factories have precisely the same chaining arguments in their decorator as a tool.
+
+Also demonstrated in the `escalate` factory is the **message truncation** feature. This parameter is present in all output types and allows the tool to decide if the output should be visible in the conversation passed on to the agent. A message can be truncated partially (show only n chars or just a caller stub) or completely. Importantly, we can choose to start applying the truncation only after the complete message has been shown to the agent n times. Below, we choose to show the message once and then truncate it completely, a useful pattern for example for long tracebacks etc.
+
+All RoboZ tools by definition include the full **conversation messages** as input. These are not intended to be altered in place (although they can be and this is how e.g. *conversation compactification* works), but can be used to alter the behavior of tools in a non-trivial way. For example, a start up hook intended to show the agent some information at the start or performing some initial maintenance can simply be one of the default tools that checks if it has already been called and if it has, does nothing.
+
+**The tool instruction is its docstring**. In addition, the system prompt includes a *technical prompt* by default that gives the specific tool calling instructions. This can of course be switched off. When in doubt, you can always use the method `.show_agent_info()` to check the complete agent configuration including the system prompt, tools, dependencies, persistence locations etc.
+
+
+
+```python
+from builtins import input as read_input
+
+from roboz import Agent, factory, tool
+from roboz.llm import EndpointLike, MockLLMEndpoint, get_completion
+from roboz.models import Empty, Int, Message, Role, Stop, Str, filter_messages
+from roboz.models.truncation import Severity, Truncation
+from roboz.runtime.io import interact_with_user
+from roboz.runtime.sinks import CliSink
+from roboz.tools import stop
+
+
+@tool
+def ask_number(input: Empty, messages: list[Message]) -> Int:
+    """Ask the user for an integer, repeating until the response is valid."""
+    while True:
+        reply = read_input("Enter an integer: ")
+        try:
+            return Int(value=int(reply))
+        except ValueError:
+            print("Please enter an integer :)")
+
+
+@factory(chained_to=ask_number, chain_condition=lambda x: x.value % 2 == 0)
+def escalate(input: Int, messages: list[Message], ctx: EndpointLike) -> Stop | Str:
+    """An even number?! Need to check this with HR!"""
+    interact_with_user("Careful now, that is pretty spicy!", with_reply=False)
+    prompt = f"The user chose {input.value}. Is this too hot to handle?! (y/n)?"
+    verdict = get_completion(
+        endpoint=ctx, messages=[Message(role=Role.SYSTEM, content=prompt)]
+    )
+    is_first_escalation = (
+        len(filter_messages(caller="escalate", messages=messages)) == 0
+    )
+    if verdict == "y" and not is_first_escalation:
+        return Stop(value="Too much spiciness, need to quit!")
+    return Str(
+        value="HR gave a pass, but still, let's show this to the agent only once.",
+        truncation=Truncation(threshold=1, severity=Severity.REMOVE),
+    )
+
+
+@tool(chained_to=ask_number, chain_condition=lambda x: x.value % 2 != 0)
+def give_praise(input: Int, messages: list[Message]) -> Str:
+    """We need to give praise for such an erudite approach to the problem."""
+    interact_with_user(f"{input.value} a fine and bold choice!", with_reply=False)
+    return Str(value=f"{input.value} is good, no biggie.")
+
+
+agent_endpoint = MockLLMEndpoint(
+    responses=[
+        *(10 * [{"action": "ask_number", "rationale": "This is my only job"}]),
+        {"action": "stop", "rationale": "Enough numbers!", "value": ""},
+    ]
+)
+guard_endpoint = MockLLMEndpoint(responses=10 * ["y"])
+
+agent = Agent(
+    name="demo",
+    system_prompt=f"Without exception, use the {ask_number.name} tool.",
+    event_sinks=[CliSink.default()],
+    agent_endpoint=agent_endpoint,
+    tools=[ask_number, escalate(guard_endpoint), give_praise, stop],
+)
+agent.invoke()
+
+
+```
+
+The above [complex example](examples/complex.py) can be run from the root with
+
+```bash
+uv run python examples/complex.py
+```
+
+
+## Try it out
+
+```bash
+uv add roboz
+```
+
+Or with pip:
+
+```bash
+python -m pip install roboz
+```
+
+## Packages
+
+This repository contains four independently versioned Python distributions.
+They share development and release tooling, but are published separately so an
+application only needs to install the parts it uses.
+
+| Distribution | Import | Provides |
+| --- | --- | --- |
+| `roboz` | `roboz` | Core agent, tool, workflow, endpoint, and runtime primitives. |
+| [`roboshed`](packages/shed/README.md) | `roboshed` | Reusable capabilities, guarded system tools, memory, agents, and deployment building blocks. |
+| [`roboz-endpoints`](packages/endpoints/README.md) | `roboz_endpoints` | Model catalogues and optional provider adapters. |
+| [`roboz-proton-bridge`](packages/proton-bridge/README.md) | `roboz_proton_bridge` | Proton Bridge email integration. |
+
+The companion packages build on `roboz`; `roboz-proton-bridge` also uses
+`roboshed`.
+
+## Development
+
+```bash
+uv sync --locked --dev
+uv run pytest
+uv run ruff check
+uv run pyright
+bash scripts/run_type_tests.sh
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development and testing guidance. The
+[verification workflow](.github/workflows/verify.yml) defines the complete CI
+gate.
+Roboz is typed and ships a PEP 561 `py.typed` marker.
+
+## License
+
+Roboz is licensed under the [Apache License 2.0](LICENSE). Copyright © 2026 Tachion Oy.