greentic-aw-runtime 1.2.0-dev.33244367809

Enterprise Agentic Worker runtime — Plan-Act-Observe loop, Redis state, tool dispatch via greentic-ext-runtime
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92

//! Bridge a [`DigitalWorkerManifest`]'s `extension_tools` snapshot into the
//! AW runtime's [`ToolRef`] catalog.
//!
//! Sub-project #2 snapshots the tools a Digital Worker invokes in
//! `DigitalWorkerManifest.extension_tools: Vec<ExtensionTool>`. A
//! [`crate::ConfigProvider`] can call [`manifest_to_tool_refs`] to derive the
//! `(extension_id, tool_name)` set to wire as `AgentConfig.tools`.
//!
//! ## Snapshot-wins-at-runtime is out of scope
//!
//! This converter only supplies the *set* of `ToolRef`s. The runtime keeps its
//! existing **live** schema resolution: `tools::list_tools_for_llm` resolves
//! each `ToolRef` against `ExtensionRuntime::list_tools()` at call time. The
//! snapshot's `description` / `input_schema_json` are intentionally ignored
//! here.

use crate::config::ToolRef;
use greentic_dw_manifest::DigitalWorkerManifest;

/// Convert a manifest's `extension_tools` into AW runtime [`ToolRef`]s.
///
/// Only tools whose `capabilities` declare [`AGENTIC_WORKER_CAPABILITY`] are
/// included; flow-only tools are skipped. Declaration order is preserved, and
/// exact `(extension_id, tool_name)` pairs are de-duplicated keeping the first
/// occurrence.
///
/// # Arguments
/// * `manifest` - the Digital Worker manifest carrying the tool snapshot
///
/// # Returns
/// The ordered, de-duplicated list of agentic-worker [`ToolRef`]s. Empty when
/// the manifest declares no agentic-worker-capable tools.
///
/// # Example
/// ```no_run
/// # use greentic_dw_manifest::DigitalWorkerManifest;
/// # use greentic_aw_runtime::manifest_tools::manifest_to_tool_refs;
/// # fn demo(manifest: &DigitalWorkerManifest) {
/// let tool_refs = manifest_to_tool_refs(manifest);
/// // feed `tool_refs` into `AgentConfig.tools`
/// # let _ = tool_refs;
/// # }
/// ```
pub fn manifest_to_tool_refs(manifest: &DigitalWorkerManifest) -> Vec<ToolRef> {
    // `DigitalWorkerManifest` on this lane's greentic-dw-manifest carries no
    // `extension_tools` field, so a manifest here can never declare extension
    // tools and the overlay is empty. That is the honest answer rather than a
    // failure: `ManifestToolOverlayProvider` is fail-soft by contract, and an
    // empty overlay leaves the base config's tools untouched.
    #[cfg(not(greentic_dw_manifest_tools))]
    {
        let _ = manifest;
        Vec::new()
    }

    #[cfg(greentic_dw_manifest_tools)]
    {
        /// Capability literal a tool must declare to be usable by an agentic
        /// worker. The manifest's own validation requires every
        /// `ExtensionTool` to carry this.
        const AGENTIC_WORKER_CAPABILITY: &str = "agentic_worker";

        let mut seen_pairs: Vec<(String, String)> = Vec::new();
        let mut tool_refs: Vec<ToolRef> = Vec::new();

        for extension_tool in &manifest.extension_tools {
            let supports_agentic_worker = extension_tool
                .capabilities
                .iter()
                .any(|capability| capability == AGENTIC_WORKER_CAPABILITY);
            if !supports_agentic_worker {
                continue;
            }

            let pair = (
                extension_tool.extension_id.clone(),
                extension_tool.tool_name.clone(),
            );
            if seen_pairs.contains(&pair) {
                continue;
            }

            seen_pairs.push(pair);
            tool_refs.push(ToolRef {
                extension_id: extension_tool.extension_id.clone(),
                tool_name: extension_tool.tool_name.clone(),
            });
        }

        tool_refs
    }
}