Merge pull request #2364 from valory-xyz/chore/update-docs

Chore (docs): New naming convention

Author: OjusWiZard

.github/PULL_REQUEST_TEMPLATE.md

@@ -26,7 +26,7 @@ _Put an `x` in the boxes that apply._
 - [ ] I am making a pull request against the `main` branch (left side). Also you should start your branch off our `main`.
 - [ ] Lint and unit tests pass locally with my changes
 - [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] I have locally run services that could be impacted and they do not present failures derived from my changes
+- [ ] I have locally run AI agents that could be impacted and they do not present failures derived from my changes
 - [ ] Public-facing documentation has been updated with the changes affected by this PR. Even if the provided contents are not in their final form, all significant information must be included.
 - [ ] Any backwards-incompatible/breaking change has been clearly documented in the upgrading document.
 

CONTRIBUTING.md

@@ -60,6 +60,6 @@ def some_method(some_arg: Type) -> ReturnType:
 - Always use guard clauses where possible. This leads to more efficient code that has less nesting and is much easier to read.
 
 
-### Agent development
+### Agent blueprint development
 
-You can find several general recommendations in the **Considerations to Develop FSM Apps** section in our documentation [here](https://stack.olas.network/open-autonomy/key_concepts/fsm_app_introduction/).
+You can find several general recommendations in the **Considerations to Develop FSM Apps** section in our documentation [here](https://stack.olas.network/open-autonomy/key_concepts/fsm_app_introduction/).

README.md

@@ -40,17 +40,17 @@
   </a>
 </p>
 
-**Open Autonomy** is a framework for the creation of **agent services**: off-chain
-autonomous services which run as a multi-agent-system (MAS) and offer enhanced functionalities
-on-chain. Agent services expand the range of operations that traditional
+**Open Autonomy** is a framework for the creation of **AI agents**: off-chain
+autonomous AI agents which run as a multi-agent-system (MAS) and offer enhanced functionalities
+on-chain. AI agents expand the range of operations that traditional
 smart contracts provide, making it possible to execute **arbitrarily complex operations**
-(such as machine-learning algorithms). Most importantly, agent services are
+(such as machine-learning algorithms). Most importantly, AI agents are
 **decentralized**, **trust-minimized**, **transparent**, and **robust**.
 
 
-## Get started developing agent services
+## Get started developing AI agents
 
-Read the [Open Autonomy documentation](https://stack.olas.network/open-autonomy/) to learn more about agent services. Follow the [set up](https://stack.olas.network/open-autonomy/guides/set_up/) and [quick start](https://stack.olas.network/open-autonomy/guides/quick_start/) guides to start building your own services.
+Read the [Open Autonomy documentation](https://stack.olas.network/open-autonomy/) to learn more about AI agents. Follow the [set up](https://stack.olas.network/open-autonomy/guides/set_up/) and [quick start](https://stack.olas.network/open-autonomy/guides/quick_start/) guides to start building your own AI agents.
 
 
 ## For developers contributing to the framework: install from source

docs/advanced_reference/commands/autonomy_analyse.md

@@ -1,6 +1,6 @@
-Tools for analysing and verifying agent services.
+Tools for analysing and verifying AI agents.
 
-This command group consists of a number of functionalities to analyse and verify agent services, including {{fsm_app}} skill consistency checks. See the appropriate subcommands for more information.
+This command group consists of a number of functionalities to analyse and verify AI agents, including {{fsm_app}} skill consistency checks. See the appropriate subcommands for more information.
 
 
 
@@ -12,7 +12,7 @@ This command verifies that the [`AbciApp` class](../../key_concepts/abci_app_cla
 
 ??? example
 
-    The docstring corresponding to the [Hello World agent service](https://stack.olas.network/demos/hello-world/) is
+    The docstring corresponding to the [Hello World AI agent](https://stack.olas.network/demos/hello-world/) is
 
 
     ```python
@@ -212,7 +212,7 @@ autonomy analyse dialogues -d abci -d http -i excluded_skill_1 -i excluded_skill
 Since the command will automatically append the `_dialogues` postfix if not provided by the user.
 
 ## `autonomy analyse logs`
-Parse logs of an agent service.
+Parse logs of an AI agent.
 
 ### Usage
 ```bash
@@ -297,13 +297,13 @@ Use regex patterns to filter logs, include lines with `consensus` and exclude li
 autonomy analyse logs --from-dir ./abci_build_hAsH/persistent_data/logs -a 'aea_0' -ir ".*consensus.*" -er ".*debug.*"
 ```
 
-These examples demonstrate various ways to filter and analyze agent service logs. You can combine multiple options to narrow down the log output to exactly what you need for debugging or analysis.
+These examples demonstrate various ways to filter and analyze AI agent logs. You can combine multiple options to narrow down the log output to exactly what you need for debugging or analysis.
 
 ## `autonomy analyse benchmarks`
 
-Aggregate benchmark results from agent service deployments.
+Aggregate benchmark results from AI agent deployments.
 
-This tool requires the benchmark data generated from service agent's runtime.
+This tool requires the benchmark data generated from agent blueprint's runtime.
 By default the tool will aggregate the output for all the periods and code block types but you can restrict the aggregation to a specific period and/or a specific block type.
 
 Read the [guide on how to use the benchmarking tool](../developer_tooling/benchmarking.md) for more information.
@@ -349,9 +349,9 @@ To aggregate stats for `consensus` block type in the second period, execute:
 
 ## `autonomy analyse service`
 
-Analyse if the service is ready to be deployed or not.
+Analyse if the AI agent is ready to be deployed or not.
 
-This tool can be used to analyse a service definition and see if there are any potential issues with configuration which can cause issues when running the deployment.
+This tool can be used to analyse an AI agent definition and see if there are any potential issues with configuration which can cause issues when running the deployment.
 
 Read the [guide on deployment readiness](../../configure_service/on-chain_deployment_checklist.md) for more information.
 
@@ -363,10 +363,10 @@ autonomy analyse service [OPTIONS]
 ### Options
 
 `--token-id INTEGER`
-:  Token ID of the service
+:  Token ID of the AI agent
 
 `--public-id PUBLIC_ID_OR_HASH`
-:   Public ID of the service
+:   Public ID of the AI agent
 
 `--use-celo`                      
 :   To use `celo` chain profile to interact with the contracts
@@ -401,13 +401,13 @@ autonomy analyse service [OPTIONS]
 
 ### Examples
 
-Analyse the service `valory/hello_world` using
+Analyse the AI agent `valory/hello_world` using
 
 ```bash
 autonomy analyse service --public-id valory/hello_world
 ```
 
-Analyse an on-chain service with token ID `1` using
+Analyse an on-chain AI agent with token ID `1` using
 
 ```bash
 autonomy analyse service --token-id 1

docs/advanced_reference/commands/autonomy_build-image.md

@@ -1,12 +1,12 @@
-Builds the agent image for a service.
+Builds the agent blueprint image for an AI agent.
 
-This command builds the Docker runtime images for the agent defined in a service configuration file `service.yaml`. By default, the command tags the generated images as
+This command builds the Docker runtime images for the agent blueprint defined in an AI agent configuration file `service.yaml`. By default, the command tags the generated images as
 
 ```
 <author>/oar-<agent_package>:<package_hash>
 ```
 
-where `<author>` is the author name from the local CLI config (specified with `autonomy init`), `oar` stands for "Open Autonomy Runtime", and `<agent_package>:<package_hash>` is the `PUBLIC_ID` of the agent. These default tags can be modified using certain options described below.
+where `<author>` is the author name from the local CLI config (specified with `autonomy init`), `oar` stands for "Open Autonomy Runtime", and `<agent_package>:<package_hash>` is the `PUBLIC_ID` of the agent blueprint. These default tags can be modified using certain options described below.
 
 !!! warning "Important"
 
@@ -21,7 +21,7 @@ autonomy build-image [OPTIONS] [AGENT_PUBLIC_ID]
 ## Options
 
 `--service-dir PATH`
-:   Path to the service directory.
+:   Path to the AI agent directory.
 
 `-e, --extra-dependency DEPENDENCY`
 
@@ -37,43 +37,43 @@ autonomy build-image [OPTIONS] [AGENT_PUBLIC_ID]
 :   Pull the latest dependencies when building the image.
 
 `-f, --dockerfile FILE`
-:   Specify custom `Dockerfile` for building the agent
+:   Specify custom `Dockerfile` for building the agent blueprint
 
 `--help`
 :   Show the help message and exit.
 
 ## Examples
 
-* Build the runtime image for a service located in the folder `your_service`:
+* Build the runtime image for an AI agent located in the folder `your_ai_agent`:
 
     ```bash
-    autonomy build-image --service-dir /your_service
+    autonomy build-image --service-dir /your_ai_agent
     ```
 
     Or, alternatively:
 
     ```bash
-    cd /your_service
+    cd /your_ai_agent
     autonomy build-image
     ```
 
-* Build the agent image for a specific service without fetching the service package:
+* Build the agent blueprint image for a specific AI agent without fetching the AI agent package:
 
     ```bash
     autonomy build-image <author>/<agent_package>:<package_hash>
     ```
 
-    where `<author>/<package_name>:<package_hash>` is the `PUBLIC_ID` of the agent.
+    where `<author>/<package_name>:<package_hash>` is the `PUBLIC_ID` of the agent blueprint.
 
-* Build an agent image with a custom version tag:
+* Build an agent blueprint image with a custom version tag:
 
     ```bash
     autonomy build-image <author>/<agent_package>:<package_hash> --version <version>
     ```
 
     This will tag the image as `<author>/oar-<agent_package>:<version>`.
 
-* Build an agent image with a custom author name:
+* Build an agent blueprint image with a custom author name:
 
     ```bash
     autonomy build-image <author>/<agent_package>:<package_hash> --image-author <custom_author>