From 79a051051e27621a6b9098559295b0b73944ec60 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Mon, 6 Jul 2026 21:11:21 +0300
Subject: [PATCH 01/12] improve create-apiops package and cli

---
 README.md                                     |  32 ++++-
 packages/create-apiops/README.md              |  62 +++++++++
 .../bin/create-apiops-project.js              | 128 +++++++++++++++---
 scripts/test-create-apiops-scaffold.mjs       | 101 ++++++++++++--
 4 files changed, 296 insertions(+), 27 deletions(-)
 create mode 100644 packages/create-apiops/README.md

diff --git a/README.md b/README.md
index 6e9ebca..b8f826e 100644
--- a/README.md
+++ b/README.md
@@ -1,10 +1,40 @@
 ## Create a new APIOps project (CLI)
 
+Interactive scaffold:
+
 ```bash
 npm create apiops@latest
 ```
 
-This command runs the `create-apiops` initializer package and generates a starter APIOps project template in your current directory. This is useful for a scaffolded proces (with or without AI) to create or review requirements for new APIs or improve existing APIs. 
+Named project scaffold:
+
+```bash
+npm create apiops@latest report-conversion-apiops
+```
+
+Non-interactive scaffold:
+
+```bash
+npm create apiops@latest -- --name report-conversion-apiops --locale en --style REST --yes
+```
+
+When using `npm create`, pass initializer flags after the `--` separator. Flags before the separator are handled by npm itself and may not reach `create-apiops`.
+
+To inspect the initializer options without starting prompts:
+
+```bash
+npm create apiops@latest -- --help
+```
+
+Useful options:
+
+- `--name <name>` or the first positional argument sets the project directory and package name
+- `--locale <locale>` sets the default method locale, such as `en` or `fi`
+- `--style <style>` sets the API style focus: `REST`, `Event`, `GraphQL`, or `"Not sure yet"`
+- `--yes` accepts defaults for omitted options and runs without prompts; use it in non-interactive shells when any prompt answer is omitted
+- `--no-install` skips dependency installation and starter canvas generation
+
+This command runs the `create-apiops` initializer package and generates a starter APIOps project template in your current directory. This is useful for a scaffolded process (with or without AI) to create or review requirements for new APIs or improve existing APIs.
 
 This scaffolded project uses the CLI and/or the method-engine library (useful for AI or applications) provided by the main package. They guide the design and development using the APIOps Cycles method and canvases. 
 
diff --git a/packages/create-apiops/README.md b/packages/create-apiops/README.md
new file mode 100644
index 0000000..bf87580
--- /dev/null
+++ b/packages/create-apiops/README.md
@@ -0,0 +1,62 @@
+# create-apiops
+
+Scaffold a new APIOps project with method guidance, API design artifacts, OpenAPI linting, and APIOps Cycles audit scaffolding.
+
+## Usage
+
+Interactive scaffold:
+
+```bash
+npm create apiops@latest
+```
+
+Named project scaffold:
+
+```bash
+npm create apiops@latest report-conversion-apiops
+```
+
+Non-interactive scaffold:
+
+```bash
+npm create apiops@latest -- --name report-conversion-apiops --locale en --style REST --yes
+```
+
+Skip dependency installation:
+
+```bash
+npm create apiops@latest -- report-conversion-apiops --locale en --style REST --yes --no-install
+```
+
+## npm create argument forwarding
+
+When using `npm create`, pass initializer flags after the `--` separator. Flags before the separator are handled by npm itself and may not reach `create-apiops`.
+
+The first positional argument is treated as the project name, so these are equivalent:
+
+```bash
+npm create apiops@latest report-conversion-apiops
+npm create apiops@latest -- --name report-conversion-apiops
+```
+
+## Help
+
+```bash
+npm create apiops@latest -- --help
+```
+
+You can also run the initializer directly:
+
+```bash
+npx create-apiops@latest --help
+```
+
+## Options
+
+- `--name <name>` or the first positional argument sets the project directory and package name.
+- `--locale <locale>` sets the default method locale. Default: `en`.
+- `--style <style>` sets the API style focus: `REST`, `Event`, `GraphQL`, or `"Not sure yet"`. Default: `REST`.
+- `--yes`, `-y` accepts defaults for omitted options and runs without prompts. Use it in non-interactive shells when any prompt answer is omitted.
+- `--no-install` skips dependency installation and starter canvas generation.
+- `--version`, `-v` prints the initializer version.
+- `--help`, `-h` prints usage without starting prompts.
diff --git a/packages/create-apiops/bin/create-apiops-project.js b/packages/create-apiops/bin/create-apiops-project.js
index 72b2fba..1c3da9e 100644
--- a/packages/create-apiops/bin/create-apiops-project.js
+++ b/packages/create-apiops/bin/create-apiops-project.js
@@ -18,17 +18,46 @@ const DEFAULTS = {
 
 function parseArgs(argv) {
   const args = {
+    help: false,
+    version: false,
     yes: false,
     name: undefined,
     locale: undefined,
     style: undefined,
-    install: undefined
+    install: undefined,
+    errors: []
+  };
+
+  const readValue = (arg, key, index) => {
+    const equalIndex = arg.indexOf("=");
+    if (equalIndex !== -1) {
+      const value = arg.slice(equalIndex + 1);
+      if (!value) {
+        args.errors.push(`Missing value for ${arg.slice(0, equalIndex)}.`);
+      }
+      return { value, nextIndex: index };
+    }
+
+    const value = argv[index + 1];
+    if (!value || value.startsWith("--")) {
+      args.errors.push(`Missing value for --${key}.`);
+      return { value: undefined, nextIndex: index };
+    }
+    return { value, nextIndex: index + 1 };
   };
 
   for (let i = 0; i < argv.length; i += 1) {
     const arg = argv[i];
 
-    if (arg === "--yes") {
+    if (arg === "--help" || arg === "-h") {
+      args.help = true;
+      continue;
+    }
+    if (arg === "--version" || arg === "-v") {
+      args.version = true;
+      continue;
+    }
+    if (arg === "--yes" || arg === "-y") {
       args.yes = true;
       continue;
     }
@@ -36,19 +65,34 @@ function parseArgs(argv) {
       args.install = false;
       continue;
     }
-    if (arg === "--name") {
-      args.name = argv[i + 1];
-      i += 1;
+    if (arg === "--name" || arg.startsWith("--name=")) {
+      const result = readValue(arg, "name", i);
+      args.name = result.value;
+      i = result.nextIndex;
+      continue;
+    }
+    if (arg === "--locale" || arg.startsWith("--locale=")) {
+      const result = readValue(arg, "locale", i);
+      args.locale = result.value;
+      i = result.nextIndex;
+      continue;
+    }
+    if (arg === "--style" || arg.startsWith("--style=")) {
+      const result = readValue(arg, "style", i);
+      args.style = result.value;
+      i = result.nextIndex;
       continue;
     }
-    if (arg === "--locale") {
-      args.locale = argv[i + 1];
-      i += 1;
+    if (arg.startsWith("-")) {
+      args.errors.push(`Unknown option: ${arg}`);
       continue;
     }
-    if (arg === "--style") {
-      args.style = argv[i + 1];
-      i += 1;
+    if (!args.name) {
+      args.name = arg;
+      continue;
+    }
+    if (args.name !== arg) {
+      args.errors.push(`Unexpected positional argument: ${arg}`);
       continue;
     }
   }
@@ -56,6 +100,40 @@ function parseArgs(argv) {
   return args;
 }
 
+function getPackageVersion() {
+  const packageJsonPath = path.resolve(__dirname, "..", "package.json");
+  const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, "utf8"));
+  return packageJson.version;
+}
+
+function printHelp() {
+  console.log(`create-apiops ${getPackageVersion()}
+
+Scaffold a new APIOps project with method guidance, API design artifacts,
+OpenAPI linting, and APIOps Cycles audit scaffolding.
+
+Usage:
+  create-apiops [project-name] [options]
+  npm create apiops@latest -- [project-name] [options]
+
+Options:
+  --name <name>        Project directory and package name. Same as project-name.
+  --locale <locale>    Default locale for generated method commands. Default: ${DEFAULTS.locale}
+  --style <style>      API style focus: REST, Event, GraphQL, or "Not sure yet". Default: ${DEFAULTS.style}
+  --yes, -y            Accept defaults for omitted options and run without prompts.
+                      Use this in non-interactive shells when any prompt answer is omitted.
+  --no-install         Skip npm install and starter canvas generation.
+  --version, -v        Show the create-apiops version.
+  --help, -h           Show this help.
+
+Examples:
+  npm create apiops@latest
+  npm create apiops@latest my-api
+  npm create apiops@latest -- --name my-api --locale en --style REST --yes
+  npm create apiops@latest -- my-api --locale en --style REST --yes --no-install
+`);
+}
+
 function normalizeStyle(style) {
   const value = String(style || "").trim().toLowerCase();
   const map = {
@@ -119,15 +197,26 @@ function runCommand(command, args, options = {}) {
   });
 }
 
-function hasMissingFlagValue(args) {
-  return ["name", "locale", "style"].some((key) => args[key] === undefined && process.argv.includes(`--${key}`));
+function hasCompleteNonInteractiveConfig(args) {
+  return args.name && args.locale && args.style && args.install !== undefined;
 }
 
 async function getScaffoldConfig() {
   const args = parseArgs(process.argv.slice(2));
 
-  if (hasMissingFlagValue(args)) {
-    console.error("Missing value for one of --name, --locale, or --style.");
+  if (args.help) {
+    printHelp();
+    process.exit(0);
+  }
+
+  if (args.version) {
+    console.log(getPackageVersion());
+    process.exit(0);
+  }
+
+  if (args.errors.length > 0) {
+    console.error(args.errors.join("\n"));
+    console.error("\nRun `create-apiops --help` for usage.");
     process.exit(1);
   }
 
@@ -138,10 +227,17 @@ async function getScaffoldConfig() {
     installNow: args.install === undefined ? DEFAULTS.install : args.install
   };
 
-  if (args.yes || (args.name && args.locale && args.style && args.install !== undefined)) {
+  if (args.yes || hasCompleteNonInteractiveConfig(args)) {
     return initial;
   }
 
+  if (!process.stdin.isTTY || !process.stdout.isTTY) {
+    console.error("create-apiops cannot prompt because stdin or stdout is not interactive.");
+    console.error("Pass --yes to accept defaults for omitted options. To skip --yes, pass --name, --locale, --style, and --no-install.");
+    console.error("Example: npm create apiops@latest -- --name my-api --locale en --style REST --yes");
+    process.exit(1);
+  }
+
   const rl = readline.createInterface({
     input: process.stdin,
     output: process.stdout
diff --git a/scripts/test-create-apiops-scaffold.mjs b/scripts/test-create-apiops-scaffold.mjs
index dd116a8..f5d18f6 100644
--- a/scripts/test-create-apiops-scaffold.mjs
+++ b/scripts/test-create-apiops-scaffold.mjs
@@ -2,7 +2,7 @@ import { fileURLToPath } from "node:url";
 import { dirname, resolve, join } from "node:path";
 import { mkdtempSync, readFileSync, existsSync, rmSync } from "node:fs";
 import { tmpdir } from "node:os";
-import { execFileSync } from "node:child_process";
+import { execFileSync, spawnSync } from "node:child_process";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
@@ -38,6 +38,7 @@ const projectName = "ci-apiops-project";
 const projectDir = join(tempRoot, projectName);
 let localTarball = null;
 const npmCommand = resolveNpmCommand();
+const runInstallIntegration = process.argv.includes("--install-integration");
 
 function assert(condition, message) {
   if (!condition) {
@@ -45,7 +46,76 @@ function assert(condition, message) {
   }
 }
 
+function runStep(label, command, args, options = {}) {
+  const timeout = options.timeout ?? 180000;
+  console.log(`\n[create-apiops test] ${label}`);
+  try {
+    return execFileSync(command, args, {
+      timeout,
+      ...options
+    });
+  } catch (error) {
+    if (error.code === "ETIMEDOUT") {
+      const commandLine = [command, ...args].join(" ");
+      throw new Error(`[create-apiops test] ${label} timed out after ${timeout} ms.\nCommand: ${commandLine}`);
+    }
+    throw error;
+  }
+}
+
 try {
+  const helpOutput = execFileSync(
+    "node",
+    [cliPath, "--help"],
+    { cwd: tempRoot, encoding: "utf8" }
+  );
+  assert(helpOutput.includes("Usage:"), "Expected create-apiops --help to print usage.");
+  assert(
+    helpOutput.includes("npm create apiops@latest -- --name my-api"),
+    "Expected help output to document npm-create flag forwarding."
+  );
+  assert(
+    !existsSync(join(tempRoot, "my-api-project")),
+    "Expected create-apiops --help to exit without creating the default project."
+  );
+
+  const nonInteractivePrompt = spawnSync(
+    "node",
+    [cliPath, "needs-prompt-answers"],
+    { cwd: tempRoot, encoding: "utf8" }
+  );
+  assert(
+    nonInteractivePrompt.status === 1,
+    "Expected omitted answers in a non-interactive shell to fail clearly instead of waiting for prompts."
+  );
+  assert(
+    nonInteractivePrompt.stderr.includes("cannot prompt"),
+    "Expected non-interactive prompt failure to explain the prompt problem."
+  );
+  assert(
+    nonInteractivePrompt.stderr.includes("--yes"),
+    "Expected non-interactive prompt failure to recommend --yes."
+  );
+
+  const positionalProjectName = "positional-apiops-project";
+  const positionalProjectDir = join(tempRoot, positionalProjectName);
+  execFileSync(
+    "node",
+    [
+      cliPath,
+      positionalProjectName,
+      "--yes",
+      "--no-install"
+    ],
+    { cwd: tempRoot, stdio: "inherit" }
+  );
+
+  const positionalPkg = JSON.parse(readFileSync(join(positionalProjectDir, "package.json"), "utf8"));
+  assert(
+    positionalPkg.name === positionalProjectName,
+    "Expected first positional argument to set the scaffolded project name."
+  );
+
   execFileSync(
     "node",
     [
@@ -105,7 +175,13 @@ try {
     "Expected scaffolded OpenAPI file to contain the canonical OpenAPI snippet content."
   );
 
-  const packJson = execFileSync(
+  if (!runInstallIntegration) {
+    console.log("create-apiops scaffold fast test passed.");
+    console.log("Install-heavy generated project integration was skipped. Run `npm run test:create-apiops:integration` to include npm install and generated project commands.");
+  } else {
+
+  const packJson = runStep(
+    "Packing apiops-cycles-method-data for generated-project install",
     npmCommand.command,
     [...npmCommand.args, "pack", "--json", "--cache", npmCacheDir],
     { cwd: repoRoot, encoding: "utf8" }
@@ -113,7 +189,8 @@ try {
   localTarball = JSON.parse(packJson)[0]?.filename;
   assert(localTarball, "Failed to create local apiops-cycles-method-data tarball for integration test.");
 
-  execFileSync(
+  runStep(
+    "Installing local package tarball into generated project",
     npmCommand.command,
     [...npmCommand.args, "install", resolve(repoRoot, localTarball), "--cache", npmCacheDir],
     {
@@ -122,7 +199,8 @@ try {
     }
   );
 
-  const engineImportOutput = execFileSync(
+  const engineImportOutput = runStep(
+    "Checking generated project method-engine import",
     process.execPath,
     [
       "--input-type=module",
@@ -139,18 +217,19 @@ try {
     "Expected installed package to expose the reusable method-engine export."
   );
 
-  execFileSync(npmCommand.command, [...npmCommand.args, "run", "method:stations", "--cache", npmCacheDir], {
+  runStep("Running generated project method:stations", npmCommand.command, [...npmCommand.args, "run", "method:stations", "--cache", npmCacheDir], {
     cwd: projectDir,
     stdio: "inherit"
   });
 
-  execFileSync(npmCommand.command, [...npmCommand.args, "run", "method:start", "--cache", npmCacheDir], {
+  runStep("Running generated project method:start", npmCommand.command, [...npmCommand.args, "run", "method:start", "--cache", npmCacheDir], {
     cwd: projectDir,
     stdio: "inherit"
   });
 
   const guidedAnswers = Array.from({ length: 21 }, () => "no").join(",");
-  const guidedStartOutput = execFileSync(
+  const guidedStartOutput = runStep(
+    "Checking generated project guided start flow",
     process.execPath,
     [
       join(projectDir, installedMethodCliPath),
@@ -173,7 +252,8 @@ try {
     "Expected guided start flow to show interactive next-step options."
   );
 
-  const interactiveResourcesOutput = execFileSync(
+  const interactiveResourcesOutput = runStep(
+    "Checking generated project interactive resources flow",
     process.execPath,
     [
       join(projectDir, installedMethodCliPath),
@@ -192,12 +272,12 @@ try {
     "Expected interactive resources flow to create or show starter canvas JSON."
   );
 
-  execFileSync(npmCommand.command, [...npmCommand.args, "run", "method:resources:strategy", "--cache", npmCacheDir], {
+  runStep("Running generated project method:resources:strategy", npmCommand.command, [...npmCommand.args, "run", "method:resources:strategy", "--cache", npmCacheDir], {
     cwd: projectDir,
     stdio: "inherit"
   });
 
-  execFileSync(npmCommand.command, [...npmCommand.args, "run", "method:canvases:new-api", "--cache", npmCacheDir], {
+  runStep("Running generated project method:canvases:new-api", npmCommand.command, [...npmCommand.args, "run", "method:canvases:new-api", "--cache", npmCacheDir], {
     cwd: projectDir,
     stdio: "inherit"
   });
@@ -219,6 +299,7 @@ try {
   }
 
   console.log("create-apiops scaffold integration test passed.");
+  }
 } finally {
   if (localTarball) {
     rmSync(resolve(repoRoot, localTarball), { force: true });

From 9a17284a976c942febcd3dfa6ccbb0a13eac5a45 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Mon, 6 Jul 2026 21:15:50 +0300
Subject: [PATCH 02/12] add branding and partner data

---
 public/partners/adorsys.svg                   |  21 ++
 ...-evangelist-logo-butterfly-transparent.png | Bin 0 -> 50305 bytes
 public/partners/apisfirst.svg                 |   1 +
 public/partners/osaango-black.svg             | 286 ++++++++++++++++++
 src/data/partners.json                        |  32 ++
 5 files changed, 340 insertions(+)
 create mode 100644 public/partners/adorsys.svg
 create mode 100644 public/partners/api-evangelist-logo-butterfly-transparent.png
 create mode 100644 public/partners/apisfirst.svg
 create mode 100644 public/partners/osaango-black.svg
 create mode 100644 src/data/partners.json

diff --git a/public/partners/adorsys.svg b/public/partners/adorsys.svg
new file mode 100644
index 0000000..605e5c8
--- /dev/null
+++ b/public/partners/adorsys.svg
@@ -0,0 +1,21 @@
+<svg width="630" height="107" viewBox="0 0 630 107" fill="none" xmlns="http://www.w3.org/2000/svg">
+<g clip-path="url(#clip0_2411_6303)">
+<g clip-path="url(#clip1_2411_6303)">
+<path d="M344.437 22.0741C343.587 21.177 342.266 20.7944 340.019 20.7944C337.348 20.7944 319.531 20.8425 316.907 20.9782C302.269 21.735 289.356 25.2179 289.356 38.2919V78.9309C289.356 82.0401 290.046 85.2194 295.166 85.2194H299.423C301.764 85.2194 304.554 84.1397 304.554 78.9969V39.7775C304.554 35.7408 305.419 34.4359 315.7 34.4359H339.31C341.996 34.4359 345.566 33.8575 345.566 28.8557L345.57 27.8389C345.585 25.1021 345.594 23.2938 344.437 22.0741Z" fill="#101828"/>
+<path d="M439.147 63.5319C439.146 51.6613 430.668 45.6418 413.949 45.6418H383.747C378.639 45.6418 374.371 45.4682 372.857 45.1963C368.756 44.5235 368.46 43.1941 368.46 41.0845V37.8393C368.46 36.171 370.371 35.0974 374.15 34.6459C375.121 34.5211 397.653 34.4582 402.43 34.4582H403.725C407.799 34.4582 409.615 32.5727 409.615 28.3452V26.9733C409.615 22.7002 407.799 20.7944 403.725 20.7944C388.103 20.7944 373.132 21.5474 369.123 22.418C356.126 25.236 353.398 32.3485 353.398 37.818V41.1931C353.398 52.7451 364.437 59.3704 383.684 59.3704H413.451C423.609 59.3704 423.609 61.6262 423.609 64.015V66.3672C423.609 71.4024 420.903 71.6429 412.35 71.6429H359.538C353.838 71.6429 353.398 74.6932 353.398 79.0019C353.398 83.3603 355.234 85.2193 359.538 85.2193H412.288C434.506 85.2193 439.169 74.955 439.169 66.3367L439.147 63.5319Z" fill="#101828"/>
+<path d="M629.899 63.5319C629.897 51.6613 621.419 45.6418 604.7 45.6418H574.498C569.391 45.6418 565.122 45.4682 563.608 45.1963C559.507 44.5235 559.211 43.1941 559.211 41.0845V37.8393C559.211 36.171 561.123 35.0974 564.901 34.6459C565.872 34.5211 588.404 34.4582 593.182 34.4582H594.476C598.55 34.4582 600.367 32.5727 600.367 28.3452V26.9733C600.367 22.7002 598.55 20.7944 594.476 20.7944C578.854 20.7944 563.884 21.5474 559.874 22.418C546.878 25.236 544.149 32.3485 544.149 37.818V41.1931C544.149 52.7451 555.188 59.3704 574.435 59.3704H604.202C614.36 59.3704 614.36 61.6262 614.36 64.015V66.3672C614.36 71.4024 611.654 71.6429 603.101 71.6429H550.289C544.589 71.6429 544.149 74.6932 544.149 79.0019C544.149 83.3603 545.986 85.2193 550.289 85.2193H603.039C625.257 85.2193 629.92 74.955 629.92 66.3367L629.899 63.5319Z" fill="#101828"/>
+<path d="M528.563 20.7944H524.961C519.815 20.7944 519.121 23.9696 519.121 27.0758V71.643H479.374C469.779 71.643 463.819 68.8717 463.819 64.4118L463.817 26.9957C463.817 22.6495 462.061 20.7945 457.946 20.7945H454.534C449.376 20.7945 448.681 23.9737 448.681 27.0839L448.689 43.0847L448.682 43.2156C448.672 43.3749 448.663 43.5342 448.663 43.7057C448.663 43.7067 448.681 56.7331 448.681 65.4174C448.681 70.3289 450.814 75.2139 454.534 78.8193C457.546 81.7388 463.05 85.2194 472.167 85.2194H519.121V99.7528C519.121 104.132 520.867 106.002 524.961 106.002H528.563C532.678 106.002 534.434 104.147 534.434 99.7781V26.9956C534.434 22.6494 532.678 20.7944 528.563 20.7944Z" fill="#101828"/>
+<path d="M181.294 9.4687L181.29 7.23929C181.29 3.47959 180.673 0 176.195 0H171.27C166.764 0 166.143 3.53032 166.143 7.34482V20.7944H127.832C101.154 20.7944 95.5543 32.0116 95.5543 41.4224C95.5543 47.0077 95.547 52.0266 95.5407 56.52C95.5354 60.1619 95.5305 63.4589 95.5305 66.4322C95.5305 81.96 113.199 85.2194 128.02 85.2194H148.1C155.515 85.2194 162.406 83.8495 168.582 81.1462C177.022 77.4433 181.301 71.9697 181.301 64.8745V9.67675C181.301 9.60468 181.297 9.53669 181.294 9.4687ZM110.856 63.9531V39.7775C110.856 37.7054 115.354 34.4186 127.422 34.4186L166.143 34.4358V64.6107C166.143 70.4232 155.626 71.6429 146.803 71.6429H127.832C122.72 71.6429 118.773 71.3436 116.716 70.7997C112.773 69.7606 110.856 67.521 110.856 63.9531Z" fill="#101828"/>
+<path d="M276.598 41.7309C276.598 27.2513 268.171 20.7944 249.274 20.7944L220.792 20.8188C219.822 20.8188 218.873 20.8117 217.944 20.8046C211.564 20.762 206.054 20.7163 201.415 23.0208C195.048 26.2153 191.098 32.1608 190.848 38.9668V64.3073C190.848 78.7869 199.361 85.2438 218.452 85.2438L249.046 85.2194C256.475 85.1575 262.798 83.8566 267.843 81.3522C275.555 77.4829 276.619 71.1122 276.619 64.8055L276.598 41.7309ZM206.044 40.8907C206.22 38.7719 208.06 37.1391 211.658 35.9062C214.525 34.9168 217.608 34.4358 221.082 34.4358H245.362C253.244 34.4358 261.396 36.8225 261.396 40.8166V64.8055L261.402 65.1464C261.226 67.2663 259.386 68.899 255.79 70.1309H255.788C252.872 71.1365 249.702 71.647 246.364 71.647H222.163C214.243 71.647 206.05 69.244 206.05 65.2215V41.2317L206.044 40.8907Z" fill="#101828"/>
+<path d="M70.4752 20.829C69.3421 20.829 68.0651 20.8523 66.6406 20.8787C63.2574 20.9416 59.0494 21.0197 53.9434 20.829H35.4277C35.3489 20.829 35.2775 20.8351 35.1806 20.8452C30.5295 20.969 29.5533 23.7687 29.5533 26.0966V29.1145C29.5533 31.558 30.5988 34.4704 35.5778 34.4704H54.1975C67.3329 34.4704 70.8805 34.4531 70.8805 45.6763H22.4322C13.6191 45.6763 7.87333 47.351 4.40709 50.6717C4.37962 50.698 4.3496 50.7224 4.32247 50.7489C1.27269 53.7246 0.0222152 58.0029 0.0213753 63.5665L0.00138582 66.1806C0.00138582 66.1806 0.00138582 66.1809 0.00138582 66.1811L0 66.3713C0 74.9897 4.66321 85.2539 26.881 85.2539H58.018C76.4332 85.2539 85.7707 78.6032 85.7707 65.4864V33.4313C85.7707 26.9531 78.3373 20.829 70.4752 20.829ZM68.9445 69.5039C67.8204 70.4953 65.0302 71.6775 58.1215 71.6775H26.8191C24.363 71.6775 22.3903 71.6571 20.8243 71.5095C20.5482 71.4835 20.285 71.4534 20.0338 71.4188C19.4085 71.3328 18.8601 71.2177 18.3806 71.0659C18.1375 70.9891 17.9126 70.9022 17.7046 70.8049C17.6152 70.7632 17.529 70.7192 17.4458 70.6734C17.1465 70.5082 16.8847 70.3176 16.6625 70.094C16.0872 69.5148 15.7603 68.7249 15.629 67.648C15.5827 67.2689 15.5599 66.8554 15.5599 66.4018V64.0496C15.5599 63.2605 15.5623 62.4866 15.9284 61.803C16.665 60.4279 18.8851 59.4215 25.5664 59.4062H25.5679C25.6191 59.406 25.6665 59.4051 25.7181 59.4051H70.9288L70.9375 62.22C70.9375 65.9218 70.271 68.3683 68.9445 69.5039Z" fill="#101828"/>
+</g>
+</g>
+<defs>
+<clipPath id="clip0_2411_6303">
+<rect width="630" height="107" fill="white"/>
+</clipPath>
+<clipPath id="clip1_2411_6303">
+<rect width="629.92" height="106.002" fill="white"/>
+</clipPath>
+</defs>
+</svg>
diff --git a/public/partners/api-evangelist-logo-butterfly-transparent.png b/public/partners/api-evangelist-logo-butterfly-transparent.png
new file mode 100644
index 0000000000000000000000000000000000000000..d6ae9a88c686f823dc866c1c9e61c9f279566e13
GIT binary patch
literal 50305
zcmeFZWmsIzvNnusu;30M0fM``COCl*+}+(>gOlK{!Ciy91R30A@WE|x{U%$^-cO$M
z{{Ma)xMpU}T3x+bs=My0y4Qp&DM+KC5TQUpL7{#8An^$b3U&{2ypMzcd2hleU4eW+
zJAINCgQ^6O>_fg3ny7y?m6wO2gB&A4Awa)|g8f|t@(%?~1O@+(V<;#!XyX4l)`h11
zR~Z;c8CEFBI}{$|Wg2Dy1^2J=-jL7Ve;*((NKOCzRI+e4v9>XAwsWLVa<rphXX0XF
zWrs8{2l_wv%z^oL9k6>ju>U@W`rT3}JuSK4^&{JV&~So+LdE|5f`&@VAb`|iZ=tI0
ztS&FdXJlu?WMFJ(Xu{-fWB*$UO2C~Da%f}XY(U{|V{Pli=Pvl>A0_x8$G=ZAzoGa?
z5oasGH|p|A6ykP{CKOyuEKDqKgit6bC<GjhP5C}aNc~G3@=frKxwEr9A2YL?n;VlG
zJCmKG88a&{FE29-8#5alBcueQlZUOdfjgtE6V*Q}`FA}MCQe3<7WU2-cD5A1>oqX6
zb8!}Y^XB)B{^#$X?KE+>_|Kheo&MD=NC%mJUtwltVqyN@#2}shpZ5Jl%H6>J|0(2b
zVfz2L*Y7L;6#K_u{IiV$zgxifj|tU~u&^<)b%OLqh>e|H;2&-K+m-+H?!P3}|0BuD
z!ou?3qW^X2zeFKD;}dr@`K>{!c6Qc6|Eod?F#lQXj~e75Q*LbFY#?FaY$C+Q!p6bK
z%ErjbtIEd0$I8aX!pg|P$@jZ8zpMF6+5f8N_n`2pe=>2hvv&DCl|tNXkRGrw|LzAw
z^lz8{6#b9nXIl$rA+~>s{BinEDUJVJ|KD!--<SUsRdlp4fhgoZ+RFN`yZ!gMf0Y+t
z{;iY$rKA5`0RK1(Sph;QkYV}vY7#=Jswvlif)auHC?Trq4t<n~sE^bCJZN_6_&zz9
z!&81wGLHHUMLW_bob3A}^{iDhJ4GL%hq|VsJzyw&O`Dnc4_XR&XypPbiuRA@0hijg
zFTm5c#7w_dcfM<XN4-O{cC~YJb-k{us{^M4?R@hS;3z5Jg8eZuVZ=m`kf8tX%m0nR
z|LMX1zt#ee0TKbtXy&@q?pQj0qZ0_w7Zvr&q;7FVSy{O;I5_yS#%R!#ICMkk+sWsX
zcb7=s&v&5nNPK3pI^$p8Tk#k*oof?&;}wN?ufEGNH6O+BpQIQZ$2a_K$*%{$wI3I}
z$%rOqAJGiOAb*ApE<go(gU8fp-Xb-Z5K-D+&3?)LTzkZ6y)a?DR9~{#<^eX`aXgqQ
z@v(dx@2LFe<{_3PQZbh!d@)2dFL2fcTlLMc-SbM-(XlqLP@8$hEUi%2(aC8x02cAG
z=Shv{<q@pc4hHbs?XR}FWi=?yiBTxQ?44QMJ>391BW}$aEobSfl=G#~lR6(Cz1vwx
zliEi|<=|z};SbRh)6z;SJD=|rbv<?xQTs}%l%`%Q{&hQ>L4#@dBm%595I>T{*Qwu1
z*7FUwTW+jy<jbTJ6wEX|_FO)8wd!86Z8|L4b8N2f>f16fF!0n<P>5Oj>5#wXyO$dl
zDs;OZ1U?v`N^X7iCIA5Gjb&^u&g%5k)Ig3vW{=}%whZT~k0-rh7|T7qy)M#I!-@2t
zw+5nTqX^kwdtUB26c~HoG5)dLimbj>I)uA~N5$hH;IUu#6{<X0Z7mBz#IWoZ;N#P*
z&}ssJR0>S%d>*bfTNNryb#=2gc`-Mq=PPxHodCR`N8rozO{bMNH3ed@zZ=XKgBwzH
zzO%F2^Q|J+{iz-Cl*X!1cxl*M$)6ZImT%xMZg1UP_9iIdr`@iW?K)Xo(m1Wu@*(58
ze^Kr>ME>U-28-BGh-{GDaS(Hu>x<D_P*YQ<W%9dmQJNn*bmU9NX1&a5*<FQpkpdpN
z-GRaQy6zjQQCPm!8g-_UMgh5!^Pnc{#i`(R<LmwDuu^BIzOPt7umG|cg$T?*GboD~
zT;=yv*2T~}_;I>W{xCqi<x$j~+u+33^?0eFc%>&-yF6CKr0H+EN^yxaQBK-CC59g2
zC_7YhElP0uS*^13;iQ!(N{iesQye<eqQAdCwJ5`J82zO4>3aF)lNz6+Hc~<|R0T)q
zE5cfAki|xZNu^ekZHqwu(J_;q=WD&cY7E2@C>g=&^R<!TbF-Qx;sHuTL8lH|0~Np)
z7b{~A_UkEG=Bu5%5Q{>U__aE-akP+!;q;6?d>Ck~6ds37ONkjg5_@a&9?@K;Am)zS
z&1(PGaUcF>WdqXQo?S270YeVc?T1XL-@Qxaz}~fUH_%f~^>$dhtOM{Jq87r--zyh9
z@HdSMJsh#q#aCv~!+B$M{d7+M?7M;8Z9SP6f_!?~BJjW`eU17z8!i^uMeg^A6&96p
zbvVzh^6Aqkm(7y7L1^JV61?paeX2@II|hi8f`u{Q>=LIDq{jA<R|o0#EsNX93KNgH
z>(RnwfgRik(RO~U(7`tNEic6%3ha+rYynf%e!bK_6oedmtoflSI5m~sEQ@5ct-G0I
z@TXnCuXBQOJ5<x9?@5@nAJ=!&?R@bc>g^Te`I@R)Pg(|L2jYQ$AD1{v5xe=JsML%M
z?E;Ioi(z_;B;C&&87V0QmOSr}0_dn%ysnQ<K4hp7n}(s2IuqKhws6kB{yUV(mDV4K
zA`JRQZ-Wx$@gs5|tCyIcwCy7%OhcMTnOa4?{#uC&&GgbP!Ih?u%6E@H7XY0cML|fw
zJJ}@dK7RIB;-Y00ET0pJguLB}cIov#ZSW^yhlqT|6ybgD8kTW(u3ziR*bko*()e>4
zl$wx&LoSX1sq7%_-SK1Bvg+!<@+`MCk1C&+r<>din_pT;*h7mvV3Nd|r}D?BOsWJd
z(}g$0Rjh`Z0A#xbhth8oo?aRnz-A}2nMv^nz$jqsFgZP*z3UiYx9Qky2wt_7mXPS%
zc=Y~KK+lXZ{Y)r5QC0triD_djtLV~eT&raw!!P0qADptPyMBtPfYrKD#Pj|w4)R||
zJ|_kXNdwwvw)8XdYKu!`P_h+#ou13>nZc9!{q-^b>^%Fu0U*i=tlg}0;piyUEbo@?
zom?jB>)YYT(_<kMmF>|66wdtyw5|)YA@I9~|8gf&R{pfxEq|qIxXe(H_(e^dR~HOd
zJMZfmW;G9b8P#$VEoaLqXnd!C7Od4gmM@-|Dm2s3JZ-dSCFISNH~H0%5RHfgoVW$=
z)HyslGWMBEYXc4jLBip2%P&Ets3Dqka$(kb`m{_D*y4J8l)$8OohXN`QqH&~lw`;B
z3Ugw-PX^9eUi|s5z%HOglEN7N60*Bag(pQsMygCGl?r-Y7ej36Nzg>c(lXWkQT%(W
zrstXtCwI7nWF+{&*Uw@y!vH{^9<G#%he@dvS9*oA)WGC37zDU=otT)+-p7Wyjei<E
zV!eCteQX_G;GuK+1*F)XRY`TK6f}(#wrH&AkCW~tcD-ZtH-0O_i9Mvtx??dP>U7GI
z2T-DO<Uv6k5zQ6mvRck8(e_*M(|V4%v17-ulV^GTDJEfbH;J)~nDO2qE21LVe|q&D
zM)JMQ0*X|eF&(b%fqr+4YNdLI%VOVki_4)orz8K3?4OuE#}*4|k#!F;B%Ap;7W{CQ
zPpS%nS2M9bf>{|EM*!BEb2=CpPj~kM$6#p@r<1Nb^zvrX+@{{27_#mXIGd7iGol8C
zwqM6G+_q5W4<b8RF%-yuT%d~#MFzwr7mbz!jdWVGglXLNf6&(^34p&f+lfb12@F3U
z(8RTZK|+<sZa@PG@so!0R1>373AOGPbAH6Zo<uB<QZ^?)W!`0w@Bw4dAo>sPEnoCz
zB;$Zz2woAY5F=Ypq01)!YJLdRadc$OSU~gkZL!HnQUfiaqVM0988=dJxqpWpu;Y1-
zsv7PxiBZef;ux%by4qR-9YSfz`JTr?ry3^(J^ArC^cu$~BypN>q<MVgm4=m`?zX~1
zc`FvD9N|V>=kX+F8^tm))}H8xuF@hllJ|6eKoyV~L#K75g)O7fR&r{sM6o5z$qa5X
z{Z3z9;Kvr?9^QAmpHN*>F$>4E1qS029ww&f+jmAbqL#I)JCz<z7{3n+S@v7BWMyV?
zO&Gb=j6p2%Z{RY**!1qN$_X(%Zpe^+_^x*a6nZm|h}(voot*(IY{p%-25hFymu$s&
zm@zv9Vw2XGFemk&ZB;U5$r(Fnysi+NT4TKz$G#H1f@UTaBdM>T2KQMROa_v|38T0H
zl&in2l{wD8yrCZMXPsMMp3a;m!YEu%oy=G@TW59M6H)r&dfAqMZhz1?9#aFFb3dPA
zl{uP(Y57!wcn#Ft{4hB#6-`u<kwKDas;Zi>7Q2Yzo!W<=NkjbCO+*AK!yQgcO(aZB
zxeU7ms|iLx$4q@W%gUV2DHD)V?(Nn=rhDWu3gm*TxPFcSr|>^ah?t10QTUV3w<QTg
z_K=3SAe~|&tPVCt(GrUL&cA|YH#&qeiKKTIGBJg&689~weRrL;!*~Ee#0H3`ibKo}
zcsR#1d7zygS2~A+J+s5P3RYbhyla910}n@Fr=Q<YN3tYgGTNV;d!Pbj6M#mdk8_Pg
zlrwVC)@1fYGI9s!F-U8@Lr=W7AfzP@tq?5<dgn^O<)z~Jz{D?NZ`4CFe`H<r^XT?<
zz9y0c$6C1@p9w~Naj!x8nA-3bA2=<gxXp6T2N+gjjXB}uR7ZRtfsKtVp4g7JU2&0~
zl|^Q5>hq5NA><FIyEp_gWSIWdhQB7E4H^u{EJj$}G-%ZMl$w?$XG>q=veVUbICnIj
zYb6q#QSgvKC+~%d0>OT)yhPS8*FRme-(!d36O6CF+-)opq4zl$eYOj4@_uWmDL6tN
z*tDg4BP!xHy&n+kPf4<rk!cD}^3O_4++pvCH8%bmyrO{$h{K&|ujyCU$-WC|y4L0k
zLKT=$&RG6F>yu>~JXkfqHQHc*!pvtvXFT36xwE`tA%vX(J1f)mRq<JE$F7_6{HPx4
zME<&8NQ*(>;swd-_I#w5Kl7@kNlwfk5Hu^fZZv_49Uv~2y)##flWT7qZDTi)6VN2*
zIr9Ao`w#bP9q!G#iak=lS8!uZR<<|1H#1JK^)*YP>$VcT@IEey<6L%hz^?_<i;ivT
zqp)4=ogz^{t95vtWap|$Aw5=Uh=_YUneZ}^@MBQwITjf?pZ#sd-lUGOV)^@eqwG|0
zD_fp|vNCDqfVcG;>@b?b*=K~dY@;BN?DX`lX^!WKT=6CL3{IQ$8&%_~KY^%AfJm2^
zjZ3dTi)uk-qnsaQ-z~Vs_c0iXZKS4KLnAeA?lJ7^Ld-Nu;a(4qDREoCp$O%eQH|(;
zBY6<QHNQ!H^I2fehguXY7=Z5!$>!eWU1!1r3*7na-iH8gU)PqdlI(rHV9<3*Eq9x~
z)MfDtkyO0G@}u!`Y<Q?!ccwV=I(fI*_vJ>LX#nP;h4Gj=CNZ&>_W?|{+3??RpaKU>
zE<;Xonk5}SzgKk?BGfr;Z|hgp`&Vi2TXW^*%YkQyQ__*AtZDVKXot5mAJ|XbOm;<C
z0nOv@<5aLm8W@Qj*VINwanniX%oLW36DXG>iYPk80z@Q=>c}0hJ&J-V&S$gfrKvvj
zhMm7Uo=9ur-7|mbe8{_BV=XNA&dVP%Ud(NBAuiO~a=#4ZZ0Z$g{KgbhV}!iqgp0fX
zxcFts@9{h=FrSAMe@9FDaJ99`E`05aSnZ#%JU~;Cf<g5Z3M}qK(iGnlH}Zp2rwrm9
zUEQSWH8qp>d=dzuzTd8$IbD$GdYro*@tIL=VI|daRZBvt3#$T6)`}TFAOllNI=MzP
zpRPeC`P28bR9NBt6g6_@fEOjH_K|tsu(jD~mZiiC0X?-P$F_SU0<<OTzFF#vh}|sU
zVHtI0e&{4T7}QQ^PtB4=VnQRn*h^BK;)YMqb||JcA*iapQr|UJOArci4n41lw@+a{
ze*AcEZ_8BsM)VIKBY;o#Hx3C!BR=U@u@IviWP4hzHIbFoQykuR_HFf=CqK^5U>(jJ
zuNi=6MYAU0Vwmt|V-XCa(&n_DxikkSy|2RSqkE{D%mI=0@o}1gzT48d%<`UO2rrkN
z70h0H9-9U?5!Z;7a1Sd;7^)%%TrvW=Ye8g=Qc@f|)&;M4Uk^z}6_Q>)ZUyvRMNM~r
z-%o~NoHS3_x>bK@kVgC@^OK4sXaU!iK$>I&%ZlRpG%C8ZiGq*PzzX88O-61Bj;3+a
zd(IRqqf8?nAho)ks>!EuD0|)1?)@EpRQ`sR?GVo}@{GmvB0wGHz9$4#OB9w2L9|%p
z$H{qpXcU3hVd!ibFu=kg!@!BV3-g-b)_lBfIhv76t8b3W#xdq-H60THdewa8C+qHN
zsrpy*NjF@;_M2P;WaFwwd+p~A=Ax8l{@1eyRxEh}iYCRhiRWWT1l-Qqm73W;I-hwC
zgYJ0YPm+Ti4(&1L!}lj-`cNS5tS%!=i=_D6U#-}0xCCi01ZwDQC_iSJc3#?Ne*d1w
zWxG=Bd%sVEay-%|SQw+zn)Ht6ODmeg^+`5=iiOt01lbbaXFnHr?NKhOl2c{7yJVjL
ztf3U%^AxKQPF5)iKa*fi{{{(_j1Te1>Iy%Vb*FZtRXQ2Tk{i|mzm#FKJA|rL%Y^Y5
z#H7wjNnEk;)XwM{?SRiCyiU8Sex}<Ie{G})(hSe<%{q7IIm8*AOrUsuR#Q^4o07Qa
zV76?$d$`QMk}9~1-15%J*J~^3amM53XHs^0fgIlpTh5M4nLw1@c#6+P_Qn{1e|~bO
zJcKfCRWmUpD&(fqhV0%h3QLfz5LeaIXr}375K7E*Xq;{Edny6K<;KfLSVg_$n!RV(
zNm#Nc8rNWL^=8K%9@7X?C1={fxbNTDRP6p9O*kM4h`ZWcgTxJ}Ag{G}2>NM=oMB_@
z8qI|99734ZCeGqL%#fRJ)XGxx2>TxOb?ppC2x+7%&_%+`WcS1-0X*n~%4VuC#OZdz
zu;+oa$d8g4mFktmKPFDDYb%kFP;?PXX@oPH%gJm%tM+riPA)sth*fGvB3VZ30?Id7
zd!gP!rH>}t+mVPrn>I%)1{1P%wo-1h(G$M@!|LQ{{zj63R&pMDim{aj|E$#15*8*M
zpR;a6o4E?D`G^N`R%6DD`;yc;fPsW!-}<IGQe<_hoA`8DGQ%Sv=sP!7U4u)Ip-(uK
z)gZBA@TO0&aaNjsPIKO5*gox$UM@}7r__F5x%?tk-IRR=mEDd+cg$Q|E=X)Gp4W1%
zt@*kpE(_4Sn8^2VRLA;~{<k>&!JB|MP6tr$-fY>tw7QNg8Wrek=wfSL(IG@*9RLTv
zqEu3$D%xs1z`F}8EA{TlBOB;$t-aQOM`v12_H>T@M6^0184qYgr<bLasBEcN?l<?l
zWsmu1kDtw5D+Z;#-iqh0jt;6GJS9GywWT|3<HhFJ?nid*KAjJ5A9*>KO1Z&wz&YE8
zMY>G8;HaVM#1cd+qA$E(Uuv+zW@nFet)+L1%n+E*@&2;*i-0`Kq>J6l*?H7C*@7e@
zQdSdM<<h^c|Dgp}Jy3hdh{Ow!3h#QdQnK!UGJcW7tG7Sm`zKhlBoBzgn~;tn;qBCE
zbwyc{O3cV8cXUK4Bz%E{6l|dmWRUml+OMN{U54qG+J1_}2|b_j_$6697YlWrN7AgW
z%c2PQ1~$y*I2E#ekIN{VU~H;VX(ktYJ9fPqme}m`IdHNx-CTh&#&`Y)$*otod<P3U
zD|^C*IYITW+dN4ih6cxJSu?;qB@>hn8?x1dN}ky9)j)f9Kw!@xr4S=PnvNvP^Pq$n
z`}J!aPS6~O6_r$!yY1b@4z7ZV0?wc6<%*4Df$f&pepEZ6yOU<*!pfL<uuzkKe>tt#
z`uGSQr*ZI;?0Mt`qPql#(T}G3vJ4Ye(8fs`Oj?<hM?^Uq@(&cmnWlkZPWpzHZe6fV
z!~jegPOE-v{%e`&jGi|FSb(Sa+8CnafdV=&Vx+a1tOxp*kR((DhK(_6Kdg#^t9zw`
zXa0l!cNdFgdjv^g1Ut@#8=7{~Who0hCQXa`9_>9a_pPTLUPR183N$Etkp2{9x-N0|
zv%MAmGsse`0tbVqYZ-wuklP8cn*K<FAC|9wdw#T7XIE;TrG0l-VFNFw_IkPiS<qCJ
zUft-Zwga!v+EVG}<Tz*cM}Rgx9bd%B5-jS6<zRO9-f#7S)!1+GkO^FEa{bYgU{N;T
z!Cs%I@C(cCoT@1Q!q5K97Fq>#^-7UXhIJm@HZo{FYsrbyH<#$z$=kl7R?HGee25|C
z4@HM6>T$NB6B5#mCKvX#`StTc>rdm`BA&yAv{wd+57l{(rE$`+vMT@h@uQ@m;H?YL
z=SBx@`lb-qLp2=jz)w-d<P=8NAR-Pt@h&HZY)Ac~D{#{LR@6i~>9St$8IY_0@p7WC
zWjgcOaJXg@&iZ5Tv#F_1G>uU~_cR&$_xyLoM$2FO6rF3gz41(}E^eHnw%5EOi`E~$
zh#5X*>oD=0i-W?s>~3BsKD@6V?C;0D#PJB<vYQVh_vO+5_5Iy@NHj(z41-*a!)bhY
z_><eJ%e>!XCe7fVQ^9kN9Ngv)kUpF5e7>@+q@to~sQXDRpLSN11~DM*p7|Mmuc+u^
zdpn=thYaGt^{#>gdTrkaUrB?XJkyvfHm-J!V(<%R+Z-gCx#+ag%McUf#C;#AF<lNw
z?Upp#y|acj2+ejUZ=nRxMpcVKTpov)!=Jyc4$pZgIGJU4`t9=nn3C@4=>adiS8<)#
zc@y`w|9hZG=u?*0iN;VSAt50h9i5DWD-6P|mb>KtW+4~?G%0iR9Dlt7-vzU{)klPf
zPxhcS>@}@8jzllax3wvbZw$qv%=F{SWsdyVXyhhx3Qy&Qg~>Onn%l+GL3%CRgr+V<
zER~gdXVKRFt0F${yW*<m+T;AyEntn?hiLV93(o6t=!G5Zs-JQPa~aMMpx+@&2&g>F
zSM;d+R@Ym-y0c^4ROT%7&aZnahyJRl(_A;Un{|bq-}OidvhVyb32j7Lgk%I-uI98}
z5HU`m`Rl-GKac*lz~``wabfs^^B%*<Joj)dNqJ3^V;Xp9_+UwF6TQgJY29vFQ4F6O
z_HYVW6L@KgIy#j6{ob@HrjgF=W_~lBbCZv;ayLM;nfR2Y;wRdj)zphMcRb=cfzU~;
zU;DZO4w~x6;J4yw@>Xikl`2=Q<R+~JzK$gU&!g#>Jp()EfqKgaSqY3i8ip+l_)@&_
zVaMc=K2ilV{uQ5_)uwujX(^0pecr-2fPFvimlYx<gm>Tn^lfN3eoqA$If_hBQ?bl6
z6@gs9UCHHSMMLm@FCX7XVPAL0Lq>y(c*lv+-%C(Y_Jn%3sIiR7;sMbsddtkrICi8n
zQpiIJo62^()l{fZc|;??L@*efS>0!wNVIy`fbh+R#`-!wm;@ybiqCEZ;A-T`%OACD
zLm<AVp3?&@^nm)-l>GgK2L-HDaoJ3}^!@$UU6&iGSOK<ZM4lf+BP;{eWj4!=B{W&?
zn@r|2Zk~c4T~Yq<dX$Qg-~>X{<yH2li^ermVEnEjTdU&H)Q`xePQT9U`Y~?<?Nje^
z7&3aY4aa5!Qw8|uWURr3kr$HSn0zcOfL@LAiGIQ5Vpu%2!!OMn`Ldy*uhxld42dv5
zK9MKz3-ab3Am@l9hzVu$<CneK8_NSC6iygrECde-lM8S99UeCU$xs<RVt=P}Aj)Gw
z69x%6e-iY(9O}4P^UA*VYb3$_(=t?I7IP9g3&nxQg<qg6dEwP~c3FiTx4-6bAN5D#
zON(RQvBko_&Ot;gg5{CLtOHC=m!)Rtmgz@Sw5^cfCgXgjgkF`2KP(2A*>Y=Qywr*C
z+z7l`&Xwq5>A`4GZd6BCM^Fb`Y#al3dcG$YsgpT6)om2B$hsWN?CVo_=+ziX3Iv1q
z88z!Cb`q!IK1Bk~M%l+NG2WtuQ^EapyAfHXP%4AF?C^Q0?7g(KGw|e`%@KtaT*WOa
z{cXzvsV@c~XdmAAV69QBseL8}v~66{)~3zqu8g^LsWB7RliuWeUvu?(ir<BglR}h1
zy}y5@ZqR~kMRlB`$*`lk1%K2=R;BifVk?)|qSMQm=KbYn2CiL4e3QxZ&;bRsw2dE6
z50w(S_V5OhG%r#wA50yh#CtR6a(<zj?ov;OaCVg?*Qq)bxbH>ydfpBwTayKu;H<ip
zO5OIfovSN@-q6o2V466A4<vuX8i)ZfT5C(+zGRLh(tnZ4_P+SFk4DU;T2oV_xtDt;
zj&b@5l6?rbU8=X}Uis`9dnyb`Bt-{fn(E&-R^MM8f=Otbqh+Fvu6;Ox(ig5T3(R(h
zQGV&ES_s7}nV}Y@Jw@8z+42;ZOkxkYnA>LeF$j<=njRE#ugQO{2~^oU&o!B)YjhTL
zMUrK~6)J3zfK1Wnn(e;=M@W;rCnd2+sl8RTPOc$IT|)ac4-jL){PoO?DlRE$MVP6Q
zlC(#(^?W6%okHNBOIl0>yVwPW&*`Zfk^EKb?Pg>rC}mCf<xwS_!pYV-=I}QfQR}Mn
z8eh8bX2%!g8T47N$Q@pjAZ&yiD&X)d)IaDEI2ueCe!!|dfWw_TDt~y>qI=<P(_D42
z&F(bcwtJEtcBC3ZIgBLBATV2JZpb6%o5luab;@MaU2N@~qOA3}iQZ|Jav2OsZG#18
zfOfaHiyLj0En|<5RP(OAhZEihL5x*>P7C<${GV|kihAT3I&3%8cfnv@NcQ#)1WD_q
za}hQ!T5Bp5b)j#x4c3hd5udp`(~qU8n=$&BMtHr5i$@nfr*O67ZeN%i2Tj+A@^F%1
zsvR2Xo_30;kE=8vGJ7z9ZkPd8;ofRjoMW@&CmcQFU5wl_H>I3=rc8|$@KR`v>h4{_
zgktvwJ8O??Go=6(lW9-}XmN2d!sG%H9Qq9~P(k8h=sHwA9wz(4cYk%z*8ASBmlT$N
zc0<D6KuSR}W1lAFbDlu|xyKV@dJ2hCsz7?O<ByC@&450e&UW*-L}#>EY$G+J)Z}QE
zpAQFEMQsnmA7Q5ksd3Sui>H%KI%-{3&#Od`R_zGOIoY@mTt+%Yoz20+G;<?J-VAL<
zG;f13O80zE`-sDBrXtWoCJ^{ymc&_J1mC@r<WCz33TlSHn+DS{B2K5>(G#-_hk;?t
z;Ywr4Kd})erIJ;l2K}$dEjN4!hhWMd8g}lCVBlL>c{#)JYUb_<CIG)X$Q7ormhaQW
ziqh@zu)xYIz&2$<T1SYJDUQNnJ#}iJ#oU20yNyjA*8GkV?TR?dg+76fBYQ^(1`l_r
z5ivu|QSlirMUHqGy4|4+B!}hGUwdu0)>gam+>SW7+w9odv)yK7YYX^zww7()w5)^m
z?OXaf<_Y5C^HcqE5U?76JaE4iEBuT<?ZB7mIm#=){60g^bN@%3Bo79H!AJ4G_9-I;
z&a%QEFbKWj&A6N53pK4S2s7w#Hk4JAInce4zSQbgl?F-NZZufUOX;sUFUWjh@@9XE
zU%qg3Ley`mfc{V-Dr#9+8x}$u?kwfE>DoMcAC3kTaOsNM3DEvE$~%>~wC)cR;_QYe
z*S4Ha^W7fc#XaU>K&S^qUTov_y~74L5Ri;MQdPU2HqDwZuw;TBP*Fi+chjLxN7pR3
zN8AlzzNF;S#iIJB@L~S#Q`6HkJ$FD(KA(xN(oa8d_gI}#-sP+81wxV<r4S0pszIN{
zGC^g>{lW5@*J-;*{CD@isvaaZzzPE`^EFo%zUM9<l4}GBxVz17O;S3Sz#^j4q8yz~
zRg(GMZp<c*J(b%Dw{DIL@@I_!h6R=rlb5@8hWpzV)U`cO9yT$4JbPT_29?ZPul(Ev
ziBy@S@jA#TTagUW!iw`p)k!v?ez?Wpz@Wsk(_-Tb=Q+vBWx$)s>GjCkm=GsM0h~X(
zfp=#ac_cOEtlJ`@BGi=Cd34fr^D^j$3CBvNaSG+Pv_VB4ia#E`I`0q4%G~h=Gm46e
z%7TO81h+Srtg4<ONM&{ul>vWCXhBTn6$~Fa4v8Zg|I_7ktkQ>~>kI>6htHBI{%G{F
z(a9zAB>?657XUznMT(tFj<=gLplxMb!FeMop>*a%hd9uMNc74KOrFrAYG|sFv^3N4
z$(}QT|MY`g&i;IoyOfMf<A(pWwqnt)v<OJun+K2&%j@Od?qag4r(U^gVyOENcy|m=
z<R?e<ZCwqqdYl{l>Dt_qoT!^KNbY^s{Xm<b!V`w?CdqvA>Nhn4HlUF5{I50?l08p{
zQ$T_y)pP<Ue$llUlXl-8!aAmnS$?=Volm<QB=fR{iP0PP!9~Wx!a~etY)Z#`ZBeQ1
z_#X5AB6nwQ@bN?HVAY9zLAjd2FH9bbIe9e40K&_2f|X4nfj6*&tlXaJTcQ~F!oG%&
zY<Z9r>=w6)Q5d|3d+j<GUMqI(ols73(Hn*Khbog*k1~Z!^k80+dyUD`&7VKSHnt{{
zP~n%Qx(g0X-f8Tf|5hPqDH#QYx#`mWzCQa7r?f^tPW$z)&nDCqSbyu+^zVLUDpo^G
zV_1=5w(mUz1vT{YAO^Er%JKHkex%7Pu>H9a`US#`hy>tzEV0%&ESCfbGHoX+goshV
zUx}x44<-p|dd5!XNhXbXOd+s)LBpxITQI+#LWTb%NJcydZ2VwS=vQuyjGZLmOz@z*
zpJ4ftRlE(ZQmQnm)&*j`O0fjcW}xc2DRj|62e$49Ld7beNEdmv1aa=_fXOjw6k`RM
zNnVcGxw5o6mT`aX2aN|OqzQOjaF7YP9;F!G)%C#RYujfxFk1bI5Q6=gVQ8ZK0mLNS
zwkvr>*}k4^B)zz)Ez=I#rly5?)0GhBhSf2IA+_n#ebx-r*~0;-)EvHJ!$=-%_f!R?
z4-nLVjyUUB>oW>ZaAu;10{aoHT-_PCo#x(aMdEkH5ZO=LGbamBx)L&a+Qgh(S+P^K
z?c=dqDFozHcEM)inEDcJUnnLr<~_~r)u>SQY9Vq-5|)#oeBOD+oOH;5)`MZX3|3{z
zaViGYnvA5m94~#g8n@W(@O|=hSu{!ZVK*Ma6r2{>siZLbGl^=Shs~1<=Pbm)6V*yK
ztx?ghJyQxH2x&$t*e#J@j6xagpIz*Xl+>d01WSj$d}LlXxn~iNfI#svBo2dohrx=;
zUOhWY#pgjI(`Q||{6<W+J8Fi*8bRW~0|nf*jmh*3A6qgrf@oL;?uo;&PXhTS<ARe^
zYj#F<PnWZybt8O&r~G4Uz3HT=vc6lAptD~UX!$zb{wG~*wsmbq50SQABm8_0#kEzc
z5IPnHnHfxTa|Qx{b}C2D`@H`~jn05q<F6Y(QUISg1r(#vu@N+y=PiVGlwN1M$`|r}
zPSw(~v;)~n=m3z(Pv7SNXGk}Ooy?Ho)>|lV^(;OP<Ve54qfO|}Z#|d>U+$8&xB-tD
zV>*3yza1ktKd8m9U{u^i?tdMw9V~d<GoRSE%J&U(EZRBcYuHJ#u#NEN6$}10b7C$D
ze%!BblH&`cXK?{J(d(@2e~1ysm&)|8eIrmsUOCjTJDv?RoX8R7Uuv?e%It*@mn@F&
zAOx=Dt}?F)fxa(q?HptNgmMjGB0uE4#Lv}uPwz@Um%V0XA{C#&DDk{Hu;|{0cn&iP
zTYJZ(FppB(?Jg8|P12zijP|cUR9u6+;@GmH%$zoU%zboCN;Z8>dG@y-H#WD#KDRzV
z0A)=!WR=%5R-G#qGcv~xw5ev1#+<F*-QA59zq`Q!oToUi`{K9t7_~GU<KhBRCm^n*
z?e5Zrmwpqz95EvJnwTO79QU_iWw1ypoB|KF+hNQ;$4R<f$37%epv%b9jopgUi(~P)
znlFuU1>v!A?=&vkKKzO}wTs>uE#X4a;cAs%wARHVt6OAi;F_xk-O19c#u}K5q`y3L
zzVP>IJyZB!gByisZgzH!xqEReSq#QQ_B|ShN5&>)6%-m9U5AE;l?G$T3_6E9BGyKx
ze#pk_dL1_`v(}5o3YwWsK*(>Z*+M?9nGhyjry7S2?;or|q<|Lb^<dnIJKAvp@aPY_
zj=NnW=Q+tbBb50WTgMn@lzj+eQd^IKIpJ#I`0nl`>XIWdF%>$@X`haL>-PIM2RV}h
zqhCA`4#$N=Eba?YwNt45TM$xO1o+{!vlAl;2L3=VR?g7dr8C{OWuKX>)w16-e)rcG
zN89_ol$46A&G_s2NZFzOyw~wWyBwBNhSFu*jpU6M%ljc&MXyLSCyB*C{Z9h(`_2cv
z<BX@r^Ez&;eG!H4LCAkN!W3`{>M*~Ff@T}La!5O-5LV(C1Zk&?rE_y{IHbqSk3qO)
z)*>3*oqJ)a;&|iPoR>wCPJ_%^jpm!<viLg9-uroFYUS!|rpHTq{HM!JufajHYt@GR
z5ysoTlq7r6mu->J#N4hur@|f2_f}~qvS$=$hgF?iU5a%oMGB^nY|&Uk0uFW(k*T{o
z&q(5bG$bbt*<FQ0)d_Fg@t^Po6DdH;w%G)JGZjJv<=$A;K|O%bbhxw{EPsStiW$(y
z6<9LFSO8E*Rv%rej(}@z)MmYA*pAna3#{s?-H6f8NTv`-og6PX{Rj!BW_O<^LM-WE
zn;kBOMyDcqQuFNwGaG2lp27%ll?q|z2q!h~J(JhXc{^M5t5htqpEiTYJk7Zk`S#z|
z`99t6{-Vh)ADMzU<H9YbPSjuU|K+YL-5^~aEjlruEO|qip@4EPH)b~mxESo)^Fi`-
z(wBEy4bdVNO>+&$=)>RiMuR$bBAGirY-rD7@?522mP7K-SI5iTK9I;>&CZ9)r99J$
zG`@-U)AaYI*J(IA12aZ+B&eo3>>0yIr=>^o)N5pmPZuD%bV_r7zfMTtiTxQel{fWM
zfff&t43w*+FNE`pR^hXwVP=z_y{UV%hsTbu60n@6U$gCvBgn4xe*Tk*M5fQe<l`gd
z2F;U;iN{psub<%EG1T4!ACF(ZexbzdUCvlKzy0Y1QV20ZCvloJe%@aCEUgc5QNDG)
zJbQs5tX7OZoETV#A9L>4lPSNtyO#P`((<eGZW&ow9ry~}v^m|+)`J98U3kAIgg}_6
zv@tE}p2Boqif}NIc#ILGEc#tF*c-YsYp|sAJrPwkBRdfyKAx}e;`Z&0(?7FiU3txw
zYoJL-6J41N#*jKeG9g|2DvBvwwg&0>!%Mj3^bn|uDA<R^PPRBTHFflKe+B-vWXN=Q
z@Xp^6Gc_^s$1=9Pt+lvT?<{0<`P5ORApCR*#Ani8AVVpTyOk{E#Onb1KG?u5$=^ZT
z_yGutzI+&2{0T{}*+Tfag`Z;b%Wgh?ezv43z<1MA&w}Lm6!w&db=y4~4kmJg#NZ3i
zNqBN{K7YXk7(HKA`L##ypy+|-`<~0+#p-2s?&mc{7f%k`*9Z7py&rqOZWvMh$g#6@
zzEZcZm;GGcK07O(2l17~CBeK9z%+m<6hXHQA)L*G?O(_Iil+gIi!i&@?l$hov-uLY
zNb=r`A(2Nt)}o7MMZ#!P1k)IOan%OgcRnXIZ>KtC`kda{O>SVWskgb;oMgs^hbw20
zLS^8XA&T62Xas{J1bMhHC%R;KJTJ|)+LFatV0$h0KFBI4DvtAPMX^7Jgf6<_$~Iq^
zDWCYR2Ow64g#6mt8!E*Yi3q|1;nC{`A)w(9O_roY*wG}BPt<@->P*Mfaws**i07<D
z^5frJFVq;ZnhTtwC2CMGoaEN}?*B+W$laPgP55T*ZXlxsE3oD0=tv|=Taulbxr!#F
zBGu(5gZ&sY_)NQk9g&~Zrjfd9XpkS$dMn87db+j>bs9$+i8jUSonM^eN`$9<?;eId
z4CNKotBf%x?n|Yg*hn?u2sP43?cw23qi$%Q-Fq&7lAfNvi~yuu<F3<XQ%&y*2{jbl
z{(*a91$B_;tKKB7lK_vHGp^%vHOt8*i0IujBW`rX!9&|lR2M8K(Vj=R3UQf00_T0$
z*@<v!#C|V3%zlK((j9tvB$A#Z!bE2o;ULXdS{Wg1^{WR^l8ZAi3^6J^X3b{Oo)f`K
zkk}nF(P=I?g1+*@RTA?_FN-MRTK9*xI%Ip9736a*1JAYly@_K8lK<wq*A+eB_1*so
zUBV52H?t0OremtBvyhBP$$&!oJf?)8V;<SRC4}?S8;U8JLSX_1E|*5hPcO`B;7%3?
zSb?b3Xnps_8~4Xu<d@~xno)l*xLc5}(-`LuIN(7?=Wi?03$gaz@0X-r)*Cd?+d?1;
zThZ^_`4TEnN6_m^9?DiLSd<WIf3iI@ov}K+?2)+Y){Dmds?W;}$K_`r+bIWaImx3`
z&SRKCW@LZ#@!N9#APeRMpV4w-0(T6yZ&ecBMG+>@V(vA-cYaaC+$X^4BE_Ps17z~j
zV<UXJx0A~&ugU9=FI&c7LJ(rFFBC*00o%KP%w?~=iQG<Au1=uB%k9Ue<s*NYTUC+D
z*h_WwL_r1yZZ@`q<cy=El!Syvze7jI(;pp`iS7Gfu1ZcbJFYyYM_8L`E_fJQWXX&G
zzBQ57Q5V(JX7<mQ8q~xl@7~<Ch@C%S2tS^Y7b9&d-KOe=920K{*fOMy!PJ2w2bmte
z3}lpXrD_l_6U7wnefS_Pq_H9pNm3WyKS8>RC_kT7kWwS;DMkD6h7$*NZAo5@fkFD#
z-x4txk`7kse7un5S4~K_qSd1GTl}Ky@dF46I@j7SR2wM1d;69|O5BNJIQ`^^mL7~5
zqnO2F&{JBw`FZj@&y5ZeVi8TxKg*p&B~_e?2#kSg&S5RA>*74bcZIpf<k}l@L?n7-
zpP0zt@_oF$`<&ob^-HWeB9J1XZ-C(<HE>|tz1(ZVXbH&$7hZJS?b}UuY^^PsfIABb
z9vs^F2J?<FPN4Z)xJka*kz-uj^GuHUyiOFM({a{%OR8Jyyh$InLfGRv52xAB_<L}l
zF!5#@=5@WeP1D^=-5ZCWU2az0vhQY86n&xxJg6^78jS{H?2{g9dmv_-EPBAEFxLHx
zp|DS;efSMlkvTVq1WNRX+Xl@J8wX$@rz1t#x%xFR?Mo)*O2sj-^F_e?RqQ6IyeQRA
z;@~qjl@RcvN>$52sfmfyE8E~az9DuESM)mcyeqr~XPA7ntU(_e@i=F(96xvy`^Q50
z^w&Q9;1!Iz^KTeJxB7`L33<nym^Rh;4r5X_OZ9iqcrjthAP(_VD@A$AjOrH1Ly%tO
zkOv{ywLBlPUmihkXXHuGqMPwavr&kgL(E7pD1~WZcKA=*ustA_AOAfIQ~Tu<d2Y8e
zrCrU$C1;5K{8wN=DayBR-|oGFV)A*ASo?pZMd&0fWp&u+tUv=d0h5!HAB$fe^07sm
z%ocP*)&X`pM2&764_#g_!VEKWBweo^p|2E3F33^Ul-*;!a$}z8mwJ!CDZ7^9Kj<0=
zlYQw3oY)&^J$-~k{12Rxie3k_2g}PGm0e{2!~l&jceddG7vcq&2O1GgaJSpdxetwI
zMp~?Kj{6W2;`VP9yi&?N$<US>=lM$Blx*pI(pExuxy$c05h70#pZn#mkiq6fb5ha|
zq2MpQCdKEccg$RJR>+*n0e6c`teiuhAJ7XVo48>$RZnlJ!;03Gcv{IZ@xv$X*G2Kk
zA@LK+yq>$C5x#Ma`WiJAG6Gh`X|$I+cF|-id>kGd*$4v^aRKCX+_F#(qiLHl0gHG2
z$rrbg;pFg|7Thr*8xIGTMUHA6f-qiYhekV(K@ohgn(I2n>#xu9NCqP9dA~2fQaW4m
z#!pR-9m(6EdBNO&om7~1`j#yB<IJ~MgPY_donI9j_qe5bJ!wBe1rYLNK@=-5VXBW@
zQ(2f+stqK*)_Ml#Zlgy`M#ej6lV+hjIVp>PMs!yJ45qWk3^b%dia;q8*SwXHk(ug!
zI}v|df&_XF2%Iz=Na1ri5X@rb6(prMR0Cw7V~OQGBjpCkDnCTU7NxP749oJERf9Zc
zYocRC$-Q5xyY1b>P$#1VR&><Qnr}+im4^xvM@Q)`&`tzm7Y15~?-0Emkn9HaikOGu
z9rTr5kK=J@tI#<iuc3y(TGmZ`eIVF%2IT_?LOFt-0iUU}DeY}x1s+l{^N6-IvX2>s
zj}{CF4Pir60yTGlTH1OKx6jooUw2T&qI6TJVHuPW3_mkLlZu(Y37)9hQ2o5o%;zHZ
z?%CcIXU-2NZ_zwh<ce{)n*eFr2<s~T^<+hMw7zI9%nl9O%_6ck!kO>lM1e?`jcXQI
zSDpD0f-@s}cojn@8rNhBYONAp8suP4S1`xx-Q{)DU9gD5=jzslE{vt0Aql_17#H8J
z(swy3b)*dLIDFWJB1oBiY&{^fNK`==hM#-hBKf|ET$LzqRWP}@yV9ydX0JD%E(oii
zP4w@*3%xrRp}P>+g29WJN4@Q-GYF3IdJg*E*1I^Wn8kSP;46TtEU{tsj@Vi4<JVYx
zE$9@dS9j6tERwVYg)BZo!merTT?dpzWjRQDdvdlz90q)ktV<t3;^}L#ow5iWy$m#?
zVONawghk~*2CMDy2Y<<E-=b8qHSv&ZLVm>{${cA5QvPx^O?`vbZ~F&)Ux93M9~m$(
z9ZNJoJ$Brj!=l*3acW91OUIKbbUdV)fr&D)HfYXjXYG1lkDClGUKD=3F7NtfuJufO
z<G`&bDVQ3-MmAR4<vC&L<}S<i?uUrG8L7;neu9rI&kbJt)I&L6INp$|nEKT_@Bw2r
zQ*L?x#i-4I(dsZK|F=cfzWy)k{2`#Jz(Hm1>b8z!`jhb5P5|<rw>>66xC_-@$g^ZX
zQw$H4ph!2J)kq58d;4B2y`dlvgI5?hJ4r}-DE9u9_&$AN6tuytEk^JB>IAM~2~r4u
z)Y;qmPvz)ZdN$BUAW9pdm^H0woei^y*pFPEn=zX~^JL6p0LWI|0V?<y@7d$rAQ#ZQ
zEtrzdC29QVOX#X~$27Ka%llQ_$p_x55y_sOilP5!T4EWVA2v4XPNWdV+w(kjW0OKR
z(Y1!^tjy?`fGxsxS0xyt$ov#cVn#Ki@14pukehnh%FqTu4dN)r>B9ymA=XRfbRn{f
z^dsQMD$9<cWF~TlK)tFXkcg+v@G6el4)P=*KO&XGOnS?wGedf~K4{pV!Rs_Ysdz=(
zRSkODjAVYs@?|2E61PMps#CrdK^MuleG7LVPXSk-D^+Bi1CJnVz1<Zm91MmpPCn`3
z%wi(s{@Q6q$w<R-6C3dG!J9#GL;CwlvuSFhP=<Aa7Xk``b$xe&d{r)QEqeAiT7n-I
zfbq@XJVKUF2})cKIWc(K!evRlLpdf}vzZYE@XEb%Y&iY(nk3h7B!k$3{SFw^I@}T)
zKniXB$}^aCCA4uZ*&fgvyOjwVnL&&U;x8A;^|xS)!+=-v_H$I^KdxWS!Ac7u)M(rf
z61{~rGbCOoX{1_)VtCM2pFevZitb!g?lS8I^|=LUTBh7tM&lj?G40h)i}_;KZgC?c
zfzk<}#mlG@qlQB1iBHO@fbLt-^k(B(PY`5C<?{I5LC`PXX-DzV)&O~18%$USJq8+i
z*ahqRhj*HGnFX<F%3+sKsh*76BY`rNtHvdCaKZ*|a6eQo?oH;Ow(aFb3W>FAzK!Y;
z>k4-(xeA0wr8anQ9Ur+!7n6PGtWT>hu_yk4*?dlbprdgMlKJj@hGa{8XTdEiyG;>d
zh<DW))xNJ>tFy2VP`Q!<vDA8&47od6BlRtuggZN{3kWVdU!LqxMsR>ZkmvCjgBq6Q
zX<r`BnF@p<oHWEhhYkHA=#9rO&PQ^hPsZ!%v*hD>jQqT}=<H`+18ieAsWvD=^g=Wz
zMuNS3Q7+L9>j~4%U7t3*)frgAEs=}0<Y@hi9~Yx)XYfvSIF_Z=cp$af^<m~U5BZVd
zb%ZHn4z=cPnZ8~N&y5;18$`#O)A&pnC#>V9;%fMWX`X5pM!t;um~^JWa`qJ9c*ySD
z;uGlj6OHtR|Jw_d`Im-)hZQW8G^@#T{wUI(SMILxxbe>}o6jZHEMJztiBP$c5%r{6
z>*qn|2+OD$UG`!Kdt=^kx8&UrU}3pH^%y)=vxHT`$rNqPMU%M^_SEkKtc%9xWoeWQ
zW0NLo#+9(nZTuJ<Sk|+D`YoAd#$dDuB>UnFWR=|j{rsL2-mAbU<kK2%b|WQX@Y21S
z6Kw(K?0ro}n_)M_V_4;<&zJ0E3#qEVoT;g~+MN6v!C)!yCZNZewAfoTZyjT7#V|+^
zfDcBZVf*)Q0pM-`Jy^NQ?;wF#TwF_PBFRpVX5PgeQT^S~RC(4cZwyYdcd#Cs<O*Ck
z8vE?k--cq*h;{c!2*Y$v4`6365j9_YxYyjb&@daNd*5D*a;W?6`~Zz-3uD6Ed-J6g
z`1?X0B^3z6pbgQZFYl33HbUP`O0Xo#$8x@hgpZke!){-Vw55{Mdb?kFU;?rO&xFb6
zHB8^(Y;*FbaJ|8}Nlavd$CV}i%*HhA&BsT8xBhfbUjEHg*S;IxOJ?93P!cW*l;veh
zQXl(89H~Gffpn(`nm9PAFam8D@=)@2Y(hc;>BL%j|MNR@k>^meGa4c`Cg<%GcRXsM
zR4!Ym=$rl+qbo|ehVB+rxP<A6YFk*R<w_QvxoE{*sPl-MdK{CH8w8?uElA|x;q?Xo
zt5Z{a*DTiR07*tP;zsMUH=P_sE1_2;9Mv6t9@9QWn$E`l4Iu+~r@d&D^}_XRk+&!8
zHm+)2qjj7liMADAF>vU8^bR3NQ}{{Q6hn-H0XM{C?e(WSTTO^%?JUnHSZ~^uDYu;#
zE(OIx(^LjgSO*(Xr;ToJZ?n+iWQFcuy;ti^T<mf)r#hHdM=IZcu7#f~+E^L<Hjo)*
z=2EYY=Iu&S3uu7Jet|4VA)cX_G+N1mH&wDZBzvKbv&4aS*hACS45}&W$@5l738@R~
zu&qI;@UG6**DZ&Yt$1hYJ&h!=A<PKQ+8jLxxAJ@KxG%69-fVD<C402ZD4LhDalk^%
z&>q%$d0BB|>6jGH#Bl>uxajQjW6iH_?o?UJ&<rF_Sz&I1q%hpZ8FIf--jhq-=-{TH
zRd`#IIMHf%2j^f;FG$2Hi5DgHmAR98bY=wb!$#`5bilI8-dZRSX98or;~*dQK-anP
z^Q>Dj3x1+r?pO;+FBvub_tztw{J9LGlVB3{;&KsEF6^sC{5Y(n&qemWkle%S{YmSo
z<%ryjk4*(YvkeR~GR;v;Q6#@wmm%@Y9-Iv4z#Q?`)T*{El!WSJy(N<{Jo4n)f}_tV
zKZuCK<G}&2Y8P@p>OTfvScy;?^fsW<$!KGGuo%=N#MaIb_EyXprdj!*9{}+oeugXk
z;rwaG13+u;wz4Xqe}@EVFKhwbn1+roVa_X(;X#1{hL)h+f!{NY!OGT|gGb{owfLx)
z-m{Fo^A31`QP^hqe3RcarYPiHHv@z14$jAT9^YO9a@P8KUPND3wWJfWkF&CyM%{Fd
zK1QZKn@Go}S@~Jq^COJFxIUy6Cz$5Z_%b*BPE15U1I}Hdm@Njldq<<}2Hya&A3>Re
zoup=_-s}WLsqm$QddNmEd6G_2oiEoTX+RqC4&?~u)c9jByLRJBz0Nm_il1-=jcbeQ
zBqQ-W(VgEK<|%usNMe^og3g1^ujch=L{M=@9zgCNkh~M1<W$%0N&CX~5mk4EoydjK
zJjn;1p89TcF)7xkR)&MQbU?=tXQHK0;BJ#2#^#F~(u*D&DMwGl2{v_s^l-eI$<`ZY
zE~X=iuDY*5XOkpbzZUJe&sk?~!eWrH(IW<O<KJdE(0h%w_zDpv$UooDcOLNJqj`)G
zL_ddiuLllHkqGf8P-ULD%<J5!n@oo&O<{`VDq!^d)cyT~0;u%qw&7rT=i9ydN%z){
zz8bna<iQ%{JsvrU%sxk(oJanN#YPf*_DQ9A57DB<?50&$;xS3NLk)x7<Qy({dPk=-
zj5A)au^_&0@@@KY>P4eL&JRn3UC8rce5fvbXQ|bg0tb++33Qf`h|{jb3c5PeHqR;4
zI6W@f(s9W`Nzr7(Fb$t-YjT7-JpVdR1!t9w4*pyiNvrmLm)Vd-z&9o3rL%aEx+gkR
zd%VY2ujl83r62uN7eh)}3_1oMr5w7wNJByK!RV6;<|^J}UUh5u^&a!xQBOE@j-@R8
zCe&k(Y<hbOi-T^-%V#h3#K0g&VJoCP&B_gaYoFG|Z=X%6hY6uci!xIc6?Dd2conz}
zj&sJl-3}5&0KL`Q2yLOWb7E$;RU&}0V}}E0Dpd0P9mo#?=ysDiU&Bn2gqq^N+QYKZ
zn+%H#ZPcTT&ul%y`hl#m5xM{L34kD*_z^oUFNXH?{AY49$D}fe1H&)3w?OGLtdp<F
zIfP>_lj1@Lc76|9Mhenl2<rUqLEgPLscW%H3oIF#+$k9{(F#Z29i7#4wFUy255;VT
zo(%mSGn)@+S4M|aIvv36%`i0d=G6_+hSxPjf-~w$BZjG&xjpAgPoNvAgEP_VT`_()
z0>S?e4?*z0^v8$+JoE7$#?v&>GL=HF@nD#I-(X>)rV-=*`a(0<(b`v&Yt$85#m}B<
z28<CKSf2dw9ii0)G<g%=dh4zGSf*)3kOGY)g=F+74=zu7m5GbIP_yG^FE@m`GzcHN
z;Oy;brb$gA0~!nm;YD~lh5{X7T)k8NRG0wjjJ@c1+RFs2?@qUF-B5{FK0x~w!&Izi
zhwHFmTB!i-(tebQE0_qsmkb!jQK9dRKDopn2%9~*%VL3X$^Ta(N|pTNR8p|&IfOci
z<(i!uc@Tnh1JJUn!+noJ=ipzN0a`lnJBd!L2sHltR!OD;OcZqw1;ZjsGCGTbLqBcN
zgGTI{0F%+t(9qruVficmpr(oePTO7r4^IuN-XDZN2}pw`vL@PE?C9V)i4QR@p4$})
z&~9JE6Hz9M$`HQK)lyFlA3l5wuWgkVT(`pa!E~&EIwFtv!$7Ss12pbz6joV)HkzF@
zI^bJ-ueDv9)_jlojpBm$+J)zH5FXCgqrLGy@53tJsBbqw2KYJHR+i;u1zF_&!gCtY
z8V~u(gp=lGuuLm>=;cTdej<Khbk_Z>s|vTvY**`u<@kg2iwWiE-1j?Vmq}alPC@$}
zt#`vHDBNXS7iFJyMNz=D%WV->baE})sM7*EpA*J7>0Wx8y-;Ab3N)OjjHu{ybc8$h
zS_RO18U^K=aafUfj{~`t=IU-JSPUxj8Led0!r!)NWoCY*!dg81s?oCN9$)GC+mErM
z&+<6U`6!s<!%)NmCb{kWo$K>hY=`eu_V>6EzPA*lJ@e0PR303L@4~k^Z@!A^cIg>D
z)ABe#dq{tBxkpsoLry_U!*gdPwqcU2dvGY2v#eOp8Jd>ul}NVEp9%r>H9~-PO0$3|
z<y+i91Mz3BITQsJ3*1yNb-Ge-)bJmEJXvp`_g&`%AJihV-STGb$}6vY99owz;gCm<
zCFS`L(nI1tt%e~?k8{g=UlQLx0SH)Hz_kQvRBb_NNTEzN<CU#3e$b|@^PiKzjzXhG
zYY#mZI|Us{uo~$Ev&+GOo$Wssv|L(S$8p3AY*_n0qiT+#!|WN3;iOL*3cRpzSqKyC
z-ypy)Lt|c#bEX+S1M;lf4^@+sfKt^RF`h9w<ccQNm};pVv}x~n9xH1bN{aoAV|~}q
zVaj1TRS}v)D5{5q+55*OC>m#2{PkyMSuZm{gSbO)RMQ`;a|!QtP}<h8YKUXjX%cLi
zJXiI50qyc{ye7ZJ5Ee_7FCMF{0cPzRnRjb!I@<g!do><Vk3P(yavb;1fZ<T5RWwtW
zX`u(tr3pWWU{+N?`&ZY`7<w_A*MKr5kWMMBQKPKI0Mqw?%2%OdM14--pBni#cxIqF
zwu4fMR7Xau>Kf=h*W*dq^T}~<mVl12OQS1#O;@ffpE9Js!0|*bS1z=L>wRh<B3cbx
zXT(g{V`eRckc)E6Db=)OT9`I}L-;kbS1BWUqB|n_ybASpLJ)Amv}_C;TpU}-F)Q?@
zXuU+}kuTRr-n#FoR>S{o)Vu76nMK5?2W?Jd9|~=1`#H6mEf&Mmp+EvFN4M{~83{d(
zSm*j%=h^Y`^OW`dL<Zx6mXx13<vE10GDQ_SpRrZZ!--KKl~Z{xRcGSDDxoc$KTV>B
z9NYT7Cr+IBPi}y*`PgHRz07UPS^>iR?fe}IVZ?|Lx(Aqz8CaTd{9uLaRE)3G_iVj)
zaQref6z<U)gAV=`9`+Lo_YsPDK>5}dK32oNGUdnf{^00I3+UDuVpv9`c^<FmHU!l}
z&?Zmicw|e9{_3l*{->hpd7g*i9_K)4+eeKdO!Boh)bn_CY{Pmd38w72e&KhJ0e%5)
zvaXHo7r1SW2S(j=2|7cXTF0w<jdxP3$gK7TJJ?wl(cvULyF);qgt9Os(0rl%{lU0a
zI|zc|_CU`qN4yEhqXXlwIX;}7|9Ry&*Kbr<`DpDgIK0J(s7r%tLFf149tY8WLSv`$
z0Ugs_n2Ocm04Jm?E1#<W6kyG!>k3c52L8{eJx9^u^gDBFbwI&dU_nji9-3$UU8PkH
z$5%tse+(M`3U`dbvENqS6WdbkXk-Yo-w2&1>Oh@1>WXdLfsO(HLJ#6#Y`TtPwQ=BJ
zu0GE#E1=W1gJ&F!Z!hS{@Z5O<ZdbT5d7`jDgCm#sLbF=-HdzG+4xvu1@I4yF7SsR*
zGNd-e_LfqC7fJa1@!Nys?DbG*Tm4HGm|5Q`({&gL;gM+zddP|S$Dld?ScNsa>C5Pm
zQ|(4lQiTdFgmPU$u!DjX7aJc|1B5xp$3bf`z1@YseMW<hd!k3Yn-G?K=Zj|Uujoiv
zR&Wo@cis+VW=vDI=#w`(N532y(PqSIe`$FhbL2a8qr`Jx>1`_64V9af!?7zt3#cfx
zMxG5AYP~Gsg@R<zE>g!5f?%sVmhdiW$0iWgUqC~>$P#4e(4muwgq=sw1S)u5HsB{g
zYf5SwRZ2>Ve&_I^*IB{1;tDqi(P-6;W9y@eMqWT4uc~HXb&Q|`rB3u(S2a&>>026f
zjE4+bCkWmlt?Bl5y~^yv`0OWnKAmCFoEk$hy1?OKkIJM8L2@L|hfvU%Yjh}l#&vZE
zIA^?>bvjH;b(;X%^UqE__0%Gv2p#$_GEba`n|v95`st@@^+pZ+!8cpCU-&(uKt*Ru
zw8G&~A**u+&ucC_;RDGY-gRB?TJ0ccYlGVHjOWZYXG;jsE?6g=G-=YLplHsmd&Bd|
z;=6=0c_sJVamO78tYg)&wuU?585DdFDtS>(=f)&p)~-{+`?k1}Nd|JdzL-_-2XaDf
ziGv{=#mY0@nICF8@A%$pD+#O34NINPmB|yVf)8U>gbwV~VJ9Posa8p6Cx!_eL_W!n
z^1)nK-Igh!BVMt9ca=^b%M7ptOJpRgBN767LC-^(XV&frbzVT{<HHMqcO+eF=&YVK
z6l|JbRVX+dVL$O@vs2K;$HEeLJ=au(I~)<Jb?eUC{awUJY?J03@c1A{$9FC^B3tb<
zUAr(WeGLTN9Z)GI<vTh}e;~5=wP*QDqpV}F9>^*g$Kt^KXs{Hh5=ur2@OR|Nm*3(z
zb$Yk37XNrnMRho)!kZ~u;+enN+kN<$bLcA_45M96fJy0SdG_2wLBX3$jE)iADS~6r
zaA#&^=@+{^>HCX|4`qREPGKZV)8OwMIp&)Hh77d8oWfTy278YgU`G3p-YEP7>xA`i
zR<xAnrk2(Yo^6Z8@r+-c+xSQoD-RqqSkddF^QQ&Rr6*tpn7nE2y#7&xe`wjjfF6Fo
zbyW>!vDRPOqrMHO69hw&y8F86XP$Yc6^~gBY-rsc^%b`w`=Q}k4gV2K(21?B&X@+?
z$4Xt}(MKPh#dPR-o*~$Rp-wb_KQJwQfYB@g6;AxLRf}~hOvksug5Xou`xam894k(B
zuF+sMcs&Ym>@a~RXg9|0!y0<O-iHoEogH|?e>aeP!6Hm|I9hS(V9VML#u@_pGf;#i
z!gTs{q}OW7lqpAok*;SNcy<QN``Njv*?1nS>TOGqMn`hN$E=JCqGKx-p1XYt^DuqZ
z)*DuNgd^2Y%1E-(hv5NSx5un|p%cYQCmJFNK!dAUTY?@sR04WVRhfMVpT)|lWldF?
zYoZR=h@ojr*TArk4=a<FuXFJ(vvcrGu>2A0Y4l&?E3U8okcqrC;!8!x_c6M}PTh%A
zV&4h(Qv`H8QoJDg;d?Zal%uf6vLa7BFVAgcW~ReoNG9gROfSA<V1H(Y$~cw=K{5bE
zaA5`_I*ywfJ$y=&=<c66qkB$CithJOT=b}q!mz(m4I?Ix&WTbl2`ey*2ZWGH_f|zT
z?zTFz=ijc28TMK|=kO_ZXa5I#MRmRK{)+H*xg6OA9UtC0Kf<8d=3>{qZE?}gxfQvF
zuXE5@p-tS$h6}9@BvhOL#&F)vv!SKZnxDJxzWYWxAuE|8dWG-cK58g99uHF?4#RYJ
zolC~6?%!yn7khW`-W2;?p8UYX_b$e_8vfAG%_-0MRTbCj6hXsbS5;j@(k&nW*2NlY
zKDd~e`j4i(UdtNBAZv3#%gh%YTtRQ3;eFJC1N(Mqnu&(*7zlF}8t_OHPYxA=GqN9<
z9_~$R4Sn2umF<R5HwYR_J@%aDp%_!Sz}r0MFc<wdGeLnEv%V<!t5FcNYQ&-k^^Gns
zmI*ZK(HYR5HG(JZEDGu5N+BIW;9t;*(zh&lXfW#zBFi$Y3dTFPfC=t)X!rZU!}<qh
z<)@;@F+_^my=o7IkAv2j#Wc0vGJ?*DE)yn9IEqe{15ZBrWT|IE58m`A0A3tVyq#%a
zh{YmrX$5m1$`VaAi>xT|tOBW%f|-RXOA8$xt(dsgw&jqWD!W*K3FDp9ZAz=`;GHd{
zFbgoLnus<Nv%1i~iSA&nstlk*uPf7LeZ~MKM!B8m=@V<&9}&>;z%X9R;QX0v{8P)#
z(4=wW3RmzWM~|P<BDw8t&6+1)-Malr|7g>;%YWOn?YyE*`z|XwcIo~>=dOLO?cBB3
zCH)7DDYtglXwf2zbA=m8?TYnu>r4mn4=W4nWeE28YNQ=_&xDtI>IOT$EOdP2WM}D4
zkgTi>tht~=B;y#oogPJ}!%>xq#U2$GR1-J!F6$33%L%n8Rxfj~H4R>F`-IyC4O{}|
z;=O@4W;wt?qxc<fH+tcP7wU!y#$^|2n4w*G+*{o0+=q8Wmu2hYiVuH<>Qqc$cG<Jf
zK6^Qw8fmjM-UG~Rr&Z^@l)M(4@g;Dd<!A;Cx1UPJk>9~305AT2g<MVt#w$XLtuG9r
zt9i*BKtP+#edxf_X1?h3T3<3wWq)%96n28rd80K}71J0EuSmMk(2eJLc$c(R1ot+*
zBI#8290;-6bl+;cqZ7hw2Qoaq{|Zy;&6uNFcLejglP6Dpsj}Cv%=uQHF)XG9(}7lh
z0N1oivdpe8zWCyR-(Suq5$pg#v=`EBif?Bu*Dt*A!rowCqo&idG~Ezt%N$a$bm`LT
zm|x7W;KDmv>e<i<DJ(X!;G~zc3bi`>?6cp&cc$E0%JMQnJs-w%tZy3L^D4h)dGlD&
z_^?tN%5$x@tu@58qUi<WJj+7Odgm~FuOGg>d{=5iu;iqjfn*l#yJDTnC}RP&m%!t1
zOdlOp|K++W#?&+2Pz(A+47E&EXMWJAXu-w~Jt)FqK~ZBA^NIdenS6{IJ@NU<oL|%D
zQUImdKLcK(VlP!q=gok3-+A9pzc@F?l@bvZc@&M4));Tzhzg~!h{#nDVd2Z|;bAac
z3O|C6-2PzZ7s86}x#P!+jUwwK23GO7PEb1of|>77ObZQ^TiAfa5EBJ&wF;)VpFxY}
zb4(J<VDG&D{`;Ti$CYEg;hbs$<|6OXr%#^(&vG?zllb6kfy!!_p&`ZJKJUR>7GHn;
z^(QfXnbw|D=-IYyn;t_72Xx<ii(g&)&}pI@309{i#(f3V8l}4Kqc&W}sz*?#`28ls
zib0nx%iAwBY(sE=?|ZpN1G55*#5<yebuY&&y$eo(`s00EYzc=iz4Q_V>vC(`AgFx`
zp@4NjZ)OUnlGUz3nmc#y$?$b?DoluVT|@_KsE-!<f`sY7u0hAb9BP_5y97E;dVcfG
zH@z_wXSuI)s$xIbm;5%{c^%ZFzhc_d+c3}bbF}i}{a_kMg{jvjp;L5<ue_kcSqo!)
z9t=nxMKd_xe{_IML6Qzw99)BSxyuR83He|Nei)9$_JH4j=Ylp1hdMg+I}g^Jpr)Ae
z0?H%jKmYm9VW@-iVN(2q-vonn5FI+jgeGqmmO;8ywI_pb>lwVL^_;vhukK9Y-P9I?
z%oBxm&I)t->8CG;qqqZ{IR)i|Wr9`>>rg&^MV@z{JRF11n$56YI*JaSbXZ~>tL}VP
z<a#B`H}1L2jx1gWZJ|qH;q(#OSAT&YhVN-vBB2ftKm+D-+@=Y$S`!UW6JtpE!87q8
z(+%c2fIt;`ku*{8O*A%4y!d8HN{Wd}z=TGxWCNfsAn|#Rm>-ud7ZXCIE-#ppPL~&W
z7S|dJpC`(JQUu12AI}aA6IuezaO%{leM&|0*a1gJEg2tXz$QLw)_dwrIPo~EYBym5
z%U&!KW{5gJ&~`)waz&WX#^8QOVJt7dG$uaGCd{@>^ypjV>DfTismeGQ=S+uKx^Cne
zX1uyVS(VqUYiZwg*IhfvmUS=J|M<s09!DM10#2^tP~J<8pLz4mHwQ8vIv#a=XhlD*
zVP<BdMve4$gZT<%E?m$27REPGkFMhRaLRVR=ke;=h9jl_@%k25XrQ0-ckM!pDg6v!
z=C0S!5YO;;PE{Ox{`u!uGvBbb(RsiWabJ2~2ldN(9><ty{hYXs`P+T^*THQ!V;rka
z4zgv~PL%VHk^UjfDStNBCt5I};nUB7ZArYV<G`;zmY9+^3L(pm?_aTZAKvzxmyA~v
zzwu5ozb1xD=zGC;KwD+hL|%e@O$>e5$$NtnMSX9<PQRk*O`0_6Yvv11>`W*JbsLAj
z%d_AecVPyK^9$Rk70pVOo@dD#RyzllBW%+J6!6X%=%msXWC5KZk!n8yIDw&Qk^UgT
z%)O|A{Qmpz_pJSQ7uX$GFO8>w?)gCvES0(u%W9ahBZuY1>d=8E>EXITAUJmkjTOgi
z>W>lEg-e-<Lm>HvaV-Iz+wiE|s>~CsAOeJOHgrvBolIEZ=zGAN&}UJwqSs`Ysx^Qa
z{>Ueuc;XdkvVMnIYz~DPp5wVBCnxJpF{`r&4ShBuYCPa$xD=T%p;grRJ&~LR)i~V3
z3|Im>J4V?-L*Bj?2w}7a(#N4W(QE80FmozQuew*zGPB+*DkHd`v&xePj6?oQ;rX<J
zF{e+T9*{<*Jl7~IE;RS;d2Ni@H!*}sbH%<cWu1r4l-GG4>mqg<a+?-CWt|ty;}Fn)
z;dLzm9i4s;c&5K-(V`AK&W?6y+H@YTyz<IdJ>z(8qb(4}_?CdqMzQDdif$LCLji;W
zx`~-O0&bXB^qMtrp5_a!r(W|uy)7&+*7pnAQQdjMc(5d?k<O`-oS<xoWqvFH9c4-n
zbt)OJHvY!9%*A{2SVH19;Pv0>(P?19LQuCY`R(;wDA=+Sv1iYoTA1g1&kn+pWsb@<
zJjbRXadRG-pi@M$r-F-XOjFs&<FITBf#U>VYSjk6bY%(0QzjQn6NUyhKU5(Zg7wj~
zZVrM3wSL7k=wxAObrvsP+|Y_EYfV54WE8B}kzqBKQD&M5pTG#9A^#C#7FE>n<o<FX
zXQG1F8borp8l2EnJQ>Kj!H$D*<70RamIjSlaQ-f9;m5Z_hYtEf%Z4y5R;+W-c;1Bf
z+pn23;#Nzz>Z+^u;zC7@$!fW19lMAnptC%aHS1kAUfA$rV~k~s<=he+DMYgI1ry|=
zGE<Yttj4^hd1n5~nIC;0h0Yesdu}-|<vltCBMwI^>STa+_h;`hi|<8;RS%xW_t$DS
zJpTCOOsm=g1oU~hn5Te#X~~P<dh4xEFb>O6p+%et!QE@)-D(S18m^LQRrL3J@4Xkz
zJV5BvmI@dS(V(Jfh46X0EL$CItmFAEv*VTZJcV*<N6CRp;k%-(75N*T{8O;5@qi%^
zDaeG0p<_CqLAIi(>H90<&+l+eXQt%!@jg$&@D%;s<ueF$VFxeE8|xujzgp+PO5@Iw
z*Qm+gR{dfL=qG4LUC<DRL_;uWcT>)U;6eIEo&vKZI2Oy`eBX)=Iq-tyVM!}za+Qh>
zyR&*n_w5^yzxTkI`3Da5cJJArqTCqSnvoG{=NPbPXNIze<+u+XirLd`c%wbNFq9@X
z%4KigYKNKUinG;ENX6P^?mys;z4+`&(PPG}FyU1f<F(85_JaG@<Id>x3}Zy}eLzSk
z@+J*uUj4B1i%Q+#33M{Fp<iKq-*`F}#291+FZcTHFphW+%!@i<ny?Kg(Cr5ORxqwE
z84VV#EwCJ;V2sgw=uIv2S{Q4!fb$P?oEAPtI{vh2)2_qD-DRE}<Opllthty;LSWJ<
zXJ%&VZPq7fq$%`jYo8YM%FcI-<5d}lj<u{gimfd1o-nNDJ~*a&972z^yGGY=IAv!B
ztnqr#uGuRxl}e4?MCe~!HxgMsSY~$Z+NBp?+2%agEN_^3q{wdy>grNsSACry?EUCa
z(qkVvz8M{s+J8cz*FeKR5?;a;1Q_iJ9fIUUG*AOQJ!tXXdFP#5JQIThqSql%dhYVN
z4U3o+aC)=>9_%|>brH1cOzT#!Cse^sJo|&5$)X%>_596kbT~W-uJ>?$baW=@!|2rf
z2R3y3NAD>7gBFK==dE@C8`QyY$mB7uIg^({$J0^I>z+v4Y&&r*F&&!v3w)Q!neRRW
zJXN!uRpS9=K(`02j9?5poi|eRT&qK2Jy}$5LP$I`XU?3Ex+m0uQ;;DpiX9`~W>MgM
zpw0=ybBX))*I$QXMw^f5u+j?jiNQ80>f;4pef8B-uyQiK_~MJFtm8GghR-40Shm_s
zv>>U;{Dk_o>#Tr|%CkOtoNi%7%0@HmBsP#3&<K4K+EB00Zu#;BO>#1_yXNHOcSP0N
z8t1jalwTQ!X{O@*Z*w73M@B|%>D8;>X0Hj9*qQpobJym5HTS+<efu^qekc}RRQRoQ
zD!1-P%Y@xj9`+?+Up)4(T)V>DKm5=d6EopgDh@>8c)U9F;Tym1QmxcZG=2`gIQjgf
zo3Hz%c-qB(4IVsLe<Ao`v4ZC|givY<zp#!4vd;eb=hhkX7T;yM@;c!AQ{TwTbDD;k
zukt`_%Z?U?Y2+JG5t*jj<a}r*9zeKJFDBb)kZ{CsIuAM;HJWd4kTg5LdE-^_-MSqP
z<eJqL2Nm9P6wvu`<(!qrjvdoZc<9^<!ufiPb6Nn+*hPK&_T5!od8$p<fpfU4nP016
zj`vWZ3<jjN;(6CxbInuukljUxYV>-Jk8CVHW_|H7Tf*bj72pV{FRx`yNkl;$A4T2h
zq7yH6BKQi>II<&f9W+&ovHj7oVZ-J^IQJF3M)u?WXpW|*lj2&0b5aO;(3LK~Lu_PW
zin0ChYw#r+GF?+sQ=8)3<Uj*H2M+t3sE4B<WW`b#W&_8XK_cimDrbTa0I!8W`x-jk
zw15unXmiXJUS{0~YZ!i4bREhyI_bWxZUG$v=pYE7dMYw>xG@`?^6_iE5x^e^=+B_B
z{3fG9=v13GZ>CR|L3mf@2XK0&qu?8q?wJU_+oia3+REE+zx@Hs67dMX>lh!cFvZsm
zu#9`SfB*jbJ<l(>4IwfD`*KR|ujp^&SNCQHJ6&J-K|9WY4pFvm*twYND_*en^S$K4
zHUY--{|8#~Lr`$^KYaLbGFm<kc1Ytrk4NXH4UVp2EFqoO$2q#b4OU(%k&bQ;S{(<K
zNGBvur6P_Fp`k&q^72p_0N#XiriXWk&xd(W#lj&YAG7m()v8s);7E5CzawlHVVKT9
zSYj=OaQ-A5(SC$>(+<R~(SYw-3NygA8v};?RjVRYU$hqesj~t)dd;<2EX=<2%gV-%
z)zF4F*U8?V;nJlG+yC;@!r!A~<BH}{gp7vmg4meXT=z)l=4hogj`$A;UVQb2jGM3j
zkG<)s%GP0!QVtYap2hTv5-m&v`*ngmrh8lqci0N7swpg5=NM*Zq=gT~$~={~W&>OO
zpA@Fzb@js!Kj@F9=RtnREg>BZ!+?5rk9_s*(Dd<_%rOQI*pqt7DNQ}o^V~KR{m?LE
zVGOUWu(N?L>;Ww9#ykRo9HaaXZtod%R+{6i;qTNtz3=N0y?gtXdKkGH0?dZy!>PxQ
zXyo+6_#j<=Xn_IqH9h4JyiE?ovJ+X+kE|N9RI4t5kIA*nur=Q|1k>-}sW#wyfN)N2
z`CSx%;R8TVB?JNeQtYc%0UaL~j+;%f1SM*k*+BOU?1aEaavwBoJ0ZN!hX(6wm^%K3
zC5>|~hjIYlNahcX$xzN_t<D=X;o1=#1#|`ohi_vFvwMBr6vjBWfaZ3G<?+{7yz1PK
z&ZYlSKxZd613KU)VD*ar;pY!b%W3Y+DWr6)U}$RnT+Ztu2<U(30m}*s!#eh)q@?Wg
z8rjQE2z_s18q&!>{q&QA9TW`ETCskbuYXkW9|%#!zA>0(#A|~W&f;F9fX?p}#>?xe
z9AT-$eBSPv#c|`tX$`k!HG{fM3u~TnDzaTTMxWZ^D4vfxMVI@Eq~+}#T4SJtB@tTa
zPUyfI1;PAUtYgs$>MeRPX5J!HbRXGTGc3Tr(cP%;HBWEpq5Uu(?T9Zid_^CI(6Yr_
zyz1TuA*v0pnU$5LFKv~H>dr@1UC$B@(f(lP(+Lp@JI`n1W(>5C&Ok@!3|e^NeK?gj
zhz`2#JjU&s3}_#X;`J@r0`);LYmJ)BTPR+;P73H~ObkM={}pW9qi0iV&)KVtG3n}W
zfBV~PRO+j}J*<qQN4v+?i&v3R(JCM1%3EnSbPuXs!Ao;Ev}3v6(y{jCO#bvgVabp~
z<M7QognHbTS0J1-LZQ%a#VyyG8H;7zQ%|{f|Jkdob5RjfI@X#$Z*lQ4P4KqA<i6ac
z%Wrh6gUY@=wW+P$K;!}Kd#f|Sx*^_IUg0}g2vD!M-;OOi`U=?DV8i0Z&Ws%8p1(0J
zd;S-<;B#?H*7D`8qI&lZxF?WawJ}exBP}g0Dl#%RKRY|z9u?(sH*41M5U%Jz$A;f$
zRPr9J-xxbH5|zzSjODXI*wR)Q>>X#t0|y=orbpDE#=>;@n01b<m4eph6liS{XoiJn
zqLDzuvmg*QH2E4lc(94FpGnU=^UP0h$aWg7Ul<;K_~GlYx?caNravP`j=UER;Kst#
ztmukpbX^Zk+Baw@A3!~l$vTBgZ46dJvo_|vw&WRtknS9{v{i66_?^GJV_fJ?%)`AA
z(|WbHrot-JsQ5drN{_**;Xz&i78m+Da4Pj5Z1@$>(McDDMy102D0Dg~c=H|q<daY8
z^Q-Gm;ZU22yq?uL538sDZ|_Xtt18a-e{NQikU-c$0)$0bMA=k!+0=@NQkNo#ySBAj
zwbftMYSq@Nt+v&_wJy}HZgs6_ErKA6iXb}(i0u0sw(RTuKhGo+Z^B)Zdy|kn^U29M
z_nbL%X1?c~IrGl@&O2Yj{5xP4SQkMUb3uS@jG18OK|miv;TP|{gSqL?hvUj_XkTmy
zm{2t%Am2?qlfdsH&);?%+PH(0CQW)7=CIc?kMNt~a2hszukOV2Q{LLZZ~QEsLX_uX
z$OY5?p@OpshQ2n^9`eVr=zLaMU}c`0(32`ZgZGYOY-v4JzSDDqCjHQq8fz0+IKF^s
zb#H>D#=V#&;StYx;o7D}9oqo#-^1YqK815$5B?^;;+p4_g<4lWFdtCJpi%mRfX?mu
z5Mb$IdO`X8GoWK6Y?dK)i4TPHPf?!^Lw))Ml}1!Ta#$Un%UT->W%=N}dyv~4qQ!uA
zpagV7!u!7lC!nM8FdQ1Yxim*(!<xPRd|@$0$`FF!e(%(&Q@zqck6RSuQ#gku`|$!T
zDrSD_ii?Y=9b~sCRl;7wAvmGSM(=LasiW|j$}Sa1%RiGi1@dW?1JfyH$2U5ucOPmO
zC>^W0;7eo2hVUGIXc#bF*7SOtAO8Mj=XQ>Apa5@?4C5Qfr8yjC=A|H}Ns2?2%gf*8
z`?!H~VF}>s-qML`Io>J$;v*;XosWKx1J_{j8#ZlP)8Xs+bG9x1dX^dE1?vWn_%0_l
zW<KP9xAV@M|8y>&bc2^ndPMiKiQdU<JS*QrK<`dXFdH>|hM-k7!a3%{-5}xocyMSS
zUCq60lvr&uG)}+1^Ugc3!~576&!8JZO99LRTj6&MI*+2*lfQNAR;O|!j6LDppPruX
zY}vBKfz`rL3@`Zd_^U={5AyRZQ?{BzSXN{}Bl2uyu2ws#^4X>~jUAXUxvrf|)Z?q-
z88(88Eh2uKXUhKewuad(t#eMMnPy!H=!{wetz|D-6wy?iCYNPe9j{r0fO`oK*oGRs
zd(ZG1F@ihMG4N9+&mlH;UR~5rmtc6(Zgft?L72p=U0eVmwK+QS8{xMbby5^NA}ZHK
zw4&jDIQw%@cRBOt&*v~63Xc&D_(qpX8$nzJmKl#yK*zYxauZY3yR>#FAHD`_I@4Ki
z>ok1(!_r2y&jQlx#;n5pmcsR;+^%YXMN$Upr`7QJ5r+=0eoTk$7k2#exuTglJ54zD
zzATubRgn_Tc?~Q4K`8(uK>q>rT$>IG<d+>FjnO%01a|*tMgAzhrIUFT3U&1<;5jjk
zKtBHrXv39181<=~EDMBl(+*;tL@Pdq=bn3xonrgVk6QY-Z{I%ij!^bu7%^f*z3e0j
z7v8W`zTwJDq|<?k*8>pFAEa>3MkhYF=8`mTqm~OFtJj7N8@AL}K9ZZJerJSM$c_}q
zjtkglcSlF(SuymuXxtHZ<VYik<q$y4_mErR4aLZ08;oCHu?@rHO|Lj5UcZ3?rv1P$
zq7~3F{;{#&6Uz>k96H?0_!7y%J4fN3+HilNGQtYK%YIOco|*5s3*a27{XnPS&;Pj^
zNnYbGSsvTDeb>!wWHd?u18DIp-!JZq#m785>lg&Z)oES3_GY6u=zuXj_hL*>cbYX)
z(@1vIN}%E4z>(Q{jQi<P`I<o|UXLT9^XnHZo^_H&^FHjO;}9->1K(3N!1!G9{Uu+^
zo+rZT<Mmk8n1Eg;gqUFs{P4g`xwMzhZz)cUgJpGwgQ;Ik1J{}bo*215adHXkB-8oH
z=a~UowSeOZ&@p%$1g&pjit7CN&wm~PfwI;MeD>LA{}BTEoAx<@26;3xHPctdo_+S&
z*HBi6!#rr-4*{-9mQ23V4`x3)^sZq%3UaK!S-)U<Rqkrbe_lfQ7YYJcxsc0qSue3Y
zVcQg_|F6XP5f{*L?Ft%n{Py|Lg{iXXG^S-2HOs7f(I)y2@>yOkbUc^`k(PxFsMoq+
zwaxsf=07;i%*6QEblms#GiT0x1j$uPKu70nJkp@RZ-jH3J+@(J%|;6o3hU6Ae-0t#
zWoQ!@V_LuUHeNW_w5VXG4WA2!PMta}U%Ys6z)N8El8fOS)pU?N{q)l>1w5e!BA|n<
zC)+YGk9Oc61+Qq`9*Pw#614fE8P}s-=Bc#_HklJ9-fg$tcJ5P8JvGw~!Na@P3Yo7p
z0Uhn7I9g3{d^{B^47e8o<q{LIf&TMZnb$WSci(;Y!x)G0AbXS87-9v^7nPN`H9>{I
zb)&y>CnUs|jqmdROqGA_{3KRz=omjNd_q06#(qu+<q$If4Z5pIBPgWtJ(@e0AF_bK
z3gkAT{S7nXpgMAjH|%JQUV&2WJ<AoYKtZ1t0gYik=B%cGW-3~L$rt4345#+bwmn!D
z&xQA%{%YXh&v6yT1ZN>ocERP#mv_Un@<)#GVNX39W$68O;H1Op)TxtGCY<|!Nc?5K
zo*si)?l5Y)SwXYmM1E}0aEJi4STqZyH)Q^1<DK!iwqx`-7Mf0V*mz{4n!>qt(nn-4
zHNA#TfocjL97LIWY(Mzu5Q?j*Ye)Jz_QP5F4mli0Uuz%sNSC!X(}#A?bWHJk#1Lp$
z6yw0eeGOKuU|kT-=W$<c2Mp`^lzFg2PS7x%;VVxVVwTQhw8~(>n91>GqXz$>p6CuI
zb#0gj3L@-?;`m{jgK|a%TNkl2pTlu%UBsCg7+8O?F5<$vh`%WqvQA<;sO#Fm?7fqT
z9KnAuNAAev+2PCp>k7Xnqqp9A>yH?Z?H)Vs9@Be`<vtr=4e_1rKt=ib+WpmCql3V-
zukfu5EV%}Ev6=8CbUuV*e!tE8fFVZ%_%88#LhU*H1FVL|d^8-ky&fsyoLL<)Vuayt
zJE-uSEC{9u5YDIByayA%rsCLl6W?OfV^vevt%>W{?==M13f4<CaqXJC2I{Tlyq+yD
z+P_|hztmKo&{i{Y2<sjy&rrvfs?lpI11I2h8iat3p2^-AGyGeOcRRoj4=Zr?c-w{d
z4V8Q<goAv4_Ye<wS>vDI0^fnH_JRWcs`04Yd`PkgOp4m(a0hChIgXnFW_hI>{{K_Z
zv@f$~ObDU=3yjEM6Yc(bO`Iz&8A|jBbWE~5ab^7kbLR#W!kVVG*k6oB3x#rD!Fa-_
zHa4mR9Sgw+j5B_Sv1!h38)R1F0L@l&E8GO1V#A1u@#m9RQoeU==%R6HJXg~zHK(MZ
znJK3^<Zn(lMGYa>Wb7-jgM<smS}`D<p}yjVdq3{8dC=`UW7pxnPF+ZkQ^zTUp8z_G
zjbv_3io<aQSob6%oma8^H5};$lLjo)jLMbf-4t?JA3|f&$J@EkT>qB)DcCZ=CxuT<
zyNM8ie=u*qh{^J~hEVIkO3c(nH0!1FNn00j7!JK6+q%fs^WL(=b_KQRR=9z$jB~uj
z3+Fz3vnzbtQMdXP&@oGZ5gb|1vfgCb;raO!Ob?o5^M(62&u*ja<Lq{I*AV=tGYv2@
zy&UM^yuP|=UVH7edC**!_HH4ud+xc%SU}oNU9|b0s_r#{Ip2Qs`E6r>@V6qE^8&?z
zWeVFGY{d9($OK9xgyZNuGtWVpEJdrppgI~txJ0c*MJHN?hN<m*uC)wB_`>KcGVNr4
zZQuxJp+fR#%b91(YV^^m`%Hxh`f(hA3YGhDN9)NB^pKm@J1U)){D9g@l*O|TFNA=A
zTITqo=%YrU4p3LRkZw-Su`d4bmBhvDD?iQ?A`z?>J1#D$E0B%15R~9CcP?yIwqg(#
z>V!yqN|>fCPY@jriHVK(mUevj&J3YYelIC1Ji}YLz3qeMB@x=8E2!nA_Jmp!R`e7$
zKmPdR{_wC&=W_~P2teEMGw$XXFm{wZ@W2CqhNHIu@TA-djrkaKlEuQgVm#OE@Zmlj
z;}}ccs^b=n|38UiKG`s~4GNgK-^gp!L_j{x_)q)6sflaW)-@nV2CN@zD{m+Ab<t=s
z8gy$K9gecVy5~Eja|Se|O#8!dq!~;a5SDIcIqbXm!V53_v+{Wh7cNYJh0*oYNK^Pt
zPfsthK2R#hjpT3CD@Hi9brGh8dkOVTU)DvedqS;?SZ~2;<QFWz)uJN3-$$|xOdIcI
z1%aGCI|5x3X6-{5hng%~cR_G3Z;v4V<--kNradB1dchtCW7E?Lv-t~P8FkD~PZ#X@
z!Nf!76vx??D;n^9_$HY1sv8I2es+qLw=K~o*j?Q;@%%)?C&KSw1@I)(!h1cSx@iVF
zANPi4(B<u72<Y1bofG8oG{iG$2N^%&(eR!JHFPu58F}Q9M|$EKY^b_9MP<0Ihfc)`
zLqG6LMu#iys-#2z9X!w0k7z@GRF!lZ(m4Su^ZEb-FTf`(#}{9GVNBWBYfg;?g>wp}
zY%E~h@Lu#Hvl8(c+=+>KFpMsJmAu4adPW?CAeozWEZs|#@?BBw+k9(&P}^)Z-Q`Ea
zutCYQEZwZ^?DF1mUn!$^JDZLhJUcIJT)a?zEejaWRW^3bCmfqtRo4{HtmNOkxxwr=
zDOZX2-iG5&!W8T!B|VPY?PCYDD}#85J@j;5MiXsnTkgOA{=dV7Z<&wN8vJgU84jd2
zoF?qlQo&?8_o0U#`ptw16PBWZet=GdIR23)zFebIsD%6cHQq5_^lmg-?k8N^8;(wZ
zD{9Kj9Zu7XNr(O5)aRQVNHbTT%O1(HSx1S~W`;4O!DPD#_pCS492mxQ{U(L6@vkug
zzp3mvLuXn4_uhN&G|!V}&z?PzziCp=fLT)}n2j3zhcUJ3|NZZOyHR^=9bv)D{uiik
zR<JH&-4kkE#Cq$>E3dql#o#xTZ3;{`*9HPs(BGD-Ab>_cj_0xM!GI2jfWy%+)X!)|
zS$3L%)8YZoVG;!BJDCQ&opWV6Qq4vf|6O<8br;dOA-<pMm@J&B{w|EkJLpg_Cj9(1
zGoT}2V>r|Il@_jNw3W8~gyCD^xURVoc%N?Pb#ZSa-bo4zm@|1TtE_=FNEUxrC*WJp
zdqPW$bE}h11kN=b>=8&eq$KaX_ue(Ei@4w&+;Qopm;O4W1bjq>^WC?3$XaK?%J86%
zs5P=1?LX7`VDkexY*&q3_yoR4gAmZm?hnW7J%^rdGjBBoD?TV}7}*cfdFP$C9b*Db
zPpG$hnv|7Q#A(z@r&235k@x(~hI({VH00taCn+UqzPB{&zNW*58IwSV4%K3C8v=`*
z_SE3lMyQ3kz1wX*;{HyA*26ptp4xKz(TDk8@E?Xql!F<k_Pn4>Suki&xk;O^GQ~#6
zul6j9uXx;#a<=ey-18W`++NGy)Y?+}Vl`jz9{v~4c-pQ=0Nf^X4?jW-aL9PR*{J3}
zc*1>^Nzj^s<3<_asBgI0i10srV9>kPU_w|W$Oc0#h=TH+phXFV+HeH=!$6(g8$!bX
zq!-fgo$6d4LTwhNOx(#%2dkMy$K^uLG~pEMdH%Lz)klmNG28QaO>Cp1-k7&jFy%K6
z!{45PCO_aeB~aebLGdNyaJY_j76t*`4C@JWZdH%Nr-%7=(XS4}#TQ>}wA6vpgDJCl
zF3^#%i-I~k6rjC(9OutL8|iYMZ#y2rC~WOSOzmd0W@vZO`YHR9Pd<4FW8lNqiGeBd
zUZc}N4wGU)r%S1%Zhl4XA3AG|Lj~Jr!t-C&SgHCo@&2057VBRC_qbElQw#1)c>NyB
zn6_O5XM#a0I((-O-#m|@P8x<7SNo1t^G9&6%38=Ze{Fk3t4v_W4wo~|IOB74YCeH!
zV}rKpv}t*+@m_U=;wTCATKN#c8*aE^zh|79-iEwYK{`PDx!TWGO_!mjuNSt8x27{*
zmFvOd?a%Sx_N7A?YCUNI$O@H>d(K_W0JFUR=PPZ@=}}map9ixtcx#1VpO0<+=8~6}
z>*VHSL#vvNUg=Dj`8D0+E1e(q!{US*bZff(!+|htq3$W`RgXu$10{$~3ey0mP-{Oj
z?7-k0qMW8AP-TYWrO%QnONI9^(4_+(XL51Tj{9H^>=*jdd@bMwTu$-&KnXJuI*B`c
z@ZjJ;aqV$504CG98LbW2vBR-^qeqY4hKA`@8%OJk1n_J`!x_#kG<}6u$s9yuc3#C;
zRr|$xp)q~X40=(wLIK9O{;_JQg?5(Jns{^s)%piNv=Ri4Z5xLW1lk0Str(#YfEl$B
zuB_uRXcbGPtWXm15*Naj>HM_<mX|0I+l5Z>OPM&oA#|{YxyBPvXAa@MfB*a6<|Esu
zPah-1!r9%I7!p(?0u--r1AK`5f!lUG`T6IcAGXd_jDddIUWaR#li%n0JKWpWKL>d;
zz-&CIItcae{+}VhBJ3p2M8Yxl^r?d32O}_czBM~}tk56sJfm~=bO_Mx@%>x{0k8mL
z;MZc_=4yAU!n~apBOEsIJv)HVdHYtl^X@A>Xr3v6mOJYMJ0r0BiXY5=)CWe$_qY#X
z>&WnReROV5;W2#MOcdOsaCAbSj>JY{8DkQyrGMx&Gi_A+uAmblpyDdhSw%;x$rFWh
z)<>u>M^P^M-S2+)O?9pf0e?ErXS(cwW7{j3c5`*E8R%SmkHYeO3v`|Obi6?c=)7?-
zsak=?W&*d_(@l@7Y{<~;iVcbfAAIn7^!Rn>@ydZ_Y%N-~c{4sf;mane%|A>{ZMh^h
zwZ%3#B-_%mRlEPDrFH&Q+jbqUKc&a%<Ad?W3*!?bcw$0s2<ertR?Xi`kLe<~%CzI=
zhmU`Fd5_bQQ}D12^gu87(a%3mH%VjO^6*;&pd2*UKV0azx|EvV`6x#D?x>RJE#*Ia
zY?$E+03Q<<8!#@DfM?#eTvOx49%lB`GoX?AlG)HduLLlqk}++=lr82s-m%|$jabE<
zuwF0%IjtI~3Bowiv*1BF;*A+}U{xMEQmbRUs)*0)X=uclZ-agRp;-xc4dwN^4QVI7
zIp&419ZPtg0-7fW!v~#*$-%^nL>zRMEkb<=CHltlZ^z&M_O}l(M)xFioK+B3ufF=~
zJ0g(>e`&(!MIUIb8e`sdqh-DR`s=5mUJ9!I_m{3chH>aGaND*gs0=`TG|(Oo_nJ=m
z7_1P7c1O^45avaG9>Q!fgaXs{VJ9bt9?&w30vd+`GQj#NtnI`no_JyvwC5Y4sUHL(
zbRoP=@5a2%^U(g<XEloE!Xf-)eTCspt9S}n7}I48pE4aWAtY1fsHh)l!d-qJAQ+jp
zLX{K5iC|Ot`*KQk(hKHXThDXo0|TsLs%=?Pc3soKYyGyA?W@rho{J`)7sR*CD5X62
z)$}&r12k?+J2WXoQ}JV+Ojb27KmYm9e*;BG54MFUpfmj84}Yk32Uu0}W6wjIxx#k|
zbxdgk+D6d&I09j<c#liHj_$xmDev>oKQ}@+d(+rJ;s=SsIs+<^n|)<{{DjGqCtP;b
zunWdtK4I+m%gz`({_;-P?tI?Z2^Wqy=YqeDI%nKVBSw$?*w^`XKdxKa;4OQB?EbK>
z%QW*P`NiD=r3+2Dsgdmq9Vq^B$M^0ZVfIDikt*vLI4(|=cK{Wuu^6l?`o!^>V!q1-
zX&#*u7;eCh1}^wj9-sG}i53+WKog$wzw!fqHc;t}vWIzoX_}4$?fEpjU+d!u+<f!R
zhA+pUGeEQP`th-<z6aibzu-rWLV?vrqEY$Fs;3y-ndsPS&zSZ(z`E9Z<b%t3;8?a%
zZp&shb%D=Rj9>}ieK3uB>p#J=4)%O+@i4Z!2egwhwC-VJuQmd-$YXh3c49Ig5X4%+
zKgUiuy_&#j6QQLu*@7^?q^9!+ZS8+}O{*b<@0qY#+d!cC7US3#(<{8~ctPic&-O$(
z%Fl*9t=$;VArQ2H&iK%-nL3MgCx=)t-yDC;XR*p{0VW(Epku+bNua?Wj%Q>urbXL~
zJhXx@oB~XTW~?v*BvIiorqA8X9cbHSK=IOn+i-lhj_aBT%a$$sF|T9CZi8Rz>RcD?
zizp0_FdbN>Z55*ptt_xt=MsL;wbw*jI4qrp_W4AeRBJK^p67Nfw9N~KB?PDK@k^?D
z2k{=1H%cvYDjFEz7vo2vq|VMQ)Ial}5P6JKLvr{oEj$@u+4MyyX+<I~+GZ7G47@AG
zf-Dl(sxN8Q+RIYg07s1)wI01n&v2}g)uP)*C`|FLk9hv(&MmEMqw#)*U7$tonI?s0
zgu(*{j0V&E@bM1<x|#E)svqT&jALi}NIDF=Q5IHX9KsT$Bg$sY3XgH<K~7F4h9BfO
zdAT{LuyWC8#JuI$UtC;dKBh6TaZYlRl#hbRB*rfOg7K)WpmqTjyg3aO&zfM)Z-{Yh
zV~cYObEpKl!MWS^aI?7UuDgEEG;IS3CSE^dBPZO~@k|eb$7KGtf)F%Oji4R+=9y=n
zS%7(WS0WE<Z@THGT^It9ZT*o<002MWNkl<Z1MQF-A5HhEr=FStGt!=(>D0w-Jmbb(
z)U!T-V0BVm%<GAoCwzO1X4P6L1QO8kJiB0ioPhDe9q@czc=z3RKMl|6-=M?m5d1Ho
za&+9|#*JG`9u(SYD?k|E0PXmb?2x0mCN0$HF`SxNE)4kgj;!hYK}$P&>C&a0SQo8b
zYcNq`9B?R9sQH{YapL_vhaD6QXfRKK)t=GnnjK;KhYpXfOp5o~YCPd2^C^sB?M{n@
zU@n7auEbgtQX3DGb8{M>Mf+R^lTH=mxP}iO{xIszp%`Y^8Fiz%{*zBW`7Y9P!+BP~
zX9Nr=WVyfn_S=rAUkhN>wvl;x@x>QYxUQ+dA(QNovBDoZ-TZde^4mmhGQG~j2SP76
z2fJa?q)BgZDquMCa)W;{z8}A4=biP}fHqo<wKJf-H|QYbbqWVV4w+y;2U1uB{;K2&
zol&L}h3z*6Od;4D_rdRds>*djIS1__wrtJ2X6t`W>&T&{usoVRWy+MF1!GkLKMv#B
zxrJwHIG!Je)-XupAk)Uwzs7oj+qD@`w;1sD9l?7aaz|Wk=D#+sZ61!=xNu##CVFqv
z@v+|AsZ%FYvGRjNVIBJ&G=!SNRPRuv@_FpPGX@_WcivY~ea~^616ide+~K}h(*&nv
z)odqe>Z^}6yYcFK{3Vax=DiRsTC?#&vpfcxaC3Zq*;qZl&&vLLA6l3H$OGM@P923>
z7(IY~WBbdAmt$;t#$ycnp<KrWnd_v(-vpKVwr#6Yj~sEgLOF0BbK(<<;&P*!G=cIY
zHx~Cg4^yN?L8Ft0ijh|cCb;>bp;m~3CQSpOftf#T+O)HSIk}<5K||{l2<YE&Y$Kl`
zHdra}!L0NhG(2+Qad$MPr;EY9ZxH8I{Qe*mMif|}>4opctdr?j<<(bT9m(MbY$$Qs
zJ6!+q+itt<H(R%EjYryr^a>wJ`jz8Sn}AM+laTg6H1H>(5jdW4_+e!u+4g)_KF`PR
zpq^nL=Z1ARh8#rUquv~5xqZ>W(VOLiCiYS^+>LN$Kd5LtW@BoUy(nu8%GwBVkD}~L
zA#{C=`@0PF#&!%XC>^{Q)*RNq#PEIT3RA@I;ZfX0p@^MV^lkCzqmMoVo+U6f?Stt-
z+u|NHTfTgGGma4sCa_^m%?aNFobO;B<u9R$8y3vD;f%v6qVT>I@!h9ZmfsS7Us-SR
zn}SfI&p!m$PUy_oLO!gA?7NBv@Q3I`IEc=tQPAMF#W&$Q@LvXj>xNKyu=50SySIU#
zn>*le?N&O9W5)#VEu7=s0Y4mOx~x#s^^DJP{HWJn$8>ea4dEeMYZ>5iPEefD*%$}&
zcw_R*d{c<w{bG8kXQT0+mw2QZ*3HKse>@!>tVRQlj?6>22hG@70G8%DsCV9h1K;1{
zTfGH43fUQjdF)$3@OTXG&lE<&zV)c58llsxBZQTnu#~7V?K!?Xr=de?C9SylE#UKx
z-|wNL>Rxo>7eZJ{L3#QkZ<o!VKmUAFs388)8jRmfSO++(SFd(3B;kCx4fr&OQ-g}a
zdLLF3ai}X|(T>S{<Bc~uPo6w^6HlfFmVzSMg)iV6{!7&DB`8+{>U=luiwo^!(`Mp!
z<%{9_TZnuop<^Ky&*{Z)zy0<<IC~4Vxv#(edK1icaIEq<k@!7z>eSZAM}NHQ1Mogi
zz_t7EI_xmC-!xdeWTX5?vCm!htZ&CXT!Li*%6|xT>38VV3%f$0Qh5zazISYUGk<*d
z*tyC3Zv&>=`><!vo-e_<<r2J;G59u&K;G^_-DT<mPWj7vpXcKKWPx{MbV{B9{|+^7
zsbuqP*JwL6hJ(nzzV_N{H}X5jcZB&wyJH`Gl01XF_Cfo@h3!W$<4>*U*XCR6S|)&T
zOMDpI_&B-Im@sSpMgt?Fy-o)o`OE7&aGhQK&T;Q*H_*MS!{G2Porbt~^&08sHI9Dr
zNkCH>IBsDj<c7l-H|D-H3mW5Yd?Z+Tm<j}IpJDHfw;kQ#B)fN=I?BB(ZBTg2!t_oa
z?%wH~jxvo3m=~X!ti}O0zHqu59~w8t_PFuUG+Z!+-__MfwmzPE8w&LaS#iM!!>sLZ
zZ);T2Q?dUaSONxc?~F*VVqq)4LfW3!LI*&FV>T|lN}qx4ssyj;At7oz%rRac!yVjk
zIBC{=M)<sNoEbWHOdOPzjbJy%!Zxi+CL(aoD(1)A0>RPb8x2oWA9#yXwr?BOk6{^#
zh3|=i4+3z`^&k$F^Y-<eddA^4zfI^ot?+zd?6j$eSZ7mcVSSCxW;Yr@ZZzb~HEy}(
z7QT<Q67Wr#fD5}}zHIWs{PQ=w2}j;St+d4NW0k{ea)GeyMrWYe=5IF2?J>IsyII(t
zj^$A-!Gtpr={_tQu#~6gSr?(<T)y8k4g{5c_#Jd8)1;ZSAgsF6)6>oUX8pqZ&V}t5
z2()f!rcFGIe{UJ=1>iid3*wsZ8-xSTJO`UZwc=fK%{ABY`dnD&ps~*9`zyQ8+Zt1N
zy@F?*L(I&15cXSPJK}*>P`n4YkXbyRD|AMc@3+T2*Sv4A7BJrl`>o)+%zb=E_|1S2
zW-PAQ)?j>||K*ooRv5#Jebou0aq<K0ef3iuZMSW3g1c)3cXv%fNML}F0KtR%;DcL`
zBzPd`U?Et7yA3YE-JJmjcbDOIzVp?&=goKjfcwLl>YD1BDyV+CpWd?e-fQVJb*u_E
zw@#`y4c6Rfh}xT7UD8g<62oLS$+CVTX}#@-gy+f&X|K2~d~KS0(w(HL3-<096ZA@-
zNl=MY4;o8%T81A8XQ0UtZjxPiMaS@yCc1IKXDvf+vI0fvNn!^Z6HmihdDZoFNFu|&
z#<lzQokW42RSZas;QH$dN`Ex}ktjsFR;(*1TEJPU;iPUmm7yzo`s$k{F3dV)UAED#
z|Jrr-w+X~4tnIc9xhZ77@=Tn4-vsi;$0vKe%<0I8l6*~+)&<!)<Sjn2%OR7*|HBn+
z>KSS*o<?VJfG)QceuR6hbj!Pk8Ut@W9Hb?`@p70LJ@hsBfpy}po%$lmTeaYQ-9c@v
zc#w6BN>)qH>DP*jXcY3*#^3r!!K%XE0J)}r$YdtbH%HtgLxK-#rM|_#Bc)+JQ&t6S
z5A0VQ3orTcs4|tsFb;N8siH`tA?HG;n-`hxQ5GB1JQ+5T(rZ@6NeostHAno8R?fI%
zx_*s{UUDlMZbJR|^zl0`Rv0hJ!cwP9q9wf>3ko{0CaijUD?iHg1)jixG>k-yPhwT@
z4L-e`sUOhVS!OjXi>>-QWSHWVRmo;ZhrkBOfmLo{@VP6vER^k+VB+$8q?Jl>PzGiS
z9%dn!BX5q#PmxxbK<gD@W~&>Ko!+o+Uy5G2;fhNyB;)`KO&BI*u%S+q!sYx>WH=~z
z=za-c;?4__W}QFcn{SV}*cj%=enS8)NqOD!>n41qDIxk)e^^5G#ljtDDgCP=@g0nz
z`cFdwO9+4mn?}>bF<ZojIDzr4whRfvLFmg&zDoODYPbY51OBj(VVFfv?a&7Oiu4A|
z*r4?Wj~l5}yFp=fD$`y!kPPBOVJTd<C)pW#JnRXbl2)hlrb8_sNk8^ftb+o*I$~Cr
zB|iigQm{9fJRVMYKAc7DWPL+g&JdNi66Jo;X!gSi<r8)lb6^6vFnJcU_C0coEfzE1
z>O_0hN&=`i^-;jq=H%g{+Ttq;AO&3#k<s(X-OLQ9(O85`#`>^W5z9r-R;u6#x6I$;
z;Nf!$vtyr`9URR}N6O~`#4BKt>Y??9R-c54tqrb?4D(gVHp|4oC7Fb8xEb~`ta!Hr
zh;-YooE+xn$YH|@csKeWgK^E{vaaDMy%s-|rVFF*$i|Ontj%NniFqQkhN<SJu-APw
zJm%(0(RZ9qNCh8+g-!<bIn=RarSzE7sx6F<*Q^U%N?+b)E3a-TIp#y@AzRBABYl98
z!8rsW(_*VDUEZSVZ2*(tjmgGaveN~<8D{vHBRyw0o)X91Y%Mb6`r|!&M~gFDP=}|#
zpt89YX?KV!A*3tlcya&xRmiu(BIsc`P2j{_+|f0s|IiG~R!>3YeaJd>x4|0$RN-0r
zE2;~rJNU(1hX2ab3vY&+ISth}I`Rq0)h>chl3StM7mRsePTG&@Hv^;WpLVoko?X4R
zHERBREkiZ&B$?)tCzt92&llym!Id}6(|ZOT-ee)Yg>Mzk({f4~<l6^M4d*O7QeI}Q
z&d^Tcrd@tEH!eh0v2}@YjRbx{Ga?fGj&gpa2ZoUsp7PUMMEWb%x0l8fB;mOd)8*AM
zv`30Aic#c(EhMM?;oZ?0YAE#UG(eA@6?T7Rq!ebwI=R(pzY^SzSf-kD_;RKr-O<Vu
z=cvE_N+XE6qQ=a|hcWmh+Hu6&nCIHKl+sc$EZjc+Tbd}@&Hxe3wJGe;bR~_hl&b?(
z7U71^`0-n-V2t)4R7Uh%-<NslL+=Q-)1P|`Cdk9fF(Wgph%Te~>4n5zGqF(wkD$5m
z&79C+;dlB`88t-UyM+RTYt0K!6ZKbx9njtP+hW4~nHDk&SC}5$(crI4eF#;~sy@A;
zW6~t56=NvmP6*T)MSWHi*6o7UPS|B~8Mr{XJByKPaEKIc^PZ+Tn@zrSS5jn>z-D$Q
zZc<Ao6Fc<jXsHx7>!CpkFr)#D-O^UK6&IC~LSJRi>~67Ad$v11IwBtp`p3>50%B(i
zBBost-Xr2}fi*%a!uK1=f|fG28N6VpM|CAXr=)iZD`Z;kuCd#+Fc;@OUSjUI&0=sL
zXz1{eAE$pGBYk|FLe|<SOPk=e!qbI#dB_#9fT;LwDasXSapiH|KR;)t7)UzCj<on4
z!+g-XHM3Ew-{Jp=&_rz5gbVFfiBr1wTt@O~?eK0rmwKN+L4p_?;c*#Ka|ZdT(6KpB
zQw~w<axD;`SR<cA;>FBm=OD+r_?F-Tn?)bcOll6<xW>2?5W`-PO458pf@QwaIWq4=
z9>+T;Wf**PYzwbLxKl{blxt+9h3s+bXgOOd60T6>fW*?F61e2Q9jw;-6+6;p&vO$W
z1{%taf{{D#A^Q5a1XA9YOpJ^n3Uml%@Z|S(Ttp;nEpIW?OzM6#2%2Fi%J%cVE~)}+
z?`IMlc;shOG-x$N9p2dYS>l(Ta>MhCOY(%wi8-{^EPV9O$LTL@`hw^`HX$1OqREGJ
zVt2PulG$<HXuQzcX_E9!pqk|lJXu(2V*A;+(nrdd)8z0)li8C^wxpquc~bnWV(H)p
zdcHcB%vgRHobDq5X&XyEo@%>T;d&9)XD2$2FY=Kb-Rbqyn*r{n!T3>*WF>Y`+cH&L
z{JJNnUoV0!%!OoZ;D@byL8eMac!k|(%`{?;%O_N$ZJ2J~P>ZLi@L5E?0vFhnxYB<`
zZR&W?z|Px`@O*GBWhvz~bx0#)IM!vMtYv=Bye1oEp~_P`mBx`y425#VFWSL)!G#HS
z{cqaQTKQ;EAuKeU?>B|g!@DGNk5qEZ+gi7;LHW3HD|y+%U3Hjq4=K;N#-!-lT=908
zSqL_63B&-Y+20o3@27b`p=<CyF`0J~ph=@=D*UmM*3-I=>hm!wa|H$fBzQ_Gd<}lM
zhCQq%{YZ1FhI>P?Q9LD@e1B5)X3<XX*w4w5kKC7ndN}DDR~QyQ-$>A1cnIw%N-4eY
zju08wYV4j{4shgIT;C#U5ovkEJT`{<D9Lu*jIK0Nu_2dT!gn>xhwT|G_)%T<;XqWY
zw?gxSr<do?kLJQav@+dxk2SHwe>Z5xnb%AycupI#7i<Y+Y3>rcf62=B=R`jR{RRkM
zx#z@76>Ly(p--$b2KZew>qgSu+E+OU587Ai&m-j!heWQscO+@OwuiSR3Jj1epSiMu
zY9o|IqwLa_>L5l`at3tSqwPIrY{SP)9s{k@8jn4)R@R0!X!^mv<(@l6Lv`7aqE5gY
zr$N~kpRGJ*Var>)$qH+1l{_8N-mqM994O64BIM=5`iUN*NQ*Bzl}Ii>JF`8g)Dvm<
zw&)YU>K5c&!CMo;$rR!?r4Aw=UXXNuvipiQ2@a6*)V^6Axek14IE~?I)=W&-S(I^5
zS@Jf}6MoZESz`%&q7-s)D_#(=njF2(d(lpWPDS|)VdCGPLs}w;`lCij>f*!hTax~Y
z^65bNJ!Vy(k(*s$AQ{)PP4mKJsCL#t2YnekPdNBqmsEy^!v32U`ZKvd$2K|2*a*t6
zL?_4Hb7dGuGLEJ>>IbbkEpf&w_eYh~iASq+wDMzonAioc2STI$BT2qSc}AI^(BPxm
zXgFzzmUNd^thHoKZcwT0aGob#No3>PM81r=kiq^y4RiX9osDGb)~wADmdjjz^}0Q2
zj12D!zcTt4!zy?s_NR6a9w<JT-7hVt#kFQ;QCjlFH^bkNN1FT=c;r(W8Y7@sYAnqd
z$KB1W>8H5OKRg`(k_kD@K;1F-zK8VUhN=gsEcw`Hp#i}sUM`&Ph=_?${v7$%sCFI=
zPoPsm=k>m@mQn46LH{b3up@m@P1;vVB0{2O0iG+`NRrU=#!qd(?jNj7t{+=#89M*y
zAFZZR;0_tu=7Bz*7sN-3ybl(UWKJJ^cZ-=Kz#n8;#|9nikfvf@aB>$fe(|zR{{)M9
z>EOAd_{&Adw{4DgLnzG(Zib61ai&hZ>@f}c8d13G%PH&2B>1efQWUhb2V~-%pIgn^
zQ`}|{!Ei@vL(lbZSV7`OPXF~J{_i&vQ6MIFX8Tws@#&^h9OzLY<XJ>q(iSCMVJ=z$
z%s@SyGBN&ggO;-4YrBg<&%>yXSH0qf^I4uAIFqV}sdIc9yhf?^4DDZgFLh`VJ6GHV
ze<!Pib=Owf?20LirK1nH`!x}#-hF#WvjYENgHu5^{Xv5$SldEBnjW1czGzR)pOWA_
zN%@yh>-X&Bk9TPa@#7}=SBdfQ_-Z0)><*d~30P6Lr3UrJqx5D{wGZ-Sx@L$aoj1iv
z$6AsI@FIvM1Z&C2UjKW4{r9STNUeqq=U0+ebic2-V&G|M;)O8;($&%_oF;5MVZ6_;
z8W`%!x!6Qkp?8D^&_Z5K`ERso2ibNy)SgHOyk$~J#h?L);i5Z*)pU>9LFf88@3{D6
zxMA$UZ&LewD<3R_DamFUj+!~E7eGC$`pqmWpE{N+1W^>Yc`2BL+~)b5Ae{<*s+y48
z7s(kZK58RN*nKKEl6xW;-gB}ozUxPQtItdaT>FGJ_o2HRNC7mpZt>Sm>E`IpB}XdP
zx0a#I&|TrE#56$BtM&0={S5>C!*bb=gK1RD-OCt-HnxMxaaebx|Js26wGDx9Ku=l7
z3WeTf)DUYZUY!q->PcJF5@H=oaNSVlkXS)Jy3XFTs{Z=*hvrfyMgenIl2v-vOi`Hg
zYX9AZjH~z2SFr!alT({DvyDm)@q}-iuT*|Ro{IE3GY;5o5B7#{)Y_Vgg6f0`;2os2
z>kTP6bnfLRB(JIu)ZB!FN~g=W__b}|To6NflKuyL^5#x<Z*N5O=DW*JaE*{R0hh8e
zNK!-%<f^xLhOme)FYb`W7`d<Mfq3ZP@q0nsIDmBG*6y;Ohm!-{1p<nN+k63iRKVVi
z57WS8WmpF~gU?6!87^3vqv)Fled!X1S}vg+1R%t`o&fz+L79cN-JH8$7}M^2o#0@&
ze1LL!o2-6AZE2}*h_9a?9)r|0K!U`egtH|C>5kVOw9N2zm#{z+qpv_|;ZTtOd++>w
zk=cr~$>@8kA+aIqK3i>X+y8B=jE<n04jTc=+~PBqfkh5><v-1PU-J%mOrf6JG3}E5
zElf~+(0WUA8hrK}O^sP1@ptHhHgR5p6F<`z%c`ZF<3i@utBVy|G<=zk+EW$$7_(BW
zKl>cJVb-#b+I(b-%HWGlgaTqWY%fDo?(hm{C?AY@R~Q8Qjw5dfc=GDt+Y5Oeu<e`t
zOHO~0<{ooO*otKJ5wm*0)p!JEn(5H%lD&02vmSDKgGt)ub&ni_Bvw%ufPH3+Pi_A>
zAmYonu}3yZ{ipL4QHC?;^PNTG@9kryj!sh;&;*P@$~TVDK|qB2u4LVg0EXRsJg$i}
z-}t(!pzUW!Kn6?d>W{Dtt*%u8=o~~aE`n~QSgSmL9jJb1-IV1lGzF>MlL+-fM!P(V
zvvDbeYy~{{2JT<C6Ev*Y-zheScn_qAX_pvcL_D{b!tnDB^==J9pIUCM8{D2DtIdvO
zZBD~5M`&<dkPd4E+>nuy?$Aj)Z*s{JM@tGht#)9sXX=Fo0fMF$x-$JI-V~LacbU%#
zg``$%g{l<)evU8yJjU0FJg}e##!dEJq%Nr_nk+DemvYUQqrV(d&XKe?tE42=4fDnB
zM5iVndI>6QAa<^Hx7VA~`H`I%Ax?@zG8g_i1(SF8WIDbWR-X${38^@+5h$kjM6Ec8
zc{n>Xb%|`SPa&qQF4BIo(&127C}k4Pbo(3Q)X^v*^Zf_9>o2j7m5S2@EkSA#Zlb!U
z@npJaVg%?HvLD={uCn|eF`@qBAbJ#t$)2fL`z0_&xY%uHvTKBLV2+T1YhqJD?n1I@
z<`}m5wdZ1P@4B>0%*QK7FvVPt;g>vk<a;N7!@;xnn#f$n2YQ$(Q;DIYQJ>h7nkXqL
zCD?n|!J)djKqY6N(jyd5<{JMbg9!!t5F}t;XU+i6awI>{l)US*Uxz5h7FO+~{HIkR
z3Ve{;az;9gyt~1wFaxl4r}FZ0x`;CO^W7P^zWa>%7$E+6vTa##m-sVj)F#I`L=Ss2
z`5VE+R>p702l)?8adBxO1WCK)A#<{~gY85ifbugdKfkpb(1>%~%ZbnwGpcjWK|Apm
zeAbp5=s9w4Qd33o_a&%f3%$g@KHVBSV0r>7*(fll2ez~eKnUc(cKe8ek_Ey4T9gsg
z%fTUjHMig?YPm*naWE|8@P4VX!~ay-_E@!+7mq+M*1`z9rQjht>jv)L-fog_53QD{
zJ=n~z4emfw|B+{WUiXZ3))zhKtZQ0lDt2=--V_jl?+m0v_2Oidc<_qB|MsYP5ny;|
zUe$5+a#hlW@-F^ibx=|c-;Yc={~Un*>3<yPkA|1gPtE%hs&=MImO2;e-CUyR#8*4I
zyJ-a>K|!S=vP7jX>5X9Gzs`&j_fr$;;2ixtuH7{m^-XidkCIGXq8vlnlB_7r&m53@
zBftFbRubM>vpX#ry4u7U<<;0U)(9z_Az7b3^$jFr(J894v~m4Gxm9X*QAUw$9~T|r
zTK9@Ir(^@8!EFcfK)KOiz|1Gz58%W>rU68l%s89SpF>`*{(uC@eJH8YwbXm8|8|}K
zK54-X{QcU{kViMQVFQp}`#hERUb34&k<YCOkl6A9-{S#HRQ79ovYZ6zp6&An;S}rS
zl1@Y&q)g!%5mzk@9raKuJ5ycJFqgp2+V5$0{k+ITm}j22q%$bB{;BO~3cXUp*(=-f
zvid8BneufmBWvRbzv+G?qEK?4ooCj%{>pf9%|02!beNj>W-qo4gqFMa%7$^znaA4&
z{*}`^cYa*3V13qMK_41j1PTT8I>B|ohFJ8uTnS@!;&H{<q~i&^8w5ZDVH04h-WkU-
zNAJ5G@3U+E<Bd}neJE7RzX?d=&BGhXp$y@HK@w;i&+aQ`@>l#BxfbrTA68uOe5X9)
zSLPpFexU(cx@2RefUq$3o^ZX~=w^zyRE+aOr*YdJQ+hP$$<FtShr`L?#%C#1lw$7+
zAN_39bM<G^J)n5~cx`NVDVzc}JM@qneeixNbnmg{-i(0R`Qo}}0%Oxjld8Bc!$Rzw
zt-XWOC{uhLKKkiZatIoaZcJI>oaN3ju<WtpcXLrcw8~x*%i6aEKO{VPWcI?+i3-O!
zRK;-#P?XUufnt}d;QV8KOsKI>)$Ln3%V%)G+f+s}c7PTc2xu})YiyJXi)tcZl(FMM
zML4>&dsnp->`kwLJj~Wtw(e59#6A;&*aHx9ObCS?cTBe7NVf(9%{Wk&G#W7|D%_bs
z{$)nv=CG+RvPRN$Hs#L16ZEcaxqPc%j8&?8T^py-=UcmE_=W10v}yO^nP;c<<GAcJ
z=1pU&ShBr{mmLz!z2XloP#YhZx#mgs3gO)hf<Cz~O6v|=_7?hvvCV5=trAO>0RzK3
z`?c^W!ls*j$vn@KjTh>96lv|O>Hf&8@DD{Jl0k{uqkk>;ETYBftBy3MQOIf|&{Rq2
zgjF>mqztH^7gYG(xFf0o(MHN#1Khr81P&$MAzbZs^{u6{{O35-6{&`4r&56+j*xde
zO{icR_=fx^aByAY5P(6RevI)RvBVPbsoqe>GD2WfEQJLy^cNVy3m4Mnj*dg9@3+xh
z?m$FMGgmDi&gyhrR=^2poe-QlM%<}N2C9ehF!T$XV`!Q;*b978_*AcA&I|UEdp}s|
z;>P0&3Z*lRj7?3omGG-2B!Dxl>;6YX62v@gjDE`7d|N&Rj8;pR15T~0F>SHNI;CGO
z%&4^m#}Yc#wCLTwRD(!|@CbFjj{$9=@r<`<vQ0AtiAbZ6cxQBt3>x4P+GS&1s*inn
zduvI#kIXb}?6VFf2v$kj7L;S*CFJ_ZUB6(##ZyUU73AE>+=YvEqC|LUHn)FYEHPSl
zyCzYpk^9`=AE?2D0PY=rw>%}tU^oHyH3lvPR}2M=V4l_dpH~h-N5y|37dBR$aU3e-
zFh7mGNtQcVY_KEe(gf*G;t#jIw%C(M@Xtjna!&5oE$Y)u1>sADERzraUP7)+mU{7a
zPj6rTG&=-m9Qdqn8F=2+E4ZY;4*_AzKrv#*o$3WK>8UMSg#6|y8$^rdlV*N$TzwuF
zm%Zvy^XsnMnhK~u^@xHi<qa#w))$YG|I?}D8=(Vp3IvhmJAqgXwcl9wl9Q7Osu1qm
zr9iXJeVK^ER<B|R!aXSO95u<Y{S|CBkj5h=JOiKkyuhGNHob=baZ&weT}vlGkdWEC
zW~sb$VY4jqy>`YoD%1YSU%D^8e_+MzMzChHe#e(!Mpl|FO-*p?i48FVFwE?q@%TM%
zz3Qa*D4TpyV<mv%?S$ucK^_a2L4Bo?SV>;xU&eTwH4u|I({%RNN~7=A*47KTJj6M@
zq<fO27a)bus4-SUL64~+C=f1D9a^ev>G&aLNR^l=BQdr2Kw97Rm0PcQh)XUCmeq}d
zsx4$BtLbLBh2YCUX?&~}s*tCwu*|IIiJUybzklIMH{bJ%*=-+BL%)Y>o<CYSCp$a;
ztg9g)zn<J2u~zl1`X4^-liVHCFcbQz^;qs5BbbujV?<FLR^vk8+HZPi0#GBoUZ|Z~
zzSFO=F>1?dBN6lXCC1QD|2{KwsB8`|DYxiV`jEAO+{&n++@{ppm1NSMus05iQ>kaI
z1mmu-wNnfM<e<WRJ>_b54>@Z{NG-57ryR#JpkL#VHugiARB)Y!o>-vq_P9?rn_S5r
zp)vJW<dQ#!z6}d#a$IR6i$DWL*IX<GUnFgGk2?!M0sEmg*|qoiv$erXWr=wb+Sld|
zY$S_m?>!9J%qvizbgOGq3}+D=QoquTXpne(@tsNsdss>ux^AZHx)<i005Tg2pNMtr
zd75~e{+?M;#*}Or5OUo2xxc#@1fmqB$yhrM+P@5wTf7{Ma#*`i$BAcVtPoaOI^61E
z6Q(;D&Qrh1X(Me5Z<32OnpGqM^^jw*tCG?3l`Z;JZWgNdVhZj)>#A|d98;NdHv=Y*
zEZD619kj9<tX<+uq|~xlmLJQw-Be2b-q5#q<C2rR=MWa2Xce@Ssz<D^Q~P7}Z-_4W
z2$n^eYtIn>^$M8&xj{03ioI<QUHb2VuSr&G>R4^#;EyoMaUNc$22;zT#VN0CZEvN!
zogJ9vKtb1Ai{t_Nh<*b9%*G+>sad8ogSzL;;-Ba0-E3VpK2czrJ?Hkav*Ut@7wJ~%
znu{o0hBfkWejp?p*5qgM^>TL-*nj;@OpA347)G00@@VoMEKI%u1gUlNRE~dXzDVQz
zD;%aqb+c&NeMv@WSVfzYmlth6@;!uK6tF(dfJ-;!5eB+kcmXLlj*LWuYUzfB)IP!{
zSGHz0*wE{xj7E~N#BW2NF;CVBenpE-HC9+7r%%`NcxAIEyk$s_osFNdvMvS2Skrfe
zXi}=|+<90vyM!;~j8-M?c+a^V_plyp_*o4?svH)spF}-3YW9PDmT=#lMq3;_swo-X
ziz2*eH<w^ixpFk09^^H!;ktf2O1xZRhm69f0a^{_7vx(3xooHxPzQ4$2-SVUZPe6g
z4amJmUrHKv|Mhy)@C14l$s3iM^~f#iS_MRY6dMd|0#t_)l+Bl&eMHZEaoicXq^Gl&
zSmz+pWt=ySTVc4Mu6#F3s$5>$8L?UF39&BfIFg;p?#pfKFx*fh<U}AOBe`KmElWn>
zAroVi_%NqFWgBOn-W=}90mV`A9(feTW#H9vI0G=s5lHk%O&8`R9K4hR($Y#e0T{Vz
za2<b6wGXUjM>ELzvAqowWKzc3jNH53$cL%6C%cP{29<mySFr??a=WORG2CPzc(fvR
z!>+cW!N|YDV2{V@B^alj;gqx$CMouU)BF>FIIDl>?%^?bzz+gv<ehJ>h7|T)5eFYR
zI2~RS6x2NU`avXq^F5JYv_g4qft!)amGF1vh?ACU(|ggi^|O6Q;vW6p(;m2cmP?DT
z(oHa7^B}kT*BJNOP|YzlF|d^kiByqi_B|bB<$>frFnjR)(`t%@n+*-6gDIO_L63ZZ
z3nwEeGFsx9h5AOAKb=I5Yq0xge$N~|H-v2E`c-Maj=|fvYaJc&vqaMfg27e4w-D!_
z(El0Q1LxzysAsxz_drXI!xKk|o$qmCwu_4;MzT2HyF<{h=6fK6)1`T$xkolA!h5X>
zHE~!UVsba}-p)HS3+?v?XQqcorW373f4C|4q^>YDssy7FVBl$IOl&6z@+n`gtdd~m
zY3l*pUA^|Ru?I4HB(iu(4;hIa8jrft^nK_EY%Y2RRxKryu%t0NdZ8OwZibmJ&A|Iu
zq1ex!R%I$)*o5HI&L91%rdP&Cc(^B(`FE+5nSKIY?24UM*-k|jX<4|H|7FNwEb3s4
zQ$Vgm_#RL^fig&YB{{Xw5&CQnGh>+!S*rJK?G-mwIwQiz2q{Gz!j(G&KRh6$F4bqd
zpvc%*!y{WwRm^0Z6zZyTR_?-jEkeJo?$vQ|uc`ZFzrN}9Xk6d%D?W>PNTYF-x)>r-
z<yokVQrE%3tjFZAW{NL$e_iYsm(JuO|GR9KGVwX_C2uMTrX)38?ovTGlZ4_Rm@bW9
zY~UO1D<pfcf2rBMIdA{c$!Uq~eEEJ#ji`exc>lU_4B2oqT)^vVbXqeb$&gVd0f(xO
zo>EX+?2pxEq`2U0X~}gT2BIvk+GhN7=>ga=axh@7F6tVOq7;xUvhWhN-H@@HE)}g^
z($n$e^EVc?s&X-Y<PZV|A8{OH`=sFqrkiH#!I$E~31RQVqiUA&YCt~GZ&=p`IF_(E
zp{y&QK?$u*sl~^hNJgGb9ed_6JwL@6EJ0*j!;p=L2^yeRZ#J>}k&gmXh$=c{;MS`p
zeO&nJNc~vQ`>r+4tFg9ev)hQ#1Ccus2EOV`Z`^03V^^^arIi-qpZy%j=i7bp9+G}>
zwU{jH3poi=A1$V%92@0E$bfc~@Fk|Kt*tG*ntPqj^!~;}xB|U6Gu!2%)c%I*>c(BD
zE-HMAKq`QkY4a|I>^ibGdROulVT^B(B`K1#u@58UruPZR4|b?AK3a?HB{$XV$uFe(
zx`FdLE)XBMyabAAw{=``5L6t519kBJK@Ruy{ROjq1JlvLbN8azY0=eqig2Z;onkj1
z;y|1z8#Nq(h>`FIed0S-StlI@?1H&?Hnf$dO(Cfjy3y%PV9Uop_*uj!ssAJh!HG?N
zRJ{SRrUGinc~KG>jP#-3j6z36k$OwIjThHH*B}7-c(N2PD{D9QCbT+A5Sy<*SuoGl
zxc(~VKR}g3v_I=My}crn*!mvx?BpECW@*9uMCsM{>bH#5la}Tz6ehdwbm+<{Z?rj?
zB7?qvT{9lNgx5xCp9WRb<#=|2G_96A_vC^Kr9nmFIk2H<3URe_m8<Q^*gYjomw}WB
z7v-=H#N>K=1fw+7JL>R35UwtZdQ3Y0$(=uR(seS;bTr7lx+^L%tZ5duA>^^F78zLb
z;7JnhZ`aFi0`ht1_BjcZwKC$;9;1YJ<40dg1dvx_7b0O&SW;IC;rnz_9>YnsW8(`F
z5r9(s3v05!+y}sjg?jczE-%6PVt)aY$Yan;-!anfF<<K>qdJs*!NQm`3vC0xd&-t>
zs{$`8bN63-*A18PBUEi&YRoj)0a0Bb--F7=&{OnnQrVLPq<Lbf`!FE;2vt+1HoBK_
zC&v4C`@<CeO}=k$vZf6XZ3B-%_2#b5Dy{WC@%Udwib#X-xkL+xR9QRbO`j7Drusyk
zDhMq3Tdm}7jYX3SgCDLyL3g{b^;w?&=mm>&wpy3`HjDw2Gz0{3j%<&hKi~tg1)@rH
zr^AscWt;kfnb|LCPSxc&ivRJV3Nigzq^#p|06%YZc({wzEC^ph@n8|=i=+EksXhYV
z2m3gCsyi4}2-e3vn+8dn!ZvhIUu5yTuXF){8jIX+wds`n(1V_Y%$U8ri7ZpMQfp0N
zS!AEib!;lm?5O+YoBiA<ZEC-<@45yVnP|4t!GoRK*~~b3yq1>PfRS?gHa`5*ty6XP
zSB*tQzUYi-&?nJBoAasEAsP03>s`Cn0_l6p7b`RE%<C>*Qkl3Me7Z6MPDE1-X(aIZ
zX6BRfp(%P9$^1C9XT1Xhs(3`t!=C@EB=+AAlZGwOt6*Rbu+UqL8A9CWc!$MzRS59V
z9tP0{rhnt0i}vq1vR#i(mT5Mp21S!pt?gK!&65*%St&Qo4X~xWsXlWlX9x)k?*o_1
z#34K6lx<k$o!iUwQI01%F0!GnpoQ~+gu-gs)Cya|BJ>v@3PpvtxR}E`jSJCBqdVcX
zUQy!rbQGxE8XNccV1D;q>mp#jitU4W7jmVM=-_pJAfmJ)<m%OnytZGz2=CBRVL_^S
z#}$@CAD?1{=l=y{GNE=8V=I4>+TWF^H$@DlAp~q)2RqA}-BW%Y!Mhm`zpcyfr3F2~
z{zw<Dl2yj>hHNP7>4}Ejla6P5M{eByH~wDk4L6RrP0?Bm%F*FY^s27p9hPf}(5fT3
z*0qJ15LkA$J~hG(gzOWC>G>@4rq#Re_MdinGgrP?xLMi*OV>Z$VO8bJZzT1w{74>h
zwlSS+EsKW{L3x)$G-$M+aUE@oSzVXb{@~}E^lvvO;Gf0~3?`2n6IsB&-#U~@K8+s}
zb(r5YZmiRMqd<Hg7W0+ljesmPpZniMzkk<U0=?8S4RJQ-s_g~g@z#qVLCB#0-~;)R
z@0Dv#-qv4yhr0Ead|WN}pLm_*lJftyWX7=3CuN&xy}d1Te|V1vuz|;RXDqsgcNY_u
z4Ri*x?sh$_#xx~zW*O9V*-XA@mb{%VH+}wb%rx6MGjmWsMRVQ@H`h#1nojQ0W@$XH
zgkk(VaY`#Y0^|AqK8v(r)fbcsgm}Sb*-VPwyiEL)e0c<!Egl=>svwe9bdcvh3;&;&
zk3xLNq|S@sioM2K7BO!4MlP&n|8#Gz#^cIaP`XO#h|>YIyKvg11X%~Q4Z~xqHpvE4
z<wtMHSmxvOI!kVPlI?S~R1BKA0{LMnzJYtpL?)(8jiaM!?Zn@;_T~~DH?2$*Dp-2z
z@@kyk>BWRRf5vanO?y>~qae{~qx)7U3{4hvAYy;kG)Z~p0E@mlqtv0mS^xa`^E$z*
z)j;cTnQ1r2TF26atI9teS!NSasbav+Yflw%rkI*FObk~^*gIX_6txp~y~{C4;RR=<
z)ZmLIw$w!E#y}uywz^oJW=%4kQ5u!O?Q{&!9a>r*{6&RbuuFM>oSw5+s>sY^HDz%s
zf|dCn)a$(~5})RNTN$E-xGoyaE?Q#EnDhA~ec)(;8@puv+1c3xuKta3fY<En>tFgC
zYI|h-aQrojFAx@k0CL~nszffX%4GS6FGTUJ&INHymA<^9Q%SS$V$#$3HWfd|lqflH
z1lDqob$M>H8$}rgvDM!=EOK_eEB=5wKw{FA<%;|m=($O~EG>diBxOW{dGN6VVaZB&
zMEBqy0Qb4^&ScSG01DdiG%>LX&6mgjOrC}hv4M+8%k7-}F}?W4YK+|$15bK3&rC)3
zm+JLup$UTO?WQWTk0u9PK}So$)Wp>Wvu@z(^ktUI>(m!Jiz(ApieB}cgkfac4+1rH
zyHc&sJfeTn^!p-Ye{b09b+2Q^4K{k7u<$cv$Y0C9eEE_u51(FQ93kZ2`s0__U%BsD
zsvL}Ln1AVtS;f*E>iV8{7C;BW@z1r=mqgumZe4V%vPIo(x>k%EeF*G9D3jRZVoIKv
zn7=ILKHcvWu!E6z-D%#KsZFaBc!61YLN~`7)kkBL#z?ozJKUM^G)1~MPA9VM^QZSy
z%ts$T(5EsG#GgEUop9>6S2ZPJ`Z6RgQF~U~H0(Xpsf!wnDPh$8x9J5EF!szEs}YmO
zV0M@lB^jAmSy|a2AW}LT?3@~QVOM9l@0s^xF)iV;OPlDhsh88KDKyb3N)1Rncl$$!
z6HxcA!w^5JZYDM>d$N8M)e0*aA6pmPYk!K0S7&sc%^LGs6`VhKIIv1^zuh0DjS;t_
z2GG(aMod*&YqE-pPKkZ#`~90Q4}fER{P?WdqW<CeKFPH|QRju#0zuD;=KP>wL0$01
zJTTxAezE{r(s-#xCFSAhP+C)O$946MR;0EBA-+&wcWh}7<n9+Jkdh~fk|$pU=Xerk
zrF2rNNWm|sES8YB9|!Jz-TjfZE~MYn6p1FSiB~v>Y0|?A#50oLt*KZO*PK;lxT@Yq
zmyk-Gm%OjYRV*=tIb@zo2?~x~%C%J55S&Z?VY9@VW<0Gx#1@MDeMhka)yczI(GwgN
z>V4ZHfas*4fgTO-VBh!Gn+G@>`X2j9gGCnxZd$2B>`?8e+-aI8=nmVd5+TLYqU|I>
zx=xrltKTTS*q4byyF57Aphi<14krtV5b;hZQAcy4q1TpLL_$gmPV~V{mvei%J5bq>
zvHj1=5egW6J14*o$mYSuAH*qz2j=&5jFT9b*71YRC%~w_W17)E;y>4wKM#KyYJ2PP
z*<(9SiUJ7=Fdi&8c4o>MlF?e5Ut+hOeVypGH`=$(fgMVaUL<&boY<@qjJY5V1S7<Q
zGyKo?Jb}n74NwO))8gCu&!_iP{U@j}V;ut7ogV2A*$<@!gWNi|rvA_)V+_`dObtEy
z^%jX;=+pp59<5B?OI2_}3aR5k<Pr)3=qCxA{WDOb-3WV{M9+(u4aG2sL-o&7tL1x-
zrtiy1rI!Gh*va?F;ZN$$4+hVa=Tvx|*&u+KZ=b{Kof3aG$5&sN|7jV3Kq{u?owmW5
z%$N23nTouIcfYhO29|2(o%?8sdG@1Y{Kl}26nnHkwiF8Agh@-7-u$`;4;B;NOL*TT
zPQfbJZAbNJqZiLs62xt5ENbwDx3CyI0ycK`$3T(;3%RPa5WpiY9C{mbZA!XrqhBo;
z@cK#z_bMO#y+_yrYnJ@HvA^u^&()L=56{(r5B5j0!-!J=G6Wb$<nxQL;~-p~TJmmO
zrX+(2U}pK@CenB!+mz4#AZ)ev!|eWsAOI&zo;05AObtod9yFc|=6k)>Cx8A=hara!
zRP_H;4_*e%lo6)@^~%TxA>;D^sQECQ2p^@8dJK-*dOHDBIF|zUv`g8>nF8fMVm@7V
z<~1q2NJ^>S1!%Wcowy+t76TDo&{-E<Td3D|!G>q;>KD$9@wbMq^nd%+{4w-&&y8fx
z7<rt*uG3nelIwu8bGYw-o)18!X<BKhQkTmg;Ymnk)-<!qli}~q^X1+x0Vp+ZSq;)?
z1p+kyNbEY9k3Wx8ZZUj;j*`KdgBdEf0v#eP!D4lM!IyUqW!al-q(>42oj+h~%OQXF
z_kuwxsE3<|JkK=RtwUTn^%sDurDh_p(IR*JsPADbR^H<U5~!m6mWEiiU{LeKblBH~
zRjrJcI)I&w<4unuR*#a9aCh~4#|+(fvS)D3B!EAV(HnmU9*`#F(<JsIsGDznmN80J
z)BC@J*MFa6qL3!Z`un{m%P<XgVSB0hX;r}mqV~aIwc~Rtu%<1g`-|p#eEm{ml!2T+
zw92v(;GS;Zj%%tdNO&AB--#Iq^I6$1aO+k&R*(j4ImuQY_pGzpWV1Y^(sWtGvZ*W>
z*tqimDtx?nmMn)6j>Rqz6O->{DVfTWAucjl?(<hgHH-CZ(5bh&e|exs>R{}aaTpd3
zyzBC?NJu{S9GYIu-r>~9hXDcD)^)hO*YCzt-mrmzLXmg|Dh*st3>;adz)cjO7Wkr;
z3wCCC(&WBBpF9^b4;gt*Ind&><}}eW33$NkC|XemtT8y>!=0%X9E6sOjMwRAd#p%F
z2}s=apDD~A;7B4+_HIiJE#~0`dmhw82tiiJ7NCjtDl3g)k=;Y{rgv$)+@(+=8nE@P
z*lXjpntTZUba043F6T<)B)Civ7&3BQ#I-6Ho%KfN45QnJ2f@)42cDwe%M5>NwjXQp
zL2P&$U+-cs3kF9q#`#SZ8!SxhVPgyXf8qVx2(Ug0oHFz-;uLTQX2+S+&zJsVJl+?o
zD+NMtta(&Fq&2h02pR%`)kun_x}~n8N<syIrN@(!yp--g1^b<(t~Bym0v;7dSNSmg
zNX7+6XusS29GHm|M~3q@y*$(M!CvF1GF{v|>Sk=lm^~bj3Jc$BEDNgJt1YwG1A1`I
zM;00&tX{7*Z~op!OjM}F#*ZfQ#K`&q=KjyoSw|aETLkEitN^sl&cWe)e0&TI3PP>e
zd%v-{X~oLS+}c`e$_luqnOdi8@!K0<XrXxNZXcrN(KX?|M;g#|qYy!UkKJ~X3!sk>
zaj(<-xUXML65jpVw7L)D^SM04!+ZC;6BfNxW~$T&ysdYRM0%z9jwYt2X%P{4c|U%1
zeE#x9U<j)VX!rn#(b8OixS}{%vlfLX@mGFZ&-H&8*hfT3ElP~OLWclB%Pl&8WaxNt
z0d-D+fbg1o*7-aG;yO3g!OMT-`*Wc@t^90sfPlu&y@hHAOGlgv7kg1Jiau`%1r+i^
z2^;~hQ{Mq-JH_bE<pw0H4kzn_hC&g;m{xGcU)k94e<viQ5po~LGPRpzIkk&bbgS)V
z^2s^1R61O35p6r(;k{0mw3?npviG+qMpQyp!;)xN1oK<mQRfrfsP}*{uC9UG#Jig$
zPV5bkzCP4tcbeanotTjkECjEN3fP!4gVG$Yu9{>s^Kx+s%^fNlbFtD0e<zgae&66;
z^gbFWNUZ~S>rGsiVpy@L<f+=<M(HOoppCn^csYVA8Z0vCvLElc<_;GXF2Z4D3Ixj6
zCok}9Jp$i{K_I5v>2YzU=x#WxwcYDE-yce1c;c*)t$Nx4+5RB%4r(yuG%Q|mquqQx
zk&|fTcQv)nYW*MGKY#WVlNjo*RUI&t>mN0}&ax+Dly@SUQlXa@czQe}J|GQux&bt*
zy%7MtG9BIg#D8`X{_B4*1%@$rS)qn<4Aag#1=TJ<fSQ|+_n(e|iv$1r21e-yES0y!
ze{bP`<@P^80VfHX5As6OY#+kkSr!QX<pKYnfAqgU{_h?5|NRbRo@3wob5h6AxzW<y
QKL9?;&q2?M6^w)a4}^FA;s5{u

literal 0
HcmV?d00001

diff --git a/public/partners/apisfirst.svg b/public/partners/apisfirst.svg
new file mode 100644
index 0000000..4635b50
--- /dev/null
+++ b/public/partners/apisfirst.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="200" zoomAndPan="magnify" viewBox="0 0 150 52.499999" height="70" preserveAspectRatio="xMidYMid meet" version="1.2"><defs><clipPath id="7e36e39dfc"><path d="M 14.160156 14.117188 L 133 14.117188 L 133 37 L 14.160156 37 Z M 14.160156 14.117188 "/></clipPath></defs><g id="44adc75107"><g clip-rule="nonzero" clip-path="url(#7e36e39dfc)"><g mask="url(#6a93f00c90)" transform="matrix(0.196801,0,0,0.195175,14.159779,14.116354)"><image width="604" xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAlwAAAB2CAIAAACS1tqeAAAABmJLR0QA/wD/AP+gvaeTAAAgAElEQVR4nO2935Ncx3Xn+T0n895b1T+ABkjKsvyy+7Tz7gfHhC0bpiiu7NjR6BdIECJlkhAFUaB+jXfC87iP9nokSiQBCqIokCJFQYQoyfLEzs6MJMOi5YmNjYnYv2BjH9a2vKSIJhr1497Mc84+VHejf3dVdd6q6sb9EGw06kdm3rx582SePD8IDQ0NdwCX5j/g2TkQi0nUMsuLzM8vzPk8c2zkXHnrVvcffr39i+7kAos+8u7/tuX1b7buF3DR7ydpXnbXAlQfubG1loaGCeOn3YCGhoYaubJ0HwQQk2BVJllWOJiVVVFVDO4t39y3BF9FZdr+OoM8JFU7ScRoh1oaGiZMIxQbGo4gr578Ixg0iPbFWkTKTqXVEUM3AgAYPHxprLb9RacGdoaQqMkg26GWhoYJ0wjFhoYjxeUT9zmhqgp5nrF30gvWr0XaMIiixFTFEcM0VWENDWPTCMWGhqPDlfl7pR+l5Z1ytdxDIimzo0wlAN4jptopKhrtacMM0AjFhoajwJWlUyRs0RwzbvQt3aO9m2A1bs4AG44gI5wrNDQ0zCYv+N/VnphTx946ymkXu4wd93BGkJ33kA0Nh5hmp9jQcLj5Vuv3EU1F8S6ZJTN72cQuQhGultoaGqbIJITi0keeFmIj2u3QgIhsF1MA2qyhWf+YcyCG9/bOd7+QtrXDMP/x5wCoDcDmxlOtSiUC2LF3zOxABDMAREYggzFFQLyr/vmVf1tjIzYw//HnbO36acOtXO0Ru/3DVv9au5D1XjIjIiJiJgCdN56aTMuPBi9kv4cIeOK+pwkfyjVqpoajyCSEInnvYgycEbBd+A1kyI5ycbt4ISJRdcyqKHKNIZmb1BgwUdSBTFpvfL0SEQMBsyZFABiRmTIIBAaLuiLrdfvFsQcvec/kwMxvvfSZWps0uHwzY+b1f9KgqQTY6o9BJw3k+KCXiACDEalZ5popdmRebJ2yqEbq+nU+yLyLpQ20EYwNR4/JqE/JtVohSBCFgdYWtDbQygzmRwCrr+8jVxyvPodlt3J+mupfVeO1/c2EiVGwwW96o1l8r184xxkzyJhd2Q3HHrjoiRggtbeuXaijPWYwg6oNemN1oTN473b37NVRouam0ZOHl2+1fh9i5Jn6tfeb7ViDGjiZR0ZDw4xQu1A5+clnNJIqAUi7G/C+iDLVneJMTuLeMYAYY4wwi2ZWFDmxUdDSYfHhS87b8kuJRaNj2lvmDVdCw7BcWTplJdQp9w/a8/uyq/WpGTUyseHIUb/2w4i9VOl8fNcpI4h46YGnk5d8ZCAiZg4h9kvpqArYeZM+Fs9cWnr4+Wm3rmF82DwVcHGqhnI2UI03NBwpJiAUmawWGzUieCdEjQHtUBAIQcp3VYWcp1DJ3APPLpx5dtrtahiZFxfu02De2hanGwKm8cdoOILUKxSXPvK0RFOpRSgykeNWEy5xJJgJqmUnqoIZMDt29pmlR5vd9qHh+aVTZqpM4d3etNuCzcfZDQ1HgZq3WewohKo2Z6YqCsEWP/qXKz+akAfC0YCZYIglvHfcrkKPFx98buX7jS/EIcALhUzbPZ7oJnFHLSkB5pEoIDiDdzbnaZh5Xmn9ATNgxOTIGICZGhmxgRggI4BAjIHf1tpmTAEbGFwSyJFTUwCVxEdWfjbFy6lZfUqMLK+veDWYlOwaDeo4OCZT6y4zw4nY/AONKnXWudz6XQRtVU7LyW3R2PPONmWOyadT1Diu3Z+poR4kQhXsAAU5IiMDwRTMDDMQjGhV1NgGobPu62MGhlnus0qilFOOC1+jODn5yWckgOBq1bFkeTvGRoczPplzVak+JyI7dvYZzmX5pS9Pu1ENO+NdFiVYd6LCY7AJ2P46McA+1dNNhCaf4iHFFKFPATAEIN4+bO4bgbbZL+84YG6/SH7Kw6DGnaIIXKahBrvTjZTBFDz3sa/UWsvRxjuGENRxLlLx/ENfm3aLGnaGwK18fsKVriq9tqGMlOtdRiMTDymm6z7JTCACr/0Z547qlM3H6lWfcgj1D3MiteA4q72io46paTdXMwuY/3gjF2eOFxZOkRLJpEWHMnQnZ0XVpAte4h1rabijsBkwaa7zNE7JkVPU7l+fZ3OqjQY1ASJmkYmUFEsfeXr5x40edYZguOjEbk0iYEU2n4FBzilQSXC0w+rZzCxUxWKbHEMMDNBQx4JrcXFXQyQyoMxB+ty4VzXMgFCsa6d41wPPwkCTcZgwNcXchxsNagKIWJW9mRXcuGrMFGyUoUazNVr0cQmduaAZVBQgMzMyEhLbYQ9nKp68QExX49vuFNt427dW/1r7nA2KVjJWa5a2DdOnrqUZEXtofyKqniBmoWJu0tikgZnNe2qXWp8zzS40Xqe7cRm/bVXweVGHhlFbVlI3j20DOcc9hE93r6O/z7fOd35RQ1sa7nBo6pvF+vQV5DhDzVY26/isUJ1mHNQjRozKnRwkCx9/5tYbE0rOtTHlVMMWXJ6H6hZSH9Jz4W9R1ys5zirqXVj5P9OW39AwOkfR+vSuhy6JQSY5vxGMqPXRr06wyiOOqpkAZEtnJqZEbSTirjD7fGExcZmF63Dl4SPbZ/t/f6HXSMSGhnqEIoHYoT9B90ExiEXfaFCTEpW8V5EmZ9708VnhOfGBYs96XiGEp/p/n7bkhobxmHSi7J2oZb4zsx3N1WqlleVNRIy0OKYQMjM0bqBTh+Ao6dMqC+w4V4sXes3RYMMMMXW5mF50veehS2pWxcmf8DGA+Y8203diVGNjKz8D0C6pfseBC68ZI3dPVs0esaFhEzVMdsQZa6eatB9uEIUGlzSP8WSYa+VigrUVCgNg8G7rlYEB++A/IwHKELCW7L4OvGuJxfkHvt55/Ys1VbHG9A3PZhYNwj7Z2LacfLCYNZqVhoatpBchZoOIiFOgyDOauNr2gFRBwiAB8HpwXAziOuwkHgzrb9pq9IewON+fzznPnGgtCxFRAwM6mQm0maZ3RqOEW2Wq0gRqkPM3fpqqwIaGI0Ni6bV09mJUdVOK1mTwQFw6/fTytcMUiqVfmnfVrR/8mzG++xuP/KVJZiSmWJjPYkC/Co5TrwzEqUrrf/pa/z98KXHJGyBq/BR3JW0+YZGKqLFKa2jYgcRCkY2VtTfBvDYbqaJmLHSobFAN8I5kXGnwz6+sJpK8++HnVaCmuXcr3WqulTIYrIgimqs/en1jKTUZXJ+l1fj1NjTsQOItBQGZTdMog31Re5LIxFgkO7jW8O1Xn3zne0/CEGJcaHMZUk55znHearIYHB1Y6Xz3zWm3oqFhFkkpP+45fdHEQFNVgRmJ2iGyQR1sEVPZFd68dsE7iGIup7Ry0cyBrPWxf5+wzIaGhoZZI+Wujpmh2p2S7nRAGQRapT9Uq51km7CVH3zx2CeeMaO5Fks6sRhVjQLZoevYTdz94ReRCZyRNwPUYGaqpmq6QYNNADMxE61lhyMyVTVTE7txrcaD1d0w2NT9t+5AXrnrfjOCkUWzSjQI1MgzZ84VTtnAEMhjbyczWbp84j5nICJPzEYwmJgF0SC2MUgYE3smz8QEZpCBDCJkRqIP966nas/kmXr2qKSqTiLvPaqQsszRKbJM9HAZbPhtyakPxM0ffOHE6ee8UcWIibqCmaD+MMrEE49c5kHvKmIMvsyQVcRMgEQFETOibOp/AwggJgBmxo6gRE61NIE/fuYi2IgMZMuvJggM+8K/+ISPYDEXDKKmCrPVP2owNVXpBg2aSi5Sxi/PfQhMm3I92UBxMRgwRCAQzBEIcPTIr/7DlkK+tfTHDGMmT0yDZSjZmvX01omNBgVi0LOb3rLVL4IYn/yHv9638d9d+mOBEREITGxmt6dRAmA72msR1nRYA92MgYkAeOce+PXWS7uydArmEC12xc85AzOTDIx2AYvKcxkMjl2FyroHfXhfOHnKGZMSG0tpoUBuBiJ2rEGJCY6sv/mi1FbTbhHBjLxTjeyIShHll+c+SKSAEeyRzt8csHkvHrvfMdPAU8xMB8MSYCYiJUPoRQ1pZjCDcua/074fgzGzOkAHI4aYGQR2DAZ7Pv3//jhJpVtIJhTvOXtR1DADWzSFN8T5j36l86M/nXZb9mdtTkrcbx4kBM9IaLRIWU71eH3Uwd2Pv4iopiZBNGMvpAxy2st6CMB+uuWohmr1M2vLPAJ85lgAB4DUgjvx4CUjA3T56ufHbmqmHLy2ItHA2YYAI9DqbyAmUi6chWRLPS48aJtz66De20IRIDZV5Ew7La0IpiCnSrlnhTLWPU23O5zeFufbxDoBasTOaLjBJTAHqkxz56EgJtONQnFnI+bVqVUBBhRELBqLLN+eivWVxQ9IpZYLXI4qhl9X20sLNze4x+RjrlQun/htZ21SRyVLoQVlqvDO4UZpgGCfAChaRt3spDP4vGt7IjMiNpWAl1r3kiMmeuTWuNvZUqRA7j0rdNVG3AZTFhGDYlb4MuzQS2NAYN/OAdVVoYjVG7Y2QzKxqvrcq9Q1F6XbKRoT663+9E3aBl78hyeTVC06sbeuXbjrzEUROJAkUkeQIYFFUP0snX0OyrFf+VbOfTGispvokR2MLhns67nlnZABYkYnzz5DpJ7Duj3w8LBhLvry//lVojbuj9xa7Y9hHtfi7rkdBxCDAJXlvuybZWoI2r+xOPQwtQpmy/2Du226JaPN0Zpemr9XgrqMw02BDjVqaPQ574X27wAeJaTo5XyShfBOFRGQQmUkvds3lzyTBxNp1O8ufIAdHNMDo/qnitHNKmBrb9Q014eb/X3Lb79ngWrbgKWLkQFgqnanG8myvFZTyYTudPW18tdXLzii3CdbHKiqzrZe+u7HXzz5yGUzBiuEwkq/W1ZlVdchdz/GECQEYnIK5zmIFCfPXBy1HGczoGDZA915qmbAp1tVmwwrEAzJog4Sso1D+qX5D1g0OAorMmRj/HxGo0QaurJ06sWFPyQrgAjLiu4JWw7SSbVm24pF1a6GW3Gge3BM/b5embt3pEIoqY9sIthqm4vSPIz3nL6oYjrtA9J11NiA1uk/r62G/TOMD0udWy9H5NMZA4uombY+/LVUBaZl8cHnQq/izJNZKBFiTHWeui9VkFCaxEVVJ4YTD11ceujZUQognWE/It1lFbhrJMKxGe52MSiViisqbO2c/KW5ey0qedbOKDKAQEP7735r7v0WwN4M3vXargedlFmilFKu6K13oxBI8PLcB15Z/MCQ35265cuOWLpQwFtItORidqrd2pbkoyJqwj1vtWpQbfZjkjGhJ6pqzAma6hxLiDx7kVBOnL6sZKqikOpmb6KJPDfQqyKAIveKoMGOfewZVln+8f7BlWzGPUB152lRp+QRrEktFwaX9p32vRqNPGlnNKWgmA0TdvjK0ikIWTSFZL2WK6dkjaiwrlLh2EGiXln4Q3h7bPn6fl8zg6VN0nJAVFFfnOQ012kA/KzoTge0NCfM3PS9GzXNib+6+iSI2+mi23hXr156DJYefRpZZCNijpVNSyKuU1YxVGTkWIUyt3R6/xTNltb4ODUK3VExYthmozIREtY7sGx6Yf79UYQd6Rh2pI739cy+snSKjOGM2HHXybQk4hpaSlgRgOHNAr04/4fTbc9YaH371wRCceljz0VNpjtNFdXaOCfjpcPgbO4Bqi3oZ+Y4lZpr0EaepZDr8w8+E/tseUUZJEqSDXESVC2baxuE4O76xNf3+TTNdhQm3XlRbmrAFMSiIVm9ZgYYm5NMY2+cmcftt565snQKykbqtbARt6G1oj1B1xlA0a7MnZp2c0ZjlyGZhgTPIjmGaD+R7vTkwnyScqKCLdaUryPx/TDh2m6xc5xK2TRjW0TMP3QJRmYUVrJy2qvv7XTLSFSwmRju+sSeB7Ez1rHDYpZSJo7QCckeFoOJBohlWoxXgqpi93X8QGsKVq7yTV4cs4FVQj0jB432YuvUtJszKySYL42IizQKunbuu45DKmOnrFWfC8G0tXTDQoQ8S6NGnqkUFkuPPk0QOEdxdkVKJdo358hU8Rsf/eq0m5Oa5ONh8ndSRSUqifbGFe+yc6wAbNSa9rx067IvPSgK7RqYoPj23GHUo6bnoELxvWeeJyCVpb5qRK+32E4jYlVJiFunZ9RacgABAwVqfVWEfZyAh2dDRJCpE70vIiqdfdfJvvncFM791hDniw2TpOx0qUXojz+ktdz1bIvNG6mT1sRMTMeDQOgbeSLFK4fyfDExB98pUsEIMc1dDyHChIiTxGkTtQjxszGH70NtB3WSzrfQAFCtyvxhOfbgJY1EZXvaDRmWmLc8qUb+jfv/cvu7NuuHipNi4iOL4VzwB7GrJOce7e0QR+3K/H0azGs7riSIbFA3BEIJ78DsXj9x37SbMxy1jZaDPoo6iPSTiBWnCuQWU7kBtrSu6Sbl9qTOjWKIO5sOjsGgjTbdLCjA0plnTRXG1cy4AO1LP6pmc9qpdj5oINJGJk5jWBEcw/G4ZurZ8TbvdDZxZek+UwVRuNk7WAMniBiQZ7vGrp4xfUyd5toHehbfe+Z5USsT7UQIaKkzaFeQuzTHYEqeDSdSa1DTD5B6JM1dD11S1U4v2XnGakTkqWLGzlmoZsiQbxhuliE7NqfM//3Hntv63ky5gG2DuT5FxvSpOuPbvxAz5zuY8rERFWydQ7NoGxA6ZacHjfJq+9S027IPyUzqdyz8IF82ooxRJtKdqgobrbz+RSa08jRCMao6Vq0t9kEapLaIRcaZp1SOCkQ0CFOdpLTxWDp70QCzbHa8L4bnhtmcY9lmxUvMsxBJf1d2Sy99+O5AasjgtvbCd5Y+ZNG8Hhon6Y1ov2Iy0e23duqL4U0wmGuzhj/Qo6gGc+mipxINFH3MMEtjYU9EojxTZpPbifUYdt79+ItKaQPSEoh6P9yULGnCfWtK7BATrcO2MDh91TovqXJOTP6HD//FpleJk/nN1AADO69AkkVbW2e2H9RtmOftbSYjzvwMOmAMA4FDdBrtCk5Nuy17wYz6lsXjP4rvPfO8moWYZhw7ZsfrK1INsnP+lzFQUBDCHz2TpLSaSBdKdQNBXDvrlckeTt05sl0tbd+RpQefMVWNidfgVZTcc577dpuLguYLl+eceUY6s+p1llUWYi9szkupwCzHPt21ZYmbfMgkIgBE3fJAXFn6oMTINRwR+8VWdmLO3T3nTrZ4qciWWn5+TN/KvdEQIcCmKOfbcmBOm0FixboKH/+rxBkl052CwLy6C3n76ueJqNhJWT8GBuqVyHzyk9l090Q0+YbrvWee1yDoVpRoPaVmBN5FAE5oOmN2TCqSbJsYojDT/LyLpjA1I9hqpE8zzTkWWfq9cNe8bj4yL0WrGU5UqWCd4eZNE1bVTWfbDLYM1c1uwkponuUkZGB+qDZYmaqaarC5QHPgRIdNq9WB0MqwNdXmbAlFharUZVUwvuBRmHN+32StQxWllmWyMeq505TBaObbIspJQ54MEwR42KLqCEMfzHKi5X7lEpksmYEgMkbuuJRQ5osQ09xJR4QWqSoJOY8br31u47snTn/NQCaaqYrPEu4Yrd3qbvYcjWqdqjq+97egdZjjbB55WxMDD6bCftX3brYiG88IMcYtxqdklJGvkGaIZktzfSqpUo4U8/jYO5vyIL4497sENgTMLROdsDLZGCXbGrbTYASS29e1qjQaGO4abGwL3u0oZL00u21mumb8DgbQ73Z9liyk8xbGfMzu/vCLMVKVSFYTIUbQRgtMU+reShUH1TufMZY+ksx1OuURL234mYiTDz6vhp5aKokIwMy6rmN1JRYdClVKmG2bY8URYLv5/aeWX3tqy7s3rn1p+doXSdRc5ilz6W75DTE1++/++H9df6WMUtxYCfOt3b5iMIAskR26QgaycE+JuFqveaCyuOPufLY2D1NgPouwzTclKBKZ9bljRUTXG1nO527+zRPvXN/ygXPdXz7efZPyjkpezd3kdrKHXcoAtW/nm3JLKXRtv7gexINsNYFGMvu7iAprI3Pb+FytkTxpqTHUFdlx3AVgJlz6XpbGC8c5VtXlq59ff4VCJflc2/kqRTSWqJSpykye2hAAD9rB3GtMTj74vKg5ppgskM0Ay6Wo3NTMB+4+82wlUlbx4AfsUZS4ArlMZOWNvVI7Lf/4yydOXzYLjqKkM1laKMuNXg5f/r9f2/crL+IPUkkhAgH2OP52qE8PpOGOTj2Ew5OHphb6K9xavC0UX1m6T3oSE0V0q3zplAnxiRvX9/jYY8v/1+UTv81Vq7R+hjSbJwLBMa8tqc/tN1RexB8k1K8a9NN4c69PRCACtU1F4woKMppLc+9VTSW6zdlg3v7Jn3mf5enSUQVPs+lsRQQP71Kc/C2dvXj8zMVo6pjKpBIxinrHgMe1f5ew2JFw7HKXIDGkqnkCmRMaKtnhjWvniSLI59uM78eHszF8MFLNOwROI18TP0+HbOOZH2sruwfeur7+ChG7dqJ7NO+4YmEdItkhzt/4byrILKO5ZIsUn+fDHxEllIgOBwowlIRxqj9x+nIkVUvTdCK0Y59sq2qIiSidSQVTFsywxRR+NvDAAX1uTjxy+fjZb4gM5H5iiQhAzTrMNlXXQCLKfX7wcoIoc3SE/g//5yG/cuPalzJHRZHuWc093GiL+rSWDrNmNwEMZOJQrZpY08mTXyy2/cmyxSJfakfWreFsiN2It3VXWg7ObVeZ7sb5/i/Jw7l0x4pMzk9FONHUheI4WzFHJsa9UCWxNmF2lW/ncasmlkwrsyJzZSJbnn4sM3KzlmHIDHDqR09nf8/pi+SIiJQoBOWMTbjbqTKfXqXlmBAl1FDy8KQywmYCjGjEIxBmUEJrN/bgQ2/PScnNjoe7vwOtbU0PsmtnkUtl4Z4nYhOlTa7YNlhRqCkT6eZAVMQuVXj6KEw8au9qkECJNKiesdXdZCJMPTwIxj5TLJxWKY7BzCxjNuff/uGfbXnrV1efvOuh55kp1fCf50KgsyYUQ5QTxUIM8p6HvzlYK693K9GaaaoBg4NmgwEiEqP2RNtgLsjBBZHuSukd1yERqyDekzOEaxe2v7uj62ItUCpnKVorbZTvmHUqADAzNRxQ3c0MpDtFnha1Cqc9qG8fEVr6bhHmI7GRtuO5lb8d7fIo5Q581LLUBP10JqCetZ4QGfsydTXGyAPs7g+/qIqYSHeqZuxktxmGAJNkqwZ2LmM6cfrPUxWYhHaRVZXSwJ1wo0Rc/3/tRVqbyZ1zqqrASpSVnqz0yhCjTxdaaAvOkcnuQiTpum7PQACUJOoLESijUaPY/9NrTw1GIhEd/ACYVWctY/MYzOIR/dg4dOZLgWXROp4+fevvnlj55ciFpLunhRvZhulc95cJ48pX/QPk0zrkjL5TzISrLJXdaZH5KOZ3U4UbgihTmijUCspdKbMXk3CsrPFEhIR+ArshaixkZFuiu60zsJJOMh3sGxoniYeOd0zqI+L8A1/vvP7FBCWOSAtYMVucfMXpSa9AnQpc+K4vvbjo4udv/dfxCzJL5a1FQojhxcV7z638PEmBo+HJKhUcsoDmqRhdKA7sThMpTRyxQN+5+rkd33376pMnH7zkyfVDmttTScHTznx0uFAomHhPXd9kOjRhYJluFfICGnX+E1/p/OBPh/xW542tvozj0QEA/HOSsqbMEfHJsLbLQ1a58PnOASQiYKacSIUWlnu2yBb0m4unPrNyfchvPY5hP7kPe/jh3AGMdgvT2p2KamX7SDvnxFEykwQirykDZB9xqqhkULLuTz6/+6cmtMhQVbM0gVZz76o+mJWQHX/g4onTlw9e5h1JUgXq8H4iSfUj/liLI1yWfa6zp2/cEJiJpPOeoxXVDE7w7cVTV5ZOpSq2YV9GG9aOQeBeSLOEcMymkD3jdBAJ+U6qmNMGMrO5f71D9vOGLZRBSKOqVT/aS8dog9AT9WMw0TQGzwDyzMWYsQObVwonzjy7dHZbmsOGvUmsvN8tQ9VO9aZb2foic0X22PJ/OnhRZqLpbCAA+BWAQA4W3bePf/DbJ+9PWHjDbow2uIioyJDE7hSAy7yprLy+g03j7Ro5lFUrz7KQwhTKzKCVawI57ke/is6zCW/3H93OZLJkmEkZYGap5KJ3LBGKKvemzCY4+cmL7ECMt17aa0w2rJJeezrcnU1r4cOc6kjFDNo3zp2my4BNHSBjKsgccYWXlj5kBDU7l0KKN+zIaOJBTSnRIk3VnMm+9oT//Mq/XXrwEhJFfSSiLG/vHMixYQ1Rc8ymRo6rH31pklXvMTm99dqFpQcuFVlWJbUUN1AZyYJlmWMyYlQ9u+uhS96Bycz0V6/uoTq+s0krnKZotZNomfUnN3720vx98IlP4ywoggJwx9rKJCpcysuL/yM8QKQaH1v+6b6FNAzPCBLurocuRdGy7CepmAjeiw6x6aSBr3WiLUIQI/Dix5/eO+jlHYuaGTGRwlD9aGeL042kM7jbf0p0BHZWhmSbxXWIKEaNEWrmCFnBjk1VuhUtnbmUZezYiMDQf2g2kfVx+N1U1MNTOiOIzYSbPQw6KWMqHLksxj569vL8/Zw7IzGoahwmMlzDHowgFAnsnYaYZkoi5qrSPN9/cUgEVUq1RVCDZ6GD5aVKKAlmCtWBR6KBufrhsLP/xJIMM4CgtYYLYCIDemXslVCFQefanhhG7BBv9ezEmUveO2Yo01svfaa2hjRMkHQj2Ag9srpyGq3XEjQul+shsbmVExGxC7FCj74zfz/nRERQ+eTyf6m5LUeQEWRDFM18mmVQEM0zZ0bvfHd/3dQ7Vy/cdeZ5pjQ6CWZyvqUH1aAmPNuaFcogzjmCGWh4iTjJmDZQq4As8zHECfQ+MwFUlrEsAUBUmago2BMiUyzlrocvEYPYmjPIQ0zS/MmR4HpiLab+5ML4hXc3eo0bWsTOW6xiZS8tfhAMIzzWSMehGfZY4H0PXcTcfwEAABoYSURBVCZDp5dIdwpAR0g7xmRIl95WRAy0+ImvH6yYI+XvWAbxWWZmAFU/GsEhz9Z/JGHPkt66doGYPCXM+DsCjpmIqire7IbuSmVqRExsoY+lM5dOPvT80pnnp9Guhhni/I2fEowoTjGAZ3y37L/dKZcDiJnICFTZy4sffPn4B18+cd+0WnWIGHqnSNT2rkqW9dcZbASbL7IQ4QhJDJ7VwCQ8k5mkpgSxy1WEneu/sXMghT1Ip3va/yNMVomRo0SmV+MTooaoqpZ5znOOYmJy7KHn2NnyHWKbozpGAqy9OBLrTCLVCMvNVVNWJUlnVbnGczkRjNUqe+nYfcZobHP2YNgxHVXByeyvM+8yx7eGDhHy1msXPHOR+1QOi5nzEzsJm2XKIJGoHVq5EWgciTjhieydqxcUINE4G/ePmUSt149VFQFmZxJx7KHnlh5+dtpNqx8zJLQEnt79TFvz471fGMERu/asuH5Jt4o3K7kRmdgYFPGdpftfuftD027XjDKUUHzfQ5dF7VYiu1NVy1lHjarMmcuYkOhQvAyqhgNrUA8xoqZEPs9YqHSxpVn1oyfHLCvVpDLciOheewpmbY2pVkhJICKNWnYBc+xMIh07e2np0SOtUE3f/0MVmFZHoDWI4yeqX3DGWsRZC5oebwVbjkxEnrUfXz5+X6NQ3c5wN42ocJwqVgOTlUHdiA6zxFTlniiNgYUCRIo7UoMqas45l+UwAGYOKz86//ZPzk27XQCGlYuZaXRMmc2axo2JNGrVBYQ5J+nL0kNHNlBOagX2sOLJcAgiVZtX6wv5ctbkIoC4EsLbfSICw4J+Z6mRi5sYaoNfieQ+S5I6zczmsrwXQtWXuY9tUjFtEXdmqzsBIhBRp1cRaKHderfTS5C7h4ict6SGZzOOmYlalnnHJGrExs53Xj8/7XaNw/KPvzz/4DNQwBsr63Qsb3aFiFQ1vqtFi9Vs6ZPPIJPll46aX2x64TTcbTRNHTeghuHz2PL1K/m/VHXqJUOeMMZNKuJKgINf9BL0yvEPgKRxcByw/+B638OX1exGt5ukPiLqhFBFZV7f9BG2ScT1V9ZdH0wshHgzhURcRWFqCx/96hhfna05eE/MLER1TD7L23OtVWNRoluvf/aQSsQBne9/AQxmuPkqElVx5iYdZg4VWBmZoMdLH3l62i1KTOKnYHg9ZlppXFvw3seq/6pMzjmbEy5mb8MIQBCXI3kPEjJuwo4P2P9WEVErd5zOzIyJ8sytFz7YCO78SSa3IXcuEXEqiQhEUWh0bkzroZmVi1FU1KogVRBi9lmWLRQCAszUssx3rn2uc23c48MdmZKRXef7X3CFhMoxiffOzHSWThkHBDH0CpQKdkdPLk6HxDe5xjHzRPUmFUAgJbX2IPXozKHvVl4LI23k4oD91aeimvmZyJrGSf21iSjPcpGxNKhJHdZFbYvNyPoqgQDQalXrL65/WA1qxkS8trBg79uFBwxmZVmpGthIYbm7+d169oXp+mGM4JcDnWT74885UOayyBqrCEo8VA5IiFoUbS17Ce23GxJSq6Qa6CRfbJ8yUFzy/mZpAp6xPJThZpkdKyKX0Jnc0U6WfYTib539ZilShkQ5hWcMMVKi+Qef6Xx//yCfW0kkF6PowvFFk4hVy4W1Lfnq38pbpbYOfihAMDEPgCAhVAM9kJkOxGhR5MvfO2RxyMbr0d4bT504fVnJSK1dcDQOVdxDAzF5yhizrDCVk5949p0f3BlejIeEyezdzvWuXz5xH5dRPSMnq8xEZ0o0hpslL2Qq8cW5e891fz7t5kyTfYSiEQp2N6pyduaXhFRBOTeeqn1YiFJKn43dqinsWlxVs8HWabPwXT0TNIBgakRQAxkoy/Ib33tiGlcwE2Gcb1w7D+DkmYtqBFhrIZfKIFJGMSBz01//BtWCYGTvPfP0r64eNaObhn05f+OnAF5onyIxZSB3JAwxS5qC8SDorWBzjCjfbv/+471fTLs5U2MfoRhEfeaOpEQEwEwZnE71fNA57lfCpNX3D2X8zJkaGe9cvQDgxCOXVcyptUuPAkQoo4gaEXkmNSSz1RqR0mjRx6gztD9omDBP9K4DeKF9ipWi0+o4FvuskaUXaAYeJutGbgOJMuYeUvZaQf/W2W+K2c1uObHWTAMysYWPTtWL3/hO8g2pnRuvnH/3tc+2+1w59UqmtujdfNu3i5yI1CyITsuLo5TClH7zY0fWebFhGJ7oXT9X/k21gDxSIAhJ/x6ixYynHQSHwYhOFBfbvz/dlkyRPe8Boe1cfyIZCaZFiEIqbkTb2oR2Nmu+mEe2h6fFP/71qmHRPacvCoGUFMJMx9oZg4NoVYkZDGYT3DtWqseMLG3I0IbDyYW3rg9+uXjPqSyykDqFeag39pkz0s40jDmCVW3zI+RrOGrsJRSjmvd85OfrPMtk9J1awo2G92nT1xxeakm+/ta123rpux9+nkBiambsyOXOKZOjUEmMUdUMNuoKaVQ085NLQdkwDNO+G+vSEcALrT8gZqiqkGWQIrT8nCo7sdBJkj1vf1rKetSn/T3YVSjec/ZiEKnKmfOJTo4Aajb/r7/a+at/M602NBsHAESwmtenb79620Fz6eFvkJGRmRjB5pj6zI4ZsBBF1RI6xW7CUQzxPR/9yv/3oz+tpfyGkajNeX88nuj/7frv31z4Xc9ZVHFGIVQBK9niMbaMieNKmkjUO+Iog8Rv5ac+XV2vr5aZZVehSMbOaaevR36nWEVhCTSiF3/KTokzZq8yMslaP8mxtvzqZ9d/v+f0xQi4NR/QPC8IGkIsoyS3XL1VhnktzZqF0HamIpxmSCJu4TO3frn++2X8NueFBYH3MVYyLx4ZSlhMr2XSfrD8zj3T2VUoippnT3Q0PRQ3wkSuyG0UL/6Eg2XVE/8Q69OOwpOzUcV64qEXAFM1EOZaLgSLoj6paDTzR6Lb0nJ4H4FJcB7/DWva0xfm389gFQVBWpJTS3uJJ2rn+BDPSQdjZ6H4W2cv9qJ1q6MvEVcxUrP8X/159df/bgq103S9Qho2se7uuXTmoogRochdr4x5wrhOPtPmGLlhXJ7ovDn45Zut9zv4KMHmwF1L6NRB7OlOlYq77RRd28sdcJ64ShSNoed4VpKCHi7q1rK879HLUcyM1DCIIk8EBrApZo2t/20GmCnMDAaomarawLiGsDx09KLlqxcAHHvgYhQpcgqlsOckAeQiQI0B6nYO7SR85T1/xEYMYqOtkmk9SOOGkWO2fpa5FrJRLViMKhXChaGzVXym/yaAF+ZOWZTQkkLbligdB9NMxmmdCDs/mWIA5RNuyhQhojxr0zRCUxIBxodXCTmBcwci9o7U1hxhtgWDHfxr/e8tWVeIiIhUMZ7dzM3XLzDDBO0sXY4qghxeCVATU+yPA1dNREpG2JbulW5/YOO/N8Y2HsBMzlyF4GnkpfkT3evKwvCVT2meOtKJ0lFihxvwm2efq0SrO6xDmJ0atU5/rX/tS5OtedPT0rAdJjbifr93sGLIOYynX7p17QtLH39WgSJzIerBrVIrbeIuzwwpJjoCEXP1q1sHLKd1smVjiejP9v/+8tz7nTmad9ZJsFkMt3o0pTwQSng+O/Xk9Axfd3w2Xe60d0SDgO9GJaassxBpqWELBM79QfUWVRTPfuzFx/Ibn3dMOXS8OWs7d9iac8Y56D1lkE/hV5X7PBt9pzjgfPdNZE6yg7diANVh1zoMIYObarDiHeoWA6hIKByi6Pof3ZYmaUZwTA5uusHBG3bE1GJ1UL1Q7p0oKNL7/tXl8UogQMCpXPtnKrnVnc3w2Y13xczSWE4FjUGeOflHYzaDYYmW9QQa3kuNfMppMy+y6XqDbL2Y9555XhRllFTNMjNRG0wBA6sHURsIyLD2Z11khm1/Bq+LqKipDbhd+JjZEHfBwcGsffqrCcvcl7XjsUnWObvsuF6qYqxSLFqrIK3SBT+mcmnQgiTHikVaD4+GaSMSo8aDlxNu3Op48uNuG5iSDSs3X3A+rFDkzPnFVqqqWUGqz7d+L1WBo7J1q05EGexmFZIIRTNj59q5gxLW54G1X9xqLPaIgSOz3/xj5xIF5ACQVFB17ULMuv00x8uiqhzdEJvFpDmGsWZFcqdju8QWEVWxBEJRzbrtwMDSo08PshOPikHMcPCbb2LcKOqPEGqqmib7SUuNYFeWTj02tA3qOmyUOReRQDxzxqbAcOf45BOKY1gnhFZko2/M/95nO3+XrNyh2Sp+1OBdsninRBRFCeSZVhMF0mrGQDIYjGAwBgxEUBCv/dhRMpkBvGpxD2JmU/FJN1kFsiHNApMJMQIaZdoqO3eqmKogcxwOphhgIoB1rkQYefpa+sTTouLYO5fizhuosT49Qqipr8gtFPHWQXMKzcEFdDB6/uFvtt6PSpCl0vDpCCEXCZY07Uxe+dCOTv03jn1QHUVyX3jnPyYsf282CcX3nf5apRIspdFR35FX6117cv+Pjs5vnr2EFHuIdRSsFttnvtK7undcyrR7xYa9uPG9zy09eAngg5unBNGsm6uT42e/TrkOuV9cevArEuFIu1XMUpjkZTajJ+sN4/HEjZ995/iHkpyCVMsdXiosxivH7wPFIfeL35j/PRIOWtm7afwUxWx4I2tjpHWpIUXe8TbHYKvIt2+W38ap2++2PDLHi8Wf/ONP1l/81sL9VAnUEFd7YAyryaxduMxtEormfC5hOSaLd2rsW9B+jecnWim3C9cr09jKlkG4FXkoRUgjFycLpXnag5g3pvmgPVs6/e8J8ca1XcMYnTh92RBVxPnQ6/skEhEAq1qjGzhiMMCJLJOXSz7eMupHc5eWPlBCvry7aLyydArwJlqhase2IM1M6HiEvZ+RcQ3BKKirrqsL27TB1o/u5JzfLLyIyXLHtyqADGMG9wm9cv7uezaVqyDO29RP062q5jIidXj9fJICt/NPrz1199nLCacXZsokl313JOkFYmOiDyLadf9EJmKrGvgDExX2rsszI1SK1okHv2602v/LV7988pPPmKgBMDILZBlzLMvMJzKxa3tfQfI71TP6yMLQXuTCa5ngSE/f7WfH2spSopqP7oWlDw7MDS3aU/1fPIPfcd6xc5nPEAk+kmvNWRbLNAnhyVPsiW+PsAQUSXDVw9PKW6qbVskMwK+uSg7iWeePL9x+zu/+8F+EqCGdaljNTGpfDhOAdPmGmEiNTWl/G9SU2oI4pTzwM8duKorlqxeYLcuTrUaJOYirdIE5W68zRjf/8eeqisgxRMFgpmghiON05qIWxBn96sefT1Xg0eEwPwWf+vX/To6pnWychJs9Wq6OLyPzntkZq0UrKvo2TrWRSxQiIgbIc5nbcv/gx5nriCeFfmr5vwz5eTNFb6KLPN5masucKEqnbbBn4TznqnurlyxQUO4cNCaUWLtAVYgJY9dGUeNIOjntVhTXHDDtCzPYiUt9W6poZXBl6UPIBumcTKnsc9A8VK4MaQ0IAKAQ0NFYBKWdBmcsr+EYkCfHjovEIZRtuaR3+sUy5vo8sNh3cAto532mFbWVUtJN2gOEg46iCn5s+afknF8s0jZjD6LqFot9Bu3ltjA8tNHIk5xfWEgYSoA8M1nn2mdSFbgjb732GSYq8mT3wzE5cZTQxHgI6k6uWyuTaTqxaawrPG1d+YS3kRmVbP5wT/5rGFIY/28sbjhmVfHMxBoit6fdjoNhhXPRrx8oDIszZJObMxXYtrBMVvtqQfecvijk1JKtcUTNRCYzXzoilzSkOzlH5k6c3jP0ySGWYimZWDe8890vAKSGOo70J0YbRoR//KsL+3909klq+D1KvWmFcTIefuc/wpkEyya4Z0qPY2J3vvvmiF+z2OvU0p4d0dpy0N7eKTKxoZMugSIRxCaUO5dgFqOkS1BXBc0428thnNBIxdtMqieWv/8UiFymMRzKrGaFUQkkC045faYknZIL43Sz1KeWfwpHpQs0wW1TQqwFxDhGQhmNgYx5FNucg8DQ+jx9V++cESFLmWrZOQfmlR88lazEPVCtQEWeLNcVESqLe2g0qYnLts5kO4KdhcqyIkvlhDMxPFjAAP3TDyfyUEyCaWmBkwrj1BchrBTUikM2PgHwfEYgsJ3rDmtis87jvV+wZy4mNyTqm3gYwInTl6PaWoDSBERR88OES0vDW9cukCNKdyzkmIldMMXpi7t9ppGK60wytcjya08RuRil3cq7iXyHJoGBpA1z7/zwSChOByTXng47o870keynl39OJBbY5qfdlFFw7cyyQBmd618frwTy0Ap+/jCrjrFmfWpQMtfpJ7PoJSK1OEm5QQBbTBhBVGPoE7JdHj9KqD6d6Qd8f2iiMhEAbl37nHMsoovtvHsY9oummjtT7pMdIdUpUmtP6zslmjiP33oTnhBxaOSiI7BSZLjxVzqfWv45HEmWTI5MB1nLdWqICec27x0JbIJWYgRVoyJLNumI2jz2iNo83dwms8Q0UlB2fnAhdxxEF4qil8JXuj7MULAXhXNx+cePTbs5SUkswoZN4TSqXeRUONe5Dg8EWLLsEXXh2pm1IKJkNEYU8o2YEwTwwnSyEydBTfnuD/8FNBC7VFbposbesXO9q5PTFL1z9UKeuWLoXCf74pgI7BU72qA2EvE2U1rc3/zBBc8uqLTbvjfDetTCZQI4uBvXjp63/nSkE5m5mOwJrO9RPte5PojXa/MYPg3ThHHzuRaBiczhTzo/O2Bpjy1fhyPzguQOxRPDwNF5H3pVTLbc7ocojDHslw6IY/JJMhgAAIioLEPOvrJJGDoehrXvbkwttPXKG59znlTs2EJ71pJXqxqDGCQmjt2NNz437RbVgKa2Ph3yBkriehOG/tjCuf51ZCA1yUrXmjnlubUhGkgcvJ7r/E2aQtm0MmnF2uXi5puWKiCGKRjsy6IdE0ViNDPPVPWqyTujM6PTDSLJZJiadbSqO9Ph4PmeqQl9JNSm2fjOtaeKLDPC/Ik5710nUWbNA+KYHK3myLz5g8/duFZX7N/pQmYpZdPQEW3ITNPtFGFWq7bjXOe6sYCyftu44HorGxpuZ7IAUxjs0ZWfHVBrupHHlq8rKQnVKxe3n0CbuZhm8ucAdpwDSDL7V1F9XhCo891JTwT/8NJnjDDXylPN0USkRhWVePR/2fLWoApJsTYxM4geXqFolj4Q2kgsf/+z2VwmVVTY0mLGoFQrvDEgIHOu3Vr0PiNg5Y1kJwgzMpluhAwuofbRbHuQkl3qpYR7LlajmqMQnOv8XcycCyakrmXTVaVSxnTM+7b35C3Dud715FU80XnTnJGQtYJr1XOxqltHi6glGo0sqt1+mcpuJIoYYFOKOZIXjnI6YCradbxjRJGFm1RuNTI2wMzSCEUArHRoFah7pbYYhYMU8va3z9149bxnVSEl9TlH0UmKRjMzs8Jzm4lBMVZF0b6V2h9x1uQiEaV0oFYZchZKfDJjOoEU3+dv/PTTt37moDAGxC+yKyYtGiljWvDVAptBVLIse+LW9ZrqeqLzJjllOG2JX0gcDHaVzTMGGTTFTpEYnilW6kzEO3YMpk2GletT1daxv5Y7iTb8q4rKzCWpm1IkT/IoPIVfKxP5AwdxDaISols5Dldt72w1EzW1A3l3iioMnmDpwvFMGCbyGQfR7GAdXkZtZQeaJpavfh7A/APPqRg78hlDqFcG78jVs0pTNWZyjtnMly2hUh2cyVvf+2wd1U3DzncvzJR8lup4z/tc4lAGU2bmvENMtPbNcgkTMtR6tP8LAN9ZvNcERuoXmaILvdprz44VxrKSxbwPJxw8Hr/xn+uu9Fzn764snSJlMaElZFJUK8m8NVi37UjMPFIkkyT4dl4QodOvQiWRmZmYibfJxYHY2yohCWamagPVKzMZKQVIOteIkfCebi6XCwV1KwlRiAaLWVpr9eC/1Ssa+BoSYbAMWF8KqKqqqcFgee4RRXWHy3HMsNArhWm1x9ZLuL2SsNuVDqC1XaaKsmPH3C68ViXSxWGfMAOjZRGt+hWY3aAjVnti4yS+Ooxse/+orSVmSrB27rz+FIDFMxehMIvHCzHOVflWWTlmIhxQQA5Gu2PKPBuZWmWawTJ10YXi7TfOHfwSdmTWJCIAA6p+jxLFrYv9PvuhthQGK/tlktECIPaGrTcVn1r5OYDvLN4LJY3BoURREHxM7VyULRRVDJX2EQgtzoWrll546+dpa9mDwVHllaVTrC5KRQsg8dpLcZmKLdq1VI8HO++jwEwdk6zLPoPBBhPbukTEdom4qjXa9E+AoIJrX0rUwtH4x2+eX/jY14LYIB0eABiMjEC3hdOGGZlWUzQbQGa2WRNoTKSqzMTb47EThSjMZGJrtQCbS1gXAhu/PGiAmRETDEQQicwO6eyDJk8UJYCYgfVeXB0+66qEdYmIbf0DIjPzjkOUVKntV65eAHDX6a8aOVNVtRNFZlA4T845YGV0k5yFVqZqJKImKLsVWsZEYLOw/MbRc7fYH4kRykZKdtAlHTuKQf1wm06JYqvLy4POhMwU47D1pmUgGl/Gv4RzEDOrcpQ0t8g+N7UQY+yXNGJUsPxYG8yiEqput1/OlSBHjnwp5ZM3/r6e69ifVdG4cArKQJWfLCmcADmDlje7Y672NG7Jn0g+sxQ+FFIlNOJqaJhV7jl90QZrECZiJ2pqwl4Kn3vvnXPe8+3sGwqFqmqsYgwaYxANYhmTGyi6TQJUIPHtn/zZdK+r4cjwKn4HWU7Ok8/VSEJUU9/OPMzlmbFb385u3B/FGClWFk2NpIzsmbwTjVWoREKI8gX8H1O5nN149eTvQFqAh+YaxUyzOV/4HORR5NhNizM4XVIFwMyxqjxYJHzirb9a/8jVYx/monAkrWML3vsYNcaoWHus1wvWTaXp4JdBnzLgfauV//+8DIKVcbfIkQAAAABJRU5ErkJggg==" height="118" preserveAspectRatio="xMidYMid meet"/><mask id="6a93f00c90"><g transform="matrix(1,0,0,1,0,0)"><image width="604" xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAlwAAAB2CAAAAAA43xIVAAAAAmJLR0QA/4ePzL8AABUWSURBVHic7V1dcBzHce69o6VEJoCT7FRs829RUeXBkomDY1UlKYlYMo5iJxFxIKWX/IgHyZYTJyUCTvIo4aDEebNBKg+pVBzdiZQqVYlEAHL8EEviLajKUxLhSMWVSlUsLH+sPLhEHEWQJni3O3k4HO5n55uf/bsDha9YxcPuTE/3bu/0TE9Pj0HbiBqf+eVDQ1kyzcZfs4WNy1YZlLcPxs9TT7Cj1wzcYdh/ZCw7mOLeYgmz0ntsK1eEsI7lMviukRwjfYJt5YoKg08dN4UFtnuubQTD0PRxQaf1McW2ckWC/Hfu6zULfYht5YoAmXlLodT2mGsb+njkjW2LyAV/1rwNDRxb2tYtPhR6rszqxkTHoNYPIiI3TUMfqTbEqM7a6mKkLzpEVLnmOP9+Q4mwx9JEjBgRMWKMyDCIsU8kZYaeLCXTzhaEgnLlqEYGERlEBhlt7yxN9Niryi15KcVe0jSJyCKi+pXK+YWKtDxjXqqDLyIictPKnIVC/qVk2rlDMc8w5pWpCIiI4F0t5ncGIxxWbiUck0pQaBa1UAm0LPQxwKDoydWVyUhfAsZqMRuEcHjR5ciuSrkvNMuOoRJ3rHLJTdUR0U0jFxknGJn8f5atBNoJgOL2WF4AuXKNC6sL70aGlPX221YiLemhIOpStyFVroy4b0qi5yIiSh16a77vegnzeK856G9IZ4sS7cmML0bFigTp3CNPJ9WWIma01H1reegfSbsGeWQYXfNw9x11GlLlktm9XHIv/FOvnX4qscYUsDffaw5ixLlOn2YLGt+IzCwOyuxeUnaRiGjH5HI/mca+0vToYRiGYYTqbmXKdUhGIHM4TPO6yJb3J9mcGMd6zUAvoOPhkZlF+Wxw4g2N5kIja1sXkmxPAMuUFqlUiZzmHx/aqFQk7GxByJ2Eq2qEpHRU8WFGkXD0D6MTc2I+5/Ofi5uDOIHE8qJrIqfwttXsogIhRXSNu2C56J4CH8siJot74m4+ZiDBIlSuosLLLoZiNgDmlQhH+BS4GBJwuHog5sbjRwKPVW4VVe2iAiFlPJvwU+ACrkMztrrVuy2K5rGKZ4uinVKbyIxptBcJvmsm3SIHFr71yOXEuEgcOr4JsXKprRwm6eoiIqJ0P8RQ7YN3Zv8rQTa2LlSsImMrKqSUKCnjsJxw3GaxjBpeHYq55UQAH70GDaGfS8kqEpkj5zVa7Ebpou/SiDki6X5PJupc4wI+m4VrSbKxZVFU7EfmFGihurcsXulP5st1YZPHpITj7rkga4mPEmIBFC+qBtSsoppdRHXX0XTAEqpXWUo4bj8XbPezMTecDOJ+rFnBy+2EQswcqsrvuYiI6PgabrG2V0a4Z8oVc7sJIQrxRLNF9YXZEEu4Am5P/v46vLdjOniT20gIIuVSHzzENMxYfAZr150xsrmzIVCurKlMxRwJzwkPp/4W3tqL/Uzb6BMIXBE6ti4fk5V6LmeCO6mxU2GJD/yKRWNNV3u1QrRE9vuXVGuzXoYt58ay2QxRpbpk27jU0KhfwP+9Eq5lnTGX4AmtmOpknGFZCcTUra8siarl4bL4iWkxYbGnbO+hMX48VrWyNA/ddpbV+j2DCs12/rn59vdNggpOqeNPVO7vf7LxIzPVngsMiLn7ywEELLR+Kokn0mwh1OeKjDEmtYuo4i3JyuQKqth0RgSY1gzkheEybLVo8SsWFJ5ENwrNyqo7rlG55oPKdXqIeHwOBRQwsGx84DGX3gxwQqu0BhbQDSsoxX1zl4RbuIky+fJK/pNB6ceFDeMw17nFzvYX3D3nqAgY/yoVVi696Zh0iRt1JLKRC9xc5Mpa5GOg4EwprGqZxSuFYA3EBpOIiIpTkmKZwmU1AZ1CWI5kgMqlMVckIsrulZcJBBst46QDBeSNX4KDiS5kZlb60N1RzHdd6A7Az62EEDBiBzBULl2/aGx2Ee7HCDBbGyqe0dibZs731SbvISKayndf7VwlzxR1WPYJmJRyoa8WWaN8aFYAquB6gAeRsfN6mRRzy32UDCJLtN8fItDxeDLlvB7N3HLHTCxi7wp62PtMcOM0uJ4N6tSUCeQErOfHiL6qmOVkMq0o4mX/pXfbfmcDCGjHaPuRciErV52uadbYQOAe1x/uFZDgftvUbz2z8KR+pbjwJEd32ixJtmzq08ycyQdlRwqkXGjItVD9N80aYRHVylJmMdgA6uV+6bseznyXc7X1OjLBRojGS7EJCJTLRP3rPC2CUVdc80X0xHRjW4J81kREVOqTcVcqf6/wflABjVJMK8NIuaAhfpNeRy9VbBfREEk6dELKpTnmmgusIplif/hTU8c5L6vliQghYCkmfypQLmTjyj+jy2jlMx8BOxzAzCPv61CxnpWXQcj+RfC6UcLkXNucLFoy56oA2ZjCDvjKBa3i64QXZEYC2UWZdcuhUaGhtbw/F+Y0h5n+De9xmj9U9jFAPL87NCM88J85tIqLhBdk4km+C0ebjg6VvNBmeCTZzVHQaStRNOfSYgFlMP4yAlb84MdzIavoXCEiuwqGQRMvRsJSBwagcjV3hSjFVQmSl97+oHKehrKm6eHOLf/sdYVGeglRdlZnQ0BBkWPTyFcdBlzlglaxYREX8vy71qDyYS1tEJvFP0MzJM/WaGMEfte1VwsbH//epwQnJh4tabSWJOzGf1nccZWe2xg/fO4ZLKCRKxEl46FH9s1rWEQY3SdymASbLZp/iu4wnZRpeXSj8tBk07BcKgzbkIBfMuE3IY62igHQyVgZmWyOTT+QC8jIdV3XdUW7Pj1qyheEUbxTfSOfzQDaUCg6rAXFm90WBjfgmLdac/rsoRIKZLpSfQ3h5vysoXZhKFDYYEEudkYkoE+ZkHhogYYHXs81YIHCG/PE6yhbtOL2/w4Iey5BzNuizqZ54M6o5TpHGtdw16s+Xk42tH6t8R9i7zFVAY3Pd18IwVQTPOU6Csp6Zzd+wAC+AMl3RUL4gpdaqMMIVQ4s/lDdO929bnkJUvV/NoG9wlHCafxngdulbncNFvAXFFvUOQyON6BH6m00OVtATpWJ0Dty2pAVxep6OsoFOtSan8YiGm5atkZ7caO6Od7c+IEshr8XgAIeFO6TCQaOcg0h5Vpqzscdx+SXyA1oT9k98KXvnf29uwTVTq1ptAGU1Ljqu9T/B4hVS2f8oxL0Ffr9Cz8M275Ox8xRrglQn7U+9AW01jD+ikbbRERU47S280vW+IPC5E7rs6K7iuC0fJGYl9ApoMFQOBnOIfVBRHwogfMKUcflndn8uYiU66i2ct0z1/20skPy93u6NZgIvjnV+CVO+JDRz7pVPfCeVnkzHjaCYwDNVtsTJcHkSnB9HVUIhHpbincXlGmbXKPthqGMIGQOVQjvilhFi/gxCKgtHgf+eRSaK3YsWMPhdDKHtcy09e4K0iJL8utb7ICVWbRZBQlo5WPiRA1+5UJW0W13kUJnhPBc2ajwH9/WK18BCnjX3/VRDLMczgl0B65WCJw5CcCnXHCueP1c2x9vov4iia1+63nNClU0LLv7e3NbKDuuA+/4p71NFOd6uDvOp1xorthpCW+gros9FpYjKW49/aOOFuU1KnCG9YkpZ65/g7WUcQFPIadW5np25IJPuVBeEK9zcIhcbkbsdtH9m1e169j4VmZqZXnrH1Vt41uZqUvLhbii5DWB5oHeYEexPWhhEx3WAmcfmnC/10W4hgq2lcnD1e2NsqvzBUvzQUFiqELo2aJg7pcXy8eYtoDa4ikgh17DcldBtL7uglGXTHpFuP/QTfg2KtlWZifyV7ShXl8uTml0YZAQqhCncolOuWpBR0Bt8TjodqKOgyFXrful2oDN1DjfTRFNIr5br3w9SLW1U8ekzacpmyU3tbhkb8HDNa+V8gqlslkiWuidgFeBvtYe6CoIc8MBuygxTGq49Qd+wio9F+1R6Lo2saK0SwtWRxXi7LnwMCWogNriyQEP7/SfYwCd9HxfRhTKtfIgh/A6KNwZtPe8VkPuypwpe1SwMqoQq3LRjJaAbGVOsldLWzwOumaLMJjMb+sWknZ1rX9nf/DjwF54V16mhZQ59X7ZCtxYLzCrZ+vMqYvxC9ilXDB63u96WEQepniUy6385p+H2YLzG4pncTdhWG9vLfU6qBsuYZXjFrBTuWCc8kf+nuttA4yRB2NIbOE6T4+i4Go1VLUffso6Gzi/RA9QPaAdjGOVy3ElhCSibuVCasFs/7XrC2ArQirqrovVK5PDnNRUejhvObpVDOvdEJvkk8Z7Y452Het8cgJ+iEZx7jpjntcclNdrjLE6PFSMa4CCDui926viuY3agJ6IKHMGlRUA5iWCNRCj8Q7oiYgy8/ryIQG1xZMBzhV5wJN7j7eEpOML2ECtvr6+PPcFCdPqykX07FV9NpaBdsEKiNH4lYtoSvUUQ6mA2uJx0GEWtU5Cx5vf9ZJGuPV6vV53XdfzGCMixphbcxmR/cpfPXr36LRe7GUbF5xrLw6f8nQP+cyW+ynrrgQnzKL2IabxCdjxCnQOZBGBd1iLC5Sx/oo/L6WzQqswiXM31sE+DsZvcM8Lf5jSXCywD3Lpo+KIuoV6ni76quUAdr9wTDejD49wsFNvMLKReNEZYy5nER7ZoxtWMGY3gcwi/IL3FldvI7c+HwUeGVgatZuEWSQiot1FXePIEVBbPA7alVy+/qZKNK9edkfcZ1H7cGly19d+4N6u4Y333ZgxY2QnelyZ3DMJXdxcPBdPyFe7ckXnQtCh1IOT5W6emsh84weGV1NVbHh0Wp9irTQxOKmxbTgV5WbmNrKtn4Ezyfth+hcB0ZcUOg9MMOVcK00Yj/71OWKeSv9lbb1o1bXShHFg1lYsbcXSdbWF3ERmFYno6a1wBLVtE42MjlhZj8k2K05tBXl8eOcdogceGrEUgjy+FbOAK5qjQBH8QRTI5So7b1EKODZXprDz8NyKwG3Hl6ePB/Q+3DM+tyIUjyOgtngctMxihFaRaK/M9bmJpNKjCbD2xvTwyItVUeapuA7xTgY3F6eHR04Ilx45A5nwaClXlFaRUk91X+nlidAKuDB97zNOHd+3EuMkJlyYvnfSEdz/cgxttpQr2uVmdWp90HU1UBr+9m1400yOj9hQGp7FDzuOKcumcmke3inDvu6w6K2AwqM/Rc6JLb/5jIiICha0jXEIuDlbtKKlazz+I3mhRsloG/Yjx0+jPcU5on7pmX8KcxhCjwAEnObEpp6bFOWtjRqbyhV1To6cYgat0LolJZC1uJcnOMpFC68+ydcuPo3+ABAwxwt8XkDbhMJO2nloPsp98IidgPhCrDGO4QGGV/N9MwSMCTCFjCo0ppVN5YIpIqher9c9/Ueeju3Q62hwF/9TvdrPud/0wBcQDbqULciX1DloKhd0RDA3Rcxz6/VaG+r1utuIvsKLJ3l1JuKFzb9s3cO9DEb0TiSsxAObf9ka5F/nw5H8vQmN8dPGmAs6CdnS855BtPmvDQYjxtIzFqiZ3fWTDkKgGNrmoQzpoiXIL+Q9wQvLvx+Qc7R4ShYogdKREueiCQo73X+jgpZ6YusN5crBrOovSTbdgNEkET1+UpWJeHGBfxBWqrDIMRHjwCzGce5SVAAC0swCT0BARF3AeYs3FeJhwyzivk42dcX384oshIS857P5l01OII3124CG6vPsCWz+ZZ6AY8i73S0gTkufqRQVLW5DufbCpbOKLN/7RbjT94GeJR3rApog5XzB4yP/jHLf29GxEz00BIRBXt2r4o6gvXz5WmMRu9D4+wBjvCDmckO5jqDP35PPXG10I51IflSIlkglmI/2xzPtWSuHCmc/DUpW7Yi4igVYwJVCu3plCjbai1Ht7qkcjfZTwH40lAtaRYVTUOBuVZ1g53gBB3/3FarzBcsiosGxY0Vn5j5UUOcwmB4ACpiZWZ0vWAeIaPBAvrgyA/f5+AS0o+GMaABl5+PFMfkAdwPUd7WVQk2sh3UNQ95bRQaFGxZUtjJyLDwsixiNMZ5LLKAKPuujWVaoVRBy3DCLR+FRKDaUpwX4VXfYxV6G3HwkXIpSWE1cuBwVK/FALKACFv7Pdym0K3/jycLMIa6KOcBcJDLoUtHaE3a4Nvo+Y0RYAf/Ef+n1cBSJGsq1EwZfGSrq+xb00j/cN0ne8z8NU3vWv2+335AP5Yib5Zw3ddkOQ5GIGsr1OBwmvKFCYu376I7R1iX2NhL14hM3g1e2C5HxERsuhon15AsYOq8QpQgn2VU9jhX629oXr2NTLjXCS398I2gDTp8vwTewNBm4KhCw5ASmuIEU0RA89MI4i+504HW4t3R8ZwCW4sGpbwbsu64e7uelnxZKQbWrOg4EDL3bLCWKtnlPbZJ0GSYNcVvfRI97LqJT3/xZEPIrB4Om2UkaAbXLsdDrWwjr3UsRjaO5uGsrEoHleuyk78TL3/DPt6WojCqn24kKgcMVS5MB+tjKKF42DUKvHSkagEPBWy8pEoFDP+Or8c8X1d/F6a++r/ni3LnRa5rs9BIl/cycJ0YFClQdC6ddKTqKduuxG6oGofIhuiM/xCx0WLFGlpzz2ZM6566Tc+hbutxEgBBP5Hz2hFZt56B4XHVBTbtQmykaR6/n9r+oECYiou/DUMCWMwJ4w0KdVESk9y6uTz8m2vnaiersg+fkpdSRRHT+tWmNzqs6O2JLilxQIoeV63fQiLimvgtpAW2F3/G7P9dkIGHlApft4a/9WEW92OqJPQWh90Kb72Q8feeGhRurW6ieMAsfSUudH1UY1UPlOlxfr7uMiIgx5m2AMY+tp20lJomI3qyBF1arNeeLnsvtIF2QXVIdd/EVex2Vf/n+r9vr4rxJHlWm901LLGhsuhL2gZSGJ21pocr0nmml4WR14qCcGsCOiZ9fW0+nUiki1tJA5rmUPqc+Prn5w9+6baQaUfVEZBiGYRC5HmN3H/7HRpE0u5lOGYbBGg0xIiLPS6fvEeX/UIJ7K5UyDCKDmrQZY3ApnohKpV1PjP/qDoMb0eyy9PmF11R39OpA1R6HfiBUKu16PGfh+5XF1zQOurFt63gw/3+f5weJDzsPfXHMNLuvOs5S+d0wp8D0DwYPjo6Z+7rfr+Msna3IraGP2JGx7IhfV2YLRET0MH+fhf2xVa4GPv/p+zaTJLzlVv+7l7zEgvs/9YtfbP7+V/fa/4Sh9Wuph7qCDW2biIg+80fc8s7/A5XBblZa1PGJAAAAAElFTkSuQmCC" height="118" preserveAspectRatio="xMidYMid meet"/></g></mask></g></g></g></svg>
\ No newline at end of file
diff --git a/public/partners/osaango-black.svg b/public/partners/osaango-black.svg
new file mode 100644
index 0000000..7e1de37
--- /dev/null
+++ b/public/partners/osaango-black.svg
@@ -0,0 +1,286 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg
+   width="708.75"
+   height="285"
+   viewBox="0 0 708.75 285"
+   version="1.2"
+   id="svg39"
+   sodipodi:docname="osaango-black.svg"
+   inkscape:version="1.4.2 (f4327f4, 2025-05-13)"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns:xlink="http://www.w3.org/1999/xlink"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:svg="http://www.w3.org/2000/svg">
+  <sodipodi:namedview
+     id="namedview1"
+     pagecolor="#ffffff"
+     bordercolor="#000000"
+     borderopacity="0.25"
+     inkscape:showpageshadow="2"
+     inkscape:pageopacity="0.0"
+     inkscape:pagecheckerboard="0"
+     inkscape:deskcolor="#d1d1d1"
+     inkscape:zoom="5.2035273"
+     inkscape:cx="458.72729"
+     inkscape:cy="142.49949"
+     inkscape:window-width="3840"
+     inkscape:window-height="2054"
+     inkscape:window-x="-11"
+     inkscape:window-y="-11"
+     inkscape:window-maximized="1"
+     inkscape:current-layer="g39" />
+  <defs
+     id="defs19">
+    <clipPath
+       id="d">
+      <path
+         d="M0 67h93v93H0Zm0 0"
+         id="path1" />
+    </clipPath>
+    <clipPath
+       id="e">
+      <path
+         d="M46.3 67.414q-2.254 0-4.503.223a46.3 46.3 0 0 0-8.832 1.754 47 47 0 0 0-4.246 1.515 46.2 46.2 0 0 0-11.566 6.918 45 45 0 0 0-3.34 3.024 45 45 0 0 0-3.028 3.336 45 45 0 0 0-2.687 3.613 47 47 0 0 0-2.32 3.86 46 46 0 0 0-1.926 4.07 45.5 45.5 0 0 0-2.613 8.602 45.4 45.4 0 0 0-.883 8.945 45.4 45.4 0 0 0 .882 8.949 45 45 0 0 0 1.094 4.363 46.4 46.4 0 0 0 3.445 8.309 47 47 0 0 0 2.32 3.859 45 45 0 0 0 2.688 3.613 45 45 0 0 0 3.028 3.336 45 45 0 0 0 3.34 3.024 46.2 46.2 0 0 0 11.566 6.918 47 47 0 0 0 4.246 1.515 46.3 46.3 0 0 0 13.336 1.977q2.261 0 4.504-.223 2.248-.221 4.46-.66a46 46 0 0 0 4.376-1.094 45.6 45.6 0 0 0 8.32-3.441 45 45 0 0 0 3.867-2.313 46 46 0 0 0 3.625-2.68 46 46 0 0 0 6.367-6.359 45.4 45.4 0 0 0 5.004-7.473 46 46 0 0 0 1.93-4.07 46 46 0 0 0 1.52-4.238q.654-2.155 1.093-4.363a46 46 0 0 0 .664-4.453 47 47 0 0 0 .219-4.497q.001-2.249-.227-4.492a46 46 0 0 0-.664-4.449 45.4 45.4 0 0 0-2.62-8.598 45 45 0 0 0-1.93-4.066 45.4 45.4 0 0 0-5.004-7.473 46.1 46.1 0 0 0-9.989-9.035 47 47 0 0 0-3.863-2.316 46 46 0 0 0-4.074-1.922 45 45 0 0 0-4.246-1.52 45 45 0 0 0-4.371-1.097 46.3 46.3 0 0 0-8.961-.89m0 74.059a28.5 28.5 0 0 1-5.51-.543 28 28 0 0 1-5.3-1.605 28 28 0 0 1-2.506-1.18 28 28 0 0 1-2.379-1.426 28 28 0 0 1-2.226-1.649 27 27 0 0 1-2.055-1.855 27 27 0 0 1-1.863-2.05 28.1 28.1 0 0 1-4.262-7.098 28 28 0 0 1-.937-2.606 28.2 28.2 0 0 1 0-16.371q.406-1.326.933-2.606a28.2 28.2 0 0 1 6.125-9.148 29 29 0 0 1 2.055-1.86 28.1 28.1 0 0 1 7.113-4.254 29 29 0 0 1 2.61-.933 29 29 0 0 1 2.691-.672c.906-.18 1.82-.312 2.742-.406.918-.09 1.844-.133 2.77-.133q1.387-.001 2.77.133 1.376.14 2.742.406 1.358.272 2.687.672 1.331.405 2.61.934a28.2 28.2 0 0 1 9.167 6.113 27.7 27.7 0 0 1 3.512 4.273q.775 1.151 1.426 2.371a28 28 0 0 1 2.12 5.11q.404 1.324.673 2.683a28.2 28.2 0 0 1 .406 8.266 29 29 0 0 1-.41 2.734q-.27 1.36-.676 2.684t-.933 2.602q-.532 1.282-1.188 2.5a28 28 0 0 1-4.937 6.644 29 29 0 0 1-2.055 1.86 28.5 28.5 0 0 1-7.105 4.254 28.4 28.4 0 0 1-5.297 1.609q-1.36.27-2.743.406-1.381.14-2.77.14m0 0"
+         id="path2" />
+    </clipPath>
+    <clipPath
+       id="f">
+      <path
+         d="M616 67h92.5v93H616Zm0 0"
+         id="path3" />
+    </clipPath>
+    <clipPath
+       id="g">
+      <path
+         d="M662.453 67.414a46.5 46.5 0 0 0-8.965.883 46 46 0 0 0-4.375 1.094 46 46 0 0 0-8.32 3.441 45 45 0 0 0-3.867 2.313 46 46 0 0 0-3.625 2.68 46 46 0 0 0-6.367 6.359 45.4 45.4 0 0 0-5.004 7.473 46 46 0 0 0-1.93 4.07 45.5 45.5 0 0 0-2.613 8.602 46 46 0 0 0-.664 4.452 47 47 0 0 0-.22 4.492q.001 2.257.22 4.497a46 46 0 0 0 1.757 8.816 46 46 0 0 0 1.52 4.238 45 45 0 0 0 1.93 4.07 45.4 45.4 0 0 0 5.004 7.473 45 45 0 0 0 3.027 3.336 45 45 0 0 0 3.34 3.024 45.6 45.6 0 0 0 7.492 4.992 45 45 0 0 0 4.074 1.926 47 47 0 0 0 4.246 1.515q2.162.655 4.375 1.094a46.3 46.3 0 0 0 8.965.883q2.256 0 4.5-.223c1.5-.148 2.984-.367 4.461-.66a46 46 0 0 0 4.375-1.094 47 47 0 0 0 4.246-1.515 45 45 0 0 0 4.074-1.926 45.6 45.6 0 0 0 7.493-4.992 45 45 0 0 0 3.34-3.024 45 45 0 0 0 3.027-3.336 45.4 45.4 0 0 0 5.004-7.473 45 45 0 0 0 1.93-4.07 46 46 0 0 0 1.519-4.238q.654-2.155 1.094-4.363a46 46 0 0 0 .664-4.453q.217-2.24.218-4.497a45.5 45.5 0 0 0-.89-8.941 45.4 45.4 0 0 0-2.621-8.598 46 46 0 0 0-1.926-4.066 47 47 0 0 0-2.32-3.86 46 46 0 0 0-2.688-3.613 45 45 0 0 0-3.027-3.332 45 45 0 0 0-3.34-3.023 47 47 0 0 0-3.617-2.68 45 45 0 0 0-3.867-2.312 45 45 0 0 0-4.075-1.926 46 46 0 0 0-4.242-1.52 47 47 0 0 0-4.37-1.097 46.3 46.3 0 0 0-8.962-.89m0 74.059a28.5 28.5 0 0 1-5.512-.543c-.91-.18-1.804-.403-2.691-.672a27 27 0 0 1-2.61-.934 28 28 0 0 1-2.507-1.18q-1.225-.654-2.38-1.425a28 28 0 0 1-2.226-1.649 29 29 0 0 1-2.054-1.855 29 29 0 0 1-1.864-2.05 28.4 28.4 0 0 1-4.261-7.099 28 28 0 0 1-.934-2.605 28 28 0 0 1-.672-2.684 28 28 0 0 1-.41-2.738q-.134-1.377-.133-2.766-.001-1.383.133-2.761c.094-.922.227-1.832.406-2.739a28.7 28.7 0 0 1 1.61-5.289c.355-.855.75-1.687 1.183-2.504.438-.812.914-1.605 1.426-2.37a29 29 0 0 1 1.652-2.223 27 27 0 0 1 1.864-2.051 28 28 0 0 1 4.28-3.508 28 28 0 0 1 2.38-1.422 29 29 0 0 1 2.504-1.183 29 29 0 0 1 2.613-.934 29 29 0 0 1 2.688-.672c.906-.18 1.82-.312 2.742-.406q1.381-.134 2.77-.133 1.387-.001 2.769.133 1.383.14 2.742.406 1.36.272 2.691.672 1.325.405 2.61.934a28.23 28.23 0 0 1 15.289 15.261q.534 1.28.933 2.606.405 1.324.676 2.683a28 28 0 0 1 .543 5.5 28.4 28.4 0 0 1-.55 5.5q-.271 1.36-.676 2.684-.4 1.324-.934 2.602-.532 1.282-1.188 2.5-.651 1.222-1.425 2.375a28 28 0 0 1-3.512 4.27 28.7 28.7 0 0 1-4.277 3.508q-1.155.765-2.38 1.42-1.22.651-2.503 1.184a29 29 0 0 1-5.297 1.61q-1.359.27-2.742.406-1.377.14-2.766.14m0 0"
+         id="path4" />
+    </clipPath>
+    <clipPath
+       id="h">
+      <path
+         d="M191 67h93v93h-93zm0 0"
+         id="path5" />
+    </clipPath>
+    <clipPath
+       id="i">
+      <path
+         d="M237.785 67.414a46 46 0 0 0-4.515.207q-2.254.21-4.473.645-2.224.432-4.39 1.082a46.3 46.3 0 0 0-8.352 3.422 46 46 0 0 0-7.524 4.992 45.5 45.5 0 0 0-6.398 6.36 46 46 0 0 0-8.492 15.808 46 46 0 0 0-1.098 4.375 45.6 45.6 0 0 0 0 17.938q.44 2.215 1.098 4.378a45.7 45.7 0 0 0 5.797 12.187 47 47 0 0 0 2.695 3.622 47 47 0 0 0 3.043 3.336 46 46 0 0 0 6.992 5.703 47 47 0 0 0 3.887 2.308 45 45 0 0 0 4.09 1.918 46 46 0 0 0 4.261 1.508c1.446.434 2.906.793 4.39 1.082q2.22.434 4.474.645 2.251.212 4.515.203c4.078 0 18.09-.961 28.25-13.246v13.246h17.695v-45.86a46.3 46.3 0 0 0-.89-8.941 47 47 0 0 0-1.098-4.363 46.3 46.3 0 0 0-3.453-8.301 45.4 45.4 0 0 0-5.004-7.473 46.1 46.1 0 0 0-9.984-9.035 47 47 0 0 0-3.867-2.312 45 45 0 0 0-4.075-1.926 46 46 0 0 0-4.242-1.52 47 47 0 0 0-4.37-1.097 46.3 46.3 0 0 0-8.962-.89m0 74.059a28.5 28.5 0 0 1-5.512-.543c-.91-.18-1.804-.403-2.691-.672a28 28 0 0 1-2.61-.934 28 28 0 0 1-2.507-1.18q-1.225-.654-2.38-1.425a28 28 0 0 1-2.226-1.649 29 29 0 0 1-2.054-1.855 29 29 0 0 1-1.864-2.05 28.4 28.4 0 0 1-4.261-7.099 30 30 0 0 1-.934-2.605 28 28 0 0 1-.672-2.684 28 28 0 0 1-.41-2.738q-.134-1.377-.133-2.766-.001-1.383.133-2.761c.094-.922.227-1.832.406-2.739a28.7 28.7 0 0 1 1.61-5.289c.355-.855.75-1.687 1.183-2.504.438-.812.914-1.605 1.426-2.37a29 29 0 0 1 1.652-2.223 27 27 0 0 1 1.864-2.051 28 28 0 0 1 4.28-3.508 28 28 0 0 1 2.38-1.422 29 29 0 0 1 2.504-1.183 29 29 0 0 1 2.613-.934 29 29 0 0 1 2.688-.672c.906-.18 1.824-.312 2.742-.406q1.381-.134 2.77-.133 1.387-.001 2.769.133 1.383.14 2.742.406 1.363.272 2.691.672 1.325.405 2.61.934a28.23 28.23 0 0 1 12.68 10.386q.768 1.151 1.425 2.371a28 28 0 0 1 1.184 2.504q.534 1.28.933 2.606.406 1.324.676 2.683a28 28 0 0 1 .543 5.5q0 1.389-.14 2.766-.136 1.376-.407 2.734-.276 1.36-.676 2.684-.404 1.324-.937 2.602-.532 1.282-1.187 2.5-.653 1.222-1.422 2.375a28.7 28.7 0 0 1-3.516 4.27 28 28 0 0 1-6.656 4.929q-1.22.65-2.504 1.183a29 29 0 0 1-5.297 1.61q-1.36.27-2.738.406-1.382.14-2.77.14m0 0"
+         id="path6" />
+    </clipPath>
+    <clipPath
+       id="j">
+      <path
+         d="M295 67h93v93h-93zm0 0"
+         id="path7" />
+    </clipPath>
+    <clipPath
+       id="k">
+      <path
+         d="M341.684 67.414q-2.25.011-4.489.238a46.1 46.1 0 0 0-13.039 3.305 46 46 0 0 0-4.058 1.934 45.6 45.6 0 0 0-7.457 5q-1.74 1.43-3.329 3.02a47 47 0 0 0-3.015 3.331 46 46 0 0 0-2.672 3.61 46 46 0 0 0-2.309 3.855 47 47 0 0 0-1.918 4.059 46 46 0 0 0-2.602 8.586 45 45 0 0 0-.655 4.437 45.3 45.3 0 0 0 0 8.969q.216 2.238.656 4.441a46 46 0 0 0 1.09 4.356 45 45 0 0 0 1.511 4.226 47 47 0 0 0 1.918 4.063 46.3 46.3 0 0 0 4.98 7.46 46 46 0 0 0 9.95 9.04 46 46 0 0 0 3.852 2.316q1.982 1.068 4.058 1.93a47 47 0 0 0 4.23 1.527q2.157.659 4.36 1.106a46 46 0 0 0 4.45.675q2.237.228 4.488.235c4.082 0 18.093-.961 28.253-13.246v13.246h17.696v-45.86q-.002-2.249-.227-4.492a46 46 0 0 0-.664-4.449 47 47 0 0 0-1.097-4.363 45 45 0 0 0-1.524-4.235 45 45 0 0 0-1.93-4.066 45.4 45.4 0 0 0-5.004-7.473 46 46 0 0 0-6.367-6.355 47 47 0 0 0-3.62-2.68 46 46 0 0 0-3.864-2.312 46 46 0 0 0-4.074-1.926 45 45 0 0 0-4.246-1.52 45 45 0 0 0-4.371-1.097 46.3 46.3 0 0 0-8.961-.89m0 17.664c.925 0 1.851.043 2.77.137q1.38.133 2.745.402c.906.184 1.805.406 2.688.676q1.33.4 2.613.93 1.278.533 2.504 1.183 1.225.656 2.379 1.422 1.155.772 2.226 1.649a27 27 0 0 1 2.055 1.859 27 27 0 0 1 1.863 2.05 29 29 0 0 1 1.653 2.223q.771 1.15 1.425 2.375a27.6 27.6 0 0 1 2.122 5.106 28.2 28.2 0 0 1 0 16.371q-.405 1.323-.934 2.605-.533 1.28-1.188 2.5a28.4 28.4 0 0 1-3.074 4.598q-.884 1.072-1.863 2.05-.983.978-2.055 1.856a28 28 0 0 1-2.226 1.649 28 28 0 0 1-4.887 2.61 28 28 0 0 1-2.61.929q-1.328.403-2.687.672a28.4 28.4 0 0 1-8.281.406 27 27 0 0 1-2.742-.406q-1.363-.27-2.692-.672a28 28 0 0 1-5.117-2.113q-1.225-.655-2.379-1.422a29 29 0 0 1-2.226-1.649 28 28 0 0 1-3.914-3.91 28 28 0 0 1-3.078-4.598 28 28 0 0 1-1.188-2.5 29 29 0 0 1-.934-2.605 28.2 28.2 0 0 1-1.078-10.95q.14-1.374.41-2.734.274-1.359.676-2.683a28.4 28.4 0 0 1 3.547-7.477 28.7 28.7 0 0 1 3.512-4.27 29 29 0 0 1 2.054-1.859A29 29 0 0 1 326 89.84a28 28 0 0 1 2.375-1.422 27 27 0 0 1 2.504-1.184 27 27 0 0 1 2.61-.933q1.328-.405 2.687-.676 1.359-.27 2.742-.41c.918-.09 1.844-.137 2.766-.137m0 0"
+         id="path8" />
+    </clipPath>
+    <clipPath
+       id="l">
+      <path
+         d="M101 67h81v93h-81zm0 0"
+         id="path9" />
+    </clipPath>
+    <clipPath
+       id="m">
+      <path
+         d="m148.39 106.2-2.5-.41c-7.027-1.067-12.035-2.177-15.312-3.392-4.973-1.832-6.015-5.351-6.015-7.976 0-2.285.93-5.531 5.382-8.016 3.215-1.804 7.797-2.683 14.008-2.683a56.3 56.3 0 0 1 12.242 1.273 56.2 56.2 0 0 1 11.676 3.887l2.024.933 7.28-15.523-2.066-.934a60.5 60.5 0 0 0-11.941-3.832 89 89 0 0 0-19.215-2.113c-11.629 0-32.156 2.344-38.976 18.035-4.274 9.82-1.711 21.34 6.093 27.395 7.434 5.777 17.715 7.332 26.778 8.703l.46.074c6.684.828 11.54 1.828 14.848 3.047 4.973 1.844 6.02 5.168 6.02 7.637 0 6.984-6.465 10.523-19.211 10.523a68.2 68.2 0 0 1-15.125-1.86 68.4 68.4 0 0 1-14.34-5.152l-2.066-1.046-7.286 15.652 1.915.98a66 66 0 0 0 13.671 4.946 88.7 88.7 0 0 0 22.184 2.785c8.832 0 16.55-1.211 22.937-3.59 8.125-3.031 14.942-9.441 17.793-16.73q.851-2.111 1.227-4.356c.254-1.492.344-3 .266-4.512a21 21 0 0 0-2.363-8.68C173.16 110.2 160 108.076 148.39 106.2m0 0"
+         id="path10" />
+    </clipPath>
+    <clipPath
+       id="n">
+      <path
+         d="M406 67h93v93h-93zm0 0"
+         id="path11" />
+    </clipPath>
+    <clipPath
+       id="o">
+      <path
+         d="M452.48 67.414a46.3 46.3 0 0 0-13.332 1.988 46 46 0 0 0-4.242 1.52 46 46 0 0 0-4.074 1.926 47 47 0 0 0-3.863 2.312 48 48 0 0 0-3.621 2.68 46 46 0 0 0-6.368 6.355 47 47 0 0 0-2.683 3.614 47 47 0 0 0-2.32 3.859 47 47 0 0 0-1.93 4.066 46 46 0 0 0-1.52 4.235 46.3 46.3 0 0 0-1.766 8.813 46 46 0 0 0-.222 4.491v45.86h17.695v-45.86a28 28 0 0 1 .121-2.773 28.3 28.3 0 0 1 1.06-5.441q.397-1.332.925-2.618a28.4 28.4 0 0 1 4.254-7.132 27 27 0 0 1 1.863-2.063 28 28 0 0 1 2.055-1.871 28.7 28.7 0 0 1 4.613-3.09q1.228-.655 2.516-1.187 1.281-.538 2.617-.942c.887-.27 1.785-.492 2.695-.676a28.4 28.4 0 0 1 5.531-.542 28.5 28.5 0 0 1 8.227 1.219q1.33.403 2.617.94 1.285.532 2.512 1.188a28 28 0 0 1 2.383 1.434 28 28 0 0 1 4.289 3.527 28 28 0 0 1 1.86 2.063 28 28 0 0 1 3.074 4.617 28.3 28.3 0 0 1 2.105 5.133q.399 1.33.664 2.695a28.3 28.3 0 0 1 .52 5.52v45.859h17.69v-45.86q.002-2.249-.226-4.492a45 45 0 0 0-.664-4.449 45.4 45.4 0 0 0-2.62-8.598 46 46 0 0 0-1.927-4.066 47 47 0 0 0-2.32-3.86 46.3 46.3 0 0 0-5.711-6.945 47 47 0 0 0-3.34-3.02 47 47 0 0 0-3.62-2.683 46 46 0 0 0-3.868-2.312 45 45 0 0 0-4.07-1.926 46.4 46.4 0 0 0-8.617-2.617 46.3 46.3 0 0 0-8.962-.89m0 0"
+         id="path12" />
+    </clipPath>
+    <clipPath
+       id="p">
+      <path
+         d="M592 45.703h24V70h-24zm0 0"
+         id="path13" />
+    </clipPath>
+    <clipPath
+       id="q">
+      <path
+         d="M610.55 47.79a12 12 0 0 0-2.01-1.118 12 12 0 0 0-2.188-.703 11.8 11.8 0 0 0-4.579-.074q-1.137.204-2.21.632-1.08.422-2.047 1.047c-.649.418-1.25.89-1.805 1.426a12 12 0 0 0-1.484 1.754 11.6 11.6 0 0 0-1.825 4.191 11.8 11.8 0 0 0-.074 4.567c.14.758.348 1.492.633 2.21q.423 1.073 1.05 2.04a12 12 0 0 0 1.43 1.8q.805.827 1.754 1.485a11.6 11.6 0 0 0 2.012 1.113q1.061.458 2.191.703a11.8 11.8 0 0 0 4.575.075 11.6 11.6 0 0 0 2.215-.633 11.5 11.5 0 0 0 2.042-1.047q.973-.627 1.805-1.43a12 12 0 0 0 1.485-1.75q.667-.944 1.128-2.004a11.6 11.6 0 0 0 .715-2.183 11.6 11.6 0 0 0 .266-2.286q.024-1.156-.188-2.289a11.4 11.4 0 0 0-.632-2.21 12 12 0 0 0-1.055-2.044 12 12 0 0 0-1.441-1.796 11.6 11.6 0 0 0-1.762-1.477m0 0"
+         id="path14" />
+    </clipPath>
+    <clipPath
+       id="r">
+      <path
+         d="M512 66h97v173.016h-97zm0 0"
+         id="path15" />
+    </clipPath>
+    <clipPath
+       id="s">
+      <path
+         d="m584.441 153.32-36.726-21.746-2.266-1.363c-7.648-4.598-12.21-12.422-12.21-20.934 0-13.66 11.73-24.777 26.148-24.777 14.422 0 26.148 11.117 26.148 24.781 0 9.223-5.312 17.434-13.734 21.73l17.21 9.946c9.563-8.012 15.208-19.422 15.208-31.676 0-23.43-20.114-42.488-44.832-42.488-24.719 0-44.836 19.055-44.836 42.488 0 15.2 8.691 29.34 22.601 36.871l37.453 22.11 1.797 1.082c8.7 5.23 13.895 14.129 13.895 23.812 0 15.547-13.352 28.196-29.754 28.196-16.406 0-29.75-12.645-29.75-28.196 0-10.988 7.004-21.039 17.52-25.582l-17.704-10.304c-11.59 8.68-18.449 21.793-18.449 35.886 0 25.29 21.703 45.86 48.383 45.86 26.676 0 48.387-20.57 48.387-45.86 0-16.441-9.371-31.664-24.489-39.836m0 0"
+         id="path16" />
+    </clipPath>
+    <linearGradient
+       id="b">
+      <stop
+         style="stop-color:#1f2d2a;stop-opacity:1"
+         offset="0"
+         id="stop16" />
+      <stop
+         style="stop-color:#1f2d2a;stop-opacity:0"
+         offset="1"
+         id="stop17" />
+    </linearGradient>
+    <linearGradient
+       id="a">
+      <stop
+         style="stop-color:#000000;stop-opacity:1;"
+         offset="0"
+         id="stop18" />
+      <stop
+         style="stop-color:#1f2d2a;stop-opacity:1"
+         offset="1"
+         id="stop19" />
+    </linearGradient>
+    <linearGradient
+       xlink:href="#a"
+       id="c"
+       x1=".355"
+       y1="142.361"
+       x2="708.398"
+       y2="142.361"
+       gradientUnits="userSpaceOnUse" />
+    <linearGradient
+       xlink:href="#b"
+       id="t"
+       x1="192.752"
+       y1="113.6"
+       x2="283.141"
+       y2="113.6"
+       gradientUnits="userSpaceOnUse" />
+  </defs>
+  <g
+     style="fill:#000000;fill-opacity:1;stroke:url(#c);stroke-opacity:1"
+     id="g39">
+    <g
+       clip-path="url(#d)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g20">
+      <g
+         clip-path="url(#e)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g19">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M.355 67.414v91.723H92.25V67.414Zm0 0"
+           id="path19" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#f)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g22">
+      <g
+         clip-path="url(#g)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g21">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M616.504 67.414v91.723h91.894V67.414Zm0 0"
+           id="path20" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#h)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g24">
+      <g
+         clip-path="url(#i)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g23">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M191.652 67.41v91.73h92.078V67.41Zm0 0"
+           id="path22" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#j)"
+       style="fill:#000000;fill-opacity:1;stroke:#004d50;stroke-opacity:1"
+       id="g26">
+      <g
+         clip-path="url(#k)"
+         style="fill:#000000;fill-opacity:1;stroke:#004d50;stroke-opacity:1"
+         id="g25">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#004d50;stroke-opacity:1"
+           d="M295.918 67.414v91.719h91.715V67.414Zm0 0"
+           id="path24" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#l)"
+       style="fill:#000000;fill-opacity:1;stroke:#004d50;stroke-opacity:1"
+       id="g28">
+      <g
+         clip-path="url(#m)"
+         style="fill:#000000;fill-opacity:1;stroke:#004d50;stroke-opacity:1"
+         id="g27">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#004d50;stroke-opacity:1"
+           d="M100.703 67.414v91.727h80.516V67.414Zm0 0"
+           id="path26" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#n)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g30">
+      <g
+         clip-path="url(#o)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g29">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M406.54 67.414v91.719h91.886V67.414Zm0 0"
+           id="path28" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#p)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g32">
+      <g
+         clip-path="url(#q)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g31">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M592.129 45.703v23.434h23.516V45.703Zm0 0"
+           id="path30" />
+      </g>
+    </g>
+    <g
+       clip-path="url(#r)"
+       style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+       id="g34">
+      <g
+         clip-path="url(#s)"
+         style="fill:#000000;fill-opacity:1;stroke:#000000;stroke-opacity:1"
+         id="g33">
+        <path
+           style="fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:#000000;stroke-opacity:1"
+           d="M512.16 66.793v172.223h96.77V66.793Zm0 0"
+           id="path32" />
+      </g>
+    </g>
+  </g>
+</svg>
diff --git a/src/data/partners.json b/src/data/partners.json
new file mode 100644
index 0000000..46532d8
--- /dev/null
+++ b/src/data/partners.json
@@ -0,0 +1,32 @@
+[
+  {
+    "title": "Osaango",
+    "href": "https://www.osaango.com",
+    "logo": "/partners/osaango-black.svg",
+    "description": "Coordinates the global APIOps Cycles community and method development. Provides consulting, training and method support globally, main partner in the Nordics."
+  },
+  {
+    "title": "adorsys GmbH & Co. KG",
+    "href": "https://adorsys.com/",
+    "logo": "/partners/adorsys.svg",
+    "description": "adorsys designs secure, scalable digital ecosystems for API-driven organisations. We combine deep technical expertise with strong API strategies, governance, and enablement models to help teams build, scale, and operate APIs effectively, turning them into strategic assets that drive innovation and sustainable digital growth. "
+  },
+  {
+    "title": "APIsFirst",
+    "href": "https://www.apisfirst.com",
+    "logo": "/partners/apisfirst.svg",
+    "description": "Provides consulting and team coaching for getting value from API-related investments and API economics, using the method to accelerate understanding and impact. Global reach with local focus in the UK and Australia. "
+  },
+  {
+    "title": "API Evangelist",
+    "href": "https://apievangelist.com/",
+    "logo": "/partners/api-evangelist-logo-butterfly-transparent.png",
+    "description": "API Evangelist is committed to helping your teams focus on the fundamentals of APIs, while also working with you to make sense of the leading edge of APIs, and where all of this is going."
+  },
+  {
+    "title": "You?",
+    "href": "https://tally.so/r/3yQEpp",
+    "logo": "/favicon.svg",
+    "description": "Join the APIOps Cycles community as a partner! Click to learn more..."
+  }
+]

From ff7a93e426086ae5b4aa29afcd8435463675aea0 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Tue, 7 Jul 2026 01:11:15 +0300
Subject: [PATCH 03/12] basic cycles support without full localization

---
 .gitignore                                  |    3 +
 package.json                                |    4 +-
 scripts/test-method-content-integrity.mjs   |  138 +-
 scripts/validate.mjs                        |    1 +
 src/data/canvas/canvasData.json             |  165 ++
 src/data/canvas/localizedData.json          |  599 ++++-
 src/data/method/cycles.json                 |  363 +++
 src/data/method/de/labels.resources.json    |   39 +-
 src/data/method/de/labels.stakeholders.json |   50 +-
 src/data/method/de/labels.stations.json     |  100 +-
 src/data/method/en/labels.cycles.json       |   93 +
 src/data/method/en/labels.lines.json        |   18 +-
 src/data/method/en/labels.resources.json    |   79 +-
 src/data/method/en/labels.stakeholders.json |   50 +-
 src/data/method/en/labels.stations.json     | 1325 ++++++++---
 src/data/method/fi/labels.cycles.json       |  107 +
 src/data/method/fi/labels.resources.json    |   37 +-
 src/data/method/fi/labels.stakeholders.json |   50 +-
 src/data/method/fi/labels.stations.json     |  846 ++++---
 src/data/method/fr/labels.resources.json    |   39 +-
 src/data/method/fr/labels.stakeholders.json |   50 +-
 src/data/method/fr/labels.stations.json     |  106 +-
 src/data/method/lines.json                  |    2 +-
 src/data/method/pt/labels.resources.json    |   39 +-
 src/data/method/pt/labels.stakeholders.json |   50 +-
 src/data/method/pt/labels.stations.json     |   98 +-
 src/data/method/resources.json              |   83 +
 src/data/method/stakeholders.json           |   89 +-
 src/data/method/station-stakeholders.json   | 2290 ++++++++++---------
 src/lib/method-engine.js                    |  218 +-
 src/schemas/cycles.schema.json              |   84 +
 src/schemas/stations.schema.json            |   56 +
 32 files changed, 5285 insertions(+), 1986 deletions(-)
 create mode 100644 src/data/method/cycles.json
 create mode 100644 src/data/method/en/labels.cycles.json
 create mode 100644 src/data/method/fi/labels.cycles.json
 create mode 100644 src/schemas/cycles.schema.json

diff --git a/.gitignore b/.gitignore
index 023f513..1400a18 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,3 +4,6 @@ node_modules
 # translation cache and temporary translation folder
 .json-autotranslate-cache
 src/data/locales/
+
+# generated method document exports
+specs/
diff --git a/package.json b/package.json
index fcd5045..9475e85 100644
--- a/package.json
+++ b/package.json
@@ -26,6 +26,7 @@
     "./localizedData.json": "./src/data/canvas/localizedData.json",
     "./method/stations.json": "./src/data/method/stations.json",
     "./method/resources.json": "./src/data/method/resources.json",
+    "./method/cycles.json": "./src/data/method/cycles.json",
     "./method/station-criteria.json": "./src/data/method/station-criteria.json",
     "./method/stakeholders.json": "./src/data/method/stakeholders.json",
     "./method/station-stakeholders.json": "./src/data/method/station-stakeholders.json",
@@ -37,7 +38,8 @@
     "release:create-apiops:publish": "npm publish --workspace packages/create-apiops --access public",
     "check:packaging:skills": "node scripts/check-packaging-skills.mjs",
     "check:package:contents": "node scripts/check-package-contents.mjs",
-    "test:create-apiops": "node scripts/test-create-apiops-scaffold.mjs && node scripts/test-method-cli.mjs && node scripts/test-run-design-audit.mjs"
+    "test:create-apiops": "node scripts/test-create-apiops-scaffold.mjs && node scripts/test-method-cli.mjs && node scripts/test-run-design-audit.mjs",
+    "test:create-apiops:integration": "node scripts/test-create-apiops-scaffold.mjs --install-integration && node scripts/test-method-cli.mjs && node scripts/test-run-design-audit.mjs"
   },
   "devDependencies": {
     "@changesets/cli": "^2.29.7",
diff --git a/scripts/test-method-content-integrity.mjs b/scripts/test-method-content-integrity.mjs
index 9d8b077..68314d7 100644
--- a/scripts/test-method-content-integrity.mjs
+++ b/scripts/test-method-content-integrity.mjs
@@ -7,6 +7,7 @@ function readJson(filePath) {
 
 const stationsJson = readJson("src/data/method/stations.json");
 const linesJson = readJson("src/data/method/lines.json");
+const cyclesJson = readJson("src/data/method/cycles.json");
 const resourcesJson = readJson("src/data/method/resources.json");
 const criteriaJson = readJson("src/data/method/criteria.json");
 const stakeholdersJson = readJson("src/data/method/stakeholders.json");
@@ -14,16 +15,18 @@ const stationCriteriaJson = readJson("src/data/method/station-criteria.json");
 const canvasDataJson = readJson("src/data/canvas/canvasData.json");
 const localizedCanvasDataJson = readJson("src/data/canvas/localizedData.json");
 const knownResourceIds = new Set((resourcesJson.resources || []).map((resource) => resource.id));
-const stationGroups = [
-  ...(stationsJson["core-stations"]?.items || []).map((station) => ({ ...station, group: "core-stations" })),
-  ...(stationsJson["sub-stations"]?.items || []).map((station) => ({ ...station, group: "sub-stations" }))
-];
+const knownCriteriaIds = new Set((criteriaJson || []).map((criterion) => criterion.id));
+const knownCycleIds = new Set((cyclesJson.cycles?.items || []).map((cycle) => cycle.id));
+const stationGroups = Object.entries(stationsJson).flatMap(([groupId, group]) => (
+  (group.items || []).map((station) => ({ ...station, group: groupId }))
+));
 const knownStationIds = new Set(stationGroups.map((station) => station.id));
 const knownCanvasIds = new Set(Object.keys(canvasDataJson));
 const localeDirs = readdirSync("src/data/method", { withFileTypes: true })
   .filter((entry) => entry.isDirectory())
   .map((entry) => entry.name);
 const findings = [];
+const warnings = [];
 const lifecycleStages = new Set(["strategy", "architecture", "design", "delivery", "publishing", "improving"]);
 
 function collectMatchingStringValues(node, pattern, results = new Set()) {
@@ -52,12 +55,15 @@ function collectMatchingStringValues(node, pattern, results = new Set()) {
 
 function validateLabelFile(locale, filename, expectedKeys, allowedExtras = []) {
   const filePath = path.join("src", "data", "method", locale, filename);
+  const fallbackFilePath = path.join("src", "data", "method", "en", filename);
   const labels = readJson(filePath);
+  const fallbackLabels = readJson(fallbackFilePath);
   const actualKeys = new Set(Object.keys(labels));
+  const fallbackKeys = new Set(Object.keys(fallbackLabels));
   const allowedExtrasSet = new Set(allowedExtras);
 
   for (const expectedKey of expectedKeys) {
-    if (!actualKeys.has(expectedKey)) {
+    if (!actualKeys.has(expectedKey) && !fallbackKeys.has(expectedKey)) {
       findings.push(`Locale ${locale} is missing label "${expectedKey}" in ${filename}.`);
     }
   }
@@ -93,7 +99,7 @@ for (const station of stationGroups) {
     }
 
     if (seenResources.has(resourceId)) {
-      findings.push(
+      warnings.push(
         `Station ${station.id} contains duplicate resource reference "${resourceId}" at indexes ${seenResources.get(resourceId)} and ${index}.`
       );
     } else {
@@ -122,6 +128,58 @@ for (const station of stationGroups) {
       findings.push(`Core station ${station.id} must define expectedEvidenceTags.`);
     }
   }
+
+  if (station.group === "sub-stations") {
+    if (station.type !== "supporting-station") {
+      findings.push(`Substation ${station.id} must have type "supporting-station".`);
+    }
+
+    const applicableCycles = new Set(station.applicableCycles || []);
+    if (applicableCycles.size === 0) {
+      findings.push(`Substation ${station.id} must define applicableCycles.`);
+    }
+
+    for (const cycleId of applicableCycles) {
+      if (!knownCycleIds.has(cycleId)) {
+        findings.push(`Substation ${station.id} applicableCycles references unknown cycle "${cycleId}".`);
+      }
+    }
+
+    for (const cycleId of station.defaultForCycles || []) {
+      if (!knownCycleIds.has(cycleId)) {
+        findings.push(`Substation ${station.id} defaultForCycles references unknown cycle "${cycleId}".`);
+      }
+      if (!applicableCycles.has(cycleId)) {
+        findings.push(`Substation ${station.id} defaultForCycles contains "${cycleId}" that is not in applicableCycles.`);
+      }
+    }
+
+    for (const cycleId of Object.keys(station.cycleSpecificLabels || {})) {
+      if (!knownCycleIds.has(cycleId)) {
+        findings.push(`Substation ${station.id} cycleSpecificLabels references unknown cycle "${cycleId}".`);
+      }
+    }
+
+    for (const cycleId of Object.keys(station.cycleSpecificDescriptions || {})) {
+      if (!knownCycleIds.has(cycleId)) {
+        findings.push(`Substation ${station.id} cycleSpecificDescriptions references unknown cycle "${cycleId}".`);
+      }
+    }
+
+    for (const [cycleId, resourceIds] of Object.entries(station.cycleSpecificResources || {})) {
+      if (!knownCycleIds.has(cycleId)) {
+        findings.push(`Substation ${station.id} cycleSpecificResources references unknown cycle "${cycleId}".`);
+      }
+      if (!applicableCycles.has(cycleId)) {
+        findings.push(`Substation ${station.id} cycleSpecificResources contains "${cycleId}" that is not in applicableCycles.`);
+      }
+      for (const resourceId of resourceIds || []) {
+        if (!knownResourceIds.has(resourceId)) {
+          findings.push(`Substation ${station.id} cycleSpecificResources for "${cycleId}" references unknown resource "${resourceId}".`);
+        }
+      }
+    }
+  }
 }
 
 for (const line of linesJson.lines?.items || []) {
@@ -142,6 +200,63 @@ for (const line of linesJson.lines?.items || []) {
   }
 }
 
+for (const cycle of cyclesJson.cycles?.items || []) {
+  const seenStations = new Map();
+
+  for (const [index, stationId] of (cycle.stations || []).entries()) {
+    if (seenStations.has(stationId)) {
+      findings.push(
+        `Cycle ${cycle.id} contains duplicate station "${stationId}" at indexes ${seenStations.get(stationId)} and ${index}.`
+      );
+    } else {
+      seenStations.set(stationId, index);
+    }
+
+    if (!knownStationIds.has(stationId)) {
+      findings.push(`Cycle ${cycle.id} references unknown station "${stationId}" at index ${index}.`);
+    }
+  }
+
+  for (const [stationId, resourceIds] of Object.entries(cycle.recommendedResources || {})) {
+    if (!knownStationIds.has(stationId)) {
+      findings.push(`Cycle ${cycle.id} recommends resources for unknown station "${stationId}".`);
+    }
+    for (const resourceId of resourceIds || []) {
+      if (!knownResourceIds.has(resourceId)) {
+        findings.push(`Cycle ${cycle.id} recommends unknown resource "${resourceId}" for station "${stationId}".`);
+      }
+    }
+  }
+
+  for (const [index, entry] of (cycle.questionnaireResources || []).entries()) {
+    if (!knownStationIds.has(entry.station)) {
+      findings.push(`Cycle ${cycle.id} questionnaire resource at index ${index} references unknown station "${entry.station}".`);
+    }
+    if (!knownResourceIds.has(entry.resource)) {
+      findings.push(`Cycle ${cycle.id} questionnaire resource at index ${index} references unknown resource "${entry.resource}".`);
+    }
+  }
+
+  for (const [index, overlay] of (cycle.overlays || []).entries()) {
+    if (!knownStationIds.has(overlay.station)) {
+      findings.push(`Cycle ${cycle.id} overlay at index ${index} references unknown station "${overlay.station}".`);
+    }
+  }
+
+  for (const criterionId of cycle.entryCriteria || []) {
+    if (!knownCriteriaIds.has(criterionId)) {
+      findings.push(`Cycle ${cycle.id} entryCriteria references unknown criterion "${criterionId}".`);
+    }
+  }
+
+  for (const criterionId of cycle.exitCriteria || []) {
+    if (!knownCriteriaIds.has(criterionId)) {
+      findings.push(`Cycle ${cycle.id} exitCriteria references unknown criterion "${criterionId}".`);
+    }
+  }
+
+}
+
 const stationsUsedInLines = new Set(
   (linesJson.lines?.items || []).flatMap((line) => line.stations || [])
 );
@@ -170,6 +285,7 @@ for (const resource of resourcesJson.resources || []) {
 
 const expectedStationLabels = collectMatchingStringValues(stationsJson, /^(group|station)\./);
 const expectedLineLabels = collectMatchingStringValues(linesJson, /^(lines|line)\./);
+const expectedCycleLabels = collectMatchingStringValues(cyclesJson, /^(cycle|cycles)\./);
 const expectedResourceLabels = collectMatchingStringValues(resourcesJson, /^resource\./);
 const expectedCriteriaLabels = new Set(criteriaJson.map((criterion) => `criterion.${criterion.id}`));
 const expectedStakeholderLabels = collectMatchingStringValues(stakeholdersJson, /^stakeholder\./);
@@ -177,6 +293,9 @@ const expectedStakeholderLabels = collectMatchingStringValues(stakeholdersJson,
 for (const locale of localeDirs) {
   validateLabelFile(locale, "labels.stations.json", expectedStationLabels);
   validateLabelFile(locale, "labels.lines.json", expectedLineLabels);
+  if (locale === "en" || existsSync(path.join("src", "data", "method", locale, "labels.cycles.json"))) {
+    validateLabelFile(locale, "labels.cycles.json", expectedCycleLabels);
+  }
   validateLabelFile(locale, "labels.resources.json", expectedResourceLabels);
   validateLabelFile(locale, "labels.criteria.json", expectedCriteriaLabels, ["entry_criteria", "exit_criteria"]);
   validateLabelFile(
@@ -236,4 +355,11 @@ if (findings.length > 0) {
   process.exit(1);
 }
 
+if (warnings.length > 0) {
+  console.log("Method content validation warnings:");
+  for (const warning of warnings) {
+    console.log(`- ${warning}`);
+  }
+}
+
 console.log("Method content validation passed.");
diff --git a/scripts/validate.mjs b/scripts/validate.mjs
index fd07460..8a6984e 100644
--- a/scripts/validate.mjs
+++ b/scripts/validate.mjs
@@ -50,6 +50,7 @@ async function gatherTemplateFiles() {
 (async () => {
   await validate('src/schemas/criteria.schema.json', ['src/data/method/criteria.json']);
   await validate('src/schemas/lines.schema.json', ['src/data/method/lines.json']);
+  await validate('src/schemas/cycles.schema.json', ['src/data/method/cycles.json']);
   await validate('src/schemas/resources.schema.json', ['src/data/method/resources.json']);
   await validate('src/schemas/stakeholders.schema.json', ['src/data/method/stakeholders.json']);
   await validate('src/schemas/station-criteria.schema.json', ['src/data/method/station-criteria.json']);
diff --git a/src/data/canvas/canvasData.json b/src/data/canvas/canvasData.json
index d3b433a..6be5b7c 100644
--- a/src/data/canvas/canvasData.json
+++ b/src/data/canvas/canvasData.json
@@ -568,5 +568,170 @@
         "fillOrder": 10
       }
     ]
+  },
+  "capabilityValuePropositionCanvas": {
+    "id": "capabilityValuePropositionCanvas",
+    "layout": {
+      "columns": 4,
+      "rows": 3
+    },
+    "metadata": {
+      "source": "APIOps Cycles",
+      "license": "CC-BY-SA 4.0",
+      "authors": ["Osaango Ltd"],
+      "website": "www.apiopscycles.com"
+    },
+    "sections": [
+      {
+        "id": "consumerTasks",
+        "gridPosition": { "column": 0, "row": 0, "colSpan": 4, "rowSpan": 1 },
+        "fillOrder": 1,
+        "highlight": true,
+        "journeySteps": true
+      },
+      {
+        "id": "gainEnablingCapabilities",
+        "gridPosition": { "column": 0, "row": 1, "colSpan": 2, "rowSpan": 1 },
+        "fillOrder": 2
+      },
+      {
+        "id": "painRelievingCapabilities",
+        "gridPosition": { "column": 2, "row": 1, "colSpan": 2, "rowSpan": 1 },
+        "fillOrder": 3
+      },
+      {
+        "id": "reusableCapabilities",
+        "gridPosition": { "column": 0, "row": 2, "colSpan": 4, "rowSpan": 1 },
+        "fillOrder": 4
+      }
+    ]
+  },
+  "capabilityBusinessModelCanvas": {
+    "id": "capabilityBusinessModelCanvas",
+    "layout": {
+      "columns": 5,
+      "rows": 3
+    },
+    "metadata": {
+      "source": "APIOps Cycles",
+      "license": "CC-BY-SA 4.0",
+      "authors": ["Osaango Ltd"],
+      "website": "www.apiopscycles.com"
+    },
+    "sections": [
+      {
+        "id": "keyPartners",
+        "gridPosition": { "column": 0, "row": 0, "colSpan": 1, "rowSpan": 2 },
+        "fillOrder": 7
+      },
+      {
+        "id": "keyActivities",
+        "gridPosition": { "column": 1, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 6
+      },
+      {
+        "id": "keyResources",
+        "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 5
+      },
+      {
+        "id": "capabilityValueProposition",
+        "gridPosition": { "column": 2, "row": 0, "colSpan": 1, "rowSpan": 2 },
+        "fillOrder": 1,
+        "highlight": true
+      },
+      {
+        "id": "consumerEngagement",
+        "gridPosition": { "column": 3, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 3
+      },
+      {
+        "id": "channels",
+        "gridPosition": { "column": 3, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 4
+      },
+      {
+        "id": "capabilityConsumerSegments",
+        "gridPosition": { "column": 4, "row": 0, "colSpan": 1, "rowSpan": 2 },
+        "fillOrder": 2
+      },
+      {
+        "id": "costs",
+        "gridPosition": { "column": 0, "row": 2, "colSpan": 2.5, "rowSpan": 1 },
+        "fillOrder": 9
+      },
+      {
+        "id": "benefits",
+        "gridPosition": { "column": 2.5, "row": 2, "colSpan": 2.5, "rowSpan": 1 },
+        "fillOrder": 8
+      }
+    ]
+  },
+  "consumerExperienceRequirementsCanvas": {
+    "id": "consumerExperienceRequirementsCanvas",
+    "layout": {
+      "columns": 4,
+      "rows": 3
+    },
+    "metadata": {
+      "source": "APIOps Cycles",
+      "license": "CC-BY-SA 4.0",
+      "authors": ["Osaango Ltd"],
+      "website": "www.apiopscycles.com"
+    },
+    "sections": [
+      {
+        "id": "consumerGoals",
+        "gridPosition": { "column": 0, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 1,
+        "highlight": true
+      },
+      {
+        "id": "availabilityAndTimeliness",
+        "gridPosition": { "column": 1, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 2
+      },
+      {
+        "id": "volumeAndPerformance",
+        "gridPosition": { "column": 2, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 3
+      },
+      {
+        "id": "dataQualityAndConsistency",
+        "gridPosition": { "column": 3, "row": 0, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 4
+      },
+      {
+        "id": "securityPrivacyAndCompliance",
+        "gridPosition": { "column": 0, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 5
+      },
+      {
+        "id": "onboardingAndAccess",
+        "gridPosition": { "column": 1, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 6
+      },
+      {
+        "id": "changeAndVersioning",
+        "gridPosition": { "column": 2, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 7
+      },
+      {
+        "id": "observabilityAndSupport",
+        "gridPosition": { "column": 3, "row": 1, "colSpan": 1, "rowSpan": 1 },
+        "fillOrder": 8
+      },
+      {
+        "id": "recoveryAndContinuity",
+        "gridPosition": { "column": 0, "row": 2, "colSpan": 2, "rowSpan": 1 },
+        "fillOrder": 9
+      },
+      {
+        "id": "architectureImplications",
+        "gridPosition": { "column": 2, "row": 2, "colSpan": 2, "rowSpan": 1 },
+        "fillOrder": 10,
+        "highlight": true
+      }
+    ]
   }
 }
diff --git a/src/data/canvas/localizedData.json b/src/data/canvas/localizedData.json
index b6892f9..4ac8ef2 100644
--- a/src/data/canvas/localizedData.json
+++ b/src/data/canvas/localizedData.json
@@ -384,6 +384,119 @@
           "description": "Gibt es noch offene Entscheidungen oder Integrationsüberlegungen?"
         }
       }
+    },
+    "capabilityValuePropositionCanvas": {
+      "title": "Capability Value Proposition Canvas",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "sections": {
+        "consumerTasks": {
+          "section": "Consumer tasks and outcomes",
+          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+        },
+        "gainEnablingCapabilities": {
+          "section": "Gain-enabling capability features",
+          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+        },
+        "painRelievingCapabilities": {
+          "section": "Pain-relieving capability features",
+          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+        },
+        "reusableCapabilities": {
+          "section": "Reusable capabilities",
+          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+        }
+      }
+    },
+    "capabilityBusinessModelCanvas": {
+      "title": "Capability Business Model Canvas",
+      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
+      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "sections": {
+        "keyPartners": {
+          "section": "Key partners",
+          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+        },
+        "keyActivities": {
+          "section": "Key activities",
+          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+        },
+        "keyResources": {
+          "section": "Key resources",
+          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+        },
+        "capabilityValueProposition": {
+          "section": "Capability value proposition",
+          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+        },
+        "consumerEngagement": {
+          "section": "Consumer engagement",
+          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+        },
+        "channels": {
+          "section": "Channels",
+          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+        },
+        "capabilityConsumerSegments": {
+          "section": "Capability consumer segments",
+          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+        },
+        "costs": {
+          "section": "Costs",
+          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+        },
+        "benefits": {
+          "section": "Benefits",
+          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+        }
+      }
+    },
+    "consumerExperienceRequirementsCanvas": {
+      "title": "Consumer Experience Requirements Canvas",
+      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "sections": {
+        "consumerGoals": {
+          "section": "Consumer goals",
+          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+        },
+        "availabilityAndTimeliness": {
+          "section": "Availability and timeliness",
+          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+        },
+        "volumeAndPerformance": {
+          "section": "Volume and performance",
+          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+        },
+        "dataQualityAndConsistency": {
+          "section": "Data quality and consistency",
+          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+        },
+        "securityPrivacyAndCompliance": {
+          "section": "Security, privacy, and compliance",
+          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+        },
+        "onboardingAndAccess": {
+          "section": "Onboarding and access",
+          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+        },
+        "changeAndVersioning": {
+          "section": "Change and versioning",
+          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+        },
+        "observabilityAndSupport": {
+          "section": "Observability and support",
+          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+        },
+        "recoveryAndContinuity": {
+          "section": "Recovery and continuity",
+          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+        },
+        "architectureImplications": {
+          "section": "Architecture implications",
+          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+        }
+      }
     }
   },
   "en": {
@@ -455,16 +568,16 @@
     },
     "businessImpactCanvas": {
       "title": "Business Impact Canvas",
-      "purpose": "What are the potential business impacts of API failure?",
-      "howToUse": "Consider the potential impact on availability, security, and data for each API.",
+      "purpose": "What are the potential business impacts if the capability, integration, or service fails?",
+      "howToUse": "Consider the potential impact on availability, security, and data for each capability, integration, or service.",
       "sections": {
         "availabilityRisks": {
           "section": "Availability Risks",
-          "description": "What are the potential risks to API availability?"
+          "description": "What are the potential risks to capability availability?"
         },
         "securityRisks": {
           "section": "Security Risks",
-          "description": "What are the potential security risks associated with the API?"
+          "description": "What are the potential security risks associated with the capability?"
         },
         "dataRisks": {
           "section": "Data Risks",
@@ -472,22 +585,22 @@
         },
         "mitigateAvailabilityRisks": {
           "section": "Mitigate Availability Risks",
-          "description": "How can the API provider mitigate the availability risks?"
+          "description": "How can the capability owner mitigate the availability risks?"
         },
         "mitigateSecurityRisks": {
           "section": "Mitigate Security Risks",
-          "description": "How can the API provider mitigate the security risks?"
+          "description": "How can the capability owner mitigate the security risks?"
         },
         "mitigateDataRisks": {
           "section": "Mitigate Data Risks",
-          "description": "How can the API provider mitigate the data risks?"
+          "description": "How can the capability owner mitigate the data risks?"
         }
       }
     },
     "capacityCanvas": {
       "title": "Capacity Canvas",
-      "purpose": "How much capacity is needed to support API consumption?",
-      "howToUse": "Analyze the current and future capacity requirements for each API.",
+      "purpose": "How much capacity is needed to support expected capability consumption?",
+      "howToUse": "Analyze the current and future capacity requirements for each capability, integration, or service.",
       "sections": {
         "currentBusinessVolumes": {
           "section": "Current Business Volumes",
@@ -517,8 +630,8 @@
     },
     "customerJourneyCanvas": {
       "title": "Customer Journey Canvas",
-      "purpose": "What is the customer or partner journey that the API is intended to support?",
-      "howToUse": "In API Product Strategy, describe the real-life customer or partner journey, not the API usage, to reveal pain points, goals, and context. In API Consumer Experience, use this canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
+      "purpose": "What customer, partner, or consumer journey is the capability intended to support?",
+      "howToUse": "Describe the real-life customer, partner, or consumer journey, not the solution usage itself, to reveal pain points, goals, context, inputs, outputs, and experience expectations.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "Customer Discovers Need",
@@ -556,8 +669,8 @@
     },
     "domainCanvas": {
       "title": "Domain Canvas",
-      "purpose": "What are the core entities and business rules related to the API?",
-      "howToUse": "Define the domain model for each API, including entities, attributes, and relationships.",
+      "purpose": "What are the core entities and business rules related to this capability or domain?",
+      "howToUse": "Define the domain model, including entities, attributes, relationships, ownership, and business rules.",
       "sections": {
         "selectedCustomerJourneySteps": {
           "section": "Selected Customer Journey Steps",
@@ -610,8 +723,8 @@
     },
     "interactionCanvas": {
       "title": "Interaction Canvas",
-      "purpose": "What kinds of interactions should this API support before choosing a protocol-specific design?",
-      "howToUse": "Identify which interaction styles are actually needed for this API, and which are out of scope. Use this canvas to clarify intent before mapping the result to REST, events, or GraphQL.",
+      "purpose": "What kinds of interactions should this capability support before choosing a protocol-specific design?",
+      "howToUse": "Identify which interaction styles are actually needed for this capability, and which are out of scope. Use this canvas to clarify intent before mapping the result to REST, events, GraphQL, or another selected pattern.",
       "sections": {
         "crudInteractions": {
           "section": "CRUD Interactions",
@@ -665,8 +778,8 @@
     },
     "locationsCanvas": {
       "title": "Locations Canvas",
-      "purpose": "What geopolitical, regulatory, network, and trust boundaries affect this API?",
-      "howToUse": "Identify where API consumers, providers, and dependent systems operate across internal networks, partner networks, public internet, and regulated regions. Describe the latency, trust, compliance, and connectivity implications between them.",
+      "purpose": "What geopolitical, regulatory, network, and trust boundaries affect this capability or integration?",
+      "howToUse": "Identify where consumers, producers, and dependent systems operate across internal networks, partner networks, public internet, and regulated regions. Describe the latency, trust, compliance, and connectivity implications between them.",
       "sections": {
         "locationGroups": {
           "section": "Location / Trust Groups",
@@ -771,6 +884,119 @@
           "description": "Any pending decisions or integration considerations?"
         }
       }
+    },
+    "capabilityValuePropositionCanvas": {
+      "title": "Capability Value Proposition Canvas",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "sections": {
+        "consumerTasks": {
+          "section": "Consumer tasks and outcomes",
+          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+        },
+        "gainEnablingCapabilities": {
+          "section": "Gain-enabling capability features",
+          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+        },
+        "painRelievingCapabilities": {
+          "section": "Pain-relieving capability features",
+          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+        },
+        "reusableCapabilities": {
+          "section": "Reusable capabilities",
+          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+        }
+      }
+    },
+    "capabilityBusinessModelCanvas": {
+      "title": "Capability Business Model Canvas",
+      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
+      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "sections": {
+        "keyPartners": {
+          "section": "Key partners",
+          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+        },
+        "keyActivities": {
+          "section": "Key activities",
+          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+        },
+        "keyResources": {
+          "section": "Key resources",
+          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+        },
+        "capabilityValueProposition": {
+          "section": "Capability value proposition",
+          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+        },
+        "consumerEngagement": {
+          "section": "Consumer engagement",
+          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+        },
+        "channels": {
+          "section": "Channels",
+          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+        },
+        "capabilityConsumerSegments": {
+          "section": "Capability consumer segments",
+          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+        },
+        "costs": {
+          "section": "Costs",
+          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+        },
+        "benefits": {
+          "section": "Benefits",
+          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+        }
+      }
+    },
+    "consumerExperienceRequirementsCanvas": {
+      "title": "Consumer Experience Requirements Canvas",
+      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "sections": {
+        "consumerGoals": {
+          "section": "Consumer goals",
+          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+        },
+        "availabilityAndTimeliness": {
+          "section": "Availability and timeliness",
+          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+        },
+        "volumeAndPerformance": {
+          "section": "Volume and performance",
+          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+        },
+        "dataQualityAndConsistency": {
+          "section": "Data quality and consistency",
+          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+        },
+        "securityPrivacyAndCompliance": {
+          "section": "Security, privacy, and compliance",
+          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+        },
+        "onboardingAndAccess": {
+          "section": "Onboarding and access",
+          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+        },
+        "changeAndVersioning": {
+          "section": "Change and versioning",
+          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+        },
+        "observabilityAndSupport": {
+          "section": "Observability and support",
+          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+        },
+        "recoveryAndContinuity": {
+          "section": "Recovery and continuity",
+          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+        },
+        "architectureImplications": {
+          "section": "Architecture implications",
+          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+        }
+      }
     }
   },
   "fi": {
@@ -1158,6 +1384,119 @@
           "description": "Onko keskeneräisiä päätöksiä tai integraatioon liittyviä huomioita?"
         }
       }
+    },
+    "capabilityValuePropositionCanvas": {
+      "title": "Capability Value Proposition Canvas",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "sections": {
+        "consumerTasks": {
+          "section": "Consumer tasks and outcomes",
+          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+        },
+        "gainEnablingCapabilities": {
+          "section": "Gain-enabling capability features",
+          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+        },
+        "painRelievingCapabilities": {
+          "section": "Pain-relieving capability features",
+          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+        },
+        "reusableCapabilities": {
+          "section": "Reusable capabilities",
+          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+        }
+      }
+    },
+    "capabilityBusinessModelCanvas": {
+      "title": "Capability Business Model Canvas",
+      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
+      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "sections": {
+        "keyPartners": {
+          "section": "Key partners",
+          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+        },
+        "keyActivities": {
+          "section": "Key activities",
+          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+        },
+        "keyResources": {
+          "section": "Key resources",
+          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+        },
+        "capabilityValueProposition": {
+          "section": "Capability value proposition",
+          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+        },
+        "consumerEngagement": {
+          "section": "Consumer engagement",
+          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+        },
+        "channels": {
+          "section": "Channels",
+          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+        },
+        "capabilityConsumerSegments": {
+          "section": "Capability consumer segments",
+          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+        },
+        "costs": {
+          "section": "Costs",
+          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+        },
+        "benefits": {
+          "section": "Benefits",
+          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+        }
+      }
+    },
+    "consumerExperienceRequirementsCanvas": {
+      "title": "Consumer Experience Requirements Canvas",
+      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "sections": {
+        "consumerGoals": {
+          "section": "Consumer goals",
+          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+        },
+        "availabilityAndTimeliness": {
+          "section": "Availability and timeliness",
+          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+        },
+        "volumeAndPerformance": {
+          "section": "Volume and performance",
+          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+        },
+        "dataQualityAndConsistency": {
+          "section": "Data quality and consistency",
+          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+        },
+        "securityPrivacyAndCompliance": {
+          "section": "Security, privacy, and compliance",
+          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+        },
+        "onboardingAndAccess": {
+          "section": "Onboarding and access",
+          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+        },
+        "changeAndVersioning": {
+          "section": "Change and versioning",
+          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+        },
+        "observabilityAndSupport": {
+          "section": "Observability and support",
+          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+        },
+        "recoveryAndContinuity": {
+          "section": "Recovery and continuity",
+          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+        },
+        "architectureImplications": {
+          "section": "Architecture implications",
+          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+        }
+      }
     }
   },
   "fr": {
@@ -1545,6 +1884,119 @@
           "description": "Y a-t-il des décisions en attente ou des considérations d'intégration ?"
         }
       }
+    },
+    "capabilityValuePropositionCanvas": {
+      "title": "Capability Value Proposition Canvas",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "sections": {
+        "consumerTasks": {
+          "section": "Consumer tasks and outcomes",
+          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+        },
+        "gainEnablingCapabilities": {
+          "section": "Gain-enabling capability features",
+          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+        },
+        "painRelievingCapabilities": {
+          "section": "Pain-relieving capability features",
+          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+        },
+        "reusableCapabilities": {
+          "section": "Reusable capabilities",
+          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+        }
+      }
+    },
+    "capabilityBusinessModelCanvas": {
+      "title": "Capability Business Model Canvas",
+      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
+      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "sections": {
+        "keyPartners": {
+          "section": "Key partners",
+          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+        },
+        "keyActivities": {
+          "section": "Key activities",
+          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+        },
+        "keyResources": {
+          "section": "Key resources",
+          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+        },
+        "capabilityValueProposition": {
+          "section": "Capability value proposition",
+          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+        },
+        "consumerEngagement": {
+          "section": "Consumer engagement",
+          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+        },
+        "channels": {
+          "section": "Channels",
+          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+        },
+        "capabilityConsumerSegments": {
+          "section": "Capability consumer segments",
+          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+        },
+        "costs": {
+          "section": "Costs",
+          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+        },
+        "benefits": {
+          "section": "Benefits",
+          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+        }
+      }
+    },
+    "consumerExperienceRequirementsCanvas": {
+      "title": "Consumer Experience Requirements Canvas",
+      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "sections": {
+        "consumerGoals": {
+          "section": "Consumer goals",
+          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+        },
+        "availabilityAndTimeliness": {
+          "section": "Availability and timeliness",
+          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+        },
+        "volumeAndPerformance": {
+          "section": "Volume and performance",
+          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+        },
+        "dataQualityAndConsistency": {
+          "section": "Data quality and consistency",
+          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+        },
+        "securityPrivacyAndCompliance": {
+          "section": "Security, privacy, and compliance",
+          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+        },
+        "onboardingAndAccess": {
+          "section": "Onboarding and access",
+          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+        },
+        "changeAndVersioning": {
+          "section": "Change and versioning",
+          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+        },
+        "observabilityAndSupport": {
+          "section": "Observability and support",
+          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+        },
+        "recoveryAndContinuity": {
+          "section": "Recovery and continuity",
+          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+        },
+        "architectureImplications": {
+          "section": "Architecture implications",
+          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+        }
+      }
     }
   },
   "pt": {
@@ -1932,6 +2384,119 @@
           "description": "Alguma decisão pendente ou considerações sobre integração?"
         }
       }
+    },
+    "capabilityValuePropositionCanvas": {
+      "title": "Capability Value Proposition Canvas",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "sections": {
+        "consumerTasks": {
+          "section": "Consumer tasks and outcomes",
+          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+        },
+        "gainEnablingCapabilities": {
+          "section": "Gain-enabling capability features",
+          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+        },
+        "painRelievingCapabilities": {
+          "section": "Pain-relieving capability features",
+          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+        },
+        "reusableCapabilities": {
+          "section": "Reusable capabilities",
+          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+        }
+      }
+    },
+    "capabilityBusinessModelCanvas": {
+      "title": "Capability Business Model Canvas",
+      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
+      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "sections": {
+        "keyPartners": {
+          "section": "Key partners",
+          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+        },
+        "keyActivities": {
+          "section": "Key activities",
+          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+        },
+        "keyResources": {
+          "section": "Key resources",
+          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+        },
+        "capabilityValueProposition": {
+          "section": "Capability value proposition",
+          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+        },
+        "consumerEngagement": {
+          "section": "Consumer engagement",
+          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+        },
+        "channels": {
+          "section": "Channels",
+          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+        },
+        "capabilityConsumerSegments": {
+          "section": "Capability consumer segments",
+          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+        },
+        "costs": {
+          "section": "Costs",
+          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+        },
+        "benefits": {
+          "section": "Benefits",
+          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+        }
+      }
+    },
+    "consumerExperienceRequirementsCanvas": {
+      "title": "Consumer Experience Requirements Canvas",
+      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "sections": {
+        "consumerGoals": {
+          "section": "Consumer goals",
+          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+        },
+        "availabilityAndTimeliness": {
+          "section": "Availability and timeliness",
+          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+        },
+        "volumeAndPerformance": {
+          "section": "Volume and performance",
+          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+        },
+        "dataQualityAndConsistency": {
+          "section": "Data quality and consistency",
+          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+        },
+        "securityPrivacyAndCompliance": {
+          "section": "Security, privacy, and compliance",
+          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+        },
+        "onboardingAndAccess": {
+          "section": "Onboarding and access",
+          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+        },
+        "changeAndVersioning": {
+          "section": "Change and versioning",
+          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+        },
+        "observabilityAndSupport": {
+          "section": "Observability and support",
+          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+        },
+        "recoveryAndContinuity": {
+          "section": "Recovery and continuity",
+          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+        },
+        "architectureImplications": {
+          "section": "Architecture implications",
+          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+        }
+      }
     }
   }
 }
diff --git a/src/data/method/cycles.json b/src/data/method/cycles.json
new file mode 100644
index 0000000..ee1b679
--- /dev/null
+++ b/src/data/method/cycles.json
@@ -0,0 +1,363 @@
+{
+  "cycles": {
+    "title": "cycles.title",
+    "slug": "cycles",
+    "order": 0,
+    "description": "cycles.description",
+    "items": [
+      {
+        "id": "capability-productization-cycle",
+        "title": "cycle.capability-productization-cycle.title",
+        "slug": "capability-productization-cycle",
+        "description": "cycle.capability-productization-cycle.description",
+        "purpose": "cycle.capability-productization-cycle.purpose",
+        "stations": [
+          "api-product-strategy",
+          "api-consumer-experience",
+          "api-platform-architecture",
+          "api-design",
+          "api-delivery",
+          "api-audit",
+          "api-publishing",
+          "monitoring-and-improving"
+        ],
+        "stationLabels": {
+          "api-product-strategy": "cycle.station.capability-strategy",
+          "api-consumer-experience": "cycle.station.consumer-requirements-onboarding",
+          "api-platform-architecture": "cycle.station.architecture-platform-decisions",
+          "api-design": "cycle.station.solution-interface-design",
+          "api-delivery": "cycle.station.delivery-operations",
+          "api-audit": "cycle.station.quality-readiness-assurance",
+          "api-publishing": "cycle.station.publishing-enablement",
+          "monitoring-and-improving": "cycle.station.monitoring-improvement"
+        },
+        "stationDescriptions": {
+          "api-product-strategy": "cycle.capability-productization-cycle.station.api-product-strategy.description",
+          "api-consumer-experience": "cycle.capability-productization-cycle.station.api-consumer-experience.description",
+          "api-platform-architecture": "cycle.capability-productization-cycle.station.api-platform-architecture.description",
+          "api-design": "cycle.capability-productization-cycle.station.api-design.description",
+          "api-delivery": "cycle.capability-productization-cycle.station.api-delivery.description",
+          "api-audit": "cycle.capability-productization-cycle.station.api-audit.description",
+          "api-publishing": "cycle.capability-productization-cycle.station.api-publishing.description",
+          "monitoring-and-improving": "cycle.capability-productization-cycle.station.monitoring-and-improving.description"
+        },
+        "recommendedResources": {
+          "api-product-strategy": [
+            "customerJourneyCanvas",
+            "domainCanvas",
+            "capabilityValuePropositionCanvas",
+            "capabilityBusinessModelCanvas"
+          ],
+          "api-consumer-experience": [
+            "consumerExperienceRequirementsCanvas",
+            "api-onboarding-best-practices"
+          ],
+          "api-platform-architecture": [
+            "businessImpactCanvas",
+            "locationsCanvas",
+            "capacityCanvas"
+          ],
+          "api-design": [
+            "domainCanvas",
+            "interactionCanvas",
+            "contract-first-design"
+          ],
+          "api-delivery": [
+            "api-development-best-practices",
+            "api-testing-best-practices",
+            "apiops-CI-CD-for-apis"
+          ],
+          "api-audit": [
+            "api-audit-checklist",
+            "api-compliance-best-practices"
+          ],
+          "api-publishing": [
+            "api-onboarding-best-practices",
+            "service-agreement-template"
+          ],
+          "monitoring-and-improving": [
+            "api-metrics-and-analytics",
+            "api-community-engagement-strategies"
+          ]
+        },
+        "entryCriteria": [
+          "business-goals-defined",
+          "stakeholder-approval"
+        ],
+        "exitCriteria": [
+          "value-prop-validated",
+          "architecture-patterns-validated",
+          "audit-passed"
+        ]
+      },
+      {
+        "id": "api-productization-cycle",
+        "title": "cycle.api-productization-cycle.title",
+        "slug": "api-productization-cycle",
+        "description": "cycle.api-productization-cycle.description",
+        "purpose": "cycle.api-productization-cycle.purpose",
+        "stations": [
+          "api-product-strategy",
+          "api-consumer-experience",
+          "api-platform-architecture",
+          "api-design",
+          "api-delivery",
+          "api-audit",
+          "api-publishing",
+          "monitoring-and-improving"
+        ],
+        "stationLabels": {
+          "api-product-strategy": "cycle.station.api-product-strategy",
+          "api-consumer-experience": "cycle.station.api-consumer-experience",
+          "api-platform-architecture": "cycle.station.api-platform-architecture",
+          "api-design": "cycle.station.api-design",
+          "api-delivery": "cycle.station.api-delivery",
+          "api-audit": "cycle.station.api-audit",
+          "api-publishing": "cycle.station.api-publishing",
+          "monitoring-and-improving": "cycle.station.monitoring-and-improving"
+        },
+        "recommendedResources": {
+          "api-product-strategy": [
+            "customerJourneyCanvas",
+            "domainCanvas",
+            "apiValuePropositionCanvas",
+            "apiBusinessModelCanvas"
+          ],
+          "api-consumer-experience": [
+            "apiValuePropositionCanvas",
+            "customerJourneyCanvas",
+            "api-onboarding-best-practices"
+          ],
+          "api-platform-architecture": [
+            "businessImpactCanvas",
+            "locationsCanvas",
+            "capacityCanvas",
+            "api-metrics-and-analytics"
+          ],
+          "api-design": [
+            "domainCanvas",
+            "interactionCanvas",
+            "restCanvas",
+            "eventCanvas",
+            "graphqlCanvas",
+            "api-design-principles",
+            "contract-first-design"
+          ],
+          "api-delivery": [
+            "api-development-best-practices",
+            "api-testing-best-practices",
+            "apiops-CI-CD-for-apis",
+            "api-security-best-practices"
+          ],
+          "api-audit": [
+            "api-audit-checklist",
+            "api-compliance-best-practices"
+          ],
+          "api-publishing": [
+            "apiops-CI-CD-for-apis",
+            "api-onboarding-best-practices",
+            "api-audit-checklist"
+          ],
+          "monitoring-and-improving": [
+            "api-metrics-and-analytics",
+            "api-community-engagement-strategies"
+          ]
+        },
+        "entryCriteria": [
+          "api-opportunity-documented",
+          "consumer-segments-identified"
+        ],
+        "exitCriteria": [
+          "api-contract-tested",
+          "api-ready-for-publishing",
+          "api-documentation-ready"
+        ],
+        "stationDescriptions": {
+          "api-product-strategy": "cycle.api-productization-cycle.station.api-product-strategy.description",
+          "api-consumer-experience": "cycle.api-productization-cycle.station.api-consumer-experience.description",
+          "api-platform-architecture": "cycle.api-productization-cycle.station.api-platform-architecture.description",
+          "api-design": "cycle.api-productization-cycle.station.api-design.description",
+          "api-delivery": "cycle.api-productization-cycle.station.api-delivery.description",
+          "api-audit": "cycle.api-productization-cycle.station.api-audit.description",
+          "api-publishing": "cycle.api-productization-cycle.station.api-publishing.description",
+          "monitoring-and-improving": "cycle.api-productization-cycle.station.monitoring-and-improving.description"
+        }
+      },
+      {
+        "id": "integration-productization-cycle",
+        "title": "cycle.integration-productization-cycle.title",
+        "slug": "integration-productization-cycle",
+        "description": "cycle.integration-productization-cycle.description",
+        "purpose": "cycle.integration-productization-cycle.purpose",
+        "stations": [
+          "api-product-strategy",
+          "api-consumer-experience",
+          "api-platform-architecture",
+          "api-design",
+          "api-delivery",
+          "api-audit",
+          "api-publishing",
+          "monitoring-and-improving"
+        ],
+        "stationLabels": {
+          "api-product-strategy": "cycle.station.integration-capability-strategy",
+          "api-consumer-experience": "cycle.station.integration-consumer-requirements-onboarding",
+          "api-platform-architecture": "cycle.station.integration-architecture-decision",
+          "api-design": "cycle.station.integration-solution-design",
+          "api-delivery": "cycle.station.integration-delivery-operations",
+          "api-audit": "cycle.station.integration-readiness-assurance",
+          "api-publishing": "cycle.station.capability-publishing",
+          "monitoring-and-improving": "cycle.station.integration-monitoring-improvement"
+        },
+        "recommendedResources": {
+          "api-product-strategy": [
+            "customerJourneyCanvas",
+            "domainCanvas",
+            "capabilityValuePropositionCanvas",
+            "capabilityBusinessModelCanvas"
+          ],
+          "api-consumer-experience": [
+            "consumerExperienceRequirementsCanvas",
+            "api-onboarding-best-practices"
+          ],
+          "api-platform-architecture": [
+            "businessImpactCanvas",
+            "locationsCanvas",
+            "capacityCanvas",
+            "api-metrics-and-analytics"
+          ],
+          "api-design": [
+            "domainCanvas",
+            "interactionCanvas",
+            "restCanvas",
+            "eventCanvas",
+            "graphqlCanvas",
+            "contract-first-design"
+          ],
+          "api-delivery": [
+            "api-development-best-practices",
+            "api-testing-best-practices",
+            "apiops-CI-CD-for-apis",
+            "api-security-best-practices"
+          ],
+          "api-audit": [
+            "api-audit-checklist",
+            "api-compliance-best-practices"
+          ],
+          "api-publishing": [
+            "api-onboarding-best-practices",
+            "service-agreement-template"
+          ],
+          "monitoring-and-improving": [
+            "api-metrics-and-analytics",
+            "api-community-engagement-strategies"
+          ]
+        },
+        "entryCriteria": [
+          "business-goals-defined",
+          "api-opportunity-documented"
+        ],
+        "exitCriteria": [
+          "architecture-patterns-validated",
+          "api-description-available",
+          "audit-passed"
+        ],
+        "stationDescriptions": {
+          "api-product-strategy": "cycle.integration-productization-cycle.station.api-product-strategy.description",
+          "api-consumer-experience": "cycle.integration-productization-cycle.station.api-consumer-experience.description",
+          "api-platform-architecture": "cycle.integration-productization-cycle.station.api-platform-architecture.description",
+          "api-design": "cycle.integration-productization-cycle.station.api-design.description",
+          "api-delivery": "cycle.integration-productization-cycle.station.api-delivery.description",
+          "api-audit": "cycle.integration-productization-cycle.station.api-audit.description",
+          "api-publishing": "cycle.integration-productization-cycle.station.api-publishing.description",
+          "monitoring-and-improving": "cycle.integration-productization-cycle.station.monitoring-and-improving.description"
+        }
+      },
+      {
+        "id": "automation-cycle",
+        "title": "cycle.automation-cycle.title",
+        "slug": "automation-cycle",
+        "description": "cycle.automation-cycle.description",
+        "purpose": "cycle.automation-cycle.purpose",
+        "stations": [
+          "api-product-strategy",
+          "api-consumer-experience",
+          "api-platform-architecture",
+          "api-design",
+          "api-delivery",
+          "api-audit",
+          "api-publishing",
+          "monitoring-and-improving"
+        ],
+        "stationLabels": {
+          "api-product-strategy": "cycle.station.automation-opportunity-strategy",
+          "api-consumer-experience": "cycle.station.process-user-requirements",
+          "api-platform-architecture": "cycle.station.automation-platform-decision",
+          "api-design": "cycle.station.automation-workflow-design",
+          "api-delivery": "cycle.station.automation-delivery",
+          "api-audit": "cycle.station.automation-readiness-review",
+          "api-publishing": "cycle.station.automation-enablement",
+          "monitoring-and-improving": "cycle.station.automation-monitoring-improvement"
+        },
+        "recommendedResources": {
+          "api-product-strategy": [
+            "customerJourneyCanvas",
+            "domainCanvas",
+            "capabilityValuePropositionCanvas"
+          ],
+          "api-consumer-experience": [
+            "consumerExperienceRequirementsCanvas"
+          ],
+          "api-platform-architecture": [
+            "businessImpactCanvas",
+            "locationsCanvas",
+            "capacityCanvas"
+          ],
+          "api-design": [
+            "domainCanvas",
+            "interactionCanvas",
+            "restCanvas",
+            "eventCanvas",
+            "graphqlCanvas",
+            "contract-first-design"
+          ],
+          "api-delivery": [
+            "api-development-best-practices",
+            "api-testing-best-practices",
+            "apiops-CI-CD-for-apis"
+          ],
+          "api-audit": [
+            "api-audit-checklist",
+            "api-compliance-best-practices"
+          ],
+          "api-publishing": [
+            "api-onboarding-best-practices"
+          ],
+          "monitoring-and-improving": [
+            "api-metrics-and-analytics"
+          ]
+        },
+        "overlays": [],
+        "entryCriteria": [
+          "business-goals-defined",
+          "stakeholder-approval"
+        ],
+        "exitCriteria": [
+          "design-reflects-business-value",
+          "api-contract-tested",
+          "audit-passed"
+        ],
+        "stationDescriptions": {
+          "api-product-strategy": "cycle.automation-cycle.station.api-product-strategy.description",
+          "api-consumer-experience": "cycle.automation-cycle.station.api-consumer-experience.description",
+          "api-platform-architecture": "cycle.automation-cycle.station.api-platform-architecture.description",
+          "api-design": "cycle.automation-cycle.station.api-design.description",
+          "api-delivery": "cycle.automation-cycle.station.api-delivery.description",
+          "api-audit": "cycle.automation-cycle.station.api-audit.description",
+          "api-publishing": "cycle.automation-cycle.station.api-publishing.description",
+          "monitoring-and-improving": "cycle.automation-cycle.station.monitoring-and-improving.description"
+        }
+      }
+    ]
+  }
+}
diff --git a/src/data/method/de/labels.resources.json b/src/data/method/de/labels.resources.json
index 9019b39..0877e95 100644
--- a/src/data/method/de/labels.resources.json
+++ b/src/data/method/de/labels.resources.json
@@ -13,7 +13,7 @@
   "resource.api-development-best-practices.description": "Implementierungsleitfaden zur Umsetzung eines validierten API-Vertrags in eine konsistente, wartbare API-Codebasis unter Verwendung von Standardbibliotheken, wiederverwendbaren Mustern und aufeinander abgestimmten Entwicklungsabläufen.",
   "resource.api-development-best-practices.outcomes": "Besseres Verständnis der Grundsätze bewährter Verfahren für die API-Entwicklung",
   "resource.api-development-best-practices.steps": "Wenden Sie diese Vorgehensweisen auf den validierten API-Vertrag und den Implementierungsplan an, bevor mit der Programmierung begonnen wird.",
-  "resource.api-development-best-practices.tips": "Verwenden Sie diese Ressource als Implementierungsleitfaden und als Bewertungsinstrument und nicht als obligatorisches eigenständiges Artefakt", 
+  "resource.api-development-best-practices.tips": "Verwenden Sie diese Ressource als Implementierungsleitfaden und als Bewertungsinstrument und nicht als obligatorisches eigenständiges Artefakt",
   "resource.api-metrics-and-analytics.title": "API-Metriken und -Analysen",
   "resource.api-metrics-and-analytics.description": "Eine Ressource zum Definieren, Sammeln und Analysieren von API-Leistungs- und -Nutzungsdaten, um technische KPIs mit den Geschäftsergebnissen in Einklang zu bringen.",
   "resource.api-metrics-and-analytics.outcomes": "Besseres Verständnis von API-Metriken und Analysegrundsätzen",
@@ -403,5 +403,40 @@
   "resource.rest-canvas.steps.2": "Angabe von HTTP-Verben für die Interaktion mit Ressourcen",
   "resource.rest-canvas.steps.3": "Geben Sie Beispiele für Anfragen und Antworten für jedes Verb an.",
   "resource.rest-canvas.tips.1": "Sicherstellen, dass Ressourcen-URIs intuitiv und konsistent sind",
-  "resource.rest-canvas.tips.2": "Fehlerbehandlung und Antwortcodes dokumentieren"
+  "resource.rest-canvas.tips.2": "Fehlerbehandlung und Antwortcodes dokumentieren",
+  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
+  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
+  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
+  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
+  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
+  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
+  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
+  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
+  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
+  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
+  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
 }
diff --git a/src/data/method/de/labels.stakeholders.json b/src/data/method/de/labels.stakeholders.json
index 340ccab..06a6d33 100644
--- a/src/data/method/de/labels.stakeholders.json
+++ b/src/data/method/de/labels.stakeholders.json
@@ -8,28 +8,42 @@
   "stakeholder.api-program-owner.description": "Koordiniert API-Portfolio-Praktiken, organisatorische Ausrichtung und langfristige API-Fähigkeitsentwicklung.",
   "stakeholder.api-product-owner.title": "API Product Owner",
   "stakeholder.api-product-owner.description": "Führt die API-Möglichkeit, Priorisierung und produktniveaubezogene Entscheidungen über den gesamten Lebenszyklus hinweg durch.",
-  "stakeholder.domain-expert.title": "Domain-Experte",
-  "stakeholder.domain-expert.description": "Bringt tiefe Kenntnisse des Geschäftsbereichs, Konzepte, Regeln und Einschränkungen mit, die die API widerspiegeln muss.",
-  "stakeholder.customer-or-partner-representative.title": "Kunden- oder Partnervertreter",
-  "stakeholder.customer-or-partner-representative.description": "Repräsentiert die Perspektive von Kunden oder Partnern für den Reise, Wert und Zusammenarbeitsmodell.",
-  "stakeholder.api-consumer-representative.title": "API-Verbrauchervertreter",
-  "stakeholder.api-consumer-representative.description": "Repräsentiert die Bedürfnisse von Entwicklern, Integratoren oder anderen API-Verbrauchern, die die API direkt verwenden.",
+  "stakeholder.capability-owner.title": "Capability Owner",
+  "stakeholder.capability-owner.description": "",
+  "stakeholder.domain-specialist.title": "Domain-Experte",
+  "stakeholder.domain-specialist.description": "Bringt tiefe Kenntnisse des Geschäftsbereichs, Konzepte, Regeln und Einschränkungen mit, die die API widerspiegeln muss.",
+  "stakeholder.customer-specialist.title": "Kunden- oder Partnervertreter",
+  "stakeholder.customer-specialist.description": "Repräsentiert die Perspektive von Kunden oder Partnern für den Reise, Wert und Zusammenarbeitsmodell.",
+  "stakeholder.api-consumer-specialist.title": "API-Verbrauchervertreter",
+  "stakeholder.api-consumer-specialist.description": "Repräsentiert die Bedürfnisse von Entwicklern, Integratoren oder anderen API-Verbrauchern, die die API direkt verwenden.",
   "stakeholder.platform-architect.title": "Plattform-Architekt",
   "stakeholder.platform-architect.description": "Leitet Entscheidungen über Plattform, Integration, Skalierbarkeit und Architektur, die beeinflussen, wie die API erstellt und betrieben wird.",
+  "stakeholder.api-architect.title": "API Architect",
+  "stakeholder.api-architect.description": "",
+  "stakeholder.integration-architect.title": "Integration Architect",
+  "stakeholder.integration-architect.description": "",
+  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.description": "",
   "stakeholder.api-designer.title": "API-Designer",
   "stakeholder.api-designer.description": "Formt den API-Vertrag, das Interaktionsmodell, die Konsistenz und die Benutzbarkeit der exponierten Fähigkeiten.",
-  "stakeholder.delivery-engineer.title": "Programmierer",
-  "stakeholder.delivery-engineer.description": "Verantwortlich für Implementierung, Automatisierung, Testing und Release-Flussbedürfnisse, die für die zuverlässige Lieferung der API erforderlich sind.",
+  "stakeholder.api-engineer.title": "Programmierer",
+  "stakeholder.api-engineer.description": "Verantwortlich für Implementierung, Automatisierung, Testing und Release-Flussbedürfnisse, die für die zuverlässige Lieferung der API erforderlich sind.",
+  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.automation-owner.description": "",
+  "stakeholder.process-owner.title": "Process Owner",
+  "stakeholder.process-owner.description": "",
+  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.description": "",
   "stakeholder.security-specialist.title": "Sicherheitsspezialist",
   "stakeholder.security-specialist.description": "Stellt sicher, dass Sicherheitsrisiken, Kontrollen und Vertrauensgrenzen im gesamten API-Lifecycle berücksichtigt werden.",
-  "stakeholder.compliance-legal-specialist.title": "Compliance and Legal Specialist",
-  "stakeholder.compliance-legal-specialist.description": "Klärt rechtliche, datenschutzrechtliche, regulatorische und vertragliche Anforderungen auf, die die API beeinflussen.",
-  "stakeholder.governance-owner.title": "Governance Owner",
-  "stakeholder.governance-owner.description": "Repräsentiert Überprüfung, Auditierung und organisationsweite Governance-Praktiken für API-Qualität und Konformität.",
-  "stakeholder.documentation-devrel-owner.title": "Documentation and DevRel Owner",
-  "stakeholder.documentation-devrel-owner.description": "Verantwortlich für Onboarding-Inhalte, Entwickler-Kommunikation und Dokumentationsqualität für API-Verbraucher.",
-  "stakeholder.support-operations-owner.title": "Support and Operations Owner",
-  "stakeholder.support-operations-owner.description": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft.",
-  "stakeholder.partner-vendor-manager.title": "Partner- oder Vendor-Manager",
-  "stakeholder.partner-vendor-manager.description": "Koordiniert externe Partner-, Lieferanten- oder Vendor-Beziehungen, die die API-Strategie und -Lieferung beeinflussen."
+  "stakeholder.compliance-specialist.title": "Compliance and Legal Specialist",
+  "stakeholder.compliance-specialist.description": "Klärt rechtliche, datenschutzrechtliche, regulatorische und vertragliche Anforderungen auf, die die API beeinflussen.",
+  "stakeholder.governance-specialist.title": "Governance Owner",
+  "stakeholder.governance-specialist.description": "Repräsentiert Überprüfung, Auditierung und organisationsweite Governance-Praktiken für API-Qualität und Konformität.",
+  "stakeholder.api-devrel-specialist.title": "Documentation and DevRel Owner",
+  "stakeholder.api-devrel-specialist.description": "Verantwortlich für Onboarding-Inhalte, Entwickler-Kommunikation und Dokumentationsqualität für API-Verbraucher.",
+  "stakeholder.operations-specialist.title": "Support and Operations Owner",
+  "stakeholder.operations-specialist.description": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft.",
+  "stakeholder.partner-specialist.title": "Partner- oder Vendor-Manager",
+  "stakeholder.partner-specialist.description": "Koordiniert externe Partner-, Lieferanten- oder Vendor-Beziehungen, die die API-Strategie und -Lieferung beeinflussen."
 }
diff --git a/src/data/method/de/labels.stations.json b/src/data/method/de/labels.stations.json
index e60ba4b..f0a19c5 100644
--- a/src/data/method/de/labels.stations.json
+++ b/src/data/method/de/labels.stations.json
@@ -13,7 +13,7 @@
   "station.api-consumer-experience.description": "Stellen Sie sicher, dass Ihre API auffindbar, verständlich und nutzbar ist - vor und nach der Einführung.",
   "station.api-consumer-experience.why_it_matters": "Großartige APIs funktionieren nicht nur - sie fühlen sich auch intuitiv an. Ganz gleich, ob Ihr Kunde ein interner Entwickler, ein externer Partner oder ein KI-Agent ist, seine Erfahrung entscheidet über die Akzeptanz.\n\nOhne einen klaren Erlebnisplan:\n- Großartige APIs bleiben ungenutzt\n- Teams verschwenden Zeit damit, zu raten, wie sie Ihre API verwenden sollen\n- Feedbackschleifen sind unterbrochen oder fehlen.\n\nDiese Station hilft Ihnen, Ihre API mit den Augen ihrer Nutzer zu sehen.",
   "station.api-consumer-experience.how_it_works": "Überprüfen Sie das bestehende API Value Proposition Canvаs von der Perspektive des API-Nutzers. Stellen Sie die Stabilität der unterstützten Geschäftsprozesse sicher und ergänzen Sie die Funktionen, die Probleme lösen und Vorteile bieten, um die Bedürfnisse der API-Nutzer zu berücksichtigen, damit diese spätere Designentscheidungen leiten können.",
-   "station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des API-Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.", 
+  "station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des API-Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
   "station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den API-Nutzer zu verbessern.",
   "station.api-consumer-experience.apply_in_work": "Bereitstellung von Richtlinien, Tools und Feedback-Mechanismen für das Verständnis, die Analyse und die Verbesserung der internen und externen Erfahrungen von Entwicklern und Partnern.",
   "station.api-consumer-experience.outcomes": "Identifizieren und priorisieren Sie Ihre API-Kunden",
@@ -373,5 +373,101 @@
   "station.budget-and-resource-management.outcomes.2": "Optimierte Investitionen in die API-Entwicklung und -Verwaltung",
   "station.budget-and-resource-management.outcomes.3": "Verbesserte finanzielle Transparenz und Kontrolle über API-Initiativen",
   "station.budget-and-resource-management.how_it_works.1": "Festlegung von Kriterien für die Bewertung und Priorisierung von Budgetzuweisungen auf der Grundlage des Geschäftswerts, der Auswirkungen und der Ausrichtung auf strategische Initiativen.",
-  "station.budget-and-resource-management.how_it_works.2": "Überwachung des Budgets und der Ressourcennutzung, um effektive Investitionen und Ressourcenzuweisung für API-Initiativen sicherzustellen."
+  "station.budget-and-resource-management.how_it_works.2": "Überwachung des Budgets und der Ressourcennutzung, um effektive Investitionen und Ressourcenzuweisung für API-Initiativen sicherzustellen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.title": "API-Produktstrategie - APIs in strategische Produkte verwandeln",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Bevor Sie etwas bauen, sollten Sie von Anfang an den Wert, die Benutzer und die Geschäftsziele Ihrer API definieren.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Viele Unternehmen betrachten APIs als technische Projekte und nicht als Produkte. Das Ergebnis? Verwirrte Kunden, schlechte Akzeptanz und verschwendeter Aufwand.\n\nDiese Station hilft Ihnen, den Zweck Ihrer API, die Zielgruppe und die Erfolgskriterien zu definieren, damit Teams APIs bereitstellen können, die echte Probleme lösen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Bereitstellung von Richtlinien und Vorlagen für die Erstellung von API-Geschäftsmodellen, Wertvorschlägen und Roadmaps.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Ein klares API-Wertversprechen und eine klare Zielgruppe",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Untersuchen Sie das Kunden- oder Partnerproblem, das Sie mit APIs lösen wollen. Zeichnen Sie die Stakeholder, deren Wege und Ergebnisse mithilfe der Customer Journey Canvas auf.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Gemeinsame Sprache zwischen Produkt, Design und Technik",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Ein solides Argument für die Finanzierung/Bewilligung",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle Journeys und eventuell APIs zu schaffen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Verwenden Sie das API Value Proposition Canvas, um die unterstützten Geschäftsaufgaben sowie die Probleme, Vorteile und Funktionen für API-Nutzer zu erfassen, die neue oder wiederverwendbare APIs prägen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Definieren Sie den Wert - für die Nutzer und das Unternehmen - mit dem API Business Model Canvas, um Ihre API-Strategie visuell, gemeinsam nutzbar und einfach mit Ihren API-Kunden an der nächsten Station zu validieren.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design für die echten Benutzer Ihrer API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Stellen Sie sicher, dass Ihre API auffindbar, verständlich und nutzbar ist - vor und nach der Einführung.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Großartige APIs funktionieren nicht nur - sie fühlen sich auch intuitiv an. Ganz gleich, ob Ihr Kunde ein interner Entwickler, ein externer Partner oder ein KI-Agent ist, seine Erfahrung entscheidet über die Akzeptanz.\n\nOhne einen klaren Erlebnisplan:\n- Großartige APIs bleiben ungenutzt\n- Teams verschwenden Zeit damit, zu raten, wie sie Ihre API verwenden sollen\n- Feedbackschleifen sind unterbrochen oder fehlen.\n\nDiese Station hilft Ihnen, Ihre API mit den Augen ihrer Nutzer zu sehen.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Überprüfen Sie das bestehende API Value Proposition Canvаs von der Perspektive des API-Nutzers. Stellen Sie die Stabilität der unterstützten Geschäftsprozesse sicher und ergänzen Sie die Funktionen, die Probleme lösen und Vorteile bieten, um die Bedürfnisse der API-Nutzer zu berücksichtigen, damit diese spätere Designentscheidungen leiten können.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des API-Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den API-Nutzer zu verbessern.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Bereitstellung von Richtlinien, Tools und Feedback-Mechanismen für das Verständnis, die Analyse und die Verbesserung der internen und externen Erfahrungen von Entwicklern und Partnern.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifizieren und priorisieren Sie Ihre API-Kunden",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Definieren Sie die API-Erlebnisreise",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Onboarding, Dokumentation und Feedback planen",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Verbesserung der Akzeptanz durch echte Empathie + Developer Experience (DX)",
+  "cycle.api-productization-cycle.station.api-platform-architecture.title": "API-Plattformarchitektur - Architektur von APIs für Skalierbarkeit und Wiederverwendung",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Gewährleisten Sie Skalierbarkeit, Wiederverwendung und Governance für Ihre API- und Plattformkomponenten.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "Wenn APIs teamübergreifend skaliert werden, muss Ihre Plattform Governance und Wiederverwendung ermöglichen, ohne die Geschwindigkeit zu beeinträchtigen. Diese Station zeigt, wie man APIs für Langlebigkeit, Sicherheit und Effizienz entwickelt.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Aufbau einer skalierbaren, sicheren und konformen Infrastruktur für den API-Betrieb. Bereitstellung von Leitlinien für bewährte Architekturverfahren.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Redundante APIs abbauen und die Kosten für die Cloud-Plattform senken",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Das Business Impact Canvas hilft dabei, Risiken in Bezug auf API-Verfügbarkeit, -Sicherheit und -Funktionalität zu identifizieren und zu mindern, um fundierte Architekturentscheidungen zu unterstützen.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Umsetzung einer einheitlichen Governance ohne starke Kontrolle von oben nach unten",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Design für interne Wiederverwendung und externe Skalierbarkeit",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartierung der Standorte von API-Anbietern und -Verbrauchern, um die Zugänglichkeit und Einhaltung von Vorschriften zu gewährleisten.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Das Capacity Canvas gleicht geschäftliche Transaktionsmuster, künftige Verbrauchstrends und technische Lösungen ab, um die Skalierbarkeit und Leistung von APIs zu gewährleisten und liefert wichtige Informationen für Skalierungsentscheidungen und die Infrastrukturplanung.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Definieren und überwachen Sie Leistungsmetriken (z. B. API-Aufrufe, Latenz, Fehlerraten) und Adoptionsmetriken (z. B. NPS).",
+  "cycle.api-productization-cycle.station.api-design.title": "API-Design - Entwerfen Sie APIs, die Wert liefern",
+  "cycle.api-productization-cycle.station.api-design.description": "Erstellen Sie API-Designs, die konsistent, wiederverwendbar und auf Geschäftszielen und gemeinsamen Standards basieren.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "Beim Entwurf von APIs geht es nicht nur um die Benennung von Endpunkten. Gutes Design stellt sicher, dass APIs benutzerfreundlich, konsistent und auf Geschäfts- und technische Ziele ausgerichtet sind. Schlecht gestaltete APIs führen zu enger Kopplung, geringer Wiederverwendung und kostspieligen Nacharbeiten in den Teams.",
+  "cycle.api-productization-cycle.station.api-design.apply_in_work": "Bereitstellung von wiederverwendbaren Designmustern, gemeinsamen Standards und Validierungstools für API-Spezifikationen. Sicherstellen, dass Designentscheidungen konsistent, frühzeitig überprüft und auf die Geschäftsabsicht ausgerichtet sind.",
+  "cycle.api-productization-cycle.station.api-design.outcomes": "Gut dokumentierte und konsistente API-Designs",
+  "cycle.api-productization-cycle.station.api-design.how_it_works": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle APIs zu schaffen.",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Wiederverwendbare und validierte API-Verträge",
+  "cycle.api-productization-cycle.station.api-design.outcomes.2": "Entwürfe, die auf Domänenmodelle und Interaktionsmuster abgestimmt sind",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Rückverfolgbarkeit des Designs zum Geschäftswert",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Verwenden Sie das Interaction Canvas, um zu definieren, wie die Verbraucher mit der API interagieren werden, um sicherzustellen, dass sie ihren Bedürfnissen und Erwartungen entspricht.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Wenden Sie REST-Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Wenden Sie ereignisgesteuerte Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Wenden Sie GraphQL-Designmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Nutzen Sie die Designprinzipien und den API-Styleguide, um Ihre Designentscheidungen an gemeinsamen Regeln auszurichten und eine konsistente Audit-Validierung zu ermöglichen.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um den API-Vertrag vor der Implementierung zu erfassen und zu validieren.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass das API-Design funktionale und nicht-funktionale Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
+  "cycle.api-productization-cycle.station.api-delivery.title": "API-Bereitstellung - Bereitstellung sicherer und zuverlässiger APIs",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Erstellen, Testen und Freigeben von APIs unter Verwendung moderner Bereitstellungspipelines und bewährter technischer Verfahren.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Selbst die besten API-Designs scheitern, wenn die Bereitstellung uneinheitlich ist. Diese Station stellt sicher, dass Ihre APIs qualitativ hochwertig erstellt, gründlich getestet und zuverlässig bereitgestellt werden - für schnellere Iterationen und mehr Vertrauen.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Bereitstellung von Kodierungsrahmen, Bibliotheken und Standards für die API-Implementierung. Implementierung von CI/CD-Pipelines, Qualitätssicherungs-Frameworks und Tools zur Automatisierung der Bereitstellung.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs, die mit getesteten Frameworks und Mustern implementiert werden",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Verwenden Sie Best Practices für die API-Entwicklung als Leitfaden für die Implementierung des validierten Vertrags mit etablierten Frameworks und Bibliotheken, um sicherzustellen, dass das Ergebnis wiederverwendbar und wartbar ist.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Zuverlässige und automatisierte CI/CD-Pipelines",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Funktionale und nicht-funktionale Tests integriert",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Sichere und gesetzeskonforme Zustellungspipelines",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Erstellen Sie die API-Implementierung auf Basis des validierten Vertrags unter Verwendung etablierter Frameworks, Bibliotheken und Teamstandards.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testen Sie APIs auf Funktionalität, Sicherheit und Leistung mit automatisierten Testwerkzeugen.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Verwenden Sie CI/CD-Pipelines, um Build-, Test- und Bereitstellungsprozesse zu automatisieren und so konsistente Qualität und Nachvollziehbarkeit zu gewährleisten.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Stellen Sie sicher, dass APIs die Sicherheits- und Compliance-Anforderungen durch automatische Prüfungen und Audits erfüllen.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass die API die funktionalen und nicht-funktionalen Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
+  "cycle.api-productization-cycle.station.api-audit.title": "API-Audit - Prüfung von APIs auf Konformität und Qualität",
+  "cycle.api-productization-cycle.station.api-audit.description": "Stellen Sie sicher, dass APIs vor der Veröffentlichung und Bereitstellung den geschäftlichen, gestalterischen und betrieblichen Standards entsprechen.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs sind langlebige Produkte und müssen den Erwartungen hinsichtlich Qualität, Konsistenz und Compliance entsprechen. Das Audit verbindet Designentscheidungen, Implementierung und Betriebsbereitschaft mit definierten Standards und reduziert so Risiken vor der Bereitstellung.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Richten Sie einen konsistenten Audit-Prozess ein, der die API-Bereitschaft über alle Lebenszyklusphasen hinweg anhand definierter Kriterien, Nachweise und Standards bewertet. Stellen Sie sicher, dass Lücken frühzeitig erkannt und vor der Veröffentlichung behoben werden.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs erfüllen interne und externe Standards",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Führen Sie Audits durch, um sicherzustellen, dass APIs vor der Veröffentlichung organisatorische, technische und rechtliche Standards erfüllen.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Klare Dokumentation des API-Designs und der Implementierungsentscheidungen",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Sicherheit, Leistung und Konformität validiert",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Geringeres Risiko von Problemen in der Produktion",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Verwenden Sie Checklisten, Linters und Testwerkzeuge, um die Konsistenz und Konformität mit den Standards zu überprüfen.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Zusammenarbeit mit Governance-Teams und Domänenexperten, um sicherzustellen, dass APIs für die Produktion bereit sind.",
+  "cycle.api-productization-cycle.station.api-publishing.title": "API-Veröffentlichung - Veröffentlichen Sie APIs mit Zuversicht",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Stellen Sie APIs mit der richtigen Dokumentation und den richtigen Prozessen sicher und klar für die richtige Zielgruppe bereit.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Bei der Veröffentlichung geht es nicht nur um die Bereitstellung, sondern auch um die Auffindbarkeit, den Zugang und die Unterstützung. Wenn APIs nicht korrekt veröffentlicht werden, können sie nicht verwendet, wiederverwendet oder effektiv gesichert werden.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Ermöglichung der Veröffentlichung von APIs in der jeweiligen Umgebung mit klaren Registrierungs- und Zugriffsmechanismen (z. B. API-Schlüssel, OAuth, Abonnementpläne) je nach den API-Verbrauchersegmenten und den Sicherheits- und Compliance-Anforderungen.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes": "Veröffentlichung von APIs in der richtigen Umgebung (privat, Partner, öffentlich)",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Veröffentlichen Sie APIs in den entsprechenden Gateways und Umgebungen, um die Wiederverwendbarkeit für mehrere API-Kunden zu unterstützen.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Klare API-Einführungs- und Registrierungsprozesse",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Dokumentation, Sicherheitsmodelle und Richtlinien verfügbar",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs bereit für Skalierung und Governance",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Dokumentieren Sie, wie die Verbraucher die API finden und nutzen, einschließlich Onboarding-Prozesse und Registrierung.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Stellen Sie sicher, dass die Sicherheitsmodelle, die Gateway-Konfiguration und die rechtlichen Bestimmungen für die Verbraucher klar und verständlich sind.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Überwachen und Verbessern - für den API-Wert",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Nutzen Sie Messgrößen und Feedback, um die API-Leistung zu verfolgen und kontinuierliche Verbesserungen voranzutreiben.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "Die API-Bereitstellung endet nicht mit dem Start. Ohne Überwachung können Teams weder die Akzeptanz noch die Leistung oder den ROI verbessern. Diese Station stellt sicher, dass APIs nützlich und sicher bleiben und sich mit den Geschäftsanforderungen weiterentwickeln.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Einrichtung von Analyserahmen zur Verfolgung von Leistung und Engagement. Entwickeln Sie Feedbackschleifen, Analysetools und Engagementstrategien für APIs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Festlegung und Verfolgung von Leistungs- und Nutzungskennzahlen",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Überwachen Sie Leistungsmetriken (z. B. API-Aufrufe, Latenz, Fehlerraten) und Akzeptanzmetriken (z. B. NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Feedback-Schleifen für Entwickler sind vorhanden",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Kontinuierlich ermittelte und behandelte Probleme",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "Iteration der API, abgestimmt auf die Bedürfnisse der Nutzer",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analysieren Sie API-Nutzungsmetriken und integrieren Sie Benutzerfeedback in API-Iterationen.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Machen Sie es sich zur Gewohnheit, die Messwerte zu überprüfen und kontinuierliche Verbesserungsmaßnahmen zu planen."
 }
diff --git a/src/data/method/en/labels.cycles.json b/src/data/method/en/labels.cycles.json
new file mode 100644
index 0000000..1af68da
--- /dev/null
+++ b/src/data/method/en/labels.cycles.json
@@ -0,0 +1,93 @@
+{
+  "cycles.title": "Cycle Views",
+  "cycles.description": "Audience-specific views over the APIOps Cycles method graph.",
+  "cycle.capability-productization-cycle.title": "Capability Productization Cycle",
+  "cycle.capability-productization-cycle.description": "A cycle for turning business capabilities into reusable digital capabilities before selecting the implementation style.",
+  "cycle.capability-productization-cycle.purpose": "Identify and productize reusable digital capabilities before deciding whether the delivery style should be APIs, events, files, streams, data products, AI-enabled services, direct integration, or a hybrid pattern.",
+  "cycle.api-productization-cycle.title": "API Productization Cycle",
+  "cycle.api-productization-cycle.description": "The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.",
+  "cycle.api-productization-cycle.purpose": "API-focused method journey for teams that already know the intended delivery style is an API product.",
+  "cycle.integration-productization-cycle.title": "Integration Productization Cycle",
+  "cycle.integration-productization-cycle.description": "A cycle for productizing reusable integration capabilities before selecting a concrete integration pattern.",
+  "cycle.integration-productization-cycle.purpose": "Guide reusable integration capability design before choosing APIs, events, files, streams, data products, direct integration, or hybrid patterns.",
+  "cycle.station.capability-strategy": "Strategy",
+  "cycle.station.consumer-requirements-onboarding": "Consumer Requirements & Onboarding",
+  "cycle.station.architecture-platform-decisions": "Architecture & Platform Decisions",
+  "cycle.station.solution-interface-design": "Solution & Interface Design",
+  "cycle.station.delivery-operations": "Delivery & Operations",
+  "cycle.station.quality-readiness-assurance": "Quality & Readiness Assurance",
+  "cycle.station.publishing-enablement": "Publishing & Adoption Enablement",
+  "cycle.station.monitoring-improvement": "Monitoring & Improvement",
+  "cycle.station.api-product-strategy": "API Product Strategy",
+  "cycle.station.api-consumer-experience": "API Consumer Experience",
+  "cycle.station.api-platform-architecture": "API Platform Architecture",
+  "cycle.station.api-design": "API Design",
+  "cycle.station.api-delivery": "API Delivery",
+  "cycle.station.api-audit": "API Audit",
+  "cycle.station.api-publishing": "API Publishing",
+  "cycle.station.monitoring-and-improving": "Monitoring & Improving",
+  "cycle.station.integration-capability-strategy": "Integration Capability Strategy",
+  "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer Requirements & Onboarding",
+  "cycle.station.integration-architecture-decision": "Integration Architecture Decision",
+  "cycle.station.integration-solution-design": "Integration Solution Design",
+  "cycle.station.integration-delivery-operations": "Integration Delivery & Operations",
+  "cycle.station.integration-readiness-assurance": "Integration Readiness Assurance",
+  "cycle.station.capability-publishing": "Capability Publishing",
+  "cycle.station.integration-monitoring-improvement": "Integration Monitoring & Improvement",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API’s value, users, and business goals from day one.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to choose architecture and platform capabilities.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver and operate the selected solution mechanism.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Assure quality, governance, and readiness before release.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish capability information so consumers can discover, request, onboard, and get support.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities.",
+  "cycle.owner.business-owner": "Business owner",
+  "cycle.owner.domain-expert": "Domain expert",
+  "cycle.owner.capability-owner": "Capability owner",
+  "cycle.owner.consumer-representative": "Consumer representative",
+  "cycle.owner.enterprise-architect": "Enterprise architect",
+  "cycle.owner.platform-owner": "Platform owner",
+  "cycle.owner.api-product-owner": "API product owner",
+  "cycle.owner.api-platform-owner": "API platform owner",
+  "cycle.owner.integration-architect": "Integration architect",
+  "cycle.owner.solution-architect": "Solution architect",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Frame the API as a product with clear value proposition, consumers, business model, ownership, and lifecycle intent.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Define API consumer segments, onboarding paths, expectations, and experience requirements before design decisions are locked.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choose and validate the API platform, architecture, governance, and operational constraints needed for the product.",
+  "cycle.api-productization-cycle.station.api-design.description": "Design the API contract, interaction model, schemas, policies, and usability details before implementation.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Implement, test, secure, automate, and operate the API product through the delivery pipeline.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validate API quality, compliance, readiness, evidence, and release criteria before publication.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publish the API product so consumers can discover, evaluate, request access, onboard, and get support.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitor API health, adoption, consumer outcomes, reliability, and improvement opportunities after release.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting a pattern.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decide the integration architecture, platform capabilities, constraints, and governance model for the capability.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Design the integration solution, contracts, payloads, events, APIs, files, or interaction patterns selected for the capability.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability across its selected delivery pattern.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover, request, reuse, onboard, and get support.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.",
+  "cycle.automation-cycle.title": "Automation Cycle",
+  "cycle.automation-cycle.description": "A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.",
+  "cycle.automation-cycle.purpose": "Productize automation opportunities into governed workflows with clear users, platforms, controls, delivery paths, enablement, and monitoring.",
+  "cycle.audience.automation-owners": "Automation owners",
+  "cycle.audience.process-owners": "Process owners",
+  "cycle.audience.automation-teams": "Automation teams",
+  "cycle.station.automation-opportunity-strategy": "Automation Opportunity Strategy",
+  "cycle.station.process-user-requirements": "Process/User Requirements",
+  "cycle.station.automation-platform-decision": "Automation Platform Decision",
+  "cycle.station.automation-workflow-design": "Automation Workflow Design",
+  "cycle.station.automation-delivery": "Automation Delivery",
+  "cycle.station.automation-readiness-review": "Automation Readiness Review",
+  "cycle.station.automation-enablement": "Automation Enablement",
+  "cycle.station.automation-monitoring-improvement": "Automation Monitoring & Improvement",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration model, governance controls, and operational constraints.",
+  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, and exception paths.",
+  "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation with clear ownership and rollback paths.",
+  "cycle.automation-cycle.station.api-audit.description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.",
+  "cycle.automation-cycle.station.api-publishing.description": "Enable users and operators with discovery, onboarding, operating instructions, support paths, and change communication.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities."
+}
diff --git a/src/data/method/en/labels.lines.json b/src/data/method/en/labels.lines.json
index 0f693aa..31ef36b 100644
--- a/src/data/method/en/labels.lines.json
+++ b/src/data/method/en/labels.lines.json
@@ -1,16 +1,16 @@
 {
   "lines.title": "Metro Lines",
-  "lines.description": "A collection of API lines that guide the development and management of APIs.",
+  "lines.description": "A collection of shared metro lines that guide reusable capability, API, integration, automation, and future data productization work.",
   "line.business-opportunities-line.title": "Business Opportunities Line",
-  "line.business-opportunities-line.description": "Focuses on identifying and leveraging business opportunities through APIs.",
+  "line.business-opportunities-line.description": "Focuses on identifying and shaping business opportunities as reusable digital capabilities.",
   "line.platform-architecture-line.title": "Platform Architecture Line",
-  "line.platform-architecture-line.description": "Covers the architectural aspects of API platforms.",
-  "line.api-design-line.title": "API Design Line",
-  "line.api-design-line.description": "Focuses on the design principles and practices for APIs.",
+  "line.platform-architecture-line.description": "Covers architecture and platform decisions for reusable capabilities across delivery styles.",
+  "line.api-design-line.title": "Design Line",
+  "line.api-design-line.description": "Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other delivery styles.",
   "line.delivery-line.title": "Delivery Line",
-  "line.delivery-line.description": "Covers the delivery processes and practices for APIs.",
+  "line.delivery-line.description": "Covers delivery and operational practices for reusable capabilities across implementation styles.",
   "line.publishing-and-adoption-line.title": "Publishing and Adoption Line",
-  "line.publishing-and-adoption-line.description": "Focuses on publishing APIs and ensuring their adoption by consumers.",
+  "line.publishing-and-adoption-line.description": "Focuses on publishing reusable capabilities and enabling adoption by consumers.",
   "line.operating-model-line.title": "Operating Model Line",
-  "line.operating-model-line.description": "Covers the operating model for API management and governance."
-}
\ No newline at end of file
+  "line.operating-model-line.description": "Covers the operating model for reusable capability management and governance."
+}
diff --git a/src/data/method/en/labels.resources.json b/src/data/method/en/labels.resources.json
index 8c185a8..be023d4 100644
--- a/src/data/method/en/labels.resources.json
+++ b/src/data/method/en/labels.resources.json
@@ -155,11 +155,11 @@
   "resource.data-privacy-guidelines.tips": "Customize the Data Privacy Guidelines for your domain",
   "resource.data-privacy-guidelines.tips.1": "Use it collaboratively across business and tech roles",
   "resource.domain-canvas.title": "Domain Canvas",
-  "resource.domain-canvas.description": "A modeling tool to define and communicate the key entities and relationships in your domain, ensuring semantic consistency across APIs.",
+  "resource.domain-canvas.description": "A modeling tool to define and communicate the key entities and relationships in your domain, ensuring semantic consistency across capabilities, integrations, APIs, data products, and services.",
   "resource.domain-canvas.outcomes": "Better understanding of domain canvas principles",
   "resource.domain-canvas.outcomes.1": "Standardized approach using Domain Canvas",
-  "resource.domain-canvas.outcomes.2": "Improved implementation of related API practices",
-  "resource.domain-canvas.steps": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
+  "resource.domain-canvas.outcomes.2": "Improved implementation of related capability and interface practices",
+  "resource.domain-canvas.steps": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across capabilities, integrations, APIs, data products, and services.",
   "resource.domain-canvas.tips": "Customize the Domain Canvas for your domain",
   "resource.domain-canvas.tips.1": "Use it collaboratively across business and tech roles",
   "resource.ecosystem-vision-template.title": "Ecosystem Vision Template",
@@ -296,10 +296,10 @@
   "resource.api-value-proposition-canvas.tips.1": "Highlight features that relieve pains or enhance gains",
   "resource.api-value-proposition-canvas.tips.2": "Validate features with API consumers to ensure alignment",
   "resource.business-impact-canvas.title": "Business Impact Canvas",
-  "resource.business-impact-canvas.description": "Design a scalable and secure API platform architecture that meets business and technical requirements.",
-  "resource.business-impact-canvas.outcomes": "Scalable API infrastructure",
+  "resource.business-impact-canvas.description": "Identify availability, security, data, and business-impact risks that shape architecture and platform decisions.",
+  "resource.business-impact-canvas.outcomes": "Scalable and resilient capability architecture",
   "resource.business-impact-canvas.outcomes.1": "Enhanced security and compliance",
-  "resource.business-impact-canvas.outcomes.2": "Improved API performance",
+  "resource.business-impact-canvas.outcomes.2": "Improved capability performance and reliability",
   "resource.business-impact-canvas.steps": "Availability Risks: Identify risks and impacts.",
   "resource.business-impact-canvas.steps.1": "Ways to Mitigate Availability Risks: Define mitigation measures.",
   "resource.business-impact-canvas.steps.2": "Security Risks: Document security-related risks.",
@@ -308,10 +308,10 @@
   "resource.business-impact-canvas.steps.5": "Ways to Mitigate Data Risks: Plan strategies to address data risks.",
   "resource.business-impact-canvas.tips": "Involve architects and developers in the design process",
   "resource.business-impact-canvas.tips.1": "Use past incidents to identify potential risks",
-  "resource.business-impact-canvas.tips.2": "Prioritize critical APIs with the highest business impact",
+  "resource.business-impact-canvas.tips.2": "Prioritize capabilities with the highest business impact",
   "resource.capacity-canvas.title": "Capacity Canvas",
-  "resource.capacity-canvas.description": "Plan API capacity to meet current and future business demands, ensuring scalability and performance.",
-  "resource.capacity-canvas.outcomes": "Aligned API capacity with business volumes",
+  "resource.capacity-canvas.description": "Plan capacity to meet current and future business demand, ensuring scalability and performance for the selected capability or solution pattern.",
+  "resource.capacity-canvas.outcomes": "Aligned capacity with business volumes",
   "resource.capacity-canvas.outcomes.1": "Prepared for future consumption trends",
   "resource.capacity-canvas.outcomes.2": "Defined caching and rate-limiting strategies",
   "resource.capacity-canvas.steps": "Document current business volumes",
@@ -323,9 +323,9 @@
   "resource.capacity-canvas.tips.1": "Define peak usage scenarios",
   "resource.capacity-canvas.tips.2": "Include scalability testing in the planning phase",
   "resource.customer-journey-canvas.title": "Customer Journey Canvas",
-  "resource.customer-journey-canvas.description": "Map customer journeys to identify needs and pain points, enhancing API design and user experience.",
+  "resource.customer-journey-canvas.description": "Map customer, partner, or consumer journeys to identify needs, pain points, gains, inputs, outputs, and experience expectations.",
   "resource.customer-journey-canvas.outcomes": "Improved customer understanding",
-  "resource.customer-journey-canvas.outcomes.1": "Enhanced API design",
+  "resource.customer-journey-canvas.outcomes.1": "Enhanced capability and solution design",
   "resource.customer-journey-canvas.outcomes.2": "Better user experience",
   "resource.customer-journey-canvas.steps": "Define customer persona",
   "resource.customer-journey-canvas.steps.1": "Identify triggers for the journey",
@@ -334,9 +334,9 @@
   "resource.customer-journey-canvas.steps.4": "Identify customer pains",
   "resource.customer-journey-canvas.steps.5": "Summarize customer gains",
   "resource.customer-journey-canvas.steps.6": "Define necessary inputs and resulting outputs",
-  "resource.customer-journey-canvas.steps.7": "Define API interactions for each step",
+  "resource.customer-journey-canvas.steps.7": "Define interactions and processing expectations for each step",
   "resource.customer-journey-canvas.tips": "Iterate with team input to refine steps",
-  "resource.customer-journey-canvas.tips.1": "Use outputs from this canvas to inform other canvases like the API Value Proposition Canvas",
+  "resource.customer-journey-canvas.tips.1": "Use outputs from this canvas to inform value proposition, domain, requirements, and architecture decisions",
   "resource.event-canvas.title": "Event Canvas",
   "resource.event-canvas.description": "Design event-driven APIs by defining events, triggers, and processing logic.",
   "resource.event-canvas.outcomes": "Defined event-driven architecture",
@@ -366,12 +366,12 @@
   "resource.graphql-canvas.tips.1": "document example queries and mutations",
   "resource.graphql-canvas.tips.2": "Ensure type names are descriptive and consistent",
   "resource.interaction-canvas.title": "Interaction Canvas",
-  "resource.interaction-canvas.description": "Define API interactions, workflows, and expected responses to ensure a consistent API consumer experience.",
-  "resource.interaction-canvas.outcomes": "Clear API interaction workflows",
+  "resource.interaction-canvas.description": "Define interactions, workflows, inputs, outputs, commands, queries, events, and expected responses to ensure a consistent consumer experience.",
+  "resource.interaction-canvas.outcomes": "Clear interaction workflows",
   "resource.interaction-canvas.outcomes.1": "Defined inputs and outputs for each interaction",
   "resource.interaction-canvas.outcomes.2": "Consistent validation rules across interactions",
-  "resource.interaction-canvas.steps": "Map API interactions to user tasks",
-  "resource.interaction-canvas.steps.1": "Define endpoints for each interaction",
+  "resource.interaction-canvas.steps": "Map interactions to user, consumer, or system tasks",
+  "resource.interaction-canvas.steps.1": "Define access points, operations, commands, queries, or events for each interaction",
   "resource.interaction-canvas.steps.2": "document inputs and outputs for each interaction",
   "resource.interaction-canvas.steps.3": "Specify validation rules and constraints",
   "resource.interaction-canvas.steps.4": "Create interaction models for CRUD, query-driven, command-driven, and event-driven interactions",
@@ -379,15 +379,15 @@
   "resource.interaction-canvas.tips.1": "Simulate interactions with mock data to validate workflows",
   "resource.interaction-canvas.tips.2": "document expected responses for successful and unsuccessful interactions",
   "resource.location-canvas.title": "Location Canvas",
-  "resource.location-canvas.description": "Map API provider and consumer locations to ensure compliance and performance across regions.",
+  "resource.location-canvas.description": "Map consumer, producer, system, data, network, regulatory, and trust-boundary locations to ensure compliance and performance across regions.",
   "resource.location-canvas.outcomes": "Compliance with local regulations",
-  "resource.location-canvas.outcomes.1": "Optimized API performance across regions",
+  "resource.location-canvas.outcomes.1": "Optimized performance across regions",
   "resource.location-canvas.outcomes.2": "Enhanced understanding of regional requirements",
-  "resource.location-canvas.steps": "Map locations of API providers.",
+  "resource.location-canvas.steps": "Map locations of producers, source systems, platforms, and consumers.",
   "resource.location-canvas.steps.1": "Document where consumers are located.",
   "resource.location-canvas.steps.2": "Identify applicable regulations.",
   "resource.location-canvas.steps.3": "Document where data must reside.",
-  "resource.location-canvas.steps.4": "nsure APIs are accessible in all intended network regions.",
+  "resource.location-canvas.steps.4": "Ensure the capability is accessible in all intended network regions.",
   "resource.location-canvas.steps.5": "Validate network performance across regions.",
   "resource.location-canvas.tips": "Collaborate with legal and compliance teams",
   "resource.location-canvas.tips.1": "Validate network performance across key regions",
@@ -403,5 +403,40 @@
   "resource.rest-canvas.steps.3": "Provide example requests and responses for each verb",
   "resource.rest-canvas.tips": "Use standard HTTP methods (GET, POST, PUT, DELETE)",
   "resource.rest-canvas.tips.1": "Ensure resource URIs are intuitive and consistent",
-  "resource.rest-canvas.tips.2": "document error handling and response codes"
+  "resource.rest-canvas.tips.2": "document error handling and response codes",
+  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
+  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
+  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
+  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
+  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
+  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
+  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
+  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
+  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
+  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
+  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
 }
diff --git a/src/data/method/en/labels.stakeholders.json b/src/data/method/en/labels.stakeholders.json
index d44d506..283fc16 100644
--- a/src/data/method/en/labels.stakeholders.json
+++ b/src/data/method/en/labels.stakeholders.json
@@ -8,28 +8,42 @@
   "stakeholder.api-program-owner.description": "Coordinates API portfolio practices, organizational alignment, and long-term API capability development.",
   "stakeholder.api-product-owner.title": "API Product Owner",
   "stakeholder.api-product-owner.description": "Drives the API opportunity, prioritization, and product-level decisions across the lifecycle.",
-  "stakeholder.domain-expert.title": "Domain Expert",
-  "stakeholder.domain-expert.description": "Brings deep knowledge of the business domain, concepts, rules, and constraints the API must reflect.",
-  "stakeholder.customer-or-partner-representative.title": "Customer or Partner Representative",
-  "stakeholder.customer-or-partner-representative.description": "Contributes the business customer or partner perspective for the journey, value, and collaboration model.",
-  "stakeholder.api-consumer-representative.title": "API Consumer Representative",
-  "stakeholder.api-consumer-representative.description": "Represents the needs of developers, integrators, or other API consumers who use the API directly.",
+  "stakeholder.capability-owner.title": "Capability owners",
+  "stakeholder.capability-owner.description": "Responsible for defining, maintaining, and evolving the capabilities.",
+  "stakeholder.domain-specialist.title": "Domain Expert",
+  "stakeholder.domain-specialist.description": "Brings deep knowledge of the business domain, concepts, rules, and constraints the API must reflect.",
+  "stakeholder.customer-specialist.title": "Customer or Partner Representative",
+  "stakeholder.customer-specialist.description": "Contributes the business customer or partner perspective for the journey, value, and collaboration model.",
+  "stakeholder.api-consumer-specialist.title": "API Consumer Representative",
+  "stakeholder.api-consumer-specialist.description": "Represents the needs of developers, integrators, or other API consumers who use the API directly.",
   "stakeholder.platform-architect.title": "Platform Architect",
   "stakeholder.platform-architect.description": "Guides platform, integration, scalability, and architecture decisions that shape how the API is built and operated.",
+  "stakeholder.api-architect.title": "API platform teams",
+  "stakeholder.api-architect.description": "Responsible for designing and maintaining the API platform.",
+  "stakeholder.integration-architect.title": "Solution architects",
+  "stakeholder.integration-architect.description": "Designs and implements integration solutions that connect the API with other systems.",
+  "stakeholder.platform-owner.title": "Platform owners",
+  "stakeholder.platform-owner.description": "Responsible for the overall management and strategic direction of the platform.",
   "stakeholder.api-designer.title": "API Designer",
   "stakeholder.api-designer.description": "Shapes the API contract, interaction model, consistency, and usability of the exposed capabilities.",
-  "stakeholder.delivery-engineer.title": "Delivery Engineer",
-  "stakeholder.delivery-engineer.description": "Owns implementation, automation, testing, and release flow concerns needed to deliver the API reliably.",
+  "stakeholder.api-engineer.title": "Delivery Engineer",
+  "stakeholder.api-engineer.description": "Owns implementation, automation, testing, and release flow concerns needed to deliver the API reliably.",
+  "stakeholder.automation-owner.title": "Automation owners",
+  "stakeholder.automation-owner.description": "Responsible for the automation of processes and workflows related to business operations.",
+  "stakeholder.process-owner.title": "Process owners",
+  "stakeholder.process-owner.description": "Responsible for managing and improving the processes and workflows related to business operations.",
+  "stakeholder.automation-engineer.title": "Automation teams",
+  "stakeholder.automation-engineer.description": "Responsible for implementing and maintaining automation solutions.",
   "stakeholder.security-specialist.title": "Security Specialist",
   "stakeholder.security-specialist.description": "Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.",
-  "stakeholder.compliance-legal-specialist.title": "Compliance and Legal Specialist",
-  "stakeholder.compliance-legal-specialist.description": "Clarifies legal, privacy, regulatory, and contractual requirements that affect the API.",
-  "stakeholder.governance-owner.title": "API Governance Owner",
-  "stakeholder.governance-owner.description": "Represents review, audit, and organization-wide governance practices for API quality and conformity.",
-  "stakeholder.documentation-devrel-owner.title": "Documentation and DevRel Owner",
-  "stakeholder.documentation-devrel-owner.description": "Owns onboarding content, developer communication, and documentation quality for API consumers.",
-  "stakeholder.support-operations-owner.title": "Support and Operations Owner",
-  "stakeholder.support-operations-owner.description": "Represents runtime support, incident handling, observability, and operational readiness.",
-  "stakeholder.partner-vendor-manager.title": "Partner or Vendor Manager",
-  "stakeholder.partner-vendor-manager.description": "Coordinates external partner, supplier, or vendor relationships that influence API strategy and delivery."
+  "stakeholder.compliance-specialist.title": "Compliance and Legal Specialist",
+  "stakeholder.compliance-specialist.description": "Clarifies legal, privacy, regulatory, and contractual requirements that affect the API.",
+  "stakeholder.governance-specialist.title": "API Governance Owner",
+  "stakeholder.governance-specialist.description": "Represents review, audit, and organization-wide governance practices for API quality and conformity.",
+  "stakeholder.api-devrel-specialist.title": "Documentation and DevRel Owner",
+  "stakeholder.api-devrel-specialist.description": "Owns onboarding content, developer communication, and documentation quality for API consumers.",
+  "stakeholder.operations-specialist.title": "Support and Operations Owner",
+  "stakeholder.operations-specialist.description": "Represents runtime support, incident handling, observability, and operational readiness.",
+  "stakeholder.partner-specialist.title": "Partner or Vendor Manager",
+  "stakeholder.partner-specialist.description": "Coordinates external partner, supplier, or vendor relationships that influence API strategy and delivery."
 }
diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json
index dc04c36..55f6b1a 100644
--- a/src/data/method/en/labels.stations.json
+++ b/src/data/method/en/labels.stations.json
@@ -1,377 +1,948 @@
-{
-  "group.core-stations.title": "API Lifecycle Core Stations",
-  "group.core-stations.description": "The core stations of the API Metro, where teams can learn how to build and manage APIs effectively.",
-  "station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
-  "station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
-  "station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
-  "station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
-  "station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
-  "station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
-  "station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
-  "station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
-  "station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
-  "station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
-  "station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
-  "station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
-  "station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
-  "station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
-  "station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
-  "station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
-  "station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
-  "station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
-  "station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
-  "station.api-consumer-experience.outcomes.1": "Define the API experience journey",
-  "station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
-  "station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
-  "station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
-  "station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
-  "station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
-  "station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
-  "station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
-  "station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
-  "station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
-  "station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
-  "station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
-  "station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
-  "station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-  "station.api-design.title": "API Design - Design APIs That Deliver Value",
-  "station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
-  "station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
-  "station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
-  "station.api-design.outcomes": "Well-documented and consistent API designs",
-  "station.api-design.outcomes.1": "Reusable and validated API contracts",
-  "station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
-  "station.api-design.outcomes.3": "Design traceability to business value",
-  "station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
-  "station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
-  "station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-  "station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-  "station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-  "station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
-  "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
-  "station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
-  "station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
-  "station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
-  "station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
-  "station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
-  "station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
-  "station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
-  "station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
-  "station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
-  "station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
-  "station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
-  "station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
-  "station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-  "station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
-  "station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
-  "station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
-  "station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
-  "station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
-  "station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
-  "station.api-audit.outcomes": "APIs meet internal and external standards",
-  "station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
-  "station.api-audit.outcomes.2": "Security, performance, and compliance validated",
-  "station.api-audit.outcomes.3": "Reduced risk of issues in production",
-  "station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
-  "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-  "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
-  "station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
-  "station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
-  "station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
-  "station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
-  "station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
-  "station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
-  "station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
-  "station.api-publishing.outcomes.3": "APIs ready for scale and governance",
-  "station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
-  "station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
-  "station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
-  "station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
-  "station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
-  "station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
-  "station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
-  "station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
-  "station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
-  "station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
-  "station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
-  "station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-  "station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
-  "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
-  "group.sub-stations.title": "API Lifecycle Sub Stations",
-  "group.sub-stations.description": "Sub stations that provide additional resources, tools, and best practices for API teams.",
-  "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
-  "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
-  "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
-  "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
-  "station.user-experience.outcomes": "APIs designed with user needs in mind",
-  "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
-  "station.user-experience.outcomes.2": "User feedback incorporated into API design",
-  "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
-  "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
-  "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
-  "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
-  "station.market-insights.title": "Market Insights - Understand the API Landscape",
-  "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
-  "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
-  "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
-  "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
-  "station.market-insights.outcomes.1": "Industry standards and best practices identified",
-  "station.market-insights.outcomes.2": "API strategy aligned with market needs",
-  "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
-  "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
-  "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
-  "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
-  "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
-  "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
-  "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
-  "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
-  "station.business-goals.outcomes": "APIs aligned with business objectives",
-  "station.business-goals.outcomes.1": "Clear business value defined for each API",
-  "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
-  "station.business-goals.outcomes.3": "APIs contribute to organizational success",
-  "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
-  "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
-  "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
-  "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
-  "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
-  "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
-  "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
-  "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
-  "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
-  "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
-  "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
-  "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
-  "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
-  "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
-  "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
-  "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
-  "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
-  "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
-  "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
-  "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
-  "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
-  "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
-  "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
-  "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
-  "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
-  "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
-  "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
-  "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
-  "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
-  "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
-  "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
-  "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
-  "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
-  "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
-  "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
-  "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
-  "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
-  "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
-  "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
-  "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
-  "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
-  "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
-  "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
-  "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
-  "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
-  "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
-  "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
-  "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
-  "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
-  "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
-  "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
-  "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
-  "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
-  "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
-  "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
-  "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
-  "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
-  "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
-  "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
-  "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
-  "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
-  "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
-  "station.design-standards.outcomes": "Consistent API design across the organization",
-  "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
-  "station.design-standards.outcomes.2": "Reusable design patterns and components",
-  "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
-  "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
-  "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
-  "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
-  "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
-  "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
-  "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
-  "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
-  "station.vendor-management.outcomes": "Effective vendor management processes established",
-  "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
-  "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
-  "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
-  "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
-  "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
-  "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
-  "station.contract-design.title": "Contract Design - Define Clear API Contracts",
-  "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-  "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
-  "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-  "station.contract-design.outcomes": "Clear API contracts defined for each API",
-  "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
-  "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
-  "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
-  "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
-  "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
-  "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
-  "station.development.title": "Development - Build APIs with Best Practices",
-  "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
-  "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
-  "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
-  "station.development.outcomes": "APIs developed using best practices and frameworks",
-  "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
-  "station.development.outcomes.2": "Consistent coding standards and practices followed",
-  "station.development.outcomes.3": "Reduced development time and technical debt",
-  "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
-  "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
-  "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
-  "station.ci-cd.title": "CI/CD - Automate API Delivery",
-  "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
-  "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
-  "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
-  "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
-  "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
-  "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
-  "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
-  "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-  "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
-  "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
-  "station.test-automation.title": "Test Automation - Ensure API Quality",
-  "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
-  "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
-  "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
-  "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
-  "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
-  "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
-  "station.test-automation.outcomes.3": "Improved API reliability and quality",
-  "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
-  "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
-  "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
-  "station.release-management.title": "Release Management - Manage API Releases Effectively",
-  "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
-  "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
-  "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
-  "station.release-management.outcomes": "Controlled and smooth API releases",
-  "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
-  "station.release-management.outcomes.2": "Rollback procedures established for API releases",
-  "station.release-management.outcomes.3": "Reduced risks associated with API changes",
-  "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
-  "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
-  "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
-  "station.service-agreements.title": "Service Agreements - Define API Service Levels",
-  "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
-  "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
-  "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
-  "station.service-agreements.outcomes": "Clear service agreements defined for each API",
-  "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
-  "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
-  "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
-  "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
-  "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
-  "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
-  "station.api-consumer-adoption.title": "API Consumer Adoption - Drive API Usage",
-  "station.api-consumer-adoption.description": "Implement strategies to drive API consumer adoption and engagement, ensuring APIs are used effectively.",
-  "station.api-consumer-adoption.why_it_matters": "Driving API consumer adoption is crucial for realizing the value of APIs. This station provides strategies and best practices for engaging API consumers, ensuring they understand how to use APIs effectively and derive value from them.",
-  "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for API consumers. Ensure teams implement strategies that drive API consumer adoption, engagement, and satisfaction.",
-  "station.api-consumer-adoption.outcomes": "API consumer adoption strategies implemented",
-  "station.api-consumer-adoption.outcomes.1": "Increased API usage and engagement",
-  "station.api-consumer-adoption.outcomes.2": "API consumers educated on API features and benefits",
-  "station.api-consumer-adoption.outcomes.3": "Improved API consumer satisfaction and loyalty",
-  "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help API consumers understand how to use APIs effectively.",
-  "station.api-consumer-adoption.how_it_works.1": "Create educational materials (e.g., tutorials, documentation) that explain API features, benefits, and usage patterns.",
-  "station.api-consumer-adoption.how_it_works.2": "Engage with API consumers through feedback loops, support channels, and community forums to understand their needs and improve API adoption.",
-  "station.api-promotion.title": "API Promotion - Increase API Visibility and Usage",
-  "station.api-promotion.description": "Promote APIs to increase visibility, usage, and adoption among target audiences.",
-  "station.api-promotion.why_it_matters": "Promoting APIs is essential for increasing their visibility and driving usage. This station provides strategies and best practices for effectively promoting APIs to target audiences, ensuring they are aware of the APIs and understand their value.",
-  "station.api-promotion.apply_in_work": "Provide marketing strategies, promotional materials, and community engagement resources. Ensure teams implement effective API promotion strategies that increase visibility, usage, and adoption among target audiences.",
-  "station.api-promotion.outcomes": "API promotion strategies implemented",
-  "station.api-promotion.outcomes.1": "Increased API visibility and awareness",
-  "station.api-promotion.outcomes.2": "Higher API usage and adoption rates",
-  "station.api-promotion.outcomes.3": "Improved API consumer engagement and satisfaction",
-  "station.api-promotion.how_it_works": "Develop marketing strategies to promote APIs to target audiences, including social media, blogs, and webinars.",
-  "station.api-promotion.how_it_works.1": "Create promotional materials (e.g., case studies, success stories) that highlight the value and benefits of APIs.",
-  "station.api-promotion.how_it_works.2": "Engage with API communities and forums to share API updates, gather feedback, and promote API usage.",
-  "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
-  "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
-  "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
-  "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
-  "station.partner-integration.outcomes": "Partner integration processes established",
-  "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
-  "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
-  "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
-  "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
-  "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
-  "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
-  "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
-  "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
-  "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
-  "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
-  "station.api-mindset.outcomes": "API-first culture established across the organization",
-  "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
-  "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
-  "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
-  "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
-  "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
-  "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
-  "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
-  "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
-  "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
-  "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
-  "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
-  "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
-  "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
-  "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
-  "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
-  "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
-  "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
-  "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
-  "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
-  "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
-  "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
-  "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
-  "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
-  "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
-  "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
-  "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
-  "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
-  "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
-  "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
-  "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
-  "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
-  "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
-  "station.operating-guidelines.outcomes": "API governance practices established",
-  "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
-  "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
-  "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
-  "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
-  "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
-  "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
-  "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
-  "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
-  "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
-  "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
-  "station.portfolio-management.outcomes": "API portfolio management practices established",
-  "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
-  "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
-  "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
-  "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
-  "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
-  "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
-  "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
-  "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
-  "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
-  "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
-  "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
-  "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
-  "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
-  "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
-  "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
-  "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
-  "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives."
-}
+[
+  {
+    "group.core-stations.title": "API Lifecycle Core Stations",
+    "group.core-stations.description": "The core stations of the API Metro, where teams can learn how to build and manage APIs effectively.",
+    "station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
+    "station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
+    "station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
+    "station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
+    "station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
+    "station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
+    "station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
+    "station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
+    "station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
+    "station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
+    "station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
+    "station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
+    "station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
+    "station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
+    "station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
+    "station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
+    "station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
+    "station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
+    "station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
+    "station.api-consumer-experience.outcomes.1": "Define the API experience journey",
+    "station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
+    "station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
+    "station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
+    "station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
+    "station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
+    "station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
+    "station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
+    "station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
+    "station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
+    "station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
+    "station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
+    "station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
+    "station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+    "station.api-design.title": "API Design - Design APIs That Deliver Value",
+    "station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
+    "station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
+    "station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
+    "station.api-design.outcomes": "Well-documented and consistent API designs",
+    "station.api-design.outcomes.1": "Reusable and validated API contracts",
+    "station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
+    "station.api-design.outcomes.3": "Design traceability to business value",
+    "station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
+    "station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
+    "station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
+    "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
+    "station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
+    "station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
+    "station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
+    "station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
+    "station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
+    "station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
+    "station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
+    "station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
+    "station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
+    "station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
+    "station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
+    "station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
+    "station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+    "station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
+    "station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
+    "station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
+    "station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
+    "station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
+    "station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
+    "station.api-audit.outcomes": "APIs meet internal and external standards",
+    "station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
+    "station.api-audit.outcomes.2": "Security, performance, and compliance validated",
+    "station.api-audit.outcomes.3": "Reduced risk of issues in production",
+    "station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
+    "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+    "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
+    "station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
+    "station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
+    "station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
+    "station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
+    "station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
+    "station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
+    "station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
+    "station.api-publishing.outcomes.3": "APIs ready for scale and governance",
+    "station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
+    "station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
+    "station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
+    "station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
+    "station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
+    "station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
+    "station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
+    "station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
+    "station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
+    "station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
+    "station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
+    "station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+    "station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
+    "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
+    "group.sub-stations.title": "API Lifecycle Sub Stations",
+    "group.sub-stations.description": "Sub stations that provide additional resources, tools, and best practices for API teams.",
+    "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
+    "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
+    "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
+    "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
+    "station.user-experience.outcomes": "APIs designed with user needs in mind",
+    "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
+    "station.user-experience.outcomes.2": "User feedback incorporated into API design",
+    "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
+    "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
+    "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
+    "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
+    "station.market-insights.title": "Market Insights - Understand the API Landscape",
+    "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
+    "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
+    "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
+    "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
+    "station.market-insights.outcomes.1": "Industry standards and best practices identified",
+    "station.market-insights.outcomes.2": "API strategy aligned with market needs",
+    "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
+    "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
+    "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
+    "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
+    "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
+    "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
+    "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
+    "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
+    "station.business-goals.outcomes": "APIs aligned with business objectives",
+    "station.business-goals.outcomes.1": "Clear business value defined for each API",
+    "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
+    "station.business-goals.outcomes.3": "APIs contribute to organizational success",
+    "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
+    "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
+    "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
+    "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
+    "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
+    "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
+    "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
+    "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
+    "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
+    "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
+    "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
+    "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
+    "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
+    "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
+    "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
+    "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
+    "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
+    "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
+    "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
+    "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
+    "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
+    "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
+    "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
+    "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
+    "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
+    "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
+    "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
+    "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
+    "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
+    "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
+    "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
+    "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
+    "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
+    "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
+    "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
+    "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
+    "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
+    "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
+    "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
+    "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
+    "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
+    "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
+    "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
+    "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
+    "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
+    "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
+    "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
+    "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
+    "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
+    "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
+    "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
+    "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
+    "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
+    "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
+    "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
+    "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
+    "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
+    "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
+    "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
+    "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
+    "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
+    "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
+    "station.design-standards.outcomes": "Consistent API design across the organization",
+    "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
+    "station.design-standards.outcomes.2": "Reusable design patterns and components",
+    "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
+    "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
+    "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
+    "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
+    "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
+    "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
+    "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
+    "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
+    "station.vendor-management.outcomes": "Effective vendor management processes established",
+    "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
+    "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
+    "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
+    "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
+    "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
+    "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
+    "station.contract-design.title": "Contract Design - Define Clear API Contracts",
+    "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+    "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
+    "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+    "station.contract-design.outcomes": "Clear API contracts defined for each API",
+    "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
+    "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
+    "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
+    "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
+    "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
+    "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
+    "station.development.title": "Development - Build APIs with Best Practices",
+    "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
+    "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
+    "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
+    "station.development.outcomes": "APIs developed using best practices and frameworks",
+    "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
+    "station.development.outcomes.2": "Consistent coding standards and practices followed",
+    "station.development.outcomes.3": "Reduced development time and technical debt",
+    "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
+    "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
+    "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
+    "station.ci-cd.title": "CI/CD - Automate API Delivery",
+    "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
+    "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
+    "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
+    "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
+    "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
+    "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
+    "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
+    "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+    "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
+    "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
+    "station.test-automation.title": "Test Automation - Ensure API Quality",
+    "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
+    "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
+    "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
+    "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
+    "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
+    "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
+    "station.test-automation.outcomes.3": "Improved API reliability and quality",
+    "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
+    "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
+    "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
+    "station.release-management.title": "Release Management - Manage API Releases Effectively",
+    "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
+    "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
+    "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
+    "station.release-management.outcomes": "Controlled and smooth API releases",
+    "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
+    "station.release-management.outcomes.2": "Rollback procedures established for API releases",
+    "station.release-management.outcomes.3": "Reduced risks associated with API changes",
+    "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
+    "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
+    "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
+    "station.service-agreements.title": "Service Agreements - Define API Service Levels",
+    "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
+    "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
+    "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
+    "station.service-agreements.outcomes": "Clear service agreements defined for each API",
+    "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
+    "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
+    "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
+    "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
+    "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
+    "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
+    "station.api-consumer-adoption.title": "API Consumer Adoption - Drive API Usage",
+    "station.api-consumer-adoption.description": "Implement strategies to drive API consumer adoption and engagement, ensuring APIs are used effectively.",
+    "station.api-consumer-adoption.why_it_matters": "Driving API consumer adoption is crucial for realizing the value of APIs. This station provides strategies and best practices for engaging API consumers, ensuring they understand how to use APIs effectively and derive value from them.",
+    "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for API consumers. Ensure teams implement strategies that drive API consumer adoption, engagement, and satisfaction.",
+    "station.api-consumer-adoption.outcomes": "API consumer adoption strategies implemented",
+    "station.api-consumer-adoption.outcomes.1": "Increased API usage and engagement",
+    "station.api-consumer-adoption.outcomes.2": "API consumers educated on API features and benefits",
+    "station.api-consumer-adoption.outcomes.3": "Improved API consumer satisfaction and loyalty",
+    "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help API consumers understand how to use APIs effectively.",
+    "station.api-consumer-adoption.how_it_works.1": "Create educational materials (e.g., tutorials, documentation) that explain API features, benefits, and usage patterns.",
+    "station.api-consumer-adoption.how_it_works.2": "Engage with API consumers through feedback loops, support channels, and community forums to understand their needs and improve API adoption.",
+    "station.api-promotion.title": "API Promotion - Increase API Visibility and Usage",
+    "station.api-promotion.description": "Promote APIs to increase visibility, usage, and adoption among target audiences.",
+    "station.api-promotion.why_it_matters": "Promoting APIs is essential for increasing their visibility and driving usage. This station provides strategies and best practices for effectively promoting APIs to target audiences, ensuring they are aware of the APIs and understand their value.",
+    "station.api-promotion.apply_in_work": "Provide marketing strategies, promotional materials, and community engagement resources. Ensure teams implement effective API promotion strategies that increase visibility, usage, and adoption among target audiences.",
+    "station.api-promotion.outcomes": "API promotion strategies implemented",
+    "station.api-promotion.outcomes.1": "Increased API visibility and awareness",
+    "station.api-promotion.outcomes.2": "Higher API usage and adoption rates",
+    "station.api-promotion.outcomes.3": "Improved API consumer engagement and satisfaction",
+    "station.api-promotion.how_it_works": "Develop marketing strategies to promote APIs to target audiences, including social media, blogs, and webinars.",
+    "station.api-promotion.how_it_works.1": "Create promotional materials (e.g., case studies, success stories) that highlight the value and benefits of APIs.",
+    "station.api-promotion.how_it_works.2": "Engage with API communities and forums to share API updates, gather feedback, and promote API usage.",
+    "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
+    "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
+    "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
+    "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
+    "station.partner-integration.outcomes": "Partner integration processes established",
+    "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
+    "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
+    "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
+    "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
+    "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
+    "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
+    "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
+    "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
+    "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
+    "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
+    "station.api-mindset.outcomes": "API-first culture established across the organization",
+    "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
+    "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
+    "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
+    "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
+    "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
+    "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
+    "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
+    "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
+    "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
+    "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
+    "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
+    "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
+    "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
+    "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
+    "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
+    "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
+    "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
+    "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
+    "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
+    "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
+    "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
+    "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
+    "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
+    "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
+    "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
+    "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
+    "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
+    "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
+    "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
+    "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
+    "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
+    "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
+    "station.operating-guidelines.outcomes": "API governance practices established",
+    "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
+    "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
+    "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
+    "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
+    "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
+    "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
+    "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
+    "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
+    "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
+    "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
+    "station.portfolio-management.outcomes": "API portfolio management practices established",
+    "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
+    "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
+    "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
+    "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
+    "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
+    "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
+    "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
+    "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
+    "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
+    "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
+    "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
+    "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
+    "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
+    "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
+    "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
+    "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
+    "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
+    "cycle.api-productization-cycle.station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
+    "cycle.api-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
+    "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
+    "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
+    "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
+    "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
+    "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
+    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
+    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
+    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
+    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
+    "cycle.api-productization-cycle.station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
+    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
+    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Define the API experience journey",
+    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
+    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
+    "cycle.api-productization-cycle.station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
+    "cycle.api-productization-cycle.station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
+    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
+    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
+    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
+    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+    "cycle.api-productization-cycle.station.api-design.title": "API Design - Design APIs That Deliver Value",
+    "cycle.api-productization-cycle.station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
+    "cycle.api-productization-cycle.station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
+    "cycle.api-productization-cycle.station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
+    "cycle.api-productization-cycle.station.api-design.outcomes": "Well-documented and consistent API designs",
+    "cycle.api-productization-cycle.station.api-design.outcomes.1": "Reusable and validated API contracts",
+    "cycle.api-productization-cycle.station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
+    "cycle.api-productization-cycle.station.api-design.outcomes.3": "Design traceability to business value",
+    "cycle.api-productization-cycle.station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
+    "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
+    "cycle.api-productization-cycle.station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
+    "cycle.api-productization-cycle.station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
+    "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
+    "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
+    "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
+    "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
+    "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
+    "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
+    "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
+    "cycle.api-productization-cycle.station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
+    "cycle.api-productization-cycle.station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
+    "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
+    "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
+    "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs meet internal and external standards",
+    "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
+    "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Security, performance, and compliance validated",
+    "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
+    "cycle.api-productization-cycle.station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
+    "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+    "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
+    "cycle.api-productization-cycle.station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
+    "cycle.api-productization-cycle.station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
+    "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
+    "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
+    "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
+    "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
+    "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
+    "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs ready for scale and governance",
+    "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
+    "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
+    "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
+    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
+  },
+  {
+    "group.core-stations.title": "Capability Lifecycle Core Stations",
+    "group.core-stations.description": "The core stations of the method, where teams can learn how to design, deliver, govern, and improve reusable capabilities across APIs, events, files, streams, data products, and other integration styles.",
+    "station.api-product-strategy.title": "Strategy",
+    "station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
+    "station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
+    "station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
+    "station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
+    "station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
+    "station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
+    "station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
+    "station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
+    "station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
+    "station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
+    "station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
+    "station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
+    "station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
+    "station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
+    "station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
+    "station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
+    "station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
+    "station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
+    "station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
+    "station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
+    "station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
+    "station.api-platform-architecture.title": "Architecture & Platform Decisions",
+    "station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
+    "station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
+    "station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
+    "station.api-platform-architecture.outcomes": "A justified architecture choice",
+    "station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
+    "station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
+    "station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
+    "station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
+    "station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
+    "station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
+    "station.api-design.title": "Solution & Interface Design",
+    "station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
+    "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+    "station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
+    "station.api-design.outcomes": "A designed contract for the selected pattern",
+    "station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+    "station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
+    "station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
+    "station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
+    "station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
+    "station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
+    "station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
+    "station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+    "station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
+    "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+    "station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
+    "station.api-delivery.title": "Delivery & Operations",
+    "station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+    "station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
+    "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
+    "station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+    "station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
+    "station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
+    "station.api-delivery.outcomes.3": "Traceable delivery and release controls",
+    "station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
+    "station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+    "station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
+    "station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
+    "station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
+    "station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
+    "station.api-audit.title": "Quality & Readiness Assurance",
+    "station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+    "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
+    "station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
+    "station.api-audit.outcomes": "Documented readiness for release and reuse",
+    "station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
+    "station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
+    "station.api-audit.outcomes.3": "Reduced risk of issues in production",
+    "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+    "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+    "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
+    "station.api-publishing.title": "Publishing & Enablement",
+    "station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
+    "station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+    "station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
+    "station.api-publishing.outcomes": "A discoverable reusable capability",
+    "station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
+    "station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
+    "station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
+    "station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
+    "station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
+    "station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
+    "station.monitoring-and-improving.title": "Monitoring & Improvement",
+    "station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
+    "station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
+    "station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
+    "station.monitoring-and-improving.outcomes": "Measured capability health and value",
+    "station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
+    "station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
+    "station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
+    "station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
+    "station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
+    "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
+    "group.sub-stations.title": "Supporting Stations",
+    "group.sub-stations.description": "Supporting stations provide reusable practices, decision points and resources that can be included in different APIOps Cycles routes, including capability, API, integration, data and AI-enabled productization.",
+    "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
+    "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
+    "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
+    "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
+    "station.user-experience.outcomes": "APIs designed with user needs in mind",
+    "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
+    "station.user-experience.outcomes.2": "User feedback incorporated into API design",
+    "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
+    "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
+    "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
+    "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
+    "station.market-insights.title": "Market Insights - Understand the API Landscape",
+    "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
+    "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
+    "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
+    "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
+    "station.market-insights.outcomes.1": "Industry standards and best practices identified",
+    "station.market-insights.outcomes.2": "API strategy aligned with market needs",
+    "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
+    "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
+    "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
+    "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
+    "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
+    "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
+    "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
+    "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
+    "station.business-goals.outcomes": "APIs aligned with business objectives",
+    "station.business-goals.outcomes.1": "Clear business value defined for each API",
+    "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
+    "station.business-goals.outcomes.3": "APIs contribute to organizational success",
+    "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
+    "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
+    "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
+    "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
+    "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
+    "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
+    "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
+    "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
+    "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
+    "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
+    "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
+    "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
+    "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
+    "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
+    "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
+    "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
+    "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
+    "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
+    "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
+    "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
+    "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
+    "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
+    "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
+    "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
+    "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
+    "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
+    "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
+    "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
+    "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
+    "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
+    "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
+    "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
+    "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
+    "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
+    "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
+    "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
+    "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
+    "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
+    "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
+    "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
+    "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
+    "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
+    "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
+    "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
+    "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
+    "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
+    "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
+    "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
+    "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
+    "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
+    "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
+    "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
+    "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
+    "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
+    "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
+    "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
+    "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
+    "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
+    "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
+    "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
+    "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
+    "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
+    "station.design-standards.outcomes": "Consistent API design across the organization",
+    "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
+    "station.design-standards.outcomes.2": "Reusable design patterns and components",
+    "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
+    "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
+    "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
+    "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
+    "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
+    "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
+    "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
+    "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
+    "station.vendor-management.outcomes": "Effective vendor management processes established",
+    "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
+    "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
+    "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
+    "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
+    "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
+    "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
+    "station.contract-design.title": "Contract Design - Define Clear API Contracts",
+    "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+    "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
+    "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+    "station.contract-design.outcomes": "Clear API contracts defined for each API",
+    "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
+    "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
+    "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
+    "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
+    "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
+    "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
+    "station.development.title": "Development - Build APIs with Best Practices",
+    "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
+    "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
+    "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
+    "station.development.outcomes": "APIs developed using best practices and frameworks",
+    "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
+    "station.development.outcomes.2": "Consistent coding standards and practices followed",
+    "station.development.outcomes.3": "Reduced development time and technical debt",
+    "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
+    "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
+    "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
+    "station.ci-cd.title": "CI/CD - Automate API Delivery",
+    "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
+    "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
+    "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
+    "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
+    "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
+    "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
+    "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
+    "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+    "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
+    "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
+    "station.test-automation.title": "Test Automation - Ensure API Quality",
+    "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
+    "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
+    "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
+    "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
+    "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
+    "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
+    "station.test-automation.outcomes.3": "Improved API reliability and quality",
+    "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
+    "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
+    "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
+    "station.release-management.title": "Release Management - Manage API Releases Effectively",
+    "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
+    "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
+    "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
+    "station.release-management.outcomes": "Controlled and smooth API releases",
+    "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
+    "station.release-management.outcomes.2": "Rollback procedures established for API releases",
+    "station.release-management.outcomes.3": "Reduced risks associated with API changes",
+    "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
+    "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
+    "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
+    "station.service-agreements.title": "Service Agreements - Define API Service Levels",
+    "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
+    "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
+    "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
+    "station.service-agreements.outcomes": "Clear service agreements defined for each API",
+    "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
+    "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
+    "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
+    "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
+    "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
+    "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
+    "station.api-consumer-adoption.title": "Consumer Adoption",
+    "station.api-consumer-adoption.description": "Implement strategies to drive consumer adoption and engagement so reusable capabilities are used effectively.",
+    "station.api-consumer-adoption.why_it_matters": "Driving consumer adoption is crucial for realizing the value of reusable capabilities. This station provides strategies and best practices for engaging consumers, helping them understand how to use capabilities effectively and derive value from them.",
+    "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for consumers. Ensure teams implement adoption practices that improve engagement, satisfaction, and reuse.",
+    "station.api-consumer-adoption.outcomes": "Consumer adoption strategies implemented",
+    "station.api-consumer-adoption.outcomes.1": "Increased usage and engagement",
+    "station.api-consumer-adoption.outcomes.2": "Consumers educated on capability features and benefits",
+    "station.api-consumer-adoption.outcomes.3": "Improved consumer satisfaction and loyalty",
+    "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help consumers understand how to use reusable capabilities effectively.",
+    "station.api-consumer-adoption.how_it_works.1": "Create educational materials that explain capability features, benefits, and usage patterns.",
+    "station.api-consumer-adoption.how_it_works.2": "Engage with consumers through feedback loops, support channels, and communities to understand needs and improve adoption.",
+    "station.api-promotion.title": "Promotion",
+    "station.api-promotion.description": "Promote reusable capabilities to increase visibility, usage, and adoption among target audiences.",
+    "station.api-promotion.why_it_matters": "Promotion increases visibility and drives usage. This station provides strategies and best practices for making target audiences aware of reusable capabilities and their value.",
+    "station.api-promotion.apply_in_work": "Provide communication strategies, promotional materials, and community engagement resources. Ensure teams implement promotion practices that increase visibility, usage, and adoption among target audiences.",
+    "station.api-promotion.outcomes": "Promotion strategies implemented",
+    "station.api-promotion.outcomes.1": "Increased visibility and awareness",
+    "station.api-promotion.outcomes.2": "Higher usage and adoption rates",
+    "station.api-promotion.outcomes.3": "Improved consumer engagement and satisfaction",
+    "station.api-promotion.how_it_works": "Develop communication strategies to promote reusable capabilities to target audiences, including internal channels, communities, demos, and enablement events.",
+    "station.api-promotion.how_it_works.1": "Create promotional materials such as use cases, success stories, and release notes that highlight value and benefits.",
+    "station.api-promotion.how_it_works.2": "Engage with relevant communities and forums to share updates, gather feedback, and promote usage.",
+    "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
+    "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
+    "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
+    "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
+    "station.partner-integration.outcomes": "Partner integration processes established",
+    "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
+    "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
+    "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
+    "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
+    "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
+    "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
+    "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
+    "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
+    "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
+    "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
+    "station.api-mindset.outcomes": "API-first culture established across the organization",
+    "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
+    "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
+    "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
+    "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
+    "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
+    "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
+    "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
+    "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
+    "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
+    "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
+    "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
+    "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
+    "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
+    "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
+    "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
+    "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
+    "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
+    "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
+    "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
+    "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
+    "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
+    "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
+    "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
+    "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
+    "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
+    "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
+    "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
+    "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
+    "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
+    "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
+    "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
+    "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
+    "station.operating-guidelines.outcomes": "API governance practices established",
+    "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
+    "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
+    "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
+    "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
+    "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
+    "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
+    "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
+    "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
+    "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
+    "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
+    "station.portfolio-management.outcomes": "API portfolio management practices established",
+    "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
+    "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
+    "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
+    "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
+    "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
+    "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
+    "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
+    "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
+    "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
+    "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
+    "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
+    "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
+    "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
+    "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
+    "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
+    "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
+    "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.title": "Strategy",
+    "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
+    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
+    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
+    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
+    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
+    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Architecture & Platform Decisions",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "A justified architecture choice",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
+    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
+    "cycle.capability-productization-cycle.station.api-design.title": "Solution & Interface Design",
+    "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
+    "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+    "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
+    "cycle.capability-productization-cycle.station.api-design.outcomes": "A designed contract for the selected pattern",
+    "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+    "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
+    "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+    "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
+    "cycle.capability-productization-cycle.station.api-delivery.title": "Delivery & Operations",
+    "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+    "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
+    "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
+    "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+    "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
+    "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
+    "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Traceable delivery and release controls",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
+    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
+    "cycle.capability-productization-cycle.station.api-audit.title": "Quality & Readiness Assurance",
+    "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+    "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
+    "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
+    "cycle.capability-productization-cycle.station.api-audit.outcomes": "Documented readiness for release and reuse",
+    "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
+    "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
+    "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
+    "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+    "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+    "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
+    "cycle.capability-productization-cycle.station.api-publishing.title": "Publishing & Enablement",
+    "cycle.capability-productization-cycle.station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
+    "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+    "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
+    "cycle.capability-productization-cycle.station.api-publishing.outcomes": "A discoverable reusable capability",
+    "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
+    "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
+    "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
+    "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
+    "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
+    "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitoring & Improvement",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Measured capability health and value",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
+    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
+  }
+]
diff --git a/src/data/method/fi/labels.cycles.json b/src/data/method/fi/labels.cycles.json
new file mode 100644
index 0000000..d6b6f75
--- /dev/null
+++ b/src/data/method/fi/labels.cycles.json
@@ -0,0 +1,107 @@
+{
+  "cycles.title": "Cycle Views",
+  "cycles.description": "Audience-specific views over the APIOps Cycles method graph.",
+  "cycle.capability-productization-cycle.title": "Kyvykkyyksien tuotteistamisen sykli",
+  "cycle.capability-productization-cycle.description": "Tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, tulisiko toteutuksen olla APIt, tapahtumat, tiedostot, virrat, datatuotteet, tekoälypohjaiset palvelut, suora integrointi vai hybridimalli.",
+  "cycle.capability-productization-cycle.purpose": "Tunnista ja tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, tulisiko toteutuksen olla APIt, tapahtumat, tiedostot, virrat, datatuotteet, tekoälypohjaiset palvelut, suora integrointi vai hybridimalli.",
+  "cycle.api-productization-cycle.title": "API tuotteistamisen sykli",
+  "cycle.api-productization-cycle.description": " Apeihin keskittynyt APIOps Cycles reitti APIen tuotteistukseen, suunnitteluun, toteutukseen, julkaisuun ja parantamiseen.",
+  "cycle.api-productization-cycle.purpose": "API-keskeinen menetelmämatka tiimeille, jotka jo tietävät että tarkoitettu toteutustapa on API-tuote.",
+  "cycle.integration-productization-cycle.title": "Integraation tuotteistamisen sykli",
+  "cycle.integration-productization-cycle.description": "Sykli uudelleenkäytettävien integraatiokykyjen tuotteistukseen ennen kuin valitaan konkreettinen integraatiomalli.",
+  "cycle.integration-productization-cycle.purpose": "Opastaa uudelleenkäytettävän integraatiokykyjen suunnittelua ennen APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden, suoran integroinnin tai hybridimallien valintaa.",
+  "cycle.station.capability-strategy": "Strategia",
+  "cycle.station.consumer-requirements-onboarding": "Hyödyntäjien vaatimukset ja käyttöönottoprosessi",
+  "cycle.station.architecture-platform-decisions": "Arkkitehtuuri ja alustaratkaisut",
+  "cycle.station.solution-interface-design": "Ratkaisu- ja rajapintasuunnittelu",
+  "cycle.station.delivery-operations": "Toteutus ja ylläpito",
+  "cycle.station.quality-readiness-assurance": "Laadun ja valmiuden varmistus",
+  "cycle.station.publishing-enablement": "Julkaisu ja käyttöönoton tuki",
+  "cycle.station.monitoring-improvement": "Seuranta & parantaminen",
+  "cycle.station.api-product-strategy": "API-tuotestrategia",
+  "cycle.station.api-consumer-experience": "API-hyödyntäjäkokemus",
+  "cycle.station.api-platform-architecture": "API-alustan arkkitehtuuri",
+  "cycle.station.api-design": "API-suunnittelu",
+  "cycle.station.api-delivery": "API-toteutus",
+  "cycle.station.api-audit": "API-auditointi",
+  "cycle.station.api-publishing": "API-julkaisu",
+  "cycle.station.monitoring-and-improving": "Seuranta & parantaminen",
+  "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyksien strategia",
+  "cycle.station.integration-consumer-requirements-onboarding": "Integraatiohyödyntäjien vaatimukset ja käyttöönottoprosessi",
+  "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuriratkaisu",
+  "cycle.station.integration-solution-design": "Integraation ratkaisusuunnittelu",
+  "cycle.station.integration-delivery-operations": "Integraation toteutus ja toiminta",
+  "cycle.station.integration-readiness-assurance": "Integraatioiden laadunvarmistus",
+  "cycle.station.capability-publishing": "Kyvykkyyksien julkaisu",
+  "cycle.station.integration-monitoring-improvement": "Integraatioden seuranta & parantaminen",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability strategy before choosing the implementation style.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to choose architecture and platform capabilities.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver and operate the selected solution mechanism.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Assure quality, governance, and readiness before release.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish capability information so consumers can discover, request, onboard, and get support.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities.",
+  "cycle.owner.business-owner": "Business owner",
+  "cycle.owner.domain-expert": "Domain expert",
+  "cycle.owner.capability-owner": "Capability owner",
+  "cycle.owner.consumer-representative": "Consumer representative",
+  "cycle.owner.enterprise-architect": "Enterprise architect",
+  "cycle.owner.platform-owner": "Platform owner",
+  "cycle.owner.api-product-owner": "API product owner",
+  "cycle.owner.api-platform-owner": "API platform owner",
+  "cycle.owner.integration-architect": "Integration architect",
+  "cycle.owner.solution-architect": "Solution architect",
+  "cycle.template.intent-fit.title": "Intent & Fit",
+  "cycle.template.intent-fit.description": "Capture the business outcome, consumers, producers, scope, constraints, and decision status.",
+  "cycle.template.requirements.title": "Requirements",
+  "cycle.template.requirements.description": "Gather expert input using the recommended questions. Treat answers as inputs to design decisions, not final design decisions.",
+  "cycle.template.architecture-decision.title": "Architecture Decision",
+  "cycle.template.architecture-decision.description": "Compare viable architecture choices against the gathered requirements, evidence, risks, and open questions.",
+  "cycle.template.api-architecture-decision.title": "API Architecture Decision",
+  "cycle.template.api-architecture-decision.description": "Document API architecture, platform, security, lifecycle, and publishing decisions.",
+  "cycle.template.integration-pattern-decision.title": "Integration Pattern Decision",
+  "cycle.template.integration-pattern-decision.description": "Compare APIs, events, files, streams, data products, direct integration, and hybrid options against requirements.",
+  "cycle.template.human-validation.title": "Human Validation",
+  "cycle.template.human-validation.description": "Document who validates AI-assisted outputs and which decisions require human accountability.",
+  "cycle.template.adr.title": "Architecture Decision Record",
+  "cycle.template.adr.description": "Record the selected decision, rationale, alternatives, consequences, evidence, and follow-up actions.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Frame the API as a product with clear value proposition, consumers, business model, ownership, and lifecycle intent.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Define API consumer segments, onboarding paths, expectations, and experience requirements before design decisions are locked.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choose and validate the API platform, architecture, governance, and operational constraints needed for the product.",
+  "cycle.api-productization-cycle.station.api-design.description": "Design the API contract, interaction model, schemas, policies, and usability details before implementation.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Implement, test, secure, automate, and operate the API product through the delivery pipeline.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validate API quality, compliance, readiness, evidence, and release criteria before publication.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publish the API product so consumers can discover, evaluate, request access, onboard, and get support.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitor API health, adoption, consumer outcomes, reliability, and improvement opportunities after release.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting a pattern.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decide the integration architecture, platform capabilities, constraints, and governance model for the capability.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Design the integration solution, contracts, payloads, events, APIs, files, or interaction patterns selected for the capability.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability across its selected delivery pattern.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover, request, reuse, onboard, and get support.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.",
+  "cycle.automation-cycle.title": "Automation Cycle",
+  "cycle.automation-cycle.description": "A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.",
+  "cycle.automation-cycle.purpose": "Productize automation opportunities into governed workflows with clear users, platforms, controls, delivery paths, enablement, and monitoring.",
+  "cycle.audience.automation-owners": "Automation owners",
+  "cycle.audience.process-owners": "Process owners",
+  "cycle.audience.automation-teams": "Automation teams",
+  "cycle.station.automation-opportunity-strategy": "Automation Opportunity Strategy",
+  "cycle.station.process-user-requirements": "Process/User Requirements",
+  "cycle.station.automation-platform-decision": "Automation Platform Decision",
+  "cycle.station.automation-workflow-design": "Automation Workflow Design",
+  "cycle.station.automation-delivery": "Automation Delivery",
+  "cycle.station.automation-readiness-review": "Automation Readiness Review",
+  "cycle.station.automation-enablement": "Automation Enablement",
+  "cycle.station.automation-monitoring-improvement": "Automation Monitoring & Improvement",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration model, governance controls, and operational constraints.",
+  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, and exception paths.",
+  "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation with clear ownership and rollback paths.",
+  "cycle.automation-cycle.station.api-audit.description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.",
+  "cycle.automation-cycle.station.api-publishing.description": "Enable users and operators with discovery, onboarding, operating instructions, support paths, and change communication.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities."
+}
diff --git a/src/data/method/fi/labels.resources.json b/src/data/method/fi/labels.resources.json
index cd88e3c..20edc66 100644
--- a/src/data/method/fi/labels.resources.json
+++ b/src/data/method/fi/labels.resources.json
@@ -403,5 +403,40 @@
   "resource.rest-canvas.steps.2": "Määritä HTTP-verbit, joita käytetään vuorovaikutuksessa resurssien kanssa.",
   "resource.rest-canvas.steps.3": "Anna esimerkkipyynnöt ja -vastaukset kullekin verbille",
   "resource.rest-canvas.tips.1": "Varmistetaan, että resurssien URI:t ovat intuitiivisia ja johdonmukaisia.",
-  "resource.rest-canvas.tips.2": "asiakirjan virheiden käsittely ja vastauskoodit"
+  "resource.rest-canvas.tips.2": "asiakirjan virheiden käsittely ja vastauskoodit",
+  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
+  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
+  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
+  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
+  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
+  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
+  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
+  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
+  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
+  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
+  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
 }
diff --git a/src/data/method/fi/labels.stakeholders.json b/src/data/method/fi/labels.stakeholders.json
index 383b1fa..206a8d4 100644
--- a/src/data/method/fi/labels.stakeholders.json
+++ b/src/data/method/fi/labels.stakeholders.json
@@ -8,28 +8,42 @@
   "stakeholder.api-program-owner.description": "Koordinoi API-portfolion käytäntöjä, organisaation suuntautumista ja pitkän aikavälin API-kyvykkyyksien kehitystä.",
   "stakeholder.api-product-owner.title": "API-tuoteomistaja",
   "stakeholder.api-product-owner.description": "Ohjaa API-mahdollisuutta, priorisointia ja tuotetasolla tehtyjä päätöksiä elinkaaren aikana.",
-  "stakeholder.domain-expert.title": "Liiketoiminta-asiantuntija",
-  "stakeholder.domain-expert.description": "Tuo syvällistä tietoa liiketoiminta-alasta, käsitteistä, säännöistä ja rajoituksista, joita APIn täytyy heijastaa.",
-  "stakeholder.customer-or-partner-representative.title": "Asiakas- tai kumppaniedustaja",
-  "stakeholder.customer-or-partner-representative.description": "Edustaa APIn ulkoisten asiakkaiden, kumppaneiden tai muiden hyödyntäjien tarpeita ja näkökulmia.",
-  "stakeholder.api-consumer-representative.title": "API-hyödyntäjien edustaja",
-  "stakeholder.api-consumer-representative.description": "Edustaa kehittäjien, integraattoreiden tai muiden API-hyödyntäjien tarpeita, jotka käyttävät APIa suoraan.",
+  "stakeholder.capability-owner.title": "Capability Owner",
+  "stakeholder.capability-owner.description": "",
+  "stakeholder.domain-specialist.title": "Liiketoiminta-asiantuntija",
+  "stakeholder.domain-specialist.description": "Tuo syvällistä tietoa liiketoiminta-alasta, käsitteistä, säännöistä ja rajoituksista, joita APIn täytyy heijastaa.",
+  "stakeholder.customer-specialist.title": "Asiakas- tai kumppaniedustaja",
+  "stakeholder.customer-specialist.description": "Edustaa APIn ulkoisten asiakkaiden, kumppaneiden tai muiden hyödyntäjien tarpeita ja näkökulmia.",
+  "stakeholder.api-consumer-specialist.title": "API-hyödyntäjien edustaja",
+  "stakeholder.api-consumer-specialist.description": "Edustaa kehittäjien, integraattoreiden tai muiden API-hyödyntäjien tarpeita, jotka käyttävät APIa suoraan.",
   "stakeholder.platform-architect.title": "Alusta-arkkitehti",
   "stakeholder.platform-architect.description": "Ohjaa alustan, integraation, skaalautuvuuden ja arkkitehtuurin päätöksiä, jotka määrittelevät, miten API on rakennettu ja toimii.",
+  "stakeholder.api-architect.title": "API Architect",
+  "stakeholder.api-architect.description": "",
+  "stakeholder.integration-architect.title": "Integration Architect",
+  "stakeholder.integration-architect.description": "",
+  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.description": "",
   "stakeholder.api-designer.title": "API-suunnittelija",
   "stakeholder.api-designer.description": "Muokkaa API-sopimusta, vuorovaikutusmallia, johdonmukaisuutta ja käytettävyyttä exponoituja kykyjä.",
-  "stakeholder.delivery-engineer.title": "Ohjelmistokehittäjä",
-  "stakeholder.delivery-engineer.description": "Omistaa toteutuksen, automaation, testauksen ja julkaisun kulkuun liittyvät kysymykset, jotka ovat tarpeen toimittaa API luotettavasti.",
+  "stakeholder.api-engineer.title": "Ohjelmistokehittäjä",
+  "stakeholder.api-engineer.description": "Omistaa toteutuksen, automaation, testauksen ja julkaisun kulkuun liittyvät kysymykset, jotka ovat tarpeen toimittaa API luotettavasti.",
+  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.automation-owner.description": "",
+  "stakeholder.process-owner.title": "Process Owner",
+  "stakeholder.process-owner.description": "",
+  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.description": "",
   "stakeholder.security-specialist.title": "Turvallisuusasiantuntija",
   "stakeholder.security-specialist.description": "Varmistaa, että turvallisuusriskit, kontrollit ja luottamusrajat käsitellään koko API-kehitysprosessin aikana.",
-  "stakeholder.compliance-legal-specialist.title": "Vaatimuksenmukaisuuden ja oikeudellinen asiantuntija",
-  "stakeholder.compliance-legal-specialist.description": "Selventää oikeudellisia, tietosuojaa koskevia, sääntelyä ja sopimusvaatimuksia, jotka vaikuttavat APIin.",
-  "stakeholder.governance-owner.title": "API-hallinnan omistaja",
-  "stakeholder.governance-owner.description": "Vastaa API-hallintaprosesseista, ohjeista ja päätöksenteosta, joka määrittelee, miten API-kehityspäätökset tehdään ja dokumentoidaan.",
-  "stakeholder.documentation-devrel-owner.title": "Dokumentoinnin ja kehittäjäsuhteiden omistaja",
-  "stakeholder.documentation-devrel-owner.description": "Varmistaa, että API-dokumentaatio, esimerkit, koulutus ja kehittäjäsuhteiden strategiat tukevat API-hyödyntäjien tarpeita.",
-  "stakeholder.support-operations-owner.title": "Tuki- ja operaatioiden omistaja",
-  "stakeholder.support-operations-owner.description": " Vastaa API-tuen, valvonnan, vianmäärityksen ja jatkuvan parantamisen prosesseista, jotka varmistavat APIn luotettavuuden ja hyödyntäjien tyytyväisyyden.",
-  "stakeholder.partner-vendor-manager.title": "Kumppani- ja toimittajavastaava",
-  "stakeholder.partner-vendor-manager.description": "Koordinoi ulkoisia kumppanisuhde, toimittajasuhteita ja vendor-suhteita, jotka vaikuttavat API-strategiaan ja -kehitykseen."
+  "stakeholder.compliance-specialist.title": "Vaatimuksenmukaisuuden ja oikeudellinen asiantuntija",
+  "stakeholder.compliance-specialist.description": "Selventää oikeudellisia, tietosuojaa koskevia, sääntelyä ja sopimusvaatimuksia, jotka vaikuttavat APIin.",
+  "stakeholder.governance-specialist.title": "API-hallinnan omistaja",
+  "stakeholder.governance-specialist.description": "Vastaa API-hallintaprosesseista, ohjeista ja päätöksenteosta, joka määrittelee, miten API-kehityspäätökset tehdään ja dokumentoidaan.",
+  "stakeholder.api-devrel-specialist.title": "Dokumentoinnin ja kehittäjäsuhteiden omistaja",
+  "stakeholder.api-devrel-specialist.description": "Varmistaa, että API-dokumentaatio, esimerkit, koulutus ja kehittäjäsuhteiden strategiat tukevat API-hyödyntäjien tarpeita.",
+  "stakeholder.operations-specialist.title": "Tuki- ja operaatioiden omistaja",
+  "stakeholder.operations-specialist.description": " Vastaa API-tuen, valvonnan, vianmäärityksen ja jatkuvan parantamisen prosesseista, jotka varmistavat APIn luotettavuuden ja hyödyntäjien tyytyväisyyden.",
+  "stakeholder.partner-specialist.title": "Kumppani- ja toimittajavastaava",
+  "stakeholder.partner-specialist.description": "Koordinoi ulkoisia kumppanisuhde, toimittajasuhteita ja vendor-suhteita, jotka vaikuttavat API-strategiaan ja -kehitykseen."
 }
diff --git a/src/data/method/fi/labels.stations.json b/src/data/method/fi/labels.stations.json
index 5b2b36f..2e96a4a 100644
--- a/src/data/method/fi/labels.stations.json
+++ b/src/data/method/fi/labels.stations.json
@@ -1,377 +1,473 @@
 {
- "group.core-stations.title": "APIn elinkaaren ydinasemat",
- "group.core-stations.description": "API Metron ydinasemat, joissa tiimit voivat oppia rakentamaan ja hallinnoimaan rajapintoja tehokkaasti.",
- "group.sub-stations.title": "APIn elinkaaren lähiöasemat",
- "group.sub-stations.description": "Lähiöasemat, jotka tarjoavat lisäresursseja, työkaluja ja parhaita käytäntöjä API-tiimeille.",
- "station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
- "station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, käyttäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
- "station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, ei tuotteina. Tulos? Hämmentyneitä kuluttajia, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
- "station.api-product-strategy.apply_in_work": "Tarjotaan ohjeita ja malleja API-liiketoimintamallien, arvolupausten ja etenemissuunnitelmien luomista varten.",
- "station.api-product-strategy.outcomes": "Suoraviivainen API-arvolupaus ja yleisö",
- "station.api-product-strategy.how_it_works": "Tutki asiakkaan tai yhteistyökumppanin ongelmaa, jonka oletat voivasi ratkaista APIen avulla. Kartoita sidosryhmät, niiden matkat ja tulokset Customer Journey canvasin avulla.",
- "station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia käyttäjiä varten.",
- "station.api-consumer-experience.description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen.",
- "station.api-consumer-experience.why_it_matters": "Hyvät aPIt eivät ainoastaan toimi - ne tuntuvat intuitiivisilta. Riippumatta siitä, onko hyödyntäjä sisäinen kehittäjä, ulkoinen kumppani vai tekoälyagentti, heidän kokemuksensa ratkaisee hyväksynnän. Ilman selkeää kokemussuunnitelmaa",
- "station.api-consumer-experience.how_it_works": "Tarkastele olemassa olevaa API Value Proposition Canvasta API-hyödyntäjän näkökulmasta. Säilytä tuetut liiketoimintatehtävät vakaina ja rikasta tuskaa lievittäviä ja hyötyjä mahdollistavia ominaisuuksia API-hyödyntäjien näkökulmalla, jotta ne voivat ohjata myöhempiä suunnittelupäätöksiä.",
- "station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-käyttäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
- "station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-käyttäjälle.",
- "station.api-consumer-experience.apply_in_work": "Tarjotaan ohjeita, työkaluja ja palautemekanismeja sisäisten ja ulkoisten kehittäjien ja kumppaneiden kokemusten ymmärtämiseksi, analysoimiseksi ja parantamiseksi.",
- "station.api-consumer-experience.outcomes": "Tunnista ja priorisoi API-asiakkaat",
- "station.api-platform-architecture.title": "API-alustan arkkitehtuuri",
- "station.api-platform-architecture.description": "Varmistetaan skaalautuvuus, uudelleenkäyttö ja hallinta API- ja alustakomponenttien välillä.",
- "station.api-platform-architecture.why_it_matters": "Kun rajapinnat skaalautuvat eri tiimeille, alustan on mahdollistettava hallinta ja uudelleenkäyttö nopeutta estämättä. Tällä asemalla kerrotaan, miten API-arkkitehtuurit voidaan suunnitella pitkäikäisiksi, turvallisiksi ja tehokkaiksi.",
- "station.api-platform-architecture.apply_in_work": "Perustetaan skaalautuva, turvallinen ja vaatimustenmukainen infrastruktuuri API-toimintoja varten. Annetaan ohjeita arkkitehtuurin parhaista käytännöistä.",
- "station.api-platform-architecture.outcomes": "Vähennä turhia API-rajapintoja ja vähennä pilvialustakustannuksia.",
- "station.api-platform-architecture.how_it_works": "Business Impact Canvas auttaa tunnistamaan ja lieventämään APIn saatavuuteen, tietoturvaan ja toiminnallisuuteen liittyviä riskejä ja tukemaan tietoon perustuvia arkkitehtuuripäätöksiä.",
- "station.api-design.title": "API-design - Suunnittele arvoa tuottavia rajapintoja",
- "station.api-design.description": "Luo API-suunnitelmia, jotka ovat johdonmukaisia, uudelleenkäytettäviä ja perustuvat liiketoiminnallisiin tavoitteisiin sekä yhteisiin standardeihin.",
- "station.api-design.why_it_matters": "APIen suunnittelu ei tarkoita pelkästään päätepisteiden (endpoints) nimeämistä. Hyvä suunnittelu varmistaa, että APIt ovat käyttökelpoisia, johdonmukaisia ja linjassa liiketoiminnallisten ja teknisten tavoitteiden kanssa. Huono suunnittelu johtaa tiukkoihin riippuvuuksiin, heikkoon uudelleenkäytettävyyteen ja kalliiseen uudelleen toteutukseen eri tiimien välillä.",
- "station.api-design.apply_in_work": "Tarjoa uudelleenkäytettäviä suunnittelumalleja, yhteisiä standardeja ja validointityökaluja API-määrityksille. Varmista, että suunnittelupäätökset ovat johdonmukaisia, tarkistettuja varhaisessa vaiheessa ja linjassa liiketoiminnallisten tavoitteiden kanssa.",
- "station.api-design.outcomes": "Hyvin dokumentoidut ja johdonmukaiset API-mallit",
- "station.api-design.how_it_works": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri rajapinnoille.",
- "station.api-delivery.title": "API-kehitys - Kehitä turvalliset ja luotettavat rajapinnat",
- "station.api-delivery.description": "Rakenna, testaa ja julkaise rajapintoja käyttämällä nykyaikaisia jakeluputkia ja parhaita teknisiä käytäntöjä.",
- "station.api-delivery.why_it_matters": "Parhaatkin API-suunnitelmat epäonnistuvat, jos kehitys on epäjohdonmukaista. Tällä asemalla varmistetaan, että rajapinnat rakennetaan laadukkaasti, testataan perusteellisesti ja otetaan käyttöön luotettavasti, mikä mahdollistaa nopeammat iteraatiot ja suuremman luottamuksen.",
- "station.api-delivery.apply_in_work": "Toimittaa koodauskehyksiä, kirjastoja ja standardeja API-toteutusta varten. CI/CD-putkien, laadunvarmistuskehysten ja käyttöönottoautomaatiotyökalujen toteuttaminen.",
- "station.api-delivery.outcomes": "Rajapinnat, jotka on toteutettu testattujen kehysten ja mallien avulla.",
- "station.api-delivery.how_it_works": "Käytä API-kehityksen parhaita käytäntöjä ohjeena validoidun sopimuksen toteuttamiseen vakiintuneilla kehysrakenteilla ja kirjastoilla varmistaen, että tulos on uudelleenkäytettävä ja ylläpidettävä.",
- "station.api-audit.title": "API-auditointi - API-rajapintojen tarkastus vaatimustenmukaisuuden ja laadun varmistamiseksi",
- "station.api-audit.description": "Varmista, että APIt täyttävät liiketoiminta-, suunnittelu- ja toimintastandardit ennen julkaisua ja käyttöönottoa.",
- "station.api-audit.why_it_matters": "APIt ovat pitkäikäisiä tuotteita, ja niiden on täytettävä laatu-, johdonmukaisuus- ja vaatimustenmukaisuusodotukset. Auditointi yhdistää suunnittelupäätökset, toteutuksen ja toimintavalmiuden määriteltyihin standardeihin, mikä vähentää riskejä ennen käyttöönottoa.",
- "station.api-audit.apply_in_work": "Luo johdonmukainen auditointiprosessi, joka arvioi APIn valmiutta elinkaaren eri vaiheissa määriteltyjen kriteerien, todisteiden ja standardien avulla. Varmista, että puutteet tunnistetaan varhaisessa vaiheessa ja korjataan ennen julkaisua.",
- "station.api-audit.outcomes": "APIt täyttävät sisäiset ja ulkoiset standardit",
- "station.api-audit.how_it_works": "Suorita tarkastuksia varmistaaksesi, että rajapinnat täyttävät organisatoriset, tekniset ja oikeudelliset standardit ennen julkaisemista.",
- "station.api-publishing.title": "API-julkaiseminen - Julkaise APIt luotettavasti",
- "station.api-publishing.description": "Esittele APIt turvallisesti ja selkeästi oikealle yleisölle oikean dokumentaation ja prosessien avulla.",
- "station.api-publishing.why_it_matters": "Julkaiseminen on muutakin kuin käyttöönottoa - kyse on löydettävyydestä, saatavuudesta ja tuesta. Jos rajapintoja ei julkaista oikein, niitä ei käytetä, käytetä uudelleen tai suojata tehokkaasti.",
- "station.api-publishing.apply_in_work": "Mahdollistetaan APIen julkaiseminen asiaankuuluvassa ympäristössä ja selkeät rekisteröinti- ja käyttöoikeusmekanismit (esim. API-avaimet, OAuth, tilaussuunnitelmat) API-hyödyntäjäsegmenttien sekä turvallisuus- ja vaatimustenmukaisuusvaatimusten mukaan.",
- "station.api-publishing.outcomes": "APIt julkaistaan oikeassa ympäristössä (yksityinen, kumppani, julkinen).",
- "station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille rajapinnan käyttäjille.",
- "station.monitoring-and-improving.title": "Seuranta ja parantaminen - API-arvoa varten",
- "station.monitoring-and-improving.description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen.",
- "station.monitoring-and-improving.why_it_matters": "API-kehitys ei lopu käynnistykseen. Ilman seurantaa tiimit eivät voi parantaa käyttöönottoa, suorituskykyä tai ROI",
- "station.monitoring-and-improving.apply_in_work": "Ota käyttöön analytiikkakehykset suorituskyvyn ja sitoutumisen seuraamiseksi. Kehitetään palautesilmukoita, analytiikkatyökaluja ja sitouttamisstrategioita API-rajapintoja varten.",
- "station.monitoring-and-improving.outcomes": "Suorituskyvyn ja käytön mittarit määritellään ja niitä seurataan.",
- "station.monitoring-and-improving.how_it_works": "Seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
- "station.user-experience.title": "Käyttäjäkokemus - Suunnittele APIt käyttäjälähtöisesti",
- "station.user-experience.description": "Varmistetaan, että rajapinnat on suunniteltu loppukäyttäjää ajatellen ja että ne tarjoavat saumattoman ja intuitiivisen käyttökokemuksen.",
- "station.user-experience.why_it_matters": "APIt eivät ole vain teknisiä tuotteita, vaan ne ovat käyttäjäkohtaisia tuotteita. Huono käyttökokemus voi johtaa vähäiseen käyttöön ja turhautumiseen. Tämä asema auttaa tiimejä suunnittelemaan APIt, jotka ovat käyttäjäystävällisiä ja vastaavat kuluttajien tarpeita.",
- "station.user-experience.apply_in_work": "Tarjotaan käyttäjäkokemusta koskevia ohjeita, malleja ja työkaluja API-suunnittelua varten. Varmistetaan, että tiimit noudattavat käyttäjäkeskeisiä suunnittelukäytäntöjä ja sisällyttävät käyttäjäpalautteen API-iteraatioihin.",
- "station.user-experience.outcomes": "APIt on suunniteltu käyttäjien tarpeet mielessä pitäen",
- "station.user-experience.how_it_works": "Käyttäjäpersoonien käyttö loppukäyttäjien tarpeiden ja odotusten ymmärtämiseksi.",
- "station.market-insights.title": "Markkinatietoa - API-maiseman ymmärtäminen",
- "station.market-insights.description": "Analysoi markkinasuuntauksia, kilpailijoiden rajapintoja ja alan standardeja rajapintastrategian laatimiseksi.",
- "station.market-insights.why_it_matters": "Markkinatilanteen ymmärtäminen auttaa tiimejä tunnistamaan mahdollisuuksia, välttämään sudenkuoppia ja mukauttamaan rajapintansa alan standardeihin. Tämä asema tarjoaa työkaluja markkinasuuntausten ja kilpailijoiden tarjonnan analysointiin.",
- "station.market-insights.apply_in_work": "Tarjotaan markkinatutkimustyökaluja, kilpailija-analyysimalleja ja alan standardeja koskevia resursseja. Varmistetaan, että tiimit pysyvät ajan tasalla markkinasuuntauksista ja sisällyttävät näkemykset API-strategiaan.",
- "station.market-insights.outcomes": "Markkinatrendit ja kilpailijoiden APIt analysoitu",
- "station.market-insights.how_it_works": "Markkinatutkimuksen tekeminen API-toimialalla vallitsevien suuntausten, mahdollisuuksien ja uhkien tunnistamiseksi.",
- "station.business-goals.title": "Liiketoiminnalliset tavoitteet - Kohdista rajapinnat liiketoimintatavoitteisiin.",
- "station.business-goals.description": "Varmistetaan, että rajapinnat ovat linjassa liiketoiminnan tavoitteiden kanssa ja edistävät organisaation yleisiä tavoitteita.",
- "station.business-goals.why_it_matters": "Rajapintoja ei pidä rakentaa erillään, vaan niiden on tuettava ja edistettävä liiketoiminnan tavoitteita. Tämä asema auttaa tiimejä sovittamaan rajapinnat strategisiin tavoitteisiin ja varmistamaan, että ne tuottavat todellista liiketoiminta-arvoa.",
- "station.business-goals.apply_in_work": "Tarjotaan liiketoimintasuuntautumiskehyksiä, malleja ja työkaluja API-liiketoiminta-arvon määrittelyyn. Varmistetaan, että tiimit tarkistavat ja sovittavat sovellusrajapinnat säännöllisesti yhteen muuttuvien liiketoimintatavoitteiden kanssa.",
- "station.business-goals.outcomes": "APIt linjassa liiketoiminnan tavoitteiden kanssa",
- "station.business-goals.how_it_works": "Määrittele liiketoimintatavoitteet ja se, miten rajapinnat voivat tukea niitä käyttämällä **liiketoimintamallia (Business Model Canvas**). Jos liiketoimintasi tarkoituksena on tarjota rajapintoja, käy läpi *API-tuotestrategia-asema* ja täytä **API-liiketoimintamalli Canvas**.",
- "station.competitive-analysis.title": "Kilpailuanalyysi - pysy kärjessä API-markkinoilla",
- "station.competitive-analysis.description": "Analysoi kilpailijoiden rajapinnat vahvuuksien, heikkouksien ja erottautumismahdollisuuksien tunnistamiseksi.",
- "station.competitive-analysis.why_it_matters": "Kilpailutilanteen ymmärtäminen auttaa tiimejä tunnistamaan API-rajapintojensa puutteet, mahdollisuudet ja parannuskohteet. Tämä asema tarjoaa työkaluja kilpailijoiden analysointiin ja API-strategian laatimiseen.",
- "station.competitive-analysis.apply_in_work": "Tarjotaan kilpailuanalyysityökaluja, malleja ja resursseja. Varmistetaan, että tiimit analysoivat säännöllisesti kilpailijoita ja sisällyttävät näkemykset API-strategiaan ja -suunnitteluun.",
- "station.competitive-analysis.outcomes": "Kilpailijoiden rajapintojen vahvuudet ja heikkoudet analysoidaan.",
- "station.competitive-analysis.how_it_works": "Suorita kilpailija-analyysi tärkeimpien kilpailijoiden, niiden API-tarjonnan sekä niiden vahvuuksien ja heikkouksien tunnistamiseksi.",
- "station.ecosystem-vision.title": "Ekosysteemin visio - Rakenna rajapinnat kukoistavaa ekosysteemiä varten.",
- "station.ecosystem-vision.description": "Luo visio siitä, miten rajapintasi sopivat laajempaan ekosysteemiin, joka mahdollistaa yhteistyön ja innovoinnin.",
- "station.ecosystem-vision.why_it_matters": "APIt eivät ole itsenäisiä tuotteita, vaan osa laajempaa ekosysteemiä. Tämä asema auttaa tiimejä määrittelemään, miten niiden rajapinnat ovat vuorovaikutuksessa muiden järjestelmien, alustojen ja palvelujen kanssa, jotta voidaan luoda kukoistava ekosysteemi, joka edistää yhteistyötä ja innovointia.",
- "station.ecosystem-vision.apply_in_work": "Tarjotaan ekosysteemin visiokehykset, kumppanien sitouttamisstrategiat ja integrointiohjeet. Varmistaa, että tiimit suunnittelevat rajapinnat ekosysteemiä silmällä pitäen ja edistävät kumppanien välistä yhteistyötä.",
- "station.ecosystem-vision.outcomes": "Selkeä ekosysteemin visio rajapinnoille",
- "station.ecosystem-vision.how_it_works": "Määrittele rajapintojesi ekosysteemivisio, mukaan lukien se, miten ne ovat vuorovaikutuksessa muiden järjestelmien ja alustojen kanssa.",
- "station.scalable-infrastructure.title": "Skaalautuva infrastruktuuri - rakenna APIt vankalle perustalle",
- "station.scalable-infrastructure.description": "Varmistetaan, että API-infrastruktuurisi voi skaalautua vastaamaan kasvavaa kysyntää ja tukea korkeaa käytettävyyttä.",
- "station.scalable-infrastructure.why_it_matters": "APIt on rakennettava vankalle infrastruktuurille, joka kestää kasvavan liikenteen ja varmistaa korkean käytettävyyden. Tämä asema tarjoaa ohjeita APIn kasvua ja suorituskykyä tukevan skaalautuvan infrastruktuurin suunnitteluun ja toteuttamiseen.",
- "station.scalable-infrastructure.apply_in_work": "Tarjotaan infrastruktuurin suunnitteluohjeita, pilvipohjaisia malleja ja valvontatyökaluja. Varmistetaan, että tiimit ottavat käyttöön skaalautuvan infrastruktuurin, joka pystyy mukautumaan muuttuviin vaatimuksiin ja tukemaan API-suorituskykyä.",
- "station.scalable-infrastructure.outcomes": "Skaalautuva ja joustava API-infrastruktuuri",
- "station.scalable-infrastructure.how_it_works": "Suunnittele API-infrastruktuuri skaalautuvaksi ja joustavaksi käyttäen pilvipohjaisia malleja ja teknologioita.",
- "station.legal-and-compliance.title": "Lainsäädäntö ja vaatimustenmukaisuus - varmista, että APIt täyttävät sääntelystandardit.",
- "station.legal-and-compliance.description": "Varmistetaan, että rajapinnat noudattavat lakisääteisiä ja lainsäädännöllisiä vaatimuksia ja suojaavat organisaatiota ja käyttäjiä.",
- "station.legal-and-compliance.why_it_matters": "API-rajapintojen on noudatettava oikeudellisia ja sääntelystandardeja organisaation ja käyttäjien suojelemiseksi. Tämä asema tarjoaa työkaluja ja ohjeita, joilla varmistetaan, että rajapinnat täyttävät vaatimustenmukaisuusvaatimukset, vähennetään oikeudellisia riskejä ja varmistetaan tietosuoja.",
- "station.legal-and-compliance.apply_in_work": "Tarjotaan oikeudellisia ja vaatimustenmukaisuutta koskevia puitteita, tarkistuslistoja ja työkaluja API-vaatimustenmukaisuuden varmistamiseksi. Varmistetaan, että tiimit ymmärtävät ja panevat täytäntöön oikeudelliset vaatimukset APIn suunnittelussa, kehittämisessä ja julkaisemisessa.",
- "station.legal-and-compliance.outcomes": "Oikeudellisten ja sääntelystandardien mukaiset APIt",
- "station.legal-and-compliance.how_it_works": "Tunnista rajapintoihin sovellettavat oikeudelliset ja sääntelyvaatimukset, kuten tietosuojaa, yksityisyyttä ja tietoturvaa koskevat vaatimukset.",
- "station.security-and-privacy.title": "Tietoturva ja yksityisyys - Suojaa APIt ja käyttäjät",
- "station.security-and-privacy.description": "Toteuta tietoturva- ja yksityisyydensuojatoimenpiteet, joilla suojataan rajapintoja ja käyttäjätietoja uhkilta ja tietoturvaloukkauksilta.",
- "station.security-and-privacy.why_it_matters": "APIt ovat alttiita tietoturvauhkille ja tietomurroille. Tämä asema tarjoaa ohjeita tietoturva- ja yksityisyydensuojatoimenpiteiden toteuttamiseen, joilla suojataan rajapintoja ja käyttäjätietoja ja varmistetaan luottamus ja vaatimustenmukaisuus.",
- "station.security-and-privacy.apply_in_work": "Tarjotaan tietoturvakehyksiä, -työkaluja ja parhaita käytäntöjä rajapintojen turvallisuutta ja yksityisyyttä varten. Varmistaa, että tiimit toteuttavat tietoturvatoimenpiteitä koko APIn elinkaaren ajan suunnittelusta julkaisuun ja seurantaan.",
- "station.security-and-privacy.outcomes": "Uhkia ja haavoittuvuuksia vastaan suojatut rajapinnat",
- "station.security-and-privacy.how_it_works": "Toteuta turvatoimia, kuten todennus, valtuutus, salaus ja nopeuden rajoittaminen, suojaamaan rajapintoja uhkilta.",
- "station.design-standards.title": "Suunnittelustandardit - Varmistaa johdonmukainen ja laadukas API-suunnittelu.",
- "station.design-standards.description": "Suunnittelustandardien ja -ohjeiden laatiminen, jotta varmistetaan yhdenmukainen ja laadukas API-suunnittelu koko organisaatiossa.",
- "station.design-standards.why_it_matters": "Johdonmukainen ja laadukas API-suunnittelu on olennaisen tärkeää käytettävyyden, ylläpidettävyyden ja skaalautuvuuden kannalta. Tämä asema tarjoaa suunnittelustandardeja ja -ohjeita, joiden avulla tiimit voivat luoda rajapintoja, joita on helppo käyttää, ymmärtää ja ylläpitää.",
- "station.design-standards.apply_in_work": "Suunnittelustandardien dokumentointi, uudelleenkäytettävät komponentit ja suunnittelun tarkistusprosessit. Varmistetaan, että tiimit noudattavat suunnittelustandardeja ja tekevät säännöllisiä tarkistuksia laadukkaan API-suunnittelun ylläpitämiseksi.",
- "station.design-standards.outcomes": "Yhdenmukainen API-suunnittelu koko organisaatiossa",
- "station.design-standards.how_it_works": "Määrittele API-suunnittelun suunnittelustandardit ja -ohjeet, mukaan lukien nimeämiskäytännöt, vastausmuodot ja virheenkäsittely.",
- "station.vendor-management.title": "Toimittajan hallinta - Kolmannen osapuolen API-integraatioiden hallinta",
- "station.vendor-management.description": "Hallinnoi tehokkaasti kolmannen osapuolen API-toimittajia ja integraatioita luotettavuuden ja vaatimustenmukaisuuden varmistamiseksi.",
- "station.vendor-management.why_it_matters": "Kolmannen osapuolen rajapinnat voivat aiheuttaa riskejä ja riippuvuuksia, jotka vaikuttavat rajapintaekosysteemiisi. Tämä asema tarjoaa ohjeita toimittajasuhteiden hallintaan, luotettavuuden ja vaatimustenmukaisuuden varmistamiseen sekä API-strategian noudattamiseen.",
- "station.vendor-management.apply_in_work": "Tarjotaan toimittajien hallintakehykset, arviointikriteerit ja seurantatyökalut. Varmistetaan, että tiimit hallinnoivat tehokkaasti kolmannen osapuolen API-toimittajia ja varmistavat luotettavuuden, vaatimustenmukaisuuden ja organisaation standardien noudattamisen.",
- "station.vendor-management.outcomes": "Tehokkaat myyjien hallinnointiprosessit on otettu käyttöön",
- "station.vendor-management.how_it_works": "Ota käyttöön toimittajahallintaprosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
- "station.contract-design.title": "Sopimussuunnittelu - Määrittele selkeät API-sopimukset",
- "station.contract-design.description": "Luo selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
- "station.contract-design.why_it_matters": "API-sopimukset ovat olennaisen tärkeitä, jotta varmistetaan selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita selkeiden, kattavien ja helposti ymmärrettävien API-sopimusten suunnitteluun.",
- "station.contract-design.apply_in_work": "Tarjotaan sopimussuunnittelumalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
- "station.contract-design.outcomes": "Kullekin ajapinnalle määritellyt selkeät API-sopimukset",
- "station.contract-design.how_it_works": "Määrittele API-sopimukset, joissa hahmotellaan kunkin APIn odotukset, vastuut ja käyttöohjeet.",
- "station.development.title": "Kehitys - Rakenna APIt parhaiden käytäntöjen avulla",
- "station.development.description": "Toteuta rajapinnat parhaiden käytäntöjen ja kehysten avulla laadun, ylläpidettävyyden ja skaalautuvuuden varmistamiseksi.",
- "station.development.why_it_matters": "APIn kehittäminen on kriittinen vaihe, joka määrittää APIn laadun ja luotettavuuden. Tämä asema tarjoaa parhaita käytäntöjä ja kehyksiä API-kehitystä varten, jotta varmistetaan, että APIt rakennetaan korkeiden standardien mukaisesti ja että niitä voidaan ylläpitää ja skaalata tehokkaasti.",
- "station.development.apply_in_work": "Kehityskehysten, kirjastojen ja koodausstandardien tarjoaminen API-toteutusta varten. Varmistaa, että tiimit noudattavat parhaita käytäntöjä, ja suorittaa koodin tarkistuksia API-kehityksen laadun ylläpitämiseksi.",
- "station.development.outcomes": "parhaita käytäntöjä ja kehyksiä hyödyntävät rajapinnat",
- "station.development.how_it_works": "Käytetään vakiintuneita kehyksiä ja kirjastoja rajapintojen toteuttamiseen ja varmistetaan, että ne ovat uudelleenkäytettäviä ja ylläpidettäviä.",
- "station.ci-cd.title": "CI/CD - Automatisoi API-kehitys",
- "station.ci-cd.description": "Ota käyttöön jatkuvan integroinnin ja jatkuvan toimituksen (CI/CD) putket API-kehityksen automatisoimiseksi ja tasaisen laadun varmistamiseksi.",
- "station.ci-cd.why_it_matters": "CI/CD on olennaisen tärkeää sen varmistamiseksi, että rajapinnat toimitetaan nopeasti, luotettavasti ja laadukkaasti. Tämä asema tarjoaa ohjeita CI/CD-putkien toteuttamiseen, jotka automatisoivat API-rajapintojen rakentamis-, testaus- ja käyttöönottoprosessit.",
- "station.ci-cd.apply_in_work": "CI/CD-kehysten, työkalujen ja parhaiden käytäntöjen tarjoaminen API-kehitystä varten. Varmistetaan, että tiimit ottavat käyttöön automatisoidut putket, jotka tukevat APIen jatkuvaa integrointia, testausta ja käyttöönottoa.",
- "station.ci-cd.outcomes": "Automaattiset CI/CD-putket API-toimituksia varten.",
- "station.ci-cd.how_it_works": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
- "station.test-automation.title": "Testausautomaatio - varmista API-laatu",
- "station.test-automation.description": "Ota käyttöön automatisoituja testauskäytäntöjä APIn laadun, luotettavuuden ja suorituskyvyn varmistamiseksi.",
- "station.test-automation.why_it_matters": "Automatisoitu testaus on ratkaisevan tärkeää sen varmistamiseksi, että rajapinnat toimivat oikein ja täyttävät laatuvaatimukset. Tämä asema tarjoaa ohjeita automaattisten testauskäytäntöjen käyttöönottoon, jotka kattavat APIen toiminnallisen, turvallisuus- ja suorituskykytestauksen.",
- "station.test-automation.apply_in_work": "Testausautomaatiokehysten, -työkalujen ja parhaiden käytäntöjen tarjoaminen API-testausta varten. Varmistetaan, että tiimit toteuttavat automatisoituja testejä, jotka kattavat APIen toiminnalliset, turvallisuus- ja suorituskykyyn liittyvät näkökohdat.",
- "station.test-automation.outcomes": "API-rajapintojen automatisoidut testauskäytännöt",
- "station.test-automation.how_it_works": "Käytetään automatisoituja testausvälineitä API-toiminnallisuuden, tietoturvan ja suorituskyvyn validointiin.",
- "station.release-management.title": "Julkaisunhallinta - Hallitse API-julkaisuja tehokkaasti",
- "station.release-management.description": "Ota käyttöön julkaisujen hallintakäytäntöjä sujuvien ja valvottujen API-julkaisujen varmistamiseksi.",
- "station.release-management.why_it_matters": "Tehokas julkaisujen hallinta on olennaisen tärkeää, jotta voidaan varmistaa, että API-julkaisut ovat sujuvia, hallittuja ja liiketoiminnan tarpeiden mukaisia. Tämä asema tarjoaa ohjeita API-julkaisujen hallintaan, mukaan lukien versiointi, käyttöönottostrategiat ja palautusmenettelyt.",
- "station.release-management.apply_in_work": "Tarjotaan julkaisunhallintakehykset, versiointiohjeet ja käyttöönottostrategiat. Varmistetaan, että tiimit noudattavat parhaita käytäntöjä API-julkaisujen hallinnassa, mukaan lukien versiointi, käyttöönotto ja palautusmenettelyt.",
- "station.release-management.outcomes": "Hallitut ja sujuvat API-julkaisut",
- "station.release-management.how_it_works": "Määrittele rajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
- "station.service-agreements.title": "Palvelusopimukset - määrittele API-palvelutasot",
- "station.service-agreements.description": "Laadi palvelusopimukset, joissa määritellään API-toimittajien ja kuluttajien odotukset, palvelutasot ja vastuut.",
- "station.service-agreements.why_it_matters": "Palvelusopimukset ovat olennaisen tärkeitä, jotta voidaan varmistaa selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita sellaisten palvelusopimusten laatimiseen, joissa hahmotellaan odotukset, palvelutasot ja vastuut, mikä vähentää väärinkäsityksiä ja riitoja.",
- "station.service-agreements.apply_in_work": "Tarjotaan palvelusopimusmalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja tarkkaan määritellyt palvelusopimukset, joissa hahmotellaan API-toimittajien ja -kuluttajien odotukset, palvelutasot ja vastuut.",
- "station.service-agreements.outcomes": "Kullekin rajapinnalle määritellyt selkeät palvelusopimukset",
- "station.service-agreements.how_it_works": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin rajapintaa varten.",
- "station.api-consumer-adoption.title": "APIn käyttöönotto - APIn käytön edistäminen",
- "station.api-consumer-adoption.description": "Toteutat strategioita, joilla edistetään API-käyttäjien hyväksyntää ja sitoutumista ja varmistetaan, että API-rajapintoja käytetään tehokkaasti.",
- "station.api-consumer-adoption.why_it_matters": "API-käyttäjien hyväksynnän edistäminen on ratkaisevan tärkeää APIen arvon hyödyntämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä API-kuluttajien sitouttamiseksi ja sen varmistamiseksi, että he ymmärtävät, miten API-rajapintoja käytetään tehokkaasti ja miten niistä saadaan arvoa.",
- "station.api-consumer-adoption.apply_in_work": "Tarjotaan API-kuluttajille resursseja, koulutusmateriaalia ja sitouttamisstrategioita. Varmistetaan, että tiimit toteuttavat strategioita, jotka edistävät API-kuluttajien hyväksyntää, sitoutumista ja tyytyväisyyttä.",
- "station.api-consumer-adoption.outcomes": "APIn käyttöönottostrategioiden toteuttaminen kuluttajille",
- "station.api-consumer-adoption.how_it_works": "Kehitetään käyttöönottoprosesseja ja resursseja, joiden avulla API-käyttäjät ymmärtävät, miten Rajapintoja käytetään tehokkaasti.",
- "station.api-promotion.title": "API-näkyvyys - APIn näkyvyyden ja käytön lisääminen",
- "station.api-promotion.description": "Edistetään rajapintoja näkyvyyden, käytön ja hyväksynnän lisäämiseksi kohdeyleisöjen keskuudessa.",
- "station.api-promotion.why_it_matters": "API-rajapintojen tunnetuksi tekeminen on olennaisen tärkeää niiden näkyvyyden lisäämiseksi ja käytön edistämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä APIen tehokkaaseen markkinointiin kohdeyleisöille, jotta varmistetaan, että nämä ovat tietoisia APIista ja ymmärtävät niiden arvon.",
- "station.api-promotion.apply_in_work": "Tarjotaan markkinointistrategioita, myynninedistämismateriaalia ja resursseja yhteisön sitouttamiseen. Varmistaa, että tiimit toteuttavat tehokkaita APIn edistämisstrategioita, jotka lisäävät näkyvyyttä, käyttöä ja käyttöönottoa kohdeyleisöjen keskuudessa.",
- "station.api-promotion.outcomes": "Toteutetut API-edistämisstrategiat",
- "station.api-promotion.how_it_works": "Kehitä markkinointistrategioita APIen markkinoimiseksi kohdeyleisöille, mukaan lukien sosiaalinen media, blogit ja webinaarit.",
- "station.partner-integration.title": "Kumppanien integrointi - Tee yhteistyötä kumppaneiden kanssa",
- "station.partner-integration.description": "Helpota kumppani-integraatioita API-ominaisuuksien parantamiseksi ja tavoittavuuden laajentamiseksi.",
- "station.partner-integration.why_it_matters": "Kumppani-integraatiot voivat parantaa API-ominaisuuksia ja laajentaa tavoitettavuutta. Tämä asema tarjoaa ohjeita kumppanien kanssa tehtävään yhteistyöhön niiden rajapintojen integroimiseksi, jotta varmistetaan saumaton yhteentoimivuus ja arvon luominen.",
- "station.partner-integration.apply_in_work": "Tarjotaan kumppaneiden integrointikehykset, ohjeet ja seurantatyökalut. Varmistaa, että tiimit tekevät tehokasta yhteistyötä kumppaneiden kanssa API-ominaisuuksien parantamiseksi, ulottuvuuden laajentamiseksi ja innovoinnin edistämiseksi.",
- "station.partner-integration.outcomes": "Kumppaneiden integrointiprosessit on luotu",
- "station.partner-integration.how_it_works": "Tunnista mahdolliset kumppanit, joiden APIt voivat parantaa API-valmiuksiasi ja arvolupaustasi.",
- "station.api-mindset.title": "API-ajattelutapa - API-first -kulttuurin edistäminen",
- "station.api-mindset.description": "Kehitä API-first -ajattelutapaa koko organisaatiossa innovoinnin ja yhteistyön edistämiseksi.",
- "station.api-mindset.why_it_matters": "API-first -ajattelutapa on olennaisen tärkeä innovoinnin ja yhteistyön edistämiseksi koko organisaatiossa. Tämä asema tarjoaa strategioita API-first -kulttuurin kehittämiseksi ja sen varmistamiseksi, että rajapinnat nähdään strategisina voimavaroina, jotka tuottavat liiketoiminta-arvoa.",
- "station.api-mindset.apply_in_work": "Tarjotaan koulutusohjelmia, resursseja ja viestintästrategioita API-first -kulttuurin edistämiseksi. Varmistetaan, että tiimit ymmärtävät APIen arvon ja että niillä on valtuudet johtaa API-strategiaa ja -aloitteita.",
- "station.api-mindset.outcomes": "API-first -kulttuuri on vakiintunut koko organisaatioon",
- "station.api-mindset.how_it_works": "Edistetään rajapintojen arvoa strategisina voimavaroina, jotka lisäävät liiketoiminnan arvoa ja innovointia.",
- "station.roles-and-responsibilities.title": "Roolit ja vastuualueet - API-tiimien rakenteiden määrittelyt",
- "station.roles-and-responsibilities.description": "Määrittele API-tiimeille selkeät roolit ja vastuualueet tehokkaan yhteistyön ja vastuuvelvollisuuden varmistamiseksi.",
- "station.roles-and-responsibilities.why_it_matters": "Selkeät roolit ja vastuualueet ovat olennaisen tärkeitä tehokkaan yhteistyön ja vastuuvelvollisuuden kannalta API-tiimeissä. Tämä asema tarjoaa ohjeita tiimirakenteiden, roolien ja vastuualueiden määrittelyyn ja varmistaa, että kaikki ymmärtävät oman panoksensa API-aloitteisiin.",
- "station.roles-and-responsibilities.apply_in_work": "Tarjotaan tiimirakenneohjeet, roolimäärittelyt ja viestintästrategiat. Varmistetaan, että tiimeillä on selkeät roolit ja vastuut, jotka edistävät tehokasta yhteistyötä ja vastuullisuutta API-aloitteissa.",
- "station.roles-and-responsibilities.outcomes": "API-tiimeille on määritelty selkeät roolit ja vastuut",
- "station.roles-and-responsibilities.how_it_works": "Määrittele API-tiimien tiimirakenteet ja roolit, mukaan lukien API-tuotteen omistajat, kehittäjät, arkkitehdit ja toiminnot.",
- "station.upskilling.title": "Osaamisen kehittäminen - API-taitojen ja -tiedon parantaminen",
- "station.upskilling.description": "Tarjotaan koulutusta ja resursseja API-taitojen ja -tiedon parantamiseksi koko organisaatiossa.",
- "station.upskilling.why_it_matters": "Jatkuva oppiminen ja täydennyskoulutus ovat olennaisen tärkeitä, jotta API-tiimit pysyvät ajan tasalla uusimmista teknologioista, käytännöistä ja suuntauksista. Tämä asema tarjoaa koulutusohjelmia ja resursseja API-taitojen ja -tiedon parantamiseen, jotta tiimit ovat valmiita toimittamaan korkealaatuisia API-rajapintoja.",
- "station.upskilling.apply_in_work": "Tarjotaan koulutusohjelmia, resursseja ja arviointivälineitä API-taitojen ja -tietojen parantamiseksi. Varmistetaan, että tiimeillä on mahdollisuus jatkuvaan oppimiseen, joka antaa heille mahdollisuuden edistää API-innovaatioita ja laatua.",
- "station.upskilling.outcomes": "API-taitojen ja -tiedon parantaminen koko organisaatiossa",
- "station.upskilling.how_it_works": "Tunnistetaan keskeiset API-taidot ja -tiedot, joita on kehitettävä, kuten API-suunnittelu, tietoturva ja suorituskyky.",
- "station.operating-guidelines.title": "Toimintaohjeet - API-hallinnon perustaminen",
- "station.operating-guidelines.description": "Laaditaan toimintaohjeet ja hallintokäytännöt, joilla varmistetaan APIn johdonmukainen hallinta ja laatu.",
- "station.operating-guidelines.why_it_matters": "Tehokas API-hallinta on olennaisen tärkeää, jotta voidaan varmistaa yhdenmukainen API-hallinta, laatu ja vaatimustenmukaisuus. Tämä asema tarjoaa toimintaohjeita ja hallintakäytäntöjä, jotka auttavat tiimejä hallinnoimaan API-rajapintoja tehokkaasti ja varmistamaan, että ne ovat organisaation standardien ja parhaiden käytäntöjen mukaisia.",
- "station.operating-guidelines.apply_in_work": "Toimintaohjeiden, hallintakehysten ja seurantatyökalujen tarjoaminen API-hallintaa varten. Varmistaa, että tiimit noudattavat vakiintuneita käytäntöjä, jotka edistävät johdonmukaista API-hallintaa, laatua ja organisaation standardien noudattamista.",
- "station.operating-guidelines.outcomes": "APIn hallintokäytännöt on vahvistettu",
- "station.operating-guidelines.how_it_works": "Määrittele APIOps Cyclesiin perustuvat toimintaohjeet, joissa hahmotellaan API-hallinnan prosessit, standardit ja parhaat käytännöt.",
- "station.portfolio-management.title": "Portfolionhallinta - hallinnoi API-portfoliota tehokkaasti",
- "station.portfolio-management.description": "Hallinnoida API-salkkua tehokkaasti varmistaaksesi, että se on linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa.",
- "station.portfolio-management.why_it_matters": "Tehokas rajapintasalkun hallinta on olennaisen tärkeää sen varmistamiseksi, että rajapinnat ovat linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa. Tämä asema tarjoaa ohjeita API-salkun hallintaan ja varmistaa, että APIt priorisoidaan, seurataan ja optimoidaan siten, että ne tuottavat mahdollisimman paljon arvoa.",
- "station.portfolio-management.apply_in_work": "Tarjotaan salkunhallintakehykset, priorisointikriteerit ja seurantatyökalut API-hallintaa varten. Varmistaa, että tiimit hallinnoivat API-salkkua tehokkaasti ja varmistavat, että se on linjassa liiketoimintatavoitteiden ja strategisten aloitteiden kanssa ja tuottaa mahdollisimman paljon arvoa.",
- "station.portfolio-management.outcomes": "API-salkunhallintakäytäntöjen käyttöönotto",
- "station.portfolio-management.how_it_works": "Määrittele salkunhallintakäytännöt, joissa hahmotellaan API-salkun hallinnointiprosessit, mukaan lukien priorisointi, seuranta ja optimointi.",
- "station.budget-and-resource-management.title": "Budjetin ja resurssien hallinta - Optimoi API-investoinnit",
- "station.budget-and-resource-management.description": "Optimoi API-aloitteiden budjetin ja resurssien hallinta tehokkaiden investointien ja resurssien kohdentamisen varmistamiseksi.",
- "station.budget-and-resource-management.why_it_matters": "Tehokas talousarvio- ja resurssienhallinta on olennaisen tärkeää, jotta voidaan varmistaa, että API-aloitteet ovat hyvin rahoitettuja ja resursoituja. Tämä asema tarjoaa ohjeita budjetin ja resurssien hallinnan optimoimiseksi ja sen varmistamiseksi, että API-aloitteet ovat linjassa liiketoimintatavoitteiden kanssa ja tuottavat maksimaalista arvoa.",
- "station.budget-and-resource-management.apply_in_work": "Tarjotaan API-aloitteille budjettihallintakehykset, priorisointikriteerit ja seurantatyökalut. Varmistaa, että tiimit hallinnoivat tehokkaasti budjetteja ja resursseja ja optimoivat API-kehitykseen ja -hallintaan tehdyt investoinnit mahdollisimman suuren arvon tuottamiseksi.",
- "station.budget-and-resource-management.outcomes": "API-aloitteita varten laaditut budjetti- ja resurssienhallintakäytännöt",
- "station.budget-and-resource-management.how_it_works": "Määrittele budjetti- ja resurssienhallintakäytännöt, joissa hahmotellaan API-aloitteiden budjettien ja resurssien hallinnointiprosessit.",
- "station.api-product-strategy.outcomes.1": "Yhteinen kieli tuotteen, suunnittelun ja tekniikan välillä",
- "station.api-product-strategy.outcomes.2": "vankka esitys tai peruste rahoituksen/hyväksynnän saamiseksi.",
- "station.api-product-strategy.how_it_works.1": "Määrittele keskeiset entiteetit, niiden ominaisuudet ja suhteet, jotta voidaan luoda yhteinen käsitteellinen ymmärrys eri matkojen ja lopulta APIen välille.",
- "station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tallentaaksesi tuetut liiketoimintatehtävät sekä API-käyttäjien ongelmat, hyödyt ja ominaisuudet, jotka muovaavat uusia tai uudelleenkäytettäviä API-rajapintoja.",
- "station.api-product-strategy.how_it_works.3": "Määrittele arvo - käyttäjille ja liiketoiminnalle - API-liiketoimintamallin avulla, jotta API-strategiastasi tulee visuaalinen, jaettavissa oleva ja helposti validoitava API-asiakkaiden kanssa seuraavalla asemalla.",
- "station.api-consumer-experience.outcomes.1": "Määrittele API-kokemuksen matka",
- "station.api-consumer-experience.outcomes.2": "Suunnittele sisäänajo, dokumentointi ja palaute",
- "station.api-consumer-experience.outcomes.3": "Paranna hyväksyntää aidon empatian ja kehittäjäkokemuksen (DX) avulla.",
- "station.api-platform-architecture.outcomes.1": "Johdonmukaisen hallinnon toteuttaminen ilman raskasta ylhäältä alaspäin suuntautuvaa valvontaa",
- "station.api-platform-architecture.outcomes.2": "Suunnittelu sisäistä uudelleenkäyttöä ja ulkoista skaalautuvuutta varten",
- "station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja kuluttajien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
- "station.api-platform-architecture.how_it_works.2": "Capacity Canvas -ohjelmassa sovitetaan yhteen liiketoimintatapahtumien mallit, tulevat kulutustrendit ja tekniset ratkaisut, jotta voidaan varmistaa APIn skaalautuvuus ja suorituskyky. Se tarjoaa kriittisen panoksen skaalautumispäätöksiä ja infrastruktuurin suunnittelua varten.",
- "station.api-platform-architecture.how_it_works.3": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
- "station.api-design.outcomes.1": "Uudelleenkäytettävät ja validoidut API-sopimukset",
- "station.api-design.outcomes.2": "Toimialamallien ja vuorovaikutusmallien mukaiset mallit",
- "station.api-design.outcomes.3": "Suunnittelun jäljitettävyys liiketoiminnan arvoon",
- "station.api-design.how_it_works.1": "Määrittele Interaction Canvasin avulla, miten hyödyntäjät ovat vuorovaikutuksessa APIn kanssa, ja Varmistetaan, että se vastaa heidän tarpeitaan ja odotuksiaan.",
- "station.api-design.how_it_works.2": "Sovellat REST-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
- "station.api-design.how_it_works.3": "Sovellat tapahtumapohjaisia suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
- "station.api-design.how_it_works.4": "Sovellat GraphQL-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
- "station.api-design.how_it_works.5": "Käytä suunnitteluperiaatteita ja API-tyyliohjetta, jotta suunnittelupäätöksesi ovat linjassa yhteisten sääntöjen kanssa ja mahdollistavat johdonmukaisen auditoinnin ja validoinnin.",
- "station.api-design.how_it_works.6": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API-suunnittelu täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
- "station.api-design.how_it_works.7": "Käytä API-tarkastuslistaa varmistaaksesi, että API-suunnittelu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien turvallisuus, suorituskyky ja vaatimustenmukaisuus.",
- "station.api-delivery.outcomes.1": "Luotettavat ja automatisoidut CI/CD-putket",
- "station.api-delivery.outcomes.2": "Toiminnallinen ja ei-toiminnallinen testaus integroitu",
- "station.api-delivery.outcomes.3": "Turvalliset ja vaatimustenmukaiset kehitysputket",
- "station.api-delivery.how_it_works.1": "Rakenna API-toteutus validoidun sopimuksen pohjalta käyttäen vakiintuneita kehysrakenteita, kirjastoja ja tiimin standardeja.",
- "station.api-delivery.how_it_works.2": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
- "station.api-delivery.how_it_works.3": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
- "station.api-delivery.how_it_works.4": "Varmistetaan, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
- "station.api-delivery.how_it_works.5": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
- "station.api-audit.outcomes.1": "Selkeä dokumentaatio API-suunnittelusta ja toteutuspäätöksistä",
- "station.api-audit.outcomes.2": "Turvallisuus, suorituskyky ja vaatimustenmukaisuus validoitu",
- "station.api-audit.outcomes.3": "Tuotannossa ilmenevien ongelmien riskin pienentäminen",
- "station.api-audit.how_it_works.1": "Käytä tarkistuslistoja, automatisoituja tarkistustyökaluja eli linttereitä ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
- "station.api-audit.how_it_works.2": "Tee yhteistyötä hallintotiimien ja toimialan asiantuntijoiden kanssa varmistaaksesi, että rajapinnat ovat valmiita tuotantoon.",
- "station.api-publishing.outcomes.1": "Selkeät API-käyttöönotto- ja rekisteröintiprosessit",
- "station.api-publishing.outcomes.2": "Dokumentaatio, turvallisuusmallit ja -käytännöt saatavilla",
- "station.api-publishing.outcomes.3": "APIt valmiina skaalautumiseen ja hallintaan",
- "station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaa, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
- "station.api-publishing.how_it_works.2": "Varmistetaan, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja kuluttajien saatavilla.",
- "station.monitoring-and-improving.outcomes.1": "Kehittäjien palautekierrokset käytössä",
- "station.monitoring-and-improving.outcomes.2": "Jatkuvasti tunnistetut ja käsitellyt ongelmat",
- "station.monitoring-and-improving.outcomes.3": "APIn iterointi käyttäjien tarpeiden mukaisesti",
- "station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
- "station.monitoring-and-improving.how_it_works.2": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia.",
- "station.user-experience.outcomes.1": "Intuitiiviset ja johdonmukaiset käyttöliittymät",
- "station.user-experience.outcomes.2": "Käyttäjien palaute sisällytetty APIn suunnitteluun",
- "station.user-experience.outcomes.3": "Parempi käyttäjätyytyväisyys ja hyväksyntä",
- "station.user-experience.how_it_works.1": "Suorita käyttäjätutkimus kerätäksesi tietoa siitä, miten hyödyntäjät ovat vuorovaikutuksessa ekosysteemipalveluiden tai API-sovelluksia käyttävien sovellusten kanssa.",
- "station.user-experience.how_it_works.2": "Dokumentoi käyttäjäkokemusta koskevat vaatimukset, jotta niitä voidaan käyttää API-suunnittelussa ja varmistaa, että ne ovat intuitiivisia ja helppokäyttöisiä.",
- "station.market-insights.outcomes.1": "Määritetyt alan standardit ja parhaat käytännöt",
- "station.market-insights.outcomes.2": "API-strategia linjassa markkinoiden tarpeiden kanssa",
- "station.market-insights.outcomes.3": "Markkinatietoon perustuva tietoon perustuva päätöksenteko",
- "station.market-insights.how_it_works.1": "Analysoi kilpailijoiden rajapinnat ymmärtämään niiden vahvuudet, heikkoudet ja ainutlaatuiset myyntivaltit.",
- "station.market-insights.how_it_works.2": "Tunnistetaan alan standardit ja parhaat käytännöt, jotta voidaan varmistaa, että rajapinnat ovat kilpailukykyisiä ja yhteensopivia.",
- "station.business-goals.outcomes.1": "Kullekin Rajapinnalle määritelty selkeä liiketoiminta-arvo",
- "station.business-goals.outcomes.2": "Sidosryhmien sitoutuminen ja tuki API-aloitteille",
- "station.business-goals.outcomes.3": "APIt edistävät organisaation menestystä",
- "station.business-goals.how_it_works.1": "Määritä keskeiset suorituskykyindikaattorit (KPI), joilla mitataan APIn onnistumista suhteessa liiketoiminnan tavoitteisiin.",
- "station.business-goals.how_it_works.2": "Sidosryhmien sitouttaminen varmistamaan API-aloitteiden yhdenmukaisuus ja tuki.",
- "station.competitive-analysis.outcomes.1": "Eriyttämismahdollisuudet tunnistettu",
- "station.competitive-analysis.outcomes.2": "API-strategia, joka perustuu kilpailutietoon",
- "station.competitive-analysis.outcomes.3": "Lisääntynyt kilpailukyky API-markkinoilla",
- "station.competitive-analysis.how_it_works.1": "Tunnista markkinapuutteet, jotka rajapintasi voivat täyttää kilpailijoiden tarjonnan perusteella.",
- "station.competitive-analysis.how_it_works.2": "Kehitä erottautumisstrategia, jossa korostetaan rajapintojesi ainutlaatuisia ominaisuuksia ja etuja.",
- "station.ecosystem-vision.outcomes.1": "APIt, jotka on suunniteltu mahdollistamaan yhteistyö ja integrointi",
- "station.ecosystem-vision.outcomes.2": "Ekosysteemikumppanit tunnistetaan ja otetaan mukaan",
- "station.ecosystem-vision.outcomes.3": "APIt edistävät elinvoimaista ekosysteemiä",
- "station.ecosystem-vision.how_it_works.1": "Tunnistetaan tärkeimmät ekosysteemikumppanit ja sidosryhmät, jotka hyötyvät ekosysteemistä tai osallistuvat siihen.",
- "station.ecosystem-vision.how_it_works.2": "Suunnittele rajapinnat, jotka mahdollistavat saumattoman integroinnin ja yhteistyön ekosysteemissä.",
- "station.scalable-infrastructure.outcomes.1": "Korkea käytettävyys ja suorituskyky kuormitettuna",
- "station.scalable-infrastructure.outcomes.2": "Tulevaa kasvua varten suunniteltu infrastruktuuri",
- "station.scalable-infrastructure.outcomes.3": "Vähentää käyttökatkoksia ja parantaa käyttäjäkokemusta",
- "station.scalable-infrastructure.how_it_works.1": "Toteuta kuorman tasapainottaminen, välimuistitallennus ja muut tekniikat korkean käytettävyyden ja suorituskyvyn varmistamiseksi. Kerää infrastruktuurivaatimukset API-tiimeiltä Capacity Canvasin avulla.",
- "station.scalable-infrastructure.how_it_works.2": "Seuraa infrastruktuurin suorituskykyä ja kapasiteettia sen varmistamiseksi, että se pystyy vastaamaan kasvavaan kysyntään.",
- "station.legal-and-compliance.outcomes.1": "Tietosuojaa ja yksityisyyden suojaa koskevat vaatimukset täyttyvät",
- "station.legal-and-compliance.outcomes.2": "Oikeudellisten riskien tunnistaminen ja lieventäminen",
- "station.legal-and-compliance.outcomes.3": "Vaatimustenmukaisuustoimenpiteiden selkeä dokumentointi",
- "station.legal-and-compliance.how_it_works.1": "Toteuta toimenpiteitä, joilla varmistetaan, että rajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
- "station.legal-and-compliance.how_it_works.2": "dokumentoida vaatimustenmukaisuustoimenpiteet ja varmistaa, että niistä tiedotetaan sidosryhmille ja kuluttajille.",
- "station.security-and-privacy.outcomes.1": "Käyttäjätiedot suojattu yksityisyydensuojatoimenpiteiden avulla",
- "station.security-and-privacy.outcomes.2": "Parhaat turvallisuuskäytännöt API-suunnittelussa ja -kehityksessä",
- "station.security-and-privacy.outcomes.3": "Turvallisuusstandardien ja -säännösten noudattaminen",
- "station.security-and-privacy.how_it_works.1": "Varmistetaan käyttäjien tietojen yksityisyys toteuttamalla tietosuojatoimenpiteitä, kuten anonymisointi ja käyttöoikeuksien valvonta.",
- "station.security-and-privacy.how_it_works.2": "Suorittaa säännöllisiä tietoturvatarkastuksia ja haavoittuvuusarviointeja riskien tunnistamiseksi ja vähentämiseksi.",
- "station.design-standards.outcomes.1": "Laadukkaat APIt, jotka vastaavat käyttäjien tarpeita",
- "station.design-standards.outcomes.2": "Uudelleenkäytettävät suunnittelumallit ja komponentit",
- "station.design-standards.outcomes.3": "Vähennetään suunnittelun epäjohdonmukaisuuksia ja teknistä velkaa.",
- "station.design-standards.how_it_works.1": "Luo uudelleenkäytettäviä suunnittelumalleja ja -komponentteja, joita tiimit voivat hyödyntää yhdenmukaisuuden ja laadun varmistamiseksi.",
- "station.design-standards.how_it_works.2": "Suoritat suunnittelun tarkastuksia ja auditointeja varmistaaksesi suunnittelustandardien noudattamisen ja yksilöidäksesi parannuskohteet.",
- "station.vendor-management.outcomes.1": "Kolmannen osapuolen APIt integroituvat luotettavasti ja turvallisesti.",
- "station.vendor-management.outcomes.2": "Myyjä noudattaa organisaation standardeja",
- "station.vendor-management.outcomes.3": "Kolmannen osapuolen riippuvuuksiin liittyvien riskien vähentäminen",
- "station.vendor-management.how_it_works.1": "Määrittele kriteerit toimittajien rajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
- "station.vendor-management.how_it_works.2": "Seuraa toimittajien suorituskykyä ja palvelutasosopimusten (SLA) ja organisaation standardien noudattamista.",
- "station.contract-design.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja vastuut hahmoteltuina",
- "station.contract-design.outcomes.2": "Käyttöohjeet ja parhaat käytännöt dokumentoitu",
- "station.contract-design.outcomes.3": "APIn käyttöä koskevien väärinkäsitysten ja riitojen väheneminen.",
- "station.contract-design.how_it_works.1": "Käytä standardoituja formaatteja (esim. OpenAPI, AsyncAPI) luodaksesi koneellisesti luettavia API-sopimuksia, joita on helppo jakaa ja validoida.",
- "station.contract-design.how_it_works.2": "Varmistetaan, että sidosryhmät tarkistavat ja hyväksyvät API-sopimukset, jotta varmistetaan niiden yhdenmukaisuus ja selkeys.",
- "station.development.outcomes.1": "Laadukkaat, ylläpidettävät ja skaalautuvat rajapinnat.",
- "station.development.outcomes.2": "Johdonmukaiset koodausstandardit ja -käytännöt",
- "station.development.outcomes.3": "Vähentää kehitysaikaa ja teknistä velkaa",
- "station.development.how_it_works.1": "Sovellat sopimuslähtöisiä tai suunnittelulähtöisiä lähestymistapoja varmistaaksesi, että API-sopimukset validoidaan ennen toteutusta.",
- "station.development.how_it_works.2": "Noudata koodausstandardeja ja parhaita käytäntöjä varmistaaksesi johdonmukaisen ja laadukkaan API-kehityksen.",
- "station.ci-cd.outcomes.1": "API-kehityksen tasainen laatu ja jäljitettävyys",
- "station.ci-cd.outcomes.2": "Nopeammat iteraatiot ja lyhyempi aika markkinoille saattamiseen",
- "station.ci-cd.outcomes.3": "Parempi yhteistyö ja palautekierrokset API-kehityksessä",
- "station.ci-cd.how_it_works.1": "Integroi toiminnallinen ja ei-toiminnallinen testaus CI/CD-putkeen varmistaaksesi, että rajapinnat täyttävät laatuvaatimukset.",
- "station.ci-cd.how_it_works.2": "Toteuta automaattiset tietoturvatarkastukset ja vaatimustenmukaisuuden validoinnit CI/CD-putkessa varmistaaksesi, että rajapinnat ovat turvallisia ja vaatimustenmukaisia.",
- "station.test-automation.outcomes.1": "Automaattiset toiminnalliset, turvallisuus- ja suorituskykytestit",
- "station.test-automation.outcomes.2": "Vähentää manuaalisen testauksen työmäärää ja lisää testien kattavuutta",
- "station.test-automation.outcomes.3": "APIn luotettavuuden ja laadun parantaminen",
- "station.test-automation.how_it_works.1": "Toteuta testiautomaatiokehykset, jotka tukevat sopimustestausta, integrointitestausta ja päästä päähän -testausta.",
- "station.test-automation.how_it_works.2": "Integroi automatisoidut testit CI/CD-putkeen API-laadun jatkuvan validoinnin varmistamiseksi.",
- "station.release-management.outcomes.1": "Versiointi- ja käyttöönottostrategioiden määrittely",
- "station.release-management.outcomes.2": "API-julkaisuja varten vahvistetut palautusmenettelyt",
- "station.release-management.outcomes.3": "API-muutoksiin liittyvien riskien vähentäminen",
- "station.release-management.how_it_works.1": "Ota käyttöön käyttöönottostrategioita (esim. sinivihreät käyttöönotot, canary releaset) API-julkaisuihin liittyvien riskien minimoimiseksi.",
- "station.release-management.how_it_works.2": "Ota käyttöön palautusmenettelyt, jotta muutokset voidaan palauttaa nopeasti, jos API-julkaisujen aikana ilmenee ongelmia.",
- "station.service-agreements.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja palvelutasot hahmoteltuina",
- "station.service-agreements.outcomes.2": "Dokumentoidut vastuualueet ja tukiprosessit",
- "station.service-agreements.outcomes.3": "Parempi viestintä ja yhteistyö API-tiimien välillä",
- "station.service-agreements.how_it_works.1": "Luo koneellisesti luettavia palvelusopimuksia, joita on helppo jakaa ja validoida, käyttämällä standardoituja muotoja.",
- "station.service-agreements.how_it_works.2": "Varmistetaan, että sidosryhmät tarkistavat ja hyväksyvät palvelusopimukset, jotta varmistetaan niiden yhdenmukaisuus ja selkeys.",
- "station.api-consumer-adoption.outcomes.1": "APIn käytön ja sitoutumisen lisääminen",
- "station.api-consumer-adoption.outcomes.2": "APIn hyödyntäjät saavat tietoa APIn ominaisuuksista ja hyödyistä",
- "station.api-consumer-adoption.outcomes.3": "Parempi API-hyödyntäjätyytyväisyys ja -uskollisuus",
- "station.api-consumer-adoption.how_it_works.1": "Luo opetusmateriaalia (esim. opetusohjelmia, dokumentaatiota), jossa selitetään APIn ominaisuuksia, hyötyjä ja käyttötapoja.",
- "station.api-consumer-adoption.how_it_works.2": "Kytkeydy API-käyttäjiin palautekierrosten, tukikanavien ja yhteisöfoorumien kautta ymmärtämään heidän tarpeitaan ja parantamaan APIn käyttöönottoa.",
- "station.api-promotion.outcomes.1": "APIn näkyvyyden ja tietoisuuden lisääminen",
- "station.api-promotion.outcomes.2": "Korkeampi APIn käyttö- ja hyväksymisaste",
- "station.api-promotion.outcomes.3": "Parempi API-kuluttajien sitoutuminen ja tyytyväisyys",
- "station.api-promotion.how_it_works.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan rajapintojen arvoa ja hyötyjä.",
- "station.api-promotion.how_it_works.2": "Osallistu API-yhteisöihin ja -foorumeihin API-päivitysten jakamiseksi, palautteen keräämiseksi ja APIn käytön edistämiseksi.",
- "station.partner-integration.outcomes.1": "Parannetut API-ominaisuudet kumppani-APIen avulla",
- "station.partner-integration.outcomes.2": "Kumppanuuksien avulla laajennettu ulottuvuus ja markkinamahdollisuudet",
- "station.partner-integration.outcomes.3": "Parempi yhteistyö ja innovointi kumppaneiden kanssa",
- "station.partner-integration.how_it_works.1": "Luodaan integraatioprosessit ja -ohjeet yhteistyökumppaneiden kanssa tehtävää yhteistyötä varten, mukaan lukien tekninen integraatio, tietojen jakaminen ja tuki.",
- "station.partner-integration.how_it_works.2": "Seuraa kumppaneiden API-suorituskykyä ja vaatimustenmukaisuutta varmistaaksesi luotettavuuden ja yhteensopivuuden API-strategiasi kanssa.",
- "station.api-mindset.outcomes.1": "Innovaation ja yhteistyön lisääminen rajapintojen avulla",
- "station.api-mindset.outcomes.2": "API-tiimit, joilla on valtuudet johtaa API-strategiaa ja -aloitteita.",
- "station.api-mindset.outcomes.3": "Liiketoiminnan tavoitteiden ja API-kehityksen parempi yhteensovittaminen.",
- "station.api-mindset.how_it_works.1": "Kannustaa API-tiimien, liiketoimintayksiköiden ja sidosryhmien välistä monialaista yhteistyötä, jotta API-aloitteet voidaan sovittaa yhteen liiketoiminnan tavoitteiden kanssa.",
- "station.api-mindset.how_it_works.2": "Tarjotaan koulutusta ja resursseja, jotta tiimit voivat omaksua API-first -ajattelutavan ja ymmärtää APIen edut.",
- "station.roles-and-responsibilities.outcomes.1": "Tehokas yhteistyö ja vastuuvelvollisuus API-tiimeissä",
- "station.roles-and-responsibilities.outcomes.2": "Parempi viestintä ja yhdenmukaistaminen tiimin jäsenten välillä",
- "station.roles-and-responsibilities.outcomes.3": "Sekaannusten ja päällekkäisyyksien vähentäminen vastuualueilla",
- "station.roles-and-responsibilities.how_it_works.1": "Määritä selkeät vastuualueet kullekin roolille, mukaan lukien API-suunnittelu, kehittäminen, testaus ja toiminta.",
- "station.roles-and-responsibilities.how_it_works.2": "Varmistaa, että roolit ja vastuualueet ilmoitetaan kaikille tiimin jäsenille ja sidosryhmille, jotta varmistetaan niiden yhdenmukaisuus.",
- "station.upskilling.outcomes.1": "API-suunnittelun, -kehityksen ja -hallinnan lisääntynyt osaaminen.",
- "station.upskilling.outcomes.2": "Parempi kyky omaksua uutta teknologiaa ja uusia käytäntöjä",
- "station.upskilling.outcomes.3": "Valtuutetaan tiimit edistämään API-innovaatioita ja laatua.",
- "station.upskilling.how_it_works.1": "Tarjotaan koulutusohjelmia, työpajoja ja resursseja, joiden avulla tiimit voivat parantaa API-taitojaan ja -tietämystään.",
- "station.upskilling.how_it_works.2": "Kannustetaan jatkuvaan oppimiseen verkkokurssien, sertifikaattien ja yhteisöllisen sitoutumisen avulla.",
- "station.operating-guidelines.outcomes.1": "Yhdenmukainen API-hallinta ja laatu koko organisaatiossa",
- "station.operating-guidelines.outcomes.2": "organisaation standardien ja parhaiden käytäntöjen noudattaminen",
- "station.operating-guidelines.outcomes.3": "Parempi näkyvyys ja API-aloitteiden hallinta",
- "station.operating-guidelines.how_it_works.1": "Ota käyttöön hallintokäytännöt, joilla varmistetaan, että rajapintoja hallinnoidaan johdonmukaisesti, mukaan lukien tarkistukset, auditoinnit ja vaatimustenmukaisuuden tarkastukset.",
- "station.operating-guidelines.how_it_works.2": "Seuraa API-aloitteita varmistaaksesi toimintaohjeiden ja hallintokäytäntöjen noudattamisen.",
- "station.portfolio-management.outcomes.1": "APIt linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa.",
- "station.portfolio-management.outcomes.2": "APIen priorisointi ja optimointi arvon ja vaikutusten perusteella.",
- "station.portfolio-management.outcomes.3": "Parempi näkyvyys ja API-portfolion hallinta",
- "station.portfolio-management.how_it_works.1": "Laaditaan kriteerit rajapintojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden kanssa yhteensopivuuden perusteella.",
- "station.portfolio-management.how_it_works.2": "Seuraa API-portfoliota varmistaaksesi, että APIt tuottavat arvoa, täyttävät suorituskykyodotukset ja ovat linjassa liiketoiminnan tavoitteiden kanssa.",
- "station.budget-and-resource-management.outcomes.1": "Resurssien tehokas kohdentaminen API-aloitteisiin",
- "station.budget-and-resource-management.outcomes.2": "Optimoidut investoinnit API-kehitykseen ja -hallintaan",
- "station.budget-and-resource-management.outcomes.3": "Parempi taloudellinen näkyvyys ja API-aloitteiden valvonta.",
- "station.budget-and-resource-management.how_it_works.1": "Laaditaan kriteerit budjettimäärärahojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden mukaisuuden perusteella.",
- "station.budget-and-resource-management.how_it_works.2": "Seuraa budjettia ja resurssien käyttöä varmistaaksesi tehokkaat investoinnit ja resurssien jakamisen API-aloitteisiin."
+  "group.core-stations.title": "APIn elinkaaren ydinasemat",
+  "group.core-stations.description": "API Metron ydinasemat, joissa tiimit voivat oppia rakentamaan ja hallinnoimaan rajapintoja tehokkaasti.",
+  "group.sub-stations.title": "APIn elinkaaren lähiöasemat",
+  "group.sub-stations.description": "Lähiöasemat, jotka tarjoavat lisäresursseja, työkaluja ja parhaita käytäntöjä API-tiimeille.",
+  "station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
+  "station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, käyttäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
+  "station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, ei tuotteina. Tulos? Hämmentyneitä kuluttajia, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
+  "station.api-product-strategy.apply_in_work": "Tarjotaan ohjeita ja malleja API-liiketoimintamallien, arvolupausten ja etenemissuunnitelmien luomista varten.",
+  "station.api-product-strategy.outcomes": "Suoraviivainen API-arvolupaus ja yleisö",
+  "station.api-product-strategy.how_it_works": "Tutki asiakkaan tai yhteistyökumppanin ongelmaa, jonka oletat voivasi ratkaista APIen avulla. Kartoita sidosryhmät, niiden matkat ja tulokset Customer Journey canvasin avulla.",
+  "station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia käyttäjiä varten.",
+  "station.api-consumer-experience.description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen.",
+  "station.api-consumer-experience.why_it_matters": "Hyvät aPIt eivät ainoastaan toimi - ne tuntuvat intuitiivisilta. Riippumatta siitä, onko hyödyntäjä sisäinen kehittäjä, ulkoinen kumppani vai tekoälyagentti, heidän kokemuksensa ratkaisee hyväksynnän. Ilman selkeää kokemussuunnitelmaa",
+  "station.api-consumer-experience.how_it_works": "Tarkastele olemassa olevaa API Value Proposition Canvasta API-hyödyntäjän näkökulmasta. Säilytä tuetut liiketoimintatehtävät vakaina ja rikasta tuskaa lievittäviä ja hyötyjä mahdollistavia ominaisuuksia API-hyödyntäjien näkökulmalla, jotta ne voivat ohjata myöhempiä suunnittelupäätöksiä.",
+  "station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-käyttäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
+  "station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-käyttäjälle.",
+  "station.api-consumer-experience.apply_in_work": "Tarjotaan ohjeita, työkaluja ja palautemekanismeja sisäisten ja ulkoisten kehittäjien ja kumppaneiden kokemusten ymmärtämiseksi, analysoimiseksi ja parantamiseksi.",
+  "station.api-consumer-experience.outcomes": "Tunnista ja priorisoi API-asiakkaat",
+  "station.api-platform-architecture.title": "API-alustan arkkitehtuuri",
+  "station.api-platform-architecture.description": "Varmistetaan skaalautuvuus, uudelleenkäyttö ja hallinta API- ja alustakomponenttien välillä.",
+  "station.api-platform-architecture.why_it_matters": "Kun rajapinnat skaalautuvat eri tiimeille, alustan on mahdollistettava hallinta ja uudelleenkäyttö nopeutta estämättä. Tällä asemalla kerrotaan, miten API-arkkitehtuurit voidaan suunnitella pitkäikäisiksi, turvallisiksi ja tehokkaiksi.",
+  "station.api-platform-architecture.apply_in_work": "Perustetaan skaalautuva, turvallinen ja vaatimustenmukainen infrastruktuuri API-toimintoja varten. Annetaan ohjeita arkkitehtuurin parhaista käytännöistä.",
+  "station.api-platform-architecture.outcomes": "Vähennä turhia API-rajapintoja ja vähennä pilvialustakustannuksia.",
+  "station.api-platform-architecture.how_it_works": "Business Impact Canvas auttaa tunnistamaan ja lieventämään APIn saatavuuteen, tietoturvaan ja toiminnallisuuteen liittyviä riskejä ja tukemaan tietoon perustuvia arkkitehtuuripäätöksiä.",
+  "station.api-design.title": "API-design - Suunnittele arvoa tuottavia rajapintoja",
+  "station.api-design.description": "Luo API-suunnitelmia, jotka ovat johdonmukaisia, uudelleenkäytettäviä ja perustuvat liiketoiminnallisiin tavoitteisiin sekä yhteisiin standardeihin.",
+  "station.api-design.why_it_matters": "APIen suunnittelu ei tarkoita pelkästään päätepisteiden (endpoints) nimeämistä. Hyvä suunnittelu varmistaa, että APIt ovat käyttökelpoisia, johdonmukaisia ja linjassa liiketoiminnallisten ja teknisten tavoitteiden kanssa. Huono suunnittelu johtaa tiukkoihin riippuvuuksiin, heikkoon uudelleenkäytettävyyteen ja kalliiseen uudelleen toteutukseen eri tiimien välillä.",
+  "station.api-design.apply_in_work": "Tarjoa uudelleenkäytettäviä suunnittelumalleja, yhteisiä standardeja ja validointityökaluja API-määrityksille. Varmista, että suunnittelupäätökset ovat johdonmukaisia, tarkistettuja varhaisessa vaiheessa ja linjassa liiketoiminnallisten tavoitteiden kanssa.",
+  "station.api-design.outcomes": "Hyvin dokumentoidut ja johdonmukaiset API-mallit",
+  "station.api-design.how_it_works": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri rajapinnoille.",
+  "station.api-delivery.title": "API-kehitys - Kehitä turvalliset ja luotettavat rajapinnat",
+  "station.api-delivery.description": "Rakenna, testaa ja julkaise rajapintoja käyttämällä nykyaikaisia jakeluputkia ja parhaita teknisiä käytäntöjä.",
+  "station.api-delivery.why_it_matters": "Parhaatkin API-suunnitelmat epäonnistuvat, jos kehitys on epäjohdonmukaista. Tällä asemalla varmistetaan, että rajapinnat rakennetaan laadukkaasti, testataan perusteellisesti ja otetaan käyttöön luotettavasti, mikä mahdollistaa nopeammat iteraatiot ja suuremman luottamuksen.",
+  "station.api-delivery.apply_in_work": "Toimittaa koodauskehyksiä, kirjastoja ja standardeja API-toteutusta varten. CI/CD-putkien, laadunvarmistuskehysten ja käyttöönottoautomaatiotyökalujen toteuttaminen.",
+  "station.api-delivery.outcomes": "Rajapinnat, jotka on toteutettu testattujen kehysten ja mallien avulla.",
+  "station.api-delivery.how_it_works": "Käytä API-kehityksen parhaita käytäntöjä ohjeena validoidun sopimuksen toteuttamiseen vakiintuneilla kehysrakenteilla ja kirjastoilla varmistaen, että tulos on uudelleenkäytettävä ja ylläpidettävä.",
+  "station.api-audit.title": "API-auditointi - API-rajapintojen tarkastus vaatimustenmukaisuuden ja laadun varmistamiseksi",
+  "station.api-audit.description": "Varmista, että APIt täyttävät liiketoiminta-, suunnittelu- ja toimintastandardit ennen julkaisua ja käyttöönottoa.",
+  "station.api-audit.why_it_matters": "APIt ovat pitkäikäisiä tuotteita, ja niiden on täytettävä laatu-, johdonmukaisuus- ja vaatimustenmukaisuusodotukset. Auditointi yhdistää suunnittelupäätökset, toteutuksen ja toimintavalmiuden määriteltyihin standardeihin, mikä vähentää riskejä ennen käyttöönottoa.",
+  "station.api-audit.apply_in_work": "Luo johdonmukainen auditointiprosessi, joka arvioi APIn valmiutta elinkaaren eri vaiheissa määriteltyjen kriteerien, todisteiden ja standardien avulla. Varmista, että puutteet tunnistetaan varhaisessa vaiheessa ja korjataan ennen julkaisua.",
+  "station.api-audit.outcomes": "APIt täyttävät sisäiset ja ulkoiset standardit",
+  "station.api-audit.how_it_works": "Suorita tarkastuksia varmistaaksesi, että rajapinnat täyttävät organisatoriset, tekniset ja oikeudelliset standardit ennen julkaisemista.",
+  "station.api-publishing.title": "API-julkaiseminen - Julkaise APIt luotettavasti",
+  "station.api-publishing.description": "Esittele APIt turvallisesti ja selkeästi oikealle yleisölle oikean dokumentaation ja prosessien avulla.",
+  "station.api-publishing.why_it_matters": "Julkaiseminen on muutakin kuin käyttöönottoa - kyse on löydettävyydestä, saatavuudesta ja tuesta. Jos rajapintoja ei julkaista oikein, niitä ei käytetä, käytetä uudelleen tai suojata tehokkaasti.",
+  "station.api-publishing.apply_in_work": "Mahdollistetaan APIen julkaiseminen asiaankuuluvassa ympäristössä ja selkeät rekisteröinti- ja käyttöoikeusmekanismit (esim. API-avaimet, OAuth, tilaussuunnitelmat) API-hyödyntäjäsegmenttien sekä turvallisuus- ja vaatimustenmukaisuusvaatimusten mukaan.",
+  "station.api-publishing.outcomes": "APIt julkaistaan oikeassa ympäristössä (yksityinen, kumppani, julkinen).",
+  "station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille rajapinnan käyttäjille.",
+  "station.monitoring-and-improving.title": "Seuranta ja parantaminen - API-arvoa varten",
+  "station.monitoring-and-improving.description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen.",
+  "station.monitoring-and-improving.why_it_matters": "API-kehitys ei lopu käynnistykseen. Ilman seurantaa tiimit eivät voi parantaa käyttöönottoa, suorituskykyä tai ROI",
+  "station.monitoring-and-improving.apply_in_work": "Ota käyttöön analytiikkakehykset suorituskyvyn ja sitoutumisen seuraamiseksi. Kehitetään palautesilmukoita, analytiikkatyökaluja ja sitouttamisstrategioita API-rajapintoja varten.",
+  "station.monitoring-and-improving.outcomes": "Suorituskyvyn ja käytön mittarit määritellään ja niitä seurataan.",
+  "station.monitoring-and-improving.how_it_works": "Seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
+  "station.user-experience.title": "Käyttäjäkokemus - Suunnittele APIt käyttäjälähtöisesti",
+  "station.user-experience.description": "Varmistetaan, että rajapinnat on suunniteltu loppukäyttäjää ajatellen ja että ne tarjoavat saumattoman ja intuitiivisen käyttökokemuksen.",
+  "station.user-experience.why_it_matters": "APIt eivät ole vain teknisiä tuotteita, vaan ne ovat käyttäjäkohtaisia tuotteita. Huono käyttökokemus voi johtaa vähäiseen käyttöön ja turhautumiseen. Tämä asema auttaa tiimejä suunnittelemaan APIt, jotka ovat käyttäjäystävällisiä ja vastaavat kuluttajien tarpeita.",
+  "station.user-experience.apply_in_work": "Tarjotaan käyttäjäkokemusta koskevia ohjeita, malleja ja työkaluja API-suunnittelua varten. Varmistetaan, että tiimit noudattavat käyttäjäkeskeisiä suunnittelukäytäntöjä ja sisällyttävät käyttäjäpalautteen API-iteraatioihin.",
+  "station.user-experience.outcomes": "APIt on suunniteltu käyttäjien tarpeet mielessä pitäen",
+  "station.user-experience.how_it_works": "Käyttäjäpersoonien käyttö loppukäyttäjien tarpeiden ja odotusten ymmärtämiseksi.",
+  "station.market-insights.title": "Markkinatietoa - API-maiseman ymmärtäminen",
+  "station.market-insights.description": "Analysoi markkinasuuntauksia, kilpailijoiden rajapintoja ja alan standardeja rajapintastrategian laatimiseksi.",
+  "station.market-insights.why_it_matters": "Markkinatilanteen ymmärtäminen auttaa tiimejä tunnistamaan mahdollisuuksia, välttämään sudenkuoppia ja mukauttamaan rajapintansa alan standardeihin. Tämä asema tarjoaa työkaluja markkinasuuntausten ja kilpailijoiden tarjonnan analysointiin.",
+  "station.market-insights.apply_in_work": "Tarjotaan markkinatutkimustyökaluja, kilpailija-analyysimalleja ja alan standardeja koskevia resursseja. Varmistetaan, että tiimit pysyvät ajan tasalla markkinasuuntauksista ja sisällyttävät näkemykset API-strategiaan.",
+  "station.market-insights.outcomes": "Markkinatrendit ja kilpailijoiden APIt analysoitu",
+  "station.market-insights.how_it_works": "Markkinatutkimuksen tekeminen API-toimialalla vallitsevien suuntausten, mahdollisuuksien ja uhkien tunnistamiseksi.",
+  "station.business-goals.title": "Liiketoiminnalliset tavoitteet - Kohdista rajapinnat liiketoimintatavoitteisiin.",
+  "station.business-goals.description": "Varmistetaan, että rajapinnat ovat linjassa liiketoiminnan tavoitteiden kanssa ja edistävät organisaation yleisiä tavoitteita.",
+  "station.business-goals.why_it_matters": "Rajapintoja ei pidä rakentaa erillään, vaan niiden on tuettava ja edistettävä liiketoiminnan tavoitteita. Tämä asema auttaa tiimejä sovittamaan rajapinnat strategisiin tavoitteisiin ja varmistamaan, että ne tuottavat todellista liiketoiminta-arvoa.",
+  "station.business-goals.apply_in_work": "Tarjotaan liiketoimintasuuntautumiskehyksiä, malleja ja työkaluja API-liiketoiminta-arvon määrittelyyn. Varmistetaan, että tiimit tarkistavat ja sovittavat sovellusrajapinnat säännöllisesti yhteen muuttuvien liiketoimintatavoitteiden kanssa.",
+  "station.business-goals.outcomes": "APIt linjassa liiketoiminnan tavoitteiden kanssa",
+  "station.business-goals.how_it_works": "Määrittele liiketoimintatavoitteet ja se, miten rajapinnat voivat tukea niitä käyttämällä **liiketoimintamallia (Business Model Canvas**). Jos liiketoimintasi tarkoituksena on tarjota rajapintoja, käy läpi *API-tuotestrategia-asema* ja täytä **API-liiketoimintamalli Canvas**.",
+  "station.competitive-analysis.title": "Kilpailuanalyysi - pysy kärjessä API-markkinoilla",
+  "station.competitive-analysis.description": "Analysoi kilpailijoiden rajapinnat vahvuuksien, heikkouksien ja erottautumismahdollisuuksien tunnistamiseksi.",
+  "station.competitive-analysis.why_it_matters": "Kilpailutilanteen ymmärtäminen auttaa tiimejä tunnistamaan API-rajapintojensa puutteet, mahdollisuudet ja parannuskohteet. Tämä asema tarjoaa työkaluja kilpailijoiden analysointiin ja API-strategian laatimiseen.",
+  "station.competitive-analysis.apply_in_work": "Tarjotaan kilpailuanalyysityökaluja, malleja ja resursseja. Varmistetaan, että tiimit analysoivat säännöllisesti kilpailijoita ja sisällyttävät näkemykset API-strategiaan ja -suunnitteluun.",
+  "station.competitive-analysis.outcomes": "Kilpailijoiden rajapintojen vahvuudet ja heikkoudet analysoidaan.",
+  "station.competitive-analysis.how_it_works": "Suorita kilpailija-analyysi tärkeimpien kilpailijoiden, niiden API-tarjonnan sekä niiden vahvuuksien ja heikkouksien tunnistamiseksi.",
+  "station.ecosystem-vision.title": "Ekosysteemin visio - Rakenna rajapinnat kukoistavaa ekosysteemiä varten.",
+  "station.ecosystem-vision.description": "Luo visio siitä, miten rajapintasi sopivat laajempaan ekosysteemiin, joka mahdollistaa yhteistyön ja innovoinnin.",
+  "station.ecosystem-vision.why_it_matters": "APIt eivät ole itsenäisiä tuotteita, vaan osa laajempaa ekosysteemiä. Tämä asema auttaa tiimejä määrittelemään, miten niiden rajapinnat ovat vuorovaikutuksessa muiden järjestelmien, alustojen ja palvelujen kanssa, jotta voidaan luoda kukoistava ekosysteemi, joka edistää yhteistyötä ja innovointia.",
+  "station.ecosystem-vision.apply_in_work": "Tarjotaan ekosysteemin visiokehykset, kumppanien sitouttamisstrategiat ja integrointiohjeet. Varmistaa, että tiimit suunnittelevat rajapinnat ekosysteemiä silmällä pitäen ja edistävät kumppanien välistä yhteistyötä.",
+  "station.ecosystem-vision.outcomes": "Selkeä ekosysteemin visio rajapinnoille",
+  "station.ecosystem-vision.how_it_works": "Määrittele rajapintojesi ekosysteemivisio, mukaan lukien se, miten ne ovat vuorovaikutuksessa muiden järjestelmien ja alustojen kanssa.",
+  "station.scalable-infrastructure.title": "Skaalautuva infrastruktuuri - rakenna APIt vankalle perustalle",
+  "station.scalable-infrastructure.description": "Varmistetaan, että API-infrastruktuurisi voi skaalautua vastaamaan kasvavaa kysyntää ja tukea korkeaa käytettävyyttä.",
+  "station.scalable-infrastructure.why_it_matters": "APIt on rakennettava vankalle infrastruktuurille, joka kestää kasvavan liikenteen ja varmistaa korkean käytettävyyden. Tämä asema tarjoaa ohjeita APIn kasvua ja suorituskykyä tukevan skaalautuvan infrastruktuurin suunnitteluun ja toteuttamiseen.",
+  "station.scalable-infrastructure.apply_in_work": "Tarjotaan infrastruktuurin suunnitteluohjeita, pilvipohjaisia malleja ja valvontatyökaluja. Varmistetaan, että tiimit ottavat käyttöön skaalautuvan infrastruktuurin, joka pystyy mukautumaan muuttuviin vaatimuksiin ja tukemaan API-suorituskykyä.",
+  "station.scalable-infrastructure.outcomes": "Skaalautuva ja joustava API-infrastruktuuri",
+  "station.scalable-infrastructure.how_it_works": "Suunnittele API-infrastruktuuri skaalautuvaksi ja joustavaksi käyttäen pilvipohjaisia malleja ja teknologioita.",
+  "station.legal-and-compliance.title": "Lainsäädäntö ja vaatimustenmukaisuus - varmista, että APIt täyttävät sääntelystandardit.",
+  "station.legal-and-compliance.description": "Varmistetaan, että rajapinnat noudattavat lakisääteisiä ja lainsäädännöllisiä vaatimuksia ja suojaavat organisaatiota ja käyttäjiä.",
+  "station.legal-and-compliance.why_it_matters": "API-rajapintojen on noudatettava oikeudellisia ja sääntelystandardeja organisaation ja käyttäjien suojelemiseksi. Tämä asema tarjoaa työkaluja ja ohjeita, joilla varmistetaan, että rajapinnat täyttävät vaatimustenmukaisuusvaatimukset, vähennetään oikeudellisia riskejä ja varmistetaan tietosuoja.",
+  "station.legal-and-compliance.apply_in_work": "Tarjotaan oikeudellisia ja vaatimustenmukaisuutta koskevia puitteita, tarkistuslistoja ja työkaluja API-vaatimustenmukaisuuden varmistamiseksi. Varmistetaan, että tiimit ymmärtävät ja panevat täytäntöön oikeudelliset vaatimukset APIn suunnittelussa, kehittämisessä ja julkaisemisessa.",
+  "station.legal-and-compliance.outcomes": "Oikeudellisten ja sääntelystandardien mukaiset APIt",
+  "station.legal-and-compliance.how_it_works": "Tunnista rajapintoihin sovellettavat oikeudelliset ja sääntelyvaatimukset, kuten tietosuojaa, yksityisyyttä ja tietoturvaa koskevat vaatimukset.",
+  "station.security-and-privacy.title": "Tietoturva ja yksityisyys - Suojaa APIt ja käyttäjät",
+  "station.security-and-privacy.description": "Toteuta tietoturva- ja yksityisyydensuojatoimenpiteet, joilla suojataan rajapintoja ja käyttäjätietoja uhkilta ja tietoturvaloukkauksilta.",
+  "station.security-and-privacy.why_it_matters": "APIt ovat alttiita tietoturvauhkille ja tietomurroille. Tämä asema tarjoaa ohjeita tietoturva- ja yksityisyydensuojatoimenpiteiden toteuttamiseen, joilla suojataan rajapintoja ja käyttäjätietoja ja varmistetaan luottamus ja vaatimustenmukaisuus.",
+  "station.security-and-privacy.apply_in_work": "Tarjotaan tietoturvakehyksiä, -työkaluja ja parhaita käytäntöjä rajapintojen turvallisuutta ja yksityisyyttä varten. Varmistaa, että tiimit toteuttavat tietoturvatoimenpiteitä koko APIn elinkaaren ajan suunnittelusta julkaisuun ja seurantaan.",
+  "station.security-and-privacy.outcomes": "Uhkia ja haavoittuvuuksia vastaan suojatut rajapinnat",
+  "station.security-and-privacy.how_it_works": "Toteuta turvatoimia, kuten todennus, valtuutus, salaus ja nopeuden rajoittaminen, suojaamaan rajapintoja uhkilta.",
+  "station.design-standards.title": "Suunnittelustandardit - Varmistaa johdonmukainen ja laadukas API-suunnittelu.",
+  "station.design-standards.description": "Suunnittelustandardien ja -ohjeiden laatiminen, jotta varmistetaan yhdenmukainen ja laadukas API-suunnittelu koko organisaatiossa.",
+  "station.design-standards.why_it_matters": "Johdonmukainen ja laadukas API-suunnittelu on olennaisen tärkeää käytettävyyden, ylläpidettävyyden ja skaalautuvuuden kannalta. Tämä asema tarjoaa suunnittelustandardeja ja -ohjeita, joiden avulla tiimit voivat luoda rajapintoja, joita on helppo käyttää, ymmärtää ja ylläpitää.",
+  "station.design-standards.apply_in_work": "Suunnittelustandardien dokumentointi, uudelleenkäytettävät komponentit ja suunnittelun tarkistusprosessit. Varmistetaan, että tiimit noudattavat suunnittelustandardeja ja tekevät säännöllisiä tarkistuksia laadukkaan API-suunnittelun ylläpitämiseksi.",
+  "station.design-standards.outcomes": "Yhdenmukainen API-suunnittelu koko organisaatiossa",
+  "station.design-standards.how_it_works": "Määrittele API-suunnittelun suunnittelustandardit ja -ohjeet, mukaan lukien nimeämiskäytännöt, vastausmuodot ja virheenkäsittely.",
+  "station.vendor-management.title": "Toimittajan hallinta - Kolmannen osapuolen API-integraatioiden hallinta",
+  "station.vendor-management.description": "Hallinnoi tehokkaasti kolmannen osapuolen API-toimittajia ja integraatioita luotettavuuden ja vaatimustenmukaisuuden varmistamiseksi.",
+  "station.vendor-management.why_it_matters": "Kolmannen osapuolen rajapinnat voivat aiheuttaa riskejä ja riippuvuuksia, jotka vaikuttavat rajapintaekosysteemiisi. Tämä asema tarjoaa ohjeita toimittajasuhteiden hallintaan, luotettavuuden ja vaatimustenmukaisuuden varmistamiseen sekä API-strategian noudattamiseen.",
+  "station.vendor-management.apply_in_work": "Tarjotaan toimittajien hallintakehykset, arviointikriteerit ja seurantatyökalut. Varmistetaan, että tiimit hallinnoivat tehokkaasti kolmannen osapuolen API-toimittajia ja varmistavat luotettavuuden, vaatimustenmukaisuuden ja organisaation standardien noudattamisen.",
+  "station.vendor-management.outcomes": "Tehokkaat myyjien hallinnointiprosessit on otettu käyttöön",
+  "station.vendor-management.how_it_works": "Ota käyttöön toimittajahallintaprosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
+  "station.contract-design.title": "Sopimussuunnittelu - Määrittele selkeät API-sopimukset",
+  "station.contract-design.description": "Luo selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
+  "station.contract-design.why_it_matters": "API-sopimukset ovat olennaisen tärkeitä, jotta varmistetaan selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita selkeiden, kattavien ja helposti ymmärrettävien API-sopimusten suunnitteluun.",
+  "station.contract-design.apply_in_work": "Tarjotaan sopimussuunnittelumalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
+  "station.contract-design.outcomes": "Kullekin ajapinnalle määritellyt selkeät API-sopimukset",
+  "station.contract-design.how_it_works": "Määrittele API-sopimukset, joissa hahmotellaan kunkin APIn odotukset, vastuut ja käyttöohjeet.",
+  "station.development.title": "Kehitys - Rakenna APIt parhaiden käytäntöjen avulla",
+  "station.development.description": "Toteuta rajapinnat parhaiden käytäntöjen ja kehysten avulla laadun, ylläpidettävyyden ja skaalautuvuuden varmistamiseksi.",
+  "station.development.why_it_matters": "APIn kehittäminen on kriittinen vaihe, joka määrittää APIn laadun ja luotettavuuden. Tämä asema tarjoaa parhaita käytäntöjä ja kehyksiä API-kehitystä varten, jotta varmistetaan, että APIt rakennetaan korkeiden standardien mukaisesti ja että niitä voidaan ylläpitää ja skaalata tehokkaasti.",
+  "station.development.apply_in_work": "Kehityskehysten, kirjastojen ja koodausstandardien tarjoaminen API-toteutusta varten. Varmistaa, että tiimit noudattavat parhaita käytäntöjä, ja suorittaa koodin tarkistuksia API-kehityksen laadun ylläpitämiseksi.",
+  "station.development.outcomes": "parhaita käytäntöjä ja kehyksiä hyödyntävät rajapinnat",
+  "station.development.how_it_works": "Käytetään vakiintuneita kehyksiä ja kirjastoja rajapintojen toteuttamiseen ja varmistetaan, että ne ovat uudelleenkäytettäviä ja ylläpidettäviä.",
+  "station.ci-cd.title": "CI/CD - Automatisoi API-kehitys",
+  "station.ci-cd.description": "Ota käyttöön jatkuvan integroinnin ja jatkuvan toimituksen (CI/CD) putket API-kehityksen automatisoimiseksi ja tasaisen laadun varmistamiseksi.",
+  "station.ci-cd.why_it_matters": "CI/CD on olennaisen tärkeää sen varmistamiseksi, että rajapinnat toimitetaan nopeasti, luotettavasti ja laadukkaasti. Tämä asema tarjoaa ohjeita CI/CD-putkien toteuttamiseen, jotka automatisoivat API-rajapintojen rakentamis-, testaus- ja käyttöönottoprosessit.",
+  "station.ci-cd.apply_in_work": "CI/CD-kehysten, työkalujen ja parhaiden käytäntöjen tarjoaminen API-kehitystä varten. Varmistetaan, että tiimit ottavat käyttöön automatisoidut putket, jotka tukevat APIen jatkuvaa integrointia, testausta ja käyttöönottoa.",
+  "station.ci-cd.outcomes": "Automaattiset CI/CD-putket API-toimituksia varten.",
+  "station.ci-cd.how_it_works": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
+  "station.test-automation.title": "Testausautomaatio - varmista API-laatu",
+  "station.test-automation.description": "Ota käyttöön automatisoituja testauskäytäntöjä APIn laadun, luotettavuuden ja suorituskyvyn varmistamiseksi.",
+  "station.test-automation.why_it_matters": "Automatisoitu testaus on ratkaisevan tärkeää sen varmistamiseksi, että rajapinnat toimivat oikein ja täyttävät laatuvaatimukset. Tämä asema tarjoaa ohjeita automaattisten testauskäytäntöjen käyttöönottoon, jotka kattavat APIen toiminnallisen, turvallisuus- ja suorituskykytestauksen.",
+  "station.test-automation.apply_in_work": "Testausautomaatiokehysten, -työkalujen ja parhaiden käytäntöjen tarjoaminen API-testausta varten. Varmistetaan, että tiimit toteuttavat automatisoituja testejä, jotka kattavat APIen toiminnalliset, turvallisuus- ja suorituskykyyn liittyvät näkökohdat.",
+  "station.test-automation.outcomes": "API-rajapintojen automatisoidut testauskäytännöt",
+  "station.test-automation.how_it_works": "Käytetään automatisoituja testausvälineitä API-toiminnallisuuden, tietoturvan ja suorituskyvyn validointiin.",
+  "station.release-management.title": "Julkaisunhallinta - Hallitse API-julkaisuja tehokkaasti",
+  "station.release-management.description": "Ota käyttöön julkaisujen hallintakäytäntöjä sujuvien ja valvottujen API-julkaisujen varmistamiseksi.",
+  "station.release-management.why_it_matters": "Tehokas julkaisujen hallinta on olennaisen tärkeää, jotta voidaan varmistaa, että API-julkaisut ovat sujuvia, hallittuja ja liiketoiminnan tarpeiden mukaisia. Tämä asema tarjoaa ohjeita API-julkaisujen hallintaan, mukaan lukien versiointi, käyttöönottostrategiat ja palautusmenettelyt.",
+  "station.release-management.apply_in_work": "Tarjotaan julkaisunhallintakehykset, versiointiohjeet ja käyttöönottostrategiat. Varmistetaan, että tiimit noudattavat parhaita käytäntöjä API-julkaisujen hallinnassa, mukaan lukien versiointi, käyttöönotto ja palautusmenettelyt.",
+  "station.release-management.outcomes": "Hallitut ja sujuvat API-julkaisut",
+  "station.release-management.how_it_works": "Määrittele rajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
+  "station.service-agreements.title": "Palvelusopimukset - määrittele API-palvelutasot",
+  "station.service-agreements.description": "Laadi palvelusopimukset, joissa määritellään API-toimittajien ja kuluttajien odotukset, palvelutasot ja vastuut.",
+  "station.service-agreements.why_it_matters": "Palvelusopimukset ovat olennaisen tärkeitä, jotta voidaan varmistaa selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita sellaisten palvelusopimusten laatimiseen, joissa hahmotellaan odotukset, palvelutasot ja vastuut, mikä vähentää väärinkäsityksiä ja riitoja.",
+  "station.service-agreements.apply_in_work": "Tarjotaan palvelusopimusmalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja tarkkaan määritellyt palvelusopimukset, joissa hahmotellaan API-toimittajien ja -kuluttajien odotukset, palvelutasot ja vastuut.",
+  "station.service-agreements.outcomes": "Kullekin rajapinnalle määritellyt selkeät palvelusopimukset",
+  "station.service-agreements.how_it_works": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin rajapintaa varten.",
+  "station.api-consumer-adoption.title": "APIn käyttöönotto - APIn käytön edistäminen",
+  "station.api-consumer-adoption.description": "Toteutat strategioita, joilla edistetään API-käyttäjien hyväksyntää ja sitoutumista ja varmistetaan, että API-rajapintoja käytetään tehokkaasti.",
+  "station.api-consumer-adoption.why_it_matters": "API-käyttäjien hyväksynnän edistäminen on ratkaisevan tärkeää APIen arvon hyödyntämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä API-kuluttajien sitouttamiseksi ja sen varmistamiseksi, että he ymmärtävät, miten API-rajapintoja käytetään tehokkaasti ja miten niistä saadaan arvoa.",
+  "station.api-consumer-adoption.apply_in_work": "Tarjotaan API-kuluttajille resursseja, koulutusmateriaalia ja sitouttamisstrategioita. Varmistetaan, että tiimit toteuttavat strategioita, jotka edistävät API-kuluttajien hyväksyntää, sitoutumista ja tyytyväisyyttä.",
+  "station.api-consumer-adoption.outcomes": "APIn käyttöönottostrategioiden toteuttaminen kuluttajille",
+  "station.api-consumer-adoption.how_it_works": "Kehitetään käyttöönottoprosesseja ja resursseja, joiden avulla API-käyttäjät ymmärtävät, miten Rajapintoja käytetään tehokkaasti.",
+  "station.api-promotion.title": "API-näkyvyys - APIn näkyvyyden ja käytön lisääminen",
+  "station.api-promotion.description": "Edistetään rajapintoja näkyvyyden, käytön ja hyväksynnän lisäämiseksi kohdeyleisöjen keskuudessa.",
+  "station.api-promotion.why_it_matters": "API-rajapintojen tunnetuksi tekeminen on olennaisen tärkeää niiden näkyvyyden lisäämiseksi ja käytön edistämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä APIen tehokkaaseen markkinointiin kohdeyleisöille, jotta varmistetaan, että nämä ovat tietoisia APIista ja ymmärtävät niiden arvon.",
+  "station.api-promotion.apply_in_work": "Tarjotaan markkinointistrategioita, myynninedistämismateriaalia ja resursseja yhteisön sitouttamiseen. Varmistaa, että tiimit toteuttavat tehokkaita APIn edistämisstrategioita, jotka lisäävät näkyvyyttä, käyttöä ja käyttöönottoa kohdeyleisöjen keskuudessa.",
+  "station.api-promotion.outcomes": "Toteutetut API-edistämisstrategiat",
+  "station.api-promotion.how_it_works": "Kehitä markkinointistrategioita APIen markkinoimiseksi kohdeyleisöille, mukaan lukien sosiaalinen media, blogit ja webinaarit.",
+  "station.partner-integration.title": "Kumppanien integrointi - Tee yhteistyötä kumppaneiden kanssa",
+  "station.partner-integration.description": "Helpota kumppani-integraatioita API-ominaisuuksien parantamiseksi ja tavoittavuuden laajentamiseksi.",
+  "station.partner-integration.why_it_matters": "Kumppani-integraatiot voivat parantaa API-ominaisuuksia ja laajentaa tavoitettavuutta. Tämä asema tarjoaa ohjeita kumppanien kanssa tehtävään yhteistyöhön niiden rajapintojen integroimiseksi, jotta varmistetaan saumaton yhteentoimivuus ja arvon luominen.",
+  "station.partner-integration.apply_in_work": "Tarjotaan kumppaneiden integrointikehykset, ohjeet ja seurantatyökalut. Varmistaa, että tiimit tekevät tehokasta yhteistyötä kumppaneiden kanssa API-ominaisuuksien parantamiseksi, ulottuvuuden laajentamiseksi ja innovoinnin edistämiseksi.",
+  "station.partner-integration.outcomes": "Kumppaneiden integrointiprosessit on luotu",
+  "station.partner-integration.how_it_works": "Tunnista mahdolliset kumppanit, joiden APIt voivat parantaa API-valmiuksiasi ja arvolupaustasi.",
+  "station.api-mindset.title": "API-ajattelutapa - API-first -kulttuurin edistäminen",
+  "station.api-mindset.description": "Kehitä API-first -ajattelutapaa koko organisaatiossa innovoinnin ja yhteistyön edistämiseksi.",
+  "station.api-mindset.why_it_matters": "API-first -ajattelutapa on olennaisen tärkeä innovoinnin ja yhteistyön edistämiseksi koko organisaatiossa. Tämä asema tarjoaa strategioita API-first -kulttuurin kehittämiseksi ja sen varmistamiseksi, että rajapinnat nähdään strategisina voimavaroina, jotka tuottavat liiketoiminta-arvoa.",
+  "station.api-mindset.apply_in_work": "Tarjotaan koulutusohjelmia, resursseja ja viestintästrategioita API-first -kulttuurin edistämiseksi. Varmistetaan, että tiimit ymmärtävät APIen arvon ja että niillä on valtuudet johtaa API-strategiaa ja -aloitteita.",
+  "station.api-mindset.outcomes": "API-first -kulttuuri on vakiintunut koko organisaatioon",
+  "station.api-mindset.how_it_works": "Edistetään rajapintojen arvoa strategisina voimavaroina, jotka lisäävät liiketoiminnan arvoa ja innovointia.",
+  "station.roles-and-responsibilities.title": "Roolit ja vastuualueet - API-tiimien rakenteiden määrittelyt",
+  "station.roles-and-responsibilities.description": "Määrittele API-tiimeille selkeät roolit ja vastuualueet tehokkaan yhteistyön ja vastuuvelvollisuuden varmistamiseksi.",
+  "station.roles-and-responsibilities.why_it_matters": "Selkeät roolit ja vastuualueet ovat olennaisen tärkeitä tehokkaan yhteistyön ja vastuuvelvollisuuden kannalta API-tiimeissä. Tämä asema tarjoaa ohjeita tiimirakenteiden, roolien ja vastuualueiden määrittelyyn ja varmistaa, että kaikki ymmärtävät oman panoksensa API-aloitteisiin.",
+  "station.roles-and-responsibilities.apply_in_work": "Tarjotaan tiimirakenneohjeet, roolimäärittelyt ja viestintästrategiat. Varmistetaan, että tiimeillä on selkeät roolit ja vastuut, jotka edistävät tehokasta yhteistyötä ja vastuullisuutta API-aloitteissa.",
+  "station.roles-and-responsibilities.outcomes": "API-tiimeille on määritelty selkeät roolit ja vastuut",
+  "station.roles-and-responsibilities.how_it_works": "Määrittele API-tiimien tiimirakenteet ja roolit, mukaan lukien API-tuotteen omistajat, kehittäjät, arkkitehdit ja toiminnot.",
+  "station.upskilling.title": "Osaamisen kehittäminen - API-taitojen ja -tiedon parantaminen",
+  "station.upskilling.description": "Tarjotaan koulutusta ja resursseja API-taitojen ja -tiedon parantamiseksi koko organisaatiossa.",
+  "station.upskilling.why_it_matters": "Jatkuva oppiminen ja täydennyskoulutus ovat olennaisen tärkeitä, jotta API-tiimit pysyvät ajan tasalla uusimmista teknologioista, käytännöistä ja suuntauksista. Tämä asema tarjoaa koulutusohjelmia ja resursseja API-taitojen ja -tiedon parantamiseen, jotta tiimit ovat valmiita toimittamaan korkealaatuisia API-rajapintoja.",
+  "station.upskilling.apply_in_work": "Tarjotaan koulutusohjelmia, resursseja ja arviointivälineitä API-taitojen ja -tietojen parantamiseksi. Varmistetaan, että tiimeillä on mahdollisuus jatkuvaan oppimiseen, joka antaa heille mahdollisuuden edistää API-innovaatioita ja laatua.",
+  "station.upskilling.outcomes": "API-taitojen ja -tiedon parantaminen koko organisaatiossa",
+  "station.upskilling.how_it_works": "Tunnistetaan keskeiset API-taidot ja -tiedot, joita on kehitettävä, kuten API-suunnittelu, tietoturva ja suorituskyky.",
+  "station.operating-guidelines.title": "Toimintaohjeet - API-hallinnon perustaminen",
+  "station.operating-guidelines.description": "Laaditaan toimintaohjeet ja hallintokäytännöt, joilla varmistetaan APIn johdonmukainen hallinta ja laatu.",
+  "station.operating-guidelines.why_it_matters": "Tehokas API-hallinta on olennaisen tärkeää, jotta voidaan varmistaa yhdenmukainen API-hallinta, laatu ja vaatimustenmukaisuus. Tämä asema tarjoaa toimintaohjeita ja hallintakäytäntöjä, jotka auttavat tiimejä hallinnoimaan API-rajapintoja tehokkaasti ja varmistamaan, että ne ovat organisaation standardien ja parhaiden käytäntöjen mukaisia.",
+  "station.operating-guidelines.apply_in_work": "Toimintaohjeiden, hallintakehysten ja seurantatyökalujen tarjoaminen API-hallintaa varten. Varmistaa, että tiimit noudattavat vakiintuneita käytäntöjä, jotka edistävät johdonmukaista API-hallintaa, laatua ja organisaation standardien noudattamista.",
+  "station.operating-guidelines.outcomes": "APIn hallintokäytännöt on vahvistettu",
+  "station.operating-guidelines.how_it_works": "Määrittele APIOps Cyclesiin perustuvat toimintaohjeet, joissa hahmotellaan API-hallinnan prosessit, standardit ja parhaat käytännöt.",
+  "station.portfolio-management.title": "Portfolionhallinta - hallinnoi API-portfoliota tehokkaasti",
+  "station.portfolio-management.description": "Hallinnoida API-salkkua tehokkaasti varmistaaksesi, että se on linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa.",
+  "station.portfolio-management.why_it_matters": "Tehokas rajapintasalkun hallinta on olennaisen tärkeää sen varmistamiseksi, että rajapinnat ovat linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa. Tämä asema tarjoaa ohjeita API-salkun hallintaan ja varmistaa, että APIt priorisoidaan, seurataan ja optimoidaan siten, että ne tuottavat mahdollisimman paljon arvoa.",
+  "station.portfolio-management.apply_in_work": "Tarjotaan salkunhallintakehykset, priorisointikriteerit ja seurantatyökalut API-hallintaa varten. Varmistaa, että tiimit hallinnoivat API-salkkua tehokkaasti ja varmistavat, että se on linjassa liiketoimintatavoitteiden ja strategisten aloitteiden kanssa ja tuottaa mahdollisimman paljon arvoa.",
+  "station.portfolio-management.outcomes": "API-salkunhallintakäytäntöjen käyttöönotto",
+  "station.portfolio-management.how_it_works": "Määrittele salkunhallintakäytännöt, joissa hahmotellaan API-salkun hallinnointiprosessit, mukaan lukien priorisointi, seuranta ja optimointi.",
+  "station.budget-and-resource-management.title": "Budjetin ja resurssien hallinta - Optimoi API-investoinnit",
+  "station.budget-and-resource-management.description": "Optimoi API-aloitteiden budjetin ja resurssien hallinta tehokkaiden investointien ja resurssien kohdentamisen varmistamiseksi.",
+  "station.budget-and-resource-management.why_it_matters": "Tehokas talousarvio- ja resurssienhallinta on olennaisen tärkeää, jotta voidaan varmistaa, että API-aloitteet ovat hyvin rahoitettuja ja resursoituja. Tämä asema tarjoaa ohjeita budjetin ja resurssien hallinnan optimoimiseksi ja sen varmistamiseksi, että API-aloitteet ovat linjassa liiketoimintatavoitteiden kanssa ja tuottavat maksimaalista arvoa.",
+  "station.budget-and-resource-management.apply_in_work": "Tarjotaan API-aloitteille budjettihallintakehykset, priorisointikriteerit ja seurantatyökalut. Varmistaa, että tiimit hallinnoivat tehokkaasti budjetteja ja resursseja ja optimoivat API-kehitykseen ja -hallintaan tehdyt investoinnit mahdollisimman suuren arvon tuottamiseksi.",
+  "station.budget-and-resource-management.outcomes": "API-aloitteita varten laaditut budjetti- ja resurssienhallintakäytännöt",
+  "station.budget-and-resource-management.how_it_works": "Määrittele budjetti- ja resurssienhallintakäytännöt, joissa hahmotellaan API-aloitteiden budjettien ja resurssien hallinnointiprosessit.",
+  "station.api-product-strategy.outcomes.1": "Yhteinen kieli tuotteen, suunnittelun ja tekniikan välillä",
+  "station.api-product-strategy.outcomes.2": "vankka esitys tai peruste rahoituksen/hyväksynnän saamiseksi.",
+  "station.api-product-strategy.how_it_works.1": "Määrittele keskeiset entiteetit, niiden ominaisuudet ja suhteet, jotta voidaan luoda yhteinen käsitteellinen ymmärrys eri matkojen ja lopulta APIen välille.",
+  "station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tallentaaksesi tuetut liiketoimintatehtävät sekä API-käyttäjien ongelmat, hyödyt ja ominaisuudet, jotka muovaavat uusia tai uudelleenkäytettäviä API-rajapintoja.",
+  "station.api-product-strategy.how_it_works.3": "Määrittele arvo - käyttäjille ja liiketoiminnalle - API-liiketoimintamallin avulla, jotta API-strategiastasi tulee visuaalinen, jaettavissa oleva ja helposti validoitava API-asiakkaiden kanssa seuraavalla asemalla.",
+  "station.api-consumer-experience.outcomes.1": "Määrittele API-kokemuksen matka",
+  "station.api-consumer-experience.outcomes.2": "Suunnittele sisäänajo, dokumentointi ja palaute",
+  "station.api-consumer-experience.outcomes.3": "Paranna hyväksyntää aidon empatian ja kehittäjäkokemuksen (DX) avulla.",
+  "station.api-platform-architecture.outcomes.1": "Johdonmukaisen hallinnon toteuttaminen ilman raskasta ylhäältä alaspäin suuntautuvaa valvontaa",
+  "station.api-platform-architecture.outcomes.2": "Suunnittelu sisäistä uudelleenkäyttöä ja ulkoista skaalautuvuutta varten",
+  "station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja kuluttajien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
+  "station.api-platform-architecture.how_it_works.2": "Capacity Canvas -ohjelmassa sovitetaan yhteen liiketoimintatapahtumien mallit, tulevat kulutustrendit ja tekniset ratkaisut, jotta voidaan varmistaa APIn skaalautuvuus ja suorituskyky. Se tarjoaa kriittisen panoksen skaalautumispäätöksiä ja infrastruktuurin suunnittelua varten.",
+  "station.api-platform-architecture.how_it_works.3": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
+  "station.api-design.outcomes.1": "Uudelleenkäytettävät ja validoidut API-sopimukset",
+  "station.api-design.outcomes.2": "Toimialamallien ja vuorovaikutusmallien mukaiset mallit",
+  "station.api-design.outcomes.3": "Suunnittelun jäljitettävyys liiketoiminnan arvoon",
+  "station.api-design.how_it_works.1": "Määrittele Interaction Canvasin avulla, miten hyödyntäjät ovat vuorovaikutuksessa APIn kanssa, ja Varmistetaan, että se vastaa heidän tarpeitaan ja odotuksiaan.",
+  "station.api-design.how_it_works.2": "Sovellat REST-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "station.api-design.how_it_works.3": "Sovellat tapahtumapohjaisia suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "station.api-design.how_it_works.4": "Sovellat GraphQL-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "station.api-design.how_it_works.5": "Käytä suunnitteluperiaatteita ja API-tyyliohjetta, jotta suunnittelupäätöksesi ovat linjassa yhteisten sääntöjen kanssa ja mahdollistavat johdonmukaisen auditoinnin ja validoinnin.",
+  "station.api-design.how_it_works.6": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API-suunnittelu täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "station.api-design.how_it_works.7": "Käytä API-tarkastuslistaa varmistaaksesi, että API-suunnittelu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien turvallisuus, suorituskyky ja vaatimustenmukaisuus.",
+  "station.api-delivery.outcomes.1": "Luotettavat ja automatisoidut CI/CD-putket",
+  "station.api-delivery.outcomes.2": "Toiminnallinen ja ei-toiminnallinen testaus integroitu",
+  "station.api-delivery.outcomes.3": "Turvalliset ja vaatimustenmukaiset kehitysputket",
+  "station.api-delivery.how_it_works.1": "Rakenna API-toteutus validoidun sopimuksen pohjalta käyttäen vakiintuneita kehysrakenteita, kirjastoja ja tiimin standardeja.",
+  "station.api-delivery.how_it_works.2": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
+  "station.api-delivery.how_it_works.3": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
+  "station.api-delivery.how_it_works.4": "Varmistetaan, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
+  "station.api-delivery.how_it_works.5": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "station.api-audit.outcomes.1": "Selkeä dokumentaatio API-suunnittelusta ja toteutuspäätöksistä",
+  "station.api-audit.outcomes.2": "Turvallisuus, suorituskyky ja vaatimustenmukaisuus validoitu",
+  "station.api-audit.outcomes.3": "Tuotannossa ilmenevien ongelmien riskin pienentäminen",
+  "station.api-audit.how_it_works.1": "Käytä tarkistuslistoja, automatisoituja tarkistustyökaluja eli linttereitä ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
+  "station.api-audit.how_it_works.2": "Tee yhteistyötä hallintotiimien ja toimialan asiantuntijoiden kanssa varmistaaksesi, että rajapinnat ovat valmiita tuotantoon.",
+  "station.api-publishing.outcomes.1": "Selkeät API-käyttöönotto- ja rekisteröintiprosessit",
+  "station.api-publishing.outcomes.2": "Dokumentaatio, turvallisuusmallit ja -käytännöt saatavilla",
+  "station.api-publishing.outcomes.3": "APIt valmiina skaalautumiseen ja hallintaan",
+  "station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaa, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
+  "station.api-publishing.how_it_works.2": "Varmistetaan, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja kuluttajien saatavilla.",
+  "station.monitoring-and-improving.outcomes.1": "Kehittäjien palautekierrokset käytössä",
+  "station.monitoring-and-improving.outcomes.2": "Jatkuvasti tunnistetut ja käsitellyt ongelmat",
+  "station.monitoring-and-improving.outcomes.3": "APIn iterointi käyttäjien tarpeiden mukaisesti",
+  "station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
+  "station.monitoring-and-improving.how_it_works.2": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia.",
+  "station.user-experience.outcomes.1": "Intuitiiviset ja johdonmukaiset käyttöliittymät",
+  "station.user-experience.outcomes.2": "Käyttäjien palaute sisällytetty APIn suunnitteluun",
+  "station.user-experience.outcomes.3": "Parempi käyttäjätyytyväisyys ja hyväksyntä",
+  "station.user-experience.how_it_works.1": "Suorita käyttäjätutkimus kerätäksesi tietoa siitä, miten hyödyntäjät ovat vuorovaikutuksessa ekosysteemipalveluiden tai API-sovelluksia käyttävien sovellusten kanssa.",
+  "station.user-experience.how_it_works.2": "Dokumentoi käyttäjäkokemusta koskevat vaatimukset, jotta niitä voidaan käyttää API-suunnittelussa ja varmistaa, että ne ovat intuitiivisia ja helppokäyttöisiä.",
+  "station.market-insights.outcomes.1": "Määritetyt alan standardit ja parhaat käytännöt",
+  "station.market-insights.outcomes.2": "API-strategia linjassa markkinoiden tarpeiden kanssa",
+  "station.market-insights.outcomes.3": "Markkinatietoon perustuva tietoon perustuva päätöksenteko",
+  "station.market-insights.how_it_works.1": "Analysoi kilpailijoiden rajapinnat ymmärtämään niiden vahvuudet, heikkoudet ja ainutlaatuiset myyntivaltit.",
+  "station.market-insights.how_it_works.2": "Tunnistetaan alan standardit ja parhaat käytännöt, jotta voidaan varmistaa, että rajapinnat ovat kilpailukykyisiä ja yhteensopivia.",
+  "station.business-goals.outcomes.1": "Kullekin Rajapinnalle määritelty selkeä liiketoiminta-arvo",
+  "station.business-goals.outcomes.2": "Sidosryhmien sitoutuminen ja tuki API-aloitteille",
+  "station.business-goals.outcomes.3": "APIt edistävät organisaation menestystä",
+  "station.business-goals.how_it_works.1": "Määritä keskeiset suorituskykyindikaattorit (KPI), joilla mitataan APIn onnistumista suhteessa liiketoiminnan tavoitteisiin.",
+  "station.business-goals.how_it_works.2": "Sidosryhmien sitouttaminen varmistamaan API-aloitteiden yhdenmukaisuus ja tuki.",
+  "station.competitive-analysis.outcomes.1": "Eriyttämismahdollisuudet tunnistettu",
+  "station.competitive-analysis.outcomes.2": "API-strategia, joka perustuu kilpailutietoon",
+  "station.competitive-analysis.outcomes.3": "Lisääntynyt kilpailukyky API-markkinoilla",
+  "station.competitive-analysis.how_it_works.1": "Tunnista markkinapuutteet, jotka rajapintasi voivat täyttää kilpailijoiden tarjonnan perusteella.",
+  "station.competitive-analysis.how_it_works.2": "Kehitä erottautumisstrategia, jossa korostetaan rajapintojesi ainutlaatuisia ominaisuuksia ja etuja.",
+  "station.ecosystem-vision.outcomes.1": "APIt, jotka on suunniteltu mahdollistamaan yhteistyö ja integrointi",
+  "station.ecosystem-vision.outcomes.2": "Ekosysteemikumppanit tunnistetaan ja otetaan mukaan",
+  "station.ecosystem-vision.outcomes.3": "APIt edistävät elinvoimaista ekosysteemiä",
+  "station.ecosystem-vision.how_it_works.1": "Tunnistetaan tärkeimmät ekosysteemikumppanit ja sidosryhmät, jotka hyötyvät ekosysteemistä tai osallistuvat siihen.",
+  "station.ecosystem-vision.how_it_works.2": "Suunnittele rajapinnat, jotka mahdollistavat saumattoman integroinnin ja yhteistyön ekosysteemissä.",
+  "station.scalable-infrastructure.outcomes.1": "Korkea käytettävyys ja suorituskyky kuormitettuna",
+  "station.scalable-infrastructure.outcomes.2": "Tulevaa kasvua varten suunniteltu infrastruktuuri",
+  "station.scalable-infrastructure.outcomes.3": "Vähentää käyttökatkoksia ja parantaa käyttäjäkokemusta",
+  "station.scalable-infrastructure.how_it_works.1": "Toteuta kuorman tasapainottaminen, välimuistitallennus ja muut tekniikat korkean käytettävyyden ja suorituskyvyn varmistamiseksi. Kerää infrastruktuurivaatimukset API-tiimeiltä Capacity Canvasin avulla.",
+  "station.scalable-infrastructure.how_it_works.2": "Seuraa infrastruktuurin suorituskykyä ja kapasiteettia sen varmistamiseksi, että se pystyy vastaamaan kasvavaan kysyntään.",
+  "station.legal-and-compliance.outcomes.1": "Tietosuojaa ja yksityisyyden suojaa koskevat vaatimukset täyttyvät",
+  "station.legal-and-compliance.outcomes.2": "Oikeudellisten riskien tunnistaminen ja lieventäminen",
+  "station.legal-and-compliance.outcomes.3": "Vaatimustenmukaisuustoimenpiteiden selkeä dokumentointi",
+  "station.legal-and-compliance.how_it_works.1": "Toteuta toimenpiteitä, joilla varmistetaan, että rajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
+  "station.legal-and-compliance.how_it_works.2": "dokumentoida vaatimustenmukaisuustoimenpiteet ja varmistaa, että niistä tiedotetaan sidosryhmille ja kuluttajille.",
+  "station.security-and-privacy.outcomes.1": "Käyttäjätiedot suojattu yksityisyydensuojatoimenpiteiden avulla",
+  "station.security-and-privacy.outcomes.2": "Parhaat turvallisuuskäytännöt API-suunnittelussa ja -kehityksessä",
+  "station.security-and-privacy.outcomes.3": "Turvallisuusstandardien ja -säännösten noudattaminen",
+  "station.security-and-privacy.how_it_works.1": "Varmistetaan käyttäjien tietojen yksityisyys toteuttamalla tietosuojatoimenpiteitä, kuten anonymisointi ja käyttöoikeuksien valvonta.",
+  "station.security-and-privacy.how_it_works.2": "Suorittaa säännöllisiä tietoturvatarkastuksia ja haavoittuvuusarviointeja riskien tunnistamiseksi ja vähentämiseksi.",
+  "station.design-standards.outcomes.1": "Laadukkaat APIt, jotka vastaavat käyttäjien tarpeita",
+  "station.design-standards.outcomes.2": "Uudelleenkäytettävät suunnittelumallit ja komponentit",
+  "station.design-standards.outcomes.3": "Vähennetään suunnittelun epäjohdonmukaisuuksia ja teknistä velkaa.",
+  "station.design-standards.how_it_works.1": "Luo uudelleenkäytettäviä suunnittelumalleja ja -komponentteja, joita tiimit voivat hyödyntää yhdenmukaisuuden ja laadun varmistamiseksi.",
+  "station.design-standards.how_it_works.2": "Suoritat suunnittelun tarkastuksia ja auditointeja varmistaaksesi suunnittelustandardien noudattamisen ja yksilöidäksesi parannuskohteet.",
+  "station.vendor-management.outcomes.1": "Kolmannen osapuolen APIt integroituvat luotettavasti ja turvallisesti.",
+  "station.vendor-management.outcomes.2": "Myyjä noudattaa organisaation standardeja",
+  "station.vendor-management.outcomes.3": "Kolmannen osapuolen riippuvuuksiin liittyvien riskien vähentäminen",
+  "station.vendor-management.how_it_works.1": "Määrittele kriteerit toimittajien rajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
+  "station.vendor-management.how_it_works.2": "Seuraa toimittajien suorituskykyä ja palvelutasosopimusten (SLA) ja organisaation standardien noudattamista.",
+  "station.contract-design.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja vastuut hahmoteltuina",
+  "station.contract-design.outcomes.2": "Käyttöohjeet ja parhaat käytännöt dokumentoitu",
+  "station.contract-design.outcomes.3": "APIn käyttöä koskevien väärinkäsitysten ja riitojen väheneminen.",
+  "station.contract-design.how_it_works.1": "Käytä standardoituja formaatteja (esim. OpenAPI, AsyncAPI) luodaksesi koneellisesti luettavia API-sopimuksia, joita on helppo jakaa ja validoida.",
+  "station.contract-design.how_it_works.2": "Varmistetaan, että sidosryhmät tarkistavat ja hyväksyvät API-sopimukset, jotta varmistetaan niiden yhdenmukaisuus ja selkeys.",
+  "station.development.outcomes.1": "Laadukkaat, ylläpidettävät ja skaalautuvat rajapinnat.",
+  "station.development.outcomes.2": "Johdonmukaiset koodausstandardit ja -käytännöt",
+  "station.development.outcomes.3": "Vähentää kehitysaikaa ja teknistä velkaa",
+  "station.development.how_it_works.1": "Sovellat sopimuslähtöisiä tai suunnittelulähtöisiä lähestymistapoja varmistaaksesi, että API-sopimukset validoidaan ennen toteutusta.",
+  "station.development.how_it_works.2": "Noudata koodausstandardeja ja parhaita käytäntöjä varmistaaksesi johdonmukaisen ja laadukkaan API-kehityksen.",
+  "station.ci-cd.outcomes.1": "API-kehityksen tasainen laatu ja jäljitettävyys",
+  "station.ci-cd.outcomes.2": "Nopeammat iteraatiot ja lyhyempi aika markkinoille saattamiseen",
+  "station.ci-cd.outcomes.3": "Parempi yhteistyö ja palautekierrokset API-kehityksessä",
+  "station.ci-cd.how_it_works.1": "Integroi toiminnallinen ja ei-toiminnallinen testaus CI/CD-putkeen varmistaaksesi, että rajapinnat täyttävät laatuvaatimukset.",
+  "station.ci-cd.how_it_works.2": "Toteuta automaattiset tietoturvatarkastukset ja vaatimustenmukaisuuden validoinnit CI/CD-putkessa varmistaaksesi, että rajapinnat ovat turvallisia ja vaatimustenmukaisia.",
+  "station.test-automation.outcomes.1": "Automaattiset toiminnalliset, turvallisuus- ja suorituskykytestit",
+  "station.test-automation.outcomes.2": "Vähentää manuaalisen testauksen työmäärää ja lisää testien kattavuutta",
+  "station.test-automation.outcomes.3": "APIn luotettavuuden ja laadun parantaminen",
+  "station.test-automation.how_it_works.1": "Toteuta testiautomaatiokehykset, jotka tukevat sopimustestausta, integrointitestausta ja päästä päähän -testausta.",
+  "station.test-automation.how_it_works.2": "Integroi automatisoidut testit CI/CD-putkeen API-laadun jatkuvan validoinnin varmistamiseksi.",
+  "station.release-management.outcomes.1": "Versiointi- ja käyttöönottostrategioiden määrittely",
+  "station.release-management.outcomes.2": "API-julkaisuja varten vahvistetut palautusmenettelyt",
+  "station.release-management.outcomes.3": "API-muutoksiin liittyvien riskien vähentäminen",
+  "station.release-management.how_it_works.1": "Ota käyttöön käyttöönottostrategioita (esim. sinivihreät käyttöönotot, canary releaset) API-julkaisuihin liittyvien riskien minimoimiseksi.",
+  "station.release-management.how_it_works.2": "Ota käyttöön palautusmenettelyt, jotta muutokset voidaan palauttaa nopeasti, jos API-julkaisujen aikana ilmenee ongelmia.",
+  "station.service-agreements.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja palvelutasot hahmoteltuina",
+  "station.service-agreements.outcomes.2": "Dokumentoidut vastuualueet ja tukiprosessit",
+  "station.service-agreements.outcomes.3": "Parempi viestintä ja yhteistyö API-tiimien välillä",
+  "station.service-agreements.how_it_works.1": "Luo koneellisesti luettavia palvelusopimuksia, joita on helppo jakaa ja validoida, käyttämällä standardoituja muotoja.",
+  "station.service-agreements.how_it_works.2": "Varmistetaan, että sidosryhmät tarkistavat ja hyväksyvät palvelusopimukset, jotta varmistetaan niiden yhdenmukaisuus ja selkeys.",
+  "station.api-consumer-adoption.outcomes.1": "APIn käytön ja sitoutumisen lisääminen",
+  "station.api-consumer-adoption.outcomes.2": "APIn hyödyntäjät saavat tietoa APIn ominaisuuksista ja hyödyistä",
+  "station.api-consumer-adoption.outcomes.3": "Parempi API-hyödyntäjätyytyväisyys ja -uskollisuus",
+  "station.api-consumer-adoption.how_it_works.1": "Luo opetusmateriaalia (esim. opetusohjelmia, dokumentaatiota), jossa selitetään APIn ominaisuuksia, hyötyjä ja käyttötapoja.",
+  "station.api-consumer-adoption.how_it_works.2": "Kytkeydy API-käyttäjiin palautekierrosten, tukikanavien ja yhteisöfoorumien kautta ymmärtämään heidän tarpeitaan ja parantamaan APIn käyttöönottoa.",
+  "station.api-promotion.outcomes.1": "APIn näkyvyyden ja tietoisuuden lisääminen",
+  "station.api-promotion.outcomes.2": "Korkeampi APIn käyttö- ja hyväksymisaste",
+  "station.api-promotion.outcomes.3": "Parempi API-kuluttajien sitoutuminen ja tyytyväisyys",
+  "station.api-promotion.how_it_works.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan rajapintojen arvoa ja hyötyjä.",
+  "station.api-promotion.how_it_works.2": "Osallistu API-yhteisöihin ja -foorumeihin API-päivitysten jakamiseksi, palautteen keräämiseksi ja APIn käytön edistämiseksi.",
+  "station.partner-integration.outcomes.1": "Parannetut API-ominaisuudet kumppani-APIen avulla",
+  "station.partner-integration.outcomes.2": "Kumppanuuksien avulla laajennettu ulottuvuus ja markkinamahdollisuudet",
+  "station.partner-integration.outcomes.3": "Parempi yhteistyö ja innovointi kumppaneiden kanssa",
+  "station.partner-integration.how_it_works.1": "Luodaan integraatioprosessit ja -ohjeet yhteistyökumppaneiden kanssa tehtävää yhteistyötä varten, mukaan lukien tekninen integraatio, tietojen jakaminen ja tuki.",
+  "station.partner-integration.how_it_works.2": "Seuraa kumppaneiden API-suorituskykyä ja vaatimustenmukaisuutta varmistaaksesi luotettavuuden ja yhteensopivuuden API-strategiasi kanssa.",
+  "station.api-mindset.outcomes.1": "Innovaation ja yhteistyön lisääminen rajapintojen avulla",
+  "station.api-mindset.outcomes.2": "API-tiimit, joilla on valtuudet johtaa API-strategiaa ja -aloitteita.",
+  "station.api-mindset.outcomes.3": "Liiketoiminnan tavoitteiden ja API-kehityksen parempi yhteensovittaminen.",
+  "station.api-mindset.how_it_works.1": "Kannustaa API-tiimien, liiketoimintayksiköiden ja sidosryhmien välistä monialaista yhteistyötä, jotta API-aloitteet voidaan sovittaa yhteen liiketoiminnan tavoitteiden kanssa.",
+  "station.api-mindset.how_it_works.2": "Tarjotaan koulutusta ja resursseja, jotta tiimit voivat omaksua API-first -ajattelutavan ja ymmärtää APIen edut.",
+  "station.roles-and-responsibilities.outcomes.1": "Tehokas yhteistyö ja vastuuvelvollisuus API-tiimeissä",
+  "station.roles-and-responsibilities.outcomes.2": "Parempi viestintä ja yhdenmukaistaminen tiimin jäsenten välillä",
+  "station.roles-and-responsibilities.outcomes.3": "Sekaannusten ja päällekkäisyyksien vähentäminen vastuualueilla",
+  "station.roles-and-responsibilities.how_it_works.1": "Määritä selkeät vastuualueet kullekin roolille, mukaan lukien API-suunnittelu, kehittäminen, testaus ja toiminta.",
+  "station.roles-and-responsibilities.how_it_works.2": "Varmistaa, että roolit ja vastuualueet ilmoitetaan kaikille tiimin jäsenille ja sidosryhmille, jotta varmistetaan niiden yhdenmukaisuus.",
+  "station.upskilling.outcomes.1": "API-suunnittelun, -kehityksen ja -hallinnan lisääntynyt osaaminen.",
+  "station.upskilling.outcomes.2": "Parempi kyky omaksua uutta teknologiaa ja uusia käytäntöjä",
+  "station.upskilling.outcomes.3": "Valtuutetaan tiimit edistämään API-innovaatioita ja laatua.",
+  "station.upskilling.how_it_works.1": "Tarjotaan koulutusohjelmia, työpajoja ja resursseja, joiden avulla tiimit voivat parantaa API-taitojaan ja -tietämystään.",
+  "station.upskilling.how_it_works.2": "Kannustetaan jatkuvaan oppimiseen verkkokurssien, sertifikaattien ja yhteisöllisen sitoutumisen avulla.",
+  "station.operating-guidelines.outcomes.1": "Yhdenmukainen API-hallinta ja laatu koko organisaatiossa",
+  "station.operating-guidelines.outcomes.2": "organisaation standardien ja parhaiden käytäntöjen noudattaminen",
+  "station.operating-guidelines.outcomes.3": "Parempi näkyvyys ja API-aloitteiden hallinta",
+  "station.operating-guidelines.how_it_works.1": "Ota käyttöön hallintokäytännöt, joilla varmistetaan, että rajapintoja hallinnoidaan johdonmukaisesti, mukaan lukien tarkistukset, auditoinnit ja vaatimustenmukaisuuden tarkastukset.",
+  "station.operating-guidelines.how_it_works.2": "Seuraa API-aloitteita varmistaaksesi toimintaohjeiden ja hallintokäytäntöjen noudattamisen.",
+  "station.portfolio-management.outcomes.1": "APIt linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa.",
+  "station.portfolio-management.outcomes.2": "APIen priorisointi ja optimointi arvon ja vaikutusten perusteella.",
+  "station.portfolio-management.outcomes.3": "Parempi näkyvyys ja API-portfolion hallinta",
+  "station.portfolio-management.how_it_works.1": "Laaditaan kriteerit rajapintojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden kanssa yhteensopivuuden perusteella.",
+  "station.portfolio-management.how_it_works.2": "Seuraa API-portfoliota varmistaaksesi, että APIt tuottavat arvoa, täyttävät suorituskykyodotukset ja ovat linjassa liiketoiminnan tavoitteiden kanssa.",
+  "station.budget-and-resource-management.outcomes.1": "Resurssien tehokas kohdentaminen API-aloitteisiin",
+  "station.budget-and-resource-management.outcomes.2": "Optimoidut investoinnit API-kehitykseen ja -hallintaan",
+  "station.budget-and-resource-management.outcomes.3": "Parempi taloudellinen näkyvyys ja API-aloitteiden valvonta.",
+  "station.budget-and-resource-management.how_it_works.1": "Laaditaan kriteerit budjettimäärärahojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden mukaisuuden perusteella.",
+  "station.budget-and-resource-management.how_it_works.2": "Seuraa budjettia ja resurssien käyttöä varmistaaksesi tehokkaat investoinnit ja resurssien jakamisen API-aloitteisiin.",
+  "cycle.api-productization-cycle.station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, käyttäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, ei tuotteina. Tulos? Hämmentyneitä kuluttajia, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
+  "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Tarjotaan ohjeita ja malleja API-liiketoimintamallien, arvolupausten ja etenemissuunnitelmien luomista varten.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Suoraviivainen API-arvolupaus ja yleisö",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Tutki asiakkaan tai yhteistyökumppanin ongelmaa, jonka oletat voivasi ratkaista APIen avulla. Kartoita sidosryhmät, niiden matkat ja tulokset Customer Journey canvasin avulla.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Yhteinen kieli tuotteen, suunnittelun ja tekniikan välillä",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "vankka esitys tai peruste rahoituksen/hyväksynnän saamiseksi.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Määrittele keskeiset entiteetit, niiden ominaisuudet ja suhteet, jotta voidaan luoda yhteinen käsitteellinen ymmärrys eri matkojen ja lopulta APIen välille.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tallentaaksesi tuetut liiketoimintatehtävät sekä API-käyttäjien ongelmat, hyödyt ja ominaisuudet, jotka muovaavat uusia tai uudelleenkäytettäviä API-rajapintoja.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Määrittele arvo - käyttäjille ja liiketoiminnalle - API-liiketoimintamallin avulla, jotta API-strategiastasi tulee visuaalinen, jaettavissa oleva ja helposti validoitava API-asiakkaiden kanssa seuraavalla asemalla.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia käyttäjiä varten.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Hyvät aPIt eivät ainoastaan toimi - ne tuntuvat intuitiivisilta. Riippumatta siitä, onko hyödyntäjä sisäinen kehittäjä, ulkoinen kumppani vai tekoälyagentti, heidän kokemuksensa ratkaisee hyväksynnän. Ilman selkeää kokemussuunnitelmaa",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Tarkastele olemassa olevaa API Value Proposition Canvasta API-hyödyntäjän näkökulmasta. Säilytä tuetut liiketoimintatehtävät vakaina ja rikasta tuskaa lievittäviä ja hyötyjä mahdollistavia ominaisuuksia API-hyödyntäjien näkökulmalla, jotta ne voivat ohjata myöhempiä suunnittelupäätöksiä.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-käyttäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-käyttäjälle.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Tarjotaan ohjeita, työkaluja ja palautemekanismeja sisäisten ja ulkoisten kehittäjien ja kumppaneiden kokemusten ymmärtämiseksi, analysoimiseksi ja parantamiseksi.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Tunnista ja priorisoi API-asiakkaat",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Määrittele API-kokemuksen matka",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Suunnittele sisäänajo, dokumentointi ja palaute",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Paranna hyväksyntää aidon empatian ja kehittäjäkokemuksen (DX) avulla.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.title": "API-alustan arkkitehtuuri",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Varmistetaan skaalautuvuus, uudelleenkäyttö ja hallinta API- ja alustakomponenttien välillä.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "Kun rajapinnat skaalautuvat eri tiimeille, alustan on mahdollistettava hallinta ja uudelleenkäyttö nopeutta estämättä. Tällä asemalla kerrotaan, miten API-arkkitehtuurit voidaan suunnitella pitkäikäisiksi, turvallisiksi ja tehokkaiksi.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Perustetaan skaalautuva, turvallinen ja vaatimustenmukainen infrastruktuuri API-toimintoja varten. Annetaan ohjeita arkkitehtuurin parhaista käytännöistä.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Vähennä turhia API-rajapintoja ja vähennä pilvialustakustannuksia.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Business Impact Canvas auttaa tunnistamaan ja lieventämään APIn saatavuuteen, tietoturvaan ja toiminnallisuuteen liittyviä riskejä ja tukemaan tietoon perustuvia arkkitehtuuripäätöksiä.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Johdonmukaisen hallinnon toteuttaminen ilman raskasta ylhäältä alaspäin suuntautuvaa valvontaa",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Suunnittelu sisäistä uudelleenkäyttöä ja ulkoista skaalautuvuutta varten",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja kuluttajien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Capacity Canvas -ohjelmassa sovitetaan yhteen liiketoimintatapahtumien mallit, tulevat kulutustrendit ja tekniset ratkaisut, jotta voidaan varmistaa APIn skaalautuvuus ja suorituskyky. Se tarjoaa kriittisen panoksen skaalautumispäätöksiä ja infrastruktuurin suunnittelua varten.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
+  "cycle.api-productization-cycle.station.api-design.title": "API-design - Suunnittele arvoa tuottavia rajapintoja",
+  "cycle.api-productization-cycle.station.api-design.description": "Luo API-suunnitelmia, jotka ovat johdonmukaisia, uudelleenkäytettäviä ja perustuvat liiketoiminnallisiin tavoitteisiin sekä yhteisiin standardeihin.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "APIen suunnittelu ei tarkoita pelkästään päätepisteiden (endpoints) nimeämistä. Hyvä suunnittelu varmistaa, että APIt ovat käyttökelpoisia, johdonmukaisia ja linjassa liiketoiminnallisten ja teknisten tavoitteiden kanssa. Huono suunnittelu johtaa tiukkoihin riippuvuuksiin, heikkoon uudelleenkäytettävyyteen ja kalliiseen uudelleen toteutukseen eri tiimien välillä.",
+  "cycle.api-productization-cycle.station.api-design.apply_in_work": "Tarjoa uudelleenkäytettäviä suunnittelumalleja, yhteisiä standardeja ja validointityökaluja API-määrityksille. Varmista, että suunnittelupäätökset ovat johdonmukaisia, tarkistettuja varhaisessa vaiheessa ja linjassa liiketoiminnallisten tavoitteiden kanssa.",
+  "cycle.api-productization-cycle.station.api-design.outcomes": "Hyvin dokumentoidut ja johdonmukaiset API-mallit",
+  "cycle.api-productization-cycle.station.api-design.how_it_works": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri rajapinnoille.",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Uudelleenkäytettävät ja validoidut API-sopimukset",
+  "cycle.api-productization-cycle.station.api-design.outcomes.2": "Toimialamallien ja vuorovaikutusmallien mukaiset mallit",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Suunnittelun jäljitettävyys liiketoiminnan arvoon",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Määrittele Interaction Canvasin avulla, miten hyödyntäjät ovat vuorovaikutuksessa APIn kanssa, ja Varmistetaan, että se vastaa heidän tarpeitaan ja odotuksiaan.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Sovellat REST-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Sovellat tapahtumapohjaisia suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Sovellat GraphQL-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Käytä suunnitteluperiaatteita ja API-tyyliohjetta, jotta suunnittelupäätöksesi ovat linjassa yhteisten sääntöjen kanssa ja mahdollistavat johdonmukaisen auditoinnin ja validoinnin.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API-suunnittelu täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Käytä API-tarkastuslistaa varmistaaksesi, että API-suunnittelu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien turvallisuus, suorituskyky ja vaatimustenmukaisuus.",
+  "cycle.api-productization-cycle.station.api-delivery.title": "API-kehitys - Kehitä turvalliset ja luotettavat rajapinnat",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Rakenna, testaa ja julkaise rajapintoja käyttämällä nykyaikaisia jakeluputkia ja parhaita teknisiä käytäntöjä.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Parhaatkin API-suunnitelmat epäonnistuvat, jos kehitys on epäjohdonmukaista. Tällä asemalla varmistetaan, että rajapinnat rakennetaan laadukkaasti, testataan perusteellisesti ja otetaan käyttöön luotettavasti, mikä mahdollistaa nopeammat iteraatiot ja suuremman luottamuksen.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Toimittaa koodauskehyksiä, kirjastoja ja standardeja API-toteutusta varten. CI/CD-putkien, laadunvarmistuskehysten ja käyttöönottoautomaatiotyökalujen toteuttaminen.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes": "Rajapinnat, jotka on toteutettu testattujen kehysten ja mallien avulla.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Käytä API-kehityksen parhaita käytäntöjä ohjeena validoidun sopimuksen toteuttamiseen vakiintuneilla kehysrakenteilla ja kirjastoilla varmistaen, että tulos on uudelleenkäytettävä ja ylläpidettävä.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Luotettavat ja automatisoidut CI/CD-putket",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Toiminnallinen ja ei-toiminnallinen testaus integroitu",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Turvalliset ja vaatimustenmukaiset kehitysputket",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Rakenna API-toteutus validoidun sopimuksen pohjalta käyttäen vakiintuneita kehysrakenteita, kirjastoja ja tiimin standardeja.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Varmistetaan, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "cycle.api-productization-cycle.station.api-audit.title": "API-auditointi - API-rajapintojen tarkastus vaatimustenmukaisuuden ja laadun varmistamiseksi",
+  "cycle.api-productization-cycle.station.api-audit.description": "Varmista, että APIt täyttävät liiketoiminta-, suunnittelu- ja toimintastandardit ennen julkaisua ja käyttöönottoa.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIt ovat pitkäikäisiä tuotteita, ja niiden on täytettävä laatu-, johdonmukaisuus- ja vaatimustenmukaisuusodotukset. Auditointi yhdistää suunnittelupäätökset, toteutuksen ja toimintavalmiuden määriteltyihin standardeihin, mikä vähentää riskejä ennen käyttöönottoa.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Luo johdonmukainen auditointiprosessi, joka arvioi APIn valmiutta elinkaaren eri vaiheissa määriteltyjen kriteerien, todisteiden ja standardien avulla. Varmista, että puutteet tunnistetaan varhaisessa vaiheessa ja korjataan ennen julkaisua.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "APIt täyttävät sisäiset ja ulkoiset standardit",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Suorita tarkastuksia varmistaaksesi, että rajapinnat täyttävät organisatoriset, tekniset ja oikeudelliset standardit ennen julkaisemista.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Selkeä dokumentaatio API-suunnittelusta ja toteutuspäätöksistä",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Turvallisuus, suorituskyky ja vaatimustenmukaisuus validoitu",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Tuotannossa ilmenevien ongelmien riskin pienentäminen",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Käytä tarkistuslistoja, automatisoituja tarkistustyökaluja eli linttereitä ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Tee yhteistyötä hallintotiimien ja toimialan asiantuntijoiden kanssa varmistaaksesi, että rajapinnat ovat valmiita tuotantoon.",
+  "cycle.api-productization-cycle.station.api-publishing.title": "API-julkaiseminen - Julkaise APIt luotettavasti",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Esittele APIt turvallisesti ja selkeästi oikealle yleisölle oikean dokumentaation ja prosessien avulla.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Julkaiseminen on muutakin kuin käyttöönottoa - kyse on löydettävyydestä, saatavuudesta ja tuesta. Jos rajapintoja ei julkaista oikein, niitä ei käytetä, käytetä uudelleen tai suojata tehokkaasti.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Mahdollistetaan APIen julkaiseminen asiaankuuluvassa ympäristössä ja selkeät rekisteröinti- ja käyttöoikeusmekanismit (esim. API-avaimet, OAuth, tilaussuunnitelmat) API-hyödyntäjäsegmenttien sekä turvallisuus- ja vaatimustenmukaisuusvaatimusten mukaan.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIt julkaistaan oikeassa ympäristössä (yksityinen, kumppani, julkinen).",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille rajapinnan käyttäjille.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Selkeät API-käyttöönotto- ja rekisteröintiprosessit",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Dokumentaatio, turvallisuusmallit ja -käytännöt saatavilla",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIt valmiina skaalautumiseen ja hallintaan",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaa, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Varmistetaan, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja kuluttajien saatavilla.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Seuranta ja parantaminen - API-arvoa varten",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API-kehitys ei lopu käynnistykseen. Ilman seurantaa tiimit eivät voi parantaa käyttöönottoa, suorituskykyä tai ROI",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Ota käyttöön analytiikkakehykset suorituskyvyn ja sitoutumisen seuraamiseksi. Kehitetään palautesilmukoita, analytiikkatyökaluja ja sitouttamisstrategioita API-rajapintoja varten.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Suorituskyvyn ja käytön mittarit määritellään ja niitä seurataan.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Kehittäjien palautekierrokset käytössä",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Jatkuvasti tunnistetut ja käsitellyt ongelmat",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "APIn iterointi käyttäjien tarpeiden mukaisesti",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia."
 }
diff --git a/src/data/method/fr/labels.resources.json b/src/data/method/fr/labels.resources.json
index 842b420..4ff3ab1 100644
--- a/src/data/method/fr/labels.resources.json
+++ b/src/data/method/fr/labels.resources.json
@@ -13,7 +13,7 @@
   "resource.api-development-best-practices.description": "Guide de mise en œuvre visant à transformer un contrat API validé en une base de code API cohérente et facile à maintenir, à l'aide de bibliothèques standard, de modèles réutilisables et de workflows de développement harmonisés.",
   "resource.api-development-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de développement d'API",
   "resource.api-development-best-practices.steps": "Appliquez ces bonnes pratiques au contrat API validé et au plan de mise en œuvre avant de commencer le codage.",
-  "resource.api-development-best-practices.tips": "Utilisez cette ressource comme guide de mise en œuvre et outil d'évaluation plutôt que comme un artefact autonome obligatoire", 
+  "resource.api-development-best-practices.tips": "Utilisez cette ressource comme guide de mise en œuvre et outil d'évaluation plutôt que comme un artefact autonome obligatoire",
   "resource.api-metrics-and-analytics.title": "Mesures et analyses de l'API",
   "resource.api-metrics-and-analytics.description": "Une ressource pour définir, collecter et analyser les performances de l'API et les données d'utilisation afin d'aligner les KPI techniques sur les résultats de l'entreprise.",
   "resource.api-metrics-and-analytics.outcomes": "Meilleure compréhension des métriques API et des principes d'analyse",
@@ -403,5 +403,40 @@
   "resource.rest-canvas.steps.2": "Spécifier les verbes HTTP utilisés pour interagir avec les ressources",
   "resource.rest-canvas.steps.3": "Fournir des exemples de demandes et de réponses pour chaque verbe",
   "resource.rest-canvas.tips.1": "Veiller à ce que les URI des ressources soient intuitifs et cohérents",
-  "resource.rest-canvas.tips.2": "gestion des erreurs de documents et codes de réponse"
+  "resource.rest-canvas.tips.2": "gestion des erreurs de documents et codes de réponse",
+  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
+  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
+  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
+  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
+  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
+  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
+  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
+  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
+  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
+  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
+  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
 }
diff --git a/src/data/method/fr/labels.stakeholders.json b/src/data/method/fr/labels.stakeholders.json
index ff8eb0d..e8a1c62 100644
--- a/src/data/method/fr/labels.stakeholders.json
+++ b/src/data/method/fr/labels.stakeholders.json
@@ -8,28 +8,42 @@
   "stakeholder.api-program-owner.description": "Coordonne les pratiques du portefeuille API, l'alignement organisationnel et le développement à long terme des capacités API.",
   "stakeholder.api-product-owner.title": "Propriétaire du produit API",
   "stakeholder.api-product-owner.description": "Piloter l'opportunité API, la priorisation et les décisions au niveau du produit tout au long du cycle de vie.",
-  "stakeholder.domain-expert.title": "Expert du domaine",
-  "stakeholder.domain-expert.description": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que l'API doit refléter.",
-  "stakeholder.customer-or-partner-representative.title": "Représentant client ou partenaire",
-  "stakeholder.customer-or-partner-representative.description": "Contribue à la perspective du client ou partenaire commercial pour le parcours, la valeur et le modèle de collaboration.",
-  "stakeholder.api-consumer-representative.title": "Représentant utilisateur API",
-  "stakeholder.api-consumer-representative.description": "Représente les besoins des développeurs, intégrateurs ou autres utilisateurs d'API qui utilisent l'API directement.",
+  "stakeholder.capability-owner.title": "Capability Owner",
+  "stakeholder.capability-owner.description": "",
+  "stakeholder.domain-specialist.title": "Expert du domaine",
+  "stakeholder.domain-specialist.description": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que l'API doit refléter.",
+  "stakeholder.customer-specialist.title": "Représentant client ou partenaire",
+  "stakeholder.customer-specialist.description": "Contribue à la perspective du client ou partenaire commercial pour le parcours, la valeur et le modèle de collaboration.",
+  "stakeholder.api-consumer-specialist.title": "Représentant utilisateur API",
+  "stakeholder.api-consumer-specialist.description": "Représente les besoins des développeurs, intégrateurs ou autres utilisateurs d'API qui utilisent l'API directement.",
   "stakeholder.platform-architect.title": "Architecte de la plateforme",
   "stakeholder.platform-architect.description": "Orienté les décisions sur la plateforme, l'intégration, l'évolutivité et l'architecture qui façonnent la construction et l'exploitation de l'API.",
+  "stakeholder.api-architect.title": "API Architect",
+  "stakeholder.api-architect.description": "",
+  "stakeholder.integration-architect.title": "Integration Architect",
+  "stakeholder.integration-architect.description": "",
+  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.description": "",
   "stakeholder.api-designer.title": "Designer API",
   "stakeholder.api-designer.description": "Conçoit le contrat API, le modèle d'interaction, la cohérence et l'utilisabilité des capacités exposées.",
-  "stakeholder.delivery-engineer.title": "Ingénieur de livraison",
-  "stakeholder.delivery-engineer.description": "Assume la responsabilité de l'implémentation, de l'automatisation, des tests et du flux de publication nécessaires pour livrer l'API de manière fiable.",
+  "stakeholder.api-engineer.title": "Ingénieur de livraison",
+  "stakeholder.api-engineer.description": "Assume la responsabilité de l'implémentation, de l'automatisation, des tests et du flux de publication nécessaires pour livrer l'API de manière fiable.",
+  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.automation-owner.description": "",
+  "stakeholder.process-owner.title": "Process Owner",
+  "stakeholder.process-owner.description": "",
+  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.description": "",
   "stakeholder.security-specialist.title": "Spécialiste en sécurité",
   "stakeholder.security-specialist.description": "Assure que les risques de sécurité, les contrôles et les limites de confiance sont pris en compte tout au long du cycle de vie de l'API.",
-  "stakeholder.compliance-legal-specialist.title": "Spécialiste en conformité et juridique",
-  "stakeholder.compliance-legal-specialist.description": "Clarifie les exigences légales, de confidentialité, réglementaires et contractuelles qui affectent l'API.",
-  "stakeholder.governance-owner.title": "Propriétaire de la gouvernance",
-  "stakeholder.governance-owner.description": "Représente les pratiques de revue, d'audit et de gouvernance à l'échelle de l'organisation pour la qualité et la conformité des API.",
-  "stakeholder.documentation-devrel-owner.title": "Propriétaire de la documentation et du développement communautaire",
-  "stakeholder.documentation-devrel-owner.description": "Possède le contenu d'intégration, la communication avec les développeurs et la qualité de la documentation pour les utilisateurs d'API.",
-  "stakeholder.support-operations-owner.title": "Propriétaire du support et des opérations",
-  "stakeholder.support-operations-owner.description": "Représente le support en production, la gestion des incidents, l'observabilité et la préparation opérationnelle.",
-  "stakeholder.partner-vendor-manager.title": "Gestionnaire de partenaires ou de fournisseurs",
-  "stakeholder.partner-vendor-manager.description": "Coordonne les relations avec les partenaires externes, les fournisseurs ou les vendeurs qui influencent la stratégie et la livraison de l'API."
+  "stakeholder.compliance-specialist.title": "Spécialiste en conformité et juridique",
+  "stakeholder.compliance-specialist.description": "Clarifie les exigences légales, de confidentialité, réglementaires et contractuelles qui affectent l'API.",
+  "stakeholder.governance-specialist.title": "Propriétaire de la gouvernance",
+  "stakeholder.governance-specialist.description": "Représente les pratiques de revue, d'audit et de gouvernance à l'échelle de l'organisation pour la qualité et la conformité des API.",
+  "stakeholder.api-devrel-specialist.title": "Propriétaire de la documentation et du développement communautaire",
+  "stakeholder.api-devrel-specialist.description": "Possède le contenu d'intégration, la communication avec les développeurs et la qualité de la documentation pour les utilisateurs d'API.",
+  "stakeholder.operations-specialist.title": "Propriétaire du support et des opérations",
+  "stakeholder.operations-specialist.description": "Représente le support en production, la gestion des incidents, l'observabilité et la préparation opérationnelle.",
+  "stakeholder.partner-specialist.title": "Gestionnaire de partenaires ou de fournisseurs",
+  "stakeholder.partner-specialist.description": "Coordonne les relations avec les partenaires externes, les fournisseurs ou les vendeurs qui influencent la stratégie et la livraison de l'API."
 }
diff --git a/src/data/method/fr/labels.stations.json b/src/data/method/fr/labels.stations.json
index f254579..48b3f9b 100644
--- a/src/data/method/fr/labels.stations.json
+++ b/src/data/method/fr/labels.stations.json
@@ -13,7 +13,7 @@
   "station.api-consumer-experience.description": "Veillez à ce que votre API soit découvrable, compréhensible et utilisable - avant et après le lancement.",
   "station.api-consumer-experience.why_it_matters": "Les meilleures API ne se contentent pas de fonctionner, elles sont intuitives. Que votre consommateur soit un développeur interne, un partenaire externe ou un agent d'intelligence artificielle, c'est son expérience qui détermine l'adoption.\n\nSans un plan d'expérience clair :\n- Les meilleures API restent inutilisées\n- Les équipes perdent du temps à deviner comment utiliser votre API.\n- Les boucles de rétroaction sont brisées ou manquantes.\n\nCette station vous aide à voir votre API à travers les yeux de ses consommateurs.",
   "station.api-consumer-experience.how_it_works": "Examinez l'API Value Proposition Canvas du point de vue de l'utilisateur. Veillez à la stabilité des tâches métier prises en charge et enrichissez les fonctionnalités qui simplifient et optimisent l'expérience utilisateur en intégrant les préoccupations des utilisateurs afin d'orienter les décisions de conception ultérieures.",
-  "station.api-consumer-experience.how_it_works.1":"Utilisez le canevas du parcours client pour le parcours de l'utilisateur de l'API, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
+  "station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur de l'API, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
   "station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur de l'API.",
   "station.api-consumer-experience.apply_in_work": "Fournir des lignes directrices, des outils et des mécanismes de retour d'information pour comprendre, analyser et améliorer l'expérience interne et externe des développeurs et des partenaires.",
   "station.api-consumer-experience.outcomes": "Identifier et hiérarchiser les consommateurs d'API",
@@ -34,7 +34,7 @@
   "station.api-delivery.why_it_matters": "Même les meilleures conceptions d'API échouent si la livraison est incohérente. Cette station garantit que vos API sont construites avec qualité, testées de manière approfondie et déployées de manière fiable, ce qui permet des itérations plus rapides et une plus grande confiance.",
   "station.api-delivery.apply_in_work": "Fournir des cadres de codage, des bibliothèques et des normes pour la mise en œuvre des API. Mettre en œuvre des pipelines CI/CD, des cadres d'assurance qualité et des outils d'automatisation du déploiement.",
   "station.api-delivery.outcomes": "API mises en œuvre à l'aide de cadres et de modèles testés",
-"station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
+  "station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
   "station.api-audit.title": "Audit API - Audit de conformité et de qualité des API",
   "station.api-audit.description": "Vérifiez que les API répondent aux normes métier, de conception et opérationnelles avant leur publication et leur mise à disposition.",
   "station.api-audit.why_it_matters": "Les API sont des produits à longue durée de vie et doivent répondre aux attentes en matière de qualité, de cohérence et de conformité. L'audit relie les décisions de conception, la mise en œuvre et l'état de préparation opérationnelle à des normes définies, réduisant ainsi les risques avant la mise à disposition.",
@@ -206,7 +206,7 @@
   "station.api-product-strategy.outcomes.1": "Un langage commun entre le produit, le design et la technologie",
   "station.api-product-strategy.outcomes.2": "Un argumentaire ou un dossier solide pour le financement/l'approbation",
   "station.api-product-strategy.how_it_works.1": "Définir les entités de base, leurs attributs et leurs relations pour créer une compréhension conceptuelle partagée à travers les parcours et éventuellement les API.",
-  "station.api-product-strategy.how_it_works.2":"Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur de l'API qui façonnent les API nouvelles ou réutilisables.",
+  "station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur de l'API qui façonnent les API nouvelles ou réutilisables.",
   "station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos consommateurs d'API à la prochaine station.",
   "station.api-consumer-experience.outcomes.1": "Définir le parcours de l'expérience API",
   "station.api-consumer-experience.outcomes.2": "Planifier l'intégration, la documentation et le retour d'information",
@@ -223,7 +223,7 @@
   "station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
   "station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
   "station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
-   "station.api-design.how_it_works.5": "Utiliser les principes de conception et le guide de style des API pour aligner vos décisions de conception sur des règles communes et permettre une validation d'audit cohérente.",
+  "station.api-design.how_it_works.5": "Utiliser les principes de conception et le guide de style des API pour aligner vos décisions de conception sur des règles communes et permettre une validation d'audit cohérente.",
   "station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou  « design-first » pour définir et valider le contrat de l'API avant sa mise en œuvre.",
   "station.api-design.how_it_works.7": "Utilisez la liste de contrôle d'audit des API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
   "station.api-delivery.outcomes.1": "Pipelines CI/CD fiables et automatisés",
@@ -373,5 +373,101 @@
   "station.budget-and-resource-management.outcomes.2": "Optimisation des investissements dans le développement et la gestion des API",
   "station.budget-and-resource-management.outcomes.3": "Amélioration de la visibilité financière et du contrôle des initiatives API",
   "station.budget-and-resource-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur commerciale, de l'impact et de l'alignement sur les initiatives stratégiques.",
-  "station.budget-and-resource-management.how_it_works.2": "Contrôler le budget et l'utilisation des ressources afin de garantir l'efficacité des investissements et de l'affectation des ressources pour les initiatives de l'API."
+  "station.budget-and-resource-management.how_it_works.2": "Contrôler le budget et l'utilisation des ressources afin de garantir l'efficacité des investissements et de l'affectation des ressources pour les initiatives de l'API.",
+  "cycle.api-productization-cycle.station.api-product-strategy.title": "Stratégie produit API - Transformer les API en produits stratégiques",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs commerciaux.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "De nombreuses organisations considèrent les API comme des projets technologiques et non comme des produits. Le résultat ? Des consommateurs désorientés, une adoption médiocre et un gaspillage d'efforts.\n\nCette station vous aide à définir l'objectif, le public cible et les critères de réussite de votre API, afin que les équipes puissent fournir des API qui résolvent des problèmes réels.",
+  "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Fournir des lignes directrices et des modèles pour la création de modèles commerciaux, de propositions de valeur et de feuilles de route pour les API.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Une proposition de valeur et un public simples pour l'API",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explorez le problème du client ou du partenaire que vous comptez résoudre avec les API. Dressez la carte des parties prenantes, de leurs parcours et de leurs résultats à l'aide du Customer Journey canvas.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Un langage commun entre le produit, le design et la technologie",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Un argumentaire ou un dossier solide pour le financement/l'approbation",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Définir les entités de base, leurs attributs et leurs relations pour créer une compréhension conceptuelle partagée à travers les parcours et éventuellement les API.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur de l'API qui façonnent les API nouvelles ou réutilisables.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos consommateurs d'API à la prochaine station.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Concevoir pour les vrais utilisateurs de votre API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Veillez à ce que votre API soit découvrable, compréhensible et utilisable - avant et après le lancement.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Les meilleures API ne se contentent pas de fonctionner, elles sont intuitives. Que votre consommateur soit un développeur interne, un partenaire externe ou un agent d'intelligence artificielle, c'est son expérience qui détermine l'adoption.\n\nSans un plan d'expérience clair :\n- Les meilleures API restent inutilisées\n- Les équipes perdent du temps à deviner comment utiliser votre API.\n- Les boucles de rétroaction sont brisées ou manquantes.\n\nCette station vous aide à voir votre API à travers les yeux de ses consommateurs.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Examinez l'API Value Proposition Canvas du point de vue de l'utilisateur. Veillez à la stabilité des tâches métier prises en charge et enrichissez les fonctionnalités qui simplifient et optimisent l'expérience utilisateur en intégrant les préoccupations des utilisateurs afin d'orienter les décisions de conception ultérieures.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur de l'API, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur de l'API.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Fournir des lignes directrices, des outils et des mécanismes de retour d'information pour comprendre, analyser et améliorer l'expérience interne et externe des développeurs et des partenaires.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifier et hiérarchiser les consommateurs d'API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Définir le parcours de l'expérience API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Planifier l'intégration, la documentation et le retour d'information",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Améliorer l'adoption grâce à une véritable empathie + l'expérience du développeur (DX)",
+  "cycle.api-productization-cycle.station.api-platform-architecture.title": "Architecture de la plateforme API - Architecturer les API pour l'évolutivité et la réutilisation",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Assurez l'évolutivité, la réutilisation et la gouvernance de vos composants d'API et de plateforme.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "Lorsque les API s'étendent à plusieurs équipes, votre plateforme doit permettre la gouvernance et la réutilisation sans bloquer la vitesse. Cette station montre comment architecturer les API pour assurer leur longévité, leur sécurité et leur efficacité.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Mettre en place une infrastructure évolutive, sécurisée et conforme pour les opérations API. Fournir des lignes directrices sur les meilleures pratiques en matière d'architecture.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Supprimer les API redondantes et réduire les coûts de la plateforme en nuage",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Le Business Impact Canvas permet d'identifier et d'atténuer les risques liés à la disponibilité, à la sécurité et à la fonctionnalité de l'API afin de prendre des décisions éclairées en matière d'architecture.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Mettre en œuvre une gouvernance cohérente sans contrôle descendant lourd",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Conception en vue d'une réutilisation interne et d'une évolutivité externe",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Cartographier les emplacements réglementaires, de conformité et de réseau des fournisseurs d'API et des consommateurs afin de garantir l'accessibilité et la conformité.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Le Capacity Canvas aligne les modèles de transactions commerciales, les tendances de consommation futures et les solutions techniques pour garantir l'évolutivité et les performances de l'API, et fournit des informations essentielles pour les décisions d'évolution et la planification de l'infrastructure.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Définir et surveiller les indicateurs de performance (par exemple, les appels API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
+  "cycle.api-productization-cycle.station.api-design.title": "Conception d'API - Concevoir des API qui apportent de la valeur",
+  "cycle.api-productization-cycle.station.api-design.description": "Créer des architectures d'API cohérentes, réutilisables et fondées sur les objectifs métier et des normes communes.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "La conception d'API ne se limite pas à nommer des points de terminaison. Une bonne conception garantit que les API sont utilisables, cohérentes et alignées sur les objectifs métier et techniques. Une mauvaise conception entraîne un couplage étroit, une faible réutilisation et des retouches coûteuses entre les équipes.",
+  "cycle.api-productization-cycle.station.api-design.apply_in_work": "Fournir des modèles de conception réutilisables, des normes communes et des outils de validation pour les spécifications d'API. S'assurer que les décisions de conception sont cohérentes, examinées dès le début et alignées sur les objectifs métier.",
+  "cycle.api-productization-cycle.station.api-design.outcomes": "Des conceptions d'API bien documentées et cohérentes",
+  "cycle.api-productization-cycle.station.api-design.how_it_works": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contrats d'API réutilisables et validés",
+  "cycle.api-productization-cycle.station.api-design.outcomes.2": "Conceptions alignées sur les modèles de domaine et les modèles d'interaction",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Traçabilité de la conception à la valeur commerciale",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Utilisez le canevas d'interaction pour définir la manière dont les consommateurs interagiront avec l'API, en veillant à ce qu'elle réponde à leurs besoins et à leurs attentes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Utiliser les principes de conception et le guide de style des API pour aligner vos décisions de conception sur des règles communes et permettre une validation d'audit cohérente.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou  « design-first » pour définir et valider le contrat de l'API avant sa mise en œuvre.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Utilisez la liste de contrôle d'audit des API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
+  "cycle.api-productization-cycle.station.api-delivery.title": "Livraison d'API - Fournir des API sécurisées et fiables",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Construire, tester et publier des API en utilisant des pipelines de livraison modernes et les meilleures pratiques d'ingénierie.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Même les meilleures conceptions d'API échouent si la livraison est incohérente. Cette station garantit que vos API sont construites avec qualité, testées de manière approfondie et déployées de manière fiable, ce qui permet des itérations plus rapides et une plus grande confiance.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fournir des cadres de codage, des bibliothèques et des normes pour la mise en œuvre des API. Mettre en œuvre des pipelines CI/CD, des cadres d'assurance qualité et des outils d'automatisation du déploiement.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes": "API mises en œuvre à l'aide de cadres et de modèles testés",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Pipelines CI/CD fiables et automatisés",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Tests fonctionnels et non fonctionnels intégrés",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Pipelines de livraison sécurisés et conformes",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construisez l'implémentation de l'API à partir du contrat validé en utilisant des frameworks, des bibliothèques et des normes d'équipe établis.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Tester les fonctionnalités, la sécurité et les performances des API à l'aide d'outils de test automatisés.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de déploiement, en garantissant une qualité et une traçabilité constantes.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "S'assurer que les API répondent aux exigences de sécurité et de conformité grâce à des contrôles et des audits automatisés.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Utilisez la liste de contrôle de l'audit de l'API pour vous assurer que l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
+  "cycle.api-productization-cycle.station.api-audit.title": "Audit API - Audit de conformité et de qualité des API",
+  "cycle.api-productization-cycle.station.api-audit.description": "Vérifiez que les API répondent aux normes métier, de conception et opérationnelles avant leur publication et leur mise à disposition.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "Les API sont des produits à longue durée de vie et doivent répondre aux attentes en matière de qualité, de cohérence et de conformité. L'audit relie les décisions de conception, la mise en œuvre et l'état de préparation opérationnelle à des normes définies, réduisant ainsi les risques avant la mise à disposition.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Mettez en place un processus d'audit cohérent qui évalue l'état de préparation des API à toutes les étapes du cycle de vie à l'aide de critères, de preuves et de normes définis. Assurez-vous que les lacunes sont identifiées tôt et résolues avant la publication.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "Les API sont conformes aux normes internes et externes",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Mener des audits pour s'assurer que les API respectent les normes organisationnelles, techniques et juridiques avant d'être publiées.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Documentation claire des décisions relatives à la conception et à la mise en œuvre de l'API",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Sécurité, performance et conformité validées",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Réduction du risque de problèmes en production",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Utiliser des listes de contrôle, des linters et des outils de test pour vérifier la cohérence et la conformité avec les normes.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Collaborer avec les équipes de gouvernance et les experts du domaine pour s'assurer que les API sont prêtes pour la production.",
+  "cycle.api-productization-cycle.station.api-publishing.title": "Publication d'API - Publier des API en toute confiance",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Exposer les API de manière sûre et claire au bon public avec la bonne documentation et les bons processus.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "La publication va plus loin que le déploiement - il s'agit de la découvrabilité, de l'accès et de l'assistance. Si les API ne sont pas publiées correctement, elles ne seront pas utilisées, réutilisées ou sécurisées efficacement.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permettre aux API d'être publiées dans l'environnement approprié et disposer de mécanismes d'enregistrement et d'accès clairs (par exemple, clés API, OAuth, plans d'abonnement) en fonction des segments de consommateurs d'API et des exigences en matière de sécurité et de conformité.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes": "API publiées dans le bon environnement (privé, partenaire, public)",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publier les API dans les passerelles et les environnements appropriés afin de favoriser la réutilisation pour de multiples consommateurs d'API.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Des processus clairs d'intégration et d'enregistrement de l'API",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentation, modèles de sécurité et politiques disponibles",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "Des API prêtes pour l'échelle et la gouvernance",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Documenter la manière dont les consommateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Veiller à ce que les modèles de sécurité, la configuration de la passerelle et les termes juridiques soient clairs et accessibles aux consommateurs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Suivi et amélioration - pour la valeur de l'API",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Utiliser les mesures et le retour d'information pour suivre les performances de l'API et favoriser l'amélioration continue.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "La livraison d'API ne s'arrête pas au lancement. Sans surveillance, les équipes ne peuvent pas améliorer l'adoption, les performances ou le retour sur investissement. Cette station garantit que les API restent utiles, sécurisées et qu'elles évoluent avec les besoins de l'entreprise.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Mettre en place des cadres d'analyse pour suivre les performances et l'engagement. Développer des boucles de rétroaction, des outils d'analyse et des stratégies d'engagement pour les API.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Définition et suivi des indicateurs de performance et d'utilisation",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Contrôler les indicateurs de performance (par exemple, les appels à l'API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Boucles de rétroaction des développeurs en place",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Questions identifiées et traitées en permanence",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "Itération de l'API alignée sur les besoins des utilisateurs",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyser les indicateurs d'utilisation de l'API et intégrer les commentaires des utilisateurs dans les itérations de l'API.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Prendre l'habitude d'examiner les mesures et de planifier des activités d'amélioration continue."
 }
diff --git a/src/data/method/lines.json b/src/data/method/lines.json
index e6b0c43..3e7df9e 100644
--- a/src/data/method/lines.json
+++ b/src/data/method/lines.json
@@ -107,4 +107,4 @@
       }
     ]
   }
-}
\ No newline at end of file
+}
diff --git a/src/data/method/pt/labels.resources.json b/src/data/method/pt/labels.resources.json
index ef876d4..43855da 100644
--- a/src/data/method/pt/labels.resources.json
+++ b/src/data/method/pt/labels.resources.json
@@ -28,7 +28,7 @@
   "resource.api-development-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-development-best-practices.steps": "Aplique essas práticas ao contrato de API validado e ao plano de implementação antes do início da codificação.",
   "resource.api-development-best-practices.steps.1": "Use frameworks, bibliotecas e padrões de codificação estabelecidos para implementar o contrato de forma consistente e sustentável.",
-  "resource.api-development-best-practices.tips": "Use este recurso como orientação de implementação e lente de revisão, em vez de como um artefato independente obrigatório", 
+  "resource.api-development-best-practices.tips": "Use este recurso como orientação de implementação e lente de revisão, em vez de como um artefato independente obrigatório",
   "resource.api-development-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.api-metrics-and-analytics.title": "Métricas e análises de API",
   "resource.api-metrics-and-analytics.description": "Um recurso para definir, recolher e analisar o desempenho da API e os dados de utilização para alinhar os KPIs técnicos com os resultados comerciais.",
@@ -403,5 +403,40 @@
   "resource.rest-canvas.steps.3": "Fornecer exemplos de pedidos e respostas para cada verbo",
   "resource.rest-canvas.tips": "Utilizar métodos HTTP padrão (GET, POST, PUT, DELETE)",
   "resource.rest-canvas.tips.1": "Assegurar que os URIs dos recursos são intuitivos e coerentes",
-  "resource.rest-canvas.tips.2": "tratamento de erros de documentos e códigos de resposta"
+  "resource.rest-canvas.tips.2": "tratamento de erros de documentos e códigos de resposta",
+  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
+  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
+  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
+  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
+  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
+  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
+  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
+  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
+  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
+  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
+  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
 }
diff --git a/src/data/method/pt/labels.stakeholders.json b/src/data/method/pt/labels.stakeholders.json
index 7edce82..8f27a7d 100644
--- a/src/data/method/pt/labels.stakeholders.json
+++ b/src/data/method/pt/labels.stakeholders.json
@@ -8,28 +8,42 @@
   "stakeholder.api-program-owner.description": "Coordena as práticas de portfólio API, alinhamento organizacional e desenvolvimento de capacidades API de longo prazo.",
   "stakeholder.api-product-owner.title": "Proprietário do Produto API",
   "stakeholder.api-product-owner.description": "Impulsiona a oportunidade API, priorização e decisões de nível de produto ao longo do ciclo de vida.",
-  "stakeholder.domain-expert.title": "Especialista em Domínio",
-  "stakeholder.domain-expert.description": "Trás conhecimento profundo do domínio de negócios, conceitos, regras e restrições que a API deve refletir.",
-  "stakeholder.customer-or-partner-representative.title": "Representante do Cliente ou Parceiro",
-  "stakeholder.customer-or-partner-representative.description": "Contribui com a perspectiva do cliente ou parceiro de negócios para o percurso, valor e modelo de colaboração.",
-  "stakeholder.api-consumer-representative.title": "Representante do Consumidor API",
-  "stakeholder.api-consumer-representative.description": "Representa as necessidades dos desenvolvedores, integradores ou outros consumidores da API que utilizam a API diretamente.",
+  "stakeholder.capability-owner.title": "Capability Owner",
+  "stakeholder.capability-owner.description": "",
+  "stakeholder.domain-specialist.title": "Especialista em Domínio",
+  "stakeholder.domain-specialist.description": "Trás conhecimento profundo do domínio de negócios, conceitos, regras e restrições que a API deve refletir.",
+  "stakeholder.customer-specialist.title": "Representante do Cliente ou Parceiro",
+  "stakeholder.customer-specialist.description": "Contribui com a perspectiva do cliente ou parceiro de negócios para o percurso, valor e modelo de colaboração.",
+  "stakeholder.api-consumer-specialist.title": "Representante do Consumidor API",
+  "stakeholder.api-consumer-specialist.description": "Representa as necessidades dos desenvolvedores, integradores ou outros consumidores da API que utilizam a API diretamente.",
   "stakeholder.platform-architect.title": "Arquiteto da Plataforma",
   "stakeholder.platform-architect.description": "Orienta decisões sobre a plataforma, integração, escalabilidade e arquitetura que moldam como a API é construída e operada.",
+  "stakeholder.api-architect.title": "API Architect",
+  "stakeholder.api-architect.description": "",
+  "stakeholder.integration-architect.title": "Integration Architect",
+  "stakeholder.integration-architect.description": "",
+  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.description": "",
   "stakeholder.api-designer.title": "Designer API",
   "stakeholder.api-designer.description": "Modela o contrato API, o modelo de interação, a consistência e a usabilidade das capacidades expostas.",
-  "stakeholder.delivery-engineer.title": "Engenheiro de Entrega",
-  "stakeholder.delivery-engineer.description": "Responsável por implementação, automação, testes e preocupações de fluxo de lançamento necessárias para entregar a API de forma confiável.",
+  "stakeholder.api-engineer.title": "Engenheiro de Entrega",
+  "stakeholder.api-engineer.description": "Responsável por implementação, automação, testes e preocupações de fluxo de lançamento necessárias para entregar a API de forma confiável.",
+  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.automation-owner.description": "",
+  "stakeholder.process-owner.title": "Process Owner",
+  "stakeholder.process-owner.description": "",
+  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.description": "",
   "stakeholder.security-specialist.title": "Especialista em Segurança",
   "stakeholder.security-specialist.description": "Garante que os riscos de segurança, controles e limites de confiança sejam abordados ao longo do ciclo de vida da API.",
-  "stakeholder.compliance-legal-specialist.title": "Especialista em Conformidade e Legal",
-  "stakeholder.compliance-legal-specialist.description": "Esclarece os requisitos legais, de privacidade, regulatórios e contratuais que afetam a API.",
-  "stakeholder.governance-owner.title": "Proprietário da Governança",
-  "stakeholder.governance-owner.description": "Representa práticas de revisão, auditoria e governança em toda a organização para qualidade e conformidade das APIs.",
-  "stakeholder.documentation-devrel-owner.title": "Proprietário da Documentação e Desenvolvimento Comunitário",
-  "stakeholder.documentation-devrel-owner.description": "Possui o conteúdo de integração, a comunicação com os desenvolvedores e a qualidade da documentação para os usuários da API.",
-  "stakeholder.support-operations-owner.title": "Proprietário do Suporte e Operações",
-  "stakeholder.support-operations-owner.description": "Representa o suporte em tempo de execução, o tratamento de incidentes, a observabilidade e a prontidão operacional.",
-  "stakeholder.partner-vendor-manager.title": "Gerente de Parceiros ou Fornecedores",
-  "stakeholder.partner-vendor-manager.description": "Coordena as relações com parceiros externos, fornecedores ou vendedores que influenciam a estratégia e a entrega da API."
+  "stakeholder.compliance-specialist.title": "Especialista em Conformidade e Legal",
+  "stakeholder.compliance-specialist.description": "Esclarece os requisitos legais, de privacidade, regulatórios e contratuais que afetam a API.",
+  "stakeholder.governance-specialist.title": "Proprietário da Governança",
+  "stakeholder.governance-specialist.description": "Representa práticas de revisão, auditoria e governança em toda a organização para qualidade e conformidade das APIs.",
+  "stakeholder.api-devrel-specialist.title": "Proprietário da Documentação e Desenvolvimento Comunitário",
+  "stakeholder.api-devrel-specialist.description": "Possui o conteúdo de integração, a comunicação com os desenvolvedores e a qualidade da documentação para os usuários da API.",
+  "stakeholder.operations-specialist.title": "Proprietário do Suporte e Operações",
+  "stakeholder.operations-specialist.description": "Representa o suporte em tempo de execução, o tratamento de incidentes, a observabilidade e a prontidão operacional.",
+  "stakeholder.partner-specialist.title": "Gerente de Parceiros ou Fornecedores",
+  "stakeholder.partner-specialist.description": "Coordena as relações com parceiros externos, fornecedores ou vendedores que influenciam a estratégia e a entrega da API."
 }
diff --git a/src/data/method/pt/labels.stations.json b/src/data/method/pt/labels.stations.json
index 91984de..2ff34c5 100644
--- a/src/data/method/pt/labels.stations.json
+++ b/src/data/method/pt/labels.stations.json
@@ -373,5 +373,101 @@
   "station.budget-and-resource-management.outcomes.3": "Melhoria da visibilidade financeira e do controlo das iniciativas API",
   "station.budget-and-resource-management.how_it_works": "Definir práticas de gestão orçamental e de recursos que descrevam os processos de gestão de orçamentos e recursos para iniciativas de API.",
   "station.budget-and-resource-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor comercial, no impacto e no alinhamento com as iniciativas estratégicas.",
-  "station.budget-and-resource-management.how_it_works.2": "Controlar o orçamento e a utilização dos recursos para garantir investimentos eficazes e a afetação de recursos às iniciativas da API."
+  "station.budget-and-resource-management.how_it_works.2": "Controlar o orçamento e a utilização dos recursos para garantir investimentos eficazes e a afetação de recursos às iniciativas da API.",
+  "cycle.api-productization-cycle.station.api-product-strategy.title": "Estratégia de produtos API - Transforme APIs em produtos estratégicos",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objectivos comerciais desde o primeiro dia.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projectos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
+  "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Fornecer diretrizes e modelos para a criação de modelos comerciais, propostas de valor e roteiros de API.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Uma proposta de valor e um público-alvo da API simples",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Linguagem partilhada entre o produto, o design e a tecnologia",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Um argumento sólido ou um caso para financiamento/aprovação",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore o problema do cliente ou parceiro que espera resolver com as APIs. Mapeie as partes interessadas, os seus percursos e os resultados utilizando a tela do Percurso do Cliente.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Definir as entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre jornadas e, eventualmente, APIs.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use o API Value Proposition Canvas para capturar as tarefas de negócios suportadas e as dores, ganhos e recursos do consumidor da API que moldam APIs novas ou reutilizáveis.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Defina o valor - para os utilizadores e para a empresa - com a tela do modelo de negócio da API para tornar a sua estratégia de API visual, partilhável e fácil de validar com os seus consumidores de API na estação seguinte.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "Experiência do consumidor da API - Design para os utilizadores reais da sua API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Certifique-se de que a sua API é detetável, compreensível e utilizável - antes e depois do lançamento.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "As APIs excelentes não funcionam apenas - elas são intuitivas. Quer o consumidor seja um programador interno, um parceiro externo ou um agente de IA, a sua experiência determina a adoção.\n\nSem um plano de experiência claro:\n- Grandes APIs ficam sem uso\n- As equipas perdem tempo a tentar adivinhar como utilizar a sua API\n- Os ciclos de feedback estão quebrados ou ausentes.\n\nEsta estação ajuda-o a ver a sua API através dos olhos dos seus consumidores.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Analise o API Value Proposition Canvas existente sob a perspectiva do consumidor da API. Mantenha as tarefas de negócios suportadas estáveis ​​e enriqueça os recursos que aliviam problemas e possibilitam ganhos com as preocupações do consumidor da API, para que elas possam orientar as decisões de design futuras.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use o Customer Journey Canvas para a jornada do consumidor da API, desde a descoberta e avaliação até a integração, resolução de problemas e uso contínuo.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use a jornada resultante para melhorar a integração, a documentação, o suporte e os ciclos de feedback para o consumidor da API.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Fornecer diretrizes, ferramentas e mecanismos de feedback para compreender, analisar e melhorar a experiência interna e externa dos programadores e parceiros.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifique e dê prioridade aos seus consumidores de API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Definir o percurso da experiência API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Planeamento da integração, documentação e feedback",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Melhorar a adoção através de empatia genuína + Experiência do Programador (DX)",
+  "cycle.api-productization-cycle.station.api-platform-architecture.title": "Arquitetura da plataforma API - Arquitetar APIs para escalabilidade e reutilização",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Garanta a escalabilidade, a reutilização e a governação da sua API e dos componentes da plataforma.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "Quando as APIs são escalonadas entre equipas, a sua plataforma deve permitir a governação e a reutilização sem bloquear a velocidade. Esta estação mostra como arquitetar APIs para longevidade, segurança e eficiência.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Estabelecer uma infraestrutura escalável, segura e compatível com as operações de API. Fornecer orientações sobre as melhores práticas de arquitetura.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Corte APIs redundantes e reduza os custos da plataforma de nuvem",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implementar uma governação consistente sem um forte controlo do topo para a base",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Conceção para reutilização interna e escalabilidade externa",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "O Business Impact Canvas ajuda a identificar e mitigar os riscos relacionados com a disponibilidade, segurança e funcionalidade da API para apoiar decisões de arquitetura informadas.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Mapear as localizações regulamentares, de conformidade e de rede dos fornecedores e consumidores de API para garantir a acessibilidade e a conformidade.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "O Capacity Canvas alinha os padrões das transacções comerciais, as tendências de consumo futuro e as soluções técnicas para garantir a escalabilidade e o desempenho da API, fornecendo dados essenciais para as decisões de escalabilidade e o planeamento da infraestrutura.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "cycle.api-productization-cycle.station.api-design.title": "Conceção da API - Conceber APIs que proporcionem valor",
+  "cycle.api-productization-cycle.station.api-design.description": "Criar projetos de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "Projetar APIs não se resume apenas a nomear endpoints. Um bom projeto garante que as APIs sejam utilizáveis, consistentes e alinhadas com os objetivos comerciais e técnicos. Um projeto inadequado leva a um acoplamento rígido, baixa reutilização e retrabalho dispendioso entre as equipes.",
+  "cycle.api-productization-cycle.station.api-design.apply_in_work": "Forneça padrões de projeto reutilizáveis, padrões compartilhados e ferramentas de validação para especificações de API. Garanta que as decisões de projeto sejam consistentes, revisadas antecipadamente e alinhadas com a intenção de negócios.",
+  "cycle.api-productization-cycle.station.api-design.outcomes": "Conceção de API bem documentada e coerente",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contratos API reutilizáveis e validados",
+  "cycle.api-productization-cycle.station.api-design.outcomes.2": "Desenhos alinhados com modelos de domínio e padrões de interação",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Rastreabilidade da conceção ao valor comercial",
+  "cycle.api-productization-cycle.station.api-design.how_it_works": "Definir entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre APIs.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Utilize o Canvas de Interação para definir a forma como os consumidores irão interagir com a API, garantindo que esta satisfaz as suas necessidades e expectativas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Aplicar padrões de conceção REST para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Aplicar padrões de conceção orientados para eventos para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Aplicar padrões de design GraphQL para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Use os princípios de projeto e o guia de estilo de API para alinhar suas decisões de projeto com regras compartilhadas e permitir uma validação de auditoria consistente.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Aplique abordagens do tipo ‘contrato primeiro’ ou ‘design primeiro’ para capturar e validar o contrato da API antes da implementação.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use a Lista de Verificação de Auditoria da API para garantir que o design da API atenda aos requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "cycle.api-productization-cycle.station.api-delivery.title": "Entrega da API - Fornecer APIs seguras e fiáveis",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e práticas recomendadas de engenharia.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Mesmo os melhores projectos de API falham se a entrega for inconsistente. Esta estação assegura que as suas APIs são construídas com qualidade, testadas exaustivamente e implementadas de forma fiável - permitindo iterações mais rápidas e maior confiança.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fornecer estruturas de codificação, bibliotecas e normas para a implementação de API. Implementar pipelines de CI/CD, estruturas de garantia de qualidade e ferramentas de automatização da implantação.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implementadas utilizando estruturas e padrões testados",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Pipelines de CI/CD fiáveis e automatizados",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Testes funcionais e não funcionais integrados",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Condutas de entrega seguras e conformes",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Use as Melhores Práticas de Desenvolvimento de API como orientação para implementar o contrato validado com frameworks e bibliotecas estabelecidos, garantindo que o resultado seja reutilizável e sustentável.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construa a implementação da API a partir do contrato validado usando frameworks, bibliotecas e padrões da equipe estabelecidos.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testar a funcionalidade, a segurança e o desempenho das API, utilizando ferramentas de teste automatizadas.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Utilize pipelines CI/CD para automatizar os processos de construção, teste e implementação, garantindo uma qualidade e rastreabilidade consistentes.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Garantir que as APIs cumprem os requisitos de segurança e conformidade através de verificações e auditorias automatizadas.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Utilize a lista de verificação de auditoria da API para garantir que a API cumpre os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "cycle.api-productization-cycle.station.api-audit.title": "Auditoria de API - Auditoria de APIs para conformidade e qualidade",
+  "cycle.api-productization-cycle.station.api-audit.description": "Valide se as APIs atendem aos padrões de negócios, design e operacionais antes da publicação e exposição.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "As APIs são produtos de longa duração e devem atender às expectativas de qualidade, consistência e conformidade. A auditoria conecta as decisões de design, a implementação e a prontidão operacional a padrões definidos, reduzindo o risco antes da exposição.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Estabeleça um processo de auditoria consistente que avalie a prontidão da API em todas as etapas do ciclo de vida usando critérios, evidências e padrões definidos. Garanta que as lacunas sejam identificadas antecipadamente e resolvidas antes da publicação.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "As APIs cumprem as normas internas e externas",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Documentação clara das decisões de conceção e implementação da API",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Segurança, desempenho e conformidade validados",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Redução do risco de problemas na produção",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Realizar auditorias para garantir que as APIs cumprem as normas organizacionais, técnicas e legais antes da publicação.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Utilizar listas de controlo, linters e ferramentas de teste para verificar a consistência e a conformidade com as normas.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Colaborar com as equipas de governação e especialistas no domínio para garantir que as API estão prontas para produção.",
+  "cycle.api-productization-cycle.station.api-publishing.title": "Publicação de API - Publique APIs com confiança",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Exponha as APIs de forma segura e clara ao público certo com a documentação e os processos corretos.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "A publicação é mais do que a implantação - trata-se de capacidade de descoberta, acesso e suporte. Se as APIs não forem publicadas corretamente, não serão utilizadas, reutilizadas ou protegidas de forma eficaz.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permitir que as API sejam publicadas no ambiente relevante e ter mecanismos claros de registo e acesso (por exemplo, chaves de API, OAuth, planos de subscrição), dependendo dos segmentos de consumidores de API e dos requisitos de segurança e conformidade.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs publicadas no ambiente correto (privado, parceiro, público)",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Processos claros de integração e registo da API",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentação, modelos e políticas de segurança disponíveis",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs prontas para escala e governação",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publicar APIs nos gateways e ambientes adequados para apoiar a reutilização por vários consumidores de API.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Documentar a forma como os consumidores encontram e utilizam a API, incluindo processos de integração e registo.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Garantir que os modelos de segurança, a configuração da porta de ligação e os termos legais sejam claros e acessíveis aos consumidores.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Monitorização e melhoria - para valor API",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Utilizar métricas e feedback para acompanhar o desempenho da API e promover a melhoria contínua.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "A entrega da API não pára no lançamento. Sem monitorização, as equipas não podem melhorar a adoção, o desempenho ou o ROI. Esta estação garante que as APIs permaneçam úteis, seguras e evoluindo com as necessidades do negócio.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Criar quadros analíticos para acompanhar o desempenho e o envolvimento. Desenvolver ciclos de feedback, ferramentas de análise e estratégias de envolvimento para APIs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Métricas de desempenho e utilização definidas e controladas",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Ciclos de feedback do programador em vigor",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Questões identificadas e tratadas continuamente",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "Iteração da API alinhada com as necessidades dos utilizadores",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua."
 }
diff --git a/src/data/method/resources.json b/src/data/method/resources.json
index 72cafb8..b85c152 100644
--- a/src/data/method/resources.json
+++ b/src/data/method/resources.json
@@ -1044,6 +1044,89 @@
         ]
       },
       "category": "canvas"
+    },
+    {
+      "id": "capabilityValuePropositionCanvas",
+      "title": "resource.capability-value-proposition-canvas.title",
+      "slug": "resources/capability-value-proposition-canvas",
+      "icon": "dashboard-outline",
+      "order": 2.1,
+      "description": "resource.capability-value-proposition-canvas.description",
+      "canvas": "capabilityValuePropositionCanvas",
+      "outcomes": [
+        "resource.capability-value-proposition-canvas.outcomes",
+        "resource.capability-value-proposition-canvas.outcomes.1",
+        "resource.capability-value-proposition-canvas.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.capability-value-proposition-canvas.steps",
+          "resource.capability-value-proposition-canvas.steps.1",
+          "resource.capability-value-proposition-canvas.steps.2",
+          "resource.capability-value-proposition-canvas.steps.3"
+        ],
+        "tips": [
+          "resource.capability-value-proposition-canvas.tips",
+          "resource.capability-value-proposition-canvas.tips.1"
+        ]
+      },
+      "category": "canvas"
+    },
+    {
+      "id": "capabilityBusinessModelCanvas",
+      "title": "resource.capability-business-model-canvas.title",
+      "slug": "resources/capability-business-model-canvas",
+      "icon": "dashboard-outline",
+      "order": 3.1,
+      "description": "resource.capability-business-model-canvas.description",
+      "canvas": "capabilityBusinessModelCanvas",
+      "outcomes": [
+        "resource.capability-business-model-canvas.outcomes",
+        "resource.capability-business-model-canvas.outcomes.1",
+        "resource.capability-business-model-canvas.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.capability-business-model-canvas.steps",
+          "resource.capability-business-model-canvas.steps.1",
+          "resource.capability-business-model-canvas.steps.2",
+          "resource.capability-business-model-canvas.steps.3",
+          "resource.capability-business-model-canvas.steps.4",
+          "resource.capability-business-model-canvas.steps.5"
+        ],
+        "tips": [
+          "resource.capability-business-model-canvas.tips",
+          "resource.capability-business-model-canvas.tips.1"
+        ]
+      },
+      "category": "canvas"
+    },
+    {
+      "id": "consumerExperienceRequirementsCanvas",
+      "title": "resource.consumer-experience-requirements-canvas.title",
+      "slug": "resources/consumer-experience-requirements-canvas",
+      "icon": "dashboard-outline",
+      "order": 3.2,
+      "description": "resource.consumer-experience-requirements-canvas.description",
+      "canvas": "consumerExperienceRequirementsCanvas",
+      "outcomes": [
+        "resource.consumer-experience-requirements-canvas.outcomes",
+        "resource.consumer-experience-requirements-canvas.outcomes.1",
+        "resource.consumer-experience-requirements-canvas.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.consumer-experience-requirements-canvas.steps",
+          "resource.consumer-experience-requirements-canvas.steps.1",
+          "resource.consumer-experience-requirements-canvas.steps.2",
+          "resource.consumer-experience-requirements-canvas.steps.3"
+        ],
+        "tips": [
+          "resource.consumer-experience-requirements-canvas.tips",
+          "resource.consumer-experience-requirements-canvas.tips.1"
+        ]
+      },
+      "category": "canvas"
     }
   ]
 }
diff --git a/src/data/method/stakeholders.json b/src/data/method/stakeholders.json
index 0ff6739..e55eef5 100644
--- a/src/data/method/stakeholders.json
+++ b/src/data/method/stakeholders.json
@@ -16,34 +16,69 @@
       "description": "stakeholder.api-product-owner.description"
     },
     {
-      "id": "domain-expert",
-      "title": "stakeholder.domain-expert.title",
-      "description": "stakeholder.domain-expert.description"
+      "id": "capability-owner",
+      "title": "stakeholder.capability-owner.title",
+      "description": "stakeholder.capability-owner.description"
     },
     {
-      "id": "customer-or-partner-representative",
-      "title": "stakeholder.customer-or-partner-representative.title",
-      "description": "stakeholder.customer-or-partner-representative.description"
+      "id": "domain-specialist",
+      "title": "stakeholder.domain-specialist.title",
+      "description": "stakeholder.domain-specialist.description"
     },
     {
-      "id": "api-consumer-representative",
-      "title": "stakeholder.api-consumer-representative.title",
-      "description": "stakeholder.api-consumer-representative.description"
+      "id": "customer-specialist",
+      "title": "stakeholder.customer-specialist.title",
+      "description": "stakeholder.customer-specialist.description"
+    },
+    {
+      "id": "api-consumer-specialist",
+      "title": "stakeholder.api-consumer-specialist.title",
+      "description": "stakeholder.api-consumer-specialist.description"
     },
     {
       "id": "platform-architect",
       "title": "stakeholder.platform-architect.title",
       "description": "stakeholder.platform-architect.description"
     },
+    {
+      "id": "api-architect",
+      "title": "stakeholder.api-architect.title",
+      "description": "stakeholder.api-architect.description"
+    },
+    {
+      "id": "integration-architect",
+      "title": "stakeholder.integration-architect.title",
+      "description": "stakeholder.integration-architect.description"
+    },
+    {
+      "id": "platform-owner",
+      "title": "stakeholder.platform-owner.title",
+      "description": "stakeholder.platform-owner.description"
+    },
     {
       "id": "api-designer",
       "title": "stakeholder.api-designer.title",
       "description": "stakeholder.api-designer.description"
     },
     {
-      "id": "delivery-engineer",
-      "title": "stakeholder.delivery-engineer.title",
-      "description": "stakeholder.delivery-engineer.description"
+      "id": "api-engineer",
+      "title": "stakeholder.api-engineer.title",
+      "description": "stakeholder.api-engineer.description"
+    },
+    {
+      "id": "automation-owner",
+      "title": "stakeholder.automation-owner.title",
+      "description": "stakeholder.automation-owner.description"
+    },
+    {
+      "id": "process-owner",
+      "title": "stakeholder.process-owner.title",
+      "description": "stakeholder.process-owner.description"
+    },
+    {
+      "id": "automation-engineer",
+      "title": "stakeholder.automation-engineer.title",
+      "description": "stakeholder.automation-engineer.description"
     },
     {
       "id": "security-specialist",
@@ -51,29 +86,29 @@
       "description": "stakeholder.security-specialist.description"
     },
     {
-      "id": "compliance-legal-specialist",
-      "title": "stakeholder.compliance-legal-specialist.title",
-      "description": "stakeholder.compliance-legal-specialist.description"
+      "id": "compliance-specialist",
+      "title": "stakeholder.compliance-specialist.title",
+      "description": "stakeholder.compliance-specialist.description"
     },
     {
-      "id": "governance-owner",
-      "title": "stakeholder.governance-owner.title",
-      "description": "stakeholder.governance-owner.description"
+      "id": "governance-specialist",
+      "title": "stakeholder.governance-specialist.title",
+      "description": "stakeholder.governance-specialist.description"
     },
     {
-      "id": "documentation-devrel-owner",
-      "title": "stakeholder.documentation-devrel-owner.title",
-      "description": "stakeholder.documentation-devrel-owner.description"
+      "id": "api-devrel-specialist",
+      "title": "stakeholder.api-devrel-specialist.title",
+      "description": "stakeholder.api-devrel-specialist.description"
     },
     {
-      "id": "support-operations-owner",
-      "title": "stakeholder.support-operations-owner.title",
-      "description": "stakeholder.support-operations-owner.description"
+      "id": "operations-specialist",
+      "title": "stakeholder.operations-specialist.title",
+      "description": "stakeholder.operations-specialist.description"
     },
     {
-      "id": "partner-vendor-manager",
-      "title": "stakeholder.partner-vendor-manager.title",
-      "description": "stakeholder.partner-vendor-manager.description"
+      "id": "partner-specialist",
+      "title": "stakeholder.partner-specialist.title",
+      "description": "stakeholder.partner-specialist.description"
     }
   ]
 }
diff --git a/src/data/method/station-stakeholders.json b/src/data/method/station-stakeholders.json
index f806c78..4c34d47 100644
--- a/src/data/method/station-stakeholders.json
+++ b/src/data/method/station-stakeholders.json
@@ -1,1044 +1,1250 @@
 {
-  "api-product-strategy": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "customer-or-partner-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    }
-  ],
-  "api-consumer-experience": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "consulted"
-    }
-  ],
-  "api-platform-architecture": [
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "api-design": [
-    {
-      "stakeholder": "api-designer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "api-delivery": [
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "api-audit": [
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "api-publishing": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "monitoring-and-improving": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    }
-  ],
-  "user-experience": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "customer-or-partner-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "market-insights": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "customer-or-partner-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "consulted"
-    }
-  ],
-  "business-goals": [
-    {
-      "stakeholder": "business-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "competitive-analysis": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "customer-or-partner-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "ecosystem-vision": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "customer-or-partner-representative",
-      "involvement": "consulted"
-    }
-  ],
-  "scalable-infrastructure": [
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "legal-and-compliance": [
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "security-and-privacy": [
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "design-standards": [
-    {
-      "stakeholder": "api-designer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "vendor-management": [
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "contract-design": [
-    {
-      "stakeholder": "api-designer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    }
-  ],
-  "development": [
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    }
-  ],
-  "ci-cd": [
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "test-automation": [
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "release-management": [
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "service-agreements": [
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "consulted"
-    }
-  ],
-  "api-consumer-adoption": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "consulted"
-    }
-  ],
-  "api-promotion": [
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-consumer-representative",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "partner-integration": [
-    {
-      "stakeholder": "partner-vendor-manager",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "api-mindset": [
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "domain-expert",
-      "involvement": "consulted"
-    }
-  ],
-  "roles-and-responsibilities": [
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "upskilling": [
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-designer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "business-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "operating-guidelines": [
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "security-specialist",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "compliance-legal-specialist",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "portfolio-management": [
-    {
-      "stakeholder": "business-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "documentation-devrel-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
-    }
-  ],
-  "budget-and-resource-management": [
-    {
-      "stakeholder": "business-owner",
-      "involvement": "lead"
-    },
-    {
-      "stakeholder": "api-program-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "api-product-owner",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "delivery-engineer",
-      "involvement": "core"
-    },
-    {
-      "stakeholder": "platform-architect",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "governance-owner",
-      "involvement": "consulted"
-    },
-    {
-      "stakeholder": "support-operations-owner",
-      "involvement": "consulted"
+  "stationStakeholdersByCycle": {
+    "capability-productization-cycle": {
+      "api-product-strategy": [
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "lead",
+          "responsibilities": [
+            {
+              "resource": "capabilityValuePropositionCanvas",
+              "role": "suggested-answer-owner"
+            },
+            {
+              "resource": "capabilityBusinessModelCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "customerJourneyCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "domainCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "customer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-program-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-consumer-experience": [
+        {
+          "stakeholder": "customer-specialist",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "consumerExperienceRequirementsCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-platform-architecture": [
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "lead",
+          "responsibilities": [
+            {
+              "resource": "locationsCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "businessImpactCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "capacityCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "consulted"
+        }
+      ],
+      "api-design": [
+        {
+          "stakeholder": "api-designer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-delivery": [
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-audit": [
+        {
+          "stakeholder": "governance-specialist",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-publishing": [
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "partner-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "monitoring-and-improving": [
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ]
+    },
+    "api-productization-cycle": {
+      "api-product-strategy": [
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "lead",
+          "responsibilities": [
+            {
+              "resource": "apiValuePropositionCanvas",
+              "role": "suggested-answer-owner"
+            },
+            {
+              "resource": "apiBusinessModelCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "customerJourneyCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "domainCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "customer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        }
+      ],
+      "api-consumer-experience": [
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "consulted"
+        }
+      ],
+      "api-platform-architecture": [
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "businessImpactCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "api-architect",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "locationsCanvas",
+              "role": "suggested-answer-owner"
+            },
+            {
+              "resource": "capacityCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "api-design": [
+        {
+          "stakeholder": "api-designer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "api-delivery": [
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "api-audit": [
+        {
+          "stakeholder": "governance-specialist",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "api-publishing": [
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "monitoring-and-improving": [
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "consulted"
+        }
+      ]
+    },
+    "integration-productization-cycle": {
+      "api-product-strategy": [
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "customerJourneyCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "domainCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "capability-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "capabilityValuePropositionCanvas",
+              "role": "suggested-answer-owner"
+            },
+            {
+              "resource": "capabilityBusinessModelCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-product-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "partner-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-consumer-experience": [
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "lead",
+          "responsibilities": [
+            {
+              "resource": "consumerExperienceRequirementsCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "customer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "partner-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-platform-architecture": [
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "lead",
+          "responsibilities": [
+            {
+              "resource": "locationsCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "businessImpactCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "capacityCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        }
+      ],
+      "api-design": [
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-delivery": [
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "partner-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-audit": [
+        {
+          "stakeholder": "governance-specialist",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "api-publishing": [
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "partner-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        }
+      ],
+      "monitoring-and-improving": [
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ]
+    },
+    "automation-cycle": {
+      "api-product-strategy": [
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "customerJourneyCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "domainCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-consumer-experience": [
+        {
+          "stakeholder": "process-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "customer-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-consumer-specialist",
+          "involvement": "consulted",
+          "responsibilities": [
+            {
+              "resource": "consumerExperienceRequirementsCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-platform-architecture": [
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "consulted"
+        }
+      ],
+      "api-design": [
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "integration-architect",
+          "involvement": "core",
+          "responsibilities": [
+            {
+              "resource": "interactionCanvas",
+              "role": "suggested-answer-owner"
+            }
+          ]
+        },
+        {
+          "stakeholder": "domain-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-designer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-delivery": [
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "api-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "api-audit": [
+        {
+          "stakeholder": "governance-specialist",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-architect",
+          "involvement": "consulted"
+        }
+      ],
+      "api-publishing": [
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "api-devrel-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ],
+      "monitoring-and-improving": [
+        {
+          "stakeholder": "automation-owner",
+          "involvement": "lead"
+        },
+        {
+          "stakeholder": "process-owner",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "operations-specialist",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "automation-engineer",
+          "involvement": "core"
+        },
+        {
+          "stakeholder": "business-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "platform-owner",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "security-specialist",
+          "involvement": "consulted"
+        },
+        {
+          "stakeholder": "compliance-specialist",
+          "involvement": "consulted"
+        }
+      ]
     }
-  ]
-}
+  }
+}
\ No newline at end of file
diff --git a/src/lib/method-engine.js b/src/lib/method-engine.js
index 8a03f9b..e9cc8ce 100644
--- a/src/lib/method-engine.js
+++ b/src/lib/method-engine.js
@@ -73,6 +73,35 @@ export const CANVAS_SECTION_NOTE_INTENTS = Object.freeze({
     painRelievingFeatures: "benefit",
     apiProducts: "neutral"
   },
+  capabilityValuePropositionCanvas: {
+    consumerTasks: "task",
+    gainEnablingCapabilities: "benefit",
+    painRelievingCapabilities: "benefit",
+    reusableCapabilities: "neutral"
+  },
+  capabilityBusinessModelCanvas: {
+    keyPartners: "neutral",
+    keyActivities: "task",
+    keyResources: "neutral",
+    capabilityValueProposition: "benefit",
+    consumerEngagement: "neutral",
+    channels: "task",
+    capabilityConsumerSegments: "neutral",
+    costs: "negative",
+    benefits: "benefit"
+  },
+  consumerExperienceRequirementsCanvas: {
+    consumerGoals: "benefit",
+    availabilityAndTimeliness: "neutral",
+    volumeAndPerformance: "neutral",
+    dataQualityAndConsistency: "neutral",
+    securityPrivacyAndCompliance: "negative",
+    onboardingAndAccess: "task",
+    changeAndVersioning: "negative",
+    observabilityAndSupport: "task",
+    recoveryAndContinuity: "task",
+    architectureImplications: "neutral"
+  },
   businessImpactCanvas: {
     availabilityRisks: "negative",
     securityRisks: "negative",
@@ -237,10 +266,8 @@ export function getCoreStations() {
 
 export function getStations() {
   const stations = readJson(resolveMethodFile("stations.json"));
-  return [
-    ...((stations["core-stations"] && stations["core-stations"].items) || []),
-    ...((stations["sub-stations"] && stations["sub-stations"].items) || [])
-  ]
+  return Object.values(stations)
+    .flatMap((group) => group.items || [])
     .slice()
     .sort((left, right) => left.order - right.order);
 }
@@ -280,6 +307,10 @@ export function getStationCriteriaMap() {
   return readJson(resolveMethodFile("station-criteria.json"));
 }
 
+export function getCriteria() {
+  return readJson(resolveMethodFile("criteria.json"));
+}
+
 export function getStakeholders() {
   return readJson(resolveMethodFile("stakeholders.json")).stakeholders || [];
 }
@@ -292,6 +323,23 @@ export function getResources() {
   return readJson(resolveMethodFile("resources.json")).resources || [];
 }
 
+export function getLines() {
+  return readJson(resolveMethodFile("lines.json")).lines?.items || [];
+}
+
+export function getCycles() {
+  return readJson(resolveMethodFile("cycles.json")).cycles?.items || [];
+}
+
+export function getCycle(cycleId) {
+  const normalizedCycleId = String(cycleId || "").trim();
+  const cycle = getCycles().find((entry) => entry.id === normalizedCycleId || entry.slug === normalizedCycleId);
+  if (!cycle) {
+    throw new Error(`Unknown cycle: ${cycleId}`);
+  }
+  return cycle;
+}
+
 export function normalizeResourceId(resourceId) {
   const normalized = String(resourceId || "").trim();
   return LEGACY_CANVAS_RESOURCE_ALIASES.get(normalized) || normalized;
@@ -707,6 +755,168 @@ export function getCanvasCreatorUrl(canvasId, locale = DEFAULT_LOCALE) {
   return `${CANVAS_CREATOR_BASE_URL}?canvas=${encodeURIComponent(canvasId)}&locale=${encodeURIComponent(locale)}`;
 }
 
+function formatMarkdownCell(value) {
+  return String(value || "")
+    .replace(/\r?\n/g, " ")
+    .trim();
+}
+
+function formatGuidanceList(values) {
+  return values
+    .map((value) => formatMarkdownCell(value).replace(/[.;:]+$/g, ""))
+    .filter(Boolean)
+    .join("; ");
+}
+
+function isPlaceholderExampleNote(content) {
+  const normalized = String(content || "").trim().replace(/\s+/g, " ");
+  return !normalized ||
+    /^placeholder$/i.test(normalized) ||
+    /^double-click on text to edit\. click and select color$/i.test(normalized);
+}
+
+function formatExampleNotes(notes) {
+  return (notes || [])
+    .map((note) => String(note.content || "").trim())
+    .filter((content) => !isPlaceholderExampleNote(content))
+    .join("; ");
+}
+
+function formatExampleAnswer(value) {
+  const text = formatMarkdownCell(value);
+  return text ? `_Example: ${text}_` : "";
+}
+
+function renderConfluencePasteTableRow(values) {
+  return `| ${values.map((value) => formatMarkdownCell(value)).join(" | ")} |`;
+}
+
+function renderConfluenceWikiHeaderRow(values) {
+  return `|| ${values.map((value) => formatMarkdownCell(value)).join(" || ")} ||`;
+}
+
+function renderConfluenceWikiRow(values) {
+  return `| ${values.map((value) => formatMarkdownCell(value)).join(" | ")} |`;
+}
+
+function buildStationCanvasGroups(canvasRows) {
+  const groups = [];
+  const groupsByStation = new Map();
+
+  for (const row of canvasRows) {
+    const stationKey = row.stationTitle || "Requirements";
+    let group = groupsByStation.get(stationKey);
+    if (!group) {
+      group = {
+        stationTitle: stationKey,
+        stationDescription: row.stationDescription || "",
+        stationWhyItMatters: row.stationWhyItMatters || "",
+        canvasRows: []
+      };
+      groupsByStation.set(stationKey, group);
+      groups.push(group);
+    }
+
+    group.canvasRows.push(row);
+  }
+
+  return groups;
+}
+
+function findCanvasResource(canvasId) {
+  return getResources().find((resource) => resource.canvas === canvasId) || null;
+}
+
+function findCanvasStationContext(canvasId, resourceId, stationPath, stationOverlays) {
+  const overlay = stationOverlays.find((entry) => {
+    const reuse = entry.reuse || [];
+    const alternatives = entry.alternativeResources || [];
+    return reuse.includes(canvasId) ||
+      reuse.includes(resourceId) ||
+      alternatives.includes(canvasId) ||
+      alternatives.includes(resourceId);
+  });
+
+  if (!overlay) {
+    return null;
+  }
+
+  return stationPath.find((station) => station.id === overlay.station) || null;
+}
+
+function getDocumentCanvasStationContext(canvasId, resourceId, extension, stationPath) {
+  const explicitStationId = extension.documentCanvasStations?.[canvasId] || extension.documentCanvasStations?.[resourceId];
+  if (explicitStationId) {
+    return stationPath.find((station) => station.id === explicitStationId) || null;
+  }
+
+  return findCanvasStationContext(canvasId, resourceId, stationPath, extension.stationOverlays || []);
+}
+
+function findStationInstruction(stationId, resourceId, locale) {
+  if (!stationId || !resourceId) {
+    return "";
+  }
+
+  const stationLabels = getLocalizedLabels(locale, "stations");
+  const station = getStations().find((entry) => entry.id === stationId);
+  const step = getStationSteps(station || {}).find((entry) => normalizeResourceId(entry.resource) === resourceId);
+  return step ? translate(step.step, stationLabels) : "";
+}
+
+function normalizeDocumentText(value) {
+  return String(value || "");
+}
+
+function getCanvasExampleAnswers(canvasId) {
+  const templatesDir = resolveCanvasFile("import-export-templates");
+  if (!fs.existsSync(templatesDir)) {
+    return new Map();
+  }
+
+  const examplesBySection = new Map();
+  const files = fs.readdirSync(templatesDir)
+    .filter((fileName) => fileName.endsWith(".json"))
+    .map((fileName) => path.join(templatesDir, fileName));
+
+  for (const filePath of files) {
+    const template = readJson(filePath);
+    if (template.templateId !== canvasId) {
+      continue;
+    }
+
+    for (const section of template.sections || []) {
+      const exampleAnswer = formatExampleNotes(section.stickyNotes);
+      if (!exampleAnswer) {
+        continue;
+      }
+
+      const existing = examplesBySection.get(section.sectionId);
+      examplesBySection.set(
+        section.sectionId,
+        existing ? `${existing}; ${exampleAnswer}` : exampleAnswer
+      );
+    }
+  }
+
+  return examplesBySection;
+}
+
+function buildCriteriaMetadata(criteriaIds, locale) {
+  const criteriaLabels = getLocalizedLabels(locale, "criteria");
+  const criteriaById = new Map(getCriteria().map((criterion) => [criterion.id, criterion]));
+  return (criteriaIds || [])
+    .map((criterionId) => {
+      const criterion = criteriaById.get(criterionId);
+      return criterion ? {
+        id: criterion.id,
+        title: translate(`criterion.${criterion.id}`, criteriaLabels),
+        description: criterion.description
+      } : null;
+    })
+    .filter(Boolean);
+}
+
 export function resolveStationIds(options = {}) {
   if (options.station) {
     return [options.station];
diff --git a/src/schemas/cycles.schema.json b/src/schemas/cycles.schema.json
new file mode 100644
index 0000000..1048f4d
--- /dev/null
+++ b/src/schemas/cycles.schema.json
@@ -0,0 +1,84 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "required": ["cycles"],
+  "additionalProperties": false,
+  "properties": {
+    "cycles": {
+      "type": "object",
+      "required": ["title", "slug", "order", "description", "items"],
+      "additionalProperties": false,
+      "properties": {
+        "title": { "type": "string" },
+        "slug": { "type": "string" },
+        "order": { "type": "number" },
+        "description": { "type": "string" },
+        "items": {
+          "type": "array",
+          "minItems": 1,
+          "items": { "$ref": "#/definitions/cycle" }
+        }
+      }
+    }
+  },
+  "definitions": {
+    "cycle": {
+      "type": "object",
+      "required": ["id", "title", "slug", "description", "audiences", "purpose", "stations"],
+      "additionalProperties": false,
+      "properties": {
+        "id": { "type": "string" },
+        "title": { "type": "string" },
+        "slug": { "type": "string" },
+        "description": { "type": "string" },
+        "audiences": {
+          "type": "array",
+          "minItems": 1,
+          "items": { "type": "string" }
+        },
+        "purpose": { "type": "string" },
+        "stations": {
+          "type": "array",
+          "minItems": 1,
+          "items": { "type": "string" }
+        },
+        "stationLabels": {
+          "type": "object",
+          "additionalProperties": { "type": "string" }
+        },
+        "stationDescriptions": {
+          "type": "object",
+          "additionalProperties": { "type": "string" }
+        },
+        "recommendedResources": {
+          "type": "object",
+          "additionalProperties": {
+            "type": "array",
+            "items": { "type": "string" }
+          }
+        },
+        "overlays": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "required": ["station", "assistance", "humanValidation"],
+            "additionalProperties": false,
+            "properties": {
+              "station": { "type": "string" },
+              "assistance": { "type": "string" },
+              "humanValidation": { "type": "string" }
+            }
+          }
+        },
+        "entryCriteria": {
+          "type": "array",
+          "items": { "type": "string" }
+        },
+        "exitCriteria": {
+          "type": "array",
+          "items": { "type": "string" }
+        }
+      }
+    }
+  }
+}
diff --git a/src/schemas/stations.schema.json b/src/schemas/stations.schema.json
index 4859a78..626a9f8 100644
--- a/src/schemas/stations.schema.json
+++ b/src/schemas/stations.schema.json
@@ -40,6 +40,30 @@
                 "type": "array",
                 "items": {"type": "string"}
               },
+              "type": {"type": "string"},
+              "applicableCycles": {
+                "type": "array",
+                "items": {"type": "string"}
+              },
+              "defaultForCycles": {
+                "type": "array",
+                "items": {"type": "string"}
+              },
+              "cycleSpecificLabels": {
+                "type": "object",
+                "additionalProperties": {"type": "string"}
+              },
+              "cycleSpecificDescriptions": {
+                "type": "object",
+                "additionalProperties": {"type": "string"}
+              },
+              "cycleSpecificResources": {
+                "type": "object",
+                "additionalProperties": {
+                  "type": "array",
+                  "items": {"type": "string"}
+                }
+              },
               "how_it_works": {
                 "type": "array",
                 "items": {
@@ -60,6 +84,14 @@
       }
     },
     "sub-stations": {
+      "$ref": "#/definitions/stationGroup"
+    },
+    "integration-stations": {
+      "$ref": "#/definitions/stationGroup"
+    }
+  },
+  "definitions": {
+    "stationGroup": {
       "type": "object",
       "required": ["title", "slug", "order", "description", "items"],
       "additionalProperties": false,
@@ -95,6 +127,30 @@
                 "type": "array",
                 "items": {"type": "string"}
               },
+              "type": {"type": "string"},
+              "applicableCycles": {
+                "type": "array",
+                "items": {"type": "string"}
+              },
+              "defaultForCycles": {
+                "type": "array",
+                "items": {"type": "string"}
+              },
+              "cycleSpecificLabels": {
+                "type": "object",
+                "additionalProperties": {"type": "string"}
+              },
+              "cycleSpecificDescriptions": {
+                "type": "object",
+                "additionalProperties": {"type": "string"}
+              },
+              "cycleSpecificResources": {
+                "type": "object",
+                "additionalProperties": {
+                  "type": "array",
+                  "items": {"type": "string"}
+                }
+              },
               "how_it_works": {
                 "type": "array",
                 "items": {

From f72f6ce15598bd60ee7c5056e9966472f1ab52cf Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Tue, 7 Jul 2026 12:00:24 +0300
Subject: [PATCH 04/12] improved support for cycles in create-apiops and cli

---
 README.md                                     |   10 +-
 packages/create-apiops/README.md              |    5 +-
 .../bin/create-apiops-project.js              |   26 +-
 packages/create-apiops/bin/method-cli.js      |   26 +-
 packages/create-apiops/template/README.md     |    5 +-
 packages/create-apiops/template/package.json  |   14 +-
 .../template/scripts/get-core-stations.js     |    9 +-
 .../template/scripts/get-station-resources.js |    8 +-
 scripts/test-method-content-integrity.mjs     |   23 +-
 scripts/test-method-stakeholders.mjs          |   92 +-
 src/data/method/en/labels.stations.json       | 1517 +++++++----------
 src/lib/method-engine.js                      |  141 +-
 src/schemas/cycles.schema.json                |    2 +-
 src/schemas/station-stakeholders.schema.json  |   42 +-
 14 files changed, 862 insertions(+), 1058 deletions(-)

diff --git a/README.md b/README.md
index b8f826e..f1da9d2 100644
--- a/README.md
+++ b/README.md
@@ -15,7 +15,7 @@ npm create apiops@latest report-conversion-apiops
 Non-interactive scaffold:
 
 ```bash
-npm create apiops@latest -- --name report-conversion-apiops --locale en --style REST --yes
+npm create apiops@latest -- --name report-conversion-apiops --locale en --cycle api-productization-cycle --style REST --yes
 ```
 
 When using `npm create`, pass initializer flags after the `--` separator. Flags before the separator are handled by npm itself and may not reach `create-apiops`.
@@ -30,6 +30,7 @@ Useful options:
 
 - `--name <name>` or the first positional argument sets the project directory and package name
 - `--locale <locale>` sets the default method locale, such as `en` or `fi`
+- `--cycle <cycle-id>` sets the APIOps cycle used for station labels, stakeholders, and recommended resources; default: `api-productization-cycle`
 - `--style <style>` sets the API style focus: `REST`, `Event`, `GraphQL`, or `"Not sure yet"`
 - `--yes` accepts defaults for omitted options and runs without prompts; use it in non-interactive shells when any prompt answer is omitted
 - `--no-install` skips dependency installation and starter canvas generation
@@ -88,7 +89,8 @@ The `snippet-engine` export resolves canonical resource snippets, including loca
 The method also includes reusable stakeholder data:
 
 - `src/data/method/stakeholders.json` defines the shared stakeholder catalog
-- `src/data/method/station-stakeholders.json` maps each station to weighted stakeholder participation
+- `src/data/method/cycles.json` defines APIOps cycles that reuse canonical core station ids while providing cycle-specific station labels, descriptions, and recommended resources
+- `src/data/method/station-stakeholders.json` maps cycle ids to station-specific stakeholder participation and optional responsibilities
 - `src/data/method/<locale>/labels.stakeholders.json` stores localized stakeholder titles, descriptions, and involvement labels
 
 Stakeholder involvement uses three lightweight levels:
@@ -136,11 +138,11 @@ If you spot a problem in the documentation or have an idea for new content, open
 
 ### Editing or adding content
 
-The main method content files are located under `src/data/method/`. These base files (`lines.json`, `stations.json`, `resources.json`, `criteria.json`, `station-criteria.json`, `stakeholders.json`, and `station-stakeholders.json`) are not localized and live at the root of the folder. Textual values in them reference label keys. English labels are in `src/data/method/en`, and translations are provided in locale folders through `labels.lines.json`, `labels.stations.json`, `labels.resources.json`, `labels.criteria.json`, and `labels.stakeholders.json`.
+The main method content files are located under `src/data/method/`. These base files (`lines.json`, `cycles.json`, `stations.json`, `resources.json`, `criteria.json`, `station-criteria.json`, `stakeholders.json`, and `station-stakeholders.json`) are not localized and live at the root of the folder. Textual values in them reference label keys. English labels are in `src/data/method/en`, and translations are provided in locale folders through `labels.lines.json`, `labels.cycles.json`, `labels.stations.json`, `labels.resources.json`, `labels.criteria.json`, and `labels.stakeholders.json`.
 
 Some longer or more complex resources also use canonical snippet assets under `src/snippets/` linked from `resources.json`. Those snippets are now primarily structured JSON or YAML files, with Markdown kept only where a resource genuinely needs prose content.
 
-Each station links to specific entry criteria followed by the next core station's criteria as exit criteria. Stakeholder participation is modeled separately through `stakeholders.json`, `station-stakeholders.json`, and `labels.stakeholders.json`.
+Each station links to specific entry criteria followed by the next core station's criteria as exit criteria. Cycles in `cycles.json` reuse canonical station ids and can override the displayed station label, station description, and recommended resources for that cycle. Stakeholder participation is modeled separately through `stakeholders.json`, cycle-scoped mappings in `station-stakeholders.json`, and `labels.stakeholders.json`.
 
 #### Editing existing method pages
 
diff --git a/packages/create-apiops/README.md b/packages/create-apiops/README.md
index bf87580..9c9ad07 100644
--- a/packages/create-apiops/README.md
+++ b/packages/create-apiops/README.md
@@ -19,13 +19,13 @@ npm create apiops@latest report-conversion-apiops
 Non-interactive scaffold:
 
 ```bash
-npm create apiops@latest -- --name report-conversion-apiops --locale en --style REST --yes
+npm create apiops@latest -- --name report-conversion-apiops --locale en --cycle api-productization-cycle --style REST --yes
 ```
 
 Skip dependency installation:
 
 ```bash
-npm create apiops@latest -- report-conversion-apiops --locale en --style REST --yes --no-install
+npm create apiops@latest -- report-conversion-apiops --locale en --cycle api-productization-cycle --style REST --yes --no-install
 ```
 
 ## npm create argument forwarding
@@ -55,6 +55,7 @@ npx create-apiops@latest --help
 
 - `--name <name>` or the first positional argument sets the project directory and package name.
 - `--locale <locale>` sets the default method locale. Default: `en`.
+- `--cycle <cycle-id>` sets the APIOps cycle for station labels, stakeholders, and recommended resources. Default: `api-productization-cycle`.
 - `--style <style>` sets the API style focus: `REST`, `Event`, `GraphQL`, or `"Not sure yet"`. Default: `REST`.
 - `--yes`, `-y` accepts defaults for omitted options and runs without prompts. Use it in non-interactive shells when any prompt answer is omitted.
 - `--no-install` skips dependency installation and starter canvas generation.
diff --git a/packages/create-apiops/bin/create-apiops-project.js b/packages/create-apiops/bin/create-apiops-project.js
index 1c3da9e..1a81e70 100644
--- a/packages/create-apiops/bin/create-apiops-project.js
+++ b/packages/create-apiops/bin/create-apiops-project.js
@@ -12,6 +12,7 @@ const templateDir = path.resolve(__dirname, "..", "template");
 const DEFAULTS = {
   name: "my-api-project",
   locale: "en",
+  cycle: "api-productization-cycle",
   style: "REST",
   install: true
 };
@@ -23,6 +24,7 @@ function parseArgs(argv) {
     yes: false,
     name: undefined,
     locale: undefined,
+    cycle: undefined,
     style: undefined,
     install: undefined,
     errors: []
@@ -77,6 +79,12 @@ function parseArgs(argv) {
       i = result.nextIndex;
       continue;
     }
+    if (arg === "--cycle" || arg.startsWith("--cycle=")) {
+      const result = readValue(arg, "cycle", i);
+      args.cycle = result.value;
+      i = result.nextIndex;
+      continue;
+    }
     if (arg === "--style" || arg.startsWith("--style=")) {
       const result = readValue(arg, "style", i);
       args.style = result.value;
@@ -119,6 +127,7 @@ Usage:
 Options:
   --name <name>        Project directory and package name. Same as project-name.
   --locale <locale>    Default locale for generated method commands. Default: ${DEFAULTS.locale}
+  --cycle <cycle-id>   APIOps cycle for station labels and resources. Default: ${DEFAULTS.cycle}
   --style <style>      API style focus: REST, Event, GraphQL, or "Not sure yet". Default: ${DEFAULTS.style}
   --yes, -y            Accept defaults for omitted options and run without prompts.
                       Use this in non-interactive shells when any prompt answer is omitted.
@@ -129,8 +138,8 @@ Options:
 Examples:
   npm create apiops@latest
   npm create apiops@latest my-api
-  npm create apiops@latest -- --name my-api --locale en --style REST --yes
-  npm create apiops@latest -- my-api --locale en --style REST --yes --no-install
+  npm create apiops@latest -- --name my-api --locale en --cycle api-productization-cycle --style REST --yes
+  npm create apiops@latest -- my-api --locale en --cycle api-productization-cycle --style REST --yes --no-install
 `);
 }
 
@@ -198,7 +207,7 @@ function runCommand(command, args, options = {}) {
 }
 
 function hasCompleteNonInteractiveConfig(args) {
-  return args.name && args.locale && args.style && args.install !== undefined;
+  return args.name && args.locale && args.cycle && args.style && args.install !== undefined;
 }
 
 async function getScaffoldConfig() {
@@ -223,6 +232,7 @@ async function getScaffoldConfig() {
   const initial = {
     projectName: args.name || DEFAULTS.name,
     locale: args.locale || DEFAULTS.locale,
+    cycle: args.cycle || DEFAULTS.cycle,
     apiStyle: normalizeStyle(args.style || DEFAULTS.style),
     installNow: args.install === undefined ? DEFAULTS.install : args.install
   };
@@ -233,8 +243,8 @@ async function getScaffoldConfig() {
 
   if (!process.stdin.isTTY || !process.stdout.isTTY) {
     console.error("create-apiops cannot prompt because stdin or stdout is not interactive.");
-    console.error("Pass --yes to accept defaults for omitted options. To skip --yes, pass --name, --locale, --style, and --no-install.");
-    console.error("Example: npm create apiops@latest -- --name my-api --locale en --style REST --yes");
+    console.error("Pass --yes to accept defaults for omitted options. To skip --yes, pass --name, --locale, --cycle, --style, and --no-install.");
+    console.error("Example: npm create apiops@latest -- --name my-api --locale en --cycle api-productization-cycle --style REST --yes");
     process.exit(1);
   }
 
@@ -245,6 +255,7 @@ async function getScaffoldConfig() {
 
   const projectName = args.name || await ask(rl, "Project name", initial.projectName);
   const locale = args.locale || await ask(rl, "Default locale", initial.locale);
+  const cycle = args.cycle || await ask(rl, "APIOps cycle", initial.cycle);
   const apiStyle = normalizeStyle(args.style || await ask(rl, "API style focus [REST/Event/GraphQL/Not sure yet]", initial.apiStyle));
   const installAnswer = args.install === undefined
     ? await ask(rl, "Install dependencies now? [yes/no]", initial.installNow ? "yes" : "no")
@@ -254,13 +265,14 @@ async function getScaffoldConfig() {
   return {
     projectName,
     locale,
+    cycle,
     apiStyle,
     installNow: installAnswer.toLowerCase() === "yes"
   };
 }
 
 async function main() {
-  const { projectName, locale, apiStyle, installNow } = await getScaffoldConfig();
+  const { projectName, locale, cycle, apiStyle, installNow } = await getScaffoldConfig();
 
   const targetDir = path.resolve(process.cwd(), projectName);
   if (fs.existsSync(targetDir)) {
@@ -273,6 +285,7 @@ async function main() {
   const replacements = {
     "__PROJECT_NAME__": projectName,
     "__LOCALE__": locale,
+    "__CYCLE__": cycle,
     "__API_TITLE__": projectName.replace(/[-_]/g, " "),
     "__API_STYLE__": apiStyle
   };
@@ -300,6 +313,7 @@ async function main() {
         "./node_modules/apiops-cycles-method-data/bin/method-cli.js",
         "generate-canvases",
         "--preset", "new-api",
+        "--cycle", cycle,
         "--style", apiStyle,
         "--locale", locale,
         "--output", "./specs/canvases"
diff --git a/packages/create-apiops/bin/method-cli.js b/packages/create-apiops/bin/method-cli.js
index c3f8033..c3e74fc 100644
--- a/packages/create-apiops/bin/method-cli.js
+++ b/packages/create-apiops/bin/method-cli.js
@@ -21,16 +21,17 @@ const STATION_SCRIPT_HINTS = {
 
 function printUsage() {
   console.log(`Usage:
-  node packages/create-apiops/bin/method-cli.js start [--locale <locale>] [--default-locale <locale>] [--json] [--list] [--answers <yes,no,...>] [--next-action <resources|canvases|exit>]
-  node packages/create-apiops/bin/method-cli.js resources --station <station-id> [--locale <locale>] [--style <style>] [--json] [--list] [--step-actions <details,next,...>]
-  node packages/create-apiops/bin/method-cli.js generate-canvases [--station <station-id> | --stations <ids> | --preset new-api] [--locale <locale>] [--style <style>] [--output <dir>] [--force] [--json]
+  node packages/create-apiops/bin/method-cli.js start [--cycle <cycle-id>] [--locale <locale>] [--default-locale <locale>] [--json] [--list] [--answers <yes,no,...>] [--next-action <resources|canvases|exit>]
+  node packages/create-apiops/bin/method-cli.js resources --station <station-id> [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--json] [--list] [--step-actions <details,next,...>]
+  node packages/create-apiops/bin/method-cli.js generate-canvases [--station <station-id> | --stations <ids> | --preset new-api] [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--output <dir>] [--force] [--json]
 
 Examples:
   node packages/create-apiops/bin/method-cli.js start --locale en
+  node packages/create-apiops/bin/method-cli.js start --cycle api-productization-cycle --locale en
   node packages/create-apiops/bin/method-cli.js start --default-locale en
   node packages/create-apiops/bin/method-cli.js start --locale en --answers yes,no,yes --next-action resources
-  node packages/create-apiops/bin/method-cli.js resources --station api-product-strategy --locale en
-  node packages/create-apiops/bin/method-cli.js generate-canvases --preset new-api --style REST --output ./specs/canvases
+  node packages/create-apiops/bin/method-cli.js resources --station api-product-strategy --cycle api-productization-cycle --locale en
+  node packages/create-apiops/bin/method-cli.js generate-canvases --preset new-api --cycle api-productization-cycle --style REST --output ./specs/canvases
 `);
 }
 
@@ -95,6 +96,10 @@ function getNextStepHints(stationId) {
   };
 }
 
+function getCycleId(options = {}) {
+  return options.cycle || methodEngine.DEFAULT_CYCLE_ID;
+}
+
 function loadCanvasJson(filePath, canvasId, locale) {
   if (fs.existsSync(filePath)) {
     return readJson(filePath);
@@ -530,7 +535,8 @@ async function runInteractiveStart(data, options) {
     await runInteractiveResources({
       station: result.recommendedStation.id,
       locale: options.locale || methodEngine.DEFAULT_LOCALE,
-      style: options.style || methodEngine.DEFAULT_STYLE
+      style: options.style || methodEngine.DEFAULT_STYLE,
+      cycle: getCycleId(options)
     });
     return;
   }
@@ -540,6 +546,7 @@ async function runInteractiveStart(data, options) {
       station: result.recommendedStation.id,
       locale: options.locale || methodEngine.DEFAULT_LOCALE,
       style: options.style || methodEngine.DEFAULT_STYLE,
+      cycle: getCycleId(options),
       output: methodEngine.DEFAULT_OUTPUT_DIR
     });
     printGeneratedCanvasText(generateResult);
@@ -578,7 +585,7 @@ async function runInteractiveResources(options) {
   const locale = options.locale || methodEngine.DEFAULT_LOCALE;
   const style = methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE);
   const output = options.output || methodEngine.DEFAULT_OUTPUT_DIR;
-  const data = methodEngine.buildStationResourceData(options.station, locale, style);
+  const data = methodEngine.buildStationResourceData(options.station, locale, style, getCycleId(options));
   const scriptedActions = (options["step-actions"] || "")
     .split(",")
     .map((entry) => entry.trim())
@@ -734,7 +741,7 @@ export async function main() {
 
   if (command === "start") {
     const locale = await maybePromptForStartLocale(options);
-    const data = methodEngine.buildStartData(locale);
+    const data = methodEngine.buildStartData(locale, getCycleId(options));
     if (options.json) {
       console.log(JSON.stringify(data, null, 2));
       return;
@@ -757,7 +764,8 @@ export async function main() {
     const data = methodEngine.buildStationResourceData(
       options.station,
       options.locale || methodEngine.DEFAULT_LOCALE,
-      methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE)
+      methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE),
+      getCycleId(options)
     );
     if (options.json) {
       console.log(JSON.stringify(data, null, 2));
diff --git a/packages/create-apiops/template/README.md b/packages/create-apiops/template/README.md
index 248ae79..58ed25f 100644
--- a/packages/create-apiops/template/README.md
+++ b/packages/create-apiops/template/README.md
@@ -68,7 +68,7 @@ Treat `specs/` as the source of truth and `docs/` as generated or review materia
 npm run method:start
 npm run method:resources:strategy
 npm run method:canvases:new-api
-npm run method -- resources --station api-design --style "__API_STYLE__"
+npm run method -- resources --station api-design --cycle "__CYCLE__" --style "__API_STYLE__"
 npm run method:stations
 npm run method:resource:audit
 npm run lint:openapi
@@ -80,7 +80,7 @@ npm run audit:design:full-crud
 ## How to use it
 
 - Use `npm run method:start` to find the right station to begin from. In an interactive terminal it checks criteria one by one and recommends where to start.
-- Use the `method:resources:*` commands or `npm run method -- resources --station ...` to walk the method resources for a station and inspect related canvases or snippets.
+- Use the `method:resources:*` commands or `npm run method -- resources --station ... --cycle "__CYCLE__"` to walk the method resources for a station and inspect related canvases or snippets.
 - Use `npm run method:canvases:new-api` to generate starter canvas JSON files for a new API initiative.
 - Use the generated canvas files to capture scope, business needs, domain understanding, and interface options before going too early into contract details.
 - Use `specs/openapi/api.yaml` when you are ready to produce or review API contract details.
@@ -159,4 +159,5 @@ The skill guidance is meant to keep AI work aligned with the project structure:
 - This project can also be used for an existing API by reviewing the current design against the canvases, style guide, and audit checklist.
 - If you are building your own helper app, agent, or automation, you can also import the shared method logic from `apiops-cycles-method-data/method-engine`.
 - Default locale: `__LOCALE__`
+- Selected APIOps cycle: `__CYCLE__`
 - Selected API style hint: `__API_STYLE__`
diff --git a/packages/create-apiops/template/package.json b/packages/create-apiops/template/package.json
index 187a0d6..31383a6 100644
--- a/packages/create-apiops/template/package.json
+++ b/packages/create-apiops/template/package.json
@@ -16,13 +16,13 @@
   "scripts": {
     "preinstall": "node ./scripts/check-node-version.js",
     "method": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js",
-    "method:start": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js start --default-locale __LOCALE__",
-    "method:stations": "node ./scripts/get-core-stations.js",
-    "method:resources:strategy": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-product-strategy --locale __LOCALE__",
-    "method:resources:architecture": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-platform-architecture --locale __LOCALE__",
-    "method:resources:design": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-design --locale __LOCALE__",
-    "method:resources:audit-station": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-audit --locale __LOCALE__",
-    "method:canvases:new-api": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js generate-canvases --preset new-api --style \"__API_STYLE__\" --locale __LOCALE__ --output ./specs/canvases",
+    "method:start": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js start --cycle __CYCLE__ --default-locale __LOCALE__",
+    "method:stations": "node ./scripts/get-core-stations.js __LOCALE__ __CYCLE__",
+    "method:resources:strategy": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-product-strategy --cycle __CYCLE__ --locale __LOCALE__",
+    "method:resources:architecture": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-platform-architecture --cycle __CYCLE__ --locale __LOCALE__",
+    "method:resources:design": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-design --cycle __CYCLE__ --locale __LOCALE__",
+    "method:resources:audit-station": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js resources --station api-audit --cycle __CYCLE__ --locale __LOCALE__",
+    "method:canvases:new-api": "node ./node_modules/apiops-cycles-method-data/bin/method-cli.js generate-canvases --preset new-api --cycle __CYCLE__ --style \"__API_STYLE__\" --locale __LOCALE__ --output ./specs/canvases",
     "method:canvas": "node ./scripts/get-method-canvas-metadata.js",
     "method:canvas:mappings": "node ./scripts/list-canvas-mappings.js",
     "method:canvas:rest": "node ./scripts/get-method-canvas-metadata.js restCanvas __LOCALE__",
diff --git a/packages/create-apiops/template/scripts/get-core-stations.js b/packages/create-apiops/template/scripts/get-core-stations.js
index edc44a3..9d4e722 100644
--- a/packages/create-apiops/template/scripts/get-core-stations.js
+++ b/packages/create-apiops/template/scripts/get-core-stations.js
@@ -1,18 +1,19 @@
-import { buildStartData } from "apiops-cycles-method-data/method-engine";
+import { DEFAULT_CYCLE_ID, buildStartData } from "apiops-cycles-method-data/method-engine";
 
 function printUsage() {
-  console.error("Usage: node scripts/get-core-stations.js [locale]");
+  console.error("Usage: node scripts/get-core-stations.js [locale] [cycle]");
 }
 
 const locale = process.argv[2] || "en";
+const cycle = process.argv[3] || DEFAULT_CYCLE_ID;
 
-if (process.argv.length > 3) {
+if (process.argv.length > 4) {
   printUsage();
   process.exit(1);
 }
 
 try {
-  console.log(JSON.stringify(buildStartData(locale), null, 2));
+  console.log(JSON.stringify(buildStartData(locale, cycle), null, 2));
 } catch (error) {
   console.error(error instanceof Error ? error.message : error);
   process.exit(1);
diff --git a/packages/create-apiops/template/scripts/get-station-resources.js b/packages/create-apiops/template/scripts/get-station-resources.js
index 939f462..f09da8e 100644
--- a/packages/create-apiops/template/scripts/get-station-resources.js
+++ b/packages/create-apiops/template/scripts/get-station-resources.js
@@ -1,12 +1,13 @@
-import { DEFAULT_STYLE, buildStationResourceData } from "apiops-cycles-method-data/method-engine";
+import { DEFAULT_CYCLE_ID, DEFAULT_STYLE, buildStationResourceData } from "apiops-cycles-method-data/method-engine";
 
 function printUsage() {
-  console.error("Usage: node scripts/get-station-resources.js <station-id> [locale] [style]");
+  console.error("Usage: node scripts/get-station-resources.js <station-id> [locale] [style] [cycle]");
 }
 
 const stationId = process.argv[2];
 const locale = process.argv[3] || "en";
 const style = process.argv[4] || DEFAULT_STYLE;
+const cycle = process.argv[5] || DEFAULT_CYCLE_ID;
 
 if (!stationId) {
   printUsage();
@@ -14,9 +15,10 @@ if (!stationId) {
 }
 
 try {
-  const data = buildStationResourceData(stationId, locale, style);
+  const data = buildStationResourceData(stationId, locale, style, cycle);
   console.log(JSON.stringify({
     stationId: data.stationId,
+    cycleId: data.cycleId,
     locale,
     style: data.style,
     title: data.stationTitle,
diff --git a/scripts/test-method-content-integrity.mjs b/scripts/test-method-content-integrity.mjs
index 68314d7..be4d38c 100644
--- a/scripts/test-method-content-integrity.mjs
+++ b/scripts/test-method-content-integrity.mjs
@@ -130,12 +130,21 @@ for (const station of stationGroups) {
   }
 
   if (station.group === "sub-stations") {
-    if (station.type !== "supporting-station") {
+    const hasCycleSpecificMetadata = Boolean(
+      station.type ||
+      station.applicableCycles ||
+      station.defaultForCycles ||
+      station.cycleSpecificLabels ||
+      station.cycleSpecificDescriptions ||
+      station.cycleSpecificResources
+    );
+
+    if (hasCycleSpecificMetadata && station.type !== "supporting-station") {
       findings.push(`Substation ${station.id} must have type "supporting-station".`);
     }
 
     const applicableCycles = new Set(station.applicableCycles || []);
-    if (applicableCycles.size === 0) {
+    if (hasCycleSpecificMetadata && applicableCycles.size === 0) {
       findings.push(`Substation ${station.id} must define applicableCycles.`);
     }
 
@@ -291,10 +300,16 @@ const expectedCriteriaLabels = new Set(criteriaJson.map((criterion) => `criterio
 const expectedStakeholderLabels = collectMatchingStringValues(stakeholdersJson, /^stakeholder\./);
 
 for (const locale of localeDirs) {
-  validateLabelFile(locale, "labels.stations.json", expectedStationLabels);
+  const stationLabelFile = path.join("src", "data", "method", locale, "labels.stations.json");
+  const stationLabelExtras = Object.keys(readJson(stationLabelFile))
+    .filter((key) => key.startsWith("cycle."));
+  validateLabelFile(locale, "labels.stations.json", expectedStationLabels, stationLabelExtras);
   validateLabelFile(locale, "labels.lines.json", expectedLineLabels);
   if (locale === "en" || existsSync(path.join("src", "data", "method", locale, "labels.cycles.json"))) {
-    validateLabelFile(locale, "labels.cycles.json", expectedCycleLabels);
+    const cycleLabelFile = path.join("src", "data", "method", locale, "labels.cycles.json");
+    const cycleLabelExtras = Object.keys(readJson(cycleLabelFile))
+      .filter((key) => key.startsWith("cycle.owner.") || key.startsWith("cycle.audience.") || key.startsWith("cycle.template."));
+    validateLabelFile(locale, "labels.cycles.json", expectedCycleLabels, cycleLabelExtras);
   }
   validateLabelFile(locale, "labels.resources.json", expectedResourceLabels);
   validateLabelFile(locale, "labels.criteria.json", expectedCriteriaLabels, ["entry_criteria", "exit_criteria"]);
diff --git a/scripts/test-method-stakeholders.mjs b/scripts/test-method-stakeholders.mjs
index 311fe77..9df1dc4 100644
--- a/scripts/test-method-stakeholders.mjs
+++ b/scripts/test-method-stakeholders.mjs
@@ -4,49 +4,87 @@ import * as methodEngine from "../src/lib/method-engine.js";
 const stations = methodEngine.getStations();
 const stationIds = new Set(stations.map((station) => station.id));
 const stakeholderIds = new Set(methodEngine.getStakeholders().map((stakeholder) => stakeholder.id));
-const stationStakeholderMap = methodEngine.getStationStakeholderMap();
+const resourceIds = new Set(methodEngine.getResources().map((resource) => resource.id));
+const stationStakeholders = methodEngine.getStationStakeholderMap();
+const stationStakeholdersByCycle = stationStakeholders.stationStakeholdersByCycle || {
+  [methodEngine.DEFAULT_CYCLE_ID]: stationStakeholders
+};
 
-for (const station of stations) {
-  const entries = stationStakeholderMap[station.id];
-  assert.ok(entries, `Missing stakeholder mapping for ${station.id}.`);
-  assert.ok(entries.length > 0, `Expected at least one stakeholder mapping for ${station.id}.`);
+for (const cycle of methodEngine.getCycles()) {
+  const stationStakeholderMap = methodEngine.getStationStakeholderMapForCycle(cycle.id);
+  const cycleStationIds = new Set(cycle.stations || []);
 
-  const seenStakeholders = new Set();
-  const leads = entries.filter((entry) => entry.involvement === "lead");
-  const cores = entries.filter((entry) => entry.involvement === "core");
+  assert.deepEqual(
+    stationStakeholderMap,
+    stationStakeholdersByCycle[cycle.id],
+    `Expected direct cycle stakeholder mapping for ${cycle.id}.`
+  );
 
-  assert.equal(leads.length, 1, `Expected exactly one lead for ${station.id}.`);
-  assert.ok(cores.length > 0, `Expected at least one core stakeholder for ${station.id}.`);
+  for (const stationId of cycleStationIds) {
+    const entries = stationStakeholderMap[stationId];
+    assert.ok(entries, `Missing stakeholder mapping for ${cycle.id}/${stationId}.`);
+    assert.ok(entries.length > 0, `Expected at least one stakeholder mapping for ${cycle.id}/${stationId}.`);
 
-  for (const entry of entries) {
-    assert.ok(stakeholderIds.has(entry.stakeholder), `Unknown stakeholder ${entry.stakeholder} in ${station.id}.`);
-    assert.ok(!seenStakeholders.has(entry.stakeholder), `Duplicate stakeholder ${entry.stakeholder} in ${station.id}.`);
-    seenStakeholders.add(entry.stakeholder);
-  }
+    const seenStakeholders = new Set();
+    const leads = entries.filter((entry) => entry.involvement === "lead");
+    const cores = entries.filter((entry) => entry.involvement === "core");
 
-  const localizedStakeholders = methodEngine.buildStationStakeholderData(station.id, "fi");
-  assert.equal(localizedStakeholders.length, entries.length, `Localized stakeholder count mismatch for ${station.id}.`);
-  assert.ok(localizedStakeholders.every((entry) => entry.title && entry.description && entry.involvementLabel), `Incomplete localized stakeholder data for ${station.id}.`);
-}
+    assert.equal(leads.length, 1, `Expected exactly one lead for ${cycle.id}/${stationId}.`);
+    assert.ok(cores.length > 0, `Expected at least one core stakeholder for ${cycle.id}/${stationId}.`);
+
+    for (const entry of entries) {
+      assert.ok(stakeholderIds.has(entry.stakeholder), `Unknown stakeholder ${entry.stakeholder} in ${cycle.id}/${stationId}.`);
+      assert.ok(!seenStakeholders.has(entry.stakeholder), `Duplicate stakeholder ${entry.stakeholder} in ${cycle.id}/${stationId}.`);
+      seenStakeholders.add(entry.stakeholder);
+
+      for (const responsibility of entry.responsibilities || []) {
+        assert.ok(
+          resourceIds.has(responsibility.resource),
+          `Unknown responsibility resource ${responsibility.resource} in ${cycle.id}/${stationId}.`
+        );
+      }
+    }
 
-for (const stationId of Object.keys(stationStakeholderMap)) {
-  assert.ok(stationIds.has(stationId), `Stakeholder mapping references unknown station ${stationId}.`);
+    const localizedStakeholders = methodEngine.buildStationStakeholderData(stationId, "fi", cycle.id);
+    assert.equal(localizedStakeholders.length, entries.length, `Localized stakeholder count mismatch for ${cycle.id}/${stationId}.`);
+    assert.ok(
+      localizedStakeholders.every((entry) => entry.title && entry.description && entry.involvementLabel && Array.isArray(entry.responsibilities)),
+      `Incomplete localized stakeholder data for ${cycle.id}/${stationId}.`
+    );
+  }
+
+  for (const stationId of Object.keys(stationStakeholderMap)) {
+    assert.ok(stationIds.has(stationId), `Stakeholder mapping references unknown station ${stationId}.`);
+    assert.ok(cycleStationIds.has(stationId), `Stakeholder mapping for ${cycle.id} references station outside the cycle: ${stationId}.`);
+  }
 }
 
-const startData = methodEngine.buildStartData("en");
+const startData = methodEngine.buildStartData("en", methodEngine.DEFAULT_CYCLE_ID);
+assert.ok(startData.every((station) => station.cycleId === methodEngine.DEFAULT_CYCLE_ID), "Expected cycle id in start data.");
 assert.ok(startData.every((station) => Array.isArray(station.stakeholders) && station.stakeholders.length > 0), "Expected stakeholders in start data.");
 
-const designData = methodEngine.buildStationResourceData("api-design", "en");
+const designData = methodEngine.buildStationResourceData("api-design", "en", methodEngine.DEFAULT_STYLE, methodEngine.DEFAULT_CYCLE_ID);
+assert.equal(designData.cycleId, methodEngine.DEFAULT_CYCLE_ID, "Expected cycle id in station resource data.");
 assert.ok(Array.isArray(designData.stakeholders) && designData.stakeholders.length > 0, "Expected stakeholders in station resource data.");
 assert.ok(designData.stakeholders.some((entry) => entry.id === "security-specialist"), "Expected api-design to include security-specialist.");
-assert.ok(designData.stakeholders.some((entry) => entry.id === "compliance-legal-specialist"), "Expected api-design to include compliance-legal-specialist.");
+assert.ok(designData.stakeholders.some((entry) => entry.id === "compliance-specialist"), "Expected api-design to include compliance-specialist.");
 assert.ok(designData.stakeholders.some((entry) => entry.id === "business-owner"), "Expected api-design to include business-owner.");
 
-const architectureData = methodEngine.buildStationResourceData("api-platform-architecture", "en");
+const architectureData = methodEngine.buildStationResourceData("api-platform-architecture", "en", methodEngine.DEFAULT_STYLE, methodEngine.DEFAULT_CYCLE_ID);
 assert.ok(architectureData.stakeholders.some((entry) => entry.id === "security-specialist"), "Expected api-platform-architecture to include security-specialist.");
-assert.ok(architectureData.stakeholders.some((entry) => entry.id === "compliance-legal-specialist"), "Expected api-platform-architecture to include compliance-legal-specialist.");
+assert.ok(architectureData.stakeholders.some((entry) => entry.id === "compliance-specialist"), "Expected api-platform-architecture to include compliance-specialist.");
+
+const capabilityStrategyData = methodEngine.buildStationResourceData("api-product-strategy", "en", methodEngine.DEFAULT_STYLE, "capability-productization-cycle");
+assert.ok(
+  capabilityStrategyData.steps.some((entry) => entry.resourceId === "capabilityValuePropositionCanvas"),
+  "Expected capability cycle strategy resources to use capability value proposition canvas."
+);
+assert.ok(
+  capabilityStrategyData.stakeholders.some((entry) => entry.id === "capability-owner" && entry.involvement === "lead"),
+  "Expected capability cycle strategy lead to be capability-owner."
+);
 
-const fallbackStakeholders = methodEngine.buildStationStakeholderData("api-product-strategy", "sv");
+const fallbackStakeholders = methodEngine.buildStationStakeholderData("api-product-strategy", "sv", methodEngine.DEFAULT_CYCLE_ID);
 assert.ok(fallbackStakeholders.some((entry) => entry.involvementLabel === "Lead"), "Expected missing locale fallback to English stakeholder labels.");
 
 console.log("Method stakeholder regression test passed.");
diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json
index 55f6b1a..1434975 100644
--- a/src/data/method/en/labels.stations.json
+++ b/src/data/method/en/labels.stations.json
@@ -1,948 +1,569 @@
-[
-  {
-    "group.core-stations.title": "API Lifecycle Core Stations",
-    "group.core-stations.description": "The core stations of the API Metro, where teams can learn how to build and manage APIs effectively.",
-    "station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
-    "station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
-    "station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
-    "station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
-    "station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
-    "station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
-    "station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
-    "station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
-    "station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
-    "station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
-    "station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
-    "station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
-    "station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
-    "station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
-    "station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
-    "station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
-    "station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
-    "station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
-    "station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
-    "station.api-consumer-experience.outcomes.1": "Define the API experience journey",
-    "station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
-    "station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
-    "station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
-    "station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
-    "station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
-    "station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
-    "station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
-    "station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
-    "station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
-    "station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
-    "station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
-    "station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
-    "station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-    "station.api-design.title": "API Design - Design APIs That Deliver Value",
-    "station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
-    "station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
-    "station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
-    "station.api-design.outcomes": "Well-documented and consistent API designs",
-    "station.api-design.outcomes.1": "Reusable and validated API contracts",
-    "station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
-    "station.api-design.outcomes.3": "Design traceability to business value",
-    "station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
-    "station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
-    "station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
-    "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
-    "station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
-    "station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
-    "station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
-    "station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
-    "station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
-    "station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
-    "station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
-    "station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
-    "station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
-    "station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
-    "station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
-    "station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
-    "station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-    "station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
-    "station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
-    "station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
-    "station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
-    "station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
-    "station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
-    "station.api-audit.outcomes": "APIs meet internal and external standards",
-    "station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
-    "station.api-audit.outcomes.2": "Security, performance, and compliance validated",
-    "station.api-audit.outcomes.3": "Reduced risk of issues in production",
-    "station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
-    "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-    "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
-    "station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
-    "station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
-    "station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
-    "station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
-    "station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
-    "station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
-    "station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
-    "station.api-publishing.outcomes.3": "APIs ready for scale and governance",
-    "station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
-    "station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
-    "station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
-    "station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
-    "station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
-    "station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
-    "station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
-    "station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
-    "station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
-    "station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
-    "station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
-    "station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-    "station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
-    "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
-    "group.sub-stations.title": "API Lifecycle Sub Stations",
-    "group.sub-stations.description": "Sub stations that provide additional resources, tools, and best practices for API teams.",
-    "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
-    "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
-    "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
-    "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
-    "station.user-experience.outcomes": "APIs designed with user needs in mind",
-    "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
-    "station.user-experience.outcomes.2": "User feedback incorporated into API design",
-    "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
-    "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
-    "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
-    "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
-    "station.market-insights.title": "Market Insights - Understand the API Landscape",
-    "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
-    "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
-    "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
-    "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
-    "station.market-insights.outcomes.1": "Industry standards and best practices identified",
-    "station.market-insights.outcomes.2": "API strategy aligned with market needs",
-    "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
-    "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
-    "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
-    "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
-    "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
-    "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
-    "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
-    "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
-    "station.business-goals.outcomes": "APIs aligned with business objectives",
-    "station.business-goals.outcomes.1": "Clear business value defined for each API",
-    "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
-    "station.business-goals.outcomes.3": "APIs contribute to organizational success",
-    "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
-    "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
-    "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
-    "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
-    "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
-    "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
-    "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
-    "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
-    "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
-    "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
-    "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
-    "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
-    "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
-    "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
-    "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
-    "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
-    "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
-    "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
-    "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
-    "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
-    "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
-    "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
-    "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
-    "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
-    "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
-    "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
-    "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
-    "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
-    "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
-    "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
-    "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
-    "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
-    "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
-    "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
-    "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
-    "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
-    "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
-    "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
-    "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
-    "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
-    "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
-    "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
-    "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
-    "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
-    "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
-    "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
-    "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
-    "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
-    "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
-    "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
-    "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
-    "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
-    "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
-    "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
-    "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
-    "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
-    "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
-    "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
-    "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
-    "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
-    "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
-    "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
-    "station.design-standards.outcomes": "Consistent API design across the organization",
-    "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
-    "station.design-standards.outcomes.2": "Reusable design patterns and components",
-    "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
-    "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
-    "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
-    "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
-    "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
-    "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
-    "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
-    "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
-    "station.vendor-management.outcomes": "Effective vendor management processes established",
-    "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
-    "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
-    "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
-    "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
-    "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
-    "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
-    "station.contract-design.title": "Contract Design - Define Clear API Contracts",
-    "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-    "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
-    "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-    "station.contract-design.outcomes": "Clear API contracts defined for each API",
-    "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
-    "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
-    "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
-    "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
-    "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
-    "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
-    "station.development.title": "Development - Build APIs with Best Practices",
-    "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
-    "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
-    "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
-    "station.development.outcomes": "APIs developed using best practices and frameworks",
-    "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
-    "station.development.outcomes.2": "Consistent coding standards and practices followed",
-    "station.development.outcomes.3": "Reduced development time and technical debt",
-    "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
-    "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
-    "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
-    "station.ci-cd.title": "CI/CD - Automate API Delivery",
-    "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
-    "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
-    "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
-    "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
-    "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
-    "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
-    "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
-    "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-    "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
-    "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
-    "station.test-automation.title": "Test Automation - Ensure API Quality",
-    "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
-    "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
-    "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
-    "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
-    "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
-    "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
-    "station.test-automation.outcomes.3": "Improved API reliability and quality",
-    "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
-    "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
-    "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
-    "station.release-management.title": "Release Management - Manage API Releases Effectively",
-    "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
-    "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
-    "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
-    "station.release-management.outcomes": "Controlled and smooth API releases",
-    "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
-    "station.release-management.outcomes.2": "Rollback procedures established for API releases",
-    "station.release-management.outcomes.3": "Reduced risks associated with API changes",
-    "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
-    "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
-    "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
-    "station.service-agreements.title": "Service Agreements - Define API Service Levels",
-    "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
-    "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
-    "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
-    "station.service-agreements.outcomes": "Clear service agreements defined for each API",
-    "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
-    "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
-    "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
-    "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
-    "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
-    "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
-    "station.api-consumer-adoption.title": "API Consumer Adoption - Drive API Usage",
-    "station.api-consumer-adoption.description": "Implement strategies to drive API consumer adoption and engagement, ensuring APIs are used effectively.",
-    "station.api-consumer-adoption.why_it_matters": "Driving API consumer adoption is crucial for realizing the value of APIs. This station provides strategies and best practices for engaging API consumers, ensuring they understand how to use APIs effectively and derive value from them.",
-    "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for API consumers. Ensure teams implement strategies that drive API consumer adoption, engagement, and satisfaction.",
-    "station.api-consumer-adoption.outcomes": "API consumer adoption strategies implemented",
-    "station.api-consumer-adoption.outcomes.1": "Increased API usage and engagement",
-    "station.api-consumer-adoption.outcomes.2": "API consumers educated on API features and benefits",
-    "station.api-consumer-adoption.outcomes.3": "Improved API consumer satisfaction and loyalty",
-    "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help API consumers understand how to use APIs effectively.",
-    "station.api-consumer-adoption.how_it_works.1": "Create educational materials (e.g., tutorials, documentation) that explain API features, benefits, and usage patterns.",
-    "station.api-consumer-adoption.how_it_works.2": "Engage with API consumers through feedback loops, support channels, and community forums to understand their needs and improve API adoption.",
-    "station.api-promotion.title": "API Promotion - Increase API Visibility and Usage",
-    "station.api-promotion.description": "Promote APIs to increase visibility, usage, and adoption among target audiences.",
-    "station.api-promotion.why_it_matters": "Promoting APIs is essential for increasing their visibility and driving usage. This station provides strategies and best practices for effectively promoting APIs to target audiences, ensuring they are aware of the APIs and understand their value.",
-    "station.api-promotion.apply_in_work": "Provide marketing strategies, promotional materials, and community engagement resources. Ensure teams implement effective API promotion strategies that increase visibility, usage, and adoption among target audiences.",
-    "station.api-promotion.outcomes": "API promotion strategies implemented",
-    "station.api-promotion.outcomes.1": "Increased API visibility and awareness",
-    "station.api-promotion.outcomes.2": "Higher API usage and adoption rates",
-    "station.api-promotion.outcomes.3": "Improved API consumer engagement and satisfaction",
-    "station.api-promotion.how_it_works": "Develop marketing strategies to promote APIs to target audiences, including social media, blogs, and webinars.",
-    "station.api-promotion.how_it_works.1": "Create promotional materials (e.g., case studies, success stories) that highlight the value and benefits of APIs.",
-    "station.api-promotion.how_it_works.2": "Engage with API communities and forums to share API updates, gather feedback, and promote API usage.",
-    "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
-    "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
-    "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
-    "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
-    "station.partner-integration.outcomes": "Partner integration processes established",
-    "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
-    "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
-    "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
-    "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
-    "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
-    "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
-    "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
-    "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
-    "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
-    "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
-    "station.api-mindset.outcomes": "API-first culture established across the organization",
-    "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
-    "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
-    "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
-    "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
-    "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
-    "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
-    "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
-    "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
-    "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
-    "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
-    "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
-    "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
-    "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
-    "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
-    "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
-    "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
-    "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
-    "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
-    "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
-    "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
-    "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
-    "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
-    "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
-    "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
-    "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
-    "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
-    "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
-    "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
-    "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
-    "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
-    "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
-    "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
-    "station.operating-guidelines.outcomes": "API governance practices established",
-    "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
-    "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
-    "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
-    "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
-    "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
-    "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
-    "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
-    "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
-    "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
-    "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
-    "station.portfolio-management.outcomes": "API portfolio management practices established",
-    "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
-    "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
-    "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
-    "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
-    "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
-    "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
-    "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
-    "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
-    "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
-    "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
-    "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
-    "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
-    "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
-    "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
-    "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
-    "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
-    "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
-    "cycle.api-productization-cycle.station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
-    "cycle.api-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
-    "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
-    "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
-    "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
-    "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
-    "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
-    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
-    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
-    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
-    "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
-    "cycle.api-productization-cycle.station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
-    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
-    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Define the API experience journey",
-    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
-    "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
-    "cycle.api-productization-cycle.station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
-    "cycle.api-productization-cycle.station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
-    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
-    "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
-    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
-    "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-    "cycle.api-productization-cycle.station.api-design.title": "API Design - Design APIs That Deliver Value",
-    "cycle.api-productization-cycle.station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
-    "cycle.api-productization-cycle.station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
-    "cycle.api-productization-cycle.station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
-    "cycle.api-productization-cycle.station.api-design.outcomes": "Well-documented and consistent API designs",
-    "cycle.api-productization-cycle.station.api-design.outcomes.1": "Reusable and validated API contracts",
-    "cycle.api-productization-cycle.station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
-    "cycle.api-productization-cycle.station.api-design.outcomes.3": "Design traceability to business value",
-    "cycle.api-productization-cycle.station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
-    "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
-    "cycle.api-productization-cycle.station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
-    "cycle.api-productization-cycle.station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
-    "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
-    "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
-    "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
-    "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
-    "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
-    "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
-    "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
-    "cycle.api-productization-cycle.station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
-    "cycle.api-productization-cycle.station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
-    "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
-    "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
-    "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs meet internal and external standards",
-    "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
-    "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Security, performance, and compliance validated",
-    "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
-    "cycle.api-productization-cycle.station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
-    "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-    "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
-    "cycle.api-productization-cycle.station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
-    "cycle.api-productization-cycle.station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
-    "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
-    "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
-    "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
-    "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
-    "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
-    "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs ready for scale and governance",
-    "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
-    "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
-    "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
-    "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
-  },
-  {
-    "group.core-stations.title": "Capability Lifecycle Core Stations",
-    "group.core-stations.description": "The core stations of the method, where teams can learn how to design, deliver, govern, and improve reusable capabilities across APIs, events, files, streams, data products, and other integration styles.",
-    "station.api-product-strategy.title": "Strategy",
-    "station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
-    "station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
-    "station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
-    "station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
-    "station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
-    "station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
-    "station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
-    "station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
-    "station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
-    "station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
-    "station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
-    "station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
-    "station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
-    "station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
-    "station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
-    "station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
-    "station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
-    "station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
-    "station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
-    "station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
-    "station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
-    "station.api-platform-architecture.title": "Architecture & Platform Decisions",
-    "station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
-    "station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
-    "station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
-    "station.api-platform-architecture.outcomes": "A justified architecture choice",
-    "station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
-    "station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
-    "station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
-    "station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
-    "station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
-    "station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
-    "station.api-design.title": "Solution & Interface Design",
-    "station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
-    "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-    "station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
-    "station.api-design.outcomes": "A designed contract for the selected pattern",
-    "station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
-    "station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
-    "station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
-    "station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
-    "station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
-    "station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
-    "station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
-    "station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
-    "station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
-    "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
-    "station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
-    "station.api-delivery.title": "Delivery & Operations",
-    "station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
-    "station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-    "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
-    "station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
-    "station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
-    "station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
-    "station.api-delivery.outcomes.3": "Traceable delivery and release controls",
-    "station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
-    "station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
-    "station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
-    "station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
-    "station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
-    "station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
-    "station.api-audit.title": "Quality & Readiness Assurance",
-    "station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
-    "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
-    "station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
-    "station.api-audit.outcomes": "Documented readiness for release and reuse",
-    "station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
-    "station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
-    "station.api-audit.outcomes.3": "Reduced risk of issues in production",
-    "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
-    "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-    "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
-    "station.api-publishing.title": "Publishing & Enablement",
-    "station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
-    "station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
-    "station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
-    "station.api-publishing.outcomes": "A discoverable reusable capability",
-    "station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
-    "station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
-    "station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
-    "station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
-    "station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
-    "station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
-    "station.monitoring-and-improving.title": "Monitoring & Improvement",
-    "station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
-    "station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
-    "station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
-    "station.monitoring-and-improving.outcomes": "Measured capability health and value",
-    "station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
-    "station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
-    "station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
-    "station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
-    "station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
-    "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
-    "group.sub-stations.title": "Supporting Stations",
-    "group.sub-stations.description": "Supporting stations provide reusable practices, decision points and resources that can be included in different APIOps Cycles routes, including capability, API, integration, data and AI-enabled productization.",
-    "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
-    "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
-    "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
-    "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
-    "station.user-experience.outcomes": "APIs designed with user needs in mind",
-    "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
-    "station.user-experience.outcomes.2": "User feedback incorporated into API design",
-    "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
-    "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
-    "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
-    "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
-    "station.market-insights.title": "Market Insights - Understand the API Landscape",
-    "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
-    "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
-    "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
-    "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
-    "station.market-insights.outcomes.1": "Industry standards and best practices identified",
-    "station.market-insights.outcomes.2": "API strategy aligned with market needs",
-    "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
-    "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
-    "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
-    "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
-    "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
-    "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
-    "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
-    "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
-    "station.business-goals.outcomes": "APIs aligned with business objectives",
-    "station.business-goals.outcomes.1": "Clear business value defined for each API",
-    "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
-    "station.business-goals.outcomes.3": "APIs contribute to organizational success",
-    "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
-    "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
-    "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
-    "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
-    "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
-    "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
-    "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
-    "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
-    "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
-    "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
-    "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
-    "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
-    "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
-    "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
-    "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
-    "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
-    "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
-    "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
-    "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
-    "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
-    "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
-    "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
-    "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
-    "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
-    "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
-    "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
-    "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
-    "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
-    "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
-    "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
-    "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
-    "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
-    "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
-    "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
-    "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
-    "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
-    "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
-    "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
-    "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
-    "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
-    "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
-    "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
-    "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
-    "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
-    "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
-    "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
-    "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
-    "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
-    "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
-    "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
-    "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
-    "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
-    "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
-    "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
-    "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
-    "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
-    "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
-    "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
-    "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
-    "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
-    "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
-    "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
-    "station.design-standards.outcomes": "Consistent API design across the organization",
-    "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
-    "station.design-standards.outcomes.2": "Reusable design patterns and components",
-    "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
-    "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
-    "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
-    "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
-    "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
-    "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
-    "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
-    "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
-    "station.vendor-management.outcomes": "Effective vendor management processes established",
-    "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
-    "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
-    "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
-    "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
-    "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
-    "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
-    "station.contract-design.title": "Contract Design - Define Clear API Contracts",
-    "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-    "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
-    "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
-    "station.contract-design.outcomes": "Clear API contracts defined for each API",
-    "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
-    "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
-    "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
-    "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
-    "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
-    "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
-    "station.development.title": "Development - Build APIs with Best Practices",
-    "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
-    "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
-    "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
-    "station.development.outcomes": "APIs developed using best practices and frameworks",
-    "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
-    "station.development.outcomes.2": "Consistent coding standards and practices followed",
-    "station.development.outcomes.3": "Reduced development time and technical debt",
-    "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
-    "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
-    "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
-    "station.ci-cd.title": "CI/CD - Automate API Delivery",
-    "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
-    "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
-    "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
-    "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
-    "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
-    "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
-    "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
-    "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
-    "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
-    "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
-    "station.test-automation.title": "Test Automation - Ensure API Quality",
-    "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
-    "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
-    "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
-    "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
-    "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
-    "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
-    "station.test-automation.outcomes.3": "Improved API reliability and quality",
-    "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
-    "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
-    "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
-    "station.release-management.title": "Release Management - Manage API Releases Effectively",
-    "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
-    "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
-    "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
-    "station.release-management.outcomes": "Controlled and smooth API releases",
-    "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
-    "station.release-management.outcomes.2": "Rollback procedures established for API releases",
-    "station.release-management.outcomes.3": "Reduced risks associated with API changes",
-    "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
-    "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
-    "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
-    "station.service-agreements.title": "Service Agreements - Define API Service Levels",
-    "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
-    "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
-    "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
-    "station.service-agreements.outcomes": "Clear service agreements defined for each API",
-    "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
-    "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
-    "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
-    "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
-    "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
-    "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
-    "station.api-consumer-adoption.title": "Consumer Adoption",
-    "station.api-consumer-adoption.description": "Implement strategies to drive consumer adoption and engagement so reusable capabilities are used effectively.",
-    "station.api-consumer-adoption.why_it_matters": "Driving consumer adoption is crucial for realizing the value of reusable capabilities. This station provides strategies and best practices for engaging consumers, helping them understand how to use capabilities effectively and derive value from them.",
-    "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for consumers. Ensure teams implement adoption practices that improve engagement, satisfaction, and reuse.",
-    "station.api-consumer-adoption.outcomes": "Consumer adoption strategies implemented",
-    "station.api-consumer-adoption.outcomes.1": "Increased usage and engagement",
-    "station.api-consumer-adoption.outcomes.2": "Consumers educated on capability features and benefits",
-    "station.api-consumer-adoption.outcomes.3": "Improved consumer satisfaction and loyalty",
-    "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help consumers understand how to use reusable capabilities effectively.",
-    "station.api-consumer-adoption.how_it_works.1": "Create educational materials that explain capability features, benefits, and usage patterns.",
-    "station.api-consumer-adoption.how_it_works.2": "Engage with consumers through feedback loops, support channels, and communities to understand needs and improve adoption.",
-    "station.api-promotion.title": "Promotion",
-    "station.api-promotion.description": "Promote reusable capabilities to increase visibility, usage, and adoption among target audiences.",
-    "station.api-promotion.why_it_matters": "Promotion increases visibility and drives usage. This station provides strategies and best practices for making target audiences aware of reusable capabilities and their value.",
-    "station.api-promotion.apply_in_work": "Provide communication strategies, promotional materials, and community engagement resources. Ensure teams implement promotion practices that increase visibility, usage, and adoption among target audiences.",
-    "station.api-promotion.outcomes": "Promotion strategies implemented",
-    "station.api-promotion.outcomes.1": "Increased visibility and awareness",
-    "station.api-promotion.outcomes.2": "Higher usage and adoption rates",
-    "station.api-promotion.outcomes.3": "Improved consumer engagement and satisfaction",
-    "station.api-promotion.how_it_works": "Develop communication strategies to promote reusable capabilities to target audiences, including internal channels, communities, demos, and enablement events.",
-    "station.api-promotion.how_it_works.1": "Create promotional materials such as use cases, success stories, and release notes that highlight value and benefits.",
-    "station.api-promotion.how_it_works.2": "Engage with relevant communities and forums to share updates, gather feedback, and promote usage.",
-    "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
-    "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
-    "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
-    "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
-    "station.partner-integration.outcomes": "Partner integration processes established",
-    "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
-    "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
-    "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
-    "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
-    "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
-    "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
-    "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
-    "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
-    "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
-    "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
-    "station.api-mindset.outcomes": "API-first culture established across the organization",
-    "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
-    "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
-    "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
-    "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
-    "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
-    "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
-    "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
-    "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
-    "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
-    "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
-    "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
-    "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
-    "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
-    "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
-    "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
-    "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
-    "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
-    "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
-    "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
-    "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
-    "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
-    "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
-    "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
-    "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
-    "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
-    "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
-    "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
-    "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
-    "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
-    "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
-    "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
-    "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
-    "station.operating-guidelines.outcomes": "API governance practices established",
-    "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
-    "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
-    "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
-    "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
-    "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
-    "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
-    "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
-    "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
-    "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
-    "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
-    "station.portfolio-management.outcomes": "API portfolio management practices established",
-    "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
-    "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
-    "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
-    "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
-    "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
-    "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
-    "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
-    "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
-    "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
-    "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
-    "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
-    "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
-    "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
-    "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
-    "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
-    "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
-    "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.title": "Strategy",
-    "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
-    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
-    "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
-    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
-    "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
-    "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Architecture & Platform Decisions",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "A justified architecture choice",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
-    "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
-    "cycle.capability-productization-cycle.station.api-design.title": "Solution & Interface Design",
-    "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
-    "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-    "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
-    "cycle.capability-productization-cycle.station.api-design.outcomes": "A designed contract for the selected pattern",
-    "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
-    "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
-    "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
-    "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
-    "cycle.capability-productization-cycle.station.api-delivery.title": "Delivery & Operations",
-    "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
-    "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-    "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
-    "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
-    "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
-    "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
-    "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Traceable delivery and release controls",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
-    "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
-    "cycle.capability-productization-cycle.station.api-audit.title": "Quality & Readiness Assurance",
-    "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
-    "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
-    "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
-    "cycle.capability-productization-cycle.station.api-audit.outcomes": "Documented readiness for release and reuse",
-    "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
-    "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
-    "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
-    "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
-    "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-    "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
-    "cycle.capability-productization-cycle.station.api-publishing.title": "Publishing & Enablement",
-    "cycle.capability-productization-cycle.station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
-    "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
-    "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
-    "cycle.capability-productization-cycle.station.api-publishing.outcomes": "A discoverable reusable capability",
-    "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
-    "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
-    "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
-    "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
-    "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
-    "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitoring & Improvement",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Measured capability health and value",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
-    "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
-  }
-]
+{
+  "group.core-stations.title": "Capability Lifecycle Core Stations",
+  "group.core-stations.description": "The core stations of the method, where teams can learn how to design, deliver, govern, and improve reusable capabilities across APIs, events, files, streams, data products, and other integration styles.",
+  "station.api-product-strategy.title": "Strategy",
+  "station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
+  "station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
+  "station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
+  "station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
+  "station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
+  "station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
+  "station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
+  "station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
+  "station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
+  "station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
+  "station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
+  "station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
+  "station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
+  "station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
+  "station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
+  "station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
+  "station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
+  "station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
+  "station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
+  "station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
+  "station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
+  "station.api-platform-architecture.title": "Architecture & Platform Decisions",
+  "station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
+  "station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
+  "station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
+  "station.api-platform-architecture.outcomes": "A justified architecture choice",
+  "station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
+  "station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
+  "station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
+  "station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
+  "station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
+  "station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
+  "station.api-design.title": "Solution & Interface Design",
+  "station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
+  "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+  "station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
+  "station.api-design.outcomes": "A designed contract for the selected pattern",
+  "station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+  "station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
+  "station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
+  "station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
+  "station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
+  "station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
+  "station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
+  "station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+  "station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
+  "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+  "station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
+  "station.api-delivery.title": "Delivery & Operations",
+  "station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+  "station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
+  "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
+  "station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+  "station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
+  "station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
+  "station.api-delivery.outcomes.3": "Traceable delivery and release controls",
+  "station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
+  "station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+  "station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
+  "station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
+  "station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
+  "station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
+  "station.api-audit.title": "Quality & Readiness Assurance",
+  "station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+  "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
+  "station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
+  "station.api-audit.outcomes": "Documented readiness for release and reuse",
+  "station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
+  "station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
+  "station.api-audit.outcomes.3": "Reduced risk of issues in production",
+  "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+  "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+  "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
+  "station.api-publishing.title": "Publishing & Enablement",
+  "station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
+  "station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+  "station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
+  "station.api-publishing.outcomes": "A discoverable reusable capability",
+  "station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
+  "station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
+  "station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
+  "station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
+  "station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
+  "station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
+  "station.monitoring-and-improving.title": "Monitoring & Improvement",
+  "station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
+  "station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
+  "station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
+  "station.monitoring-and-improving.outcomes": "Measured capability health and value",
+  "station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
+  "station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
+  "station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
+  "station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
+  "station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
+  "station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
+  "group.sub-stations.title": "Supporting Stations",
+  "group.sub-stations.description": "Supporting stations provide reusable practices, decision points and resources that can be included in different APIOps Cycles routes, including capability, API, integration, data and AI-enabled productization.",
+  "station.user-experience.title": "User Experience - Design APIs with the User in Mind",
+  "station.user-experience.description": "Ensure APIs are designed with the end user in mind, providing a seamless and intuitive experience.",
+  "station.user-experience.why_it_matters": "APIs are not just technical products; they are user-facing products. A poor user experience can lead to low adoption and frustration. This station helps teams design APIs that are user-friendly and meet consumer needs.",
+  "station.user-experience.apply_in_work": "Provide user experience guidelines, templates, and tools for API design. Ensure teams follow user-centered design practices and incorporate user feedback into API iterations.",
+  "station.user-experience.outcomes": "APIs designed with user needs in mind",
+  "station.user-experience.outcomes.1": "Intuitive and consistent user interfaces",
+  "station.user-experience.outcomes.2": "User feedback incorporated into API design",
+  "station.user-experience.outcomes.3": "Improved user satisfaction and adoption",
+  "station.user-experience.how_it_works": "Use user personas to understand the needs and expectations of end-users",
+  "station.user-experience.how_it_works.1": "Conduct user research to gather insights on how consumers interact with the ecosystem services or your API consuming applications.",
+  "station.user-experience.how_it_works.2": "Document the user experience requirements so that they can be used in API design, ensuring they are intuitive and easy to use.",
+  "station.market-insights.title": "Market Insights - Understand the API Landscape",
+  "station.market-insights.description": "Analyze market trends, competitor APIs, and industry standards to inform API strategy.",
+  "station.market-insights.why_it_matters": "Understanding the market landscape helps teams identify opportunities, avoid pitfalls, and align their APIs with industry standards. This station provides tools to analyze market trends and competitor offerings.",
+  "station.market-insights.apply_in_work": "Provide market research tools, competitor analysis templates, and industry standards resources. Ensure teams stay informed about market trends and incorporate insights into API strategy.",
+  "station.market-insights.outcomes": "Market trends and competitor APIs analyzed",
+  "station.market-insights.outcomes.1": "Industry standards and best practices identified",
+  "station.market-insights.outcomes.2": "API strategy aligned with market needs",
+  "station.market-insights.outcomes.3": "Informed decision-making based on market insights",
+  "station.market-insights.how_it_works": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
+  "station.market-insights.how_it_works.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
+  "station.market-insights.how_it_works.2": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
+  "station.business-goals.title": "Business Goals - Align APIs with Business Objectives",
+  "station.business-goals.description": "Ensure APIs are aligned with business objectives and contribute to overall organizational goals.",
+  "station.business-goals.why_it_matters": "APIs should not be built in isolation; they must support and drive business objectives. This station helps teams align their APIs with strategic goals, ensuring they deliver real business value.",
+  "station.business-goals.apply_in_work": "Provide business alignment frameworks, templates, and tools for defining API business value. Ensure teams regularly review and align APIs with changing business objectives.",
+  "station.business-goals.outcomes": "APIs aligned with business objectives",
+  "station.business-goals.outcomes.1": "Clear business value defined for each API",
+  "station.business-goals.outcomes.2": "Stakeholder buy-in and support for API initiatives",
+  "station.business-goals.outcomes.3": "APIs contribute to organizational success",
+  "station.business-goals.how_it_works": "Define business objectives and how APIs can support them using **the Business Model Canvas**. If your business is to provide APIs, go through *the API Product Strategy station* and fill in **the API Business Model Canvas.**",
+  "station.business-goals.how_it_works.1": "Identify key performance indicators (KPIs) to measure API success against business goals.",
+  "station.business-goals.how_it_works.2": "Engage stakeholders to ensure alignment and support for API initiatives.",
+  "station.competitive-analysis.title": "Competitive Analysis - Stay Ahead in the API Market",
+  "station.competitive-analysis.description": "Analyze competitors' APIs to identify strengths, weaknesses, and opportunities for differentiation.",
+  "station.competitive-analysis.why_it_matters": "Understanding the competitive landscape helps teams identify gaps, opportunities, and areas for improvement in their APIs. This station provides tools to analyze competitors and inform API strategy.",
+  "station.competitive-analysis.apply_in_work": "Provide competitive analysis tools, templates, and resources. Ensure teams regularly analyze competitors and incorporate insights into API strategy and design.",
+  "station.competitive-analysis.outcomes": "Competitor APIs analyzed for strengths and weaknesses",
+  "station.competitive-analysis.outcomes.1": "Opportunities for differentiation identified",
+  "station.competitive-analysis.outcomes.2": "API strategy informed by competitive insights",
+  "station.competitive-analysis.outcomes.3": "Increased competitiveness in the API market",
+  "station.competitive-analysis.how_it_works": "Conduct a competitive analysis to identify key competitors, their API offerings, and their strengths and weaknesses.",
+  "station.competitive-analysis.how_it_works.1": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
+  "station.competitive-analysis.how_it_works.2": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
+  "station.ecosystem-vision.title": "Ecosystem Vision - Build APIs for a Thriving Ecosystem",
+  "station.ecosystem-vision.description": "Create a vision for how your APIs fit into a larger ecosystem, enabling collaboration and innovation.",
+  "station.ecosystem-vision.why_it_matters": "APIs are not standalone products; they are part of a larger ecosystem. This station helps teams define how their APIs interact with other systems, platforms, and services to create a thriving ecosystem that fosters collaboration and innovation.",
+  "station.ecosystem-vision.apply_in_work": "Provide ecosystem vision frameworks, partner engagement strategies, and integration guidelines. Ensure teams design APIs with the ecosystem in mind and foster collaboration among partners.",
+  "station.ecosystem-vision.outcomes": "Clear ecosystem vision defined for APIs",
+  "station.ecosystem-vision.outcomes.1": "APIs designed to enable collaboration and integration",
+  "station.ecosystem-vision.outcomes.2": "Ecosystem partners identified and engaged",
+  "station.ecosystem-vision.outcomes.3": "APIs contribute to a vibrant ecosystem",
+  "station.ecosystem-vision.how_it_works": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
+  "station.ecosystem-vision.how_it_works.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
+  "station.ecosystem-vision.how_it_works.2": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
+  "station.scalable-infrastructure.title": "Scalable Infrastructure - Build APIs on a Solid Foundation",
+  "station.scalable-infrastructure.description": "Ensure your API infrastructure can scale to meet growing demand and support high availability.",
+  "station.scalable-infrastructure.why_it_matters": "APIs must be built on a robust infrastructure that can handle increasing traffic and ensure high availability. This station provides guidelines for designing and implementing scalable infrastructure that supports API growth and performance.",
+  "station.scalable-infrastructure.apply_in_work": "Provide infrastructure design guidelines, cloud-native patterns, and monitoring tools. Ensure teams implement scalable infrastructure that can adapt to changing demands and support API performance.",
+  "station.scalable-infrastructure.outcomes": "Scalable and resilient API infrastructure",
+  "station.scalable-infrastructure.outcomes.1": "High availability and performance under load",
+  "station.scalable-infrastructure.outcomes.2": "Infrastructure designed for future growth",
+  "station.scalable-infrastructure.outcomes.3": "Reduced downtime and improved user experience",
+  "station.scalable-infrastructure.how_it_works": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
+  "station.scalable-infrastructure.how_it_works.1": "Implement load balancing, caching, and other techniques to ensure high availability and performance. Collect infrastructure requirements from API teams using Capacity Canvas",
+  "station.scalable-infrastructure.how_it_works.2": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
+  "station.legal-and-compliance.title": "Legal and Compliance - Ensure APIs Meet Regulatory Standards",
+  "station.legal-and-compliance.description": "Ensure APIs comply with legal and regulatory requirements, protecting your organization and users.",
+  "station.legal-and-compliance.why_it_matters": "APIs must adhere to legal and regulatory standards to protect your organization and users. This station provides tools and guidelines for ensuring APIs meet compliance requirements, reducing legal risks and ensuring data protection.",
+  "station.legal-and-compliance.apply_in_work": "Provide legal and compliance frameworks, checklists, and tools for ensuring API compliance. Ensure teams understand and implement legal requirements in API design, development, and publishing.",
+  "station.legal-and-compliance.outcomes": "APIs compliant with legal and regulatory standards",
+  "station.legal-and-compliance.outcomes.1": "Data protection and privacy requirements met",
+  "station.legal-and-compliance.outcomes.2": "Legal risks identified and mitigated",
+  "station.legal-and-compliance.outcomes.3": "Clear documentation of compliance measures",
+  "station.legal-and-compliance.how_it_works": "Identify legal and regulatory requirements that apply to your APIs, such as data protection, privacy, and security standards.",
+  "station.legal-and-compliance.how_it_works.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
+  "station.legal-and-compliance.how_it_works.2": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
+  "station.security-and-privacy.title": "Security and Privacy - Protect Your APIs and Users",
+  "station.security-and-privacy.description": "Implement security and privacy measures to protect APIs and user data from threats and breaches.",
+  "station.security-and-privacy.why_it_matters": "APIs are vulnerable to security threats and data breaches. This station provides guidelines for implementing security and privacy measures that protect APIs and user data, ensuring trust and compliance.",
+  "station.security-and-privacy.apply_in_work": "Provide security frameworks, tools, and best practices for API security and privacy. Ensure teams implement security measures throughout the API lifecycle, from design to publishing and monitoring.",
+  "station.security-and-privacy.outcomes": "APIs secured against threats and vulnerabilities",
+  "station.security-and-privacy.outcomes.1": "User data protected through privacy measures",
+  "station.security-and-privacy.outcomes.2": "Security best practices implemented in API design and development",
+  "station.security-and-privacy.outcomes.3": "Compliance with security standards and regulations",
+  "station.security-and-privacy.how_it_works": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
+  "station.security-and-privacy.how_it_works.1": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
+  "station.security-and-privacy.how_it_works.2": "Conduct regular security audits and vulnerability assessments to identify and mitigate risks.",
+  "station.design-standards.title": "Design Standards - Ensure Consistent and High-Quality API Design",
+  "station.design-standards.description": "Establish design standards and guidelines to ensure consistent and high-quality API design across the organization.",
+  "station.design-standards.why_it_matters": "Consistent and high-quality API design is essential for usability, maintainability, and scalability. This station provides design standards and guidelines that help teams create APIs that are easy to use, understand, and maintain.",
+  "station.design-standards.apply_in_work": "Provide design standards documentation, reusable components, and design review processes. Ensure teams follow design standards and conduct regular reviews to maintain high-quality API design.",
+  "station.design-standards.outcomes": "Consistent API design across the organization",
+  "station.design-standards.outcomes.1": "High-quality APIs that meet user needs",
+  "station.design-standards.outcomes.2": "Reusable design patterns and components",
+  "station.design-standards.outcomes.3": "Reduced design inconsistencies and technical debt",
+  "station.design-standards.how_it_works": "Define design standards and guidelines for API design, including naming conventions, response formats, and error handling.",
+  "station.design-standards.how_it_works.1": "Create reusable design patterns and components that teams can leverage to ensure consistency and quality.",
+  "station.design-standards.how_it_works.2": "Conduct design reviews and audits to ensure adherence to design standards and identify areas for improvement.",
+  "station.vendor-management.title": "Vendor Management - Manage Third-Party API Integrations",
+  "station.vendor-management.description": "Effectively manage third-party API vendors and integrations to ensure reliability and compliance.",
+  "station.vendor-management.why_it_matters": "Third-party APIs can introduce risks and dependencies that impact your API ecosystem. This station provides guidelines for managing vendor relationships, ensuring reliability, compliance, and alignment with your API strategy.",
+  "station.vendor-management.apply_in_work": "Provide vendor management frameworks, evaluation criteria, and monitoring tools. Ensure teams effectively manage third-party API vendors, ensuring reliability, compliance, and alignment with organizational standards.",
+  "station.vendor-management.outcomes": "Effective vendor management processes established",
+  "station.vendor-management.outcomes.1": "Third-party APIs integrated reliably and securely",
+  "station.vendor-management.outcomes.2": "Vendor compliance with organizational standards",
+  "station.vendor-management.outcomes.3": "Reduced risks associated with third-party dependencies",
+  "station.vendor-management.how_it_works": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
+  "station.vendor-management.how_it_works.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
+  "station.vendor-management.how_it_works.2": "Monitor vendor performance and compliance with service level agreements (SLAs) and organizational standards.",
+  "station.contract-design.title": "Contract Design - Define Clear API Contracts",
+  "station.contract-design.description": "Create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+  "station.contract-design.why_it_matters": "API contracts are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for designing API contracts that are clear, comprehensive, and easy to understand.",
+  "station.contract-design.apply_in_work": "Provide contract design templates, standardized formats, and review processes. Ensure teams create clear and well-defined API contracts that outline expectations, responsibilities, and usage guidelines.",
+  "station.contract-design.outcomes": "Clear API contracts defined for each API",
+  "station.contract-design.outcomes.1": "Expectations and responsibilities outlined for API providers and consumers",
+  "station.contract-design.outcomes.2": "Usage guidelines and best practices documented",
+  "station.contract-design.outcomes.3": "Reduced misunderstandings and disputes over API usage",
+  "station.contract-design.how_it_works": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
+  "station.contract-design.how_it_works.1": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
+  "station.contract-design.how_it_works.2": "Ensure API contracts are reviewed and approved by stakeholders to ensure alignment and clarity.",
+  "station.development.title": "Development - Build APIs with Best Practices",
+  "station.development.description": "Implement APIs using best practices and frameworks to ensure quality, maintainability, and scalability.",
+  "station.development.why_it_matters": "API development is a critical phase that determines the quality and reliability of the API. This station provides best practices and frameworks for API development, ensuring APIs are built to high standards and can be maintained and scaled effectively.",
+  "station.development.apply_in_work": "Provide development frameworks, libraries, and coding standards for API implementation. Ensure teams follow best practices and conduct code reviews to maintain high-quality API development.",
+  "station.development.outcomes": "APIs developed using best practices and frameworks",
+  "station.development.outcomes.1": "High-quality, maintainable, and scalable APIs",
+  "station.development.outcomes.2": "Consistent coding standards and practices followed",
+  "station.development.outcomes.3": "Reduced development time and technical debt",
+  "station.development.how_it_works": "Use established frameworks and libraries to implement APIs, ensuring they are reusable and maintainable.",
+  "station.development.how_it_works.1": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
+  "station.development.how_it_works.2": "Follow coding standards and best practices to ensure consistent and high-quality API development.",
+  "station.ci-cd.title": "CI/CD - Automate API Delivery",
+  "station.ci-cd.description": "Implement continuous integration and continuous delivery (CI/CD) pipelines to automate API delivery and ensure consistent quality.",
+  "station.ci-cd.why_it_matters": "CI/CD is essential for ensuring that APIs are delivered quickly, reliably, and with high quality. This station provides guidelines for implementing CI/CD pipelines that automate the build, test, and deployment processes for APIs.",
+  "station.ci-cd.apply_in_work": "Provide CI/CD frameworks, tools, and best practices for API delivery. Ensure teams implement automated pipelines that support continuous integration, testing, and deployment of APIs.",
+  "station.ci-cd.outcomes": "Automated CI/CD pipelines established for API delivery",
+  "station.ci-cd.outcomes.1": "Consistent quality and traceability in API delivery",
+  "station.ci-cd.outcomes.2": "Faster iterations and reduced time to market",
+  "station.ci-cd.outcomes.3": "Improved collaboration and feedback loops in API development",
+  "station.ci-cd.how_it_works": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+  "station.ci-cd.how_it_works.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
+  "station.ci-cd.how_it_works.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
+  "station.test-automation.title": "Test Automation - Ensure API Quality",
+  "station.test-automation.description": "Implement automated testing practices to ensure API quality, reliability, and performance.",
+  "station.test-automation.why_it_matters": "Automated testing is crucial for ensuring that APIs function correctly and meet quality standards. This station provides guidelines for implementing automated testing practices that cover functional, security, and performance testing for APIs.",
+  "station.test-automation.apply_in_work": "Provide test automation frameworks, tools, and best practices for API testing. Ensure teams implement automated tests that cover functional, security, and performance aspects of APIs.",
+  "station.test-automation.outcomes": "Automated testing practices implemented for APIs",
+  "station.test-automation.outcomes.1": "Functional, security, and performance tests automated",
+  "station.test-automation.outcomes.2": "Reduced manual testing effort and increased test coverage",
+  "station.test-automation.outcomes.3": "Improved API reliability and quality",
+  "station.test-automation.how_it_works": "Use automated testing tools to validate API functionality, security, and performance.",
+  "station.test-automation.how_it_works.1": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
+  "station.test-automation.how_it_works.2": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
+  "station.release-management.title": "Release Management - Manage API Releases Effectively",
+  "station.release-management.description": "Implement release management practices to ensure smooth and controlled API releases.",
+  "station.release-management.why_it_matters": "Effective release management is essential for ensuring that API releases are smooth, controlled, and aligned with business needs. This station provides guidelines for managing API releases, including versioning, deployment strategies, and rollback procedures.",
+  "station.release-management.apply_in_work": "Provide release management frameworks, versioning guidelines, and deployment strategies. Ensure teams follow best practices for managing API releases, including versioning, deployment, and rollback procedures.",
+  "station.release-management.outcomes": "Controlled and smooth API releases",
+  "station.release-management.outcomes.1": "Versioning and deployment strategies defined",
+  "station.release-management.outcomes.2": "Rollback procedures established for API releases",
+  "station.release-management.outcomes.3": "Reduced risks associated with API changes",
+  "station.release-management.how_it_works": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
+  "station.release-management.how_it_works.1": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
+  "station.release-management.how_it_works.2": "Establish rollback procedures to quickly revert changes in case of issues during API releases.",
+  "station.service-agreements.title": "Service Agreements - Define API Service Levels",
+  "station.service-agreements.description": "Establish service agreements that define expectations, service levels, and responsibilities for API providers and consumers.",
+  "station.service-agreements.why_it_matters": "Service agreements are essential for ensuring clarity and alignment between API providers and consumers. This station provides guidelines for creating service agreements that outline expectations, service levels, and responsibilities, reducing misunderstandings and disputes.",
+  "station.service-agreements.apply_in_work": "Provide service agreement templates, standardized formats, and review processes. Ensure teams create clear and well-defined service agreements that outline expectations, service levels, and responsibilities for API providers and consumers.",
+  "station.service-agreements.outcomes": "Clear service agreements defined for each API",
+  "station.service-agreements.outcomes.1": "Expectations and service levels outlined for API providers and consumers",
+  "station.service-agreements.outcomes.2": "Responsibilities and support processes documented",
+  "station.service-agreements.outcomes.3": "Improved communication and collaboration between API teams",
+  "station.service-agreements.how_it_works": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
+  "station.service-agreements.how_it_works.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
+  "station.service-agreements.how_it_works.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
+  "station.api-consumer-adoption.title": "Consumer Adoption",
+  "station.api-consumer-adoption.description": "Implement strategies to drive consumer adoption and engagement so reusable capabilities are used effectively.",
+  "station.api-consumer-adoption.why_it_matters": "Driving consumer adoption is crucial for realizing the value of reusable capabilities. This station provides strategies and best practices for engaging consumers, helping them understand how to use capabilities effectively and derive value from them.",
+  "station.api-consumer-adoption.apply_in_work": "Provide onboarding resources, educational materials, and engagement strategies for consumers. Ensure teams implement adoption practices that improve engagement, satisfaction, and reuse.",
+  "station.api-consumer-adoption.outcomes": "Consumer adoption strategies implemented",
+  "station.api-consumer-adoption.outcomes.1": "Increased usage and engagement",
+  "station.api-consumer-adoption.outcomes.2": "Consumers educated on capability features and benefits",
+  "station.api-consumer-adoption.outcomes.3": "Improved consumer satisfaction and loyalty",
+  "station.api-consumer-adoption.how_it_works": "Develop onboarding processes and resources to help consumers understand how to use reusable capabilities effectively.",
+  "station.api-consumer-adoption.how_it_works.1": "Create educational materials that explain capability features, benefits, and usage patterns.",
+  "station.api-consumer-adoption.how_it_works.2": "Engage with consumers through feedback loops, support channels, and communities to understand needs and improve adoption.",
+  "station.api-promotion.title": "Promotion",
+  "station.api-promotion.description": "Promote reusable capabilities to increase visibility, usage, and adoption among target audiences.",
+  "station.api-promotion.why_it_matters": "Promotion increases visibility and drives usage. This station provides strategies and best practices for making target audiences aware of reusable capabilities and their value.",
+  "station.api-promotion.apply_in_work": "Provide communication strategies, promotional materials, and community engagement resources. Ensure teams implement promotion practices that increase visibility, usage, and adoption among target audiences.",
+  "station.api-promotion.outcomes": "Promotion strategies implemented",
+  "station.api-promotion.outcomes.1": "Increased visibility and awareness",
+  "station.api-promotion.outcomes.2": "Higher usage and adoption rates",
+  "station.api-promotion.outcomes.3": "Improved consumer engagement and satisfaction",
+  "station.api-promotion.how_it_works": "Develop communication strategies to promote reusable capabilities to target audiences, including internal channels, communities, demos, and enablement events.",
+  "station.api-promotion.how_it_works.1": "Create promotional materials such as use cases, success stories, and release notes that highlight value and benefits.",
+  "station.api-promotion.how_it_works.2": "Engage with relevant communities and forums to share updates, gather feedback, and promote usage.",
+  "station.partner-integration.title": "Partner Integration - Collaborate with Partners",
+  "station.partner-integration.description": "Facilitate partner integrations to enhance API capabilities and expand reach.",
+  "station.partner-integration.why_it_matters": "Partner integrations can enhance API capabilities and expand reach. This station provides guidelines for collaborating with partners to integrate their APIs, ensuring seamless interoperability and value creation.",
+  "station.partner-integration.apply_in_work": "Provide partner integration frameworks, guidelines, and monitoring tools. Ensure teams effectively collaborate with partners to enhance API capabilities, expand reach, and drive innovation.",
+  "station.partner-integration.outcomes": "Partner integration processes established",
+  "station.partner-integration.outcomes.1": "Enhanced API capabilities through partner APIs",
+  "station.partner-integration.outcomes.2": "Expanded reach and market opportunities through partnerships",
+  "station.partner-integration.outcomes.3": "Improved collaboration and innovation with partners",
+  "station.partner-integration.how_it_works": "Identify potential partners whose APIs can enhance your API capabilities and value proposition.",
+  "station.partner-integration.how_it_works.1": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
+  "station.partner-integration.how_it_works.2": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
+  "station.api-mindset.title": "API Mindset - Foster an API-First Culture",
+  "station.api-mindset.description": "Cultivate an API-first mindset across the organization to drive innovation and collaboration.",
+  "station.api-mindset.why_it_matters": "An API-first mindset is essential for fostering innovation and collaboration across the organization. This station provides strategies for cultivating an API-first culture, ensuring that APIs are seen as strategic assets that drive business value.",
+  "station.api-mindset.apply_in_work": "Provide training programs, resources, and communication strategies to foster an API-first culture. Ensure teams understand the value of APIs and are empowered to drive API strategy and initiatives.",
+  "station.api-mindset.outcomes": "API-first culture established across the organization",
+  "station.api-mindset.outcomes.1": "Increased innovation and collaboration through APIs",
+  "station.api-mindset.outcomes.2": "API teams empowered to drive API strategy and initiatives",
+  "station.api-mindset.outcomes.3": "Improved alignment between business goals and API development",
+  "station.api-mindset.how_it_works": "Promote the value of APIs as strategic assets that drive business value and innovation.",
+  "station.api-mindset.how_it_works.1": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
+  "station.api-mindset.how_it_works.2": "Provide training and resources to help teams adopt an API-first mindset  and understand the benefits of APIs.",
+  "station.roles-and-responsibilities.title": "Roles and Responsibilities - Define API Team Structures",
+  "station.roles-and-responsibilities.description": "Define clear roles and responsibilities for API teams to ensure effective collaboration and accountability.",
+  "station.roles-and-responsibilities.why_it_matters": "Clear roles and responsibilities are essential for effective collaboration and accountability within API teams. This station provides guidelines for defining team structures, roles, and responsibilities, ensuring that everyone understands their contributions to API initiatives.",
+  "station.roles-and-responsibilities.apply_in_work": "Provide team structure guidelines, role definitions, and communication strategies. Ensure teams have clear roles and responsibilities that promote effective collaboration and accountability in API initiatives.",
+  "station.roles-and-responsibilities.outcomes": "Clear roles and responsibilities defined for API teams",
+  "station.roles-and-responsibilities.outcomes.1": "Effective collaboration and accountability within API teams",
+  "station.roles-and-responsibilities.outcomes.2": "Improved communication and alignment between team members",
+  "station.roles-and-responsibilities.outcomes.3": "Reduced confusion and overlap in responsibilities",
+  "station.roles-and-responsibilities.how_it_works": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
+  "station.roles-and-responsibilities.how_it_works.1": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
+  "station.roles-and-responsibilities.how_it_works.2": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
+  "station.upskilling.title": "Upskilling - Enhance API Skills and Knowledge",
+  "station.upskilling.description": "Provide training and resources to enhance API skills and knowledge across the organization.",
+  "station.upskilling.why_it_matters": "Continuous learning and upskilling are essential for keeping API teams updated with the latest technologies, practices, and trends. This station provides training programs and resources to enhance API skills and knowledge, ensuring teams are equipped to deliver high-quality APIs.",
+  "station.upskilling.apply_in_work": "Provide training programs, resources, and assessment tools to enhance API skills and knowledge. Ensure teams have access to continuous learning opportunities that empower them to drive API innovation and quality.",
+  "station.upskilling.outcomes": "API skills and knowledge enhanced across the organization",
+  "station.upskilling.outcomes.1": "Increased proficiency in API design, development, and management",
+  "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
+  "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
+  "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
+  "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
+  "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
+  "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
+  "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
+  "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
+  "station.operating-guidelines.apply_in_work": "Provide operating guidelines, governance frameworks, and monitoring tools for API management. Ensure teams follow established practices that promote consistent API management, quality, and compliance with organizational standards.",
+  "station.operating-guidelines.outcomes": "API governance practices established",
+  "station.operating-guidelines.outcomes.1": "Consistent API management and quality across the organization",
+  "station.operating-guidelines.outcomes.2": "Compliance with organizational standards and best practices",
+  "station.operating-guidelines.outcomes.3": "Improved visibility and control over API initiatives",
+  "station.operating-guidelines.how_it_works": "Define operating guidelines based on APIOps Cycles that outline the processes, standards, and best practices for API management.",
+  "station.operating-guidelines.how_it_works.1": "Establish governance practices that ensure APIs are managed consistently, including reviews, audits, and compliance checks.",
+  "station.operating-guidelines.how_it_works.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
+  "station.portfolio-management.title": "Portfolio Management - Manage API Portfolio Effectively",
+  "station.portfolio-management.description": "Manage the API portfolio effectively to ensure alignment with business goals and strategic initiatives.",
+  "station.portfolio-management.why_it_matters": "Effective API portfolio management is essential for ensuring that APIs align with business goals and strategic initiatives. This station provides guidelines for managing the API portfolio, ensuring that APIs are prioritized, monitored, and optimized to deliver maximum value.",
+  "station.portfolio-management.apply_in_work": "Provide portfolio management frameworks, prioritization criteria, and monitoring tools for API management. Ensure teams effectively manage the API portfolio, ensuring alignment with business goals, strategic initiatives, and delivering maximum value.",
+  "station.portfolio-management.outcomes": "API portfolio management practices established",
+  "station.portfolio-management.outcomes.1": "APIs aligned with business goals and strategic initiatives",
+  "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
+  "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
+  "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
+  "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
+  "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
+  "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
+  "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
+  "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
+  "station.budget-and-resource-management.apply_in_work": "Provide budget management frameworks, prioritization criteria, and monitoring tools for API initiatives. Ensure teams effectively manage budgets and resources, optimizing investments in API development and management to deliver maximum value.",
+  "station.budget-and-resource-management.outcomes": "Budget and resource management practices established for API initiatives",
+  "station.budget-and-resource-management.outcomes.1": "Effective allocation of resources to API initiatives",
+  "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
+  "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
+  "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
+  "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
+  "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
+  "cycle.api-productization-cycle.station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
+  "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "A solid pitch or case for funding/approval",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Provide guidelines, tools, and feedback mechanisms for understanding, analyzing, and improving internal and external developer and partner experience.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identify and prioritize your API consumers",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Define the API experience journey",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Plan onboarding, documentation, and feedback",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Improve adoption through genuine empathy + Developer Experience (DX)",
+  "cycle.api-productization-cycle.station.api-platform-architecture.title": "API Platform Architecture - Architect APIs for Scalability and Reuse",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Ensure scalability, reuse, and governance across your API and platform components.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "When APIs scale across teams, your platform must enable governance and reuse without blocking speed. This station shows how to architect APIs for longevity, security, and efficiency.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Establish a scalable, secure, and compliant infrastructure for API operations. Provide guidelines on architecture best practices.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Cut redundant APIs and reduce cloud platform costs",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implement consistent governance without heavy top-down control",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Design for internal reuse and external scalability",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "The Business Impact Canvas helps to identify and mitigate risks related to API availability, security, and functionality to support informed architectural decisions.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Map the regulatory, compliance, and network locations of API providers and consumers to ensure accessibility and compliance.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "The Capacity Canvas aligns business transaction patterns, future consumption trends, and technical solutions to ensure API scalability and performance.It provides critical input for scaling decisions and infrastructure planning.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+  "cycle.api-productization-cycle.station.api-design.title": "API Design - Design APIs That Deliver Value",
+  "cycle.api-productization-cycle.station.api-design.description": "Create API designs that are consistent, reusable, and grounded in business intent and shared standards.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "Designing APIs is not just about naming endpoints. Good design ensures APIs are usable, consistent, and aligned with business and technical goals. Poor design leads to tight coupling, low reuse, and costly rework across teams.",
+  "cycle.api-productization-cycle.station.api-design.apply_in_work": "Provide reusable design patterns, shared standards, and validation tools for API specifications. Ensure design decisions are consistent, reviewed early, and aligned with business intent.",
+  "cycle.api-productization-cycle.station.api-design.outcomes": "Well-documented and consistent API designs",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Reusable and validated API contracts",
+  "cycle.api-productization-cycle.station.api-design.outcomes.2": "Designs aligned with domain models and interaction patterns",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Design traceability to business value",
+  "cycle.api-productization-cycle.station.api-design.how_it_works": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across APIs.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to define how consumers will interact with the API, ensuring it meets their needs and expectations.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Apply REST design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Apply Event-driven design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Apply GraphQL design patterns to create consistent, reusable API contracts that are validated with stakeholders.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and API style guide to align your design decisions with shared rules and enable consistent audit validation.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the API contract before implementation.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
+  "cycle.api-productization-cycle.station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Functional and non-functional testing integrated",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Secure and compliant delivery pipelines",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Use API Development Best Practices as guidance for implementing the validated contract with established frameworks and libraries, ensuring the result is reusable and maintainable.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Build the API implementation from the validated contract using established frameworks, libraries, and team standards.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Test APIs for functionality, security, and performance using automated testing tools.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
+  "cycle.api-productization-cycle.station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs meet internal and external standards",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Security, performance, and compliance validated",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
+  "cycle.api-productization-cycle.station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentation, security models, and policies available",
+  "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs ready for scale and governance",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publish APIs to the appropriate gateways and environments to support reusability for multiple API consumers.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the API, including onboarding processes and registration.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Issues identified and addressed continuously",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.title": "Strategy",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Architecture & Platform Decisions",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "A justified architecture choice",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
+  "cycle.capability-productization-cycle.station.api-design.title": "Solution & Interface Design",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
+  "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+  "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
+  "cycle.capability-productization-cycle.station.api-design.outcomes": "A designed contract for the selected pattern",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
+  "cycle.capability-productization-cycle.station.api-delivery.title": "Delivery & Operations",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+  "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
+  "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Traceable delivery and release controls",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
+  "cycle.capability-productization-cycle.station.api-audit.title": "Quality & Readiness Assurance",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+  "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
+  "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes": "Documented readiness for release and reuse",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
+  "cycle.capability-productization-cycle.station.api-publishing.title": "Publishing & Enablement",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
+  "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+  "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes": "A discoverable reusable capability",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitoring & Improvement",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Measured capability health and value",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
+}
diff --git a/src/lib/method-engine.js b/src/lib/method-engine.js
index e9cc8ce..2a51c08 100644
--- a/src/lib/method-engine.js
+++ b/src/lib/method-engine.js
@@ -9,6 +9,7 @@ const repoRoot = path.resolve(__dirname, "..", "..");
 export const DEFAULT_LOCALE = "en";
 export const DEFAULT_OUTPUT_DIR = "specs/canvases";
 export const DEFAULT_STYLE = "Not sure yet";
+export const DEFAULT_CYCLE_ID = "api-productization-cycle";
 export const DEFAULT_NOTE_SIZE = 80;
 export const NOTE_COLOR_PALETTE = Object.freeze({
   benefit: "#C0EB6A",
@@ -319,6 +320,20 @@ export function getStationStakeholderMap() {
   return readJson(resolveMethodFile("station-stakeholders.json"));
 }
 
+export function getStationStakeholderMapForCycle(cycleId = DEFAULT_CYCLE_ID) {
+  const stationStakeholderMap = getStationStakeholderMap();
+  if (stationStakeholderMap.stationStakeholdersByCycle) {
+    const cycle = resolveCycle(cycleId);
+    const entries = stationStakeholderMap.stationStakeholdersByCycle[cycle.id];
+    if (!entries) {
+      throw new Error(`Unknown station stakeholder cycle mapping: ${cycle.id}`);
+    }
+    return entries;
+  }
+
+  return stationStakeholderMap;
+}
+
 export function getResources() {
   return readJson(resolveMethodFile("resources.json")).resources || [];
 }
@@ -340,6 +355,10 @@ export function getCycle(cycleId) {
   return cycle;
 }
 
+export function resolveCycle(cycleId = DEFAULT_CYCLE_ID) {
+  return getCycle(cycleId || DEFAULT_CYCLE_ID);
+}
+
 export function normalizeResourceId(resourceId) {
   const normalized = String(resourceId || "").trim();
   return LEGACY_CANVAS_RESOURCE_ALIASES.get(normalized) || normalized;
@@ -358,6 +377,15 @@ function translate(labelKey, labels) {
   return labels[labelKey] || labelKey;
 }
 
+function translateFromLabelSets(labelKey, ...labelSets) {
+  for (const labels of labelSets) {
+    if (labels[labelKey]) {
+      return labels[labelKey];
+    }
+  }
+  return labelKey;
+}
+
 export function buildStakeholderCatalog(locale = DEFAULT_LOCALE) {
   const stakeholderLabels = getLocalizedLabels(locale, "stakeholders");
   return new Map(getStakeholders().map((stakeholder) => [
@@ -370,14 +398,14 @@ export function buildStakeholderCatalog(locale = DEFAULT_LOCALE) {
   ]));
 }
 
-export function buildStationStakeholderData(stationId, locale = DEFAULT_LOCALE) {
+export function buildStationStakeholderData(stationId, locale = DEFAULT_LOCALE, cycleId = DEFAULT_CYCLE_ID) {
   const stakeholderCatalog = buildStakeholderCatalog(locale);
   const stakeholderLabels = getLocalizedLabels(locale, "stakeholders");
-  const stationStakeholderMap = getStationStakeholderMap();
+  const stationStakeholderMap = getStationStakeholderMapForCycle(cycleId);
   const entries = stationStakeholderMap[stationId];
 
   if (!entries) {
-    throw new Error(`Unknown station stakeholder mapping: ${stationId}`);
+    throw new Error(`Unknown station stakeholder mapping: ${stationId} in ${cycleId || DEFAULT_CYCLE_ID}`);
   }
 
   return entries.map((entry) => {
@@ -389,14 +417,20 @@ export function buildStationStakeholderData(stationId, locale = DEFAULT_LOCALE)
     return {
       ...stakeholder,
       involvement: entry.involvement,
-      involvementLabel: translate(`stakeholder.involvement.${entry.involvement}`, stakeholderLabels)
+      involvementLabel: translate(`stakeholder.involvement.${entry.involvement}`, stakeholderLabels),
+      responsibilities: entry.responsibilities || []
     };
   });
 }
 
-export function buildStartData(locale = DEFAULT_LOCALE) {
-  const stations = getCoreStations();
+export function buildStartData(locale = DEFAULT_LOCALE, cycleId = DEFAULT_CYCLE_ID) {
+  const cycle = resolveCycle(cycleId);
+  const stationById = new Map(getCoreStations().map((station) => [station.id, station]));
+  const stations = (cycle.stations || [])
+    .map((stationId) => stationById.get(stationId))
+    .filter(Boolean);
   const stationLabels = getLocalizedLabels(locale, "stations");
+  const cycleLabels = getLocalizedLabels(locale, "cycles");
   const criteriaLabels = getLocalizedLabels(locale, "criteria");
   const stationCriteriaMap = getStationCriteriaMap();
 
@@ -404,10 +438,15 @@ export function buildStartData(locale = DEFAULT_LOCALE) {
     id: station.id,
     order: station.order,
     slug: station.slug,
-    title: translate(station.title, stationLabels),
-    description: translate(station.description, stationLabels),
+    cycleId: cycle.id,
+    title: cycle.stationLabels?.[station.id]
+      ? translateFromLabelSets(cycle.stationLabels[station.id], stationLabels, cycleLabels)
+      : translate(station.title, stationLabels),
+    description: cycle.stationDescriptions?.[station.id]
+      ? translateFromLabelSets(cycle.stationDescriptions[station.id], stationLabels, cycleLabels)
+      : translate(station.description, stationLabels),
     suggestedForNewApi: index === 0,
-    stakeholders: buildStationStakeholderData(station.id, locale),
+    stakeholders: buildStationStakeholderData(station.id, locale, cycle.id),
     criteria: (stationCriteriaMap[station.id] || []).map((criterionId) => ({
       id: criterionId,
       label: translate(`criterion.${criterionId}`, criteriaLabels)
@@ -641,27 +680,39 @@ export function shouldIncludeResourceForStyle(resourceId, stationId, style) {
   return !["restCanvas", "eventCanvas", "graphqlCanvas"].includes(normalizedResourceId);
 }
 
-export function buildStationResourceData(stationId, locale = DEFAULT_LOCALE, style = DEFAULT_STYLE) {
-  const stations = getStations();
-  const resources = getResources();
-  const stationLabels = getLocalizedLabels(locale, "stations");
-  const resourceLabels = getLocalizedLabels(locale, "resources");
-  const station = stations.find((entry) => entry.id === stationId);
+function getCycleStepLabelKey(cycleId, stationId, index) {
+  const baseKey = `cycle.${cycleId}.station.${stationId}.how_it_works`;
+  return index === 0 ? baseKey : `${baseKey}.${index}`;
+}
 
-  if (!station) {
-    throw new Error(`Unknown station id: ${stationId}`);
-  }
+function buildStationResourceSteps(station, stationId, cycle, style, resources, stationLabels, cycleLabels, resourceLabels) {
+  const stationSteps = getStationSteps(station);
+  const stationStepsByResource = new Map(
+    stationSteps
+      .filter((step) => step.resource)
+      .map((step) => [normalizeResourceId(step.resource), step])
+  );
+  const resourceIds = cycle.recommendedResources?.[stationId] || stationSteps.map((step) => step.resource).filter(Boolean);
 
-  const steps = getStationSteps(station)
-    .filter((step) => step.resource)
-    .filter((step) => shouldIncludeResourceForStyle(step.resource, stationId, style))
-    .map((step, index) => {
-      const normalizedResourceId = normalizeResourceId(step.resource);
+  return resourceIds
+    .filter((resourceId) => shouldIncludeResourceForStyle(resourceId, stationId, style))
+    .map((resourceId, index) => {
+      const normalizedResourceId = normalizeResourceId(resourceId);
       const resource = resources.find((entry) => entry.id === normalizedResourceId);
+      const stationStep = stationStepsByResource.get(normalizedResourceId);
+      const resourceTitle = resource ? translate(resource.title, resourceLabels) : normalizedResourceId;
+      const cycleStepLabelKey = getCycleStepLabelKey(cycle.id, stationId, index);
+      const hasCycleStepLabel = cycleLabels[cycleStepLabelKey] || stationLabels[cycleStepLabelKey];
+      const stepText = hasCycleStepLabel
+        ? translateFromLabelSets(cycleStepLabelKey, cycleLabels, stationLabels)
+        : (stationStep
+          ? translate(stationStep.step, stationLabels)
+          : `Use ${resourceTitle}.`);
+
       if (!resource) {
         return {
           order: index + 1,
-          step: translate(step.step, stationLabels),
+          step: stepText,
           resourceId: normalizedResourceId,
           missing: true
         };
@@ -669,9 +720,9 @@ export function buildStationResourceData(stationId, locale = DEFAULT_LOCALE, sty
 
       return {
         order: index + 1,
-        step: translate(step.step, stationLabels),
+        step: stepText,
         resourceId: resource.id,
-        resourceTitle: translate(resource.title, resourceLabels),
+        resourceTitle,
         resourceDescription: translate(resource.description, resourceLabels),
         category: resource.category || "",
         canvasId: resource.canvas || null,
@@ -679,12 +730,37 @@ export function buildStationResourceData(stationId, locale = DEFAULT_LOCALE, sty
         slug: resource.slug
       };
     });
+}
+
+export function buildStationResourceData(stationId, locale = DEFAULT_LOCALE, style = DEFAULT_STYLE, cycleId = DEFAULT_CYCLE_ID) {
+  const stations = getStations();
+  const resources = getResources();
+  const stationLabels = getLocalizedLabels(locale, "stations");
+  const cycleLabels = getLocalizedLabels(locale, "cycles");
+  const resourceLabels = getLocalizedLabels(locale, "resources");
+  const cycle = resolveCycle(cycleId);
+  const station = stations.find((entry) => entry.id === stationId);
+
+  if (!station) {
+    throw new Error(`Unknown station id: ${stationId}`);
+  }
+
+  if (!(cycle.stations || []).includes(stationId)) {
+    throw new Error(`Station ${stationId} is not part of cycle ${cycle.id}`);
+  }
+
+  const steps = buildStationResourceSteps(station, stationId, cycle, style, resources, stationLabels, cycleLabels, resourceLabels);
 
   return {
     stationId: station.id,
-    stationTitle: translate(station.title, stationLabels),
-    stationDescription: translate(station.description, stationLabels),
-    stakeholders: buildStationStakeholderData(station.id, locale),
+    cycleId: cycle.id,
+    stationTitle: cycle.stationLabels?.[station.id]
+      ? translateFromLabelSets(cycle.stationLabels[station.id], stationLabels, cycleLabels)
+      : translate(station.title, stationLabels),
+    stationDescription: cycle.stationDescriptions?.[station.id]
+      ? translateFromLabelSets(cycle.stationDescriptions[station.id], stationLabels, cycleLabels)
+      : translate(station.description, stationLabels),
+    stakeholders: buildStationStakeholderData(station.id, locale, cycle.id),
     style,
     steps
   };
@@ -930,7 +1006,8 @@ export function resolveStationIds(options = {}) {
   }
 
   if (!options.preset || options.preset === "new-api") {
-    return NEW_API_STATIONS;
+    const cycle = resolveCycle(options.cycle || DEFAULT_CYCLE_ID);
+    return NEW_API_STATIONS.filter((stationId) => (cycle.stations || []).includes(stationId));
   }
 
   throw new Error(`Unknown preset: ${options.preset}`);
@@ -939,6 +1016,7 @@ export function resolveStationIds(options = {}) {
 export function generateCanvases(options = {}) {
   const locale = options.locale || DEFAULT_LOCALE;
   const style = normalizeStyle(options.style || DEFAULT_STYLE);
+  const cycle = resolveCycle(options.cycle || DEFAULT_CYCLE_ID);
   const outputRoot = path.resolve(process.cwd(), options.output || DEFAULT_OUTPUT_DIR);
   const resources = getResources();
   const generated = [];
@@ -946,7 +1024,7 @@ export function generateCanvases(options = {}) {
   const seenResourceIds = new Set();
 
   for (const stationId of resolveStationIds(options)) {
-    const stationResources = buildStationResourceData(stationId, locale, style);
+    const stationResources = buildStationResourceData(stationId, locale, style, cycle.id);
     const canvasResources = stationResources.steps
       .map((step) => resources.find((resource) => resource.id === step.resourceId))
       .filter((resource) => resource && resource.category === "canvas");
@@ -984,6 +1062,7 @@ export function generateCanvases(options = {}) {
   return {
     locale,
     style,
+    cycleId: cycle.id,
     outputRoot,
     generated,
     skipped
diff --git a/src/schemas/cycles.schema.json b/src/schemas/cycles.schema.json
index 1048f4d..e100a90 100644
--- a/src/schemas/cycles.schema.json
+++ b/src/schemas/cycles.schema.json
@@ -24,7 +24,7 @@
   "definitions": {
     "cycle": {
       "type": "object",
-      "required": ["id", "title", "slug", "description", "audiences", "purpose", "stations"],
+      "required": ["id", "title", "slug", "description", "purpose", "stations"],
       "additionalProperties": false,
       "properties": {
         "id": { "type": "string" },
diff --git a/src/schemas/station-stakeholders.schema.json b/src/schemas/station-stakeholders.schema.json
index 8965b63..b70c3f0 100644
--- a/src/schemas/station-stakeholders.schema.json
+++ b/src/schemas/station-stakeholders.schema.json
@@ -1,17 +1,39 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "type": "object",
-  "additionalProperties": {
-    "type": "array",
-    "items": {
+  "required": ["stationStakeholdersByCycle"],
+  "additionalProperties": false,
+  "properties": {
+    "stationStakeholdersByCycle": {
       "type": "object",
-      "required": ["stakeholder", "involvement"],
-      "additionalProperties": false,
-      "properties": {
-        "stakeholder": {"type": "string"},
-        "involvement": {
-          "type": "string",
-          "enum": ["lead", "core", "consulted"]
+      "additionalProperties": {
+        "type": "object",
+        "additionalProperties": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "required": ["stakeholder", "involvement"],
+            "additionalProperties": false,
+            "properties": {
+              "stakeholder": { "type": "string" },
+              "involvement": {
+                "type": "string",
+                "enum": ["lead", "core", "consulted"]
+              },
+              "responsibilities": {
+                "type": "array",
+                "items": {
+                  "type": "object",
+                  "required": ["resource", "role"],
+                  "additionalProperties": false,
+                  "properties": {
+                    "resource": { "type": "string" },
+                    "role": { "type": "string" }
+                  }
+                }
+              }
+            }
+          }
         }
       }
     }

From 294c40764bcba8d1538b3745050185f7b9430532 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Tue, 7 Jul 2026 12:24:41 +0300
Subject: [PATCH 05/12] fail create-apiops with non existing cycles

---
 .../bin/create-apiops-project.js              | 19 ++++++++++++
 scripts/test-create-apiops-scaffold.mjs       | 29 +++++++++++++++++++
 2 files changed, 48 insertions(+)

diff --git a/packages/create-apiops/bin/create-apiops-project.js b/packages/create-apiops/bin/create-apiops-project.js
index 1a81e70..67c1fc4 100644
--- a/packages/create-apiops/bin/create-apiops-project.js
+++ b/packages/create-apiops/bin/create-apiops-project.js
@@ -8,6 +8,7 @@ import { spawnSync } from "node:child_process";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 const templateDir = path.resolve(__dirname, "..", "template");
+const methodDataRoot = path.resolve(__dirname, "..", "..", "..", "src", "data", "method");
 
 const DEFAULTS = {
   name: "my-api-project",
@@ -210,6 +211,23 @@ function hasCompleteNonInteractiveConfig(args) {
   return args.name && args.locale && args.cycle && args.style && args.install !== undefined;
 }
 
+function getSupportedCycleIds() {
+  const cyclesPath = path.join(methodDataRoot, "cycles.json");
+  const cyclesJson = JSON.parse(fs.readFileSync(cyclesPath, "utf8"));
+  return (cyclesJson.cycles?.items || []).flatMap((cycle) => [cycle.id, cycle.slug].filter(Boolean));
+}
+
+function validateCycle(cycle) {
+  const supportedCycleIds = getSupportedCycleIds();
+  if (supportedCycleIds.includes(cycle)) {
+    return;
+  }
+
+  console.error(`Unknown APIOps cycle: ${cycle}`);
+  console.error(`Supported cycles: ${supportedCycleIds.join(", ")}`);
+  process.exit(1);
+}
+
 async function getScaffoldConfig() {
   const args = parseArgs(process.argv.slice(2));
 
@@ -273,6 +291,7 @@ async function getScaffoldConfig() {
 
 async function main() {
   const { projectName, locale, cycle, apiStyle, installNow } = await getScaffoldConfig();
+  validateCycle(cycle);
 
   const targetDir = path.resolve(process.cwd(), projectName);
   if (fs.existsSync(targetDir)) {
diff --git a/scripts/test-create-apiops-scaffold.mjs b/scripts/test-create-apiops-scaffold.mjs
index f5d18f6..f30d16c 100644
--- a/scripts/test-create-apiops-scaffold.mjs
+++ b/scripts/test-create-apiops-scaffold.mjs
@@ -97,6 +97,35 @@ try {
     "Expected non-interactive prompt failure to recommend --yes."
   );
 
+  const invalidCycleProjectName = "invalid-cycle-project";
+  const invalidCycleResult = spawnSync(
+    "node",
+    [
+      cliPath,
+      "--name", invalidCycleProjectName,
+      "--cycle", "not-a-cycle",
+      "--yes",
+      "--no-install"
+    ],
+    { cwd: tempRoot, encoding: "utf8" }
+  );
+  assert(
+    invalidCycleResult.status === 1,
+    "Expected an unknown --cycle value to fail before scaffolding."
+  );
+  assert(
+    invalidCycleResult.stderr.includes("Unknown APIOps cycle: not-a-cycle"),
+    "Expected invalid cycle failure to explain the unknown cycle."
+  );
+  assert(
+    invalidCycleResult.stderr.includes("api-productization-cycle"),
+    "Expected invalid cycle failure to list supported cycles."
+  );
+  assert(
+    !existsSync(join(tempRoot, invalidCycleProjectName)),
+    "Expected invalid cycle failure to avoid creating the project directory."
+  );
+
   const positionalProjectName = "positional-apiops-project";
   const positionalProjectDir = join(tempRoot, positionalProjectName);
   execFileSync(

From 3615701d4b9fe4bc30668d7353d9cd8180c8e89f Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Wed, 8 Jul 2026 07:49:32 +0300
Subject: [PATCH 06/12] all localizations include cycles, language improvements

---
 src/data/canvas/localizedData.json          | 826 ++++++++++----------
 src/data/method/de/labels.criteria.json     |  44 +-
 src/data/method/de/labels.cycles.json       |  93 +++
 src/data/method/de/labels.lines.json        |  24 +-
 src/data/method/de/labels.stakeholders.json |  66 +-
 src/data/method/de/labels.stations.json     | 236 +++---
 src/data/method/en/labels.criteria.json     |  38 +-
 src/data/method/en/labels.cycles.json       |  18 +-
 src/data/method/en/labels.stations.json     |  76 +-
 src/data/method/fi/labels.criteria.json     |  44 +-
 src/data/method/fi/labels.cycles.json       | 180 ++---
 src/data/method/fi/labels.lines.json        |  22 +-
 src/data/method/fi/labels.resources.json    | 306 ++++----
 src/data/method/fi/labels.stakeholders.json |  38 +-
 src/data/method/fi/labels.stations.json     | 250 +++---
 src/data/method/fr/labels.criteria.json     |  44 +-
 src/data/method/fr/labels.cycles.json       | 107 +++
 src/data/method/fr/labels.lines.json        |  20 +-
 src/data/method/fr/labels.resources.json    | 502 ++++++------
 src/data/method/fr/labels.stakeholders.json |  46 +-
 src/data/method/fr/labels.stations.json     | 246 +++---
 src/data/method/pt/labels.criteria.json     |  26 +-
 src/data/method/pt/labels.cycles.json       |  93 +++
 src/data/method/pt/labels.json              |  10 +-
 src/data/method/pt/labels.lines.json        |   8 +-
 src/data/method/pt/labels.resources.json    | 330 ++++----
 src/data/method/pt/labels.stakeholders.json |  28 +-
 src/data/method/pt/labels.stations.json     | 424 ++++++----
 28 files changed, 2267 insertions(+), 1878 deletions(-)
 create mode 100644 src/data/method/de/labels.cycles.json
 create mode 100644 src/data/method/fr/labels.cycles.json
 create mode 100644 src/data/method/pt/labels.cycles.json

diff --git a/src/data/canvas/localizedData.json b/src/data/canvas/localizedData.json
index 4ac8ef2..9e12603 100644
--- a/src/data/canvas/localizedData.json
+++ b/src/data/canvas/localizedData.json
@@ -11,31 +11,31 @@
         },
         "keyActivities": {
           "section": "Schlüsselaktivitäten",
-          "description": "Was sind die wichtigsten Maßnahmen, die der API-Anbieter ergreifen muss, um erfolgreich zu arbeiten?"
+          "description": "Welche wichtigsten Aktivitäten muss der API-Anbieter ausführen, damit die API erfolgreich betrieben werden kann?"
         },
         "keyResources": {
           "section": "Schlüsselressourcen",
-          "description": "Welche einzigartigen strategischen Vermögenswerte muss der API-Anbieter erwerben oder aufbauen?"
+          "description": "Welche strategischen Ressourcen muss der API-Anbieter beschaffen oder aufbauen?"
         },
         "apiValueProposition": {
           "section": "Wertversprechen der API",
           "description": "Beginnen Sie mit einem Haftzettel, auf dem Sie die API oder die API-Familie benennen, und erfassen Sie dann, welchen Nutzen die API den API-Nutzern bietet."
         },
         "developerRelations": {
-          "section": "Entwicklerbeziehungen",
-          "description": "Wie erreicht und unterstützt der API-Anbieter API-Konsumenten?"
+          "section": "Developer Relations",
+          "description": "Wie erreicht und unterstützt der API-Anbieter die API-Nutzer?"
         },
         "channels": {
           "section": "Kanäle",
-          "description": "Über welche Mechanismen interagieren API-Konsumenten mit der API?"
+          "description": "Über welche Mechanismen interagieren API-Nutzer mit der API?"
         },
         "apiConsumerSegments": {
-          "section": "Konsumenten der API",
+          "section": "API-Nutzersegmente",
           "description": "Wer sind die Zielgruppen für die API?"
         },
         "costs": {
           "section": "Kosten",
-          "description": "Was sind die wesentlichen Kosten für die Erstellung, Bereitstellung und den Betrieb der API?"
+          "description": "Welche wesentlichen Kosten entstehen durch Aufbau, Bereitstellung und Betrieb der API?"
         },
         "benefits": {
           "section": "Vorteile",
@@ -45,20 +45,20 @@
     },
     "apiValuePropositionCanvas": {
       "title": "API Value Proposition Canvas",
-      "purpose": "Wie lässt sich die Customer Journey auf APIs abbilden? Welche Probleme und Vorteile von Endnutzern und API-Nutzern müssen berücksichtigt werden?",
-      "howToUse": "Beschreiben Sie die Perspektive der Endnutzer, beginnend mit ihren Aufgaben, dann die Probleme und Vorteile von Endnutzern und API-Nutzern und schließlich die Produkte und Funktionen der API.",
+      "purpose": "Wie hängt die Customer Journey mit APIs zusammen? Welche Pain Points und Nutzen von Endnutzern und API-Nutzern müssen adressiert werden?",
+      "howToUse": "Beschreiben Sie die Perspektive der Endnutzer: zuerst ihre Aufgaben, dann ihre Pain Points und Nutzen sowie die der API-Nutzer, und schließlich die API-Produkte und API-Funktionen.",
       "sections": {
         "tasks": {
           "section": "Aufgaben",
-          "description": "Was wollen die Kunden (Endnutzer) erreichen?"
+          "description": "Was möchten Kunden oder Endnutzer erreichen?"
         },
         "gainEnablingFeatures": {
-          "section": "Nutzenstiftende Features",
-          "description": "Welche Features ermöglichen es API-Konsumenten ihre Bedürfnisse zu bedienen?"
+          "section": "Nutzenstiftende Funktionen",
+          "description": "Welche Funktionen helfen Endnutzern und API-Nutzern, den gewünschten Nutzen zu erreichen?"
         },
         "painRelievingFeatures": {
-          "section": "Problemlösende Features",
-          "description": "Welche Funktionen helfen Endnutzern und API-Nutzern, Probleme zu überwinden?"
+          "section": "Funktionen zur Reduktion von Pain Points",
+          "description": "Welche Funktionen helfen Endnutzern und API-Nutzern, Pain Points zu reduzieren?"
         },
         "apiProducts": {
           "section": "API-Produkte",
@@ -68,8 +68,8 @@
     },
     "businessImpactCanvas": {
       "title": "Business Impact Canvas",
-      "purpose": "Was sind die potenziellen geschäftlichen Auswirkungen eines Ausfalls einer API?",
-      "howToUse": "Berücksichtigen Sie die potenziellen Auswirkungen auf Verfügbarkeit, Sicherheit und Daten für jede API.",
+      "purpose": "Welche geschäftlichen Auswirkungen kann ein Ausfall oder Fehlverhalten der Capability oder Schnittstelle haben?",
+      "howToUse": "Bewerten Sie mögliche Auswirkungen auf Verfügbarkeit, Sicherheit und Daten, bevor der Umsetzungsstil endgültig festgelegt wird.",
       "sections": {
         "availabilityRisks": {
           "section": "Risiken der Verfügbarkeit",
@@ -85,22 +85,22 @@
         },
         "mitigateAvailabilityRisks": {
           "section": "Reduzierung von Risiken der Verfügbarkeit",
-          "description": "Wie kann der API-Anbieter die Risiken der Verfügbarkeit reduzieren?"
+          "description": "Wie lassen sich Verfügbarkeitsrisiken reduzieren?"
         },
         "mitigateSecurityRisks": {
           "section": "Reduktion der Sicherheitsrisiken",
-          "description": "Wie kann der API-Anbieter die Sicherheitsrisiken reduzieren?"
+          "description": "Wie lassen sich Sicherheitsrisiken reduzieren?"
         },
         "mitigateDataRisks": {
           "section": "Reduktion der Datenrisiken",
-          "description": "Wie kann der API-Anbieter die Datenrisiken reduzieren?"
+          "description": "Wie lassen sich Datenrisiken reduzieren?"
         }
       }
     },
     "capacityCanvas": {
       "title": "Capacity Canvas",
-      "purpose": "Welche Anforderungen ergeben sich, um den Konsum der API zu gewährleisten?",
-      "howToUse": "Analysieren Sie die aktuellen und zukünftigen Kapazitätsanforderungen für jede API.",
+      "purpose": "Welche Kapazität ist erforderlich, um die Nutzung der Capability oder Schnittstelle zu unterstützen?",
+      "howToUse": "Analysieren Sie aktuelle und zukünftige Kapazitätsanforderungen für die Capability oder Schnittstelle.",
       "sections": {
         "currentBusinessVolumes": {
           "section": "Aktuelles Geschäftsvolumen",
@@ -119,8 +119,8 @@
           "description": "Welche Caching-Strategien können zur Performanceoptimierung eingesetzt werden?"
         },
         "rateLimitingStrategies": {
-          "section": "Rate-Limiting-Strategien",
-          "description": "Welche Rate-Limiting-Strategien können zur Konsumsteuerung eingesetzt werden?"
+          "section": "Strategien zur Ratenbegrenzung",
+          "description": "Welche Strategien zur Ratenbegrenzung können genutzt werden, um die Nutzung zu steuern?"
         },
         "scalingStrategies": {
           "section": "Strategien zur Skalierung",
@@ -130,8 +130,8 @@
     },
     "customerJourneyCanvas": {
       "title": "Customer Journey Canvas",
-      "purpose": "Welche Reise eines Kunden oder Partners soll mit der API unterstützt werden?",
-      "howToUse": "Beschreiben Sie eine reale Reise eines Kunden oder Nutzers – nicht die API-Nutzung selbst. Diese Reise macht Probleme, Ziele und Kontexte sichtbar, um spätere API-Anforderungen und Nutzen zu definieren.",
+      "purpose": "Welche Customer Journey oder Partner Journey erzeugt den Bedarf für eine Capability oder Schnittstelle?",
+      "howToUse": "Beschreiben Sie eine reale Reise eines Kunden, Partners oder Nutzers - nicht die API-Nutzung selbst. Diese Reise macht Probleme, Ziele und Kontext sichtbar und hilft, spätere Anforderungen an Capability- und Schnittstellendesign zu klären.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "Kunde erkennt Bedarf",
@@ -143,15 +143,15 @@
         },
         "pains": {
           "section": "Probleme",
-          "description": "Was sind die Probleme oder Herausforderungen des Kunden?"
+          "description": "Welche Probleme oder Pain Points erlebt der Kunde oder Nutzer?"
         },
         "journeySteps": {
           "section": "Customer Journey Schritte",
           "description": "Welche Schritte durchläuft der Kunde bei der Reise?"
         },
         "customerNeedIsResolved": {
-          "section": "Kundenbedürfnis wird gelöst",
-          "description": "Wie wird das Bedürfnis des Kunden letztendlich gelöst?"
+          "section": "Kundenbedarf wird erfüllt",
+          "description": "Wie wird der Bedarf des Kunden oder Nutzers letztlich erfüllt?"
         },
         "gains": {
           "section": "Nutzen",
@@ -169,8 +169,8 @@
     },
     "domainCanvas": {
       "title": "Domain Canvas",
-      "purpose": "Was sind die wesentlichen Entitäten und Geschäftsregeln im Zusammenhang mit der API?",
-      "howToUse": "Definieren Sie das Domänenmodell für jede API, einschließlich Entitäten, Attribute und Beziehungen.",
+      "purpose": "Welche wesentlichen Entitäten, Begriffe und Fachregeln muss die Capability oder Schnittstelle respektieren?",
+      "howToUse": "Definieren Sie das Fachdomänenmodell für die Capability oder Schnittstelle, einschließlich Entitäten, Attributen und Beziehungen.",
       "sections": {
         "selectedCustomerJourneySteps": {
           "section": "Ausgewählte Customer Journey Schritte",
@@ -189,8 +189,8 @@
           "description": "Welche Beziehungen bestehen zwischen den Entitäten?"
         },
         "businessComplianceAndIntegrityRules": {
-          "section": "Geschäfts-, Compliance- und Integritätsregeln",
-          "description": "Welche Geschäfts-, Compliance- und Integritätsregeln gelten für die Entitäten?"
+          "section": "Fachregeln, Compliance und Integrität",
+          "description": "Welche Fachregeln sowie Compliance- und Integritätsanforderungen beziehen sich auf die Entitäten?"
         },
         "securityAndPrivacyConsiderations": {
           "section": "Überlegungen zu Sicherheit und Datenschutz",
@@ -200,12 +200,12 @@
     },
     "eventCanvas": {
       "title": "Event Canvas",
-      "purpose": "Welche Events sind für die API relevant, und wie werden sie verarbeitet?",
-      "howToUse": "Definieren Sie die Events, ihre Trigger und die Verarbeitungslogik für jede API.",
+      "purpose": "Welche Ereignisse sind für die Capability oder Schnittstelle relevant und wie werden sie verarbeitet?",
+      "howToUse": "Definieren Sie Ereignisse, Auslöser und Verarbeitungslogik für die Capability oder Schnittstelle.",
       "sections": {
         "userTaskTrigger": {
-          "section": "Nutzeraufgabe / Trigger",
-          "description": "Welche Nutzeraktion oder welches System-Event löst diese Eventoperation aus?"
+          "section": "Nutzeraufgabe / Auslöser",
+          "description": "Welche Nutzeraktion oder welches Systemereignis löst diese Ereignisoperation aus?"
         },
         "inputEventPayload": {
           "section": "Input / Event-Payload",
@@ -213,7 +213,7 @@
         },
         "processingLogic": {
           "section": "Verarbeitung / Logik",
-          "description": "Beschreiben Sie die Backend-Verarbeitungslogik, inklusive Validierungen, Transformationen, oder Routing-Entscheidungen."
+          "description": "Beschreiben Sie die Verarbeitungslogik der Backend-Systeme, einschließlich Validierungen, Transformationen oder Routing-Entscheidungen."
         },
         "outputEventResult": {
           "section": "Output / Event-Ergebnis",
@@ -223,8 +223,8 @@
     },
     "interactionCanvas": {
       "title": "Interaction Canvas",
-      "purpose": "Welche Arten von Interaktionen sollte diese API unterstützen, bevor Sie sich für ein protokollspezifisches Design entscheiden?",
-      "howToUse": "Ermitteln Sie, welche Interaktionsarten für diese API tatsächlich benötigt werden und welche nicht in den Anwendungsbereich fallen. Verwenden Sie diese Arbeitsfläche, um die Absicht zu klären, bevor Sie das Ergebnis auf REST, Events oder GraphQL abbilden.",
+      "purpose": "Welche Arten von Interaktionen muss diese Capability oder Schnittstelle unterstützen, bevor ein konkretes Protokolldesign gewählt wird?",
+      "howToUse": "Identifizieren Sie, welche Interaktionsstile wirklich benötigt werden und welche außerhalb des Umfangs liegen. Nutzen Sie dieses Canvas, um die Absicht zu klären, bevor das Ergebnis auf REST, Events oder GraphQL abgebildet wird.",
       "sections": {
         "crudInteractions": {
           "section": "CRUD Interaktionen",
@@ -240,7 +240,7 @@
         },
         "queryDrivenInteractions": {
           "section": "Abfragegesteuerte Interaktionen",
-          "description": "Welche Lese- oder Abfrageinteraktionen sind erforderlich, um Verbraucherfragen zu beantworten?"
+          "description": "Welche Lese- oder Abfrageinteraktionen sind erforderlich, um Nutzerfragen zu beantworten?"
         },
         "queryDrivenInputOutputModels": {
           "section": "Abfragegesteuerte Input- & Output-Modelle",
@@ -277,9 +277,9 @@
       }
     },
     "locationsCanvas": {
-      "title": "Location Canvas",
-      "purpose": "Welche geopolitischen, regulatorischen, netzwerkbezogenen und vertrauensbezogenen Grenzen wirken sich auf diese API aus?",
-      "howToUse": "Ermitteln Sie, wo API-Nutzer, -Anbieter und abhängige Systeme in internen Netzwerken, Partnernetzwerken, im öffentlichen Internet und in regulierten Regionen operieren. Beschreiben Sie die Auswirkungen auf Latenz, Vertrauen, Compliance und Konnektivität zwischen ihnen.",
+      "title": "Locations Canvas",
+      "purpose": "Welche geopolitischen, regulatorischen, Netzwerk- und Vertrauensgrenzen betreffen diese Capability oder Schnittstelle?",
+      "howToUse": "Identifizieren Sie, wo Nutzer, Anbieter und abhängige Systeme in internen Netzwerken, Partnernetzwerken, im öffentlichen Internet und in regulierten Regionen betrieben werden. Beschreiben Sie die Auswirkungen auf Latenz, Vertrauen, Compliance und Konnektivität.",
       "sections": {
         "locationGroups": {
           "section": "Standort-/Vertrauensgruppen",
@@ -318,7 +318,7 @@
     "restCanvas": {
       "title": "REST Canvas",
       "purpose": "Wie kann die API nach RESTful-Prinzipien gestaltet werden?",
-      "howToUse": "Definieren Sie die API-Ressourcen, HTTP-Methoden und Beispielanfragen und -antworten.",
+      "howToUse": "Definieren Sie Ressourcen, Verben sowie Beispiele für API-Requests und API-Responses.",
       "sections": {
         "apiResources": {
           "section": "API-Ressourcen",
@@ -340,20 +340,20 @@
     },
     "graphqlCanvas": {
       "title": "GraphQL Canvas",
-      "purpose": "Wie kann die API unter Verwendung von GraphQL-Prinzipien gestaltet werden?",
-      "howToUse": "Definieren Sie die Schlüsseltypen, Abfragen, Mutationen und Einschränkungen für Ihre GraphQL-API.",
+      "purpose": "Wie kann die API nach GraphQL-Prinzipien gestaltet werden?",
+      "howToUse": "Definieren Sie zentrale Typen, Queries, Mutations und Einschränkungen für die GraphQL-API.",
       "sections": {
         "apiName": {
           "section": "API-Name",
           "description": "Wie lautet der Name der GraphQL-API oder des Endpunkts?"
         },
         "consumerGoals": {
-          "section": "Ziele der Konsumenten",
-          "description": "Welche Probleme versuchen API-Konsumenten zu lösen? Welche Daten benötigen sie?"
+          "section": "Ziele der API-Nutzer",
+          "description": "Welche Probleme versuchen API-Nutzer zu lösen? Welche Daten benötigen sie?"
         },
         "keyTypes": {
           "section": "Schlüsseltypen",
-          "description": "Welche Kern-Typen werden bereitgestellt (z.B. Benutzer, Bestellung, Produkt)?"
+          "description": "Welche zentralen Typen werden bereitgestellt (z. B. Nutzer, Bestellung, Produkt)?"
         },
         "relationships": {
           "section": "Beziehungen",
@@ -369,14 +369,14 @@
         },
         "subscriptions": {
           "section": "Subscriptions",
-          "description": "Gibt es Echtzeit-Updates oder Ereignisse, die Konsumenten abonnieren können?"
+          "description": "Gibt es Echtzeit-Updates oder Ereignisse, die Nutzer abonnieren können?"
         },
         "authorizationRules": {
           "section": "Autorisierungsregeln",
           "description": "Wer darf auf welche Felder oder Typen zugreifen?"
         },
         "consumerConstraints": {
-          "section": "Einschränkungen für Konsumenten",
+          "section": "Einschränkungen für Nutzer",
           "description": "Gibt es Paginierungs-, Filter- oder Ratenbegrenzungen?"
         },
         "openQuestions": {
@@ -387,114 +387,114 @@
     },
     "capabilityValuePropositionCanvas": {
       "title": "Capability Value Proposition Canvas",
-      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
-      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "purpose": "Welche wiederverwendbare Capability würde Nutzern Wert liefern, ohne bereits zu entscheiden, ob sie als API, Event, Datei, Stream, Datenprodukt oder ein anderer Integrationsstil bereitgestellt werden soll?",
+      "howToUse": "Starten Sie mit Nutzeraufgaben und Ergebnissen. Erfassen Sie nutzenstiftende und Pain-Point-reduzierende Capability-Funktionen und beschreiben Sie mögliche wiederverwendbare Capabilities, ohne die Technologie zu früh festzulegen.",
       "sections": {
         "consumerTasks": {
-          "section": "Consumer tasks and outcomes",
-          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+          "section": "Nutzeraufgaben und Ergebnisse",
+          "description": "Was möchten Nutzer, Partner, Systeme oder Teams erreichen?"
         },
         "gainEnablingCapabilities": {
-          "section": "Gain-enabling capability features",
-          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+          "section": "Nutzenstiftende Capability-Funktionen",
+          "description": "Welche Capability-Funktionen helfen Nutzern, bessere Ergebnisse, Geschwindigkeit, Automatisierung, Erkenntnisse, Reichweite oder Compliance zu erreichen?"
         },
         "painRelievingCapabilities": {
-          "section": "Pain-relieving capability features",
-          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+          "section": "Pain-Point-reduzierende Capability-Funktionen",
+          "description": "Welche Capability-Funktionen reduzieren Reibung, manuelle Arbeit, Fehler, Verzögerungen, Risiken oder Unsicherheit für Nutzer?"
         },
         "reusableCapabilities": {
-          "section": "Reusable capabilities",
-          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+          "section": "Wiederverwendbare Capabilities",
+          "description": "Welche wiederverwendbaren Geschäfts- oder Daten-Capabilities könnten diese Aufgaben, Nutzen und Pain Points über mehr als einen Nutzer oder Use Case hinweg unterstützen?"
         }
       }
     },
     "capabilityBusinessModelCanvas": {
       "title": "Capability Business Model Canvas",
-      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
-      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "purpose": "Wie tragfähig, wiederverwendbar, finanziert, verantwortet, unterstützt und auffindbar soll diese Integrations-Capability sein?",
+      "howToUse": "Fassen Sie das Wertversprechen der Capability zusammen, identifizieren Sie Nutzer und Interaktionskanäle und erfassen Sie anschließend Verantwortlichkeiten, Aktivitäten, Ressourcen, Partner, Nutzen und Kosten.",
       "sections": {
         "keyPartners": {
-          "section": "Key partners",
-          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+          "section": "Schlüsselpartner",
+          "description": "Welche Partner aus Business, Technologie, Daten, Sicherheit, Recht, Plattform oder externen Organisationen werden benötigt, damit die Capability funktioniert?"
         },
         "keyActivities": {
-          "section": "Key activities",
-          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+          "section": "Schlüsselaktivitäten",
+          "description": "Was müssen Capability Owner und Produzenten tun, um die Capability zu gestalten, bereitzustellen, zu steuern, zu unterstützen und zu verbessern?"
         },
         "keyResources": {
-          "section": "Key resources",
-          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+          "section": "Schlüsselressourcen",
+          "description": "Welche Systeme, Datenbestände, Plattformen, Personen, Standards, Finanzierungen und operativen Fähigkeiten werden benötigt?"
         },
         "capabilityValueProposition": {
-          "section": "Capability value proposition",
-          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+          "section": "Wertversprechen der Capability",
+          "description": "Welchen Wert liefert diese wiederverwendbare Capability für Nutzer und für die Organisation oder das Ökosystem?"
         },
         "consumerEngagement": {
-          "section": "Consumer engagement",
-          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+          "section": "Nutzerinteraktion",
+          "description": "Wie werden Nutzer die Capability entdecken, bewerten, anfordern, onboarden, Unterstützung erhalten und Feedback geben?"
         },
         "channels": {
-          "section": "Channels",
-          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+          "section": "Kanäle",
+          "description": "Über welche Kataloge, Portale, Marktplätze, Dokumentationsseiten, Support-Wege oder Governance-Prozesse interagieren Nutzer mit der Capability?"
         },
         "capabilityConsumerSegments": {
-          "section": "Capability consumer segments",
-          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+          "section": "Nutzersegmente der Capability",
+          "description": "Wer sind die aktuellen und potenziellen Nutzer der Capability, einschließlich Teams, Partnern, Systemen, Produkten oder Datennutzern?"
         },
         "costs": {
-          "section": "Costs",
-          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+          "section": "Kosten",
+          "description": "Welche wesentlichen Kosten entstehen durch Aufbau, Betrieb, Governance, Support und Weiterentwicklung der Capability?"
         },
         "benefits": {
-          "section": "Benefits",
-          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+          "section": "Nutzen",
+          "description": "Welcher geschäftliche, operative, ökologische, wiederverwendungsbezogene, Compliance- oder Kostennutzen rechtfertigt die Capability?"
         }
       }
     },
     "consumerExperienceRequirementsCanvas": {
       "title": "Consumer Experience Requirements Canvas",
-      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
-      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "purpose": "Welche Erfahrungs- und nichtfunktionalen Anforderungen benötigen Nutzer, bevor die beste Integrationsarchitektur entschieden wird?",
+      "howToUse": "Nutzen Sie dieses Canvas als technologieunabhängige Anforderungstabelle. Erfassen Sie Erwartungen und Einschränkungen der Nutzer und verwenden Sie anschließend die Architekturimplikationen, um APIs, Events, Dateien, Streams, Datenprodukte oder ein anderes Muster auszuwählen.",
       "sections": {
         "consumerGoals": {
-          "section": "Consumer goals",
-          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+          "section": "Nutzerziele",
+          "description": "Welche Geschäfts-, Workflow-, Entscheidungs-, Automatisierungs- oder Datennutzungsziele haben die Nutzer?"
         },
         "availabilityAndTimeliness": {
-          "section": "Availability and timeliness",
-          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+          "section": "Verfügbarkeit und Aktualität",
+          "description": "Wann muss die Capability verfügbar sein, wie aktuell müssen Informationen sein und welche Latenz- oder Bereitstellungsfenster sind relevant?"
         },
         "volumeAndPerformance": {
-          "section": "Volume and performance",
-          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+          "section": "Volumen und Performance",
+          "description": "Welche Volumina an Requests, Events, Datensätzen, Dateien, Batches, Nutzern oder Transaktionen muss die Capability heute und künftig unterstützen?"
         },
         "dataQualityAndConsistency": {
-          "section": "Data quality and consistency",
-          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+          "section": "Datenqualität und Konsistenz",
+          "description": "Welche Erwartungen an Genauigkeit, Vollständigkeit, Konsistenz, Reihenfolge, Deduplizierung, Abstimmung oder Validierung haben Nutzer?"
         },
         "securityPrivacyAndCompliance": {
-          "section": "Security, privacy, and compliance",
-          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+          "section": "Sicherheit, Datenschutz und Compliance",
+          "description": "Welche Anforderungen an Identität, Autorisierung, Vertraulichkeit, Datenresidenz, Einwilligung, Aufbewahrung, Audit oder Regulierung gelten?"
         },
         "onboardingAndAccess": {
-          "section": "Onboarding and access",
-          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+          "section": "Onboarding und Zugriff",
+          "description": "Wie sollen Nutzer die Capability finden, anfordern, testen, freigeben lassen und mit der Nutzung beginnen?"
         },
         "changeAndVersioning": {
-          "section": "Change and versioning",
-          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+          "section": "Änderungen und Versionierung",
+          "description": "Wie viel Änderungstoleranz haben Nutzer und welche Erwartungen an Vorankündigung, Kompatibilität, Migration oder Versionierung gelten?"
         },
         "observabilityAndSupport": {
-          "section": "Observability and support",
-          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+          "section": "Observability und Support",
+          "description": "Welche Überwachung, Statusinformationen, Nachvollziehbarkeit, Sichtbarkeit der Datenqualität, Unterstützung, Verantwortlichkeiten und Incident-Kommunikation benötigen Nutzer?"
         },
         "recoveryAndContinuity": {
-          "section": "Recovery and continuity",
-          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+          "section": "Recovery und Kontinuität",
+          "description": "Welche Erwartungen an Replay, Retry, Abstimmung, Backup, Fallback, Kontinuität oder manuelle Wiederherstellung müssen unterstützt werden?"
         },
         "architectureImplications": {
-          "section": "Architecture implications",
-          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+          "section": "Architekturimplikationen",
+          "description": "Was bedeuten diese Anforderungen für mögliche Architekturstile wie APIs, Events, Dateien, Streams, Datenprodukte oder direkte Integration?"
         }
       }
     }
@@ -1001,9 +1001,9 @@
   },
   "fi": {
     "apiBusinessModelCanvas": {
-      "title": "API Business Model Canvas",
-      "purpose": "Kuinka toteuttamiskelpoinen ja uudelleenkäytettävä API on? Onko meillä liiketoimintaperuste kustannus-hyötynäkökulmasta?",
-      "howToUse": "Yhteenveto APIn arvolupauksesta API Value Proposition Canvasin pohjalta, ja etene sitten numeroidussa järjestyksessä.",
+      "title": "API-liiketoimintamallikanvas",
+      "purpose": "Kuinka elinkelpoinen ja uudelleenkäytettävä tämä API on? Onko sille kustannus-hyötynäkökulmasta perusteltu liiketoimintamalli?",
+      "howToUse": "Tiivistä API-rajapinnan arvolupaus API-arvolupauskanvas -kanvaksesta ja etene numeroidussa järjestyksessä.",
       "sections": {
         "keyPartners": {
           "section": "Keskeiset kumppanit",
@@ -1019,7 +1019,7 @@
         },
         "apiValueProposition": {
           "section": "APIn arvolupaus",
-          "description": "Aloita yhdellä tarralapulla, jossa nimeät APIn tai API-perheen, kerro sitten mitä arvoa API tarjoaa API-käyttäjille."
+          "description": "Aloita yhdellä tarralapulla, jossa nimeät APIn tai API-perheen, kerro sitten mitä arvoa API tarjoaa API-hyödyntäjille."
         },
         "developerRelations": {
           "section": "Suhde kehittäjiin",
@@ -1030,7 +1030,7 @@
           "description": "Minkä kanavien kautta APIn käyttäjät ovat vuorovaikutuksessa APIn kanssa?"
         },
         "apiConsumerSegments": {
-          "section": "APIn kohderyhmät",
+          "section": "API-hyödyntäjäsegmentit",
           "description": "Keitä ovat APIn kohdeyleisöt?"
         },
         "costs": {
@@ -1044,21 +1044,21 @@
       }
     },
     "apiValuePropositionCanvas": {
-      "title": "API Value Proposition Canvas",
-      "purpose": "Miten asiakaspolku liittyy API-rajapintoihin? Mitä loppukäyttäjien ja API-käyttäjien ongelmia ja hyötyjä on käsiteltävä?",
-      "howToUse": "Kuvaile loppukäyttäjien näkökulmaa aloittaen heidän tehtävistään, sitten heidän ja API-käyttäjien ongelmista ja hyödyistä ja lopuksi API:n tuotteista ja ominaisuuksista.",
+      "title": "API-arvolupauskanvas",
+      "purpose": "Miten asiakaspolku liittyy API-rajapintoihin? Mitkä loppukäyttäjien ja API-hyödyntäjien kipupisteet ja tavoitellut hyödyt täytyy huomioida?",
+      "howToUse": "Kuvaa loppukäyttäjien näkökulma aloittamalla heidän tehtävistään, kipupisteistään ja hyödyistään. Lisää sen jälkeen API-hyödyntäjien vastaavat tarpeet sekä API-tuotteet ja API-ominaisuudet.",
       "sections": {
         "tasks": {
           "section": "Tehtävät",
-          "description": "Mitä asiakkaat (loppukäyttäjät) yrittävät saavuttaa?"
+          "description": "Mitä asiakkaat tai loppukäyttäjät yrittävät saavuttaa?"
         },
         "gainEnablingFeatures": {
-          "section": "Hyötyä mahdollistavat ominaisuudet",
-          "description": "Mitkä ominaisuudet mahdollistavat loppukäyttäjien ja API-käyttäjien hyötyjen saavuttamisen?"
+          "section": "Hyötyjä mahdollistavat ominaisuudet",
+          "description": "Mitkä ominaisuudet auttavat loppukäyttäjiä ja API-hyödyntäjiä saavuttamaan tavoitellut hyödyt?"
         },
         "painRelievingFeatures": {
-          "section": "Kipua lievittävät ominaisuudet",
-          "description": "Mitkä ominaisuudet auttavat loppukäyttäjiä ja API-käyttäjiä voittamaan ongelmia?"
+          "section": "Kipupisteitä vähentävät ominaisuudet",
+          "description": "Mitkä ominaisuudet auttavat loppukäyttäjiä ja API-hyödyntäjiä vähentämään kipupisteitä?"
         },
         "apiProducts": {
           "section": "APIn tuotteet",
@@ -1067,9 +1067,9 @@
       }
     },
     "businessImpactCanvas": {
-      "title": "Business Impact Canvas",
-      "purpose": "Mitkä ovat mahdolliset liiketoiminnalliset vaikutukset APIn virhetilanteissa?",
-      "howToUse": "Ota huomioon mahdolliset vaikutukset saatavuuteen, tietoturvaan ja dataan kullekin APIlle.",
+      "title": "Liiketoimintavaikutuskanvas",
+      "purpose": "Mitkä ovat kyvykkyyden tai rajapinnan epäonnistumisen mahdolliset liiketoimintavaikutukset?",
+      "howToUse": "Arvioi vaikutukset saatavuuteen, turvallisuuteen, dataan ja operointiin ennen toteutustyylin lukitsemista.",
       "sections": {
         "availabilityRisks": {
           "section": "Saatavuuteen liittyvät riskit",
@@ -1077,7 +1077,7 @@
         },
         "securityRisks": {
           "section": "Tietoturvariskit",
-          "description": "Mitkä ovat APIin liittyvät mahdolliset tietoturvariskit?"
+          "description": "Mitkä ovat API-rajapintaan liittyvät mahdolliset tietoturvariskit?"
         },
         "dataRisks": {
           "section": "Tietoriskit",
@@ -1098,9 +1098,9 @@
       }
     },
     "capacityCanvas": {
-      "title": "Capacity Canvas",
-      "purpose": "Kuinka paljon kapasiteettia tarvitaan APIn käytön tukemiseksi?",
-      "howToUse": "Analysoi kunkin APIn nykyiset ja tulevat kapasiteettitarpeet.",
+      "title": "Kapasiteettikanvas",
+      "purpose": "Kuinka paljon kapasiteettia kyvykkyyden tai rajapinnan käytön tukeminen edellyttää?",
+      "howToUse": "Analysoi nykyiset ja tulevat kapasiteettivaatimukset kyvykkyydelle tai rajapinnalle.",
       "sections": {
         "currentBusinessVolumes": {
           "section": "Nykyinen liiketoimintavolyymi",
@@ -1129,9 +1129,9 @@
       }
     },
     "customerJourneyCanvas": {
-      "title": "Customer Journey Canvas",
-      "purpose": "Mikä on se asiakkaan tai kumppanin asiakaspolku, jota API:n tulisi tukea?",
-      "howToUse": "Kuvaa oikea asiakkaan tai käyttäjän polku, ei API:n käyttöpolkua. Tunnista kipupisteet, tavoitteet ja konteksti. Tämä toimii pohjana API-tarpeiden ja arvolupausten muotoilulle.",
+      "title": "Asiakaspolkukanvas",
+      "purpose": "Mikä asiakkaan tai kumppanin polku synnyttää tarpeen kyvykkyydelle tai rajapinnalle?",
+      "howToUse": "Kuvaa todellinen asiakkaan, kumppanin tai käyttäjän polku, ei API-rajapinnan käyttöä. Polku tuo näkyviin kipupisteet, tavoitteet ja kontekstin, jotka auttavat määrittämään kyvykkyyden ja rajapinnan vaatimukset.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "Asiakas havaitsee tarpeen",
@@ -1168,9 +1168,9 @@
       }
     },
     "domainCanvas": {
-      "title": "Domain Canvas",
-      "purpose": "Mitkä ovat APIn keskeiset entiteetit ja liiketoimintasäännöt?",
-      "howToUse": "Määrittele kunkin APIn toimialuemalli, mukaan lukien entiteetit, attribuutit ja suhteet.",
+      "title": "Toimialuekanvas",
+      "purpose": "Mitkä keskeiset käsitteet, entiteetit ja toimialueen säännöt kyvykkyyden tai rajapinnan täytyy huomioida?",
+      "howToUse": "Määritä toimialuemalli kyvykkyydelle tai rajapinnalle, mukaan lukien entiteetit, attribuutit ja suhteet.",
       "sections": {
         "selectedCustomerJourneySteps": {
           "section": "Valitut asiakaspolun vaiheet",
@@ -1199,9 +1199,9 @@
       }
     },
     "eventCanvas": {
-      "title": "Event Canvas",
-      "purpose": "Mitkä tapahtumat liittyvät APIin ja miten ne käsitellään?",
-      "howToUse": "Määrittele tapahtumat, niiden laukaisijat ja käsittelylogiikka kullekin APIlle.",
+      "title": "Tapahtumakanvas",
+      "purpose": "Mitkä tapahtumat ovat olennaisia kyvykkyydelle tai rajapinnalle ja miten ne käsitellään?",
+      "howToUse": "Määritä tapahtumat, niiden laukaisijat ja käsittelylogiikka kyvykkyydelle tai rajapinnalle.",
       "sections": {
         "userTaskTrigger": {
           "section": "Käyttäjän tehtävä / Laukaisija",
@@ -1222,9 +1222,9 @@
       }
     },
     "interactionCanvas": {
-      "title": "Interaction Canvas",
-      "purpose": "Minkälaisia vuorovaikutustapoja tämän APIn tulisi tukea ennen protokollakohtaisen suunnittelun valitsemista?",
-      "howToUse": "Määritä, mitkä vuorovaikutustavat ovat tämän APIn kannalta todella tarpeellisia ja mitkä eivät kuulu sen piiriin. Käytä tätä kankaata tarkentamaan tarkoitusta ennen tuloksen kartoittamista RESTiin, eventeihin tai GraphQLään.",
+      "title": "Vuorovaikutuskanvas",
+      "purpose": "Minkä tyyppisiä vuorovaikutuksia kyvykkyyden tai rajapinnan täytyy tukea ennen protokollakohtaisen suunnittelun valintaa?",
+      "howToUse": "Tunnista, mitä vuorovaikutustyylejä todella tarvitaan ja mitkä jäävät rajauksen ulkopuolelle. Käytä kanvasta tarkoituksen selkeyttämiseen ennen kuin ratkaisu mallinnetaan REST-, tapahtuma- tai GraphQL-toteutukseksi.",
       "sections": {
         "crudInteractions": {
           "section": "CRUD-vuorovaikutukset",
@@ -1240,7 +1240,7 @@
         },
         "queryDrivenInteractions": {
           "section": "Kyselyohjatut vuorovaikutukset",
-          "description": "Mitä luku- tai kyselyvuorovaikutuksia tarvitaan vastaamaan kuluttajien kysymyksiin?"
+          "description": "Mitä luku- tai kyselyvuorovaikutuksia tarvitaan vastaamaan hyödyntäjien kysymyksiin?"
         },
         "queryDrivenInputOutputModels": {
           "section": "Kyselyohjatut syötteet ja vastaukset",
@@ -1277,9 +1277,9 @@
       }
     },
     "locationsCanvas": {
-      "title": "Locations Canvas",
-      "purpose": "”Mitkä geopoliittiset, sääntely-, verkko- ja luottamusrajat vaikuttavat tähän APIin?",
-      "howToUse": "Tunnista, missä APIn käyttäjät, tarjoajat ja riippuvaiset järjestelmät toimivat sisäisissä verkoissa, kumppaniverkoissa, julkisessa internetissä ja säännellyillä alueilla. Kuvaile niiden välisiä viive-, luottamus-, vaatimustenmukaisuus- ja yhteysvaikutuksia.",
+      "title": "Sijaintikanvas",
+      "purpose": "Mitkä geopoliittiset, sääntelyyn liittyvät, verkko- ja luottamusrajat vaikuttavat tähän kyvykkyyteen tai rajapintaan?",
+      "howToUse": "Tunnista, missä hyödyntäjät, tuottajat ja riippuvat järjestelmät toimivat sisäverkoissa, kumppaniverkoissa, julkisessa internetissä ja säännellyillä alueilla. Kuvaa vaikutukset latenssiin, luottamukseen, vaatimustenmukaisuuteen ja yhteyksiin.",
       "sections": {
         "locationGroups": {
           "section": "Sijainti-/luottamusryhmät",
@@ -1316,7 +1316,7 @@
       }
     },
     "restCanvas": {
-      "title": "REST Canvas",
+      "title": "REST-kanvas",
       "purpose": "Miten API voidaan suunnitella REST-periaatteiden mukaisesti?",
       "howToUse": "Määrittele APIn resurssit, verbit sekä esimerkkipyynnöt ja -vastaukset.",
       "sections": {
@@ -1339,9 +1339,9 @@
       }
     },
     "graphqlCanvas": {
-      "title": "GraphQL Canvas",
-      "purpose": "Kuinka API voidaan suunnitella GraphQL-periaatteiden mukaisesti?",
-      "howToUse": "Määrittele keskeiset tyypit, kyselyt, mutaatiot ja rajoitukset GraphQL-API:a varten.",
+      "title": "GraphQL-kanvas",
+      "purpose": "Miten API voidaan suunnitella GraphQL-periaatteiden mukaisesti?",
+      "howToUse": "Määritä GraphQL-API-rajapinnan keskeiset tyypit, kyselyt, mutaatiot ja rajoitteet.",
       "sections": {
         "apiName": {
           "section": "APIn nimi",
@@ -1386,115 +1386,115 @@
       }
     },
     "capabilityValuePropositionCanvas": {
-      "title": "Capability Value Proposition Canvas",
-      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
-      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "title": "Kyvykkyyden arvolupauskanvas",
+      "purpose": "Mikä uudelleenkäytettävä kyvykkyys loisi arvoa hyödyntäjille ilman, että vielä päätetään toteutetaanko se API-rajapintana, tapahtumana, tiedostona, streamina, datatuotteena tai muuna integraatiotyylinä?",
+      "howToUse": "Aloita hyödyntäjien tehtävistä ja lopputuloksista. Kuvaa hyödyt mahdollistavat ja kipupisteitä vähentävät kyvykkyyden ominaisuudet. Määritä sen jälkeen mahdolliset uudelleenkäytettävät kyvykkyydet nimeämättä teknologiaa liian aikaisin.",
       "sections": {
         "consumerTasks": {
-          "section": "Consumer tasks and outcomes",
-          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+          "section": "Hyödyntäjien tehtävät ja lopputulokset",
+          "description": "Mitä hyödyntäjät, kumppanit, käyttäjät, järjestelmät tai tiimit yrittävät saavuttaa?"
         },
         "gainEnablingCapabilities": {
-          "section": "Gain-enabling capability features",
-          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+          "section": "Hyötyjä mahdollistavat kyvykkyyden ominaisuudet",
+          "description": "Mitkä kyvykkyyden ominaisuudet auttaisivat hyödyntäjiä saavuttamaan parempia tuloksia, nopeutta, automaatiota, oivalluksia, kattavuutta tai vaatimustenmukaisuutta?"
         },
         "painRelievingCapabilities": {
-          "section": "Pain-relieving capability features",
-          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+          "section": "Kipupisteitä vähentävät kyvykkyyden ominaisuudet",
+          "description": "Mitkä kyvykkyyden ominaisuudet poistaisivat kitkaa, manuaalista työtä, virheitä, viiveitä, riskejä tai epävarmuutta hyödyntäjiltä?"
         },
         "reusableCapabilities": {
-          "section": "Reusable capabilities",
-          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+          "section": "Uudelleenkäytettävät kyvykkyydet",
+          "description": "Mitkä uudelleenkäytettävät liiketoiminta- tai datakyvykkyydet voisivat palvella näitä tehtäviä, hyötyjä ja kipupisteitä useamman kuin yhden hyödyntäjän tai käyttötapauksen tarpeisiin?"
         }
       }
     },
     "capabilityBusinessModelCanvas": {
-      "title": "Capability Business Model Canvas",
-      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
-      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "title": "Kyvykkyyden liiketoimintamallikanvas",
+      "purpose": "Kuinka elinkelpoinen, uudelleenkäytettävä, rahoitettu, omistettu, tuettu ja löydettävä tämän integraatiokyvykkyyden tulisi olla?",
+      "howToUse": "Tiivistä kyvykkyyden arvolupaus, tunnista hyödyntäjät ja osallistamiskanavat sekä kartoita omistajuus, toiminnot, resurssit, kumppanit, hyödyt ja kustannukset.",
       "sections": {
         "keyPartners": {
-          "section": "Key partners",
-          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+          "section": "Keskeiset kumppanit",
+          "description": "Mitä liiketoiminnan, teknologian, datan, turvallisuuden, juridiikan, alustan tai ulkoisia kumppaneita tarvitaan, jotta kyvykkyys toimii?"
         },
         "keyActivities": {
-          "section": "Key activities",
-          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+          "section": "Keskeiset toiminnot",
+          "description": "Mitä kyvykkyyden omistajan ja tuottajien täytyy tehdä kyvykkyyden suunnittelemiseksi, toimittamiseksi, hallitsemiseksi, tukemiseksi ja parantamiseksi?"
         },
         "keyResources": {
-          "section": "Key resources",
-          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+          "section": "Keskeiset resurssit",
+          "description": "Mitä järjestelmiä, data-aineistoja, alustoja, ihmisiä, standardeja, rahoitusta ja operatiivisia kyvykkyyksiä tarvitaan?"
         },
         "capabilityValueProposition": {
-          "section": "Capability value proposition",
-          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+          "section": "Kyvykkyyden arvolupaus",
+          "description": "Mitä arvoa tämä uudelleenkäytettävä kyvykkyys tuottaa hyödyntäjille sekä organisaatiolle tai ekosysteemille?"
         },
         "consumerEngagement": {
-          "section": "Consumer engagement",
-          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+          "section": "Hyödyntäjien osallistaminen",
+          "description": "Miten hyödyntäjät löytävät, arvioivat, pyytävät käyttöönsä, ottavat käyttöön, saavat tukea ja antavat palautetta kyvykkyydestä?"
         },
         "channels": {
-          "section": "Channels",
-          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+          "section": "Kanavat",
+          "description": "Minkä katalogien, portaalien, markkinapaikkojen, dokumentaatiosivustojen, tukikanavien tai governance-prosessien kautta hyödyntäjät ovat vuorovaikutuksessa kyvykkyyden kanssa?"
         },
         "capabilityConsumerSegments": {
-          "section": "Capability consumer segments",
-          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+          "section": "Kyvykkyyden hyödyntäjäsegmentit",
+          "description": "Ketkä ovat kyvykkyyden nykyisiä ja mahdollisia hyödyntäjiä, mukaan lukien tiimit, kumppanit, järjestelmät, tuotteet tai datan käyttäjät?"
         },
         "costs": {
-          "section": "Costs",
-          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+          "section": "Kustannukset",
+          "description": "Mitkä ovat kyvykkyyden rakentamisen, operoinnin, governancen, tuen ja kehittämisen merkittävät kustannukset?"
         },
         "benefits": {
-          "section": "Benefits",
-          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+          "section": "Hyödyt",
+          "description": "Mitkä liiketoiminnalliset, operatiiviset, ekosysteemiin, uudelleenkäyttöön, vaatimustenmukaisuuteen tai kustannuksiin liittyvät hyödyt perustelevat kyvykkyyden?"
         }
       }
     },
     "consumerExperienceRequirementsCanvas": {
-      "title": "Consumer Experience Requirements Canvas",
-      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
-      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "title": "Hyödyntäjäkokemuksen vaatimuskanvas",
+      "purpose": "Mitä kokemukseen liittyviä ja ei-toiminnallisia vaatimuksia hyödyntäjillä on ennen parhaan integraatioarkkitehtuurin valintaa?",
+      "howToUse": "Käytä tätä teknologiariippumattomana vaatimuskanvaksena. Kuvaa hyödyntäjien odotukset ja rajoitteet ja käytä arkkitehtuurivaikutuksia API-rajapintojen, tapahtumien, tiedostojen, streamien, datatuotteiden tai muun mallin valintaan.",
       "sections": {
         "consumerGoals": {
-          "section": "Consumer goals",
-          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+          "section": "Hyödyntäjien tavoitteet",
+          "description": "Mitkä ovat hyödyntäjien liiketoiminta-, työnkulku-, päätöksenteko-, automaatio- tai datankäyttötavoitteet?"
         },
         "availabilityAndTimeliness": {
-          "section": "Availability and timeliness",
-          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+          "section": "Saatavuus ja ajantasaisuus",
+          "description": "Milloin kyvykkyyden täytyy olla saatavilla, kuinka ajantasaista tiedon täytyy olla ja millä latenssi- tai toimitusikkunoilla on merkitystä?"
         },
         "volumeAndPerformance": {
-          "section": "Volume and performance",
-          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+          "section": "Volyymi ja suorituskyky",
+          "description": "Mitä pyyntö-, tapahtuma-, tietue-, tiedosto-, eräajo-, käyttäjä- tai transaktiovolyymeja kyvykkyyden täytyy tukea nyt ja myöhemmin?"
         },
         "dataQualityAndConsistency": {
-          "section": "Data quality and consistency",
-          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+          "section": "Datan laatu ja yhdenmukaisuus",
+          "description": "Mitä tarkkuuteen, täydellisyyteen, yhdenmukaisuuteen, järjestykseen, deduplikointiin, täsmäytykseen tai validointiin liittyviä odotuksia hyödyntäjillä on?"
         },
         "securityPrivacyAndCompliance": {
-          "section": "Security, privacy, and compliance",
-          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+          "section": "Turvallisuus, tietosuoja ja vaatimustenmukaisuus",
+          "description": "Mitä identiteettiin, valtuutukseen, luottamuksellisuuteen, datan sijaintiin, suostumukseen, säilytykseen, auditointiin tai sääntelyyn liittyviä rajoitteita sovelletaan?"
         },
         "onboardingAndAccess": {
-          "section": "Onboarding and access",
-          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+          "section": "Käyttöönotto ja pääsy",
+          "description": "Miten hyödyntäjien tulisi löytää, pyytää, testata, saada hyväksyntä ja aloittaa kyvykkyyden käyttö?"
         },
         "changeAndVersioning": {
-          "section": "Change and versioning",
-          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+          "section": "Muutokset ja versiointi",
+          "description": "Kuinka paljon muutoksia hyödyntäjät sietävät ja mitä ennakkoilmoituksiin, yhteensopivuuteen, migraatioon tai versiointiin liittyviä odotuksia sovelletaan?"
         },
         "observabilityAndSupport": {
-          "section": "Observability and support",
-          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+          "section": "Havainnoitavuus ja tuki",
+          "description": "Mitä monitorointia, tilatietoa, jäljitettävyyttä, datan laadun näkyvyyttä, tukea, omistajuutta ja häiriöviestintää hyödyntäjät tarvitsevat?"
         },
         "recoveryAndContinuity": {
-          "section": "Recovery and continuity",
-          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+          "section": "Palautuminen ja jatkuvuus",
+          "description": "Mitä uudelleentoistoon, uudelleenyrityksiin, täsmäytykseen, varmuuskopiointiin, varamenettelyihin, jatkuvuuteen tai manuaaliseen palautumiseen liittyviä odotuksia täytyy tukea?"
         },
         "architectureImplications": {
-          "section": "Architecture implications",
-          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+          "section": "Arkkitehtuurivaikutukset",
+          "description": "Mitä nämä vaatimukset tarkoittavat mahdollisille arkkitehtuurityyleille, kuten API-rajapinnoille, tapahtumille, tiedostoille, streameille, datatuotteille tai suoralle integraatiolle?"
         }
       }
     }
@@ -1502,8 +1502,8 @@
   "fr": {
     "apiBusinessModelCanvas": {
       "title": "API Business Model Canvas",
-      "purpose": "Dans quelle mesure cette API sera-t-elle viable et réutilisable ? Avons-nous un cas commercial du point de vue coût-bénéfice ?",
-      "howToUse": "Résumez la proposition de valeur d'une API à partir du Canvas de proposition de valeur API, puis suivez la séquence numérotée.",
+      "purpose": "Quelle sera la viabilité et la réutilisabilité de cette API ? Existe-t-il un modèle métier justifié du point de vue coût-bénéfice ?",
+      "howToUse": "Résumer la proposition de valeur d’une API à partir de l’API Value Proposition Canvas, puis suivre la séquence numérotée.",
       "sections": {
         "keyPartners": {
           "section": "Partenaires clés",
@@ -1511,54 +1511,54 @@
         },
         "keyActivities": {
           "section": "Activités clés",
-          "description": "Quelles sont les actions les plus importantes que le fournisseur d'API doit entreprendre pour réussir?"
+          "description": "Quelles sont les actions les plus importantes que le fournisseur d’API doit entreprendre pour réussir?"
         },
         "keyResources": {
           "section": "Ressources clés",
-          "description": "Quels actifs stratégiques uniques le fournisseur d'API doit-il acquérir ou développer?"
+          "description": "Quels actifs stratégiques uniques le fournisseur d’API doit-il acquérir ou développer?"
         },
         "apiValueProposition": {
-          "section": "Proposition de valeur de l'API",
-          "description": "Commencez par une note adhésive indiquant le nom de l'API ou de la famille d'API, puis notez la valeur ajoutée que l'API offre aux consommateurs d'API."
+          "section": "Proposition de valeur de l’API",
+          "description": "Commencez par une note adhésive indiquant le nom de l’API ou de la famille d’API, puis notez la valeur ajoutée que l’API offre aux utilisateurs API."
         },
         "developerRelations": {
           "section": "Relations développeurs",
-          "description": "Comment le fournisseur d'API atteint-il et soutient-il les consommateurs d'API?"
+          "description": "Comment le fournisseur d’API atteint-il et soutient-il les utilisateurs API?"
         },
         "channels": {
           "section": "Canaux",
-          "description": "Par quels mécanismes les consommateurs d'API interagissent-ils avec l'API?"
+          "description": "Par quels mécanismes les utilisateurs API interagissent-ils avec l’API?"
         },
         "apiConsumerSegments": {
-          "section": "Segments de consommateurs de l'API",
-          "description": "Quelles sont les audiences cibles pour l'API?"
+          "section": "Segments d’utilisateurs API",
+          "description": "Quelles sont les audiences cibles pour l’API?"
         },
         "costs": {
           "section": "Coûts",
-          "description": "Quels sont les coûts importants liés à la création, au déploiement et à l'exploitation de l'API?"
+          "description": "Quels sont les coûts importants liés à la création, au déploiement et à l'exploitation de l’API?"
         },
         "benefits": {
           "section": "Avantages",
-          "description": "Quels sont les avantages significatifs ou les sources de revenus générés par l'API?"
+          "description": "Quels sont les avantages significatifs ou les sources de revenus générés par l’API?"
         }
       }
     },
     "apiValuePropositionCanvas": {
       "title": "API Value Proposition Canvas",
-      "purpose": "Comment le parcours client s'articule-t-il avec les API ? Quels sont les problèmes et les avantages rencontrés par les utilisateurs finaux et les consommateurs d'API ?",
-      "howToUse": "Décrire le point de vue des utilisateurs finaux, en commençant par leurs tâches, puis leurs problèmes et avantages ainsi que ceux des consommateurs d'API, et enfin les produits et fonctionnalités de l'API.",
+      "purpose": "Comment le parcours client est-il lié aux API ? Quels irritants et gains des utilisateurs finaux et des utilisateurs API doivent être traités ?",
+      "howToUse": "Décrire la perspective des utilisateurs finaux, en commençant par leurs tâches, puis leurs irritants et gains ainsi que ceux des utilisateurs API, et enfin les produits et fonctionnalités API.",
       "sections": {
         "tasks": {
           "section": "Tâches",
-          "description": "Qu'est-ce que les clients (utilisateurs finaux) cherchent à réaliser ?"
+          "description": "Que cherchent à accomplir les clients ou utilisateurs finaux ?"
         },
         "gainEnablingFeatures": {
           "section": "Fonctionnalités génératrices de gains",
-          "description": "Quelles fonctionnalités permettent aux utilisateurs finaux et aux consommateurs d'API de réaliser des gains ?"
+          "description": "Quelles fonctionnalités aident les utilisateurs finaux et les utilisateurs API à obtenir les gains attendus ?"
         },
         "painRelievingFeatures": {
-          "section": "Fonctionnalités soulageant les peines",
-          "description": "Quelles fonctionnalités aident les utilisateurs finaux et les consommateurs d'API à surmonter les difficultés ?"
+          "section": "Fonctionnalités qui réduisent les irritants",
+          "description": "Quelles fonctionnalités aident les utilisateurs finaux et les utilisateurs API à réduire les irritants ?"
         },
         "apiProducts": {
           "section": "Produits API",
@@ -1568,39 +1568,39 @@
     },
     "businessImpactCanvas": {
       "title": "Business Impact Canvas",
-      "purpose": "Quels sont les impacts commerciaux potentiels d'une défaillance de l'API?",
-      "howToUse": "Considérez l'impact potentiel sur la disponibilité, la sécurité et les données pour chaque API.",
+      "purpose": "Quels impacts métier une défaillance ou un mauvais comportement de la capacité ou de l’interface peut-il avoir ?",
+      "howToUse": "Évaluer les impacts potentiels sur la disponibilité, la sécurité, les données et les opérations avant de figer le mode de mise en œuvre.",
       "sections": {
         "availabilityRisks": {
           "section": "Risques de disponibilité",
-          "description": "Quels sont les risques potentiels pour la disponibilité de l'API?"
+          "description": "Quels sont les risques potentiels pour la disponibilité de l’API?"
         },
         "securityRisks": {
           "section": "Risques de sécurité",
-          "description": "Quels sont les risques de sécurité potentiels associés à l'API?"
+          "description": "Quels sont les risques de sécurité potentiels associés à l’API?"
         },
         "dataRisks": {
           "section": "Risques liés aux données",
-          "description": "Quels sont les risques potententiels pour l'intégrité ou la confidentialité des données?"
+          "description": "Quels sont les risques potententiels pour l'intégrité ou la protection des données?"
         },
         "mitigateAvailabilityRisks": {
           "section": "Atténuer les risques de disponibilité",
-          "description": "Comment le fournisseur d'API peut-il atténuer les risques de disponibilité?"
+          "description": "Comment le fournisseur d’API peut-il atténuer les risques de disponibilité?"
         },
         "mitigateSecurityRisks": {
           "section": "Atténuer les risques de sécurité",
-          "description": "Comment le fournisseur d'API peut-il atténuer les risques de sécurité?"
+          "description": "Comment le fournisseur d’API peut-il atténuer les risques de sécurité?"
         },
         "mitigateDataRisks": {
           "section": "Atténuer les risques liés aux données",
-          "description": "Comment le fournisseur d'API peut-il atténuer les risques liés aux données?"
+          "description": "Comment le fournisseur d’API peut-il atténuer les risques liés aux données?"
         }
       }
     },
     "capacityCanvas": {
       "title": "Capacity Canvas",
-      "purpose": "Quelle capacité est nécessaire pour soutenir la consommation de l'API?",
-      "howToUse": "Analysez les besoins de capacité actuels et futurs pour chaque API.",
+      "purpose": "Quelle capacité est nécessaire pour soutenir l’usage de la capacité ou de l’interface ?",
+      "howToUse": "Analyser les exigences de capacité actuelles et futures pour la capacité ou l’interface.",
       "sections": {
         "currentBusinessVolumes": {
           "section": "Volumes d'activité actuels",
@@ -1630,8 +1630,8 @@
     },
     "customerJourneyCanvas": {
       "title": "Customer Journey Canvas",
-      "purpose": "Quel est le parcours client ou partenaire que l'API est censée soutenir?",
-      "howToUse": "Décrivez un parcours client ou utilisateur réel — pas l'utilisation de l'API — afin de révéler les points de douleur, les objectifs et le contexte. Ces informations aident à définir le type de support API réellement nécessaire plus tard.",
+      "purpose": "Quel parcours client ou partenaire crée le besoin de capacité ou d’interface ?",
+      "howToUse": "Décrire un parcours réel de client, partenaire ou utilisateur, et non l’usage de l’API elle-même. Ce parcours révèle les irritants, objectifs et contextes qui aident à définir les exigences de capacité et d’interface.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "Le client découvre le besoin",
@@ -1643,7 +1643,7 @@
         },
         "pains": {
           "section": "Douleurs",
-          "description": "Quels sont les points de douleur ou défis du client?"
+          "description": "Quels sont les irritants ou défis du client?"
         },
         "journeySteps": {
           "section": "Étapes du parcours",
@@ -1669,8 +1669,8 @@
     },
     "domainCanvas": {
       "title": "Domain Canvas",
-      "purpose": "Quelles sont les entités principales et les règles métier liées à l'API?",
-      "howToUse": "Définissez le modèle de domaine pour chaque API, incluant entités, attributs et relations.",
+      "purpose": "Quels concepts, entités et règles de domaine métier la capacité ou l’interface doit-elle respecter ?",
+      "howToUse": "Définir le modèle de domaine métier pour la capacité ou l’interface, y compris entités, attributs et relations.",
       "sections": {
         "selectedCustomerJourneySteps": {
           "section": "Étapes du parcours client sélectionnées",
@@ -1700,8 +1700,8 @@
     },
     "eventCanvas": {
       "title": "Event Canvas",
-      "purpose": "Quels événements sont pertinents pour l'API et comment sont-ils traités?",
-      "howToUse": "Définissez les événements, leurs déclencheurs et la logique de traitement pour chaque API.",
+      "purpose": "Quels événements sont pertinents pour la capacité ou l’interface, et comment sont-ils traités ?",
+      "howToUse": "Définir les événements, leurs déclencheurs et la logique de traitement pour la capacité ou l’interface.",
       "sections": {
         "userTaskTrigger": {
           "section": "Tâche utilisateur / Déclencheur",
@@ -1713,7 +1713,7 @@
         },
         "processingLogic": {
           "section": "Traitement / Logique",
-          "description": "Décrivez la logique de traitement backend, y compris les validations, transformations ou décisions de routage."
+          "description": "Décrivez la logique de traitement systèmes backend, y compris les validations, transformations ou décisions de routage."
         },
         "outputEventResult": {
           "section": "Sortie / Résultat de l'événement",
@@ -1723,8 +1723,8 @@
     },
     "interactionCanvas": {
       "title": "Interaction Canvas",
-      "purpose": "Quels types d'interactions cette API doit-elle prendre en charge avant de choisir une conception spécifique à un protocole ?",
-      "howToUse": "Identifiez les styles d'interaction réellement nécessaires pour cette API et ceux qui ne relèvent pas de son champ d'application. Utilisez ce canevas pour clarifier l'intention avant de mapper le résultat vers REST, des événements ou GraphQL.",
+      "purpose": "Quels types d’interactions cette capacité ou interface doit-elle prendre en charge avant de choisir une conception propre au protocole ?",
+      "howToUse": "Identifier les styles d’interaction réellement nécessaires et ceux qui sont hors périmètre. Utiliser ce canvas pour clarifier l’intention avant de mapper le résultat vers REST, événements ou GraphQL.",
       "sections": {
         "crudInteractions": {
           "section": "Interactions CRUD",
@@ -1778,8 +1778,8 @@
     },
     "locationsCanvas": {
       "title": "Locations Canvas",
-      "purpose": "Quelles sont les frontières géopolitiques, réglementaires, réseau et de confiance qui affectent cette API ?",
-      "howToUse": "Identifiez où les consommateurs, les fournisseurs et les systèmes dépendants de l'API opèrent sur les réseaux internes, les réseaux partenaires, l'Internet public et les régions réglementées. Décrivez les implications en termes de latence, de confiance, de conformité et de connectivité entre eux.",
+      "purpose": "Quelles frontières géopolitiques, réglementaires, réseau et de confiance affectent cette capacité ou interface ?",
+      "howToUse": "Identifier où les utilisateurs, fournisseurs et systèmes dépendants opèrent dans les réseaux internes, réseaux partenaires, Internet public et régions réglementées. Décrire les implications sur la latence, la confiance, la conformité et la connectivité.",
       "sections": {
         "locationGroups": {
           "section": "Groupes de localisation / de confiance",
@@ -1817,20 +1817,20 @@
     },
     "restCanvas": {
       "title": "REST Canvas",
-      "purpose": "Comment l'API peut-elle être conçue selon les principes REST?",
-      "howToUse": "Définissez les ressources de l'API, les verbes et les exemples de requêtes et réponses.",
+      "purpose": "Comment concevoir l’API selon les principes RESTful ?",
+      "howToUse": "Définissez les ressources de l’API, les verbes et les exemples de requêtes et réponses.",
       "sections": {
         "apiResources": {
           "section": "Ressources API",
-          "description": "Quelles sont les ressources clés exposées par l'API?"
+          "description": "Quelles sont les ressources clés exposées par l’API?"
         },
         "apiResourceModel": {
           "section": "Modèle de ressource API",
-          "description": "Quelle est la structure du modèle de ressources de l'API?"
+          "description": "Quelle est la structure du modèle de ressources de l’API?"
         },
         "apiVerbs": {
           "section": "Verbes API",
-          "description": "Quels verbes HTTP sont utilisés pour interagir avec les ressources de l'API?"
+          "description": "Quels verbes HTTP sont utilisés pour interagir avec les ressources de l’API?"
         },
         "apiVerbExample": {
           "section": "Exemple de verbe API",
@@ -1840,16 +1840,16 @@
     },
     "graphqlCanvas": {
       "title": "GraphQL Canvas",
-      "purpose": "Comment l'API peut-elle être conçue selon les principes GraphQL ?",
-      "howToUse": "Définissez les principaux types, requêtes, mutations et contraintes pour votre API GraphQL.",
+      "purpose": "Comment concevoir l’API selon les principes GraphQL ?",
+      "howToUse": "Définir les types clés, requêtes, mutations et contraintes pour l’API GraphQL.",
       "sections": {
         "apiName": {
-          "section": "Nom de l'API",
-          "description": "Quel est le nom de l'API GraphQL ou du point de terminaison ?"
+          "section": "Nom de l’API",
+          "description": "Quel est le nom de l’API GraphQL ou du point de terminaison ?"
         },
         "consumerGoals": {
-          "section": "Objectifs des consommateurs",
-          "description": "Quels problèmes les consommateurs de l'API cherchent-ils à résoudre ? Quelles données leur sont nécessaires ?"
+          "section": "Objectifs des utilisateurs",
+          "description": "Quels problèmes les utilisateurs de l’API cherchent-ils à résoudre ? Quelles données leur sont nécessaires ?"
         },
         "keyTypes": {
           "section": "Types clés",
@@ -1869,141 +1869,141 @@
         },
         "subscriptions": {
           "section": "Abonnements",
-          "description": "Existe-t-il des mises à jour en temps réel ou des événements auxquels les consommateurs peuvent s'abonner ?"
+          "description": "Existe-t-il des mises à jour en temps réel ou des événements auxquels les utilisateurs peuvent s'abonner ?"
         },
         "authorizationRules": {
           "section": "Règles d'autorisation",
           "description": "Qui peut accéder à quels champs ou types ?"
         },
         "consumerConstraints": {
-          "section": "Contraintes des consommateurs",
+          "section": "Contraintes des utilisateurs",
           "description": "Y a-t-il des contraintes de pagination, de filtrage ou de limitation du débit ?"
         },
         "openQuestions": {
           "section": "Notes / Questions ouvertes",
-          "description": "Y a-t-il des décisions en attente ou des considérations d'intégration ?"
+          "description": "Y a-t-il des décisions en attente ou des considérations d’intégration ?"
         }
       }
     },
     "capabilityValuePropositionCanvas": {
       "title": "Capability Value Proposition Canvas",
-      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
-      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "purpose": "Quelle capacité réutilisable créerait de la valeur pour les utilisateurs sans décider encore si elle doit être mise à disposition sous forme d’API, d’événement, de fichier, de flux, de produit de données ou d’un autre style d’intégration ?",
+      "howToUse": "Partir des tâches et résultats attendus des utilisateurs. Capturer les fonctionnalités de capacité qui créent des gains et réduisent les irritants, puis décrire les capacités réutilisables candidates sans nommer la technologie trop tôt.",
       "sections": {
         "consumerTasks": {
-          "section": "Consumer tasks and outcomes",
-          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+          "section": "Tâches et résultats des utilisateurs",
+          "description": "Que cherchent à accomplir les utilisateurs, partenaires, systèmes ou équipes ?"
         },
         "gainEnablingCapabilities": {
-          "section": "Gain-enabling capability features",
-          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+          "section": "Fonctionnalités de capacité génératrices de gains",
+          "description": "Quelles fonctionnalités de capacité aideraient les utilisateurs à obtenir de meilleurs résultats, plus de rapidité, d’automatisation, d’insights, de portée ou de conformité ?"
         },
         "painRelievingCapabilities": {
-          "section": "Pain-relieving capability features",
-          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+          "section": "Fonctionnalités de capacité qui réduisent les irritants",
+          "description": "Quelles fonctionnalités de capacité supprimeraient les frictions, le travail manuel, les erreurs, les retards, les risques ou l’incertitude pour les utilisateurs ?"
         },
         "reusableCapabilities": {
-          "section": "Reusable capabilities",
-          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+          "section": "Capacités réutilisables",
+          "description": "Quelles capacités métier ou données réutilisables pourraient répondre à ces tâches, gains et irritants pour plusieurs utilisateurs ou cas d’usage ?"
         }
       }
     },
     "capabilityBusinessModelCanvas": {
       "title": "Capability Business Model Canvas",
-      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
-      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "purpose": "Dans quelle mesure cette capacité d’intégration doit-elle être viable, réutilisable, financée, possédée, accompagnée et découvrable ?",
+      "howToUse": "Résumer la proposition de valeur de la capacité, identifier les utilisateurs et canaux d’engagement, puis cartographier propriété, activités, ressources, partenaires, bénéfices et coûts.",
       "sections": {
         "keyPartners": {
-          "section": "Key partners",
-          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+          "section": "Partenaires clés",
+          "description": "Quels partenaires métier, technologie, données, sécurité, juridique, plateforme ou externes sont nécessaires pour faire fonctionner la capacité ?"
         },
         "keyActivities": {
-          "section": "Key activities",
-          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+          "section": "Activités clés",
+          "description": "Que doivent faire le responsable de la capacité et les producteurs pour concevoir, mettre à disposition, gouverner, accompagner et améliorer la capacité ?"
         },
         "keyResources": {
-          "section": "Key resources",
-          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+          "section": "Ressources clés",
+          "description": "Quels systèmes, actifs de données, plateformes, personnes, standards, financements et capacités opérationnelles sont nécessaires ?"
         },
         "capabilityValueProposition": {
-          "section": "Capability value proposition",
-          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+          "section": "Proposition de valeur de la capacité",
+          "description": "Quelle valeur cette capacité réutilisable apporte-t-elle aux utilisateurs et à l’organisation ou à l’écosystème ?"
         },
         "consumerEngagement": {
-          "section": "Consumer engagement",
-          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+          "section": "Engagement des utilisateurs",
+          "description": "Comment les utilisateurs découvriront-ils, évalueront-ils, demanderont-ils, onboarderont-ils, obtiendront-ils du support et donneront-ils du feedback sur la capacité ?"
         },
         "channels": {
-          "section": "Channels",
-          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+          "section": "Canaux",
+          "description": "Par quels catalogues, portails, marketplaces, sites de documentation, parcours de support ou processus de gouvernance les utilisateurs interagiront-ils avec la capacité ?"
         },
         "capabilityConsumerSegments": {
-          "section": "Capability consumer segments",
-          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+          "section": "Segments d’utilisateurs de la capacité",
+          "description": "Qui sont les utilisateurs actuels et potentiels de la capacité, y compris équipes, partenaires, systèmes, produits ou utilisateurs de données ?"
         },
         "costs": {
-          "section": "Costs",
-          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+          "section": "Coûts",
+          "description": "Quels sont les coûts significatifs de construction, d’exploitation, de gouvernance, de support et d’évolution de la capacité ?"
         },
         "benefits": {
-          "section": "Benefits",
-          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+          "section": "Bénéfices",
+          "description": "Quels bénéfices métier, opérationnels, écosystémiques, de réutilisation, de conformité ou de coût justifient la capacité ?"
         }
       }
     },
     "consumerExperienceRequirementsCanvas": {
       "title": "Consumer Experience Requirements Canvas",
-      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
-      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "purpose": "Quelles exigences d’expérience et non fonctionnelles les utilisateurs doivent-ils préciser avant de décider de la meilleure architecture d’intégration ?",
+      "howToUse": "Utiliser ce canvas comme tableau d’exigences indépendant de la technologie. Capturer les attentes et contraintes des utilisateurs, puis utiliser les implications d’architecture pour choisir API, événements, fichiers, flux, produits de données ou un autre pattern.",
       "sections": {
         "consumerGoals": {
-          "section": "Consumer goals",
-          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+          "section": "Objectifs des utilisateurs",
+          "description": "Quels sont les objectifs métier, de workflow, de décision, d’automatisation ou d’usage des données des utilisateurs ?"
         },
         "availabilityAndTimeliness": {
-          "section": "Availability and timeliness",
-          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+          "section": "Disponibilité et fraîcheur",
+          "description": "Quand la capacité doit-elle être disponible, quelle fraîcheur d’information est nécessaire et quelles fenêtres de latence ou de mise à disposition comptent ?"
         },
         "volumeAndPerformance": {
-          "section": "Volume and performance",
-          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+          "section": "Volume et performance",
+          "description": "Quels volumes de requêtes, événements, enregistrements, fichiers, lots, utilisateurs ou transactions la capacité doit-elle supporter aujourd’hui et demain ?"
         },
         "dataQualityAndConsistency": {
-          "section": "Data quality and consistency",
-          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+          "section": "Qualité et cohérence des données",
+          "description": "Quelles attentes les utilisateurs ont-ils en matière d’exactitude, complétude, cohérence, ordre, déduplication, rapprochement ou validation ?"
         },
         "securityPrivacyAndCompliance": {
-          "section": "Security, privacy, and compliance",
-          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+          "section": "Sécurité, protection des données et conformité",
+          "description": "Quelles contraintes d’identité, d’autorisation, de confidentialité, de résidence, de consentement, de conservation, d’audit ou de réglementation s’appliquent ?"
         },
         "onboardingAndAccess": {
-          "section": "Onboarding and access",
-          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+          "section": "Onboarding et accès",
+          "description": "Comment les utilisateurs doivent-ils trouver, demander, tester, obtenir l’approbation et commencer à utiliser la capacité ?"
         },
         "changeAndVersioning": {
-          "section": "Change and versioning",
-          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+          "section": "Changement et versionnement",
+          "description": "Quelle tolérance au changement les utilisateurs ont-ils, et quelles attentes de préavis, compatibilité, migration ou versionnement s’appliquent ?"
         },
         "observabilityAndSupport": {
-          "section": "Observability and support",
-          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+          "section": "Observabilité et support",
+          "description": "De quelle surveillance, information de statut, traçabilité, visibilité sur la qualité des données, support, propriété et communication d’incident les utilisateurs ont-ils besoin ?"
         },
         "recoveryAndContinuity": {
-          "section": "Recovery and continuity",
-          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+          "section": "Reprise et continuité",
+          "description": "Quelles attentes de replay, retry, rapprochement, sauvegarde, fallback, continuité ou reprise manuelle doivent être prises en charge ?"
         },
         "architectureImplications": {
-          "section": "Architecture implications",
-          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+          "section": "Implications d’architecture",
+          "description": "Que signifient ces exigences pour les styles d’architecture possibles, tels que API, événements, fichiers, flux, produits de données ou intégration directe ?"
         }
       }
     }
   },
   "pt": {
     "apiBusinessModelCanvas": {
-      "title": "API Business Model Canvas",
-      "purpose": "Qual será a viabilidade e a reutilização desta API? Temos um caso de negócios do ponto de vista de custo-benefício?",
-      "howToUse": "Resuma a proposta de valor de uma API a partir do API Value Proposition Canvas e siga a sequência numerada.",
+      "title": "Canvas do Modelo de Negócio da API",
+      "purpose": "Qual será a viabilidade e a reutilização desta API? Temos um caso de negócio do ponto de vista de custo-benefício?",
+      "howToUse": "Resuma a proposta de valor de uma API a partir do Canvas da Proposta de Valor da API e siga a sequência numerada.",
       "sections": {
         "keyPartners": {
           "section": "Parceiros-chave",
@@ -2011,23 +2011,23 @@
         },
         "keyActivities": {
           "section": "Atividades-chave",
-          "description": "Quais são as ações mais importantes que o provedor da API deve realizar para operar com sucesso?"
+          "description": "Quais são as ações mais importantes que o fornecedor da API deve realizar para operar com sucesso?"
         },
         "keyResources": {
           "section": "Recursos-chave",
-          "description": "Que ativos estratégicos exclusivos o provedor da API deve adquirir ou construir?"
+          "description": "Que ativos estratégicos exclusivos deve o fornecedor da API adquirir ou construir?"
         },
         "apiValueProposition": {
           "section": "Proposta de valor da API",
-          "description": "Comece com um post-it nomeando a API ou a família de APIs e, em seguida, anote o valor que a API oferece aos seus consumidores."
+          "description": "Comece com uma nota adesiva que nomeie a API ou a família de APIs e, em seguida, anote o valor que a API oferece aos seus consumidores."
         },
         "developerRelations": {
-          "section": "Relações com desenvolvedores",
-          "description": "Como o provedor da API alcança e oferece suporte aos consumidores da API?"
+          "section": "Relações com programadores",
+          "description": "Como o fornecedor da API alcança e oferece apoio aos consumidores da API?"
         },
         "channels": {
           "section": "Canais",
-          "description": "Por meio de quais mecanismos os consumidores da API interagem com a API?"
+          "description": "Através de quais mecanismos os consumidores da API interagem com a API?"
         },
         "apiConsumerSegments": {
           "section": "Segmentos de consumidores da API",
@@ -2035,7 +2035,7 @@
         },
         "costs": {
           "section": "Custos",
-          "description": "Quais são os custos significativos envolvidos na construção, implantação e operação da API?"
+          "description": "Quais são os custos significativos envolvidos na construção, disponibilização e operação da API?"
         },
         "benefits": {
           "section": "Benefícios",
@@ -2044,21 +2044,21 @@
       }
     },
     "apiValuePropositionCanvas": {
-      "title": "API Value Proposition Canvas",
-      "purpose": "Como a jornada do cliente se relaciona com as APIs? Quais dificuldades e benefícios dos usuários finais e consumidores de API precisam ser abordados?",
-      "howToUse": "Descreva a perspectiva dos usuários finais, começando com suas tarefas, depois suas dificuldades e benefícios e os dos consumidores de API e, finalmente, os produtos e recursos da API.",
+      "title": "Canvas da Proposta de Valor da API",
+      "purpose": "Como a jornada do cliente se relaciona com as APIs? Quais dificuldades e benefícios dos utilizadores finais e consumidores de API precisam ser abordados?",
+      "howToUse": "Descreva a perspetiva dos utilizadores finais, começando pelas suas tarefas, depois as suas dificuldades e benefícios e os dos consumidores de API e, finalmente, os produtos e funcionalidades da API.",
       "sections": {
         "tasks": {
           "section": "Tarefas",
-          "description": "O que os clientes (usuários finais) estão tentando alcançar?"
+          "description": "O que os clientes (utilizadores finais) estão a tentar alcançar?"
         },
         "gainEnablingFeatures": {
           "section": "Recursos que possibilitam ganhos",
-          "description": "Quais recursos permitem que os usuários finais e consumidores de API alcancem ganhos?"
+          "description": "Que funcionalidades permitem que os utilizadores finais e consumidores de API alcancem ganhos?"
         },
         "painRelievingFeatures": {
           "section": "Recursos que aliviam dificuldades",
-          "description": "Quais recursos ajudam os usuários finais e os consumidores da API a superar dificuldades?"
+          "description": "Que funcionalidades ajudam os utilizadores finais e os consumidores da API a superar dificuldades?"
         },
         "apiProducts": {
           "section": "Produtos API",
@@ -2067,8 +2067,8 @@
       }
     },
     "businessImpactCanvas": {
-      "title": "Business Impact Canvas",
-      "purpose": "Quais são os possíveis impactos nos negócios da falha da API?",
+      "title": "Canvas de Impacto no Negócio",
+      "purpose": "Quais são os possíveis impactos no negócio da falha da API?",
       "howToUse": "Considere o impacto potencial na disponibilidade, segurança e dados para cada API.",
       "sections": {
         "availabilityRisks": {
@@ -2085,20 +2085,20 @@
         },
         "mitigateAvailabilityRisks": {
           "section": "Mitigar riscos de disponibilidade",
-          "description": "Como o provedor da API pode mitigar os riscos de disponibilidade?"
+          "description": "Como o fornecedor da API pode mitigar os riscos de disponibilidade?"
         },
         "mitigateSecurityRisks": {
           "section": "Mitigar riscos de segurança",
-          "description": "Como o provedor da API pode mitigar os riscos de segurança?"
+          "description": "Como o fornecedor da API pode mitigar os riscos de segurança?"
         },
         "mitigateDataRisks": {
           "section": "Mitigar riscos de dados",
-          "description": "Como o provedor da API pode mitigar os riscos de dados?"
+          "description": "Como o fornecedor da API pode mitigar os riscos de dados?"
         }
       }
     },
     "capacityCanvas": {
-      "title": "Capacity Canvas",
+      "title": "Canvas de Capacidade",
       "purpose": "Quanta capacidade é necessária para suportar o consumo da API?",
       "howToUse": "Analise os requisitos de capacidade atuais e futuros para cada API.",
       "sections": {
@@ -2119,8 +2119,8 @@
           "description": "Quais estratégias de cache podem ser usadas para otimizar o desempenho?"
         },
         "rateLimitingStrategies": {
-          "section": "Estratégias de limitação de taxa",
-          "description": "Que estratégias de limitação de taxa podem ser usadas para gerenciar o consumo?"
+          "section": "Estratégias de limitação de pedidos",
+          "description": "Que estratégias de limitação de pedidos podem ser usadas para gerir o consumo?"
         },
         "scalingStrategies": {
           "section": "Estratégias de dimensionamento",
@@ -2129,9 +2129,9 @@
       }
     },
     "customerJourneyCanvas": {
-      "title": "Customer Journey Canvas",
+      "title": "Canvas do Percurso do Cliente",
       "purpose": "Qual é a jornada do cliente ou parceiro que a API pretende apoiar?",
-      "howToUse": "Descreva uma jornada real de um cliente ou usuário — não o uso da API — para revelar pontos fracos, objetivos e contexto. Essa informação ajuda a definir que tipo de suporte de API será realmente necessário mais tarde.",
+      "howToUse": "Descreva uma jornada real de um cliente ou utilizador — não o uso da API — para revelar pontos fracos, objetivos e contexto. Esta informação ajuda a definir que tipo de apoio de API será realmente necessário mais tarde.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "O cliente descobre a necessidade",
@@ -2139,7 +2139,7 @@
         },
         "persona": {
           "section": "Persona",
-          "description": "Quem é o cliente típico que passa por essa jornada?"
+          "description": "Quem é o cliente típico que passa por esta jornada?"
         },
         "pains": {
           "section": "Dores",
@@ -2168,8 +2168,8 @@
       }
     },
     "domainCanvas": {
-      "title": "Domain Canvas",
-      "purpose": "Quais são as entidades principais e as regras de negócios relacionadas à API?",
+      "title": "Canvas de Domínio",
+      "purpose": "Quais são as entidades principais e as regras de negócio relacionadas com a API?",
       "howToUse": "Defina o modelo de domínio para cada API, incluindo entidades, atributos e relações.",
       "sections": {
         "selectedCustomerJourneySteps": {
@@ -2189,23 +2189,23 @@
           "description": "Quais são as relações entre as entidades?"
         },
         "businessComplianceAndIntegrityRules": {
-          "section": "Regras de negócios, conformidade e integridade",
-          "description": "Quais são as regras de negócios, conformidade e integridade relacionadas às entidades?"
+          "section": "Regras de negócio, conformidade e integridade",
+          "description": "Quais são as regras de negócio, conformidade e integridade relacionadas com as entidades?"
         },
         "securityAndPrivacyConsiderations": {
           "section": "Considerações sobre segurança e privacidade",
-          "description": "Quais são as considerações sobre segurança e privacidade relacionadas às entidades?"
+          "description": "Quais são as considerações sobre segurança e privacidade relacionadas com as entidades?"
         }
       }
     },
     "eventCanvas": {
-      "title": "Event Canvas",
+      "title": "Canvas de Eventos",
       "purpose": "Quais eventos são relevantes para a API e como são processados?",
-      "howToUse": "Defina os eventos, seus gatilhos e a lógica de processamento para cada API.",
+      "howToUse": "Defina os eventos, os seus acionadores e a lógica de processamento para cada API.",
       "sections": {
         "userTaskTrigger": {
-          "section": "Tarefa do usuário/gatilho",
-          "description": "Que ação do usuário ou evento do sistema aciona essa operação de evento?"
+          "section": "Tarefa do utilizador/gatilho",
+          "description": "Que ação do utilizador ou evento do sistema aciona esta operação de evento?"
         },
         "inputEventPayload": {
           "section": "Entrada / Carga útil do evento",
@@ -2222,9 +2222,9 @@
       }
     },
     "interactionCanvas": {
-      "title": "Interaction Canvas",
-      "purpose": "Que tipos de interações esta API deve suportar antes de escolher um projeto específico para o protocolo?",
-      "howToUse": "Identifique quais estilos de interação são realmente necessários para esta API e quais estão fora do escopo. Use esta tela para esclarecer a intenção antes de mapear o resultado para REST, eventos ou GraphQL.",
+      "title": "Canvas de Interação",
+      "purpose": "Que tipos de interações esta API deve suportar antes de escolher uma conceção específica para o protocolo?",
+      "howToUse": "Identifique que estilos de interação são realmente necessários para esta API e quais estão fora do âmbito. Utilize este canvas para esclarecer a intenção antes de mapear o resultado para REST, eventos ou GraphQL.",
       "sections": {
         "crudInteractions": {
           "section": "Interações CRUD",
@@ -2240,7 +2240,7 @@
         },
         "queryDrivenInteractions": {
           "section": "Interações orientadas por consulta",
-          "description": "Quais interações de leitura ou consulta são necessárias para responder às perguntas dos usuários?"
+          "description": "Quais interações de leitura ou consulta são necessárias para responder às perguntas dos utilizadores?"
         },
         "queryDrivenInputOutputModels": {
           "section": "Modelos de entrada e saída orientados por consulta",
@@ -2277,13 +2277,13 @@
       }
     },
     "locationsCanvas": {
-      "title": "Location Canvas",
-      "purpose": "“Quais limites geopolíticos, regulatórios, de rede e de confiança afetam esta API?",
-      "howToUse": "Identifique onde os consumidores, provedores e sistemas dependentes da API operam em redes internas, redes de parceiros, internet pública e regiões regulamentadas. Descreva as implicações de latência, confiança, conformidade e conectividade entre eles.",
+      "title": "Canvas de Localizações",
+      "purpose": "Que fronteiras geopolíticas, regulamentares, de rede e de confiança afetam esta API?",
+      "howToUse": "Identifique onde os consumidores, fornecedores e sistemas dependentes da API operam em redes internas, redes de parceiros, internet pública e regiões regulamentadas. Descreva as implicações de latência, confiança, conformidade e conectividade entre eles.",
       "sections": {
         "locationGroups": {
           "section": "Grupos de Localização / Confiança",
-          "description": "Quais são os grupos geopolíticos, regulatórios, de rede ou de confiança relevantes?"
+          "description": "Quais são os grupos geopolíticos, regulamentares, de rede ou de confiança relevantes?"
         },
         "locationGroupCharacteristics": {
           "section": "Características do grupo",
@@ -2316,9 +2316,9 @@
       }
     },
     "restCanvas": {
-      "title": "REST Canvas",
-      "purpose": "Como a API pode ser projetada usando os princípios RESTful?",
-      "howToUse": "Defina os recursos, verbos e exemplos de solicitações e respostas da API.",
+      "title": "Canvas REST",
+      "purpose": "Como a API pode ser concebida usando os princípios RESTful?",
+      "howToUse": "Defina os recursos, verbos e exemplos de pedidos e respostas da API.",
       "sections": {
         "apiResources": {
           "section": "Recursos da API",
@@ -2334,14 +2334,14 @@
         },
         "apiVerbExample": {
           "section": "Exemplo de verbo da API",
-          "description": "Forneça um exemplo de solicitação e resposta da API para cada verbo."
+          "description": "Forneça um exemplo de pedido e resposta da API para cada verbo."
         }
       }
     },
     "graphqlCanvas": {
-      "title": "GraphQL Canvas",
-      "purpose": "Como a API pode ser projetada usando os princípios do GraphQL?",
-      "howToUse": "Defina os tipos de chave, consultas, mutações e restrições para sua API GraphQL.",
+      "title": "Canvas GraphQL",
+      "purpose": "Como a API pode ser concebida usando os princípios do GraphQL?",
+      "howToUse": "Defina os tipos-chave, consultas, mutações e restrições para a sua API GraphQL.",
       "sections": {
         "apiName": {
           "section": "Nome da API",
@@ -2349,11 +2349,11 @@
         },
         "consumerGoals": {
           "section": "Objetivos do consumidor",
-          "description": "Quais problemas os consumidores da API estão tentando resolver? De quais dados eles precisam?"
+          "description": "Que problemas os consumidores da API estão a tentar resolver? De que dados precisam?"
         },
         "keyTypes": {
           "section": "Tipos de chave",
-          "description": "Quais são os tipos principais expostos (por exemplo, Usuário, Pedido, Produto)?"
+          "description": "Quais são os tipos principais expostos (por exemplo, Utilizador, Pedido, Produto)?"
         },
         "relationships": {
           "section": "Relações",
@@ -2377,7 +2377,7 @@
         },
         "consumerConstraints": {
           "section": "Restrições do consumidor",
-          "description": "Existem restrições de paginação, filtragem ou limitação de taxa?"
+          "description": "Existem restrições de paginação, filtragem ou limitação de pedidos?"
         },
         "openQuestions": {
           "section": "Notas/Questões em aberto",
@@ -2386,115 +2386,115 @@
       }
     },
     "capabilityValuePropositionCanvas": {
-      "title": "Capability Value Proposition Canvas",
-      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
-      "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
+      "title": "Canvas da Proposta de Valor da Capacidade",
+      "purpose": "Que capacidade reutilizável criaria valor para os consumidores sem decidir ainda se deve ser disponibilizada como API, evento, ficheiro, stream, produto de dados ou outro estilo de integração?",
+      "howToUse": "Comece pelas tarefas e resultados dos consumidores. Capte funcionalidades da capacidade que permitem ganhos e aliviam dores; depois descreva capacidades reutilizáveis candidatas sem nomear a tecnologia demasiado cedo.",
       "sections": {
         "consumerTasks": {
-          "section": "Consumer tasks and outcomes",
-          "description": "What are consumers, partners, users, systems, or teams trying to achieve?"
+          "section": "Tarefas e resultados dos consumidores",
+          "description": "O que os consumidores, parceiros, utilizadores, sistemas ou equipas estão a tentar alcançar?"
         },
         "gainEnablingCapabilities": {
-          "section": "Gain-enabling capability features",
-          "description": "What capability features would help consumers achieve better outcomes, speed, automation, insight, reach, or compliance?"
+          "section": "Funcionalidades da capacidade que permitem ganhos",
+          "description": "Que funcionalidades da capacidade ajudariam os consumidores a alcançar melhores resultados, rapidez, automação, conhecimento, alcance ou conformidade?"
         },
         "painRelievingCapabilities": {
-          "section": "Pain-relieving capability features",
-          "description": "What capability features would remove friction, manual work, errors, delays, risk, or uncertainty for consumers?"
+          "section": "Funcionalidades da capacidade que aliviam dores",
+          "description": "Que funcionalidades da capacidade removeriam atrito, trabalho manual, erros, atrasos, risco ou incerteza para os consumidores?"
         },
         "reusableCapabilities": {
-          "section": "Reusable capabilities",
-          "description": "What reusable business or data capabilities could serve these tasks, gains, and pains across more than one consumer or use case?"
+          "section": "Capacidades reutilizáveis",
+          "description": "Que capacidades de negócio ou de dados reutilizáveis poderiam servir estas tarefas, ganhos e dores em mais do que um consumidor ou caso de utilização?"
         }
       }
     },
     "capabilityBusinessModelCanvas": {
-      "title": "Capability Business Model Canvas",
-      "purpose": "How viable, reusable, funded, owned, supported, and discoverable should this integration capability be?",
-      "howToUse": "Summarize the capability value proposition, identify consumers and engagement channels, then map ownership, activities, resources, partners, benefits, and costs.",
+      "title": "Canvas do Modelo de Negócio da Capacidade",
+      "purpose": "Quão viável, reutilizável, financiada, atribuída, apoiada e detetável deve ser esta capacidade de integração?",
+      "howToUse": "Resuma a proposta de valor da capacidade, identifique consumidores e canais de envolvimento, e depois mapeie propriedade, atividades, recursos, parceiros, benefícios e custos.",
       "sections": {
         "keyPartners": {
-          "section": "Key partners",
-          "description": "Which business, technology, data, security, legal, platform, or external partners are needed to make the capability work?"
+          "section": "Parceiros-chave",
+          "description": "Que parceiros de negócio, tecnologia, dados, segurança, jurídico, plataforma ou externos são necessários para que a capacidade funcione?"
         },
         "keyActivities": {
-          "section": "Key activities",
-          "description": "What must the capability owner and producers do to design, deliver, govern, support, and improve the capability?"
+          "section": "Atividades-chave",
+          "description": "O que o responsável pela capacidade e os produtores devem fazer para conceber, entregar, governar, apoiar e melhorar a capacidade?"
         },
         "keyResources": {
-          "section": "Key resources",
-          "description": "Which systems, data assets, platforms, people, standards, funding, and operational capabilities are required?"
+          "section": "Recursos-chave",
+          "description": "Que sistemas, ativos de dados, plataformas, pessoas, normas, financiamento e capacidades operacionais são necessários?"
         },
         "capabilityValueProposition": {
-          "section": "Capability value proposition",
-          "description": "What value does this reusable capability provide to consumers and to the organization or ecosystem?"
+          "section": "Proposta de valor da capacidade",
+          "description": "Que valor esta capacidade reutilizável oferece aos consumidores e à organização ou ecossistema?"
         },
         "consumerEngagement": {
-          "section": "Consumer engagement",
-          "description": "How will consumers discover, evaluate, request, onboard, get support for, and provide feedback on the capability?"
+          "section": "Envolvimento dos consumidores",
+          "description": "Como irão os consumidores descobrir, avaliar, solicitar, integrar-se, obter apoio e dar feedback sobre a capacidade?"
         },
         "channels": {
-          "section": "Channels",
-          "description": "Through which catalogs, portals, marketplaces, documentation sites, support paths, or governance processes will consumers interact with the capability?"
+          "section": "Canais",
+          "description": "Através de que catálogos, portais, marketplaces, sites de documentação, caminhos de apoio ou processos de governação os consumidores irão interagir com a capacidade?"
         },
         "capabilityConsumerSegments": {
-          "section": "Capability consumer segments",
-          "description": "Who are the current and potential consumers of the capability, including teams, partners, systems, products, or data users?"
+          "section": "Segmentos de consumidores da capacidade",
+          "description": "Quem são os consumidores atuais e potenciais da capacidade, incluindo equipas, parceiros, sistemas, produtos ou utilizadores de dados?"
         },
         "costs": {
-          "section": "Costs",
-          "description": "What are the significant costs of building, operating, governing, supporting, and evolving the capability?"
+          "section": "Custos",
+          "description": "Quais são os custos significativos de construir, operar, governar, apoiar e evoluir a capacidade?"
         },
         "benefits": {
-          "section": "Benefits",
-          "description": "What business, operational, ecosystem, reuse, compliance, or cost benefits justify the capability?"
+          "section": "Benefícios",
+          "description": "Que benefícios de negócio, operacionais, de ecossistema, reutilização, conformidade ou custo justificam a capacidade?"
         }
       }
     },
     "consumerExperienceRequirementsCanvas": {
-      "title": "Consumer Experience Requirements Canvas",
-      "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
-      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "title": "Canvas de Requisitos da Experiência do Consumidor",
+      "purpose": "Que requisitos de experiência e requisitos não funcionais os consumidores precisam de esclarecer antes de decidir a melhor arquitetura de integração?",
+      "howToUse": "Utilize isto como uma tabela de requisitos independente da tecnologia. Capte expectativas e restrições dos consumidores; depois utilize as implicações de arquitetura para escolher APIs, eventos, ficheiros, streams, produtos de dados ou outro padrão.",
       "sections": {
         "consumerGoals": {
-          "section": "Consumer goals",
-          "description": "What are the consumer's business goals, workflow goals, decision goals, automation goals, or data usage goals?"
+          "section": "Objetivos dos consumidores",
+          "description": "Quais são os objetivos de negócio, de fluxo de trabalho, de decisão, de automação ou de utilização de dados dos consumidores?"
         },
         "availabilityAndTimeliness": {
-          "section": "Availability and timeliness",
-          "description": "When must the capability be available, how fresh must information be, and what latency or delivery windows matter?"
+          "section": "Disponibilidade e atualidade",
+          "description": "Quando é que a capacidade deve estar disponível, quão atualizada deve estar a informação e que latência ou janelas de entrega importam?"
         },
         "volumeAndPerformance": {
-          "section": "Volume and performance",
-          "description": "What request, event, record, file, batch, user, or transaction volumes must the capability support now and later?"
+          "section": "Volume e desempenho",
+          "description": "Que volumes de pedidos, eventos, registos, ficheiros, lotes, utilizadores ou transações a capacidade deve suportar agora e no futuro?"
         },
         "dataQualityAndConsistency": {
-          "section": "Data quality and consistency",
-          "description": "What accuracy, completeness, consistency, ordering, deduplication, reconciliation, or validation expectations do consumers have?"
+          "section": "Qualidade e consistência dos dados",
+          "description": "Que expectativas de exatidão, completude, consistência, ordenação, deduplicação, reconciliação ou validação têm os consumidores?"
         },
         "securityPrivacyAndCompliance": {
-          "section": "Security, privacy, and compliance",
-          "description": "What identity, authorization, confidentiality, residency, consent, retention, audit, or regulatory constraints apply?"
+          "section": "Segurança, privacidade e conformidade",
+          "description": "Que restrições de identidade, autorização, confidencialidade, residência, consentimento, retenção, auditoria ou regulamentação se aplicam?"
         },
         "onboardingAndAccess": {
-          "section": "Onboarding and access",
-          "description": "How should consumers find, request, test, get approved for, and start using the capability?"
+          "section": "Integração e acesso",
+          "description": "Como devem os consumidores encontrar, solicitar, testar, obter aprovação e começar a utilizar a capacidade?"
         },
         "changeAndVersioning": {
-          "section": "Change and versioning",
-          "description": "How much change tolerance do consumers have, and what notice, compatibility, migration, or versioning expectations apply?"
+          "section": "Mudança e controlo de versões",
+          "description": "Que tolerância à mudança têm os consumidores e que expectativas de aviso prévio, compatibilidade, migração ou controlo de versões se aplicam?"
         },
         "observabilityAndSupport": {
-          "section": "Observability and support",
-          "description": "What monitoring, status, traceability, data quality visibility, support, ownership, and incident communication do consumers need?"
+          "section": "Observabilidade e apoio",
+          "description": "Que monitorização, estado, rastreabilidade, visibilidade da qualidade dos dados, apoio, propriedade e comunicação de incidentes os consumidores precisam?"
         },
         "recoveryAndContinuity": {
-          "section": "Recovery and continuity",
-          "description": "What replay, retry, reconciliation, backup, fallback, continuity, or manual recovery expectations must be supported?"
+          "section": "Recuperação e continuidade",
+          "description": "Que expectativas de repetição, nova tentativa, reconciliação, cópia de segurança, fallback, continuidade ou recuperação manual devem ser suportadas?"
         },
         "architectureImplications": {
-          "section": "Architecture implications",
-          "description": "What do these requirements imply for possible architecture styles, such as APIs, events, files, streams, data products, or direct integration?"
+          "section": "Implicações de arquitetura",
+          "description": "O que estes requisitos implicam para possíveis estilos de arquitetura, como APIs, eventos, ficheiros, streams, produtos de dados ou integração direta?"
         }
       }
     }
diff --git a/src/data/method/de/labels.criteria.json b/src/data/method/de/labels.criteria.json
index 4657d51..60fdeaf 100644
--- a/src/data/method/de/labels.criteria.json
+++ b/src/data/method/de/labels.criteria.json
@@ -1,25 +1,25 @@
 {
   "exit_criteria": "Austrittskriterien",
   "entry_criteria": "Eintrittskriterien",
-  "criterion.metrics-feedback-available": "Relevante Marktsignale, Feedback oder operative Erkenntnisse sind verfügbar, um diese API-Möglichkeit zu steuern.",
-  "criterion.business-goals-defined": "Geschäftsziele sind definiert",
-  "criterion.market-research-done": "Marktforschung identifiziert API-Möglichkeiten",
-  "criterion.stakeholder-approval": "Relevante Stakeholder stimmen zu, dass diese API-Möglichkeit es wert ist, sie zu erkunden und Priorität einzuräumen.",
-  "criterion.api-opportunity-documented": "Individuelle API-Möglichkeiten werden identifiziert und dokumentiert",
-  "criterion.api-reusability": "Die API erfüllt einen klaren Geschäftsbedarf und ist für mehrere API-Nutzer wiederverwendbar",
-  "criterion.hide-backend-discrepancies": "Die API ist dazu gedacht, Verbraucher vor Backend-Komplexität und Inkonsistenzen zu schützen.",
-  "criterion.value-prop-validated": "Die API-Wert proposition wurde mit den relevanten Geschäft und Verbraucher-Stakeholdern überprüft und validiert.",
-  "criterion.consumer-segments-identified": "API-Nutzersegmente (intern und extern) werden identifiziert.",
-  "criterion.api-roadmap-defined": "Hochrangige Roadmaps für die API-Entwicklung werden erstellt.",
-  "criterion.architecture-patterns-validated": "Die gewählten API-Architektur- und Plattformmuster wurden mit den relevanten Architektur-, Sicherheits- und Plattform-Stakeholdern validiert.",
-  "criterion.design-reflects-business-value": "Die API-Design und die offengelegten Funktionen spiegeln klar den Geschäftswert und die Bedürfnisse der Benutzer wider.",
-  "criterion.api-consistency": "Das API-Design folgt unseren gemeinsamen API-Produkt- und Design-Vorgaben.",
-  "criterion.api-contract-tested": "Der API-Vertrag wurde getestet und erfüllt die funktionalen und nicht-funktionalen Anforderungen.",
-  "criterion.api-description-available": "Die API und ihre offengelegten Funktionen sind ausreichend beschrieben für Überprüfung, Auditierung und Onboarding.",
-  "criterion.audit-passed": "Die API besteht Compliance-, Sicherheits- und Audit-Prüfungen.",
-  "criterion.audit-reports-shared": "API-Auditberichte wurden mit relevanten Stakeholdern geteilt.",
-  "criterion.api-ready-for-publishing": "Die API ist bereit, für Verbraucher verfügbar gemacht zu werden.",
-  "criterion.api-documentation-ready": "Die API-Dokumentation ist vollständig und für die Veröffentlichung und das Onboarding geeignet.",
-  "criterion.consumer-support-ready": "Registrierungs-, Support- und Kommunikationsprozesse sind für API-Nutzer bereit.",
-  "criterion.legal-compliance-clear": "Rechtliche, datenschutzrechtliche und Compliance-Anforderungen für die Veröffentlichung sind definiert und verstanden."
-}
\ No newline at end of file
+  "criterion.metrics-feedback-available": "Relevante Marktsignale, Feedback oder operative Erkenntnisse liegen vor, um diese Capability-Möglichkeit zu bewerten.",
+  "criterion.business-goals-defined": "Die Geschäftsziele sind definiert.",
+  "criterion.market-research-done": "Die Marktrecherche identifiziert relevante Capability-Möglichkeiten.",
+  "criterion.stakeholder-approval": "Die relevanten Stakeholder stimmen zu, dass diese Capability-Möglichkeit weiter untersucht und priorisiert werden sollte.",
+  "criterion.api-opportunity-documented": "Die Capability-Möglichkeit wurde identifiziert und dokumentiert.",
+  "criterion.api-reusability": "Die Capability erfüllt einen klaren Geschäftsbedarf und kann von den vorgesehenen Nutzern wiederverwendet werden.",
+  "criterion.hide-backend-discrepancies": "Die gewählte Schnittstelle kapselt die Komplexität und Inkonsistenzen der Backend-Systeme angemessen vor den Nutzern.",
+  "criterion.value-prop-validated": "Das Wertversprechen der Capability wurde mit den relevanten Geschäfts- und Nutzervertretern validiert.",
+  "criterion.consumer-segments-identified": "Die Nutzersegmente sind identifiziert.",
+  "criterion.api-roadmap-defined": "Eine übergeordnete Roadmap für die Umsetzung ist definiert.",
+  "criterion.architecture-patterns-validated": "Die gewählte Architektur, Plattform und Umsetzungsweise wurden mit den relevanten Architektur-, Sicherheits- und Plattform-Stakeholdern validiert.",
+  "criterion.design-reflects-business-value": "Das Schnittstellendesign und die offengelegten Fähigkeiten lassen sich klar auf Geschäftswert und Nutzerbedürfnisse zurückführen.",
+  "criterion.api-consistency": "Das Schnittstellendesign folgt den vereinbarten Produkt-, Design- und Qualitätsstandards.",
+  "criterion.api-contract-tested": "Der Schnittstellenvertrag wurde validiert und gegen funktionale und nicht-funktionale Anforderungen getestet.",
+  "criterion.api-description-available": "Die Schnittstelle und ihre Fähigkeiten sind ausreichend für Review, Auditierung und Onboarding dokumentiert.",
+  "criterion.audit-passed": "Die Lösung besteht Qualitäts-, Sicherheits-, Compliance- und Bereitschaftsprüfungen.",
+  "criterion.audit-reports-shared": "Audit-Ergebnisse und Maßnahmenentscheidungen wurden mit den relevanten Stakeholdern geteilt.",
+  "criterion.api-ready-for-publishing": "Die Capability ist bereit, über den gewählten Bereitstellungsmechanismus veröffentlicht zu werden.",
+  "criterion.api-documentation-ready": "Nutzerorientierte Dokumentation und Onboarding-Materialien sind bereit.",
+  "criterion.consumer-support-ready": "Onboarding-, Support- und Kommunikationsprozesse für Nutzer sind bereit.",
+  "criterion.legal-compliance-clear": "Rechtliche, Datenschutz- und Compliance-Anforderungen für die Veröffentlichung sind definiert und verstanden."
+}
diff --git a/src/data/method/de/labels.cycles.json b/src/data/method/de/labels.cycles.json
new file mode 100644
index 0000000..c3213c8
--- /dev/null
+++ b/src/data/method/de/labels.cycles.json
@@ -0,0 +1,93 @@
+{
+  "cycles.title": "Zyklusansichten",
+  "cycles.description": "Zielgruppenspezifische Ansichten auf den APIOps-Cycles-Methoden.",
+  "cycle.capability-productization-cycle.title": "Capability-Produktisierungszyklus",
+  "cycle.capability-productization-cycle.description": "Ein Zyklus, um Geschäftsfähigkeiten in wiederverwendbare digitale Capabilities zu überführen, bevor die Umsetzungsweise gewählt wird.",
+  "cycle.capability-productization-cycle.purpose": "Identifizieren und produktisieren Sie wiederverwendbare digitale Capabilities, bevor entschieden wird, ob die Umsetzungsweise APIs, Events, Dateien, Streams, Datenprodukte, KI-gestützte Services, direkte Integration oder ein Hybridmuster sein soll.",
+  "cycle.api-productization-cycle.title": "API-Produktisierungszyklus",
+  "cycle.api-productization-cycle.description": "Die API-fokussierte APIOps-Cycles-Journey für Produktisierung, Design, Bereitstellung, Veröffentlichung und Verbesserung von APIs.",
+  "cycle.api-productization-cycle.purpose": "API-fokussierte Method Journey für Teams, die bereits wissen, dass die vorgesehene Umsetzungsweise ein API-Produkt ist.",
+  "cycle.integration-productization-cycle.title": "Integrationszyklus",
+  "cycle.integration-productization-cycle.description": "Ein Zyklus zur Produktisierung wiederverwendbarer Integrations-Capabilities, bevor ein konkretes Integrationsmuster gewählt wird.",
+  "cycle.integration-productization-cycle.purpose": "Unterstützt das Design wiederverwendbarer Integrations-Capabilities, bevor APIs, Events, Dateien, Streams, Datenprodukte, direkte Integration oder Hybridmuster gewählt werden.",
+  "cycle.station.capability-strategy": "Strategie",
+  "cycle.station.consumer-requirements-onboarding": "Nutzeranforderungen & Onboarding",
+  "cycle.station.architecture-platform-decisions": "Architektur & Plattformentscheidungen",
+  "cycle.station.solution-interface-design": "Lösungs- & Schnittstellendesign",
+  "cycle.station.delivery-operations": "Bereitstellung & Betrieb",
+  "cycle.station.quality-readiness-assurance": "Qualitäts- & Bereitschaftssicherung",
+  "cycle.station.publishing-enablement": "Veröffentlichung & Adoption Enablement",
+  "cycle.station.monitoring-improvement": "Monitoring & Verbesserung",
+  "cycle.station.api-product-strategy": "API-Produktstrategie",
+  "cycle.station.api-consumer-experience": "API Consumer Experience",
+  "cycle.station.api-platform-architecture": "API-Plattformarchitektur",
+  "cycle.station.api-design": "API-Design",
+  "cycle.station.api-delivery": "API-Bereitstellung",
+  "cycle.station.api-audit": "API-Audit",
+  "cycle.station.api-publishing": "API-Veröffentlichung",
+  "cycle.station.monitoring-and-improving": "Monitoring & Verbesserung",
+  "cycle.station.integration-capability-strategy": "Integrations-Capability-Strategie",
+  "cycle.station.integration-consumer-requirements-onboarding": "Integrationsnutzeranforderungen & Onboarding",
+  "cycle.station.integration-architecture-decision": "Integrationsarchitekturentscheidung",
+  "cycle.station.integration-solution-design": "Integrationsdesign",
+  "cycle.station.integration-delivery-operations": "Integrationsbereitstellung & Betrieb",
+  "cycle.station.integration-readiness-assurance": "Integrationsbereitschaftssicherung",
+  "cycle.station.capability-publishing": "Capability-Veröffentlichung",
+  "cycle.station.integration-monitoring-improvement": "Integrationsmonitoring & Verbesserung",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Definieren Sie Wert, Nutzer, Ownership und Geschäftsziele der Capability, bevor etwas gebaut wird.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Erfassen Sie Nutzeranforderungen, Onboarding-Bedarf, Einschränkungen, Serviceerwartungen und Verantwortlichkeiten der Anbieter.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Nutzen Sie Anforderungen und Einschränkungen, um Architektur und Plattformfähigkeiten auszuwählen.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Entwerfen Sie den Schnittstellenvertrag und das Interaktionsmodell für die gewählte Umsetzungsweise.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Bauen, testen, veröffentlichen und betreiben Sie die Capability mit der gewählten Umsetzungsweise und dem validierten Schnittstellenvertrag.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Sichern Sie Qualität, Governance und Bereitschaft vor der Veröffentlichung ab.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie Capability-Informationen so, dass Nutzer sie finden, Zugriff beantragen, onboarden und Support erhalten können.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie Capability-Gesundheit, Nutzerergebnisse, Zuverlässigkeit, Wiederverwendung und Verbesserungsmöglichkeiten.",
+  "cycle.owner.business-owner": "Business Owner",
+  "cycle.owner.domain-expert": "Domänenexperte",
+  "cycle.owner.capability-owner": "Capability Owner",
+  "cycle.owner.consumer-representative": "Nutzervertreter",
+  "cycle.owner.enterprise-architect": "Enterprise Architect",
+  "cycle.owner.platform-owner": "Platform Owner",
+  "cycle.owner.api-product-owner": "API Product Owner",
+  "cycle.owner.api-platform-owner": "API Platform Owner",
+  "cycle.owner.integration-architect": "Integration Architect",
+  "cycle.owner.solution-architect": "Solution Architect",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Rahmen Sie die API als Produkt mit klarem Wertversprechen, Nutzern, Geschäftsmodell, Ownership und Lifecycle-Intention.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Definieren Sie API-Nutzersegmente, Onboarding-Pfade, Erwartungen und Experience-Anforderungen, bevor Designentscheidungen festgelegt werden.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Wählen und validieren Sie API-Plattform, Architektur, Governance und betriebliche Einschränkungen, die für das Produkt benötigt werden.",
+  "cycle.api-productization-cycle.station.api-design.description": "Entwerfen Sie API-Schnittstellenvertrag, Interaktionsmodell, Schemas, Policies und Usability-Details vor der Implementierung.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Implementieren, testen, sichern, automatisieren und betreiben Sie das API-Produkt über die Bereitstellungspipeline.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validieren Sie API-Qualität, Compliance, Bereitschaft, Nachweise und Freigabekriterien vor der Veröffentlichung.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie das API-Produkt so, dass Nutzer es finden, bewerten, Zugriff beantragen, onboarden und Support erhalten können.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie API-Gesundheit, Adoption, Nutzerergebnisse, Zuverlässigkeit und Verbesserungsmöglichkeiten nach der Veröffentlichung.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Rahmen Sie die wiederverwendbare Integrations-Capability, den Geschäftsbedarf, Ownership und erwartete Wiederverwendung, bevor ein Muster gewählt wird.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Erfassen Sie Integrationsnutzer, Anbieter-Verantwortlichkeiten, Onboarding-Bedarf, Serviceerwartungen und operative Einschränkungen.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Entscheiden Sie Integrationsarchitektur, Plattformfähigkeiten, Einschränkungen und Governance-Modell für die Capability.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Entwerfen Sie Schnittstellenvertrag, Payloads, Events, APIs, Dateien oder Interaktionsmuster, die für die Integrations-Capability gewählt wurden.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Bauen, testen, automatisieren, veröffentlichen und betreiben Sie die Integrations-Capability mit dem gewählten Bereitstellungsmuster und dem validierten Schnittstellenvertrag.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Sichern Sie Integrationsbereitschaft, Governance, Qualität, Sicherheit, Compliance und operative Nachweise vor der Veröffentlichung ab.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie die Integrations-Capability so, dass Teams sie finden, anfragen, wiederverwenden, onboarden und Support erhalten können.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie Integrationszuverlässigkeit, Wiederverwendung, Incidents, Performance, Nutzerergebnisse und Verbesserungsbedarf.",
+  "cycle.automation-cycle.title": "Automatisierungszyklus",
+  "cycle.automation-cycle.description": "Ein Zyklus zum Identifizieren, Entwerfen, Bereitstellen, Enablement und Verbessern von Automatisierungsmöglichkeiten.",
+  "cycle.automation-cycle.purpose": "Produktisieren Sie Automatisierungsmöglichkeiten zu gesteuerten Workflows mit klaren Nutzern, Plattformen, Kontrollen, Bereitstellungspfaden, Enablement und Monitoring.",
+  "cycle.audience.automation-owners": "Automation Owner",
+  "cycle.audience.process-owners": "Prozessverantwortliche",
+  "cycle.audience.automation-teams": "Automatisierungsteams",
+  "cycle.station.automation-opportunity-strategy": "Automatisierungschance & Strategie",
+  "cycle.station.process-user-requirements": "Prozess-/Nutzeranforderungen",
+  "cycle.station.automation-platform-decision": "Automatisierungsplattformentscheidung",
+  "cycle.station.automation-workflow-design": "Automatisierungs-Workflow-Design",
+  "cycle.station.automation-delivery": "Automatisierungsbereitstellung",
+  "cycle.station.automation-readiness-review": "Automatisierungsbereitschaftsprüfung",
+  "cycle.station.automation-enablement": "Automatisierungs-Enablement",
+  "cycle.station.automation-monitoring-improvement": "Automatisierungsmonitoring & Verbesserung",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Identifizieren und priorisieren Sie Automatisierungsmöglichkeiten nach Wert, Machbarkeit, Risiko, Ownership und erwarteter Prozesswirkung.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Erfassen Sie Prozessnutzer, Rollen, Übergaben, Ausnahmen, Einschränkungen und Serviceerwartungen, bevor die Automatisierung entworfen wird.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Wählen Sie Automatisierungsplattform, Runtime, Integrationsmodell, Governance-Kontrollen und operative Einschränkungen.",
+  "cycle.automation-cycle.station.api-design.description": "Entwerfen Sie Automatisierungsworkflow, Trigger, Entscheidungspunkte, Integrationen, Datenverarbeitung, Schnittstellenverträge und Ausnahmefälle.",
+  "cycle.automation-cycle.station.api-delivery.description": "Bauen, testen, deployen, dokumentieren und betreiben Sie die Automatisierung mit klarer Ownership, Kontrollen und Rollback-Pfaden.",
+  "cycle.automation-cycle.station.api-audit.description": "Prüfen Sie Automatisierungsbereitschaft, Qualität, Risiko, Compliance, menschliche Aufsicht, Nachweise und Freigabekriterien.",
+  "cycle.automation-cycle.station.api-publishing.description": "Befähigen Sie Nutzer und Betreiber mit Auffindbarkeit, Onboarding, Betriebsanweisungen, Supportpfaden und Änderungs kommunikation.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Überwachen Sie Automatisierungsleistung, Ausnahmen, Zuverlässigkeit, Nutzerergebnisse, operative Auswirkungen und Verbesserungsmöglichkeiten."
+}
diff --git a/src/data/method/de/labels.lines.json b/src/data/method/de/labels.lines.json
index 5ccb018..8b0d33b 100644
--- a/src/data/method/de/labels.lines.json
+++ b/src/data/method/de/labels.lines.json
@@ -1,16 +1,16 @@
 {
   "lines.title": "Metro-Linien",
-  "lines.description": "Eine Sammlung von API-Linien, die die Entwicklung und Verwaltung von APIs leiten.",
-  "line.business-opportunities-line.title": "Geschäftsmöglichkeiten Linie",
-  "line.business-opportunities-line.description": "Konzentriert sich auf die Identifizierung und Nutzung von Geschäftsmöglichkeiten durch APIs.",
-  "line.platform-architecture-line.title": "Plattform Architektur Linie",
-  "line.platform-architecture-line.description": "Behandelt die architektonischen Aspekte von API-Plattformen.",
+  "lines.description": "APIOps Cycles-Metrolinien zur Unterstützung der Planung, Umsetzung und Weiterentwicklung von Capabilities, APIs und Integrationen.",
+  "line.business-opportunities-line.title": "Linie Geschäftsmöglichkeiten",
+  "line.business-opportunities-line.description": "Konzentriert sich auf die Identifizierung, Bewertung und Produktisierung von Geschäftsmöglichkeiten als wiederverwendbare Capabilities.",
+  "line.platform-architecture-line.title": "Linie Plattformarchitektur",
+  "line.platform-architecture-line.description": "Behandelt Architekturentscheidungen für Plattformen, Integrationen und Schnittstellen.",
   "line.api-design-line.title": "API-Entwurfslinie",
-  "line.api-design-line.description": "Konzentriert sich auf die Designprinzipien und -praktiken für APIs.",
+  "line.api-design-line.description": "Konzentriert sich auf Entwurfsprinzipien und Best Practices für Schnittstellen und Integrationslösungen.",
   "line.delivery-line.title": "Bereitstellungslinie",
-  "line.delivery-line.description": "Behandelt die Bereitstellungsprozesse und -praktiken für APIs.",
-  "line.publishing-and-adoption-line.title": "Veröffentlichungs- und Adoptionslinie",
-  "line.publishing-and-adoption-line.description": "Der Schwerpunkt liegt auf der Veröffentlichung von APIs und der Gewährleistung ihrer Annahme durch die Verbraucher.",
-  "line.operating-model-line.title": "Betriebsmodell Linie",
-  "line.operating-model-line.description": "Deckt das Betriebsmodell für die API-Verwaltung und -Governance ab."
-}
+  "line.delivery-line.description": "Behandelt Implementierung, Tests, Automatisierung und Bereitstellungspraktiken.",
+  "line.publishing-and-adoption-line.title": "Linie Veröffentlichung & Enablement",
+  "line.publishing-and-adoption-line.description": "Konzentriert sich auf die Veröffentlichung von Capabilities sowie deren Auffindbarkeit, Onboarding und Nutzung.",
+  "line.operating-model-line.title": "Linie Betriebsmodell",
+  "line.operating-model-line.description": "Behandelt Governance, Verantwortlichkeiten und das Betriebsmodell für Capabilities."
+}
\ No newline at end of file
diff --git a/src/data/method/de/labels.stakeholders.json b/src/data/method/de/labels.stakeholders.json
index 06a6d33..5794f9a 100644
--- a/src/data/method/de/labels.stakeholders.json
+++ b/src/data/method/de/labels.stakeholders.json
@@ -1,49 +1,49 @@
 {
-  "stakeholder.involvement.lead": "Leider",
+  "stakeholder.involvement.lead": "Federführend",
   "stakeholder.involvement.core": "Kern",
-  "stakeholder.involvement.consulted": "Beratung",
-  "stakeholder.business-owner.title": "Geschäftsinhaber",
-  "stakeholder.business-owner.description": "Repräsentiert Geschäftsziele, Finanzierung und erwartete Ergebnisse für das API-Initiative.",
-  "stakeholder.api-program-owner.title": "API Program Owner",
+  "stakeholder.involvement.consulted": "Konsultiert",
+  "stakeholder.business-owner.title": "Business Owner",
+  "stakeholder.business-owner.description": "Vertritt Geschäftsziele, Finanzierung und erwartete Ergebnisse der Capability-Initiative.",
+  "stakeholder.api-program-owner.title": "API-Programmverantwortlicher",
   "stakeholder.api-program-owner.description": "Koordiniert API-Portfolio-Praktiken, organisatorische Ausrichtung und langfristige API-Fähigkeitsentwicklung.",
   "stakeholder.api-product-owner.title": "API Product Owner",
   "stakeholder.api-product-owner.description": "Führt die API-Möglichkeit, Priorisierung und produktniveaubezogene Entscheidungen über den gesamten Lebenszyklus hinweg durch.",
   "stakeholder.capability-owner.title": "Capability Owner",
-  "stakeholder.capability-owner.description": "",
+  "stakeholder.capability-owner.description": "Verantwortet Vision, Ziele, Priorisierung und Weiterentwicklung der Capability über ihren gesamten Lebenszyklus.",
   "stakeholder.domain-specialist.title": "Domain-Experte",
   "stakeholder.domain-specialist.description": "Bringt tiefe Kenntnisse des Geschäftsbereichs, Konzepte, Regeln und Einschränkungen mit, die die API widerspiegeln muss.",
   "stakeholder.customer-specialist.title": "Kunden- oder Partnervertreter",
-  "stakeholder.customer-specialist.description": "Repräsentiert die Perspektive von Kunden oder Partnern für den Reise, Wert und Zusammenarbeitsmodell.",
-  "stakeholder.api-consumer-specialist.title": "API-Verbrauchervertreter",
-  "stakeholder.api-consumer-specialist.description": "Repräsentiert die Bedürfnisse von Entwicklern, Integratoren oder anderen API-Verbrauchern, die die API direkt verwenden.",
+  "stakeholder.customer-specialist.description": "Vertritt die Perspektive von Kunden oder Partnern hinsichtlich Journey, Wert und Zusammenarbeitsmodell.",
+  "stakeholder.api-consumer-specialist.title": "Vertreter der API-Nutzer",
+  "stakeholder.api-consumer-specialist.description": "Vertritt die Anforderungen von Entwicklern, Integratoren und anderen Nutzern der API.",
   "stakeholder.platform-architect.title": "Plattform-Architekt",
   "stakeholder.platform-architect.description": "Leitet Entscheidungen über Plattform, Integration, Skalierbarkeit und Architektur, die beeinflussen, wie die API erstellt und betrieben wird.",
-  "stakeholder.api-architect.title": "API Architect",
-  "stakeholder.api-architect.description": "",
-  "stakeholder.integration-architect.title": "Integration Architect",
-  "stakeholder.integration-architect.description": "",
-  "stakeholder.platform-owner.title": "Platform Owner",
-  "stakeholder.platform-owner.description": "",
+  "stakeholder.api-architect.title": "API-Architekt",
+  "stakeholder.api-architect.description": "Verantwortet API-Architektur, Entwurfsprinzipien und die Qualität der Schnittstellenverträge.",
+  "stakeholder.integration-architect.title": "Integrationsarchitekt",
+  "stakeholder.integration-architect.description": "Entwirft Integrationslösungen und Integrationsmuster im Einklang mit der Gesamtarchitektur.",
+  "stakeholder.platform-owner.title": "Plattformverantwortlicher",
+  "stakeholder.platform-owner.description": "Verantwortet Plattformfähigkeiten, Weiterentwicklung und Betrieb.",
   "stakeholder.api-designer.title": "API-Designer",
-  "stakeholder.api-designer.description": "Formt den API-Vertrag, das Interaktionsmodell, die Konsistenz und die Benutzbarkeit der exponierten Fähigkeiten.",
-  "stakeholder.api-engineer.title": "Programmierer",
-  "stakeholder.api-engineer.description": "Verantwortlich für Implementierung, Automatisierung, Testing und Release-Flussbedürfnisse, die für die zuverlässige Lieferung der API erforderlich sind.",
-  "stakeholder.automation-owner.title": "Automation Owner",
-  "stakeholder.automation-owner.description": "",
-  "stakeholder.process-owner.title": "Process Owner",
-  "stakeholder.process-owner.description": "",
-  "stakeholder.automation-engineer.title": "Automation Engineer",
-  "stakeholder.automation-engineer.description": "",
+  "stakeholder.api-designer.description": "Gestaltet Schnittstellenvertrag, Interaktionsmodell, Konsistenz, Benutzerfreundlichkeit und bereitgestellte Capabilities.",
+  "stakeholder.api-engineer.title": "API-Entwickler",
+  "stakeholder.api-engineer.description": "Verantwortet Implementierung, Automatisierung, Tests und Release-Prozesse für eine zuverlässige Bereitstellung.",
+  "stakeholder.automation-owner.title": "Automatisierungsverantwortlicher",
+  "stakeholder.automation-owner.description": "Verantwortet Ziele, Priorisierung und Geschäftswert der Automatisierung.",
+  "stakeholder.process-owner.title": "Prozessverantwortlicher",
+  "stakeholder.process-owner.description": "Verantwortet Ziele, Weiterentwicklung und Ergebnisse des Geschäftsprozesses.",
+  "stakeholder.automation-engineer.title": "Automatisierungsingenieur",
+  "stakeholder.automation-engineer.description": "Implementiert, testet und betreibt Automatisierungslösungen und deren Integrationen.",
   "stakeholder.security-specialist.title": "Sicherheitsspezialist",
   "stakeholder.security-specialist.description": "Stellt sicher, dass Sicherheitsrisiken, Kontrollen und Vertrauensgrenzen im gesamten API-Lifecycle berücksichtigt werden.",
-  "stakeholder.compliance-specialist.title": "Compliance and Legal Specialist",
-  "stakeholder.compliance-specialist.description": "Klärt rechtliche, datenschutzrechtliche, regulatorische und vertragliche Anforderungen auf, die die API beeinflussen.",
-  "stakeholder.governance-specialist.title": "Governance Owner",
+  "stakeholder.compliance-specialist.title": "Compliance- und Rechtsexperte",
+  "stakeholder.compliance-specialist.description": "Klärt rechtliche, Datenschutz- und Compliance-Anforderungen, die die Capability oder Schnittstelle betreffen.",
+  "stakeholder.governance-specialist.title": "Governance-Verantwortlicher",
   "stakeholder.governance-specialist.description": "Repräsentiert Überprüfung, Auditierung und organisationsweite Governance-Praktiken für API-Qualität und Konformität.",
-  "stakeholder.api-devrel-specialist.title": "Documentation and DevRel Owner",
-  "stakeholder.api-devrel-specialist.description": "Verantwortlich für Onboarding-Inhalte, Entwickler-Kommunikation und Dokumentationsqualität für API-Verbraucher.",
-  "stakeholder.operations-specialist.title": "Support and Operations Owner",
+  "stakeholder.api-devrel-specialist.title": "Verantwortlicher für Dokumentation und DevRel",
+  "stakeholder.api-devrel-specialist.description": "Verantwortet Onboarding-Inhalte, Entwicklerkommunikation und Dokumentationsqualität für API-Nutzer.",
+  "stakeholder.operations-specialist.title": "Verantwortlicher für Support und Betrieb",
   "stakeholder.operations-specialist.description": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft.",
-  "stakeholder.partner-specialist.title": "Partner- oder Vendor-Manager",
-  "stakeholder.partner-specialist.description": "Koordiniert externe Partner-, Lieferanten- oder Vendor-Beziehungen, die die API-Strategie und -Lieferung beeinflussen."
-}
+  "stakeholder.partner-specialist.title": "Partner- und Lieferantenmanager",
+  "stakeholder.partner-specialist.description": "Koordiniert Partner- und Lieferantenbeziehungen, die die Capability-Strategie und Umsetzung beeinflussen."
+}
\ No newline at end of file
diff --git a/src/data/method/de/labels.stations.json b/src/data/method/de/labels.stations.json
index f0a19c5..b875124 100644
--- a/src/data/method/de/labels.stations.json
+++ b/src/data/method/de/labels.stations.json
@@ -1,61 +1,61 @@
 {
-  "group.core-stations.title": "API-Lebenszyklus Kernstationen",
-  "group.core-stations.description": "Die Kernstationen der API Metro, wo Teams lernen können, wie man APIs effektiv erstellt und verwaltet.",
-  "group.sub-stations.title": "API-Lebenszyklus-Unterstationen",
-  "group.sub-stations.description": "Unterstationen, die zusätzliche Ressourcen, Tools und bewährte Verfahren für API-Teams bereitstellen.",
-  "station.api-product-strategy.title": "API-Produktstrategie - APIs in strategische Produkte verwandeln",
-  "station.api-product-strategy.description": "Bevor Sie etwas bauen, sollten Sie von Anfang an den Wert, die Benutzer und die Geschäftsziele Ihrer API definieren.",
-  "station.api-product-strategy.why_it_matters": "Viele Unternehmen betrachten APIs als technische Projekte und nicht als Produkte. Das Ergebnis? Verwirrte Kunden, schlechte Akzeptanz und verschwendeter Aufwand.\n\nDiese Station hilft Ihnen, den Zweck Ihrer API, die Zielgruppe und die Erfolgskriterien zu definieren, damit Teams APIs bereitstellen können, die echte Probleme lösen.",
-  "station.api-product-strategy.apply_in_work": "Bereitstellung von Richtlinien und Vorlagen für die Erstellung von API-Geschäftsmodellen, Wertvorschlägen und Roadmaps.",
-  "station.api-product-strategy.outcomes": "Ein klares API-Wertversprechen und eine klare Zielgruppe",
-  "station.api-product-strategy.how_it_works": "Untersuchen Sie das Kunden- oder Partnerproblem, das Sie mit APIs lösen wollen. Zeichnen Sie die Stakeholder, deren Wege und Ergebnisse mithilfe der Customer Journey Canvas auf.",
-  "station.api-consumer-experience.title": "API Consumer Experience - Design für die echten Benutzer Ihrer API",
-  "station.api-consumer-experience.description": "Stellen Sie sicher, dass Ihre API auffindbar, verständlich und nutzbar ist - vor und nach der Einführung.",
-  "station.api-consumer-experience.why_it_matters": "Großartige APIs funktionieren nicht nur - sie fühlen sich auch intuitiv an. Ganz gleich, ob Ihr Kunde ein interner Entwickler, ein externer Partner oder ein KI-Agent ist, seine Erfahrung entscheidet über die Akzeptanz.\n\nOhne einen klaren Erlebnisplan:\n- Großartige APIs bleiben ungenutzt\n- Teams verschwenden Zeit damit, zu raten, wie sie Ihre API verwenden sollen\n- Feedbackschleifen sind unterbrochen oder fehlen.\n\nDiese Station hilft Ihnen, Ihre API mit den Augen ihrer Nutzer zu sehen.",
-  "station.api-consumer-experience.how_it_works": "Überprüfen Sie das bestehende API Value Proposition Canvаs von der Perspektive des API-Nutzers. Stellen Sie die Stabilität der unterstützten Geschäftsprozesse sicher und ergänzen Sie die Funktionen, die Probleme lösen und Vorteile bieten, um die Bedürfnisse der API-Nutzer zu berücksichtigen, damit diese spätere Designentscheidungen leiten können.",
-  "station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des API-Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
-  "station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den API-Nutzer zu verbessern.",
-  "station.api-consumer-experience.apply_in_work": "Bereitstellung von Richtlinien, Tools und Feedback-Mechanismen für das Verständnis, die Analyse und die Verbesserung der internen und externen Erfahrungen von Entwicklern und Partnern.",
-  "station.api-consumer-experience.outcomes": "Identifizieren und priorisieren Sie Ihre API-Kunden",
-  "station.api-platform-architecture.title": "API-Plattformarchitektur - Architektur von APIs für Skalierbarkeit und Wiederverwendung",
-  "station.api-platform-architecture.description": "Gewährleisten Sie Skalierbarkeit, Wiederverwendung und Governance für Ihre API- und Plattformkomponenten.",
-  "station.api-platform-architecture.why_it_matters": "Wenn APIs teamübergreifend skaliert werden, muss Ihre Plattform Governance und Wiederverwendung ermöglichen, ohne die Geschwindigkeit zu beeinträchtigen. Diese Station zeigt, wie man APIs für Langlebigkeit, Sicherheit und Effizienz entwickelt.",
-  "station.api-platform-architecture.apply_in_work": "Aufbau einer skalierbaren, sicheren und konformen Infrastruktur für den API-Betrieb. Bereitstellung von Leitlinien für bewährte Architekturverfahren.",
-  "station.api-platform-architecture.outcomes": "Redundante APIs abbauen und die Kosten für die Cloud-Plattform senken",
-  "station.api-platform-architecture.how_it_works": "Das Business Impact Canvas hilft dabei, Risiken in Bezug auf API-Verfügbarkeit, -Sicherheit und -Funktionalität zu identifizieren und zu mindern, um fundierte Architekturentscheidungen zu unterstützen.",
-  "station.api-design.title": "API-Design - Entwerfen Sie APIs, die Wert liefern",
-  "station.api-design.description": "Erstellen Sie API-Designs, die konsistent, wiederverwendbar und auf Geschäftszielen und gemeinsamen Standards basieren.",
-  "station.api-design.why_it_matters": "Beim Entwurf von APIs geht es nicht nur um die Benennung von Endpunkten. Gutes Design stellt sicher, dass APIs benutzerfreundlich, konsistent und auf Geschäfts- und technische Ziele ausgerichtet sind. Schlecht gestaltete APIs führen zu enger Kopplung, geringer Wiederverwendung und kostspieligen Nacharbeiten in den Teams.",
-  "station.api-design.apply_in_work": "Bereitstellung von wiederverwendbaren Designmustern, gemeinsamen Standards und Validierungstools für API-Spezifikationen. Sicherstellen, dass Designentscheidungen konsistent, frühzeitig überprüft und auf die Geschäftsabsicht ausgerichtet sind.",
-  "station.api-design.outcomes": "Gut dokumentierte und konsistente API-Designs",
-  "station.api-design.how_it_works": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle APIs zu schaffen.",
-  "station.api-delivery.title": "API-Bereitstellung - Bereitstellung sicherer und zuverlässiger APIs",
-  "station.api-delivery.description": "Erstellen, Testen und Freigeben von APIs unter Verwendung moderner Bereitstellungspipelines und bewährter technischer Verfahren.",
-  "station.api-delivery.why_it_matters": "Selbst die besten API-Designs scheitern, wenn die Bereitstellung uneinheitlich ist. Diese Station stellt sicher, dass Ihre APIs qualitativ hochwertig erstellt, gründlich getestet und zuverlässig bereitgestellt werden - für schnellere Iterationen und mehr Vertrauen.",
-  "station.api-delivery.apply_in_work": "Bereitstellung von Kodierungsrahmen, Bibliotheken und Standards für die API-Implementierung. Implementierung von CI/CD-Pipelines, Qualitätssicherungs-Frameworks und Tools zur Automatisierung der Bereitstellung.",
-  "station.api-delivery.outcomes": "APIs, die mit getesteten Frameworks und Mustern implementiert werden",
-  "station.api-delivery.how_it_works": "Verwenden Sie Best Practices für die API-Entwicklung als Leitfaden für die Implementierung des validierten Vertrags mit etablierten Frameworks und Bibliotheken, um sicherzustellen, dass das Ergebnis wiederverwendbar und wartbar ist.",
-  "station.api-audit.title": "API-Audit - Prüfung von APIs auf Konformität und Qualität",
-  "station.api-audit.description": "Stellen Sie sicher, dass APIs vor der Veröffentlichung und Bereitstellung den geschäftlichen, gestalterischen und betrieblichen Standards entsprechen.",
-  "station.api-audit.why_it_matters": "APIs sind langlebige Produkte und müssen den Erwartungen hinsichtlich Qualität, Konsistenz und Compliance entsprechen. Das Audit verbindet Designentscheidungen, Implementierung und Betriebsbereitschaft mit definierten Standards und reduziert so Risiken vor der Bereitstellung.",
-  "station.api-audit.apply_in_work": "Richten Sie einen konsistenten Audit-Prozess ein, der die API-Bereitschaft über alle Lebenszyklusphasen hinweg anhand definierter Kriterien, Nachweise und Standards bewertet. Stellen Sie sicher, dass Lücken frühzeitig erkannt und vor der Veröffentlichung behoben werden.",
-  "station.api-audit.outcomes": "APIs erfüllen interne und externe Standards",
-  "station.api-audit.how_it_works": "Führen Sie Audits durch, um sicherzustellen, dass APIs vor der Veröffentlichung organisatorische, technische und rechtliche Standards erfüllen.",
-  "station.api-publishing.title": "API-Veröffentlichung - Veröffentlichen Sie APIs mit Zuversicht",
-  "station.api-publishing.description": "Stellen Sie APIs mit der richtigen Dokumentation und den richtigen Prozessen sicher und klar für die richtige Zielgruppe bereit.",
-  "station.api-publishing.why_it_matters": "Bei der Veröffentlichung geht es nicht nur um die Bereitstellung, sondern auch um die Auffindbarkeit, den Zugang und die Unterstützung. Wenn APIs nicht korrekt veröffentlicht werden, können sie nicht verwendet, wiederverwendet oder effektiv gesichert werden.",
-  "station.api-publishing.apply_in_work": "Ermöglichung der Veröffentlichung von APIs in der jeweiligen Umgebung mit klaren Registrierungs- und Zugriffsmechanismen (z. B. API-Schlüssel, OAuth, Abonnementpläne) je nach den API-Verbrauchersegmenten und den Sicherheits- und Compliance-Anforderungen.",
-  "station.api-publishing.outcomes": "Veröffentlichung von APIs in der richtigen Umgebung (privat, Partner, öffentlich)",
-  "station.api-publishing.how_it_works": "Veröffentlichen Sie APIs in den entsprechenden Gateways und Umgebungen, um die Wiederverwendbarkeit für mehrere API-Kunden zu unterstützen.",
-  "station.monitoring-and-improving.title": "Überwachen und Verbessern - für den API-Wert",
-  "station.monitoring-and-improving.description": "Nutzen Sie Messgrößen und Feedback, um die API-Leistung zu verfolgen und kontinuierliche Verbesserungen voranzutreiben.",
-  "station.monitoring-and-improving.why_it_matters": "Die API-Bereitstellung endet nicht mit dem Start. Ohne Überwachung können Teams weder die Akzeptanz noch die Leistung oder den ROI verbessern. Diese Station stellt sicher, dass APIs nützlich und sicher bleiben und sich mit den Geschäftsanforderungen weiterentwickeln.",
-  "station.monitoring-and-improving.apply_in_work": "Einrichtung von Analyserahmen zur Verfolgung von Leistung und Engagement. Entwickeln Sie Feedbackschleifen, Analysetools und Engagementstrategien für APIs.",
-  "station.monitoring-and-improving.outcomes": "Festlegung und Verfolgung von Leistungs- und Nutzungskennzahlen",
-  "station.monitoring-and-improving.how_it_works": "Überwachen Sie Leistungsmetriken (z. B. API-Aufrufe, Latenz, Fehlerraten) und Akzeptanzmetriken (z. B. NPS).",
+  "group.core-stations.title": "Kernstationen des Capability-Lebenszyklus",
+  "group.core-stations.description": "Die Kernstationen des APIOps-Cycles-Methodengraphen, in denen Teams lernen, wiederverwendbare Capabilities über APIs, Events, Dateien, Streams, Datenprodukte und andere Integrationsstile hinweg zu entwerfen, bereitzustellen, zu steuern und kontinuierlich zu verbessern.",
+  "group.sub-stations.title": "Unterstützende Stationen",
+  "group.sub-stations.description": "Unterstützende Stationen bieten wiederverwendbare Praktiken, Entscheidungspunkte und Ressourcen, die in verschiedenen APIOps-Cycles-Routen genutzt werden können.",
+  "station.api-product-strategy.title": "Strategie",
+  "station.api-product-strategy.description": "Beschreiben Sie den Geschäftsbedarf als wiederverwendbare Capability, bevor Sie die Umsetzungsweise festlegen.",
+  "station.api-product-strategy.why_it_matters": "Integrations- und API-Arbeit springt oft zu früh zu einem technischen Muster. Diese Station hält das Team auf Geschäftsreise, Domänenverständnis, Wert, Wiederverwendungspotenzial, Ownership und Machbarkeit fokussiert, bevor APIs, Events, Dateien, Streams, Datenprodukte oder direkte Integration gewählt werden.",
+  "station.api-product-strategy.apply_in_work": "Nutzen Sie gemeinsame Journey-, Domänen-, Wertversprechen- und Geschäftsmodell-Canvases, um technologieunabhängige Anforderungen zu erfassen und zu entscheiden, ob die Capability wiederverwendbar sein sollte.",
+  "station.api-product-strategy.outcomes": "Eine technologieunabhängige Capability Opportunity",
+  "station.api-product-strategy.how_it_works": "Analysieren Sie die Kunden- oder Partner-Journey, aus der der Capability-Bedarf entsteht, und identifizieren Sie Aufgaben, Pain Points, Gains, Inputs, Outputs und Entscheidungspunkte.",
+  "station.api-consumer-experience.title": "Nutzeranforderungen & Onboarding",
+  "station.api-consumer-experience.description": "Erfassen Sie Nutzeranforderungen, Onboarding, Standards, nicht-funktionale Anforderungen, Serviceerwartungen, Einschränkungen, Sicherheitsbedarf, Protokolle, Datenaktualität, SLAs, Observability, Wiederherstellung, Adoption und Verantwortlichkeiten der Anbieter.",
+  "station.api-consumer-experience.why_it_matters": "Die richtige Architektur hängt von Nutzerzielen, Onboarding-Erwartungen, Service Levels, Datenqualität, Änderungsverträglichkeit, Observability, Support und Anbieterrestriktionen ab.",
+  "station.api-consumer-experience.how_it_works": "Nutzen Sie das Consumer Experience Requirements Canvas, um Nutzerziele, Verfügbarkeit, Aktualität, Volumen, Performance, Datenqualität, Sicherheit, Onboarding, Änderungen, Observability und Wiederherstellungserwartungen festzuhalten.",
+  "station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
+  "station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den Nutzer zu verbessern.",
+  "station.api-consumer-experience.apply_in_work": "Nutzen Sie Consumer-Experience- und Onboarding-Guidance, um Erwartungen für Nutzer und Anbieter explizit zu machen.",
+  "station.api-consumer-experience.outcomes": "Explizite Nutzeranforderungen und Onboarding-Erwartungen",
+  "station.api-platform-architecture.title": "Architektur & Plattformentscheidungen",
+  "station.api-platform-architecture.description": "Nutzen Sie Anforderungen und Einschränkungen, um Architektur, Plattformfähigkeiten, Governance und Betriebsmodell zu wählen.",
+  "station.api-platform-architecture.why_it_matters": "Eine wiederverwendbare Capability braucht Architekturentscheidungen, die zu Nutzeranforderungen, Sicherheitsanforderungen, Datenflüssen, Betriebsmodell und Plattformrealität passen.",
+  "station.api-platform-architecture.apply_in_work": "Nutzen Sie Architektur- und Plattformressourcen, um tragfähige Umsetzungsoptionen zu vergleichen und eine nachvollziehbare Entscheidung zu treffen.",
+  "station.api-platform-architecture.outcomes": "Validierte Architektur- und Plattformentscheidung",
+  "station.api-platform-architecture.how_it_works": "Nutzen Sie Business Impact, Capacity, Security und Architecture Decision Ressourcen, um Risiken, Constraints und Alternativen systematisch zu bewerten.",
+  "station.api-design.title": "Lösungs- & Schnittstellendesign",
+  "station.api-design.description": "Entwerfen Sie die gewählte Umsetzungsweise, den Schnittstellenvertrag, Interaktionsmuster, Datenstrukturen und Nutzungsdetails vor der Implementierung.",
+  "station.api-design.why_it_matters": "Gutes Design geht über die Benennung von Endpunkten hinaus. Es stellt sicher, dass die Schnittstelle nutzbar, konsistent, überprüfbar und auf Geschäfts- und Nutzeranforderungen zurückführbar ist.",
+  "station.api-design.apply_in_work": "Nutzen Sie passende Designressourcen für die gewählte Umsetzungsweise, z. B. REST, GraphQL, Events, Dateien, Datenprodukte oder direkte Integration.",
+  "station.api-design.outcomes": "Ein validierter Schnittstellenvertrag für die gewählte Umsetzungsweise",
+  "station.api-design.how_it_works": "Prüfen Sie Domänenobjekte, Begriffe, Regeln und Ownership, bevor Sie den Schnittstellenvertrag entwerfen.",
+  "station.api-delivery.title": "Bereitstellung & Betrieb",
+  "station.api-delivery.description": "Setzen Sie die gewählte Umsetzungsweise mit geeigneten Engineering-, Test-, Sicherheits-, Automatisierungs- und Betriebspraktiken um.",
+  "station.api-delivery.why_it_matters": "Eine wiederverwendbare Capability braucht zuverlässige Bereitstellung und Betrieb, unabhängig davon, ob sie als API, Event-Stream, Dateiaustausch, Datenprodukt oder direkte Integration umgesetzt wird.",
+  "station.api-delivery.apply_in_work": "Wenden Sie Guidance für Umsetzung, Tests, CI/CD, Betrieb und Sicherheit auf die gewählte Umsetzungsweise an.",
+  "station.api-delivery.outcomes": "Eine bereitgestellte Capability, die mit dem validierten Schnittstellenvertrag übereinstimmt",
+  "station.api-delivery.how_it_works": "Nutzen Sie Entwicklungspraktiken, um den validierten Schnittstellenvertrag mit etablierten Frameworks, Bibliotheken und Teamstandards umzusetzen.",
+  "station.api-audit.title": "Qualitäts- & Bereitschaftssicherung",
+  "station.api-audit.description": "Prüfen Sie Schnittstellenvertrag, Kontrollen, Supportmodell, Observability, Dokumentation und Lifecycle-Bereitschaft vor der Veröffentlichung.",
+  "station.api-audit.why_it_matters": "Wiederverwendbare Capabilities erzeugen operative, datenbezogene, sicherheitsrelevante, datenschutzbezogene, Compliance- und Nutzerimpact-Risiken. Bereitschaftsprüfungen reduzieren Überraschungen vor Veröffentlichung oder produktiver Nutzung.",
+  "station.api-audit.apply_in_work": "Nutzen Sie Audit- und Compliance-Ressourcen, um sicherzustellen, dass die Capability kontrolliert veröffentlicht und wiederverwendet werden kann.",
+  "station.api-audit.outcomes": "Dokumentierte Bereitschaft für Veröffentlichung und Wiederverwendung",
+  "station.api-audit.how_it_works": "Nutzen Sie Checklisten, Linters, Tests und Reviews, um Konsistenz, Standards, Sicherheit, Performance und Compliance zu prüfen.",
+  "station.api-publishing.title": "Veröffentlichung & Enablement",
+  "station.api-publishing.description": "Veröffentlichen Sie Capability-Informationen so, dass Nutzer sie finden, bewerten, Zugriff beantragen, onboarden, nutzen und Support erhalten können.",
+  "station.api-publishing.why_it_matters": "Wiederverwendbare Capabilities erzeugen nur dann Wert, wenn Nutzer sie finden, den Schnittstellenvertrag und die Serviceerwartungen verstehen, Zugriff beantragen und Support sowie Lifecycle-Ownership kennen.",
+  "station.api-publishing.apply_in_work": "Veröffentlichen Sie Ownership, Dokumentation, Onboarding, Supportkontakte, Serviceerwartungen, Lifecycle-Status und Zugriffspfade.",
+  "station.api-publishing.outcomes": "Eine auffindbare und nutzbare Capability",
+  "station.api-publishing.how_it_works": "Veröffentlichen Sie Capability-Informationen in passenden Katalogen, Portalen, Gateways oder Umgebungen, damit mehrere Nutzer die Capability wiederverwenden können.",
+  "station.monitoring-and-improving.title": "Monitoring & Verbesserung",
+  "station.monitoring-and-improving.description": "Überwachen Sie Nutzung, Zuverlässigkeit, Datenqualität, Nutzerergebnisse, Betriebskosten und Wiederverwendungsmöglichkeiten nach der Veröffentlichung.",
+  "station.monitoring-and-improving.why_it_matters": "Capabilities brauchen kontinuierliches Feedback, um zuverlässig, wertvoll, kosteneffizient und wiederverwendbar zu bleiben, wenn sich Nutzer, Systeme, Daten und Plattformen ändern.",
+  "station.monitoring-and-improving.apply_in_work": "Nutzen Sie Metriken, Analytics und Feedbackpraktiken, um die Capability kontinuierlich zu verbessern.",
+  "station.monitoring-and-improving.outcomes": "Gemessene Capability-Gesundheit und Wertbeitrag",
+  "station.monitoring-and-improving.how_it_works": "Definieren Sie Metriken für Nutzung, Zuverlässigkeit, Datenqualität, Kosten, Adoption und Nutzerwert.",
   "station.user-experience.title": "Benutzerfreundlichkeit - Entwerfen Sie APIs mit dem Benutzer im Hinterkopf",
   "station.user-experience.description": "Stellen Sie sicher, dass die APIs mit Blick auf den Endnutzer entwickelt werden und eine nahtlose und intuitive Erfahrung bieten.",
-  "station.user-experience.why_it_matters": "APIs sind nicht nur technische Produkte, sondern auch Produkte für die Benutzer. Ein schlechtes Benutzererlebnis kann zu geringer Akzeptanz und Frustration führen. Diese Station hilft Teams bei der Entwicklung von APIs, die benutzerfreundlich sind und die Bedürfnisse der Verbraucher erfüllen.",
+  "station.user-experience.why_it_matters": "APIs sind nicht nur technische Produkte, sondern auch Produkte für die Benutzer. Ein schlechtes Benutzererlebnis kann zu geringer Akzeptanz und Frustration führen. Diese Station hilft Teams bei der Entwicklung von APIs, die benutzerfreundlich sind und die Bedürfnisse der Nutzer erfüllen.",
   "station.user-experience.apply_in_work": "Bereitstellung von Richtlinien, Vorlagen und Tools für die Benutzererfahrung beim API-Design. Sicherstellen, dass die Teams nutzerzentrierte Designpraktiken befolgen und Nutzerfeedback in API-Iterationen einbeziehen.",
   "station.user-experience.outcomes": "APIs, die auf die Bedürfnisse der Nutzer abgestimmt sind",
   "station.user-experience.how_it_works": "Verwendung von User Personas, um die Bedürfnisse und Erwartungen der Endnutzer zu verstehen",
@@ -108,17 +108,17 @@
   "station.design-standards.outcomes": "Einheitliches API-Design in der gesamten Organisation",
   "station.design-standards.how_it_works": "Definition von Designstandards und Richtlinien für das API-Design, einschließlich Benennungskonventionen, Antwortformaten und Fehlerbehandlung.",
   "station.vendor-management.title": "Vendor Management - Verwalten von API-Integrationen von Drittanbietern",
-  "station.vendor-management.description": "Effiziente Verwaltung von Drittanbieter-APIs und Integrationen zur Gewährleistung von Zuverlässigkeit und Konformität.",
-  "station.vendor-management.why_it_matters": "APIs von Drittanbietern können Risiken und Abhängigkeiten mit sich bringen, die sich auf Ihr API-Ökosystem auswirken. Diese Station enthält Richtlinien für die Verwaltung von Anbieterbeziehungen, die Zuverlässigkeit, Konformität und Übereinstimmung mit Ihrer API-Strategie sicherstellen.",
-  "station.vendor-management.apply_in_work": "Bereitstellung von Rahmenwerken für die Anbieterverwaltung, Bewertungskriterien und Überwachungsinstrumenten. Sicherstellen, dass die Teams API-Anbieter von Drittanbietern effektiv verwalten, um Zuverlässigkeit, Konformität und Übereinstimmung mit den Unternehmensstandards zu gewährleisten.",
+  "station.vendor-management.description": "Effiziente Verwaltung von Drittanbieter-APIs und Integrationen zur Gewährleistung von Zuverlässigkeit und Compliance.",
+  "station.vendor-management.why_it_matters": "APIs von Drittanbietern können Risiken und Abhängigkeiten mit sich bringen, die sich auf Ihr API-Ökosystem auswirken. Diese Station enthält Richtlinien für die Verwaltung von Anbieterbeziehungen, die Zuverlässigkeit, Compliance und Übereinstimmung mit Ihrer API-Strategie sicherstellen.",
+  "station.vendor-management.apply_in_work": "Bereitstellung von Rahmenwerken für die Anbieterverwaltung, Bewertungskriterien und Überwachungsinstrumenten. Sicherstellen, dass die Teams API-Anbieter von Drittanbietern effektiv verwalten, um Zuverlässigkeit, Compliance und Übereinstimmung mit den Unternehmensstandards zu gewährleisten.",
   "station.vendor-management.outcomes": "Effektive Prozesse für das Lieferantenmanagement eingeführt",
   "station.vendor-management.how_it_works": "Einführung von Prozessen für das Anbietermanagement, um Drittanbieter von APIs zu bewerten, einzubinden und zu überwachen.",
-  "station.contract-design.title": "Vertragsgestaltung - Definieren Sie klare API-Verträge",
-  "station.contract-design.description": "Erstellen Sie klare und genau definierte API-Verträge, die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien umreißen.",
-  "station.contract-design.why_it_matters": "API-Verträge sind wichtig, um Klarheit und Übereinstimmung zwischen API-Anbietern und Kunden zu gewährleisten. Diese Station bietet Richtlinien für die Gestaltung von API-Verträgen, die klar, umfassend und leicht verständlich sind.",
-  "station.contract-design.apply_in_work": "Bereitstellung von Vertragsentwurfsvorlagen, standardisierten Formaten und Überprüfungsprozessen. Sicherstellen, dass Teams klare und gut definierte API-Verträge erstellen, die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien umreißen.",
-  "station.contract-design.outcomes": "Klare API-Verträge für jede API definiert",
-  "station.contract-design.how_it_works": "Definieren Sie API-Verträge, in denen die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien für jede API festgelegt sind.",
+  "station.contract-design.title": "Vertragsgestaltung - Definieren Sie klare Schnittstellenverträge",
+  "station.contract-design.description": "Erstellen Sie klare und genau definierte Schnittstellenverträge, die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien umreißen.",
+  "station.contract-design.why_it_matters": "Schnittstellenverträge sind wichtig, um Klarheit und Übereinstimmung zwischen API-Anbietern und Kunden zu gewährleisten. Diese Station bietet Richtlinien für die Gestaltung von Schnittstellenverträgen, die klar, umfassend und leicht verständlich sind.",
+  "station.contract-design.apply_in_work": "Bereitstellung von Vertragsentwurfsvorlagen, standardisierten Formaten und Überprüfungsprozessen. Sicherstellen, dass Teams klare und gut definierte Schnittstellenverträge erstellen, die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien umreißen.",
+  "station.contract-design.outcomes": "Klare Schnittstellenverträge für jede API definiert",
+  "station.contract-design.how_it_works": "Definieren Sie Schnittstellenverträge, in denen die Erwartungen, Verantwortlichkeiten und Nutzungsrichtlinien für jede API festgelegt sind.",
   "station.development.title": "Entwicklung - Erstellen von APIs mit bewährten Praktiken",
   "station.development.description": "Implementierung von APIs unter Verwendung von Best Practices und Frameworks zur Gewährleistung von Qualität, Wartbarkeit und Skalierbarkeit.",
   "station.development.why_it_matters": "Die API-Entwicklung ist eine entscheidende Phase, die die Qualität und Zuverlässigkeit der API bestimmt. Diese Station bietet Best Practices und Frameworks für die API-Entwicklung, die sicherstellen, dass APIs nach hohen Standards erstellt werden und effektiv gewartet und skaliert werden können.",
@@ -149,12 +149,12 @@
   "station.service-agreements.apply_in_work": "Bereitstellung von Vorlagen für Servicevereinbarungen, standardisierten Formaten und Überprüfungsprozessen. Stellen Sie sicher, dass die Teams klare und genau definierte Servicevereinbarungen erstellen, in denen die Erwartungen, Servicelevel und Verantwortlichkeiten für API-Anbieter und -Kunden festgelegt sind.",
   "station.service-agreements.outcomes": "Klare Dienstvereinbarungen für jede API definiert",
   "station.service-agreements.how_it_works": "Definieren Sie Servicevereinbarungen, in denen die Erwartungen, Servicelevel und Verantwortlichkeiten für jede API festgelegt sind.",
-  "station.api-consumer-adoption.title": "API-Verbraucherakzeptanz - Förderung der API-Nutzung",
-  "station.api-consumer-adoption.description": "Implementierung von Strategien zur Förderung der Akzeptanz und des Engagements von API-Kunden, um sicherzustellen, dass APIs effektiv genutzt werden.",
-  "station.api-consumer-adoption.why_it_matters": "Die Förderung der Akzeptanz von APIs durch die Verbraucher ist entscheidend für die Realisierung des Werts von APIs. Diese Station bietet Strategien und Best Practices für die Einbindung von API-Nutzern, um sicherzustellen, dass sie verstehen, wie APIs effektiv genutzt werden können und einen Nutzen aus ihnen ziehen.",
-  "station.api-consumer-adoption.apply_in_work": "Bereitstellung von Onboarding-Ressourcen, Lehrmaterial und Strategien zur Einbindung von API-Kunden. Sicherstellen, dass die Teams Strategien umsetzen, die die Akzeptanz, das Engagement und die Zufriedenheit der API-Kunden fördern.",
-  "station.api-consumer-adoption.outcomes": "Strategien zur Übernahme von API durch die Verbraucher umgesetzt",
-  "station.api-consumer-adoption.how_it_works": "Entwicklung von Onboarding-Prozessen und -Ressourcen, damit API-Kunden verstehen, wie sie APIs effektiv nutzen können.",
+  "station.api-consumer-adoption.title": "Nutzerakzeptanz - Förderung der API-Nutzung",
+  "station.api-consumer-adoption.description": "Implementierung von Strategien zur Förderung der Akzeptanz und des Engagements von Nutzer, um sicherzustellen, dass APIs effektiv genutzt werden.",
+  "station.api-consumer-adoption.why_it_matters": "Die Förderung der Akzeptanz von APIs durch die Nutzer ist entscheidend für die Realisierung des Werts von APIs. Diese Station bietet Strategien und Best Practices für die Einbindung von Nutzern, um sicherzustellen, dass sie verstehen, wie APIs effektiv genutzt werden können und einen Nutzen aus ihnen ziehen.",
+  "station.api-consumer-adoption.apply_in_work": "Bereitstellung von Onboarding-Ressourcen, Lehrmaterial und Strategien zur Einbindung von Nutzer. Sicherstellen, dass die Teams Strategien umsetzen, die die Akzeptanz, das Engagement und die Zufriedenheit der Nutzer fördern.",
+  "station.api-consumer-adoption.outcomes": "Strategien zur Übernahme von API durch die Nutzer umgesetzt",
+  "station.api-consumer-adoption.how_it_works": "Entwicklung von Onboarding-Prozessen und -Ressourcen, damit Nutzer verstehen, wie sie APIs effektiv nutzen können.",
   "station.api-promotion.title": "API-Promotion - Erhöhen Sie die Sichtbarkeit und Nutzung von APIs",
   "station.api-promotion.description": "Förderung von APIs, um die Sichtbarkeit, Nutzung und Akzeptanz bei den Zielgruppen zu erhöhen.",
   "station.api-promotion.why_it_matters": "Die Förderung von APIs ist wichtig, um ihre Sichtbarkeit zu erhöhen und ihre Nutzung zu fördern. Diese Station bietet Strategien und Best Practices für eine effektive Werbung für APIs bei den Zielgruppen, um sicherzustellen, dass diese die APIs kennen und ihren Wert verstehen.",
@@ -206,44 +206,44 @@
   "station.api-product-strategy.outcomes.1": "Gemeinsame Sprache zwischen Produkt, Design und Technik",
   "station.api-product-strategy.outcomes.2": "Ein solides Argument für die Finanzierung/Bewilligung",
   "station.api-product-strategy.how_it_works.1": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle Journeys und eventuell APIs zu schaffen.",
-  "station.api-product-strategy.how_it_works.2": "Verwenden Sie das API Value Proposition Canvas, um die unterstützten Geschäftsaufgaben sowie die Probleme, Vorteile und Funktionen für API-Nutzer zu erfassen, die neue oder wiederverwendbare APIs prägen.",
-  "station.api-product-strategy.how_it_works.3": "Definieren Sie den Wert - für die Nutzer und das Unternehmen - mit dem API Business Model Canvas, um Ihre API-Strategie visuell, gemeinsam nutzbar und einfach mit Ihren API-Kunden an der nächsten Station zu validieren.",
+  "station.api-product-strategy.how_it_works.2": "Verwenden Sie das API Value Proposition Canvas, um die unterstützten Geschäftsaufgaben sowie die Probleme, Vorteile und Funktionen für Nutzer zu erfassen, die neue oder wiederverwendbare APIs prägen.",
+  "station.api-product-strategy.how_it_works.3": "Definieren Sie den Wert - für die Nutzer und das Unternehmen - mit dem API Business Model Canvas, um Ihre API-Strategie visuell, gemeinsam nutzbar und einfach mit Ihren Nutzer an der nächsten Station zu validieren.",
   "station.api-consumer-experience.outcomes.1": "Definieren Sie die API-Erlebnisreise",
   "station.api-consumer-experience.outcomes.2": "Onboarding, Dokumentation und Feedback planen",
   "station.api-consumer-experience.outcomes.3": "Verbesserung der Akzeptanz durch echte Empathie + Developer Experience (DX)",
   "station.api-platform-architecture.outcomes.1": "Umsetzung einer einheitlichen Governance ohne starke Kontrolle von oben nach unten",
   "station.api-platform-architecture.outcomes.2": "Design für interne Wiederverwendung und externe Skalierbarkeit",
-  "station.api-platform-architecture.how_it_works.1": "Kartierung der Standorte von API-Anbietern und -Verbrauchern, um die Zugänglichkeit und Einhaltung von Vorschriften zu gewährleisten.",
+  "station.api-platform-architecture.how_it_works.1": "Kartierung der Standorte von API-Anbietern und -Nutzern, um die Zugänglichkeit und Einhaltung von Vorschriften zu gewährleisten.",
   "station.api-platform-architecture.how_it_works.2": "Das Capacity Canvas gleicht geschäftliche Transaktionsmuster, künftige Verbrauchstrends und technische Lösungen ab, um die Skalierbarkeit und Leistung von APIs zu gewährleisten und liefert wichtige Informationen für Skalierungsentscheidungen und die Infrastrukturplanung.",
   "station.api-platform-architecture.how_it_works.3": "Definieren und überwachen Sie Leistungsmetriken (z. B. API-Aufrufe, Latenz, Fehlerraten) und Adoptionsmetriken (z. B. NPS).",
-  "station.api-design.outcomes.1": "Wiederverwendbare und validierte API-Verträge",
+  "station.api-design.outcomes.1": "Wiederverwendbare und validierte Schnittstellenverträge",
   "station.api-design.outcomes.2": "Entwürfe, die auf Domänenmodelle und Interaktionsmuster abgestimmt sind",
   "station.api-design.outcomes.3": "Rückverfolgbarkeit des Designs zum Geschäftswert",
-  "station.api-design.how_it_works.1": "Verwenden Sie das Interaction Canvas, um zu definieren, wie die Verbraucher mit der API interagieren werden, um sicherzustellen, dass sie ihren Bedürfnissen und Erwartungen entspricht.",
-  "station.api-design.how_it_works.2": "Wenden Sie REST-Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
-  "station.api-design.how_it_works.3": "Wenden Sie ereignisgesteuerte Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
-  "station.api-design.how_it_works.4": "Wenden Sie GraphQL-Designmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "station.api-design.how_it_works.1": "Verwenden Sie das Interaction Canvas, um zu definieren, wie die Nutzer mit der API interagieren werden, um sicherzustellen, dass sie ihren Bedürfnissen und Erwartungen entspricht.",
+  "station.api-design.how_it_works.2": "Wenden Sie REST-Entwurfsmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "station.api-design.how_it_works.3": "Wenden Sie ereignisgesteuerte Entwurfsmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "station.api-design.how_it_works.4": "Wenden Sie GraphQL-Designmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
   "station.api-design.how_it_works.5": "Nutzen Sie die Designprinzipien und den API-Styleguide, um Ihre Designentscheidungen an gemeinsamen Regeln auszurichten und eine konsistente Audit-Validierung zu ermöglichen.",
-  "station.api-design.how_it_works.6": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um den API-Vertrag vor der Implementierung zu erfassen und zu validieren.",
+  "station.api-design.how_it_works.6": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um den Schnittstellenvertrag vor der Implementierung zu erfassen und zu validieren.",
   "station.api-design.how_it_works.7": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass das API-Design funktionale und nicht-funktionale Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
   "station.api-delivery.outcomes.1": "Zuverlässige und automatisierte CI/CD-Pipelines",
   "station.api-delivery.outcomes.2": "Funktionale und nicht-funktionale Tests integriert",
-  "station.api-delivery.outcomes.3": "Sichere und gesetzeskonforme Zustellungspipelines",
+  "station.api-delivery.outcomes.3": "Sichere und gesetzeskonforme Bereitstellungspipelines",
   "station.api-delivery.how_it_works.1": "Erstellen Sie die API-Implementierung auf Basis des validierten Vertrags unter Verwendung etablierter Frameworks, Bibliotheken und Teamstandards.",
   "station.api-delivery.how_it_works.2": "Testen Sie APIs auf Funktionalität, Sicherheit und Leistung mit automatisierten Testwerkzeugen.",
   "station.api-delivery.how_it_works.3": "Verwenden Sie CI/CD-Pipelines, um Build-, Test- und Bereitstellungsprozesse zu automatisieren und so konsistente Qualität und Nachvollziehbarkeit zu gewährleisten.",
   "station.api-delivery.how_it_works.4": "Stellen Sie sicher, dass APIs die Sicherheits- und Compliance-Anforderungen durch automatische Prüfungen und Audits erfüllen.",
   "station.api-delivery.how_it_works.5": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass die API die funktionalen und nicht-funktionalen Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
   "station.api-audit.outcomes.1": "Klare Dokumentation des API-Designs und der Implementierungsentscheidungen",
-  "station.api-audit.outcomes.2": "Sicherheit, Leistung und Konformität validiert",
+  "station.api-audit.outcomes.2": "Sicherheit, Leistung und Compliance validiert",
   "station.api-audit.outcomes.3": "Geringeres Risiko von Problemen in der Produktion",
-  "station.api-audit.how_it_works.1": "Verwenden Sie Checklisten, Linters und Testwerkzeuge, um die Konsistenz und Konformität mit den Standards zu überprüfen.",
+  "station.api-audit.how_it_works.1": "Verwenden Sie Checklisten, Linters und Testwerkzeuge, um die Konsistenz und Compliance mit den Standards zu überprüfen.",
   "station.api-audit.how_it_works.2": "Zusammenarbeit mit Governance-Teams und Domänenexperten, um sicherzustellen, dass APIs für die Produktion bereit sind.",
   "station.api-publishing.outcomes.1": "Klare API-Einführungs- und Registrierungsprozesse",
   "station.api-publishing.outcomes.2": "Dokumentation, Sicherheitsmodelle und Richtlinien verfügbar",
   "station.api-publishing.outcomes.3": "APIs bereit für Skalierung und Governance",
-  "station.api-publishing.how_it_works.1": "Dokumentieren Sie, wie die Verbraucher die API finden und nutzen, einschließlich Onboarding-Prozesse und Registrierung.",
-  "station.api-publishing.how_it_works.2": "Stellen Sie sicher, dass die Sicherheitsmodelle, die Gateway-Konfiguration und die rechtlichen Bestimmungen für die Verbraucher klar und verständlich sind.",
+  "station.api-publishing.how_it_works.1": "Dokumentieren Sie, wie die Nutzer die API finden und nutzen, einschließlich Onboarding-Prozesse und Registrierung.",
+  "station.api-publishing.how_it_works.2": "Stellen Sie sicher, dass die Sicherheitsmodelle, die Gateway-Konfiguration und die rechtlichen Bestimmungen für die Nutzer klar und verständlich sind.",
   "station.monitoring-and-improving.outcomes.1": "Feedback-Schleifen für Entwickler sind vorhanden",
   "station.monitoring-and-improving.outcomes.2": "Kontinuierlich ermittelte und behandelte Probleme",
   "station.monitoring-and-improving.outcomes.3": "Iteration der API, abgestimmt auf die Bedürfnisse der Nutzer",
@@ -252,7 +252,7 @@
   "station.user-experience.outcomes.1": "Intuitive und einheitliche Benutzeroberflächen",
   "station.user-experience.outcomes.2": "Nutzer-Feedback in API-Design integriert",
   "station.user-experience.outcomes.3": "Verbesserte Nutzerzufriedenheit und Akzeptanz",
-  "station.user-experience.how_it_works.1": "Führen Sie Nutzerforschung durch, um Erkenntnisse darüber zu gewinnen, wie die Verbraucher mit den Ökosystemdiensten oder Ihren API nutzenden Anwendungen interagieren.",
+  "station.user-experience.how_it_works.1": "Führen Sie Nutzerforschung durch, um Erkenntnisse darüber zu gewinnen, wie die Nutzer mit den Ökosystemdiensten oder Ihren API nutzenden Anwendungen interagieren.",
   "station.user-experience.how_it_works.2": "Dokumentieren Sie die Anforderungen an die Benutzererfahrung, damit sie beim API-Design verwendet werden können, um sicherzustellen, dass sie intuitiv und einfach zu bedienen sind.",
   "station.market-insights.outcomes.1": "Ermittlung von Industriestandards und bewährten Verfahren",
   "station.market-insights.outcomes.2": "API-Strategie auf die Bedürfnisse des Marktes abgestimmt",
@@ -283,7 +283,7 @@
   "station.legal-and-compliance.outcomes.2": "Ermittelte und abgemilderte rechtliche Risiken",
   "station.legal-and-compliance.outcomes.3": "Klare Dokumentation der Compliance-Maßnahmen",
   "station.legal-and-compliance.how_it_works.1": "Implementieren Sie Maßnahmen, die sicherstellen, dass APIs diese Anforderungen erfüllen, einschließlich Datenverschlüsselung, Zugriffskontrollen und Prüfpfade.",
-  "station.legal-and-compliance.how_it_works.2": "Dokumentieren Sie die Maßnahmen zur Einhaltung der Vorschriften und stellen Sie sicher, dass sie den Beteiligten und Verbrauchern mitgeteilt werden.",
+  "station.legal-and-compliance.how_it_works.2": "Dokumentieren Sie die Maßnahmen zur Einhaltung der Vorschriften und stellen Sie sicher, dass sie den Beteiligten und Nutzern mitgeteilt werden.",
   "station.security-and-privacy.outcomes.1": "Schutz der Nutzerdaten durch Maßnahmen zum Schutz der Privatsphäre",
   "station.security-and-privacy.outcomes.2": "Bewährte Sicherheitspraktiken bei der Gestaltung und Entwicklung von APIs",
   "station.security-and-privacy.outcomes.3": "Einhaltung von Sicherheitsstandards und -vorschriften",
@@ -299,15 +299,15 @@
   "station.vendor-management.outcomes.3": "Geringere Risiken im Zusammenhang mit Abhängigkeiten von Dritten",
   "station.vendor-management.how_it_works.1": "Definieren Sie Kriterien für die Bewertung von Anbieter-APIs, einschließlich Zuverlässigkeit, Sicherheit und Compliance.",
   "station.vendor-management.how_it_works.2": "Überwachung der Leistung von Anbietern und der Einhaltung von Service Level Agreements (SLAs) und Organisationsstandards.",
-  "station.contract-design.outcomes.1": "Umriss der Erwartungen und Verantwortlichkeiten von API-Anbietern und Verbrauchern",
+  "station.contract-design.outcomes.1": "Umriss der Erwartungen und Verantwortlichkeiten von API-Anbietern und Nutzern",
   "station.contract-design.outcomes.2": "Dokumentierte Verwendungsrichtlinien und bewährte Verfahren",
   "station.contract-design.outcomes.3": "Weniger Missverständnisse und Streitigkeiten über die API-Nutzung",
-  "station.contract-design.how_it_works.1": "Verwenden Sie standardisierte Formate (z. B. OpenAPI, AsyncAPI), um maschinenlesbare API-Verträge zu erstellen, die sich leicht austauschen und validieren lassen.",
-  "station.contract-design.how_it_works.2": "Sicherstellen, dass die API-Verträge von den Beteiligten geprüft und genehmigt werden, um Übereinstimmung und Klarheit zu gewährleisten.",
+  "station.contract-design.how_it_works.1": "Verwenden Sie standardisierte Formate (z. B. OpenAPI, AsyncAPI), um maschinenlesbare Schnittstellenverträge zu erstellen, die sich leicht austauschen und validieren lassen.",
+  "station.contract-design.how_it_works.2": "Sicherstellen, dass die Schnittstellenverträge von den Beteiligten geprüft und genehmigt werden, um Übereinstimmung und Klarheit zu gewährleisten.",
   "station.development.outcomes.1": "Hochwertige, wartbare und skalierbare APIs",
   "station.development.outcomes.2": "Befolgung einheitlicher Kodierungsstandards und -praktiken",
   "station.development.outcomes.3": "Geringere Entwicklungszeit und weniger technische Schulden",
-  "station.development.how_it_works.1": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um sicherzustellen, dass API-Verträge vor der Implementierung validiert werden.",
+  "station.development.how_it_works.1": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um sicherzustellen, dass Schnittstellenverträge vor der Implementierung validiert werden.",
   "station.development.how_it_works.2": "Befolgen Sie Kodierungsstandards und bewährte Verfahren, um eine konsistente und hochwertige API-Entwicklung zu gewährleisten.",
   "station.ci-cd.outcomes.1": "Konsistente Qualität und Rückverfolgbarkeit bei der API-Lieferung",
   "station.ci-cd.outcomes.2": "Schnellere Iterationen und kürzere Markteinführungszeiten",
@@ -324,19 +324,19 @@
   "station.release-management.outcomes.3": "Geringere Risiken im Zusammenhang mit API-Änderungen",
   "station.release-management.how_it_works.1": "Implementierung von Bereitstellungsstrategien (z. B. blau-grüne Bereitstellungen, Canary-Releases) zur Minimierung der Risiken bei API-Releases.",
   "station.release-management.how_it_works.2": "Einführung von Rollback-Verfahren zur schnellen Rückgängigmachung von Änderungen im Falle von Problemen bei API-Releases.",
-  "station.service-agreements.outcomes.1": "Erwartungen und Dienstleistungsniveaus für API-Anbieter und Verbraucher",
+  "station.service-agreements.outcomes.1": "Erwartungen und Dienstleistungsniveaus für API-Anbieter und Nutzer",
   "station.service-agreements.outcomes.2": "Zuständigkeiten und Unterstützungsprozesse dokumentiert",
   "station.service-agreements.outcomes.3": "Verbesserte Kommunikation und Zusammenarbeit zwischen API-Teams",
   "station.service-agreements.how_it_works.1": "Verwenden Sie standardisierte Formate, um maschinenlesbare Servicevereinbarungen zu erstellen, die sich leicht austauschen und validieren lassen.",
   "station.service-agreements.how_it_works.2": "Sicherstellen, dass die Dienstleistungsvereinbarungen von den Beteiligten überprüft und genehmigt werden, um die Übereinstimmung und Klarheit zu gewährleisten.",
   "station.api-consumer-adoption.outcomes.1": "Erhöhte API-Nutzung und Engagement",
-  "station.api-consumer-adoption.outcomes.2": "API-Kunden werden über die Funktionen und Vorteile von APIs aufgeklärt",
-  "station.api-consumer-adoption.outcomes.3": "Verbesserte Zufriedenheit und Loyalität der API-Kunden",
+  "station.api-consumer-adoption.outcomes.2": "Nutzer werden über die Funktionen und Vorteile von APIs aufgeklärt",
+  "station.api-consumer-adoption.outcomes.3": "Verbesserte Zufriedenheit und Loyalität der Nutzer",
   "station.api-consumer-adoption.how_it_works.1": "Erstellung von Lehrmaterial (z. B. Tutorials, Dokumentation), das die Funktionen, Vorteile und Nutzungsmuster der API erläutert.",
   "station.api-consumer-adoption.how_it_works.2": "Engagieren Sie sich mit API-Benutzern über Feedbackschleifen, Support-Kanäle und Community-Foren, um ihre Bedürfnisse zu verstehen und die API-Akzeptanz zu verbessern.",
   "station.api-promotion.outcomes.1": "Erhöhte Sichtbarkeit und Bekanntheit von API",
   "station.api-promotion.outcomes.2": "Höhere API-Nutzungs- und Akzeptanzraten",
-  "station.api-promotion.outcomes.3": "Verbesserte API-Kundenbindung und -zufriedenheit",
+  "station.api-promotion.outcomes.3": "Verbesserte Nutzerbindung und -zufriedenheit",
   "station.api-promotion.how_it_works.1": "Erstellen Sie Werbematerialien (z. B. Fallstudien, Erfolgsgeschichten), die den Wert und die Vorteile von APIs hervorheben.",
   "station.api-promotion.how_it_works.2": "Engagieren Sie sich in API-Gemeinschaften und Foren, um API-Aktualisierungen weiterzugeben, Feedback zu sammeln und die API-Nutzung zu fördern.",
   "station.partner-integration.outcomes.1": "Verbesserte API-Funktionen durch Partner-APIs",
@@ -383,16 +383,16 @@
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Gemeinsame Sprache zwischen Produkt, Design und Technik",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Ein solides Argument für die Finanzierung/Bewilligung",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle Journeys und eventuell APIs zu schaffen.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Verwenden Sie das API Value Proposition Canvas, um die unterstützten Geschäftsaufgaben sowie die Probleme, Vorteile und Funktionen für API-Nutzer zu erfassen, die neue oder wiederverwendbare APIs prägen.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Definieren Sie den Wert - für die Nutzer und das Unternehmen - mit dem API Business Model Canvas, um Ihre API-Strategie visuell, gemeinsam nutzbar und einfach mit Ihren API-Kunden an der nächsten Station zu validieren.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Verwenden Sie das API Value Proposition Canvas, um die unterstützten Geschäftsaufgaben sowie die Probleme, Vorteile und Funktionen für Nutzer zu erfassen, die neue oder wiederverwendbare APIs prägen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Definieren Sie den Wert - für die Nutzer und das Unternehmen - mit dem API Business Model Canvas, um Ihre API-Strategie visuell, gemeinsam nutzbar und einfach mit Ihren Nutzer an der nächsten Station zu validieren.",
   "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design für die echten Benutzer Ihrer API",
   "cycle.api-productization-cycle.station.api-consumer-experience.description": "Stellen Sie sicher, dass Ihre API auffindbar, verständlich und nutzbar ist - vor und nach der Einführung.",
   "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Großartige APIs funktionieren nicht nur - sie fühlen sich auch intuitiv an. Ganz gleich, ob Ihr Kunde ein interner Entwickler, ein externer Partner oder ein KI-Agent ist, seine Erfahrung entscheidet über die Akzeptanz.\n\nOhne einen klaren Erlebnisplan:\n- Großartige APIs bleiben ungenutzt\n- Teams verschwenden Zeit damit, zu raten, wie sie Ihre API verwenden sollen\n- Feedbackschleifen sind unterbrochen oder fehlen.\n\nDiese Station hilft Ihnen, Ihre API mit den Augen ihrer Nutzer zu sehen.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Überprüfen Sie das bestehende API Value Proposition Canvаs von der Perspektive des API-Nutzers. Stellen Sie die Stabilität der unterstützten Geschäftsprozesse sicher und ergänzen Sie die Funktionen, die Probleme lösen und Vorteile bieten, um die Bedürfnisse der API-Nutzer zu berücksichtigen, damit diese spätere Designentscheidungen leiten können.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des API-Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den API-Nutzer zu verbessern.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Überprüfen Sie das bestehende API Value Proposition Canvаs von der Perspektive des Nutzers. Stellen Sie die Stabilität der unterstützten Geschäftsprozesse sicher und ergänzen Sie die Funktionen, die Probleme lösen und Vorteile bieten, um die Bedürfnisse der Nutzer zu berücksichtigen, damit diese spätere Designentscheidungen leiten können.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Verwenden Sie das Customer Journey Canvas für die Customer Journey des Nutzers von der Entdeckung und Bewertung bis hin zu Onboarding, Integration, Fehlerbehebung und fortlaufender Nutzung.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Nutzen Sie die daraus resultierende Customer Journey, um Onboarding, Dokumentation, Support und Feedback-Schleifen für den Nutzer zu verbessern.",
   "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Bereitstellung von Richtlinien, Tools und Feedback-Mechanismen für das Verständnis, die Analyse und die Verbesserung der internen und externen Erfahrungen von Entwicklern und Partnern.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifizieren und priorisieren Sie Ihre API-Kunden",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifizieren und priorisieren Sie Ihre Nutzer",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Definieren Sie die API-Erlebnisreise",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Onboarding, Dokumentation und Feedback planen",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Verbesserung der Akzeptanz durch echte Empathie + Developer Experience (DX)",
@@ -404,7 +404,7 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Das Business Impact Canvas hilft dabei, Risiken in Bezug auf API-Verfügbarkeit, -Sicherheit und -Funktionalität zu identifizieren und zu mindern, um fundierte Architekturentscheidungen zu unterstützen.",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Umsetzung einer einheitlichen Governance ohne starke Kontrolle von oben nach unten",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Design für interne Wiederverwendung und externe Skalierbarkeit",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartierung der Standorte von API-Anbietern und -Verbrauchern, um die Zugänglichkeit und Einhaltung von Vorschriften zu gewährleisten.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartierung der Standorte von API-Anbietern und -Nutzern, um die Zugänglichkeit und Einhaltung von Vorschriften zu gewährleisten.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Das Capacity Canvas gleicht geschäftliche Transaktionsmuster, künftige Verbrauchstrends und technische Lösungen ab, um die Skalierbarkeit und Leistung von APIs zu gewährleisten und liefert wichtige Informationen für Skalierungsentscheidungen und die Infrastrukturplanung.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Definieren und überwachen Sie Leistungsmetriken (z. B. API-Aufrufe, Latenz, Fehlerraten) und Adoptionsmetriken (z. B. NPS).",
   "cycle.api-productization-cycle.station.api-design.title": "API-Design - Entwerfen Sie APIs, die Wert liefern",
@@ -413,52 +413,52 @@
   "cycle.api-productization-cycle.station.api-design.apply_in_work": "Bereitstellung von wiederverwendbaren Designmustern, gemeinsamen Standards und Validierungstools für API-Spezifikationen. Sicherstellen, dass Designentscheidungen konsistent, frühzeitig überprüft und auf die Geschäftsabsicht ausgerichtet sind.",
   "cycle.api-productization-cycle.station.api-design.outcomes": "Gut dokumentierte und konsistente API-Designs",
   "cycle.api-productization-cycle.station.api-design.how_it_works": "Definieren Sie zentrale Entitäten, ihre Attribute und Beziehungen, um ein gemeinsames konzeptionelles Verständnis für alle APIs zu schaffen.",
-  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Wiederverwendbare und validierte API-Verträge",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Wiederverwendbare und validierte API-Schnittstellenverträge",
   "cycle.api-productization-cycle.station.api-design.outcomes.2": "Entwürfe, die auf Domänenmodelle und Interaktionsmuster abgestimmt sind",
   "cycle.api-productization-cycle.station.api-design.outcomes.3": "Rückverfolgbarkeit des Designs zum Geschäftswert",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Verwenden Sie das Interaction Canvas, um zu definieren, wie die Verbraucher mit der API interagieren werden, um sicherzustellen, dass sie ihren Bedürfnissen und Erwartungen entspricht.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Wenden Sie REST-Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Wenden Sie ereignisgesteuerte Entwurfsmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Wenden Sie GraphQL-Designmuster an, um konsistente, wiederverwendbare API-Verträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Verwenden Sie das Interaction Canvas, um zu definieren, wie die Nutzer mit der API interagieren werden, um sicherzustellen, dass sie ihren Bedürfnissen und Erwartungen entspricht.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Wenden Sie REST-Entwurfsmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Wenden Sie ereignisgesteuerte Entwurfsmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Wenden Sie GraphQL-Designmuster an, um konsistente, wiederverwendbare Schnittstellenverträge zu erstellen, die mit den Beteiligten validiert werden.",
   "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Nutzen Sie die Designprinzipien und den API-Styleguide, um Ihre Designentscheidungen an gemeinsamen Regeln auszurichten und eine konsistente Audit-Validierung zu ermöglichen.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um den API-Vertrag vor der Implementierung zu erfassen und zu validieren.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Wenden Sie Contract-First- oder Design-First-Ansätze an, um den API-Schnittstellenvertrag vor der Implementierung zu erfassen und zu validieren.",
   "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass das API-Design funktionale und nicht-funktionale Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
   "cycle.api-productization-cycle.station.api-delivery.title": "API-Bereitstellung - Bereitstellung sicherer und zuverlässiger APIs",
   "cycle.api-productization-cycle.station.api-delivery.description": "Erstellen, Testen und Freigeben von APIs unter Verwendung moderner Bereitstellungspipelines und bewährter technischer Verfahren.",
   "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Selbst die besten API-Designs scheitern, wenn die Bereitstellung uneinheitlich ist. Diese Station stellt sicher, dass Ihre APIs qualitativ hochwertig erstellt, gründlich getestet und zuverlässig bereitgestellt werden - für schnellere Iterationen und mehr Vertrauen.",
-  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Bereitstellung von Kodierungsrahmen, Bibliotheken und Standards für die API-Implementierung. Implementierung von CI/CD-Pipelines, Qualitätssicherungs-Frameworks und Tools zur Automatisierung der Bereitstellung.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Bereitstellung von Frameworks, Bibliotheken und Standards für die API-Implementierung. Implementierung von CI/CD-Pipelines, Qualitätssicherungs-Frameworks und Tools zur Automatisierung der Bereitstellung.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs, die mit getesteten Frameworks und Mustern implementiert werden",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Verwenden Sie Best Practices für die API-Entwicklung als Leitfaden für die Implementierung des validierten Vertrags mit etablierten Frameworks und Bibliotheken, um sicherzustellen, dass das Ergebnis wiederverwendbar und wartbar ist.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Verwenden Sie Best Practices für die API-Entwicklung als Leitfaden für die Implementierung des validierten Schnittstellenvertrags mit etablierten Frameworks und Bibliotheken, um sicherzustellen, dass das Ergebnis wiederverwendbar und wartbar ist.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Zuverlässige und automatisierte CI/CD-Pipelines",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Funktionale und nicht-funktionale Tests integriert",
-  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Sichere und gesetzeskonforme Zustellungspipelines",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Erstellen Sie die API-Implementierung auf Basis des validierten Vertrags unter Verwendung etablierter Frameworks, Bibliotheken und Teamstandards.",
+  "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Sichere und gesetzeskonforme Bereitstellungspipelines",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Erstellen Sie die API-Implementierung auf Basis des validierten Schnittstellenvertrags unter Verwendung etablierter Frameworks, Bibliotheken und Teamstandards.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testen Sie APIs auf Funktionalität, Sicherheit und Leistung mit automatisierten Testwerkzeugen.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Verwenden Sie CI/CD-Pipelines, um Build-, Test- und Bereitstellungsprozesse zu automatisieren und so konsistente Qualität und Nachvollziehbarkeit zu gewährleisten.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Stellen Sie sicher, dass APIs die Sicherheits- und Compliance-Anforderungen durch automatische Prüfungen und Audits erfüllen.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Verwenden Sie die API-Audit-Checkliste, um sicherzustellen, dass die API die funktionalen und nicht-funktionalen Anforderungen erfüllt, einschließlich Sicherheit, Leistung und Compliance.",
-  "cycle.api-productization-cycle.station.api-audit.title": "API-Audit - Prüfung von APIs auf Konformität und Qualität",
+  "cycle.api-productization-cycle.station.api-audit.title": "API-Audit - Prüfung von APIs auf Compliance und Qualität",
   "cycle.api-productization-cycle.station.api-audit.description": "Stellen Sie sicher, dass APIs vor der Veröffentlichung und Bereitstellung den geschäftlichen, gestalterischen und betrieblichen Standards entsprechen.",
   "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs sind langlebige Produkte und müssen den Erwartungen hinsichtlich Qualität, Konsistenz und Compliance entsprechen. Das Audit verbindet Designentscheidungen, Implementierung und Betriebsbereitschaft mit definierten Standards und reduziert so Risiken vor der Bereitstellung.",
   "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Richten Sie einen konsistenten Audit-Prozess ein, der die API-Bereitschaft über alle Lebenszyklusphasen hinweg anhand definierter Kriterien, Nachweise und Standards bewertet. Stellen Sie sicher, dass Lücken frühzeitig erkannt und vor der Veröffentlichung behoben werden.",
   "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs erfüllen interne und externe Standards",
   "cycle.api-productization-cycle.station.api-audit.how_it_works": "Führen Sie Audits durch, um sicherzustellen, dass APIs vor der Veröffentlichung organisatorische, technische und rechtliche Standards erfüllen.",
   "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Klare Dokumentation des API-Designs und der Implementierungsentscheidungen",
-  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Sicherheit, Leistung und Konformität validiert",
+  "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Sicherheit, Leistung und Compliance validiert",
   "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Geringeres Risiko von Problemen in der Produktion",
-  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Verwenden Sie Checklisten, Linters und Testwerkzeuge, um die Konsistenz und Konformität mit den Standards zu überprüfen.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Verwenden Sie Checklisten, Linters und Testwerkzeuge, um die Konsistenz und Compliance mit den Standards zu überprüfen.",
   "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Zusammenarbeit mit Governance-Teams und Domänenexperten, um sicherzustellen, dass APIs für die Produktion bereit sind.",
   "cycle.api-productization-cycle.station.api-publishing.title": "API-Veröffentlichung - Veröffentlichen Sie APIs mit Zuversicht",
   "cycle.api-productization-cycle.station.api-publishing.description": "Stellen Sie APIs mit der richtigen Dokumentation und den richtigen Prozessen sicher und klar für die richtige Zielgruppe bereit.",
   "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Bei der Veröffentlichung geht es nicht nur um die Bereitstellung, sondern auch um die Auffindbarkeit, den Zugang und die Unterstützung. Wenn APIs nicht korrekt veröffentlicht werden, können sie nicht verwendet, wiederverwendet oder effektiv gesichert werden.",
-  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Ermöglichung der Veröffentlichung von APIs in der jeweiligen Umgebung mit klaren Registrierungs- und Zugriffsmechanismen (z. B. API-Schlüssel, OAuth, Abonnementpläne) je nach den API-Verbrauchersegmenten und den Sicherheits- und Compliance-Anforderungen.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Ermöglichung der Veröffentlichung von APIs in der jeweiligen Umgebung mit klaren Registrierungs- und Zugriffsmechanismen (z. B. API-Schlüssel, OAuth, Abonnementpläne) je nach den Nutzersegmenten und den Sicherheits- und Compliance-Anforderungen.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes": "Veröffentlichung von APIs in der richtigen Umgebung (privat, Partner, öffentlich)",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Veröffentlichen Sie APIs in den entsprechenden Gateways und Umgebungen, um die Wiederverwendbarkeit für mehrere API-Kunden zu unterstützen.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Veröffentlichen Sie APIs in den entsprechenden Gateways und Umgebungen, um die Wiederverwendbarkeit für mehrere Nutzer zu unterstützen.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Klare API-Einführungs- und Registrierungsprozesse",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Dokumentation, Sicherheitsmodelle und Richtlinien verfügbar",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIs bereit für Skalierung und Governance",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Dokumentieren Sie, wie die Verbraucher die API finden und nutzen, einschließlich Onboarding-Prozesse und Registrierung.",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Stellen Sie sicher, dass die Sicherheitsmodelle, die Gateway-Konfiguration und die rechtlichen Bestimmungen für die Verbraucher klar und verständlich sind.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Dokumentieren Sie, wie die Nutzer die API finden und nutzen, einschließlich Onboarding-Prozesse und Registrierung.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Stellen Sie sicher, dass die Sicherheitsmodelle, die Gateway-Konfiguration und die rechtlichen Bestimmungen für die Nutzer klar und verständlich sind.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Überwachen und Verbessern - für den API-Wert",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Nutzen Sie Messgrößen und Feedback, um die API-Leistung zu verfolgen und kontinuierliche Verbesserungen voranzutreiben.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "Die API-Bereitstellung endet nicht mit dem Start. Ohne Überwachung können Teams weder die Akzeptanz noch die Leistung oder den ROI verbessern. Diese Station stellt sicher, dass APIs nützlich und sicher bleiben und sich mit den Geschäftsanforderungen weiterentwickeln.",
diff --git a/src/data/method/en/labels.criteria.json b/src/data/method/en/labels.criteria.json
index 1725671..41ae368 100644
--- a/src/data/method/en/labels.criteria.json
+++ b/src/data/method/en/labels.criteria.json
@@ -1,25 +1,25 @@
 {
   "exit_criteria": "Exit criteria",
   "entry_criteria": "Entry criteria",
-  "criterion.metrics-feedback-available": "Relevant market signals, feedback, or operational insights are available to guide this API opportunity.",
+  "criterion.metrics-feedback-available": "Relevant market signals, feedback, or operational insights are available to guide this capability opportunity.",
   "criterion.business-goals-defined": "Business goals are defined.",
-  "criterion.market-research-done": "Market research identifies API opportunities.",
-  "criterion.stakeholder-approval": "Relevant stakeholders agree this API opportunity is worth exploring and prioritizing.",
-  "criterion.api-opportunity-documented": "Individual API opportunities are identified and documented.",
-  "criterion.api-reusability": "The API meets a clear business need and is reusable for multiple API consumers.",
-  "criterion.hide-backend-discrepancies": "The API is intended to shield consumers from backend complexity and inconsistencies.",
-  "criterion.value-prop-validated": "The API value proposition has been reviewed and validated with the relevant business and consumer stakeholders.",
-  "criterion.consumer-segments-identified": "API consumer segments (internal and external) are identified.",
-  "criterion.api-roadmap-defined": "High-level roadmaps for API development are established.",
-  "criterion.architecture-patterns-validated": "The chosen API architecture and platform patterns have been validated with the relevant architecture, security, and platform stakeholders.",
-  "criterion.design-reflects-business-value": "The API design and exposed capabilities clearly trace back to business value and user needs.",
-  "criterion.api-consistency": "The API design follows our shared API product and design conventions.",
-  "criterion.api-contract-tested": "The API contract is tested and meets functional and non-functional requirements.",
-  "criterion.api-description-available": "The API and its exposed capabilities are described clearly enough for review, audit, and onboarding.",
-  "criterion.audit-passed": "The API passes compliance, security, and audit checks.",
+  "criterion.market-research-done": "Market research identifies capability opportunities.",
+  "criterion.stakeholder-approval": "Relevant stakeholders agree this capability opportunity is worth exploring and prioritizing.",
+  "criterion.api-opportunity-documented": "Capability opportunity is identified and documented.",
+  "criterion.api-reusability": "The capability addresses a clear business need and is reusable by its intended consumers.",
+  "criterion.hide-backend-discrepancies": "The selected interface provides an appropriate abstraction for consumers.",
+  "criterion.value-prop-validated": "The capability value proposition has been validated with business and consumer stakeholders.",
+  "criterion.consumer-segments-identified": "Consumer segments are identified.",
+  "criterion.api-roadmap-defined": "A high-level implementation roadmap is defined.",
+  "criterion.architecture-patterns-validated": "The chosen architecture, platform, and delivery approach have been validated with the relevant architecture, security, and platform stakeholders.",
+  "criterion.design-reflects-business-value": "The interface design and exposed capabilities trace back to business value and consumer needs.",
+  "criterion.api-consistency": "The interface design follows agreed design standards and conventions.",
+  "criterion.api-contract-tested": "The interface contract has been validated and tested against functional and non-functional requirements.",
+  "criterion.api-description-available": "The interface and its capabilities are documented clearly enough for review, audit, and onboarding.",
+  "criterion.audit-passed": "The solution passes quality, security, compliance, and readiness checks.",
   "criterion.audit-reports-shared": "Audit findings and remediation decisions are shared with the relevant stakeholders.",
-  "criterion.api-ready-for-publishing": "The API is ready to be deployed and exposed through the intended gateways and environments.",
-  "criterion.api-documentation-ready": "Consumer-facing API documentation is complete enough for publishing and onboarding.",
-  "criterion.consumer-support-ready": "Registration, support, and communication processes are ready for API consumers.",
-  "criterion.legal-compliance-clear": "Legal, privacy, and compliance requirements for publishing are defined and understood."
+  "criterion.api-ready-for-publishing": "The capability is ready for release through the selected delivery mechanism.",
+  "criterion.api-documentation-ready": "Consumer-facing documentation and onboarding materials are ready.",
+  "criterion.consumer-support-ready": "Consumer onboarding, support, and communication processes are ready.",
+  "criterion.legal-compliance-clear": "Legal, privacy, and compliance requirements for release are defined and understood."
 }
diff --git a/src/data/method/en/labels.cycles.json b/src/data/method/en/labels.cycles.json
index 1af68da..23d5f16 100644
--- a/src/data/method/en/labels.cycles.json
+++ b/src/data/method/en/labels.cycles.json
@@ -1,6 +1,6 @@
 {
   "cycles.title": "Cycle Views",
-  "cycles.description": "Audience-specific views over the APIOps Cycles method graph.",
+  "cycles.description": "Audience-specific views over the APIOps Cycles method",
   "cycle.capability-productization-cycle.title": "Capability Productization Cycle",
   "cycle.capability-productization-cycle.description": "A cycle for turning business capabilities into reusable digital capabilities before selecting the implementation style.",
   "cycle.capability-productization-cycle.purpose": "Identify and productize reusable digital capabilities before deciding whether the delivery style should be APIs, events, files, streams, data products, AI-enabled services, direct integration, or a hybrid pattern.",
@@ -34,11 +34,11 @@
   "cycle.station.integration-readiness-assurance": "Integration Readiness Assurance",
   "cycle.station.capability-publishing": "Capability Publishing",
   "cycle.station.integration-monitoring-improvement": "Integration Monitoring & Improvement",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API’s value, users, and business goals from day one.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define the capability’s value, consumers, ownership, and business goals.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities.",
   "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to choose architecture and platform capabilities.",
-  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract.",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver and operate the selected solution mechanism.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the interface contract and interaction model for the selected delivery style.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Build, test, deploy, and operate the capability using the selected delivery style and validated interface contract.",
   "cycle.capability-productization-cycle.station.api-audit.description": "Assure quality, governance, and readiness before release.",
   "cycle.capability-productization-cycle.station.api-publishing.description": "Publish capability information so consumers can discover, request, onboard, and get support.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities.",
@@ -63,8 +63,8 @@
   "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting a pattern.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.",
   "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decide the integration architecture, platform capabilities, constraints, and governance model for the capability.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Design the integration solution, contracts, payloads, events, APIs, files, or interaction patterns selected for the capability.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability across its selected delivery pattern.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Design the interface contract, payloads, events, APIs, files, or interaction patterns selected for the integration capability.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability using its selected delivery pattern and validated interface contract.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.",
   "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover, request, reuse, onboard, and get support.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.",
@@ -85,9 +85,9 @@
   "cycle.automation-cycle.station.api-product-strategy.description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.",
   "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration model, governance controls, and operational constraints.",
-  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, and exception paths.",
-  "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation with clear ownership and rollback paths.",
+  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, interface contracts, and exception paths.",
+  "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation using clear ownership, controls, and rollback paths.",
   "cycle.automation-cycle.station.api-audit.description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.",
   "cycle.automation-cycle.station.api-publishing.description": "Enable users and operators with discovery, onboarding, operating instructions, support paths, and change communication.",
   "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities."
-}
+}
\ No newline at end of file
diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json
index 1434975..e4be48c 100644
--- a/src/data/method/en/labels.stations.json
+++ b/src/data/method/en/labels.stations.json
@@ -35,49 +35,49 @@
   "station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
   "station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
   "station.api-design.title": "Solution & Interface Design",
-  "station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
-  "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-  "station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
-  "station.api-design.outcomes": "A designed contract for the selected pattern",
-  "station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+  "station.api-design.description": "Design the interface contract and interaction model after the architecture choice is justified.",
+  "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+  "station.api-design.apply_in_work": "Select the design resources that fit the chosen delivery style and document the interface contract before implementation.",
+  "station.api-design.outcomes": "A validated interface contract for the selected delivery style",
+  "station.api-design.outcomes.1": "Consistent interaction, data, event, file, workflow, or API contract decisions",
   "station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
   "station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
   "station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
-  "station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
-  "station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
-  "station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
-  "station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+  "station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers, systems, or users interact with the capability.",
+  "station.api-design.how_it_works.2": "Use REST design resources when the selected interface is a REST API.",
+  "station.api-design.how_it_works.3": "Use Event Canvas resources when the selected interface is event-driven.",
+  "station.api-design.how_it_works.4": "Use GraphQL design resources when the selected interface is GraphQL.",
   "station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
-  "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+  "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the interface contract before implementation.",
   "station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
   "station.api-delivery.title": "Delivery & Operations",
-  "station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+  "station.api-delivery.description": "Deliver the selected delivery style with appropriate engineering, testing, security, automation, and operational practices.",
   "station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-  "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
-  "station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+  "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the chosen delivery style.",
+  "station.api-delivery.outcomes": "A delivered capability aligned with the validated interface contract",
   "station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
   "station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
   "station.api-delivery.outcomes.3": "Traceable delivery and release controls",
-  "station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
-  "station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+  "station.api-delivery.how_it_works": "Use development best practices to implement the validated interface contract with established frameworks, libraries, and team standards.",
+  "station.api-delivery.how_it_works.1": "Build the implementation from the validated interface contract using established frameworks, libraries, and team standards.",
   "station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
   "station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
   "station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
   "station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
   "station.api-audit.title": "Quality & Readiness Assurance",
-  "station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+  "station.api-audit.description": "Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
   "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
   "station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
   "station.api-audit.outcomes": "Documented readiness for release and reuse",
   "station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
   "station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
   "station.api-audit.outcomes.3": "Reduced risk of issues in production",
-  "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+  "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for interface contract, documentation, security, performance, and compliance readiness.",
   "station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
   "station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
   "station.api-publishing.title": "Publishing & Enablement",
   "station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
-  "station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+  "station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their interface contract and service expectations, request access, and know who owns support and lifecycle decisions.",
   "station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
   "station.api-publishing.outcomes": "A discoverable reusable capability",
   "station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
@@ -471,7 +471,7 @@
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
   "cycle.capability-productization-cycle.station.api-product-strategy.title": "Strategy",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability before choosing the implementation style.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define the capability’s value, consumers, ownership, and business goals.",
   "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
   "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
   "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
@@ -504,49 +504,49 @@
   "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
   "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
   "cycle.capability-productization-cycle.station.api-design.title": "Solution & Interface Design",
-  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract after the architecture choice is justified.",
-  "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-  "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen architecture pattern and document the contract before implementation.",
-  "cycle.capability-productization-cycle.station.api-design.outcomes": "A designed contract for the selected pattern",
-  "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, or API contract decisions",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the interface contract and interaction model for the selected delivery style.",
+  "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
+  "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen delivery style and document the interface contract before implementation.",
+  "cycle.capability-productization-cycle.station.api-design.outcomes": "A validated interface contract for the selected delivery style",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, workflow, or API contract decisions",
   "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
   "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
   "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers interact with the capability.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected pattern is a REST API.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected pattern is event-driven integration.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected pattern is GraphQL.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers, systems, or users interact with the capability.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected interface is a REST API.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected interface is event-driven.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected interface is GraphQL.",
   "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the contract before implementation.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the interface contract before implementation.",
   "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
   "cycle.capability-productization-cycle.station.api-delivery.title": "Delivery & Operations",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver the selected solution mechanism with appropriate engineering, testing, security, automation, and operational practices.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Build, test, deploy, and operate the capability using the selected delivery style and validated interface contract.",
   "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-  "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the selected solution style.",
-  "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the selected contract",
+  "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the chosen delivery style.",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the validated interface contract",
   "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
   "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
   "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Traceable delivery and release controls",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated contract using established frameworks, libraries, and team standards.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated contract using established frameworks, libraries, and team standards.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated interface contract with established frameworks, libraries, and team standards.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated interface contract using established frameworks, libraries, and team standards.",
   "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
   "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
   "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
   "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
   "cycle.capability-productization-cycle.station.api-audit.title": "Quality & Readiness Assurance",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
   "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
   "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
   "cycle.capability-productization-cycle.station.api-audit.outcomes": "Documented readiness for release and reuse",
   "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
   "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
   "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
-  "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for contract, documentation, security, performance, and compliance readiness.",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for interface contract, documentation, security, performance, and compliance readiness.",
   "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
   "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
   "cycle.capability-productization-cycle.station.api-publishing.title": "Publishing & Enablement",
   "cycle.capability-productization-cycle.station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
-  "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their contract and service expectations, request access, and know who owns support and lifecycle decisions.",
+  "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their interface contract and service expectations, request access, and know who owns support and lifecycle decisions.",
   "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
   "cycle.capability-productization-cycle.station.api-publishing.outcomes": "A discoverable reusable capability",
   "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
@@ -566,4 +566,4 @@
   "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
-}
+}
\ No newline at end of file
diff --git a/src/data/method/fi/labels.criteria.json b/src/data/method/fi/labels.criteria.json
index c9dbb06..0bb354e 100644
--- a/src/data/method/fi/labels.criteria.json
+++ b/src/data/method/fi/labels.criteria.json
@@ -1,25 +1,25 @@
 {
   "exit_criteria": "Poistumiskriteerit",
-  "entry_criteria": "Pääsykriteerit",
-  "criterion.metrics-feedback-available": "Olennaiset markkinasignaalit, palautteet tai toiminnalliset lähtötiedot ovat saatavilla ohjaamaan tätä API-mahdollisuutta.",
+  "entry_criteria": "Sisäänpääsykriteerit",
+  "criterion.metrics-feedback-available": "Olennaiset markkinasignaalit, palaute tai toiminnalliset havainnot ovat saatavilla tämän kyvykkyysmahdollisuuden ohjaamiseksi.",
   "criterion.business-goals-defined": "Liiketoimintatavoitteet on määritelty.",
-  "criterion.market-research-done": "Markkinatutkimus tunnistaa API-mahdollisuudet.",
-  "criterion.stakeholder-approval": "Olennaiset sidosryhmät ovat tarkastelleet ja hyväksyneet API-mahdollisuuden.",
-  "criterion.api-opportunity-documented": "Yksittäiset API-mahdollisuudet on tunnistettu ja dokumentoitu.",
-  "criterion.api-reusability": "API vastaa selkeää liiketoimintatarvetta ja on uudelleenkäytettävissä useille API-käyttäjille.",
-  "criterion.hide-backend-discrepancies": "API on tarkoitettu suojamaan hyödyntäjiä backend-kompleksisuudesta ja epäjohdonmukaisuuksista.",
-  "criterion.value-prop-validated": "APIn arvolupaus on tarkistettu ja validointi on tehty yhdessä liiketoiminnan ja hyödyntäjien sidosryhmien kanssa.",
-  "criterion.consumer-segments-identified": "API-käyttäjäsegmentit (sisäiset ja ulkoiset) on tunnistettu.",
-  "criterion.api-roadmap-defined": "API-kehityksen yleiset etenemissuunnitelmat on laadittu.",
-  "criterion.architecture-patterns-validated": "API-arkkitehtuurimallit on tarkistettu ja validointi on tehty yhdessä teknisten sidosryhmien kanssa.",
-  "criterion.design-reflects-business-value": "APIn suunnittelun on heijastettava liiketoiminnan arvoa ja API-käyttäjien tarpeita.",
-  "criterion.api-consistency": "API-suunnittelu noudattaa yhteisiä API-tuote- ja suunnitteluohjeita.",
-  "criterion.api-contract-tested": "API-sopimus on testattu ja se täyttää toiminnalliset ja ei-toiminnalliset vaatimukset.",
-  "criterion.api-description-available": "APIn kuvaus on saatavilla ja se on riittävä API-hyödyntäjien tarpeisiin.",
-  "criterion.audit-passed": "API läpäisee vaatimustenmukaisuus-, turvallisuus- ja auditointitarkastukset.",
-  "criterion.audit-reports-shared": " API-auditointiraportit on jaettu olennaisille sidosryhmille.",
-  "criterion.api-ready-for-publishing": "API on valmis julkaistavaksi hyödyntäjien saataville.",
-  "criterion.api-documentation-ready": "API-dokumentaatio on valmis ja saatavilla API-hyödyntäjille.",
-  "criterion.consumer-support-ready": "Rekisteröinti, tuki ja viestintäprosessit ovat valmiita API-hyödyntäjille.",
-  "criterion.legal-compliance-clear": "Lakien, tietosuojan ja valvontavaatimukset julkaisuun ovat määritelty ja ymmärretty."
-}
\ No newline at end of file
+  "criterion.market-research-done": "Markkinatutkimus tunnistaa kyvykkyysmahdollisuuksia.",
+  "criterion.stakeholder-approval": "Olennaiset sidosryhmät ovat yhtä mieltä siitä, että kyvykkyysmahdollisuus kannattaa selvittää ja priorisoida.",
+  "criterion.api-opportunity-documented": "Kyvykkyysmahdollisuus on tunnistettu ja dokumentoitu.",
+  "criterion.api-reusability": "Kyvykkyys vastaa selkeään liiketoimintatarpeeseen ja on uudelleenkäytettävissä tarkoitetuille hyödyntäjille.",
+  "criterion.hide-backend-discrepancies": "Valittu rajapinta tarjoaa hyödyntäjille sopivan abstraktion.",
+  "criterion.value-prop-validated": "Kyvykkyyden arvolupaus on validoitu liiketoiminnan ja hyödyntäjien sidosryhmien kanssa.",
+  "criterion.consumer-segments-identified": "Hyödyntäjäsegmentit on tunnistettu.",
+  "criterion.api-roadmap-defined": "Ylätason toteutuksen etenemissuunnitelma on määritelty.",
+  "criterion.architecture-patterns-validated": "Valittu arkkitehtuuri, alusta ja toteutustapa on validoitu olennaisten arkkitehtuuri-, tietoturva- ja alustasidosryhmien kanssa.",
+  "criterion.design-reflects-business-value": "Rajapintasuunnittelu ja tarjottavat kyvykkyydet ovat jäljitettävissä liiketoiminta-arvoon ja hyödyntäjien tarpeisiin.",
+  "criterion.api-consistency": "Rajapintasuunnittelu noudattaa sovittuja suunnittelustandardeja ja käytäntöjä.",
+  "criterion.api-contract-tested": "Rajapintasopimus on validoitu ja testattu toiminnallisia ja ei-toiminnallisia vaatimuksia vasten.",
+  "criterion.api-description-available": "Rajapinta ja sen kyvykkyydet on dokumentoitu riittävän selkeästi katselmointia, auditointia ja käyttöönottoa varten.",
+  "criterion.audit-passed": "Ratkaisu läpäisee laatu-, tietoturva-, vaatimustenmukaisuus- ja valmiustarkastukset.",
+  "criterion.audit-reports-shared": "Auditointihavainnot ja korjauspäätökset on jaettu olennaisille sidosryhmille.",
+  "criterion.api-ready-for-publishing": "Kyvykkyys on valmis julkaistavaksi valitun toimitusmekanismin kautta.",
+  "criterion.api-documentation-ready": "Hyödyntäjille suunnattu dokumentaatio ja käyttöönottomateriaalit ovat valmiit.",
+  "criterion.consumer-support-ready": "Hyödyntäjien käyttöönotto-, tuki- ja viestintäprosessit ovat valmiit.",
+  "criterion.legal-compliance-clear": "Julkaisun oikeudelliset, tietosuoja- ja vaatimustenmukaisuusvaatimukset on määritelty ja ymmärretty."
+}
diff --git a/src/data/method/fi/labels.cycles.json b/src/data/method/fi/labels.cycles.json
index d6b6f75..845ff69 100644
--- a/src/data/method/fi/labels.cycles.json
+++ b/src/data/method/fi/labels.cycles.json
@@ -1,23 +1,23 @@
 {
-  "cycles.title": "Cycle Views",
-  "cycles.description": "Audience-specific views over the APIOps Cycles method graph.",
-  "cycle.capability-productization-cycle.title": "Kyvykkyyksien tuotteistamisen sykli",
-  "cycle.capability-productization-cycle.description": "Tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, tulisiko toteutuksen olla APIt, tapahtumat, tiedostot, virrat, datatuotteet, tekoälypohjaiset palvelut, suora integrointi vai hybridimalli.",
-  "cycle.capability-productization-cycle.purpose": "Tunnista ja tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, tulisiko toteutuksen olla APIt, tapahtumat, tiedostot, virrat, datatuotteet, tekoälypohjaiset palvelut, suora integrointi vai hybridimalli.",
-  "cycle.api-productization-cycle.title": "API tuotteistamisen sykli",
-  "cycle.api-productization-cycle.description": " Apeihin keskittynyt APIOps Cycles reitti APIen tuotteistukseen, suunnitteluun, toteutukseen, julkaisuun ja parantamiseen.",
-  "cycle.api-productization-cycle.purpose": "API-keskeinen menetelmämatka tiimeille, jotka jo tietävät että tarkoitettu toteutustapa on API-tuote.",
-  "cycle.integration-productization-cycle.title": "Integraation tuotteistamisen sykli",
-  "cycle.integration-productization-cycle.description": "Sykli uudelleenkäytettävien integraatiokykyjen tuotteistukseen ennen kuin valitaan konkreettinen integraatiomalli.",
-  "cycle.integration-productization-cycle.purpose": "Opastaa uudelleenkäytettävän integraatiokykyjen suunnittelua ennen APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden, suoran integroinnin tai hybridimallien valintaa.",
+  "cycles.title": "Syklinäkymät",
+  "cycles.description": "Kohderyhmäkohtaiset näkymät APIOps Cycles -menetelmään.",
+  "cycle.capability-productization-cycle.title": "Kyvykkyyden tuotteistamisen sykli",
+  "cycle.capability-productization-cycle.description": "Sykli liiketoiminnan kyvykkyyksien muuttamiseen uudelleenkäytettäviksi digitaalisiksi kyvykkyyksiksi ennen toteutustavan valintaa.",
+  "cycle.capability-productization-cycle.purpose": "Tunnista ja tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, onko toteutustapa API, tapahtumat, tiedostot, virrat, datatuotteet, tekoälyä hyödyntävät palvelut, suora integraatio vai hybridimalli.",
+  "cycle.api-productization-cycle.title": "API-tuotteistamisen sykli",
+  "cycle.api-productization-cycle.description": "API-keskeinen APIOps Cycles -polku APIen tuotteistamiseen, suunnitteluun, toimittamiseen, julkaisuun ja parantamiseen.",
+  "cycle.api-productization-cycle.purpose": "API-keskeinen menetelmäpolku tiimeille, jotka jo tietävät, että tarkoitettu toteutustapa on API-tuote.",
+  "cycle.integration-productization-cycle.title": "Integraatiokyvykkyyden tuotteistamisen sykli",
+  "cycle.integration-productization-cycle.description": "Sykli uudelleenkäytettävien integraatiokyvykkyyksien tuotteistamiseen ennen konkreettisen integraatiomallin valintaa.",
+  "cycle.integration-productization-cycle.purpose": "Ohjaa uudelleenkäytettävän integraatiokyvykkyyden suunnittelua ennen APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden, suoran integraation tai hybridimallien valintaa.",
   "cycle.station.capability-strategy": "Strategia",
-  "cycle.station.consumer-requirements-onboarding": "Hyödyntäjien vaatimukset ja käyttöönottoprosessi",
+  "cycle.station.consumer-requirements-onboarding": "Hyödyntäjien vaatimukset ja käyttöönotto",
   "cycle.station.architecture-platform-decisions": "Arkkitehtuuri ja alustaratkaisut",
   "cycle.station.solution-interface-design": "Ratkaisu- ja rajapintasuunnittelu",
-  "cycle.station.delivery-operations": "Toteutus ja ylläpito",
+  "cycle.station.delivery-operations": "Toimitus ja operointi",
   "cycle.station.quality-readiness-assurance": "Laadun ja valmiuden varmistus",
-  "cycle.station.publishing-enablement": "Julkaisu ja käyttöönoton tuki",
-  "cycle.station.monitoring-improvement": "Seuranta & parantaminen",
+  "cycle.station.publishing-enablement": "Julkaisu ja käyttöönoton mahdollistaminen",
+  "cycle.station.monitoring-improvement": "Seuranta ja parantaminen",
   "cycle.station.api-product-strategy": "API-tuotestrategia",
   "cycle.station.api-consumer-experience": "API-hyödyntäjäkokemus",
   "cycle.station.api-platform-architecture": "API-alustan arkkitehtuuri",
@@ -26,82 +26,82 @@
   "cycle.station.api-audit": "API-auditointi",
   "cycle.station.api-publishing": "API-julkaisu",
   "cycle.station.monitoring-and-improving": "Seuranta & parantaminen",
-  "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyksien strategia",
-  "cycle.station.integration-consumer-requirements-onboarding": "Integraatiohyödyntäjien vaatimukset ja käyttöönottoprosessi",
+  "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyden strategia",
+  "cycle.station.integration-consumer-requirements-onboarding": "Integraation hyödyntäjien vaatimukset ja käyttöönotto",
   "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuriratkaisu",
   "cycle.station.integration-solution-design": "Integraation ratkaisusuunnittelu",
-  "cycle.station.integration-delivery-operations": "Integraation toteutus ja toiminta",
-  "cycle.station.integration-readiness-assurance": "Integraatioiden laadunvarmistus",
+  "cycle.station.integration-delivery-operations": "Integraation toimitus ja operointi",
+  "cycle.station.integration-readiness-assurance": "Integraation valmiuden varmistus",
   "cycle.station.capability-publishing": "Kyvykkyyksien julkaisu",
-  "cycle.station.integration-monitoring-improvement": "Integraatioden seuranta & parantaminen",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability strategy before choosing the implementation style.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to choose architecture and platform capabilities.",
-  "cycle.capability-productization-cycle.station.api-design.description": "Design the selected solution mechanism and interface contract.",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Deliver and operate the selected solution mechanism.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Assure quality, governance, and readiness before release.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish capability information so consumers can discover, request, onboard, and get support.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities.",
-  "cycle.owner.business-owner": "Business owner",
-  "cycle.owner.domain-expert": "Domain expert",
-  "cycle.owner.capability-owner": "Capability owner",
-  "cycle.owner.consumer-representative": "Consumer representative",
-  "cycle.owner.enterprise-architect": "Enterprise architect",
-  "cycle.owner.platform-owner": "Platform owner",
-  "cycle.owner.api-product-owner": "API product owner",
-  "cycle.owner.api-platform-owner": "API platform owner",
-  "cycle.owner.integration-architect": "Integration architect",
-  "cycle.owner.solution-architect": "Solution architect",
-  "cycle.template.intent-fit.title": "Intent & Fit",
-  "cycle.template.intent-fit.description": "Capture the business outcome, consumers, producers, scope, constraints, and decision status.",
-  "cycle.template.requirements.title": "Requirements",
-  "cycle.template.requirements.description": "Gather expert input using the recommended questions. Treat answers as inputs to design decisions, not final design decisions.",
-  "cycle.template.architecture-decision.title": "Architecture Decision",
-  "cycle.template.architecture-decision.description": "Compare viable architecture choices against the gathered requirements, evidence, risks, and open questions.",
-  "cycle.template.api-architecture-decision.title": "API Architecture Decision",
-  "cycle.template.api-architecture-decision.description": "Document API architecture, platform, security, lifecycle, and publishing decisions.",
-  "cycle.template.integration-pattern-decision.title": "Integration Pattern Decision",
-  "cycle.template.integration-pattern-decision.description": "Compare APIs, events, files, streams, data products, direct integration, and hybrid options against requirements.",
-  "cycle.template.human-validation.title": "Human Validation",
-  "cycle.template.human-validation.description": "Document who validates AI-assisted outputs and which decisions require human accountability.",
-  "cycle.template.adr.title": "Architecture Decision Record",
-  "cycle.template.adr.description": "Record the selected decision, rationale, alternatives, consequences, evidence, and follow-up actions.",
-  "cycle.api-productization-cycle.station.api-product-strategy.description": "Frame the API as a product with clear value proposition, consumers, business model, ownership, and lifecycle intent.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Define API consumer segments, onboarding paths, expectations, and experience requirements before design decisions are locked.",
-  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choose and validate the API platform, architecture, governance, and operational constraints needed for the product.",
-  "cycle.api-productization-cycle.station.api-design.description": "Design the API contract, interaction model, schemas, policies, and usability details before implementation.",
-  "cycle.api-productization-cycle.station.api-delivery.description": "Implement, test, secure, automate, and operate the API product through the delivery pipeline.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validate API quality, compliance, readiness, evidence, and release criteria before publication.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Publish the API product so consumers can discover, evaluate, request access, onboard, and get support.",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitor API health, adoption, consumer outcomes, reliability, and improvement opportunities after release.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting a pattern.",
-  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decide the integration architecture, platform capabilities, constraints, and governance model for the capability.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Design the integration solution, contracts, payloads, events, APIs, files, or interaction patterns selected for the capability.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability across its selected delivery pattern.",
-  "cycle.integration-productization-cycle.station.api-audit.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover, request, reuse, onboard, and get support.",
-  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.",
-  "cycle.automation-cycle.title": "Automation Cycle",
-  "cycle.automation-cycle.description": "A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.",
-  "cycle.automation-cycle.purpose": "Productize automation opportunities into governed workflows with clear users, platforms, controls, delivery paths, enablement, and monitoring.",
-  "cycle.audience.automation-owners": "Automation owners",
-  "cycle.audience.process-owners": "Process owners",
-  "cycle.audience.automation-teams": "Automation teams",
-  "cycle.station.automation-opportunity-strategy": "Automation Opportunity Strategy",
-  "cycle.station.process-user-requirements": "Process/User Requirements",
-  "cycle.station.automation-platform-decision": "Automation Platform Decision",
-  "cycle.station.automation-workflow-design": "Automation Workflow Design",
-  "cycle.station.automation-delivery": "Automation Delivery",
-  "cycle.station.automation-readiness-review": "Automation Readiness Review",
-  "cycle.station.automation-enablement": "Automation Enablement",
-  "cycle.station.automation-monitoring-improvement": "Automation Monitoring & Improvement",
-  "cycle.automation-cycle.station.api-product-strategy.description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact.",
-  "cycle.automation-cycle.station.api-consumer-experience.description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration model, governance controls, and operational constraints.",
-  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, and exception paths.",
-  "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation with clear ownership and rollback paths.",
-  "cycle.automation-cycle.station.api-audit.description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.",
-  "cycle.automation-cycle.station.api-publishing.description": "Enable users and operators with discovery, onboarding, operating instructions, support paths, and change communication.",
-  "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities."
+  "cycle.station.integration-monitoring-improvement": "Integraation seuranta ja parantaminen",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Määrittele kyvykkyyden arvo, hyödyntäjät, omistajuus ja liiketoimintatavoitteet ennen kuin mitään rakennetaan.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Kokoa hyödyntäjien vaatimukset, käyttöönoton tarpeet, rajoitteet, palveluodotukset ja tuottajan vastuut.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Käytä vaatimuksia ja rajoitteita arkkitehtuurin ja alustakyvykkyyksien valintaan.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Suunnittele rajapintasopimus ja vuorovaikutusmalli valitulle toteutustavalle.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Rakenna, testaa, julkaise ja operoi kyvykkyyttä valitulla toteutustavalla ja validoidulla rajapintasopimuksella.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Varmista laatu, hallintamalli ja julkaisukelpoisuus ennen julkaisua.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Julkaise kyvykkyyden tiedot, jotta hyödyntäjät voivat löytää sen, pyytää käyttöoikeutta, ottaa sen käyttöön ja saada tukea.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Seuraa kyvykkyyden tilaa, hyödyntäjien tuloksia, luotettavuutta, uudelleenkäyttöä ja parannusmahdollisuuksia.",
+  "cycle.owner.business-owner": "Liiketoimintaomistaja",
+  "cycle.owner.domain-expert": "Toimialan asiantuntija",
+  "cycle.owner.capability-owner": "Kyvykkyyden omistaja",
+  "cycle.owner.consumer-representative": "Hyödyntäjien edustaja",
+  "cycle.owner.enterprise-architect": "Kokonaisarkkitehti",
+  "cycle.owner.platform-owner": "Alustan omistaja",
+  "cycle.owner.api-product-owner": "API-tuoteomistaja",
+  "cycle.owner.api-platform-owner": "API-alustan omistaja",
+  "cycle.owner.integration-architect": "Integraatioarkkitehti",
+  "cycle.owner.solution-architect": "Ratkaisuarkkitehti",
+  "cycle.template.intent-fit.title": "Tarkoitus ja soveltuvuus",
+  "cycle.template.intent-fit.description": "Kuvaa liiketoimintatulos, hyödyntäjät, tuottajat, rajaus, rajoitteet ja päätöksen tila.",
+  "cycle.template.requirements.title": "Vaatimukset",
+  "cycle.template.requirements.description": "Kokoa asiantuntijoiden syötteet suositeltujen kysymysten avulla. Käsittele vastauksia suunnittelupäätösten lähtötietoina, älä lopullisina suunnittelupäätöksinä.",
+  "cycle.template.architecture-decision.title": "Arkkitehtuuripäätös",
+  "cycle.template.architecture-decision.description": "Vertaa mahdollisia arkkitehtuurivalintoja koottuihin vaatimuksiin, näyttöön, riskeihin ja avoimiin kysymyksiin.",
+  "cycle.template.api-architecture-decision.title": "API-arkkitehtuuripäätös",
+  "cycle.template.api-architecture-decision.description": "Dokumentoi API-arkkitehtuuria, alustaa, tietoturvaa, elinkaarta ja julkaisua koskevat päätökset.",
+  "cycle.template.integration-pattern-decision.title": "Integraatiomallin päätös",
+  "cycle.template.integration-pattern-decision.description": "Vertaa API-, tapahtuma-, tiedosto-, virta-, datatuote-, suora integraatio- ja hybridivaihtoehtoja vaatimuksiin.",
+  "cycle.template.human-validation.title": "Ihmisen tekemä validointi",
+  "cycle.template.human-validation.description": "Dokumentoi, kuka validoi tekoälyavusteiset tuotokset ja mitkä päätökset edellyttävät ihmisen vastuuta.",
+  "cycle.template.adr.title": "Arkkitehtuuripäätöksen dokumentti",
+  "cycle.template.adr.description": "Kirjaa valittu päätös, perustelut, vaihtoehdot, seuraukset, näyttö ja jatkotoimet.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Miellä API tuotteena, jolla on selkeä arvolupaus, hyödyntäjät, liiketoimintamalli, omistajuus ja elinkaaren tavoite.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Määrittele API-hyödyntäjäsegmentit, käyttöönoton polut, odotukset ja kokemukseen liittyvät vaatimukset ennen suunnittelupäätösten lukitsemista.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Valitse ja validoi API-tuotteen tarvitsema API-alusta, arkkitehtuuri, hallintamalli ja operatiiviset rajoitteet.",
+  "cycle.api-productization-cycle.station.api-design.description": "Suunnittele API-rajapintasopimus, vuorovaikutusmalli, skeemat, käytännöt ja käytettävyyden yksityiskohdat ennen toteutusta.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Toteuta, testaa, suojaa, automatisoi ja operoi API-tuotetta toimitusputken kautta.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validoi API-laatu, vaatimustenmukaisuus, valmius, näyttö ja julkaisukriteerit ennen julkaisua.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Julkaise API-tuote, jotta hyödyntäjät voivat löytää sen, arvioida sen, pyytää käyttöoikeutta, ottaa sen käyttöön ja saada tukea.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Seuraa APIen tilaa, käyttöönottoa, hyödyntäjien tuloksia, luotettavuutta ja parannusmahdollisuuksia julkaisun jälkeen.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Rajaa uudelleenkäytettävä integraatiokyvykkyys, liiketoimintatarve, omistajuus ja odotettu uudelleenkäyttö ennen mallin valintaa.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Kokoa integraation hyödyntäjät, tuottajan vastuut, käyttöönoton tarpeet, palveluodotukset ja operatiiviset rajoitteet.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Päätä integraatioarkkitehtuuri, alustakyvykkyydet, rajoitteet ja kyvykkyyden hallintamalli.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Suunnittele integraatiokyvykkyydelle valittu rajapintasopimus, tietosisällöt, tapahtumat, APIt, tiedostot tai vuorovaikutusmallit.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Rakenna, testaa, automatisoi, julkaise ja operoi integraatiokyvykkyyttä sen valitulla toteutustavalla ja validoidulla rajapintasopimuksella.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Varmista integraation valmius, hallintamalli, laatu, tietoturva, vaatimustenmukaisuus ja operatiivinen näyttö ennen julkaisua.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat löytää sen, pyytää käyttöoikeutta, käyttää sitä uudelleen, ottaa sen käyttöön ja saada tukea.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Seuraa integraation luotettavuutta, uudelleenkäyttöä, häiriöitä, suorituskykyä, hyödyntäjien tuloksia ja parannustarpeita.",
+  "cycle.automation-cycle.title": "Automaatiosykli",
+  "cycle.automation-cycle.description": "Sykli automaatiomahdollisuuksien tunnistamiseen, suunnitteluun, toimittamiseen, käyttöönoton mahdollistamiseen ja parantamiseen.",
+  "cycle.automation-cycle.purpose": "Tuotteista automaatiomahdollisuuksia hallituiksi työnkuluiksi, joilla on selkeät käyttäjät, alustat, kontrollit, toimituspolut, käyttöönoton tuki ja seuranta.",
+  "cycle.audience.automation-owners": "Automaation omistajat",
+  "cycle.audience.process-owners": "Prosessinomistajat",
+  "cycle.audience.automation-teams": "Automaatiotiimit",
+  "cycle.station.automation-opportunity-strategy": "Automaatiomahdollisuuden strategia",
+  "cycle.station.process-user-requirements": "Prosessin ja käyttäjien vaatimukset",
+  "cycle.station.automation-platform-decision": "Automaatioalustan päätös",
+  "cycle.station.automation-workflow-design": "Automaatiotyönkulun suunnittelu",
+  "cycle.station.automation-delivery": "Automaation toimitus",
+  "cycle.station.automation-readiness-review": "Automaation valmiuskatselmointi",
+  "cycle.station.automation-enablement": "Automaation käyttöönoton mahdollistaminen",
+  "cycle.station.automation-monitoring-improvement": "Automaation seuranta ja parantaminen",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Tunnista ja priorisoi automaatiomahdollisuudet arvon, toteutettavuuden, riskin, omistajuuden ja odotetun prosessivaikutuksen perusteella.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Kokoa prosessin käyttäjät, roolit, luovutukset, poikkeukset, rajoitteet ja palveluodotukset ennen automaation suunnittelua.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Valitse automaatioalusta, ajoympäristö, integraatiomalli, hallintakontrollit ja operatiiviset rajoitteet.",
+  "cycle.automation-cycle.station.api-design.description": "Suunnittele automaation työnkulku, käynnistimet, päätöspisteet, integraatiot, datankäsittely, rajapintasopimukset ja poikkeuspolut.",
+  "cycle.automation-cycle.station.api-delivery.description": "Rakenna, testaa, julkaise, dokumentoi ja operoi automaatiota selkeällä omistajuudella, kontrolleilla ja palautuspoluilla.",
+  "cycle.automation-cycle.station.api-audit.description": "Katselmoi automaation valmius, laatu, riski, vaatimustenmukaisuus, ihmisen valvonta, näyttö ja julkaisukriteerit.",
+  "cycle.automation-cycle.station.api-publishing.description": "Mahdollista käyttäjien ja operaattorien työ löydettävyyden, käyttöönoton, käyttöohjeiden, tukipolkujen ja muutosviestinnän avulla.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Seuraa automaation suorituskykyä, poikkeuksia, luotettavuutta, käyttäjien tuloksia, operatiivista vaikutusta ja parannusmahdollisuuksia."
 }
diff --git a/src/data/method/fi/labels.lines.json b/src/data/method/fi/labels.lines.json
index 26913f5..487ff2e 100644
--- a/src/data/method/fi/labels.lines.json
+++ b/src/data/method/fi/labels.lines.json
@@ -1,16 +1,16 @@
 {
   "lines.title": "Metrolinjat",
-  "lines.description": "API-linjausten kokoelma, joka ohjaa APIen kehittämistä ja hallintaa.",
-  "line.business-opportunities-line.title": "Liiketoimintamahdollisuudet linja",
-  "line.business-opportunities-line.description": "Keskittyy tunnistamaan ja hyödyntämään liiketoimintamahdollisuuksia sovellusrajapintojen avulla.",
+  "lines.description": "APIOps Cycles -metrolinjat, jotka ohjaavat kyvykkyyksien, APIen ja integraatioiden suunnittelua, toteutusta ja kehittämistä.",
+  "line.business-opportunities-line.title": "Liiketoimintamahdollisuuksien linja",
+  "line.business-opportunities-line.description": "Keskittyy tunnistamaan, arvioimaan ja tuotteistamaan liiketoimintamahdollisuuksia uudelleenkäytettävinä kyvykkyyksinä.",
   "line.platform-architecture-line.title": "Alusta-arkkitehtuurilinja",
-  "line.platform-architecture-line.description": "Kattaa API-alustojen arkkitehtuurinäkökohtia.",
+  "line.platform-architecture-line.description": "Kattaa alustojen, integraatioiden ja rajapintojen arkkitehtuurin suunnittelun.",
   "line.api-design-line.title": "API-suunnittelulinja",
-  "line.api-design-line.description": "Keskittyy APIen suunnitteluperiaatteisiin ja -käytäntöihin.",
+  "line.api-design-line.description": "Keskittyy rajapintojen ja integraatioratkaisujen suunnitteluperiaatteisiin ja -käytäntöihin.",
   "line.delivery-line.title": "Toimituslinja",
-  "line.delivery-line.description": "Kattaa APIen toimitusprosessit ja -käytännöt.",
-  "line.publishing-and-adoption-line.title": "Julkaisu- ja hyväksymislinja",
-  "line.publishing-and-adoption-line.description": "Keskittyy API-rajapintojen julkaisemiseen ja sen varmistamiseen, että kuluttajat hyväksyvät ne.",
-  "line.operating-model-line.title": "Toimintamalli Line",
-  "line.operating-model-line.description": "Kattaa API-hallinnan ja -hallinnan toimintamallin."
-}
+  "line.delivery-line.description": "Kattaa toteutuksen, testauksen, automaation ja toimituskäytännöt.",
+  "line.publishing-and-adoption-line.title": "Julkaisu- ja käyttöönoton linja",
+  "line.publishing-and-adoption-line.description": "Keskittyy kyvykkyyksien julkaisemiseen, käyttöönottoon ja hyödyntämisen tukemiseen.",
+  "line.operating-model-line.title": "Toimintamallilinja",
+  "line.operating-model-line.description": "Kattaa kyvykkyyksien hallintamallin, vastuut ja governance-käytännöt."
+}
\ No newline at end of file
diff --git a/src/data/method/fi/labels.resources.json b/src/data/method/fi/labels.resources.json
index 20edc66..61e6985 100644
--- a/src/data/method/fi/labels.resources.json
+++ b/src/data/method/fi/labels.resources.json
@@ -3,202 +3,202 @@
   "resource.api-community-engagement-strategies.description": "Toimintakirja API-käyttöliittymien käyttöönoton edistämiseksi kehittämällä yhteisöjä sisällön, tukikanavien, palautesilmukoiden ja sosiaalisen sitoutumisen strategioiden avulla.",
   "resource.api-community-engagement-strategies.outcomes": "API-yhteisön sitouttamisstrategioiden periaatteiden parempi ymmärtäminen",
   "resource.api-community-engagement-strategies.steps": "Kehitä markkinointistrategioita APIen markkinoimiseksi kohdeyleisöille, mukaan lukien sosiaalinen media, blogit ja webinaarit.",
-  "resource.api-community-engagement-strategies.tips": "Mukauta API-yhteisön sitouttamisstrategiat toimialueellesi sopiviksi",
+  "resource.api-community-engagement-strategies.tips": "Mukauta API-yhteisön sitouttamisstrategiat omaan kontekstiisi sopiviksi",
   "resource.api-compliance-best-practices.title": "API-vaatimustenmukaisuuden parhaat käytännöt",
-  "resource.api-compliance-best-practices.description": "Varmista, että sovellusrajapinnat täyttävät oikeudelliset, sääntelyyn liittyvät ja sisäiset vaatimukset dokumentoinnin, valvonnan ja automaattisten validointien avulla.",
+  "resource.api-compliance-best-practices.description": "Varmista, että rajapinnat täyttävät oikeudelliset, sääntelyyn liittyvät ja sisäiset vaatimukset dokumentoinnin, valvonnan ja automaattisten validointien avulla.",
   "resource.api-compliance-best-practices.outcomes": "Parempi ymmärrys API-vaatimustenmukaisuuden parhaiden käytäntöjen periaatteista",
-  "resource.api-compliance-best-practices.steps": "dokumentoida vaatimustenmukaisuustoimenpiteet ja varmistaa, että niistä tiedotetaan sidosryhmille ja kuluttajille.",
-  "resource.api-compliance-best-practices.tips": "Mukauta API Compliance Best Practices -käytännöt omaan toimialueeseesi.",
+  "resource.api-compliance-best-practices.steps": "Dokumentoi vaatimustenmukaisuustoimenpiteet ja varmista, että niistä tiedotetaan sidosryhmille ja hyödyntäjille.",
+  "resource.api-compliance-best-practices.tips": "Mukauta API Compliance Best Practices -käytännöt omaan kontekstiisi.",
   "resource.api-development-best-practices.title": "API-kehityksen parhaat käytännöt",
-  "resource.api-development-best-practices.description": "Ohjeet, joiden avulla validoitu API-sopimus voidaan muuttaa johdonmukaiseksi ja ylläpidettäväksi API-koodiksi käyttämällä vakiokirjastoja, uudelleenkäytettäviä malleja ja yhdenmukaistettuja kehitystyönkulkuja.",
+  "resource.api-development-best-practices.description": "Ohjeet, joiden avulla validoitu API-rajapintasopimus voidaan muuttaa johdonmukaiseksi ja ylläpidettäväksi API-koodiksi käyttämällä vakiokirjastoja, uudelleenkäytettäviä malleja ja yhdenmukaistettuja kehitystyönkulkuja.",
   "resource.api-development-best-practices.outcomes": "API-kehityksen parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
   "resource.api-development-best-practices.steps": "Sovella näitä käytäntöjä validoituun API-sopimukseen ja toteutussuunnitelmaan ennen koodaamisen aloittamista.",
-  "resource.api-development-best-practices.tips": "Mukauta API-kehityksen parhaat käytännöt omaan toimialueeseesi sopiviksi",
+  "resource.api-development-best-practices.tips": "Mukauta API-kehityksen parhaat käytännöt omaan kontekstiisi sopiviksi",
   "resource.api-metrics-and-analytics.title": "API-mittarit ja analytiikka",
   "resource.api-metrics-and-analytics.description": "Resurssi API-suorituskyvyn ja käyttötietojen määrittelyyn, keräämiseen ja analysointiin, jotta tekniset KPI:t voidaan sovittaa yhteen liiketoiminnan tulosten kanssa.",
   "resource.api-metrics-and-analytics.outcomes": "Parempi ymmärrys API-mittareista ja analytiikan periaatteista.",
   "resource.api-metrics-and-analytics.steps": "Määritä keskeiset suorituskykyindikaattorit (KPI), joilla mitataan APIn onnistumista suhteessa liiketoiminnan tavoitteisiin.",
-  "resource.api-metrics-and-analytics.tips": "Mukauta API-mittareita ja analytiikkaa toimialueellesi.",
+  "resource.api-metrics-and-analytics.tips": "Mukauta API-mittareita ja analytiikkaa omaan kontekstiisi.",
   "resource.api-onboarding-best-practices.title": "API-käyttöönoton parhaat käytännöt",
   "resource.api-onboarding-best-practices.description": "Parhaat käytännöt API-asiakkaiden käyttöönoton sujuvoittamiseksi vaiheittaisella rekisteröinnillä, tutustumisella ja ensisoitto-opastuksella.",
   "resource.api-onboarding-best-practices.outcomes": "Parempi ymmärrys API-käyttöönoton parhaiden käytäntöjen periaatteista.",
-  "resource.api-onboarding-best-practices.steps": "Määrittele API-kuluttajan matka löytämisestä vianmääritykseen ja tunnista keskeiset kosketuspisteet ja kipupisteet.",
-  "resource.api-onboarding-best-practices.tips": "Mukauta API Onboarding Best Practices -käytännöt omalle toimialueellesi.",
+  "resource.api-onboarding-best-practices.steps": "Määrittele API-hyödyntäjän matka löytämisestä vianmääritykseen ja tunnista keskeiset kosketuspisteet ja kipupisteet.",
+  "resource.api-onboarding-best-practices.tips": "Mukauta API Onboarding Best Practices -käytännöt omaan kontekstiisi.",
   "resource.api-portfolio-management-guidelines.title": "API-portfolion hallinnan suuntaviivat",
   "resource.api-portfolio-management-guidelines.description": "Opas organisaation API-sarjan strategiseen hallintaan - APIen priorisointiin, resurssien jakamiseen ja suorituskyvyn seurantaan koko elinkaaren ajan.",
   "resource.api-portfolio-management-guidelines.outcomes": "API-salkunhallinnan suuntaviivojen periaatteiden parempi ymmärtäminen",
   "resource.api-portfolio-management-guidelines.steps": "Määrittele salkunhallintakäytännöt, joissa hahmotellaan API-salkun hallinnointiprosessit, mukaan lukien priorisointi, seuranta ja optimointi.",
-  "resource.api-portfolio-management-guidelines.tips": "Mukauta API-salkunhallintaohjeet toimialueellesi sopiviksi",
+  "resource.api-portfolio-management-guidelines.tips": "Mukauta API-salkunhallintaohjeet omaan kontekstiisi sopiviksi",
   "resource.api-security-best-practices.title": "API-turvallisuuden parhaat käytännöt",
-  "resource.api-security-best-practices.description": "Joukko toimivia valvontatoimia sovellusrajapintojen suojaamiseksi, mukaan lukien todennus, valtuutus, salaus, nopeuden rajoittaminen ja putkitason vaatimustenmukaisuustarkastukset.",
+  "resource.api-security-best-practices.description": "Joukko toimivia valvontatoimia rajapintojen suojaamiseksi, mukaan lukien todennus, valtuutus, salaus, nopeuden rajoittaminen ja putkitason vaatimustenmukaisuustarkastukset.",
   "resource.api-security-best-practices.outcomes": "API-turvan parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
-  "resource.api-security-best-practices.steps": "Varmista, että sovellusrajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
-  "resource.api-security-best-practices.tips": "Mukauta API Security Best Practices -käytännöt toimialueellesi.",
+  "resource.api-security-best-practices.steps": "Varmista, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
+  "resource.api-security-best-practices.tips": "Mukauta API Security Best Practices -käytännöt omaan kontekstiisi.",
   "resource.api-team-structure-guidelines.title": "API-tiimin rakennetta koskevat ohjeet",
   "resource.api-team-structure-guidelines.description": "Organisatoriset ohjeet roolien ja vastuualueiden määrittelemiseksi API-tiimeissä selkeyden, yhteistyön ja vastuuvelvollisuuden varmistamiseksi.",
   "resource.api-team-structure-guidelines.outcomes": "API-tiimin rakenteen suuntaviivojen periaatteiden parempi ymmärtäminen",
   "resource.api-team-structure-guidelines.steps": "Määrittele API-tiimien tiimirakenteet ja roolit, mukaan lukien API-tuotteen omistajat, kehittäjät, arkkitehdit ja toiminnot.",
-  "resource.api-team-structure-guidelines.tips": "Mukauta API-tiimirakenneohjeet omaan toimialueeseesi sopiviksi",
+  "resource.api-team-structure-guidelines.tips": "Mukauta API-tiimirakenneohjeet omaan kontekstiisi sopiviksi",
   "resource.api-testing-best-practices.title": "API-testauksen parhaat käytännöt",
-  "resource.api-testing-best-practices.description": "Ohjeet automatisoidun toiminnallisen, suorituskyky- ja tietoturvatestauksen toteuttamiseksi koko sovellusrajapinnan elinkaaren ajan.",
+  "resource.api-testing-best-practices.description": "Ohjeet automatisoidun toiminnallisen, suorituskyky- ja tietoturvatestauksen toteuttamiseksi koko rajapinnan elinkaaren ajan.",
   "resource.api-testing-best-practices.outcomes": "Parempi ymmärrys API-testauksen parhaiden käytäntöjen periaatteista",
-  "resource.api-testing-best-practices.steps": "Testaa sovellusrajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
-  "resource.api-testing-best-practices.tips": "Mukauta API-testauksen parhaat käytännöt omaan toimialueeseesi sopiviksi",
+  "resource.api-testing-best-practices.steps": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
+  "resource.api-testing-best-practices.tips": "Mukauta API-testauksen parhaat käytännöt omaan kontekstiisi sopiviksi",
   "resource.api-training-programs.title": "API-koulutusohjelmat",
-  "resource.api-training-programs.description": "Etenemissuunnitelma tiimien pätevöittämistä varten, jossa on jäsenneltyjä oppimispolkuja API-suunnittelun, hallinnan, suorituskyvyn ja tietoturvan alalla.",
+  "resource.api-training-programs.description": "Etenemissuunnitelma tiimien pätevöittämistä varten, jossa on jäsenneltyjä oppimispolkuja API-designin, hallinnan, suorituskyvyn ja tietoturvan alalla.",
   "resource.api-training-programs.outcomes": "API-koulutusohjelmien periaatteiden parempi ymmärtäminen",
-  "resource.api-training-programs.steps": "Tunnistetaan keskeiset API-taidot ja -tiedot, joita on kehitettävä, kuten API-suunnittelu, tietoturva ja suorituskyky.",
-  "resource.api-training-programs.tips": "Mukauta API-koulutusohjelmat toimialueellesi sopiviksi",
+  "resource.api-training-programs.steps": "Tunnistetaan keskeiset API-taidot ja -tiedot, joita on kehitettävä, kuten API-design, tietoturva ja suorituskyky.",
+  "resource.api-training-programs.tips": "Mukauta API-koulutusohjelmat omaan kontekstiisi sopiviksi",
   "resource.api-versioning-best-practices.title": "API-versionoinnin parhaat käytännöt",
-  "resource.api-versioning-best-practices.description": "Strategiat API-versioiden käyttöönottoa, ylläpitoa ja käytöstä poistamista varten siten, että taaksepäin yhteensopivuus ja kuluttajien luottamus säilyvät.",
+  "resource.api-versioning-best-practices.description": "Strategiat API-versioiden käyttöönottoa, ylläpitoa ja käytöstä poistamista varten siten, että taaksepäin yhteensopivuus ja hyödyntäjien luottamus säilyvät.",
   "resource.api-versioning-best-practices.outcomes": "Parempi ymmärrys API-versionoinnin parhaiden käytäntöjen periaatteista",
-  "resource.api-versioning-best-practices.steps": "Määrittele sovellusrajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
-  "resource.api-versioning-best-practices.tips": "Mukauta API Versioning Best Practices -käytännöt toimialuettasi varten",
-  "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD sovellusrajapinnoille",
+  "resource.api-versioning-best-practices.steps": "Määrittele rajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
+  "resource.api-versioning-best-practices.tips": "Mukauta API Versioning Best Practices -käytännöt omaan kontekstiisi",
+  "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD rajapinnoille",
   "resource.apiops-CI-CD-for-apis.description": "Käyttöönotto-ohjeet, jotka integroivat APIn elinkaaren tehtävät - suunnittelun, testauksen ja hallinnan - jatkuvaan integrointiin ja toimitusputkiin.",
   "resource.apiops-CI-CD-for-apis.outcomes": "Parempi ymmärrys CI/CD for APIs -periaatteista",
   "resource.apiops-CI-CD-for-apis.steps": "Käytä CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
-  "resource.apiops-CI-CD-for-apis.tips": "Mukauta CI/CD for APIs -ohjelmistoa toimialueellesi sopivaksi",
-  "resource.competitor-analysis-template.title": "Kilpailija-analyysi malli",
+  "resource.apiops-CI-CD-for-apis.tips": "Mukauta CI/CD for APIs -ohjelmistoa omaan kontekstiisi sopivaksi",
+  "resource.competitor-analysis-template.title": "Kilpailija-analyysimalli",
   "resource.competitor-analysis-template.description": "Strukturoitu työlista, jonka avulla voit vertailla API-tarjouksiasi kilpailijoihin kartoittamalla vahvuudet, heikkoudet ja erottavia tekijöitä.",
   "resource.competitor-analysis-template.outcomes": "Kilpailija-analyysin malliperiaatteiden parempi ymmärtäminen",
   "resource.competitor-analysis-template.steps": "Suorita kilpailija-analyysi tärkeimpien kilpailijoiden ja niiden API-tarjonnan tunnistamiseksi.",
-  "resource.competitor-analysis-template.tips": "Mukauta kilpailija-analyysimalli omalle verkkotunnuksellesi.",
-  "resource.contract-first-design.title": "Sopimus First Design",
+  "resource.competitor-analysis-template.tips": "Mukauta kilpailija-analyysimalli omalle kontekstiisi.",
+  "resource.contract-first-design.title": "Sopimuslähtöinen suunnittelu",
   "resource.contract-first-design.description": "Suuntaviiva, jossa kannatetaan API-lähestymistapaa, jossa käytetään virallisia sopimuksia (esim. OpenAPI) sidosryhmien yhdenmukaistamiseksi ennen kehitystä.",
   "resource.contract-first-design.outcomes": "Parempi ymmärrys sopimuksen suunnitteluperiaatteista",
   "resource.contract-first-design.steps": "Sovellat sopimuslähtöisiä tai suunnittelulähtöisiä lähestymistapoja varmistaaksesi, että API-sopimukset validoidaan ennen toteutusta.",
-  "resource.contract-first-design.tips": "Mukauta Sopimus ensin -suunnittelua verkkotunnuksellesi",
+  "resource.contract-first-design.tips": "Mukauta Sopimus ensin -suunnittelua kontekstiisi",
   "resource.cross-functional-collaboration-best-practices.title": "Toimialarajat ylittävän yhteistyön parhaat käytännöt",
   "resource.cross-functional-collaboration-best-practices.description": "Käytännöt, joilla helpotetaan viestintää ja yhdenmukaistamista liiketoiminta- ja tekniikkatiimien välillä API-rajapintoja suunniteltaessa tai toimitettaessa.",
   "resource.cross-functional-collaboration-best-practices.outcomes": "Toimialojen välisen yhteistyön parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
   "resource.cross-functional-collaboration-best-practices.steps": "Kannustaa API-tiimien, liiketoimintayksiköiden ja sidosryhmien välistä monialaista yhteistyötä, jotta API-aloitteet voidaan sovittaa yhteen liiketoiminnan tavoitteiden kanssa.",
-  "resource.cross-functional-collaboration-best-practices.tips": "Räätälöi monialaisen yhteistyön parhaat käytännöt omalle toimialueellesi.",
+  "resource.cross-functional-collaboration-best-practices.tips": "Räätälöi monialaisen yhteistyön parhaat käytännöt omaan kontekstiisi.",
   "resource.data-privacy-guidelines.title": "Tietosuojaa koskevat ohjeet",
-  "resource.data-privacy-guidelines.description": "Suunnitteluun liittyvät näkökohdat, joilla varmistetaan, että sovellusrajapinnat täyttävät tietosuojasäännökset, kuten GDPR:n, anonymisoinnin ja pääsynvalvonnan avulla.",
+  "resource.data-privacy-guidelines.description": "Suunnitteluun liittyvät näkökohdat, joilla varmistetaan, että rajapinnat täyttävät tietosuojasäännökset, kuten GDPR:n, anonymisoinnin ja pääsynvalvonnan avulla.",
   "resource.data-privacy-guidelines.outcomes": "Tietosuojaa koskevien suuntaviivojen periaatteiden parempi ymmärtäminen",
   "resource.data-privacy-guidelines.steps": "Varmista käyttäjien tietojen yksityisyys toteuttamalla tietosuojatoimenpiteitä, kuten anonymisointi ja käyttöoikeuksien valvonta.",
-  "resource.data-privacy-guidelines.tips": "Mukauta tietosuojaohjeet verkkotunnuksellesi",
-  "resource.domain-canvas.title": "Domain Canvas",
-  "resource.domain-canvas.description": "Mallinnustyökalu, jolla määritellään ja välitetään toimialueesi keskeiset entiteetit ja suhteet ja varmistetaan semanttinen yhdenmukaisuus eri sovellusrajapinnoissa.",
-  "resource.domain-canvas.outcomes": "Parempi ymmärrys toimialueen kangasperiaatteista",
-  "resource.domain-canvas.steps": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri sovellusliittymille.",
-  "resource.domain-canvas.tips": "Mukauta Domain Canvas verkkotunnusta varten",
-  "resource.ecosystem-vision-template.title": "Ekosysteemivision malli",
+  "resource.data-privacy-guidelines.tips": "Mukauta tietosuojaohjeet kontekstiisi",
+  "resource.domain-canvas.title": "Toimialuekanvas",
+  "resource.domain-canvas.description": "Mallinnustyökalu toimialueen keskeisten käsitteiden, entiteettien, suhteiden ja sääntöjen määrittelyyn, jotta kyvykkyydet, rajapinnat ja integraatiot pysyvät semanttisesti yhdenmukaisina.",
+  "resource.domain-canvas.outcomes": "Parempi ymmärrys toimialueen mallinnuksesta",
+  "resource.domain-canvas.steps": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri rajapinnoille ja kyvykkyyksille.",
+  "resource.domain-canvas.tips": "Mukauta Toimialuekanvas omaan kontekstiisi",
+  "resource.ecosystem-vision-template.title": "Ekosysteemivisiomalli",
   "resource.ecosystem-vision-template.description": "Strateginen suunnittelutyökalu API-ekosysteemin määrittelemiseksi, mukaan lukien kohdekumppanit, arvoketjut ja integrointimahdollisuudet.",
   "resource.ecosystem-vision-template.outcomes": "Parempi ymmärrys ekosysteemivision malliperiaatteista",
   "resource.ecosystem-vision-template.steps": "Markkinatutkimuksen tekeminen API-toimialalla vallitsevien suuntausten, mahdollisuuksien ja uhkien tunnistamiseksi.",
-  "resource.ecosystem-vision-template.tips": "Mukauta Ecosystem Vision Template -mallia toimialueellesi.",
+  "resource.ecosystem-vision-template.tips": "Mukauta Ecosystem Vision Template -mallia omaan kontekstiisi.",
   "resource.industry-standards-and-best-practices.title": "Alan standardit ja parhaat käytännöt",
-  "resource.industry-standards-and-best-practices.description": "Viiteresurssi API-suunnittelun ja -toiminnan mukauttamiseksi laajalti tunnustettuihin alan kehyksiin ja eritelmiin.",
+  "resource.industry-standards-and-best-practices.description": "Viiteresurssi API-designin ja -toiminnan mukauttamiseksi laajalti tunnustettuihin alan kehyksiin ja eritelmiin.",
   "resource.industry-standards-and-best-practices.outcomes": "alan standardien ja parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
-  "resource.industry-standards-and-best-practices.steps": "Tunnistetaan alan standardit ja parhaat käytännöt, jotta voidaan varmistaa, että sovellusrajapinnat ovat kilpailukykyisiä ja yhteensopivia.",
-  "resource.industry-standards-and-best-practices.tips": "Mukauta toimialan standardit ja parhaat käytännöt omaan toimialueeseesi.",
+  "resource.industry-standards-and-best-practices.steps": "Tunnistetaan alan standardit ja parhaat käytännöt, jotta voidaan varmistaa, että rajapinnat ovat kilpailukykyisiä ja yhteensopivia.",
+  "resource.industry-standards-and-best-practices.tips": "Mukauta toimialan standardit ja parhaat käytännöt omaan kontekstiisi.",
   "resource.partner-integration-guidelines.title": "Kumppanien integrointiohjeet",
   "resource.partner-integration-guidelines.description": "Integroinnin tarkistuslistat ja viestintämallit kolmannen osapuolen API-suhteiden teknisten ja oikeudellisten näkökohtien hallintaan.",
   "resource.partner-integration-guidelines.outcomes": "Parempi ymmärrys kumppanien integroinnin suuntaviivojen periaatteista",
   "resource.partner-integration-guidelines.steps": "Luodaan integraatioprosessit ja -ohjeet yhteistyökumppaneiden kanssa tehtävää yhteistyötä varten, mukaan lukien tekninen integraatio, tietojen jakaminen ja tuki.",
-  "resource.partner-integration-guidelines.tips": "Mukauta kumppanien integrointiohjeet toimialueellesi",
+  "resource.partner-integration-guidelines.tips": "Mukauta kumppanien integrointiohjeet omaan kontekstiisi",
   "resource.role-communication-best-practices.title": "Rooliviestinnän parhaat käytännöt",
-  "resource.role-communication-best-practices.description": "Työkalut, joilla määritetään ja dokumentoidaan, kuka on vastuussa mistäkin API-aloitteesta, ja varmistetaan, että vastuunjako ja vastuuvelvollisuus ovat selkeät.",
+  "resource.role-communication-best-practices.description": "Työkalut, joilla määritetään ja kuvataan API-aloitteiden vastuut sekä varmistetaan selkeä työnjako ja vastuuvelvollisuus.",
   "resource.role-communication-best-practices.outcomes": "rooliviestinnän parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
-  "resource.role-communication-best-practices.steps": "Määritä selkeät vastuualueet kullekin roolille, mukaan lukien API-suunnittelu, kehittäminen, testaus ja toiminta.",
-  "resource.role-communication-best-practices.tips": "Mukauta rooliviestinnän parhaat käytännöt toimialueellesi.",
+  "resource.role-communication-best-practices.steps": "Määritä selkeät vastuualueet kullekin roolille, mukaan lukien API-design, kehittäminen, testaus ja toiminta.",
+  "resource.role-communication-best-practices.tips": "Mukauta rooliviestinnän parhaat käytännöt omaan kontekstiisi.",
   "resource.scalable-infrastructure-best-practices.title": "Skaalautuvan infrastruktuurin parhaat käytännöt",
-  "resource.scalable-infrastructure-best-practices.description": "Arkkitehtuuriohjeet sen varmistamiseksi, että sovellusrajapinnat otetaan käyttöön infrastruktuurissa, joka pystyy käsittelemään joustavasti käyttöpiikkejä ja -kasvua.",
+  "resource.scalable-infrastructure-best-practices.description": "Arkkitehtuuriohjeet sen varmistamiseksi, että rajapinnat otetaan käyttöön infrastruktuurissa, joka pystyy käsittelemään joustavasti käyttöpiikkejä ja -kasvua.",
   "resource.scalable-infrastructure-best-practices.outcomes": "Parempi ymmärrys skaalautuvan infrastruktuurin parhaiden käytäntöjen periaatteista.",
   "resource.scalable-infrastructure-best-practices.steps": "Suunnittele API-infrastruktuuri skaalautuvaksi ja joustavaksi käyttäen pilvipohjaisia malleja ja teknologioita.",
-  "resource.scalable-infrastructure-best-practices.tips": "Mukauta skaalautuvan infrastruktuurin parhaat käytännöt toimialueellesi.",
+  "resource.scalable-infrastructure-best-practices.tips": "Mukauta skaalautuvan infrastruktuurin parhaat käytännöt omaan kontekstiisi.",
   "resource.service-agreement-template.title": "Palvelusopimusmalli",
   "resource.service-agreement-template.description": "Mukautettava sopimusmuoto, jossa määritellään odotukset, SLA:t, vastuut ja käyttöoikeusehdot API-käyttöä varten.",
   "resource.service-agreement-template.outcomes": "Palvelusopimusmallin periaatteiden parempi ymmärtäminen",
-  "resource.service-agreement-template.steps": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin sovellusrajapintaa varten.",
-  "resource.service-agreement-template.tips": "Mukauta palvelusopimusmalli omalle verkkotunnuksellesi.",
+  "resource.service-agreement-template.steps": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin rajapintaa varten.",
+  "resource.service-agreement-template.tips": "Mukauta palvelusopimusmalli omalle kontekstiisi.",
   "resource.stakeholder-engagement-best-practices.title": "Sidosryhmien sitouttamisen parhaat käytännöt",
   "resource.stakeholder-engagement-best-practices.description": "sitouttamistaktiikat sisäisten ja ulkoisten sidosryhmien saattamiseksi yhteisten API-tavoitteiden, -arvon ja -hallinnan piiriin.",
   "resource.stakeholder-engagement-best-practices.outcomes": "Sidosryhmien sitouttamisen parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
   "resource.stakeholder-engagement-best-practices.steps": "Sidosryhmien sitouttaminen varmistamaan API-aloitteiden yhdenmukaisuus ja tuki.",
-  "resource.stakeholder-engagement-best-practices.tips": "Mukauta sidosryhmien sitouttamisen parhaat käytännöt omalle toimialueellesi.",
+  "resource.stakeholder-engagement-best-practices.tips": "Mukauta sidosryhmien sitouttamisen parhaat käytännöt omaan kontekstiisi.",
   "resource.test-automation-frameworks.title": "Testausautomaation kehykset",
-  "resource.test-automation-frameworks.description": "Suositellut työkalut ja mallit API-sopimus-, regressio- ja integrointitestauksen automatisointiin eri ympäristöissä.",
+  "resource.test-automation-frameworks.description": "Suositellut työkalut ja mallit API-rajapintasopimus-, regressio- ja integrointitestauksen automatisointiin eri ympäristöissä.",
   "resource.test-automation-frameworks.outcomes": "Parempi ymmärrys testiautomaatiokehysten periaatteista.",
   "resource.test-automation-frameworks.steps": "Toteuta testiautomaatiokehykset, jotka tukevat sopimustestausta, integrointitestausta ja päästä päähän -testausta.",
-  "resource.test-automation-frameworks.tips": "Testausautomaatiokehysten mukauttaminen omaan toimialueeseesi sopiviksi",
+  "resource.test-automation-frameworks.tips": "Mukauta testausautomaatiokehykset omaan kontekstiisi sopiviksi.",
   "resource.vendor-management-best-practices.title": "Toimittajien hallinnan parhaat käytännöt",
   "resource.vendor-management-best-practices.description": "Kehys ulkoisten API-toimittajien ja kolmansien osapuolten integraatioiden arviointia ja hallintaa varten riskien, suorituskyvyn ja vaatimustenmukaisuuden perusteella.",
-  "resource.vendor-management-best-practices.outcomes": "Parempi ymmärrys myyjien hallinnan parhaiden käytäntöjen periaatteista",
-  "resource.vendor-management-best-practices.steps": "Ota käyttöön toimittajahallintaprosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
-  "resource.vendor-management-best-practices.tips": "Mukauta myyjien hallinnan parhaat käytännöt omalle toimialueellesi.",
+  "resource.vendor-management-best-practices.outcomes": "Parempi ymmärrys toimittajahallinnan parhaiden käytäntöjen periaatteista",
+  "resource.vendor-management-best-practices.steps": "Ota käyttöön toimittajagovernance-prosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
+  "resource.vendor-management-best-practices.tips": "Mukauta toimittajahallinnan parhaat käytännöt omaan kontekstiisi.",
   "resource.api-audit-checklist.title": "API-auditoinnin tarkistuslista",
   "resource.api-audit-checklist.description": "Elinkaaripohjainen tarkistuslista, jolla varmistetaan APIn valmius suunnittelun, toimituksen, julkaisun ja vaatimustenmukaisuuden osalta määriteltyjen auditointikriteerien ja todisteiden avulla.",
   "resource.api-audit-checklist.outcomes": "Parempi ymmärrys API-auditoinnin tarkistuslistan periaatteista",
-  "resource.api-audit-checklist.steps": "Varmista API-auditoinnin tarkistuslistan avulla, että API-suunnittelu täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "resource.api-audit-checklist.steps": "Varmista API-auditoinnin tarkistuslistan avulla, että API-design täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
   "resource.api-audit-checklist.tips": "Jokainen auditointikohta yhdistää elinkaaren työvaiheet (asemat), ohjaavat ohjeet ja tukevat todisteet, jotta APIn valmiudesta saadaan selkeä kuva.",
-  "resource.api-business-model-canvas.title": "API Business Model Canvas",
-  "resource.api-business-model-canvas.description": "Arvioi strategisesti API-liiketoiminnan elinkelpoisuutta kartoittamalla arvolupaukset, kuluttajasegmentit ja tärkeimmät resurssit.",
-  "resource.api-business-model-canvas.outcomes": "Selkeä liiketoimintastrategia sovellusrajapintoja varten",
+  "resource.api-business-model-canvas.title": "API-liiketoimintamallikanvas",
+  "resource.api-business-model-canvas.description": "Arvioi API-liiketoiminnan elinkelpoisuutta kartoittamalla arvolupaus, API-hyödyntäjäsegmentit ja keskeiset resurssit.",
+  "resource.api-business-model-canvas.outcomes": "Selkeä liiketoimintastrategia rajapintoja varten",
   "resource.api-business-model-canvas.steps": "Tiivistä APIn arvolupauksen tiivistelmä",
-  "resource.api-business-model-canvas.tips": "Aloita yhdestä sovellusrajapinnasta selkeyden varmistamiseksi",
+  "resource.api-business-model-canvas.tips": "Aloita yhdestä rajapinnasta selkeyden varmistamiseksi",
   "resource.api-design-principles.title": "APIn suunnitteluperiaatteet",
-  "resource.api-design-principles.description": "Tiivis opas APIn käytettävyyteen, löydettävyyteen ja johdonmukaisuuteen, joka perustuu yhteisiin suunnittelusääntöihin ja todellisiin kuluttajien tarpeisiin.",
-  "resource.api-design-principles.outcomes": "API-suunnittelun periaatteiden parempi ymmärtäminen",
-  "resource.api-design-principles.steps": "**Kuluttaja ensin -suunnittelu:** Aloita jokainen APIOps-sykli keräämällä käyttäjien tavoitteet ja toimialan ehdot, jotta APIt ratkaisevat todellisia ongelmia.",
-  "resource.api-design-principles.tips": "Mukauta API-suunnitteluperiaatteet omaan toimialueeseesi sopiviksi",
-  "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas",
+  "resource.api-design-principles.description": "Tiivis opas APIn käytettävyyteen, löydettävyyteen ja johdonmukaisuuteen, joka perustuu yhteisiin suunnittelusääntöihin ja todellisiin hyödyntäjien tarpeisiin.",
+  "resource.api-design-principles.outcomes": "API-designin periaatteiden parempi ymmärtäminen",
+  "resource.api-design-principles.steps": "**Hyödyntäjä ensin -suunnittelu:** Aloita jokainen APIOps-sykli keräämällä käyttäjien tavoitteet ja toimialan ehdot, jotta APIt ratkaisevat todellisia ongelmia.",
+  "resource.api-design-principles.tips": "Mukauta API-designperiaatteet omaan kontekstiisi sopiviksi",
+  "resource.api-value-proposition-canvas.title": "API-arvolupauskanvas",
   "resource.api-value-proposition-canvas.description": "Kohdista API-ominaisuudet käyttäjien tarpeisiin kartoittamalla tehtävät, ongelmat ja hyödyt API-tuotteisiin.",
   "resource.api-value-proposition-canvas.outcomes": "Keskitetty ominaisuuksien kehittäminen",
-  "resource.api-value-proposition-canvas.steps": "Luettelo käyttäjän matkan tehtävistä",
-  "resource.api-value-proposition-canvas.tips": "Hyödynnä Customer Journey Canvasin tietoja",
-  "resource.business-impact-canvas.title": "Business Impact Canvas",
+  "resource.api-value-proposition-canvas.steps": "Listaa käyttäjäpolun tehtävät.",
+  "resource.api-value-proposition-canvas.tips": "Hyödynnä Asiakaspolkukanvasin tietoja",
+  "resource.business-impact-canvas.title": "Liiketoimintavaikutuskanvas",
   "resource.business-impact-canvas.description": "Suunnittele skaalautuva ja turvallinen API-alusta-arkkitehtuuri, joka täyttää liiketoiminnan ja tekniset vaatimukset.",
   "resource.business-impact-canvas.outcomes": "Skaalautuva API-infrastruktuuri",
   "resource.business-impact-canvas.steps": "Saatavuusriskit: Tunnista riskit ja vaikutukset.",
   "resource.business-impact-canvas.tips": "Otetaan arkkitehdit ja rakennuttajat mukaan suunnitteluprosessiin.",
-  "resource.capacity-canvas.title": "Capacity Canvas",
+  "resource.capacity-canvas.title": "Kapasiteettikanvas",
   "resource.capacity-canvas.description": "Suunnittele API-kapasiteetti vastaamaan nykyisiä ja tulevia liiketoiminnan vaatimuksia ja varmista skaalautuvuus ja suorituskyky.",
   "resource.capacity-canvas.outcomes": "API-kapasiteetin mukauttaminen liiketoiminnan volyymiin",
   "resource.capacity-canvas.steps": "Dokumentoi nykyiset liiketoiminnan volyymit",
   "resource.capacity-canvas.tips": "Käytä analytiikkaa kasvusuuntausten ennustamiseen",
-  "resource.customer-journey-canvas.title": "Customer Journey Canvas",
-  "resource.customer-journey-canvas.description": "Kartoita asiakkaan matkat tarpeiden ja kipupisteiden tunnistamiseksi, jotta API-suunnittelua ja käyttäjäkokemusta voidaan parantaa.",
+  "resource.customer-journey-canvas.title": "Asiakaspolkukanvas",
+  "resource.customer-journey-canvas.description": "Kartoittaa asiakkaan tai käyttäjän polun tarpeiden ja kipupisteiden tunnistamiseksi, jotta kyvykkyyden ja rajapinnan suunnittelu perustuu todelliseen kontekstiin.",
   "resource.customer-journey-canvas.outcomes": "Parempi asiakasymmärrys",
   "resource.customer-journey-canvas.steps": "Määrittele asiakaspersoona",
   "resource.customer-journey-canvas.tips": "Toista vaiheet tiimin panoksen avulla vaiheiden tarkentamiseksi.",
-  "resource.event-canvas.title": "Event Canvas",
-  "resource.event-canvas.description": "Suunnittele tapahtumapohjaisia sovellusliittymiä määrittelemällä tapahtumia, laukaisimia ja käsittelylogiikkaa.",
+  "resource.event-canvas.title": "Tapahtumakanvas",
+  "resource.event-canvas.description": "Suunnittele tapahtumapohjaisia rajapintoja ja kyvykkyyksiä määrittelemällä tapahtumat, laukaisijat ja käsittelylogiikka.",
   "resource.event-canvas.outcomes": "Määritelty tapahtumapohjainen arkkitehtuuri",
   "resource.event-canvas.steps": "Järjestelmän keskeisten tapahtumien tunnistaminen",
   "resource.event-canvas.tips": "Tapahtumaskeemojen käyttäminen tapahtumamuotojen standardoimiseksi",
-  "resource.graphql-canvas.title": "GraphQL Canvas",
+  "resource.graphql-canvas.title": "GraphQL-kanvas",
   "resource.graphql-canvas.description": "Suunnittele GraphQL APIt määrittelemällä tyypit, kyselyt, mutaatiot ja tilaukset.",
   "resource.graphql-canvas.outcomes": "Strukturoidun GraphQL APIn suunnittelu",
-  "resource.graphql-canvas.steps": "Mitä ongelmia API-käyttäjät yrittävät ratkaista? Mitä tietoja he tarvitsevat?",
+  "resource.graphql-canvas.steps": "Mitä ongelmia API-hyödyntäjät yrittävät ratkaista? Mitä tietoja he tarvitsevat?",
   "resource.graphql-canvas.tips": "Käytä introspektiota tyyppimääritysten validointiin",
-  "resource.interaction-canvas.title": "Interaction Canvas",
+  "resource.interaction-canvas.title": "Vuorovaikutuskanvas",
   "resource.interaction-canvas.description": "Määrittele API-vuorovaikutukset, työnkulut ja odotetut vastaukset, jotta varmistetaan yhdenmukainen API-kokemus.",
   "resource.interaction-canvas.outcomes": "Selkeät API-vuorovaikutuksen työnkulut",
-  "resource.interaction-canvas.steps": "API-vuorovaikutusten kartoittaminen käyttäjän tehtäviin",
+  "resource.interaction-canvas.steps": "Kartoita rajapinnan vuorovaikutukset käyttäjän tehtäviin.",
   "resource.interaction-canvas.tips": "Aloita yleisistä käyttötapauksista ennen ääritapausten käsittelyä",
-  "resource.location-canvas.title": "Location Canvas",
-  "resource.location-canvas.description": "Kartoita API-palveluntarjoajien ja -kuluttajien sijainnit vaatimustenmukaisuuden ja suorituskyvyn varmistamiseksi eri alueilla.",
+  "resource.location-canvas.title": "Sijaintikanvas",
+  "resource.location-canvas.description": "Kartoita API-palveluntarjoajien ja -hyödyntäjien sijainnit vaatimustenmukaisuuden ja suorituskyvyn varmistamiseksi eri alueilla.",
   "resource.location-canvas.outcomes": "Paikallisten säännösten noudattaminen",
   "resource.location-canvas.steps": "API-palveluntarjoajien sijainnit kartalla.",
   "resource.location-canvas.tips": "Yhteistyö oikeudellisten ja sääntöjen noudattamista käsittelevien tiimien kanssa",
-  "resource.rest-canvas.title": "REST Canvas",
-  "resource.rest-canvas.description": "Suunnittele sovellusrajapinnat RESTful-periaatteiden mukaisesti määrittelemällä resurssit, verbit sekä esimerkkipyynnöt ja -vastaukset.",
-  "resource.rest-canvas.outcomes": "Johdonmukainen RESTful API-suunnittelu",
+  "resource.rest-canvas.title": "REST-kanvas",
+  "resource.rest-canvas.description": "Suunnittele rajapinnat RESTful-periaatteiden mukaisesti määrittelemällä resurssit, verbit sekä esimerkkipyynnöt ja -vastaukset.",
+  "resource.rest-canvas.outcomes": "Johdonmukainen RESTful API-design",
   "resource.rest-canvas.steps": "Tunnista APIn tarjoamat keskeiset resurssit",
   "resource.rest-canvas.tips": "Käytä tavallisia HTTP-menetelmiä (GET, POST, PUT, DELETE).",
   "resource.api-community-engagement-strategies.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään API-yhteisön sitouttamisstrategioita",
   "resource.api-community-engagement-strategies.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-community-engagement-strategies.steps.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan sovellusrajapintojen arvoa ja hyötyjä.",
+  "resource.api-community-engagement-strategies.steps.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan rajapintojen arvoa ja hyötyjä.",
   "resource.api-community-engagement-strategies.steps.2": "Luo opetusmateriaalia (esim. opetusohjelmia, dokumentaatiota), jossa selitetään APIn ominaisuuksia, hyötyjä ja käyttötapoja.",
   "resource.api-community-engagement-strategies.steps.3": "Kytkeydy API-käyttäjiin palautekierrosten, tukikanavien ja yhteisöfoorumien kautta ymmärtämään heidän tarpeitaan ja parantamaan APIn käyttöönottoa.",
   "resource.api-community-engagement-strategies.steps.4": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
   "resource.api-community-engagement-strategies.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-compliance-best-practices.outcomes.1": "Standardoitu lähestymistapa API Compliance Best Practices -käytäntöjen avulla",
   "resource.api-compliance-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-compliance-best-practices.steps.1": "Toteuta toimenpiteitä, joilla varmistetaan, että sovellusrajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
+  "resource.api-compliance-best-practices.steps.1": "Toteuta toimenpiteitä, joilla varmistetaan, että rajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
   "resource.api-compliance-best-practices.steps.2": "Käytä tarkistuslistoja, linereita ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
   "resource.api-compliance-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-development-best-practices.outcomes.1": "Standardoitu lähestymistapa API-kehityksen parhaiden käytäntöjen avulla",
@@ -208,12 +208,12 @@
   "resource.api-metrics-and-analytics.outcomes.1": "Standardoitu lähestymistapa API Metrics And Analyticsin avulla",
   "resource.api-metrics-and-analytics.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.api-metrics-and-analytics.steps.1": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
-  "resource.api-metrics-and-analytics.steps.2": "Seuraa API-aloitteita varmistaaksesi toimintaohjeiden ja hallintokäytäntöjen noudattamisen.",
+  "resource.api-metrics-and-analytics.steps.2": "Seuraa API-aloitteita varmistaaksesi toimintaohjeiden ja governance-käytäntöjen noudattamisen.",
   "resource.api-metrics-and-analytics.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-onboarding-best-practices.outcomes.1": "Standardoitu lähestymistapa API Onboarding Best Practices -käytäntöjen avulla",
   "resource.api-onboarding-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-onboarding-best-practices.steps.1": "Kehitetään käyttöönottoprosesseja ja resursseja, joiden avulla API-käyttäjät ymmärtävät, miten APIita käytetään tehokkaasti.",
-  "resource.api-onboarding-best-practices.steps.2": "Dokumentoi, miten kuluttajat löytävät ja käyttävät sovellusliittymää, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
+  "resource.api-onboarding-best-practices.steps.1": "Kehitä käyttöönottoprosesseja ja resursseja, joiden avulla API-hyödyntäjät ymmärtävät, miten API-rajapintoja käytetään tehokkaasti.",
+  "resource.api-onboarding-best-practices.steps.2": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaä, mukaan lukien käyttöönottoprosessit ja rekisteröinti.",
   "resource.api-onboarding-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-portfolio-management-guidelines.outcomes.1": "Standardoitu lähestymistapa API-salkunhallintaohjeiden avulla",
   "resource.api-portfolio-management-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
@@ -223,15 +223,15 @@
   "resource.api-portfolio-management-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-security-best-practices.outcomes.1": "Standardoitu lähestymistapa API-turvallisuuden parhaiden käytäntöjen avulla",
   "resource.api-security-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-security-best-practices.steps.1": "Toteuta turvatoimia, kuten todennus, valtuutus, salaus ja nopeuden rajoittaminen, suojaamaan sovellusrajapintoja uhkilta.",
-  "resource.api-security-best-practices.steps.2": "Toteuta automaattiset tietoturvatarkastukset ja vaatimustenmukaisuuden validoinnit CI/CD-putkessa varmistaaksesi, että sovellusrajapinnat ovat turvallisia ja vaatimustenmukaisia.",
+  "resource.api-security-best-practices.steps.1": "Toteuta turvatoimia, kuten todennus, valtuutus, salaus ja nopeuden rajoittaminen, suojaamaan rajapintoja uhkilta.",
+  "resource.api-security-best-practices.steps.2": "Toteuta automaattiset tietoturvatarkastukset ja vaatimustenmukaisuuden validoinnit CI/CD-putkessa varmistaaksesi, että rajapinnat ovat turvallisia ja vaatimustenmukaisia.",
   "resource.api-security-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-team-structure-guidelines.outcomes.1": "Standardoitu lähestymistapa API-tiimirakenneohjeiden avulla",
   "resource.api-team-structure-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.api-team-structure-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-testing-best-practices.outcomes.1": "Standardoitu lähestymistapa API-testauksen parhaiden käytäntöjen avulla",
   "resource.api-testing-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-testing-best-practices.steps.1": "Integroi toiminnallinen ja ei-toiminnallinen testaus CI/CD-putkeen varmistaaksesi, että sovellusrajapinnat täyttävät laatuvaatimukset.",
+  "resource.api-testing-best-practices.steps.1": "Integroi toiminnallinen ja ei-toiminnallinen testaus CI/CD-putkeen varmistaaksesi, että rajapinnat täyttävät laatuvaatimukset.",
   "resource.api-testing-best-practices.steps.2": "Käytä automatisoituja testausvälineitä API-toiminnallisuuden, tietoturvan ja suorituskyvyn validointiin.",
   "resource.api-testing-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-training-programs.outcomes.1": "Standardoitu lähestymistapa API-koulutusohjelmien avulla",
@@ -251,7 +251,7 @@
   "resource.apiops-CI-CD-for-apis.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.competitor-analysis-template.outcomes.1": "Vakioitu lähestymistapa käyttäen kilpailija-analyysimallia",
   "resource.competitor-analysis-template.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.competitor-analysis-template.steps.1": "Analysoi kilpailijoiden sovellusrajapinnat ymmärtämään niiden vahvuudet, heikkoudet ja ainutlaatuiset myyntivaltit.",
+  "resource.competitor-analysis-template.steps.1": "Analysoi kilpailijoiden rajapinnat ymmärtämään niiden vahvuudet, heikkoudet ja ainutlaatuiset myyntivaltit.",
   "resource.competitor-analysis-template.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.contract-first-design.outcomes.1": "Vakioitu lähestymistapa, jossa käytetään sopimusperusteista suunnittelua (Contract First Design)",
   "resource.contract-first-design.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
@@ -264,17 +264,17 @@
   "resource.data-privacy-guidelines.outcomes.1": "Standardoitu lähestymistapa tietosuojaa koskevien suuntaviivojen avulla",
   "resource.data-privacy-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.data-privacy-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.domain-canvas.outcomes.1": "Vakioitu lähestymistapa Domain Canvasin avulla",
+  "resource.domain-canvas.outcomes.1": "Vakioitu lähestymistapa Toimialuekanvasin avulla",
   "resource.domain-canvas.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.domain-canvas.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.ecosystem-vision-template.outcomes.1": "Yhdenmukaistettu lähestymistapa ekosysteemivision mallin avulla",
   "resource.ecosystem-vision-template.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.ecosystem-vision-template.steps.1": "Tunnistetaan tärkeimmät ekosysteemikumppanit ja sidosryhmät, jotka hyötyvät ekosysteemistä tai osallistuvat siihen.",
-  "resource.ecosystem-vision-template.steps.2": "Tunnista markkinapuutteet, jotka sovellusrajapintasi voivat täyttää kilpailijoiden tarjonnan perusteella.",
+  "resource.ecosystem-vision-template.steps.2": "Tunnista markkinapuutteet, jotka rajapintasi voivat täyttää kilpailijoiden tarjonnan perusteella.",
   "resource.ecosystem-vision-template.steps.3": "Tunnista mahdolliset kumppanit, joiden APIt voivat parantaa API-valmiuksiasi ja arvolupaustasi.",
   "resource.ecosystem-vision-template.steps.4": "Kehitä erottautumisstrategia, jossa korostetaan sovellusrajapintojesi ainutlaatuisia ominaisuuksia ja etuja.",
   "resource.ecosystem-vision-template.steps.5": "Määrittele sovellusrajapintojesi ekosysteemivisio, mukaan lukien se, miten ne ovat vuorovaikutuksessa muiden järjestelmien ja alustojen kanssa.",
-  "resource.ecosystem-vision-template.steps.6": "Suunnittele sovellusrajapinnat, jotka mahdollistavat saumattoman integroinnin ja yhteistyön ekosysteemissä.",
+  "resource.ecosystem-vision-template.steps.6": "Suunnittele rajapinnat, jotka mahdollistavat saumattoman integroinnin ja yhteistyön ekosysteemissä.",
   "resource.ecosystem-vision-template.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.industry-standards-and-best-practices.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään alan standardeja ja parhaita käytäntöjä.",
   "resource.industry-standards-and-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
@@ -304,7 +304,7 @@
   "resource.test-automation-frameworks.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.vendor-management-best-practices.outcomes.1": "Myyjähallinnon parhaita käytäntöjä käyttävä standardoitu lähestymistapa",
   "resource.vendor-management-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.vendor-management-best-practices.steps.1": "Määrittele kriteerit toimittajien sovellusrajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
+  "resource.vendor-management-best-practices.steps.1": "Määrittele kriteerit toimittajien rajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
   "resource.vendor-management-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-audit-checklist.outcomes.1": "Standardoitu lähestymistapa API-auditoinnin tarkistuslistan avulla",
   "resource.api-audit-checklist.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
@@ -313,28 +313,28 @@
   "resource.api-audit-checklist.tips.1": "Käytä API-auditointilistaa yhteistyössä liiketoiminta- ja teknologia-roolien välillä",
   "resource.api-business-model-canvas.outcomes.1": "Keskeisten resurssien ja kumppaneiden tunnistaminen",
   "resource.api-business-model-canvas.outcomes.2": "API-ominaisuuksien ja liiketoiminnan tavoitteiden yhteensovittaminen",
-  "resource.api-business-model-canvas.steps.1": "Kuluttajasegmenttien määrittely",
+  "resource.api-business-model-canvas.steps.1": "Hyödyntäjäsegmenttien määrittely",
   "resource.api-business-model-canvas.steps.2": "Kehittäjäsuhdestrategioiden määrittäminen",
   "resource.api-business-model-canvas.steps.3": "Kartoita jakelukanavat",
-  "resource.api-business-model-canvas.steps.4": "dokumentoida keskeiset resurssit ja toimet",
+  "resource.api-business-model-canvas.steps.4": "Dokumentoi keskeiset resurssit ja toimet",
   "resource.api-business-model-canvas.steps.5": "Tunnistetaan tärkeimmät kumppanit ja sidosryhmät",
   "resource.api-business-model-canvas.steps.6": "Korosta hyötyjä ja kustannuksia",
   "resource.api-business-model-canvas.tips.1": "Mahdollisuuksien priorisointi kustannus-hyöty -suhteen kaltaisten mittareiden avulla.",
   "resource.api-business-model-canvas.tips.2": "Validoi tuotokset tärkeimpien sidosryhmien kanssa",
-  "resource.api-design-principles.outcomes.1": "Standardoitu lähestymistapa API-suunnitteluperiaatteiden avulla",
+  "resource.api-design-principles.outcomes.1": "Standardoitu lähestymistapa API-designperiaatteiden avulla",
   "resource.api-design-principles.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-design-principles.steps.1": "**Johdonmukainen nimeäminen ja käyttäytyminen:** Sovelletaan yhteisiä käytäntöjä resursseja, virheitä ja formaatteja varten, jotta sovellusrajapinnat olisivat ennakoitavissa.",
+  "resource.api-design-principles.steps.1": "**Johdonmukainen nimeäminen ja käyttäytyminen:** Sovelletaan yhteisiä käytäntöjä resursseja, virheitä ja formaatteja varten, jotta rajapinnat olisivat ennakoitavissa.",
   "resource.api-design-principles.steps.2": "**Sopimusperusteinen:** kaappaa rajapinta OpenAPIlla tai AsyncAPIlla ennen koodausta tiimien yhdenmukaistamiseksi ja automaation mahdollistamiseksi.",
   "resource.api-design-principles.steps.3": "**Käytettävyys ja löydettävyys:** Selkeä dokumentaatio ja esimerkit, jotta kehittäjät ymmärtävät nopeasti, miten APIta käytetään.",
-  "resource.api-design-principles.steps.4": "**Iteroi turvallisesti:** Kehitä malleja pienissä, versioiduissa vaiheissa, jotta muutokset eivät häiritse nykyisiä kuluttajia.",
+  "resource.api-design-principles.steps.4": "**Iteroi turvallisesti:** Kehitä malleja pienissä, versioiduissa vaiheissa, jotta muutokset eivät häiritse nykyisiä API-hyödyntäjiä.",
   "resource.api-design-principles.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
   "resource.api-value-proposition-canvas.outcomes.1": "Yhdenmukaisuus käyttäjien tarpeiden kanssa",
-  "resource.api-value-proposition-canvas.outcomes.2": "Parempi API-kuluttajien tyytyväisyys",
+  "resource.api-value-proposition-canvas.outcomes.2": "Parempi API-hyödyntäjien tyytyväisyys",
   "resource.api-value-proposition-canvas.steps.1": "Tunnistetaan ominaisuudet, jotka tuottavat odotettuja hyötyjä",
   "resource.api-value-proposition-canvas.steps.2": "Määritellään haasteisiin vastaavat ominaisuudet",
   "resource.api-value-proposition-canvas.steps.3": "Ominaisuuksien kartoittaminen API-tuotteisiin",
-  "resource.api-value-proposition-canvas.tips.1": "Korosta ominaisuuksia, jotka helpottavat kipuja tai parantavat voittoja.",
-  "resource.api-value-proposition-canvas.tips.2": "Validoi ominaisuudet API-käyttäjien kanssa yhdenmukaistamisen varmistamiseksi.",
+  "resource.api-value-proposition-canvas.tips.1": "Korosta ominaisuuksia, jotka vähentävät kipupisteitä tai vahvistavat tavoiteltuja hyötyjä.",
+  "resource.api-value-proposition-canvas.tips.2": "Validoi ominaisuudet API-hyödyntäjien kanssa yhdenmukaistamisen varmistamiseksi.",
   "resource.business-impact-canvas.outcomes.1": "Parannettu turvallisuus ja vaatimustenmukaisuus",
   "resource.business-impact-canvas.outcomes.2": "Parannettu API-suorituskyky",
   "resource.business-impact-canvas.steps.1": "Saatavuusriskien lieventämistavat: Määrittele lieventämistoimenpiteet.",
@@ -352,48 +352,48 @@
   "resource.capacity-canvas.steps.4": "Ehdotetaan skaalausstrategioita",
   "resource.capacity-canvas.tips.1": "Määrittele huippukäytön skenaariot",
   "resource.capacity-canvas.tips.2": "Sisällytä skaalautuvuuden testaus suunnitteluvaiheeseen.",
-  "resource.customer-journey-canvas.outcomes.1": "Parannettu API-suunnittelu",
-  "resource.customer-journey-canvas.outcomes.2": "Parempi käyttäjäkokemus",
+  "resource.customer-journey-canvas.outcomes.1": "Parannettu API-design",
+  "resource.customer-journey-canvas.outcomes.2": "Parempi käyttäjä- ja hyödyntäjäkokemus",
   "resource.customer-journey-canvas.steps.1": "Tunnista matkan käynnistäjät",
   "resource.customer-journey-canvas.steps.2": "Kuvaile matkan loppua",
   "resource.customer-journey-canvas.steps.3": "Kartoita matkan vaiheet ja syötteet/lähtötiedot",
   "resource.customer-journey-canvas.steps.4": "Tunnista asiakkaan kipupisteet",
   "resource.customer-journey-canvas.steps.5": "Yhteenveto asiakkaan saamista eduista",
-  "resource.customer-journey-canvas.steps.6": "Määritellään tarvittavat panokset ja tuotokset",
+  "resource.customer-journey-canvas.steps.6": "Määritellään tarvittavat syötteet ja tuotokset",
   "resource.customer-journey-canvas.steps.7": "Määrittele API-vuorovaikutukset kullekin vaiheelle",
-  "resource.customer-journey-canvas.tips.1": "Käytä tämän kanvaasin tuotoksia muiden kanvaasien, kuten API Value Proposition Canvas -kanvaasin, laatimiseen.",
+  "resource.customer-journey-canvas.tips.1": "Käytä tämän kanvaksen tuotoksia muiden kanvasten, kuten API-arvolupauskanvas -kanvaksen, laatimiseen.",
   "resource.event-canvas.outcomes.1": "Selkeät tapahtumien laukaisijat ja käsittelylogiikka",
   "resource.event-canvas.outcomes.2": "Parempi reagointikyky reaaliaikaisiin muutoksiin",
   "resource.event-canvas.steps.1": "Määritä laukaisimet kullekin tapahtumalle",
-  "resource.event-canvas.steps.2": "Tapahtumien backend-käsittelylogiikan kuvaaminen",
+  "resource.event-canvas.steps.2": "Kuvaa tapahtumien taustajärjestelmän käsittelylogiikka.",
   "resource.event-canvas.steps.3": "Määritä tuloksena olevat tuotokset tai kuittaukset",
-  "resource.event-canvas.tips.1": "dokumentoida tapahtumavirtoja ja riippuvuuksia",
+  "resource.event-canvas.tips.1": "Dokumentoi tapahtumavirrat ja riippuvuudet.",
   "resource.event-canvas.tips.2": "Validoi tapahtumien käsittely testitapauksilla",
   "resource.graphql-canvas.outcomes.1": "Määritellyt tyypit ja niiden väliset suhteet",
   "resource.graphql-canvas.outcomes.2": "Selkeät kyselyt, mutaatiot ja tilaukset",
-  "resource.graphql-canvas.steps.1": "Määritä GraphQL-tyypit ja niiden attribuutit: Mitkä ovat keskeiset tyypit (esim. käyttäjä, tilaus, tuote)?",
+  "resource.graphql-canvas.steps.1": "Määritä GraphQL-tyypit ja niiden attribuutit: mitkä ovat keskeiset tyypit (esim. käyttäjä, tilaus, tuote)?",
   "resource.graphql-canvas.steps.2": "Kartoita tyyppien väliset suhteet: Miten tyypit liittyvät toisiinsa sisäkkäisissä kyselyissä?",
   "resource.graphql-canvas.steps.3": "Määritä kyselyt tiedonhakua varten",
   "resource.graphql-canvas.steps.4": "Määritä tietojen muuttamista koskevat mutaatiot: Millaisilla operaatioilla tietoja muutetaan (esim. luodaan, päivitetään, poistetaan)?",
   "resource.graphql-canvas.steps.5": "Reaaliaikaisten päivitysten tilaukset",
   "resource.graphql-canvas.steps.6": "Määrittele todennus ja valtuutus: Kuka voi käyttää mitä kenttiä tai tyyppejä?",
   "resource.graphql-canvas.steps.7": "Harkitse, onko olemassa sivutus-, suodatus- tai nopeusrajoituksia.",
-  "resource.graphql-canvas.tips.1": "asiakirjan esimerkkikyselyt ja mutaatiot",
+  "resource.graphql-canvas.tips.1": "Dokumentoi esimerkkikyselyt ja mutaatiot.",
   "resource.graphql-canvas.tips.2": "Varmista, että tyyppien nimet ovat kuvaavia ja johdonmukaisia.",
-  "resource.interaction-canvas.outcomes.1": "Määritellyt panokset ja tuotokset kutakin vuorovaikutusta varten.",
+  "resource.interaction-canvas.outcomes.1": "Määritellyt syötteet ja tuotokset kutakin vuorovaikutusta varten.",
   "resource.interaction-canvas.outcomes.2": "Yhdenmukaiset validointisäännöt vuorovaikutustilanteissa",
   "resource.interaction-canvas.steps.1": "Määritä päätepisteet kullekin vuorovaikutukselle",
-  "resource.interaction-canvas.steps.2": "dokumentoida kunkin vuorovaikutuksen panokset ja tuotokset",
+  "resource.interaction-canvas.steps.2": "Dokumentoi kunkin vuorovaikutuksen syötteet ja tuotokset.",
   "resource.interaction-canvas.steps.3": "Validointisääntöjen ja -rajoitusten määrittäminen",
   "resource.interaction-canvas.steps.4": "Luo vuorovaikutusmalleja CRUD-, kysely-, komento- ja tapahtumapohjaista vuorovaikutusta varten.",
   "resource.interaction-canvas.tips.1": "Simuloi vuorovaikutusta mallitietojen kanssa työnkulkujen validoimiseksi.",
-  "resource.interaction-canvas.tips.2": "dokumentoida odotetut reaktiot onnistuneisiin ja epäonnistuneisiin vuorovaikutustilanteisiin.",
+  "resource.interaction-canvas.tips.2": "Dokumentoi odotetut vastaukset onnistuneissa ja epäonnistuneissa vuorovaikutustilanteissa.",
   "resource.location-canvas.outcomes.1": "Optimoitu API-suorituskyky eri alueilla",
   "resource.location-canvas.outcomes.2": "Parempi ymmärrys alueellisista vaatimuksista",
-  "resource.location-canvas.steps.1": "Dokumentoi, missä kuluttajat sijaitsevat.",
+  "resource.location-canvas.steps.1": "Dokumentoi, missä hyödyntäjät sijaitsevat.",
   "resource.location-canvas.steps.2": "Tunnista sovellettavat säädökset.",
   "resource.location-canvas.steps.3": "Dokumentoi, missä tietojen on oltava.",
-  "resource.location-canvas.steps.4": "Varmista, että sovellusrajapinnat ovat käytettävissä kaikilla aiotuilla verkkoalueilla.",
+  "resource.location-canvas.steps.4": "Varmista, että rajapinnat ovat käytettävissä kaikilla aiotuilla verkkoalueilla.",
   "resource.location-canvas.steps.5": "Validoi verkon suorituskyky eri alueilla.",
   "resource.location-canvas.tips.1": "Verkon suorituskyvyn validointi keskeisillä alueilla",
   "resource.location-canvas.tips.2": "Ratkaise ennakoivasti sijaintiin liittyviä rajoitteita",
@@ -403,40 +403,40 @@
   "resource.rest-canvas.steps.2": "Määritä HTTP-verbit, joita käytetään vuorovaikutuksessa resurssien kanssa.",
   "resource.rest-canvas.steps.3": "Anna esimerkkipyynnöt ja -vastaukset kullekin verbille",
   "resource.rest-canvas.tips.1": "Varmistetaan, että resurssien URI:t ovat intuitiivisia ja johdonmukaisia.",
-  "resource.rest-canvas.tips.2": "asiakirjan virheiden käsittely ja vastauskoodit",
-  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
-  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
-  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
-  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
-  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
-  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
-  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
-  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
-  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
-  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
-  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
-  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
-  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
-  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
-  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
-  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
-  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
-  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
-  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
-  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
-  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
-  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
-  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
-  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
-  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
-  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
+  "resource.rest-canvas.tips.2": "Dokumentoi virheiden käsittely ja vastauskoodit.",
+  "resource.capability-value-proposition-canvas.title": "Kyvykkyyden arvolupauskanvas",
+  "resource.capability-value-proposition-canvas.description": "Teknologiariippumaton kanvas hyödyntäjien tehtävien, tavoiteltujen hyötyjen, kipupisteiden ja mahdollisten uudelleenkäytettävien kyvykkyyksien kartoittamiseen ennen integraatiotyylin valintaa.",
+  "resource.capability-value-proposition-canvas.outcomes": "Selkeä arvolupaus uudelleenkäytettävälle kyvykkyydelle",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Hyödyntäjien tehtävät, tavoitellut hyödyt ja kipupisteet on kuvattu ilman oletusta tietystä teknologiasta.",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Mahdolliset uudelleenkäytettävät kyvykkyydet on tunnistettu arkkitehtuurin arviointia varten.",
+  "resource.capability-value-proposition-canvas.steps": "Listaa hyödyntäjien tehtävät ja lopputulokset, joita kyvykkyyden tulee tukea.",
+  "resource.capability-value-proposition-canvas.steps.1": "Tunnista kyvykkyyden ominaisuudet, jotka mahdollistavat tavoitellut hyödyt.",
+  "resource.capability-value-proposition-canvas.steps.2": "Tunnista kyvykkyyden ominaisuudet, jotka vähentävät kipupisteitä.",
+  "resource.capability-value-proposition-canvas.steps.3": "Ryhmittele ominaisuudet mahdollisiksi uudelleenkäytettäviksi kyvykkyyksiksi.",
+  "resource.capability-value-proposition-canvas.tips": "Pysy teknologiariippumattomana, kunnes vaatimukset osoittavat sopivan toteutustyylin.",
+  "resource.capability-value-proposition-canvas.tips.1": "Käytä tätä API-arvolupauskanvaksen sijaan, kun API-rajapintaa ei vielä ole valittu integraatiotyyliä varten.",
+  "resource.capability-business-model-canvas.title": "Kyvykkyyden liiketoimintamallikanvas",
+  "resource.capability-business-model-canvas.description": "Liiketoimintamallikanvas uudelleenkäytettäville integraatiokyvykkyyksille. Se kattaa arvon, hyödyntäjät, omistajuuden, osallistamisen, kustannukset ja hyödyt ilman oletusta API-toteutuksesta.",
+  "resource.capability-business-model-canvas.outcomes": "Toteuttamiskelpoinen toimintamalli uudelleenkäytettävälle kyvykkyydelle",
+  "resource.capability-business-model-canvas.outcomes.1": "Omistajuus, hyödyntäjät, kanavat, kumppanit ja tuen tarpeet on selkeytetty.",
+  "resource.capability-business-model-canvas.outcomes.2": "Kustannukset ja hyödyt ovat näkyvissä ennen arkkitehtuurisitoumusta.",
+  "resource.capability-business-model-canvas.steps": "Tiivistä kyvykkyyden arvolupaus.",
+  "resource.capability-business-model-canvas.steps.1": "Tunnista hyödyntäjäsegmentit ja osallistamiskanavat.",
+  "resource.capability-business-model-canvas.steps.2": "Määritä keskeiset toiminnot, resurssit ja kumppanit.",
+  "resource.capability-business-model-canvas.steps.3": "Kuvaa kustannukset ja hyödyt.",
+  "resource.capability-business-model-canvas.steps.4": "Selkeytä omistajuus, rahoitus, tuki ja elinkaaren odotukset.",
+  "resource.capability-business-model-canvas.steps.5": "Validoi malli hyödyntäjien, tuottajien ja governance-sidosryhmien kanssa.",
+  "resource.capability-business-model-canvas.tips": "Käytä tätä API-liiketoimintamallikanvaksen sijaan, kun integraatiotyyli on vielä avoin.",
+  "resource.capability-business-model-canvas.tips.1": "Pidä fokus uudelleenkäytettävän kyvykkyyden elinkelpoisuudessa, ei yksittäisessä yhteydessä.",
+  "resource.consumer-experience-requirements-canvas.title": "Hyödyntäjäkokemuksen vaatimuskanvas",
+  "resource.consumer-experience-requirements-canvas.description": "Vaatimuskanvas hyödyntäjäkokemuksen ja ei-toiminnallisten tarpeiden kuvaamiseen ennen myöhempää arkkitehtuurivalintaa.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Teknologiariippumattomat hyödyntäjävaatimukset",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Kokemukseen ja ei-toiminnallisiin tarpeisiin liittyvät vaatimukset on kuvattu ennen suunnittelun aloittamista.",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Arkkitehtuurivaikutukset on dokumentoitu toteutustyylin valintaa varten.",
+  "resource.consumer-experience-requirements-canvas.steps": "Kuvaa hyödyntäjien tavoitteet ja käyttökonteksti.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Dokumentoi saatavuuteen, ajantasaisuuteen, volyymiin, suorituskykyyn, datan laatuun ja yhdenmukaisuuteen liittyvät odotukset.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Dokumentoi turvallisuuteen, tietosuojaan, käyttöönottoon, muutoksiin, havainnoitavuuteen, tukeen ja palautumiseen liittyvät odotukset.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Tiivistä, mitä vaatimukset tarkoittavat mahdollisille arkkitehtuurityyleille.",
+  "resource.consumer-experience-requirements-canvas.tips": "Käytä tätä siltana kyvykkyyden arvon ja arkkitehtuuripäätöksen välillä.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Älä valitse API-rajapintaa, tapahtumaa, tiedostoa, streamia tai datatuotetta ennen kuin vaatimukset osoittavat sopivan vaihtoehdon."
 }
diff --git a/src/data/method/fi/labels.stakeholders.json b/src/data/method/fi/labels.stakeholders.json
index 206a8d4..046d0b7 100644
--- a/src/data/method/fi/labels.stakeholders.json
+++ b/src/data/method/fi/labels.stakeholders.json
@@ -8,8 +8,8 @@
   "stakeholder.api-program-owner.description": "Koordinoi API-portfolion käytäntöjä, organisaation suuntautumista ja pitkän aikavälin API-kyvykkyyksien kehitystä.",
   "stakeholder.api-product-owner.title": "API-tuoteomistaja",
   "stakeholder.api-product-owner.description": "Ohjaa API-mahdollisuutta, priorisointia ja tuotetasolla tehtyjä päätöksiä elinkaaren aikana.",
-  "stakeholder.capability-owner.title": "Capability Owner",
-  "stakeholder.capability-owner.description": "",
+  "stakeholder.capability-owner.title": "Kyvykkyyden omistaja",
+  "stakeholder.capability-owner.description": "Vastaa kyvykkyyden visiosta, tavoitteista, priorisoinnista ja elinkaaren aikaisesta kehittämisestä.",
   "stakeholder.domain-specialist.title": "Liiketoiminta-asiantuntija",
   "stakeholder.domain-specialist.description": "Tuo syvällistä tietoa liiketoiminta-alasta, käsitteistä, säännöistä ja rajoituksista, joita APIn täytyy heijastaa.",
   "stakeholder.customer-specialist.title": "Asiakas- tai kumppaniedustaja",
@@ -18,32 +18,32 @@
   "stakeholder.api-consumer-specialist.description": "Edustaa kehittäjien, integraattoreiden tai muiden API-hyödyntäjien tarpeita, jotka käyttävät APIa suoraan.",
   "stakeholder.platform-architect.title": "Alusta-arkkitehti",
   "stakeholder.platform-architect.description": "Ohjaa alustan, integraation, skaalautuvuuden ja arkkitehtuurin päätöksiä, jotka määrittelevät, miten API on rakennettu ja toimii.",
-  "stakeholder.api-architect.title": "API Architect",
-  "stakeholder.api-architect.description": "",
-  "stakeholder.integration-architect.title": "Integration Architect",
-  "stakeholder.integration-architect.description": "",
-  "stakeholder.platform-owner.title": "Platform Owner",
-  "stakeholder.platform-owner.description": "",
+  "stakeholder.api-architect.title": "API-arkkitehti",
+  "stakeholder.api-architect.description": "Vastaa API-arkkitehtuurista, suunnitteluperiaatteista ja rajapintasopimusten laadusta.",
+  "stakeholder.integration-architect.title": "Integraatioarkkitehti",
+  "stakeholder.integration-architect.description": "Suunnittelee integraatioratkaisut, integraatiomallit ja niiden yhteensopivuuden kokonaisarkkitehtuurin kanssa.",
+  "stakeholder.platform-owner.title": "Alustan omistaja",
+  "stakeholder.platform-owner.description": "Vastaa alustan kyvykkyyksistä, kehittämisestä ja operatiivisesta toiminnasta.",
   "stakeholder.api-designer.title": "API-suunnittelija",
-  "stakeholder.api-designer.description": "Muokkaa API-sopimusta, vuorovaikutusmallia, johdonmukaisuutta ja käytettävyyttä exponoituja kykyjä.",
+  "stakeholder.api-designer.description": "Suunnittelee rajapintasopimukset, vuorovaikutusmallit, johdonmukaisuuden, käytettävyyden ja tarjottavat kyvykkyydet.",
   "stakeholder.api-engineer.title": "Ohjelmistokehittäjä",
   "stakeholder.api-engineer.description": "Omistaa toteutuksen, automaation, testauksen ja julkaisun kulkuun liittyvät kysymykset, jotka ovat tarpeen toimittaa API luotettavasti.",
-  "stakeholder.automation-owner.title": "Automation Owner",
-  "stakeholder.automation-owner.description": "",
-  "stakeholder.process-owner.title": "Process Owner",
-  "stakeholder.process-owner.description": "",
-  "stakeholder.automation-engineer.title": "Automation Engineer",
-  "stakeholder.automation-engineer.description": "",
+  "stakeholder.automation-owner.title": "Automaation omistaja",
+  "stakeholder.automation-owner.description": "Vastaa automaatiokyvykkyyksien tavoitteista, priorisoinnista ja liiketoiminta-arvosta.",
+  "stakeholder.process-owner.title": "Prosessin omistaja",
+  "stakeholder.process-owner.description": "Vastaa automatisoitavan liiketoimintaprosessin tavoitteista, kehittämisestä ja tuloksista.",
+  "stakeholder.automation-engineer.title": "Automaatiokehittäjä",
+  "stakeholder.automation-engineer.description": "Toteuttaa, testaa ja ylläpitää automaatioratkaisuja sekä niiden integraatioita.",
   "stakeholder.security-specialist.title": "Turvallisuusasiantuntija",
   "stakeholder.security-specialist.description": "Varmistaa, että turvallisuusriskit, kontrollit ja luottamusrajat käsitellään koko API-kehitysprosessin aikana.",
   "stakeholder.compliance-specialist.title": "Vaatimuksenmukaisuuden ja oikeudellinen asiantuntija",
-  "stakeholder.compliance-specialist.description": "Selventää oikeudellisia, tietosuojaa koskevia, sääntelyä ja sopimusvaatimuksia, jotka vaikuttavat APIin.",
+  "stakeholder.compliance-specialist.description": "Selventää juridiset, tietosuojaan liittyvät ja muut vaatimustenmukaisuusvaatimukset, jotka vaikuttavat kyvykkyyteen tai rajapintaan.",
   "stakeholder.governance-specialist.title": "API-hallinnan omistaja",
   "stakeholder.governance-specialist.description": "Vastaa API-hallintaprosesseista, ohjeista ja päätöksenteosta, joka määrittelee, miten API-kehityspäätökset tehdään ja dokumentoidaan.",
   "stakeholder.api-devrel-specialist.title": "Dokumentoinnin ja kehittäjäsuhteiden omistaja",
   "stakeholder.api-devrel-specialist.description": "Varmistaa, että API-dokumentaatio, esimerkit, koulutus ja kehittäjäsuhteiden strategiat tukevat API-hyödyntäjien tarpeita.",
   "stakeholder.operations-specialist.title": "Tuki- ja operaatioiden omistaja",
-  "stakeholder.operations-specialist.description": " Vastaa API-tuen, valvonnan, vianmäärityksen ja jatkuvan parantamisen prosesseista, jotka varmistavat APIn luotettavuuden ja hyödyntäjien tyytyväisyyden.",
+  "stakeholder.operations-specialist.description": "Vastaa tuesta, valvonnasta, vianmäärityksestä ja jatkuvasta parantamisesta, jotka varmistavat ratkaisun luotettavuuden ja hyödyntäjien tyytyväisyyden.",
   "stakeholder.partner-specialist.title": "Kumppani- ja toimittajavastaava",
-  "stakeholder.partner-specialist.description": "Koordinoi ulkoisia kumppanisuhde, toimittajasuhteita ja vendor-suhteita, jotka vaikuttavat API-strategiaan ja -kehitykseen."
-}
+  "stakeholder.partner-specialist.description": "Koordinoi kumppani- ja toimittajasuhteita, jotka vaikuttavat kyvykkyyden suunnitteluun ja kehittämiseen."
+}
\ No newline at end of file
diff --git a/src/data/method/fi/labels.stations.json b/src/data/method/fi/labels.stations.json
index 2e96a4a..c35a04a 100644
--- a/src/data/method/fi/labels.stations.json
+++ b/src/data/method/fi/labels.stations.json
@@ -1,61 +1,61 @@
 {
-  "group.core-stations.title": "APIn elinkaaren ydinasemat",
-  "group.core-stations.description": "API Metron ydinasemat, joissa tiimit voivat oppia rakentamaan ja hallinnoimaan rajapintoja tehokkaasti.",
+  "group.core-stations.title": "Kyvykkyyden elinkaaren ydinasemat",
+  "group.core-stations.description": "Menetelmän ydinasemat, joissa tiimit oppivat suunnittelemaan, toimittamaan, hallitsemaan ja parantamaan uudelleenkäytettäviä kyvykkyyksiä APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden ja muiden integraatiotapojen yli.",
   "group.sub-stations.title": "APIn elinkaaren lähiöasemat",
   "group.sub-stations.description": "Lähiöasemat, jotka tarjoavat lisäresursseja, työkaluja ja parhaita käytäntöjä API-tiimeille.",
-  "station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
-  "station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, käyttäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
-  "station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, ei tuotteina. Tulos? Hämmentyneitä kuluttajia, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
-  "station.api-product-strategy.apply_in_work": "Tarjotaan ohjeita ja malleja API-liiketoimintamallien, arvolupausten ja etenemissuunnitelmien luomista varten.",
-  "station.api-product-strategy.outcomes": "Suoraviivainen API-arvolupaus ja yleisö",
-  "station.api-product-strategy.how_it_works": "Tutki asiakkaan tai yhteistyökumppanin ongelmaa, jonka oletat voivasi ratkaista APIen avulla. Kartoita sidosryhmät, niiden matkat ja tulokset Customer Journey canvasin avulla.",
-  "station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia käyttäjiä varten.",
-  "station.api-consumer-experience.description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen.",
-  "station.api-consumer-experience.why_it_matters": "Hyvät aPIt eivät ainoastaan toimi - ne tuntuvat intuitiivisilta. Riippumatta siitä, onko hyödyntäjä sisäinen kehittäjä, ulkoinen kumppani vai tekoälyagentti, heidän kokemuksensa ratkaisee hyväksynnän. Ilman selkeää kokemussuunnitelmaa",
-  "station.api-consumer-experience.how_it_works": "Tarkastele olemassa olevaa API Value Proposition Canvasta API-hyödyntäjän näkökulmasta. Säilytä tuetut liiketoimintatehtävät vakaina ja rikasta tuskaa lievittäviä ja hyötyjä mahdollistavia ominaisuuksia API-hyödyntäjien näkökulmalla, jotta ne voivat ohjata myöhempiä suunnittelupäätöksiä.",
-  "station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-käyttäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
-  "station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-käyttäjälle.",
-  "station.api-consumer-experience.apply_in_work": "Tarjotaan ohjeita, työkaluja ja palautemekanismeja sisäisten ja ulkoisten kehittäjien ja kumppaneiden kokemusten ymmärtämiseksi, analysoimiseksi ja parantamiseksi.",
-  "station.api-consumer-experience.outcomes": "Tunnista ja priorisoi API-asiakkaat",
-  "station.api-platform-architecture.title": "API-alustan arkkitehtuuri",
-  "station.api-platform-architecture.description": "Varmistetaan skaalautuvuus, uudelleenkäyttö ja hallinta API- ja alustakomponenttien välillä.",
-  "station.api-platform-architecture.why_it_matters": "Kun rajapinnat skaalautuvat eri tiimeille, alustan on mahdollistettava hallinta ja uudelleenkäyttö nopeutta estämättä. Tällä asemalla kerrotaan, miten API-arkkitehtuurit voidaan suunnitella pitkäikäisiksi, turvallisiksi ja tehokkaiksi.",
-  "station.api-platform-architecture.apply_in_work": "Perustetaan skaalautuva, turvallinen ja vaatimustenmukainen infrastruktuuri API-toimintoja varten. Annetaan ohjeita arkkitehtuurin parhaista käytännöistä.",
-  "station.api-platform-architecture.outcomes": "Vähennä turhia API-rajapintoja ja vähennä pilvialustakustannuksia.",
-  "station.api-platform-architecture.how_it_works": "Business Impact Canvas auttaa tunnistamaan ja lieventämään APIn saatavuuteen, tietoturvaan ja toiminnallisuuteen liittyviä riskejä ja tukemaan tietoon perustuvia arkkitehtuuripäätöksiä.",
-  "station.api-design.title": "API-design - Suunnittele arvoa tuottavia rajapintoja",
-  "station.api-design.description": "Luo API-suunnitelmia, jotka ovat johdonmukaisia, uudelleenkäytettäviä ja perustuvat liiketoiminnallisiin tavoitteisiin sekä yhteisiin standardeihin.",
-  "station.api-design.why_it_matters": "APIen suunnittelu ei tarkoita pelkästään päätepisteiden (endpoints) nimeämistä. Hyvä suunnittelu varmistaa, että APIt ovat käyttökelpoisia, johdonmukaisia ja linjassa liiketoiminnallisten ja teknisten tavoitteiden kanssa. Huono suunnittelu johtaa tiukkoihin riippuvuuksiin, heikkoon uudelleenkäytettävyyteen ja kalliiseen uudelleen toteutukseen eri tiimien välillä.",
-  "station.api-design.apply_in_work": "Tarjoa uudelleenkäytettäviä suunnittelumalleja, yhteisiä standardeja ja validointityökaluja API-määrityksille. Varmista, että suunnittelupäätökset ovat johdonmukaisia, tarkistettuja varhaisessa vaiheessa ja linjassa liiketoiminnallisten tavoitteiden kanssa.",
-  "station.api-design.outcomes": "Hyvin dokumentoidut ja johdonmukaiset API-mallit",
-  "station.api-design.how_it_works": "Määrittele keskeiset oliot, niiden attribuutit ja suhteet yhteisen käsitteellisen ymmärryksen luomiseksi eri rajapinnoille.",
-  "station.api-delivery.title": "API-kehitys - Kehitä turvalliset ja luotettavat rajapinnat",
-  "station.api-delivery.description": "Rakenna, testaa ja julkaise rajapintoja käyttämällä nykyaikaisia jakeluputkia ja parhaita teknisiä käytäntöjä.",
-  "station.api-delivery.why_it_matters": "Parhaatkin API-suunnitelmat epäonnistuvat, jos kehitys on epäjohdonmukaista. Tällä asemalla varmistetaan, että rajapinnat rakennetaan laadukkaasti, testataan perusteellisesti ja otetaan käyttöön luotettavasti, mikä mahdollistaa nopeammat iteraatiot ja suuremman luottamuksen.",
-  "station.api-delivery.apply_in_work": "Toimittaa koodauskehyksiä, kirjastoja ja standardeja API-toteutusta varten. CI/CD-putkien, laadunvarmistuskehysten ja käyttöönottoautomaatiotyökalujen toteuttaminen.",
-  "station.api-delivery.outcomes": "Rajapinnat, jotka on toteutettu testattujen kehysten ja mallien avulla.",
-  "station.api-delivery.how_it_works": "Käytä API-kehityksen parhaita käytäntöjä ohjeena validoidun sopimuksen toteuttamiseen vakiintuneilla kehysrakenteilla ja kirjastoilla varmistaen, että tulos on uudelleenkäytettävä ja ylläpidettävä.",
-  "station.api-audit.title": "API-auditointi - API-rajapintojen tarkastus vaatimustenmukaisuuden ja laadun varmistamiseksi",
-  "station.api-audit.description": "Varmista, että APIt täyttävät liiketoiminta-, suunnittelu- ja toimintastandardit ennen julkaisua ja käyttöönottoa.",
-  "station.api-audit.why_it_matters": "APIt ovat pitkäikäisiä tuotteita, ja niiden on täytettävä laatu-, johdonmukaisuus- ja vaatimustenmukaisuusodotukset. Auditointi yhdistää suunnittelupäätökset, toteutuksen ja toimintavalmiuden määriteltyihin standardeihin, mikä vähentää riskejä ennen käyttöönottoa.",
-  "station.api-audit.apply_in_work": "Luo johdonmukainen auditointiprosessi, joka arvioi APIn valmiutta elinkaaren eri vaiheissa määriteltyjen kriteerien, todisteiden ja standardien avulla. Varmista, että puutteet tunnistetaan varhaisessa vaiheessa ja korjataan ennen julkaisua.",
-  "station.api-audit.outcomes": "APIt täyttävät sisäiset ja ulkoiset standardit",
-  "station.api-audit.how_it_works": "Suorita tarkastuksia varmistaaksesi, että rajapinnat täyttävät organisatoriset, tekniset ja oikeudelliset standardit ennen julkaisemista.",
-  "station.api-publishing.title": "API-julkaiseminen - Julkaise APIt luotettavasti",
-  "station.api-publishing.description": "Esittele APIt turvallisesti ja selkeästi oikealle yleisölle oikean dokumentaation ja prosessien avulla.",
-  "station.api-publishing.why_it_matters": "Julkaiseminen on muutakin kuin käyttöönottoa - kyse on löydettävyydestä, saatavuudesta ja tuesta. Jos rajapintoja ei julkaista oikein, niitä ei käytetä, käytetä uudelleen tai suojata tehokkaasti.",
-  "station.api-publishing.apply_in_work": "Mahdollistetaan APIen julkaiseminen asiaankuuluvassa ympäristössä ja selkeät rekisteröinti- ja käyttöoikeusmekanismit (esim. API-avaimet, OAuth, tilaussuunnitelmat) API-hyödyntäjäsegmenttien sekä turvallisuus- ja vaatimustenmukaisuusvaatimusten mukaan.",
-  "station.api-publishing.outcomes": "APIt julkaistaan oikeassa ympäristössä (yksityinen, kumppani, julkinen).",
-  "station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille rajapinnan käyttäjille.",
-  "station.monitoring-and-improving.title": "Seuranta ja parantaminen - API-arvoa varten",
-  "station.monitoring-and-improving.description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen.",
-  "station.monitoring-and-improving.why_it_matters": "API-kehitys ei lopu käynnistykseen. Ilman seurantaa tiimit eivät voi parantaa käyttöönottoa, suorituskykyä tai ROI",
-  "station.monitoring-and-improving.apply_in_work": "Ota käyttöön analytiikkakehykset suorituskyvyn ja sitoutumisen seuraamiseksi. Kehitetään palautesilmukoita, analytiikkatyökaluja ja sitouttamisstrategioita API-rajapintoja varten.",
-  "station.monitoring-and-improving.outcomes": "Suorituskyvyn ja käytön mittarit määritellään ja niitä seurataan.",
-  "station.monitoring-and-improving.how_it_works": "Seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
+  "station.api-product-strategy.title": "Strategia",
+  "station.api-product-strategy.description": "Kehystä liiketoimintatarve uudelleenkäytettävänä kyvykkyytenä ennen toteutustavan valintaa.",
+  "station.api-product-strategy.why_it_matters": "Integraatio- ja API-työssä hypätään usein liian nopeasti tekniseen malliin. Tämä asema pitää tiimin keskittyneenä liiketoimintapolkuun, toimialan merkitykseen, arvoon, uudelleenkäyttöpotentiaaliin, omistajuuteen ja elinkelpoisuuteen ennen APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden tai suoran integraation valintaa.",
+  "station.api-product-strategy.apply_in_work": "Käytä yhteisiä polku-, toimiala-, arvolupaus- ja liiketoimintamallipohjia teknologiariippumattomien vaatimusten kokoamiseen ja päätä, pitäisikö kyvykkyyden olla uudelleenkäytettävä.",
+  "station.api-product-strategy.outcomes": "Teknologiariippumaton kyvykkyysmahdollisuuden kuvaus",
+  "station.api-product-strategy.how_it_works": "Kuvaa asiakkaan tai kumppanin polku, joka synnyttää kyvykkyystarpeen ja paljastaa tehtävät, ongelmat, hyödyt, syötteet, tuotokset ja päätöspisteet.",
+  "station.api-consumer-experience.title": "Hyödyntäjien vaatimukset ja käyttöönotto",
+  "station.api-consumer-experience.description": "Kokoa hyödyntäjien käyttöönotto, standardit, ei-toiminnalliset vaatimukset, palveluodotukset, rajoitteet, tietoturvatarpeet, sallitut protokollat, datan tuoreus, palvelutasot, havainnoitavuus, palautuminen, käyttöönoton vaatimukset ja tuottajan vastuut.",
+  "station.api-consumer-experience.why_it_matters": "Oikea arkkitehtuuri riippuu hyödyntäjien tavoitteista, käyttöönotto-odotuksista, palvelutasoista, datan laatutarpeista, muutosten sietokyvystä, havainnoitavuudesta, tuesta ja tuottajan rajoitteista.",
+  "station.api-consumer-experience.how_it_works": "Käytä Consumer Experience Requirements Canvas -pohjaa hyödyntäjien tavoitteiden, saatavuuden, tuoreuden, volyymin, suorituskyvyn, datan laadun, tietoturvan, käyttöönoton, muutoksen, havainnoitavuuden ja palautumisen odotusten kuvaamiseen.",
+  "station.api-consumer-experience.how_it_works.1": "Kuvaa käyttöönotto-ohjeistuksen avulla, miten hyödyntäjät löytävät kyvykkyyden, pyytävät sen käyttöä, testaavat sitä, saavat hyväksynnän ja aloittavat käytön.",
+  "station.api-consumer-experience.how_it_works.2": "Käytä syntyvää polkua ja vaatimuksia kyvykkyyden hyödyntäjien käyttöönoton, dokumentaation, tuen ja palautesilmukoiden parantamiseen.",
+  "station.api-consumer-experience.apply_in_work": "Käytä hyödyntäjäkokemuksen ja käyttöönoton ohjeistusta, jotta odotukset ovat selkeitä sekä hyödyntäjille että tuottajille.",
+  "station.api-consumer-experience.outcomes": "Dokumentoidut hyödyntäjävaatimukset ja käyttöönotto-odotukset",
+  "station.api-platform-architecture.title": "Arkkitehtuuri- ja alustapäätökset",
+  "station.api-platform-architecture.description": "Käytä vaatimuksia ja rajoitteita oikean arkkitehtuurimallin ja tarvittavien alustakyvykkyyksien valintaan.",
+  "station.api-platform-architecture.why_it_matters": "Arkkitehtuurivalintojen tulee perustua näyttöön liiketoimintavaikutuksesta, sijainneista, luottamusrajoista, kapasiteetista, viiveestä, datan omistajuudesta, yhdenmukaisuudesta, operoitavuudesta, tietoturvasta, tietosuojasta, hallintamallista ja kustannuksista.",
+  "station.api-platform-architecture.apply_in_work": "Vertaa mahdollisia arkkitehtuurityylejä koottuihin vaatimuksiin ja dokumentoi valittu malli sekä sen perustelut.",
+  "station.api-platform-architecture.outcomes": "Perusteltu arkkitehtuurivalinta",
+  "station.api-platform-architecture.how_it_works": "Käytä Business Impact Canvas -pohjaa saatavuus-, tietoturva- ja datariskien tunnistamiseen, koska ne vaikuttavat arkkitehtuurivaihtoehtoihin.",
+  "station.api-design.title": "Ratkaisu- ja rajapintasuunnittelu",
+  "station.api-design.description": "Suunnittele rajapintasopimus ja vuorovaikutusmalli sen jälkeen, kun arkkitehtuurivalinta on perusteltu.",
+  "station.api-design.why_it_matters": "Kun arkkitehtuurimalli on tiedossa, suunnittelun on muutettava kyvykkyysvaatimukset selkeiksi rajapintasopimuksiksi, vuorovaikutuksiksi, skeemoiksi, datasäännöiksi, elinkaariodotuksiksi ja hyödyntäjien velvoitteiksi.",
+  "station.api-design.apply_in_work": "Valitse valittuun toteutustapaan sopivat suunnitteluresurssit ja dokumentoi rajapintasopimus ennen toteutusta.",
+  "station.api-design.outcomes": "Validoitu rajapintasopimus valitulle toteutustavalle",
+  "station.api-design.how_it_works": "Käytä Domain Canvas -pohjaa uudelleen liiketoimintaolioiden, termien, sääntöjen ja omistajuuden vahvistamiseen ennen sopimussuunnittelua.",
+  "station.api-delivery.title": "Toimitus ja operointi",
+  "station.api-delivery.description": "Toimita valittu toteutustapa asianmukaisilla suunnittelu-, testaus-, tietoturva-, automaatio- ja operointikäytännöillä.",
+  "station.api-delivery.why_it_matters": "Uudelleenkäytettävä kyvykkyys tarvitsee luotettavan toimituksen ja operoinnin riippumatta siitä, toteutuuko se APIlla, tapahtumavirtana, tiedostosiirtona, datatuotteena vai suorana integraationa.",
+  "station.api-delivery.apply_in_work": "Sovella toimituksen, testauksen, CI/CD:n, operoinnin ja tietoturvan ohjeistusta valittuun toteutustapaan.",
+  "station.api-delivery.outcomes": "Toimitettu kyvykkyys, joka vastaa validoitua rajapintasopimusta",
+  "station.api-delivery.how_it_works": "Käytä kehityksen parhaita käytäntöjä validoidun rajapintasopimuksen toteuttamiseen vakiintuneilla kehyksillä, kirjastoilla ja tiimin standardeilla.",
+  "station.api-audit.title": "Laadun ja valmiuden varmistus",
+  "station.api-audit.description": "Auditoi kyvykkyyden rajapintasopimus, kontrollit, tukimalli, havainnoitavuus, dokumentaatio ja elinkaarivalmius ennen julkaisua.",
+  "station.api-audit.why_it_matters": "Uudelleenkäytettävät kyvykkyydet luovat operatiivisia, dataan, tietoturvaan, tietosuojaan, vaatimustenmukaisuuteen ja hyödyntäjiin liittyviä riskejä. Valmiustarkastukset vähentävät yllätyksiä ennen julkaisua tai tuotantokäyttöä.",
+  "station.api-audit.apply_in_work": "Käytä auditointi- ja vaatimustenmukaisuusresursseja varmistaaksesi, että kyvykkyys on valmis hallittuun julkaisuun ja uudelleenkäyttöön.",
+  "station.api-audit.outcomes": "Dokumentoitu valmius julkaisuun ja uudelleenkäyttöön",
+  "station.api-audit.how_it_works": "Käytä auditoinnin tarkistuslistaa uudelleenkäytettävänä laatutarkistuslistana rajapintasopimuksen, dokumentaation, tietoturvan, suorituskyvyn ja vaatimustenmukaisuuden valmiudelle.",
+  "station.api-publishing.title": "Julkaisu ja käyttöönoton mahdollistaminen",
+  "station.api-publishing.description": "Julkaise uudelleenkäytettävän kyvykkyyden tiedot, jotta hyödyntäjät voivat löytää sen, pyytää käyttöä, ottaa sen käyttöön, käyttää sitä ja saada tukea.",
+  "station.api-publishing.why_it_matters": "Uudelleenkäytettävät kyvykkyydet tuottavat arvoa vain, kun hyödyntäjät löytävät ne, ymmärtävät rajapintasopimuksen ja palveluodotukset, voivat pyytää käyttöoikeutta ja tietävät, kuka omistaa tuen ja elinkaaripäätökset.",
+  "station.api-publishing.apply_in_work": "Julkaise omistajuus, dokumentaatio, käyttöönotto, tukiyhteystiedot, palveluodotukset, elinkaaren tila ja käyttöoikeuspyyntöjen polut.",
+  "station.api-publishing.outcomes": "Löydettävä uudelleenkäytettävä kyvykkyys",
+  "station.api-publishing.how_it_works": "Julkaise kyvykkyyden tiedot asianmukaisiin katalogeihin, portaaleihin, yhdyskäytäviin tai ympäristöihin, jotta useat hyödyntäjät voivat käyttää sitä uudelleen.",
+  "station.monitoring-and-improving.title": "Seuranta ja parantaminen",
+  "station.monitoring-and-improving.description": "Seuraa käyttöä, luotettavuutta, datan laatua, hyödyntäjien tuloksia, operatiivisia kustannuksia ja uudelleenkäytön mahdollisuuksia julkaisun jälkeen.",
+  "station.monitoring-and-improving.why_it_matters": "Kyvykkyydet tarvitsevat jatkuvaa palautetta pysyäkseen luotettavina, arvokkaina, kustannustehokkaina ja uudelleenkäytettävinä, kun hyödyntäjät, järjestelmät, data ja alustat muuttuvat.",
+  "station.monitoring-and-improving.apply_in_work": "Käytä mittareita, analytiikkaa ja osallistamisen käytäntöjä kyvykkyyden jatkuvaan parantamiseen.",
+  "station.monitoring-and-improving.outcomes": "Mitattu kyvykkyyden tila ja arvo",
+  "station.monitoring-and-improving.how_it_works": "Käytä mittari- ja analytiikkaohjeistusta kyvykkyyden käytön, luotettavuuden, datan laadun, kustannusten, käyttöönoton ja hyödyntäjäarvon mittareiden määrittelyyn.",
   "station.user-experience.title": "Käyttäjäkokemus - Suunnittele APIt käyttäjälähtöisesti",
   "station.user-experience.description": "Varmistetaan, että rajapinnat on suunniteltu loppukäyttäjää ajatellen ja että ne tarjoavat saumattoman ja intuitiivisen käyttökokemuksen.",
-  "station.user-experience.why_it_matters": "APIt eivät ole vain teknisiä tuotteita, vaan ne ovat käyttäjäkohtaisia tuotteita. Huono käyttökokemus voi johtaa vähäiseen käyttöön ja turhautumiseen. Tämä asema auttaa tiimejä suunnittelemaan APIt, jotka ovat käyttäjäystävällisiä ja vastaavat kuluttajien tarpeita.",
+  "station.user-experience.why_it_matters": "APIt eivät ole vain teknisiä tuotteita, vaan ne ovat myös käyttäjälle näkyviä tuotteita. Huono käyttökokemus voi johtaa vähäiseen käyttöön ja turhautumiseen. Tämä asema auttaa tiimejä suunnittelemaan APIt, jotka ovat käyttäjäystävällisiä ja vastaavat hyödyntäjien tarpeita.",
   "station.user-experience.apply_in_work": "Tarjotaan käyttäjäkokemusta koskevia ohjeita, malleja ja työkaluja API-suunnittelua varten. Varmistetaan, että tiimit noudattavat käyttäjäkeskeisiä suunnittelukäytäntöjä ja sisällyttävät käyttäjäpalautteen API-iteraatioihin.",
   "station.user-experience.outcomes": "APIt on suunniteltu käyttäjien tarpeet mielessä pitäen",
   "station.user-experience.how_it_works": "Käyttäjäpersoonien käyttö loppukäyttäjien tarpeiden ja odotusten ymmärtämiseksi.",
@@ -115,7 +115,7 @@
   "station.vendor-management.how_it_works": "Ota käyttöön toimittajahallintaprosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
   "station.contract-design.title": "Sopimussuunnittelu - Määrittele selkeät API-sopimukset",
   "station.contract-design.description": "Luo selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
-  "station.contract-design.why_it_matters": "API-sopimukset ovat olennaisen tärkeitä, jotta varmistetaan selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita selkeiden, kattavien ja helposti ymmärrettävien API-sopimusten suunnitteluun.",
+  "station.contract-design.why_it_matters": "API-rajapintasopimukset ovat olennaisen tärkeitä, jotta API-toimittajien ja hyödyntäjien välillä on selkeys ja yhdenmukaisuus. Tämä asema tarjoaa ohjeita selkeiden, kattavien ja helposti ymmärrettävien API-rajapintasopimusten suunnitteluun.",
   "station.contract-design.apply_in_work": "Tarjotaan sopimussuunnittelumalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja hyvin määritellyt API-sopimukset, joissa hahmotellaan odotukset, vastuut ja käyttöohjeet.",
   "station.contract-design.outcomes": "Kullekin ajapinnalle määritellyt selkeät API-sopimukset",
   "station.contract-design.how_it_works": "Määrittele API-sopimukset, joissa hahmotellaan kunkin APIn odotukset, vastuut ja käyttöohjeet.",
@@ -144,17 +144,17 @@
   "station.release-management.outcomes": "Hallitut ja sujuvat API-julkaisut",
   "station.release-management.how_it_works": "Määrittele rajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
   "station.service-agreements.title": "Palvelusopimukset - määrittele API-palvelutasot",
-  "station.service-agreements.description": "Laadi palvelusopimukset, joissa määritellään API-toimittajien ja kuluttajien odotukset, palvelutasot ja vastuut.",
-  "station.service-agreements.why_it_matters": "Palvelusopimukset ovat olennaisen tärkeitä, jotta voidaan varmistaa selkeys ja yhdenmukaisuus API-toimittajien ja kuluttajien välillä. Tämä asema tarjoaa ohjeita sellaisten palvelusopimusten laatimiseen, joissa hahmotellaan odotukset, palvelutasot ja vastuut, mikä vähentää väärinkäsityksiä ja riitoja.",
-  "station.service-agreements.apply_in_work": "Tarjotaan palvelusopimusmalleja, standardoituja muotoja ja tarkistusprosesseja. Varmistetaan, että tiimit luovat selkeät ja tarkkaan määritellyt palvelusopimukset, joissa hahmotellaan API-toimittajien ja -kuluttajien odotukset, palvelutasot ja vastuut.",
+  "station.service-agreements.description": "Laadi palvelusopimukset, joissa määritellään API-toimittajien ja hyödyntäjien odotukset, palvelutasot ja vastuut.",
+  "station.service-agreements.why_it_matters": "Palvelusopimukset ovat olennaisen tärkeitä, jotta API-toimittajien ja hyödyntäjien välillä on selkeys ja yhdenmukaisuus. Tämä asema tarjoaa ohjeita palvelusopimusten laatimiseen niin, että odotukset, palvelutasot ja vastuut ovat selvät ja väärinkäsitysten riski pienenee.",
+  "station.service-agreements.apply_in_work": "Tarjoa palvelusopimusmalleja, standardoituja muotoja ja katselmointiprosesseja. Varmista, että tiimit luovat selkeät ja tarkkaan määritellyt palvelusopimukset, joissa kuvataan API-toimittajien ja hyödyntäjien odotukset, palvelutasot ja vastuut.",
   "station.service-agreements.outcomes": "Kullekin rajapinnalle määritellyt selkeät palvelusopimukset",
   "station.service-agreements.how_it_works": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin rajapintaa varten.",
   "station.api-consumer-adoption.title": "APIn käyttöönotto - APIn käytön edistäminen",
-  "station.api-consumer-adoption.description": "Toteutat strategioita, joilla edistetään API-käyttäjien hyväksyntää ja sitoutumista ja varmistetaan, että API-rajapintoja käytetään tehokkaasti.",
-  "station.api-consumer-adoption.why_it_matters": "API-käyttäjien hyväksynnän edistäminen on ratkaisevan tärkeää APIen arvon hyödyntämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä API-kuluttajien sitouttamiseksi ja sen varmistamiseksi, että he ymmärtävät, miten API-rajapintoja käytetään tehokkaasti ja miten niistä saadaan arvoa.",
-  "station.api-consumer-adoption.apply_in_work": "Tarjotaan API-kuluttajille resursseja, koulutusmateriaalia ja sitouttamisstrategioita. Varmistetaan, että tiimit toteuttavat strategioita, jotka edistävät API-kuluttajien hyväksyntää, sitoutumista ja tyytyväisyyttä.",
-  "station.api-consumer-adoption.outcomes": "APIn käyttöönottostrategioiden toteuttaminen kuluttajille",
-  "station.api-consumer-adoption.how_it_works": "Kehitetään käyttöönottoprosesseja ja resursseja, joiden avulla API-käyttäjät ymmärtävät, miten Rajapintoja käytetään tehokkaasti.",
+  "station.api-consumer-adoption.description": "Toteuta strategioita, joilla edistetään API-hyödyntäjien käyttöönottoa ja sitoutumista sekä varmistetaan, että API-rajapintoja käytetään tehokkaasti.",
+  "station.api-consumer-adoption.why_it_matters": "API-hyödyntäjien käyttöönoton edistäminen on ratkaisevan tärkeää APIen arvon hyödyntämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä API-hyödyntäjien sitouttamiseen ja sen varmistamiseen, että he ymmärtävät, miten API-rajapintoja käytetään tehokkaasti ja miten niistä saadaan arvoa.",
+  "station.api-consumer-adoption.apply_in_work": "Tarjoa API-hyödyntäjille resursseja, koulutusmateriaalia ja sitouttamisstrategioita. Varmista, että tiimit toteuttavat strategioita, jotka edistävät API-hyödyntäjien käyttöönottoa, sitoutumista ja tyytyväisyyttä.",
+  "station.api-consumer-adoption.outcomes": "APIn käyttöönottoa edistävät strategiat hyödyntäjille",
+  "station.api-consumer-adoption.how_it_works": "Kehitä käyttöönoton prosesseja ja resursseja, joiden avulla API-hyödyntäjät ymmärtävät, miten rajapintoja käytetään tehokkaasti.",
   "station.api-promotion.title": "API-näkyvyys - APIn näkyvyyden ja käytön lisääminen",
   "station.api-promotion.description": "Edistetään rajapintoja näkyvyyden, käytön ja hyväksynnän lisäämiseksi kohdeyleisöjen keskuudessa.",
   "station.api-promotion.why_it_matters": "API-rajapintojen tunnetuksi tekeminen on olennaisen tärkeää niiden näkyvyyden lisäämiseksi ja käytön edistämiseksi. Tämä asema tarjoaa strategioita ja parhaita käytäntöjä APIen tehokkaaseen markkinointiin kohdeyleisöille, jotta varmistetaan, että nämä ovat tietoisia APIista ja ymmärtävät niiden arvon.",
@@ -203,52 +203,52 @@
   "station.budget-and-resource-management.apply_in_work": "Tarjotaan API-aloitteille budjettihallintakehykset, priorisointikriteerit ja seurantatyökalut. Varmistaa, että tiimit hallinnoivat tehokkaasti budjetteja ja resursseja ja optimoivat API-kehitykseen ja -hallintaan tehdyt investoinnit mahdollisimman suuren arvon tuottamiseksi.",
   "station.budget-and-resource-management.outcomes": "API-aloitteita varten laaditut budjetti- ja resurssienhallintakäytännöt",
   "station.budget-and-resource-management.how_it_works": "Määrittele budjetti- ja resurssienhallintakäytännöt, joissa hahmotellaan API-aloitteiden budjettien ja resurssien hallinnointiprosessit.",
-  "station.api-product-strategy.outcomes.1": "Yhteinen kieli tuotteen, suunnittelun ja tekniikan välillä",
-  "station.api-product-strategy.outcomes.2": "vankka esitys tai peruste rahoituksen/hyväksynnän saamiseksi.",
-  "station.api-product-strategy.how_it_works.1": "Määrittele keskeiset entiteetit, niiden ominaisuudet ja suhteet, jotta voidaan luoda yhteinen käsitteellinen ymmärrys eri matkojen ja lopulta APIen välille.",
-  "station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tallentaaksesi tuetut liiketoimintatehtävät sekä API-käyttäjien ongelmat, hyödyt ja ominaisuudet, jotka muovaavat uusia tai uudelleenkäytettäviä API-rajapintoja.",
-  "station.api-product-strategy.how_it_works.3": "Määrittele arvo - käyttäjille ja liiketoiminnalle - API-liiketoimintamallin avulla, jotta API-strategiastasi tulee visuaalinen, jaettavissa oleva ja helposti validoitava API-asiakkaiden kanssa seuraavalla asemalla.",
-  "station.api-consumer-experience.outcomes.1": "Määrittele API-kokemuksen matka",
-  "station.api-consumer-experience.outcomes.2": "Suunnittele sisäänajo, dokumentointi ja palaute",
-  "station.api-consumer-experience.outcomes.3": "Paranna hyväksyntää aidon empatian ja kehittäjäkokemuksen (DX) avulla.",
-  "station.api-platform-architecture.outcomes.1": "Johdonmukaisen hallinnon toteuttaminen ilman raskasta ylhäältä alaspäin suuntautuvaa valvontaa",
-  "station.api-platform-architecture.outcomes.2": "Suunnittelu sisäistä uudelleenkäyttöä ja ulkoista skaalautuvuutta varten",
-  "station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja kuluttajien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
-  "station.api-platform-architecture.how_it_works.2": "Capacity Canvas -ohjelmassa sovitetaan yhteen liiketoimintatapahtumien mallit, tulevat kulutustrendit ja tekniset ratkaisut, jotta voidaan varmistaa APIn skaalautuvuus ja suorituskyky. Se tarjoaa kriittisen panoksen skaalautumispäätöksiä ja infrastruktuurin suunnittelua varten.",
-  "station.api-platform-architecture.how_it_works.3": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
-  "station.api-design.outcomes.1": "Uudelleenkäytettävät ja validoidut API-sopimukset",
-  "station.api-design.outcomes.2": "Toimialamallien ja vuorovaikutusmallien mukaiset mallit",
-  "station.api-design.outcomes.3": "Suunnittelun jäljitettävyys liiketoiminnan arvoon",
-  "station.api-design.how_it_works.1": "Määrittele Interaction Canvasin avulla, miten hyödyntäjät ovat vuorovaikutuksessa APIn kanssa, ja Varmistetaan, että se vastaa heidän tarpeitaan ja odotuksiaan.",
-  "station.api-design.how_it_works.2": "Sovellat REST-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
-  "station.api-design.how_it_works.3": "Sovellat tapahtumapohjaisia suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
-  "station.api-design.how_it_works.4": "Sovellat GraphQL-suunnittelumalleja luodaksesi johdonmukaisia, uudelleenkäytettäviä API-sopimuksia, jotka validoidaan sidosryhmien kanssa.",
-  "station.api-design.how_it_works.5": "Käytä suunnitteluperiaatteita ja API-tyyliohjetta, jotta suunnittelupäätöksesi ovat linjassa yhteisten sääntöjen kanssa ja mahdollistavat johdonmukaisen auditoinnin ja validoinnin.",
-  "station.api-design.how_it_works.6": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API-suunnittelu täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
-  "station.api-design.how_it_works.7": "Käytä API-tarkastuslistaa varmistaaksesi, että API-suunnittelu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien turvallisuus, suorituskyky ja vaatimustenmukaisuus.",
-  "station.api-delivery.outcomes.1": "Luotettavat ja automatisoidut CI/CD-putket",
-  "station.api-delivery.outcomes.2": "Toiminnallinen ja ei-toiminnallinen testaus integroitu",
-  "station.api-delivery.outcomes.3": "Turvalliset ja vaatimustenmukaiset kehitysputket",
-  "station.api-delivery.how_it_works.1": "Rakenna API-toteutus validoidun sopimuksen pohjalta käyttäen vakiintuneita kehysrakenteita, kirjastoja ja tiimin standardeja.",
-  "station.api-delivery.how_it_works.2": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
-  "station.api-delivery.how_it_works.3": "Käytetään CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
-  "station.api-delivery.how_it_works.4": "Varmistetaan, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
-  "station.api-delivery.how_it_works.5": "Varmistetaan API-auditoinnin tarkistuslistan avulla, että API täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
-  "station.api-audit.outcomes.1": "Selkeä dokumentaatio API-suunnittelusta ja toteutuspäätöksistä",
-  "station.api-audit.outcomes.2": "Turvallisuus, suorituskyky ja vaatimustenmukaisuus validoitu",
-  "station.api-audit.outcomes.3": "Tuotannossa ilmenevien ongelmien riskin pienentäminen",
-  "station.api-audit.how_it_works.1": "Käytä tarkistuslistoja, automatisoituja tarkistustyökaluja eli linttereitä ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
-  "station.api-audit.how_it_works.2": "Tee yhteistyötä hallintotiimien ja toimialan asiantuntijoiden kanssa varmistaaksesi, että rajapinnat ovat valmiita tuotantoon.",
-  "station.api-publishing.outcomes.1": "Selkeät API-käyttöönotto- ja rekisteröintiprosessit",
-  "station.api-publishing.outcomes.2": "Dokumentaatio, turvallisuusmallit ja -käytännöt saatavilla",
-  "station.api-publishing.outcomes.3": "APIt valmiina skaalautumiseen ja hallintaan",
-  "station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaa, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
-  "station.api-publishing.how_it_works.2": "Varmistetaan, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja kuluttajien saatavilla.",
-  "station.monitoring-and-improving.outcomes.1": "Kehittäjien palautekierrokset käytössä",
-  "station.monitoring-and-improving.outcomes.2": "Jatkuvasti tunnistetut ja käsitellyt ongelmat",
-  "station.monitoring-and-improving.outcomes.3": "APIn iterointi käyttäjien tarpeiden mukaisesti",
-  "station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
-  "station.monitoring-and-improving.how_it_works.2": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia.",
+  "station.api-product-strategy.outcomes.1": "Yhteinen ymmärrys hyödyntäjistä, tuottajista, toimialan käsitteistä ja uudelleenkäyttöpotentiaalista",
+  "station.api-product-strategy.outcomes.2": "Kyvykkyyden arvolupaus ja liiketoimintamalli ennen arkkitehtuurin valintaa",
+  "station.api-product-strategy.how_it_works.1": "Määrittele keskeiset oliot, attribuutit, suhteet, omistajuus ja liiketoimintasäännöt, joita kyvykkyyden on noudatettava.",
+  "station.api-product-strategy.how_it_works.2": "Käytä Capability Value Proposition Canvas -pohjaa hyödyntäjien tehtävien, hyötyjen, ongelmien ja uudelleenkäytettävien kyvykkyysominaisuuksien kuvaamiseen nimeämättä toimitusteknologiaa liian aikaisin.",
+  "station.api-product-strategy.how_it_works.3": "Käytä Capability Business Model Canvas -pohjaa omistajuuden, kumppaneiden, kanavien, kustannusten, hyötyjen, tuen ja elinkaariodotusten selkeyttämiseen uudelleenkäytettävälle kyvykkyydelle.",
+  "station.api-consumer-experience.outcomes.1": "Selkeät tuottajan vastuut ja tukiin liittyvät odotukset",
+  "station.api-consumer-experience.outcomes.2": "Arkkitehtuurin kannalta olennaiset rajoitteet valmiina päätöksentekoon",
+  "station.api-consumer-experience.outcomes.3": "Parempi käyttöönotto hyödyntäjäymmärryksen, standardien ja tuottajan selkeyden kautta",
+  "station.api-platform-architecture.outcomes.1": "Dokumentoidut riskit sekä sijainti-, kapasiteetti-, tietoturva-, tietosuoja- ja operoitavuusrajoitteet",
+  "station.api-platform-architecture.outcomes.2": "Selkeä perustelu API-, tapahtuma-, tiedosto-, virta-, datatuote-, suora integraatio- tai hybriditoteutukselle",
+  "station.api-platform-architecture.how_it_works.1": "Käytä Locations Canvas -pohjaa geopoliittisten, sääntelyyn liittyvien, verkko-, datan sijainti- ja luottamusrajarajoitteiden kuvaamiseen.",
+  "station.api-platform-architecture.how_it_works.2": "Käytä Capacity Canvas -pohjaa nykyisten ja tulevien volyymien, huippujen, viiveen, välimuistin, nopeusrajoitusten ja skaalautumisodotusten kuvaamiseen.",
+  "station.api-platform-architecture.how_it_works.3": "Käytä mittari- ja analytiikkaohjeistusta määrittelemään, miten valittua kyvykkyyttä seurataan ja parannetaan.",
+  "station.api-design.outcomes.1": "Johdonmukaiset vuorovaikutus-, data-, tapahtuma-, tiedosto-, työnkulku- tai API-rajapintasopimuspäätökset",
+  "station.api-design.outcomes.2": "Suunnittelun jäljitettävyys kyvykkyyden ja hyödyntäjien vaatimuksiin",
+  "station.api-design.outcomes.3": "Suunnitelmat linjassa toimialamallien ja vuorovaikutusmallien kanssa",
+  "station.api-design.how_it_works.1": "Kuvaa Interaction Canvas -pohjan avulla, miten hyödyntäjät, järjestelmät tai käyttäjät ovat vuorovaikutuksessa kyvykkyyden kanssa.",
+  "station.api-design.how_it_works.2": "Käytä REST-suunnitteluresursseja, kun valittu rajapinta on REST API.",
+  "station.api-design.how_it_works.3": "Käytä Event Canvas -resursseja, kun valittu rajapinta on tapahtumapohjainen.",
+  "station.api-design.how_it_works.4": "Käytä GraphQL-suunnitteluresursseja, kun valittu rajapinta on GraphQL.",
+  "station.api-design.how_it_works.5": "Käytä suunnitteluperiaatteita ja tyyliopasta, jotta suunnittelupäätökset ovat linjassa yhteisten sääntöjen kanssa ja auditointi voi validoida ne johdonmukaisesti.",
+  "station.api-design.how_it_works.6": "Sovella contract-first- tai design-first-lähestymistapaa rajapintasopimuksen kuvaamiseen ja validointiin ennen toteutusta.",
+  "station.api-design.how_it_works.7": "Käytä auditoinnin tarkistuslistaa varmistaaksesi, että suunnittelu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "station.api-delivery.outcomes.1": "Automatisoitu testaus, julkaisu ja ympäristökontrollit",
+  "station.api-delivery.outcomes.2": "Valittuun malliin sopivat tietoturva-, operointi- ja laatukäytännöt",
+  "station.api-delivery.outcomes.3": "Jäljitettävät toimitus- ja julkaisukontrollit",
+  "station.api-delivery.how_it_works.1": "Rakenna toteutus validoidun rajapintasopimuksen pohjalta vakiintuneilla kehyksillä, kirjastoilla ja tiimin standardeilla.",
+  "station.api-delivery.how_it_works.2": "Käytä testausohjeistusta toiminnallisuuden, datan laadun, yhteensopivuuden, tietoturvan, suorituskyvyn, resilienssin ja palautumisodotusten varmistamiseen.",
+  "station.api-delivery.how_it_works.3": "Käytä CI/CD-ohjeistusta koonnin, testauksen, julkaisun, konfiguraation ja jäljitettävyyden automatisointiin.",
+  "station.api-delivery.how_it_works.4": "Käytä tietoturvaohjeistusta datan, käyttöoikeuksien, tunnistetietojen ja alustarajojen suojaamiseen.",
+  "station.api-delivery.how_it_works.5": "Käytä auditoinnin tarkistuslistaa varmistaaksesi, että ratkaisu täyttää toiminnalliset ja ei-toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
+  "station.api-audit.outcomes.1": "Tunnetut puutteet ja korjaustoimet ennen julkaisua",
+  "station.api-audit.outcomes.2": "Näyttö hallintamallin, vaatimustenmukaisuuden, tuen ja operatiivisen hyväksynnän tueksi",
+  "station.api-audit.outcomes.3": "Pienempi riski tuotannon ongelmille",
+  "station.api-audit.how_it_works.1": "Käytä tarkistuslistoja, linttereitä ja testausvälineitä johdonmukaisuuden ja standardien noudattamisen varmistamiseen.",
+  "station.api-audit.how_it_works.2": "Tee yhteistyötä hallintatiimien ja toimialan asiantuntijoiden kanssa varmistaaksesi, että kyvykkyys on valmis tuotantoon.",
+  "station.api-publishing.outcomes.1": "Selkeät käyttöönotto-, käyttöoikeus-, tuki- ja palveluodotukset",
+  "station.api-publishing.outcomes.2": "Elinkaari- ja omistajuustiedot hyödyntäjien ja hallintatiimien saatavilla",
+  "station.api-publishing.outcomes.3": "Hyödyntäjät voivat käyttää ja uudelleenkäyttää kyvykkyyttä",
+  "station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät kyvykkyyden ja käyttävät sitä, mukaan lukien käyttöönotto- ja rekisteröintiprosessit.",
+  "station.api-publishing.how_it_works.2": "Varmista, että tietoturvamallit, käyttöoikeuskonfiguraatio ja oikeudelliset ehdot ovat selkeitä ja hyödyntäjien saatavilla.",
+  "station.monitoring-and-improving.outcomes.1": "Parannusjono, joka perustuu operatiiviseen ja hyödyntäjien palautteeseen",
+  "station.monitoring-and-improving.outcomes.2": "Uudelleenkäytön, luotettavuuden, datan laadun ja kustannusten signaalit omistajien saatavilla",
+  "station.monitoring-and-improving.outcomes.3": "Jatkuva parantaminen linjassa hyödyntäjien tarpeiden kanssa",
+  "station.monitoring-and-improving.how_it_works.1": "Analysoi käyttömittareita ja ota hyödyntäjien palaute mukaan kyvykkyyden kehitysversioihin.",
+  "station.monitoring-and-improving.how_it_works.2": "Luo tapa tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia.",
   "station.user-experience.outcomes.1": "Intuitiiviset ja johdonmukaiset käyttöliittymät",
   "station.user-experience.outcomes.2": "Käyttäjien palaute sisällytetty APIn suunnitteluun",
   "station.user-experience.outcomes.3": "Parempi käyttäjätyytyväisyys ja hyväksyntä",
@@ -283,7 +283,7 @@
   "station.legal-and-compliance.outcomes.2": "Oikeudellisten riskien tunnistaminen ja lieventäminen",
   "station.legal-and-compliance.outcomes.3": "Vaatimustenmukaisuustoimenpiteiden selkeä dokumentointi",
   "station.legal-and-compliance.how_it_works.1": "Toteuta toimenpiteitä, joilla varmistetaan, että rajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
-  "station.legal-and-compliance.how_it_works.2": "dokumentoida vaatimustenmukaisuustoimenpiteet ja varmistaa, että niistä tiedotetaan sidosryhmille ja kuluttajille.",
+  "station.legal-and-compliance.how_it_works.2": "Dokumentoi vaatimustenmukaisuustoimenpiteet ja varmista, että niistä tiedotetaan sidosryhmille ja hyödyntäjille.",
   "station.security-and-privacy.outcomes.1": "Käyttäjätiedot suojattu yksityisyydensuojatoimenpiteiden avulla",
   "station.security-and-privacy.outcomes.2": "Parhaat turvallisuuskäytännöt API-suunnittelussa ja -kehityksessä",
   "station.security-and-privacy.outcomes.3": "Turvallisuusstandardien ja -säännösten noudattaminen",
@@ -299,7 +299,7 @@
   "station.vendor-management.outcomes.3": "Kolmannen osapuolen riippuvuuksiin liittyvien riskien vähentäminen",
   "station.vendor-management.how_it_works.1": "Määrittele kriteerit toimittajien rajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
   "station.vendor-management.how_it_works.2": "Seuraa toimittajien suorituskykyä ja palvelutasosopimusten (SLA) ja organisaation standardien noudattamista.",
-  "station.contract-design.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja vastuut hahmoteltuina",
+  "station.contract-design.outcomes.1": "API-toimittajien ja hyödyntäjien odotukset ja vastuut kuvattuina",
   "station.contract-design.outcomes.2": "Käyttöohjeet ja parhaat käytännöt dokumentoitu",
   "station.contract-design.outcomes.3": "APIn käyttöä koskevien väärinkäsitysten ja riitojen väheneminen.",
   "station.contract-design.how_it_works.1": "Käytä standardoituja formaatteja (esim. OpenAPI, AsyncAPI) luodaksesi koneellisesti luettavia API-sopimuksia, joita on helppo jakaa ja validoida.",
@@ -324,7 +324,7 @@
   "station.release-management.outcomes.3": "API-muutoksiin liittyvien riskien vähentäminen",
   "station.release-management.how_it_works.1": "Ota käyttöön käyttöönottostrategioita (esim. sinivihreät käyttöönotot, canary releaset) API-julkaisuihin liittyvien riskien minimoimiseksi.",
   "station.release-management.how_it_works.2": "Ota käyttöön palautusmenettelyt, jotta muutokset voidaan palauttaa nopeasti, jos API-julkaisujen aikana ilmenee ongelmia.",
-  "station.service-agreements.outcomes.1": "API-toimittajien ja kuluttajien odotukset ja palvelutasot hahmoteltuina",
+  "station.service-agreements.outcomes.1": "API-toimittajien ja hyödyntäjien odotukset ja palvelutasot kuvattuina",
   "station.service-agreements.outcomes.2": "Dokumentoidut vastuualueet ja tukiprosessit",
   "station.service-agreements.outcomes.3": "Parempi viestintä ja yhteistyö API-tiimien välillä",
   "station.service-agreements.how_it_works.1": "Luo koneellisesti luettavia palvelusopimuksia, joita on helppo jakaa ja validoida, käyttämällä standardoituja muotoja.",
@@ -333,10 +333,10 @@
   "station.api-consumer-adoption.outcomes.2": "APIn hyödyntäjät saavat tietoa APIn ominaisuuksista ja hyödyistä",
   "station.api-consumer-adoption.outcomes.3": "Parempi API-hyödyntäjätyytyväisyys ja -uskollisuus",
   "station.api-consumer-adoption.how_it_works.1": "Luo opetusmateriaalia (esim. opetusohjelmia, dokumentaatiota), jossa selitetään APIn ominaisuuksia, hyötyjä ja käyttötapoja.",
-  "station.api-consumer-adoption.how_it_works.2": "Kytkeydy API-käyttäjiin palautekierrosten, tukikanavien ja yhteisöfoorumien kautta ymmärtämään heidän tarpeitaan ja parantamaan APIn käyttöönottoa.",
+  "station.api-consumer-adoption.how_it_works.2": "Ole vuorovaikutuksessa API-hyödyntäjien kanssa palautekierrosten, tukikanavien ja yhteisöfoorumien kautta, jotta heidän tarpeensa ymmärretään ja APIn käyttöönottoa voidaan parantaa.",
   "station.api-promotion.outcomes.1": "APIn näkyvyyden ja tietoisuuden lisääminen",
   "station.api-promotion.outcomes.2": "Korkeampi APIn käyttö- ja hyväksymisaste",
-  "station.api-promotion.outcomes.3": "Parempi API-kuluttajien sitoutuminen ja tyytyväisyys",
+  "station.api-promotion.outcomes.3": "Parempi API-hyödyntäjien sitoutuminen ja tyytyväisyys",
   "station.api-promotion.how_it_works.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan rajapintojen arvoa ja hyötyjä.",
   "station.api-promotion.how_it_works.2": "Osallistu API-yhteisöihin ja -foorumeihin API-päivitysten jakamiseksi, palautteen keräämiseksi ja APIn käytön edistämiseksi.",
   "station.partner-integration.outcomes.1": "Parannetut API-ominaisuudet kumppani-APIen avulla",
@@ -375,22 +375,22 @@
   "station.budget-and-resource-management.how_it_works.1": "Laaditaan kriteerit budjettimäärärahojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden mukaisuuden perusteella.",
   "station.budget-and-resource-management.how_it_works.2": "Seuraa budjettia ja resurssien käyttöä varmistaaksesi tehokkaat investoinnit ja resurssien jakamisen API-aloitteisiin.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
-  "cycle.api-productization-cycle.station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, käyttäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
-  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, ei tuotteina. Tulos? Hämmentyneitä kuluttajia, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, hyödyntäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, eivät tuotteina. Tulos? Hämmentyneitä hyödyntäjiä, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
   "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Tarjotaan ohjeita ja malleja API-liiketoimintamallien, arvolupausten ja etenemissuunnitelmien luomista varten.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Suoraviivainen API-arvolupaus ja yleisö",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Tutki asiakkaan tai yhteistyökumppanin ongelmaa, jonka oletat voivasi ratkaista APIen avulla. Kartoita sidosryhmät, niiden matkat ja tulokset Customer Journey canvasin avulla.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Yhteinen kieli tuotteen, suunnittelun ja tekniikan välillä",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "vankka esitys tai peruste rahoituksen/hyväksynnän saamiseksi.",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Määrittele keskeiset entiteetit, niiden ominaisuudet ja suhteet, jotta voidaan luoda yhteinen käsitteellinen ymmärrys eri matkojen ja lopulta APIen välille.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tallentaaksesi tuetut liiketoimintatehtävät sekä API-käyttäjien ongelmat, hyödyt ja ominaisuudet, jotka muovaavat uusia tai uudelleenkäytettäviä API-rajapintoja.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Määrittele arvo - käyttäjille ja liiketoiminnalle - API-liiketoimintamallin avulla, jotta API-strategiastasi tulee visuaalinen, jaettavissa oleva ja helposti validoitava API-asiakkaiden kanssa seuraavalla asemalla.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia käyttäjiä varten.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Käytä API Value Proposition Canvas -pohjaa tuettujen liiketoimintatehtävien sekä API-hyödyntäjien ongelmien, hyötyjen ja ominaisuuksien kuvaamiseen. Nämä ohjaavat uusien tai uudelleenkäytettävien API-rajapintojen muotoilua.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Määrittele arvo API-hyödyntäjille ja liiketoiminnalle API Business Model Canvas -pohjan avulla, jotta API-strategiasta tulee visuaalinen, jaettava ja helposti validoitava seuraavalla asemalla.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API-hyödyntäjäkokemus - Suunnittele APIn todellisia hyödyntäjiä varten",
   "cycle.api-productization-cycle.station.api-consumer-experience.description": "Varmistetaan, että API on löydettävissä, ymmärrettävissä ja käyttökelpoinen ennen käyttöönottoa ja sen jälkeen.",
   "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Hyvät aPIt eivät ainoastaan toimi - ne tuntuvat intuitiivisilta. Riippumatta siitä, onko hyödyntäjä sisäinen kehittäjä, ulkoinen kumppani vai tekoälyagentti, heidän kokemuksensa ratkaisee hyväksynnän. Ilman selkeää kokemussuunnitelmaa",
   "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Tarkastele olemassa olevaa API Value Proposition Canvasta API-hyödyntäjän näkökulmasta. Säilytä tuetut liiketoimintatehtävät vakaina ja rikasta tuskaa lievittäviä ja hyötyjä mahdollistavia ominaisuuksia API-hyödyntäjien näkökulmalla, jotta ne voivat ohjata myöhempiä suunnittelupäätöksiä.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-käyttäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-käyttäjälle.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Käytä Customer Journey Canvas -pohjaa API-hyödyntäjän matkan kuvaamiseen löytämisestä ja arvioinnista käyttöönottoon, integrointiin, vianmääritykseen ja jatkuvaan käyttöön.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Käytä tuloksena saatua polkua parantaaksesi käyttöönottoa, dokumentaatiota, tukea ja palautesilmukoita API-hyödyntäjille.",
   "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Tarjotaan ohjeita, työkaluja ja palautemekanismeja sisäisten ja ulkoisten kehittäjien ja kumppaneiden kokemusten ymmärtämiseksi, analysoimiseksi ja parantamiseksi.",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Tunnista ja priorisoi API-asiakkaat",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Määrittele API-kokemuksen matka",
@@ -404,7 +404,7 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Business Impact Canvas auttaa tunnistamaan ja lieventämään APIn saatavuuteen, tietoturvaan ja toiminnallisuuteen liittyviä riskejä ja tukemaan tietoon perustuvia arkkitehtuuripäätöksiä.",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Johdonmukaisen hallinnon toteuttaminen ilman raskasta ylhäältä alaspäin suuntautuvaa valvontaa",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Suunnittelu sisäistä uudelleenkäyttöä ja ulkoista skaalautuvuutta varten",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja kuluttajien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Kartoita API-palveluntarjoajien ja hyödyntäjien sääntely-, vaatimustenmukaisuus- ja verkkoasiointipaikat käytettävyyden ja vaatimustenmukaisuuden varmistamiseksi.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Capacity Canvas -ohjelmassa sovitetaan yhteen liiketoimintatapahtumien mallit, tulevat kulutustrendit ja tekniset ratkaisut, jotta voidaan varmistaa APIn skaalautuvuus ja suorituskyky. Se tarjoaa kriittisen panoksen skaalautumispäätöksiä ja infrastruktuurin suunnittelua varten.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
   "cycle.api-productization-cycle.station.api-design.title": "API-design - Suunnittele arvoa tuottavia rajapintoja",
@@ -453,12 +453,12 @@
   "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Julkaiseminen on muutakin kuin käyttöönottoa - kyse on löydettävyydestä, saatavuudesta ja tuesta. Jos rajapintoja ei julkaista oikein, niitä ei käytetä, käytetä uudelleen tai suojata tehokkaasti.",
   "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Mahdollistetaan APIen julkaiseminen asiaankuuluvassa ympäristössä ja selkeät rekisteröinti- ja käyttöoikeusmekanismit (esim. API-avaimet, OAuth, tilaussuunnitelmat) API-hyödyntäjäsegmenttien sekä turvallisuus- ja vaatimustenmukaisuusvaatimusten mukaan.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIt julkaistaan oikeassa ympäristössä (yksityinen, kumppani, julkinen).",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille rajapinnan käyttäjille.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Julkaise rajapinnat asianmukaisiin yhdyskäytäviin ja ympäristöihin, jotta ne ovat uudelleenkäytettävissä useille API-hyödyntäjille.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Selkeät API-käyttöönotto- ja rekisteröintiprosessit",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Dokumentaatio, turvallisuusmallit ja -käytännöt saatavilla",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "APIt valmiina skaalautumiseen ja hallintaan",
   "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaa, mukaan lukien sisäänkirjautumisprosessit ja rekisteröinti.",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Varmistetaan, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja kuluttajien saatavilla.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Varmista, että turvamallit, yhdyskäytävän kokoonpano ja oikeudelliset ehdot ovat selkeitä ja hyödyntäjien saatavilla.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Seuranta ja parantaminen - API-arvoa varten",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Käytä mittareita ja palautetta API-suorituskyvyn seuraamiseen ja jatkuvan parantamisen edistämiseen.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API-kehitys ei lopu käynnistykseen. Ilman seurantaa tiimit eivät voi parantaa käyttöönottoa, suorituskykyä tai ROI",
@@ -467,7 +467,7 @@
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Kehittäjien palautekierrokset käytössä",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Jatkuvasti tunnistetut ja käsitellyt ongelmat",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "APIn iterointi käyttäjien tarpeiden mukaisesti",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "APIn iterointi hyödyntäjien tarpeiden mukaisesti",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analysoi APIn käyttömittareita ja ota hyödyntäjien palaute huomioon API-iteraatioissa.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia."
 }
diff --git a/src/data/method/fr/labels.criteria.json b/src/data/method/fr/labels.criteria.json
index be8b511..1270c1d 100644
--- a/src/data/method/fr/labels.criteria.json
+++ b/src/data/method/fr/labels.criteria.json
@@ -1,25 +1,25 @@
 {
   "exit_criteria": "Critères de sortie",
   "entry_criteria": "Critères d'entrée",
-  "criterion.metrics-feedback-available": "Des signaux de marché pertinents, des retours d'expérience ou des informations opérationnelles sont disponibles pour guider cette opportunité d'API.",
-  "criterion.business-goals-defined": "Les objectifs commerciaux sont définis.",
-  "criterion.market-research-done": "Une étude de marché identifie les opportunités en matière d'API.",
-  "criterion.stakeholder-approval": "Les parties prenantes pertinentes conviennent que cette opportunité d'API vaut la peine d'être explorée et priorisée.",
-  "criterion.api-opportunity-documented": "Les opportunités individuelles en matière d'API sont identifiées et documentées.",
-  "criterion.api-reusability": "L'API répond à un besoin commercial clair et est réutilisable par plusieurs consommateurs d'API.",
-  "criterion.hide-backend-discrepancies": "L'API est destinée à protéger les consommateurs de la complexité et des incohérences du backend.",
-  "criterion.value-prop-validated": "La proposition de valeur de l'API a été examinée et validée avec les parties prenantes commerciales et de consommateurs pertinentes.",
-  "criterion.consumer-segments-identified": "Les segments d'utilisateurs de l'API (internes et externes) sont identifiés.",
-  "criterion.api-roadmap-defined": "Des feuilles de route de haut niveau pour le développement de l'API sont établies.",
-  "criterion.architecture-patterns-validated": "Les modèles d'architecture et de plateforme API choisis ont été validés avec les parties prenantes d'architecture, de sécurité et de plateforme pertinentes.",
-  "criterion.design-reflects-business-value": "La conception de l'API et ses capacités exposées reflètent clairement la valeur commerciale et les besoins des utilisateurs.",
-  "criterion.api-consistency": "La conception de l'API suit nos conventions partagées pour le produit API et la conception.",
-  "criterion.api-contract-tested": "Le contrat d'API est testé et répond aux exigences fonctionnelles et non fonctionnelles.",
-  "criterion.api-description-available": "L'API et ses capacités exposées sont décrites de manière suffisante pour être examinées, auditées et intégrées.",
-  "criterion.audit-passed": "L'API passe avec succès les contrôles de conformité, de sécurité et d'audit.",
-  "criterion.audit-reports-shared": "Les résultats de l'audit et les décisions de correction sont partagés avec les parties prenantes pertinentes.",
-  "criterion.api-ready-for-publishing": "L'API est prête à être déployée et exposée via les passerelles et environnements prévus.",
-  "criterion.api-documentation-ready": "La documentation API destinée aux utilisateurs est suffisamment complète pour la publication et l'intégration.",
-  "criterion.consumer-support-ready": "Les processus d'enregistrement, de support et de communication sont prêts pour les utilisateurs de l'API.",
-  "criterion.legal-compliance-clear": "Les exigences légales, de confidentialité et de conformité pour la publication sont définies et comprises."
-}
\ No newline at end of file
+  "criterion.metrics-feedback-available": "Des signaux de marché pertinents, des retours d'expérience ou des informations opérationnelles sont disponibles pour guider cette opportunité de capacité.",
+  "criterion.business-goals-defined": "Les objectifs métier sont définis.",
+  "criterion.market-research-done": "L'étude de marché identifie des opportunités de capacité.",
+  "criterion.stakeholder-approval": "Les parties prenantes concernées conviennent que cette opportunité de capacité mérite d'être explorée et priorisée.",
+  "criterion.api-opportunity-documented": "L'opportunité de capacité est identifiée et documentée.",
+  "criterion.api-reusability": "La capacité répond à un besoin métier clair et peut être réutilisée par les utilisateurs prévus.",
+  "criterion.hide-backend-discrepancies": "L'interface choisie masque de manière appropriée la complexité et les incohérences des systèmes systèmes backend pour les utilisateurs.",
+  "criterion.value-prop-validated": "La proposition de valeur de la capacité a été validée avec les parties prenantes métier et les représentants des utilisateurs.",
+  "criterion.consumer-segments-identified": "Les segments d'utilisateurs sont identifiés.",
+  "criterion.api-roadmap-defined": "Une feuille de route de haut niveau pour la mise en œuvre est définie.",
+  "criterion.architecture-patterns-validated": "L'architecture, la plateforme et le mode de mise en œuvre choisis ont été validés avec les parties prenantes concernées en architecture, sécurité et plateforme.",
+  "criterion.design-reflects-business-value": "La conception de l'interface et les capacités exposées sont clairement reliées à la valeur métier et aux besoins des utilisateurs.",
+  "criterion.api-consistency": "La conception de l'interface respecte les standards partagés de produit, de conception et de qualité.",
+  "criterion.api-contract-tested": "Le contrat d'interface a été validé et testé par rapport aux exigences fonctionnelles et non fonctionnelles.",
+  "criterion.api-description-available": "L'interface et ses capacités sont documentées de manière suffisante pour la revue, l'audit et l'onboarding.",
+  "criterion.audit-passed": "La solution réussit les contrôles de qualité, de sécurité, de conformité et de préparation.",
+  "criterion.audit-reports-shared": "Les résultats d'audit et les décisions de correction sont partagés avec les parties prenantes concernées.",
+  "criterion.api-ready-for-publishing": "La capacité est prête à être publiée via le mécanisme de mise à disposition choisi.",
+  "criterion.api-documentation-ready": "La documentation et les supports d'onboarding destinés aux utilisateurs sont prêts.",
+  "criterion.consumer-support-ready": "Les processus d'onboarding, de support et de communication sont prêts pour les utilisateurs.",
+  "criterion.legal-compliance-clear": "Les exigences juridiques, de confidentialité et de conformité liées à la publication sont définies et comprises."
+}
diff --git a/src/data/method/fr/labels.cycles.json b/src/data/method/fr/labels.cycles.json
new file mode 100644
index 0000000..ec6b41a
--- /dev/null
+++ b/src/data/method/fr/labels.cycles.json
@@ -0,0 +1,107 @@
+{
+  "cycles.title": "Vues de cycle",
+  "cycles.description": "Vues adaptées aux publics sur le méthode APIOps Cycles.",
+  "cycle.capability-productization-cycle.title": "Cycle de productisation des capacités",
+  "cycle.capability-productization-cycle.description": "Productisez des capacités numériques réutilisables avant de décider si la mise en œuvre doit prendre la forme d’API, d’événements, de fichiers, de flux, de produits de données, de services basés sur l’IA, d’intégration directe ou d’un modèle hybride.",
+  "cycle.capability-productization-cycle.purpose": "Identifier et productiser des capacités numériques réutilisables avant de choisir le mode de mise en œuvre.",
+  "cycle.api-productization-cycle.title": "Cycle de productisation des API",
+  "cycle.api-productization-cycle.description": "Parcours APIOps Cycles centré sur les API pour productiser, concevoir, livrer, publier et améliorer des produits API.",
+  "cycle.api-productization-cycle.purpose": "Parcours méthodologique centré sur les API pour les équipes qui savent déjà que le mode de mise en œuvre prévu est un produit API.",
+  "cycle.integration-productization-cycle.title": "Cycle de productisation des capacités d’intégration",
+  "cycle.integration-productization-cycle.description": "Cycle pour productiser des capacités d’intégration réutilisables avant de choisir le modèle d’intégration concret.",
+  "cycle.integration-productization-cycle.purpose": "Guider la conception de capacités d’intégration réutilisables avant de choisir entre API, événements, fichiers, flux, produits de données, intégration directe ou modèles hybrides.",
+  "cycle.station.capability-strategy": "Stratégie de capacité",
+  "cycle.station.consumer-requirements-onboarding": "Exigences utilisateurs & onboarding",
+  "cycle.station.architecture-platform-decisions": "Architecture & décisions de plateforme",
+  "cycle.station.solution-interface-design": "Conception de solution & d’interface",
+  "cycle.station.delivery-operations": "Mise à disposition & opérations",
+  "cycle.station.quality-readiness-assurance": "Assurance qualité & préparation",
+  "cycle.station.publishing-enablement": "Publication & enablement",
+  "cycle.station.monitoring-improvement": "Suivi & amélioration",
+  "cycle.station.api-product-strategy": "Stratégie produit API",
+  "cycle.station.api-consumer-experience": "Expérience utilisateur API",
+  "cycle.station.api-platform-architecture": "Architecture de plateforme API",
+  "cycle.station.api-design": "Conception d’API",
+  "cycle.station.api-delivery": "Livraison d’API",
+  "cycle.station.api-audit": "Audit API",
+  "cycle.station.api-publishing": "Publication d’API",
+  "cycle.station.monitoring-and-improving": "Suivi & amélioration",
+  "cycle.station.integration-capability-strategy": "Stratégie de capacité d’intégration",
+  "cycle.station.integration-consumer-requirements-onboarding": "Exigences des utilisateurs d’intégration & onboarding",
+  "cycle.station.integration-architecture-decision": "Décision d’architecture d’intégration",
+  "cycle.station.integration-solution-design": "Conception de solution d’intégration",
+  "cycle.station.integration-delivery-operations": "Livraison & opérations d’intégration",
+  "cycle.station.integration-readiness-assurance": "Assurance qualité des intégrations",
+  "cycle.station.capability-publishing": "Publication de capacité",
+  "cycle.station.integration-monitoring-improvement": "Suivi & amélioration des intégrations",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Décrivez le besoin métier comme une stratégie de capacité réutilisable avant de choisir le mode de mise en œuvre.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capturez les exigences des utilisateurs, les besoins d’onboarding, les contraintes, les attentes de service et les responsabilités des fournisseurs.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilisez les exigences et contraintes pour choisir l’architecture et les capacités de plateforme.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Concevez le mode de mise en œuvre choisi et le contrat d’interface.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Livrez et exploitez le mode de mise en œuvre choisi.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Assurez la qualité, la gouvernance et la préparation avant publication.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publiez les informations de capacité afin que les utilisateurs puissent la découvrir, demander l’accès, s’onboarder et obtenir du support.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de la capacité, les résultats utilisateurs, la fiabilité, la réutilisation et les opportunités d’amélioration.",
+  "cycle.owner.business-owner": "Responsable métier",
+  "cycle.owner.domain-expert": "Expert domaine",
+  "cycle.owner.capability-owner": "Responsable de capacité",
+  "cycle.owner.consumer-representative": "Représentant des utilisateurs",
+  "cycle.owner.enterprise-architect": "Architecte d’entreprise",
+  "cycle.owner.platform-owner": "Responsable plateforme",
+  "cycle.owner.api-product-owner": "Product owner API",
+  "cycle.owner.api-platform-owner": "Responsable plateforme API",
+  "cycle.owner.integration-architect": "Architecte d’intégration",
+  "cycle.owner.solution-architect": "Architecte solution",
+  "cycle.template.intent-fit.title": "Intention & adéquation",
+  "cycle.template.intent-fit.description": "Capturez le résultat métier, les utilisateurs, les fournisseurs, le périmètre, les contraintes et le statut de décision.",
+  "cycle.template.requirements.title": "Exigences",
+  "cycle.template.requirements.description": "Collectez les contributions d’experts à l’aide des questions recommandées. Traitez les réponses comme des entrées pour les décisions de conception, et non comme des décisions finales.",
+  "cycle.template.architecture-decision.title": "Décision d’architecture",
+  "cycle.template.architecture-decision.description": "Comparez les choix d’architecture viables par rapport aux exigences, preuves, risques et questions ouvertes.",
+  "cycle.template.api-architecture-decision.title": "Décision d’architecture API",
+  "cycle.template.api-architecture-decision.description": "Documentez les décisions relatives à l’architecture API, à la plateforme, à la sécurité, au cycle de vie et à la publication.",
+  "cycle.template.integration-pattern-decision.title": "Décision de modèle d’intégration",
+  "cycle.template.integration-pattern-decision.description": "Comparez API, événements, fichiers, flux, produits de données, intégration directe et options hybrides par rapport aux exigences.",
+  "cycle.template.human-validation.title": "Validation humaine",
+  "cycle.template.human-validation.description": "Documentez qui valide les résultats assistés par l’IA et quelles décisions nécessitent une responsabilité humaine.",
+  "cycle.template.adr.title": "Architecture Decision Record",
+  "cycle.template.adr.description": "Documentez la décision choisie, la justification, les alternatives, les conséquences, les preuves et les actions de suivi.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Cadrez l’API comme un produit avec une proposition de valeur claire, des utilisateurs, un modèle économique, une responsabilité et une intention de cycle de vie.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Définissez les segments d’utilisateurs API, les parcours d’onboarding, les attentes et les exigences d’expérience avant de verrouiller les décisions de conception.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choisissez et validez la plateforme API, l’architecture, la gouvernance et les contraintes opérationnelles nécessaires au produit.",
+  "cycle.api-productization-cycle.station.api-design.description": "Concevez le contrat d’interface API, le modèle d’interaction, les schémas, les politiques et les détails d’utilisabilité avant l’implémentation.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Implémentez, testez, sécurisez, automatisez et exploitez le produit API via le pipeline de livraison.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validez la qualité, la conformité, la préparation, les preuves et les critères de publication de l’API avant publication.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publiez le produit API afin que les utilisateurs puissent le découvrir, l’évaluer, demander l’accès, s’onboarder et obtenir du support.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de l’API, l’adoption, les résultats utilisateurs, la fiabilité et les opportunités d’amélioration après publication.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Cadrez la capacité d’intégration réutilisable, le besoin métier, la responsabilité et la réutilisation attendue avant de choisir un modèle.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capturez les utilisateurs d’intégration, les responsabilités des fournisseurs, les besoins d’onboarding, les attentes de service et les contraintes opérationnelles.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Décidez de l’architecture d’intégration, des capacités de plateforme, des contraintes et du modèle de gouvernance de la capacité.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Concevez la solution d’intégration, les contrats, les payloads, les événements, les API, les fichiers ou les modèles d’interaction choisis pour la capacité.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Construisez, testez, automatisez, déployez et exploitez la capacité d’intégration selon son modèle de livraison choisi.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Assurez la préparation, la gouvernance, la qualité, la sécurité, la conformité et les preuves opérationnelles de l’intégration avant publication.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publiez la capacité d’intégration afin que les équipes puissent la découvrir, la demander, la réutiliser, s’onboarder et obtenir du support.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Suivez la fiabilité, la réutilisation, les incidents, la performance, les résultats utilisateurs et les besoins d’amélioration de l’intégration.",
+  "cycle.automation-cycle.title": "Cycle d’automatisation",
+  "cycle.automation-cycle.description": "Cycle pour identifier, concevoir, livrer, enable et améliorer des opportunités d’automatisation.",
+  "cycle.automation-cycle.purpose": "Productiser les opportunités d’automatisation en workflows gouvernés avec des utilisateurs, plateformes, contrôles, chemins de livraison, enablement et suivi clairement définis.",
+  "cycle.audience.automation-owners": "Responsables automatisation",
+  "cycle.audience.process-owners": "Responsables de processus",
+  "cycle.audience.automation-teams": "Équipes d’automatisation",
+  "cycle.station.automation-opportunity-strategy": "Stratégie d’opportunité d’automatisation",
+  "cycle.station.process-user-requirements": "Exigences processus/utilisateur",
+  "cycle.station.automation-platform-decision": "Décision de plateforme d’automatisation",
+  "cycle.station.automation-workflow-design": "Conception de workflow d’automatisation",
+  "cycle.station.automation-delivery": "Livraison de l’automatisation",
+  "cycle.station.automation-readiness-review": "Revue de préparation de l’automatisation",
+  "cycle.station.automation-enablement": "Enablement de l’automatisation",
+  "cycle.station.automation-monitoring-improvement": "Suivi & amélioration de l’automatisation",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Identifiez et priorisez les opportunités d’automatisation selon la valeur, la faisabilité, le risque, la responsabilité et l’impact attendu sur le processus.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Capturez les utilisateurs du processus, les rôles, les transferts, les exceptions, les contraintes et les attentes de service avant de concevoir l’automatisation.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Choisissez la plateforme d’automatisation, le runtime, le modèle d’intégration, les contrôles de gouvernance et les contraintes opérationnelles.",
+  "cycle.automation-cycle.station.api-design.description": "Concevez le workflow d’automatisation, les déclencheurs, les points de décision, les intégrations, le traitement des données et les chemins d’exception.",
+  "cycle.automation-cycle.station.api-delivery.description": "Construisez, testez, déployez, documentez et exploitez l’automatisation avec une responsabilité et des chemins de rollback clairs.",
+  "cycle.automation-cycle.station.api-audit.description": "Revoyez la préparation, la qualité, les risques, la conformité, la supervision humaine, les preuves et les critères de publication de l’automatisation.",
+  "cycle.automation-cycle.station.api-publishing.description": "Enablez les utilisateurs et opérateurs avec découverte, onboarding, instructions d’exploitation, chemins de support et communication de changement.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Suivez la performance de l’automatisation, les exceptions, la fiabilité, les résultats utilisateurs, l’impact opérationnel et les opportunités d’amélioration."
+}
diff --git a/src/data/method/fr/labels.lines.json b/src/data/method/fr/labels.lines.json
index 892acc3..03ce0e7 100644
--- a/src/data/method/fr/labels.lines.json
+++ b/src/data/method/fr/labels.lines.json
@@ -1,16 +1,16 @@
 {
   "lines.title": "Lignes de métro",
-  "lines.description": "Une collection de lignes d'API qui guident le développement et la gestion des API.",
-  "line.business-opportunities-line.title": "Ligne sur les opportunités d'affaires",
-  "line.business-opportunities-line.description": "L'accent est mis sur l'identification et l'exploitation des opportunités commerciales grâce aux API.",
+  "lines.description": "Lignes du métro APIOps Cycles qui guident la conception, la mise en œuvre et l'évolution des capacités, des API et des intégrations.",
+  "line.business-opportunities-line.title": "Ligne des opportunités métier",
+  "line.business-opportunities-line.description": "Se concentre sur l'identification, l'évaluation et la productisation des opportunités métier sous forme de capacités réutilisables.",
   "line.platform-architecture-line.title": "Ligne d'architecture de la plateforme",
-  "line.platform-architecture-line.description": "Couvre les aspects architecturaux des plateformes API.",
+  "line.platform-architecture-line.description": "Couvre les décisions d'architecture relatives aux plateformes, aux intégrations et aux interfaces.",
   "line.api-design-line.title": "Ligne de conception de l'API",
-  "line.api-design-line.description": "Se concentre sur les principes et les pratiques de conception des API.",
+  "line.api-design-line.description": "Se concentre sur les principes et les bonnes pratiques de conception des interfaces et des solutions d'intégration.",
   "line.delivery-line.title": "Ligne de livraison",
-  "line.delivery-line.description": "Couvre les processus et pratiques de livraison des API.",
-  "line.publishing-and-adoption-line.title": "Ligne d'édition et d'adoption",
-  "line.publishing-and-adoption-line.description": "Se concentre sur la publication d'API et sur leur adoption par les consommateurs.",
+  "line.delivery-line.description": "Couvre les pratiques de mise en œuvre, de test, d'automatisation et de livraison.",
+  "line.publishing-and-adoption-line.title": "Ligne Publication & Enablement",
+  "line.publishing-and-adoption-line.description": "Se concentre sur la publication des capacités, leur découvrabilité, leur onboarding et leur adoption.",
   "line.operating-model-line.title": "Ligne de modèle opérationnel",
-  "line.operating-model-line.description": "Couvre le modèle d'exploitation pour la gestion et la gouvernance des API."
-}
+  "line.operating-model-line.description": "Couvre la gouvernance, les responsabilités et le modèle opérationnel des capacités."
+}
\ No newline at end of file
diff --git a/src/data/method/fr/labels.resources.json b/src/data/method/fr/labels.resources.json
index 4ff3ab1..a280efd 100644
--- a/src/data/method/fr/labels.resources.json
+++ b/src/data/method/fr/labels.resources.json
@@ -1,167 +1,167 @@
 {
-  "resource.api-community-engagement-strategies.title": "Stratégies d'engagement de la communauté de l'API",
+  "resource.api-community-engagement-strategies.title": "Stratégies d'engagement de la communauté de l’API",
   "resource.api-community-engagement-strategies.description": "Un guide pour favoriser l'adoption des API en cultivant des communautés grâce à des contenus, des canaux d'assistance, des boucles de retour d'information et des stratégies d'engagement social.",
-  "resource.api-community-engagement-strategies.outcomes": "Meilleure compréhension des principes des stratégies d'engagement communautaire de l'API",
+  "resource.api-community-engagement-strategies.outcomes": "Meilleure compréhension des principes des stratégies d'engagement communautaire de l’API",
   "resource.api-community-engagement-strategies.steps": "Élaborer des stratégies de marketing pour promouvoir les API auprès des publics cibles, y compris les médias sociaux, les blogs et les webinaires.",
-  "resource.api-community-engagement-strategies.tips": "Personnalisez les stratégies d'engagement communautaire de l'API pour votre domaine",
-  "resource.api-compliance-best-practices.title": "Meilleures pratiques en matière de conformité de l'API",
+  "resource.api-community-engagement-strategies.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-compliance-best-practices.title": "Meilleures pratiques en matière de conformité de l’API",
   "resource.api-compliance-best-practices.description": "Veiller à ce que les API respectent la conformité légale, réglementaire et interne grâce à la documentation, aux contrôles et aux validations automatisées.",
   "resource.api-compliance-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de conformité des API",
-  "resource.api-compliance-best-practices.steps": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux consommateurs.",
-  "resource.api-compliance-best-practices.tips": "Personnalisez les meilleures pratiques de conformité de l'API pour votre domaine",
-  "resource.api-development-best-practices.title": "Meilleures pratiques en matière de développement d'API",
-  "resource.api-development-best-practices.description": "Guide de mise en œuvre visant à transformer un contrat API validé en une base de code API cohérente et facile à maintenir, à l'aide de bibliothèques standard, de modèles réutilisables et de workflows de développement harmonisés.",
-  "resource.api-development-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de développement d'API",
-  "resource.api-development-best-practices.steps": "Appliquez ces bonnes pratiques au contrat API validé et au plan de mise en œuvre avant de commencer le codage.",
+  "resource.api-compliance-best-practices.steps": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux utilisateurs.",
+  "resource.api-compliance-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-development-best-practices.title": "Meilleures pratiques en matière de développement d’API",
+  "resource.api-development-best-practices.description": "Guide de mise en œuvre visant à transformer un contrat d’interface API validé en une base de code API cohérente et maintenable, à l’aide de bibliothèques standard, de patterns réutilisables et de workflows de développement harmonisés.",
+  "resource.api-development-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de développement d’API",
+  "resource.api-development-best-practices.steps": "Appliquer ces bonnes pratiques au contrat d’interface API validé et au plan de mise en œuvre avant de commencer le codage.",
   "resource.api-development-best-practices.tips": "Utilisez cette ressource comme guide de mise en œuvre et outil d'évaluation plutôt que comme un artefact autonome obligatoire",
-  "resource.api-metrics-and-analytics.title": "Mesures et analyses de l'API",
-  "resource.api-metrics-and-analytics.description": "Une ressource pour définir, collecter et analyser les performances de l'API et les données d'utilisation afin d'aligner les KPI techniques sur les résultats de l'entreprise.",
+  "resource.api-metrics-and-analytics.title": "Mesures et analyses de l’API",
+  "resource.api-metrics-and-analytics.description": "Une ressource pour définir, collecter et analyser les performances de l’API et les données d’utilisation afin d’aligner les KPI techniques sur les résultats métier.",
   "resource.api-metrics-and-analytics.outcomes": "Meilleure compréhension des métriques API et des principes d'analyse",
-  "resource.api-metrics-and-analytics.steps": "Identifier les indicateurs clés de performance (KPI) pour mesurer la réussite de l'API par rapport aux objectifs de l'entreprise.",
-  "resource.api-metrics-and-analytics.tips": "Personnalisez les mesures et les analyses de l'API pour votre domaine",
-  "resource.api-onboarding-best-practices.title": "Meilleures pratiques en matière d'intégration de l'API",
-  "resource.api-onboarding-best-practices.description": "Meilleures pratiques pour rationaliser les parcours d'accueil des consommateurs d'API avec une inscription étape par étape, une découverte et des conseils pour le premier appel.",
-  "resource.api-onboarding-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d'intégration de l'API",
-  "resource.api-onboarding-best-practices.steps": "Définir le parcours du consommateur d'API, de la découverte au dépannage, en identifiant les points de contact clés et les points douloureux.",
-  "resource.api-onboarding-best-practices.tips": "Personnalisez les meilleures pratiques d'intégration de l'API pour votre domaine",
-  "resource.api-portfolio-management-guidelines.title": "Lignes directrices pour la gestion du portefeuille de l'API",
-  "resource.api-portfolio-management-guidelines.description": "Un guide pour gérer stratégiquement la suite d'API d'une organisation - en donnant la priorité aux API, en allouant des ressources et en contrôlant les performances tout au long du cycle de vie.",
-  "resource.api-portfolio-management-guidelines.outcomes": "Meilleure compréhension des principes directeurs de la gestion du portefeuille de l'API",
-  "resource.api-portfolio-management-guidelines.steps": "Définir des pratiques de gestion de portefeuille qui décrivent les processus de gestion du portefeuille d'API, y compris l'établissement de priorités, le suivi et l'optimisation.",
-  "resource.api-portfolio-management-guidelines.tips": "Personnaliser les lignes directrices de la gestion du portefeuille d'API pour votre domaine",
+  "resource.api-metrics-and-analytics.steps": "Identifier les indicateurs clés de performance (KPI) pour mesurer la réussite de l’API par rapport aux objectifs métier.",
+  "resource.api-metrics-and-analytics.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-onboarding-best-practices.title": "Meilleures pratiques en matière d’intégration de l’API",
+  "resource.api-onboarding-best-practices.description": "Bonnes pratiques pour rationaliser les parcours d’onboarding des utilisateurs API avec inscription étape par étape, découverte et guidage du premier appel.",
+  "resource.api-onboarding-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d’intégration de l’API",
+  "resource.api-onboarding-best-practices.steps": "Définir le parcours de l’utilisateur API, de la découverte au dépannage, en identifiant les points de contact clés et les irritants.",
+  "resource.api-onboarding-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-portfolio-management-guidelines.title": "Lignes directrices pour la gestion du portefeuille de l’API",
+  "resource.api-portfolio-management-guidelines.description": "Un guide pour gérer stratégiquement la suite d’API d'une organisation - en donnant la priorité aux API, en allouant des ressources et en contrôlant les performances tout au long du cycle de vie.",
+  "resource.api-portfolio-management-guidelines.outcomes": "Meilleure compréhension des principes directeurs de la gestion du portefeuille de l’API",
+  "resource.api-portfolio-management-guidelines.steps": "Définir des pratiques de gestion de portefeuille qui décrivent les processus de gestion du portefeuille d’API, y compris l'établissement de priorités, le suivi et l'optimisation.",
+  "resource.api-portfolio-management-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.api-security-best-practices.title": "Meilleures pratiques en matière de sécurité des API",
   "resource.api-security-best-practices.description": "Un ensemble de contrôles exploitables pour sécuriser les API, y compris l'authentification, l'autorisation, le cryptage, la limitation du débit et les contrôles de conformité au niveau du pipeline.",
   "resource.api-security-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de sécurité des API",
   "resource.api-security-best-practices.steps": "S'assurer que les API répondent aux exigences de sécurité et de conformité grâce à des contrôles et des audits automatisés.",
-  "resource.api-security-best-practices.tips": "Personnalisez les meilleures pratiques de sécurité de l'API pour votre domaine",
-  "resource.api-team-structure-guidelines.title": "Lignes directrices relatives à la structure des équipes de l'API",
+  "resource.api-security-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-team-structure-guidelines.title": "Lignes directrices relatives à la structure des équipes de l’API",
   "resource.api-team-structure-guidelines.description": "Orientation organisationnelle pour définir les rôles et les responsabilités au sein des équipes API afin de garantir la clarté, la collaboration et la responsabilité.",
   "resource.api-team-structure-guidelines.outcomes": "Meilleure compréhension des principes directeurs de la structure de l'équipe API",
   "resource.api-team-structure-guidelines.steps": "Définir les structures et les rôles des équipes API, y compris les propriétaires de produits API, les développeurs, les architectes et les opérations.",
-  "resource.api-team-structure-guidelines.tips": "Personnalisez les lignes directrices de la structure de l'équipe API pour votre domaine",
-  "resource.api-testing-best-practices.title": "Meilleures pratiques de test de l'API",
-  "resource.api-testing-best-practices.description": "Lignes directrices pour la mise en œuvre de tests fonctionnels, de performance et de sécurité automatisés tout au long du cycle de vie de l'API.",
-  "resource.api-testing-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de tests d'API",
+  "resource.api-team-structure-guidelines.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-testing-best-practices.title": "Meilleures pratiques de test de l’API",
+  "resource.api-testing-best-practices.description": "Lignes directrices pour la mise en œuvre de tests fonctionnels, de performance et de sécurité automatisés tout au long du cycle de vie de l’API.",
+  "resource.api-testing-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de tests d’API",
   "resource.api-testing-best-practices.steps": "Tester les fonctionnalités, la sécurité et les performances des API à l'aide d'outils de test automatisés.",
-  "resource.api-testing-best-practices.tips": "Personnalisez les meilleures pratiques de test de l'API pour votre domaine",
-  "resource.api-training-programs.title": "Programmes de formation de l'API",
+  "resource.api-testing-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-training-programs.title": "Programmes de formation de l’API",
   "resource.api-training-programs.description": "Une feuille de route pour l'amélioration des compétences des équipes avec des parcours d'apprentissage structurés en matière de conception, de gouvernance, de performance et de sécurité des API.",
-  "resource.api-training-programs.outcomes": "Meilleure compréhension des principes des programmes de formation de l'API",
-  "resource.api-training-programs.steps": "Identifier les compétences et les connaissances clés en matière d'API qui doivent être améliorées, telles que la conception, la sécurité et les performances des API.",
-  "resource.api-training-programs.tips": "Personnalisez les programmes de formation à l'API pour votre domaine",
-  "resource.api-versioning-best-practices.title": "Meilleures pratiques en matière de versionnement de l'API",
-  "resource.api-versioning-best-practices.description": "Stratégies d'introduction, de maintenance et de retrait des versions de l'API tout en préservant la compatibilité ascendante et la confiance des consommateurs.",
-  "resource.api-versioning-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de versions d'API",
+  "resource.api-training-programs.outcomes": "Meilleure compréhension des principes des programmes de formation de l’API",
+  "resource.api-training-programs.steps": "Identifier les compétences et les connaissances clés en matière d’API qui doivent être améliorées, telles que la conception, la sécurité et les performances des API.",
+  "resource.api-training-programs.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-versioning-best-practices.title": "Meilleures pratiques en matière de versionnement de l’API",
+  "resource.api-versioning-best-practices.description": "Stratégies pour introduire, maintenir et retirer des versions d’API tout en préservant la rétrocompatibilité et la confiance des utilisateurs.",
+  "resource.api-versioning-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de versions d’API",
   "resource.api-versioning-best-practices.steps": "Définir des stratégies de versionnement pour les API afin de gérer les changements et d'assurer la compatibilité ascendante.",
-  "resource.api-versioning-best-practices.tips": "Personnalisez les meilleures pratiques de versionnement de l'API pour votre domaine",
+  "resource.api-versioning-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.description": "Des conseils de déploiement qui intègrent les tâches du cycle de vie de l'API - conception, test, gouvernance - dans les pipelines d'intégration et de livraison en continu.",
+  "resource.apiops-CI-CD-for-apis.description": "Conseils de mise à disposition qui intègrent les tâches du cycle de vie de l’API - conception, test, gouvernance - dans les pipelines d’intégration et de livraison en continu.",
   "resource.apiops-CI-CD-for-apis.outcomes": "Meilleure compréhension des principes CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.steps": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de déploiement, en garantissant une qualité et une traçabilité constantes.",
-  "resource.apiops-CI-CD-for-apis.tips": "Personnalisez les API CI/CD pour votre domaine",
+  "resource.apiops-CI-CD-for-apis.steps": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de mise à disposition, en garantissant une qualité et une traçabilité constantes.",
+  "resource.apiops-CI-CD-for-apis.tips": "Adaptez cette ressource à votre contexte.",
   "resource.competitor-analysis-template.title": "Modèle d'analyse des concurrents",
-  "resource.competitor-analysis-template.description": "Une feuille de travail structurée pour comparer vos offres d'API à celles de vos concurrents en identifiant les forces, les faiblesses et les différentiateurs de valeur.",
+  "resource.competitor-analysis-template.description": "Une feuille de travail structurée pour comparer vos offres d’API à celles de vos concurrents en identifiant les forces, les faiblesses et les différentiateurs de valeur.",
   "resource.competitor-analysis-template.outcomes": "Meilleure compréhension des principes du modèle d'analyse de la concurrence",
-  "resource.competitor-analysis-template.steps": "Effectuer une analyse concurrentielle afin d'identifier les principaux concurrents et leurs offres d'API.",
-  "resource.competitor-analysis-template.tips": "Personnalisez le modèle d'analyse de la concurrence pour votre domaine",
-  "resource.contract-first-design.title": "Contrat de première conception",
+  "resource.competitor-analysis-template.steps": "Effectuer une analyse concurrentielle afin d'identifier les principaux concurrents et leurs offres d’API.",
+  "resource.competitor-analysis-template.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.contract-first-design.title": "Conception contract-first",
   "resource.contract-first-design.description": "Une ligne directrice qui préconise des approches \"API-first\" utilisant des contrats formels (par exemple, OpenAPI) pour aligner les parties prenantes avant le développement.",
   "resource.contract-first-design.outcomes": "Meilleure compréhension des principes de conception du contrat d'abord",
-  "resource.contract-first-design.steps": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d'API sont validés avant leur mise en œuvre.",
-  "resource.contract-first-design.tips": "Personnalisez le Contract First Design pour votre domaine",
+  "resource.contract-first-design.steps": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d’API sont validés avant leur mise en œuvre.",
+  "resource.contract-first-design.tips": "Adaptez cette ressource à votre contexte.",
   "resource.cross-functional-collaboration-best-practices.title": "Meilleures pratiques en matière de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.description": "Pratiques visant à faciliter la communication et l'alignement entre les équipes commerciales et techniques lors de la planification ou de la fourniture d'API.",
+  "resource.cross-functional-collaboration-best-practices.description": "Pratiques visant à faciliter la communication et l’alignement entre les rôles métier et techniques lors de la planification ou de la mise à disposition d’API.",
   "resource.cross-functional-collaboration-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.steps": "Encourager la collaboration interfonctionnelle entre les équipes API, les unités opérationnelles et les parties prenantes afin d'aligner les initiatives API sur les objectifs de l'entreprise.",
-  "resource.cross-functional-collaboration-best-practices.tips": "Personnalisez les bonnes pratiques de collaboration interfonctionnelle pour votre domaine",
+  "resource.cross-functional-collaboration-best-practices.steps": "Encourager la collaboration interfonctionnelle entre les équipes API, les unités métier et les parties prenantes afin d’aligner les initiatives API sur les objectifs métier.",
+  "resource.cross-functional-collaboration-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.data-privacy-guidelines.title": "Lignes directrices sur la protection des données",
   "resource.data-privacy-guidelines.description": "Les considérations de conception pour s'assurer que les API respectent les réglementations sur la protection des données comme le GDPR grâce à l'anonymisation et aux contrôles d'accès.",
-  "resource.data-privacy-guidelines.outcomes": "Meilleure compréhension des principes des lignes directrices sur la confidentialité des données",
-  "resource.data-privacy-guidelines.steps": "Garantir la confidentialité des données des utilisateurs en mettant en œuvre des mesures de protection des données, telles que l'anonymisation et les contrôles d'accès.",
-  "resource.data-privacy-guidelines.tips": "Personnalisez les lignes directrices sur la confidentialité des données pour votre domaine",
+  "resource.data-privacy-guidelines.outcomes": "Meilleure compréhension des lignes directrices de protection des données",
+  "resource.data-privacy-guidelines.steps": "Garantir la protection des données des utilisateurs en mettant en œuvre des mesures telles que l’anonymisation et les contrôles d’accès.",
+  "resource.data-privacy-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.domain-canvas.title": "Domain Canvas",
-  "resource.domain-canvas.description": "Un outil de modélisation pour définir et communiquer les entités et les relations clés de votre domaine, en assurant la cohérence sémantique entre les API.",
+  "resource.domain-canvas.description": "Outil de modélisation pour définir les concepts, entités, relations et règles du domaine métier, afin d’assurer la cohérence sémantique entre capacités, interfaces et intégrations.",
   "resource.domain-canvas.outcomes": "Meilleure compréhension des principes du domain canvas",
   "resource.domain-canvas.steps": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.",
-  "resource.domain-canvas.tips": "Personnaliser le Domain Canvas pour votre domaine",
+  "resource.domain-canvas.tips": "Adaptez cette ressource à votre contexte.",
   "resource.ecosystem-vision-template.title": "Modèle de vision de l'écosystème",
-  "resource.ecosystem-vision-template.description": "Un outil de planification stratégique pour définir l'écosystème de l'API, y compris les partenaires cibles, les chaînes de valeur et les possibilités d'intégration.",
+  "resource.ecosystem-vision-template.description": "Un outil de planification stratégique pour définir l'écosystème de l’API, y compris les partenaires cibles, les chaînes de valeur et les possibilités d’intégration.",
   "resource.ecosystem-vision-template.outcomes": "Meilleure compréhension des principes du modèle de vision de l'écosystème",
   "resource.ecosystem-vision-template.steps": "Réaliser des études de marché pour identifier les tendances, les opportunités et les menaces dans le domaine des API.",
-  "resource.ecosystem-vision-template.tips": "Personnalisez le modèle de vision de l'écosystème pour votre domaine",
+  "resource.ecosystem-vision-template.tips": "Adaptez cette ressource à votre contexte.",
   "resource.industry-standards-and-best-practices.title": "Normes industrielles et meilleures pratiques",
-  "resource.industry-standards-and-best-practices.description": "Une ressource de référence pour aligner la conception et le fonctionnement de l'API sur des cadres et des spécifications largement reconnus dans l'industrie.",
+  "resource.industry-standards-and-best-practices.description": "Une ressource de référence pour aligner la conception et le fonctionnement de l’API sur des cadres et des spécifications largement reconnus dans l'industrie.",
   "resource.industry-standards-and-best-practices.outcomes": "Meilleure compréhension des normes du secteur et des principes des meilleures pratiques",
   "resource.industry-standards-and-best-practices.steps": "Identifier les normes et les meilleures pratiques du secteur pour s'assurer que les API sont compétitives et conformes.",
-  "resource.industry-standards-and-best-practices.tips": "Personnaliser les normes et les meilleures pratiques de l'industrie pour votre domaine",
-  "resource.partner-integration-guidelines.title": "Lignes directrices pour l'intégration des partenaires",
-  "resource.partner-integration-guidelines.description": "Listes de contrôle de l'intégration et modèles de communication pour gérer les aspects techniques et juridiques des relations avec des API tierces.",
-  "resource.partner-integration-guidelines.outcomes": "Meilleure compréhension des principes directeurs de l'intégration des partenaires",
-  "resource.partner-integration-guidelines.steps": "Établir des processus d'intégration et des lignes directrices pour la collaboration avec les partenaires, y compris l'intégration technique, le partage des données et le soutien.",
-  "resource.partner-integration-guidelines.tips": "Personnalisez les directives d'intégration des partenaires pour votre domaine",
+  "resource.industry-standards-and-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.partner-integration-guidelines.title": "Lignes directrices pour l’intégration des partenaires",
+  "resource.partner-integration-guidelines.description": "Listes de contrôle de l’intégration et modèles de communication pour gérer les aspects techniques et juridiques des relations avec des API tierces.",
+  "resource.partner-integration-guidelines.outcomes": "Meilleure compréhension des principes directeurs de l’intégration des partenaires",
+  "resource.partner-integration-guidelines.steps": "Établir des processus d’intégration et des lignes directrices pour la collaboration avec les partenaires, y compris l’intégration technique, le partage des données et le soutien.",
+  "resource.partner-integration-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.role-communication-best-practices.title": "Meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.description": "Outils permettant de définir et de documenter les responsabilités de chacun dans le cadre des initiatives API, afin de garantir la clarté des transferts et des responsabilités.",
+  "resource.role-communication-best-practices.description": "Outils permettant de définir et de clarifier les responsabilités dans les initiatives API, afin de garantir des passages de relais et des responsabilités explicites.",
   "resource.role-communication-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.steps": "Établir des responsabilités claires pour chaque rôle, notamment en ce qui concerne la conception, le développement, les tests et les opérations de l'API.",
-  "resource.role-communication-best-practices.tips": "Personnalisez les meilleures pratiques de communication de rôle pour votre domaine",
+  "resource.role-communication-best-practices.steps": "Établir des responsabilités claires pour chaque rôle, notamment en ce qui concerne la conception, le développement, les tests et les opérations de l’API.",
+  "resource.role-communication-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.scalable-infrastructure-best-practices.title": "Meilleures pratiques en matière d'infrastructure évolutive",
   "resource.scalable-infrastructure-best-practices.description": "Des conseils architecturaux pour s'assurer que les API sont déployées sur une infrastructure capable de gérer avec élasticité les pics d'utilisation et la croissance.",
   "resource.scalable-infrastructure-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d'infrastructure évolutive",
-  "resource.scalable-infrastructure-best-practices.steps": "Concevoir une infrastructure d'API évolutive et résiliente, en utilisant des modèles et des technologies \"cloud-native\".",
-  "resource.scalable-infrastructure-best-practices.tips": "Personnalisez les meilleures pratiques de l'infrastructure évolutive pour votre domaine",
+  "resource.scalable-infrastructure-best-practices.steps": "Concevoir une infrastructure d’API évolutive et résiliente, en utilisant des modèles et des technologies \"cloud-native\".",
+  "resource.scalable-infrastructure-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.service-agreement-template.title": "Modèle de contrat de service",
-  "resource.service-agreement-template.description": "Un format d'accord personnalisable qui définit les attentes, les accords de niveau de service, les responsabilités et les conditions d'accès pour la consommation d'API.",
+  "resource.service-agreement-template.description": "Un format d’accord personnalisable qui définit les attentes, les accords de niveau de service, les responsabilités et les conditions d’accès pour l’utilisation d’API.",
   "resource.service-agreement-template.outcomes": "Meilleure compréhension des principes du modèle d'accord de service",
   "resource.service-agreement-template.steps": "Définir des accords de service qui décrivent les attentes, les niveaux de service et les responsabilités pour chaque API.",
-  "resource.service-agreement-template.tips": "Personnalisez le modèle de contrat de service pour votre domaine",
+  "resource.service-agreement-template.tips": "Adaptez cette ressource à votre contexte.",
   "resource.stakeholder-engagement-best-practices.title": "Meilleures pratiques en matière d'engagement des parties prenantes",
-  "resource.stakeholder-engagement-best-practices.description": "Tactiques d'engagement pour aligner les parties prenantes internes et externes sur les objectifs, la valeur et la gouvernance partagés de l'API.",
+  "resource.stakeholder-engagement-best-practices.description": "Tactiques d'engagement pour aligner les parties prenantes internes et externes sur les objectifs, la valeur et la gouvernance partagés de l’API.",
   "resource.stakeholder-engagement-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d'engagement des parties prenantes",
   "resource.stakeholder-engagement-best-practices.steps": "Engager les parties prenantes pour assurer l'alignement et le soutien des initiatives API.",
-  "resource.stakeholder-engagement-best-practices.tips": "Personnalisez les meilleures pratiques d'engagement des parties prenantes pour votre domaine",
+  "resource.stakeholder-engagement-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.test-automation-frameworks.title": "Cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.description": "Outils et modèles recommandés pour automatiser les tests de contrat, de régression et d'intégration des API dans les différents environnements.",
+  "resource.test-automation-frameworks.description": "Outils et modèles recommandés pour automatiser les tests de contrat, de régression et d’intégration des API dans les différents environnements.",
   "resource.test-automation-frameworks.outcomes": "Meilleure compréhension des principes des cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.steps": "Mettre en œuvre des cadres d'automatisation des tests qui prennent en charge les tests de contrat, les tests d'intégration et les tests de bout en bout.",
-  "resource.test-automation-frameworks.tips": "Personnaliser les cadres d'automatisation des tests pour votre domaine",
+  "resource.test-automation-frameworks.steps": "Mettre en œuvre des cadres d'automatisation des tests qui prennent en charge les tests de contrat, les tests d’intégration et les tests de bout en bout.",
+  "resource.test-automation-frameworks.tips": "Adaptez cette ressource à votre contexte.",
   "resource.vendor-management-best-practices.title": "Meilleures pratiques de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.description": "Cadre pour l'évaluation et la gestion des fournisseurs d'API externes et des intégrations de tiers en fonction des risques, des performances et de la conformité.",
+  "resource.vendor-management-best-practices.description": "Cadre pour l'évaluation et la gestion des fournisseurs d’API externes et des intégrations de tiers en fonction des risques, des performances et de la conformité.",
   "resource.vendor-management-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.steps": "Mettre en place des processus de gestion des fournisseurs afin d'évaluer, d'intégrer et de contrôler les fournisseurs d'API tiers.",
-  "resource.vendor-management-best-practices.tips": "Personnalisez les bonnes pratiques de gestion des fournisseurs pour votre domaine",
-  "resource.api-audit-checklist.title": "Liste de contrôle de l'audit de l'API",
-  "resource.api-audit-checklist.description": "Une liste de contrôle basée sur le cycle de vie permettant de vérifier l'état de préparation de l'API à travers les phases de conception, de livraison, de publication et de conformité à l'aide de critères d'audit et de preuves définis.",
-  "resource.api-audit-checklist.outcomes": "Meilleure compréhension des principes de la liste de contrôle de l'audit de l'API",
-  "resource.api-audit-checklist.steps": "Utilisez la liste de contrôle de l'audit de l'API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
-  "resource.api-audit-checklist.tips": "Chaque élément d'audit relie les tâches du cycle de vie (étapes), les directives applicables et les preuves à l'appui afin de fournir une vision claire de l'état de préparation de l'API.",
+  "resource.vendor-management-best-practices.steps": "Mettre en place des processus de gestion des fournisseurs afin d'évaluer, d'intégrer et de contrôler les fournisseurs d’API tiers.",
+  "resource.vendor-management-best-practices.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.api-audit-checklist.title": "Liste de contrôle de l'audit de l’API",
+  "resource.api-audit-checklist.description": "Une liste de contrôle basée sur le cycle de vie permettant de vérifier l'état de préparation de l’API à travers les phases de conception, de livraison, de publication et de conformité à l'aide de critères d'audit et de preuves définis.",
+  "resource.api-audit-checklist.outcomes": "Meilleure compréhension des principes de la liste de contrôle de l'audit de l’API",
+  "resource.api-audit-checklist.steps": "Utilisez la liste de contrôle de l'audit de l’API pour vous assurer que la conception de l’API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
+  "resource.api-audit-checklist.tips": "Chaque élément d'audit relie les tâches du cycle de vie (étapes), les directives applicables et les preuves à l'appui afin de fournir une vision claire de l'état de préparation de l’API.",
   "resource.api-business-model-canvas.title": "API Business Model Canvas",
-  "resource.api-business-model-canvas.description": "Évaluer stratégiquement la viabilité de l'activité API en établissant une cartographie des propositions de valeur, des segments de consommateurs et des ressources clés.",
-  "resource.api-business-model-canvas.outcomes": "Une stratégie commerciale claire pour les API",
-  "resource.api-business-model-canvas.steps": "Résumer la proposition de valeur de l'API",
+  "resource.api-business-model-canvas.description": "Évaluer stratégiquement la viabilité du modèle API en cartographiant les propositions de valeur, les segments d’utilisateurs et les ressources clés.",
+  "resource.api-business-model-canvas.outcomes": "Stratégie métier claire pour les API",
+  "resource.api-business-model-canvas.steps": "Résumer la proposition de valeur de l’API",
   "resource.api-business-model-canvas.tips": "Commencer par une seule API pour plus de clarté",
-  "resource.api-design-principles.title": "Principes de conception de l'API",
-  "resource.api-design-principles.description": "Un guide concis sur l'ergonomie, la facilité de découverte et la cohérence des API, fondé sur des règles de conception communes et les besoins réels des consommateurs.",
+  "resource.api-design-principles.title": "Principes de conception de l’API",
+  "resource.api-design-principles.description": "Un guide concis sur l’ergonomie, la découvrabilité et la cohérence des API, fondé sur des règles de conception communes et les besoins réels des utilisateurs.",
   "resource.api-design-principles.outcomes": "Meilleure compréhension des principes de conception des API",
-  "resource.api-design-principles.steps": "**Consumer-first design:** commencer chaque cycle APIOps en rassemblant les objectifs des utilisateurs et les termes du domaine afin que les APIs résolvent des problèmes réels.",
-  "resource.api-design-principles.tips": "Personnalisez les principes de conception de l'API pour votre domaine",
+  "resource.api-design-principles.steps": "**Conception centrée utilisateur :** commencer chaque cycle APIOps en rassemblant les objectifs des utilisateurs et les termes du domaine métier afin que les API résolvent des problèmes réels.",
+  "resource.api-design-principles.tips": "Adaptez cette ressource à votre contexte.",
   "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas",
-  "resource.api-value-proposition-canvas.description": "Aligner les fonctionnalités de l'API sur les besoins des utilisateurs en établissant une correspondance entre les tâches, les douleurs et les gains et les produits de l'API.",
+  "resource.api-value-proposition-canvas.description": "Aligner les fonctionnalités de l’API sur les besoins des utilisateurs en reliant les tâches, irritants et gains aux produits API.",
   "resource.api-value-proposition-canvas.outcomes": "Développement de fonctionnalités ciblées",
-  "resource.api-value-proposition-canvas.steps": "Liste des tâches liées au parcours de l'utilisateur",
+  "resource.api-value-proposition-canvas.steps": "Liste des tâches liées au parcours de l’utilisateur",
   "resource.api-value-proposition-canvas.tips": "Utiliser les données du Customer Journey Canvas",
   "resource.business-impact-canvas.title": "Business Impact Canvas",
-  "resource.business-impact-canvas.description": "Concevoir une architecture de plateforme API évolutive et sécurisée qui réponde aux exigences commerciales et techniques.",
+  "resource.business-impact-canvas.description": "Identifie les impacts métier, données, sécurité, disponibilité et opérations avant de choisir le mode de mise en œuvre.",
   "resource.business-impact-canvas.outcomes": "Infrastructure API évolutive",
   "resource.business-impact-canvas.steps": "Risques liés à la disponibilité : Identifier les risques et les impacts.",
-  "resource.business-impact-canvas.tips": "Impliquer les architectes et les promoteurs dans le processus de conception",
+  "resource.business-impact-canvas.tips": "Impliquer les architectes et les développeurs dans le processus de conception.",
   "resource.capacity-canvas.title": "Capacity Canvas",
-  "resource.capacity-canvas.description": "Planifier la capacité de l'API pour répondre aux demandes actuelles et futures de l'entreprise, en garantissant l'évolutivité et les performances.",
-  "resource.capacity-canvas.outcomes": "Alignement de la capacité de l'API sur les volumes d'activité",
-  "resource.capacity-canvas.steps": "Documenter les volumes d'affaires actuels",
+  "resource.capacity-canvas.description": "Planifier la capacité nécessaire pour soutenir les volumes actuels et futurs d’une capacité, d’une interface ou d’un mode de mise en œuvre, en garantissant l’évolutivité et la performance.",
+  "resource.capacity-canvas.outcomes": "Capacité alignée sur les volumes métier et les modes d’usage attendus",
+  "resource.capacity-canvas.steps": "Documenter les volumes métier actuels",
   "resource.capacity-canvas.tips": "Utiliser l'analyse pour prévoir les tendances de la croissance",
   "resource.customer-journey-canvas.title": "Customer Journey Canvas",
-  "resource.customer-journey-canvas.description": "Cartographier les parcours des clients pour identifier les besoins et les points de douleur, afin d'améliorer la conception de l'API et l'expérience de l'utilisateur.",
-  "resource.customer-journey-canvas.outcomes": "Amélioration de la compréhension du client",
+  "resource.customer-journey-canvas.description": "Cartographier les parcours des clients ou utilisateurs pour identifier les besoins et irritants, afin d’améliorer la conception de la capacité et de l’interface.",
+  "resource.customer-journey-canvas.outcomes": "Meilleure compréhension du parcours client ou utilisateur",
   "resource.customer-journey-canvas.steps": "Définir le profil du client",
   "resource.customer-journey-canvas.tips": "Répéter avec l'aide de l'équipe pour affiner les étapes",
   "resource.event-canvas.title": "Event Canvas",
@@ -172,202 +172,202 @@
   "resource.graphql-canvas.title": "GraphQL Canvas",
   "resource.graphql-canvas.description": "Concevoir des API GraphQL en définissant des types, des requêtes, des mutations et des abonnements.",
   "resource.graphql-canvas.outcomes": "Conception d'une API GraphQL structurée",
-  "resource.graphql-canvas.steps": "Quels sont les problèmes que les consommateurs d'API tentent de résoudre ? De quelles données ont-ils besoin ?",
+  "resource.graphql-canvas.steps": "Quels problèmes les utilisateurs API tentent-ils de résoudre ? De quelles données ont-ils besoin ?",
   "resource.graphql-canvas.tips": "Utiliser l'introspection pour valider les définitions de type",
   "resource.interaction-canvas.title": "Interaction Canvas",
-  "resource.interaction-canvas.description": "Définir les interactions API, les flux de travail et les réponses attendues afin de garantir une expérience cohérente pour les consommateurs d'API.",
-  "resource.interaction-canvas.outcomes": "Des flux de travail clairs pour les interactions avec l'API",
-  "resource.interaction-canvas.steps": "Associer les interactions de l'API aux tâches de l'utilisateur",
+  "resource.interaction-canvas.description": "Définir les interactions, workflows et réponses attendues afin de garantir une expérience cohérente pour les utilisateurs de la capacité ou de l’interface.",
+  "resource.interaction-canvas.outcomes": "Des flux de travail clairs pour les interactions avec l’API",
+  "resource.interaction-canvas.steps": "Associer les interactions de l’API aux tâches de l’utilisateur",
   "resource.interaction-canvas.tips": "Commencer par les cas d'utilisation courants avant de traiter les cas marginaux",
   "resource.location-canvas.title": "Location Canvas",
-  "resource.location-canvas.description": "Cartographier les emplacements des fournisseurs d'API et des consommateurs pour garantir la conformité et les performances dans toutes les régions.",
+  "resource.location-canvas.description": "Cartographier les emplacements des fournisseurs et des utilisateurs pour garantir conformité, connectivité et performance entre régions.",
   "resource.location-canvas.outcomes": "Respect des réglementations locales",
-  "resource.location-canvas.steps": "Carte des emplacements des fournisseurs d'API.",
+  "resource.location-canvas.steps": "Carte des emplacements des fournisseurs d’API.",
   "resource.location-canvas.tips": "Collaborer avec les équipes juridiques et de conformité",
   "resource.rest-canvas.title": "REST Canvas",
   "resource.rest-canvas.description": "Concevoir des API en utilisant les principes RESTful, en définissant des ressources, des verbes et des exemples de requêtes et de réponses.",
-  "resource.rest-canvas.outcomes": "Conception cohérente de l'API RESTful",
-  "resource.rest-canvas.steps": "Identifier les ressources clés exposées par l'API",
+  "resource.rest-canvas.outcomes": "Conception cohérente de l’API RESTful",
+  "resource.rest-canvas.steps": "Identifier les ressources clés exposées par l’API",
   "resource.rest-canvas.tips": "Utiliser les méthodes HTTP standard (GET, POST, PUT, DELETE)",
-  "resource.api-community-engagement-strategies.outcomes.1": "Approche standardisée utilisant les stratégies d'engagement communautaire de l'API",
-  "resource.api-community-engagement-strategies.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-community-engagement-strategies.outcomes.1": "Approche standardisée utilisant les stratégies d'engagement communautaire de l’API",
+  "resource.api-community-engagement-strategies.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-community-engagement-strategies.steps.1": "Créer du matériel promotionnel (par exemple, des études de cas, des exemples de réussite) qui met en évidence la valeur et les avantages des API.",
-  "resource.api-community-engagement-strategies.steps.2": "Créer des supports pédagogiques (par exemple, des tutoriels, de la documentation) qui expliquent les caractéristiques, les avantages et les modes d'utilisation de l'API.",
-  "resource.api-community-engagement-strategies.steps.3": "S'engager auprès des consommateurs d'API par le biais de boucles de retour d'information, de canaux d'assistance et de forums communautaires afin de comprendre leurs besoins et d'améliorer l'adoption de l'API.",
-  "resource.api-community-engagement-strategies.steps.4": "Analyser les indicateurs d'utilisation de l'API et intégrer les commentaires des utilisateurs dans les itérations de l'API.",
-  "resource.api-community-engagement-strategies.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.api-community-engagement-strategies.steps.2": "Créer des supports pédagogiques (par exemple, des tutoriels, de la documentation) qui expliquent les caractéristiques, les avantages et les modes d'utilisation de l’API.",
+  "resource.api-community-engagement-strategies.steps.3": "Interagir avec les utilisateurs API par le biais de boucles de feedback, de canaux d’assistance et de forums communautaires afin de comprendre leurs besoins et d’améliorer l’adoption de l’API.",
+  "resource.api-community-engagement-strategies.steps.4": "Analyser les indicateurs d'utilisation de l’API et intégrer les commentaires des utilisateurs dans les itérations de l’API.",
+  "resource.api-community-engagement-strategies.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.api-compliance-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de conformité des API",
-  "resource.api-compliance-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-compliance-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-compliance-best-practices.steps.1": "Mettre en œuvre des mesures pour s'assurer que les API sont conformes à ces exigences, y compris le cryptage des données, les contrôles d'accès et les pistes d'audit.",
   "resource.api-compliance-best-practices.steps.2": "Utiliser des listes de contrôle, des linters et des outils de test pour vérifier la cohérence et la conformité avec les normes.",
-  "resource.api-compliance-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-development-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de développement d'API",
-  "resource.api-development-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-compliance-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-development-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de développement d’API",
+  "resource.api-development-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-development-best-practices.steps.1": "Utilisez des frameworks, des bibliothèques et des normes de codage établis pour implémenter le contrat de manière cohérente et maintenable.",
-  "resource.api-development-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-metrics-and-analytics.outcomes.1": "Approche standardisée utilisant les métriques et l'analyse de l'API",
-  "resource.api-metrics-and-analytics.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-development-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-metrics-and-analytics.outcomes.1": "Approche standardisée utilisant les métriques et l'analyse de l’API",
+  "resource.api-metrics-and-analytics.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-metrics-and-analytics.steps.1": "Définir et surveiller les indicateurs de performance (par exemple, les appels API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
   "resource.api-metrics-and-analytics.steps.2": "Contrôler les initiatives API afin de garantir le respect des lignes directrices opérationnelles et des pratiques de gouvernance.",
-  "resource.api-metrics-and-analytics.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-onboarding-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de l'API Onboarding",
-  "resource.api-onboarding-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.api-onboarding-best-practices.steps.1": "Développer des processus et des ressources d'intégration pour aider les consommateurs d'API à comprendre comment utiliser efficacement les API.",
-  "resource.api-onboarding-best-practices.steps.2": "Documenter la manière dont les consommateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
-  "resource.api-onboarding-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices de gestion du portefeuille de l'API",
-  "resource.api-portfolio-management-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.api-portfolio-management-guidelines.steps.1": "Définir des pratiques de gestion du budget et des ressources qui décrivent les processus de gestion des budgets et des ressources pour les initiatives de l'API.",
-  "resource.api-portfolio-management-guidelines.steps.2": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur commerciale, de l'impact et de l'alignement sur les initiatives stratégiques.",
-  "resource.api-portfolio-management-guidelines.steps.3": "Contrôler le portefeuille d'API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l'entreprise.",
-  "resource.api-portfolio-management-guidelines.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.api-metrics-and-analytics.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-onboarding-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de l’API Onboarding",
+  "resource.api-onboarding-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-onboarding-best-practices.steps.1": "Développer des processus et ressources d’onboarding pour aider les utilisateurs API à comprendre comment utiliser efficacement les API.",
+  "resource.api-onboarding-best-practices.steps.2": "Documenter la manière dont les utilisateurs trouvent et utilisent l’API, y compris les processus d’onboarding et d’enregistrement.",
+  "resource.api-onboarding-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices de gestion du portefeuille de l’API",
+  "resource.api-portfolio-management-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-portfolio-management-guidelines.steps.1": "Définir des pratiques de gestion du budget et des ressources qui décrivent les processus de gestion des budgets et des ressources pour les initiatives de l’API.",
+  "resource.api-portfolio-management-guidelines.steps.2": "Établir des critères d’évaluation et de priorisation des affectations budgétaires en fonction de la valeur métier, de l’impact et de l’alignement sur les initiatives stratégiques.",
+  "resource.api-portfolio-management-guidelines.steps.3": "Contrôler le portefeuille d’API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l’entreprise.",
+  "resource.api-portfolio-management-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.api-security-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de sécurité des API",
-  "resource.api-security-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-security-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-security-best-practices.steps.1": "Mettre en œuvre des mesures de sécurité telles que l'authentification, l'autorisation, le cryptage et la limitation du débit pour protéger les API contre les menaces.",
   "resource.api-security-best-practices.steps.2": "Mettre en œuvre des contrôles de sécurité automatisés et des validations de conformité dans le pipeline CI/CD pour s'assurer que les API sont sécurisées et conformes.",
-  "resource.api-security-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-team-structure-guidelines.outcomes.1": "Approche normalisée à l'aide des lignes directrices sur la structure des équipes de l'API",
-  "resource.api-team-structure-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.api-team-structure-guidelines.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.api-security-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-team-structure-guidelines.outcomes.1": "Approche normalisée à l'aide des lignes directrices sur la structure des équipes de l’API",
+  "resource.api-team-structure-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-team-structure-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.api-testing-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de test des API",
-  "resource.api-testing-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-testing-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-testing-best-practices.steps.1": "Intégrer des tests fonctionnels et non fonctionnels dans le pipeline CI/CD pour s'assurer que les API répondent aux normes de qualité.",
-  "resource.api-testing-best-practices.steps.2": "Utiliser des outils de test automatisés pour valider les fonctionnalités, la sécurité et les performances de l'API.",
-  "resource.api-testing-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-training-programs.outcomes.1": "Approche normalisée à l'aide des programmes de formation de l'API",
-  "resource.api-training-programs.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-testing-best-practices.steps.2": "Utiliser des outils de test automatisés pour valider les fonctionnalités, la sécurité et les performances de l’API.",
+  "resource.api-testing-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-training-programs.outcomes.1": "Approche normalisée à l'aide des programmes de formation de l’API",
+  "resource.api-training-programs.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-training-programs.steps.1": "Encourager la formation continue par des cours en ligne, des certifications et l'engagement communautaire.",
   "resource.api-training-programs.steps.2": "Fournir des formations et des ressources pour aider les équipes à adopter un état d'esprit \"API-first\" et à comprendre les avantages des API.",
-  "resource.api-training-programs.steps.3": "Fournir des programmes de formation, des ateliers et des ressources pour aider les équipes à améliorer leurs compétences et leurs connaissances en matière d'API.",
-  "resource.api-training-programs.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-versioning-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de versionnement de l'API",
-  "resource.api-versioning-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.api-versioning-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.api-training-programs.steps.3": "Fournir des programmes de formation, des ateliers et des ressources pour aider les équipes à améliorer leurs compétences et leurs connaissances en matière d’API.",
+  "resource.api-training-programs.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-versioning-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de versionnement de l’API",
+  "resource.api-versioning-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-versioning-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.apiops-CI-CD-for-apis.outcomes.1": "Approche standardisée utilisant CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.apiops-CI-CD-for-apis.steps.1": "Intégrer des tests automatisés dans le pipeline CI/CD pour assurer une validation continue de la qualité de l'API.",
-  "resource.apiops-CI-CD-for-apis.steps.2": "Mettre en œuvre des stratégies de déploiement (par exemple, des déploiements \"bleu-vert\", des versions \"canari\") afin de minimiser les risques lors des mises à jour de l'API.",
+  "resource.apiops-CI-CD-for-apis.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.apiops-CI-CD-for-apis.steps.1": "Intégrer des tests automatisés dans le pipeline CI/CD pour assurer une validation continue de la qualité de l’API.",
+  "resource.apiops-CI-CD-for-apis.steps.2": "Mettre en œuvre des stratégies de mise à disposition (par exemple, blue-green ou canary releases) afin de minimiser les risques lors des mises à jour de l’API.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Prendre l'habitude d'examiner les mesures et de planifier des activités d'amélioration continue.",
-  "resource.apiops-CI-CD-for-apis.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.apiops-CI-CD-for-apis.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.competitor-analysis-template.outcomes.1": "Approche standardisée à l'aide du modèle d'analyse des concurrents",
-  "resource.competitor-analysis-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.competitor-analysis-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.competitor-analysis-template.steps.1": "Analyser les API des concurrents pour comprendre leurs forces, leurs faiblesses et leurs arguments de vente uniques.",
-  "resource.competitor-analysis-template.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.competitor-analysis-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.contract-first-design.outcomes.1": "Approche normalisée utilisant la méthode du contrat d'abord (Contract First Design)",
-  "resource.contract-first-design.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.contract-first-design.steps.1": "Définir des contrats d'API qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
-  "resource.contract-first-design.steps.2": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d'API lisibles par machine, faciles à partager et à valider.",
-  "resource.contract-first-design.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.contract-first-design.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.contract-first-design.steps.1": "Définir des contrats d’API qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
+  "resource.contract-first-design.steps.2": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d’API lisibles par machine, faciles à partager et à valider.",
+  "resource.contract-first-design.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.cross-functional-collaboration-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.cross-functional-collaboration-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.data-privacy-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices sur la confidentialité des données",
-  "resource.data-privacy-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.data-privacy-guidelines.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.cross-functional-collaboration-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.data-privacy-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices sur la protection des données",
+  "resource.data-privacy-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.data-privacy-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.domain-canvas.outcomes.1": "Approche standardisée utilisant Domain Canvas",
-  "resource.domain-canvas.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.domain-canvas.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.domain-canvas.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.domain-canvas.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.ecosystem-vision-template.outcomes.1": "Approche standardisée utilisant le modèle de vision écosystémique",
-  "resource.ecosystem-vision-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.ecosystem-vision-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.ecosystem-vision-template.steps.1": "Identifier les principaux partenaires de l'écosystème et les parties prenantes qui bénéficieront de l'écosystème ou y contribueront.",
   "resource.ecosystem-vision-template.steps.2": "Identifier les lacunes du marché que vos API peuvent combler, en se basant sur les offres des concurrents.",
-  "resource.ecosystem-vision-template.steps.3": "Identifier les partenaires potentiels dont les API peuvent améliorer vos capacités en matière d'API et votre proposition de valeur.",
+  "resource.ecosystem-vision-template.steps.3": "Identifier les partenaires potentiels dont les API peuvent améliorer vos capacités en matière d’API et votre proposition de valeur.",
   "resource.ecosystem-vision-template.steps.4": "Élaborer une stratégie de différenciation qui mette en évidence les caractéristiques et les avantages uniques de vos API.",
   "resource.ecosystem-vision-template.steps.5": "Définissez la vision de l'écosystème pour vos API, y compris la manière dont elles interagiront avec d'autres systèmes et plateformes.",
   "resource.ecosystem-vision-template.steps.6": "Concevoir des API pour permettre une intégration et une collaboration transparentes au sein de l'écosystème.",
-  "resource.ecosystem-vision-template.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.ecosystem-vision-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.industry-standards-and-best-practices.outcomes.1": "Approche standardisée utilisant les normes et les meilleures pratiques de l'industrie",
-  "resource.industry-standards-and-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.industry-standards-and-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.partner-integration-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices pour l'intégration des partenaires",
-  "resource.partner-integration-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.partner-integration-guidelines.steps.1": "Surveillez les performances et la conformité de l'API de vos partenaires pour garantir la fiabilité et l'alignement avec votre stratégie d'API.",
-  "resource.partner-integration-guidelines.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.industry-standards-and-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.industry-standards-and-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.partner-integration-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices pour l’intégration des partenaires",
+  "resource.partner-integration-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.partner-integration-guidelines.steps.1": "Surveiller les performances et la conformité des API de vos partenaires pour garantir la fiabilité et l’alignement avec votre stratégie API.",
+  "resource.partner-integration-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.role-communication-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.role-communication-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.role-communication-best-practices.steps.1": "Veiller à ce que les rôles et les responsabilités soient communiqués à tous les membres de l'équipe et aux parties prenantes afin d'assurer l'alignement.",
-  "resource.role-communication-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.role-communication-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.scalable-infrastructure-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière d'infrastructure évolutive",
-  "resource.scalable-infrastructure-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.scalable-infrastructure-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.scalable-infrastructure-best-practices.steps.1": "Contrôler les performances et la capacité de l'infrastructure pour s'assurer qu'elle peut répondre à une demande croissante.",
-  "resource.scalable-infrastructure-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.scalable-infrastructure-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.service-agreement-template.outcomes.1": "Approche standardisée utilisant le modèle d'accord de service",
-  "resource.service-agreement-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.service-agreement-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.service-agreement-template.steps.1": "Utiliser des formats normalisés pour créer des accords de service lisibles par machine, faciles à partager et à valider.",
   "resource.service-agreement-template.steps.2": "Veiller à ce que les accords de service soient examinés et approuvés par les parties prenantes afin de garantir l'alignement et la clarté.",
-  "resource.service-agreement-template.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.service-agreement-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.stakeholder-engagement-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques en matière d'engagement des parties prenantes",
-  "resource.stakeholder-engagement-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.stakeholder-engagement-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.stakeholder-engagement-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.stakeholder-engagement-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.test-automation-frameworks.outcomes.1": "Approche standardisée utilisant des cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.test-automation-frameworks.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.test-automation-frameworks.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.test-automation-frameworks.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.vendor-management-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.vendor-management-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.vendor-management-best-practices.steps.1": "Définir les critères d'évaluation des API des fournisseurs, y compris la fiabilité, la sécurité et la conformité.",
-  "resource.vendor-management-best-practices.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
-  "resource.api-audit-checklist.outcomes.1": "Approche normalisée à l'aide de la liste de contrôle de l'audit de l'API",
-  "resource.api-audit-checklist.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
-  "resource.api-audit-checklist.steps.1": "Réalisez des audits pour évaluer la couverture du cycle de vie et vérifier que l'API respecte les normes métier, de conception et opérationnelles.",
+  "resource.vendor-management-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-audit-checklist.outcomes.1": "Approche normalisée à l'aide de la liste de contrôle de l'audit de l’API",
+  "resource.api-audit-checklist.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-audit-checklist.steps.1": "Réalisez des audits pour évaluer la couverture du cycle de vie et vérifier que l’API respecte les normes métier, de conception et opérationnelles.",
   "resource.api-audit-checklist.steps.2": "S'assurer que la documentation, les modèles de sécurité, la configuration de la passerelle et les exigences légales sont clairement définis, validés et étayés par des preuves.",
   "resource.api-audit-checklist.tips.1": "Utilisez la liste de contrôle d'audit des API de manière collaborative entre les rôles métier et techniques",
   "resource.api-business-model-canvas.outcomes.1": "Identification des ressources et des partenaires clés",
-  "resource.api-business-model-canvas.outcomes.2": "Alignement des fonctionnalités de l'API sur les objectifs de l'entreprise",
-  "resource.api-business-model-canvas.steps.1": "Définir les segments de consommateurs",
+  "resource.api-business-model-canvas.outcomes.2": "Alignement des fonctionnalités de l’API sur les objectifs métier",
+  "resource.api-business-model-canvas.steps.1": "Définir les segments d’utilisateurs",
   "resource.api-business-model-canvas.steps.2": "Identifier les stratégies de relations avec les développeurs",
   "resource.api-business-model-canvas.steps.3": "Cartographier les canaux de distribution",
-  "resource.api-business-model-canvas.steps.4": "documenter les ressources et activités clés",
+  "resource.api-business-model-canvas.steps.4": "Documenter les ressources clés et les activités clés",
   "resource.api-business-model-canvas.steps.5": "Identifier les principaux partenaires et parties prenantes",
   "resource.api-business-model-canvas.steps.6": "Mettre en évidence les avantages et les coûts",
   "resource.api-business-model-canvas.tips.1": "Utiliser des mesures telles que le rapport coût/bénéfice pour hiérarchiser les opportunités",
   "resource.api-business-model-canvas.tips.2": "Valider les résultats avec les principales parties prenantes",
-  "resource.api-design-principles.outcomes.1": "Approche normalisée utilisant les principes de conception de l'API",
-  "resource.api-design-principles.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l'API",
+  "resource.api-design-principles.outcomes.1": "Approche normalisée utilisant les principes de conception de l’API",
+  "resource.api-design-principles.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
   "resource.api-design-principles.steps.1": "**Noms et comportements cohérents:** appliquer des conventions partagées pour les ressources, les erreurs et les formats afin de rendre les API prévisibles.",
-  "resource.api-design-principles.steps.2": "**Dirigé par le contrat:** capturer l'interface avec OpenAPI ou AsyncAPI avant le codage pour aligner les équipes et permettre l'automatisation.",
-  "resource.api-design-principles.steps.3": "**Utilisabilité et facilité de découverte:** fournir une documentation et des exemples clairs afin que les développeurs comprennent rapidement comment utiliser l'API.",
-  "resource.api-design-principles.steps.4": "**Les conceptions évoluent par petites étapes et par versions, de sorte que les changements ne perturbent pas les consommateurs existants.",
-  "resource.api-design-principles.tips.1": "L'utiliser en collaboration avec les entreprises et les techniciens",
+  "resource.api-design-principles.steps.2": "**Dirigé par le contrat:** capturer l’interface avec OpenAPI ou AsyncAPI avant le codage pour aligner les équipes et permettre l'automatisation.",
+  "resource.api-design-principles.steps.3": "**Utilisabilité et découvrabilité:** fournir une documentation et des exemples clairs afin que les développeurs comprennent rapidement comment utiliser l’API.",
+  "resource.api-design-principles.steps.4": "**Itérer en sécurité :** faire évoluer les conceptions par petits incréments versionnés afin que les changements ne perturbent pas les utilisateurs existants.",
+  "resource.api-design-principles.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
   "resource.api-value-proposition-canvas.outcomes.1": "Alignement sur les besoins des utilisateurs",
-  "resource.api-value-proposition-canvas.outcomes.2": "Amélioration de la satisfaction des consommateurs d'API",
+  "resource.api-value-proposition-canvas.outcomes.2": "Meilleure satisfaction des utilisateurs API",
   "resource.api-value-proposition-canvas.steps.1": "Identifier les caractéristiques permettant d'obtenir les gains escomptés",
   "resource.api-value-proposition-canvas.steps.2": "Définir des caractéristiques permettant de relever les défis",
-  "resource.api-value-proposition-canvas.steps.3": "Cartographier les caractéristiques des produits de l'API",
-  "resource.api-value-proposition-canvas.tips.1": "Mettre en évidence les caractéristiques qui soulagent les douleurs ou améliorent les gains",
-  "resource.api-value-proposition-canvas.tips.2": "Valider les caractéristiques avec les consommateurs d'API pour garantir l'alignement",
+  "resource.api-value-proposition-canvas.steps.3": "Cartographier les caractéristiques des produits de l’API",
+  "resource.api-value-proposition-canvas.tips.1": "Mettre en évidence les fonctionnalités qui réduisent les irritants ou renforcent les gains.",
+  "resource.api-value-proposition-canvas.tips.2": "Valider les fonctionnalités avec les utilisateurs API pour garantir l’alignement.",
   "resource.business-impact-canvas.outcomes.1": "Sécurité et conformité renforcées",
-  "resource.business-impact-canvas.outcomes.2": "Amélioration des performances de l'API",
+  "resource.business-impact-canvas.outcomes.2": "Amélioration des performances de l’API",
   "resource.business-impact-canvas.steps.1": "Moyens d'atténuer les risques liés à la disponibilité : Définir les mesures d'atténuation.",
   "resource.business-impact-canvas.steps.2": "Risques liés à la sécurité : Documenter les risques liés à la sécurité.",
   "resource.business-impact-canvas.steps.3": "Moyens d'atténuer les risques de sécurité : Proposer des stratégies pour atténuer les risques de sécurité.",
   "resource.business-impact-canvas.steps.4": "Risques liés aux données : Identifier les risques pour l'exactitude ou la disponibilité des données.",
   "resource.business-impact-canvas.steps.5": "Moyens d'atténuer les risques liés aux données : Prévoir des stratégies pour faire face aux risques liés aux données.",
   "resource.business-impact-canvas.tips.1": "Utiliser les incidents passés pour identifier les risques potentiels",
-  "resource.business-impact-canvas.tips.2": "Priorité aux API critiques ayant le plus d'impact sur l'activité de l'entreprise",
-  "resource.capacity-canvas.outcomes.1": "Préparés aux futures tendances de la consommation",
+  "resource.business-impact-canvas.tips.2": "Prioriser les API critiques ayant le plus d’impact sur l’activité métier",
+  "resource.capacity-canvas.outcomes.1": "Préparation aux tendances futures d’usage",
   "resource.capacity-canvas.outcomes.2": "Stratégies définies de mise en cache et de limitation du débit",
-  "resource.capacity-canvas.steps.1": "Prévoir les tendances futures de la consommation",
+  "resource.capacity-canvas.steps.1": "Prévoir les tendances futures d’usage",
   "resource.capacity-canvas.steps.2": "Planifier les pics de charge et les exigences de disponibilité",
   "resource.capacity-canvas.steps.3": "Définir les stratégies de mise en cache et de limitation du débit",
   "resource.capacity-canvas.steps.4": "Proposer des stratégies de mise à l'échelle",
   "resource.capacity-canvas.tips.1": "Définir des scénarios d'utilisation maximale",
   "resource.capacity-canvas.tips.2": "Inclure des tests d'évolutivité dans la phase de planification",
-  "resource.customer-journey-canvas.outcomes.1": "Conception améliorée de l'API",
-  "resource.customer-journey-canvas.outcomes.2": "Une meilleure expérience pour l'utilisateur",
+  "resource.customer-journey-canvas.outcomes.1": "Conception améliorée de l’API",
+  "resource.customer-journey-canvas.outcomes.2": "Une meilleure expérience pour l’utilisateur",
   "resource.customer-journey-canvas.steps.1": "Identifier les éléments déclencheurs du voyage",
   "resource.customer-journey-canvas.steps.2": "Décrire la fin du voyage",
   "resource.customer-journey-canvas.steps.3": "Cartographier les étapes du voyage avec les intrants et les extrants",
-  "resource.customer-journey-canvas.steps.4": "Identifier les problèmes des clients",
+  "resource.customer-journey-canvas.steps.4": "Identifier les irritants des clients",
   "resource.customer-journey-canvas.steps.5": "Résumer les gains pour les clients",
   "resource.customer-journey-canvas.steps.6": "Définir les intrants nécessaires et les résultats qui en découlent",
   "resource.customer-journey-canvas.steps.7": "Définir les interactions API pour chaque étape",
-  "resource.customer-journey-canvas.tips.1": "Utiliser les résultats de ce canevas pour informer d'autres canevas tels que le canevas de proposition de valeur de l'API.",
+  "resource.customer-journey-canvas.tips.1": "Utiliser les résultats de ce canevas pour informer d'autres canevas tels que le canevas de proposition de valeur de l’API.",
   "resource.event-canvas.outcomes.1": "Déclencheurs d'événements et logique de traitement clairs",
   "resource.event-canvas.outcomes.2": "Amélioration de la réactivité aux changements en temps réel",
   "resource.event-canvas.steps.1": "Définir des déclencheurs pour chaque événement",
-  "resource.event-canvas.steps.2": "Décrire la logique de traitement des événements par le backend",
+  "resource.event-canvas.steps.2": "Décrire la logique de traitement des événements par le systèmes backend",
   "resource.event-canvas.steps.3": "Préciser les résultats obtenus ou les remerciements",
-  "resource.event-canvas.tips.1": "documenter les flux d'événements et les dépendances",
+  "resource.event-canvas.tips.1": "Documenter les flux d’événements et les dépendances",
   "resource.event-canvas.tips.2": "Valider le traitement des événements à l'aide de cas de test",
   "resource.graphql-canvas.outcomes.1": "Types définis et leurs relations",
   "resource.graphql-canvas.outcomes.2": "Des requêtes, des mutations et des abonnements clairs",
@@ -378,19 +378,19 @@
   "resource.graphql-canvas.steps.5": "Abonnements aux grandes lignes pour des mises à jour en temps réel",
   "resource.graphql-canvas.steps.6": "Définir l'authentification et l'autorisation : Qui peut accéder à quels champs ou types ?",
   "resource.graphql-canvas.steps.7": "Tenez compte des contraintes de pagination, de filtrage ou de limitation du débit.",
-  "resource.graphql-canvas.tips.1": "documenter les exemples de requêtes et de mutations",
+  "resource.graphql-canvas.tips.1": "Documenter les exemples de requêtes et de mutations",
   "resource.graphql-canvas.tips.2": "Veiller à ce que les noms des types soient descriptifs et cohérents",
   "resource.interaction-canvas.outcomes.1": "Entrées et sorties définies pour chaque interaction",
   "resource.interaction-canvas.outcomes.2": "Règles de validation cohérentes entre les interactions",
   "resource.interaction-canvas.steps.1": "Définir des points finaux pour chaque interaction",
-  "resource.interaction-canvas.steps.2": "documenter les entrées et les sorties pour chaque interaction",
+  "resource.interaction-canvas.steps.2": "Documenter les entrées et sorties de chaque interaction",
   "resource.interaction-canvas.steps.3": "Spécifier les règles et contraintes de validation",
   "resource.interaction-canvas.steps.4": "Créer des modèles d'interaction pour les interactions CRUD, axées sur les requêtes, axées sur les commandes et axées sur les événements.",
   "resource.interaction-canvas.tips.1": "Simuler des interactions avec des données fictives pour valider les flux de travail",
-  "resource.interaction-canvas.tips.2": "documenter les réponses attendues en cas d'interactions réussies ou non",
-  "resource.location-canvas.outcomes.1": "Optimisation des performances de l'API dans toutes les régions",
+  "resource.interaction-canvas.tips.2": "Documenter les réponses attendues pour les interactions réussies et en erreur",
+  "resource.location-canvas.outcomes.1": "Optimisation des performances de l’API dans toutes les régions",
   "resource.location-canvas.outcomes.2": "Meilleure compréhension des besoins régionaux",
-  "resource.location-canvas.steps.1": "Documenter l'emplacement des consommateurs.",
+  "resource.location-canvas.steps.1": "Documenter l’emplacement des utilisateurs.",
   "resource.location-canvas.steps.2": "Identifier les réglementations applicables.",
   "resource.location-canvas.steps.3": "Documenter l'endroit où les données doivent être stockées.",
   "resource.location-canvas.steps.4": "s'assurer que les API sont accessibles dans toutes les régions du réseau prévues.",
@@ -399,44 +399,44 @@
   "resource.location-canvas.tips.2": "Résoudre de manière proactive les contraintes liées à la localisation",
   "resource.rest-canvas.outcomes.1": "Ressources définies et leurs interactions",
   "resource.rest-canvas.outcomes.2": "Exemples de demandes et de réponses pour plus de clarté",
-  "resource.rest-canvas.steps.1": "Définir la structure du modèle de ressources de l'API",
+  "resource.rest-canvas.steps.1": "Définir la structure du modèle de ressources de l’API",
   "resource.rest-canvas.steps.2": "Spécifier les verbes HTTP utilisés pour interagir avec les ressources",
   "resource.rest-canvas.steps.3": "Fournir des exemples de demandes et de réponses pour chaque verbe",
   "resource.rest-canvas.tips.1": "Veiller à ce que les URI des ressources soient intuitifs et cohérents",
   "resource.rest-canvas.tips.2": "gestion des erreurs de documents et codes de réponse",
   "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
-  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
-  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
-  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
-  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
-  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
-  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
-  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
-  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-value-proposition-canvas.description": "Un canvas indépendant de la technologie pour cartographier les tâches, gains, irritants et capacités réutilisables candidates des utilisateurs avant de choisir un style d’intégration.",
+  "resource.capability-value-proposition-canvas.outcomes": "Proposition de valeur claire pour une capacité réutilisable",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Les tâches, gains et irritants des utilisateurs sont capturés sans présupposer de technologie.",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Les capacités réutilisables candidates sont identifiées pour l’évaluation d’architecture.",
+  "resource.capability-value-proposition-canvas.steps": "Lister les tâches et résultats utilisateur que la capacité doit soutenir.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identifier les fonctionnalités de capacité qui créent des gains.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identifier les fonctionnalités de capacité qui réduisent les irritants.",
+  "resource.capability-value-proposition-canvas.steps.3": "Regrouper les fonctionnalités en capacités réutilisables candidates.",
+  "resource.capability-value-proposition-canvas.tips": "Rester indépendant de la technologie jusqu’à ce que les exigences indiquent le style adapté.",
+  "resource.capability-value-proposition-canvas.tips.1": "Utilisez ce canvas à la place de l’API Value Proposition Canvas lorsque l’API n’est pas encore le style d’intégration retenu.",
   "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
-  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
-  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
-  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
-  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
-  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
-  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
-  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
-  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
-  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
-  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
-  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.capability-business-model-canvas.description": "Un canvas de modèle économique pour les capacités d’intégration réutilisables, couvrant la valeur, les utilisateurs, la propriété, l’engagement, les coûts et les bénéfices sans présupposer une mise à disposition par API.",
+  "resource.capability-business-model-canvas.outcomes": "Modèle opérationnel viable pour une capacité réutilisable",
+  "resource.capability-business-model-canvas.outcomes.1": "La propriété, les utilisateurs, les canaux, les partenaires et les besoins de support sont clarifiés.",
+  "resource.capability-business-model-canvas.outcomes.2": "Les coûts et bénéfices sont visibles avant l’engagement architectural.",
+  "resource.capability-business-model-canvas.steps": "Résumer la proposition de valeur de la capacité.",
+  "resource.capability-business-model-canvas.steps.1": "Identifier les segments d’utilisateurs et les canaux d’engagement.",
+  "resource.capability-business-model-canvas.steps.2": "Définir les activités, ressources et partenaires clés.",
+  "resource.capability-business-model-canvas.steps.3": "Capturer les coûts et bénéfices.",
+  "resource.capability-business-model-canvas.steps.4": "Clarifier la propriété, le financement, le support et les attentes de cycle de vie.",
+  "resource.capability-business-model-canvas.steps.5": "Valider le modèle avec les utilisateurs, les producteurs et les parties prenantes de gouvernance.",
+  "resource.capability-business-model-canvas.tips": "Utilisez ce canvas à la place de l’API Business Model Canvas lorsque le style d’intégration reste ouvert.",
+  "resource.capability-business-model-canvas.tips.1": "Gardez le focus sur la viabilité de la capacité réutilisable, pas sur une connexion ponctuelle.",
   "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
-  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
-  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
-  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
-  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
+  "resource.consumer-experience-requirements-canvas.description": "Un canvas d’exigences pour l’expérience utilisateur et les besoins non fonctionnels qui doivent guider le choix d’architecture ultérieur.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Exigences utilisateur indépendantes de la technologie",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Les besoins d’expérience et les besoins non fonctionnels sont capturés avant le début de la conception.",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Les implications d’architecture sont documentées pour sélectionner le style adapté.",
+  "resource.consumer-experience-requirements-canvas.steps": "Capturer les objectifs utilisateur et le contexte d’usage.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Documenter les attentes de disponibilité, fraîcheur, volume, performance, qualité des données et cohérence.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Documenter les attentes de sécurité, protection des données, onboarding, changement, observabilité, support et reprise.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Résumer ce que les exigences impliquent pour les styles d’architecture possibles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Utilisez ce canvas comme passerelle entre la valeur de la capacité et la décision d’architecture.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Ne choisissez pas API, événement, fichier, flux ou produit de données avant que les exigences n’indiquent l’option la plus adaptée."
 }
diff --git a/src/data/method/fr/labels.stakeholders.json b/src/data/method/fr/labels.stakeholders.json
index e8a1c62..72499b7 100644
--- a/src/data/method/fr/labels.stakeholders.json
+++ b/src/data/method/fr/labels.stakeholders.json
@@ -1,15 +1,15 @@
 {
-  "stakeholder.involvement.lead": "Chef",
+  "stakeholder.involvement.lead": "Responsable",
   "stakeholder.involvement.core": "Principal",
   "stakeholder.involvement.consulted": "Consulté",
   "stakeholder.business-owner.title": "Responsable métier",
-  "stakeholder.business-owner.description": "Représente les objectifs commerciaux, le financement et les résultats attendus pour l'initiative API.",
+  "stakeholder.business-owner.description": "Représente les objectifs métier, le financement et les résultats attendus de l'initiative de capacité.",
   "stakeholder.api-program-owner.title": "Responsable du programme API",
   "stakeholder.api-program-owner.description": "Coordonne les pratiques du portefeuille API, l'alignement organisationnel et le développement à long terme des capacités API.",
   "stakeholder.api-product-owner.title": "Propriétaire du produit API",
   "stakeholder.api-product-owner.description": "Piloter l'opportunité API, la priorisation et les décisions au niveau du produit tout au long du cycle de vie.",
-  "stakeholder.capability-owner.title": "Capability Owner",
-  "stakeholder.capability-owner.description": "",
+  "stakeholder.capability-owner.title": "Responsable de capacité",
+  "stakeholder.capability-owner.description": "Responsable de la vision, des objectifs, de la priorisation et de l'évolution de la capacité tout au long de son cycle de vie.",
   "stakeholder.domain-specialist.title": "Expert du domaine",
   "stakeholder.domain-specialist.description": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que l'API doit refléter.",
   "stakeholder.customer-specialist.title": "Représentant client ou partenaire",
@@ -17,33 +17,33 @@
   "stakeholder.api-consumer-specialist.title": "Représentant utilisateur API",
   "stakeholder.api-consumer-specialist.description": "Représente les besoins des développeurs, intégrateurs ou autres utilisateurs d'API qui utilisent l'API directement.",
   "stakeholder.platform-architect.title": "Architecte de la plateforme",
-  "stakeholder.platform-architect.description": "Orienté les décisions sur la plateforme, l'intégration, l'évolutivité et l'architecture qui façonnent la construction et l'exploitation de l'API.",
-  "stakeholder.api-architect.title": "API Architect",
-  "stakeholder.api-architect.description": "",
-  "stakeholder.integration-architect.title": "Integration Architect",
-  "stakeholder.integration-architect.description": "",
-  "stakeholder.platform-owner.title": "Platform Owner",
-  "stakeholder.platform-owner.description": "",
+  "stakeholder.platform-architect.description": "Oriente les décisions relatives à la plateforme, aux intégrations, à l'évolutivité et à l'architecture.",
+  "stakeholder.api-architect.title": "Architecte API",
+  "stakeholder.api-architect.description": "Responsable de l'architecture API, des principes de conception et de la qualité des contrats d'interface.",
+  "stakeholder.integration-architect.title": "Architecte d'intégration",
+  "stakeholder.integration-architect.description": "Conçoit les solutions et modèles d'intégration en cohérence avec l'architecture d'entreprise.",
+  "stakeholder.platform-owner.title": "Responsable de plateforme",
+  "stakeholder.platform-owner.description": "Responsable des capacités de la plateforme, de son évolution et de son exploitation.",
   "stakeholder.api-designer.title": "Designer API",
   "stakeholder.api-designer.description": "Conçoit le contrat API, le modèle d'interaction, la cohérence et l'utilisabilité des capacités exposées.",
   "stakeholder.api-engineer.title": "Ingénieur de livraison",
   "stakeholder.api-engineer.description": "Assume la responsabilité de l'implémentation, de l'automatisation, des tests et du flux de publication nécessaires pour livrer l'API de manière fiable.",
-  "stakeholder.automation-owner.title": "Automation Owner",
-  "stakeholder.automation-owner.description": "",
-  "stakeholder.process-owner.title": "Process Owner",
-  "stakeholder.process-owner.description": "",
-  "stakeholder.automation-engineer.title": "Automation Engineer",
-  "stakeholder.automation-engineer.description": "",
+  "stakeholder.automation-owner.title": "Responsable de l'automatisation",
+  "stakeholder.automation-owner.description": "Responsable des objectifs, de la priorisation et de la valeur métier des capacités d'automatisation.",
+  "stakeholder.process-owner.title": "Responsable de processus",
+  "stakeholder.process-owner.description": "Responsable des objectifs, de l'évolution et des résultats du processus métier.",
+  "stakeholder.automation-engineer.title": "Ingénieur automatisation",
+  "stakeholder.automation-engineer.description": "Met en œuvre, teste et exploite les solutions d'automatisation et leurs intégrations.",
   "stakeholder.security-specialist.title": "Spécialiste en sécurité",
   "stakeholder.security-specialist.description": "Assure que les risques de sécurité, les contrôles et les limites de confiance sont pris en compte tout au long du cycle de vie de l'API.",
   "stakeholder.compliance-specialist.title": "Spécialiste en conformité et juridique",
-  "stakeholder.compliance-specialist.description": "Clarifie les exigences légales, de confidentialité, réglementaires et contractuelles qui affectent l'API.",
-  "stakeholder.governance-specialist.title": "Propriétaire de la gouvernance",
+  "stakeholder.compliance-specialist.description": "Clarifie les exigences juridiques, de confidentialité et de conformité qui affectent la capacité ou l'interface.",
+  "stakeholder.governance-specialist.title": "Responsable gouvernance",
   "stakeholder.governance-specialist.description": "Représente les pratiques de revue, d'audit et de gouvernance à l'échelle de l'organisation pour la qualité et la conformité des API.",
-  "stakeholder.api-devrel-specialist.title": "Propriétaire de la documentation et du développement communautaire",
-  "stakeholder.api-devrel-specialist.description": "Possède le contenu d'intégration, la communication avec les développeurs et la qualité de la documentation pour les utilisateurs d'API.",
+  "stakeholder.api-devrel-specialist.title": "Responsable Documentation & DevRel",
+  "stakeholder.api-devrel-specialist.description": "Responsable des contenus d'onboarding, de la communication avec les développeurs et de la qualité de la documentation API.",
   "stakeholder.operations-specialist.title": "Propriétaire du support et des opérations",
   "stakeholder.operations-specialist.description": "Représente le support en production, la gestion des incidents, l'observabilité et la préparation opérationnelle.",
   "stakeholder.partner-specialist.title": "Gestionnaire de partenaires ou de fournisseurs",
-  "stakeholder.partner-specialist.description": "Coordonne les relations avec les partenaires externes, les fournisseurs ou les vendeurs qui influencent la stratégie et la livraison de l'API."
-}
+  "stakeholder.partner-specialist.description": "Coordonne les relations avec les partenaires et fournisseurs qui influencent la stratégie et la mise en œuvre de la capacité."
+}
\ No newline at end of file
diff --git a/src/data/method/fr/labels.stations.json b/src/data/method/fr/labels.stations.json
index 48b3f9b..30b6cd2 100644
--- a/src/data/method/fr/labels.stations.json
+++ b/src/data/method/fr/labels.stations.json
@@ -1,61 +1,61 @@
 {
-  "group.core-stations.title": "Stations centrales du cycle de vie de l'API",
-  "group.core-stations.description": "Les stations centrales de l'API Metro, où les équipes peuvent apprendre à créer et à gérer des API de manière efficace.",
-  "group.sub-stations.title": "Sous-stations du cycle de vie de l'API",
-  "group.sub-stations.description": "Sous-stations qui fournissent des ressources supplémentaires, des outils et des meilleures pratiques pour les équipes API.",
-  "station.api-product-strategy.title": "Stratégie produit API - Transformer les API en produits stratégiques",
-  "station.api-product-strategy.description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs commerciaux.",
-  "station.api-product-strategy.why_it_matters": "De nombreuses organisations considèrent les API comme des projets technologiques et non comme des produits. Le résultat ? Des consommateurs désorientés, une adoption médiocre et un gaspillage d'efforts.\n\nCette station vous aide à définir l'objectif, le public cible et les critères de réussite de votre API, afin que les équipes puissent fournir des API qui résolvent des problèmes réels.",
-  "station.api-product-strategy.apply_in_work": "Fournir des lignes directrices et des modèles pour la création de modèles commerciaux, de propositions de valeur et de feuilles de route pour les API.",
-  "station.api-product-strategy.outcomes": "Une proposition de valeur et un public simples pour l'API",
-  "station.api-product-strategy.how_it_works": "Explorez le problème du client ou du partenaire que vous comptez résoudre avec les API. Dressez la carte des parties prenantes, de leurs parcours et de leurs résultats à l'aide du Customer Journey canvas.",
-  "station.api-consumer-experience.title": "API Consumer Experience - Concevoir pour les vrais utilisateurs de votre API",
-  "station.api-consumer-experience.description": "Veillez à ce que votre API soit découvrable, compréhensible et utilisable - avant et après le lancement.",
-  "station.api-consumer-experience.why_it_matters": "Les meilleures API ne se contentent pas de fonctionner, elles sont intuitives. Que votre consommateur soit un développeur interne, un partenaire externe ou un agent d'intelligence artificielle, c'est son expérience qui détermine l'adoption.\n\nSans un plan d'expérience clair :\n- Les meilleures API restent inutilisées\n- Les équipes perdent du temps à deviner comment utiliser votre API.\n- Les boucles de rétroaction sont brisées ou manquantes.\n\nCette station vous aide à voir votre API à travers les yeux de ses consommateurs.",
-  "station.api-consumer-experience.how_it_works": "Examinez l'API Value Proposition Canvas du point de vue de l'utilisateur. Veillez à la stabilité des tâches métier prises en charge et enrichissez les fonctionnalités qui simplifient et optimisent l'expérience utilisateur en intégrant les préoccupations des utilisateurs afin d'orienter les décisions de conception ultérieures.",
-  "station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur de l'API, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
-  "station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur de l'API.",
-  "station.api-consumer-experience.apply_in_work": "Fournir des lignes directrices, des outils et des mécanismes de retour d'information pour comprendre, analyser et améliorer l'expérience interne et externe des développeurs et des partenaires.",
-  "station.api-consumer-experience.outcomes": "Identifier et hiérarchiser les consommateurs d'API",
-  "station.api-platform-architecture.title": "Architecture de la plateforme API - Architecturer les API pour l'évolutivité et la réutilisation",
-  "station.api-platform-architecture.description": "Assurez l'évolutivité, la réutilisation et la gouvernance de vos composants d'API et de plateforme.",
-  "station.api-platform-architecture.why_it_matters": "Lorsque les API s'étendent à plusieurs équipes, votre plateforme doit permettre la gouvernance et la réutilisation sans bloquer la vitesse. Cette station montre comment architecturer les API pour assurer leur longévité, leur sécurité et leur efficacité.",
-  "station.api-platform-architecture.apply_in_work": "Mettre en place une infrastructure évolutive, sécurisée et conforme pour les opérations API. Fournir des lignes directrices sur les meilleures pratiques en matière d'architecture.",
-  "station.api-platform-architecture.outcomes": "Supprimer les API redondantes et réduire les coûts de la plateforme en nuage",
-  "station.api-platform-architecture.how_it_works": "Le Business Impact Canvas permet d'identifier et d'atténuer les risques liés à la disponibilité, à la sécurité et à la fonctionnalité de l'API afin de prendre des décisions éclairées en matière d'architecture.",
-  "station.api-design.title": "Conception d'API - Concevoir des API qui apportent de la valeur",
-  "station.api-design.description": "Créer des architectures d'API cohérentes, réutilisables et fondées sur les objectifs métier et des normes communes.",
-  "station.api-design.why_it_matters": "La conception d'API ne se limite pas à nommer des points de terminaison. Une bonne conception garantit que les API sont utilisables, cohérentes et alignées sur les objectifs métier et techniques. Une mauvaise conception entraîne un couplage étroit, une faible réutilisation et des retouches coûteuses entre les équipes.",
-  "station.api-design.apply_in_work": "Fournir des modèles de conception réutilisables, des normes communes et des outils de validation pour les spécifications d'API. S'assurer que les décisions de conception sont cohérentes, examinées dès le début et alignées sur les objectifs métier.",
-  "station.api-design.outcomes": "Des conceptions d'API bien documentées et cohérentes",
-  "station.api-design.how_it_works": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.",
-  "station.api-delivery.title": "Livraison d'API - Fournir des API sécurisées et fiables",
-  "station.api-delivery.description": "Construire, tester et publier des API en utilisant des pipelines de livraison modernes et les meilleures pratiques d'ingénierie.",
-  "station.api-delivery.why_it_matters": "Même les meilleures conceptions d'API échouent si la livraison est incohérente. Cette station garantit que vos API sont construites avec qualité, testées de manière approfondie et déployées de manière fiable, ce qui permet des itérations plus rapides et une plus grande confiance.",
-  "station.api-delivery.apply_in_work": "Fournir des cadres de codage, des bibliothèques et des normes pour la mise en œuvre des API. Mettre en œuvre des pipelines CI/CD, des cadres d'assurance qualité et des outils d'automatisation du déploiement.",
-  "station.api-delivery.outcomes": "API mises en œuvre à l'aide de cadres et de modèles testés",
-  "station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
-  "station.api-audit.title": "Audit API - Audit de conformité et de qualité des API",
-  "station.api-audit.description": "Vérifiez que les API répondent aux normes métier, de conception et opérationnelles avant leur publication et leur mise à disposition.",
-  "station.api-audit.why_it_matters": "Les API sont des produits à longue durée de vie et doivent répondre aux attentes en matière de qualité, de cohérence et de conformité. L'audit relie les décisions de conception, la mise en œuvre et l'état de préparation opérationnelle à des normes définies, réduisant ainsi les risques avant la mise à disposition.",
-  "station.api-audit.apply_in_work": "Mettez en place un processus d'audit cohérent qui évalue l'état de préparation des API à toutes les étapes du cycle de vie à l'aide de critères, de preuves et de normes définis. Assurez-vous que les lacunes sont identifiées tôt et résolues avant la publication.",
-  "station.api-audit.outcomes": "Les API sont conformes aux normes internes et externes",
-  "station.api-audit.how_it_works": "Mener des audits pour s'assurer que les API respectent les normes organisationnelles, techniques et juridiques avant d'être publiées.",
-  "station.api-publishing.title": "Publication d'API - Publier des API en toute confiance",
-  "station.api-publishing.description": "Exposer les API de manière sûre et claire au bon public avec la bonne documentation et les bons processus.",
-  "station.api-publishing.why_it_matters": "La publication va plus loin que le déploiement - il s'agit de la découvrabilité, de l'accès et de l'assistance. Si les API ne sont pas publiées correctement, elles ne seront pas utilisées, réutilisées ou sécurisées efficacement.",
-  "station.api-publishing.apply_in_work": "Permettre aux API d'être publiées dans l'environnement approprié et disposer de mécanismes d'enregistrement et d'accès clairs (par exemple, clés API, OAuth, plans d'abonnement) en fonction des segments de consommateurs d'API et des exigences en matière de sécurité et de conformité.",
-  "station.api-publishing.outcomes": "API publiées dans le bon environnement (privé, partenaire, public)",
-  "station.api-publishing.how_it_works": "Publier les API dans les passerelles et les environnements appropriés afin de favoriser la réutilisation pour de multiples consommateurs d'API.",
-  "station.monitoring-and-improving.title": "Suivi et amélioration - pour la valeur de l'API",
-  "station.monitoring-and-improving.description": "Utiliser les mesures et le retour d'information pour suivre les performances de l'API et favoriser l'amélioration continue.",
-  "station.monitoring-and-improving.why_it_matters": "La livraison d'API ne s'arrête pas au lancement. Sans surveillance, les équipes ne peuvent pas améliorer l'adoption, les performances ou le retour sur investissement. Cette station garantit que les API restent utiles, sécurisées et qu'elles évoluent avec les besoins de l'entreprise.",
-  "station.monitoring-and-improving.apply_in_work": "Mettre en place des cadres d'analyse pour suivre les performances et l'engagement. Développer des boucles de rétroaction, des outils d'analyse et des stratégies d'engagement pour les API.",
-  "station.monitoring-and-improving.outcomes": "Définition et suivi des indicateurs de performance et d'utilisation",
-  "station.monitoring-and-improving.how_it_works": "Contrôler les indicateurs de performance (par exemple, les appels à l'API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
+  "group.core-stations.title": "Stations centrales du cycle de vie des capacités",
+  "group.core-stations.description": "Les stations centrales du graphe de méthode APIOps Cycles, où les équipes apprennent à concevoir, fournir, gouverner et améliorer des capacités réutilisables via des API, événements, fichiers, flux, produits de données et autres modes d'intégration.",
+  "group.sub-stations.title": "Stations de soutien",
+  "group.sub-stations.description": "Stations de soutien qui fournissent des pratiques, points de décision et ressources réutilisables dans différents parcours APIOps Cycles.",
+  "station.api-product-strategy.title": "Stratégie de capacité",
+  "station.api-product-strategy.description": "Décrivez le besoin métier comme une capacité réutilisable avant de choisir le mode de mise en œuvre.",
+  "station.api-product-strategy.why_it_matters": "Les initiatives d'intégration et d'API passent souvent trop vite à un choix technique. Cette station maintient l'équipe concentrée sur le parcours métier, le domaine, la valeur, le potentiel de réutilisation, la responsabilité et la faisabilité avant de choisir API, événements, fichiers, flux, produits de données ou intégration directe.",
+  "station.api-product-strategy.apply_in_work": "Utilisez des canvases de parcours, de domaine, de proposition de valeur et de modèle métier pour capturer les exigences indépendamment de la technologie et décider si la capacité doit être réutilisable.",
+  "station.api-product-strategy.outcomes": "Une opportunité de capacité indépendante de la technologie",
+  "station.api-product-strategy.how_it_works": "Analysez le parcours client ou partenaire d'où émerge le besoin de capacité, puis identifiez les tâches, irritants, gains, entrées, sorties et points de décision.",
+  "station.api-consumer-experience.title": "Exigences utilisateurs & onboarding",
+  "station.api-consumer-experience.description": "Capturez les exigences des utilisateurs, l'onboarding, les standards, les exigences non fonctionnelles, les attentes de service, les contraintes, la sécurité, les protocoles, la fraîcheur des données, les SLA, l'observabilité, la reprise, l'adoption et les responsabilités des fournisseurs.",
+  "station.api-consumer-experience.why_it_matters": "La bonne architecture dépend des objectifs des utilisateurs, des attentes d'onboarding, des niveaux de service, de la qualité des données, de la tolérance au changement, de l'observabilité, du support et des contraintes du fournisseur.",
+  "station.api-consumer-experience.how_it_works": "Utilisez le Consumer Experience Requirements Canvas pour documenter objectifs utilisateurs, disponibilité, fraîcheur, volumes, performance, qualité des données, sécurité, onboarding, changements, observabilité et attentes de reprise.",
+  "station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
+  "station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur.",
+  "station.api-consumer-experience.apply_in_work": "Utilisez les ressources d'expérience utilisateur et d'onboarding pour rendre explicites les attentes des utilisateurs et des fournisseurs.",
+  "station.api-consumer-experience.outcomes": "Exigences utilisateurs et attentes d'onboarding explicites",
+  "station.api-platform-architecture.title": "Architecture & décisions de plateforme",
+  "station.api-platform-architecture.description": "Utilisez les exigences et contraintes pour choisir l'architecture, les capacités de plateforme, la gouvernance et le modèle opérationnel.",
+  "station.api-platform-architecture.why_it_matters": "Une capacité réutilisable nécessite des décisions d'architecture alignées sur les exigences utilisateurs, la sécurité, les flux de données, le modèle opérationnel et la réalité des plateformes existantes.",
+  "station.api-platform-architecture.apply_in_work": "Utilisez les ressources d'architecture et de plateforme pour comparer les options de mise en œuvre viables et prendre une décision traçable.",
+  "station.api-platform-architecture.outcomes": "Décision d'architecture et de plateforme validée",
+  "station.api-platform-architecture.how_it_works": "Utilisez les ressources Business Impact, Capacity, Security et Architecture Decision pour évaluer systématiquement les risques, contraintes et alternatives.",
+  "station.api-design.title": "Conception de solution & d'interface",
+  "station.api-design.description": "Concevez le mode de mise en œuvre choisi, le contrat d'interface, les modèles d'interaction, les structures de données et les détails d'utilisation avant l'implémentation.",
+  "station.api-design.why_it_matters": "Une bonne conception va au-delà du nommage des endpoints. Elle garantit que l'interface est utilisable, cohérente, vérifiable et traçable aux besoins métier et utilisateurs.",
+  "station.api-design.apply_in_work": "Utilisez les ressources de conception adaptées au mode de mise en œuvre choisi, par exemple REST, GraphQL, événements, fichiers, produits de données ou intégration directe.",
+  "station.api-design.outcomes": "Un contrat d'interface validé pour le mode de mise en œuvre choisi",
+  "station.api-design.how_it_works": "Clarifiez les objets métier, les termes, les règles et les responsabilités avant de concevoir le contrat d'interface.",
+  "station.api-delivery.title": "Mise à disposition & opérations",
+  "station.api-delivery.description": "Mettez en œuvre le mode choisi avec des pratiques adaptées d'ingénierie, de test, de sécurité, d'automatisation et d'exploitation.",
+  "station.api-delivery.why_it_matters": "Une capacité réutilisable a besoin d'une mise à disposition et d'un fonctionnement fiables, qu'elle soit réalisée sous forme d'API, de flux d'événements, d'échange de fichiers, de produit de données ou d'intégration directe.",
+  "station.api-delivery.apply_in_work": "Appliquez les pratiques de mise en œuvre, de test, de CI/CD, d'exploitation et de sécurité au mode de mise en œuvre choisi.",
+  "station.api-delivery.outcomes": "Une capacité livrée conformément au contrat d'interface validé",
+  "station.api-delivery.how_it_works": "Utilisez les pratiques de développement pour implémenter le contrat d'interface validé avec les frameworks, bibliothèques et standards d'équipe établis.",
+  "station.api-audit.title": "Assurance qualité & préparation",
+  "station.api-audit.description": "Vérifiez le contrat d'interface, les contrôles, le modèle de support, l'observabilité, la documentation et la préparation du cycle de vie avant publication.",
+  "station.api-audit.why_it_matters": "Les capacités réutilisables créent des risques opérationnels, liés aux données, à la sécurité, à la confidentialité, à la conformité et à l'expérience utilisateur. Les revues de préparation réduisent les surprises avant la publication ou l'utilisation en production.",
+  "station.api-audit.apply_in_work": "Utilisez les ressources d'audit et de conformité pour vérifier que la capacité peut être publiée et réutilisée de manière contrôlée.",
+  "station.api-audit.outcomes": "Préparation documentée pour la publication et la réutilisation",
+  "station.api-audit.how_it_works": "Utilisez des checklists, linters, tests et revues pour vérifier cohérence, standards, sécurité, performance et conformité.",
+  "station.api-publishing.title": "Publication & enablement",
+  "station.api-publishing.description": "Publiez les informations de capacité afin que les utilisateurs puissent la trouver, l'évaluer, demander l'accès, s'onboarder, l'utiliser et obtenir du support.",
+  "station.api-publishing.why_it_matters": "Une capacité réutilisable ne crée de la valeur que si les utilisateurs peuvent la trouver, comprendre le contrat d'interface et les attentes de service, demander l'accès et connaître le support ainsi que la responsabilité du cycle de vie.",
+  "station.api-publishing.apply_in_work": "Publiez la responsabilité, la documentation, l'onboarding, les contacts support, les attentes de service, le statut de cycle de vie et les chemins d'accès.",
+  "station.api-publishing.outcomes": "Une capacité découvrable et utilisable",
+  "station.api-publishing.how_it_works": "Publiez les informations de capacité dans les catalogues, portails, passerelles ou environnements appropriés afin que plusieurs utilisateurs puissent la réutiliser.",
+  "station.monitoring-and-improving.title": "Suivi & amélioration",
+  "station.monitoring-and-improving.description": "Suivez l'utilisation, la fiabilité, la qualité des données, les résultats utilisateurs, les coûts opérationnels et les opportunités de réutilisation après publication.",
+  "station.monitoring-and-improving.why_it_matters": "Les capacités ont besoin de retours continus pour rester fiables, utiles, économiquement pertinentes et réutilisables lorsque les utilisateurs, systèmes, données et plateformes évoluent.",
+  "station.monitoring-and-improving.apply_in_work": "Utilisez des métriques, analyses et pratiques de feedback pour améliorer continuellement la capacité.",
+  "station.monitoring-and-improving.outcomes": "Santé et contribution de valeur de la capacité mesurées",
+  "station.monitoring-and-improving.how_it_works": "Définissez des métriques d'utilisation, fiabilité, qualité des données, coût, adoption et valeur utilisateur.",
   "station.user-experience.title": "Expérience utilisateur - Concevoir des API en pensant à l'utilisateur",
   "station.user-experience.description": "Veiller à ce que les API soient conçues en pensant à l'utilisateur final, en lui offrant une expérience transparente et intuitive.",
-  "station.user-experience.why_it_matters": "Les API ne sont pas seulement des produits techniques, ce sont des produits orientés vers l'utilisateur. Une mauvaise expérience utilisateur peut entraîner une faible adoption et de la frustration. Cette station aide les équipes à concevoir des API conviviales et répondant aux besoins des consommateurs.",
+  "station.user-experience.why_it_matters": "Les API ne sont pas seulement des produits techniques, ce sont des produits orientés vers l'utilisateur. Une mauvaise expérience utilisateur peut entraîner une faible adoption et de la frustration. Cette station aide les équipes à concevoir des API conviviales et répondant aux besoins des utilisateurs.",
   "station.user-experience.apply_in_work": "Fournir des lignes directrices, des modèles et des outils en matière d'expérience utilisateur pour la conception d'API. Veiller à ce que les équipes suivent des pratiques de conception centrées sur l'utilisateur et intègrent les commentaires des utilisateurs dans les itérations de l'API.",
   "station.user-experience.outcomes": "Des API conçues en fonction des besoins des utilisateurs",
   "station.user-experience.how_it_works": "Utiliser des profils d'utilisateurs pour comprendre les besoins et les attentes des utilisateurs finaux.",
@@ -68,7 +68,7 @@
   "station.business-goals.title": "Objectifs de l'entreprise - Aligner les API sur les objectifs de l'entreprise",
   "station.business-goals.description": "Veiller à ce que les API soient alignées sur les objectifs de l'entreprise et contribuent aux objectifs généraux de l'organisation.",
   "station.business-goals.why_it_matters": "Les API ne doivent pas être conçues de manière isolée ; elles doivent soutenir et stimuler les objectifs de l'entreprise. Cette station aide les équipes à aligner leurs API sur les objectifs stratégiques, en veillant à ce qu'elles apportent une réelle valeur ajoutée à l'entreprise.",
-  "station.business-goals.apply_in_work": "Fournir des cadres, des modèles et des outils d'alignement commercial pour définir la valeur commerciale des API. Veiller à ce que les équipes examinent et alignent régulièrement les API sur l'évolution des objectifs de l'entreprise.",
+  "station.business-goals.apply_in_work": "Fournir des cadres, des modèles et des outils d'alignement commercial pour définir la valeur métier des API. Veiller à ce que les équipes examinent et alignent régulièrement les API sur l'évolution des objectifs de l'entreprise.",
   "station.business-goals.outcomes": "Des API alignées sur les objectifs de l'entreprise",
   "station.business-goals.how_it_works": "Définissez les objectifs de l'entreprise et la manière dont les API peuvent les soutenir en utilisant **le Business Model Canvas**. Si votre activité consiste à fournir des API, passez par *la station API Product Strategy* et remplissez **l'API Business Model Canvas**.",
   "station.competitive-analysis.title": "Analyse concurrentielle - Garder une longueur d'avance sur le marché des API",
@@ -109,20 +109,20 @@
   "station.design-standards.how_it_works": "Définir des normes et des lignes directrices pour la conception des API, y compris les conventions de dénomination, les formats de réponse et la gestion des erreurs.",
   "station.vendor-management.title": "Gestion des fournisseurs - Gestion des intégrations d'API de tiers",
   "station.vendor-management.description": "Gérer efficacement les fournisseurs d'API tiers et les intégrations pour garantir la fiabilité et la conformité.",
-  "station.vendor-management.why_it_matters": "Les API tierces peuvent présenter des risques et des dépendances qui ont un impact sur votre écosystème d'API. Ce poste fournit des lignes directrices pour gérer les relations avec les fournisseurs, garantir la fiabilité, la conformité et l'alignement sur votre stratégie d'API.",
+  "station.vendor-management.why_it_matters": "Les API tierces peuvent présenter des risques et des dépendances qui ont un impact sur votre écosystème d'API. Ce station fournit des lignes directrices pour gérer les relations avec les fournisseurs, garantir la fiabilité, la conformité et l'alignement sur votre stratégie d'API.",
   "station.vendor-management.apply_in_work": "Fournir des cadres de gestion des fournisseurs, des critères d'évaluation et des outils de suivi. Veiller à ce que les équipes gèrent efficacement les fournisseurs d'API tiers, en garantissant la fiabilité, la conformité et l'alignement sur les normes de l'organisation.",
   "station.vendor-management.outcomes": "Mise en place de processus efficaces de gestion des fournisseurs",
   "station.vendor-management.how_it_works": "Mettre en place des processus de gestion des fournisseurs afin d'évaluer, d'intégrer et de contrôler les fournisseurs d'API tiers.",
   "station.contract-design.title": "Conception des contrats - Définir des contrats API clairs",
-  "station.contract-design.description": "Créer des contrats d'API clairs et bien définis qui décrivent les attentes, les responsabilités et les directives d'utilisation.",
-  "station.contract-design.why_it_matters": "Les contrats d'API sont essentiels pour garantir la clarté et l'alignement entre les fournisseurs d'API et les consommateurs. Cette station fournit des lignes directrices pour la conception de contrats d'API clairs, complets et faciles à comprendre.",
-  "station.contract-design.apply_in_work": "Fournir des modèles de conception de contrats, des formats normalisés et des processus d'examen. Veiller à ce que les équipes créent des contrats d'API clairs et bien définis qui décrivent les attentes, les responsabilités et les directives d'utilisation.",
-  "station.contract-design.outcomes": "Contrats d'API clairs définis pour chaque API",
-  "station.contract-design.how_it_works": "Définir des contrats d'API qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
+  "station.contract-design.description": "Créer des contrats d'interface clairs et bien définis qui décrivent les attentes, les responsabilités et les directives d'utilisation.",
+  "station.contract-design.why_it_matters": "Les contrats d'interface sont essentiels pour garantir la clarté et l'alignement entre les fournisseurs d'API et les utilisateurs. Cette station fournit des lignes directrices pour la conception de contrats d'interface clairs, complets et faciles à comprendre.",
+  "station.contract-design.apply_in_work": "Fournir des modèles de conception de contrats, des formats normalisés et des processus d'examen. Veiller à ce que les équipes créent des contrats d'interface clairs et bien définis qui décrivent les attentes, les responsabilités et les directives d'utilisation.",
+  "station.contract-design.outcomes": "Contrats d'interface clairs définis pour chaque API",
+  "station.contract-design.how_it_works": "Définir des contrats d'interface qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
   "station.development.title": "Développement - Construire des API avec les meilleures pratiques",
   "station.development.description": "Mettre en œuvre des API en utilisant les meilleures pratiques et les meilleurs cadres afin de garantir la qualité, la maintenabilité et l'évolutivité.",
   "station.development.why_it_matters": "Le développement de l'API est une phase critique qui détermine la qualité et la fiabilité de l'API. Cette station fournit les meilleures pratiques et les cadres pour le développement d'API, garantissant que les API sont construites selon des normes élevées et qu'elles peuvent être maintenues et mises à l'échelle efficacement.",
-  "station.development.apply_in_work": "Fournir des cadres de développement, des bibliothèques et des normes de codage pour la mise en œuvre de l'API. Veiller à ce que les équipes suivent les meilleures pratiques et effectuent des révisions de code afin de maintenir un développement d'API de haute qualité.",
+  "station.development.apply_in_work": "Fournir des frameworks de développement, des bibliothèques et des normes de codage pour la mise en œuvre de l'API. Veiller à ce que les équipes suivent les meilleures pratiques et effectuent des révisions de code afin de maintenir un développement d'API de haute qualité.",
   "station.development.outcomes": "API développées à l'aide des meilleures pratiques et des meilleurs cadres",
   "station.development.how_it_works": "Utiliser des cadres et des bibliothèques établis pour mettre en œuvre les API, en veillant à ce qu'elles soient réutilisables et faciles à entretenir.",
   "station.ci-cd.title": "CI/CD - Automatiser la livraison des API",
@@ -144,17 +144,17 @@
   "station.release-management.outcomes": "Des versions contrôlées et fluides de l'API",
   "station.release-management.how_it_works": "Définir des stratégies de versionnement pour les API afin de gérer les changements et d'assurer la compatibilité ascendante.",
   "station.service-agreements.title": "Accords de service - Définir les niveaux de service de l'API",
-  "station.service-agreements.description": "Établir des accords de service qui définissent les attentes, les niveaux de service et les responsabilités des fournisseurs et des consommateurs d'API.",
-  "station.service-agreements.why_it_matters": "Les accords de service sont essentiels pour garantir la clarté et l'alignement entre les fournisseurs d'API et les consommateurs. Cette station fournit des lignes directrices pour la création d'accords de service qui décrivent les attentes, les niveaux de service et les responsabilités, réduisant ainsi les malentendus et les litiges.",
-  "station.service-agreements.apply_in_work": "Fournir des modèles d'accords de service, des formats normalisés et des processus d'examen. Veiller à ce que les équipes créent des accords de service clairs et bien définis qui décrivent les attentes, les niveaux de service et les responsabilités des fournisseurs d'API et des consommateurs.",
+  "station.service-agreements.description": "Établir des accords de service qui définissent les attentes, les niveaux de service et les responsabilités des fournisseurs et des utilisateurs.",
+  "station.service-agreements.why_it_matters": "Les accords de service sont essentiels pour garantir la clarté et l'alignement entre les fournisseurs d'API et les utilisateurs. Cette station fournit des lignes directrices pour la création d'accords de service qui décrivent les attentes, les niveaux de service et les responsabilités, réduisant ainsi les malentendus et les litiges.",
+  "station.service-agreements.apply_in_work": "Fournir des modèles d'accords de service, des formats normalisés et des processus d'examen. Veiller à ce que les équipes créent des accords de service clairs et bien définis qui décrivent les attentes, les niveaux de service et les responsabilités des fournisseurs d'API et des utilisateurs.",
   "station.service-agreements.outcomes": "Des accords de service clairs définis pour chaque API",
   "station.service-agreements.how_it_works": "Définir des accords de service qui décrivent les attentes, les niveaux de service et les responsabilités pour chaque API.",
-  "station.api-consumer-adoption.title": "Adoption de l'API par les consommateurs - Favoriser l'utilisation de l'API",
+  "station.api-consumer-adoption.title": "Adoption de l'API par les utilisateurs - Favoriser l'utilisation de l'API",
   "station.api-consumer-adoption.description": "Mettre en œuvre des stratégies visant à favoriser l'adoption et l'engagement des utilisateurs d'API, en veillant à ce que les API soient utilisées efficacement.",
-  "station.api-consumer-adoption.why_it_matters": "Il est essentiel de favoriser l'adoption par les consommateurs d'API pour réaliser la valeur des API. Cette station fournit des stratégies et des meilleures pratiques pour engager les consommateurs d'API, en s'assurant qu'ils comprennent comment utiliser efficacement les API et en tirer de la valeur.",
-  "station.api-consumer-adoption.apply_in_work": "Fournir des ressources d'accueil, du matériel pédagogique et des stratégies d'engagement pour les consommateurs d'API. Veiller à ce que les équipes mettent en œuvre des stratégies qui favorisent l'adoption, l'engagement et la satisfaction des consommateurs d'API.",
-  "station.api-consumer-adoption.outcomes": "Mise en œuvre de stratégies d'adoption de l'API par les consommateurs",
-  "station.api-consumer-adoption.how_it_works": "Développer des processus et des ressources d'intégration pour aider les consommateurs d'API à comprendre comment utiliser efficacement les API.",
+  "station.api-consumer-adoption.why_it_matters": "Il est essentiel de favoriser l'adoption par les utilisateurs pour réaliser la valeur des API. Cette station fournit des stratégies et des meilleures pratiques pour engager les utilisateurs, en s'assurant qu'ils comprennent comment utiliser efficacement les API et en tirer de la valeur.",
+  "station.api-consumer-adoption.apply_in_work": "Fournir des ressources d'accueil, du matériel pédagogique et des stratégies d'engagement pour les utilisateurs. Veiller à ce que les équipes mettent en œuvre des stratégies qui favorisent l'adoption, l'engagement et la satisfaction des utilisateurs.",
+  "station.api-consumer-adoption.outcomes": "Mise en œuvre de stratégies d'adoption de l'API par les utilisateurs",
+  "station.api-consumer-adoption.how_it_works": "Développer des processus et des ressources d'intégration pour aider les utilisateurs à comprendre comment utiliser efficacement les API.",
   "station.api-promotion.title": "Promotion de l'API - Augmenter la visibilité et l'utilisation de l'API",
   "station.api-promotion.description": "Promouvoir les API afin d'accroître la visibilité, l'utilisation et l'adoption parmi les publics cibles.",
   "station.api-promotion.why_it_matters": "La promotion des API est essentielle pour accroître leur visibilité et favoriser leur utilisation. Cette station propose des stratégies et des bonnes pratiques pour promouvoir efficacement les API auprès des publics cibles, en veillant à ce qu'ils connaissent les API et comprennent leur valeur.",
@@ -172,11 +172,11 @@
   "station.api-mindset.why_it_matters": "Un état d'esprit axé sur les API est essentiel pour favoriser l'innovation et la collaboration au sein de l'entreprise. Cette station fournit des stratégies pour cultiver une culture API-first, en veillant à ce que les API soient considérées comme des actifs stratégiques qui génèrent de la valeur pour l'entreprise.",
   "station.api-mindset.apply_in_work": "Fournir des programmes de formation, des ressources et des stratégies de communication pour favoriser une culture de l'API. S'assurer que les équipes comprennent la valeur des API et sont habilitées à conduire la stratégie et les initiatives en matière d'API.",
   "station.api-mindset.outcomes": "Culture de la priorité aux API établie dans l'ensemble de l'organisation",
-  "station.api-mindset.how_it_works": "Promouvoir la valeur des API en tant qu'actifs stratégiques qui génèrent de la valeur commerciale et de l'innovation.",
+  "station.api-mindset.how_it_works": "Promouvoir la valeur des API en tant qu'actifs stratégiques qui génèrent de la valeur métier et de l'innovation.",
   "station.roles-and-responsibilities.title": "Rôles et responsabilités - Définir les structures de l'équipe API",
   "station.roles-and-responsibilities.description": "Définir clairement les rôles et les responsabilités des équipes chargées de l'API afin de garantir une collaboration et une responsabilisation efficaces.",
   "station.roles-and-responsibilities.why_it_matters": "Des rôles et des responsabilités clairs sont essentiels pour une collaboration et une responsabilisation efficaces au sein des équipes de l'API. Cette station fournit des lignes directrices pour définir les structures, les rôles et les responsabilités des équipes, en veillant à ce que chacun comprenne sa contribution aux initiatives de l'API.",
-  "station.roles-and-responsibilities.apply_in_work": "Fournir des lignes directrices sur la structure des équipes, des définitions des rôles et des stratégies de communication. Veiller à ce que les équipes aient des rôles et des responsabilités clairs qui favorisent une collaboration et une responsabilisation efficaces dans le cadre des initiatives de l'IPA.",
+  "station.roles-and-responsibilities.apply_in_work": "Fournir des lignes directrices sur la structure des équipes, des définitions des rôles et des stratégies de communication. Veiller à ce que les équipes aient des rôles et des responsabilités clairs qui favorisent une collaboration et une responsabilisation efficaces dans le cadre des initiatives de l'API.",
   "station.roles-and-responsibilities.outcomes": "Rôles et responsabilités clairement définis pour les équipes API",
   "station.roles-and-responsibilities.how_it_works": "Définir les structures et les rôles des équipes API, y compris les propriétaires de produits API, les développeurs, les architectes et les opérations.",
   "station.upskilling.title": "Upkilling - Améliorer les compétences et les connaissances en matière d'API",
@@ -193,38 +193,38 @@
   "station.operating-guidelines.how_it_works": "Définir des lignes directrices opérationnelles basées sur les cycles APIOps qui décrivent les processus, les normes et les meilleures pratiques pour la gestion de l'API.",
   "station.portfolio-management.title": "Gestion de portefeuille - Gérer efficacement le portefeuille d'API",
   "station.portfolio-management.description": "Gérer efficacement le portefeuille d'API afin de garantir l'alignement sur les objectifs de l'entreprise et les initiatives stratégiques.",
-  "station.portfolio-management.why_it_matters": "Une gestion efficace du portefeuille d'API est essentielle pour garantir que les API s'alignent sur les objectifs de l'entreprise et les initiatives stratégiques. Ce poste fournit des lignes directrices pour la gestion du portefeuille d'API, en veillant à ce que les API soient classées par ordre de priorité, contrôlées et optimisées pour offrir une valeur maximale.",
+  "station.portfolio-management.why_it_matters": "Une gestion efficace du portefeuille d'API est essentielle pour garantir que les API s'alignent sur les objectifs de l'entreprise et les initiatives stratégiques. Ce station fournit des lignes directrices pour la gestion du portefeuille d'API, en veillant à ce que les API soient classées par ordre de priorité, contrôlées et optimisées pour offrir une valeur maximale.",
   "station.portfolio-management.apply_in_work": "Fournir des cadres de gestion de portefeuille, des critères de priorisation et des outils de suivi pour la gestion des API. Veiller à ce que les équipes gèrent efficacement le portefeuille d'API, en assurant l'alignement sur les objectifs de l'entreprise, les initiatives stratégiques et la fourniture d'une valeur maximale.",
   "station.portfolio-management.outcomes": "Mise en place de pratiques de gestion du portefeuille API",
   "station.portfolio-management.how_it_works": "Définir des pratiques de gestion de portefeuille qui décrivent les processus de gestion du portefeuille d'API, y compris l'établissement de priorités, le suivi et l'optimisation.",
   "station.budget-and-resource-management.title": "Gestion du budget et des ressources - Optimiser les investissements dans l'API",
   "station.budget-and-resource-management.description": "Optimiser la gestion du budget et des ressources pour les initiatives API afin de garantir l'efficacité des investissements et de l'affectation des ressources.",
-  "station.budget-and-resource-management.why_it_matters": "Une gestion efficace du budget et des ressources est essentielle pour garantir que les initiatives en matière d'API sont bien financées et disposent des ressources nécessaires. Ce poste fournit des lignes directrices pour optimiser la gestion du budget et des ressources, en veillant à ce que les initiatives en matière d'API soient alignées sur les objectifs de l'entreprise et apportent une valeur maximale.",
+  "station.budget-and-resource-management.why_it_matters": "Une gestion efficace du budget et des ressources est essentielle pour garantir que les initiatives en matière d'API sont bien financées et disposent des ressources nécessaires. Ce station fournit des lignes directrices pour optimiser la gestion du budget et des ressources, en veillant à ce que les initiatives en matière d'API soient alignées sur les objectifs de l'entreprise et apportent une valeur maximale.",
   "station.budget-and-resource-management.apply_in_work": "Fournir des cadres de gestion budgétaire, des critères de priorisation et des outils de suivi pour les initiatives API. Veiller à ce que les équipes gèrent efficacement les budgets et les ressources, en optimisant les investissements dans le développement et la gestion des API afin d'obtenir une valeur maximale.",
   "station.budget-and-resource-management.outcomes": "Pratiques de gestion du budget et des ressources établies pour les initiatives de l'API",
   "station.budget-and-resource-management.how_it_works": "Définir des pratiques de gestion du budget et des ressources qui décrivent les processus de gestion des budgets et des ressources pour les initiatives de l'API.",
   "station.api-product-strategy.outcomes.1": "Un langage commun entre le produit, le design et la technologie",
   "station.api-product-strategy.outcomes.2": "Un argumentaire ou un dossier solide pour le financement/l'approbation",
   "station.api-product-strategy.how_it_works.1": "Définir les entités de base, leurs attributs et leurs relations pour créer une compréhension conceptuelle partagée à travers les parcours et éventuellement les API.",
-  "station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur de l'API qui façonnent les API nouvelles ou réutilisables.",
-  "station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos consommateurs d'API à la prochaine station.",
+  "station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur qui façonnent les API nouvelles ou réutilisables.",
+  "station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos utilisateurs à la prochaine station.",
   "station.api-consumer-experience.outcomes.1": "Définir le parcours de l'expérience API",
   "station.api-consumer-experience.outcomes.2": "Planifier l'intégration, la documentation et le retour d'information",
   "station.api-consumer-experience.outcomes.3": "Améliorer l'adoption grâce à une véritable empathie + l'expérience du développeur (DX)",
   "station.api-platform-architecture.outcomes.1": "Mettre en œuvre une gouvernance cohérente sans contrôle descendant lourd",
   "station.api-platform-architecture.outcomes.2": "Conception en vue d'une réutilisation interne et d'une évolutivité externe",
-  "station.api-platform-architecture.how_it_works.1": "Cartographier les emplacements réglementaires, de conformité et de réseau des fournisseurs d'API et des consommateurs afin de garantir l'accessibilité et la conformité.",
+  "station.api-platform-architecture.how_it_works.1": "Cartographier les emplacements réglementaires, de conformité et de réseau des fournisseurs d'API et des utilisateurs afin de garantir l'accessibilité et la conformité.",
   "station.api-platform-architecture.how_it_works.2": "Le Capacity Canvas aligne les modèles de transactions commerciales, les tendances de consommation futures et les solutions techniques pour garantir l'évolutivité et les performances de l'API, et fournit des informations essentielles pour les décisions d'évolution et la planification de l'infrastructure.",
   "station.api-platform-architecture.how_it_works.3": "Définir et surveiller les indicateurs de performance (par exemple, les appels API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
-  "station.api-design.outcomes.1": "Contrats d'API réutilisables et validés",
+  "station.api-design.outcomes.1": "Contrats d'interface réutilisables et validés",
   "station.api-design.outcomes.2": "Conceptions alignées sur les modèles de domaine et les modèles d'interaction",
-  "station.api-design.outcomes.3": "Traçabilité de la conception à la valeur commerciale",
-  "station.api-design.how_it_works.1": "Utilisez le canevas d'interaction pour définir la manière dont les consommateurs interagiront avec l'API, en veillant à ce qu'elle réponde à leurs besoins et à leurs attentes.",
-  "station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
-  "station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
-  "station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "station.api-design.outcomes.3": "Traçabilité de la conception à la valeur métier",
+  "station.api-design.how_it_works.1": "Utilisez le canevas d'interaction pour définir la manière dont les utilisateurs interagiront avec l'API, en veillant à ce qu'elle réponde à leurs besoins et à leurs attentes.",
+  "station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
   "station.api-design.how_it_works.5": "Utiliser les principes de conception et le guide de style des API pour aligner vos décisions de conception sur des règles communes et permettre une validation d'audit cohérente.",
-  "station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou  « design-first » pour définir et valider le contrat de l'API avant sa mise en œuvre.",
+  "station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou « design-first » pour définir et valider le contrat de l'API avant sa mise en œuvre.",
   "station.api-design.how_it_works.7": "Utilisez la liste de contrôle d'audit des API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
   "station.api-delivery.outcomes.1": "Pipelines CI/CD fiables et automatisés",
   "station.api-delivery.outcomes.2": "Tests fonctionnels et non fonctionnels intégrés",
@@ -242,8 +242,8 @@
   "station.api-publishing.outcomes.1": "Des processus clairs d'intégration et d'enregistrement de l'API",
   "station.api-publishing.outcomes.2": "Documentation, modèles de sécurité et politiques disponibles",
   "station.api-publishing.outcomes.3": "Des API prêtes pour l'échelle et la gouvernance",
-  "station.api-publishing.how_it_works.1": "Documenter la manière dont les consommateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
-  "station.api-publishing.how_it_works.2": "Veiller à ce que les modèles de sécurité, la configuration de la passerelle et les termes juridiques soient clairs et accessibles aux consommateurs.",
+  "station.api-publishing.how_it_works.1": "Documenter la manière dont les utilisateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
+  "station.api-publishing.how_it_works.2": "Veiller à ce que les modèles de sécurité, la configuration de la passerelle et les termes juridiques soient clairs et accessibles aux utilisateurs.",
   "station.monitoring-and-improving.outcomes.1": "Boucles de rétroaction des développeurs en place",
   "station.monitoring-and-improving.outcomes.2": "Questions identifiées et traitées en permanence",
   "station.monitoring-and-improving.outcomes.3": "Itération de l'API alignée sur les besoins des utilisateurs",
@@ -252,14 +252,14 @@
   "station.user-experience.outcomes.1": "Interfaces utilisateur intuitives et cohérentes",
   "station.user-experience.outcomes.2": "Le retour d'information des utilisateurs est intégré dans la conception de l'API",
   "station.user-experience.outcomes.3": "Amélioration de la satisfaction et de l'adoption des utilisateurs",
-  "station.user-experience.how_it_works.1": "Mener des études sur les utilisateurs pour comprendre comment les consommateurs interagissent avec les services de l'écosystème ou avec vos applications consommatrices d'API.",
+  "station.user-experience.how_it_works.1": "Mener des études sur les utilisateurs pour comprendre comment les utilisateurs interagissent avec les services de l'écosystème ou avec vos applications consommatrices d'API.",
   "station.user-experience.how_it_works.2": "Documenter les exigences en matière d'expérience utilisateur afin qu'elles puissent être utilisées dans la conception de l'API, en veillant à ce qu'elles soient intuitives et faciles à utiliser.",
   "station.market-insights.outcomes.1": "Identification des normes industrielles et des meilleures pratiques",
   "station.market-insights.outcomes.2": "Stratégie API alignée sur les besoins du marché",
   "station.market-insights.outcomes.3": "Une prise de décision éclairée basée sur la connaissance du marché",
   "station.market-insights.how_it_works.1": "Analyser les API des concurrents pour comprendre leurs forces, leurs faiblesses et leurs arguments de vente uniques.",
   "station.market-insights.how_it_works.2": "Identifier les normes et les meilleures pratiques du secteur pour garantir la compétitivité et la conformité des API.",
-  "station.business-goals.outcomes.1": "Valeur commerciale clairement définie pour chaque API",
+  "station.business-goals.outcomes.1": "Valeur métier clairement définie pour chaque API",
   "station.business-goals.outcomes.2": "Adhésion et soutien des parties prenantes aux initiatives API",
   "station.business-goals.outcomes.3": "Les API contribuent au succès de l'organisation",
   "station.business-goals.how_it_works.1": "Identifier les indicateurs clés de performance (KPI) pour mesurer la réussite de l'API par rapport aux objectifs de l'entreprise.",
@@ -283,7 +283,7 @@
   "station.legal-and-compliance.outcomes.2": "Risques juridiques identifiés et atténués",
   "station.legal-and-compliance.outcomes.3": "Documentation claire des mesures de conformité",
   "station.legal-and-compliance.how_it_works.1": "Mettre en œuvre des mesures pour s'assurer que les API sont conformes à ces exigences, y compris le cryptage des données, les contrôles d'accès et les pistes d'audit.",
-  "station.legal-and-compliance.how_it_works.2": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux consommateurs.",
+  "station.legal-and-compliance.how_it_works.2": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux utilisateurs.",
   "station.security-and-privacy.outcomes.1": "Les données des utilisateurs sont protégées par des mesures de protection de la vie privée",
   "station.security-and-privacy.outcomes.2": "Mise en œuvre des meilleures pratiques de sécurité dans la conception et le développement des API",
   "station.security-and-privacy.outcomes.3": "Respect des normes et réglementations en matière de sécurité",
@@ -299,15 +299,15 @@
   "station.vendor-management.outcomes.3": "Réduction des risques liés aux dépendances avec des tiers",
   "station.vendor-management.how_it_works.1": "Définir les critères d'évaluation des API des fournisseurs, y compris la fiabilité, la sécurité et la conformité.",
   "station.vendor-management.how_it_works.2": "Contrôler les performances des fournisseurs et le respect des accords de niveau de service (SLA) et des normes de l'organisation.",
-  "station.contract-design.outcomes.1": "Attentes et responsabilités des fournisseurs d'API et des consommateurs",
+  "station.contract-design.outcomes.1": "Attentes et responsabilités des fournisseurs d'API et des utilisateurs",
   "station.contract-design.outcomes.2": "Directives d'utilisation et bonnes pratiques documentées",
   "station.contract-design.outcomes.3": "Réduction des malentendus et des litiges concernant l'utilisation de l'API",
-  "station.contract-design.how_it_works.1": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d'API lisibles par machine, faciles à partager et à valider.",
+  "station.contract-design.how_it_works.1": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d'interface lisibles par machine, faciles à partager et à valider.",
   "station.contract-design.how_it_works.2": "Veiller à ce que les contrats API soient examinés et approuvés par les parties prenantes afin de garantir l'alignement et la clarté.",
   "station.development.outcomes.1": "Des API de haute qualité, faciles à entretenir et évolutives",
   "station.development.outcomes.2": "Respect des normes et pratiques de codage cohérentes",
   "station.development.outcomes.3": "Réduction du temps de développement et de la dette technique",
-  "station.development.how_it_works.1": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d'API sont validés avant leur mise en œuvre.",
+  "station.development.how_it_works.1": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d'interface sont validés avant leur mise en œuvre.",
   "station.development.how_it_works.2": "Respecter les normes de codage et les meilleures pratiques afin d'assurer un développement cohérent et de haute qualité de l'API.",
   "station.ci-cd.outcomes.1": "Qualité et traçabilité constantes dans la livraison des API",
   "station.ci-cd.outcomes.2": "Des itérations plus rapides et une réduction du temps de mise sur le marché",
@@ -324,19 +324,19 @@
   "station.release-management.outcomes.3": "Réduction des risques liés aux changements d'API",
   "station.release-management.how_it_works.1": "Mettre en œuvre des stratégies de déploiement (par exemple, des déploiements \"bleu-vert\", des versions \"canari\") afin de minimiser les risques lors des mises à jour de l'API.",
   "station.release-management.how_it_works.2": "Mettre en place des procédures de retour en arrière pour revenir rapidement sur les modifications en cas de problèmes lors des mises à jour de l'API.",
-  "station.service-agreements.outcomes.1": "Attentes et niveaux de service définis pour les fournisseurs d'API et les consommateurs",
+  "station.service-agreements.outcomes.1": "Attentes et niveaux de service définis pour les fournisseurs d'API et les utilisateurs",
   "station.service-agreements.outcomes.2": "Responsabilités et processus de soutien documentés",
   "station.service-agreements.outcomes.3": "Amélioration de la communication et de la collaboration entre les équipes API",
   "station.service-agreements.how_it_works.1": "Utiliser des formats normalisés pour créer des accords de service lisibles par machine, faciles à partager et à valider.",
   "station.service-agreements.how_it_works.2": "Veiller à ce que les accords de service soient examinés et approuvés par les parties prenantes afin de garantir l'alignement et la clarté.",
   "station.api-consumer-adoption.outcomes.1": "Augmentation de l'utilisation de l'API et de l'engagement",
-  "station.api-consumer-adoption.outcomes.2": "Les consommateurs d'API sont informés des caractéristiques et des avantages de l'API",
-  "station.api-consumer-adoption.outcomes.3": "Amélioration de la satisfaction et de la fidélité des consommateurs d'API",
+  "station.api-consumer-adoption.outcomes.2": "Les utilisateurs sont informés des caractéristiques et des avantages de l'API",
+  "station.api-consumer-adoption.outcomes.3": "Amélioration de la satisfaction et de la fidélité des utilisateurs",
   "station.api-consumer-adoption.how_it_works.1": "Créer des supports pédagogiques (par exemple, des tutoriels, de la documentation) qui expliquent les caractéristiques, les avantages et les modes d'utilisation de l'API.",
-  "station.api-consumer-adoption.how_it_works.2": "S'engager auprès des consommateurs d'API par le biais de boucles de retour d'information, de canaux d'assistance et de forums communautaires afin de comprendre leurs besoins et d'améliorer l'adoption de l'API.",
+  "station.api-consumer-adoption.how_it_works.2": "S'engager auprès des utilisateurs par le biais de boucles de retour d'information, de canaux d'assistance et de forums communautaires afin de comprendre leurs besoins et d'améliorer l'adoption de l'API.",
   "station.api-promotion.outcomes.1": "Augmentation de la visibilité et de la notoriété de l'API",
   "station.api-promotion.outcomes.2": "Taux d'utilisation et d'adoption de l'API plus élevés",
-  "station.api-promotion.outcomes.3": "Amélioration de l'engagement et de la satisfaction des consommateurs d'API",
+  "station.api-promotion.outcomes.3": "Amélioration de l'engagement et de la satisfaction des utilisateurs",
   "station.api-promotion.how_it_works.1": "Créer du matériel promotionnel (par exemple, des études de cas, des exemples de réussite) qui met en évidence la valeur et les avantages des API.",
   "station.api-promotion.how_it_works.2": "S'impliquer dans les communautés et les forums API pour partager les mises à jour de l'API, recueillir des commentaires et promouvoir l'utilisation de l'API.",
   "station.partner-integration.outcomes.1": "Capacités API améliorées grâce aux API des partenaires",
@@ -367,32 +367,32 @@
   "station.portfolio-management.outcomes.1": "Des API alignées sur les objectifs de l'entreprise et les initiatives stratégiques",
   "station.portfolio-management.outcomes.2": "Hiérarchisation et optimisation des API en fonction de leur valeur et de leur impact",
   "station.portfolio-management.outcomes.3": "Amélioration de la visibilité et du contrôle du portefeuille d'API",
-  "station.portfolio-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des API en fonction de la valeur commerciale, de l'impact et de l'alignement sur les initiatives stratégiques.",
+  "station.portfolio-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des API en fonction de la valeur métier, de l'impact et de l'alignement sur les initiatives stratégiques.",
   "station.portfolio-management.how_it_works.2": "Contrôler le portefeuille d'API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l'entreprise.",
   "station.budget-and-resource-management.outcomes.1": "Affectation efficace des ressources aux initiatives de l'API",
   "station.budget-and-resource-management.outcomes.2": "Optimisation des investissements dans le développement et la gestion des API",
   "station.budget-and-resource-management.outcomes.3": "Amélioration de la visibilité financière et du contrôle des initiatives API",
-  "station.budget-and-resource-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur commerciale, de l'impact et de l'alignement sur les initiatives stratégiques.",
+  "station.budget-and-resource-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur métier, de l'impact et de l'alignement sur les initiatives stratégiques.",
   "station.budget-and-resource-management.how_it_works.2": "Contrôler le budget et l'utilisation des ressources afin de garantir l'efficacité des investissements et de l'affectation des ressources pour les initiatives de l'API.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "Stratégie produit API - Transformer les API en produits stratégiques",
-  "cycle.api-productization-cycle.station.api-product-strategy.description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs commerciaux.",
-  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "De nombreuses organisations considèrent les API comme des projets technologiques et non comme des produits. Le résultat ? Des consommateurs désorientés, une adoption médiocre et un gaspillage d'efforts.\n\nCette station vous aide à définir l'objectif, le public cible et les critères de réussite de votre API, afin que les équipes puissent fournir des API qui résolvent des problèmes réels.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs métier.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "De nombreuses organisations considèrent les API comme des projets technologiques et non comme des produits. Le résultat ? Des utilisateurs désorientés, une adoption médiocre et un gaspillage d'efforts.\n\nCette station vous aide à définir l'objectif, le public cible et les critères de réussite de votre API, afin que les équipes puissent fournir des API qui résolvent des problèmes réels.",
   "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Fournir des lignes directrices et des modèles pour la création de modèles commerciaux, de propositions de valeur et de feuilles de route pour les API.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Une proposition de valeur et un public simples pour l'API",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explorez le problème du client ou du partenaire que vous comptez résoudre avec les API. Dressez la carte des parties prenantes, de leurs parcours et de leurs résultats à l'aide du Customer Journey canvas.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Un langage commun entre le produit, le design et la technologie",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Un argumentaire ou un dossier solide pour le financement/l'approbation",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Définir les entités de base, leurs attributs et leurs relations pour créer une compréhension conceptuelle partagée à travers les parcours et éventuellement les API.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur de l'API qui façonnent les API nouvelles ou réutilisables.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos consommateurs d'API à la prochaine station.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilisez le canevas de proposition de valeur de l'API pour recenser les tâches métier prises en charge ainsi que les difficultés, les avantages et les fonctionnalités pour l'utilisateur qui façonnent les API nouvelles ou réutilisables.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Définissez la valeur - pour les utilisateurs et l'entreprise - à l'aide du modèle commercial de l'API, afin de rendre votre stratégie API visuelle, partageable et facile à valider avec vos utilisateurs à la prochaine station.",
   "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Concevoir pour les vrais utilisateurs de votre API",
   "cycle.api-productization-cycle.station.api-consumer-experience.description": "Veillez à ce que votre API soit découvrable, compréhensible et utilisable - avant et après le lancement.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Les meilleures API ne se contentent pas de fonctionner, elles sont intuitives. Que votre consommateur soit un développeur interne, un partenaire externe ou un agent d'intelligence artificielle, c'est son expérience qui détermine l'adoption.\n\nSans un plan d'expérience clair :\n- Les meilleures API restent inutilisées\n- Les équipes perdent du temps à deviner comment utiliser votre API.\n- Les boucles de rétroaction sont brisées ou manquantes.\n\nCette station vous aide à voir votre API à travers les yeux de ses consommateurs.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Les meilleures API ne se contentent pas de fonctionner, elles sont intuitives. Que votre utilisateur soit un développeur interne, un partenaire externe ou un agent d'intelligence artificielle, c'est son expérience qui détermine l'adoption.\n\nSans un plan d'expérience clair :\n- Les meilleures API restent inutilisées\n- Les équipes perdent du temps à deviner comment utiliser votre API.\n- Les boucles de rétroaction sont brisées ou manquantes.\n\nCette station vous aide à voir votre API à travers les yeux de ses utilisateurs.",
   "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Examinez l'API Value Proposition Canvas du point de vue de l'utilisateur. Veillez à la stabilité des tâches métier prises en charge et enrichissez les fonctionnalités qui simplifient et optimisent l'expérience utilisateur en intégrant les préoccupations des utilisateurs afin d'orienter les décisions de conception ultérieures.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur de l'API, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur de l'API.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilisez le canevas du parcours client pour le parcours de l'utilisateur, de la découverte et de l'évaluation à l'intégration, au dépannage et à l'utilisation continue.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilisez le parcours ainsi obtenu pour améliorer l'intégration, la documentation, l'assistance et les boucles de rétroaction pour l'utilisateur.",
   "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Fournir des lignes directrices, des outils et des mécanismes de retour d'information pour comprendre, analyser et améliorer l'expérience interne et externe des développeurs et des partenaires.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifier et hiérarchiser les consommateurs d'API",
+  "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifier et hiérarchiser les utilisateurs",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Définir le parcours de l'expérience API",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.2": "Planifier l'intégration, la documentation et le retour d'information",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.3": "Améliorer l'adoption grâce à une véritable empathie + l'expérience du développeur (DX)",
@@ -404,7 +404,7 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "Le Business Impact Canvas permet d'identifier et d'atténuer les risques liés à la disponibilité, à la sécurité et à la fonctionnalité de l'API afin de prendre des décisions éclairées en matière d'architecture.",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Mettre en œuvre une gouvernance cohérente sans contrôle descendant lourd",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Conception en vue d'une réutilisation interne et d'une évolutivité externe",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Cartographier les emplacements réglementaires, de conformité et de réseau des fournisseurs d'API et des consommateurs afin de garantir l'accessibilité et la conformité.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Cartographier les emplacements réglementaires, de conformité et de réseau des fournisseurs d'API et des utilisateurs afin de garantir l'accessibilité et la conformité.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "Le Capacity Canvas aligne les modèles de transactions commerciales, les tendances de consommation futures et les solutions techniques pour garantir l'évolutivité et les performances de l'API, et fournit des informations essentielles pour les décisions d'évolution et la planification de l'infrastructure.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Définir et surveiller les indicateurs de performance (par exemple, les appels API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
   "cycle.api-productization-cycle.station.api-design.title": "Conception d'API - Concevoir des API qui apportent de la valeur",
@@ -413,26 +413,26 @@
   "cycle.api-productization-cycle.station.api-design.apply_in_work": "Fournir des modèles de conception réutilisables, des normes communes et des outils de validation pour les spécifications d'API. S'assurer que les décisions de conception sont cohérentes, examinées dès le début et alignées sur les objectifs métier.",
   "cycle.api-productization-cycle.station.api-design.outcomes": "Des conceptions d'API bien documentées et cohérentes",
   "cycle.api-productization-cycle.station.api-design.how_it_works": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.",
-  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contrats d'API réutilisables et validés",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contrats d'interface API réutilisables et validés",
   "cycle.api-productization-cycle.station.api-design.outcomes.2": "Conceptions alignées sur les modèles de domaine et les modèles d'interaction",
-  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Traçabilité de la conception à la valeur commerciale",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Utilisez le canevas d'interaction pour définir la manière dont les consommateurs interagiront avec l'API, en veillant à ce qu'elle réponde à leurs besoins et à leurs attentes.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'API cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Traçabilité de la conception à la valeur métier",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Utilisez le canevas d'interaction pour définir la manière dont les utilisateurs interagiront avec l'API, en veillant à ce qu'elle réponde à leurs besoins et à leurs attentes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Appliquer les modèles de conception REST pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Appliquer des modèles de conception orientés événements pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Appliquer les modèles de conception GraphQL pour créer des contrats d'interface cohérents et réutilisables qui sont validés avec les parties prenantes.",
   "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Utiliser les principes de conception et le guide de style des API pour aligner vos décisions de conception sur des règles communes et permettre une validation d'audit cohérente.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou  « design-first » pour définir et valider le contrat de l'API avant sa mise en œuvre.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Appliquez des approches « contract-first » ou « design-first » pour définir et valider le contrat d'interface API avant sa mise en œuvre.",
   "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Utilisez la liste de contrôle d'audit des API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
   "cycle.api-productization-cycle.station.api-delivery.title": "Livraison d'API - Fournir des API sécurisées et fiables",
   "cycle.api-productization-cycle.station.api-delivery.description": "Construire, tester et publier des API en utilisant des pipelines de livraison modernes et les meilleures pratiques d'ingénierie.",
   "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Même les meilleures conceptions d'API échouent si la livraison est incohérente. Cette station garantit que vos API sont construites avec qualité, testées de manière approfondie et déployées de manière fiable, ce qui permet des itérations plus rapides et une plus grande confiance.",
-  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fournir des cadres de codage, des bibliothèques et des normes pour la mise en œuvre des API. Mettre en œuvre des pipelines CI/CD, des cadres d'assurance qualité et des outils d'automatisation du déploiement.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fournir des frameworks de développement, des bibliothèques et des normes pour la mise en œuvre des API. Mettre en œuvre des pipelines CI/CD, des cadres d'assurance qualité et des outils d'automatisation du déploiement.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes": "API mises en œuvre à l'aide de cadres et de modèles testés",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Utilisez les meilleures pratiques de développement d'API comme guide pour mettre en œuvre le contrat d'interface validé à l'aide de frameworks et de bibliothèques établis, en veillant à ce que le résultat soit réutilisable et maintenable.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Pipelines CI/CD fiables et automatisés",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Tests fonctionnels et non fonctionnels intégrés",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Pipelines de livraison sécurisés et conformes",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construisez l'implémentation de l'API à partir du contrat validé en utilisant des frameworks, des bibliothèques et des normes d'équipe établis.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construisez l'implémentation de l'API à partir du contrat d'interface validé en utilisant des frameworks, des bibliothèques et des standards d'équipe établis.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Tester les fonctionnalités, la sécurité et les performances des API à l'aide d'outils de test automatisés.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de déploiement, en garantissant une qualité et une traçabilité constantes.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "S'assurer que les API répondent aux exigences de sécurité et de conformité grâce à des contrôles et des audits automatisés.",
@@ -451,14 +451,14 @@
   "cycle.api-productization-cycle.station.api-publishing.title": "Publication d'API - Publier des API en toute confiance",
   "cycle.api-productization-cycle.station.api-publishing.description": "Exposer les API de manière sûre et claire au bon public avec la bonne documentation et les bons processus.",
   "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "La publication va plus loin que le déploiement - il s'agit de la découvrabilité, de l'accès et de l'assistance. Si les API ne sont pas publiées correctement, elles ne seront pas utilisées, réutilisées ou sécurisées efficacement.",
-  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permettre aux API d'être publiées dans l'environnement approprié et disposer de mécanismes d'enregistrement et d'accès clairs (par exemple, clés API, OAuth, plans d'abonnement) en fonction des segments de consommateurs d'API et des exigences en matière de sécurité et de conformité.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permettre aux API d'être publiées dans l'environnement approprié et disposer de mécanismes d'enregistrement et d'accès clairs (par exemple, clés API, OAuth, plans d'abonnement) en fonction des segments de utilisateurs et des exigences en matière de sécurité et de conformité.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes": "API publiées dans le bon environnement (privé, partenaire, public)",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publier les API dans les passerelles et les environnements appropriés afin de favoriser la réutilisation pour de multiples consommateurs d'API.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works": "Publier les API dans les passerelles et les environnements appropriés afin de favoriser la réutilisation pour de multiples utilisateurs.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Des processus clairs d'intégration et d'enregistrement de l'API",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentation, modèles de sécurité et politiques disponibles",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.3": "Des API prêtes pour l'échelle et la gouvernance",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Documenter la manière dont les consommateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
-  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Veiller à ce que les modèles de sécurité, la configuration de la passerelle et les termes juridiques soient clairs et accessibles aux consommateurs.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.1": "Documenter la manière dont les utilisateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
+  "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Veiller à ce que les modèles de sécurité, la configuration de la passerelle et les termes juridiques soient clairs et accessibles aux utilisateurs.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Suivi et amélioration - pour la valeur de l'API",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Utiliser les mesures et le retour d'information pour suivre les performances de l'API et favoriser l'amélioration continue.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "La livraison d'API ne s'arrête pas au lancement. Sans surveillance, les équipes ne peuvent pas améliorer l'adoption, les performances ou le retour sur investissement. Cette station garantit que les API restent utiles, sécurisées et qu'elles évoluent avec les besoins de l'entreprise.",
diff --git a/src/data/method/pt/labels.criteria.json b/src/data/method/pt/labels.criteria.json
index 9fbf93c..d4f434d 100644
--- a/src/data/method/pt/labels.criteria.json
+++ b/src/data/method/pt/labels.criteria.json
@@ -2,24 +2,24 @@
   "exit_criteria": "Critérios de saída",
   "entry_criteria": "Critérios de entrada",
   "criterion.metrics-feedback-available": "Sinais de mercado relevantes, feedback ou insights operacionais estão disponíveis para orientar esta oportunidade de API.",
-  "criterion.business-goals-defined": "As metas de negócios estão definidas",
-  "criterion.market-research-done": "A pesquisa de mercado identifica oportunidades de API",
+  "criterion.business-goals-defined": "Os objetivos de negócio estão definidos",
+  "criterion.market-research-done": "A investigação de mercado identifica oportunidades de API",
   "criterion.stakeholder-approval": "As partes interessadas relevantes concordam que esta oportunidade de API vale a pena ser explorada e priorizada.",
   "criterion.api-opportunity-documented": "As oportunidades individuais de API são identificadas e documentadas",
-  "criterion.api-reusability": "A API atende a uma necessidade clara de negócios e é reutilizável para vários consumidores de API",
-  "criterion.hide-backend-discrepancies": "A API é destinada a proteger os consumidores da complexidade e das inconsistências do backend.",
-  "criterion.value-prop-validated": "A proposta de valor da API foi revisada e validada com as partes interessadas relevantes do negócio e dos consumidores.",
+  "criterion.api-reusability": "A API satisfaz uma necessidade clara de negócio e é reutilizável por vários consumidores de API",
+  "criterion.hide-backend-discrepancies": "A API é destinada a proteger os consumidores da complexidade e das inconsistências do back-end.",
+  "criterion.value-prop-validated": "A proposta de valor da API foi revista e validada com as partes interessadas relevantes do negócio e dos consumidores.",
   "criterion.consumer-segments-identified": "Os segmentos de consumidores de API (internos e externos) são identificados.",
   "criterion.api-roadmap-defined": "Roteiros de alto nível para o desenvolvimento de API são estabelecidos.",
   "criterion.architecture-patterns-validated": "Os padrões de arquitetura e plataforma da API escolhidos foram validados com as partes interessadas relevantes de arquitetura, segurança e plataforma.",
-  "criterion.design-reflects-business-value": "A design da API e suas capacidades expostas refletem claramente o valor comercial e as necessidades dos usuários.",
-  "criterion.api-consistency": "O design da API segue nossas convenções compartilhadas para o produto API e o design.",
-  "criterion.api-contract-tested": "O contrato da API é testado e atende aos requisitos funcionais e não funcionais.",
+  "criterion.design-reflects-business-value": "A conceção da API e as capacidades expostas refletem claramente o valor de negócio e as necessidades dos utilizadores.",
+  "criterion.api-consistency": "A conceção da API segue as nossas convenções partilhadas para o produto API e a conceção.",
+  "criterion.api-contract-tested": "O contrato de interface da API é testado e satisfaz os requisitos funcionais e não funcionais.",
   "criterion.api-description-available": "A API e suas capacidades expostas são descritas de forma suficiente para revisão, auditoria e integração.",
   "criterion.audit-passed": "A API é aprovada nas verificações de conformidade, segurança e auditoria.",
-  "criterion.audit-reports-shared": "Os resultados da auditoria e as decisões de correção são compartilhados com as partes interessadas relevantes.",
-  "criterion.api-ready-for-publishing": "A API está pronta para ser implantada e exposta através das portarias e ambientes intencionados.",
-  "criterion.api-documentation-ready": "A documentação da API voltada para os consumidores está completa o suficiente para publicação e integração.",
-  "criterion.consumer-support-ready": "Os processos de registro, suporte e comunicação estão prontos para os consumidores da API.",
+  "criterion.audit-reports-shared": "Os resultados da auditoria e as decisões de correção são partilhados com as partes interessadas relevantes.",
+  "criterion.api-ready-for-publishing": "A API está pronta para ser disponibilizada e exposta através dos gateways e ambientes pretendidos.",
+  "criterion.api-documentation-ready": "A documentação da API orientada para os consumidores está suficientemente completa para publicação e integração.",
+  "criterion.consumer-support-ready": "Os processos de registo, suporte e comunicação estão prontos para os consumidores da API.",
   "criterion.legal-compliance-clear": "Os requisitos legais, de privacidade e de conformidade para publicação são definidos e compreendidos."
-}
\ No newline at end of file
+}
diff --git a/src/data/method/pt/labels.cycles.json b/src/data/method/pt/labels.cycles.json
new file mode 100644
index 0000000..c3677ab
--- /dev/null
+++ b/src/data/method/pt/labels.cycles.json
@@ -0,0 +1,93 @@
+{
+  "cycles.title": "Vistas de ciclo",
+  "cycles.description": "Vistas específicas por público sobre o método APIOps Cycles",
+  "cycle.capability-productization-cycle.title": "Ciclo de Produto de Capacidades",
+  "cycle.capability-productization-cycle.description": "Um ciclo para transformar capacidades de negócio em capacidades digitais reutilizáveis antes de selecionar o estilo de implementação.",
+  "cycle.capability-productization-cycle.purpose": "Identificar e transformar capacidades digitais reutilizáveis em produto antes de decidir se o estilo de disponibilização deve ser API, eventos, ficheiros, streams, produtos de dados, serviços com IA, integração direta ou um padrão híbrido.",
+  "cycle.api-productization-cycle.title": "Ciclo de Produto de API",
+  "cycle.api-productization-cycle.description": "A jornada APIOps Cycles focada em API para transformar APIs em produto, concebê-las, entregá-las, publicá-las e melhorá-las.",
+  "cycle.api-productization-cycle.purpose": "Jornada do método focada em API para equipas que já sabem que o estilo de disponibilização pretendido é um produto API.",
+  "cycle.integration-productization-cycle.title": "Ciclo de Produto de Integração",
+  "cycle.integration-productization-cycle.description": "Um ciclo para transformar capacidades de integração reutilizáveis em produto antes de selecionar um padrão de integração concreto.",
+  "cycle.integration-productization-cycle.purpose": "Orientar a conceção de capacidades de integração reutilizáveis antes de escolher APIs, eventos, ficheiros, streams, produtos de dados, integração direta ou padrões híbridos.",
+  "cycle.station.capability-strategy": "Estratégia",
+  "cycle.station.consumer-requirements-onboarding": "Requisitos e integração de consumidores",
+  "cycle.station.architecture-platform-decisions": "Decisões de arquitetura e plataforma",
+  "cycle.station.solution-interface-design": "Conceção da solução e da interface",
+  "cycle.station.delivery-operations": "Entrega e operações",
+  "cycle.station.quality-readiness-assurance": "Garantia de qualidade e prontidão",
+  "cycle.station.publishing-enablement": "Publicação e promoção da adoção",
+  "cycle.station.monitoring-improvement": "Monitorização e melhoria",
+  "cycle.station.api-product-strategy": "Estratégia de produto API",
+  "cycle.station.api-consumer-experience": "Experiência do consumidor da API",
+  "cycle.station.api-platform-architecture": "Arquitetura da plataforma API",
+  "cycle.station.api-design": "Conceção da API",
+  "cycle.station.api-delivery": "Entrega da API",
+  "cycle.station.api-audit": "Auditoria da API",
+  "cycle.station.api-publishing": "Publicação da API",
+  "cycle.station.monitoring-and-improving": "Monitorização e melhoria",
+  "cycle.station.integration-capability-strategy": "Estratégia da capacidade de integração",
+  "cycle.station.integration-consumer-requirements-onboarding": "Requisitos e integração de consumidores da integração",
+  "cycle.station.integration-architecture-decision": "Decisão de arquitetura da integração",
+  "cycle.station.integration-solution-design": "Conceção da solução de integração",
+  "cycle.station.integration-delivery-operations": "Entrega e operações da integração",
+  "cycle.station.integration-readiness-assurance": "Garantia de prontidão da integração",
+  "cycle.station.capability-publishing": "Publicação da capacidade",
+  "cycle.station.integration-monitoring-improvement": "Monitorização e melhoria da integração",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor, os consumidores, a propriedade e os objetivos de negócio da capacidade.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Recolha requisitos dos consumidores, necessidades de integração, restrições, expectativas de serviço e responsabilidades dos produtores.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilize requisitos e restrições para escolher a arquitetura e as capacidades de plataforma.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Conceba o contrato de interface e o modelo de interação para o estilo de disponibilização selecionado.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Construa, teste, disponibilize e opere a capacidade usando o estilo de disponibilização selecionado e o contrato de interface validado.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Assegure a qualidade, a governação e a prontidão antes da disponibilização.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publique informação sobre a capacidade para que os consumidores a possam descobrir, solicitar, integrar e obter suporte.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da capacidade, os resultados dos consumidores, a fiabilidade, a reutilização e as oportunidades de melhoria.",
+  "cycle.owner.business-owner": "Responsável de negócio",
+  "cycle.owner.domain-expert": "Especialista de domínio",
+  "cycle.owner.capability-owner": "Responsável pela capacidade",
+  "cycle.owner.consumer-representative": "Representante dos consumidores",
+  "cycle.owner.enterprise-architect": "Arquiteto empresarial",
+  "cycle.owner.platform-owner": "Responsável pela plataforma",
+  "cycle.owner.api-product-owner": "Responsável pelo produto API",
+  "cycle.owner.api-platform-owner": "Responsável pela plataforma API",
+  "cycle.owner.integration-architect": "Arquiteto de integração",
+  "cycle.owner.solution-architect": "Arquiteto de solução",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Enquadre a API como um produto com proposta de valor, consumidores, modelo de negócio, propriedade e intenção de ciclo de vida claros.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Defina segmentos de consumidores da API, percursos de integração, expectativas e requisitos de experiência antes de bloquear decisões de conceção.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.description": "Escolha e valide a plataforma API, a arquitetura, a governação e as restrições operacionais necessárias para o produto.",
+  "cycle.api-productization-cycle.station.api-design.description": "Conceba o contrato de interface da API, o modelo de interação, os esquemas, as políticas e os detalhes de usabilidade antes da implementação.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Implemente, teste, proteja, automatize e opere o produto API através do pipeline de entrega.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Valide a qualidade, a conformidade, a prontidão, as evidências e os critérios de disponibilização da API antes da publicação.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publique o produto API para que os consumidores o possam descobrir, avaliar, solicitar acesso, integrar e obter suporte.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da API, a adoção, os resultados dos consumidores, a fiabilidade e as oportunidades de melhoria após a disponibilização.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Enquadre a capacidade de integração reutilizável, a necessidade de negócio, a propriedade e a reutilização esperada antes de selecionar um padrão.",
+  "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Recolha consumidores da integração, responsabilidades dos fornecedores, necessidades de integração, expectativas de serviço e restrições operacionais.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decida a arquitetura de integração, as capacidades de plataforma, as restrições e o modelo de governação da capacidade.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Conceba o contrato de interface, payloads, eventos, APIs, ficheiros ou padrões de interação selecionados para a capacidade de integração.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Construa, teste, automatize, disponibilize e opere a capacidade de integração usando o padrão de disponibilização selecionado e o contrato de interface validado.",
+  "cycle.integration-productization-cycle.station.api-audit.description": "Assegure a prontidão, a governação, a qualidade, a segurança, a conformidade e as evidências operacionais da integração antes da disponibilização.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publique a capacidade de integração para que as equipas a possam descobrir, solicitar, reutilizar, integrar e obter suporte.",
+  "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitorize a fiabilidade da integração, a reutilização, os incidentes, o desempenho, os resultados dos consumidores e as necessidades de melhoria.",
+  "cycle.automation-cycle.title": "Ciclo de Automação",
+  "cycle.automation-cycle.description": "Um ciclo para identificar, conceber, entregar, capacitar e melhorar oportunidades de automação.",
+  "cycle.automation-cycle.purpose": "Transformar oportunidades de automação em fluxos de trabalho governados com utilizadores, plataformas, controlos, percursos de entrega, capacitação e monitorização claros.",
+  "cycle.audience.automation-owners": "Responsáveis pela automação",
+  "cycle.audience.process-owners": "Responsáveis pelo processo",
+  "cycle.audience.automation-teams": "Equipas de automação",
+  "cycle.station.automation-opportunity-strategy": "Estratégia da oportunidade de automação",
+  "cycle.station.process-user-requirements": "Requisitos do processo/utilizador",
+  "cycle.station.automation-platform-decision": "Decisão de plataforma de automação",
+  "cycle.station.automation-workflow-design": "Conceção do fluxo de trabalho de automação",
+  "cycle.station.automation-delivery": "Entrega da automação",
+  "cycle.station.automation-readiness-review": "Revisão de prontidão da automação",
+  "cycle.station.automation-enablement": "Capacitação da automação",
+  "cycle.station.automation-monitoring-improvement": "Monitorização e melhoria da automação",
+  "cycle.automation-cycle.station.api-product-strategy.description": "Identifique e priorize oportunidades de automação por valor, viabilidade, risco, propriedade e impacto esperado no processo.",
+  "cycle.automation-cycle.station.api-consumer-experience.description": "Recolha utilizadores do processo, funções, transferências, exceções, restrições e expectativas de serviço antes de conceber a automação.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Escolha a plataforma de automação, o runtime, o modelo de integração, os controlos de governação e as restrições operacionais.",
+  "cycle.automation-cycle.station.api-design.description": "Conceba o fluxo de trabalho de automação, gatilhos, pontos de decisão, integrações, tratamento de dados, contratos de interface e caminhos de exceção.",
+  "cycle.automation-cycle.station.api-delivery.description": "Construa, teste, disponibilize, documente e opere a automação com propriedade, controlos e caminhos de reversão claros.",
+  "cycle.automation-cycle.station.api-audit.description": "Reveja a prontidão, a qualidade, o risco, a conformidade, a supervisão humana, as evidências e os critérios de disponibilização da automação.",
+  "cycle.automation-cycle.station.api-publishing.description": "Capacite utilizadores e operadores com descoberta, integração, instruções operacionais, caminhos de suporte e comunicação de alterações.",
+  "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitorize o desempenho da automação, exceções, fiabilidade, resultados dos utilizadores, impacto operacional e oportunidades de melhoria."
+}
diff --git a/src/data/method/pt/labels.json b/src/data/method/pt/labels.json
index 6efbd2b..c8ee178 100644
--- a/src/data/method/pt/labels.json
+++ b/src/data/method/pt/labels.json
@@ -1,11 +1,11 @@
 {
   "stations": "Estações",
-  "why_it_matters": "Por que esta estação existe?",
+  "why_it_matters": "Porque existe esta estação?",
   "outcomes": "Resultados",
   "how_it_works": "Como funciona",
   "steps": "Passos",
-  "apply_in_work": "Isto é o que significa sucesso",
-  "related_metrolines": "Incluído nestas linhas de metrô",
+  "apply_in_work": "Como é o sucesso na prática",
+  "related_metrolines": "Incluído nestas linhas",
   "entry_criteria_title": "Sinais de partida",
-  "exit_criteria_title": "Feito bem quando"
-}
\ No newline at end of file
+  "exit_criteria_title": "Concluído com qualidade quando"
+}
diff --git a/src/data/method/pt/labels.lines.json b/src/data/method/pt/labels.lines.json
index d16251b..092746e 100644
--- a/src/data/method/pt/labels.lines.json
+++ b/src/data/method/pt/labels.lines.json
@@ -1,11 +1,11 @@
 {
-  "lines.title": "Linhas de metro",
-  "lines.description": "Uma coleção de linhas API que orientam o desenvolvimento e a gestão de APIs.",
+  "lines.title": "Linhas",
+  "lines.description": "Uma coleção de linhas de API que orientam o desenvolvimento e a gestão de APIs.",
   "line.business-opportunities-line.title": "Linha oportunidades de negócio",
   "line.business-opportunities-line.description": "Centra-se na identificação e aproveitamento de oportunidades de negócio através de APIs.",
   "line.platform-architecture-line.title": "Linha de arquitetura da plataforma",
-  "line.platform-architecture-line.description": "Abrange os aspectos arquitecturais das plataformas API.",
-  "line.api-design-line.title": "Linha de conceção API",
+  "line.platform-architecture-line.description": "Abrange os aspetos arquiteturais das plataformas API.",
+  "line.api-design-line.title": "Linha de conceção de API",
   "line.api-design-line.description": "Centra-se nos princípios e práticas de conceção de APIs.",
   "line.delivery-line.title": "Linha de entrega",
   "line.delivery-line.description": "Abrange os processos e práticas de entrega de APIs.",
diff --git a/src/data/method/pt/labels.resources.json b/src/data/method/pt/labels.resources.json
index 43855da..3786cc0 100644
--- a/src/data/method/pt/labels.resources.json
+++ b/src/data/method/pt/labels.resources.json
@@ -2,74 +2,74 @@
   "resource.api-community-engagement-strategies.title": "Estratégias de envolvimento da comunidade API",
   "resource.api-community-engagement-strategies.description": "Um manual para promover a adoção de APIs, cultivando comunidades através de conteúdos, canais de apoio, ciclos de feedback e estratégias de envolvimento social.",
   "resource.api-community-engagement-strategies.outcomes": "Melhor compreensão dos princípios das estratégias de envolvimento da comunidade da API",
-  "resource.api-community-engagement-strategies.outcomes.1": "Abordagem padronizada usando as estratégias de envolvimento da comunidade da API",
+  "resource.api-community-engagement-strategies.outcomes.1": "Abordagem normalizada usando as estratégias de envolvimento da comunidade da API",
   "resource.api-community-engagement-strategies.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-community-engagement-strategies.steps": "Desenvolver estratégias de marketing para promover as API junto de públicos-alvo, incluindo redes sociais, blogues e webinars.",
-  "resource.api-community-engagement-strategies.steps.1": "Criar materiais promocionais (por exemplo, estudos de casos, histórias de sucesso) que realcem o valor e as vantagens das API.",
-  "resource.api-community-engagement-strategies.steps.2": "Criar materiais educativos (por exemplo, tutoriais, documentação) que expliquem as caraterísticas, as vantagens e os padrões de utilização da API.",
+  "resource.api-community-engagement-strategies.steps": "Desenvolver estratégias de marketing para promover as APIs junto de públicos-alvo, incluindo redes sociais, blogues e webinars.",
+  "resource.api-community-engagement-strategies.steps.1": "Criar materiais promocionais (por exemplo, estudos de casos, histórias de sucesso) que realcem o valor e as vantagens das APIs.",
+  "resource.api-community-engagement-strategies.steps.2": "Criar materiais educativos (por exemplo, tutoriais, documentação) que expliquem as características, as vantagens e os padrões de utilização da API.",
   "resource.api-community-engagement-strategies.steps.3": "Interagir com os consumidores da API através de ciclos de feedback, canais de apoio e fóruns da comunidade para compreender as suas necessidades e melhorar a adoção da API.",
   "resource.api-community-engagement-strategies.steps.4": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.",
-  "resource.api-community-engagement-strategies.tips": "Personalize as estratégias de envolvimento da comunidade da API para o seu domínio",
+  "resource.api-community-engagement-strategies.tips": "Personalize as estratégias de envolvimento da comunidade de API ao seu domínio",
   "resource.api-community-engagement-strategies.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-compliance-best-practices.title": "Melhores práticas de conformidade da API",
-  "resource.api-compliance-best-practices.description": "Garantir que as APIs cumprem a conformidade legal, regulamentar e interna através de documentação, controlos e validações automatizadas.",
-  "resource.api-compliance-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de conformidade da API",
+  "resource.api-compliance-best-practices.title": "Boas práticas de conformidade da API",
+  "resource.api-compliance-best-practices.description": "Garantir que as APIs cumprem conformidade legal, regulamentar e interna através de documentação, controlos e validações automatizadas.",
+  "resource.api-compliance-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de conformidade da API",
   "resource.api-compliance-best-practices.outcomes.1": "Abordagem normalizada utilizando as Melhores Práticas de Conformidade da API",
   "resource.api-compliance-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-compliance-best-practices.steps": "Documentar as medidas de conformidade e garantir que são comunicadas às partes interessadas e aos consumidores.",
   "resource.api-compliance-best-practices.steps.1": "Implementar medidas para garantir que as APIs cumprem estes requisitos, incluindo encriptação de dados, controlos de acesso e pistas de auditoria.",
   "resource.api-compliance-best-practices.steps.2": "Utilizar listas de controlo, linters e ferramentas de teste para verificar a consistência e a conformidade com as normas.",
-  "resource.api-compliance-best-practices.tips": "Personalizar as Melhores Práticas de Conformidade da API para o seu domínio",
+  "resource.api-compliance-best-practices.tips": "Personalizar as Melhores Práticas de Conformidade de API ao seu domínio",
   "resource.api-compliance-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-development-best-practices.title": "Melhores práticas de desenvolvimento de API",
-  "resource.api-development-best-practices.description": "Orientações de implementação para transformar um contrato de API validado em uma base de código de API consistente e sustentável, utilizando bibliotecas padrão, padrões reutilizáveis e fluxos de trabalho de desenvolvimento alinhados.",
-  "resource.api-development-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de desenvolvimento de API",
-  "resource.api-development-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de desenvolvimento de API",
+  "resource.api-development-best-practices.title": "Boas práticas de desenvolvimento de API",
+  "resource.api-development-best-practices.description": "Orientações de implementação para transformar um contrato de interface da API validado numa base de código de API consistente e sustentável, utilizando bibliotecas padrão, padrões reutilizáveis e fluxos de trabalho de desenvolvimento alinhados.",
+  "resource.api-development-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de desenvolvimento de API",
+  "resource.api-development-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de desenvolvimento de API",
   "resource.api-development-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-development-best-practices.steps": "Aplique essas práticas ao contrato de API validado e ao plano de implementação antes do início da codificação.",
-  "resource.api-development-best-practices.steps.1": "Use frameworks, bibliotecas e padrões de codificação estabelecidos para implementar o contrato de forma consistente e sustentável.",
-  "resource.api-development-best-practices.tips": "Use este recurso como orientação de implementação e lente de revisão, em vez de como um artefato independente obrigatório",
+  "resource.api-development-best-practices.steps": "Aplique essas práticas ao contrato de interface da API validado e ao plano de implementação antes do início da codificação.",
+  "resource.api-development-best-practices.steps.1": "Utilize frameworks, bibliotecas e padrões de codificação estabelecidos para implementar o contrato de forma consistente e sustentável.",
+  "resource.api-development-best-practices.tips": "Utilize este recurso como orientação de implementação e lente de revisão, em vez de como um artefato independente obrigatório",
   "resource.api-development-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-metrics-and-analytics.title": "Métricas e análises de API",
+  "resource.api-metrics-and-analytics.title": "Métricas e análise de API",
   "resource.api-metrics-and-analytics.description": "Um recurso para definir, recolher e analisar o desempenho da API e os dados de utilização para alinhar os KPIs técnicos com os resultados comerciais.",
   "resource.api-metrics-and-analytics.outcomes": "Melhor compreensão dos princípios de métrica e análise de API",
-  "resource.api-metrics-and-analytics.outcomes.1": "Abordagem padronizada usando métricas e análises de API",
+  "resource.api-metrics-and-analytics.outcomes.1": "Abordagem normalizada usando métricas e análise de API",
   "resource.api-metrics-and-analytics.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-metrics-and-analytics.steps": "Identificar indicadores-chave de desempenho (KPIs) para medir o sucesso da API em relação aos objectivos comerciais.",
-  "resource.api-metrics-and-analytics.steps.1": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
-  "resource.api-metrics-and-analytics.steps.2": "Monitorizar as iniciativas API para garantir o cumprimento das orientações operacionais e das práticas de governação",
-  "resource.api-metrics-and-analytics.tips": "Personalizar as métricas e análises da API para o seu domínio",
+  "resource.api-metrics-and-analytics.steps": "Identificar indicadores-chave de desempenho (KPIs) para medir o sucesso da API em relação aos objetivos de negócio.",
+  "resource.api-metrics-and-analytics.steps.1": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "resource.api-metrics-and-analytics.steps.2": "Monitorizar as iniciativas APIs para garantir o cumprimento das orientações operacionais e das práticas de governação",
+  "resource.api-metrics-and-analytics.tips": "Personalizar as métricas e análise de API ao seu domínio",
   "resource.api-metrics-and-analytics.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-onboarding-best-practices.title": "Melhores práticas de integração de API",
-  "resource.api-onboarding-best-practices.description": "Práticas recomendadas para simplificar as jornadas de integração do consumidor da API com registo passo a passo, descoberta e orientação na primeira chamada.",
-  "resource.api-onboarding-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de integração de API",
-  "resource.api-onboarding-best-practices.outcomes.1": "Abordagem padronizada usando as práticas recomendadas de integração de API",
+  "resource.api-onboarding-best-practices.title": "Boas práticas de integração de API",
+  "resource.api-onboarding-best-practices.description": "Boas práticas para simplificar as jornadas de integração do consumidor da API com registo passo a passo, descoberta e orientação na primeira chamada.",
+  "resource.api-onboarding-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de integração de API",
+  "resource.api-onboarding-best-practices.outcomes.1": "Abordagem normalizada usando as boas práticas de integração de API",
   "resource.api-onboarding-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-onboarding-best-practices.steps": "Definir o percurso do consumidor da API desde a descoberta até à resolução de problemas, identificando os principais pontos de contacto e os pontos problemáticos.",
-  "resource.api-onboarding-best-practices.steps.1": "Desenvolver processos de integração e recursos para ajudar os consumidores de API a compreender como utilizar as API de forma eficaz.",
+  "resource.api-onboarding-best-practices.steps.1": "Desenvolver processos de integração e recursos para ajudar os consumidores de API a compreender como utilizar as APIs de forma eficaz.",
   "resource.api-onboarding-best-practices.steps.2": "Documentar a forma como os consumidores encontram e utilizam a API, incluindo processos de integração e registo.",
-  "resource.api-onboarding-best-practices.tips": "Personalizar as práticas recomendadas de integração da API para o seu domínio",
+  "resource.api-onboarding-best-practices.tips": "Personalizar as boas práticas de integração de API ao seu domínio",
   "resource.api-onboarding-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.api-portfolio-management-guidelines.title": "Diretrizes de gestão da carteira API",
-  "resource.api-portfolio-management-guidelines.description": "Um guia para gerenciar estrategicamente o conjunto de APIs de uma organização - priorizando APIs, alocando recursos e monitorando o desempenho em todos os ciclos de vida.",
+  "resource.api-portfolio-management-guidelines.description": "Um guia para gerir estrategicamente o conjunto de APIs de uma organização - priorizando APIs, alocando recursos e monitorando o desempenho ao longo de todo o ciclo de vida.",
   "resource.api-portfolio-management-guidelines.outcomes": "Melhor compreensão dos princípios orientadores da gestão de carteiras API",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Abordagem padronizada usando as diretrizes de gerenciamento de portfólio da API",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "Abordagem normalizada usando as diretrizes de gestão de portfólio da API",
   "resource.api-portfolio-management-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-portfolio-management-guidelines.steps": "Definir práticas de gestão da carteira que descrevam os processos de gestão da carteira de API, incluindo a definição de prioridades, a monitorização e a otimização.",
   "resource.api-portfolio-management-guidelines.steps.1": "Definir práticas de gestão orçamental e de recursos que descrevam os processos de gestão de orçamentos e recursos para iniciativas de API.",
-  "resource.api-portfolio-management-guidelines.steps.2": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor comercial, no impacto e no alinhamento com as iniciativas estratégicas.",
-  "resource.api-portfolio-management-guidelines.steps.3": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objectivos comerciais.",
-  "resource.api-portfolio-management-guidelines.tips": "Personalizar as Diretrizes de Gestão de Portfólio API para o seu domínio",
+  "resource.api-portfolio-management-guidelines.steps.2": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor de negócio, no impacto e no alinhamento com as iniciativas estratégicas.",
+  "resource.api-portfolio-management-guidelines.steps.3": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objetivos de negócio.",
+  "resource.api-portfolio-management-guidelines.tips": "Personalizar as Diretrizes de Gestão de Portfólio API ao seu domínio",
   "resource.api-portfolio-management-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-security-best-practices.title": "Melhores práticas de segurança da API",
+  "resource.api-security-best-practices.title": "Boas práticas de segurança da API",
   "resource.api-security-best-practices.description": "Um conjunto de controlos acionáveis para proteger APIs, incluindo autenticação, autorização, encriptação, limitação de taxas e verificações de conformidade ao nível do pipeline.",
-  "resource.api-security-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de segurança da API",
-  "resource.api-security-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de segurança da API",
+  "resource.api-security-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de segurança da API",
+  "resource.api-security-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de segurança da API",
   "resource.api-security-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-security-best-practices.steps": "Garantir que as APIs cumprem os requisitos de segurança e conformidade através de verificações e auditorias automatizadas.",
   "resource.api-security-best-practices.steps.1": "Implemente medidas de segurança como autenticação, autorização, encriptação e limitação de taxas para proteger as APIs de ameaças.",
   "resource.api-security-best-practices.steps.2": "Implementar verificações de segurança automatizadas e validações de conformidade no pipeline CI/CD para garantir que as APIs são seguras e compatíveis.",
-  "resource.api-security-best-practices.tips": "Personalize as práticas recomendadas de segurança da API para o seu domínio",
+  "resource.api-security-best-practices.tips": "Personalize as boas práticas de segurança de API ao seu domínio",
   "resource.api-security-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.api-team-structure-guidelines.title": "Diretrizes da estrutura da equipa API",
   "resource.api-team-structure-guidelines.description": "Orientação organizacional para a definição de funções e responsabilidades nas equipas de API para garantir clareza, colaboração e responsabilidade.",
@@ -77,47 +77,47 @@
   "resource.api-team-structure-guidelines.outcomes.1": "Abordagem normalizada utilizando as Diretrizes da Estrutura da Equipa API",
   "resource.api-team-structure-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-team-structure-guidelines.steps": "Definir estruturas de equipa e funções para equipas de API, incluindo proprietários de produtos de API, programadores, arquitectos e operações.",
-  "resource.api-team-structure-guidelines.tips": "Personalizar as Diretrizes da estrutura da equipa API para o seu domínio",
+  "resource.api-team-structure-guidelines.tips": "Personalizar as Diretrizes da estrutura da equipa API ao seu domínio",
   "resource.api-team-structure-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-testing-best-practices.title": "Melhores práticas de teste de API",
+  "resource.api-testing-best-practices.title": "Boas práticas de teste de API",
   "resource.api-testing-best-practices.description": "Diretrizes para a implementação de testes automatizados funcionais, de desempenho e de segurança ao longo do ciclo de vida da API.",
-  "resource.api-testing-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de teste de API",
-  "resource.api-testing-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de teste de API",
+  "resource.api-testing-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de teste de API",
+  "resource.api-testing-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de teste de API",
   "resource.api-testing-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-testing-best-practices.steps": "Testar a funcionalidade, a segurança e o desempenho das API, utilizando ferramentas de teste automatizadas.",
-  "resource.api-testing-best-practices.steps.1": "Integrar testes funcionais e não funcionais no pipeline CI/CD para garantir que as APIs cumprem as normas de qualidade.",
+  "resource.api-testing-best-practices.steps": "Testar a funcionalidade, a segurança e o desempenho das APIs, utilizando ferramentas de teste automatizadas.",
+  "resource.api-testing-best-practices.steps.1": "Integrar testes funcionais e não funcionais no pipeline CI/CD para garantir que as APIs cumprems normas de qualidade.",
   "resource.api-testing-best-practices.steps.2": "Utilizar ferramentas de teste automatizadas para validar a funcionalidade, a segurança e o desempenho da API.",
-  "resource.api-testing-best-practices.tips": "Personalize as práticas recomendadas de teste de API para o seu domínio",
+  "resource.api-testing-best-practices.tips": "Personalize as boas práticas de teste de API ao seu domínio",
   "resource.api-testing-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.api-training-programs.title": "Programas de formação API",
   "resource.api-training-programs.description": "Um roteiro para melhorar as competências das equipas com percursos de aprendizagem estruturados em design, governação, desempenho e segurança de API.",
   "resource.api-training-programs.outcomes": "Melhor compreensão dos princípios dos programas de formação API",
-  "resource.api-training-programs.outcomes.1": "Abordagem padronizada utilizando Programas de Formação API",
+  "resource.api-training-programs.outcomes.1": "Abordagem normalizada utilizando Programas de Formação API",
   "resource.api-training-programs.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-training-programs.steps": "Identificar as principais competências e áreas de conhecimento da API que precisam de ser melhoradas, como a conceção, a segurança e o desempenho da API.",
   "resource.api-training-programs.steps.1": "Incentivar a aprendizagem contínua através de cursos em linha, certificações e envolvimento da comunidade.",
-  "resource.api-training-programs.steps.2": "Fornecer formação e recursos para ajudar as equipas a adotar uma mentalidade de prioridade à API e a compreender as vantagens das API.",
+  "resource.api-training-programs.steps.2": "Fornecer formação e recursos para ajudar as equipas a adotar uma mentalidade de prioridade à API e a compreender as vantagens das APIs.",
   "resource.api-training-programs.steps.3": "Fornecer programas de formação, workshops e recursos para ajudar as equipas a melhorar as suas competências e conhecimentos em matéria de API.",
-  "resource.api-training-programs.tips": "Personalizar os programas de formação API para o seu domínio",
+  "resource.api-training-programs.tips": "Personalizar os programas de formação API ao seu domínio",
   "resource.api-training-programs.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-versioning-best-practices.title": "Práticas recomendadas de controle de versão da API",
+  "resource.api-versioning-best-practices.title": "Boas práticas de controlo de versões da API",
   "resource.api-versioning-best-practices.description": "Estratégias para introduzir, manter e retirar versões de API, preservando a compatibilidade com versões anteriores e a confiança dos consumidores.",
-  "resource.api-versioning-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de controlo de versões da API",
-  "resource.api-versioning-best-practices.outcomes.1": "Abordagem padronizada usando as práticas recomendadas de controle de versão da API",
+  "resource.api-versioning-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de controlo de versões da API",
+  "resource.api-versioning-best-practices.outcomes.1": "Abordagem normalizada usando as boas práticas de controlo de versões da API",
   "resource.api-versioning-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-versioning-best-practices.steps": "Definir estratégias de controlo de versões para as API para gerir as alterações e garantir a compatibilidade com as versões anteriores.",
-  "resource.api-versioning-best-practices.tips": "Personalizar as práticas recomendadas de controle de versão da API para o seu domínio",
+  "resource.api-versioning-best-practices.steps": "Definir estratégias de controlo de versões para as APIs para gerir as alterações e garantir a compatibilidade com as versões anteriores.",
+  "resource.api-versioning-best-practices.tips": "Personalizar as boas práticas de controlo de versões de API ao seu domínio",
   "resource.api-versioning-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD para APIs",
-  "resource.apiops-CI-CD-for-apis.description": "Orientação de implantação que integra tarefas do ciclo de vida da API - design, teste, governança - em pipelines de integração e entrega contínuas.",
+  "resource.apiops-CI-CD-for-apis.description": "Orientação de disponibilização que integra tarefas do ciclo de vida da API - design, teste, governação - em pipelines de integração e entrega contínuas.",
   "resource.apiops-CI-CD-for-apis.outcomes": "Melhor compreensão dos princípios de CI/CD para APIs",
-  "resource.apiops-CI-CD-for-apis.outcomes.1": "Abordagem padronizada usando CI/CD para APIs",
+  "resource.apiops-CI-CD-for-apis.outcomes.1": "Abordagem normalizada usando CI/CD para APIs",
   "resource.apiops-CI-CD-for-apis.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.apiops-CI-CD-for-apis.steps": "Utilizar pipelines CI/CD para automatizar os processos de construção, teste e implementação, garantindo uma qualidade e rastreabilidade consistentes.",
   "resource.apiops-CI-CD-for-apis.steps.1": "Integrar testes automatizados no pipeline CI/CD para garantir a validação contínua da qualidade da API.",
-  "resource.apiops-CI-CD-for-apis.steps.2": "Implementar estratégias de implantação (por exemplo, implantações blue-green, lançamentos canários) para minimizar os riscos durante os lançamentos de API.",
+  "resource.apiops-CI-CD-for-apis.steps.2": "Implementar estratégias de disponibilização (por exemplo, disponibilizações blue-green, lançamentos canários) para minimizar os riscos durante os lançamentos de API.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua.",
-  "resource.apiops-CI-CD-for-apis.tips": "Personalize as APIs CI/CD For para o seu domínio",
+  "resource.apiops-CI-CD-for-apis.tips": "Personalize as APIs CI/CD For ao seu domínio",
   "resource.apiops-CI-CD-for-apis.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.competitor-analysis-template.title": "Modelo de análise da concorrência",
   "resource.competitor-analysis-template.description": "Uma folha de cálculo estruturada para comparar as suas ofertas de API com a concorrência, mapeando os pontos fortes, os pontos fracos e os diferenciadores de valor.",
@@ -125,26 +125,26 @@
   "resource.competitor-analysis-template.outcomes.1": "Abordagem normalizada utilizando o modelo de análise da concorrência",
   "resource.competitor-analysis-template.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.competitor-analysis-template.steps": "Efetuar uma análise da concorrência para identificar os principais concorrentes e as suas ofertas de API.",
-  "resource.competitor-analysis-template.steps.1": "Analisar as API da concorrência para compreender os seus pontos fortes, fracos e pontos de venda únicos.",
-  "resource.competitor-analysis-template.tips": "Personalizar o modelo de análise da concorrência para o seu domínio",
+  "resource.competitor-analysis-template.steps.1": "Analisar as APIs da concorrência para compreender os seus pontos fortes, fracos e pontos de venda únicos.",
+  "resource.competitor-analysis-template.tips": "Personalizar o modelo de análise da concorrência ao seu domínio",
   "resource.competitor-analysis-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.contract-first-design.title": "Primeira conceção do contrato",
   "resource.contract-first-design.description": "Uma diretriz que defende abordagens API-first utilizando contratos formais (por exemplo, OpenAPI) para alinhar as partes interessadas antes do desenvolvimento.",
   "resource.contract-first-design.outcomes": "Melhor compreensão dos princípios de conceção da primeira fase do contrato",
-  "resource.contract-first-design.outcomes.1": "Abordagem normalizada utilizando o Contract First Design",
+  "resource.contract-first-design.outcomes.1": "Abordagem normalizada utilizando a conceção orientada por contrato",
   "resource.contract-first-design.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.contract-first-design.steps": "Aplicar abordagens \"contract-first\" ou \"design-first\" para garantir que os contratos API são validados antes da implementação.",
-  "resource.contract-first-design.steps.1": "Definir contratos de API que descrevam as expectativas, responsabilidades e diretrizes de utilização para cada API.",
-  "resource.contract-first-design.steps.2": "Utilizar formatos normalizados (por exemplo, OpenAPI, AsyncAPI) para criar contratos de API legíveis por máquina que sejam fáceis de partilhar e validar.",
-  "resource.contract-first-design.tips": "Personalize o design do Contract First para o seu domínio",
+  "resource.contract-first-design.steps": "Aplicar abordagens \"contract-first\" ou \"design-first\" para garantir que os contratos de interface da API são validados antes da implementação.",
+  "resource.contract-first-design.steps.1": "Definir contratos de interface da API que descrevam as expectativas, responsabilidades e diretrizes de utilização para cada API.",
+  "resource.contract-first-design.steps.2": "Utilizar formatos normalizados (por exemplo, OpenAPI, AsyncAPI) para criar contratos de interface da API legíveis por máquina que sejam fáceis de partilhar e validar.",
+  "resource.contract-first-design.tips": "Personalize a conceção do Contract First ao seu domínio",
   "resource.contract-first-design.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.cross-functional-collaboration-best-practices.title": "Melhores práticas de colaboração interfuncional",
+  "resource.cross-functional-collaboration-best-practices.title": "Boas práticas de colaboração interfuncional",
   "resource.cross-functional-collaboration-best-practices.description": "Práticas para facilitar a comunicação e o alinhamento entre as equipas comerciais e técnicas ao planear ou fornecer APIs.",
-  "resource.cross-functional-collaboration-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de colaboração interfuncional",
-  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de colaboração interfuncional",
+  "resource.cross-functional-collaboration-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de colaboração interfuncional",
+  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de colaboração interfuncional",
   "resource.cross-functional-collaboration-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.cross-functional-collaboration-best-practices.steps": "Incentivar a colaboração multifuncional entre equipas de API, unidades empresariais e partes interessadas para alinhar as iniciativas de API com os objectivos empresariais.",
-  "resource.cross-functional-collaboration-best-practices.tips": "Personalize as Melhores Práticas de Colaboração Interfuncional para o seu domínio",
+  "resource.cross-functional-collaboration-best-practices.steps": "Incentivar a colaboração multifuncional entre equipas de API, unidades empresariais e partes interessadas para alinhar as iniciativas de API com os objetivos empresariais.",
+  "resource.cross-functional-collaboration-best-practices.tips": "Personalize as Melhores Práticas de Colaboração Interfuncional ao seu domínio",
   "resource.cross-functional-collaboration-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.data-privacy-guidelines.title": "Diretrizes de privacidade de dados",
   "resource.data-privacy-guidelines.description": "Considerações de design para garantir que as APIs cumprem os regulamentos de proteção de dados, como o RGPD, através de anonimização e controlos de acesso.",
@@ -152,37 +152,37 @@
   "resource.data-privacy-guidelines.outcomes.1": "Abordagem normalizada utilizando as Diretrizes de Privacidade de Dados",
   "resource.data-privacy-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.data-privacy-guidelines.steps": "Garantir a privacidade dos dados dos utilizadores através da implementação de medidas de proteção de dados, como a anonimização e os controlos de acesso.",
-  "resource.data-privacy-guidelines.tips": "Personalizar as Diretrizes de Privacidade de Dados para o seu domínio",
+  "resource.data-privacy-guidelines.tips": "Personalizar as Diretrizes de Privacidade de Dados ao seu domínio",
   "resource.data-privacy-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.domain-canvas.title": "Domain Canvas",
+  "resource.domain-canvas.title": "Canvas de Domínio",
   "resource.domain-canvas.description": "Uma ferramenta de modelação para definir e comunicar as principais entidades e relações no seu domínio, assegurando a consistência semântica entre APIs.",
   "resource.domain-canvas.outcomes": "Melhor compreensão dos princípios do domínio canvas",
-  "resource.domain-canvas.outcomes.1": "Abordagem normalizada utilizando o Domain Canvas",
+  "resource.domain-canvas.outcomes.1": "Abordagem normalizada utilizando o Canvas de Domínio",
   "resource.domain-canvas.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.domain-canvas.steps": "Definir entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre APIs.",
-  "resource.domain-canvas.tips": "Personalizar o Canvas do domínio para o seu domínio",
+  "resource.domain-canvas.tips": "Personalizar o Canvas de Domínio ao seu domínio",
   "resource.domain-canvas.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.ecosystem-vision-template.title": "Modelo de visão do ecossistema",
   "resource.ecosystem-vision-template.description": "Uma ferramenta de planeamento estratégico para definir o ecossistema API, incluindo parceiros-alvo, cadeias de valor e oportunidades de integração.",
   "resource.ecosystem-vision-template.outcomes": "Melhor compreensão dos princípios do modelo de visão do ecossistema",
-  "resource.ecosystem-vision-template.outcomes.1": "Abordagem padronizada usando o Modelo de Visão do Ecossistema",
+  "resource.ecosystem-vision-template.outcomes.1": "Abordagem normalizada usando o Modelo de Visão do Ecossistema",
   "resource.ecosystem-vision-template.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.ecosystem-vision-template.steps": "Realizar estudos de mercado para identificar tendências, oportunidades e ameaças no panorama das API.",
+  "resource.ecosystem-vision-template.steps": "Realizar estudos de mercado para identificar tendências, oportunidades e ameaças no panorama das APIs.",
   "resource.ecosystem-vision-template.steps.1": "Identificar os principais parceiros e intervenientes do ecosistema que irão beneficiar ou contribuir para o ecosistema.",
-  "resource.ecosystem-vision-template.steps.2": "Identifique as lacunas no mercado que as suas API podem preencher, com base nas ofertas da concorrência.",
+  "resource.ecosystem-vision-template.steps.2": "Identifique as lacunas no mercado que as suas APIs podem preencher, com base nas ofertas da concorrência.",
   "resource.ecosystem-vision-template.steps.3": "Identifique potenciais parceiros cujas APIs possam melhorar as suas capacidades de API e a sua proposta de valor.",
-  "resource.ecosystem-vision-template.steps.4": "Desenvolva uma estratégia de diferenciação que destaque as caraterísticas e benefícios únicos das suas APIs.",
+  "resource.ecosystem-vision-template.steps.4": "Desenvolva uma estratégia de diferenciação que destaque as características e benefícios únicos das suas APIs.",
   "resource.ecosystem-vision-template.steps.5": "Defina a visão do ecossistema para as suas APIs, incluindo a forma como estas irão interagir com outros sistemas e plataformas.",
   "resource.ecosystem-vision-template.steps.6": "Conceber APIs para permitir uma integração e colaboração perfeitas no ecossistema.",
-  "resource.ecosystem-vision-template.tips": "Personalizar o modelo de visão do ecossistema para o seu domínio",
+  "resource.ecosystem-vision-template.tips": "Personalizar o modelo de visão do ecossistema ao seu domínio",
   "resource.ecosystem-vision-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.industry-standards-and-best-practices.title": "Normas e melhores práticas do sector",
-  "resource.industry-standards-and-best-practices.description": "Um recurso de referência para alinhar o design e a operação da API com estruturas e especificações amplamente reconhecidas do sector.",
-  "resource.industry-standards-and-best-practices.outcomes": "Melhor compreensão das normas do sector e dos princípios das melhores práticas",
-  "resource.industry-standards-and-best-practices.outcomes.1": "Abordagem normalizada utilizando as normas e as melhores práticas do sector",
+  "resource.industry-standards-and-best-practices.title": "Normas e boas práticas do sector",
+  "resource.industry-standards-and-best-practices.description": "Um recurso de referência para alinhar a conceção e a operação da API com estruturas e especificações amplamente reconhecidas do sector.",
+  "resource.industry-standards-and-best-practices.outcomes": "Melhor compreensão das normas do sector e dos princípios das boas práticas",
+  "resource.industry-standards-and-best-practices.outcomes.1": "Abordagem normalizada utilizando as normas e as boas práticas do sector",
   "resource.industry-standards-and-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.industry-standards-and-best-practices.steps": "Identificar as normas e as melhores práticas do sector para garantir que as API são competitivas e estão em conformidade.",
-  "resource.industry-standards-and-best-practices.tips": "Personalize os padrões e as melhores práticas da indústria para o seu domínio",
+  "resource.industry-standards-and-best-practices.steps": "Identificar as normas e as boas práticas do sector para garantir que as APIs são competitivas e estão em conformidade.",
+  "resource.industry-standards-and-best-practices.tips": "Personalize os padrões e as boas práticas da indústria ao seu domínio",
   "resource.industry-standards-and-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.partner-integration-guidelines.title": "Diretrizes de integração de parceiros",
   "resource.partner-integration-guidelines.description": "Listas de verificação de integração e padrões de comunicação para gerir os aspectos técnicos e legais das relações com APIs de terceiros.",
@@ -191,25 +191,25 @@
   "resource.partner-integration-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.partner-integration-guidelines.steps": "Estabelecer processos de integração e orientações para colaborar com os parceiros, incluindo a integração técnica, a partilha de dados e o apoio.",
   "resource.partner-integration-guidelines.steps.1": "Monitorize o desempenho e a conformidade da API do parceiro para garantir a fiabilidade e o alinhamento com a sua estratégia de API.",
-  "resource.partner-integration-guidelines.tips": "Personalizar as Diretrizes de Integração de Parceiros para o seu domínio",
+  "resource.partner-integration-guidelines.tips": "Personalizar as Diretrizes de Integração de Parceiros ao seu domínio",
   "resource.partner-integration-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.role-communication-best-practices.title": "Melhores práticas de comunicação de funções",
+  "resource.role-communication-best-practices.title": "Boas práticas de comunicação de funções",
   "resource.role-communication-best-practices.description": "Ferramentas para definir e documentar quem é responsável por quê nas iniciativas de API, garantindo que as transferências e a responsabilidade sejam claras.",
-  "resource.role-communication-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de comunicação de funções",
-  "resource.role-communication-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de comunicação de funções",
+  "resource.role-communication-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de comunicação de funções",
+  "resource.role-communication-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de comunicação de funções",
   "resource.role-communication-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.role-communication-best-practices.steps": "Estabelecer responsabilidades claras para cada função, incluindo a conceção, o desenvolvimento, os testes e as operações da API.",
   "resource.role-communication-best-practices.steps.1": "Assegurar que as funções e responsabilidades são comunicadas a todos os membros da equipa e partes interessadas para garantir o alinhamento.",
-  "resource.role-communication-best-practices.tips": "Personalizar as Melhores Práticas de Comunicação de Funções para o seu domínio",
+  "resource.role-communication-best-practices.tips": "Personalizar as Melhores Práticas de Comunicação de Funções ao seu domínio",
   "resource.role-communication-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.scalable-infrastructure-best-practices.title": "Melhores práticas de infraestrutura escalável",
-  "resource.scalable-infrastructure-best-practices.description": "Orientação arquitetónica para garantir que as API são implementadas em infra-estruturas que podem lidar elasticamente com picos de utilização e crescimento.",
-  "resource.scalable-infrastructure-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de infra-estruturas escaláveis",
+  "resource.scalable-infrastructure-best-practices.title": "Boas práticas de infraestrutura escalável",
+  "resource.scalable-infrastructure-best-practices.description": "Orientação arquitetónica para garantir que as APIs são implementadas em infra-estruturas que podem lidar elasticamente com picos de utilização e crescimento.",
+  "resource.scalable-infrastructure-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de infra-estruturas escaláveis",
   "resource.scalable-infrastructure-best-practices.outcomes.1": "Abordagem normalizada utilizando as Melhores Práticas de Infraestrutura Escalável",
   "resource.scalable-infrastructure-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.scalable-infrastructure-best-practices.steps": "Conceber a infraestrutura da API para ser escalável e resiliente, utilizando padrões e tecnologias nativos da nuvem.",
   "resource.scalable-infrastructure-best-practices.steps.1": "Monitorizar o desempenho e a capacidade da infraestrutura para garantir que esta consegue dar resposta à crescente procura.",
-  "resource.scalable-infrastructure-best-practices.tips": "Personalize as Melhores Práticas de Infraestrutura Escalável para o seu domínio",
+  "resource.scalable-infrastructure-best-practices.tips": "Personalize as Melhores Práticas de Infraestrutura Escalável ao seu domínio",
   "resource.scalable-infrastructure-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.service-agreement-template.title": "Modelo de contrato de serviço",
   "resource.service-agreement-template.description": "Um formato de acordo personalizável que define expectativas, SLAs, responsabilidades e termos de acesso para o consumo de API.",
@@ -219,15 +219,15 @@
   "resource.service-agreement-template.steps": "Defina acordos de serviço que descrevam as expectativas, os níveis de serviço e as responsabilidades de cada API.",
   "resource.service-agreement-template.steps.1": "Utilize formatos normalizados para criar contratos de serviço legíveis por máquina que sejam fáceis de partilhar e validar.",
   "resource.service-agreement-template.steps.2": "Assegurar que os acordos de serviço são revistos e aprovados pelas partes interessadas para garantir o alinhamento e a clareza.",
-  "resource.service-agreement-template.tips": "Personalizar o modelo de contrato de serviço para o seu domínio",
+  "resource.service-agreement-template.tips": "Personalizar o modelo de contrato de serviço ao seu domínio",
   "resource.service-agreement-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.stakeholder-engagement-best-practices.title": "Melhores práticas de envolvimento das partes interessadas",
-  "resource.stakeholder-engagement-best-practices.description": "Tácticas de envolvimento para alinhar as partes interessadas internas e externas em torno dos objectivos, valor e governação partilhados da API.",
-  "resource.stakeholder-engagement-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de envolvimento das partes interessadas",
-  "resource.stakeholder-engagement-best-practices.outcomes.1": "Abordagem padronizada usando as Melhores Práticas de Envolvimento das Partes Interessadas",
+  "resource.stakeholder-engagement-best-practices.title": "Boas práticas de envolvimento das partes interessadas",
+  "resource.stakeholder-engagement-best-practices.description": "Tácticas de envolvimento para alinhar as partes interessadas internas e externas em torno dos objetivos, valor e governação partilhados da API.",
+  "resource.stakeholder-engagement-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de envolvimento das partes interessadas",
+  "resource.stakeholder-engagement-best-practices.outcomes.1": "Abordagem normalizada usando as Melhores Práticas de Envolvimento das Partes Interessadas",
   "resource.stakeholder-engagement-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.stakeholder-engagement-best-practices.steps": "Envolver as partes interessadas para garantir o alinhamento e o apoio às iniciativas da API.",
-  "resource.stakeholder-engagement-best-practices.tips": "Personalize as Melhores Práticas de Envolvimento das Partes Interessadas para o seu domínio",
+  "resource.stakeholder-engagement-best-practices.tips": "Personalize as Melhores Práticas de Envolvimento das Partes Interessadas ao seu domínio",
   "resource.stakeholder-engagement-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.test-automation-frameworks.title": "Estruturas de automatização de testes",
   "resource.test-automation-frameworks.description": "Ferramentas e padrões recomendados para automatizar testes de contrato, regressão e integração de API em vários ambientes.",
@@ -235,32 +235,32 @@
   "resource.test-automation-frameworks.outcomes.1": "Abordagem normalizada utilizando estruturas de automatização de testes",
   "resource.test-automation-frameworks.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.test-automation-frameworks.steps": "Implementar estruturas de automatização de testes que apoiem os testes de contrato, os testes de integração e os testes de ponta a ponta.",
-  "resource.test-automation-frameworks.tips": "Personalizar as estruturas de automatização de testes para o seu domínio",
+  "resource.test-automation-frameworks.tips": "Personalizar as estruturas de automatização de testes ao seu domínio",
   "resource.test-automation-frameworks.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.vendor-management-best-practices.title": "Melhores práticas de gestão de fornecedores",
+  "resource.vendor-management-best-practices.title": "Boas práticas de gestão de fornecedores",
   "resource.vendor-management-best-practices.description": "Estrutura para avaliar e gerir fornecedores externos de API e integrações de terceiros com base no risco, desempenho e conformidade.",
-  "resource.vendor-management-best-practices.outcomes": "Melhor compreensão dos princípios das melhores práticas de gestão de fornecedores",
-  "resource.vendor-management-best-practices.outcomes.1": "Abordagem normalizada utilizando as melhores práticas de gestão de fornecedores",
+  "resource.vendor-management-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de gestão de fornecedores",
+  "resource.vendor-management-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de gestão de fornecedores",
   "resource.vendor-management-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.vendor-management-best-practices.steps": "Estabelecer processos de gestão de fornecedores para avaliar, integrar e monitorizar fornecedores de API de terceiros.",
-  "resource.vendor-management-best-practices.steps.1": "Definir critérios para avaliar as API dos fornecedores, incluindo fiabilidade, segurança e conformidade.",
-  "resource.vendor-management-best-practices.tips": "Personalize as Melhores Práticas de Gestão de Fornecedores para o seu domínio",
+  "resource.vendor-management-best-practices.steps.1": "Definir critérios para avaliar as APIs dos fornecedores, incluindo fiabilidade, segurança e conformidade.",
+  "resource.vendor-management-best-practices.tips": "Personalize as Melhores Práticas de Gestão de Fornecedores ao seu domínio",
   "resource.vendor-management-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
   "resource.api-audit-checklist.title": "Lista de verificação de auditoria da API",
   "resource.api-audit-checklist.description": "Uma lista de verificação baseada no ciclo de vida para verificar a prontidão da API em design, entrega, publicação e conformidade usando critérios de auditoria e evidências definidos.",
   "resource.api-audit-checklist.outcomes": "Melhor compreensão dos princípios da lista de controlo de auditoria da API",
-  "resource.api-audit-checklist.outcomes.1": "Abordagem padronizada usando a lista de verificação de auditoria da API",
+  "resource.api-audit-checklist.outcomes.1": "Abordagem normalizada usando a lista de verificação de auditoria da API",
   "resource.api-audit-checklist.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-audit-checklist.steps": "Utilize a lista de verificação de auditoria da API para garantir que a conceção da API cumpre os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
-  "resource.api-audit-checklist.steps.1": "Realize auditorias para avaliar a cobertura do ciclo de vida e verificar se a API atende aos padrões de negócios, design e operacionais.",
+  "resource.api-audit-checklist.steps.1": "Realize auditorias para avaliar a cobertura do ciclo de vida e verificar se a API satisfaz os padrões de negócio, conceção e operacionais.",
   "resource.api-audit-checklist.steps.2": "Certifique-se de que a documentação, os modelos de segurança, a configuração do gateway e os requisitos legais estejam claramente definidos, validados e comprovados por evidências.",
   "resource.api-audit-checklist.tips": "Cada item de auditoria vincula o trabalho do ciclo de vida (etapas), as diretrizes regulatórias e as evidências de apoio para fornecer uma visão clara da prontidão da API.",
-  "resource.api-audit-checklist.tips.1": "Use a Lista de Verificação de Auditoria de API de forma colaborativa entre as funções de negócios e tecnologia",
-  "resource.api-business-model-canvas.title": "API Business Model Canvas",
+  "resource.api-audit-checklist.tips.1": "Utilize a Lista de Verificação de Auditoria de API de forma colaborativa entre as funções de negócios e tecnologia",
+  "resource.api-business-model-canvas.title": "Canvas do Modelo de Negócio da API",
   "resource.api-business-model-canvas.description": "Avaliar estrategicamente a viabilidade do negócio de API, mapeando propostas de valor, segmentos de consumidores e recursos-chave.",
   "resource.api-business-model-canvas.outcomes": "Estratégia comercial clara para APIs",
   "resource.api-business-model-canvas.outcomes.1": "Identificação dos principais recursos e parceiros",
-  "resource.api-business-model-canvas.outcomes.2": "Alinhamento das caraterísticas da API com os objectivos comerciais",
+  "resource.api-business-model-canvas.outcomes.2": "Alinhamento das características da API com os objetivos de negócio",
   "resource.api-business-model-canvas.steps": "Resumir a proposta de valor da API",
   "resource.api-business-model-canvas.steps.1": "Definir segmentos de consumidores",
   "resource.api-business-model-canvas.steps.2": "Identificar estratégias de relações com os promotores",
@@ -276,26 +276,26 @@
   "resource.api-design-principles.outcomes": "Melhor compreensão dos princípios de conceção das API",
   "resource.api-design-principles.outcomes.1": "Abordagem normalizada utilizando os princípios de conceção da API",
   "resource.api-design-principles.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-design-principles.steps": "**Design que coloca o consumidor em primeiro lugar:** iniciar cada ciclo de APIOps recolhendo os objectivos do utilizador e os termos do domínio para que as APIs resolvam problemas reais.",
-  "resource.api-design-principles.steps.1": "**Nomeação e comportamento consistentes:** aplicar convenções partilhadas para recursos, erros e formatos para tornar as API previsíveis.",
+  "resource.api-design-principles.steps": "**Conceção que coloca o consumidor em primeiro lugar:** iniciar cada ciclo de APIOps recolhendo os objetivos do utilizador e os termos do domínio para que as APIs resolvam problemas reais.",
+  "resource.api-design-principles.steps.1": "**Nomeação e comportamento consistentes:** aplicar convenções partilhadas para recursos, erros e formatos para tornar as APIs previsíveis.",
   "resource.api-design-principles.steps.2": "**Orientado para contratos:** capturar a interface com OpenAPI ou AsyncAPI antes da codificação para alinhar as equipas e permitir a automatização.",
   "resource.api-design-principles.steps.3": "**Usabilidade e facilidade de descoberta:** fornecer documentação e exemplos claros para que os programadores compreendam rapidamente como utilizar a API.",
-  "resource.api-design-principles.steps.4": "**Iterar com segurança:** desenvolver os projectos em pequenos incrementos, com versões, para que as alterações não perturbem os consumidores existentes.",
-  "resource.api-design-principles.tips": "Personalizar os princípios de conceção da API para o seu domínio",
+  "resource.api-design-principles.steps.4": "**Iterar com segurança:** desenvolver os projetos em pequenos incrementos, com versões, para que as alterações não perturbem os consumidores existentes.",
+  "resource.api-design-principles.tips": "Personalizar os princípios de conceção de API ao seu domínio",
   "resource.api-design-principles.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
-  "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas",
+  "resource.api-value-proposition-canvas.title": "Canvas da Proposta de Valor da API",
   "resource.api-value-proposition-canvas.description": "Alinhar as funcionalidades da API com as necessidades dos utilizadores, mapeando tarefas, problemas e ganhos para os produtos da API.",
   "resource.api-value-proposition-canvas.outcomes": "Desenvolvimento de funcionalidades específicas",
   "resource.api-value-proposition-canvas.outcomes.1": "Alinhamento com as necessidades dos utilizadores",
   "resource.api-value-proposition-canvas.outcomes.2": "Melhoria da satisfação do consumidor da API",
   "resource.api-value-proposition-canvas.steps": "Listar as tarefas do percurso do utilizador",
-  "resource.api-value-proposition-canvas.steps.1": "Identificar as caraterísticas que proporcionam os ganhos esperados",
-  "resource.api-value-proposition-canvas.steps.2": "Definir caraterísticas para enfrentar os desafios",
-  "resource.api-value-proposition-canvas.steps.3": "Mapear caraterísticas para produtos API",
-  "resource.api-value-proposition-canvas.tips": "Utilizar os dados do Customer Journey Canvas",
-  "resource.api-value-proposition-canvas.tips.1": "Destaque para as caraterísticas que aliviam as dores ou aumentam os ganhos",
-  "resource.api-value-proposition-canvas.tips.2": "Validar as caraterísticas com os consumidores da API para garantir o alinhamento",
-  "resource.business-impact-canvas.title": "Business Impact Canvas",
+  "resource.api-value-proposition-canvas.steps.1": "Identificar as características que proporcionam os ganhos esperados",
+  "resource.api-value-proposition-canvas.steps.2": "Definir características para enfrentar os desafios",
+  "resource.api-value-proposition-canvas.steps.3": "Mapear características para produtos API",
+  "resource.api-value-proposition-canvas.tips": "Utilizar os dados do Canvas do Percurso do Cliente",
+  "resource.api-value-proposition-canvas.tips.1": "Destaque para as características que aliviam as dores ou aumentam os ganhos",
+  "resource.api-value-proposition-canvas.tips.2": "Validar as características com os consumidores da API para garantir o alinhamento",
+  "resource.business-impact-canvas.title": "Canvas de Impacto no Negócio",
   "resource.business-impact-canvas.description": "Conceber uma arquitetura de plataforma API escalável e segura que satisfaça os requisitos comerciais e técnicos.",
   "resource.business-impact-canvas.outcomes": "Infraestrutura API escalável",
   "resource.business-impact-canvas.outcomes.1": "Segurança e conformidade melhoradas",
@@ -309,7 +309,7 @@
   "resource.business-impact-canvas.tips": "Envolver os arquitectos e os promotores no processo de conceção",
   "resource.business-impact-canvas.tips.1": "Utilizar incidentes anteriores para identificar potenciais riscos",
   "resource.business-impact-canvas.tips.2": "Dar prioridade às APIs críticas com o maior impacto comercial",
-  "resource.capacity-canvas.title": "Capacity Canvas",
+  "resource.capacity-canvas.title": "Canvas de Capacidade",
   "resource.capacity-canvas.description": "Planear a capacidade da API para satisfazer as exigências comerciais actuais e futuras, garantindo a escalabilidade e o desempenho.",
   "resource.capacity-canvas.outcomes": "Alinhamento da capacidade da API com os volumes de negócios",
   "resource.capacity-canvas.outcomes.1": "Preparado para as futuras tendências de consumo",
@@ -322,7 +322,7 @@
   "resource.capacity-canvas.tips": "Utilizar a análise para prever tendências de crescimento",
   "resource.capacity-canvas.tips.1": "Definir cenários de picos de utilização",
   "resource.capacity-canvas.tips.2": "Incluir testes de escalabilidade na fase de planeamento",
-  "resource.customer-journey-canvas.title": "Customer Journey Canvas",
+  "resource.customer-journey-canvas.title": "Canvas do Percurso do Cliente",
   "resource.customer-journey-canvas.description": "Mapear os percursos dos clientes para identificar necessidades e pontos problemáticos, melhorando a conceção da API e a experiência do utilizador.",
   "resource.customer-journey-canvas.outcomes": "Melhoria da compreensão do cliente",
   "resource.customer-journey-canvas.outcomes.1": "Conceção melhorada da API",
@@ -337,19 +337,19 @@
   "resource.customer-journey-canvas.steps.7": "Definir interações API para cada etapa",
   "resource.customer-journey-canvas.tips": "Iterar com o contributo da equipa para aperfeiçoar as etapas",
   "resource.customer-journey-canvas.tips.1": "Utilize os resultados deste quadro para informar outros quadros, como o quadro de proposta de valor da API",
-  "resource.event-canvas.title": "Event Canvas",
+  "resource.event-canvas.title": "Canvas de Eventos",
   "resource.event-canvas.description": "Conceber APIs orientadas para eventos, definindo eventos, accionadores e lógica de processamento.",
   "resource.event-canvas.outcomes": "Arquitetura orientada para eventos definida",
   "resource.event-canvas.outcomes.1": "Limpar os accionadores de eventos e a lógica de processamento",
   "resource.event-canvas.outcomes.2": "Melhoria da capacidade de resposta a alterações em tempo real",
   "resource.event-canvas.steps": "Identificar os principais eventos do sistema",
   "resource.event-canvas.steps.1": "Definir accionadores para cada evento",
-  "resource.event-canvas.steps.2": "Descrever a lógica de processamento backend para eventos",
+  "resource.event-canvas.steps.2": "Descrever a lógica de processamento back-end para eventos",
   "resource.event-canvas.steps.3": "Especificar os resultados ou reconhecimentos resultantes",
   "resource.event-canvas.tips": "Utilizar esquemas de eventos para normalizar os formatos de eventos",
   "resource.event-canvas.tips.1": "documentar fluxos e dependências de eventos",
   "resource.event-canvas.tips.2": "Validar o processamento de eventos com casos de teste",
-  "resource.graphql-canvas.title": "GraphQL Canvas",
+  "resource.graphql-canvas.title": "Canvas GraphQL",
   "resource.graphql-canvas.description": "Conceber APIs GraphQL definindo tipos, consultas, mutações e subscrições.",
   "resource.graphql-canvas.outcomes": "Conceção da API GraphQL estruturada",
   "resource.graphql-canvas.outcomes.1": "Tipos definidos e suas relações",
@@ -365,7 +365,7 @@
   "resource.graphql-canvas.tips": "Utilizar a introspeção para validar definições de tipos",
   "resource.graphql-canvas.tips.1": "documentar exemplos de consultas e mutações",
   "resource.graphql-canvas.tips.2": "Assegurar que os nomes dos tipos são descritivos e coerentes",
-  "resource.interaction-canvas.title": "Interaction Canvas",
+  "resource.interaction-canvas.title": "Canvas de Interação",
   "resource.interaction-canvas.description": "Definir interações API, fluxos de trabalho e respostas esperadas para garantir uma experiência consistente do consumidor API.",
   "resource.interaction-canvas.outcomes": "Fluxos de trabalho de interação API claros",
   "resource.interaction-canvas.outcomes.1": "Entradas e saídas definidas para cada interação",
@@ -378,7 +378,7 @@
   "resource.interaction-canvas.tips": "Comece com casos de utilização comuns antes de lidar com casos extremos",
   "resource.interaction-canvas.tips.1": "Simular interações com dados simulados para validar fluxos de trabalho",
   "resource.interaction-canvas.tips.2": "documentar as respostas esperadas para interações bem e mal sucedidas",
-  "resource.location-canvas.title": "Location Canvas",
+  "resource.location-canvas.title": "Canvas de Localização",
   "resource.location-canvas.description": "Mapeie as localizações dos fornecedores e consumidores de API para garantir a conformidade e o desempenho em todas as regiões.",
   "resource.location-canvas.outcomes": "Conformidade com a regulamentação local",
   "resource.location-canvas.outcomes.1": "Desempenho optimizado da API em todas as regiões",
@@ -387,12 +387,12 @@
   "resource.location-canvas.steps.1": "Documentar a localização dos consumidores.",
   "resource.location-canvas.steps.2": "Identificar os regulamentos aplicáveis.",
   "resource.location-canvas.steps.3": "Documentar onde os dados devem residir.",
-  "resource.location-canvas.steps.4": "Assegurar que as API estão acessíveis em todas as regiões da rede previstas.",
+  "resource.location-canvas.steps.4": "Assegurar que as APIs estão acessíveis em todas as regiões da rede previstas.",
   "resource.location-canvas.steps.5": "Validar o desempenho da rede em todas as regiões.",
   "resource.location-canvas.tips": "Colaborar com as equipas jurídicas e de conformidade",
   "resource.location-canvas.tips.1": "Validar o desempenho da rede nas principais regiões",
   "resource.location-canvas.tips.2": "Resolver proactivamente as restrições baseadas na localização",
-  "resource.rest-canvas.title": "REST Canvas",
+  "resource.rest-canvas.title": "Canvas REST",
   "resource.rest-canvas.description": "Conceber APIs utilizando os princípios RESTful, definindo recursos, verbos e exemplos de pedidos e respostas.",
   "resource.rest-canvas.outcomes": "Conceção consistente da API RESTful",
   "resource.rest-canvas.outcomes.1": "Recursos definidos e suas interações",
@@ -404,39 +404,39 @@
   "resource.rest-canvas.tips": "Utilizar métodos HTTP padrão (GET, POST, PUT, DELETE)",
   "resource.rest-canvas.tips.1": "Assegurar que os URIs dos recursos são intuitivos e coerentes",
   "resource.rest-canvas.tips.2": "tratamento de erros de documentos e códigos de resposta",
-  "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
-  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
-  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
-  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
-  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
-  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
-  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
-  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
-  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
-  "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
-  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
-  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
-  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
-  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
-  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
-  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
-  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
-  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
-  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
-  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
-  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
-  "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
-  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
-  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
-  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
-  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
+  "resource.capability-value-proposition-canvas.title": "Canvas da Proposta de Valor da Capacidade",
+  "resource.capability-value-proposition-canvas.description": "Um canvas independente da tecnologia para mapear tarefas, ganhos, dores e capacidades reutilizáveis candidatas dos consumidores antes de selecionar um estilo de integração.",
+  "resource.capability-value-proposition-canvas.outcomes": "Proposta de valor clara para a capacidade reutilizável",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Tarefas, ganhos e dores dos consumidores captados sem assumir uma tecnologia",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Capacidades reutilizáveis candidatas identificadas para avaliação de arquitetura",
+  "resource.capability-value-proposition-canvas.steps": "Liste as tarefas e resultados dos consumidores que a capacidade deve suportar.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identifique funcionalidades da capacidade que permitem ganhos.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identifique funcionalidades da capacidade que aliviam dores.",
+  "resource.capability-value-proposition-canvas.steps.3": "Agrupe as funcionalidades em capacidades reutilizáveis candidatas.",
+  "resource.capability-value-proposition-canvas.tips": "Mantenha-se independente da tecnologia até os requisitos apontarem para um estilo.",
+  "resource.capability-value-proposition-canvas.tips.1": "Utilize este recurso em vez do Canvas da Proposta de Valor da API quando a API ainda não é o estilo de integração escolhido.",
+  "resource.capability-business-model-canvas.title": "Canvas do Modelo de Negócio da Capacidade",
+  "resource.capability-business-model-canvas.description": "Um canvas de modelo de negócio para capacidades de integração reutilizáveis, cobrindo valor, consumidores, propriedade, envolvimento, custos e benefícios sem assumir disponibilização por API.",
+  "resource.capability-business-model-canvas.outcomes": "Modelo operacional viável para a capacidade reutilizável",
+  "resource.capability-business-model-canvas.outcomes.1": "Propriedade, consumidores, canais, parceiros e necessidades de suporte clarificados",
+  "resource.capability-business-model-canvas.outcomes.2": "Custos e benefícios visíveis antes do compromisso com a arquitetura",
+  "resource.capability-business-model-canvas.steps": "Resuma a proposta de valor da capacidade.",
+  "resource.capability-business-model-canvas.steps.1": "Identifique segmentos de consumidores e canais de envolvimento.",
+  "resource.capability-business-model-canvas.steps.2": "Defina atividades, recursos e parceiros-chave.",
+  "resource.capability-business-model-canvas.steps.3": "Capte custos e benefícios.",
+  "resource.capability-business-model-canvas.steps.4": "Clarifique propriedade, financiamento, suporte e expectativas de ciclo de vida.",
+  "resource.capability-business-model-canvas.steps.5": "Valide o modelo com consumidores, produtores e partes interessadas de governação.",
+  "resource.capability-business-model-canvas.tips": "Utilize este recurso em vez do Canvas do Modelo de Negócio da API quando o estilo de integração ainda está em aberto.",
+  "resource.capability-business-model-canvas.tips.1": "Mantenha o foco na viabilidade da capacidade reutilizável, não numa ligação pontual.",
+  "resource.consumer-experience-requirements-canvas.title": "Canvas de Requisitos da Experiência do Consumidor",
+  "resource.consumer-experience-requirements-canvas.description": "Um canvas de requisitos para a experiência orientada para os consumidores e necessidades não funcionais que deve orientar a escolha de arquitetura posterior.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Requisitos dos consumidores independentes da tecnologia",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Necessidades de experiência e não funcionais captadas antes do início da conceção",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Implicações de arquitetura documentadas para a seleção do estilo",
+  "resource.consumer-experience-requirements-canvas.steps": "Capte objetivos dos consumidores e contexto de utilização.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Documente expectativas de disponibilidade, atualidade, volume, desempenho, qualidade dos dados e consistência.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Documente expectativas de segurança, privacidade, integração, mudança, observabilidade, suporte e recuperação.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Resuma o que os requisitos implicam para possíveis estilos de arquitetura.",
+  "resource.consumer-experience-requirements-canvas.tips": "Utilize this as the bridge between capability value and architecture decision.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Não escolha API, evento, ficheiro, stream ou produto de dados até os requisitos indicarem o melhor ajuste."
 }
diff --git a/src/data/method/pt/labels.stakeholders.json b/src/data/method/pt/labels.stakeholders.json
index 8f27a7d..3d250b7 100644
--- a/src/data/method/pt/labels.stakeholders.json
+++ b/src/data/method/pt/labels.stakeholders.json
@@ -22,28 +22,28 @@
   "stakeholder.api-architect.description": "",
   "stakeholder.integration-architect.title": "Integration Architect",
   "stakeholder.integration-architect.description": "",
-  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.title": "Responsável pela plataforma",
   "stakeholder.platform-owner.description": "",
-  "stakeholder.api-designer.title": "Designer API",
-  "stakeholder.api-designer.description": "Modela o contrato API, o modelo de interação, a consistência e a usabilidade das capacidades expostas.",
+  "stakeholder.api-designer.title": "Designer de API",
+  "stakeholder.api-designer.description": "Modela o contrato de interface da API, o modelo de interação, a consistência e a usabilidade das capacidades expostas.",
   "stakeholder.api-engineer.title": "Engenheiro de Entrega",
-  "stakeholder.api-engineer.description": "Responsável por implementação, automação, testes e preocupações de fluxo de lançamento necessárias para entregar a API de forma confiável.",
-  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.api-engineer.description": "Responsável pela implementação, automação, testes e preocupações do fluxo de lançamento necessárias para entregar a API de forma fiável.",
+  "stakeholder.automation-owner.title": "Responsável pela automação",
   "stakeholder.automation-owner.description": "",
   "stakeholder.process-owner.title": "Process Owner",
   "stakeholder.process-owner.description": "",
-  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.title": "Engenheiro de automação",
   "stakeholder.automation-engineer.description": "",
   "stakeholder.security-specialist.title": "Especialista em Segurança",
-  "stakeholder.security-specialist.description": "Garante que os riscos de segurança, controles e limites de confiança sejam abordados ao longo do ciclo de vida da API.",
+  "stakeholder.security-specialist.description": "Garante que os riscos de segurança, controlos e fronteiras de confiança são tratados ao longo do ciclo de vida da API.",
   "stakeholder.compliance-specialist.title": "Especialista em Conformidade e Legal",
-  "stakeholder.compliance-specialist.description": "Esclarece os requisitos legais, de privacidade, regulatórios e contratuais que afetam a API.",
-  "stakeholder.governance-specialist.title": "Proprietário da Governança",
-  "stakeholder.governance-specialist.description": "Representa práticas de revisão, auditoria e governança em toda a organização para qualidade e conformidade das APIs.",
-  "stakeholder.api-devrel-specialist.title": "Proprietário da Documentação e Desenvolvimento Comunitário",
-  "stakeholder.api-devrel-specialist.description": "Possui o conteúdo de integração, a comunicação com os desenvolvedores e a qualidade da documentação para os usuários da API.",
-  "stakeholder.operations-specialist.title": "Proprietário do Suporte e Operações",
+  "stakeholder.compliance-specialist.description": "Esclarece os requisitos legais, de privacidade, regulamentares e contratuais que afetam a API.",
+  "stakeholder.governance-specialist.title": "Responsável pela governação",
+  "stakeholder.governance-specialist.description": "Representa práticas de revisão, auditoria e governação em toda a organização para qualidade e conformidade das APIs.",
+  "stakeholder.api-devrel-specialist.title": "Responsável pela documentação e desenvolvimento da comunidade",
+  "stakeholder.api-devrel-specialist.description": "É responsável pelo conteúdo de integração, pela comunicação com programadores e pela qualidade da documentação para os utilizadores da API.",
+  "stakeholder.operations-specialist.title": "Responsável pelo suporte e operações",
   "stakeholder.operations-specialist.description": "Representa o suporte em tempo de execução, o tratamento de incidentes, a observabilidade e a prontidão operacional.",
-  "stakeholder.partner-specialist.title": "Gerente de Parceiros ou Fornecedores",
+  "stakeholder.partner-specialist.title": "Gestor de parceiros ou fornecedores",
   "stakeholder.partner-specialist.description": "Coordena as relações com parceiros externos, fornecedores ou vendedores que influenciam a estratégia e a entrega da API."
 }
diff --git a/src/data/method/pt/labels.stations.json b/src/data/method/pt/labels.stations.json
index 2ff34c5..fef1321 100644
--- a/src/data/method/pt/labels.stations.json
+++ b/src/data/method/pt/labels.stations.json
@@ -2,22 +2,22 @@
   "group.core-stations.title": "Estações centrais do ciclo de vida da API",
   "group.core-stations.description": "As estações centrais do API Metro, onde as equipas podem aprender a criar e gerir APIs de forma eficaz.",
   "station.api-product-strategy.title": "Estratégia de produtos API - Transforme APIs em produtos estratégicos",
-  "station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objectivos comerciais desde o primeiro dia.",
-  "station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projectos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
+  "station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objetivos de negócio desde o primeiro dia.",
+  "station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projetos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
   "station.api-product-strategy.apply_in_work": "Fornecer diretrizes e modelos para a criação de modelos comerciais, propostas de valor e roteiros de API.",
   "station.api-product-strategy.outcomes": "Uma proposta de valor e um público-alvo da API simples",
-  "station.api-product-strategy.outcomes.1": "Linguagem partilhada entre o produto, o design e a tecnologia",
+  "station.api-product-strategy.outcomes.1": "Linguagem partilhada entre o produto, a conceção e a tecnologia",
   "station.api-product-strategy.outcomes.2": "Um argumento sólido ou um caso para financiamento/aprovação",
-  "station.api-product-strategy.how_it_works": "Explore o problema do cliente ou parceiro que espera resolver com as APIs. Mapeie as partes interessadas, os seus percursos e os resultados utilizando a tela do Percurso do Cliente.",
+  "station.api-product-strategy.how_it_works": "Explore o problema do cliente ou parceiro que espera resolver com as APIs. Mapeie as partes interessadas, os seus percursos e os resultados utilizando a Canvas do Percurso do Cliente.",
   "station.api-product-strategy.how_it_works.1": "Definir as entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre jornadas e, eventualmente, APIs.",
-  "station.api-product-strategy.how_it_works.2": "Use o API Value Proposition Canvas para capturar as tarefas de negócios suportadas e as dores, ganhos e recursos do consumidor da API que moldam APIs novas ou reutilizáveis.",
-  "station.api-product-strategy.how_it_works.3": "Defina o valor - para os utilizadores e para a empresa - com a tela do modelo de negócio da API para tornar a sua estratégia de API visual, partilhável e fácil de validar com os seus consumidores de API na estação seguinte.",
-  "station.api-consumer-experience.title": "Experiência do consumidor da API - Design para os utilizadores reais da sua API",
+  "station.api-product-strategy.how_it_works.2": "Utilize o Canvas da Proposta de Valor da API para capturar as tarefas de negócios suportadas e as dores, ganhos e recursos do consumidor da API que moldam APIs novas ou reutilizáveis.",
+  "station.api-product-strategy.how_it_works.3": "Defina o valor - para os utilizadores e para a empresa - com a Canvas do Modelo de Negócio da API para tornar a sua estratégia de API visual, partilhável e fácil de validar com os seus consumidores de API na estação seguinte.",
+  "station.api-consumer-experience.title": "Experiência do consumidor da API - Conceção para os utilizadores reais da sua API",
   "station.api-consumer-experience.description": "Certifique-se de que a sua API é detetável, compreensível e utilizável - antes e depois do lançamento.",
-  "station.api-consumer-experience.why_it_matters": "As APIs excelentes não funcionam apenas - elas são intuitivas. Quer o consumidor seja um programador interno, um parceiro externo ou um agente de IA, a sua experiência determina a adoção.\n\nSem um plano de experiência claro:\n- Grandes APIs ficam sem uso\n- As equipas perdem tempo a tentar adivinhar como utilizar a sua API\n- Os ciclos de feedback estão quebrados ou ausentes.\n\nEsta estação ajuda-o a ver a sua API através dos olhos dos seus consumidores.",
-  "station.api-consumer-experience.how_it_works": "Analise o API Value Proposition Canvas existente sob a perspectiva do consumidor da API. Mantenha as tarefas de negócios suportadas estáveis ​​e enriqueça os recursos que aliviam problemas e possibilitam ganhos com as preocupações do consumidor da API, para que elas possam orientar as decisões de design futuras.",
-  "station.api-consumer-experience.how_it_works.1": "Use o Customer Journey Canvas para a jornada do consumidor da API, desde a descoberta e avaliação até a integração, resolução de problemas e uso contínuo.",
-  "station.api-consumer-experience.how_it_works.2": "Use a jornada resultante para melhorar a integração, a documentação, o suporte e os ciclos de feedback para o consumidor da API.",
+  "station.api-consumer-experience.why_it_matters": "As APIs excelentes não funcionam apenas - elas são intuitivas. Quer o consumidor seja um programador interno, um parceiro externo ou um agente de IA, a sua experiência determina a adoção.\n\nSnum plano de experiência claro:\n- Grandes APIs ficam sem uso\n- As equipas perdem tempo a tentar adivinhar como utilizar a sua API\n- Os ciclos de feedback estão quebrados ou ausentes.\n\nEsta estação ajuda-o a ver a sua API através dos olhos dos seus consumidores.",
+  "station.api-consumer-experience.how_it_works": "Analise o Canvas da Proposta de Valor da API existente sob a perspectiva do consumidor da API. Mantenha as tarefas de negócios suportadas estáveis ​​e enriqueça os recursos que aliviam problemas e possibilitam ganhos com as preocupações do consumidor da API, para que elas possam orientar as decisões de conceção futuras.",
+  "station.api-consumer-experience.how_it_works.1": "Utilize o Canvas do Percurso do Cliente para a jornada do consumidor da API, desde a descoberta e avaliação até a integração, resolução de problemas e uso contínuo.",
+  "station.api-consumer-experience.how_it_works.2": "Utilize a jornada resultante para melhorar a integração, a documentação, o suporte e os ciclos de feedback para o consumidor da API.",
   "station.api-consumer-experience.apply_in_work": "Fornecer diretrizes, ferramentas e mecanismos de feedback para compreender, analisar e melhorar a experiência interna e externa dos programadores e parceiros.",
   "station.api-consumer-experience.outcomes": "Identifique e dê prioridade aos seus consumidores de API",
   "station.api-consumer-experience.outcomes.1": "Definir o percurso da experiência API",
@@ -26,59 +26,59 @@
   "station.api-platform-architecture.title": "Arquitetura da plataforma API - Arquitetar APIs para escalabilidade e reutilização",
   "station.api-platform-architecture.description": "Garanta a escalabilidade, a reutilização e a governação da sua API e dos componentes da plataforma.",
   "station.api-platform-architecture.why_it_matters": "Quando as APIs são escalonadas entre equipas, a sua plataforma deve permitir a governação e a reutilização sem bloquear a velocidade. Esta estação mostra como arquitetar APIs para longevidade, segurança e eficiência.",
-  "station.api-platform-architecture.apply_in_work": "Estabelecer uma infraestrutura escalável, segura e compatível com as operações de API. Fornecer orientações sobre as melhores práticas de arquitetura.",
+  "station.api-platform-architecture.apply_in_work": "Estabelecer uma infraestrutura escalável, segura e compatível com as operações de API. Fornecer orientações sobre as boas práticas de arquitetura.",
   "station.api-platform-architecture.outcomes": "Corte APIs redundantes e reduza os custos da plataforma de nuvem",
-  "station.api-platform-architecture.outcomes.1": "Implementar uma governação consistente sem um forte controlo do topo para a base",
+  "station.api-platform-architecture.outcomes.1": "Implementar uma governação consistente snum forte controlo do topo para a base",
   "station.api-platform-architecture.outcomes.2": "Conceção para reutilização interna e escalabilidade externa",
-  "station.api-platform-architecture.how_it_works": "O Business Impact Canvas ajuda a identificar e mitigar os riscos relacionados com a disponibilidade, segurança e funcionalidade da API para apoiar decisões de arquitetura informadas.",
+  "station.api-platform-architecture.how_it_works": "O Canvas de Impacto no Negócio ajuda a identificar e mitigar os riscos relacionados com a disponibilidade, segurança e funcionalidade da API para apoiar decisões de arquitetura informadas.",
   "station.api-platform-architecture.how_it_works.1": "Mapear as localizações regulamentares, de conformidade e de rede dos fornecedores e consumidores de API para garantir a acessibilidade e a conformidade.",
-  "station.api-platform-architecture.how_it_works.2": "O Capacity Canvas alinha os padrões das transacções comerciais, as tendências de consumo futuro e as soluções técnicas para garantir a escalabilidade e o desempenho da API, fornecendo dados essenciais para as decisões de escalabilidade e o planeamento da infraestrutura.",
-  "station.api-platform-architecture.how_it_works.3": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "station.api-platform-architecture.how_it_works.2": "O Canvas de Capacidade alinha os padrões das transacções comerciais, as tendências de consumo futuro e as soluções técnicas para garantir a escalabilidade e o desempenho da API, fornecendo dados essenciais para as decisões de escalabilidade e o planeamento da infraestrutura.",
+  "station.api-platform-architecture.how_it_works.3": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
   "station.api-design.title": "Conceção da API - Conceber APIs que proporcionem valor",
-  "station.api-design.description": "Criar projetos de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados.",
-  "station.api-design.why_it_matters": "Projetar APIs não se resume apenas a nomear endpoints. Um bom projeto garante que as APIs sejam utilizáveis, consistentes e alinhadas com os objetivos comerciais e técnicos. Um projeto inadequado leva a um acoplamento rígido, baixa reutilização e retrabalho dispendioso entre as equipes.",
+  "station.api-design.description": "Criar conceções de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados.",
+  "station.api-design.why_it_matters": "Conceber APIs não se resume apenas a nomear endpoints. Um bom projeto garante que as APIs sejam utilizáveis, consistentes e alinhadas com os objetivos de negócio e técnicos. Um projeto inadequado leva a um acoplamento rígido, baixa reutilização e retrabalho dispendioso entre as equipas.",
   "station.api-design.apply_in_work": "Forneça padrões de projeto reutilizáveis, padrões compartilhados e ferramentas de validação para especificações de API. Garanta que as decisões de projeto sejam consistentes, revisadas antecipadamente e alinhadas com a intenção de negócios.",
   "station.api-design.outcomes": "Conceção de API bem documentada e coerente",
-  "station.api-design.outcomes.1": "Contratos API reutilizáveis e validados",
+  "station.api-design.outcomes.1": "Contratos de interface da API reutilizáveis e validados",
   "station.api-design.outcomes.2": "Desenhos alinhados com modelos de domínio e padrões de interação",
-  "station.api-design.outcomes.3": "Rastreabilidade da conceção ao valor comercial",
+  "station.api-design.outcomes.3": "Rastreabilidade da conceção ao valor de negócio",
   "station.api-design.how_it_works": "Definir entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre APIs.",
   "station.api-design.how_it_works.1": "Utilize o Canvas de Interação para definir a forma como os consumidores irão interagir com a API, garantindo que esta satisfaz as suas necessidades e expectativas.",
-  "station.api-design.how_it_works.2": "Aplicar padrões de conceção REST para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "station.api-design.how_it_works.3": "Aplicar padrões de conceção orientados para eventos para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "station.api-design.how_it_works.4": "Aplicar padrões de design GraphQL para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "station.api-design.how_it_works.5": "Use os princípios de projeto e o guia de estilo de API para alinhar suas decisões de projeto com regras compartilhadas e permitir uma validação de auditoria consistente.",
-  "station.api-design.how_it_works.6": "Aplique abordagens do tipo ‘contrato primeiro’ ou ‘design primeiro’ para capturar e validar o contrato da API antes da implementação.",
-  "station.api-design.how_it_works.7": "Use a Lista de Verificação de Auditoria da API para garantir que o design da API atenda aos requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "station.api-design.how_it_works.2": "Aplicar padrões de conceção REST para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "station.api-design.how_it_works.3": "Aplicar padrões de conceção orientados para eventos para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "station.api-design.how_it_works.4": "Aplicar padrões de conceção GraphQL para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "station.api-design.how_it_works.5": "Utilize os princípios de projeto e o guia de estilo da API para alinhar suas decisões de projeto com regras compartilhadas e permitir uma validação de auditoria consistente.",
+  "station.api-design.how_it_works.6": "Aplique abordagens do tipo ‘contrato primeiro’ ou ‘design primeiro’ para capturar e validar o contrato de interface da API antes da implementação.",
+  "station.api-design.how_it_works.7": "Utilize a Lista de Verificação de Auditoria da API para garantir que a conceção da API satisfaça os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
   "station.api-delivery.title": "Entrega da API - Fornecer APIs seguras e fiáveis",
-  "station.api-delivery.description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e práticas recomendadas de engenharia.",
-  "station.api-delivery.why_it_matters": "Mesmo os melhores projectos de API falham se a entrega for inconsistente. Esta estação assegura que as suas APIs são construídas com qualidade, testadas exaustivamente e implementadas de forma fiável - permitindo iterações mais rápidas e maior confiança.",
-  "station.api-delivery.apply_in_work": "Fornecer estruturas de codificação, bibliotecas e normas para a implementação de API. Implementar pipelines de CI/CD, estruturas de garantia de qualidade e ferramentas de automatização da implantação.",
+  "station.api-delivery.description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e boas práticas de engenharia.",
+  "station.api-delivery.why_it_matters": "Mesmo os melhores conceções de API falham se a entrega for inconsistente. Esta estação assegura que as suas APIs são construídas com qualidade, testadas exaustivamente e implementadas de forma fiável - permitindo iterações mais rápidas e maior confiança.",
+  "station.api-delivery.apply_in_work": "Fornecer estruturas de codificação, bibliotecas e normas para a implementação de API. Implementar pipelines de CI/CD, estruturas de garantia de qualidade e ferramentas de automatização da disponibilização.",
   "station.api-delivery.outcomes": "APIs implementadas utilizando estruturas e padrões testados",
   "station.api-delivery.outcomes.1": "Pipelines de CI/CD fiáveis e automatizados",
   "station.api-delivery.outcomes.2": "Testes funcionais e não funcionais integrados",
   "station.api-delivery.outcomes.3": "Condutas de entrega seguras e conformes",
-  "station.api-delivery.how_it_works": "Use as Melhores Práticas de Desenvolvimento de API como orientação para implementar o contrato validado com frameworks e bibliotecas estabelecidos, garantindo que o resultado seja reutilizável e sustentável.",
-  "station.api-delivery.how_it_works.1": "Construa a implementação da API a partir do contrato validado usando frameworks, bibliotecas e padrões da equipe estabelecidos.",
-  "station.api-delivery.how_it_works.2": "Testar a funcionalidade, a segurança e o desempenho das API, utilizando ferramentas de teste automatizadas.",
+  "station.api-delivery.how_it_works": "Utilize as Melhores Práticas de Desenvolvimento de API como orientação para implementar o contrato validado com frameworks e bibliotecas estabelecidos, garantindo que o resultado seja reutilizável e sustentável.",
+  "station.api-delivery.how_it_works.1": "Construa a implementação da API a partir do contrato validado usando frameworks, bibliotecas e padrões da equipa estabelecidos.",
+  "station.api-delivery.how_it_works.2": "Testar a funcionalidade, a segurança e o desempenho das APIs, utilizando ferramentas de teste automatizadas.",
   "station.api-delivery.how_it_works.3": "Utilize pipelines CI/CD para automatizar os processos de construção, teste e implementação, garantindo uma qualidade e rastreabilidade consistentes.",
   "station.api-delivery.how_it_works.4": "Garantir que as APIs cumprem os requisitos de segurança e conformidade através de verificações e auditorias automatizadas.",
   "station.api-delivery.how_it_works.5": "Utilize a lista de verificação de auditoria da API para garantir que a API cumpre os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
   "station.api-audit.title": "Auditoria de API - Auditoria de APIs para conformidade e qualidade",
-  "station.api-audit.description": "Valide se as APIs atendem aos padrões de negócios, design e operacionais antes da publicação e exposição.",
-  "station.api-audit.why_it_matters": "As APIs são produtos de longa duração e devem atender às expectativas de qualidade, consistência e conformidade. A auditoria conecta as decisões de design, a implementação e a prontidão operacional a padrões definidos, reduzindo o risco antes da exposição.",
+  "station.api-audit.description": "Valide se as APIs satisfazemos padrões de negócio, conceção e operacionais antes da publicação e exposição.",
+  "station.api-audit.why_it_matters": "As APIs são produtos de longa duração e devem atender às expectativas de qualidade, consistência e conformidade. A auditoria conecta as decisões de conceção, a implementação e a prontidão operacional a padrões definidos, reduzindo o risco antes da exposição.",
   "station.api-audit.apply_in_work": "Estabeleça um processo de auditoria consistente que avalie a prontidão da API em todas as etapas do ciclo de vida usando critérios, evidências e padrões definidos. Garanta que as lacunas sejam identificadas antecipadamente e resolvidas antes da publicação.",
-  "station.api-audit.outcomes": "As APIs cumprem as normas internas e externas",
+  "station.api-audit.outcomes": "As APIs cumprems normas internas e externas",
   "station.api-audit.outcomes.1": "Documentação clara das decisões de conceção e implementação da API",
   "station.api-audit.outcomes.2": "Segurança, desempenho e conformidade validados",
   "station.api-audit.outcomes.3": "Redução do risco de problemas na produção",
-  "station.api-audit.how_it_works": "Realizar auditorias para garantir que as APIs cumprem as normas organizacionais, técnicas e legais antes da publicação.",
+  "station.api-audit.how_it_works": "Realizar auditorias para garantir que as APIs cumprems normas organizacionais, técnicas e legais antes da publicação.",
   "station.api-audit.how_it_works.1": "Utilizar listas de controlo, linters e ferramentas de teste para verificar a consistência e a conformidade com as normas.",
-  "station.api-audit.how_it_works.2": "Colaborar com as equipas de governação e especialistas no domínio para garantir que as API estão prontas para produção.",
+  "station.api-audit.how_it_works.2": "Colaborar com as equipas de governação e especialistas no domínio para garantir que as APIs estão prontas para produção.",
   "station.api-publishing.title": "Publicação de API - Publique APIs com confiança",
   "station.api-publishing.description": "Exponha as APIs de forma segura e clara ao público certo com a documentação e os processos corretos.",
-  "station.api-publishing.why_it_matters": "A publicação é mais do que a implantação - trata-se de capacidade de descoberta, acesso e suporte. Se as APIs não forem publicadas corretamente, não serão utilizadas, reutilizadas ou protegidas de forma eficaz.",
-  "station.api-publishing.apply_in_work": "Permitir que as API sejam publicadas no ambiente relevante e ter mecanismos claros de registo e acesso (por exemplo, chaves de API, OAuth, planos de subscrição), dependendo dos segmentos de consumidores de API e dos requisitos de segurança e conformidade.",
+  "station.api-publishing.why_it_matters": "A publicação é mais do que a disponibilização - trata-se de capacidade de descoberta, acesso e suporte. Se as APIs não forem publicadas corretamente, não serão utilizadas, reutilizadas ou protegidas de forma eficaz.",
+  "station.api-publishing.apply_in_work": "Permitir que as APIs sejam publicadas no ambiente relevante e ter mecanismos claros de registo e acesso (por exemplo, chaves de API, OAuth, planos de subscrição), dependendo dos segmentos de consumidores de API e dos requisitos de segurança e conformidade.",
   "station.api-publishing.outcomes": "APIs publicadas no ambiente correto (privado, parceiro, público)",
   "station.api-publishing.outcomes.1": "Processos claros de integração e registo da API",
   "station.api-publishing.outcomes.2": "Documentação, modelos e políticas de segurança disponíveis",
@@ -94,14 +94,14 @@
   "station.monitoring-and-improving.outcomes.1": "Ciclos de feedback do programador em vigor",
   "station.monitoring-and-improving.outcomes.2": "Questões identificadas e tratadas continuamente",
   "station.monitoring-and-improving.outcomes.3": "Iteração da API alinhada com as necessidades dos utilizadores",
-  "station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
   "station.monitoring-and-improving.how_it_works.1": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.",
   "station.monitoring-and-improving.how_it_works.2": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua.",
   "group.sub-stations.title": "Sub-estações do ciclo de vida API",
-  "group.sub-stations.description": "Subestações que fornecem recursos adicionais, ferramentas e melhores práticas para equipas de API.",
+  "group.sub-stations.description": "Subestações que fornecem recursos adicionais, ferramentas e boas práticas para equipas de API.",
   "station.user-experience.title": "Experiência do utilizador - Conceber APIs com o utilizador em mente",
-  "station.user-experience.description": "Assegurar que as API são concebidas tendo em mente o utilizador final, proporcionando uma experiência intuitiva e sem descontinuidades.",
-  "station.user-experience.why_it_matters": "As API não são apenas produtos técnicos; são produtos virados para o utilizador. Uma má experiência do utilizador pode levar a uma baixa adoção e à frustração. Esta estação ajuda as equipas a conceber APIs que sejam fáceis de utilizar e que satisfaçam as necessidades dos consumidores.",
+  "station.user-experience.description": "Assegurar que as APIs são concebidas tendo em mente o utilizador final, proporcionando uma experiência intuitiva e sem descontinuidades.",
+  "station.user-experience.why_it_matters": "As APIs não são apenas produtos técnicos; são produtos virados para o utilizador. Uma má experiência do utilizador pode levar a uma baixa adoção e à frustração. Esta estação ajuda as equipas a conceber APIs que sejam fáceis de utilizar e que satisfaçam as necessidades dos consumidores.",
   "station.user-experience.apply_in_work": "Fornecer orientações, modelos e ferramentas de experiência do utilizador para a conceção de API. Assegurar que as equipas seguem práticas de design centradas no utilizador e incorporam o feedback do utilizador nas iterações da API.",
   "station.user-experience.outcomes": "APIs concebidas a pensar nas necessidades dos utilizadores",
   "station.user-experience.outcomes.1": "Interfaces de utilizador intuitivas e coerentes",
@@ -111,26 +111,26 @@
   "station.user-experience.how_it_works.1": "Realize estudos de utilizadores para obter informações sobre a forma como os consumidores interagem com os serviços do ecossistema ou com as suas aplicações que consomem API.",
   "station.user-experience.how_it_works.2": "Documentar os requisitos da experiência do utilizador para que possam ser utilizados na conceção da API, garantindo que são intuitivos e fáceis de utilizar.",
   "station.market-insights.title": "Informações sobre o mercado - Compreender o cenário das API",
-  "station.market-insights.description": "Analisar as tendências do mercado, as API da concorrência e as normas da indústria para informar a estratégia de API.",
+  "station.market-insights.description": "Analisar as tendências do mercado, as APIs da concorrência e as normas da indústria para informar a estratégia de API.",
   "station.market-insights.why_it_matters": "Compreender o panorama do mercado ajuda as equipas a identificar oportunidades, evitar armadilhas e alinhar as suas APIs com as normas da indústria. Esta estação fornece ferramentas para analisar as tendências do mercado e as ofertas dos concorrentes.",
   "station.market-insights.apply_in_work": "Fornecer ferramentas de pesquisa de mercado, modelos de análise da concorrência e recursos de normas do sector. Assegurar que as equipas se mantêm informadas sobre as tendências do mercado e incorporam os conhecimentos na estratégia de API.",
   "station.market-insights.outcomes": "Análise das tendências do mercado e das APIs dos concorrentes",
-  "station.market-insights.outcomes.1": "Identificação das normas e melhores práticas do sector",
+  "station.market-insights.outcomes.1": "Identificação das normas e boas práticas do sector",
   "station.market-insights.outcomes.2": "Estratégia de API alinhada com as necessidades do mercado",
   "station.market-insights.outcomes.3": "Tomada de decisões informadas com base em conhecimentos do mercado",
-  "station.market-insights.how_it_works": "Realizar estudos de mercado para identificar tendências, oportunidades e ameaças no panorama das API.",
-  "station.market-insights.how_it_works.1": "Analisar as API da concorrência para compreender os seus pontos fortes, fracos e pontos de venda únicos.",
-  "station.market-insights.how_it_works.2": "Identificar as normas e as melhores práticas do sector para garantir que as API são competitivas e estão em conformidade.",
-  "station.business-goals.title": "Objectivos comerciais - Alinhar as APIs com os objectivos comerciais",
-  "station.business-goals.description": "Assegurar que as API estão alinhadas com os objectivos comerciais e contribuem para os objectivos organizacionais globais.",
-  "station.business-goals.why_it_matters": "As APIs não devem ser construídas isoladamente; elas devem apoiar e impulsionar os objectivos comerciais. Esta estação ajuda as equipas a alinharem as suas APIs com os objectivos estratégicos, assegurando que fornecem um verdadeiro valor comercial.",
-  "station.business-goals.apply_in_work": "Fornecer estruturas, modelos e ferramentas de alinhamento comercial para definir o valor comercial da API. Garantir que as equipas revejam e alinhem regularmente as APIs com os objectivos comerciais em mudança.",
-  "station.business-goals.outcomes": "APIs alinhadas com os objectivos comerciais",
-  "station.business-goals.outcomes.1": "Valor comercial claro definido para cada API",
+  "station.market-insights.how_it_works": "Realizar estudos de mercado para identificar tendências, oportunidades e ameaças no panorama das APIs.",
+  "station.market-insights.how_it_works.1": "Analisar as APIs da concorrência para compreender os seus pontos fortes, fracos e pontos de venda únicos.",
+  "station.market-insights.how_it_works.2": "Identificar as normas e as boas práticas do sector para garantir que as APIs são competitivas e estão em conformidade.",
+  "station.business-goals.title": "Objectivos comerciais - Alinhar as APIs com os objetivos de negócio",
+  "station.business-goals.description": "Assegurar que as APIs estão alinhadas com os objetivos de negócio e contribuem para os objetivos organizacionais globais.",
+  "station.business-goals.why_it_matters": "As APIs não devem ser construídas isoladamente; elas devem apoiar e impulsionar os objetivos de negócio. Esta estação ajuda as equipas a alinharem as suas APIs com os objetivos estratégicos, assegurando que fornecnum verdadeiro valor de negócio.",
+  "station.business-goals.apply_in_work": "Fornecer estruturas, modelos e ferramentas de alinhamento comercial para definir o valor de negócio da API. Garantir que as equipas revejam e alinhem regularmente as APIs com os objetivos de negócio em mudança.",
+  "station.business-goals.outcomes": "APIs alinhadas com os objetivos de negócio",
+  "station.business-goals.outcomes.1": "Valor de negócio claro definido para cada API",
   "station.business-goals.outcomes.2": "Adesão e apoio das partes interessadas às iniciativas API",
   "station.business-goals.outcomes.3": "As APIs contribuem para o sucesso organizacional",
-  "station.business-goals.how_it_works": "Definir os objectivos comerciais e a forma como as API podem apoiá-los utilizando **o Business Model Canvas**. Se o seu negócio é fornecer APIs, passe pela *estação de Estratégia de Produto de API* e preencha **o Modelo de Negócio de API Canvas**.",
-  "station.business-goals.how_it_works.1": "Identificar indicadores-chave de desempenho (KPIs) para medir o sucesso da API em relação aos objectivos comerciais.",
+  "station.business-goals.how_it_works": "Definir os objetivos de negócio e a forma como as APIs podem apoiá-los utilizando **o Business Model Canvas**. Se o seu negócio é fornecer APIs, passe pela *estação de Estratégia de Produto de API* e preencha **o Modelo de Negócio de API Canvas**.",
+  "station.business-goals.how_it_works.1": "Identificar indicadores-chave de desempenho (KPIs) para medir o sucesso da API em relação aos objetivos de negócio.",
   "station.business-goals.how_it_works.2": "Envolver as partes interessadas para garantir o alinhamento e o apoio às iniciativas da API.",
   "station.competitive-analysis.title": "Análise competitiva - Fique à frente no mercado de API",
   "station.competitive-analysis.description": "Analisar as APIs dos concorrentes para identificar pontos fortes, pontos fracos e oportunidades de diferenciação.",
@@ -141,8 +141,8 @@
   "station.competitive-analysis.outcomes.2": "Estratégia de API baseada em informações sobre a concorrência",
   "station.competitive-analysis.outcomes.3": "Aumento da competitividade no mercado de API",
   "station.competitive-analysis.how_it_works": "Efetuar uma análise da concorrência para identificar os principais concorrentes, as suas ofertas de API e os seus pontos fortes e fracos.",
-  "station.competitive-analysis.how_it_works.1": "Identifique as lacunas no mercado que as suas API podem preencher, com base nas ofertas da concorrência.",
-  "station.competitive-analysis.how_it_works.2": "Desenvolva uma estratégia de diferenciação que destaque as caraterísticas e benefícios únicos das suas APIs.",
+  "station.competitive-analysis.how_it_works.1": "Identifique as lacunas no mercado que as suas APIs podem preencher, com base nas ofertas da concorrência.",
+  "station.competitive-analysis.how_it_works.2": "Desenvolva uma estratégia de diferenciação que destaque as características e benefícios únicos das suas APIs.",
   "station.ecosystem-vision.title": "Visão do ecossistema - Criar APIs para um ecossistema próspero",
   "station.ecosystem-vision.description": "Crie uma visão de como as suas APIs se encaixam num ecossistema maior, permitindo a colaboração e a inovação.",
   "station.ecosystem-vision.why_it_matters": "As APIs não são produtos autónomos; fazem parte de um ecossistema maior. Esta estação ajuda as equipas a definir como as suas APIs interagem com outros sistemas, plataformas e serviços para criar um ecossistema próspero que promove a colaboração e a inovação.",
@@ -150,7 +150,7 @@
   "station.ecosystem-vision.outcomes": "Definição de uma visão clara do ecossistema para as API",
   "station.ecosystem-vision.outcomes.1": "APIs concebidas para permitir a colaboração e a integração",
   "station.ecosystem-vision.outcomes.2": "Parceiros do ecossistema identificados e envolvidos",
-  "station.ecosystem-vision.outcomes.3": "As API contribuem para um ecossistema dinâmico",
+  "station.ecosystem-vision.outcomes.3": "As APIs contribuem para um ecossistema dinâmico",
   "station.ecosystem-vision.how_it_works": "Defina a visão do ecossistema para as suas APIs, incluindo a forma como estas irão interagir com outros sistemas e plataformas.",
   "station.ecosystem-vision.how_it_works.1": "Identificar os principais parceiros e intervenientes do ecosistema que irão beneficiar ou contribuir para o ecosistema.",
   "station.ecosystem-vision.how_it_works.2": "Conceber APIs para permitir uma integração e colaboração perfeitas no ecossistema.",
@@ -163,9 +163,9 @@
   "station.scalable-infrastructure.outcomes.2": "Infra-estruturas concebidas para o crescimento futuro",
   "station.scalable-infrastructure.outcomes.3": "Redução do tempo de inatividade e melhoria da experiência do utilizador",
   "station.scalable-infrastructure.how_it_works": "Conceber a infraestrutura da API para ser escalável e resiliente, utilizando padrões e tecnologias nativos da nuvem.",
-  "station.scalable-infrastructure.how_it_works.1": "Implementar o equilíbrio de carga, o armazenamento em cache e outras técnicas para garantir uma elevada disponibilidade e desempenho. Recolher os requisitos de infraestrutura das equipas de API utilizando o Capacity Canvas",
+  "station.scalable-infrastructure.how_it_works.1": "Implementar o equilíbrio de carga, o armazenamento em cache e outras técnicas para garantir uma elevada disponibilidade e desempenho. Recolher os requisitos de infraestrutura das equipas de API utilizando o Canvas de Capacidade",
   "station.scalable-infrastructure.how_it_works.2": "Monitorizar o desempenho e a capacidade da infraestrutura para garantir que esta consegue dar resposta à crescente procura.",
-  "station.legal-and-compliance.title": "Legal e Conformidade - Garantir que as APIs cumprem as normas regulamentares",
+  "station.legal-and-compliance.title": "Legal e Conformidade - Garantir que as APIs cumprems normas regulamentares",
   "station.legal-and-compliance.description": "Garanta que as APIs cumprem os requisitos legais e regulamentares, protegendo a sua organização e os seus utilizadores.",
   "station.legal-and-compliance.why_it_matters": "As APIs devem cumprir as normas legais e regulamentares para proteger a sua organização e os utilizadores. Esta estação fornece ferramentas e diretrizes para garantir que as APIs cumprem os requisitos de conformidade, reduzindo os riscos legais e garantindo a proteção de dados.",
   "station.legal-and-compliance.apply_in_work": "Fornecer estruturas legais e de conformidade, listas de verificação e ferramentas para garantir a conformidade da API. Assegurar que as equipas compreendem e implementam os requisitos legais na conceção, desenvolvimento e publicação de API.",
@@ -177,21 +177,21 @@
   "station.legal-and-compliance.how_it_works.1": "Implementar medidas para garantir que as APIs cumprem estes requisitos, incluindo encriptação de dados, controlos de acesso e pistas de auditoria.",
   "station.legal-and-compliance.how_it_works.2": "Documentar as medidas de conformidade e garantir que são comunicadas às partes interessadas e aos consumidores.",
   "station.security-and-privacy.title": "Segurança e privacidade - Proteja as suas APIs e os seus utilizadores",
-  "station.security-and-privacy.description": "Implementar medidas de segurança e privacidade para proteger as API e os dados dos utilizadores contra ameaças e violações.",
+  "station.security-and-privacy.description": "Implementar medidas de segurança e privacidade para proteger as APIs e os dados dos utilizadores contra ameaças e violações.",
   "station.security-and-privacy.why_it_matters": "As APIs são vulneráveis a ameaças de segurança e violações de dados. Esta estação fornece orientações para a implementação de medidas de segurança e privacidade que protegem as APIs e os dados dos utilizadores, garantindo a confiança e a conformidade.",
-  "station.security-and-privacy.apply_in_work": "Fornecer estruturas de segurança, ferramentas e melhores práticas para a segurança e privacidade da API. Assegurar que as equipas implementam medidas de segurança em todo o ciclo de vida da API, desde a conceção até à publicação e monitorização.",
+  "station.security-and-privacy.apply_in_work": "Fornecer estruturas de segurança, ferramentas e boas práticas para a segurança e privacidade da API. Assegurar que as equipas implementam medidas de segurança em todo o ciclo de vida da API, desde a conceção até à publicação e monitorização.",
   "station.security-and-privacy.outcomes": "APIs protegidas contra ameaças e vulnerabilidades",
   "station.security-and-privacy.outcomes.1": "Dados do utilizador protegidos através de medidas de privacidade",
-  "station.security-and-privacy.outcomes.2": "Melhores práticas de segurança implementadas na conceção e desenvolvimento de API",
+  "station.security-and-privacy.outcomes.2": "Boas práticas de segurança implementadas na conceção e desenvolvimento de API",
   "station.security-and-privacy.outcomes.3": "Conformidade com as normas e regulamentos de segurança",
   "station.security-and-privacy.how_it_works": "Implemente medidas de segurança como autenticação, autorização, encriptação e limitação de taxas para proteger as APIs de ameaças.",
   "station.security-and-privacy.how_it_works.1": "Garantir a privacidade dos dados dos utilizadores através da implementação de medidas de proteção de dados, como a anonimização e os controlos de acesso.",
   "station.security-and-privacy.how_it_works.2": "Efetuar auditorias de segurança regulares e avaliações de vulnerabilidade para identificar e atenuar os riscos.",
   "station.design-standards.title": "Normas de conceção - Garantir uma conceção de API consistente e de alta qualidade",
   "station.design-standards.description": "Estabelecer normas e diretrizes de design para garantir um design API consistente e de alta qualidade em toda a organização.",
-  "station.design-standards.why_it_matters": "Um design de API consistente e de alta qualidade é essencial para a usabilidade, manutenção e escalabilidade. Esta estação fornece normas e diretrizes de design que ajudam as equipas a criar APIs que são fáceis de utilizar, compreender e manter.",
+  "station.design-standards.why_it_matters": "Um conceção de API consistente e de alta qualidade é essencial para a usabilidade, manutenção e escalabilidade. Esta estação fornece normas e diretrizes de design que ajudam as equipas a criar APIs que são fáceis de utilizar, compreender e manter.",
   "station.design-standards.apply_in_work": "Fornecer documentação sobre normas de conceção, componentes reutilizáveis e processos de revisão da conceção. Assegurar que as equipas seguem as normas de conceção e realizam revisões regulares para manter uma conceção de API de alta qualidade.",
-  "station.design-standards.outcomes": "Design consistente da API em toda a organização",
+  "station.design-standards.outcomes": "Conceção consistente da API em toda a organização",
   "station.design-standards.outcomes.1": "APIs de alta qualidade que satisfazem as necessidades dos utilizadores",
   "station.design-standards.outcomes.2": "Componentes e padrões de conceção reutilizáveis",
   "station.design-standards.outcomes.3": "Redução das inconsistências de conceção e da dívida técnica",
@@ -207,45 +207,45 @@
   "station.vendor-management.outcomes.2": "Conformidade do fornecedor com as normas organizacionais",
   "station.vendor-management.outcomes.3": "Redução dos riscos associados a dependências de terceiros",
   "station.vendor-management.how_it_works": "Estabelecer processos de gestão de fornecedores para avaliar, integrar e monitorizar fornecedores de API de terceiros.",
-  "station.vendor-management.how_it_works.1": "Definir critérios para avaliar as API dos fornecedores, incluindo fiabilidade, segurança e conformidade.",
+  "station.vendor-management.how_it_works.1": "Definir critérios para avaliar as APIs dos fornecedores, incluindo fiabilidade, segurança e conformidade.",
   "station.vendor-management.how_it_works.2": "Monitorizar o desempenho dos fornecedores e o cumprimento dos acordos de nível de serviço (SLA) e das normas organizacionais.",
-  "station.contract-design.title": "Conceção de contratos - Definir contratos API claros",
-  "station.contract-design.description": "Criar contratos de API claros e bem definidos que descrevam as expectativas, responsabilidades e diretrizes de utilização.",
-  "station.contract-design.why_it_matters": "Os contratos de API são essenciais para garantir a clareza e o alinhamento entre os fornecedores e os consumidores de API. Esta estação fornece diretrizes para a conceção de contratos de API que sejam claros, abrangentes e fáceis de compreender.",
-  "station.contract-design.apply_in_work": "Fornecer modelos de design de contratos, formatos padronizados e processos de revisão. Assegurar que as equipas criam contratos de API claros e bem definidos que descrevem as expectativas, responsabilidades e diretrizes de utilização.",
-  "station.contract-design.outcomes": "Contratos API claros definidos para cada API",
+  "station.contract-design.title": "Conceção de contratos - Definir contratos de interface da API claros",
+  "station.contract-design.description": "Criar contratos de interface da API claros e bem definidos que descrevam as expectativas, responsabilidades e diretrizes de utilização.",
+  "station.contract-design.why_it_matters": "Os contratos de interface da API são essenciais para garantir a clareza e o alinhamento entre os fornecedores e os consumidores de API. Esta estação fornece diretrizes para a conceção de contratos de interface da API que sejam claros, abrangentes e fáceis de compreender.",
+  "station.contract-design.apply_in_work": "Fornecer modelos de design de contratos, formatos normalizados e processos de revisão. Assegurar que as equipas criam contratos de interface da API claros e bem definidos que descrevem as expectativas, responsabilidades e diretrizes de utilização.",
+  "station.contract-design.outcomes": "Contratos de interface da API claros definidos para cada API",
   "station.contract-design.outcomes.1": "Expectativas e responsabilidades definidas para os fornecedores e consumidores de API",
-  "station.contract-design.outcomes.2": "Orientações de utilização e melhores práticas documentadas",
+  "station.contract-design.outcomes.2": "Orientações de utilização e boas práticas documentadas",
   "station.contract-design.outcomes.3": "Redução de mal-entendidos e litígios sobre a utilização da API",
-  "station.contract-design.how_it_works": "Definir contratos de API que descrevam as expectativas, responsabilidades e diretrizes de utilização para cada API.",
-  "station.contract-design.how_it_works.1": "Utilizar formatos normalizados (por exemplo, OpenAPI, AsyncAPI) para criar contratos de API legíveis por máquina que sejam fáceis de partilhar e validar.",
-  "station.contract-design.how_it_works.2": "Assegurar que os contratos API são revistos e aprovados pelas partes interessadas para garantir o alinhamento e a clareza.",
-  "station.development.title": "Desenvolvimento - Criar APIs com as melhores práticas",
-  "station.development.description": "Implementar APIs utilizando as melhores práticas e estruturas para garantir a qualidade, a capacidade de manutenção e a escalabilidade.",
-  "station.development.why_it_matters": "O desenvolvimento de API é uma fase crítica que determina a qualidade e a fiabilidade da API. Esta estação fornece as melhores práticas e estruturas para o desenvolvimento de APIs, garantindo que as APIs são construídas de acordo com padrões elevados e podem ser mantidas e escaladas de forma eficaz.",
-  "station.development.apply_in_work": "Fornecer estruturas de desenvolvimento, bibliotecas e normas de codificação para a implementação da API. Garantir que as equipas seguem as melhores práticas e realizam revisões de código para manter um desenvolvimento de API de alta qualidade.",
-  "station.development.outcomes": "APIs desenvolvidas utilizando as melhores práticas e estruturas",
+  "station.contract-design.how_it_works": "Definir contratos de interface da API que descrevam as expectativas, responsabilidades e diretrizes de utilização para cada API.",
+  "station.contract-design.how_it_works.1": "Utilizar formatos normalizados (por exemplo, OpenAPI, AsyncAPI) para criar contratos de interface da API legíveis por máquina que sejam fáceis de partilhar e validar.",
+  "station.contract-design.how_it_works.2": "Assegurar que os contratos de interface da API são revistos e aprovados pelas partes interessadas para garantir o alinhamento e a clareza.",
+  "station.development.title": "Desenvolvimento - Criar APIs com as boas práticas",
+  "station.development.description": "Implementar APIs utilizando as boas práticas e estruturas para garantir a qualidade, a capacidade de manutenção e a escalabilidade.",
+  "station.development.why_it_matters": "O desenvolvimento de API é uma fase crítica que determina a qualidade e a fiabilidade da API. Esta estação fornece as boas práticas e estruturas para o desenvolvimento de APIs, garantindo que as APIs são construídas de acordo com padrões elevados e podem ser mantidas e escaladas de forma eficaz.",
+  "station.development.apply_in_work": "Fornecer estruturas de desenvolvimento, bibliotecas e normas de codificação para a implementação da API. Garantir que as equipas seguem as boas práticas e realizam revisões de código para manter um desenvolvimento de API de alta qualidade.",
+  "station.development.outcomes": "APIs desenvolvidas utilizando as boas práticas e estruturas",
   "station.development.outcomes.1": "APIs de alta qualidade, fáceis de manter e escaláveis",
   "station.development.outcomes.2": "Seguimento de normas e práticas de codificação consistentes",
   "station.development.outcomes.3": "Redução do tempo de desenvolvimento e da dívida técnica",
   "station.development.how_it_works": "Utilizar estruturas e bibliotecas estabelecidas para implementar APIs, assegurando a sua reutilização e manutenção.",
-  "station.development.how_it_works.1": "Aplicar abordagens \"contract-first\" ou \"design-first\" para garantir que os contratos API são validados antes da implementação.",
-  "station.development.how_it_works.2": "Seguir as normas de codificação e as melhores práticas para garantir um desenvolvimento de API consistente e de alta qualidade.",
+  "station.development.how_it_works.1": "Aplicar abordagens \"contract-first\" ou \"design-first\" para garantir que os contratos de interface da API são validados antes da implementação.",
+  "station.development.how_it_works.2": "Seguir as normas de codificação e as boas práticas para garantir um desenvolvimento de API consistente e de alta qualidade.",
   "station.ci-cd.title": "CI/CD - Automatizar a entrega da API",
   "station.ci-cd.description": "Implementar pipelines de integração contínua e entrega contínua (CI/CD) para automatizar a entrega de API e garantir uma qualidade consistente.",
-  "station.ci-cd.why_it_matters": "A CI/CD é essencial para garantir que as APIs sejam entregues rapidamente, de forma confiável e com alta qualidade. Esta estação fornece diretrizes para a implementação de pipelines de CI/CD que automatizam os processos de criação, teste e implantação de APIs.",
-  "station.ci-cd.apply_in_work": "Fornecer estruturas, ferramentas e melhores práticas de CI/CD para a entrega de API. Garantir que as equipas implementam pipelines automatizados que suportam a integração, os testes e a implementação contínuos de APIs.",
+  "station.ci-cd.why_it_matters": "A CI/CD é essencial para garantir que as APIs sejam entregues rapidamente, de forma confiável e com alta qualidade. Esta estação fornece diretrizes para a implementação de pipelines de CI/CD que automatizam os processos de criação, teste e disponibilização de APIs.",
+  "station.ci-cd.apply_in_work": "Fornecer estruturas, ferramentas e boas práticas de CI/CD para a entrega de API. Garantir que as equipas implementam pipelines automatizados que suportam a integração, os testes e a implementação contínuos de APIs.",
   "station.ci-cd.outcomes": "Pipelines CI/CD automatizados estabelecidos para a entrega de API",
   "station.ci-cd.outcomes.1": "Qualidade e rastreabilidade consistentes na entrega de API",
   "station.ci-cd.outcomes.2": "iterações mais rápidas e redução do tempo de colocação no mercado",
   "station.ci-cd.outcomes.3": "Melhoria da colaboração e dos ciclos de feedback no desenvolvimento de API",
-  "station.ci-cd.how_it_works": "Utilize pipelines CI/CD para automatizar os processos de construção, teste e implantação, garantindo qualidade e rastreabilidade consistentes.",
-  "station.ci-cd.how_it_works.1": "Integrar testes funcionais e não funcionais no pipeline CI/CD para garantir que as APIs cumprem as normas de qualidade.",
+  "station.ci-cd.how_it_works": "Utilize pipelines CI/CD para automatizar os processos de construção, teste e disponibilização, garantindo qualidade e rastreabilidade consistentes.",
+  "station.ci-cd.how_it_works.1": "Integrar testes funcionais e não funcionais no pipeline CI/CD para garantir que as APIs cumprems normas de qualidade.",
   "station.ci-cd.how_it_works.2": "Implementar verificações de segurança automatizadas e validações de conformidade no pipeline CI/CD para garantir que as APIs são seguras e compatíveis.",
   "station.test-automation.title": "Automatização de testes - Garantir a qualidade da API",
   "station.test-automation.description": "Implementar práticas de teste automatizadas para garantir a qualidade, fiabilidade e desempenho da API.",
-  "station.test-automation.why_it_matters": "Os testes automatizados são cruciais para garantir que as APIs funcionam corretamente e cumprem as normas de qualidade. Esta estação fornece diretrizes para a implementação de práticas de teste automatizado que abrangem testes funcionais, de segurança e de desempenho para APIs.",
-  "station.test-automation.apply_in_work": "Fornecer estruturas de automatização de testes, ferramentas e melhores práticas para testes de API. Assegurar que as equipas implementam testes automatizados que abrangem aspectos funcionais, de segurança e de desempenho das API.",
+  "station.test-automation.why_it_matters": "Os testes automatizados são cruciais para garantir que as APIs funcionam corretamente e cumprems normas de qualidade. Esta estação fornece diretrizes para a implementação de práticas de teste automatizado que abrangem testes funcionais, de segurança e de desempenho para APIs.",
+  "station.test-automation.apply_in_work": "Fornecer estruturas de automatização de testes, ferramentas e boas práticas para testes de API. Assegurar que as equipas implementam testes automatizados que abrangem aspectos funcionais, de segurança e de desempenho das APIs.",
   "station.test-automation.outcomes": "Práticas de teste automatizadas implementadas para APIs",
   "station.test-automation.outcomes.1": "Testes funcionais, de segurança e de desempenho automatizados",
   "station.test-automation.outcomes.2": "Redução do esforço de teste manual e aumento da cobertura dos testes",
@@ -256,18 +256,18 @@
   "station.release-management.title": "Gestão de versões - Gerir eficazmente as versões da API",
   "station.release-management.description": "Implementar práticas de gestão de lançamentos para garantir lançamentos de API sem problemas e controlados.",
   "station.release-management.why_it_matters": "A gestão eficaz de lançamentos é essencial para garantir que os lançamentos de APIs sejam fáceis, controlados e alinhados com as necessidades do negócio. Esta estação fornece diretrizes para a gestão de lançamentos de API, incluindo versões, estratégias de implementação e procedimentos de reversão.",
-  "station.release-management.apply_in_work": "Fornecer estruturas de gestão de versões, diretrizes de controlo de versões e estratégias de implementação. Assegurar que as equipas seguem as melhores práticas para a gestão de lançamentos de API, incluindo procedimentos de versão, implementação e reversão.",
+  "station.release-management.apply_in_work": "Fornecer estruturas de gestão de versões, diretrizes de controlo de versões e estratégias de implementação. Assegurar que as equipas seguem as boas práticas para a gestão de lançamentos de API, incluindo procedimentos de versão, implementação e reversão.",
   "station.release-management.outcomes": "Lançamentos de API controlados e sem problemas",
-  "station.release-management.outcomes.1": "Definição de estratégias de versão e implantação",
+  "station.release-management.outcomes.1": "Definição de estratégias de versão e disponibilização",
   "station.release-management.outcomes.2": "Procedimentos de reversão estabelecidos para libertações de API",
   "station.release-management.outcomes.3": "Redução dos riscos associados às alterações da API",
-  "station.release-management.how_it_works": "Definir estratégias de controlo de versões para as API para gerir as alterações e garantir a compatibilidade com as versões anteriores.",
-  "station.release-management.how_it_works.1": "Implementar estratégias de implantação (por exemplo, implantações blue-green, lançamentos canários) para minimizar os riscos durante os lançamentos de API.",
+  "station.release-management.how_it_works": "Definir estratégias de controlo de versões para as APIs para gerir as alterações e garantir a compatibilidade com as versões anteriores.",
+  "station.release-management.how_it_works.1": "Implementar estratégias de disponibilização (por exemplo, disponibilizações blue-green, lançamentos canários) para minimizar os riscos durante os lançamentos de API.",
   "station.release-management.how_it_works.2": "Estabelecer procedimentos de reversão para reverter rapidamente as alterações em caso de problemas durante os lançamentos da API.",
   "station.service-agreements.title": "Acordos de serviço - Definir níveis de serviço de API",
   "station.service-agreements.description": "Estabelecer acordos de serviço que definam as expectativas, os níveis de serviço e as responsabilidades dos fornecedores e consumidores de API.",
   "station.service-agreements.why_it_matters": "Os acordos de serviço são essenciais para garantir a clareza e o alinhamento entre os fornecedores de API e os consumidores. Esta estação fornece diretrizes para a criação de acordos de serviço que definem expectativas, níveis de serviço e responsabilidades, reduzindo mal-entendidos e disputas.",
-  "station.service-agreements.apply_in_work": "Fornecer modelos de contratos de serviço, formatos padronizados e processos de revisão. Garantir que as equipas criam contratos de serviço claros e bem definidos que descrevem as expectativas, os níveis de serviço e as responsabilidades dos fornecedores e consumidores de API.",
+  "station.service-agreements.apply_in_work": "Fornecer modelos de contratos de serviço, formatos normalizados e processos de revisão. Garantir que as equipas criam contratos de serviço claros e bem definidos que descrevem as expectativas, os níveis de serviço e as responsabilidades dos fornecedores e consumidores de API.",
   "station.service-agreements.outcomes": "Acordos de serviço claros definidos para cada API",
   "station.service-agreements.outcomes.1": "Expectativas e níveis de serviço definidos para fornecedores e consumidores de API",
   "station.service-agreements.outcomes.2": "Responsabilidades e processos de apoio documentados",
@@ -276,33 +276,33 @@
   "station.service-agreements.how_it_works.1": "Utilize formatos normalizados para criar contratos de serviço legíveis por máquina que sejam fáceis de partilhar e validar.",
   "station.service-agreements.how_it_works.2": "Assegurar que os acordos de serviço são revistos e aprovados pelas partes interessadas para garantir o alinhamento e a clareza.",
   "station.api-consumer-adoption.title": "Adoção pelo consumidor da API - Impulsionar a utilização da API",
-  "station.api-consumer-adoption.description": "Implementar estratégias para promover a adoção e o envolvimento dos consumidores de API, assegurando que as API são utilizadas eficazmente.",
-  "station.api-consumer-adoption.why_it_matters": "A adoção pelos consumidores de APIs é crucial para a concretização do valor das APIs. Esta estação fornece estratégias e práticas recomendadas para envolver os consumidores de API, garantindo que eles entendam como usar as APIs de forma eficaz e obter valor delas.",
+  "station.api-consumer-adoption.description": "Implementar estratégias para promover a adoção e o envolvimento dos consumidores de API, assegurando que as APIs são utilizadas eficazmente.",
+  "station.api-consumer-adoption.why_it_matters": "A adoção pelos consumidores de APIs é crucial para a concretização do valor das APIs. Esta estação fornece estratégias e boas práticas para envolver os consumidores de API, garantindo que eles entendam como utilizar as APIs de forma eficaz e obter valor delas.",
   "station.api-consumer-adoption.apply_in_work": "Fornecer recursos de integração, materiais educativos e estratégias de envolvimento para os consumidores da API. Assegurar que as equipas implementam estratégias que promovem a adoção, o envolvimento e a satisfação dos consumidores da API.",
   "station.api-consumer-adoption.outcomes": "Estratégias de adoção pelos consumidores da API implementadas",
   "station.api-consumer-adoption.outcomes.1": "Aumento da utilização e do envolvimento da API",
-  "station.api-consumer-adoption.outcomes.2": "Consumidores da API informados sobre as caraterísticas e vantagens da API",
+  "station.api-consumer-adoption.outcomes.2": "Consumidores da API informados sobre as características e vantagens da API",
   "station.api-consumer-adoption.outcomes.3": "Melhoria da satisfação e da lealdade do consumidor API",
-  "station.api-consumer-adoption.how_it_works": "Desenvolver processos de integração e recursos para ajudar os consumidores de API a compreender como utilizar as API de forma eficaz.",
-  "station.api-consumer-adoption.how_it_works.1": "Criar materiais educativos (por exemplo, tutoriais, documentação) que expliquem as caraterísticas, as vantagens e os padrões de utilização da API.",
+  "station.api-consumer-adoption.how_it_works": "Desenvolver processos de integração e recursos para ajudar os consumidores de API a compreender como utilizar as APIs de forma eficaz.",
+  "station.api-consumer-adoption.how_it_works.1": "Criar materiais educativos (por exemplo, tutoriais, documentação) que expliquem as características, as vantagens e os padrões de utilização da API.",
   "station.api-consumer-adoption.how_it_works.2": "Interagir com os consumidores da API através de ciclos de feedback, canais de apoio e fóruns da comunidade para compreender as suas necessidades e melhorar a adoção da API.",
   "station.api-promotion.title": "Promoção da API - Aumente a visibilidade e a utilização da API",
-  "station.api-promotion.description": "Promover as API para aumentar a visibilidade, a utilização e a adoção entre os públicos-alvo.",
-  "station.api-promotion.why_it_matters": "A promoção das APIs é essencial para aumentar a sua visibilidade e impulsionar a sua utilização. Esta estação fornece estratégias e melhores práticas para promover eficazmente as APIs junto de públicos-alvo, assegurando que estes têm conhecimento das APIs e compreendem o seu valor.",
+  "station.api-promotion.description": "Promover as APIs para aumentar a visibilidade, a utilização e a adoção entre os públicos-alvo.",
+  "station.api-promotion.why_it_matters": "A promoção das APIs é essencial para aumentar a sua visibilidade e impulsionar a sua utilização. Esta estação fornece estratégias e boas práticas para promover eficazmente as APIs junto de públicos-alvo, assegurando que estes têm conhecimento das APIs e compreendem o seu valor.",
   "station.api-promotion.apply_in_work": "Fornecer estratégias de marketing, materiais promocionais e recursos de envolvimento da comunidade. Assegurar que as equipas implementam estratégias eficazes de promoção da API que aumentam a visibilidade, a utilização e a adoção entre os públicos-alvo.",
   "station.api-promotion.outcomes": "Estratégias de promoção da API implementadas",
   "station.api-promotion.outcomes.1": "Maior visibilidade e conhecimento da API",
   "station.api-promotion.outcomes.2": "Taxas de utilização e adoção de API mais elevadas",
   "station.api-promotion.outcomes.3": "Melhoria do envolvimento e da satisfação dos consumidores da API",
-  "station.api-promotion.how_it_works": "Desenvolver estratégias de marketing para promover as API junto de públicos-alvo, incluindo redes sociais, blogues e webinars.",
-  "station.api-promotion.how_it_works.1": "Criar materiais promocionais (por exemplo, estudos de casos, histórias de sucesso) que realcem o valor e as vantagens das API.",
+  "station.api-promotion.how_it_works": "Desenvolver estratégias de marketing para promover as APIs junto de públicos-alvo, incluindo redes sociais, blogues e webinars.",
+  "station.api-promotion.how_it_works.1": "Criar materiais promocionais (por exemplo, estudos de casos, histórias de sucesso) que realcem o valor e as vantagens das APIs.",
   "station.api-promotion.how_it_works.2": "Participar em comunidades e fóruns de API para partilhar actualizações da API, recolher feedback e promover a utilização da API.",
   "station.partner-integration.title": "Integração de parceiros - Colaborar com parceiros",
   "station.partner-integration.description": "Facilitar as integrações de parceiros para melhorar as capacidades da API e expandir o alcance.",
   "station.partner-integration.why_it_matters": "As integrações de parceiros podem melhorar as capacidades da API e expandir o seu alcance. Esta estação fornece diretrizes para colaborar com os parceiros na integração das suas APIs, garantindo uma interoperabilidade perfeita e a criação de valor.",
   "station.partner-integration.apply_in_work": "Fornecer estruturas de integração de parceiros, diretrizes e ferramentas de monitorização. Garantir que as equipas colaboram eficazmente com os parceiros para melhorar as capacidades da API, expandir o alcance e impulsionar a inovação.",
   "station.partner-integration.outcomes": "Processos de integração de parceiros estabelecidos",
-  "station.partner-integration.outcomes.1": "Capacidades API melhoradas através de APIs de parceiros",
+  "station.partner-integration.outcomes.1": "Capacidades API melhoradas através de API de parceiros",
   "station.partner-integration.outcomes.2": "Maior alcance e oportunidades de mercado através de parcerias",
   "station.partner-integration.outcomes.3": "Melhoria da colaboração e da inovação com os parceiros",
   "station.partner-integration.how_it_works": "Identifique potenciais parceiros cujas APIs possam melhorar as suas capacidades de API e a sua proposta de valor.",
@@ -310,15 +310,15 @@
   "station.partner-integration.how_it_works.2": "Monitorize o desempenho e a conformidade da API do parceiro para garantir a fiabilidade e o alinhamento com a sua estratégia de API.",
   "station.api-mindset.title": "Mentalidade API - Promover uma cultura API-First",
   "station.api-mindset.description": "Cultivar uma mentalidade API-first em toda a organização para impulsionar a inovação e a colaboração.",
-  "station.api-mindset.why_it_matters": "Uma mentalidade API-first é essencial para promover a inovação e a colaboração em toda a organização. Esta estação fornece estratégias para cultivar uma cultura API-first, garantindo que as APIs sejam vistas como activos estratégicos que geram valor comercial.",
+  "station.api-mindset.why_it_matters": "Uma mentalidade API-first é essencial para promover a inovação e a colaboração em toda a organização. Esta estação fornece estratégias para cultivar uma cultura API-first, garantindo que as APIs sejam vistas como activos estratégicos que geram valor de negócio.",
   "station.api-mindset.apply_in_work": "Fornecer programas de formação, recursos e estratégias de comunicação para promover uma cultura de prioridade à API. Assegurar que as equipas compreendem o valor das APIs e estão habilitadas a conduzir a estratégia e as iniciativas das APIs.",
   "station.api-mindset.outcomes": "Cultura API-first estabelecida em toda a organização",
-  "station.api-mindset.outcomes.1": "Maior inovação e colaboração através de APIs",
+  "station.api-mindset.outcomes.1": "Maior inovação e colaboração através de API",
   "station.api-mindset.outcomes.2": "Equipas de API habilitadas a conduzir a estratégia e as iniciativas de API",
-  "station.api-mindset.outcomes.3": "Melhoria do alinhamento entre os objectivos comerciais e o desenvolvimento de API",
-  "station.api-mindset.how_it_works": "Promover o valor das APIs como activos estratégicos que geram valor comercial e inovação.",
-  "station.api-mindset.how_it_works.1": "Incentivar a colaboração multifuncional entre equipas de API, unidades empresariais e partes interessadas para alinhar as iniciativas de API com os objectivos empresariais.",
-  "station.api-mindset.how_it_works.2": "Fornecer formação e recursos para ajudar as equipas a adotar uma mentalidade de prioridade à API e a compreender as vantagens das API.",
+  "station.api-mindset.outcomes.3": "Melhoria do alinhamento entre os objetivos de negócio e o desenvolvimento de API",
+  "station.api-mindset.how_it_works": "Promover o valor das APIs como activos estratégicos que geram valor de negócio e inovação.",
+  "station.api-mindset.how_it_works.1": "Incentivar a colaboração multifuncional entre equipas de API, unidades empresariais e partes interessadas para alinhar as iniciativas de API com os objetivos empresariais.",
+  "station.api-mindset.how_it_works.2": "Fornecer formação e recursos para ajudar as equipas a adotar uma mentalidade de prioridade à API e a compreender as vantagens das APIs.",
   "station.roles-and-responsibilities.title": "Funções e responsabilidades - Definir as estruturas da equipa API",
   "station.roles-and-responsibilities.description": "Definir funções e responsabilidades claras para as equipas de API para garantir uma colaboração e responsabilização eficazes.",
   "station.roles-and-responsibilities.why_it_matters": "Funções e responsabilidades claras são essenciais para uma colaboração e responsabilidade eficazes nas equipas de API. Esta estação fornece diretrizes para a definição das estruturas, funções e responsabilidades da equipa, assegurando que todos compreendem as suas contribuições para as iniciativas da API.",
@@ -343,54 +343,54 @@
   "station.upskilling.how_it_works.2": "Incentivar a aprendizagem contínua através de cursos em linha, certificações e envolvimento da comunidade.",
   "station.operating-guidelines.title": "Diretrizes operacionais - Estabelecer a governação da API",
   "station.operating-guidelines.description": "Estabelecer diretrizes operacionais e práticas de governação para garantir uma gestão e qualidade consistentes da API.",
-  "station.operating-guidelines.why_it_matters": "A governação eficaz da API é essencial para garantir uma gestão, qualidade e conformidade consistentes da API. Esta estação fornece diretrizes operacionais e práticas de governação que ajudam as equipas a gerir as APIs de forma eficaz, assegurando o seu alinhamento com as normas organizacionais e as melhores práticas.",
+  "station.operating-guidelines.why_it_matters": "A governação eficaz da API é essencial para garantir uma gestão, qualidade e conformidade consistentes da API. Esta estação fornece diretrizes operacionais e práticas de governação que ajudam as equipas a gerir as APIs de forma eficaz, assegurando o seu alinhamento com as normas organizacionais e as boas práticas.",
   "station.operating-guidelines.apply_in_work": "Fornecer diretrizes operacionais, quadros de governação e ferramentas de monitorização para a gestão de API. Assegurar que as equipas seguem as práticas estabelecidas que promovem a gestão consistente da API, a qualidade e a conformidade com as normas organizacionais.",
   "station.operating-guidelines.outcomes": "Práticas de governação da API estabelecidas",
   "station.operating-guidelines.outcomes.1": "Gestão e qualidade consistentes da API em toda a organização",
-  "station.operating-guidelines.outcomes.2": "Conformidade com as normas organizacionais e as melhores práticas",
+  "station.operating-guidelines.outcomes.2": "Conformidade com as normas organizacionais e as boas práticas",
   "station.operating-guidelines.outcomes.3": "Melhoria da visibilidade e do controlo das iniciativas API",
-  "station.operating-guidelines.how_it_works": "Definir diretrizes operacionais baseadas nos Ciclos APIOps que descrevem os processos, as normas e as melhores práticas para a gestão de API.",
-  "station.operating-guidelines.how_it_works.1": "Estabelecer práticas de governação que garantam que as API são geridas de forma consistente, incluindo análises, auditorias e verificações de conformidade.",
-  "station.operating-guidelines.how_it_works.2": "Monitorizar as iniciativas API para garantir o cumprimento das orientações operacionais e das práticas de governação",
+  "station.operating-guidelines.how_it_works": "Definir diretrizes operacionais baseadas nos Ciclos APIOps que descrevem os processos, as normas e as boas práticas para a gestão de API.",
+  "station.operating-guidelines.how_it_works.1": "Estabelecer práticas de governação que garantam que as APIs são geridas de forma consistente, incluindo análises, auditorias e verificações de conformidade.",
+  "station.operating-guidelines.how_it_works.2": "Monitorizar as iniciativas APIs para garantir o cumprimento das orientações operacionais e das práticas de governação",
   "station.portfolio-management.title": "Gestão de portfólio - Gerir eficazmente o portfólio de API",
-  "station.portfolio-management.description": "Gerir eficazmente a carteira de API para garantir o alinhamento com os objectivos comerciais e as iniciativas estratégicas.",
-  "station.portfolio-management.why_it_matters": "O gerenciamento eficaz do portfólio de APIs é essencial para garantir que as APIs se alinhem às metas comerciais e às iniciativas estratégicas. Esta estação fornece diretrizes para o gerenciamento do portfólio de APIs, garantindo que as APIs sejam priorizadas, monitoradas e otimizadas para fornecer o máximo de valor.",
-  "station.portfolio-management.apply_in_work": "Fornecer estruturas de gestão de carteiras, critérios de priorização e ferramentas de monitorização para a gestão de API. Assegurar que as equipas gerem eficazmente o portfólio de API, garantindo o alinhamento com os objectivos comerciais, as iniciativas estratégicas e a obtenção do máximo valor.",
+  "station.portfolio-management.description": "Gerir eficazmente a carteira de API para garantir o alinhamento com os objetivos de negócio e as iniciativas estratégicas.",
+  "station.portfolio-management.why_it_matters": "O gestão eficaz do portfólio de APIs é essencial para garantir que as APIs se alinhem às metas comerciais e às iniciativas estratégicas. Esta estação fornece diretrizes para o gestão do portfólio de APIs, garantindo que as APIs sejam priorizadas, monitoradas e otimizadas para fornecer o máximo de valor.",
+  "station.portfolio-management.apply_in_work": "Fornecer estruturas de gestão de carteiras, critérios de priorização e ferramentas de monitorização para a gestão de API. Assegurar que as equipas gerem eficazmente o portfólio de API, garantindo o alinhamento com os objetivos de negócio, as iniciativas estratégicas e a obtenção do máximo valor.",
   "station.portfolio-management.outcomes": "Estabelecimento de práticas de gestão de carteiras API",
-  "station.portfolio-management.outcomes.1": "APIs alinhadas com objectivos comerciais e iniciativas estratégicas",
+  "station.portfolio-management.outcomes.1": "APIs alinhadas com objetivos de negócio e iniciativas estratégicas",
   "station.portfolio-management.outcomes.2": "Priorização e otimização de APIs com base no valor e no impacto",
   "station.portfolio-management.outcomes.3": "Melhoria da visibilidade e do controlo da carteira de API",
   "station.portfolio-management.how_it_works": "Definir práticas de gestão da carteira que descrevam os processos de gestão da carteira de API, incluindo a definição de prioridades, a monitorização e a otimização.",
-  "station.portfolio-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às APIs com base no valor comercial, no impacto e no alinhamento com iniciativas estratégicas.",
-  "station.portfolio-management.how_it_works.2": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objectivos comerciais.",
+  "station.portfolio-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às APIs com base no valor de negócio, no impacto e no alinhamento com iniciativas estratégicas.",
+  "station.portfolio-management.how_it_works.2": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objetivos de negócio.",
   "station.budget-and-resource-management.title": "Orçamento e gestão de recursos - Otimizar os investimentos em API",
   "station.budget-and-resource-management.description": "Otimizar o orçamento e a gestão de recursos para as iniciativas API, a fim de garantir investimentos e atribuição de recursos eficazes.",
-  "station.budget-and-resource-management.why_it_matters": "A gestão eficaz do orçamento e dos recursos é essencial para garantir que as iniciativas de API sejam bem financiadas e dotadas de recursos. Esta estação fornece diretrizes para otimizar a gestão do orçamento e dos recursos, assegurando que as iniciativas de API estão alinhadas com os objectivos comerciais e proporcionam o máximo valor.",
+  "station.budget-and-resource-management.why_it_matters": "A gestão eficaz do orçamento e dos recursos é essencial para garantir que as iniciativas de API sejam bem financiadas e dotadas de recursos. Esta estação fornece diretrizes para otimizar a gestão do orçamento e dos recursos, assegurando que as iniciativas de API estão alinhadas com os objetivos de negócio e proporcionam o máximo valor.",
   "station.budget-and-resource-management.apply_in_work": "Fornecer estruturas de gestão orçamental, critérios de prioritização e ferramentas de monitorização para iniciativas de API. Assegurar que as equipas gerem eficazmente os orçamentos e os recursos, optimizando os investimentos no desenvolvimento e na gestão de API para obter o máximo valor.",
   "station.budget-and-resource-management.outcomes": "Práticas de gestão orçamental e de recursos estabelecidas para as iniciativas API",
   "station.budget-and-resource-management.outcomes.1": "Afetação efectiva de recursos às iniciativas API",
   "station.budget-and-resource-management.outcomes.2": "Investimentos optimizados no desenvolvimento e gestão de API",
   "station.budget-and-resource-management.outcomes.3": "Melhoria da visibilidade financeira e do controlo das iniciativas API",
   "station.budget-and-resource-management.how_it_works": "Definir práticas de gestão orçamental e de recursos que descrevam os processos de gestão de orçamentos e recursos para iniciativas de API.",
-  "station.budget-and-resource-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor comercial, no impacto e no alinhamento com as iniciativas estratégicas.",
+  "station.budget-and-resource-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor de negócio, no impacto e no alinhamento com as iniciativas estratégicas.",
   "station.budget-and-resource-management.how_it_works.2": "Controlar o orçamento e a utilização dos recursos para garantir investimentos eficazes e a afetação de recursos às iniciativas da API.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "Estratégia de produtos API - Transforme APIs em produtos estratégicos",
-  "cycle.api-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objectivos comerciais desde o primeiro dia.",
-  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projectos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
+  "cycle.api-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objetivos de negócio desde o primeiro dia.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projetos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
   "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Fornecer diretrizes e modelos para a criação de modelos comerciais, propostas de valor e roteiros de API.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "Uma proposta de valor e um público-alvo da API simples",
-  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Linguagem partilhada entre o produto, o design e a tecnologia",
+  "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Linguagem partilhada entre o produto, a conceção e a tecnologia",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.2": "Um argumento sólido ou um caso para financiamento/aprovação",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore o problema do cliente ou parceiro que espera resolver com as APIs. Mapeie as partes interessadas, os seus percursos e os resultados utilizando a tela do Percurso do Cliente.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore o problema do cliente ou parceiro que espera resolver com as APIs. Mapeie as partes interessadas, os seus percursos e os resultados utilizando a Canvas do Percurso do Cliente.",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Definir as entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre jornadas e, eventualmente, APIs.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use o API Value Proposition Canvas para capturar as tarefas de negócios suportadas e as dores, ganhos e recursos do consumidor da API que moldam APIs novas ou reutilizáveis.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Defina o valor - para os utilizadores e para a empresa - com a tela do modelo de negócio da API para tornar a sua estratégia de API visual, partilhável e fácil de validar com os seus consumidores de API na estação seguinte.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.title": "Experiência do consumidor da API - Design para os utilizadores reais da sua API",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilize o Canvas da Proposta de Valor da API para capturar as tarefas de negócios suportadas e as dores, ganhos e recursos do consumidor da API que moldam APIs novas ou reutilizáveis.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Defina o valor - para os utilizadores e para a empresa - com a Canvas do Modelo de Negócio da API para tornar a sua estratégia de API visual, partilhável e fácil de validar com os seus consumidores de API na estação seguinte.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "Experiência do consumidor da API - Conceção para os utilizadores reais da sua API",
   "cycle.api-productization-cycle.station.api-consumer-experience.description": "Certifique-se de que a sua API é detetável, compreensível e utilizável - antes e depois do lançamento.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "As APIs excelentes não funcionam apenas - elas são intuitivas. Quer o consumidor seja um programador interno, um parceiro externo ou um agente de IA, a sua experiência determina a adoção.\n\nSem um plano de experiência claro:\n- Grandes APIs ficam sem uso\n- As equipas perdem tempo a tentar adivinhar como utilizar a sua API\n- Os ciclos de feedback estão quebrados ou ausentes.\n\nEsta estação ajuda-o a ver a sua API através dos olhos dos seus consumidores.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Analise o API Value Proposition Canvas existente sob a perspectiva do consumidor da API. Mantenha as tarefas de negócios suportadas estáveis ​​e enriqueça os recursos que aliviam problemas e possibilitam ganhos com as preocupações do consumidor da API, para que elas possam orientar as decisões de design futuras.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use o Customer Journey Canvas para a jornada do consumidor da API, desde a descoberta e avaliação até a integração, resolução de problemas e uso contínuo.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use a jornada resultante para melhorar a integração, a documentação, o suporte e os ciclos de feedback para o consumidor da API.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "As APIs excelentes não funcionam apenas - elas são intuitivas. Quer o consumidor seja um programador interno, um parceiro externo ou um agente de IA, a sua experiência determina a adoção.\n\nSnum plano de experiência claro:\n- Grandes APIs ficam sem uso\n- As equipas perdem tempo a tentar adivinhar como utilizar a sua API\n- Os ciclos de feedback estão quebrados ou ausentes.\n\nEsta estação ajuda-o a ver a sua API através dos olhos dos seus consumidores.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Analise o Canvas da Proposta de Valor da API existente sob a perspectiva do consumidor da API. Mantenha as tarefas de negócios suportadas estáveis ​​e enriqueça os recursos que aliviam problemas e possibilitam ganhos com as preocupações do consumidor da API, para que elas possam orientar as decisões de conceção futuras.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilize o Canvas do Percurso do Cliente para a jornada do consumidor da API, desde a descoberta e avaliação até a integração, resolução de problemas e uso contínuo.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilize a jornada resultante para melhorar a integração, a documentação, o suporte e os ciclos de feedback para o consumidor da API.",
   "cycle.api-productization-cycle.station.api-consumer-experience.apply_in_work": "Fornecer diretrizes, ferramentas e mecanismos de feedback para compreender, analisar e melhorar a experiência interna e externa dos programadores e parceiros.",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes": "Identifique e dê prioridade aos seus consumidores de API",
   "cycle.api-productization-cycle.station.api-consumer-experience.outcomes.1": "Definir o percurso da experiência API",
@@ -399,59 +399,59 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.title": "Arquitetura da plataforma API - Arquitetar APIs para escalabilidade e reutilização",
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Garanta a escalabilidade, a reutilização e a governação da sua API e dos componentes da plataforma.",
   "cycle.api-productization-cycle.station.api-platform-architecture.why_it_matters": "Quando as APIs são escalonadas entre equipas, a sua plataforma deve permitir a governação e a reutilização sem bloquear a velocidade. Esta estação mostra como arquitetar APIs para longevidade, segurança e eficiência.",
-  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Estabelecer uma infraestrutura escalável, segura e compatível com as operações de API. Fornecer orientações sobre as melhores práticas de arquitetura.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.apply_in_work": "Estabelecer uma infraestrutura escalável, segura e compatível com as operações de API. Fornecer orientações sobre as boas práticas de arquitetura.",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes": "Corte APIs redundantes e reduza os custos da plataforma de nuvem",
-  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implementar uma governação consistente sem um forte controlo do topo para a base",
+  "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.1": "Implementar uma governação consistente snum forte controlo do topo para a base",
   "cycle.api-productization-cycle.station.api-platform-architecture.outcomes.2": "Conceção para reutilização interna e escalabilidade externa",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "O Business Impact Canvas ajuda a identificar e mitigar os riscos relacionados com a disponibilidade, segurança e funcionalidade da API para apoiar decisões de arquitetura informadas.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works": "O Canvas de Impacto no Negócio ajuda a identificar e mitigar os riscos relacionados com a disponibilidade, segurança e funcionalidade da API para apoiar decisões de arquitetura informadas.",
   "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.1": "Mapear as localizações regulamentares, de conformidade e de rede dos fornecedores e consumidores de API para garantir a acessibilidade e a conformidade.",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "O Capacity Canvas alinha os padrões das transacções comerciais, as tendências de consumo futuro e as soluções técnicas para garantir a escalabilidade e o desempenho da API, fornecendo dados essenciais para as decisões de escalabilidade e o planeamento da infraestrutura.",
-  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.2": "O Canvas de Capacidade alinha os padrões das transacções comerciais, as tendências de consumo futuro e as soluções técnicas para garantir a escalabilidade e o desempenho da API, fornecendo dados essenciais para as decisões de escalabilidade e o planeamento da infraestrutura.",
+  "cycle.api-productization-cycle.station.api-platform-architecture.how_it_works.3": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
   "cycle.api-productization-cycle.station.api-design.title": "Conceção da API - Conceber APIs que proporcionem valor",
-  "cycle.api-productization-cycle.station.api-design.description": "Criar projetos de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados.",
-  "cycle.api-productization-cycle.station.api-design.why_it_matters": "Projetar APIs não se resume apenas a nomear endpoints. Um bom projeto garante que as APIs sejam utilizáveis, consistentes e alinhadas com os objetivos comerciais e técnicos. Um projeto inadequado leva a um acoplamento rígido, baixa reutilização e retrabalho dispendioso entre as equipes.",
+  "cycle.api-productization-cycle.station.api-design.description": "Criar conceções de API que sejam consistentes, reutilizáveis e baseados na intenção de negócios e em padrões compartilhados.",
+  "cycle.api-productization-cycle.station.api-design.why_it_matters": "Conceber APIs não se resume apenas a nomear endpoints. Um bom projeto garante que as APIs sejam utilizáveis, consistentes e alinhadas com os objetivos de negócio e técnicos. Um projeto inadequado leva a um acoplamento rígido, baixa reutilização e retrabalho dispendioso entre as equipas.",
   "cycle.api-productization-cycle.station.api-design.apply_in_work": "Forneça padrões de projeto reutilizáveis, padrões compartilhados e ferramentas de validação para especificações de API. Garanta que as decisões de projeto sejam consistentes, revisadas antecipadamente e alinhadas com a intenção de negócios.",
   "cycle.api-productization-cycle.station.api-design.outcomes": "Conceção de API bem documentada e coerente",
-  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contratos API reutilizáveis e validados",
+  "cycle.api-productization-cycle.station.api-design.outcomes.1": "Contratos de interface da API reutilizáveis e validados",
   "cycle.api-productization-cycle.station.api-design.outcomes.2": "Desenhos alinhados com modelos de domínio e padrões de interação",
-  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Rastreabilidade da conceção ao valor comercial",
+  "cycle.api-productization-cycle.station.api-design.outcomes.3": "Rastreabilidade da conceção ao valor de negócio",
   "cycle.api-productization-cycle.station.api-design.how_it_works": "Definir entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre APIs.",
   "cycle.api-productization-cycle.station.api-design.how_it_works.1": "Utilize o Canvas de Interação para definir a forma como os consumidores irão interagir com a API, garantindo que esta satisfaz as suas necessidades e expectativas.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Aplicar padrões de conceção REST para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Aplicar padrões de conceção orientados para eventos para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Aplicar padrões de design GraphQL para criar contratos de API consistentes e reutilizáveis que são validados com as partes interessadas.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Use os princípios de projeto e o guia de estilo de API para alinhar suas decisões de projeto com regras compartilhadas e permitir uma validação de auditoria consistente.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Aplique abordagens do tipo ‘contrato primeiro’ ou ‘design primeiro’ para capturar e validar o contrato da API antes da implementação.",
-  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use a Lista de Verificação de Auditoria da API para garantir que o design da API atenda aos requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.2": "Aplicar padrões de conceção REST para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.3": "Aplicar padrões de conceção orientados para eventos para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.4": "Aplicar padrões de conceção GraphQL para criar contratos de interface da API consistentes e reutilizáveis que são validados com as partes interessadas.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.5": "Utilize os princípios de projeto e o guia de estilo da API para alinhar suas decisões de projeto com regras compartilhadas e permitir uma validação de auditoria consistente.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.6": "Aplique abordagens do tipo ‘contrato primeiro’ ou ‘design primeiro’ para capturar e validar o contrato de interface da API antes da implementação.",
+  "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Utilize a Lista de Verificação de Auditoria da API para garantir que a conceção da API satisfaça os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
   "cycle.api-productization-cycle.station.api-delivery.title": "Entrega da API - Fornecer APIs seguras e fiáveis",
-  "cycle.api-productization-cycle.station.api-delivery.description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e práticas recomendadas de engenharia.",
-  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Mesmo os melhores projectos de API falham se a entrega for inconsistente. Esta estação assegura que as suas APIs são construídas com qualidade, testadas exaustivamente e implementadas de forma fiável - permitindo iterações mais rápidas e maior confiança.",
-  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fornecer estruturas de codificação, bibliotecas e normas para a implementação de API. Implementar pipelines de CI/CD, estruturas de garantia de qualidade e ferramentas de automatização da implantação.",
+  "cycle.api-productization-cycle.station.api-delivery.description": "Criar, testar e lançar APIs usando pipelines de entrega modernos e boas práticas de engenharia.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Mesmo os melhores conceções de API falham se a entrega for inconsistente. Esta estação assegura que as suas APIs são construídas com qualidade, testadas exaustivamente e implementadas de forma fiável - permitindo iterações mais rápidas e maior confiança.",
+  "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Fornecer estruturas de codificação, bibliotecas e normas para a implementação de API. Implementar pipelines de CI/CD, estruturas de garantia de qualidade e ferramentas de automatização da disponibilização.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implementadas utilizando estruturas e padrões testados",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Pipelines de CI/CD fiáveis e automatizados",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.2": "Testes funcionais e não funcionais integrados",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.3": "Condutas de entrega seguras e conformes",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Use as Melhores Práticas de Desenvolvimento de API como orientação para implementar o contrato validado com frameworks e bibliotecas estabelecidos, garantindo que o resultado seja reutilizável e sustentável.",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construa a implementação da API a partir do contrato validado usando frameworks, bibliotecas e padrões da equipe estabelecidos.",
-  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testar a funcionalidade, a segurança e o desempenho das API, utilizando ferramentas de teste automatizadas.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works": "Utilize as Melhores Práticas de Desenvolvimento de API como orientação para implementar o contrato validado com frameworks e bibliotecas estabelecidos, garantindo que o resultado seja reutilizável e sustentável.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.1": "Construa a implementação da API a partir do contrato validado usando frameworks, bibliotecas e padrões da equipa estabelecidos.",
+  "cycle.api-productization-cycle.station.api-delivery.how_it_works.2": "Testar a funcionalidade, a segurança e o desempenho das APIs, utilizando ferramentas de teste automatizadas.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.3": "Utilize pipelines CI/CD para automatizar os processos de construção, teste e implementação, garantindo uma qualidade e rastreabilidade consistentes.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Garantir que as APIs cumprem os requisitos de segurança e conformidade através de verificações e auditorias automatizadas.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Utilize a lista de verificação de auditoria da API para garantir que a API cumpre os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
   "cycle.api-productization-cycle.station.api-audit.title": "Auditoria de API - Auditoria de APIs para conformidade e qualidade",
-  "cycle.api-productization-cycle.station.api-audit.description": "Valide se as APIs atendem aos padrões de negócios, design e operacionais antes da publicação e exposição.",
-  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "As APIs são produtos de longa duração e devem atender às expectativas de qualidade, consistência e conformidade. A auditoria conecta as decisões de design, a implementação e a prontidão operacional a padrões definidos, reduzindo o risco antes da exposição.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Valide se as APIs satisfazemos padrões de negócio, conceção e operacionais antes da publicação e exposição.",
+  "cycle.api-productization-cycle.station.api-audit.why_it_matters": "As APIs são produtos de longa duração e devem atender às expectativas de qualidade, consistência e conformidade. A auditoria conecta as decisões de conceção, a implementação e a prontidão operacional a padrões definidos, reduzindo o risco antes da exposição.",
   "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Estabeleça um processo de auditoria consistente que avalie a prontidão da API em todas as etapas do ciclo de vida usando critérios, evidências e padrões definidos. Garanta que as lacunas sejam identificadas antecipadamente e resolvidas antes da publicação.",
-  "cycle.api-productization-cycle.station.api-audit.outcomes": "As APIs cumprem as normas internas e externas",
+  "cycle.api-productization-cycle.station.api-audit.outcomes": "As APIs cumprems normas internas e externas",
   "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Documentação clara das decisões de conceção e implementação da API",
   "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Segurança, desempenho e conformidade validados",
   "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Redução do risco de problemas na produção",
-  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Realizar auditorias para garantir que as APIs cumprem as normas organizacionais, técnicas e legais antes da publicação.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Realizar auditorias para garantir que as APIs cumprems normas organizacionais, técnicas e legais antes da publicação.",
   "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Utilizar listas de controlo, linters e ferramentas de teste para verificar a consistência e a conformidade com as normas.",
-  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Colaborar com as equipas de governação e especialistas no domínio para garantir que as API estão prontas para produção.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Colaborar com as equipas de governação e especialistas no domínio para garantir que as APIs estão prontas para produção.",
   "cycle.api-productization-cycle.station.api-publishing.title": "Publicação de API - Publique APIs com confiança",
   "cycle.api-productization-cycle.station.api-publishing.description": "Exponha as APIs de forma segura e clara ao público certo com a documentação e os processos corretos.",
-  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "A publicação é mais do que a implantação - trata-se de capacidade de descoberta, acesso e suporte. Se as APIs não forem publicadas corretamente, não serão utilizadas, reutilizadas ou protegidas de forma eficaz.",
-  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permitir que as API sejam publicadas no ambiente relevante e ter mecanismos claros de registo e acesso (por exemplo, chaves de API, OAuth, planos de subscrição), dependendo dos segmentos de consumidores de API e dos requisitos de segurança e conformidade.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "A publicação é mais do que a disponibilização - trata-se de capacidade de descoberta, acesso e suporte. Se as APIs não forem publicadas corretamente, não serão utilizadas, reutilizadas ou protegidas de forma eficaz.",
+  "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Permitir que as APIs sejam publicadas no ambiente relevante e ter mecanismos claros de registo e acesso (por exemplo, chaves de API, OAuth, planos de subscrição), dependendo dos segmentos de consumidores de API e dos requisitos de segurança e conformidade.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs publicadas no ambiente correto (privado, parceiro, público)",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Processos claros de integração e registo da API",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.2": "Documentação, modelos e políticas de segurança disponíveis",
@@ -467,7 +467,103 @@
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Ciclos de feedback do programador em vigor",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.2": "Questões identificadas e tratadas continuamente",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "Iteração da API alinhada com as necessidades dos utilizadores",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas API, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua."
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.title": "Estratégia",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor, os consumidores, a propriedade e os objetivos de negócio da capacidade.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "O trabalho de integração e API salta muitas vezes demasiado cedo para um padrão técnico. Esta estação mantém a equipa focada na jornada de negócio, no significado do domínio, no valor, no potencial de reutilização, na propriedade e na viabilidade antes de selecionar APIs, eventos, ficheiros, streams, produtos de dados ou integração direta.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Utilize canvases partilhados de jornada, domínio, proposta de valor e modelo de negócio para recolher requisitos independentes da tecnologia e decidir se a capacidade deve ser reutilizável.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "Uma declaração de oportunidade de capacidade independente da tecnologia",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Compreensão partilhada dos consumidores, produtores, conceitos de domínio e potencial de reutilização",
+  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "Uma proposta de valor e um modelo de negócio da capacidade antes da seleção da arquitetura",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Mapeie a jornada do cliente ou parceiro que cria a necessidade da capacidade e revela tarefas, dores, ganhos, entradas, saídas e pontos de decisão.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Defina as entidades principais, atributos, relações, propriedade e regras de negócio que a capacidade deve respeitar.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Utilize o Canvas da Proposta de Valor da Capacidade para captar tarefas, ganhos, dores e funcionalidades reutilizáveis da capacidade para os consumidores, sem nomear a tecnologia de disponibilização demasiado cedo.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Utilize o Canvas do Modelo de Negócio da Capacidade para clarificar propriedade, parceiros, canais, custos, benefícios, suporte e expectativas de ciclo de vida da capacidade reutilizável.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Requisitos e integração de consumidores",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Recolha requisitos de integração dos consumidores, normas, requisitos não funcionais, expectativas de serviço, restrições, necessidades de segurança, protocolos permitidos, atualidade dos dados, SLAs, observabilidade, recuperação, requisitos de adoção e responsabilidades dos produtores.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "A arquitetura certa depende dos objetivos dos consumidores, das expectativas de integração, dos níveis de serviço, das necessidades de qualidade dos dados, da tolerância à mudança, da observabilidade, do suporte e das restrições dos produtores.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Utilize o Canvas de Requisitos da Experiência do Consumidor para captar objetivos dos consumidores, disponibilidade, atualidade, volume, desempenho, qualidade dos dados, segurança, integração, mudança, observabilidade e expectativas de recuperação.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Utilize orientação de integração para descrever como os consumidores vão encontrar, solicitar, testar, obter aprovação e começar a utilizar a capacidade.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Utilize a jornada e os requisitos resultantes para melhorar a integração, a documentação, o suporte e os ciclos de feedback dos consumidores da capacidade.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Utilize orientação de experiência e integração de consumidores para tornar explícitas as expectativas de consumidores e produtores.",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Requisitos dos consumidores e expectativas de integração documentados",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Responsabilidades dos produtores e expectativas de suporte claras",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Restrições relevantes para a arquitetura prontas para apoiar decisões",
+  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Adoção melhorada através de empatia com os consumidores, normas e clareza dos produtores",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Decisões de arquitetura e plataforma",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilize requisitos e restrições para decidir o padrão de arquitetura certo e as capacidades de plataforma de suporte.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "As escolhas de arquitetura devem resultar de evidências sobre impacto de negócio, localizações, fronteiras de confiança, capacidade, latência, propriedade dos dados, consistência, operabilidade, segurança, privacidade, governação e custo.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare estilos de arquitetura viáveis com os requisitos recolhidos e documente o padrão selecionado e a respetiva justificação.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "Uma escolha de arquitetura justificada",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Riscos, localizações, capacidade, segurança, privacidade e restrições de operabilidade documentados",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Justificação clara para API, evento, ficheiro, stream, produto de dados, integração direta ou disponibilização híbrida",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Utilize o Canvas de Impacto no Negócio para identificar riscos de disponibilidade, segurança e dados que influenciam as opções de arquitetura.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Utilize o Canvas de Localizações para captar restrições geopolíticas, regulamentares, de rede, residência e fronteiras de confiança.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Utilize o Canvas de Capacidade para captar volumes atuais e futuros, picos, latência, cache, limitação de pedidos e expectativas de escala.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Utilize orientação de métricas e análise para definir como a capacidade escolhida será monitorizada e melhorada.",
+  "cycle.capability-productization-cycle.station.api-design.title": "Conceção da solução e da interface",
+  "cycle.capability-productization-cycle.station.api-design.description": "Conceba o contrato de interface e o modelo de interação para o estilo de disponibilização selecionado.",
+  "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Depois de conhecido o padrão de arquitetura, a conceção deve transformar os requisitos da capacidade em contratos de interface, interações, esquemas, regras de dados, expectativas de ciclo de vida e obrigações dos consumidores claros.",
+  "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Selecione os recursos de conceção adequados ao estilo de disponibilização escolhido e documente o contrato de interface antes da implementação.",
+  "cycle.capability-productization-cycle.station.api-design.outcomes": "Um contrato de interface validado para o estilo de disponibilização selecionado",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Decisões consistentes sobre interação, dados, eventos, ficheiros, fluxos de trabalho ou contratos de API",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Rastreabilidade da conceção até aos requisitos da capacidade e dos consumidores",
+  "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Conceções alinhadas com modelos de domínio e padrões de interação",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reutilize o Canvas de Domínio para confirmar objetos de negócio, termos, regras e propriedade antes da conceção do contrato.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Utilize o Canvas de Interação para descrever como consumidores, sistemas ou utilizadores interagem com a capacidade.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Utilize recursos de conceção REST quando a interface selecionada for uma API REST.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Utilize recursos de Canvas de Eventos quando a interface selecionada for orientada por eventos.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Utilize recursos de conceção GraphQL quando a interface selecionada for GraphQL.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Utilize os princípios de conceção e a orientação de estilo para alinhar decisões de conceção com regras partilhadas e permitir validação de auditoria consistente.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Aplique abordagens contract-first ou design-first para captar e validar o contrato de interface antes da implementação.",
+  "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Utilize a lista de verificação de auditoria para garantir que a conceção cumpre requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "cycle.capability-productization-cycle.station.api-delivery.title": "Entrega e operações",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Construa, teste, disponibilize e opere a capacidade usando o estilo de disponibilização selecionado e o contrato de interface validado.",
+  "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "Uma capacidade reutilizável precisa de entrega e operações fiáveis, quer se torne uma API, stream de eventos, troca de ficheiros, produto de dados ou integração direta.",
+  "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Aplique orientação de entrega, testes, CI/CD, operações e segurança ao estilo de disponibilização escolhido.",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes": "Uma capacidade entregue e alinhada com o contrato de interface validado",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Testes, disponibilização e controlos de ambiente automatizados",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Práticas de segurança, operações e qualidade adequadas ao padrão escolhido",
+  "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Controlos de entrega e disponibilização rastreáveis",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Utilize boas práticas de desenvolvimento para implementar o contrato de interface validado com frameworks, bibliotecas e normas da equipa estabelecidos.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Construa a implementação a partir do contrato de interface validado, usando frameworks, bibliotecas e normas da equipa estabelecidos.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Utilize orientação de testes para verificar funcionalidade, qualidade dos dados, compatibilidade, segurança, desempenho, resiliência e expectativas de recuperação.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Utilize orientação de CI/CD para automatizar construção, testes, disponibilização, configuração e rastreabilidade.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Utilize orientação de segurança para proteger dados, acesso, credenciais e fronteiras da plataforma.",
+  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Utilize a lista de verificação de auditoria para garantir que a solução cumpre requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
+  "cycle.capability-productization-cycle.station.api-audit.title": "Garantia de qualidade e prontidão",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Audite o contrato de interface, os controlos, o modelo de suporte, a observabilidade, a documentação e a prontidão de ciclo de vida da capacidade antes da disponibilização.",
+  "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "As capacidades reutilizáveis criam riscos operacionais, de dados, segurança, privacidade, conformidade e impacto nos consumidores. As verificações de prontidão reduzem surpresas antes da publicação ou utilização em produção.",
+  "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Utilize recursos de auditoria e conformidade para verificar que a capacidade está pronta para disponibilização controlada e reutilização.",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes": "Prontidão para disponibilização e reutilização documentada",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Lacunas e mitigações conhecidas antes da publicação",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidências para aprovação de governação, conformidade, suporte e operações",
+  "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Risco reduzido de problemas em produção",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Utilize a lista de verificação de auditoria como checklist de qualidade reutilizável para contrato de interface, documentação, segurança, desempenho e prontidão de conformidade.",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Utilize checklists, linters e ferramentas de teste para verificar consistência e conformidade com normas.",
+  "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Colabore com equipas de governação e especialistas de domínio para garantir que a capacidade está pronta para produção.",
+  "cycle.capability-productization-cycle.station.api-publishing.title": "Publicação e capacitação",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publique informação sobre a capacidade reutilizável para que os consumidores a possam descobrir, solicitar, integrar, utilizar e obter suporte.",
+  "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "As capacidades reutilizáveis só criam valor quando os consumidores as conseguem encontrar, compreender o respetivo contrato de interface e expectativas de serviço, solicitar acesso e saber quem é responsável pelo suporte e pelas decisões de ciclo de vida.",
+  "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publique propriedade, documentação, integração, contactos de suporte, expectativas de serviço, estado de ciclo de vida e caminhos para pedidos de acesso.",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes": "Uma capacidade reutilizável detetável",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Expectativas claras de integração, acesso, suporte e serviço",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Informação de ciclo de vida e propriedade disponível para consumidores e equipas de governação",
+  "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumidores capacitados para utilizar e reutilizar a capacidade",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publique informação sobre a capacidade nos catálogos, portais, gateways ou ambientes adequados para apoiar a reutilização por vários consumidores.",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Documente como os consumidores encontram e utilizam a capacidade, incluindo processos de integração e registo.",
+  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Garanta que os modelos de segurança, a configuração de acesso e os termos legais são claros e acessíveis aos consumidores.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitorização e melhoria",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitorize a utilização, fiabilidade, qualidade dos dados, resultados dos consumidores, custo operacional e oportunidades de reutilização após a disponibilização.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "As capacidades precisam de feedback contínuo para permanecerem fiáveis, valiosas, rentáveis e reutilizáveis à medida que consumidores, sistemas, dados e plataformas mudam.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Utilize práticas de métricas, análise e envolvimento para melhorar a capacidade ao longo do tempo.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Saúde e valor da capacidade medidos",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Backlog de melhorias informado por feedback operacional e dos consumidores",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Sinais de reutilização, fiabilidade, qualidade dos dados e custo disponíveis para os responsáveis",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Melhoria contínua alinhada com as necessidades dos consumidores",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Utilize orientação de métricas e análise para definir medidas de utilização da capacidade, fiabilidade, qualidade dos dados, custo, adoção e valor para os consumidores.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analise métricas de utilização e incorpore feedback dos consumidores nas iterações da capacidade.",
+  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Estabeleça o hábito de rever métricas e planear atividades de melhoria contínua."
 }

From 109da49bcb739150f4d5fafcad6576c5fc4fbe37 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Sat, 11 Jul 2026 23:54:14 +0300
Subject: [PATCH 07/12] consistency update to all cycles and languages with
 localization guidance

---
 README.md                                |  28 ++-
 src/data.zip                             | Bin 0 -> 240839 bytes
 src/data/method/criteria.json            |   4 +
 src/data/method/cycles.json              |  30 +--
 src/data/method/de/labels.criteria.json  |   1 +
 src/data/method/de/labels.cycles.json    |  46 ++---
 src/data/method/en/labels.criteria.json  |   1 +
 src/data/method/en/labels.cycles.json    |  58 +++---
 src/data/method/en/labels.lines.json     |   4 +-
 src/data/method/en/labels.resources.json |  99 ++++++++-
 src/data/method/en/labels.stations.json  | 136 ++----------
 src/data/method/fi/labels.criteria.json  |   1 +
 src/data/method/fi/labels.cycles.json    |  44 ++--
 src/data/method/fr/labels.criteria.json  |   1 +
 src/data/method/fr/labels.cycles.json    |  50 ++---
 src/data/method/pt/labels.criteria.json  |   1 +
 src/data/method/pt/labels.cycles.json    |  56 ++---
 src/data/method/resources.json           | 250 +++++++++++++++++++++++
 18 files changed, 550 insertions(+), 260 deletions(-)
 create mode 100644 src/data.zip

diff --git a/README.md b/README.md
index f1da9d2..dc7368b 100644
--- a/README.md
+++ b/README.md
@@ -142,7 +142,33 @@ The main method content files are located under `src/data/method/`. These base f
 
 Some longer or more complex resources also use canonical snippet assets under `src/snippets/` linked from `resources.json`. Those snippets are now primarily structured JSON or YAML files, with Markdown kept only where a resource genuinely needs prose content.
 
-Each station links to specific entry criteria followed by the next core station's criteria as exit criteria. Cycles in `cycles.json` reuse canonical station ids and can override the displayed station label, station description, and recommended resources for that cycle. Stakeholder participation is modeled separately through `stakeholders.json`, cycle-scoped mappings in `station-stakeholders.json`, and `labels.stakeholders.json`.
+Each station links to specific entry criteria followed by the next core station's criteria as exit criteria. Cycles in `cycles.json` reuse canonical station ids and can override the displayed station label, station description, and recommended resources for that cycle. The `api-*` station and criteria ids are legacy canonical identifiers, not user-facing semantic labels; use cycle labels and descriptions for capability, integration, automation, or API-specific wording. Stakeholder participation is modeled separately through `stakeholders.json`, cycle-scoped mappings in `station-stakeholders.json`, and `labels.stakeholders.json`.
+
+#### Canonical localization terms
+
+Use these terms consistently when editing or translating method labels. The English labels are the editorial master; other locales should express the same concept naturally rather than translating the English sentence literally.
+
+Localization principles:
+
+1. English is the canonical source.
+2. Translate concepts, not words.
+3. Generic method terminology uses Capability, Interface, Interface contract, Implementation style, Publishing, and Enablement.
+4. The API Productization Cycle intentionally remains API-specific.
+5. Resource names remain unchanged unless they are already officially localized.
+6. Prefer natural language over literal translation.
+
+| English | FI | DE | FR | PT |
+| --- | --- | --- | --- | --- |
+| Capability | Kyvykkyys | Capability | Capacité | Capacidade |
+| Interface | Rajapinta | Schnittstelle | Interface | Interface |
+| Interface contract | Rajapintasopimus | Schnittstellenvertrag | Contrat d'interface | Contrato de interface |
+| Consumer | Hyödyntäjä | Nutzer | Utilisateur | Utilizador |
+| Business value | Liiketoiminta-arvo | Geschäftswert | Valeur métier | Valor de negócio |
+| Business goals | Liiketoimintatavoitteet | Geschäftsziele | Objectifs métier | Objectivos de negócio |
+| Implementation style | Toteutustapa | Implementierungsstil | Mode de mise en œuvre | Estilo de implementação |
+| Publishing | Julkaisu | Veröffentlichung | Publication | Publicação |
+| Enablement | Käyttöönoton tuki | Enablement | Enablement | Enablement |
+| Readiness | Valmius | Bereitschaft | Préparation | Prontidão |
 
 #### Editing existing method pages
 
diff --git a/src/data.zip b/src/data.zip
new file mode 100644
index 0000000000000000000000000000000000000000..f66aa88fce6089cd758795434ff268716e6a903e
GIT binary patch
literal 240839
zcmb5VV|?UIyYHK1!ijAg9ox1uv2EM7ZQB!PVmlMtw(UK$p0&@}YoEQIv+sUU-Jg0<
zeRX{={Hm`0%S(L&MFINz8WB0t`i~F)Ie-BX02%2!>C-v8K?4DU{+<1gLHP$P5JXvm
zv_(;+qD7-Rjk)}Py9CVtT*6S_#zo)p|8gZrAjtoZG1&jxO8;6=_>XzC7LK+y|DB19
z#s4z#LQC6rjTOb4Zu(1ap96L`wnlqPk(`>*C>k3AIHUl+(TUhGUOX9Jw!`4dyU1w8
z0m)posE|F|AJm>igR`xJ`|0{tkx!@l)ag-NlFvc{Q~U)2o)8a-mDu4*=qQxO8f$v`
zU1`C}cZPz@v1Z{^^H9FWFq_`9xaDm;Fkowy_~X5YZ*U1&o`fW#N}JyS0P>TK4=X#T
zw4Nyof`R7B{7Ukh9-}2APS?xxQRa<;shypgg+OD5gTC#H^A$x1SDzq4wqrT}dcv~T
z=GxVHwv?dS0GBD%`djnsB|w@)d1b-Y))qbr%#A7#reB~ZvD0&kfKWck6#l)bb?8<<
z#ihglB@A+qKM8LjD;gA5Y<+!7t4|~UXYPwvYwn8m%_t6D=>Xo<;V}BwLyCC)nf4qz
zFZv@epVKDluqpr#%*6;#&jbMoO9LIOS`+pHoum<Zq_Y=TeF=6&6NYgQS(Rjw9*G-Z
zM*#fj<=Ldk%TPSS%-Zb&NtF-$jW-B$fE&ynm|;{KJ-qX3?ZO+TOHUFba2Yt+Fcm&d
zo0qv{7AlNE7>Yg^oc;RZ7H`Z-YnQOPwYUYm-1QpGvPqXAkE~}qW7i&VbrpF2fu#Pq
zllhU@;$yY1BGwg=Qnt;u4Axyti5kzgsc-9d@u?9&llwNloYCu5MUV{p%tVxwP0tuk
z8R_$_ps^>kwEug}sXjiO2w1s**+_QZ1hByrI#I-av|+kG>S<4I!*opD?n`I~y?WUC
z90{p^MP85?cK&kSmmjRhR4=$SoChN@GZ`|L5=(a;HUW?m_mhhFA#jt~_ccxACvSbt
zCv#BDQjxQPdb<6Ao`|pjVqa5x6kiHKfL_c8&K~81Iq=Q$1{BUt^`Qg2ISWAuWppnU
z<in=97?n4g{sLJtRw=Scp8|<NO%*_kdD!vhq^bEkNiJ_O+D@^1)^w&i8%>7adX_yB
zUY%WZ^mcm*2$sxqg?M@QiaR4ziRe~zGJQX<MO<e&l42$)N#tpihK57$^21=**xrcW
zfb6wL*R_R&lGGqFLif>KBGsi=W3r)v%k`a-nN77J)i>U6gnZwEsu?H}{DStQp6iJ+
zj5^FWWSQ7#<}DKR%78mri=XCAy=m$NUV;o2^RMO3Qc7n_I`=R)1?(|JxBQS<POkiI
zeG5|{DWsYbjx<*I%v5PeG2d(=K$;o_(?J9nU9h0=Fb+%%CWB+JgD`!IoJXhQ$V;TC
zcgI&HeyE*%eDy^HEjI?*wc<r#-^eLD3Ao-Uk#m2e-3}_Z3Z5?8JMf@KFv0O?H#rri
z6d>2ACghP(q(#vm8fWD+t<|SP$&WAqwvkkNL7WEwQNwg<8+46$!MP_4&1=l2J<VTh
zCKU^1*sbb=6<VvU&@r-rABs<7LLIuiN=%|=0Nh=?XBMHn)6&(A!9G%^@|Rtu(6UyI
zbO8cdNbZi5W+*Gh)hYWOEe^kp#=|dm5YvaV*e8T>+@aWz)hm*j@Md~anLV*dWpcth
zC)`BI&eW`%W%Fc@mS7GN7ArBP;Wf`g9`<-}AhQQkf}3>Y3z)=g)|qnSjZhsmo0Iej
zYfOk$NlFOK6}$JV+2jM?+rb(5SpBinBFWuq2VuQ<^e=#Ma0{|EnvoRoyRT)J3l85x
zl#u!aU8k;fZoQ5s5zk_`kFhr^U9PYVA8z2Tyf`XWY33#_yLPlUmwE1;W17hAoM5j!
zMr>LLf8b9Yzj=tdqCVn{)u%zcc-0CfZSY-DjQYG9<n+nrf-ZfgS3iQTU|sGcsYwC}
z6c_ZSoYWVScV&4Lg47pkua!qq^5bFKvDz*e*e5}Ai)q^Y41)lE3<{<!h5b&{K}>DY
zdBFQ;+GBXCjT9ZYo@!5(vuPZLd$a$LD%us4#}|Pr|98^53+dZAF9bp&I*Kb=nB1j!
z!qBD^=d<x=hCVJ-f^4^{b%7RNJNA0=#%nss@#noR>)^A-&*i&^aOBj{7bP^B&7OCM
zoYyO!6{|xVYZ=G(qP$5bj)i9)<5$4Um^1RBk|a+#IU@qIvvd#F?*j!!x+C&eSCeK@
zsi{p4NuybsQkeGbDp2!+#5IY;8<b^q>-mz*wO@zkaF)BJ8<25Jn#8WApGW8}3eB5b
zbiS)R>HU2ySruj)YpEw74cVRPAdSo=pnO8Sy=0RMdBYuTMO`cr_|5yUWbNq5Udx?j
z`@D=vZB=lIbVuH#A_JWIh~f3oYVA+S%qK4!mQp&OmQpE(+q6xNYH0lKx(3QX177B(
ziIwlOgf|UfzYb>?7l_exW(SUCD!nx#)5;Y1#+&KacC8SWv`Azu?mE#A<*RJ6Un0q%
zxl9K46w?`)Z2`}DW?f~Dx+uR)<s*?k7LfueDEn4|kP$P|V>k41L1lSgk|^o0hl$S;
zRYl*h5MUph-AcbJd{2`j30twSi*>emYU1v1Gr8DjSkrCCV2)t4?(rCYiWYSx3Mdap
z_xGmkEytySrKYQ>cY02S(8^X*2k-DP_W1;pmx6%wlQ>;Ag#ZF-Qvw3|f0cm()PEHh
zB>!7IH@CL4b#MY0yZy(Tld-j(mA;el|5-7tlK)G4H2pu?<F8_PRNVhB@<sIj@*9Ny
zLz?L7+nEbGJDS@VJ37kP8W~&tYx=(x7eGzo77TyH#a|m1lw{;U7!W!$pYcaL27@9C
zHucbv;ITkvB5&l|<jjwoGhNUEgT5}EpanYOw)GoUgi38Uy*jdgAKn(sNkEE}gY7WL
z;c<pjEd0D3>v<#36e{hj3X*GMQP!kn27x_%HEtGyjvE1k8e#+18(AA0&A{LwRFS~&
zjS7!ITXY}V+<aO_Kh#m!2Q$NtbQ4!xoL?VVU*LQ$@FQJB-Wln6@y_NaBuzatm3mIz
zp^%bETtt8g=0*mPps5_$g>o~bzQSE>Jhb^5G&vLAQem5_dnDp?taZNNMO!~51p(`-
zMxbCJ&rHp}DSYV?m4sd8H3e=PyP>xA4Xn)GRvL*ZDb8-1xpA@UO2(iz0(MHajceJ;
zi-qE$^<kVW(F5_7$GW?zwoRUCTJs-c`d$w+@M9s~v$x)H!0{`7eahK7u`eIqLHzZd
z7_ls7QD7jTia-AIFW>n;k(KzzWL5O7oQ>rjZ0&3v&7I6`ZT<n=4W&BSetLwB_~+1(
zDuGi$Xsfs)Bq?QoJptUB-{noGuS9QJpvs@PTsA0U)BeRsbJ?4nu2-9OZ{v|P$Wd#e
z-}aOMmrTIX9^WqPZOREt)#538&U?Z;3@sD#7#L@?y1Q_u0gUrK2-n`AAp0YlD~QPC
z7RkbUF$~uoWM?3cUB`9sTHr?mk@A_+IAd<I!!i?rOY~Bh80$k1aP}jTHoT?-&qAI>
zS7r$?g*&bKH3GXCPSGyQi7w@}Zp#-GU&RYXg|`-pXs!#wFmuhe=;h{jiNm%0>0>>L
z)D0O#KU>_IX$H$YaQNPNq>$^m3sqX*AoTl8gG$Rf_ZvhgN{!Xmvmy|rj)gwJ|00sr
zRj!2jgJ|R1ze6Pa&kz~>XXHs(+vyuR{R27+O1+Zb{)8U%XFpOcwVUOGiUxFNSfg74
zo=HO>ZibAcNwebkXZvW$xCXq3yqOdnle_z!37+)hlB#+MXk|2TuX;Hiqw>5oTDs{1
zcw<zrjlc3HQuLf2eZur+7Y&?QFbF9ms29FJP+euGO?Wu6r9|O@A&iAO#}u%qw#zaX
znskC2qJ<)|C}7`eTxLS3_7e~duSxI?3^QRP%WYD-MI2@JY$Fl*y}+?(VYaa$K&4={
z0XUl4RPw%4cD5jvegB&FOT{uPHkobigaT)wn^n6_S|ahwj6}=A_k?U$N2}34B51R3
z3nP161D0&>ZMb&}7VulY^K*P+f8O%3Jsv|4Z<qWpnU#tAa>zeqoWcGb8Qy<J#!&wc
z5pyT^f52qphm2f5JxnL@4St0K012IWn^hw&jw}enPJqj;T)nzjLLw`l;h{V6UTA~e
zZaZLXbn))4A$Q-%)eA+0!BAa7uVZ|#k^)WMpJ1~jk5zB4C|?}FZ$MGV>7C<h77oKf
z@8*RL1h0M(Wfle?zfa&dhG($TGBf0PZ2KE48oMdzd2P4`3iRd+cA6$^mSxV7T!!*D
zO$|lUtLOmj@Me6>Wod)X&ZQ_%1Bd`v8M8qha&ca91U0ktLQE$Oz$;9qP8R8wM=@*u
z9ZCCS{XI8cg>x?LYLTpu)7{}RrgW#hstT~r?cwdrYB|Cp6YR^6gE`o^AW{imquA%m
z5xo<1oN5-}0)nQDh8tTm5noq_M4HZy^!H8iWnWR!n{GS9k60EYV#4S3VY<KIW;`QE
z0e`^7|66b({}7zBqm!+*v4f<ovxANCKjHT$reyp0|CTfOA|1;<5e3`jSx|U!f*hDo
zV=n)N3)u#yL4uR+_O)UGZnqvGQl5$Zi%hmF((H``ky>;HlwvfPJ#LR<k$R#bkaJ{}
z#U55f6Jm-8>=IE*W;e97v(y(nfS(Ah8oSpKFho3d3M_-&dsTwoF$OYf?My<y4m#iw
zSV|Gc4X>gf31sxUOh4?zM@|1)-Pe!!0a&#Rp#2L`ITO;Y7G$I666d0&X%Z~(ejWRY
z;2@S$oO1zkvvN7x`x^YOv<0(|edUZ|a|dKxowH``ppqD0SS8Lcvw@XW^f7tW!v?G4
zuDQwX;BRS6N!i92MWY{Pb{-**81JxA=HNjda~muqA2WLw*Z0how7#X?8LA~!X*tx7
z2U_qN9LOrnJ@W;iM8+x&lKp(L`;lkbA0U5O@<BJ!ar|L<1^(}Xko%vpG_tkUH~%L^
zYvG5C<zGdD{)%tp*)%OxcQJWMrDhf{DK{uI0msSArJfL8kNV|Fj*V^!kLQ87B9y>p
z%Zo>sdGVlJo67K`NdYF2(eu=}xEe*V#;n?F(H3gR!k7Tu--ge`vk^q4*nsqz6$Hc`
zJL_*wbX55EVkix!qkaVTmgTw(j)uo^L)0iG!)+!i1z=-%>V&IfZiXNhqqy5%QQ6ip
zLJ2S#l7FkQpU|Jzoy;_TR=zE>lA24w2s7L%SHMzPOxlKXRs_7q-0`kIeC=bM85~aL
zjo^y~o+E5Hueq<Dzml_<pXmulMQw-v;Dv|<-Ruq^DmwV}19h)p<m#(dl7UMLly{c7
z+~Q0vemw^|`GEg3-%VLn?ag!>7RdQfyP{-pGkbju+J6SO&Wb1zfa`FFH*p}DC=^B{
zJUzdoaYBZEB~K<nn<KU4#+`JPRMR@5vxxtfu6Als`;R|#yZ>#Za{V*9#xBM-|ET6E
z$Vm17iBIUyP=s1UkC_TK86rp`kuwPo3^t)Qr*>o)Q|hMu?sj}wYo7b<Vz-Q)PBz;^
zhRnMLnsLn3Y>=T+vhHyQt^7lz`|nmd!aDIl!SQpcSGJl?;V`g&ax3zm-0C1ItUnv1
zPAR`81cNg*sut@#0e%k6SG`{ZEuWjBhC(ADX02%BdeQ3C)L>Skhpt4thBo<=dPFT^
z@HH6YNeeEkKswF@pW96a1u`qq;?X-H^&O6UGb%#2AwoK>14H$|n&-Ex6<=e+{Qckz
zhN5fC*|k4Z6{>(^1;K)$a<Zx~{46GtS@rw{Q<LKR62`up+X%Hr>GKbPF@+C1Z(ka5
zims=J|Im!Ftap*nf0!)(TS3C}&zP7x=-Zju|D!{I^8ZrxaA!$C4cA56iD;2?$r}Sx
zHJCLrjKaUImVCG-n9N~7#0}+Fc-Y;)Tk(zC)bsL4BqaS@1cAI7zbBK}f<3k%WQ@bt
zo73q>i16>(7IFW4?GUjfq44k7I|FhXp)yqyipoM5$CUI8^DmUdJgaLtfqNTBKR|H@
zUL7Dp!?Y*GwlT7?yzo|FGvoEga%Bm~WY44{kGR&n7YGR%N+L-@ao~p3Q=?QUSUC#+
z^-Lw+e);4x@ZDH&UtIwOy<flW$;M^aoZHHyd+dp-s&ZzX5}~=8tp4-)(Zb0K*-@*D
zhNZcLkM5Scom;0{;0r&<y0Z1s3K=>yq=hX|AP06haPMF#W*4Sy)z6t}9A+uohG=uz
zYawcPH2m?goI>>T?Q1Z@T?)Ll=y!7g^O#s@^TOooTR!wqZs)&}=#Q&peepj?^&tOU
z5*7GoNX>1Wj2-@{%YP{U75|ICjIUVI4#t}gI2Q51NbCh~kdPru)_B~KVbykNA@2=j
zPBn77JDlWpYoALj&<mQ>0N&C1nHeA<W9Fa8+y>GKJUkXt3<D7y@BjM#VjjyXPT)td
z-3|#lf@$k6CY{Aj&0)bd*fTe#hW>NOIM#b7GcoCpx|~A_-Qd9elStb`blS2t=??op
zYIM=uNnVB@dl6!c$P{s-GwEw6BLFCNT9~BMaGVlSKEv3xv}1wl##UL}nF|XK7g4Yq
z&2*{dX5+fgYMvhVD4U+d@*kP$uQfH5<K5}%YW*`D<y*S^qX=o!JSu#-co)sh4uPDZ
zRWj#BNWbDsvl517=KRoJjIMg*$xbp`$0&U<-sO2uGM7h5Jc;FolRKV+Ip6vI=Ey3t
zUK-jz@RGm(J9vEm44##(q5fZTj{ii5#>+?z&?AIg1$^ZXSc1_(@5*RU>lg`ekKzqE
z<>@!1CrG1eziv%3Yg+KQBNUN_!c2AC-7pUS$&*S^p^G4ULe(~m#uDGK9rA&mzy%Hh
zMax7+3){VXIA^~7J+Qqf@C*BM)<WpdidWAZ_hktT!@eM_jN2GpJ!8R;XXo+4LY0Mj
z3uh*ksw>%ay>yn=!0u5f)XlubiW$5w8ZDZ|nL9+q6fZ0W424)l`<y0vq|2>bzfyfE
zSdK~^h^QwU*C{A9<M(TSe|>+VjR5~sPHhMJcX<GtJ!6*&qS)KapPBI$ZP8a(QB~)>
zt~EBJ>^jl$gX>~l7{g!Ce^D$II8J~5Y1@$e+v7CnKSSYQ?D&tWmC}Dok#~5h4x9Yc
z-C^e?L3lv%tWHEI1DBrJggB#$=E|3i$zJ`cQa;23bHAtUW+tK0Qu`?5V5^q8o>$d8
zyAs|v^zAN!vW|R!`A-UzwzZZMU~M8HFc`!wD1>}|%UW#x*^#P05GcVdb>iR=-_n|v
z!H;_FW}$wR#`$Hy{u0eh3ayHflIkDpFc^ckjx$?6p1LwM;I3z{GdIe>DKup8sLQh#
zXcpXhA)&h?euKTb)on=WkbWEwt*5zE9$vKOl9I{(dI%w}nAW+$y*fTJ^$ZnIk0J~7
zz2aLDd`ENpr79loUFG?A+W}b$?^l1eefZy2B-#JVZU5Jmn68PlmDPW9Nu_IS^Z$EK
z)$;eADn%xC^>08Vzv9z)z*6k@%eL0($9tGHt=9Y*AQGk95yPVmLIn}OIuk+FTt-!#
z3$1^!FT3+##^T2guXK6~jqnR~jkSh6jp_-4dnM~6Q=#U~L!|Sg+1DLf=q;3_N4bM1
zV}=DL1s*~z;S6e%<`o&K4>To%7h|`d9x#LF(>m*%La0;Bce8%yz+jep5^Kl*DPL}5
zvSk;ADOxunXG0(6F;R!>YX%{-){Wf|E<?_W9X$V~*uKUlKpo~xHMo-1J~tm)7czv@
z%+@gt^4&SBjB&=iW8EhS<G_91RL7!0?K`ZXs*g#%mJxkad~brd0J9bIOagzxDPp)q
zdSnpAh@A)0xHK9B-6C=>bvO)thuC^)KCHz=Lr%HokKr1}n#<g_A171awe&Qn3WhN%
zmbWGk8`SsV@x-2nFTLkDIK41;QSg^A*x$kT@VVN9$@*Vc6S|ktL+hKP?J+JK4X>+w
z57nXAg1HB`h!urO@NiqmJoQ}lu~wE;ojiWedpsm#*JS=8j^G=H$9$+WFWgq-{LX{6
zIuG4hXX-lEAVp^4p3;NG_$y!+?Yf{G+E&ioL^R{|;$YtXjl1dQ8#+imUS%$!NNQJH
zzBWa@I*Lw%Y!h9dFpVPxZ|@UM-95zobqu`5RYHt&t)q(M0<r*;#~!^|;Za>4bmxm#
z#Fww5Wm@%;adqjGD_3^c_(O*AI0&eh)ElRR38?q5`DEJl*UN8un&m3z-Y)E}OEKXE
zJ^VG@zmCoD_0-7&0tA!}_rIq0NS@>Wa`B4yzd82b+-+s<VQlnoyS1eYG8X@{TRYh)
z6-y$PK;~Aft6wIhin=YZ=?O2)$fQ0fQ=c|DVUT}jvQvX+b8=`R>nS{INY9V|$asWH
z^RowJE*7+8nSZj_74qC_1LsZbHMPo%sKCPF@KOHmr}*#u2uws13!;L8TSfQxP+j2}
zI<~`9U+fQvSM(1qUb5UJ<An73ch0S}d-tr3;o>(g9tBe62y~y9^M}-UZ`R#VVs8)Q
zT%N^22D+CMJ~A>+w3{x;#~T2ThH2)pw*hNOE8C!FqP5LlfRBPzfsBD9vi`#?$%^UB
z)$t3AZ^ZE*d)^N3(sClt7(J3xlSgfQbXDQ+bJ<2cRJ|90>c+RaC%*{fy%1AL0XHFj
zD+9*&VoE>mUvAaX9%6iA;ZferY1$beKA&9eH8PK#<B@44lK0bhF?r^Vz1XKc`AsrQ
zU2RTi3R@y6Do>_F1a<Sfy)2Pl!TBB~zG<5;s?Cx!e7M-k*6tM$nXUSo=>W0XF1Fvl
ztM*awjP={7`#2bmImhE%%mrBqCmDhubA*eJ;vS=IWQ>uRJB0dnm+yA298d~;t<Y^4
zeAzF6Twn^=$tBV2_vp`^+}uID_J9UaS_?rpn{Kwx<kL!(P+yEqHk`8(_CQ-LJiae!
z>(`?ye8&BVB4GWElINmt#zP>1-J4|;0sCPpm&qKp+fp)dW`G-}FK|8*3$dfBBBGVv
zUSyQ>w%Ez#w*>&yN498s5Ny$Rt*y1P3iZrEnS?w%JA;N^LQU7k7Tj?3<`|Ei<*~&~
z`u{#j`K_y*?gWPM@_cPRy`i`L5SmG6R;c*OW*ye6LCq`FsQ(E(dAxL$ZlX>Sx&{cr
z9pHRF3vk0|tl&K%A01lHWai7*)if9ypIa;$fqt`_=jLfE2aTsp8>JF0_-(c{cKW__
zn%}lABLxKPr3Y``9ZqqAkyg8V{_YQYgJE{`b(YdaffCils>VV|Sc~L`u@$dp5g*T{
zM2L4-b0i#}F|dm5C}yc_$j>U3dV9^@0f2fa9hhFJjuium|J_o!jxZ_?5j7j>EFAYt
z_>ib<-e*N#E7H@z=*53rc3EKR1+F@CB-{(?D>=v6zIXAZ1v&|e+xxU;gtB{e3*z7&
zU{n->m47K@qnqmZlpt%>!IgGp36e}oDvPma5Q}0?H=|5N=sn`Q^QC%ooXCuP*cV5J
z+lb+E1iz9Ed4J@relXxN^CdaU$V6_UqS2_(pDWT9Si46OsdF@NKx!L47UTK4Ic}9$
zKGLJ>h3KHCo+EMtzS|)ZrlYy*IAXl|sYzXX>|0AH3G0-i4{n$HrWt^wNGN%X`g01m
zDkC}V`+GZZ-uQcGjkQR44>d?40Rg4QC*86mxkgx5riU(O=nlGbGenaNtGU|``(OAx
zGv8lGl<<D@#q$q95m8i~I_&>Ma+HtUKxEM|xv|bLa@9?1t%y`mrWv5BG?L0)Pb=$X
z-ydL;6XQx0oPlc?jZmJ-cK7|XRQVp#rUd^$q9WE8(I{zf**|>?<XM&<_p_FrRnIt9
zKSgZzNK~*YkB;wW8^$8^gv*(Px85%%&_igOt~z1j%x||5zaiMSPD5w;H12n;E#O3p
zZ$olc5<aOXi}c!+;rGV-8FW;M87F@c-R_q$BS&2lF#pDHR*~eZl)ANgEaILg31$f1
zve{!!7P<>wDK;v&*lkq&cH!<7WjpFsA$tpoS)i^MjzyFXbq`^@=xHyy?8NouG_2Q{
z?|1Qtt8Q@Ay%{gpO#aavv8{v%d2d^C2wkrm-q&)-ONUXwha;)PGyO)I-J3LjaCrH?
zloa)BW;u5HyC|fHy`x<M7-ef%qGH)QGYXpc)w5nTqmdA9=}!k+o^UZlCF(q&tJ8i?
z$KCG>s-g`N=og`p`pB^0Zvp6$aZ*t1DYwXxh~M}~$3KDH*z8f|ddJ$m07)rH`<-Ds
z`(|U~eIT9G%XP?j;OV1u6}@r9PGlsBTpHUeIIIdgV9>AucN)!v%S!fgYR8Sb&YldE
zRDkccAnGOYuU?C$jPel2c!yBn&murmjsCDld2nf;k>7wGB`;YdhFE5tgiZLC#6W@`
zs6Fll+?WaHV0S?4A)tR!r0YT)nwUw`FE(nCv7G)22_$+|M=LE=)M64panr4v{2lO=
zznQpESNw6EPrWBifDC*oyGp^Gn2^?*s8?1M^F}K-dWOAl`Q04zW6|Q*ZO&H4=DW6R
zJFQ@PQA7WW0bvP<ou}r2Iwn(PGGr+X!&P%gCjl?D?+t*k2~%iKjyL+HQ&I<Nk+Q@M
zKQSdZ$63m_x+&yb2>GgeY;Ur`Y7WV6znL^R{kC}v2l*N`yYMvRWIkRVKnpc&vRE&)
z>E5v!Kl&z0tXpVxua(nj4-Y|^JKhrZ$Y;Fh<TDxigkWl!I9Caw3}IvyFJgjF{>#aO
z=eh1s6$(_J00|Gn>Q|tUt;Ak@K+#nQ0drS?P>h)l+qP~PDH5mC`sf2rUzOJINwRq7
z%3P)NF!i;$j!T)ARft|7JCC)E`V4$3qmv||**t$BxS>Zrwr<)YJbLZVq=lZ&w_-{>
z>1YD*OWFxC+Ge7BL>6518GnBWoicic(Q#WD#W6Zb=MGi097W!|oz`QrF?NHKVd6T>
zVhP*v)5K#iPo?@z!lA^)Tn&3O*?Yv%#<6$#y4f1Lz(C#01Sct8A$Q?<yqTC3mk1_!
zb3_V25!5l`FGE+4+#Eg>U;*g%QMv?&Y~qX$PeWG2I)3?($Ka^Qs#zYWu$!?xf&!ZD
znZ(ZKq2V8*2m!ETuLTngZlDuOuLD0uP@18-RI_8eO6{OFsb-hk*A(jwCNARQqv;3J
zaDHYXIGksr*O(SUQA0w0+~WY9XXBK!C3D1B#9jU(0VkH?qB+#dO+Kcu*Xw-n?_h!Y
z8Zg3{b$Rvvxsys-lQ80+Yb2g<NrUr@l%#BxA?r!vU@Qq#Znn~zxW#)#xla`ebumjE
z-*O_a2}H_Nzqv`C4ljmwVGx`44S{5(u4c^k^!pd4|GtzD?Q7-;FP7Epab_IPEA7=8
zSHG)DA5dV=&S{W7!J-baV%CPYW@%x>os^G6l(MPNAeeW9;6xF<D;cbP+^J-3PXHRu
zaJj0s&Fwequdo!aUU<;sp+)V1@v2!aEv@vpt?rG8&u5|#GDE$CTgNd=LLPEp7kdcL
zhdt;9nff9B0AT+s1e+sxBU7BXia2l&32O02m86Z~19fH8QNUFMDCVflMqNhcyn2!8
z$&<-lhjpHGc(bW<`0`z-w#LIUzT^J-_PB#|N8BkiAx=Cm%ac8;6XT-0ej58d5(hnP
z^uPcnZaiX^k5o!887Zxwm-UDgL_01ZIE={|)x;J~JJS8kaQyjnu)0!hI0u3Y<*J$M
zs_^w-Ck-9dE2<8+(N<^oNld~kEk@Xx;obqTeu`ZuiFa%To5%D1Ku9;D6Lytg`0}fK
z6FYGQ7r*yU4{oO4Q^wN_=)1m(FBH0hlclxB8SF;uDH+cc{4jGb+01Y6a{ZCHBv4z>
z1u6>_Jq@3gAjZH;eXMwLSI<cYwv7i)|7^{YfarMp7!iXKhL$?>z9;AS_2Dz*K0+t}
zS2|2DCa4p$^WEuYB+x3T;w53LYbtfy8Bbj7Q8nfUsSzPkDS7CzoX2>3<Vlufm8aQ~
zr*h^mazgro6`kEH;D`%ScO6%+*m<<1L=UN;QW>uXb8*s-yUkM@rlgid1#?&!>h+DH
zqg+WPtqfpupVafz?+}ak;Vt&Rd^Jg2T}#sH5hB%ScMIgOA%)b0byF}H17CECH!_h0
zJm@1lf=H<s<Wum(*YtBl6_?YTM>9V-d5hh-O;Q`O#WAk;*dAYiXwpK1`4T1~cDb^&
z4>f!__ESbSHcgA1-;Dxz%kfOVamb39M)`=eci{<)nIiVV#$J)%cG4o_dOSyE$GOSq
z+#ZTPoz8l^(#j^v6o6QhDrmt?oGdV3J-4_=^RK~X+dw`W6_P2_?Q&pWODo<sS~#SK
zD4-i|Ss#z@{$58~1EtiA|8s&$P^2RCL<(!T)l>8{?_`5}abmkqFU^vA;HJS&%C5dh
z*3Y?PAR6tm%K08=I`zzp@nn#rq>ts<k(FRo?U&VwBFb%)Yx>p~7al~wpL})4ys#X@
zqMxqujp#~>lTx`}1}|&5Vbl+B1@Sa_4tAv^aX0asZzg3Kp&(4t9Z)m%6?`>goBrv`
zZY7Z%M<Ai+;bXw_W20&|Ns=2~$=hXIpO%jCpr&WkpmAcr<7F+?cC#kPm>J`KjfnU1
z^Rkknt9TfRNO;@(xvh+CGbAR2r|Y9X@{uft@i8;V&>2+Ib5CN)pg5DwEAeW>9d_jd
zhOn-lp4l`2!VhZGwd)PGn}vMof)ol;k<Ngzm%0Fdpn)l8=o=p3Tm=z{I;k!^(Z6t*
zX(A?2jTMeBvd)dDB?Zx1Vy*k;K$pD+pkI0E(-8CUm<w`tWvP^<6E|a4&rjy%(hk_=
z3J|ZsrD6&sRwnWm;olr7pIJyi3uM%$r8OM1+a6v~>?G}O@Q5WDA#86A)?)v9)PH73
z<GA!`A+9T}%Np%Y4f}+d@FHD2d$$W~n50?!Sht#_1>pC$)d%S>h2W$_@Ka3TGu~_m
zf%gPAY#xY*KrXY=?qscoP7iO-uU)!wdAf8WJW?_wX3~Y<FxlNDDui^dsjvSY8Z~s=
za163ObqZ}6t>yU&>O+m8FTXkGXy0?a1SIvPe<Ib!_TDZ6vYQ${SB3$b%!DSlUa4q&
z--dNX()3fVoFiww0P$6brN`87(((y5J`<xG@z=XlL|GQMy?1?|yH6z^1e+V}mFPya
z8CCn|Fy&>`FsfEy?DCH9x$D};Z2?652wM*Mpo}T=ccRPw)npjbXj*jG1b03n;N7m$
z7oXF}NL0T;eN_kD$W_!@@-7q0=w$8U)!$Kxh~X<k%+PP<RozoCRUg?-2v#P)tmBso
zRmpAhqDS#MUgo#xY3aWsx+Y5NOL$n~IgHA*+{*GTzVEbXEDeNO>}nJTZ{2Cb%-9?k
zD%a!ntMJ(q_`%)a*grLO>BAS%Htyyfe7m?Mk1sB2iQEre()0|rbw7j9JY@1;brUR?
zA8xHBDtaz8Cq39RlCY{bNlvCABKX?jkB~}3DUL=W=~*Zr^aTmL_BL;g<NJF4Fdykl
zdzUb>Xi%q%_flI3MPdOxf;TU=H{=-6NJVZ_qDx4)Y7s>S&9Zw(!7pc-gm$&lM4|>>
z2|Wd`FKWF>KQ~#>P{<x=?lJQ=-L4;*p+VWY{_sBO(&6>7)%7TQ_M|Fe2;EEBY{a~4
z{l08L|7*WsCm<;xVpA(|V=cl0<SljOkm5na&^Z}**EWWN`FmRco=1zAM6(6XJ8Y0w
z=Ydx$ztN#panGH+<B;GeshCzIuAAk{tgrvPks@d0c5#1ll7UpS1zGla8FW^&q}_fV
z^^ffA9OjhooQT9ONJObh%IR9AM&qIlX;G>jP1SRmOCkw8B*Q`8z?_`rwg;i>RxAtG
zUYEAoVEaeHoy14D_2%J8B1Ix|Vv?$zqICEYnQ0DfW5;PhKc3GD1e!kVue`l>b^^QC
zk7|Z;jF2NjSLkKupiD=;rQxRO<qayOPXMTp3rF*8D+)GMoqHK>yPC%0$61m<=W3#7
z?p<xSy1HIgf3$lU_PxR$n_G03?RX!Vy72}lB3U03TQeJgJ92_Pr}7OL#l{rdH4^-)
z%i@R-azq?J=x;P5EP^VkPe{e5>HNkHN(L4;MN)?8py?D!9eOpa(Yh=ZzH+3k>-FwV
zPAW_lF8i>CjGgYQS_s~$C8E2O{A$VnMygBf@j7wQ9vs9E&GFD33tu?OF%lG0%BX2g
zn^VNN`!dqL`^!8-dwW$L>|;7y-I6VM>+r@*O~|2Ujb*#x);1npTWZpL?s_Nx(9@~b
zMaQP5`Wr3O_kL@|pO*Rn#R{doTw@L*<dmNfoy0W0fYn)#{#@*}K!0a4i)kO^gaMS4
zCT0Ln6Ps{>7fdPUJ=sDml0EJEf*I!}*|E{^id|^-)d7sO*kRzYc|#u$q$DE+3G&3*
z55@`~xJTv~AY(Zz47IK0AFzlMNF-B9A7-xRj=-5NmHYx~S!9Z6Ee1JYl0u$Zi!GO#
zh36|CHa~nUiDso%ryvXlGWl@W7;2gaeQ$5=tsY=GAJ!B6sq1AewL+NXWF+&%@zMyC
z%FU)M;5Zw1trJ;5van;GBR7M6^{00w^3YR)lPwc2MxrAisrF-LfV1tOU%_1bmg|Fj
zaJTAm^!RL1z2gyv(N3?OE%LzyenZuE2Zpovf_G0<g6g-+71|<z6Q4@w(n6bt^bKn1
zSRPeERwYc5haSDF(tQBRQj`NinA)n`;)mQPRjkgcUBsGIj&FIacZL{UhbHIZxa$r=
z5MOASsEU3W2Guq8xKG-0Ohq%}B*l`6Rz3eDr~dQnc}HSb6pC69;6)Lo#^4C0ppc%@
zrfAl{rQsd0GB+WNh?;NbNt6c2?32PwyYAZ+jI-g0-LMvD*t8}c=H@AEy)xXZRiC5R
zWWyTGd+7z;n?uvOs`Ox9200XKT8rE?v%cE)XrbX*j^yP`la2*^xMog`lel+2bgLp3
zd+x?W%0wQgf2TII^*$S=2W+m@Zt_4;(_E}cTj%e-7EceQlsQ{cG$!EOKJ6n*DzfY{
zDaS~&C2u&v6_reg?1zD0*)x$f-t6u=dX9r4nWKHvm8&wb-gX-=!{3#b?8v<_o{d<`
z^5Yo+^UPD)Q3SPa0S})uF-8Wz`7xGPt(rQ(LKcVPi^CJBUk%MgZKMO$Zb66U$o4sA
zfct}%eg6LEOcpb>mDLFjb;7Zp3)uLNlgM(>(CKix?Bg#NiO0?LNkE2kJH{&X{2bDq
zMnD3oeG8B8GO24N^lo(l0LIu3?grvAnkBzfqe(`!3#76IGNb?;m5QJ8ggP1<Ui^~A
zLpgF<HWy;e(+ZUo{mI!y%u2CaMtxoCtZO_bv~E0^C1VT#xdus>isKH;pjvI0j{FmE
zPW-Jcw|t}Q(IC;njQK}XRo!j!@|X*<1xQv;WD-Pv(1d9bL?y>{ppKc3(t3V!{sVqi
zWLe9Q55Bx@Z8KH8=;|)Fv7?eoL<0E^@WbSrw0h8oid*+RzcO3#JHW<KA8nC?-Y@K1
zb?Q9ITP-csK~qOS|3OuyPsw2^Ez^52#*KJBS@PZm%N=7XFOw?4EIxWB60hH%KgZSj
z$C14!a$tJ*DhkJpf{DR27h^Ei4L1&y2}4pvJxH5s_R(9oduGUbz^)yq`XVqN3R}5+
z@;$nbI^|p+=$N?fALrGM6yY8h>&Y&WKtG^v!@<uDvzm0GgQwUS?QdCTBYOp(v&I&`
z_2XlKADZAcLtv@KU<ny%ToM0fe+~2gp*!gGdCO%-6Y(KW^y;j2UTG-FxD6bYeKk`q
z`i-o3?1Jq9anPU5mjqjzsc)u&V6TnNpaTMD%*Aj~R%tOLBypX)P{gvG=ZxFrv8`z}
zhNqsRT2?OwR)bnsCFCdh^nNKjAE6^6k0ogR{`BwQuSDm-gQT?NmL{9MbXs3fro8gm
zH=|BDx;0VlEgIHVs_x???;0%3wus++7wVL$@1ZH;f;dBDKdUrYB0V5<S7rP=<yNul
z0l&_ucFfo2B1-UM!UAT|-!H`s$;!GgSZqZ<D+P+Z*W6T@-L2ON2Q^@E5_}fRhn*B0
z&JHYiAWJ<`l-Gcw!&S|`UL0ilhzaaiRX~}3B=(v3E?_7)9~S$$^Cwi>jW2j#=nYBP
z$S;)5M4DwUt$_Nru$g+BP;Ei8q><`Hd0RQYS=i+3u4-UJzl0h5d79)+AAc_TEe;#_
zE#zW2G@~-aB#6C)RvA<TvLeq5Y${n(#CIa{gLQIij_;!t|8xH4PBTWA%-cosv+Vx#
zUT{e0M!yzwxxwm=l_RbYUdjWs#U+*Y7jY`Zt5Y%K<=g8k!+JZ*N?<|<80yFG)(^%z
z=-2Bk-JoK19>I8*w{wR`zvu-jWOMsjcsSBY8Pi$@3%85CcQz20Y+ceh<m^bRF@en7
zh6H8bL;I&A`{0V+<j54s#!7Py(^tw4rl#h$rtG~CZ`W8Xv!fT+j+SkB+N%(5om^4z
zzBpf7%)Szxu}Fc1^)8ff#N(0O)sVI@v+}gZN4CjTYF`xanF%Y41Wb5VipTTjs)T;v
zRfYPLjB^7Xx<b=Im3GT=uEc(-N(SGdJKm4)PH}^p1b#H=7d0e_=)!0-^31?JvU5rw
z%;7x3$YJs%X<OvxW27ZnTOwo)Wfbp?b-(y^6miO*oY-q+qR&X$g(7<&JhXzm_Hs-Z
z&4y;~t<5&;-#BI6h_pw!BfA4igz?yIX4vHfHT@TLR5jOf&s9R@qSW495uk-vkh(t2
zj^gjWQmnmPXS-11kYcs)iY!`5$Ef5G>)g#4%IRJ?j}F?ia)v0kjvu>-Sc&UKgA7bw
zI2Go4i?3LwWzO#a?$1xrL-NE<R<$2&Mbw#H$UV2`1f8)<Ttk6ckKg0*<Y41)in<df
zWbMm0EvT&%H!?!%WXYU)dX#OYrS~i?;d(X@5G9<-z#Po;VZkGQ*=K#9q8hbu<1<tr
zz3s3J7`6p<0Xn(vZ8=OEB8METV1L=Q9Xz;yut)VqETzoaP(IV_L#2(QojJ?i%m@^z
z5{2tNQbl%-&MDUwJeDChgJ1DU?ER^E*)|8-N$0uj0Xvo%yBuKa7_I+{&{l7Ybv%?O
zL6^eX$2`MsdJcBvRr`~7HKSG9Mk#HX-f#bwC;&XHLR-;daocnzGOIa$e}abxb7hEi
z1`GI)!p1*Nweu^?6z3TZW6~}3f=++%IreDe#n~ltr@sdv*?4(+-P^>TTxc=Q?h_|7
zALDnJ>g<HWIM$6w9+oz|`lTI&L<uq$if7ZJr1==j){GypuU*_i=Cc3^Nr@RVT~tIR
zoaemV^Dr{Q=ygC0_l8qLOaXJHm_bm!HpTTTq`U0$?%c_K%7eBRQmJlb|FD^C^U^Fm
zkw+k;uYtbKJR-{{SCG;?5!I-kao>z<0LZ)O$1a`6itQ6^ElO|-pSlxQdAQqk+yNs2
zAFC;I9h&X?U&$$?AQLt`133;0=17%XqRmyvj!mCEL*8I?LVP+%ukWn^*uz=D`PAte
z-#La91+uIh=KA?baA$bF&lxf^FMvG0%AY#EjbLcmx{By*U4(f+zT%$CQ#k~23P)Ns
zAg@q}7?#)lh=)f1btD7^!7!Db|4s6c%}7lGsU{7`mI~)3>kE&DYFdbNCBcS_qgRS+
zC3rxHR~>316jmMWCHxDMEtM43Qy1UneVx|<b>i_GyAD`|rbvJt6{K7~k$Qc&jhwgL
zBRFiX8<O%F&B|fT3>Q}@74K;{9bY7dsT03oJ55R3)I6f=V)Di|Z>53>q>{&53iC?{
zgj{;Q+BS5_Wp&(~Pr<vg(|)>=W%zaqf;H3=VS-R1f-TXESa9ll2{gKjz8#Jp2=V2X
zMB%dcvoa>G^GNKwdgu+eM@3Q*5!hYAMgZe$Q(?a?QGHH&%SjPYy$4@XGq+>oyluRz
zes1hKbYhRqMo~djH9N!!=>tz%@GEq5>~0d`Qy<IED`}5&{!L(9o9PTzA&ld?xqPCh
zWs<0hIoe+{cqFKc6K@-iPj^v%x9(}RBNZgF*l#>LsK?!!I}TU%H0JNgs6}L64@NSJ
zK3PQvejPt$@VIglYlV;Fk3^Cs9L(0G%Yyufs99OjK={?2ekSt06D5QO1`7q6`=i@8
zV_j>q^SLA?^1AZ)JxYD23}LNCUiALGuP(O%3l8THflfet7lga+)VG<4u`Ic%#0|2`
z!j##y=vt6o1*9y)DjMpd@LQb~4dJtL3Mybv@Gb-Am<fXf=bUwlhQ4mpAA5v!Cy%jP
z%Ws9+20dd9bQ!McJB<%JBC=Ez&Dm8Ne$2Y(TBz@aG$a=G#JwH>At#!|Ba|G5C70%1
z>PST7_&i*C3RSwa=$x8K8lc`wN%_kaIa>3^IfXeRXp(mz=FXJfn~?cICwvneM*o(O
zT#Q(qTnw$$C9>ln#}01J(u1q-%;2O6G_6~(m1ZcQT>B@WwF4|QvlGP~UQV$5tQ{kc
zQk^%hP*8MFwBSct>phV0`sA5nV2V66$_krF@1%djd>01{kALLpT8iH>8_r>rVuGnD
zaMf9?A6D%QAwbMn!%21js&b=o-#Y_XVgln8WWrWP1}#&-OaF|I+*mc0pV!1X9d{Sm
z5Oh{1!%Aj5RTc6jT#+<?NHL$bZb3ph!>PUR2r-8M8}c&{bY?WNRY+y@`?&ri;s6I(
z*fhCOQW(Z`$*3TbGciN^peg1rZF@T5cTqd5=|Ltt2$xjzcRorIW&tBEpC|^=_Vruf
zQ|0g(>{c97QU{UPlTU4~&af|Du4TV%v3{@#xpoZn4c9;qIy<d+?4I7KV6pjYH&1AL
zfS+F8<u-e^i5#UvRR~)F-S|i+)1Z~a3Mna*YIcGSfqJrF?4L(s>6C=ReLNp>Br)L7
zk+729%Y?$c^7f&T$`|s5!$|ww22|+yV#Q%vy2CS`h}`YLM<zM_+RX*=QPs>5{B@KY
z2d?uMX^+7AY#4Kcb{tiz_=l^3geQM$-E5>2A=wSBs+DCD%iBAmPy{+_IF3bqFrIv4
zqcK5kT7|C~u<q+t<pJVdK*(o%)tG|G140b)%#0*xg(Q~Wgl+rzqsi$UU2q8w)+1)J
z$rcHj4gKQPqLsc?4>>-^h7PWNcTNVxqW7v3D+=VY9-G}xX{t0Pp7S9;sWp~{>-0$T
zt4VyzaSbI#{_M_-W%O)hFtqA{M9C)ugr)ZJ(RN)pXHM(I?QBuA{b4_kO}`OOfjRtu
znC!JR4`rXX8_RhUmW}^hk?7U9&e^gKp~J(ucdzu}S|kfbuN6f~^c4ZfF5widFi}~L
z*ws$<9D9;$mWwq#qHu_h>mr&~IO4Mn3M{yh>U(bU9fTJ1?#%Jr2ro}|b8kyxK`Wx)
zt|GR;Xg<-brq2=h84b@5^6yv`{Yu0fuUZuW$(1&B0>@T$T?Y>_^_!+M*bZ$87v;p*
z_&hwrOesb#zdcayQvyAx=j>_K`dhFrwRKIeRV=w>M|G?S`|S&0^Hn3HRw8E~9PNp`
zeK-U9rdS%MdX?U2d~-8k$(8lG_hVvYQ5=}-9C2m9`XH-Zu6S=TaP;cs>S2ZU0NSDl
zw6$}S!PaK|BP}M-bNZd*j+^5cttu~^a<-Btyqx!p*Cri<cM^&EUY2cDvQ~U^ulJc5
zwmU3wfD<x6obc%gm0R#Jl+hSV_L^KPre9Z2lTa(7)E)@_p?GBfJ_3F$E06Fa+SC{g
zHuYuWC}x8})&VNjSQVxuwpza6TX@K7Rq4ZAgWyoEaJP?6TI+5J){P0OL<`wGR#6FK
zx4CV@Y%)D2&avl181@mQ=<6)E>+~J?V6Rzy^fNXu9`!Hw5^s}3^BP{X9J4(MerrOy
z+ThTJOfWwk;+uIi4VeCyIm>CEYbWB`Ajj<Q{b~Ki?=!4{z&D3z5yG#Ydm_Z$Ew~ja
zxJq*Z2NLe_0v#(OEnf5Jxe{}Ir-k;rTJJUKymwlgzhYj-A_mrA(Yt{#Kf0#ey<B#!
z=rP<bqSB#%<|fUcOmtPJ0Y32<q)Gzs#rFEaX1X2pCY;a9ebQ3T-KuQoiq=PA10(t<
z@w_Ma(_#m5VRrl0949AIV}GZ|3Uw@v>Dp94BRK4FE!v;LUa{Y-$2_^$sZMqB@AO&g
z6rR8ge{0b!u-5fj9^XxCzKWLO+a~bm6k*l*$sk5sTRV?Tr>!s6L3^v{xYNMi)RS^)
zGWP}hdww;>yIe&>WFQUe6TLlBVVrz$tDeOI+wa9V&mtP{L-Dsm1X3-@MC=%DO6IJA
zYf>TRGPJj$?6Euu4=@+p;X&;BjaW)fk6^6W#!-L&>;?LuGFgm@nrhh#p)EWiYYm!<
zCq^*^s{TI8Oc;6HeBk9|76*-j<GvBhIE&^UZ)*hJPtb3c^>0NZOrx2CAVvui9Z`rn
zRzQ)%dO%-LtRwmmRVaMz>YLuNSz-b_R=yymwbv<U=ctFzW$yM!?KRxjQ_*FoqBvIP
z^+Eg~bti)-xQJ-EKMl6r0<s+;S+Gm)!z2^)<@a+60hc3n(n~fYIqc^5!yw2iId3Gk
zI%&VhZ?~8pc`AQJSa&o7m*jNpO<%OzRD4%0lzj6iUls|qY>0gHtJVtpE$4RBO8PBu
zheE{RWbFZqA~vgNmwZ-Izg84F9+R-;hEW;Jm3oDfqr`+_VXHl*M>4p2YriJFg_bz{
zNW*T7AXWzPPVXh2((zR616vxR*=k7-YPkZv%&(3Dj=t`#G=HuGbvHaiYS+4BmAt+c
zXlY7l$Aa0%1PKQQCLY(gZKbMvQ*bmSBR1Q`066Nr(9o_cg-Yq3<>z}!f2mSj+MPz!
zl2#;eT`bd_(d+(-$YB=uPx=zAY5TWLSq6JY<SYj3Ca^v40$hhJ4XXeNW}e;w!%LVw
zsiayS`2iwif!C24(wcb{yev>@WVql_u3(3nq1d^>#?6FUaJFAsJALgPK6+4NTL<ax
zFT@=;vNj*9UJg&A-_hv?sb0ag0V>V)7j=db8klIn>N(%j*ZTwQycYL2LtxHfI$c>)
z^lS0N3k*F4qZ0c4t!%YtHh*qld6u)bx;m1@f%fdsHcFY-3JBuFa5^SjZfe-ZS#)x(
zj%>_`VRPI{KSP6SxFqZ!Qsp;jtc?-}M^~~OeN&Vn^!LrBW40}FXQ%i^X39Qal%P3k
zZ7>VlKk?o=5`{>v`aaxG;W6NZ2<Tb4HAAdP7=GXcIjN!QL0*o{WiZ%g^bJ&}o`f#k
zo^2+koo~Ci63*d#Vf{*kMct`(^|tD`Uh(98bm(gg9a<cpM*qTZS?<Y%vg^~U%SQaA
z>>dypW9%@cZ9I*}lsJG#{7ux%@)w!TVdVABV#3biN0XdfjA9HdLi{1y<zozVl(jHM
z@bm$>nd{IZkwc_y6ae>#hVs3{4s``j#Ok4b@x<0DDn@peY$qT_ic>H^L(n~1N=sM1
zUd#dVornj(in{+ozpGC*7aL$Pm4kXj+^d~<T<SKv4!4_8@Y!Py-)(&%JEano#H-y=
zR5clV2g|i~`l%TR3MIzS_iSc&g=je}KT;S3cfS!MM0cMds%<6ja<YS8*zt@3f^rzQ
zRfwDHHph5PEK3a4kx?*Gx8vlthg@HfsMuG>vZM9`p|!MGSk0twxW(I)V&6tr*Ac35
z1U{7AJbRGEFvdc5k*U~{Z@X!Jnim^sk?-e8D{*<Scu^u{o{)KK?$Q@c1E-$!CV5`(
zn1W$&_;;_SsIo(og=IUB%6wD_X%4>BisEi8GaHBln@Xniry-F<Mz)Z>eSBU}KCRNX
z5f?^9iO5HQ4_cSyM$_#cMRZxcGtpupb>+#jgd28)p&B;R@dDYeR>bFm{r6=Ri%Yu?
zdy+f+@E|Ok#Wj+*CfSfN|MtiWPOSE2x@pX6!mImoN1g%Nv5BTd;hO2?(b0uKU3E_&
zV~?kGogcpx?`q(W0~ZD_Zvb-<J#px)zs)&P2xjT4R|wzd_Qe>q*3Y4{8f}Ql?@4T-
z2_&2jBer`RLoG#hxbZn0=H4i3&3g3}AF+Z~v!fi5H6c{znjG<*@_8ZE+&Z^|piSqP
z6%A$^Ols?Z7sfc#a)M~NqOdL<hyh`wqhU=eg^f$p<0Db8i?WR)?USgy7E;Yk6D>g4
zw_eb~b<_DxMBx7eH9*S0Wl^}v*Ufy3h?qdGO9ZQ9T<yeuyK^%TTvmPArP^iWavJGt
zhFp03>y&Icx9^+Z^P%aE;&npmYujVfx+`f(+NcpH1Z)qZm9r_>82-6B$q^P!13A|*
z&Pr4Mr|z{AM+Uv;tn)Fsfs1yRYjmI|6IYFN5M#x((;C>UEWI{#@9L6GhGF>oO)o2B
zKI*6n&ZlbL!v<t|c0&qcttz3_fMnwfR8GLsWN+tLb7ca;^1fN-Hv%58%3NAG{BF+%
zxry(x99ME}Kq`p*#y587(65f~2FcY#t4nR^;Q`goMS<Et8oq4`Y_ru704Qw)plpW#
z%2o^@ICXt)(EBbd=-ot<<-K2(jkBQ*2j1(%3H!5+3E7_;C({0=ktk?uz`tB@!bGdH
z3G3?St#N#1_`!v7ck8+`!TLdA)|Tw5ojmLH6Q>7l#Y2;^z{ra2N7ibRZSwczVDYXl
zIYL6jf9M1WaURtS(4Z9hEWj9$;M6S!MMwZd69}4~I=0tNAFZsy%}~BZAb|=)h+a7z
zB95dJ`^g<k``R=&uSr|RNF!mvYv?sCgLI1k+l|IuH!=cZtq~AVC|eVrO^YNi@vtQ@
zTH*~2u@{~S;ruAAZ?s-t*gy!rW|Qd;CqAD|Abr(sp5|qh2%VH!*wDc9XgDiz%O)qM
zb)y&`kAvNxuO9rs9f#!kDU(=T{ANEe>%lXFEB=4(oqJ?2Y||LQ+_zLOUxSU`@IepH
z`DsaEZJwV(NLq=>t2*6bZ7x~PlSQOVlC_!}c9a8c=OOXieKintl;7C?J#wIf*X}vM
z@h0Ffri6_>9_GNMh->2v+l?<B?nw)|E|S*S?ld+?bUp)L0M?lv^-Jqy>G=#Qx$GMO
z!diwg6f%sVD~WD(Aj8%TWM~%Wz11kEg}1%IEXM=xI<KF?aA_I^6xQY%tZbQUSVKav
zWO?dP0{<IQpx9(s&9%EQiD6x}lc<O6?O!N)ez{E?31$vrxJi?QeAqlW&==zaZC|n<
zHnLyUNw$w87&Cj5A_syjmUm=F)f<f3Fxme6;Z&KbI)Au7e~9Qm2l@|ZO=O=%-(>ro
zJS)uP*w={RWOaG7JDq>3PTBdx{`}LvP7iSjikO0@w^ns@3EzO({WeMHz*X|Sn<9Qk
zgvc`7w-&G$ju^CyzcfDzqR|cicVA+FERbQPjF}9k$dgT7mh{{6hvFUm{e-8=^M}O(
zo8{glB?<n0eK;Otk}jic`N~v8;3&T*?j%Gp9_Dbsz!TDsd0Cux_~FsPNDGq?oh0`t
zOkXDhFyVD1+rP^zVi{1LRN1?n_9f#;PF`WkNmY?$8y#Q<RVQMC(hSaE3645i1W>A5
z&>5XXfZ!)fp{~-HWI74$*tL?wzjYb&t_KU!f%`;osNy8r8wdhr|D}dF_#8ZbFP`QJ
zvG8e!!-(S-7e$=L$2v`8>;pJCqfNo?@VWpQC>=2#2P0zkxPL<E3gc%ELKylsBOVFj
zLIj-J%_*Y?-r+niG05RfO>heZdD&z<g8DU&IPy1y0KCt!8GMSXdT)%N$wG<O9Nd(!
zfw;8IQ@jKT813<BLg4Mmw5{R}6g;5_$K}4x$=ZvPeNDhZu-GTb(<$SnCOY_gb^f5y
zy-7jCd(Th`NI7i|DYm2}X?^W%S(W*OYPd)tH22I9_bOKQ-YNoH5$_RoJtRy*V)Q!Q
z$Ml2#0?cs2c{oBy4$?Is{PsI0WH{_{#_GI+;_^`e9<nPHpTVk5^ZSGjYc&~Ln?2Ft
zLf`c&b~#NkiMxGV9`kh1inppxCtsVANZ%!-$Q4OC+Q+&%Tw)4zr2|eua;%T=ZfVEd
zF~uk@j|y0YKDMj#Lqb|N9#HbH>U%ogmml`*hbT^23cyx~BTOGXf1qtJJ7yvn2=w!+
z0m}Xgpb0qkH=jgb5x>*FP~-p`Al)04IUNk|VYS4p0^{NcJWI1zON1FfQOD0{%0lc3
zlc{?AfCxcrYQUQ6IBf4ej)m#kL<CEoiiSN)LI<*I=(x-r7V$f_^5`q%2<$dFS#f2>
z^zx|@bg;bVBbKgMrNa>PTn{H=9~G-Zj4bC%K3r(N#4E>JAUn}>XEICJkBhMT_Ca`j
z??d+3p%g0IOc)~Fv(P#S{t42PnzRoo{cKNYbz(8J*r<xHd>2FY@r1B+GJb!$KkfIY
z6J|i;RC#`fIi5e{Sw`U3P(@k8`h;)V^G&F<p&skSJ&DE0dl0-#Z`Nc(!*U~*yoYmC
z+F!u4jG1IGz>uvD3L1<ERoj~s>FGr0H%jY0I{O}QCKnx7@x}vD^$DK=WHn7&<!wD$
z4y@%9Rn~pv_=>j)?F*B0KA28Xg7gDGR-N@9F~5RAoeAY7y#Ub$@#CF2u^TVyLF^Xr
zny?lBX~9VrmN`m>0!q}$s$^<RW{>fIkK<ui5K(`@FOZ1%nt3-U{N@g|=y1#8XtcQ{
z0Pv8}77gD#4ZMAz_KN6$@fNS>5#&;kR~-<UI>za{93E8jQamQ3S%sc|%Gh0G0z?Lk
z&UzIH^h;w*yeJ9t?6g1eNn(c+Mch^E+hnX($wB0G1BE?e4i5I9r|wth&batJV9SL0
zJynyZr_&(`78ee~zEuQoH@lr}jAA$hHGka2TT9bAWqpO`XUICzcJUrDysFuq)=Ez@
z=HhpCLdF@HF*&PWD~LAiCpdlxMq<ay?d!ZCg5%Y(RTmg_@g4a&v>J+sZ4_)W>Y-+C
z_dO0r-NT)WoA?K0Ga-|}#-byU$rKDQ7WqtNvef*GS9Mj^8QDHeB06e0zBmh`{pb=y
z$O(t>KA{i37z0a8#vsovjc1}zc3v6;Ixg>PD+RkT*nZI+JRjqk7gZRws`s9cDw5iU
z#W7s~F^Te&Wfo-dw6h7hIvPi)a6gi=kaXW&c^_pE8V^~aSVbo3-ZAJ?Kb=2(61`?n
z$<^Vg#0j2^9|Bp~IHmeQdyLE2)2Yd9tlW8dB2d{WxBi=_%IIAW0#67mK1)M)5SO|!
zJOyKkA7CxS_T4%^faLPxU>I(hu^F$3(fE>q3Fim4YQ!@4$-BYtPYhIe)of&l1mDH6
z#J#{ud3I+~L;{l(7ar^x2uLwZn<0<_r)50zaio3P1%L>#jVBY%x0a0pD@PnIU1~nY
z+n5VK_=udw@0x{YDt;l&k9A6b*%zaK|A+tVxi55LKuD=<8w*n{5Yoj?a^QjGPNJ70
zmSUw1Ng|F5!9N5|=&X!4_?8Qo(xSoq29PS=LJmA=%n9~_sSAm(m?CkTzU1tT@4VZL
z@`feb`2$}ik*&<qD<iBzkSKDrr&_sNS2{F&p-6;p7SdRV2ujkq`?{W1T9cDB-og$+
ze0@6nvu`eM6;H@^zFVPxscmeRBc}F1A8|-R1L0q*Y5+spkMQmIgg!*;1y-*J`oP<9
z@VapvwE|z(JN)IThHaqhUWKNCSI8}ADRkZwi#bnW`19Q@(TAzv_F*`NarMNFzu%DS
zneXg*^&F)vR_j8peoo`px2>?EW3DzsWeKu{M!)e?<2Wo^EQ4R2?GumtG7sYp8(xp{
zm9sitDo~Y1M<iCJr(uTgIkL)=4C!cvv2Ru?a3FqJ8Y8?{UgLl|Obo*AepoY|_r>Lh
zb~Mp9{@{uH$Lf@nr&FmHg86O}<R>*@Hi?-xD|O?C%}pbTmtN9L7f4JE@pu~_<6TuB
z;%O~Z*+(yB-?$<GmIt=BGNT%dvqoqG15}Rt>dKwZxW=tJS=Los_hXVnLax<g17P8k
zKVJDRTV-!ZF_yx?IKdLE-&?B)ljjU}+b*%BuoN)HxgG9rON<9$qtKxJr{fO9gr-n&
z+$}+)W6h~btremY*W9T@JR`f!gr4b_%8#BE^2#xX&I$p4OgMCi!+~p%{?XcitdG~)
zMh+**=fr5Rat>rDX8B&Dwgs8NP$5TPO%A;H&%OA~865H!M!UaPS>qv0Y01{H)-VVX
z8tM}956GA34R2U_5(kbbBJrkyJ?fP~VY5P7M*XNX;>0Hc?nvG--#oXHo5rK?*62m}
zDb_nm?nk&MS1*Qb74rpZiLK+Eu4Pj*PEhDi2d&uyidUM)=EK7mpSYmV2oQ%Q?h|`q
zdJxh24lE(}l?19#nEVX#N=e8<Vnr-yB;Sj70n6-j8>J<?cyCyQNJvc)qs`>0(2x~%
z#5Ozqp1+O0hBvEb^KY0?+I;LrZ*BJ+CS7`z$W131ZCq)-wdC68I#wjD^A#O8G?F}j
zK$hwG0}5ra1HXxG_@cR&EfyRsa#K3D8N2AtMYyGNK?qdjM5XVIH>+|+C0Mr-#!nLo
zN(y0?oh@?Hh&Ta4<XIJdkJFD@v+PZK-NsqH3eEWgMqZuhxSaAGnGf|vW@Ly3N20!#
z^RnlqF62*h#3k2+bAY;;YNzsafbBOpm+{J>BW?5sI4azGYF4Z2cTjMFJiGYVkv3id
z?6e?`0bg5i49Tk;_kQ`!BUrRb(io-*N3Ea{WyyCQZ^~&Sle!8KCfCj;>EiNee)QLy
z$C1}b(MOCZdDVtBdbDH>LH?=a?EGOR&LBMkUbgJ#a&p)0%xuQBD}zv}n%PPS!3~K-
z;+YPPOT2QDNe@z8cAL%9RcFoWshRrv$tE52vlhc$$<;yVFUr=vUP{QUlQ#*F9?cF?
z%yjYvft>IzHSwyGAJ^jU;QM{fNZCBN5>7z-)`3vk`IoXBD)L+#!En+$K|xv6D$>9m
zF@IKrDMf-55PY(GC4#U7e$O5}peBnOH4yd=+xry`sa8bTNhtDZ1O{Zkkoc5v=@4S&
z^sktF9KI>{6HmFXKv{Bvu9qc<q*D#{fjJHw4AJ~MMAUYb5zA`1nJ9MWZ$52yNs8cR
z)|Z?#%h6OLJaW_Ug`XffQFnLckd$wE(QJOYI45n93&trcv<S>ve-ZEoi!P;Ivxmfv
zr3APH%{Z+jcR3p@$qN~f@^!21MLtVTeDrB_PdvY)lQSo*t``S|lIPIB_{v|KQ92!t
zh-#J9uvIvJWXc=;Ue-e9%1wj8D{|IujY<=@GVf{MUgn&-{jNqmI`<UgJL>T53z?tt
zowEL?-ia_oc*Mvz<Lw?a(I6pdbmOsG=fZ$@2|}W@%kDX1;8BCGQCL0=S`gQdPkHH(
zdE}|{z#rHzCdCc}J)y~`#ZWWMSje^|3>3iv6I1@4$t$5wGb4-T)bn0DhFAI5LW+;+
zR%wht9llMkJt&ymHudUJdv@%u+P7`~iCTF9%2xG7>1U1o<ZbB^V^eM>OZZTzYxDaw
zT*?7XejClPVs!pt6h%WLk7nY+hi?L;)Y4W|%K(+c*14H7fh681N3x_i#Q_CAjX}KN
z5S1*vth?tn-9z9V=R$&BNE+vm&?3WB8UQ)AI{_qIA{gv>7G1upwXNAu%0k!_l}z_4
zKt^Mb$_<|8;J7w(kj%ptbjB7b_tY>iFjj>@Kze{>tMRgTl0VI(QqV4J$lV}XoQNR(
zzD`pEBZ9xusb23rnZd(Vu0Nl4fh&(F;b~XsW~Mg%98RYr7+)f5l?-8l6s|OtRFhJd
z8Mcz4)xZ?@^9jv-(EnC!o|dkWr5-tK<&|G9++^Se912O>OjuU@ZKsakFPYUlohs%6
zX?l@M@S>ejf44*d!eb_|v^Vk!=_fBnzs6zt<VmKmya~&a!4?QCp4mXoEZoCV@1ys7
zm{H=Q3d{1puO7uBq3Vzg=ROBX^I81vn6Oos$Q|V)XR+|13ktK@7A!VutV4ZbyN6^V
zvJa=1Zl_W&-SWqdV|kmT0Rc1a=u?<DP7|asb8ydsBGx;%H_%v85?if{sxd^v2QyG-
z4PyC@46_<BslaOn&JG6%UI7GO67M+=EhE?8LXP|Fk)peKb6LE+6wfZ4CUBYDi*_~K
zwL2#cke?VvE>J0XK`%XvOC43D4=4JD4r%!vXQRSre|FDpecVl12>dL7GE?vY!dY^;
z7M9N1?Fze{w@}bD*fs*aI{K;sF0Z_tgup%-IF<wLu528zj8cd)%@Xgl%8{J)Rm5+R
zCumYf5o>DM)<|-{F1=fu%Hk~cG6eVsl<(4!$G@eqSb~2-PH4S-CSiGGzQjJQrT%-k
z%u)IYb?!+0P8u8_Z8G1vfLtSnwzEg4-vd&^M!F;TNg}OA8Ifn{w7PNl_00YI;;&k1
z10)3OI3jKK+?+RwIk7dCQViO>@P@ZjgJFKxOFm7@_sa%Cs}TG!vFjVQYS|^dx${+m
z`njvSd<0Gs8SL~iw6!66aOhnrm7?w9LdlU{AIG>bhhrku6i5eHiQKFZf|vfld?4tj
zJb^1;%R~FPk}C2_j!<8Kdr-PwGkj*Ob;y%YP;zvXgnN28j&&wY%v(n~kTw)|c=t)M
zGl~8)xz~T%T5l!~T3+18g%~Ss$v50@Wag-vKTIF;5P}TJigr#jV+Bd-i;(+V$#sm=
zd-mQCMiOx%vJr&Yxr1;a^Xig>G;#tt7YzN{vi8Ytl^*^CX)h^dTs@a`(^Dq&VQ4o<
zUl~5SE97c`z{D`|F6SnB^-2QQ^3STqe_1A;e*&2+zlUVztF2ZhVU5JH2w}L%zL5J~
zZI4gOWn4$Pa_^Kf770dx?xg{ohP?K1QL%dTgYV8>U-^+HPe@y>2$t{~nf*-tBsFu&
zudF~T8K)DqjZC|}%m$nLt}c>I0;b>_2VlZ1i~LAQJ{JJEvapri0>RK2O8nU&*Zv7x
zR$fX(?4hK8>eVYNYnzyAcAL&CO)jd@%5~lTN?OtJFSr0)TI=W&T3}5-;8UcQ;><n&
zbM(FR>;#rt*zX&JB;iE9i*<MTU&-#k_Iopb$Kcm;o@;HMs^cbb<h-0;Yw1s<^;|Q8
zr{9DR>4wJExrmo(i(Z)G(wY}xAX9ismQJ>~!R%$$2JQD)(b<e~JRM8YlTBfbTRP$m
za#pq83e-qo`OrU)r<2pEwygc9ti;CWw%)S&{fZ4OWJ7TBHnBjQ$wNnU9^ekI-oYt{
z?SQ3waPqjGgs*B)<VNO<$z)~^`T4|Z$$p=|<5pSuUIzDI``~PY;iak8K5@M~v8T=K
zo||KlBi!wE`RtH)sKuu*L`FM(UNzCjKMq$l{_JmUCT(D}&zv*tlelAacdJXq<!EWZ
zwqvq#E##b~)sC=!%wD5D!d_F+Y-L-hWk`8xcz`)XvRiE1T5a^!%1ZDR{YPm&+AWpj
zJQhzdbDeS{ostV<&7SO`bRMZmu~;STqCjin*dE@dL)xbsAM`t)-}gCbTCtif8snEU
zkQw%!cF7+~8Iv2Iph?{H+eo@fLGCoPiX|>~I1irn%JK(}LQOW*WEqPsF|iqR&Nh>r
zFwAku5e8}_$xR5_k(fqpY;w&pXx;i~(cVc^qX(j&L*MEJD<aaycKHX5MDbrV6lHr6
z$~jML^$%iETKwWju-uTLZp<b4x~J*7)Lx-m=?bSf<E{fYD=(gD(8?vh@k0uY3z;?k
zoCRmWp+l~n9;@JYP{Jjj*eP2mP4lGPSjJktaH_P?RKjTvdvWxd)nVLA^T5_STtmeN
z!R87I6~sO!cXYq6vm9&Uq}VF%Vas6tKq7P}lO6`P)6{;l@d)CuCv5potr{$5Ym)Of
z4S(NYQ1AHzot>Lj+)c4`4bh}c8XCv<kyi|+OuWGZlDy2}FqkoO?W`hH=EmY!bD+Tr
z@(>dl<!pP`VU)n;c1c<ky=t!~zw!qq@X40}Mtki)%Bz$ICO~t8(c}%c?=MtR^$XZ#
z=NY~A5_n|8b7Gx$v7|L$Xu%NT>3kz@0g$jVm0K#M%te3ArfqAJ0hq{z50Z}D{m=PB
zlAauadH9i~UDF|@ozvX842sGeVJkD@ip?8~^r|r$2&tSsTYyo9H2djZFGxT~ofEDi
zJlTI?P?C)CjpGft;vN$t_+6HIskZ-bnb->3BIA<2rfqVi!!oXDGONDbnerejBp2=i
zc@o~efYhvV|3W%D=|L_FnIDjhM=~`(Ca(D}k5SUgGtJ*s$c7G700+z-tn@pmtt>-O
z%<3UHPyt6p=PEJ8e4&M813H2+3zYPoovCqRL2C~Q$+b<LX_GbkCl;!!CMZ`)SYk(~
zrbx~|ktc^vYjWq?*@5XSjk(j7Ub6=*34;*}lWJezhlvkokym`5pZi8Su5eDu4jq9C
zIfM9nxhDp3QkQ-gqvaUaYT%l9<zR6Jy^Hx9wp$hQt}WcKP)m(1Ik2hE_6)il%OsZL
zH(k|&Y;C9K{MMAGHhCZ7g7Ad<BT25OpGB3+ADpQxKdCJsKZ&ucD|qIv4F<su;jSB=
zBhZNowSA#qM0T`O)9GU7Xr~!d?EkJd63i;l#)1dh<J_NrjJVz-D$YOFbSjh5{eEMj
zHQ0$0+CGb3{s3#_rn*Ve2!?&WIscg!Je+?dIu$xdHo<#!#0kGx;J(IK&-4FV-Q1pk
z%+5b<leLKk{Ge~oKg!t9H1>yV^D=R2>LS|w`#=1jbtV9v|B)vOCzyO0rSu2<l7oto
z7gbb>kcO#~lC~(hFAUZ%&p&=&^AOprCJc(45T5Q&5*DJzBjlTrH(N&Ql#m+b>%Xgs
zbx6`gDLsBHFf5KvCjJfV_;<7zv6RduOTMoO(xG-pq2Y9Wh+qqX5S&vsP-+RHK%CYL
z826Y0kVIDcL$pPQu%s;QwqbY30OVFfg#k_*+KD4Q#hgd}!_WlJz}PrFqYnk5BzSB~
z83c9y@h-uvMq+LG?+6Y!0r46eQ4ss(b+kGE$WxGxgJVeNO@w;g&;5?iM{y%#_yEp+
z00%`lE@ZKhEZppfD#<<M(}qxtc{Ay62mb&889pG}n1!IlTMrOcdSLM(Ad$gY<K)P$
z+cmaZ+S<7OAyR=-(W5+=ZHXCD?ir8jw0r<bs-ZpQT-=Pe6=kJ_5?QJIBRIT^#3Lrs
z#~D#&6jG8Mpd~RUNu@O|91f=J1w#kO-vJi}miYPJtnDr=GFr+$B7(OAz)YDzP7Jt`
zPA3K`mU8sRft?=sPKqVupgSm76?yWCNSi<ik}@HtUXvu!VV5x<>LYm@9FhcI;F({U
zAC8<cWsl}K0s%4KXZHxS+?iQu#P+3Th&@X(I=w=4k%Jq|wY)bON$5M)z6EfFROkV_
zH%>cy6xE;x?zKt0b4gIGb8yxgcQ{1wQVt*t3WyT1L4*!TLDn4a9*Q~9{*_SeoRDpT
zvxWyQ{-k0Ywb;@5Un>kBFJe)K1D44PI*TOgSumn|G3J^=k`8<oEkb$NtI5v)6>^qI
z&JR@Qe_rp5wMXQ4J?P;75*Dg!Ls;~ofb>H8&KB+;TM7AwToqnpn`g{lS)2-5EP5ww
zo5?X$0{Il1M)VMQ1Wen1#Pnni%@lI_cx#zW`}S&?F;ri4kyqA_t0K`uAsvH5#McES
zW0~Z8A&?t(>y_0+iu{(0LM4Q5GDa|N>T(G2xg)7AF#n!ROFHtz7o`Q-@!H2mU*NzI
z@}U?)J#0SJYs>Q?+GzTS0LEjUF^0gVIjaUfmOGuxO{H?)n>;z?zOmw>=St^v!MY<o
zwT%&Ihc|<xg-aLo(kposH-;^<kQKX5$FY!9Ra1{N0b3H=m|jP^BwM%lIkD=1G(7*O
zdkA@9Wed?U=V9%vrfPQKHc3g;Ow^lPsn^A!TmBJekv0I{jAfks$Oo0JJJxZ4aGTum
zx8QL?<f5H|frS14{`Z=^xkaa0(cjtl$A?<r&(Y3>F5;0yjGZn`rVWVDfmR;e4UMmX
zxwU|gK}_D&+Sy8@K!=RAvH*+uh0|tv;d)B9iTx{t0DrtIEU!yYp%M^SquMVnIPmIO
zMPJM8*(k2!rU_@o9nr8)Ei?mb5V1gZdn{7TXBL=^)sM_fR(upjm)}}qj@EO1Bp?jf
zr~xvxBZ2_eKL}aL>46U{)(RZIl3a}-^)Wh2OG#jUAbFmtCDtrQN<@tgXlI@x)rig3
zS6iQ4ex{Z_5p8}I+aQ?&H%m0#H_L3d5)0&5HCyv~e=MR%7hi6m7X3YT1g00!NsYgx
zWS!@@SA)xueoofOaYTeZZphZl7N_jug1GPy|A4xABaYo%CEY^I%w2wg!CP-^s8POZ
zEg38^-e1K*Ke7O1j_1^h70%`rpCg{ZmDpo=Y|<<Sd+X1g$JN0u#k($2LT2hzgMtAh
z`_`Gjm3+QJE)sl>U1CC4hyHoS;ZJM<bI^SJes%s4vcig*alFKzj_)!>uHeRBw1*4M
z^0G5NB7Jm9n_Pr$NJbys6$l5__(tH?l*mGANqs1h5Dnr2Fm={^4hyHe9)EY`f3+QA
z;8;n9veTA2Q&o*kxjCHw^<X}Uo}1SC_k6|Ga#>g8$-gslb3m)EG1}_~x%fz|e@rGa
zyt2gl`vW=;LT08in>W<!D@z-ILrC%Em)(g_>qb|=#W=ak=l{lL4M|bEp+su@M8@@P
zdj9iaC=Gs@sb9D)gT>OoRh^E8X;0@TS~uHw<?yc;d7Vz)Cv<du6V8ykpe?!Hn_2;U
z+{CZ*f2!i6;pHr1^R(RgM_B+@pNY}vZ^IU3hRE)XQ*HJ<u&<i)UV9;3oGE&@4&}YR
zHNbv|H>DER&=s#74))uiP@qRo3Ej~?H}~1rPBr5@9y%H9WmXk7C{pHp2RzfT@fMIj
z$VD<qB~nrdDhpFAIT`HR^PlfHqVp^7b+w{6x-Nw;v+yW_)*MBvR~1f92z$W~Oh@BL
zAg;|3DuL4g;nJZr%Yscxh8JpbBt~5sxmsrLjEr<#F_^&++>1uLxI~Pe?@jwptLVg0
zLUK$U5^hSEgi2jsn5UW&)+6KWaVOI!l?TIOL%zi8TMn#6il{=iR%H+F+7WK)v0*PQ
zTlje$IM&Ur9r6Wbw`L#m-lh3kzIXkn8X6{ClDId5@$oM--BO&pp&l8|wBqSdyZp|w
zlfjzw0!~zE(R!x%8d>Q{hJ#rdtaMpHK5coVw9wBBh+Zd%-NF(H@Ymk7!mS8z8HsOA
zVEl-|VDeydVbBg;i<$tGlB6A95g}M#@r5bedo|M3urMA-G_8-|ul$%vT%{xHLSktv
z@n^*N!t0z=5^y)(I66KAE4|)^>yeW8v*Vv6*%0MTINfbczCgGye1e$VXZv1a^l9|M
zgEfFxG!w412!ZTTAwmTnydsYbnpN3cc1aMxzOuj^F*P9xq306U0)XQ4`d<n<4epMP
z8H#jGN;EFTbHHAWeSjq&IYysFZwT2nsU&2NUCR4MPaAvNFp*3fBjy^#P67(|lFZi6
zjdthC=r&&OO}6oEB@Xer#{H-#K}44$Y9cGd6I>^yl^jK0BV}iS!DDaOo+m^(VK%Me
zYW~i)c$8p`*W}{Kjbwq#fTP&j<gw|k`Df9W*!qk8(`$ha7l_NT(10>;?8USUL^z;q
z!YVdZRgPRsu=E+;HZRr1^O|eu^$uMx<jP$Q|3tzbN6vPXX2I(`9SmZ9$!cPoXau&b
zPU$7664g@Q*1MOHU=xyozPAa(yPV`Hgh+BY|Cua|Poh7t95QUuu9;G5;ihq+AJ(sB
z62Z5~9b)9J!kZ`@Pa(d<J%v|o#X_XhW}Zt9DDxlVNmfC^De1ly{rY)fND!~0Z%s@m
z_7BGm|MY@flgj)?)SA58B5txCY(6@3Oxf4sj=^nJM_erhITK;Hc}B=#Vm*yL^w0ub
z$H58AXczZ<%S|uygfBWLxmN;E9rpQKqF502R$dtC`LoPg?0QU6t{;%-T4BDg&;MEl
zdaEr2AWWr_Mz2@xT0)=}$J*3+WGrdA_4l^T<7L9&vZKzXcw7l$qmAVZnmn5G+ndq)
zcmNfaV*N)@V7c>f1u3o>n>KP5bh$vR-P725(pOxf@GHb~s>=hg;(%)mpJTl{|A=Ro
zo}o62%`NaBo5SsQuaowVn6ehm`}4Tqsd(Q(aTTTJk6{}*7F}04fM;4JSUY?DSl>!M
z5$O!Q?&c_N==r#EBHL^w5RCETR-VG~$=H0>jy@%)x1%s!W`_<)+6ti8ISZM~_LY5R
zI_0d4wgn2R&wqyXa(DibXK+<qY`20Tb0<!Z3U~M+hP)~-%Em$8c)P_NLspHubki<a
ze*S+hlGRs!DxXB^T@V1}K%5Fyah~#@3wM7iJILVvVCSwi82sR+CD3ob)VXYOYS(gM
z^y3}Vupt7r^OLA4J26`PX{oI#*4%mpfjdcb5fZtdyzs32CNnmpZMpeu{D9`^<Vd6`
zg;zgqZQHCHR$XzDMI=_iTq4$T!zEtabJ>|~&-p?4+@-+9rnZ7SiseOcxo4$l-7JPy
z82kp8R>m#rvTVoXzqo@p;-#ojv$a>2K988~_LBIHPLwE~PoqEOD1~U~J7;H&x6~?n
z;FSnslieo;xKqC2?Hxg08qFD!>mVV{6h4pLPt(SkA)R@3Ftod^r3ranySvvMR3epb
z>n2n}Tx{<GGvC}Zj#obIp0s(GZ`^|13B5R|aIm7v=U01%?bj+rQl4qVm4Acg({J$s
zasBLIQCf%v9EG~uUYe|QwINcH+DLf0kCF)#vKBTBS5JEGO(~g@rfkcE1%}GK<_Fk3
zp$+BE;*yNn+NC+7;MlvOufoeqE@)~{_;zguC(NHg*TV_Fir4G&pXKAd@Grz4y=%95
z#S;Ro3ta5EQ)Xou19Rt!#73DcB1?>`3n}mAa5-0$*_6xDq`9qI<@5z3q2_I!PTVt+
zY4%`I^6H#Z+opgoW-#5%r9YV;z$toUT>L}qt|QUIOeeMkj;`}sP|U86FFNfjBHrP~
zte>jt51n53b(1aRJ{btDBwofyU#=xcxvBl^quw34eyrVhvWsE0ox0^1ZYMOgnbR65
zwapR=ZIUp=K#!el_fnXR9XEh93H}$>;dnr9vuR#;p<nTUEVIfqL%!4zi-<q7+<3d?
z&a+)GByT`&?U?ab%^{WXb(%v{wbY;AJtFuzYI>;M?_1qarf*R-6}i(y#bORi#_NUT
zYr02Hy8FhZpm!tvVRg`wsom39#KXcB@^c!9lyK95!DWLqVrXRtNZ#4SEyeY-@ZL5o
zF~_hFPO?dHFcU<MmeH@x5B7#sivpgz(5Y6E|7Hl@(AjuR1Dmh}XA7^(wvj+y6IO8g
zDmmO1+WTqj8e=NCZO$b`^Km3mN_VGD<gviyO7FJ(kwf#QNoQg6E5+}z_i|&PSL==|
zdC$25g|_=(DgaHKjO2TC-8>QkblL{DJ#>=Zvs>rBjzaIZP~&S3CZ7T%{?g%S3tQL^
z>I8m?p`|;}#lf|8L*=hx2BsKntuSZoUX#|1ZpVd&A0{g_Q2dINlJk!n0)+4rpovL<
z9w8=NzsSVB=PjpbhA{m5C~kJ5<60fbRLC^c!Yv3=`s<y&mGukKYFm)@$nkr>&++L`
zBlj$Qi&Xp6S#2TVB^+T=M#V+(mX9uy86^`0Ih*lCFrn9mxN7{KoA`8^*Ba=ePTA{E
zm}*rSLgku(r2WWTguHb&$~aTvfE~$U&PfcE2^W4zQ#ui6Tuq7EEtGvKh@|n*2c<Z8
zt<dlf?^r5}tammycAKIH(8k!@DM`&&k)$PWWbDzADr{iBXE%DSrq{ORp=%|io{S{z
zcui%xXW<i~_7PUQ5a^--N~<yrIYvz4O!_BD)r)+ox1EeOG}`zPYqwn4-aPyz+u%~e
z=-y;dh#b+b%z7u??{O899|_C<dwO(I=$yW{y(F7!LXEXJYTqWbBLB@*0;h-)iAQAM
z6;t^x+W)k6bkQzI?aF=5)=ql+0(pIpkY&crQnj>FslSpAlJIcIJl{xf7@P)auV1-{
zx15kNx!Y9|`$ruBt_GXfzrFBSa8}<qQI~J9)LPydC=GSDHj2YxA5uyvtLMJHCY9ia
zDGFgeG2yDX*w`Pm`GiZVUL(?8)f+P)H<uaa_k2hUgyn=ZZ`-OSY`B%C9l-)Tlv+({
z6bi(Q*Luwfv!-s7@dqO&jChL*xK)p}1tOOYKfzo+PfLb(^nC%*`Mv1L1LlF5i#yQ^
zwbG=zipoP9U_=dDbX;+LWk%+k!C<A5+@}ry+m)Z&D|xLdW|e$>SKoGLk(IX9ch-Ds
zHxLKlHkyo^aWl140j)8zkAodt|K{JLxON^KVz9BFj*#}NIyvNkevv;@Utspty?0#s
zji)46?kKEU-L+(RA2A2yE0Int7+kjfAotTl8HL=dq>)SAqQ#Hgci8!x0+yCW68)Lu
zx-DspZKBMb<HRlENSTdS`97d$<YC|wjO`4>^;;}p`YcgBP4Xg~5Kq*s*qIM2+qc-W
zD*avNhIOc<=Zi%<$FH=9T0KcVM^3ah?sVqGr9&b)R}J(V?r-doI3yyiZ+69A+gFHr
zssY??soCi^Cf44rBu?y%KYI_UzlM}^bv#Q<`D-4UXMFmBqjuO%1u^c?IgrFT``o3^
z{bFM{*wy?(2Y~p$xkcyWjr|3@+frsiu(W4+;QeiD%m%eFHXUX1bS&K?c`X9~IX#5S
zLKzE;|1%X|4s!aF`t+N8UAtT6RZ|;`yfQ^H=PC~HyqKga7Wf+Vg68f@A#b%`4k5!e
zQ~!p0G0!_UUbp$yD%yrB;(5`om)?bLZc3o63p3>AteS?K-G;BeKm4(KKesz3Yfme_
z(Q<Bv-{g7K;e(aWFWSJxcJR@b&;c9}&=~sj#u5p@(zjcjozRl%ED}_X{dmxvD!Ev)
zdt=e{eJSf*5$)`V2bMrXNcJ1V*N*$M=Ob#~jQm$a(hj}mJF>U9a_5z_DNtkV@bj0#
zRcsJG<Hv$yY^G>xr(9r3_TD<Vm_E`>MhOn^^ptRMNp4g@m&LUrVNpu5CNEI|@T|j5
z%ts@F7nf;W9i+B&Z9%z6KV<*h$4)OKr9zHlWbGVOjgH}892;|zp%WQ%QL!UnEtZ=W
z_^1mrCqkOePkt%<`@Gn1)BOF)aYN}uNjr++f`8hA%Dbrut=PF{Zs3b{*I6`JEaLNj
z3#oD@i=lniyAGsnkq56)ebHud<$6~Zdy#BUpnPvbAtvJ${cJInK7DanXdzAmUTmHq
zJ<iI{dp;oVz_xib{<U?R`At@sy9DEdE>1(5<L7R;!RroL4pCoK5Cl<;+apkVhvrxn
z8+ys$74tPi2IYBSopruLb3N>i&%i;!94CM-WURHJFj+U2Byp8=paWu5E8cQ)mh2A}
z4AOJOrhsBbB+f}GOf5gcn%lV|XD^k0+0lY;JkNWe$*{^?t5*Z-p*$IlleE!}5{+yr
zx_aC1Md4DUB}>pg!y`=H#RdPOxc8#0Ja5nzAa;^7OZ@%FV~9o$-@MU+-?*pQ;pW`5
zE8QSZQ&$BWZH?a}vjy2Mx^0@<GLPJ<bh7O))^cmvD8NA9CVa}^bAH-YmB=f>T^XV(
zPhr||K|~#`o5h9>*2)*P?ilhF)%nNxJ}KpR5glB=cAhwBwN?wlP%fA~Uho_54Usk~
z=Ei$D7^`{654|_q3V#*(iU&qJCbm`Fsp0%zV}~Z;?lhzNvEN&9=O5seg=OW36)n%y
zneDbDDsMe7D8b4(ZEUyD5W;T_XJS~pj-L;dF+ML8hMeXTqN7!D>c~$F<fQX-hkyZT
zusBWO`LF!%flmsBL~bNfb7jKF6+;ET95YZS<BaMRN?nofGq{@(uU$jO^es!CXv7)1
zlArqs3%DJvCmU&9jomo>Lh1I)V{@+N%n+165d?DGkOQ3Go4fPBtrPlp+)7_;J6Cav
zS%T+(irg&0O-wJ7Kq4k!o`0ZocK#PEi6PQRu8iKALry2+fEyM5R_4By6D6~Xe|gVS
zr=gqBNbZK6<?~<Ysi7+dLq0$p+4}`~my~_ZJ{kVRQ@-51z&x^O$C{2HuY4!3$m7ft
zShQrjj!txpS%IdAH}P^80&9~Ld3i&p;eL`y4^atn#!Y%#q89`jjDl6YiE+HhEWM}w
zc=VV+JcDfwgAnjo5V80F9l;3vvO6CzM@B_v)@IYt8$;lTb7JsK0kq->BjKdNnPe}F
zi2Sipce2vTP;!%KOzw$WjceDu#!o+>0TTa#A?`yZ-XKCDqX9L#G&tSxn!$iA29GCG
zjLBRwh$avjaTc<i-p8JjiOai@(ccrCTO9z%!~f2IA*&akp<fc#WIxa*n7f+TVHL$Z
zQ7~5!u!g?8B_@PTLewcuElEf9AtBnBp(anWhyN*K0UbK;Bq|RvuRleDynnCKb&M%p
zblx5G$D9NbaPYy`7akYcPR5~ph6{a71Nfeg6YU%i0VH7h;jv+8+8$73492Tw|K%=5
z+WGLbw1Pzt9nb#*b*}kMoZjaXG@J_gLK{punob6RT>OF`@#XWZ(vkj|#rAx%rds(8
z|E=~iB8F6zjlmxh)OD(C4jzpHyg-JIE9{9}?YA}0e!qi~%8?VAUclQMpPe`6Z(4Z{
zRS(dqir&!?#AJ8U!qSx$Gl{ubCgH~$a)ADT*g={(=zz@Lb)B*zicE_fKvRtkVa_dQ
z*hgKK)w&6y5SikTWJMI;=EVkd8Y)o0mY93CD|qH#1%Wy6L3W=Erv1T?A!JaaP5)QL
zh1td&X(y?IF-r3L5tK}%c=chRxfv;rCL$kt+g<T{+d5+!iYaCf>f<N>2@azS`;F*z
z+i4f6*F9AF4U{Px2pB6uv~l8hNIlLR{%18jLnD?sTszwFyExlT9=b~s9#OMVkuX#A
z!g-A`TO0f3g=YM<5F{wc^ggthX*P!OyLv-w4B|GRc4D~0Y@YdFfBZN<aPqWvVavB+
z{K8U2rumv|1NHNd{_$&{x63{0m5afH{H#bcI>|35qssYFLk^TD;W^3bFZU*~1NESs
za?d-0O_uIrr+|7TmTjF2(@d9<yIk^JQYbr5y@3)dw&)6L|7=8Q!17+lfwE)faJ{uC
zstz18RAC`&SgaC-_X4$XO+90*o<iIZ>QTV9R?>QAruz9GN5BmnsAq|b1(zUcB8{h+
zoZ`uFbQ#Q~G{y%-gZ9FG%>=!#`JKW-HIrEe&HQ7|_eipKgY@O{3(d>BL?e)cuE3yK
zd4bt@J@lXCr)#L*Wt(348#MFIN?yq`Zm~#5;F86maeQW9@=pLSN#1`dl32K&lo}!x
z1g&bld|c#Wv>oD|d8vJs66-NF-yx+gs+8xi%@(m&Pq2eUTF8kO5M~I4`^z;<#P;kD
zvF%fpmFgAA>WdDrlYpD&d*({L86l`@Y#sOl9A|u**>&HxnBhncurNh&$C~zf{WoXb
z1qRl=bipqrV!)(2W|qG9SRRP;RZFB&!hD!Z_rPb4)-s2qA>(YRnRHzQq;}5+rpdnF
zB-85BT;S8c%m9Mqk0+i)SzruZ7pqNjK<^kb>p5mK8=cPk19-$F4f2f$M{)($2|v8#
z=s9;A@tUL#OnMI1i%U6t4}l`2zPN%6qT>*|7o?<v&mIED`QUhtd;bWT+O-j$mMaDS
z8;#!-{rf-s=P2W&N`$kjgMZ5eED-BNbUWw3+O{By>OeV-P1$*J`6tm!1XlD8Q{^mN
zHQ2gFIwt_9DmgL-O3+e$Pq~-@v>Ye!)LbqBc~k{0KW^?DM-{MKev2G9{dTbFW>?^G
zb324%%eu9QCh6X$<}hUMEH!G*#xN~R)%h<haXGj^#(RvU<A`s!ltZo_Iyc>BtL-j&
z{G$cF@mAtt7TU+noqJi4{ld<^Vm3qX8hKYPdMxc|Pu6*Xl&=Ht=s3Y<&zt+b#~>S@
zi%Pi(n`XT>lX+{Pp1>{xr<~(&SC5+uh(h^0ErAN2H`j`KPVDlWS#xq_7?Cmem(4_!
zud~k=FJp7ru4NWjbiN#UqN1wgbsL-4bp0T;=fhrvtT&8Kub!KnE7$lcFY?3rFWGcx
zNT_UMk<G2IY2)DHL@tcJk-Xt(%y)SKHA3bWdS~d>|3=|zyC^Fe`;s8G?ZCm5IGzEb
z5jcA>_f%8jR3h=)7Q;=S+7Gc#yV9+78v()-KIUF7teF(Z9COrpiZO9LTkNiS0G#?^
z>AdsVyR51Emwti)aSek=3c&fFIgesCHhBw&hVj_5zyVcMBQY2HKeqg!IK7IN?v#$)
zv&2wm5r5mBW=PzH&}inwDFwZ_-&GPdWZ@o3HI4bBhsBAY|L<Ji2<x;J{yy@ObJ1SU
zS~wi-UJWxfC$3R2JV`1aDvV)4AW!s*JDUOphfkicigE0|RMd%Eny)804Mb7q`y==S
z>G|L8Ncd=r6i?yKi;T?}_Qv->kn)YQ_URpQO}d+QmaUubzs#l7j3$21DfGxdlPhfY
z2>h%8qt7lh+70yiG<wcKpY#8y(ETUZFH9Fy^L2w>!?Ic@%S}@u`WED*g4<-1e?|`J
z(O`y~UWGPNxDm~d9_04gXNOO}5<Z#8{&m;%gKR~=K(^`)4{>X38L0=5gX>Rl)1%CO
z)jBEp2b|r!GP2+jL)_S6{#2fW8V=t=-57f%<H7@ltff8+UynZU#_{B~*jJmK&9(;o
zLIc~p+t9|i9;(sf2u9lyXLYDKqmpIk!t$}rRYrgz-624Ah^4?^O?WWr`7f|-G`i@T
z;|`^d+Mxj8>+dBvmZbTGbD)B<C#KTah*oZXZ-bzChj@xb&-tGZw+SLUT;um(#Hh4$
z+GGVxYBMN5kn6Wh13wn)LwqzGe=8i{@QX60&5HD=oY1D*GdbGpS=ruCf|Ns5c1T+i
z7pv$iRAW4=YDxNBMK6(DnH0YfT6>o>ByGO07o5;$bbr-_bslWUbT;28J&Y_RinK!p
z8BxaB&xD)hHPVvrVxOay8_xE+?a($d?_cs+$hIuJ<H({<fcCZH*{mE#xo;(5?7WaD
zJe{2Y%-bA{9so&IL#EVjl^#~rP%o}xr2QeM5#7}U!)3zS;)B@+`O%UgpG}6VxqX20
zi;rO&WAaC${W!j#M}X^xuMK?;%Y}r+^hriCPOFyXTC$qyusN)II>$S%v3r8KYvEiR
zisEui%wK$j5P!tXwONcli!uxI`6Fp`?X<Oia7@P;9wvpgpjwH-GO39PYXv`&Ap=gp
z^^?^?`9B=BCHOyXT>Axf_UU+kCRG;Y{p%>y>urThU~7D>uXsSzgMu~aZt)a0lK|U0
zg8^ITzf{EC+!XJwP8sjm&DSy<xU;q8nzpz#$f$NzebZhQ454l!@yg2=GZOCRAPR6n
zLldn^)xshKQx3R~0Yth1nE<`fLS|b`x3V+XDqDOK^999S!rSFxNn7?w)Wi>5lM~P2
ziz~?>T6qMxh-=c1GNeX+mS}Jqa1}CR%37^XvbW2`ke^1+9awX26=gYZ|MQXkZw*%i
z12oaXrx>ngit}GeW=S}W4C<VC?8O>5f)?eKL^KJ#WMelrL*jMXL6JKpq87&4K_JB=
z#;9T65*?sMP<`u2IF4I;-%?(LN2kTCjN-$smRoocTpXPucXuO<`N9L!TJ+V?bPZ2F
zOs7^%ZdqLV%W61|@m@uhnyk52;u}e3=Og|vd1vnynvo`#NsR8dI251Ke{fu?^S{CA
zn~uA-*BB5ig}-KV@O<gQBLogAWgJgD(Ihl~Q{t$h!veeO5kya=8-FI*x&P=BNd{Oo
zg4sL4+|T%8@Y!%S^t{1mwgS@pfc`z29Maj8kYbhIh5F{5`FpL!Qcama9J=Ax4m@ig
z?3jzL`K!GMEFhPA*Y%IMca&F6D7RI*!hI*&{1IQ2i}zYs69dlFxI%PwtfbMUx^v$)
z#G-GJD^!<U4QMY&kUW;VF=vyPXtt(l#S@<R4qc{0Y3i?LoN7nhvWkQ2{eq{NX;D>B
zz3;$Py{pXPZL9{0Qdhme1&lJ&v=#kIAf%cw3XZ8coVW2)VA^XvZhYAs;^{8S1Tzq_
zE}MF+W_%g$j6LoM0yA`MnKa)393fzT0rMTluRd7LY#7tyOIHly?soYT3ydt&<EeKY
zi=9yVjV?KPNcrwc+DWWjbWi7&*^8{UY|`s>WT`AZy3EWu06F)4u$$wLEJKo)XpaS^
zlu2ImCii^5Nn6RL_YU?v=vEO+ex@lti=-EnEoIaw&Lf79*}KVE?N2OYwDPX3{QETr
z3FN%2^ePZn0juaWpBx=VR^`80U=~>?7SIQ`<Xu~c{Zf2uWMWdzq2cZb>1?}rxVy~s
z9J1$jt)S4f{Vs{VI+M055}4Cl;bBNZ=Z*!CNr16Q9o*T5CytR_qgyUK*WTW>+;hgw
z6{pcF&c{w1L);A2;uAD{sqTV>zzU@Uj~bKv>?W6`bXENRp_5{en7=sK#%9)3F&Au;
z7KRU<41s?76AUcE*|g&p;LIMR+9WW`47|ulv2R<(WU%P6wC>uXGE7V@SUXDW;M|sr
zDx$|v5{t`E`ANIi@vSK)5=)+?cgUoWgcpQ5H3Vlv-j_LUlFb)iIN80*{L0y3qm4!;
z3qD&_n6@d|`JWK&;e(mP+QCQ?MLKL>ngf$#gQ2lWwm~N_%|=19XTMX-CKg|XbEV}d
zNyj$?Br$`5j@e;lI~KV5SI{=E5v$P%@uo}FUh_lyIZ2lh?QkGwhNOgCb`Oz0(7g>p
zJPL7Hi|u!zg$G`f2`u!#*ghs38#Qg-FIyx|nkiqg&=TebGI-FSTKZFCJ4wqYoP}&Q
z`Eql<LWmOB&!iQy_JYj*CH|@jUPG3mFMeEJSSfRQorI33n!BO1+k>=M<O;MRk$xeq
z(-Jr6MF*4a_?Hd!S2EtqJgg#ViLK&LioB$daAkX@*wi)~VqbEe*CfGO{QgLC73P4t
zIV^|dJD^Cy|28J_aEHt|U145VF2xivd;44?FOeb4=Q0m*uXtK=Hdo*2oy6Qf_<jkB
z1T96rbp!&`HxmP0UK6RD^Ln&6k)t<42dP!uNWoow@bK56Tr4sDUXxEUnrpm6=A;&a
z47g8N?X22b$d2S80T|nI8r;LKq%@UpW;doXmFO&|d-&$fW3w=|G1ev1U#^+I1+upe
zIcF<s9}{h(rYF}}#efXO#IytRv1=o_^1@o4EN!>HlD2I>Pmj$8s&*wqqqA1R+kOC&
z$8FKZCF@)UF~yul+>G0@Y4(>nqf(aa?WGEoA({6iojX<8+1XmcZ5*fb05e{*F==xJ
zH*6a}7`2}ytb&YAb{p^D?cC)&H>FUHCe~Huz=lAx`bX{SX?69=cKEdN%HKSmqE(hT
z{*mb~>}j>B0lo-i&yZC?(zDsi56>DrzLV(7J6##lHjn*Ao*fB*k)Avz%ii~a%hzbN
z##CKqJXRxG=9z6A%t)+9-f7FmCFvLf7bB+wOj+h>vL+9#SXlvD+>}Nd#1~pp58f!e
zQCC{lKFPaJ(Ge6ZN6LWYQ0^vP1q{5hwpM&dSi`z@0nNNC`K=yT-PaBQg{<vJbO;?D
zG3+Y$8n-kNz;IqaG_62ewyJH&<9FujsKBP+Rjm1zzG@_hYeLuR17Z4m9JS8FN9lFC
zapSELo(F}7eZ5lIpy5vvB$O9zbK2?V>8o5{qH;2dCuJH#%5x-|lpI)xpog7UwT_2b
zwckv<dSI1H$MQP>#X7%AFRani<T9kxja{@`{TP3N)*myjF;PDxxr~{+Tt=yyaRnx}
zro_cKR5eF&L2HxM$yZ}Rrll=tNkDUsguv3Q;#=4dn-;Wmrd)a#2-6r=Hb?<X*NEHR
z#}~IJU1i|n5w$|lm&E1cW6Nx$b_h*oS53yAjo6enWaA(3%b?9M-asTSI-|;7m(0+4
zZ8^~Nl4%{LjZCFy@5Q>HE4%xp^n|@*kZn<xg`2i*+qP}nwr$(C?VGl3<EG7<w)5S3
z-5pU?ud832i2dut`mti}vBsWQA0Jz<b)BD1d17Bu0rc+DbXDU62!{)9k{y8KjB*Dz
z8!NXQgNM!UIObl4Uz2Y1O9Xi@2IWt27W(N4Ko{N7%yIqeDSh19?tC8mF2^!e73Wc`
zwp*+Z6)ahocWp6+7Y<%o593v7_fE_ej|jR-O_bwZ!mio-qZC^jw&xAXvT>w44oJ-~
z7tZU6WHjREyV$Cj?Wk>sCEdrKMJbMiAF&G!O7F~VWLn4_S;+_FkV{19`wgLEvYvV6
z`Z{)6S`JAp+ul%)A1kIW^k!=5J^bodI8wP(rp16;hSK`SmP($97Flu9j4MS_8ASzG
z^O>3KQWw(l>Y{AW78}M0`p<)F6D9!an~D`0d@OuIiMw4lmhcV|@VxSZXe-?diu!BV
zo0<XpQ@T51m=4hsO~o>WJ&fa-+`o_CU)7HFUJwioRA!5duamo3Ii);;#l<^@7QjvW
zNBPaXQdDtooyZ`a2%_5Bb*1tU8qJss2Bv1C8gaw=+<_(`Ng662Qt<(iXZH{l<q|g#
z70rGdXxnfsciMR&Vz4(*N{G3*_cELX|8kj(csh0h_U}W88OAvE=bl7C<kxWH<e9{}
z5`|WYOqlDq>GQKu`PG7fz#<IkUQJ!Dl@H#)($l-6r`qunncBtCJ&EvS>zs$C8rxj?
z4*LCq?|=6L{10%J*I{n=j1>UDD+17ebM61);Q+=(PyYp+1@k}PEL&3-3wslKR}W|a
zK#+g@^Z$LQs=xw(S0u?;l~gNPHUH(gDM$l@pa4Mp{SmbN`InV2|7|5>C(FO^OH0H5
zh>3$KP_ioi?`31vWaAInV0z#gegwxWL5scsds=#20?{bYytN+-Bw}bq(sX=H$Y|ep
zKPc8C&6(X!m@ue`-X!?=E;b*M5q|FR3EfsN{gAo>otn8Oh!Z&}e3LF}YLvmnyS`i&
z6c!ia*1_h`^v4%8-)O*4<x@l(bJgjtMlOx$g-{GjDt`ZM`QW{N<b*_()cK0W5mB!h
z;O~(=IOXRbvVdVkw|_WZiYxwU>l62(nDCO4bOSUjEhOff!P?L-+br6tgCL83f}mx@
zq)d$JOecF?vHDzyV%S9;A2auEe)JXN(EQt+z@><vQ%JGGG3uapZTN*QCQ%dp=tl|~
zr+2#m?S-owvFa}5Njz$Cmw3g`p&?!-MvXqJ0IdsF(yn(mxAVJ+6*RW5TA=o)MWpPY
z-E&I}v695K9*$yF$p5Nx6el9XR*0KLbUFkvuPmWL;^8k2S#Y(m-9~&Z#`P95;6SX)
ztArr);wY8{4Z}i3k9a_Q9ATYE)jj~^Q@)4P+>UUBF-%Y<&yfdUnfj%^=-FqEEaQ(X
zTOdy;i3W?*r*-Vc*(yxU21G05#C?2`x+G2nkCbccBU9@2g+jN60@V=DY)Chn)|<AR
zy+vo7XD=PH>vR~2J&Wd0?`2xX)nC`YH{LnKaMt4c`HK65=RixrTydA!{t2d;ERmO!
zL8Ekx49x6<BQ~lcjC|qX!1k2gKuE}zJWE;>NX7j8*g$r{N5T><OyAS2=uQQ^Mqrk1
zah<8<-iFob(kve88fc*NZ13w=(<cza8%W5<^(uW|b&%>2|9icrJS?bCpnB!^a)4<m
zTxVAVPHGt!KaZ|DADdH?t7HMxpMEeEvVPk|yr`LwD~udyddUzVy63a@%08nanS~BY
z-7d&o^D;uAZooS@uvzjcm}`dzcEjm5O`|Nq*!7ZIjqbcOM*R1^;{%Gt-4U^>!v{-s
z!0mlXP8ipG>C2=g#7a8LjwqYnZuAC@LE^yhCTsfO<p>v3?c7abc8A$x-@Hb}DF;}Z
zsJ8w_pGBLr`Y4*9Ug?HsCxb5F9~Q(o9|~Rl@ZJd$C#untG_Bk4g1>aW=cq^8wO1xG
z-oIoBUHj5jRGQV9Z3#7V1fa!oTCcT)-x?ZIl5ACVR5ni#utzwH%XNV<wXh<*&9Yk)
zTDg%=FHHB0p%&bFnb9Jw#~M`{M3>-dR;<;?bG(DZr%Veb*CyA-SI9%1*Sl~wUW(~y
zXm3ri1M<xEp^kpPnk_2|*9gA3=vnKt@^w||(oSG{ZQo?1>9!mD4i^qVwJxHqvDeWr
z2<&a)1dGiY^U+=y_BzV21<umTCb{h#sUN!!_->V)mMO{YQ&L?WRu#Tx+g?7Ic&U9m
z1~YAT&z5yF?chJi9`n}IgfrT%9+vdy<o`?1^58S_3I3`QAnZSr0IB{>hS2|AhCGdJ
zOr8Iu2oe0Z2>nCjuC%1%H`x$+(a-!fE;(Vmt{bxPlu85=h3Q4%nnk9Dm5PLvcG?Ah
zyu-bekn$UIF2SH_>RUN-*u@_lKc7zXudlD0q(>vVf1a+ZzoFn!RAc&I{Els3zGVBT
zG?itd4~^-Zi1yy-hk|p)W#+XM^)S1q%YjK%OP23{&U<%Zqg<jryRg?@1u#|7RiN|O
zGmCzVW<Xkez}3*6cEMU_YqPa82$s!k6`DsdX`4C`S<@leV6e^9D$<Nje!Bs#x$Fg%
zAZa8X7+qgVGX3665h1uQB@0TTB1WsqGITvE645XrhcGF_GAssGwp7$a$KXXaTmoR{
zRAtMY2~_kfQf<(n@f1ZxuMcoYCDsbcG?!&l^lfZE1Li|8!vV<8A5D1lo|z}%a-Ojw
zKss_32BnlNB{^6LG*0|g>)Pc%vaXZ+d_+>*D2r&`t(HS#E}QMqtR#ZtC`KgIb-+|Z
z0Jn3tw2b<*axw>Nw@nKH_6va$F|85tcVdBZV-1I_b%e@mzgGO%$#PV-;JTvgC7Ioi
zrqj)~3Xl>rg9^&%o_2e?l)Ox5*?0>BR0N!fOVR?H8sObjw|wH-6)cnnUK9)B_H{tQ
z$b@9#ydCVwxKmjY5cBm51QdR^Mk1XY^M0H$mBgqt#~9}XKhgwtV&a)Im-p3$Sassx
zwu4vT-zrD<0oBZU%e>o?w@6Eq4IG)D>}IfU(heRs%C-UyL-w&Y)yMfbNfqU6k^CcR
zfvK9jD>uXo;)h?y^U_WEJ2qzmB|zv#5QT0I0`%&!8dh#+vVQuj{p*F0hng>7_Z|$u
zKO-GBHTcrH-G;XMWg8yuIG&{}pj=9Tbr&NbshHL?O1XA#G8n&HGtvO-L!|*DN!8Gl
z^rRne@p!w15lBJcgY2-O(qw1cU`@%Bc!gFJ)VB8$R%0&E2v}36mCTZ_<rYivk|LOC
z2y`G8Pxw4)mMf)vq&y~bWOI`!1ew<t51^W$&y3*H>$GJ{qlqh_bX>5WRwC(e4=eoY
zMRo8%a2N&epd?_%piyy{A<tbxe!UgN2qXHDkk10(3XxeHGB`gS9zm<hS(@wKx@6WO
z`jl|~Zb)IZcWwX@OLb9h^HddnfRGLo8ycHHw&t-?`LrOo*f<m{P&BHUU!tVJa^~Xf
z4w`Yh^A4Dy?zTL3jorMOEEOG}GzQL#iK=x~7x{e^MphmQPv41j#@SXxK-mZmI+@Ly
zf2TE^`Dyf_luh_-w$JTa52SOh5yaQ*REr9<Rz5dvY+BAB5~+q+n_0^2eLm9^TS%fw
z?BbrDRy5bT5XZvZi`%C8X#BiitACLNy)rT3xoSaK9p_F{nS`=^%rvu)&%5Xej<cQo
z;@Zir!!@!d%cgJ^y&;XQcB<XPtJt%l`)l0}>QPBuCy%RZQ+qp0407wMlVx`L?<Gma
zAhz8Eu}3|}W-L)ptJDh|r#H^%SShJqkXXS%Pttv7C+rgz9L;ONQOUzv3yumNEK+bz
zUZPXqFujCYY{pH88E&J`X2jaclb3qd85=u&k)SJN)sB8$fTr0#by<5^F?IO|S;hp!
zU#)>o$}P=-*UZ7EzmkdQiQ)l|0C}#%4<A;rpj89Cryr@Xs^k&Jd-5^&!H#-w!S`RY
z3~C@R1|bZ9#2O_Vj=_+7z302oyT=Od1E|Sl^1vnz5j|0uV#f~ENd~6?Z+<B^QkR?H
zLG(eUm%|Qr5;3!ML*z4>zMm>20yp_4de#^Bq6*0)b#p7pGkb#%=aD!NJISXsfDVvH
z{*F3Y3TlEcicj-|Hi^eR<2OFtfY#dO*&JKt8`EQo&)27S?<I2dKiNiz#BN~Nby_2G
zM94X3w<bo1_>3ZaE;+w&U!-)tjGRG6j~5@!XPapuXH$j}39>Q1326Z3RK8E)y2<0X
zx@EQu-i(K>@543mBP8%p1AW&fo<{Ho5&)@Gf9ZeN4Bjt{qlv4+g@9iHh>h*Bz({m6
z8Zr?e5e3}m8+h9rBM#vuZV7B_1JV~3inkEXdd<1nA>}Xz&*3FnU&b1mkXR9)zc}GZ
zBM0s+D^UOS$?5i#HHK}f!qFwp^SV+Q2H$gyL`r_ds@kZoO3@j#FTDvk19-yxer4{D
z2g-TDO~r}Z^DJH%tzLAzVojh=UckD%fjnEcF`o^a;T!afPvbqaVO(&DT<@B2dD>wa
zaB1A(>2T?KEeC9z9y8<6_%W}SG+_Svf&UK!PpJb#5Df+ZpwII^=iNVSIb+Me8hH4B
zJMT<P|5p!huO|DyczD@=J3NX1zl+%z8kyQS)BXRtd82=F^Py_ePT1@S+aD+twUGD(
z-0O|Xl;V-Zst2Y}IFHi>V8Al_!eTPVH0!T0dY)s^$E*yWF(OpdNe0FIH$B&*yY?aN
zg?%#bO^{@Y3>PQhj?US}gL5e1UJ}=4sxZ1x^3YT8qq@yGw%y*`NHAFx+C)8SGXyJQ
znANLkuiwC$8x-jhTh$CD7F^{twZmiUS{|~3uaQAgX2J);7~>sBGBG4Ig>gB*U+a-P
zQ8p0ZcB>_8V_DB7cW(MzS6RLU$Rc&otT&V-j&}Iw9CM2uQHn3S8x^gr?v$PV+{1?B
zQL_DhT4Wu~6Y2tL(MCr5x1r66p$bWWlN1ZjOP}N5>ZB3_v+{1?A&UbmEN9|yBOQhh
zq+rpR;w531y`fV|vdZ?@C-H)Czc}wan2;GW9f#NHeubzpe#6^o!{La8<s&#Rk^8I|
z2|XGZO<)%k!6EjvMCzGTkP&~eyd^aLeYe;#_m?1ds}q?&`Gz8lt@%;l(HBk~0-bVr
zdt(SGnm=wNR1qZHjOwZO4n^*>nxSkXSt!QtorKggT>+}dd!MA`xS`~1U;&q4Luol>
z!D;kNR*In}yuwnK$=CwPj<EpzCF+Z>zOCT_MvRxZuPa2*jIftcASZ%I?k3`skIlCI
zYb8F9z;22HD>o6%F^9W2#}AR^#E~XlUj^DyfTReWuj!LQT$m&+ERtTWnz<ZGie7<g
z6isuYJgh62WvEq&B@O}12e}8Rq(@oVcnYDBfHjD8O&SF)_c+HTaF=k81)<2#Rot5f
zwlbjybXLRFy;PPw^Nr&YfBWkrb36-jlaS+8Wd`U74g9<?Ds7mqK?;0Ng6y@9y^tLP
z@TeXL9Wu+Hr|hmm1Jl(En@3~U!W#o#VlWpWE|h^<x<g(tlRJ^(!NO<a`LYoEyHL-C
z4OqWgA6UkiS<y;G-gA&d%fSt5RIIFUw@51%+G_`W)41mBiK|$5a*c<miY6mkrlFxw
zwV7M3<7M?Q#pHoN+Twn6;XLnV12#YI3;kjonkl5sDpyCg?YW{#NFX^G(7N+O$PZrg
zlnA)13sO*eqXnkE?un@U!$9KFjm87ILXt^=cP7?FgG@nN(AnV}N0TC;t7&cPCLAPx
zIplN!pqg}A-UjCrBw7Ld{P)&Q^rMVqd{q4;ZTzs+_ba6s{gb6s4*`=uY8W(;oeI|q
zr4P+HbSr_@;HG@^$687NP$YW>RGGATpj)_8jN`p9XL?Z;k6n|9%Xcb^Evony#t<W0
zX0{%Z4ny}}`r8}9EW!D|ej)UR_lB;<^}IiPYn$*}*MV{0mV}!3v?ASjN@2^mS2cQ$
zO-doO2Gx;Ew9)$LLPn1SsA8I4Hl(@u#@xMu!<4zM@N@U5fB5HKi0g@6X2;Y~we#Vl
z+0J!ic-#6?eUT8-avry^Hh>$UKU2*0yH?t&lAA+%;8<NNa3GIASP!2lR2WPrcG>>K
zh6^9q>f@QKvzaeUe412X(VaW;xw3fpxu6kAZp}2K4VmXmd8_Kxda%q6R!;Oax;uHc
z<^bh!0-rzhk;1S&M4Zkj00o=$9j0m@Yb^P&l7N*oW?+l&v!L0Jz4L+b#31eryHoTB
zTEA8+&ZV^CfR4pJjRBdX-QM46ZQbgf29BQfy`9eZ|3jC1=3O^8{(grb!~Bmf|05mp
z+3~OG5W@c~rT_OAiEqh&rA7Xs*ezN!PFwAWy&sece6K7n*BujSNluM%sMbAo8`vB+
zP71<7IsiDLQpagy;|p_p$@ULMo3OXw1Ou7-7RsemlAo53H*5O9pD)y-diMFPq-Skn
z8Ay6RnLXc6minz((zLDI!1qt1-W0$+szr=NY0rv)riB}2fR)%DXdUyLxb@lJx}%#p
zrmr6--$UhM<Tte`N5mPrvFW>Bjk|W9L&}O!4=F5Fvm3RDb2(^ITVH~GFNeV|k9#{1
zv;r-S^K)uXtV-ly+mI7EU)ZZ^m%lvR-9OW?bMgDGL>j;a)%Jzsf&PMc72*k+Qm73w
zDMI#1>jn7%vv}JsUx`6e@%=AR#$l!R6{vkMey2+Xdy=)_3tAX}@*EJA3a(RWA7_=R
z%GTC8^A%{rj_zaf24%G}8ONTIbUy}2>sR>xqU`|^>f|89c609+y?vo&C%AnHR_w37
z4!T?&^8fiJ^z1hsM!U_Iq4<q$fL{_Qr1|7J$N-D7$y+L=kmXa6g+$fZKcbAS*eDLy
z<&;FzjcDE&!or)67wtsm=@^Yi5b4=t&l<_hFmc|uQk!%;%rGA%izYS}fCeh|gBvD*
zVOv0R^`tL=+jq*TrDHU*M~cnZofWkDtm{@$yZL1L>|M#QvZjg)jq-(gSjNtVt6YwC
z0#+AOWu{~84a{5s0Lz{5kTX(akXN2LPd2X{Gr)&T&rf^e$VF}55Z3@?ewT6D2erhc
z29i>-@HyOB3KP40rCHl!;X7cS%0}C{mT=RR(jm3NN0qLA@phnN+s&pH1FyGHU_p^b
zM)AEz2OZHHm(`3~Au?c3Yb6PFR+45pqe^BX*!aDWWv-xe(lS|N2SIB8yZkOQLZ_~k
z8|0zZ5|u=D0=8F&6w`)L(m_&N;5w0)FX-U<4)X(nGC)_(#H}#HMmN1SmWecAlJh{{
ztXNXXpUZFUs29YP&&FK|BODw<??pz$0Iakh#Y5@>tn)0P0zp<`hnqo401Np}d#bjH
z@%s!(Bpu{WmuR`I?fci#4xb;h+Aq0Vx3PvNMfx_q*ht%rW)!b*IXQv*Wl{)85twR1
zfmZfQJ0BvVs;UL_79z!>!DSwpMm{)qg$Ve#h5opC43Zph<#(0Ag%9Dyfxh{DATIJk
zi09s}k?T=yX{|@i<I{}-seCz~=|)mP<NNvSwrI<PJlD!ae%zDsMeXjHkaPWxh94SC
zR*-IgpVgsRko2h<=z4M!)d*i5-GFosvAlsSfostALwcfL{RI9!0P$WJS#*QHL`nQh
z0dq&2@7FZM2=&K-h~9!0QO}N|^#m#+&Y*86%4Y>n-Vfla8z$G>G21>_tE7=WaTfSP
z9hIRTGjFQmu8~_>i($YY)uAxeIS)(YrU8vB>!mPS>F<n2dWizJ7}m@ZvHbqt*rn=L
z)L`S95+f{rKEv^ca|r8$7=zb1@V9s5v=+ID#NcSPJcyJNv=SNN0-oz9*~_-@HcYVI
z!DRd7wFX!ENrM`jb>~9D-`1Q;0Gm(sY&2UO<-;1@+2(8jSBbV+2)JNGj+xP*21C3l
zO9Xj_el?(qs<0p$Vk0Ia*|<V%FvFdTQ#Q8z+J;rYSsJ%9ts^--uy7N|WHjX68EKL9
z%2kwI_m;3*l}^ZTvJAh*ycv4>`SpQal|Sy?q~_QHw0AFr7O}cEN+E&>miCz$sJO@T
z1&ui~I;%!BlfX=^({XOly&W4|Q($FfUyHPB=eW9v;@?_Ws_AH8c8;$lE=@rVF&kwA
zM(07oYA!v80D$`@ydKjOM^B)v0zcDL2C)`07AR%)8~}zK!i_oxvKj^6&ELEA`kO+L
zJY&=mkY|y0LC*kTcPLlXpzU{A!xHL)M^Uq!8gATn#l61-C#kEgB5h=2`M>E&6|gU#
zJ&=O9szP&&`h68ZOOn{Y$F*QQJU_#F)`SMae4n@_ZSaNF$8JU-QUY~ZpOV`wt93Wq
zem1Nw>e|DY{fVoo=}N2tTK9KWQ4iQ8+(A$5J@9bU?yBq!apR%cpqi!6fn$oxW&MLb
z-?{|amnmqr5NEi3{?xrdbhAFRh08Hmc<<_JF0Pb=4N0@KZ*@hJ?`GGU>GL!hrHsg(
z%~4{5^I>&=&g;hZb+rGu(h56$c&DK}d21qn2Q#i>_)?+8L&b6r!>yGaoslO7uh0<M
zOH^-K3DXsDwFP9b6fwuD$ce*(8Zv<BobsJw>UCr@WI2||+6m<yVdQ4>3|R&r|NaAY
z<O_Pwsj#H`H3j4fx%(#dRj>Sr@LXh&2ZsR*2JzOO#3BMSgKmxh{ft;8?zv|HjE@Yc
z{dCubNY8MK6eTQ1!?MEJwyy9K8ubUZ>(>GXmleT7?-|~X-GD>jdUyZuuLeRnPoDw4
z7e`~v?*Z+<1o0ex5ekI&ja`vea56TO{gY5TkzgqajbERnF<~kWn+7=b#XY|k7z87O
zkK=e3lYY%0nG;rj2mPS)g!T+x7ISqLA*msy&O0NQ1##YiBcP@<rj_TgK4}FBwZ2au
zkyT@h)6F@jILCxY>Xe`6?uV^*%6_3Y7rgQG*2lL*&OR=k9FnOWkurNd|L`n(OeFB_
zDsI9Yx*%b<7ZZOD_VcA(qrB=P>_uy(XD67WIrS-u4hdL|iQlAo0U0VlZ}#xop^N(K
zaO8e(v(3yyB*(Xg>)1b%UfC3;#@a^nr?SrJY(in_R8KT^m*NEszRQ#x8qT>N<)v#l
zEPUd%(ouDm)#Rg{zJ?lIg}qZTm{M;1A^%Vf6UW{Uwq9xad~DP7C2KJpazqqc?!CPA
zxXerr!p5rL-;$T>^?VOv(&68uC$7FKd^Y)v$9e|V(O;6JcN=WMW#w?==UzcZ-Cj(`
z3Zue^&Yk^*Bb@cP>)GZ?OLYXP>nYm1a|>m^KNWl4Ro)9wq4BB<6UWD^0lI6_&iys&
zZxQUGZzO}l-B8WAG|zqY!Y^^wF(WzgNT?`SvCO6Ms#Wc)w;Jz-qkPPf>P0TRpSG2v
zu!O_W=E)P2jgis;cdcnA?r{|klgqM6fw41OvjwNk)A=yWtj7t`gF8!WUBP7>d0;m@
zOUIjQyWisEWyX;j+Ac2f9G1(&aw%)|bW}gzME9nA^td0B)?|-lM8(!X+|L|@-?e-f
zpGt0&%-17_%NCCm%zPSI!CD@WH-3kpFd*1}2)S^LQm;6M|K@o(6pv!&=0D0+sqOsy
zIhWk-^T}R)CLIT0UeREd6XEwo?l3XsI4UQ2-F-v+9Vr}P4Vr%!>f6I%_}jjQV#QJK
z_uMnO+<LQ{$l2<7dGH)=<NB!B68pFBl9eTR^_yj$bx+e<{|}w>0Rb3Vdc@kSS>e)v
z7B?0R8oO4ci@r)d<QVuT;~XEOv{+5NJkOAXLkA}Mm98wy4WZePpIQ+Gg`7K{z<F7!
zH?o#7e9T!f%LRxA)}TgjVL=G6TiB}rU??$`Z@;6^V79eQmj%q3CI9ydt|hIVsp!4A
z#k>^_ULUnKW6EFl+x7P9Wz?+*<QH$?zL1TO(hcHU@8DM~ee=q_#)qnV_9o}jCR~@v
z<{y(tn#E`Lz20^>xSK1d8?JEbKN>1guWta##Gt#6xnO@nQm)`1aIf5^$Dnw=)jQK_
z5`)xH?}K>rZ<gpY9iP-zNoYu`&Xjh9f4y;T`s7>JIQldQ@7_U&9zV3H|9C!e|HDaZ
z4;xZ#LID8$(EqcOepWjAm%<{}e{|AT&h~cyTfq{bMZ$`)^uG$0w(*R1LkuvYF903D
z`|IRqN(BP*mC9j2x-g@Kv_wp%3Mg9y<1Jo+dNqwS_S+EmKVv`mW55E)u(83zC!ksE
zE(d=8U{)JW+FL!wf5=#fX`|$qSq4%mk#g9{=h?-LmAq?P6Kdd*QHLbOJ0Zr}nRPYP
zPLLkeKu!UKlQyNaFcWNTVZ|QG&T^gP6ka&y_{NfgDniDOVC1+!_<_oB3y&7gHe^k(
zc&5<Ksck_)_%8Auc$DnwNLHkbyl&n<Gg2Cu+2oHi3$>0E=Wha?{6ECs@@Ry~FLPV!
z6C|8@cz*s?cflc^7#g7u|E7mr0RMR_MY{hrSw!$3x6;Pa?*FKg3>e8;G5z<3#;Qo$
zZ89KipQ41I>q>G8xVtHUh%Jo@WV^{m5?dQYk#LyAw4d2}f&FS+8sRG0+EBV&<qpi6
z^S0laj>jf6!-Ac+?JqEV)|=)NylwRn2sSVqVH5yd!P6D6R{HJJ;^RVct!D+Razc{p
zJWS_xX9DB_^=18Av<VHWTf@@wwF^NWci<K$7HJod6Gi5?QP0Bp(>j(Td2Wq@u|R>4
z1O4QHG+oy-lOce!w}`v8s1!kE^Q<O*(L|={_e;9w3CVS)_~wrlkn5LUZG#;<WKc)r
zhDcca>Lo_E_^luUIx-WRkYj%7fxC^vSRd03s0|@1w#Tn-RY&B6u-(ijQVSs~ByEti
zJIqhCn5vTSM2T`E4q9PjUv(+{wjBNNv;7)0p5z2!_(bfu?z(xAFwo{jih055_|y#k
z2SAnScuAJ8YJN8m<(RQd)i<R!8n*%ft$1=8+_Wu}HM7Bx8AU&X50PC3w>|!(I;@?1
zquJv1!Xe;hP=&q92`&RzmU_&gT&)zBzVhj>6o~2&o{@COSWtRExKxf~*ks35(Wms>
zrFqgrT$z_t#d6rF0k`|J*1-9S;)kTGcFbVchDC|LsM-l!sY)9=uT`1d{+Exk{ga7~
z$|>$uB{kpz>u9|mefv#W_;7+L>Et;0IWxR$u!n<^T&m&X%9=+gcq5;<H<DbZHn>F`
zOjC2st)?9GgaXwR;>VvP`nao|dz)AmR+Pwe6Y%?OPEG*Gq9m4c_6!FfFgw3*uzy7A
zg_;;U4-f#r3g|ya>c96Tko?C;bux9fcXcxUKce*?wY>j{))wE1xUJE&vu~gme28B(
z#OGpD&$j*9Vv<yqD@iq0sWyN+qGn=djmeTH#|p01csq4{`?Xl@*#5z4J1g-$%)`S5
zAmKGNp|q5eqYekdnc+VVYkedW?5Q<Vty&W|BaG7O$NTeWn$GEyM%1nM1kq%**-|V{
z*%R*{WY$h^GjkK{YwvAD>pY*Dq}Gb$=_ko1wADuk7q;(U-<haSR^)6m?9p!zwWd8)
zjmF8TptD|?s1x3qtk?}~$mUF*U$-qmn43n{WW5wn4cy}<u*z3wrPZ=@ZA=}M(Zjl^
zF+(@qv~EQ9M?@WV@nelvi|$1puf*Z_deR+wQ7e2sdRI=FwtLB~8svNs7x#R~9WMK~
zUzFZ-n_zm0tah)VHP(>&<b4xWc6i?utD<U4WV`)tYfnS?GrTtwnlrxIqyUwsYBjnE
zJkK;2VtAH{>7vfre`kooH394KMOxBj)of<EMu;roIm~luOw;x>zw#!0v;j@_Z=^fW
zK?x>&vvG#4!hbys-plZPGSBTXpwLtw1?wz%(BC_0BmeG`_?=O4Bw26Ev@@6r(0+f9
z$Zk+MA^lb9>{sbOYVVHv`2>msS*L`O$cpnIgF>B2XS!W7CRLMVbG(y>e*e55ue$=E
zre?Hj;_YhXA>-f_5#iwU0QOQh$x4IZD0ad*2!CxpLq7QXyK1YgT{!TDKFQs5L4~we
ziUG}58E;Q9S5oK5o@fq0#$(_w7NMW2V}sR0iNlSw&6X~!ankBDP;5L(Obzt&u;_Qn
zh0|c438=xarBONh`qn46;8+VxzotI;Z>E~dgaL?#KM0yJ9S~R%09fFed=cUPNOz3v
zin-*nU)q|0DOE8P@Iq3!h`xGDg_TQHjy!{{VrHJLEBO7b>8TcXGem(;_UE3-TT%fJ
zI{l;cBJYcSAO!XZA)kpoPyu4#8~~Udkk+2W5BC!6mb0q!;w2EWcpcEdL*D88w3i}P
z$w31bTek>2h5GO<HrICn0Wbs4b|{_1{f?Lb4g|mgegPkQ*b}`p7cjH60&b4fRc4Tn
z5(750=|FgclB^yZjh(47VVM%qMzmE=Oxh=!>z7A(H*>aRhGXoXRB);!_#0R^@trZ)
z8K`_Acf(H5*fVh8I@!Q^S~L&g{Cgv}Z}0+E-!n|<QLSx=B1o|Gep?-x)lZ-ThIb8V
z9`>zB71F-c%)=@HP}_0ihKNVE9sZAFI{jk+Po>?I)ZP5e1JzYqY6lK`ZF~EzGzmW2
zW-DHF5>L5G;k)aj<N%DYNfF)Gw6h1KxIEo}Yrt$Fa{<C^sEOEK8UU3RXQ@aIme%9;
zuoO@!Y4PyiU@G_qO@Y;@8zX{js;yPZ{dBMLNAC5&r%pry{Cm{iEhGumd!zwBj|1;S
zInbfr2q=0JvT6vhp!?9X0HDx0F{efcQElMrz>E5_dlH_!ea$Y;e^~1+(YUb;WI+Ro
zJi|ZZ<S|0|Ua$7!Wq~PrQ>8sX7a;0bYAoO-8bm!!G)>3LgUIoAc3!_0q;CL}1{|$#
zR$vmcwC~+w+nXk?X~8>1y91o%VM+vGrk^A5Z%5l8lFUKMTRIuiSIVZ_97x@Q>R{%D
zPqxPgtS~s!Nh<euP5{JqgQ5?{yG50s7=%ENs^@h~8)yOp1}SF_C<wxm1hV{CcIU9S
zhYm6TUJ!TYSwQ$CFI^}VGQ2|yjq*u?nniFCgeA!=u!!t#>jk9dk>u1Iv|AlgP~p2I
z=&F6EXg~oY&?Am`P+F?oka-GUduJ&$c(F#+>X<+RDak+IM41F|>-T#GM*!P2r&jXD
z*=o=UpS6OD)Mx|sX;^a_zg0Ci{|MazH+#Q2kLeWAKG$<9J*YV#R(XG$lDU8{!$Oyk
zkm<%!VpWt5ZqH0U0<6hd(rlu+WfkKX+k;e1a|$ght|BI=n+3p|1t^ncm6ckv#z-*V
zi-}W>uIRL32IPn`q=S%B0+0(om(isWRXh>B^^8Cl`!nl=N=^;^&^acp$jKK`8r|QL
z^AI)zeN#xJdC{j!TwM!TR0fChfCayyOWthe48{gdP(t6@!Q+7mj=<RScP$ug2Em2Z
z5Jzz>Je}jjg;TleYu@C{7D2o7K!j5eodTx#y_$!l#uU4#=t2@Yzf=CbUoE4wf6Zw{
z%|bY1$dC(&fqIv_9oTskURnxsD~(tlScq>grnvgh@J?sjdq00(6uL8v(BB2_Hrd-E
zqVjfRC?8-g$L}o!33Yq`;Fq^=Qr)Z$exR0}My<HvCl&W1VQIQU@?Z#4>z(*Hfv(4z
zxG#}2n!)v~s|=?366EKF%m`6MF`2t9u8jp_8A{3DVQv!=kXCC9vtbIPvC%zMh6Ku@
zgv^>gb|sv7uhqJ&)}$qk=uW`=edSLlc>P)IjV@69>RJF8hWA)<Y|r8A<Q7A~Z-{x}
zK&m~|-$U#q*XRJSiS&On0MMj?uex*)3gc>4D#B2JL?WvqV#0+UQ~k4~n!rJ0=(}g<
zIEOBKqarl!BB1=BQp7b>0#6dqNjp_KL*?wa7!#q43VXDj0aF0t^=oQ1=oO&jq?O%`
zS&*Ftb_>N%ggQADW-Jz_nU%&I302u%qZN3g;4k}{P(0AI65SMeg8;6b5<Ix;gn;b<
zT!p35O3zl*fDLZEM4+N>w-!Kg1k6ekF_Ex*hX7FNkt)REiwuaIj5VRakU%ks;EI5M
zfSM&7`n5H$ZcMS6Aw&{M0&?Iq;|!-&mTN%vz+}8ll2gs=09{K-qYJ!z5|+Rqq3}yJ
z@P`+S_R%|QrfAsFWIMHM2CA^j_FnLgUW$tW_crt<xHg04-@rt-fi%lR)!<c!0B&mE
zS@bnA<P5w2$Z}4+1~GSs0nfEY-6fnx$;dq=&8aos`UZPZ(dl5{CIdqn+Mvr__sQ$|
z>;me6M3Mv92n1XUn{<xDbX5R4pCrl5%=;<lBim-P_uf3;e=XK?_8-S8U7~Nm${egE
z<rHFzyRA|eA`2fpieA>}dqQ$oWO>0O;VVG3gNdl8RA%17nb|9v>NYv*d{_pBBkwL1
z$1<(b`GY}>nSimH=z0^Fqk@1`{T)G$VSpJ-QnGLP3voJOskDOF4Xd<=#}IaMG`P6e
zD5u{oqt`Db_)~r>oc`^{vpO-=_H%!q8amP}=mj<!h3S^(jspz60k6C6)`Tj(VX$qy
zBPlhgu5F7pJYki7HaHZs-L7R`ePy~H?3Rg2+aDIvenhJSTmVL5*tB&*7xUSzUG!Gy
z40ZXy66K2|0ej$v%gCZ;)hbu<UIdz###FP|&zDGM^&ugyGB3Ba=n6&lvjP>)_DQ7H
zg`H3qsCb!%LBpu(32~qm@5gMTmkyI<$%2hLh;)k<Zb~l=djK<@;gC$r=RclB`ko(P
zY{||0zVFm<wH-462>d({*Brn{wcLC`+P#w?`4LK^)&&dz4O`NltrhxYbKD4`Ny$yH
zXyd$r50Gp-9IHvMlL906nV>VosB&Zm`V9uajtHec{%bX1TiA?Zei=OB1&#<jje_d2
zX>eV9`yv>dFEL=LMa@C1=ElZi6$s{{Pi(XtA=GEhZCb0Ma$I46k8qCYnogjhLux_6
z70HE=Br60!i@6XbQ4}RiGohP0+E=>}SL&AsQ5-sKW2j3q;NBAJggjbDOYtjGF1hRA
z!Adh@*yXlNLG1X{t}e<&M*Q0l{!y*o**Jv>x2dRxIJMU+aO*d1v@d>qV}M{DDHWT5
zl?_Yy@n~29xAvQG^UHQLZo56D8$rZOp>Lj9;ru?5NATdu<*g0j?vM1>iM1Cqr6Uj@
z)l)KHtwBZo3Y`0eC|@aBH<nVblC2TsK{{WIk}nThi>9{_v}*PBBnCllI6@oMA1=@a
zmyr$YPM{OQG*ah%K)|jWF(I6FizR>#-d0pmhPqPoW3MfuZtMluC_OciGHmR^w>aag
zXSEstO&rDKX|Fb_xM{D;Oj3Wcxo<p9FsfXiz^WrEbWlI>_Welm4U!%H3C&IJD<Tdh
z^COt3CcGfwM@qcaq-9GA1Hzl%A361rHNQ1Y(T)eBjDYNJ^(MkR=)!%=>=#I&t-BR>
zY`GyukWq%3Ey&)%Gsh3<hFHLw&|(8pP1ucG+0AguInW;~00=ft{4NxBdW^7yq`_&^
zSgH++%7=LAqZ-?}G2p52_HJm$ud-!(+OA2=1Eni(h(QG>j%KQ><$?2}euK$%an1@k
z0S{FwXIbBlBG$LiFJZ2WLc<UX^-PLHZ)OOP5YDQDV{dy(A80|;1BFNeuT9iP6*Mw?
zvaaQJkl`iQi8vDD46D?fl78`g$_lK$0i>|ar9N+^m|lAu{Z>6o^59WXuLr>leI!1F
z5!jAMgeB|ORn-C~H#q?S@<a%|FX>s@Snat#L2kThJW#Xi%2L&5yt2DRfvHW#M2K0J
zzb2goCwS2`2v`hC8W3GlS#MMYq=0icYXruXYsHzOH`uQ5*pcQU=>FW<fRqOLoCN?f
z%(c}kq`usjnu|NQ>Lj0h1)fyZ+#R@vKbH-AP74ToyZw2-$US2BA}`Y)9fP7yCtEC8
zy${3|INz^sE%?0xf}@);;DDm4j8H6mh3L7lMw|uzhnGSM&R7L3`Th3R)w(C1H)4$4
z6>Giuk3449xs3%Fs`&J+1sh7coXhfAbpAptNWE8wa92|A)Ss$mcTH@9-C(4_4)TbQ
zZHpSrfXMmrDOL2?#W*BRF;YfFFo#3BT2&vmF{V+FtF})svY9{4cLFk7mdK%p0&EbK
zACn@pTxh`Eg>{J9l~^eHm7g{B)(TdQX5v`kH59<$wcb|Ls0}PG9*hf;e~1%uV~chJ
ziL+W$Ej@4m&r<pymeNd>Gsm3_RYDt*X)lM3oz`kwnry}qMToCB1IPvnwvYukNT;=m
zvGm_mcc*cmn5nqZ&C=3j<GvkWM^XICEKa65KVjg)tAM7}KXTgr^_MH)Q@9r5jjMCU
z9lmEJjil%Rb{P+p^$FF91Yu85#ZJNM2FB^+iVx)>)TDO-l{LZ@GVJ%OZMUi5NKoST
zDy1O`sfVzAXD#>jIv!{=8c`keZt=Urn-urR1y1FWdQXG62XU7dmE4mB6}jw^0VVY=
zE(cdKaLF#ujsmiJqH7+^@9IX-aSH{GA};sDMvu;JO|Hl)Y3Cb9K6+4H32-J?wz}?k
zAa&XSi^LW4FB77~^sk&1LnU`#NAXdO?m@r}=@z{^R4c+ZllOCxhkvx|NagcvNPw78
zq)WFy<51JLmA2a}kqJ1Kl#l`zSuCscB5{aS_mk|X3=iAP#*`BKigut?SSg3DYw;LR
zUfCSAZh$iDn;UNjp~p14rNC=C|432v7T<k}LmQh3xEAu6W!w$<Q8a9<z+Sj=#so$i
zOwTYTfLy~sSoI9$wXcb1)Aj&I=85XVWw#H?$#F)g)s;`?#{PEg7*<v=nGE${Si3jX
zYyH!#&^#?$LBj2nnU2xuKxJXBQwCU3sKV!!YvKwVTxz5(31@Xvy?|>Q9`Hgngd<@4
zUS;p_3Y3O$I|?I%FkcHAncJSZ;o&tNxKdwu(l{8R;p$(vtG^u0AnGEUARXz+Kx5-d
z#J=Los8ee{g{kowxkHVf0;~X2;NwHdh&<2gzliHTV8!eOCfRZYkitLC_{K78PTMvh
zLwv-l{c5rq;(0?51lq7gmmT*ry4G@Ngc9N9-9haf(5zi(XqO98-We)Yy;_{dVT`}9
z^7`75zqinMTQQ_xCB!*)%)iWEV=t24-S41c-9)@4=8Y6#OR1Hlaomc?^~Idk9PNDS
zM2yjl=Rzi+9kk0kh&LV+y?F=oj2cp~b<uE%9LOoI1JrpMK;{ayFO!tPkifB`C`!-{
z7|$WmzT|yMRRD1YhNtNBV*PLsL+Go+kHdZpw?~pZXPVix9k5;+{g9iv?I1}6cn;L0
zatA;O)?*HF-2V{c0+rxUzX!P3rVp<@IS+%g*bgQLO$ZH`U>oME#K+J9`|}hGPUOrH
zJ}guara9#3>B~TPOBe0BkwW=>r}<@Z>xb7&<iXRpY#9OFW~-}aSGR*Bm4}=3g1NyO
z7(8)+AS;NQJ0f3T@RB2_rz|Y!EMto@NUSWP4bDo-Y<VPdYC?joI}SxMEv*wQREX6e
zFewP+aV<^XxNR2sG;8PLZ9cughdr*#W!Fx)UK(>Z-qepcF<(G@u@hJZxl+Ic<6>0B
zu<RQhGl<19zUwX>T6{9(M5YQ4WbLKV-4D{Y{F|CPaWLmAy_;opni4of2e<?ICA!7D
z!Xz0tZ8ormnagnL)kLKp#@kfmY#Dpd0>Cu#ENnS}<L4HYH-g0J8F4EuNkNEvR_wz=
z-SAzaEDmYNsB%Y;VQ_QzZDQSte1H>)t0wv7ix8X!)Q+~eb;Bh{A!Jsy#E8!F^weOx
zCSYc~ELf(T!*KZs_NQDY`=N6XlyGVX9o`=gP<#vFL1pB!Y7&*{?YUF2`F@>ffB|yv
z3P<=lE5XqcR}V}pY5?SFSFKg(H5dUseEm<2Zz-0W1G*%bQldj+e`D<emrgl2jLsRT
z@LpiA!Y>CK;o(|*eCnhSAu!S@UmHR`T-X*yN+GJpqZc%|p7|prRp7z{n+6H&m7a=Y
zw8#XY;}*#cw!8sO0SEgPZYKSWk<9M6f%cE_{?)m8*r;LJLKqK`)94xbK;)WYPK|~K
zZYrbtnF<wTxxhGx)(OHx0${9|9myM4V}ilZT#C*|4bu@SV8pp0lw<9lDu+*F0vbvl
zvHm2dVS{C%gsaK4selzmFLaco=1P)DG^w_+<}X-<l@>W-1<5xmlrZD?uFkTu!_=*d
zPN}o!pk2(|G$+{dF2&;nl%EKd?t6CDSTgDq^@jcy<$H?_8nD#fk84t!7T$m`(YrRt
zzK;j@T~d9f6n7M&g5%)Xufqm8|5G0f-P1ovDLQ{>))dqfBO!9u1fuIN1jAkfS#bJD
zIzsxx?q`sWze)UGv8W?ZgbF1XNk-5viU-OiH6_kt$F(CZea9Nh2+{~NKVWwUN&mEg
zQE0miD|j`sRJK;mHkw+KMI+EjIjYbNVLCLiMPkaqEeWZwD~8{S?Hni~QE@|_+zufn
z%Nt7?HsH2<ymxN3wIC(QEH>lNX`ti&E+|WmF?H7_lpf-(|K)YU2zCq~nU-W6eLm^Y
z0XHFyz;0lzdY{i=L3l$1ZX;pg#$oi?8BY`T(^Go-Aa-Y&o#c`M$GvKwN+k*ut<+w}
zupd4>wgJDSRz(q8a=|klosx{l@1Fab7o%bj3q3rG=O%)7eK68uTzcb)K^Au^73&b)
z7A3VtSsBv!$_aS{Q*B;FAmN*B==m!_l*B6x3bY3Zy7e^(?TWUR5ET|aV#eEdO9wIo
zC_3&n;$De2!XV-&Hy=F#dZw}k=LN2}UH$E?iVByax|YS2=X&#ND1RiZ$54$6F}G<~
z3hG4Q+LFm+Z__RcH+yS_6B`Umw(!~g@IadVv#bl5D1_kh_sUL+Cw79}CuA7a)Sw3z
z!vpy9c;w2M>K*SgVgrbo;>9xaacT&50HI&c9qPK|PxgcyzI@q2>2D6aozFO`%4p8-
zTb0{DW=`CbrC+<N@x06D*_~ur$lPOLfMv%vIHy(2Z07t4-3aRm(Oi9*DgFrQ8c<!1
zA!U`qSSI^~i_{pvDdOZHChwJ$$z+zNSce)WTohr!jDH7S;XDJI55^GI5qfUG0e1^f
zN5$i%KUss2bLoM)M;wuX!?%Hk$Jcg{q)(5WsSS0i)D_x5E~JFCO?k{q29*3<J7%8Y
zj@}U~uZy;Zd`xR_297ma**J{qD?;u%F>vLxwi76CvZmLF5#aTFfYJ7f!T;v4NXmr3
zxz+r>$UZziI9h6l9baC0)xN;|e}26rGC%iX@tCqIUEp7xayudG(gZ3dJ3k6n!y-_X
z!braoq1J}Wt!hh&lQ|@(P`eXq+2LbOOIl8Me5Whn-S)QC09f;li_-4XH5lF9M81aw
z9SL+$;`K7Yhb+ClEGR4d4xyw#S&wMs$275}bbr>^!d)Xn$TRNM*trBR2Z9);s<7&A
znIk&IeeF!&SiXyCf(XN>JT@wH9(FCYRx_R8q`NC?K;N23RCu!@;a;s;wv`L@CpXyz
zN84&k^@wJX&SuCMh^ZSXZ?n~@IuR72#7vGOGr~dioNWa}%14zH;6}-&>7Zz>^Ap$C
zNzdS|*$F^rE9rl?9+yUSIXN8lej*6M_;$xr>keMJLbD+y3I(^_TXEeevGep9s?H($
zWX~~Kq#caE!T4i2CmRXsan3NxGxcq!lXCYCz~fWftaVstW+O87h<IaJ0vHiPr*J6w
zci<KoYWWK*oCNqW2!3JWApf&`>d#!FvioklMf@l(3e5Fj1G{aW7V}n-I@J7c;R(}1
zU}gP&%ApTWb$^0s#H^6VVCvkbcXKPr7_AgyF}PS{(>K4moG!#F3{|ZrONLd4SC^ps
z0JE=if1hukP}EL$Qm113T^&C?5_SAvcRziDKYF^oeV;yWG$xZ78>=TD{-&!J<5)+8
zK=<og<dYj|aBWSVHq_WnX{UKS*GIkwJT^)M(k*o9cr#a-TSDQ04wc?b2&NxF(gJT)
zlM1}FE}#)>0>1(&9N}^5mi3ZVLt-7~YHEi=5G#?eG|+`Mv_VXuDL&x7*vVOE_fz@Z
z)#?;ad$v@)j=k3NE8A<v1@->0WO<q;bJngq7^X|x38E5L-*d2(O+k5DBQwj%YyZH@
z818{islXIF&s>Mzvz@QXw_JZNTf>*07iWFBRyqe$BsUeuHs*m)uXE~zpFQCrbBH?f
z7wO3Dp2gb~)qf#3%a|7YLEC2+%~_5feJgN_$4MkXPGKf`Gf?iLXMFB!XmB7KO~x@u
z%!0=brcLw|e+P?2&h=PsI=6B%GA<)0VH1Xp@|dzqNm^dd;R?>J6vw?n5yh1zg3Wo)
zvrtm8^KvZ#b_KgNs6=5xjmTMV7%vpj)1}WwYn9kZR?wlwagy@HN}Qh{c#+m_+OkGE
zcbSG9k<VE+Jf}?X6OzwwGWeS4@yUa_8QTEAtLthf#Gao?SsH^J^WJ|nR0{E_6$XB~
z!)|J(!!U*JSs<_aLDod$PQOZN6_gL881l6yi!`19#{>3LtF?BBK_=s7rh;i6+xP9c
zC>!D|G!8*4Q))B}-`xnRM!zZpGR3oqG&tpQM-{YF<1vO_>f~{nt$cZ-S6`bmYo2tJ
z&?@&7B53C<TexuANJY0YHl9>w57}Y%m(jmaCOr2D&oUH&wTcY(Rg=>h$z=2>!H!!*
z&55#W|0SSKSUTwDB8uB-fOTTApDYc%)~VLIWiv12k({usPVy1{OH^hUTl?mr;3bM&
zWngZD%ed&AjjcObeLkHQi2LNoq>XhEa>g?cD7D-zDzgj%d^4*%9!)f>C4l+xz66ey
zw^Ig6ylY2F)nlco{wmzq`Vow46~l1^n(ai;+Fn6BYe5#%Q%4;O{Hdqe3;PZ$QtZZ^
z?Z9;R&#V{|idoz&M|3ua-b{nO9YA1Z;XWD7zDBN?3>*qx!wWuF_mrciyMhOW%qjvg
zldOM27gSs75lTR9+;+XSrSn0Jn9#?S`-gIa?(q9vnt0W$>=oZ53W{+J{VWaVH_n$s
zUX&2b^KK+n&8*$$g>};h79;CfD_i4s)xz8UD*b`Ng2e31YgnE*+fj@9b&guOV1lvx
z&9i}8XliF^&Dj0Q+kyvfRzsbzyd&u7=FxP@k5G@(mYV@N-N7`vQTxcu5`b5I@RSS%
zxV25r7R2d!0ggRhaYdXtpsNz&AS9NKs{YzSzB|0*OqozOD@*%k){;G$6~e<fOdUow
z>uQ<IpCd3%i!`-Ib3ghV@__>j@{GvqQsu5b9?Yn)kLg>x&L<zyZR^F`JY@{b0(@wz
zp_jT^hO={bjhy3nGPY$B3Tn9nuVu2<B*$Ai1y@aBjhQp5G7XLdDvn>Es}5jC8xuao
z%Y5f4vOfWS#GB|MqLzPH!s?5sTpOo1#^H&v9TiLyeFQ)D>v-NbLYp{s^EUP%LeUgV
zmkits9&>4;Mm?g!9()gHeDe-kW8JGb!%N=~X|3`u)Zp4OJ%JS9S!6K5?<8fF@*rFq
z+-MBlu=iAiyHm$Q<bk)x*=Rr4`Dlz2xrL>#BkxwvHqH?bS%j3__DtzET%ehJ3478L
zRk}e)n>wZW1O2G1H2I4q!r>jt;b+-gya1Arx03w4SK%UBee1J2OiTmFe2DF*bO#_y
zAa39tzEga!K6;uD=0iJ$w{@;ydU=)Ve`0#sPJ88(wVHDZ)Bwa0rf|$$un*V8D61qV
zEUP&WX>sfkhP+>fKw>Dt$X&DmD8(^)(5$PR0n?#v|5jBq!nlHUJewt_-w=%}HYY%Y
zurDqdos*jIT$*#G<~KGh!<bZTskGXq#S<T+Ead38Ses7*sFdC1fxC1KrxVvG%oBB%
z-AACbPY@dMK*Xd5R-H7nhyPZ1!?@5jzhuUM9GjAcmq}H<TcH$^lp!u-t{Ke5_mVr)
zV~E|FWhHAQjyN~dc_vmewxy4@#93D{j6W3yzwpiGoW&~OSnD~sKZ9nl$OLS?g2TuG
z6@O(8b^tQ(@EG7o_^tb7q>gbIHZlX*m+%HI624b9`+ab2!V9j%syXg_h_$A=6j#E}
zc0rykWy@s#sjNf^d%lFD2x3pMLa~NtYrQ^AbXE2b{oJ2Rb#zdA{|U7-x#Ir0g;9Os
z{S+^k&UXtN$$2%l{v>Q1C0->E)Ytld=sE`;QJ^l%7GBx5U)i>8+qP}nwr$(CZQFKL
zznM%j-JN`Y;U+id=AOOQwz)8;wc_mCsA{ua^CRtUz+)MEJ_`Oh6B5Z2A6ts{4lc%`
z(6CyTpRBq~iwxAW8BfWImXIiJ;<J|bsFY@wxpUfOVriMk1$scksCnzjCt5w{I9T%8
zvts3i1&aM-KFEXF&-*7_96zqe!RbtKw&8w{q;pag=FSc4_Js;AxMNtwe98M}W<P=d
zv^MPigQV%U73x>zw3xK+%|9cpf7;xJUfL3m3p1!M&WL6&Lc!IIGu#fyTVFl^QPHUx
z9^tU#PGVZ1xauI%Cu_dn=XoovMRr}I2u}6PFbn+*3UmJY5`sv1p^=<lKsNsCEI@om
zDWGH6&Qi{fv_MAsWXZ<*AZ1HzCm^&RW$+%Wwu)hIZa@SK62V8}x2@f^)08)Q_5vUU
zxIw*Y12H{ui5Py?RNT{??b34fX}{qYL%7<M0(Lr5o8J72cZk96+x=b2SI=Jjb7)j4
z*pQ__VcFaJuUNHvg#!SUmOdGzoU3o$gMte}A{wn8PqeT+_)<3gD{GBGftWX`8=?Lu
z*xIW<<HNM|Iojs%9iAWOiZV}Wp<r=qlfwX0dA%&I6PW9fGvGCib(^&GWglD~=N#0|
zWhqyA?I#NR6T)JXcicH$tMX@ylrbORlTDsOclo0f;6`lu$x+bBA^%oXSaGOACATMo
zQNT+>`#x{gf-Y%?nkFYinzW~4G1A3TD*UB1qAOgvKPRQxRpR)v6tWmXWo>2Ox@DP)
zy4^)%$^j~l*=vMxHJfnBrrxcz!{~1(zLJuIKd+v(MjtgL02O<-42oI%ivUv~Gs$75
zk$hkIOJAgt<t4J1np41b`7BEqyRF~nPDCfNV^X8_W!kddwH*m|#Ju!UiH>K<pU;6X
zrV6n?`9<ZOFrU$#7KY0M?{_}?S@f$PeZzy<kWVF;^dA}O>e!Um;}oW5<b%OgpFM!l
zb^8evR^-N%!w`-0^BfYDuv`w22Q6Ap->Nn!LG$!ki45KyxbjTGHd#&_ifCRpZ53sr
zr3f{OKEwGfEyNUBoSM2$FHuK^bs$k=M6u(Qo;2n3u51r~-g@wE!)WRH<y*5}I}K*C
z??~Yccs#V(cS>{&3)>UFr`wIS%KT0MnmSU|^I+EPhM!_Qie*0oWpsOrJHVT<PV!-j
zySbQ`A3aZ=rj)znx+g6po!2eQA6m8SWPtR$INq6b+zqr}ODP@TsRCy_-)}e-y9)9x
zs2j+dDqgYPmG>Z0gjrE`vI6c<Qabt&<E3)WJURiVvW{n(=Ww_+Pel=m*UJOILhaB}
z@?p46Va`azN>oT_QX?BVw~jC|1P1vNqp&CzLcbe0HbNg-$nYdmZRrYtM-2vz{kIcS
zsSqTSV96llmbGqLS_mck{opLj9C`0f28KVEt!%!1wwll!W|SM1Un66z`cfbi%-e&~
zr5{`@xL4K4SZBYDY^ee5@pBrg@kw(VyYbvTsS5t4*Pu#@f>HKKh$5<g@sv`{fb?O`
zwiYvZc4$$(=8xVsU8>w3?E69z_3U}bkEC1-lp(uJ42oZz>|1vAiIlzkBnl13CTFVd
zC+oaWH!74;ArlhIZ{z_m@JPl!eC^m!P-u%)M3c*IhfH|Hq_)CIDowGh+15Z?w4j#K
z?A9i@%BCg0JoSsj8fcU>>|U(@0z(<B)Qn-#dU5HCbaZSRWSRJOkcZj`()A|s0?%8G
zm5;Q{1<5q?j@6?J6a&dJ;p>O@U6=|mOxfBS#yD9>2-%rN7s!A8L>m$>aZRyOe^g?W
zH`ofn1(xLi-K6McaJt+gw%N>u2eP02@Xz}m?+JwYCDj^aGoyD?{3g>p+=gz_xT^QW
zv#|MC82{!FxUX81%+Vt1Zmv>TAx4tmXY<q9s&v5W9;t}D+)#~OWnQM82yE7MW5y_g
zrnib6h$7>%mk$Qa8|{n<G)?SlQ@{+di`zVt3as4sAAd0cF=8(8O`ZqOEw=n^9zmXX
zzVTr#r4*9o2b+lvG^mtiqog^POh~}mD$ZZ7OyV^)5zwe)EPH>&2PmVtB$KvK_toU~
z@_r*-rm>q;g>Q7~Bzp?*B)Y~x&L^j=iJ`#4oH!?nr)!REVhM}>*kYD2h~)N<DYeF=
zAm2LzijKbZ=vM0zq0LdZG<N<{qYc^f^8!L01+U+U?6CKo^+c{xL~`9=5+X(Z+qNz6
zy5MPtVIc#Lom<m(vA%z-wyoyC$db|xv-*l2XkwEgV>HK?-oq7nvK>R%Z0;;6Y_SJG
z=ITUh!M<i^Tx2U0>)x?VVFFi@;8Jdwn!qg`7+D?&6MC?r1H~c&N*(<uvU>SvncqaR
z8r>k(-RVY=Z}p4cS1%KXC4m75!K%AFIzWIzS*56hboO7+X)hW*D}=6f*U&ns3^w*X
z5y!DoNN}5tRx8EZt*zG`RhU6ZNeVbgJ0-(+sU&GmBX2Id@6CF~0Sxgj);iF3I`eCn
zFkO86;gzIvj4V#k^jy6YyEDMhu7I$#c>+mHNQX0ig^7K1<pRw{x&4@ZdpV$6&<Vxt
zriNfdBXMt0+0Q0u^hSIzx5z?%&nZi&<g8+guYrbNwj1v6!;@!n5Yl8vDsF5w3ycs+
z6h_ZY87&lav~DS2-<(v-<YbWg+Yj2BgumT}ph?&5(nR%<j?G$X=<*E0nPw1U=|xKg
z05iaN7(_H)6W=RX47!Ya0Tvj|$Zd@V%bTF+N467Oll--E8yAym1Ix;9IT6L_SkMa<
z{S|DpB7{MX&GZ5FM}c{T)jG?==}~0ac=xg-;=ZgBVSdXN_1T{DsA2IdFP3HJLchVN
zx<h4_23PWpKDcGU8cF$P-<{#2w}4*wYu1nfh#>yUMijd>Id2=Oo->pJ*-*oPhMlOI
zSri7y=odYJ&#BqJ-3@7<i%LX`UyX!Ii>8hF<GtBMSmhn@@-ZmOj4tyBAC2|X(r{0|
zlg|n%>bPexBa-YfDUw^51Vc-F{n;p!(0tF+>LDg7<4Qx>C_fIx8459@iOC_~I|h<L
zT)IsdBxPM!3i`>QQ>guZk1~7O;>(+@No@O;gtB|1mO;lav9KV%(`(2Ea7>F;Vi)3O
z)m+NsDh9`({dN<gZosaIKT{gtFF{Xf$##f{Ku~ZXO`sATlLb>v48Dro=w`7ofu(jc
zU#gV|=G?4P7|Z8*ys#*~f<bKJ`_&kY<4GQOI}J|g%xZ-_?IdAYp6j0?h{d6D60!LT
z>YZ{;yT=U@Ad{s}%<K{4EhFDc!SDy1w>OvyS=?O42`OFJtbyyBq5=9P`L3_0%SvQ!
z?4VWh7MYDP?Hd-~Lr~@J96QI^S$UmC!Az*buUm-;rAFKukiFJ97RlYa%jUTZu208n
zeO8vAfv}_r1)_3xabj}hVAmMlG^08h(aQeESY~+xbT2LzCA?wA`wAbN62(OtN*iO@
z)M(gis40Jz6%-ih8^1^bPVqX!#10?-jxk~|!q4XT)PzdHSQopCVY@ReF>HIu2Vj(1
zR}U#^?8nfz1oDvdI_SF(F;ks$v7;ltVV2UFheNq6rgRADsX1wN{jSBB2<0!r%uk72
zmOJ{SYVsLc^g-mD&(b)lXkf$EFs~+@wW1ph36Osw4Vk@At}}9y>Aa|F;+;Ay@qqZA
zyXFg+mLxSmEKwhNDeOwV(n?&oCj(2dCEOy5e)-(a2f&r=LU<NR;<OkasR{UY4M;R7
z^zto;gD;!u78ePkd^rJ{vLe>OKR$Kp>5iM&B0|!QO0o2YHxBB!uZoM0QL=Zyo|Vmz
zR@grkZK~)JF*DJY;zM?LjH%U6wz=BYAD5&ZLDHG}(Qgn3O17xV7+8lADGp%h<`nl8
z%e4|(&-ki*pOk0PX8t&LZXDVb@5kdJ8RUna)fY5u2K7^u*V+_yt`3RSh(4@<u<_VK
z_hBygD4eR5MF`9-IO~vcBWUCCzW{D~qL<L`EOqJsOhHmp0Sw{8fAqQJPyxYI)J%~$
zr8wD>?PhNueAXV4xZAI<bWRkM{86@upWF|;e$vX(FLgrv1LpAi_MX!Gnn4HFt|YG9
zbqB$k+`;Z*HO3r8QuNm>1F5V2z$rUdlpfUy9bor6&5~c1IYafm+GQfnVRB0m=$#Ee
zIC}nN?)$4t%G^rCd4Bat^2Ny!f?N&Eu3wXFO9W!muIpy=AvMd%xKCc1JjLkl_*0%1
zpknO#x9uF^ej&-Q^}5L1*>Lz$WQ+YQ9lc|2pvF-{iuiZOB)NebTT)E{C=xNYZ73z>
z7xKWRani03037hFF`qs3YI*!xM!jjjv%o5Wv%Jn;RiX5pJ%|MLbG>wmb}4fl%*!#0
zDpd4l-soFHptk*J4ZEe2;B^np?$@Rc^WQUNXJAXzO=$=9?v#d;1~D@%*mfzJP_wUw
zf5+^Cr~hCp5WA@H!iMLLqx+C?gFj3p)k;|qiq6OTfk|SvVbj^K4(LXEEGrFdn60v!
zk|GINp~m0gw16<c{R1<Nfyk;eZ@2@m&2|``a|m6rzmX*Al8K`>e`xi3A0V<fm8bpM
zzVH1Mov<}zuky}&r$(3#_+GKJQ67q6T{2IU5;BO?YSj><Wm44RLWu%(uMBpOw^K3n
zJ6;$`sGRc^)rQY+YEG{_E|xXk6sx^M6EI@T7aNfNEG3t#bs0Wh6JLT(xgYChCz8km
zT;+trN_w?=NPLe=A0?v_I{q0S$2cRV_Nk0j!Tn#-G6wnZ4^zw3Np@01cS>c8j9x(A
zRa$v3byz#Nn{3IkN#Gsj5rtPOvY8^65cI0r_>ys^cTd6XeDOPg6ME>Z$lBzPyN6cE
z;2;jJA?Q{ZN`e6=4S|TidPxapK4I##43kDy;Q`qnMXC0eBI&(Rb$m|y3lc4!2lk?N
zGxQETUKfUAglqs%qFc(1nfNU?{|ZK`KxY@UjJ0a{Wf=Z#$Km~2s-s6?`3n`kwp_MO
zeaaLH3V2&dXl6dOCgj`TX2D}#AcL>0^rqza)`T#u_~Vls=5_zd8-VBzaz{6iF;rns
z>^Qmno!zjbTP6BW8S`R|S>5euxkdF#uO0Q`8>T>^BnpXuGGmXH`k{JaR#X)dy3X^t
zFNuULmlffkxnxkA`<Ry?SD}1P0rWUXHM(;xHG#rK)rG>JfaX5q<m&PwaYsty`BVjX
zl5FRy<A{r5ZVO_}&aenza)C)6l<i_YkiAh1k$?W#0=7PP<tVu+jLfu;L_j!Q^BqWq
zf!E!yXWHM_THp8I|C7_tKVgSt`3L4?p8WTmzR3R~N=W}>PT$c<-_qF3*2>7(;XmuQ
zhW;N|Li{pno~*|2aL5ARbxSG7Bk99u^RltyaAkzUX<y+GI7Sdm2tfxxHY{;W%Kic4
zxsl0}g6o&^FY=p>1q05wn3j{{|NHZIDE+aapt#(z;Z&kls=FYhiMLk##FRIz5o<uE
z{=28C=&^CVoG871Nc3jx;?<{ITh$X1_vQdEqKcQN`7CSUXltvA`R8e3wSUyOm!{|8
zqx00kAziszRpjy9^sQmS^B&}K^4fBLTSQ)((Y~;0>8&N3M!3|G--WuGRQ6yarD<-0
z9q|sIXHtbmsrqa3ONFwwNR^U<H%6$%Vn;(!V?Byri)(8J??9!Ikg{19>(Vlr`d<e$
zOtjoKhM{BeJE1TgjA3wjvOki#yK;OEgrOt^`~p^`U-ppjDHYcTYhUw{u|IdM1f+>g
zOReO;*I}37%?d@O#g_}F`HnG<zY^C_b$Jv{E^dFPKB7l_CHji&rY*593K&bE{jeWs
zI8+NoZ9K|4wV9#Bf>^;zl*aKJhWWpf;iGW$N<K0=ytkKyTCjNpN|K>U)=?yXm@%3B
zb6_>=kFdwhS#pP)&3$4f3;u9`F$dl7Dr$62zp-l%Wd!z)Vc#TL(H6C+hIHq!C{}!0
zQ!F)(nY4D;8KJrA+pLG>eRKxCQ>@(a1Z1om*G5$Rt!duQuS{qn5VI}CN6fP1;pbbF
zV1Xm2OBt=Zaa~zsz=L%H#8_k+u0|<zsDU!elr6bG#c?Vv$P)ep8zVLwybtB=hl;OC
zxdLY<Kv4~$sdzES&tvDNRPPp+JWtrcc~_Di5@VV4PUFLrz5K)=I3o}11>@^9MjE8N
z0itRiIOxnRpU3Y}TF2A74|%mu@!9^ES#BYn&H?f)fCgXIr;cw_x5};SZ%<;=Od5t2
z6mH-`Y!lFH2>n4_@~5sPMUG>0iueLKI1Yx6TaVU8XK0#Y-UJa;MC_)$&r5^Xh2{lc
zpqWRx4Y>izT)haWL>oFgT1Xq7Ts!XvyYkV4PaA%aDE59Uz%Ev+`Yn8#)FG2^mYvK0
z^KOY8goAFV-|>b+vkf)4OTMfwjVb0Q6}IjBWjQp7+gS2R6t6E1wz$!oTCrN;nwB=$
z*sfJZ#!x~NLmz6YF&K|zYI)O^<|H{D+7%yL3#CGTyu3}gVd;;XZa~_^_j1<3X_@3z
z*rU%YUOHQHMfS46YJ0loD0P6mj);LY9i)wtJ5!_9bLDLo#&B5VL&FIGQdFFARW@DO
zT`(97RKsl^Wf3c5P(>gjati#r=I!kyu=hY=ZE!@s_n~4Eq8DtUQ#gb@v~{i6Z5Bte
z-)2emU>+9M6Eq{L2T<D44yuoE5slDKSO^WyJ$4&`jbB=GwI4~`np0bb$L9rhtU)TE
z0RS7l&$A5Q=lzrO*^al~3ic)kh^qtH`s+P&Yen8}Xnv8!a0V6q-RtY4zW_ViuYcR3
zvpwB4oM=LetWtvNr={eaWfI7+L}3}H_qSpYmIE|ntm(zACP;ZO-tM#5j)5&s820%e
zLQ!>7cM<7mC|Lp!$r9ogR{Kvw77?=?gHp$Se9Xe3NgKUva}*ugIAB|tN|8SJ5vX<j
z5Nbe^KxMKgn~r0T9#s%yTJ`DZ6`NjD<+MU%5?MJ0S%Deo8Wr(udBmsFZx`J@x-&Bi
zco|Ks-YvOfGI+`FC@>WraXx_4Jh%DTzT1BM=3G~>#U6Hxu6R`8_#iFJrR1ETFXP_t
zFPraT>u3O8g-C+F=O>g+-*}uVFItcGsbsvfv770MZ2jqD3Q&S;+*WxG_RCMepx8jB
zEttUpqg+k(ic*sU;Gy}+<Z_Oh9(ct&2VqLHchTwGh2mNd{lC3Olke3!4wG3hB*zm>
z(xuAGcU)1!-|d4voiS{Dq<L6zEIA)|bGaQY%-@rRxwt$Q?@Um*oL)>!w>VQnjrGA*
zmmt*l$YsFHG~-l%D~#9_|E-8Sanq@d<0qW3b``~|zBMUVHn@8wFgVXeEYwLpr|RpG
zeq+-adi|^x92(+IW#?GQm{8yMY@>;K_Z!f8ux4g?z90Xu@v6lY!S3fD7B+?S-$%|>
z)Bl7R|Ffj(-^g(?x3&4t<K{~F|8tDj-s3iZ#Z%V0dk5x2`IRXN!4j8=01E^8PFUE*
zT}((D8G;7@VBkW8gIKw@47~_A$<In`=fwH6FMypY6t~}iKmK+Pr<g|4@{7zm#X6PU
z{Ke3Jxms^*rTx8DRe!m(R(uULU3D%@u}*ar)^48dD4<-f{U!K(=3G|#Xswu7shHL|
z3iVP>5`J}d&sV9ixb59Z^8UOWp3}H1zARzegKImO6fnN8FvZ*H;cc2k)2)?UrlD1C
ztz50xV0qUstq@k(E4^#XRqC;AMC^&}?V()K_;*9v6_-7dSts~a`wHNCtCRvITO+TQ
zt1CF(epB5`A-`^vSNAl&GB4(qE`LfC)pe^Iy8@JzUs^7Z`S?oBIt!H6YszkxSUPVR
z)vjciv9!Qn<b+*!TeB%7zd*h)ezt+5nl_}horRatD##-*aehz$bjn+T;kXjbEI*YG
zKzqQ*GFm*}iaSFEDf~1Kt?w!U2f)zARDuHvN$cM7$89?fK;a%C>s-1OhdXLpuJddE
z!Q=yg7d`DGvsL>N`yqNDZ)7wfk)Ny|^*8pF)fFE%J(B>gcjZ?n`=^jRmGyaWcT~K{
zk{z*^u&^L#c`dp)JT-5u!5R0(07$2Ihp;qIWh|XQX$V2AZ=IpJEZUt4mtE^d?&~r0
z%c@;>n;rWgd%d@>)d8DeS6k%;%IhM{0Ou|{<u@+6zj98#Yo|Cn2m@r{HsWcZLNv2}
zdJ#01aMJSDomD$dVxpNR`)Gt@%1Rcw&KDl4C~lg{F5yROT$6jv%`X#-Y-a1mmtDoK
zNypzJS-t#s`|L}fp}BhsHsNMI6)SZ|gr5Z&us^B?!QcfUn%(~hxcKhg$~~;k13o_8
zlT}W>Ef|6Ba@&s<YBP|LZF^ZnHh$nT8{{ASJK!a!*Sp0UrXwb>{r7!2povP}t>tN$
zgHKm(9;lA#>J4DRO|RMpU!aAWrPX4=(FA)xHFhRQ`>EE$yH+r^Nr!jBTAN3eesT|Q
zVrO;W_7~-z063LRgUW_R3q{~Dm_2xwQ7kJKcDp|(=u^6H>jXL%DDoMF{b78KsQ9xR
z9aNmmU@&)>wU^z55uPAJjNoN!kKg-ptlGN$y{1=nmA7#X2-8iI>dC3P@!(UNg7g5P
z!dwd=zGIoNWM<{^y#N<hj2-T8vf$Z{J|$s!GS_}Z@P=WfHEYPPHi3;kjnk@OJ#g%M
zCxY7W_1*q>d%rs>p}4+YyRL6=8h`sQ5Zk&!Lf3Br<(^9eE&Ob1lMQ8rq@{1RZ+4At
zE0wcZE!{dEQ=ryXC<U?Hs)k^p>H&EO;dSqTv1@?b7pYm@5Y;GXfja_cfnZQpA;-u@
zGmHO`!}zIxfZFJD1B{h`!|1sX<u;bIy@8KPo(w_U|C!Wy;duL_wY0McEL8FLZKzj`
zcIpLdfM$zC<z`oyaT4l&F=UqkyPe2L;_c%s0Hz8E*_WrfBGZZsM&|J;&W@S!3pn(M
zy%Q0VUDv7k`piHc$i2O2bj7#Kyo}K<RFXqvzau%{27k-Y+o`#xVeQ(OO~dExmlquk
zU~6U9{LaiGu&A>im#2_IWu@zwjGk$qR2x)ZDDk_0i@`!VMpcvOM+tq1=j!^f{&A%Z
z%U0Mmk~{aO9YMnP&i$nqCb@$R^a9xDZ$cIb!fPpM1VKVg3y_G!5T3iY4tvhzIlRFI
zroN$KA5&e52M|Ig(QXUaVu!@Q*i2KtgK&8V6X=%VVR0J%;Z@7bJUATV?Lg~6c7YAc
z1wUa^+6Dq+jlwS)*Ah!Gt`^3qYkPqJ{LytRO;}&Y^rb$y37|Ng{4`KbtEo8kGtOR8
zgwPNVl5wYE?3iZa<F&~^_D<f7T^%8b$XH#}0=W#bROP=iI7U(ySPwcJ4<_SOxc8Yo
zYK;B^@;c%Q0((q)55y*Q?hp$>OI6-62R<ZaIY!Hof7@Na3jrtzbSAq7Ra>Ugy|sZq
z5e-BcntR82`a;haCBU2BD?t}T^FF8ocu`UP^Z=&^02=|7tJfHG!RWPs5tQ6WKhgmX
z6)CF)2^Pc~B`=-C%M4p&J*Lx0a;yD5_^HJFyp!t9f#?1f*ThBk>xRMDOoZynS<wzG
z?)y_~@EsbPq~nN<&GOu>Wx|7Lglw`m!aV;&XCH>e1Vf4$C`<f0sJo09DC~%tm>VE<
zhN#7S;gLB7DwMMCH1o!6Swyi#dNOAH;+Qp{3{T@;nOqYQ*xh$p?P^-4cW&U`nZYTG
z5-d@dE;?+Z^f-_%jcJ#i=L<d_=0z_=->BDT#xei~%iJDX`3(T)T|v-!)IU*zu;M5&
zt-=~m#3TOB><Oc8PH?|QhURK^l@fEkP&U1H$Z+DlB?eLkMHJf`sQK$rRg6_>!$ZBY
z65)`pGDLBK+U;;-<a|K%oqPHyJNZy|Z!}*#6bPk{Z*b#x|J5$aLt~2ae~a%u=Y$`i
zJ)Z^O<}z{l*wdexhm$7|F0k`au2wItm4gmk^GxZsVB~;AUwKMGD+6nK(!MRi;Gp)K
zK|7l?hk7#(p1`$n0zmQ#1Vw+3=JNC~pT&0g`NZvU_68m>UEOolAKqt-?RGT5uq;N{
z!);a65V3jsQFr;F`h2^%K)N%0YWn^m)K8ji91h)wlbXI-;khM|mSxn#+oJM1z`OHc
zYKS7%t^Em`BhuVq0jVno;o7UFXcl6zfu5aZ6#ATjOB3RQpzTKJsdRKe!7N7AsZD_<
z+J(uvN`63Y<A*l(oYQWR08|(oeTAHQhlJ){VnSUfoy$wj0SL^U@sRtB!@H+kda^WH
z?Qi?zKNy|;Oz!a36AG6E$J<OjQ3#+8gx>UC9SgK`Wj!r}=$EzS`fqky2<S9OiYGF1
zeZc;7?z}5;U+G=EY6hEK1N@k9yIh?m``C{J&-0|$T?^kc_bGbbzu4+_HE96hENw&6
zC*N1jh=$WTJlFMN!irSQx>_HIh_PEXqro|cy@dl8Ojc38eA@g8K^Tu@C~NB>AiCY#
zn!y)A@Lr_DZ^D;RDgIfyB-y3h0H@RFtG%=-wP^w<IP<@c?ZbWbmb@kR@9ok>%l2&V
zWo4m;(3Z|v?ZkfLnv5yJ9f<rRtM*U?=>Jhu(@}C_7Qj-g<{GsHo<l8S+67Q~iJ5&P
z2~nKftoO?E71e>!uD-C4(jTMyka}+yX>p?*`%n#P8P<f2TxLg3>8v|=yFa>OpCyuf
z!BWfdNZ^N5T=jhxiP;oD*m{BuwGi;sSgcZ?^UlgYkS1(ZxYF$c%JW5=w?JZh-Xx~z
z3<Na=%p}NHfJ5Jm!Cm;l>J!laZ)dY4G!h(!rG6|}H-aS%A+}u>301a!@Pc0H5TD$I
zSz<Ac2n|?2a2*d_Ux}_b!+!__D99Pj^@YX>GMkfB4gyaNQqCl~1X!{uuwActkuBeO
z!~I+GL<7O9<makX1NU{J@FE7s1$4x{)#QD3pZ*K_hJ1&vpdh*mzSGg0z~1g?(pwE~
zW^L2lOagQr&*$DkUcoGivCgGt#QRj#(r3H(4A7Ye4)}?1my1%ERuuL!1rRf)&Vp*|
zDC+jrS?jS!&*#RW@h7)NK@?-91m0|+hp3kc1nr-2lBkc<T5~WH-f9k{#LrMFhsR@O
zoDx~XU=QX|>mC}RXFrQ+CaHHDFhaf~CtMe=p4;ldnIZ2GAm)gZ3_8rbgH%fri#Fj#
z1Pyxk%AN@tv!`C7;!1nx*jRe>3m|MPe7YOZ#y8d1I{nxOj$&nkP17Oi#IxCw?yH8}
zl<I+5Y~d5LtdhhUt!)^wNJMeh!}e>z2MG7o^e`?;ZGBImUyzi*F;(-+?A(9o!b!uW
zFqFrEr_=%fPI<m%;yu#F;>cY*Wb+2kXD5OW!o$d9{Iwr=cy`D0sH%`?pxX)bE%N>y
zu{4E(%fYWikQV`S#tpeSA6`2dUfT?;@L%!bU6%<i86mUJ-hJHQ&>su|SGkb<i?u>7
zw=Md6@9;NL=A?oYZToGHoohbXXyO;4j?uq%57NE<jE9~NJ6l-GKzv4c@Xi1^^!xy6
z`%^drqCX0Nvv&Q8fq<v@x#Cl|7N}=BX0f*L;RJjDWxMBW7wpI3eqy%BRC;GznkGGy
zkdNS1-3C30D4$n&;<;_*aGCcof|nV?2-P_4L02ZH0JAWg#zyM3&pi>+7{*A5MT1VO
z$<C9|7<!jbN(_uqS2vh3u;pv7XaZQg@&V=4ag&K6|Ei6O{q@pPwpjAqR-ZT+yoO#@
zXBG|YUZJ@^)Fb<`)L?O2-+{F_>q!-;;>%i(B>V2Jrn@=(WL#!ti_XbG0BUo-G|P&>
z#L0vqCWuKL0OvEx((8f7)kh%+!PhAY{_xbwqs%O0!qyYaq^HAU=zxyUOtJ;QA21yN
z`)>l~zlXI^-+L>ezgbCCI(k)HHbl>tZFN)RiA?S3!)-HGH;!=d9tQTpdVzxgP#k?R
zpL(g6OKWFrzn5W6C(At@$k=i&qnkqyfuSnrAG|4tfsH$0zeGRkgHOIgeuJBRFIGp{
z#>-JPF%ePu?i!$i@0HXzF>!393&;qN8!gb^#;Q|Wh67>^!Mn6l^+l}RaKvl5LinD+
zi@z12+@;Q%0A3mhCg}h?8Woy(ZTn>hvC}qbhRUn3;c;toy&BKQJM=O@1lj_Urh(^a
zm|g&|gvH}Cu>jBfB}7~d50V7X{Aa_qeedF!jGPmvOL^&fXbzC>5e$?drK)G?9@9BB
z4&NgLdWU>TY8~o=Wdp!tu5EY(?dch;^Rw?i^7h<Sv=Nyi4I_5>2=6adLmvbKH-}B;
zu!FilA}O5L?Jb+xcLJhyL<hJA^#J{Z-+<*u%<|jeT`Obt2L7kPfi^`s5`P#yn9M$a
zz@Cc(qY*nKN%dPvrQ-AwUR}6%?5|oUEW*GqlvXbb#WO5s?~58m9I>+{TNnI%+aREI
zn{F83MvA<)f?3;~hk7f@jUf<pfvC;Y@N|L9raS6ZD-!4Breb@M82w4v<e&wywTs7|
z2n9URJ7ar;l2}$jx<6aUZ=tul7N``zI%e0_9>DiO#U(tY8|Wp!Y*pywHZgl-Z4O}z
z_9LJUOn{=SHbcH6LeMLE`Z8^Je#QQT?FTaxW?<;|(KOsaGd+$ehrGnz(|v;$HpRNg
zTE)9ER?89KEW)v-?gc?k_>u>su&BVmwncJ`1yFTN3w;ucC5N-|6_ml2vSm=2fgs{g
z^*IOT92cZgXGTBY;Qe~KGpt8Jkb;RP;ArS<;!plN;8i?si_Lu~AuLpIcp+5x5(IK+
zxCD=fksTGzET178yOHkq3~DC7$I<&ft#JaTRe+^q8uER@n*J=v1$+V)alfg3=ra6N
z0hF69qf~5NXyISI$Pzbi+)GcTX?Y$pvd;S_><#8LxZZ_QFX$F}Abj5jFVl_|Y&jmI
z!N^}3eCL$Sy|NhNLWKE*he*ERdN6|8{u0Ad_Dm#2AU;r%Um)uj(kUqf`lj-7dwWop
z1?PCdHE_<dKaFNWKgO`30VrvEm_q?^E<GZFPris|KXaa95k%wz;SNB-z<c0&X$KHb
zZL^J3!*&P*yEpQ9jUF<QG_!e*&wA+NM(7}@lx~WD9h>EiTrLCX7(73`+$N&d{VGaf
zq8c^jIAGwUQuJwjt0W2Bnw(M*LPOlEh>5faLvZA()+NbGYA5W?^oqGeJbpaRZBnLK
z;Ln!54bwa3cdBWat@)DWwN~ja9FECRcll+;VopkH68kaw%;0Yqz3<1AxU%Hbp6+qC
zAZ#~SmE&5Hb77-0KX=P+)*5B}*HB2JVDgSf_MwWBP6)PkZ*M>u!6pkFFEBgP&dSEA
z^i%rxTr2y;NLHlFT2bYNrjLmq)-;5Gt=gaawBFMY0F^#EiWA8<+RJr);wYXsaTMb0
z8s|J!peGlpbHd?;F=df3L$NYyyK*h#tj6Vm$MJ)C{rd>9NG*qV7209Y>p5iw7#xSC
zXnqRB3pN8*I9|hu<-aPX?p_W{5;tRG&X^elaBxd07ytUB!)ALZDwOxLusS-1(cfxD
zD(!oU$xTun_)c(FvKadux&TaHT{YB25RCm7%KjPj6KcCD=}U^_2cC%I2EyjJq9MvM
z)x1IkQhNZb)v!9W@R`mAgj%Fw1&=Cf=O6STZJZM%#X9B1_!X==Myk4JB%`1L^*hZS
zq+FpH8f$GFni9!=URJz99-5-rAzH_dJ<a6ztGhty9HPh$cKrZDM2_cj9KF{;<t6cQ
zRs<s6!#IFT$LUIn3*CDIeQn^Q&%Tti>QLM}T$#;ie2&38Bk4WM$x(vuO%3e*ela!|
z@@mF2JeHAS?_>Yq0n{hIjxZTN8cH)nT*H2`2GiNxmj^!d2(V4otjT1L^TMBM7CqDN
zbGr<~lX-ub80MPC0aeZ(-~8pu<bmY+rFG-S*-BBr0OC)GaWX#&+Oh|K7VQ{*?gzkz
zlbD&%GNPU6(500=VO%X?@Uh-n`dBV$!`~L;e5-==7jrx`nmKt3icgW0N_&>Xc!)S=
z6=j7c9FH}Mdk4psupxg3$jrCYf`tJ~^u^;Ickc|cT8xboUK^Nxb`+-r<S<5MI|;SD
zO{~O(*>x&!aTn(wwag4ZTssgIE(%ncQTLQ9DZ>sTF{wz4=1qjFBWHOVND=RtL;P1$
z(8673Ge@G<v(7|NfxJxI$;g*ADSSPWMWE3E8J@h6&$irq4<X$rfQ|YMG5|BM0r+5w
zHDx3m_KoBy$JNgW(j*0myYYABjRF_!G)-UPU(tA3HMNDJsw9dIOE67eN%%c=!w5ps
z42;lahG5c%FqX<}c*r3ldH4o9*L=Uc@VT!*sn*yN>prv)<y$mB)YtAt@pVeZ;dP?l
zn_6L9Q3`J)*~dhg#PPSfy+NSW)4oscRKB#qzdz_BrRO~qnBLPqKpw-*IN_e?%3+Z2
zzd6EkEYW<Q9Hf1-wjj@vHI?v9A<qjSYUJ1YU?h!@3|*RN5Rhy=HCzRU*ml8|>tKV$
zVTtL)VxHkAZ7$|I?krTIQg7okYgBq6`3V8Y1eV|ed@t{Vu_*G~@GrRj0%t)Q1_EnI
z08-)Y3|WPh1N>({Sz#)~fVhomkC1<@)lobC=`<}~Sx`j#ywGG?@Qf_$F_Y#_PYNye
zwekr9r~;YG06QCF(WirIvIRD=XGro>31CK-XO%bgFVik-+EiwMv|tr4kcp5yAvFpX
z$qy9Y?)rL!kLp@ZFcF0__N=YfaZwD3YNbtCC5xS4Kfau(iwfeR=D9^YI4qF>n6jgs
z>s&@q5uhGnN1Okc8_9Ecv^rwPYSKOpZB51ImOI0tRcX-Q#XG*Xo=F$WK6@fvKI2`4
z#SEbKE!4A3_OA6`C;)PO&!q8Hm$faH9T_nyiS*L|HvyrJYdDItT>k+FRP~&O@r2F}
zwcF2`6rrHna1O>q#Md<CKN$VPRqY3cv_O?EL2WTX6N4{{sw$4$Ohop;Z_&wSJwDr_
z>1V#~G_pfX(c%*HlPm)|WD89<ip)ZEO*;l+$<-r>+^Tpy;)SXG&^}#tbhkMm`9n`{
zFNIuSW`eR}Bb=5!2-q!U+tah>79L}y`~u6y=(7V)=Q}#A)BaH2Q%W_<UZEYPNJ}au
zB82S7Ade~-<C~po3gHggjxAlzuhQX0mH^JKJJ=KbI?YlWk&=?7#(PcmcLK{}NZd6z
zki-RR<6|FH2VDheq1jM@uDN`FEM27YdJB*<rGCxNw)WDbeYVm|(n=FGb1%0+@{@E%
zpz|;S<{Kzwz_`ly6Vd2TR_v#;lHz7?KU`v1^^{J^*l~koWysrS=@jypLmD2o8A+lT
zhTQJKVTM>Y^9vc=cv8>>Jmm(;(T93G&KY~)2h4g?n8rTu?B`33nT>%moZsP&xwtVc
zU%olvKzizcN!Vg(@QMivoZ-fvgWI2_olJa*^YzI@GjFe<LG0s|9J_sujV4w*(xfen
z&Iibf?_H$TOoUanjS<T5&Jh(vwWQST3{(E9OZzpgPlh!N-9#>$k;>5{rnn?0>8>sM
zbSMep0gcfKZ>;rc6$ILw5|#)rFMOc;NR|$xp-??5Om7<$fs9ZMQeEL+h=ah_?}&)z
zsK3PK&Z!rHj?o|yY6%!D<$8}sn+77WKG>5~Vdq<N(B$$^FL#S7(YHv?VwS<BF{{FB
z``5=bA?q+UEpz991$30_aZ)Yy@Dc=hsASao#UXm5*fs$8E$Yr@Ig$ALaw}mGW}Bcd
zN0tU|?bA8|J+XDByKS0(4e4N-P8`F0{-kfN*w^qp$DK25DleEk$l_bU-ZB)GtaVu0
zI>(F?GS+5N;ZVS(3T!UMlsM6yC<ior*nnyqJEZ%fKt>ui3Fgfo|HxOfJ6qvPVbSm+
z6ytd5v;^KR*6j^OW$*EAD{s<NAMI8&@Vs55JUP=aj<Qfu3K7&FxGu<x1k-e*>v)Ew
zP6h7|>`Ck~?PFpdYGWuh`P@>}j6^pfBo$#16Mn|A2?)k3N^6NK^!<ct?^u+C|Ejw=
zJzL~~TA;BM3mCYZ0-R!u1}jQ<!IKh#D`A8qXwi}^osIA^cv&w&?<JVAJ*YcfSrr)9
z4_#u%5O?Y@ZCs-{SGvj9I#Z&S7P*Omf09U_sRMd&HzK?YfPyGF<TfEDH^C55q_@D~
z_$=`Io!PIkiuDeAP{35oDIH!t?pupi#A^M<i6COXGaVPpjU4q|;+mh&q1yjq!2&%l
zN=Nh?xOcl~MQRMmNn~Bl7Xr8OI2Ws6?8|0Y`jWv`{B^~eSCu=sY#k~eh&hoj&9MdF
zu(kHlhbCT-q=_L+q;A{Hs<Bj;TwxG4^4bu>VI+XVNLMOda2?(Uf;U*Q5>{cnT#z;(
zj`o|dEj3&S%0Z{Vk4t^gz%JyzjdZZ)U^B1n9I9G25CTexJ^#CKaz_<n-gC+8{cJd)
ze52S}IH9BfMxHSk6hY6ba)qcSQ8EIZH)5#D<JV6ejgwi;T_XX(OtoR+$9)clIS&kf
z=cORl+tQMfbI2F;J9B%-Mj2fx$Tuaz(2hnh^?hTovQ100g&K74T>7rgC)V~`9Z!%#
z4S_>(-Wu^(29!c?{}seY2`V{CQtZGyoNaRf%9(6jQrkLarz*gRED<=y;SOo|P`?pm
zR$SJ0$=nlmm<?KJElTQ&J&_iHgr2Qz0>8LXe=pIIO7w=jYZxIqEhJi_m`9a=OnF7X
z9UhCYa<m=Y*A(P%kRI(=^as{Sok|oUwf1_wP-pMwabPUk<`Fd;Ju}EZKi(<J_o(+h
z$MG}-D!Tz7;YWnCeH1!UrncFslQugegJH970D%^3laEOynxVU!35*F|rjP&!l8Ghi
zAb?nk4h>gS$-gUao2^p)f|#sx2B`PWGhv@!ia)nZ?`e_pyP?O>ZElQu1P}|R7QzDT
zpw3zS!$_nLqD;BHyT!bSH{XeGH^iw34reXfALc{IxgR^*V(u<8P|FerH~d(%aK%w`
zJT$*B<K~{u)qi)+Ep|MZ6kFxQU;|)sr39%EQfe$+&=K1qKy=6HTDqGT;LlRFX-xTo
z15urEk2SKaK76?LSF7g3ZNSa2rf82NB>1_p8}9HCY9Wtf%_99(#d9m(<F0(rpjS1}
zPU36BhY%X6d2ddBV^OHbR(2|z+(Iz3S41yeu1DNiT-R&Rs+w=j5GQN69t2p0JsOtw
zZ-bd8`=WTOVn1lRu<7mS^K{n857lbdDv{w{SnTsctg~gr*0Vf5+56NVB%G2rcUHY;
zajeZErGn7~kE>Nv4LDf3$?{w^pNZPsp7z8&vl7nT%(nQ;AA|Wb;>~D_^zM@i7IXcJ
zxPh$T)1w}abbn0Uw%k>8C`S}sWlid24SFZDi5(;#b9OFURF?&wAAUY<9EN7XKFQ_i
z95QJ9D5cS1o&x|V!{tNrdJJvLR7|}v)gA_xqWnL~NzhYjpIT4N5i0pDn}Yy|*0|yJ
zycgVMkzy)WWb4GsJe1Kl?AY>AUhy#gv`aB=I*LceWiJHw#Psy(yp(lSi%;2)Q#zcH
zcA{AV9=4d6r)`Y<*wQe-&jsd1ZpLyy`C-k91r_<JX%AL#FYKPh5&1^C?EYS<jQm#X
znWp02V$VN-%*_bG=OLYija0AAvsF&Ma6in$1g>zrlQo8JwK{6Djx?V&BP|d}THB7V
z1t|MGP@NFvEh&_C1|+Ym>nz{<c~0@XgIpd5;-E(AGH1D`xWI@o2C^<Ax0st|$s_uh
z6<$n}`+TL&1OTLk>{>J434FtDw6`iwEc+qms7^MCS7(;Uv5uWd<u!c28SLaR)mr3(
zYE{=*u#oq=y)%<ugO7CO_2Wj$CBm2qEY=$_^tq!8+f)UK*r%R@JWbnUOb2>cnx=l4
zX(<TeUYXeM$aj>%&&38MYF1jU%rc6@KDHLpm)WV$Dci}q$lw5Tp8<t<Pg_$0(1!J1
zBC2nZy?~7n8bJ89jM)GssWDb!GFSYaV|O$dG)diXU4D7?a2k~wtz*ptr$jZLp%w?=
zjpF=iChUTI_T#od74~sdT%yDgF?u?!hxUA^B-e@Q&DZ#ngDGYM0naRS&P-+5++SX6
zQxIdN@UB*jjP65D)UBNEQelql5@E#Q{LHZ>s6>B?8#ATR5FF(F@*Q?FQ=Asv60c4I
zBiot71v`}j&y7u$s4wm(nF=LrMNqOOCY3fX_M6drOe0(e-A57*LX*?E$@2STy_HW8
zD+!tCH994c^N_$nw3yX;jg{7EQl%?t`W1A1w=P0T_n?v2?cN(M5eMJJcNnp|?I5=L
ztP1txK%-0e05L;t_ly=TVzy!Hb+$aJiQ&(p+Y-nkD-v1AWRw%8Q5zZa5@Cz6Nx%%G
zI4$ZCniPYWBds@#=+3g0gTc3k|FrJsU!8{pa|rgdV{W?+!(8Lzbo$5N!0+4CPN3r?
zI<u*GOR5UjBDXr<-6OVQYW56QBxh+-PLT}db&Q+@#Acg?MTNMAb4Eh60&c!npzu$|
ziEt%SNTY}}M1bu*1H*KEI+truL|Q3%_HBVM=I{xDm|G>di}XCYmk)Nn<J$I1kvPHB
znB1b;l^dya0vK&^mtlcqFmaZOlWu4aQ%XyG#2XHMU1@`R1PMCimqr!4&t2die}$bO
z!;?Ih<!wZcdZa^XOXd3v83?KxB{p9{aGd(Ihw0PwBhn`0d8X-b23(FZFVTOExP0#y
zR$sr9s_ld&YH^H}nmMP|3Oyg+x5kXfg$)4WEr3HB!oAtsT8&}xG#m%1Zjo|feM)uR
z%*}8*!sys?k1Y?7fE_BYL$s|}_800)aOokvJn=TM3afiK+Vr&c60stk_vT1)DZr%O
zT18Iv9|ME35tbRo2G(@8X3LuLGiXq9M1}kbg&JMe%EMn0bOC3#dp|N+HY6Evf)JG{
z$*NN5F5sbQz*!hjhMn8k>fCaf>7FCn9#@zzyaIb_7dvE!5FizqyN3XKfH9(QGyKS9
zg6nMpw<UBSqB&CH$e|QSN)Cw?99FAXh2xIH2=~KZZ6X|iD4~Pk3HLE5{G%{WSI;Xu
z?TV3F7?InT!%Fg5Bx`0jiJ?;VvH`1>p=)<rp?zL65`|-FvB5XB11;%_<78z0!uO!&
zN5SpZutC%6U4Npb&aO0eFGFpdimqDUy^{TLHL^Inrq`7lwB8KSMQjsUe282=L?0sI
zl36C@k}|%NpV{(nhffY%Qgu7xjQ{aXh#1X**()Ckw@WBS^K#)-s@!Ktmu5kx52sAb
zkRxRaA(JS!=~bOUh9fhC6hNcwcw+=>E461pfPj!x8`XaF#ffPcP{Shv&YX&GvMi7;
z!y^O8(L$N|T};oJM@({$hKvgFfKr|wsJuE(O#0M|Y}^nOY6>0Y9^FnGvao}<aSW$x
zD}ez@e<MJ@qSOgz1$bb}8_C+!-aj!1%v??u$&t?U+5hFto6c()BC}T8#K@AdY)`1O
z&fx@B`C6!t{N&Irj=wOI_7qg=munPTXv)Si?_#tu`L-@V^4K=CF$CzQNnsYzse_v#
z@EUW0TEhsyYxU1rEZqGU$1C@@eC_Z~)+N0^x+t{rZ|y-md#igUF<BPJefx;2Ar95w
z)}?3zt(w;&PdYfc3^RlNC^}N|;8+c4Z}Dk#%+fzMleu!s?U5<Iz}G}NLvfSyf1NfG
zJD^QjXT3*0kYKzKT``h!#9S<{{ODPbG>&lfskk)ow|ZBTwjD{Em?pKKFRL%2X#KB}
z|2}e`&Vr<5jfM~V6hO^UlPokIo|a_;+gPEpVvzFHB;u>5hU9f7Z7Kj@P`T_HY8lD6
zIUF!04#OpevbP`$^e|t20Su)t24R?Zj`aoyXS{B`6g7h0BV?)Ta8V$hH;xGetjCo$
zt;N?H0Pf;ugfV+4$I_<nIZisxoNVXF;tRJXq98T7V(odwg`?pvS4zaBKxAG@Ojoze
z&hZpU=xLV{Dl}!(p0jO9=5Rj~9vINaI)E;pK){zEpFwQc!1d^#(!b|(r1(!t=2(Ws
zUkc?p`)*S=FFAYj<bLD0eiS{C)wMQM0*mk`Q=-q+YzJcy3E}c(OnN#_@yx<l9<IaR
z<z-smrqK&0zz_v2{$96t2)0hMq#s~g6WxZyB5%QhAowHB6G^vV6?-Yl@PmcSR;(_w
zpEk^=+fcMMujS+Bq%8)^0_$kfNk+;f7=jM+_6sXtQ0it4gm`j$?XZ+FJnEfnCAl`8
z+CLYp%r?xruOkWLT%-`A#!5A+gjs#wo}aR50(E-}JO&u65KEK&LVJWzJPonOCmWQS
zI}SQ|Ie1vXd*N)4sY^4m4v-{>+?L=<ist@yE-|4DE~UmKNex&JBh?v|E)-`sc(X7W
z&pd_06>hcS-<PKc6oXHsF>}*NvC1x<*EAFcuWPFBE0I6cV6C&O&|VmWkd|PPj&C_w
za36N`A4L<b5@R~94@32;lP&tEFM5$Z{!`R!?R7TIu98SP>@Y<)OzG&;Z@|ht<N5u{
zfgxK}TA)q$xWDW6O2f;iE6Pq9&(M?lhJhH~cuE{$KS)6O>UR&eBjK2cnUrM3auYD~
zU|LKB+EOO_vcrx#u5zi#ju~=H_l&6;7FB;B{m$P;Fu5+K3HD58%AA=THTRG5$gQ;`
zp+IE;whiMZvoJ*9VP<;J7n98fWygcYehB-F)kfY_`ZRTHLO$=Bj*LVz@i4P@DH&*9
z=YaZ9HDreBR=~W!$3tUf{oRcq?=!gi8XlajF8^{)Khb~OQwj|}YkOi>;o?LygExeN
zQC*%aoY7OP(Rzz#W}-j;v#W>An-)GDm!I%+&hZyfu^uJf^9iBA;4?bXBI`M`WY;gR
zt&gJhGuQ?%lB)3|r7_Q0Sn%n2*Sqb51<-l!D?0pH@~^0!`5;$l=881!?^coEp_R+=
zNJmfAE8k9@YJuL|LoA{Sw+3eJW5z}--4BAOc|ndwstYs{g>c6@?KJw`V<aeA44z9B
z9^KYzzDgW=IBC$SjuWS36kKMR)<FXR`$JB+<V@G839c{~kKLJ@ldA64I!{l>N7GXD
z-E}aX(SU!hnKAd8Sez0@?Q}jp(=5sb|8R<gFU&R!T3zwKW)1+n=~3#v5DuDWp%Gv1
z(06OQG*)S!weKH+Q1;)4{a;T_^K&KA5F9bYsklJ;(Nzv`w`K2PH8ONs8Qvq>KUy5A
zB)~1JYX<4UOp}~3jL(+^nm#L|^F73@hK?`eKZbUUv{Jj0GnyvDSp=)S9F-b$;Wx?c
zv>zs3<nJjb#CxlQm<swpbNeMso5)+g<o#VuJd<VifgvLbJY6bh4Yn|VB8<DK53S?;
zQrcI_&i0?eBqrt2P9Ud&DSFwg`NPzkO!Rv1W`Z^BP)M#`-0nKthoK9PhtLgA3q$Sb
zfF+>W6M1#nT+(S#m@d-*Tq#;USfTzqaeuRCA5%h9TLr-EwjCSGKny!*4GI*APy35Y
z(P0FCx1K;1TM9u)#ing=gcP~B5%)ml&Lp~2y*JckfFHHLVtyzxYG88D{^7x#9KACn
zj$tiIfrl$=LrtLq(!YUN)chKh4p}SH#+fjeySX8eC>@vl`^`HQ3$`2?)2;?2DMWjK
zV2jaMT)TZ6SP}CU_ZZ@leO2jOx9x{Kg>jrZbnQp3S1(899stZRx@FQ}9uMB@`M4Xv
zn8hjW#-&bn^aOBzq{bb~TOwU{mbyKRvll#EdGo$CMwPy-zQp1s5b(K;;1LvWLK)%W
zmb#jPVOs2m?5CzKE$uFZ7G38v1%lOdu-tU}E~JY<#L@ABlf&kkhlaaAF__ZwA*$1w
zS>E6YPTe^!3rC6e)ta2Ft~)Hd={<cXU;gfRMLy9q8FzM;Z`H4~4SUc?>urGGTKjm9
z!9uM5=#z)4Xo_oQs+s7!RR_J}oX)Af+5<#u$eTJ(7sI_1>T#zNf0xG8GI=;vfa_xQ
zDx`mVK)G8*Wcc!P4d9xbuoesM-D&vgLEoF{Jv)$HWg0<YFi8K4uXhX*CJ44f$L2S-
zZQHhO+qP%EvF({}Y}>YN+xDA#cVFz?eeZ7nsOX4}sEX*$&dQUOdCp0&wT)-$iGwVg
z<xgJF0l#Rrl!#Pn_QNb*2lU+GhAc~{QDQ((oG;7*upH)1fywYBj!_^Fu)<T*(}r*Q
z@ar<0Fb!ywt)<h#qdeV#>v9p>Gdki<COC@0=R8L{@{0&dS;bSep+nGUYcQFBl89i8
z6hhdRSCL!Clc|_xsz)07Rt(46j;fBHykKB6R#oA8K{1#=D+w67U_X}jdz%$Yqc@KJ
zvTTzi7G#jsd-d0J=df4JN5l%If%jh8UtK3Uw{|*RZy{MzN25YjvHdfY;T@TJb_mIK
z`YL}^6_(Shaz-{m3mKlWT{UAmCw}lYiU#?6DCPA|`Q#IV%+}3dE-vGv$@ZYW?RSOy
z5T~e2N66L@XtOgkFAqP{QteeD^KrM5v#ChSIc=Q5aLJhb4JGh!lE2A@9Z0{js0Lx)
zlco}#pq25;7Gz2yX4m(d#^degTL4&AWow`*UYsdxPKh^-0aZHFHNmJGw$5UO&ePO3
zXX1|g$_teXtcHD6w2?8SxK+-;wAC3sK=~sN=?;cuPGG*C_8Vy`1y!9qrMYQ^d(k*q
zt($3qcz%6K=ZD$nk9Uvm9s~AsH*p1n$#7@1EiSsD!Qz-ENXysL=ge%4w23(@1Xo^Y
zmM>1*+RdR>a3a$lmOKA4D<(IVDN;}G<+)SUO@$ns0X_Op0~zX~mxfl=5q5E`n5{ks
z*=_)$?5a-UfM**$bo2WKl`%;y6>iXzPm_7T@+64jVFw98+GR1RG97syG>1P54)AT4
z;>p3f0&|ST^;3N@P|E+%MNWY+lqqS|3+}REDlj+qAtXkwMkD)i;>ngsq_sFtHm|EL
z+rV>@q|C`BY;qOj#w|n!>`bj1q2A3Il88=9qxZ@H#?HuL(uhy0Y~8`bX<ELBZf6Bl
z<1f&!o9CP72*-TxCg|+dPdxV<I1jO|2>H^%?i3~HC7KwK5gRhd1vLk2hRiXzRIwx-
z+03E3pi}ZR1eyOqnX0FWg`t_;+VgN1JGKF}n=excGv+Ja!};SKP2V{qi5=cWdKfN{
zis%=ak|SblHF6|=775oYfxux7=VK)KGwQ!CW!^izimVw+)P<Nw=L%B9E6XU(0@pyy
zX?Gk(u700EIR?pQ0FH|9MK3>rQYHv@?@B$t_**OhcT8#yz<GzCtnk}%s>Qo5_UA;j
zR_z-ImEF-};K`-npUjSV108cj=Z;ej<FgiQJyFc&*bB5F$p9(cgqIqyCskDDW9^v-
z7wKQdxfB$K5VFF>6p?2jS*=s>uo!<)6;d=MsjjU>9O89uJp!Mk<dh;HH{S~{B3hfF
z*J^UMPl!O}EHQn5+f`EDNVc;!&z)ZpG;Cx1Olcr4gN4}-QNw%*Y4n`cT`%M0M&p#I
zuLYoS@Q87#djf4PaF1R)A*L&m<L*3(^*Yv9K=2*6D?sFFQH`BXh7SmojrYJ=&o#88
z4Dz|Qp-J>Tqm&=p)!dy?^zkAW<4JX&tllbfHY(Yu?t}Ry<0PV^>3>xGR$#soORL;E
zH(|aT{#mwDtKeV76pv1;hZpqE3_i7p4_}JyKA7p4VdhVY2iDP=;~MMd*lOty`~<Ai
zBLk_eMSQTt{EffWjJpo=9B|^1D+bK(5#dX3ugi<|SvJTw*dNl~%S4w(tUl9ANbBfH
z)w@CD<223})6GatdlU@rlgm363WN*DL*Lz9?VTts%tonc#{*FAlJ}0E0<3>oWxcG>
z+hJ5Ph_AXyup<^x+RH0yyf#`hLU^A&?VWkUi2pd-gpoZnKY@Z=e(#lp;gzX{@@r1l
zDQ=?sz!E2fr>PY;g?Io@OZnq<Q&Y}y$TC%%ZxSArwZ?guI=LrePr0{|KS?`#qZ0i)
zwteEx4n!xmiVp_j4fsC&s~d{O#;df<ap|&f5;-2adh^uaHdfZ&C2pu}T)U)PAd(f&
z;>%d_RZkmdD?F`4@hN}&3HkRROgye6T_i#uPqEJX0tG_1=S`7|n|EvFbGCE9`j`2G
z-7FBw)Dx>JozIp>7VOUyR`7?8R>z(2+Zq-R{3|Xm#2SkTww@C{dvn?|uU8>|&~go?
z)-#5baq5M4YQqv7(`Z*XrE}-m6)Cju_F4kx+?$va5h^xjh?FT-J{aQkTqL6#7!oO|
z{}YRj6N>M5YpQ#!9~>yE+`mzCby-(aF+Jm*-}2|CEZ6Mr&2*#|nQ&pH#!I6Vi;lxu
z@h5UAG&pk}ljGrh!J<rR`z(_4OhcS;A;6$MA8A_Jv3d_+lSaI$SnU`)wq*4A_XESp
zM)X92pYJ@%i0Pary$Y+>m6mo$fk@Z9a>*s!bbhHj869%KP!h~kR{GsPtPPAT1NM*h
zgkogV#+ZSzION@y9V&xeT-m07agElzkVn)*u9(HS)9=J$(|54X{y;O$ra|U6f#Ol-
z+mos-Qqp?%xkSgquCwB!tSrl%o@D~tfF*E&M5#{ib+bvI%ObUwnq$mk%pVlFJPj!&
zgfFnZ(M$Y8iXyA;1m8n@(I*}NxJT+7d;*C}k9plIkw$n4yE|`P)F(A5R~}pyZDpD`
zO+$Li<X$nwO|AlJ`nw1jQxXt2SXvJk6JbsD>=R9kEAoXDb0Yj6#U0YCXIT-<L@<h&
zKK;PzF*6wd8N6DCewby^n5fT(cN+i_zLUdnSytDNL=*v{owM&?HqUu1Oz&bYTjA>S
zmX~RK;>y9n;C4(K+z{&-howoFr}8A+@5y<640jNjRKl-w`}C=r!-<8su*(YxB^#yS
z3a^xS^?LrG-I=K5>!Jl9X-&3C^Dj2nuSkdJ!bFYk?uYkG4^9pQ5A@mNJfuhr6rPuC
zfc2}BTw(K1^mq<LcZ~EpGlr*biy#vmQ~CxkGmD8e66vrxe(A-qK3NQ0a~itVH~Ii1
zE7AZr*-M&O_<)dU6K6Z+gKryXv2w^0?x?12ukVyvWU$@XffHnV`z3&ptjRk0Ozxj7
zY2e$+pTQ-3h^iD%l*oCS%q%Y(Z-rXLNfA)zo@tqY7AeqNe>daNe23Q8XC?a0M6>9K
zzOC)NA?59()fm#Q4LdhnGyYbn*e3ec;~OLgnHo1Y%J<V~0+N%tL)%#9d@z`z!+(<t
z84^ln=uJt(Vco@-B&m^{hKwW~2)HJ!(eQ&z!qp<RzjBVojKFO%n##XY(mMqWeIj&!
z=z{uT9ZuP_T$J|Z4+>pnPJs-b&qcmeEP={iICvIk9tPL_YqGLS*RD%&mC~KC#cx7R
zx{oZvco_p@XjpqPaN3G<GMzJVeG|(&a{#o=h^%EeS|Qan#*F*-kDH^;cQB{$8VA1p
zs~%Er?$7tgV9%jVako~EF4k9d7xPD?c9S$BnkoI+i>G=Yz(}Vus!`+YnCot{O0uuq
z2W3$ze1Rwalz$_JF|qizf6U7T7TZELsA7xPvX-$O3g6aOji_cvKnnxEFbfp;gM2p@
z$8=?#tthU*R@;6rgBo;?j*;IXHBrbSDcv5=<xcCQHheQjvj-YVo_VsJCM!D5s(J6&
zp*(T7jNPu5Nt}p^OG-^yJm%wJRhgKib@em(ZKHMUJi%0&T-svle71>=8p@&%ZOk@<
zcPg*!v4UxdT{4fHqUr3%Vojxve!L`mSped6-j$5VRz&LjOlurR*J;^9ESCdAhFF4O
zOip+bjKoZOYk=iraS>MSl-Mj8&lqItkTZ&(Kz!S)D@hL=81<wr8!F0H+x&JTcE-CH
ze0=HY55sv<;4%bR4o@RWM1C4nw2^kK#kALkf+?g2qB5Y#rhGIL^9Y1fn|BU3Qg$KK
zTKF|E3IWQ5GIMBBuo|rylvkKKk9vogdX)cs?4C8AxO}st1dcM}hz3EQgv*P4gkYtO
z1Z^KC@h)!b2wvCLVwBmXF_ei-j1-y)w^>h^j-IABd^}hvQHfMq4Ka95B2rR}^Z7BV
zb1H`ptIe$nBN;Lo8)ROSxoTSL`%Q1N`4Xayzg~L`FWmYQm+$4ZiL8Nvh<d8WV+<1D
zQo9MrZ|fJlF*ELTW@g+cE#wAaVR`pEoTol?N?4}t-iDV^2MB(~-0vsj7)K#eFMux$
z6mn>=ryF_>{O#R(Ot$albWOGHgcLE|PzGUdT65zhA9RA1DcRI7E}(+H6V7~4gS-Cy
z+?#X!dbd;^?+C8mD3x=Y{ww@*va2|FnZQZ($4I!G{SV@@TQE^Mh5|p`f^@g{Iy<}U
zfAQ$0O(Q{>m63?reOg7uj0f);=E4~tOvPeu(2wVLUEmJqC#kHkcW4!*2tO8^ii{(<
z5H6TlrP2c1jbe^F2aqhmoLogFH(b+QqbLt2AA5BMtqeG8LE`BwixAuON@9`CwusAn
zLKz2Rvb>P(H+o6YGsSnI+~cGHq2k;$UF04)PAc~T7@$TjB}eZ#6P&;lHk<iW>_hzO
zUB6Qc!Ut>*I`HJS=fop0He@uD3L%X+qxJC3K?u?gF3{4Np_hN&pJVO{wJlTGsDYR7
zkEh3ZZ$@w#ZL~v6Gp_{}&rPpWEmt<fkKdqccnekP>k7vvOO)U+Q4WHNOkIOpBHGf&
z9)fVD_yzLss?TCK610dj-{@m6(tcXA3r7r#*>*4TR9nJ28P=M`!b6DKcXH3a?A^S$
zB!!AdWxp!8i;bpp#&;e|sO7U35_E>P1(zq45=98PR;N%Up5Nre#%g+WQzc#H>8{VL
zrM`uB)t<B}H#BI?Y?CUYzwb*eA|Aa~7ju=U*XyWco}9%C3@X#$L|K}*aO|s9wu#&<
z1Bzuzc&1ag4!JEyU$fA3YhW&rA=u*{!oqo5$$HJW7mk>0$Tns-93Bi0TSw=CFMpFN
zNA23A@4*7^4KQ5#J(kUjM_)bY71%OO-GomOfi#PPTXr(NA_|)*!MHFcv)msi=ebmV
z)zGTHBv^5VlE$+;0l)fq#Zpmw`r0mb@s+?pw#5>&rfD0=wG2cVM(MplRk(Tcs+<9k
z17=49GglI}r>ls|oc-#@x)o*kt|NWmLI&++D3~t%aoXa_^NYZ~*Dl@LCt=SZVUWif
zb&0`4+%~Xm)rpJj3K4&tM&tKwZ_ea{4-{6Jw!JdIkxFDSmuN46^=L;J?}9j^R?j!4
zuSd=9VJ=63zNDuWpprZbU0G82X`L4m=_K8hSmc6EbR3H)k46DEK(tv*1;Z?G;rsW4
z*&G7PD9Hd1#)Q;lMG*Xam^5Tv@BMO#v}8kbe!xlFu>&d=H<8P-4c>Wt_^0_bOdUi2
zqGTp7_*KsGLh=VBu&y4>?P8@<HID#Q(gwOl{o67RKEUoEIr>?!b1D}ooF_{>a>Mi<
zUSG>B_I+h=6ZyvqGD19duC~MmfQxEG#9pL2$drY%k6C<#U$UK7Zo<jBNF@vm&1<Ob
zIT(3~CDBdKv^_K~;v4mv>SmW}rp0pxkIa>@QzQM+GWk5O@+)!4D2Zp`dgBlbt93{G
zS|@}657BQM{Bt{lpFo5Sz|>c3A?l4b!F8up*#wDGFIcx(C)>h*UZRY8UA+<^`zyqP
zGe+2pTa8Kr<^V3U?^#hyDj=c0x+@)TDJjw9g%LKOA%~GI{26o8L<sOItO(_TdoqBW
z<y*vlT-p&?l>Ytmwo^5I4GhE|BC`=r-iYz|tU;=mq3TZ#W^z9ZHWV`TfGqJ--Y2cj
z@x@OXFA;8t%s@94Gq03A;+&^O?gnd3f784~Ggt}QOM|lx4E3F_07Wvw@M$YU*4daJ
zKp|vVa8x@7J}9yl8BA6^fzXI+v`IiEFYO8{0nK4PA;r4K!AX^um8_v3)F-H43}I!Y
z`0))R?%<Ic!@leh1Uas+{z!sWQ)xtvzyT8j*I?l%1S$}vLuR5B?k&fC5+Axl_#xbo
z$m36kax9N>r5g@8rFgcuMzP30xi&O6$V3CxsPatq6?AmTxwA3`xm78ALX!=KH}4A5
zZn$S^%iBx}x?jh*^CbL%$2E1Wyus_bx>ff4^Dx=ZCCVi?4e`Jec#HTR^$p>wC0LX9
zIwmS)9Oi`44@tJ34KdA+;&b3;!;g7ypz%-aBHY5y8NiC-Hj?S2$AN|(*8q$J9)YS*
zPr1lpEujAB$UmLa7)^NVMRcZ_e|+E{{mqky)~&P91y&c8bU&Pw?JPzet(w%e{o_Ly
zWi!r&=ZE&6UJ=~@pia!wEPX?k7h1atE)-s(Z{KA*RgW4o?g&m>=lFYWtc|`*ur&~x
z*(~Y(N!Mu@D6$2oW8b}^>~=@PJNZlVeWh%*d%McS%4H9e_K-uW`&2E!$7)-f0^~D#
zldYPq3$UTqb`KE0%p6AX%IxEMtA$S*`}&J%a+S(KrSYBq<gWZT&mAXpF*E1C#jcUo
z81hSu=uJY|Xhz|oGG=902p84*XJ@w4`zb&q&iGcx#%?bs*<zlY^m1&~kN*~*Qdy=R
z8^u0;24uy;vU5<^{0JK4W7(5z2lp+k-UDdI?0eHOYzZ+oNc4o^MvUBG9%*~5#ijlC
zadaM{+~0}vK|Q<~Yjmd-oS9-(JwC*L%E9=S+ov5I1Fu1jM?EWc!vhR%xc!&66by`a
zToJVJ<X`hbAB%4;vDL26R!#02>s1yxTnTEEddC>OEBNGv)7!W2<t2D@C_3f?^o(I~
ziZ&@K($6x?XFHmc2B63P6p>oHEO}%k?)Y!d;_CBRCPY*zah&Otw4Vkai3u}4*-X}r
z73Kw>#f@lJYr@1qy;W*21T+&lZ6B*><1F%=g0p3i@JuL%Z%E7}{X3HZF6}B&RZ!rl
zP8TFFWUE+SL;-huQ3sLyJ<Oh|I93(yc$znQdhossjdy&p!(8?91i5h_Dhc-=9+u?;
z4CEV8J}2{k_?N#VS6I{YoW3l_{iXLhdO?<RU1Lf3j5PC}%1i$dKJsyqUGg;;lxw>A
z>`(8pKYB%md$ltqd|h~(SMu(us*;yLD+HhSOv3t3I%t0*irmWs7Db>mL8ajx?Tyrd
z#=b#<84yhgOo9#*ef}Joj9CNs{cwPj`b=E6<We-QA{DP6lQ6LtWFyM$pZvk)9MQ0M
zl;2fj9FHi^e_9}`p>OLs+as@neykE18WS1<q@YkkHLcvoIf2UZbQ|dMPAO42k7}5)
zSmfGzw6A-GxwTs5_eb|+Rj!a}CcDkpXTa=k^U2IXPFA_Ae{8=%j*x)o)NCX@#yG^F
z>nMHaEe1Us{u>E_=!)><hd<ujR!L&gJ{G2#tU)kqN&EbO01}oow`3oG;}V#nVTH04
zL_;7DV;9}DR|2I!7Ec%Y{BT;jOmSVXy9kmteO|;DQdpcaUH_VNjrD4CF5CIch4+j0
zAm+>yJ7OoB9)AMqazdoGp(E-&NGZ4R!L7PL+oA?N6iV63P&Ekqiy0)-5|+7_XjGJE
zMgTNZDkMJ5k$5f2iN=u=)MqN!Te;nYMm>5X2@XX#wIHu}iSL;iO74%*QLKj_R7Grb
ziT<qjX!PDz&WlK!Zhd>)Wr#(?0Dn+YoE3LVQ;EvQR`?v2yH+X*r(=}dE=Yd-V}Ku5
zhOOl>$WWD;$XjiVrlV^J4-?upv8Y&U;II<T(T!Z82AZd##U2ZP^?Ya9dy7h?g=AEX
z%7TJ`3ZwW-h2@rMquZ?8-f8wpG0lYpR`gl@?JW~0io}3(x_3@s2-_+6{wUtm^-HmR
z6_HvNU!GCB8j;VxSYDk<?F-r&^f0C~^a9IRW_ir$AzJUVf%UySJs$bVd>=$OC&U*b
zc>W>_?}nDmbhyUjB!iy6%xH5yMN29Mi|~RS43FyDqkTJRU~{7t(m(-ieI=HOQQP7p
z-=#e8rU0c;5c1~?y!-Hz8h60jjh5T5ZQR&qHi=XpKsK$<-&ChwR|csq-WYC@((^3h
z=GsG7fvfbW(dGQPCxFuB4^Ck`jy=15<+=#K!YI#N#$hkJQtD+mCfMA|k%MWl$<7Mg
zw)fDT&OlDhVzy|O`;IxCrq8xfpW+{n291lwNa9m+egp%q($%i&x%z;ysr0<KLs=K*
z8G09ME5)iD?jZu$-(|aheZ>obhA1NCw&v{qZ83_K28B+yUqt=p8<BEk<;vtk5)b%!
z(S+yL!BRN$r<&1C>xL7(NJf;~%nuGA$(H?)w*H7zAXNhjoJ!M2{L$)AV46DuJ0Ay%
zcDds5F#dd)4WhPjATF;_8;o_t;8rf%K6o3=BhG(8#urtF=|ED{F|s81b2jWga(#nm
zZ70Q11BlxqRQy(3Ib>SN3z<KL9S)enmOw@jLZ^DIbdIAYlTL8e%o&CB(dvOcP1i`l
zFOWJlc{F+-!{)M3iZ#y$VoWQex)Ljo5Zhxg9^W5@EU(gfE$L>-&k}?1^Qs@-Yw=H{
zvwjZZ;4>oL%EfT1{u_d^Ygaq!=0&R-PN082SqHC90JvQK(t`*)qpieCp$-2&rTQ{y
zQRMl%@`nF4yUMZ`UGX@7knNks+RE}?+DEja*=yMqW^1~+GbdQ2j6u3^qKhQ5%Fg_d
zM7!&%fO6Sg7^(}HX72<`pOe!`lze)TknCnrr`jqBwzFW8a#8}{E0Z12Gcmbpid|&d
zGRnS8GtN#i3R3f&lr-Tr%4m<+%PVN_v~W8PBOQT&i*0kgaW9d7uXw?#4~6(w4+W&8
zfJ6ruX&NKu9xF-+0HfRiSYDj9`A%mpl0iw?J4B8!Q&?+~fQZ<B<8;E<uge!nN<Nx(
zs2Q#BO5$C^q@9qD^QANC+94YAPew6tL<K*u?%nE&N<cdgJ{%Spir4F7RY~Azu~w45
zY2>Q4NC%vY4~Oa&&L+1!k1+oCpXO~KEYDYkH&B_B3iqwzwo};|sf9M9Zx}p<s(<~o
z6J&xWmEN6?G-d~$2JusjTfcJeux)^msS!C{qB5ee`moQk8j+hRS}ILBUDk5~>j1hd
zBQJI)Ec;RHL{#LXel}Gds{7hDPwUaLw_5*>aw=lD7CTr+$ON4#W08}ua)+{$OGE1%
zj3)V*Z2p#`nN9v?HD;vO2u&^V5lKz?Pn)>3^v}9!Md8zxr-*nygTzwCgHH8}b1lxz
zH5=3CVA=A#wolY!eKGwLSPsc1+1VPu9-|&4vNF2u&-!)MM#ps}vOfKN24sW9^c37r
z7-+cCHMn@yB3x-j?8=aU1v~?zUo*1?LZl~|)BAvn9!g4Rw{((nvZa=jjU=d}@e{0J
z7DUTjrrXQHmL6DzbqB&vDO9m(x4h)J+vC#auw2w`C|#+lno5bn%ucb=k&Ul-{a))B
ztz}c+c|V?NzCUWd>HdS<>}@of{Y?Y_Ktmc3Kwb(M1R3BzuKW56?f<;_p9B2=L2hPZ
zOXuPa4FCx8AJ6}DP*H{j0B28AwES10XxXSiZSg-Qg8+a4U~T!|C;LBXYknuQHZU}?
zcA_<Mv~V_Yv@oExbh5Mk|6L$Y(X#M=F5sg&k#IqZur;IRJhi?FKT0cMl4`BER-!rE
zOinZlde|mQ`I7@IUeBCjW+t={>m=)TvBOs2_Ga*~!?{j9cmE;x_>J|OzGYXz%02M0
zQ<mk`nEDC)VHJ;2C38V#z`3Z{$I=?fPP~7Xb8!4^DB5*TmLAjP?r<&``V=NmL?>|!
zWpg#=v3}3`TR3|j>6kZR4D0*I8h;$mbz$9oaD{G|!|m($k)_2(azR4k0trzbm36n0
z)ajdUSGv8Z{&1C;n9>%J5L|ej4B4IXELLI8K}LMiz@z06k4u~5T{5Y57R2-iCDsUr
z&6R7F6>RkW&yf@W1RLJ#LgFX7&fjIdzg_u=eFzKRK|v+h?v0iQz)xou{1mXIdU{}*
z7c4Bp2Wtkw<VqPhC@p?Z^;H4UfH9D>3>M(r7WpxqlYj{I908b|#sJ~!!M{r3oUg&B
zcNlxP7UhJ@=#)l@F^u&q_(l>$fL76s6)o<jG|GQ_xr`6W=79h>gkp5Y<6RUev-3Ar
z4Ehd;%R7}{EnsKteakyClI@Meo7=BA6v*~1d_?h3gR9+<$x~XnJh+c))ys%e`=u4(
z$0?gCQs26p`v#8FMtV(m9X6!+lwxC4<SX-h!saCIR6o*99|X56zA2}Ib~xn_|2hoU
z$$^(X5dfxCJ%x*oU<kvMkP0|FlcuR8Gl|MQdnXF9GjR_WjXm=wo<fdoWzLZFugD8g
zp<5%owV6|tx!fuTrvAYNvU+9#;6w>Y52G9hpr91mkF&w>rh1W~<pNE5cAqYxSCO_B
z3_AUo0GaM<yJe6=ZOAH6wqwswv2G!RZ1qAZVGS8iVD;uPqyZCKrv+T+I_ypRN}o<#
zd7ve4;dO7~h`9HuucN%g&!z~=hmtdZ(VZ#1(h#4R3g15jsVFt}wD=%nnO8I6MvI4I
zc_KeRAl!`zsv~XIiuKAnPnxix3u(_-URy6N>_~j2*Lmj*DcG#c!_JACs`B6M004p?
z@u?HcHCV5X`?p)XUj4*A_Y$si<u68e>Ob6^mQ~L`SRAhSQcxqNoy4Bjyow=FgzM61
zp)d_um}i`7suzU*D};b(qhwHkx}Ag5c$vDj`V5=d0mN;Y#c8G#YYq<FN{gaC%@4Gx
z%xYb^dwk`p9yWpBZf3V&Fa0E~qGa&YmE8m-oLbe%^dXGVoqV3U{Hdep<IS*H(w>ql
zWWyaeYU+}~<%wQ9>;fI5P<FEQ!I+T<&Gj_vU(QH9=S#;{av$Pg<fHdB<J#f6WzhMy
zUv5XLS2{_M7qtED_3@v)SI+sjlC!`705wqmmG?^j|8O7#|6gzP|2hy4BWsiYp7ko^
zf4Yy-1Zm45&9Q_HR)nsPUy{XF;x}N&%vD)SI10H-b`Bw8VnQKAX25A-iKCr`=%zj$
z%nru{VgKmu+jo{cKV63B_EzMkS-WWFCigF3uP->ihMgk!<r+6*K?>)&v1Re4-NugY
zqymaT-IjtlF^yU>?~pRGIR+(2*BASrx~0j8g-dGbB1ytqn?5byxF+UQpN+D5x~R|0
z!pANwIjEuVOM=W(V?81#bKr*9HHCn2pOw+$LAb7z=-CVrjX#U2(F&DFUB}>QdgF=A
zozo@QAb%01BQ<;L@gcMEXKZMu3m9Y#Y-sa_STI|BRw!-0?DYb%Jv!;Plc;4;Hx?-=
zi<m8ku%aeo!pY*Ajl?t}aZZ;YeYfipuyBQMR=2)%naSHgD%#03dM6cK^>N>YvN$VF
zV**~vC-M`I+S@vlspi0rR0p`JOb~W<v@x$^%THO<<4X>6p#*7ZS>F{fTOp#5HFGe3
zno{ECp1n5kEX$}qaEt(!UC$x2p?>SBxg@yDOl`f4DKY;34JF<Wy~FHR(p@zw%+b*d
z_{db0=E{<|D#V@~S0>8Wf*kV6Xv0iUDTCIE<>WJAihreHT`vzLX5@RRN2bcq_D<<E
z4(hUJvS1Tr09oF{zhvy4n%TQs+$f*>(s2He^}Z4y&{nunagy((>cgiRpE1ZC#eNR;
zk!~O*eyA?}2MGNkd%2N;Wxwd5C)hSiUulCGM}dFSCuewb@DH+0bEyj!o3onBkz9}#
zmHe&&55(fd0DW+64^qR|Pw%-Lg%(7$=H;7VJq?U>`)A$h!hJKZ+4iz+*=Ho5u^>xt
zi~jE$GHGoGyMdr?KYDD}sb$h50yzI_7&9}$K_#XIvf=W!fHLyE6t=)iTwU2I3B<&F
z1i+)A?%oGO%b?z_$OKy8-!w(M`PnQ~0vB^Z5f#DlS>=qxq<Ij%>=`Jwl_LI(E5Dh^
z6aK%_Y2IdjlWRyq7}4T#DF=`yW_S~_?jISYis)H=uuvaZ48)1;fO7RDw*9E>hM`P=
zx}g)B!OYIde>o|_OF#c|J!ps&P3^)Zw_*g9Zem~;II<BUniOmFn>OlmQ7X`!AVxs#
zB&=9{dO%KvW*wHq<c63a)j^tr#8Ja}Q`Q0Y1LPEyp;z{EJr7>so_mY?!iIdd1<Xh`
z$54yLlMP+mEYVcz-^}W-Zn<&=mqpoX)Z$<BUw~gt0-s25U3vk9-b1(4ZpR-FjxW$~
zCkJ$FSx*{6qGvpaL{0)#Kr5sRz@K3AUf9g$?h8-A%KshKFu7phBqC3oo6nSSvS(}@
z$`>d8h#B^$(T6Iv>wx!$;gf%90OEGg5kg6@Eaq|#$bpLq&G=rOXx|j*D2ShnXjVl#
zp$oIN6^fTxxQM%s^wdPGtss^+Rgh)hGZnJV$JM;+(6bmm;Chi+irXW3v{ukq1@qY`
zpKe8$pD;kqxPurqm~hi)S!o#|2)LUCgC7<Ovr5*7%wd~#J?+O`5D&6}!bii5;j@3?
z$Ht(8nnjNu9_`f+48#GMl@XPa>jwefG@iw7!pJz50%WQ9)5)q5s9o#{{0<dux;QVl
zp|OkFXwZ@l#voYqVcO|IW8VYo-qpgVQ{V;SCMRl_bPhv*u)Dlm|MCp@05AFw9=nej
zY&TUYc&Y+@dwzc_VXU*RZ%!<v@7t2SNVrD<^@@;7hK}8XQ^#(JGqxBt-S|43I{G%a
z?^U>T8A(MYJ3m0sqh8C9&~<q<dPlmG#q-b>9h8@z;sHViy9Nf=C@BRl6zm~fzDHou
zD{Se3e0@8FOO$Q{uBN6K`LYkesZO*HwzSV|iYjkN<<3ZoDB-HR$P@Lxkm{ZRz<^k(
zI#ftr!)A`u<sL@H?V%G900rduT?<?f&c1;^gsTQNE*+;QkPMCDeZFa%NKj$i4?c+2
zgc#=UsH(g_NdQ(=ZbA?e3zo2Be`(Sx4Z~Wq)nd*qLv<ar$xqWrUMb~a2cQ;>o(K~`
zUVN_X=h#F~-KV+MzhZh2|L8jH5B(8@ug6pb-R7Q9RJ%h;5x~@k1O!$<fSIrp*PTfY
z=rZ%u2dOI4mI9L}5CD3s*u;S_eHS1?*!w!S3dDJAUI9MZ()T$|@j!bcBBp<Buap#X
z>|N7vhxIW&`A<35T74q?*}nWJ>xR*+_7PNILlKlW5zH|{N<AvWf~Jlo=Nt!c|Fy7-
ziyUgnNEWx@+@Eeguq=bUv3qL~D??Tj^R-B|^U)zsWRPvrvjB}`+S35c_FPygJ?%om
ztlCA}kFxJ-r<Sj4ynD>hXy)9pNCGFHn@E*Vi$RRVqSZw(TJv14W<xZyd@kxGpS~?}
z#!fy7o47i;XsTI9E9YK5noDsF`PAcZ009o<mn|?Hh_zA!73*RDe4fW5n|ASFbWr5|
zwkkwR^X$jB)>#NQW;FEWz#==O+v^`pTYU7&jG=1EM{MW@L@hzC%8PsDQbVy1((4u~
zK72nX*K#=ZoEz~S^M*!ZKi};77kp^>jpbwS+xOmL#cnYnE{nOH9bznIu^!>Y8V-~C
zG*4!G0HLSo&k-BH@Z<=y$sHJZnm_Ket#2ud-6|SS>#4?^y|Wd!yq$A&10kI;XcwgP
z{P%646kCvls;fX+uyuDcLBV{L4B4%nGI0Fa@NpuRZc2(Cwh~8qHK4L;jpg6Uw@gez
zw+WFcb2mMqRB%6^gxY0BRBYNk(PM}qY0<;vcZVFo4{Xs*%;g)As~Y`514wvbe{P5y
zl+yedF)tX!zspXWm-V11*#-S?4&wTs5?fcQ+D>2zH3G7HoccBQ)UF(Cwtd#R%1Olt
zyClINi@8Skk?l3}8U@z=0QeEv+}YOHK<%}v9BxQYO+PDeU}evp1z?QxX^``1Gu6N1
zs0?kxaa6P#{UU>D>wlbZvR#g1iG8nqUsdtk@7$}}6Q!37ke31wmVOT<RsRh(o(BM|
z{lp5cQVPk*EyqfrGI^!M5#ke0VIDy!hW7H(bwsHYD<`Lw`RpYUZvuO~>)+rKn8~JL
zpD+O^?HLoL)^Fqr%eY`=`_h0HWhOaFM=)WqiA+J<{fiC^8d}OsQv2zChyM>iXxt}x
zfeZ-%picc?L$GJX!~YEsV*a-w*nbDz0Gh-t8H)Y~HZ+lEupFdExP-rkkG${_$Y53@
zR*3*n#3Z0A8M?2YtDZ}b>k&(FCO|+i{FkmVb$a0qgua*+UkfKk-^q7dq{wkewARYb
zB&~9b;abZNwFT-<#^Q4gwl+BtsPg{Y8x55ZtD!NkeTFv14|e5!CSiZY05?m!)jpgM
zSn+_*7jrT(-iL8|%u_CioIWAT<f_$w3RB`BAoV9)t61&XA=4gcUlAB(4}K?VH061Y
zj52vFS`@X;Plj<Hi+pQ!NbjvH>Aj{KipV&sZcrF^y5#0RgI6N#IfeOOJZuB_U*FtZ
z!~c$c@&DU5XKi8oe~Dc;(*GCqEmEF{*`SB%1Rv!?;2nAM?<%5!LOwNoK{F0_{X3qJ
zH$uBv@S`i)j5H$K4C>kNkAQ<I>u|*vT;75aJtn?j_#Cp_ENZ*|#ajah6(B^w(=ons
ztQJYUf@RzrY(tP8Iu`0(QHK&gM<kdwUhp<8(409CS(f=91sphgmoFDU`rmA{wkbg2
zi00g$=s?z?L&T)NKv^x6cdfZcINMb}4%!IZtQ3c3`OVWBc!~Mq=;!yYh%XjEeG`9_
z7r(7)lHv8Lqyx0*Nl+~bn}E}+Yt5vzzjHeJWY`e)EF%kI3TD;3(CrJSEfBRXJ~Z7u
zibuN}7^oa-kbX6?Cq*~FvsLGLH`pF0oz`eBGPwK&B?9^YU){|{M2a3$ij;1cpD$-x
zyAZ&2kaf-LR9I$8rYn_wC{nR7tUeE#Kq{0lGTKgB-&Dn$y)Q4gF(jmI$19M*FhOWl
zncSu=S|KgfNt59xyh9n<SaarnbeaTZtnX{*xOMH6clK{?tcIhwv177+`yZjdzr;Ud
zU1$uGFlF{8->N-iX_9ETm*YG0pfVSN*F*0MZDZBEXuOES!V302`t@_RVLnex1kcy1
zu@n-uCJS1u4<siiKA~pbT!{8<pT2M$ICp`<fc$Ec06h(a)lw7=o!f#CMfdC0Z+vgu
z{C=}D;1DYb<Q-4H<~97w4g9|nEVloLi4p&|Cgy13War{&^nWok{QqKRT|Qg&ht2WF
zT}00~=-qWkrSpS1DQ1MuOayK%hdJ@8U0XD787d)4B5aY=cPH4%WUPj`hB@{*#t-oP
zfglpKvKF+)Qd`vc@uQz{>7&x0BR}stDPP?THd}074<^18%^&aH*A)dFwlXf0vB%cs
zwi~W8+v!FI>vSCjR8u!S)4o4bA8u<_9}dsUK3P7_ct5@kzMnxBFES2i5$y#U^-}42
zZZ2OOUX@s{C0Ei)$|Eo(Gw>`vX;;;2-E<xM6gRiO=UMc+%h?(2d^x)_<#5I8#x{O!
zi!!NKavmz_^;^cV!`QBG-%hH_PoUpiHE<eQH<6u_+|lU;cPTDQKH#|ka{3B>3^<j9
z7ZpJk>u|+F1s7tPiCAR3Zmt1KH<3~vSZ*{Zdf#^c4v40+*~0emj^mC}rIb!Sl$Kjk
zdV2bvIe~EF{N2pb9w15SrfUg5Sxde^beW5Tcd-A)NG0BM82W8Q;nSn-zhgZZkH05m
zKO8p@a41+`S*8{7u4MONob_~ca%9j>d<Yp(rg<j<o=oJhN(~-Z!-;f{xtjPOw|TI3
z6pUwX7zc|VRe5ZozbfTJss|<>k-vManffv7;r47Ae{{0cg8i!zY1;;lr}-4v>c#U0
zOvrUxD`U@*d@Tw3VO~?xeGWa{Odsb))uA$c`QwR)+;u#A^FZO*fh#ega0K_%?Y2Sl
zFGEjYDKf(K6H)X6OFM-mX>Fs0U(|I>!LK|O;R`C<v}`&j@|w6^t%+atK*0zC*65bM
zymJ~z^vNs%w`Ozntze82y}W1!I^`XpU$-`?27)Z$V8!n?ZSr5kS%x7Ulj=u1V827;
zJ8IrYRYj@4>ZbxAcF|UAbcIfz<a0at8y9e1TqlV?MBh6KDNs85!1E3#N5zy}9wMl<
zoKDIc+=`a}v|fYv&SD-WS1{`$;yMbj`pV)0zb8c`_M>kHlTC{Y0y8JTQNtzOt;Vx2
zU>WH!Hnyjo01OsjK?5KR<rD)Qn}7HSu6&*CZ%34>GO#=gUwz^x{{XA=XP=>nzSHa=
zQy&$+phMcu3uJ~Gws{IGc3;rjy+Sj+(>;M}EX}(NTy=QcXFN$}X}UWrha@<3oq+_P
z4lqHOAEL|}5@_C9Ek^EC8LfjJNIA&9>UA?`#`YSCm!dvtp>axR8)G$)MP6d`TM-@R
zyNZ2G;OWurf{#;IZPu~(U)Z5107=+)-K3VeFa0_LKgN$4lQ}{ZlCoIoxxSgWyy{R5
z2Oc?lS03GPy<3hr_oh$aUd{#C*>_FEo~Ga_AX9C9q<lxyey*Uy02<1`1CAu`gC42b
zzH|j}_BUGPZX<a4P-`LHfH(QQ&|}nnVG@aYeQw@2$DY1jOnfD-SF)XCQC{9O98C=v
zGS?ab=ifgyZfyyj-S*DQD(UZN;G9Zdk|o2M)0Vd{^~FhR=_EB5ish4WMJ=nrHFIs(
zhU^ZWtr@A4`^OZhLnOh(1Dp>aYmSj4F={p`^riZ(1nge|LdL6EIO^nZBG+*Gn#S8y
zd`l58AWYoMPiy%Ch_NhoMp2x`#(5y@kVa&&&eZROJDIXx7n&y2`MAYv<;L_cgOnB_
zR1O^ylK{G0s0SEVS<s&GfI%>yKq$Yoje!GvD#{Be-(}|^B57~na5pf4x`vipl22e&
z_DSa69=t*1A26_wVc!JaWpd*E*9d+$fES2(TOlikkC^Z5RY~3em8nRJ&9NgL3Qm7S
z2*eumB6FUkwVneGS@0~Q5T!BaaisvM56bHm=rk5SBTVfsd!uW3#XApd-Y%}*Qu7pV
zFfTbfbHK~ZLNkDAR@*JK))K><xk^^fI6Q$iz|^g3+zapi(v19&whu6p*pM^rATO}~
zQj7Xb%5A;?Q{4iYut|U*%f$5J0K9xWaO8#KjlbKwBR?l!BXp`r5*_zJ@}j)7!ypn1
zO=B5&0Jbo1vM#E6qp)Ca{K1SQjN#;5{mX$hA-P+%K?}>e${<SAU1#CfF!nA@6$)YH
z2bJ+Jg&)*=hq<^;0Iq(JQ|OKsn2EU#MuBNE$6=G-a7Zf0>zdG8+RYsos6Ti*r-6jv
zhc?&|uCX7K-;YLsqm3d2E+<OLr^RJ*pxh#tltMNh$IQDO3#MCm03|1i4%&e@75uUQ
zzl5=j<ukr!W1d#$xYCc$$}8TSsDXv8zQOa=*Dobfu*L9HgP;d-pF32b`2J!sY!zK#
z-}q3_|5gbkD&>khVFKeQgWbz>DN0u(!fbHy?*55IcZc_e;kWx2epm!_fY%{lr#8*-
zHsIE1QI%y3k4Q+!^o_nj-b5v$qx)7)6m0junH45|BSX&JcYU#c^!@HDC%oMzpYiG9
zeq?bH`HI5LR>M7^pe8O(lNI}TjRt<^L$c(Y4?90^dH_N$z$Ha2cymqU6P`0>g^8Qd
zyk8Q8jmcxw)X;HD7u{L4*r_SWP-V7Rld*;HcOLpOMTD@renDGZe2cVG>>!)uK}&N{
zZtVOf7JX|$z?PI>p@h~2tG4XXG_se6{?7?R38Bk-8sE>P7MPhe9pC&b-cWIR&HT9b
z5O=XgSdXC4_yq1&1ArK(JX=k3)L?dR>T+k)3mMjEROK*fxdz_Q=vp47g<Acv5vbHU
zAr0(*he(qF#<No%B(=_o05L*S8D^t<{Pv{*2+-&xLm`ZPyLuVMpjDvzW(0R!*P%5<
zpUM)g06`R|Ym&xpyd#=Sci7yQSj{f{l4Acvjg;MqmZ(5GLf(e>={bQc>jEK^xMRDa
zdyI~H>9ealc?H0H+99|{;=elrhPY}0`M;u%6}2MJwUB69z2}5fL+vv%G!-uvj(_`R
zU-d9st<O1!RdxI*Fta3b1&Xp2#DqBh*t*H+F}HQd`)!S7p3@~SU)eqWnN--f9niEV
zC3j4xO?Ot^z3NPsl@JHixpH4RT<Q&!_C=b5Cz#72it!%89FlY4gW(igeSY8K>+(H7
zCIg#hE`|&}SDoXAEl1kV1S)n)+`<s%O3Y;t$lozSo%n}z3&}g64DoH<$Dj3U`$c?|
z6})r<S`1j!rt?+dj(uAGItq@%ziIe{&>*LC`L*uJ_#mt)LaOdJU%i*SPiEOos%%|B
zO2>VObS#3cPQ4rsSe~0kqZhH+vo=wOME?*%U}D&1;Ub+CG3pszyj?PlFYURaHtqV`
z-^iQ~1wy5&Y2M5!{J7Cb@`el}x8UsoX<O%oB2j<Y_nmkRY{Kkz&>T1!uXbQ8epL+U
zDb{CbSfy=FwVt?BQ{N>W!P`Bsv|YwN=X0=GR6<70CdVyVrjg#PT(QTV%@^7wM)uGd
zLjtt}prK%E_z(L=6*9Ein^31I9iqVUM25^#iaclz{u*r#Oh#*YMb$eI7ut~y^#-Ex
z(bxP!0&0S_sfBYHA5ulJHeTD>$>M^rX*Gcf+=^j+Dwt)W(iYZSMphJ9T2W{=FMOZ$
zH|FR`k1UpvcZJSLn3HdQ(@W~JlR`?PlyT5%EwIol0hP@38&7H{SG>hIBt1>*3zmxp
zTafb|EcRS_lwJz#bE?!V3x^V+<<{`?4nT#d)8I|T*u#*HN&1KO(o7MDJ~3t%CS;94
z0&{OKq}v7c5$2`z*_BRNqQiUIgdJ6_CRS9KQDc7Td%Iniy#{!FHAKPf0&38<SI`;R
z{%UkWuTR1~rKh=&K2t8arJWm_ufm|DK+6&ODEP7U**zl{+ERY9y=hutPRc!>$Yuq(
z!*e0*QF9ZS8ZVPbopsf}K{*LwLKCJ^&c$eA{%BcyGip$6O99gqn8DmFGf363$28z5
z9OErCbY0-WoInHCy9tqD%mtL{dC6h`Y+jVK3y6oz<M7EQ@1HjeC&IY}@b20Vv_s6G
z&R#eXHkXV?<<%#m$_DIIGufa$uB*i_0}s#Ye6dpX)zCkNQu&AD2o<_92FD)WA8OZ6
zjf8TJY$Ew5WSupJ!1p$KJsaJ=4WRwax8V7LKkgPo+h3}y8LY$n0Xu0@8hTq(#rzhs
zW0TgwE%}8hE*>9kUpGIWbY9L8OQkZzuUhqEOMvEKLg@oV6E+h|8W(c|M1p=1s7QKQ
zjZ>CalQ0wOp3pxx)hY2DS)2vbp|Xe+xh~rLn34CrTCMRm4*R>;glv`Rpvisfhq@=?
z@z}r~rlitrBKxyj&^YC+eRWEIjt|CBM?(fxkYNkfBk-U`i9_two=v^1qskWD%qIYw
z1B?g20#Pi9o&HP<^ye1?JdMF!ACLJoM@*{i+1TV{`+wm?!XEP+>~eylK8#SU36vyI
zdtrBtEaE{elO`a7ugVkrL2xlV<RYZVA=GzsX6HU;4*U!(gvNr&JOg}c`iM{>-J`Pq
z_g0}o6hlYQ6*h)SBTB%J-|M=aTWg=jAxz;N8|(aY>16q(Or!cQh|VjX356TzR<Tc#
z_3cD*5gDWJsWl8JOi(VI(Ot}ovm+Qe_zBq9)qfI>9=KKFfpqt}%k`pLpPMUr;Bdu7
z#NcL=0dY{%q0Y4}`0#)dF|M8Q<doe*qooJR(<ZuRUDhfux;)w}7%pp3&$IL2!Rxqi
z#z7#d=$)}?Vd|`jLwiRcj9O3aM5oDucwr>+h_@8(6W04hBf~z0yED{r7+EF{S#ym0
zrK;BMKSQ5<ebF;Z=S{%pgCXVH20HIHQTZ*3C(-g(lKK*cf&~O&_kQLFI<tHu+hXL&
zRuA~==s$HFV4y~OVi;Qu`)&s~aDkhak$20RE2(3up~Pg@$LxJHSr$n{sK?^4c0n#1
zAx7>K#`Ychw<^JH_TCk4xx&80XPK9ozxoGNlQ(TcgBZm_!8orqL6nOy%VC!wOwkEF
z8%nfo5Gj4(AaViP!i=eNHkN^2{g}R$w%W~oBwxm@XDm~9RXwF1ResF~i|TAA0JvRD
z@Eeb5HwuULVLpf*PkcV_d(+M{=KZlAgfAduN**8S%yT4AqCq(qs&T=|gYqs9C{by+
zMeWh`Al6^G8@F6Wcjav=*J;pq@L=dyFcT@`0rrNW@je@vlDX~I)VRy3MTe=?ORMC#
zRclisS(-AlICs!e3I>n+6gzr_6iRlrs!u$A^ogEKEYsvEqN6eb2|-h8;oE{r(Ursp
z1ad{N&^~&oxiZgNnJ;+W^#&?xYMF($Ooh&Jk@4u#h*?0af>;m46gZX^%_aaId%T-y
z$i=1@#W9K-h5lN*1>oU~12)ZXS>JH?zFJr-N07s`7FV0ZFN<;+-W@X)CE8XbUk=Y1
z-|pXRL@%e>NL5)80qt(LB){xBungc^R+|*#3Wv~?3jIixNK638k;=%8EGO8B_5-T4
zo%cSzV_iiR1>0Am_mfrf`Ut)IeB0hvM0G9pbrS0nod<f8XV%V#ATlyLnM;~y?ru+A
zrM-VMDPrNsu(t)T=8o#HI^*d@w_RlFF1QY^lb>?DO7P8?a<8#pj_0535kfb=@mB93
zi<Z4=OUDZVZ%TVj^;*>QKRiB^cZbx8>))4s6TYN#rNPdNM<Rxli_}Ngj(}ZST6}Ef
zv%M*8(CIuD9F8f#WnRc&+TVH2pWDle!F=YwoEi-lj7v%@K3s--WFZS^XId+V-By!7
zaNB<sJ%LI#ZIBM2z!rjo{!$E+!`FuO<*c<*sBo@k0Jkp&^VtdbjeLIqaX2~@9W?rq
zRcS}de4Hr3s(Ndz4`R^v0elrL<j9XTgE<aVkzNttU#017CWJU3&(x;E{nb->h7h*#
z-pYXjmm5h-J#|N!btvO%k0Iyr^2cg^#kQyo=f36?2Cit|0O06Yv_XW`r<r?9t}d7f
zvigIp+LwHhH)ml5yxAOfTDntqaBLaz&3(#84+H{!GeF5gxjRDZL#*JeZio=xIhgT|
zbH{%TR6CHi>IwCu(Z>4h*lW+B6KTVAn}oi79rg=_{Wd9=?}Y6C^rgTJzJ*`Av!ep2
z;VZ0?3Oh!ZHH<4SUS@meXlx$C(LVGgHgXVN<=_?xMB{|F9!qNYSQ@MQ^vyp-eFJRU
z-B`V1%b`hyo)Zk8x-od=F0rpaFrO<;D~S2qDGYOFpkru>jorV!W7!`2%xpDsjGVPt
zz{D!whot5>9eJ0%BMF5Of720&a00ps!*bxZKq(gHSG;`cJj)8)I3F4tEE=FmvlQRh
zao*<N(b<GaCeNK<b?==lnzBzIg1`O?PR!%5j?b!?^1ZuW5eGpXl@$QPAY?B{D9{Xd
zqBH8#aXar`@1akRb#Id<ni{TEo7tt6vk16~-o>FkisW!mAc~xbf@_t+P2oMW5)n?n
zXvPXo{;LixwDr7hfL2>S8xSsV0cBRJ`QShk?EsO9mPv9cnRXwO7vk3nn`baT`38`?
z4tM>L^pSs52Y&iAhH6kYn|q}rON;)3cqDa}K$C06{Q8^tX?Ify;Io&9+eK)KKR4#x
zsGT%w{Fs0i?_<C=@$Vj6mf-}QFn`9n-0@+s@#u!AoSTk@UeQqmg5#{zYlfVq<P$X!
zqEn_JQ?!tZKo2XXx-`mOuRFs}HqD*#K#LYDjY&qGx5a0M(~ESh57xIp+WFlJ*h6Nk
zKqo=ihSA*Q2-d{ja1k{9dh+1H8(?%;wcvNy+5v?cqY+IBov_KW0t+#bEh+Zoirlaa
zH7$toO1hA9uN<})XSOVe;ld9~@H22M#Z4J2tNxi_Z1^tVbkU8I$d*?NYvw8;NP->{
zeoP^_1L_lS8x3DhwDVb0%~RPuYPpo3*T-}lHieGPiek;OGcMdqb(bsy$pS*5+8~-G
z>9z+9RkROO1rNp3$VjH_+JHj746=8-tskp5^LO<Ov$5j6WnN-^OdTHePMR0SE$F(B
z3Lb|ZbMu6fHm|G;eD99j^rTM`CQUdZj5OG>_KO7GvBjB^%LY;#M3?aGb(0!QgP6CE
z6mMb#7L#Fa55~MUr?FW23CJvZL*52^piW@u5YAYsFgrMt@;F<vP&o;sL3+zK>lsgH
zX)9GeGi>Ul3WKpZyXiDOpo_M>&0~&};yWmEq8a=@be#ilreWJ|YfNq1Zl|_w+wIi0
zZM#$3_EX!oZQJ<f-N{bAy_5Gp+&S;$%CXk^H$3tZ$~_79eYBcyf5^Qs8%CE2DB={e
za{|n9zZby;-CfJlQzw3@ev^2Il>@6k8Ze_PSW)rX8*^(O3wFHS`BEfggT+T$oi~p;
zC)uKrLD#))T<vG~u~^8Z1d83jl3M_L3>k~{tt%2m1PMb{qW<w&y?FV++0WIexdpjr
zcJ(~?_I{)<vd`5Ye}>FKr+y4(dsy>CAT97j)SH*P$x-7SNRJH`zR!;M((CE08+q{3
zo3FxyVM;uyGcv%8IuDo^ODK81c^>#zF#H#^au`n<EO$(WuPX<cQQmM^eyrzNE=IHL
z8G_c|5iztQFQ3G;C~;eK;UW*Tl&aTm+O*^!JS5XFO4<uS`1>L+#9CQ$xR(7&7+ii1
z-x>`Z4g;jPuLrTsIzqRvQBQnHI6`O@b>q%dgmN>3o(>YwRlfI)nhv6*CFY#)MOvBU
z`4*B+^q1c{Znk}%{2baP4m~C{{HjAKxTFy;8#;NAI^!7I<<K;>7(fq*d&=Q&g>D(~
zBy|(vHY~bC*bdU0NFk+1lUc5^KUfsqPOCfQ5IUHBgl`hMTm1gse<%hIHJh*f)@YMo
zIw<r$${`3g*9-0$-OZr|V&H`?<yK#8rlcVbv%KW4kW)E@?GM#c&Rz(OlDHZpeP~1b
zr%TDmAglhFhx2my(UTs)3QVPE^K%g>zX!U+NE{3i6~7W<pDKrR>7uXYbS7URjGNma
zhg$rdZCi<Wx41x$#oIDCGmcyJny72CG91-_-R59~yV+S^%Cm6JELQ~IWpDl4`*Xe3
ze8dwa{S#{AJxh7-+1TOI1;=VS0D672W5P%PS+O{#b{QTSpChYLs+{&uw<zGx6cwXl
z18v1j#(+u5XMIZg21ZK|ify|*8dNyZhNwh>@BLyoLmG^Vr=zmUa-YoaDSZ1<u+Jk(
zYyPeI;TWkn`}v;LIp1D+aw*-Ck&M&$kyabxBaRq9+##~GGIWMQofFrCj-BRXO3O%?
z;Y%lJ^{h1qA=c;ak}D@tfQb2qh}Bn_U}R?(FvJ{G8Jb_(LZEGW(BdNw#ueh2lf`;M
z<l3Vo?!NEk%t@yr@8S1sY^&K(TYfR?=1Ox=2-QzbT)TXY@>Jz=>=eS;A%^!)tQ9H;
z4Pz~JV@7tC|4pL9aKrA0LN(soOkrg77*}+&urkD_z74Ct{O1Wtoo=H(dPX0F1*s41
z%<O%94N74c(lXo?(jwbWfu#}YZ!gOpXBP^vt^4pK=qOV)If;Uo#w%C2NRKmaMV`$d
zvKDD|6uW7-Tn~zeqpyDDg8`=Dv^dsJRjbbr7Y>f@2Kw(vpN+XMLHa2%8<&#=kjvyV
z+rmpDE!Hmi@jZO*s)<!M_j8wPqOP;rdW4KaTE2chR^{`J3-<b-R(A^@jxga9{;#v<
zI`2wuXrHfA{`}j3L@Y~YDm>=3+ciU7)YQ>kq4Ma=X^1h@qJ61uC0i@GDvOKzv0I1%
zBiFj<#cEaanPjPtL2CYuvf1gZdkO_HQqIzA{_gun=)0;^jk+KykK=S`HH=g<1-6Zc
zdE7|eVa$E<1JrzkSOs`ad~C+1@V_6Q^O`gL>c@!%(oT4^CXH7v5OzzIC%q4iSI^^r
zf#`YKBB#}5PUNenC-BUflx*Ns*yKS;^lBFFnW>btD__KaGcNV*cgl69QUB?s4(u@s
z+%Zf+2Qtm%5B!Qm&7er6`^HN-Z$81TyenFvHJsk&f)^;U`Ri5I7j$7iC+i2y^wYeX
z*W=~Nn$Ufw1|WHow@ARr-QDJ`o%>v;exR`&{gDw{_xf3irsL<_zom7k))b;iQV3?$
z*S=e%aTAXFiL954!MlPsvFbmViYcX>FCA(noWs08GIFLrm;D!B?PcuSs=aDq8ZhoH
zJ<S_}`8~^b{6U4{>1ZGJvs0)qfx5nu5pi|_iL?0Fex-Vq!y!5}O25rG6x8tU!*sSM
z!0u7jL80IibnY{-JFVnKf-q=ZO#bGstQeqbwiCsSMFMXBxf6WAUX}t0Zl~eZ&a@v0
zY$|*fTE>JKlnS!<G#RH+k^gM@H(IX<q0|YTiQj@NkN`v2UEGhqFF!&tbV);v^r5tq
zl7z{XHr3D>3zl*!^o{K<SwGrOeWJU>>>^Nb@<j!n8=?@JnibY3`cE7L9Pi>F4MiR2
zZPQ0sxf}KhJa%AWfpfZ51w9+`$!!<zQm83`Jwx~OrtSUq>=N%6*WbHe)!(W5k~)4s
z4*c^@!U<U5cGI7-`R|C;nRfw6!XY27_7@W!t%%i%@)z3d1C^&4q009Gw$8$~mUVQw
z+;43GK-UQV&1QF7{RPCI8{P;`2GV4cvkJ8O>>Ig-6H5y{3=fuda-4MOv8vKd;omhz
zNeeyo6xBP~Z!|;i(_2L!qiBupRyT>QugSeR*v`RIF+So@T0<FoN4hu|y--}Dh<PM$
zt3AMW;MuxkBybcBfI|{kKbxe<gI(UwtvWO^+w5uO(qTJ7wwS32&r85&U*ZVhynO~W
zzv9J?<u~tm<8n3C8mS^ws2$FVX)TTONDK(%q7@6p!%P|N2V?B7`Gs7PE>sFJ6GQi%
zbQsR&&vqS(sSlfi78YAcd}S;p2@3Ml@d2@S!Q;PmC-x?}_13^swoB_SH16N%I=j4<
zy;CsDHyrr_L@)H@KUpa*^pZW;cTZ%>>$A1axbJ%2Cb%vfa7LZBh&EnIH?~rdL#Z{X
z`8wIjqap~B4GQ~tDm+)RDWHi(aQ$MSx-l67y#Ly_MJY9OOGnAA2dR%n{B}deSS0cp
z0lci!KoPTKb-A|ID&8bEVXJUSz(W4yadFw|7H8dt8(stOz%82l?zN=30d9+^&a7ol
zZzHqJf-RwhcIldGV8C<D!tgSqf`y!rsbTKQx5a$~&YS4GiZc<5^<vc*mkoD3HI?2=
z9H8<oR*?rtaV}neM(vhksKTQXo0&b+`3(Zk47UuXRh#*^znF5FX|;by3z}^=YXd{P
z$cK4`-x9uYw?6^-1=A;=3O`lP&A-j1_AVGZWiA+>$ofWPqrNd%yKO*4nT#8-R^1=w
zqBcj8%AFxbBp@m43CSYIO3+g=oq~a83ljnf5>L<uJd@_Oi6q<d&25;a2TLNom*%c6
zhFQ;G8#PY-7wKys9K)KhqMPFUU+KQjz}_Kx!refQ<vBv99p1K<_|xV5qI{@C`Pm2H
z1}etC+7wfB)QwA6!vZx=KCe$D5_5&`9N&8n#G^Z#n1szb61eDJlPg{<+cno*ht_zZ
z*txAgnH2t%@&*8gR_+-CbP);3EFixK4U-Y^?x49*3{#7ghN~J!)4>u6%7d0&qLB_g
zudhJU6r=127q(0GeQaJRZaKn#DnR7Em26Yc!%V&bI6iL<n*7?O_kl-nyFm1p7NjC0
z##H#fHVyC*`O;Z&Z&nY}78nk)a&B&Cer{e+EO}m4brP-+N${>~FgjyDibo#szmGOM
zeu>Ftt^@XlLuU=n3G<HiW0aiaF)2|F%;)$Ri_d}c^X`<+!x8Xt5>q=FYm^Ur41?#l
ztCU<f35hp!j<6GKjeb}Q2^63X6`U|cn$&(+O}hmS=$yhf?{ouujscE<_oAHsPu8qb
z*6prQ6p}m*1J$2Z+}odRr_rw{mPq_6&VPx8mRiVJXMHoj>RgLv7EbXsN|hLnAvgly
z4<JP*Y{HHtHXk6Cd+9*xSSCYq=wm;Mn5Pt@nj~2MRRCX`HRE2DU1EPW?O76yAAQx4
z(5CFNKK$bkq;keI>F+dJ073CAN4y+BrBxguE{C)+KsN2A*ZUH(CZlbDU@4}_WyEE9
zF-u^4DOVocdd=8y9JG()%6#4ETQt$^EFhq&*VnQn|E0!IPsW1_J*6mz58c$P%@3WP
z`SwJy@zi0TsXtCZMIY2fR<?SR(m!7hFoFg}S#s)gxw{+XPT{L^XmCVf+D2%MF;;%x
zSWl;DGNU^om>J51tMPZH(D*R>rz4_}^!{Sb;djIQTfP++6NxYDGUV~%-0EI6D^B%<
z>>NK+d0=W3z_(@r@V?C+!=i&b$3KmvO5icB9*vqKH4fwG+SA;%NN6?eXHVTvqka=8
zRfArNb1Ex=xs$CLz7UW(q)8MrGeZ`VblfyIaaz6?R4CcoFQ&&MBUapxmD+kQpDiLs
zb<@h75cH>$p&$dLmxYrWkFyq_9+WC4H$@St@ArBJ$9zE@n_yh<VOOK8ShFAn98u)D
zk17Cl44W`y*;r5}2?y{GD~!NtL_v|*)^oU?=yN3VbgX&FeY;$I?G#hw&7ii&?}K%0
zzLFFn@T#FWqj`dK`e%<gJ7Eo8y*Xkazjb--(8yXSC#2xr?OB5add=trDg4z|UvGE4
z7*pgmpLD;0ckE&0JuFv(q?#fKcVi5uVlZ1)&QHqQtIAJpL*%P{P7$C4X}tG}gy~ok
zJ#F!xDDDllUvf|q%(9u+ZfbE0B*~juuU>hH_3W3wvyOg@v(vMAay*>0S<nbw_f8&P
z!Zh9`Koa0<He6k>e-MK8lHLq`Oh7JBW+RPzt{TkJk|Kyt^>?3<ui`-1r`RShY0lxg
zAO*B|H`Zzq4>2XVAw!fZaY$Wrd0MyCxKn^ehq^!-v5C6RCKwV<iz$u8RAT!JRR};x
zBq{nR>MUytvx$<e9I~~d6v^pR#j4@X1=f#X$M2f~B>3gSqai5x%VHV&fDrq`dNL+X
zca=zcoOO#cDG|<L(R|?@iuK^Tjkk!H0*uwnUz4~56tiAXh<k3X!ut_GLe51Tw08O4
z=Hk%#C=`c<Am~YLV{PEpyw(&|7?LoWbjJ|pv|~-8>Jk`jvPFyVo+n$=<NN-Y^TJhF
zr5IUu;YP9vk_zcdRv>@2^dNK)BbMc*2i)0eVVo%QwB|1kcYROL<Mm;Y)b(>m@_i$J
z%Wt>s`}4f8!H_Bjhf}Ua{{1M}{s#o-ow!dB7mk}TnUQWM(=7ug{TD&c+n->$Q48Oz
zJs#F(PSa1t=IDzv_pRfR3fr@C=I$VmA~o==%}X7rF~`&n!<5TTap?fYRwfM_Wq2i*
zLEK|p^gkN28%0+&3GX4vtTA89OyDa=)ZMJgfc|4l<+f=g6wTt;eSu$)Jwu7JIaY$G
z2l^sVUcE4#X;$AtN{)frzc;S-*g}KL*Kk>uWa__3k+_?bwRR;rxBj7(-+g!-wgahB
zauSYT-fRf3;LIT{gxB|}PH8v%OEldxWgjqiQ)Em*^NZ5!t_w}$<z3WwleqMcb?1rU
z(7!gRECtUZ85H&nW!(c{z{L(BeTd}*iTF2V;AXTck^$HWV%~0+WV5u%F*GJ}75MtN
z9>HVuFfn`!_Lpqh43yr<@f8I+ssIEP!_Cuw5-<57)57;Bo3<(!lx`<h5L&j=HnUOB
zV~g-_0OE;7^c?a_;8_8>{5{J)?#B@|`Ksk{jAwz6+w?&@{%;s0M!Ql$qoida$Eu;U
zGW#t@LI{Is!J>jFG$Pt*ZpD5+H;|g05zNh4>h<Eo8CLKn+#VM$U5TL7)>@n$^B%EQ
zj5e1F^@807tbwi$7mZl0L<!wybiQX)-8GH9Bz)o;ixF>2-Sy4<137t6<O+$|`LmG7
zkzhQLp!RERd*zpghyhPjajXR!XiNX?@OyjW6f)vrIHOC1Oh0z9SasT(!W=86jXAfD
z{sFSEo5>bmZ;@|RZ&5b#el_Y3>GWzowvm&_rNUOe*83nnGm6->K@Z}a{_^@ItOE$|
z$rrX1nb8PmWTUp^3X<O^Mc4T5k%kum&Cn+fNPrkA-C#a(z9AlriGj7l)0CtL?!Ubd
zW;ZY`(u&|qB|TZNw*Ccx2-WB3K3?@(S}{JF$Tn@H13m}WAL2@3QNwzM!jnr&Yh4T9
znDjfVKiFV)1JoRy0ES{<REkrCcNIm-r!>B}7ngML1yvP3FqMiL&42Mzt6lNkX$#w1
zGj41DE30>w<AaaL#g5%rk?vpB0cIQWGz#9RM7Cd`YQQ+;0sV=XTXJJiUrx^;Zn6O@
zhHMw6CdD%3P9S9LC`KVs0=V%KIYlW}uHyy%HkKX3hi2`jOK~3Z9{k|Ad)Fx*jL4y2
z=i-3yzuKiqpAzcnE(SAzxT0=?tI|*G)$@GFyq|0z=}>!oEPo(7cEb#`41`qy@S<jz
z9s2=^RWx>&)wiG{@n#k{t-_Gj-V4prnIOLl?Fa{RFCww&sf9WqAItlo{L((u!wQk0
zS(S1d*Uf4tDXNlW-@Clkx`FtVz<MA*1ZoVkb{P$~5g7TQ6tK6XJU(L&3{6qfL9QU5
zVhIg#2!RlL^Eprbm$XEI1QDsseu1%w{H@F!OYlJWmW64$CWKFPoZoFh|Lj0qnBVl6
zCN}uJ)lH!k(MpMMX$rQXXj^<Qt~v~u%7NO@h05TWf7u}oh_-`1vnj@;&z)qtjvLK7
z*F@5rSvEnUDi|;8aWGvzfktZ0e^9eIER397447|uvmTr0)K+brDb0ZG+OkF^q|Ovv
zDRH!N@y?|x(L{h;ysIV}e7D<;it-xu1&T?<>}+hqt~!5n2y8!?t?e8#Z!D3yx=$i-
zy4lCmh*Gsv7%R5`piBmIb=a=&24lEeb!|~v@>mv3O}$9oGTIXai?vI&16S_My(JN`
z=5;l<8SChLR4?<$0B)p9hC~I}6-PFW$Z~C8a>n%NzjC!Q_Y_ycRFxsA@KBAET&DAk
z#Sf6*$~g$#N4oh>vRG-ToThgF=DK8Jhqz3@=vx{C_J0L}Z58Si6oC!|s9Lyq!zdE@
zaue0HppzrD;N;#HFn>F<BtD*{zUfO!?A7}(1SG|4k`GDm09<wM^AP<=5NU9pUUDjB
zm-~?>Ap43_z+n0{u;h3(>-MFwBf$GEfi1l%H*9FtBE}9XY09y67{eJr<TkJxdm#vM
zdB*Zl48k6?>hJr=#~pA3A8?|AA2|Rq?ml_WqnH9S2;5d{NtJRI1iXC?ZbBCo^a%OL
zw>V0Vu82VI^@uo8*iY+bZJsQK)qmMcpq;Go_*oEpnon9us86j24tH3%ZXO}itj;;}
z9MX;QI@>q??8Qg_3D*@j$k+cjNezLN5E^rS%%-N6<I`aBbHAt{=RG6$%2E;Y0ig<5
z*lwuFHb+b%N&sTzT~!;>YX1br568gcR}tRv(B4H?>i<wD%Z}bcwV127N{iXQM6AOR
z_wO$1bF4S2kJ@%(1Z6T6aiZ&UJAC(8f${TX!wZ{Lm%BEcXl5i0Z4cfj{7Fj}D(6cZ
zc5c}+Vl4J76_p#S&Qj2B4G?}+Qu>bYYaII?=O-5Nx~Pi6Os`INfM3($%S?3in|{bY
zvXQsDU8T*AQQ>gV<870v=2>ls%j(iHm^1JM#xO4KNFW=WY)X@-u3iB-mZ4>FuDoV!
zF52@@u>WjrS++;8Mnh;Vc96r{;n|U!t2+bf5~5mS)xh=IO-j`Imm<0?#<Lb0&jjOH
z0<zI3#Cw<3sVm>YM=CI9DzDxe9aUl%D!e2i8|zMwopodl>gwRiEa1SIM6AQJ@en6?
zXc&w<#ju)eGnUoM7}lfrno@z}cEK^)A(%>jfcI~^)}9iiNMisV+)X&jR}M)tU(Imu
zU~r=SX%wq8L)jv1!JY3VjXJRKMy)9l*C9MpMR`<HMN9iE;tA=p=7n!JA+~WMwI9d?
zpa^R1(+c`A&f?B?s9$Bp6;PifLs#xh{i;ULppz~*;W>rw7C7ITBe6+)jtFFl0bVh}
zZOPOTiC;4!c$y_PE7j-DWBE!_wUfA7{B?i;-0~cfu++$FuMvknqXx_WnNREMfO?j^
z6=;v4;?wCY0lx5t`8&;?X(}#R+zX)NQ5Vx-%|-&`7&c<rr^<M7PXxh++scF}Jy%R8
z)y|TxOb2O|(`IRWG>PDCwdE?u#(uqR=ggh{fa2&wf22B(>y4#Og3>d8DnJn)7@FY)
zWYjlWoTLS_%u6qi^@`d;!m6&?#@;mFHvs8E#t}&{HvwM5n--U=^!aZlrC7q-qpZ?A
z^zMUs?6a%aMqztc17K-U(ZQeIH%l`+R`~P13>arNcq?>-(TQD0cAl0^G-0ajNG+*#
zb%~+(^$))m(!$SDPFulEEthsHhnFdCY~JN#xWpXJxqOyRM@a-MO^MlxV+Aq%HB4s1
z)S06xG;UH7891Q5B%hk;BEo%XmcJm-7a2Rm@oI|r0`}Y36z*8%uNTGYeNCQw#aGm^
z^_odG0b@XB`o&C1ME0Nt56O^?^*ehX=6UGxR`+eM<|#qroch-hbqkJph>87dkcMw=
zJon7?>$7?zeHA$`rL7qH#y}#iRK0en8yQ<n8W$<9`vC{#zMYo2TcxoqFI*R2k3apz
z1Ywz1Z~|$$;CH3Vl{bMXSk*Jj1g4k2?b0oC_($J*AZFQX8KoA`)?bTbrq+~`%`ZW}
zvAx}`RT8|JPl!<HdRLR&_A0_>y7@cj&|ASh{Bb)ht*X5$h76JZI$`?wL1>t)fGUti
zhRmd9XHqv{VR5K#bM~1@9(qLQD`G}H0mD_icJ#-|5%?>2qrreqH}r^mOHM~dC&qRW
zF$K-jp&4<l;f4^wGtiXOV0>rAtBcTi{AG{XC{p-_lSR2Rh2I|^0c1RFGQQAowIJ+-
z!_g*T_UO?XjC}bW2f9ko-2l@QI@6ks<kLQvCU>%5<aQKd&3Y;)0K0YB@@jMAY?u$~
z`m6i0)9iN4C1;Hf&i7w6fq%@*D#bNcV7YvMCb|eC_N$2T5;{6#c>Bq!{}ftI+wcI$
zt9f(UV;-WbX6h8N**g20Asc+Lou=9Y<Lk$n7dYs8+HDLRf~h%rQ(B!S$?W?0i5OKv
za7qsp>YiHc?Q}}6)1M;Ggbx<<XsSsD3?Cs|79hA<utY$b4D1=e$FOeMp%XN|#_5)U
zp*<d4m3mQsgNK5A@CFqH;E2lQH%{S(d&Vq$?+H9#scngb$+29}eA>K;%-rcfw63O8
z%gn)iAP)UHjV(w<Pz(mWQ%T>Tgtov$wYpUWrI5ws%==J;PugT`ZpemwWsc|A(HPw>
zkmgo-^1a=p0*)M0ZTO^o?|h1u`}aH!ASha$o})UZHTz6><XuXw@yz%|bNDV5iQmuT
zMF7)#xKPsC$^rVLNV?nu$-s_bK$=*P;^L$Eo2~!`<~PnM187?;*tQ;HL~B)oI<wAP
zZ?Em3XpWit*d;;%QK7>AE*kGIl=bv~LoEA1Iy_3{VAuild!jD?n1&e)m1u<w_KMG>
z4}l|Gyr^R|3KU|1-xqw-Ych2hk}O{&eY6k;RPDX>Yz*qV8JWRU3aY$zq{7oMdlcZt
zlJ=zcYC)PyE26wvZ;7;e<vQCuA6`fTz?~A^%P{`#j#J?w(b@=16U)0y2iJL?$A>iK
z8mNKb#o2S}(>Jxv0N(Y73VU;X3B;j{A}&jb4$t(GJUHW6XLVkL#G&WIujk|EKlp>j
zOYUL}BM?wN@c)%n{KqdbDthw&ut^mE6@PGYHncJ|x3e}eb^Py;_<!K=-~T`*vgZ+t
zYK<w|4GzR^$Wd-Y&J7R$u4YLE+F8*ch|}y6F=Tes@_X@`j#alEtjGe?zYRXCNybUc
zS$4kNf5-S=+@g6oW_I#fD?mOdp9~g(@XUY8{M8Zs>cVOt0UhqDm@v*y5q!0}OZ1co
zOYVN}j`Yq@a+dbCcCpw!o@c7w2Tt$VK7~8AFlxKODP3t|Nw03FbR12C^=HIZu<EuW
z=Xo^cnRo~7Mz@ua0jW$Vos4)KYB&?#FqaD#xiXe#WG{~XBZ1(ZX&>7e!}qo}ywE+d
z;+a6xL+Y40(e>t3FXm`emoZPxit}~bj(f#GBF5GO&7V_};WWc3)-0k1!KKl*&-m6D
zXi(b^K`QgP8sMOm3nLmf8*1Qt?0Iu@tmZIxXia8Od@gG<B^1`cT|VnX92T_iK7%a#
z>B&^Tabhs$_x>8|XdH;~N-Y!0384wIlIRb3WcVP<Z_>@1jU9V7iQ%ITK9=VVPv)au
zv@Pb8GBE9wiQH<la9*VBN~x)b9=^aUs~8z%=T7;?ieG{+th{H6sI&RCn1=`}=bPQE
z<D#j+F)E7>IF3bIy24Iq3fwU5SSuvE28UQ~Y723QH^59Y!!-9-P(y&s)K6L?Eh=*j
z7X7K+^mJyO2*I7W6^k(oDe6iI+f^PnbvL>*$i){4OC<NCbL!h6*MLjU1XTwnf0Vil
zs%MhcG^19~PC*^Bhhg!!qS9@Pb(P*?`%3u2&T~ZFRC$JS2s=Cm9vi{Iu?WWMv=Gmc
zK;Uq-hJ%53bf>YHV?9?9TBnJ9H0j`NEl9~hCJgeHHM?AJcFhb#t6~t`XRvPPFb)^l
z15+=T8$mSX?duO@@t)vyqPq!bKITZ`ZT?m6jY>v9bf>0GL}w6<%Dea2+ku?oo!m7}
z0>75E8YrV>FWKVZS!;6K&rasF6a9<H<w0|7yCIP^Q=D73Ny)V<lEhydA`I}Tb<g)F
zT}%{fMDd-CERUNLK{o-xDX@xz$83c>sFt+$HM{CJD7nAVsmoL*6lFh2zp#o@krJVG
z1PjAZU_YOj)0R~3LhVYh8hMZ6`*agc_?|sECJnJ1Bnp-2z3V7ao@hnXuHyub><HB;
z2X0^uD`^9ibI>6m_zw2h*m%yWG*>%0pg&MKIP>Ap`8)7m&aarxD<{Zie-s)erRq9Y
zWBmq7IoL3u&c1?(Ws{X%pD_f}@eBgaOvn2%SEX#pop?3x{MM3sh%gRF<1^eC9}1ON
zYw~*{4uE=0v<R6BZH(fArfD?4K4mn5qdL%_R{ALv=pR{p({FxKnA)7ubz<5~Snc?p
zK$;W12ulp42~xF&jR2@ru|cIIKk2YbI)d#oBhz;n*FTq+*6rg}&NsH~$o`5JzaLVE
z>w@}Z!?Yy@`yfUu$Cbiw+nUK)=xTTXQuOjO5O}1VsahV^6C-zbwX?g#j!5R3d!Clc
z=3cVPH1n7kK>;XXn&yE8eMiZVbECe%JI%Mugv@Rh&wY9W7oKyLQm@#=UR@D!pATgE
zYdW6eS}l;wFhRj2OuA$X?JYXT&*E7wt5wc=??%&!iu_27M*{c2tOTF!TYeB#!!b5O
z!INEzTg<RK4h!u~yV(~sckOeK0~RqhM(O*1GD;Ob%P;J&P@+_8-wh_f90Ie%7m&yQ
zYK)6w?q^`>zopjN8qr#HAkO%M%>z6ATO&k*hay6Tq3f&E2mB2J<@Ux@dSGVq@Id2i
zkhnVtR0?LZkv=UZ$fNmurJ1H9(*ftj_`U<`;UUY*crMf(EG7L4nSnj9N;n=<t-e%V
zlhi$^5s8p?kak)~uPhfeF4^As^74E6Kh&hS%*>+xKb$QO`F|sAoBtou_TQaB|8Bao
zg`Mqxzvp-Vi)dT&*@z__Nm=daCeDYHEUNsoSJDJiMG$>_yRYdmIR`810SqkUs_Lrh
z*zh~b<4kRi(E#%suIIAxr{AwZf8Qx89Hn)#>Uvq~gYe%(lX`zJ0_DW_?S`KwGMC`p
zmaAvo#ito>*s-d^)tz<OSo!OdAS$<qe&$GbYw@7?wWPb&HBDC;t#+?*2=eW6h8-aK
zyi|8_!Tjwn?c-MU>r=pxPr><R2&#ui^`L&kE^@>e+z+qvo&~j|fi9!sa$|p$7u{IB
z*XSvKtJg2{J^!42C_m`u-yhahf3egFfgjz6748U6ppDsJWl15qqZ=o5|KC>8P+0{*
zmAl{X=AtC<2i7?5qp$r)1HEqCcYQC{VF}*<BB~v)Qdk~wpp@aZTHV`(bGY(e$L=V~
z-u2bQrHup3H-4w;RnEV*_WfQ3De$@^-<F0$NL%%zAQ**A&Xel8!b{}lde!Cj4b%sX
zaY2QGqk*dz`;{OrjeqGNSMG>I?aP0+Q_)@E5{N5mq~-^zl|#+uZoruf!Cq1K?m*>+
zj}4=<3E9@k&H6%j4b@Dm!bjEHtqM{YbZDfazZUOpJL<!h9nN0tHOlRlpuOC#5=KYa
zjrsyzqQrVHJaa$ay2MiWv@FsIGCta6%{ubB9=t8?>2K|QK72fjifl6ulC*k)=nBS1
zdzhVNgGSKIy|*n;;Z-i8Y54RGXy-uv<z8Li-l0O<1r|N>%Av4^brzR9_^Sy1c)m~(
zMp&YGO5GOg)?Nc0f(?806TAW_#ykofY|~`-`qIZQeH_1&Q=~cj%MyrZ$2g0ryLO9B
zm(ob6BR1&J^#bnP4&N-Tb$B(h)tc4ACBLGuq0!8BUY$oM$bkv4*apz)-`TrvH~{wd
z(pk7q2lebJP=vB$Y((4FqH~qG;^J$Wvf4|x5$rk^xmeV_IffgANyJ<-WTd_Ke{>B@
zRw&Z$d4j-<DL=>^PD5Z%nsGg-Cw?VSr_CSA;K;BF>)o59TO=mP(ZC<vSAG|-obdP3
zgdf9E^Iqc|Zg-f<^n%bFhP$Y9{Mi8oBBNX4c(VcYgVhzch47#2%1|<h&J!Zf4fLU}
z#aZaRwmv3#e|!y74$y*Hh{s_bbsd$lft$1bopKmISq9`Cl1o`PtMIv9RYdAjRu;_P
z_g-x@ug?lR%Y;~^_2v^vhNr|o^ydjkE8v=IIyHP7W`7%fZ0+AuN7eAEs6O7m3vL8X
z;ien8Q*E?aUm4sVZ*w~;LSTmd;81uy`J9YdBhF{s$qL|m7YI3!DJ5|y^IW5>9$ml@
zw9DxrZf;m#K1A<qyjD_p8zNm`Ac)^w+^e&75lkVn;C%fTT68<Qa<x2{2;W&?LT6OJ
zgu5PQy7S5QA}!xWZO^AZM1(9du95Vpb&glB+J~V^y#6VKw--uYZ>Q+^Vz_m5<3kb5
z!nBY-D>vPoBZ1I6;ReXg0)SAP6|>ZcdDYMq7A`IZ93HW@y1CS^d<FJwk=#$Ecwz>O
z{n3M}AYPMrpW~F*C@%@u@ce^2O3tPIDTRW>y`S5D9ni>QJL-SfPg-<0<vu~%g)%{b
zjE6PY()OO~5wt__LDp8C@A+iCdSk=HYO&#S{#GN_VVp5+xV8TR!(~Jer!D*7mU+U@
zM=i$7K{!P&8`SQDwXU`hSg?G-As(^xuf#h0K|q_G{G0s7dk-3lVQ@ZT)F5@W<V`d)
z13afJ?3ss@7ES2lVGnPtZ~l2LsM;LqB4GR?knVPLZ9M0^^%pDC=ms5$CSU$MHr0O<
za?M<FXR!Pe(_Z^EzufIfVs<N_x{zL?C#hM%673eI4^F2bgn3?=+3vf2D;-R~usq$&
zL`KA0aAqwkg>PuSCGW2af+@G<ACQf-519O=a|!?NrQajA;{9(^l6pZ$y9Y?tR|ATQ
zz0lT`2SZ5$e5Jzqyd^RUvz76c)~va%N-6|s!6)2r&UYcWGyy%2kpY;Z?=ho-#_<}E
znpDPG$>B_r`c+yA=<$)0+c{6UN)d^S!$y<bd>TuHVGzayTW*wz0g7%Eb$Gx^o_=m+
zRhmAiZDIh>*jZ<8lIdZ5R>fD$ZIm+r)I}@@vjBLdPH+beI1H0A!u<&R=^!-Q#M_L|
zm%{$e8eP9p;2amJ>NY7nvD`y@5OeR@oUg4=M@SZts3aF%<)(G0+DGsl6>b3EFgn6H
z^EvifD*eLqA7rha(@$VV?VXiZrG2jsSIK%gT$~H5`JE-z_9*F1kUMra<&3skh@)W#
zjwq6S`qrE6@PoiF^kJJlFFH2pIB?G2v1uLM+Z4PaR)&*QBFo<H!tw%V{I5!4EQH=6
zBl+>+;C&R)jjZaeF9w!#FbnDvpY~rc@|E;ZH|)n+C>iVdAfN~yWAI;6J}&77cknLf
zE!YlppGN|?0==c;-6`U}nzPL6{@7S~60TI)j^|$9MnwTKk2K5pbNf|N1^NTVu4I>?
zmatkO2JzYF3BII~&=hdR_X~ur$4BKLR=y)ud0-&j(XUCh)QJ@Son7LdEy7Ed)e*^J
z3S{!S+MwS<c0?I#e82==(J2(@_JX9}Q6N5lzkHy%{R9cdeK`?zJ}q3U*2#8#_dMOA
z-QHa!Lv!1_$3GN1t)aVB7K4m+-k1j)&a{QJ+sgJz>&{2eNk_$WAi!8T1$T|{)p*6=
zdJ9A1vdH=H-vTc8W?44yDwQp)e>-+t|1S9&mU3^&5Y!`Ra3(X0HJO7<#C{jKy%w<8
z!782c;k8_sWNOhsC%ab6a{hjK@P9Wt1>S}yELtyBW5b810a{_&F(8@qh*4ua_uAWl
z8U!)A#a~1-`Z#TE1-g33&}lo1@ddg)8uwhBn>A!J@jcpVA+JBO;d9ym>Hy-h0G2(4
zY^?F~Ruz6+4Ssy!4sJN-<@CE_>)s7P6TVviz<!jd9CLBwS9t_6fQkMERiBj1?wJAC
z!?8KvT?uqQ^v~x=52?DI9_r=}OwHk74-&hGfX)!zDjLNJ9+$#-)AM<&`?-xDr;4M{
zQ2dO2p!~>6*qpMVDR@UVU(NY={uRF7>NVS4(G2y|ymoid%|qb#GPPuud{e!7&HnCd
zN;8YTq3dHC9UuiOH6cRm_h9j%@}@@SI>={d1)(~v0p!7Q6+rS!IK$KszsyfQ8WvDn
zd_>0siHL79w~ujXcE9LPtmt70HM9{7(~TJQwEF=WBgIGJU-z-PNV&r$Fz9b!KBlfp
zxRor7E|~Q+*FVI90w7OztmU<z+ynZ=_LCEu_Vq0F^ETvp>7ncvT_8LNsMC*jMtJ{f
z_%wLW>j3^WAYHZ&dRt#X0f&HRb6M-k^}+%I;~X$N?H^{SZ6wlBL}Vi<yE;AA3&Cm4
zlr?Z%6l3b1xep0%+G7{~u)QH*8e<|X1j1JvO<?tuR|ncWz`^H3Vs3M|oI^Fw|0<c@
zLnG4d``}jFvswlkj%}0m`Yy?EO5p_b<{A2l&1)@nZRruAJ!L^c(_&QbJaGsdwMueR
z>9n9LS7gli;8FHbLslKRe3QXB|C|zuFzttzH_P!(hvaE;Rj7>W&)SjL^cL%q9uGTL
zs1CoBp<Gn8!#hmX&P=oqUso((#{XOYZU5*Ntsmrc13UH<Zp0aJ9j5uRL+?}E#NOyU
z*yVd_PNB-ln{R1~FNIpDrdpJ7jp`>YWMQpG#&<g?Fs_ih&%u$HlwTk)8k<eheTqd|
zoTi%y<I+Vjk!4n`km!0h%Ed!IPaou3_EeakN=X1gxz@cw4WJHcn36@x&~HxsTcibZ
zd@B}2j(e9X3&C)6bh!F_Gqn=<b;?td7xUq>mZ%z<g`&cb!utec=%Zq@5zd|)sO<G=
zvlZ0CN4gXa8EGG*sXl9XIDU07g4j*4cMPHE1zk?DIylaB20QBVW$chs4tI_^fQbpk
zRzA#lXMd-GCd<dO7F8(%Q(@OQ4`h00Kq-CxkRY%@OCz2nK!$llYIr>T)|+^C8gxQb
z2|&^ee>$qmnu3DLmOu%kO#b`0239>bRa+}&?Zs|xN*Q;Y83*`u7-dGve_-e+e8Sg4
z2n#9^p6oR9Nhn)O{czNVI)Qrig1Lmf)7iDUFh_j=v~t#6)h%0_>ckyhGdh>XViEeq
zjpxs~Y-ryWtM!nsc`EWec@KCPDY=mG5!pmX{ROsc2{oZf&R<}u=m9LOO#fgKSb^mu
zUGZ-NtwG(M!^4J~Xm2vqnnQtXqdkE7!8P-dSdN5~zZ2K@$MiS6#%-F(>K{k2tu)YQ
z8fnt0_>8$BOSjVf?R1yUTFAr?YIZ^5C7eSZZ|3w;!Wn~a39B{hl>)$2XDT!F*w=1Q
zC>2V$d7X>SI>~o|oMJsDQMm~T=iijKS4n5gff78=CJ35HZz^LS#D}oh^f~}6+9Ir8
zdYS~8*MZ>bT^3(R5X@fsA+9&Mmk4YOgFg<Yn&XeNIP|$@bF!TDtT;2&i-!5R^Mz}E
z*v0+5k6%%VV?+yUN*lXsj`-{3%GKxJ=?0v^x2BOL3c5j%7RC<O(FM3U6Z{$tzjeaR
z0KIu<NLV*uN67$iLk-?kjOSQtniP#RA{K}z_y>_pBs|APDlV+}uXu;}I}rwqdgKF<
z%35kN2)U3V;_0q#uEpd&z^JhC@HZK=xfMtq=+>;!__BEgsD#tK3kK%bNqoGQj*El@
zumo}esC~<AG2O^155&*1FG!&S?m!f$w`;cl%7mr==Dk3ujxu*OXC0U<loXW50Tp99
zZNBn=ZV8tuk|HTXwT78s40x~A)C(0b4wmkg+!jmQBopaOeW!*QmOA)t58|Yai(j0@
z0YVCBx)V#NiM>EHkLe6tB5~U@spOItNCyta5-WT@=q7kq@GPj%U*~}K*#xsjzG?`u
zhs#!b0_9z3ZZ*>&J%wjc`K6SJdt<d=Nk#fyy8b|e#*V1kkMsC6z>t+&SA9UaCN-M}
zFSutblhuy#4J~lZ);goJaCkFU$B9}~7^&IyxQ){L`*{|SOSP3A2d|-ID$Jz9a+RD6
zLnT0M^2iQpGnX1-gd6JizJ|XM9WNmWY&C@kC#L5?vX0S<y_>zxIkxWhUy4+pcX5fN
zK^+da^Amldgk|9F8tW}$I^&?C+pt|)1;W>0FJhut3b=~_{8P(kX&Gc5_(kfV!P*!l
zH3O>W!RV(9e@B&AYD^V664zcrDjeYRa;(i5uV0u5mSH%eN+x${X(;0W&Y&838b!Um
zZ5@+iOq-Fbgp3tbH&y|b=gA=MO>;(}5_FvP{K&-7tF3^2tPX!motUFW<Aw4)f9D^m
zim3H10=*jTHYfy5E#y&976rCaihUF{&Zx&>P7G@zV9}9)tm`b8r?T`#5qv3>TL9h{
zjszb5{aMi#;+3}AGVPj*tf<7rgt0(As`QO=Y!K0XsE&(Y2|)utR<K3$h=RpQXrJUW
z@XYE-3fkT3AF&F8d=HNha0#ETsjcYP2W{H;l$x}}5aCOnnHSIf=amd5#dRlN9lAI#
zhJGVmvNsJ1B9~$hUh@ws{&Zs+q6=U4+&%6Y3bl4?)~JrOYp9bni}t8m)u!Q52K)0?
zIjFYE<<{9tgh<_Gh3_9WLAGA?P%p`K!UXa|jvf;!#(B@%2w+qgr3`OleS2xGRJl{g
z76j6cV$}Gj%ykoDZ|i@?mgQdy<0^(0a4Ys4u__%0+H4LrlHkPYO>)Mo@aA5+{@R(F
zB(Ky=S<GsLRm1>|OP~Ctwtn>^(`LBrrwhI4tUTg_c2)KsL-Ew)bVlw9UM;ZdJz@x3
z%Ib-4V^&+Z#N@xiew5pomo`y5AL<bwexUrYgn>eMtQst^4B@}}3227#r7KtEwPQ@+
z91NNHzj+-8q8?xpspT?g0}P@-PXxo?K5n|swW*KI+_9Y~<960B^=In(&r53{^0ne#
zOpW{HvOfE#=_m*e3c)UQAH(}NWhYSo72nn3m-1_X%)(LYfxtC~=_@N+7g)c25OI5_
zg!ppX@G3XKK67Y=tOD!-g5I=K7gqz#(Y8mrUJ%Q;#~Opou`d_PELnV9>?sfLicUm-
zJ)hRuiBm5HeI7(-Q-13?()?~^*I*w%O||muWlRnQZ)kY?{@f?pVTa`)CwVcS#6ciH
zxI=cvOX~f1;k$c7qNcUk_sGN(q4da)x0}N5pzL|njz&^-)L>D7UJpb7Qaag5)F`>&
zp|<xioId-1Nk@mkNvqB+V)vYX#jXbDcqLr{iW6l<25p!IR$je!_gZ6W8#fTVr7a5T
zW*9r}1DCH8tl|SBt#F1U&JV^8#r<3s{IhtIt1-#)3?Ez@>r7N!%N>QPzhWOy<Ljb4
zPur07on57<R`Nll`ecB43xi9sx;nQ#&8SU$?r6^-Fik8seNA>|2skEsuZY1A%F($}
z$SSjvl7z4$g5zH|Gp)qmkBN@~$WGUrhe;&ei30nVW5mtg5%Fr(B_vqiXM?=LF70`^
zz>R^rE7fBb`o?edT&{5Ts2Xn|GQE`xETQr--Zh;dyEC*Pf#Uo8v4+I@&zBiQX{oMg
z0P%<nCOcTI5>CkB3sTwh1^KRh$}R1^1$limyK7BpSMcDVqBF#R20ph_Yv9w;(4`(@
zWdLJW=p^$;vaBI(7Vx33C4X-4?ow%P&2R{m{XhnPe~?OmgUM3aikkuc=Xop86NO5^
zq#paSAm&Sp>uioY_=prZ$LvaU7~5mfk-yh8%p#g~<>2sgnQePtFbZ|6Sp7x;#ii0F
z{v1ud2-Af;P3p|)s~jRiPgB8a1voSDYMee|>u<Swt|NdHNVC|*%5PV}rxBf$B6!e-
zS`)%%`G(~J!{(Y=Msn)A#Ofp-Pc@BKu8_G4%_9U-QMoj?c|wFoY~GwB+lpmU4^lcZ
zJ+mhFb}(tRrhvjKnr8#HyDMa*KQ5ndL&l=|BYz&@idFC5mPF4+lB4t2FOJe#J63$O
zKH8nQ{Qi<qyqL!iP~We%vG38U8$-KWdf0ndQJRF#Dd+sf-CE5))nb~)ODdUX!7;<A
zu4_o!i$7<Us(}a&K{b)|@8#^bVgJ+_gsR6&SvA?M5jkaQjE6+jq*#6qsNx-Y>uI{K
zzTu>-r{f6An2tNt1xW+p#q=ory6rzV%q5ZoqlWoru8tfJ8DL)KLZ+b%*m;I@_WR4q
zUPID9ee8@?YqHg{B^>!APDsb`u=dNUy+w-izMcZLfIZZ98K+j-KZbRe8xufL7-PAi
z(UK-Pa3lc{RtSJSNk4R)v&E!pJjaq4{{_{W1`slpPKURlmav_~J3)2aLf4HZL?rr9
zc^ti>-F8z0Ijh^#l*hw9p6{_btI9bf^djUcYJozmNTG?`=z}4P2cbZ-x%<*MtlHWe
z_G>?$lzJ>{3i(=Bbt-}2+w8#q=vSe^5*VJpWl(Vdoq%@6Ro07L9G~IA<wr0%+s9z}
zp&q9060MFk*2_n|MY%aTM@~|(xjV*tp{{dwX_$)-@wHY_?xA|lH}4msjWC}G@Q*>V
zmt<7k;~YrJ4h-caI0PNSxdH9|SC)%H&{e*Psx2!ZE;-l~vzSSMtA5S>L*uOOs0KB}
zh~OhG3H))c^2?YJ0%=^PmTF|Y(QFXRBed!wJa*H~?R5f30;h`~gauCYR`G~<pn&1#
z<|3O%hRYJxbePzlM>&f{0t?mIQgw;clrWuJ8kl@F|F|!hcZ^DD`C5v{luWd)`qmi_
zW1DrWX{W`cc%91)9fe*#xH?Wipv|*!O_}(8!pEZ|5%<F1i1;qkj0n4izatg*IU?Lf
zgiPHy(7RSU<89s#dW@u#*3|$*R{gqG=SM6M=uS7HGbxrvhE$#YdP(@QV+37!54OC5
zuo1?gW`i)5I#f{1d3MhVFEOnV=|wdWzF0xfGhw*d&`O|j%~hz%o!5Y$#ol;xe3qq>
zC^z)NIl7|D^+{xt$g>h$jnf{f&dr;_K&AoOVK6Qnf#7k=qo2smxx%uphg=a^_7A&T
z+q!WQ9|eNF+*?O7M@i&%Rs4HsgO@|vN{y?j_9^3_HY)m!O(lu5mBXm%5Fhg#-1}n4
zQ^K&&o)$H@sgF`__y{RdDP9}-UoIu>B*rP|a>p5)lMWUMz0pk-ndt!Li-Lk+FMXD^
zHi)3Xa<PgM3FF}N!`nt!>ekVQ{e)A&$n6noRl6h+Ikn%M-jx1Lc!e-&pLyYY$u*si
zLrIb3o<?i9GdHq_WL9NdR%4c~RJSzKxI<Fb3ihE~VKjPzvl7!iXb|a9<X_4;LgMqE
z`|Q`e%yeMK(aE5p5L2H8xtyRgH1m7M=c$M?=vR@&!b~PpVWQ-OnjVWDz}vYEo}m_Q
zgE}w%yFvKgEvJT~DuZ<WIOF6_myGjO9yk(ZMBeSwQY7Jmp)VLo1=cW3MeynPU}*?1
zgp)O4YcuguIvLC5)e8`OZW)a1P9`54jl0hHE~E$G6JSZZ`dFgJ@b(dILQmSTT1X6E
zW)}<nJwJTYdeSxc5?F5hLEBTEOg<K&VH<Rkjft-7i}(J@RHMqP>WkZdraa6(O%aqA
zqy(`FmITV&3cjvfFQTz`qW|)<^A&!Mxj1KYCBMt~P2Dvr4T2ntE^teq3W9_|PZm!n
zwc1+SBylqiNiYeHlMkkI0pRqTG_)j;Yc?0zE0%G2kjWmYOnO_GDmwlMLo0nd4c)is
zw7qEPHMj2V-p<!*Ze9!^7aL&lgmESzdp0D#X5jHN15@tFWIZC)ThZa3m(l+Qh?3g;
z86A{Ja0H>Y5FZmOj+GG4^UpmLkJE1T>aqAUsKSDyDJ)puhV(mk(dJ=mTlZ6)K!V?k
zk%C~N#fpKVx&&hX*b>Ul`BJJN{TxuR85x21?SEI=*R0YSV~~<V3`gu8UUZb6v|CY#
zu9)8}mxWfCL9+jTim{qef-lii-jX}VmrrI4V-x)DL##TvRt~{U0MDY(%1_NP$-NJ)
zI$GYOS|1!PVzbx&RcDH?1L@*H6dT3Lt^^eH^hNSHlZn|2aa}cHgG7b;w=$#g@9oeX
zR?oB0k;VnKn}aK~iM07xWC7G*9@Lhq7pVTZ7CZ64Gel7nopwfM&9DTq5k@D5p5^ZH
zr+3w+4ISP}-08-LK6!1*1=mUjgdBa$rK<W}y{n}5DJ5K6n~`Wo@+Ml9?t)tZbbf1%
zdMFmyE_M9#(pFoYCpmqi$ffU6?DDs1GJ=0d*M+6Uh`__IvWs6lf0TtbUNE0U{p716
zCqbw=y*_*2T{Kd$p;`YyXi^qcQiGF4SK$f+s_`EE172!D%wGTcD~>a59>h%R*`$(W
zh~Trp^DnwRyeZWpdf6;*Io~Rs&3+&b{rrR@7cU!brVI$mQ~fxp%Lv8cR2vY+3H;#c
zBTF-`E_wsaZLHi>Rb?Qn9=g1t6s$EP8@V?<Vpsm{zd0FD5N;Dn2ea1zwMj7oNBy6i
zD51OkFTM7mN!?Yd`)Hq`x+OZH1XKy==`tni(TP>Ph-I7Nyd)(Bk=|Scn~VmH^y;Ff
z6-%VIBCx@KYp{02qoL@eX!FVIb~BXArv0oi%&t+9vh$s7t3!AZ=%+(K%e1;aV>~B2
zdV5C=|2*w0o>Ty%ZP==#?CyU#P%JR~v4~Sx<nVF228pL&#8azKOepBbwV^{6cGb!y
za(#XrC$YEVn3TGuTp@V02j3VEQ!?403`Sl{wM@jsJn<o;AJ*SHZIb6`X}aE9Z5iDQ
z4_GOAO4K0N*p;O;cB3}h@g|iLdrXs|2nLAJ#;Gn?%eKeZp3z5RL7@Yz7hlE*qDe!z
z7Ka2(v8IAjot?|SB;#JHU?v7l5EXkHuPg5AD^}|X1Bo3u^l*;l^9EfT48PaZ4ek(H
z{34rqs^;qbL;r3X)B<--L$ZOXN+(t;KcmY;ZSBl{jd&P*e@~ba0nmot@}n}a*!wsb
zIJ2ghClsf~b&JI|#f8S%0j*Ow>NS^=QOdmT1D2wt6=BTJg}dk+?wIYdZ*afW#$fRj
zv=&gz`#Ofe`z74iW#+u^D$kepmLNXzS{LmPT-%zsUsouoogPFK{j%!SuE+exIxQX?
z%SrgSbBc`bSZ~kOG@1AhPN)=Fx$|zX8){BPR`pCMHAl)_EdbwhddryV*u=cu%#Z2%
z^f-9=#T@xWc{afdRITTfEsfI!#*_&1S|+D@Yb-1vXfU>Lj<k?tvg_)rVKO`tH6aua
z;AUWBlpdt>(PioUwalxkI%^11BzX2*ID}zJvLF};t>}#A$VT~Kon6asX16Q{0LQWn
zi@L6h=Xn+J-3C*+@4S$r9qItWgXTb&%4T{Rw~T+^Bc8}<T=GeiMApQ`Fg=ZIw`{RR
z8rDRHXv|H&`zo=uQ`xv^gS+KTWD4j?N{3Y@B->4sqjbr8L{UfMLPM(W=k;S%{|FqD
zP7>!)tn6g?j38;m_R0);xnuMiYpFi75-ALZ?v?r{eB%G`^-e*eM9sEt+qUi1wr$(C
zZQHhO+qP}nwpRCD|J`xooPBTX6H!t1QdJK#a%NPH%KXM!CJmF`>-`ztaP98x>!fQw
z@59!hv{pPjsGEwM57X4Ki(4JV$;QuwEYCaY&9{U@?HsMIf+a;aAml^Gk}p3PBVu8`
zlPDsDi1o=iMlH6}fBk+<i+O>&CnoC<-(L5B2;S!yDn{V%3=#Opg{V{Mdmk*;>0=y~
z*%3lQ)i|B)(nH5<yLojYd{~6Lfru^Xx*An39L)qN1A)xq$sC)z86{NZ;YG<dvRyIX
z%}@pERxoDe>@igEeI!j8X<t<<RHr8=yOlbmRX8}SJ9P_=lu`|hm`9tJzRp&YV|WTz
zc6uUl6s~;t{0=2fCadF0z&FWugLcA}7IUJ~DRM~Nbr>wBiloJyZ`@7CD8<er>}=B?
zT4r=7ut(|8&}f}@!0TURUd^$i2^`z)q?C%i@C&Q^TKyT28loZ5=jl^cg-SkH&ecvs
zDLe4W?R0FNCIlfaI1u|<J0DATWy0B$hazYk(~#->)s+U5(|>LfFHnSF9Ksz5#gn=*
zVU{v(_YE(k{>86A?II4mA_?Gc5JcD~&$FL)<Zl~@M+7*aTq-0OZIz{xOoKjEHI02*
zx%`8L1Ep$ff7D?!>8h9w4a2c?UD~>G;2gBg!t1<a%=SPEwrh;B{N*t7B{vbCKDh$|
z$&?Py1`|qVve0gS;&jpIu^HQf=$NVbB2-nID;p>SH)gBV^6I|U?{*Ybb?-tAO;*Cj
z;XoKiTm&UGb#J`<(KGEM5t8E|^6@2K-v4lTsZpR`I_+LitWE_}R+}Wr#_}L)p4_j&
zYe0>tEzAHo+9;s^W?CUdV2k2Sg@VPxbC_GBHd_3W%b5>4hXXBd<%giFJQyRNFez5K
z#=GFa8PHN4FP<+w1qq&{#)&}@05_~cn{TFngh>JMm;v*WFcx~D7}V&=aVovX#ckqX
zM1*mbW*UHq&ua0g4gV3D&*ULmp7Z<InQ<OKL>K~1oV5W*)JpPYZU>P2g_z9fx4iqP
zGZzv2yd!?RUz<@$GitB(!a*$&*isQ1>@b~EcG=3i!j~bP+EXR1IX83qSxa7y(}o%b
z`YH1#**>rZ>#Xj`8j|b55|bc8$4+NiGfmB2`)gIC*=8LxjoI%P%w~qdk5iK^>)G<~
zjLMM~?(>U%{v32mhnR#fx(%U6YgB;Rkaw8>2X$xxW&H3kn)!B7VUuNCsm1@vVZ?-b
zR@oLr{uevAQ4ddPj=YI|KgZvZ<C3Szk?j5k|1QGduES<z9uh%RD@ym)JF8>=ZTqu8
zZF)IvWdaW8^MF)Tfs}PpypfbBGU%WRk`ft8&)<d+ix>H67WbsG{|(9cC%v2m{I3*9
zzk_26?u_B)iPwZOxBUU@h6LZ=8*iO_B|`dy^v~tZ1i0OEh@F%QDQW+z5ugIR$B%Yf
ztX_3vAHtmqLwz7W%+}5tKSo^i4$wa_o)Q4*$nsFom}y8kx<kNqfK{x<dr7pLrM^Pk
z4>Lotvi2r4S@SalSsjZ8PC3lIje`;~l1;d1Y@n0ENj+hvK6j%S<XJWu1+}8pXWr(g
zl0bF^8Kx(zyY4{*%hU}jWw25l-k$RMf9^I|uCUB{9<&@<{|!=Ct#&QM!v*?Ue4UNr
zkapeaw8&A2gRm^j!_tFHlChZ4>vE;yZfo0{g5_ahNQX$<LWzDV6nl)dP!nryB#^k0
zNyppDXpqwx7}@cgd1q9{UlA_Sxc2}Wv_h~!_*MYs=_9qM?nZjjLq(}lxB$yd2Q}pn
z?+=2@=Fmy(X6ViMaAxC6`Hk=VoBrHa6V};~o)<n%N{DY}4C%a%SqFD0{zR)bm4Hia
zt{+w$#2dKfDv!ySdR-3B<ag)%O{)MSY!~?mXQU&yW49HT!B*l~|GPBfvZ4Z2_*%9>
zH|D()KO^GwuDzr)ws;eXDEAA!TXlMOE4udh;+_+q2aY1(wkj$!%Vf2ao?TI?7C3;1
zZlK*JAF5GxMF=hQaNA+x<jpBYtr*Mm>prBl1SfNuCBDQ@<E2;)nUh^Mdx>Jo?4rP<
z{NNt-Ex|3CTWqT}Fmt&=AhM&}#iQ?%U`0QZd(et)lTl;g|A#Xzwd+bCnw{(RS>90$
zajKHCtKh0^Y2P~GqT7rvAUci_h@VKxk!!lb+rBvDSXIOi1wXB~qVl_T9c^LX@ngNd
z+p+(tkIGG)*qO9ZMcdD<xS!}lO9%`?F^vwSx*hdQ(*9$)HeIdLcPk~A(##!r1bNl^
zNjA}jjQ14lp|TsXuE<nQNgj30Akk<~jif-yeS9)#nABY$j(*WWWM_w#1k2|er<Dz_
zl1=vVlnbnE_DUjP7*S1mZHC55Q+yutm0@Dtm$1<V$0JYYuc)?){ktSR;YI#3{5C!Z
z!nKG=j@orgvdYQ)t={1y+D5AKnJtQ1LrM6U5nDQ~+$BwCgzG`jF}lCgL|1{X1WE)M
z!Rkvc8QiwT-=<ZhSyJS&AlZa~E%`2r%eBC}lru`ktg3~nHC8>1-6$Z~EnWDO$i}0y
zy+=9$L+_E9dMQU1+rC2YqctUDH{2Dg5L6F#s-FNw2zN|btyH-)O<MN7B%+;hWKO3-
z;anBVFN)0BzkM1#6L#4)!j0Cl2p^EL?46bUn+%R@9n^b(JG~`Zc49k**1;3_R4GjK
zFp-ZQsy-7*nE<}|Tgd1Fm}?1*q=}p-Jz~te9gjA!JaRcVT_UqvOC4Ut!=_S5ndKop
zC!tH{PhcY`yym(fo+|k9%Zmj$3{pa&XJd|}9nH8$go2-(-PP;;=tK_LbNIZ%*wd${
zmokD3hTUKhUVWjRzz3{O9~HX_Tm%-8OGh?W*IOa>Q=<X_k6Y8q5IEni`Wd~U1UqCb
zqm<AuGLJE(JhqGsa5js~dnReAzW^`Yal&9mdjYgkH?@P|ag&RKbMu=D&C}4We&F{9
z7__!m*rkTYY*4{bl+9)OMs{zrp{$rRvcZ}%Yz0gyT={XX(r0dS{^{k%>Ogdeo_et9
z7h`sDZJi+6qYnpZP+JC=9y~yqQKesjkW8$!?3=?1iv*?dxa#`UgZre_V&~Gl^`YBM
zj`kcJM1b^ktw0^l)cC6N$rh**-q(>|mBgj>c&HA+K4AU&<Kk4x-G+Y*Qsv6VuH3pI
zt25}a@S?~HgOyx5qpUMozC0|9_}ku=^jim&PfEFuN<#MZdgN@4BYtnC@$|=Qnt6yi
zV3aL4c^X>`sRSSP*dg0S(ZXD-bxaliN}3CON$v`>?#4}p-jiV~czI0Dg(`-fptoDE
zccO<4SRP79KGG}W&+7BR<6C9!TpjP<-Q1Nck90`z?$>!_?X~V0DcuYSySHfLSZc)o
z-6Ujc&*9C?QDv1^CLqxw&+N7(0f!F%QWVVfsjh4)fKd3E^V)%e7$a1K>&8o{cVGaw
z$d*mYX{tFA>N@cRu>c&SLcu#3tKiKOSxWWjH27;N-USshSKp*fC$E-K?;M;=pQKuv
z&X?5QGmjb)m{S8iYkUtA-Crz0{#dmHuBw(v{pToH%fy3J6&{wZ|J<jisseORQOrB7
zr?WeTE;D*uNK~-WRg1?HgxdDo7(a6PktCwmIW<Q?Ep0wehvTYuC_veRRsa?#0)f8R
zx>oFwm1Minp|h2U3>b57ce*KG4wsUQ*X%C6>>!kv41b(6-4=+L;lVx{bgw0uHVnVy
zeyR4-p&g)#n(1H-00}Yp#-Pd*MkC>|=ELftW$9R;UHu~Z>@OB-YHKvu9!c74DgBmQ
zn2#@<>qiOJuNKz(#wEXLrV0sRR#n763M$TrXF4@Aw%Wu6mzq=HiKI6OthZdN_ylx~
zun+OL9{rXNT|!hnSk}jO{cs2Cr#xqPG8B%6ii!#V3AAam8%=*QLqTm{ZB-^a83Qs@
z*|CplkW`bD=*asAdV}oc%pDn|>6Ls^ev#GdBW{QQZOC#)2dj<-xv^tXbVIUtfU6^|
z_0x?9h3?UOpfFSu)kPacIt{AovN!2?!AP<hf`JS7U5DBnfJX2woP<sY>*5ESC$x6C
zA4|6`1eLR@X(zPa2wYG+21RB+(j~3N(Z}pJi`K~nZvxGev@K$IXIp6&b)9A3VMwo%
z#3tlhO?vdGNzU6937}S@GhB0(B|kWgtm=@L$&OiYul4rj_8RUh^%rE7oJe@Opt5up
zr$S~QW1Z|t-qn(`<Y;}O`}CP;F~T`4CTsme#Tge09dx(x(jj-Qsf1NhFS$~!WO?Ca
zsZ|5&WDiNAs(Am#$V&5}bHf7=hi+5KuxNLd^6*F>Jt5g2Hf5NIPba;mBTqsMo!>|s
zMnn69+{Z+_hXYQ5qrR{hPoOM_5-W3?)q?bk_-WIoegkaiO|PdQf9#GP<ET4wrqk}^
z=n~PwjTp}yAQDzH!tcs$xW4wuK)WPGQ{WIcWQ?Ywhqy$6?BvS4r88;ySl+X#HM<bt
zrHb8V|NI1~%-T)b_<GkFuC}g^%&`cw6*zR&3S9LcP11GrE))jZelBu%bbZ~0KmmO4
zi2zHsJ90_TrKwxBNo^13<wpm!_F#xue~rUYtKfSe*QP`Dd_M(^>k4|Q!E`_f?IG+K
zeHlxK--dpZc2x_F{xr1lyg4O3Md~v92NHlm`#djQ?WKGiJG#c57*n*bEBoJOT%Q40
zL)0?zAtB#J+^%{D(PX;&^s5lh#QG$=<B5Gf4ezWWO~cPA$S14VqllN~5NTqB;3;wM
zNaf59K&(b{C}{ffKUy{)@B$}*zWP>996ix9Zb-;K`iXt5BW_B2jjWGgTr58I=}B{N
zbKr#W?|Dvo8kaTW!uFVPi#MSZyClUwi@GeZfoO8kbfNC|#vXt`6}kXg4fWul=Z7C-
z_XR6AVmV=<2{_(1eD=aUH=@Ws<Vu)K_F)y6zf7~0?PXMED$w4yoN9?wH0lizr@EX)
zJ)cHjW2;Gj&l&L$qzDIp_WHiBen0#EbC^)fD*4^oA8W~{88yb67#5&r36+tlU^2K^
zg(br32+5SvM|9oQ3!agRGyVAjwo9-{Ja_{T2y9)pzkF3zM=^=q+EqCDQO?x^vYsO&
zQw<6c0Kj^=5-2AkNEe&H?ZyF_Hs#X~neR29e5Fq~B<i4jY>9#GWuSE%LkHOxjR#nT
zeI3DdJC{0j<xVEyQ2<WqJNf}LdHT*N%HZ|mWy77*rgdGScU8wIOFRzI{zn2s6cJGo
zo-3V0=3Z<&$w-~Y#LWtntnu|9TTw+P6LGS?sFd}&nXdgE#vdksmhS~AI5`77h*+rJ
zSLTW}1ez*j=2RIO{f3efRu+S)71zgWu9_u&HGJOONv8;Mv#%TtieuG98j8xf9c_N1
zXMK8m4&JRGf6knj1gD%Un%-aqMNL71F|rt~${4X8ImQHsFhbO^c@L~9Hsf`po<jva
ztKbP<=KLXr`_7QPZ|s<v?*BdeO+YLpn+yLknR>9sgUP*idfI9m{|$a_Z(1Lts=eml
zaVZ4L69=kw=(F%P%+mM_A*==HIlh>)c{y7MFS=qdy4rgXcpXOeVHt6?d|&kSZw$2f
zgfBeJBMx}OGfB#H`H{9C3}?G?LL(%IetYTvD*+jC3&>Fn^|H>D@()H1b=&Y*Kv}lB
z%EF7hukP@HmB%%8@3V#_9Ww&Y9*Yw(FCc1g@>N;*SW+Rn@}%+*W+d_*2WO*)5Q}P|
zBT^?rH7v>dkyF15+gq^31{zK>c}z@pLa^#2Zv6zP?D7Lp9HulXH9@4T2S}6ucZ{!f
zOEBlgKL%F5Y;ey{j1#6pZrkdce&C2dw=`2cU2B-m`@{{gEP}-64Y8P9Q<}xcO%@QF
zN(7Z`DyWlChe|STjQXRVX_cvt6D8oTg9qbHzY@F(+eD+>0t5M86ySdPbh7HOO~obm
ztj>4~^L63%C3Y?b$2AJnY$b@{K7Px#qCU%$3p@0xlNt*`oZx_9rNAgr*d*CmVDf|M
ziF%)}%TwMWpDtW(O^u3j6Ba1NX-$ysP>~wx0FLosV5Viby!<BY@Z~s!9OxLB9XD2|
zEKzq$D9qgn*G~7bJ$KvW4=5Xx*#RcmGJ&uVuCxal76Z_Vmjb17&oqasI=pV19rSv|
zATP*^z2Q0c4mh7CYg!)l=f}G)I&kL#Ul>fh4`!hY6}{eZ_2#jA(OGwwyM>@;-}!1T
zkfp8igDGJ~+D=lDOaIH+xSZbYlx-c4f301Z!4tt6*=2q>tY%!=As>pKx}kjJR9)}8
zU7mIwH_*_~{@kkRrIAYU-BdyxO4}td`|arW_#>jkcTg53*#ho986Aj{rjnx4v^!L{
zI8@3zp=v0p7Ll0~8Jp-AWTYF?thxXYs2H~%v*I+FngavqfXM+z!Q$|YL^o6OVsvyd
zrX`J=Ok0sJAAwX+KCJ!g*g!dviMJdqy;ppe!`1ucE(v8H3MbL+MRrR`&Jn4;vM(H>
z>vPAQl$x9gPFf{zk$Ah~JZzx^OGe)Nb&yAj+>*GCj=&$bqR;nHbC|c<3$nQ5&@y%|
zvj7M#`l@9S5s^^WSd|Zd#<%Vrx40Te>TYInw&}4N8j}+&<VNzHWhP%jdchOao}$%o
zpP`{SktstOY!w8W2U&s}IP*fsJBvq0dr1U_gnxb6j7<qW2QbH=iM1B|vjF5^+PK9e
zn|alyw0Sv{L+v@Am-GW_oxBW@-8G_(tJ=cCqQu6TE0@m9j!&NhmHNETQ+Su7+80+y
zwn%I#UB&Oy`PSjR*5DRQ=A0)s`=O#qxV$;S>xzVNPdbiiF$GrIJ>^*4Odx@>=osCY
zI`iAJBh_0^!yTaSD#u%|s~UfwIB>D@YqH`V8poGt2~kI1ANgfhAWBnhHfLuPv6LMi
zF#Wv&xVrBaJVJgPa|dit)Apx+Uv|ReYWc+33%*iAFE<XhgO(fN2|gwlqPL8+o-4dc
z#N4_Xk$7S^8P{W8_99LJC9zFZmZ=iMyXTzcjLOW@QGI!uBSM=!!(aVrQKAtN@JqXe
zM)y+5zyHX8Vp{XSVEOF0cp2R?`oPngjN?e*uYw5_Im7;**!#*q)HWRvHb|Px@obk5
zY}97W!d`5o$JIHrp~Nry<gF*HrshUhWgOrf@*rd2#zFkkQIvv=zLVjdE!v^5vtAHA
zk&uRoZ!)SH*^&^K-c7JP8KIhcAHglRZMOoodTXJ8gAen%u%q(cJU`2^zdfqL0(rg2
zOYA^Ca=zfmb0yDZ*J);9pGO9p0N<r4xp(b_2t4@8_A9hZ7}<Vo2ASoeWT#~@#8Qr9
zI-$@#6a1eNN;|Pajv8#Syj*m>1xYhjh)G#9YvF5wYh-P_Go0+@6HO0$e;<e32;mjP
zWh0>TzH`hS?t~PjwTtgf`hTVa{*sDrwJJ|<{CENWGXVUq`+D^L-eLRICHRdg^#W!>
zxT)pM!UMz+?qW8a?`-8cCJQfy1fINW%bO-T<eLYMZ4efNtV`pV+w00|w<K$hsIs)k
z&uQb9v$dsuW&->TqlfaAdiRJym6G9!mfT{?Ls(|A%D_+AH1hD(o6sgs8@sI*F0l|p
z&68u#he3f;Hp%$zZs~jgXS;pokuzKcUe0SYO1DRqZD4`5l_)xv216O_k@?$E?$IvY
z0shWrR>8MsV^knbqDtI#1f~>Jc8l_+zl#3S6I3TUGSySuzhJ6tdZe8^j<+vxoJ4~n
zQk?&_zn-A9R_@6S6t(H_Xl;#7?UGP^Tz&-1zz$`)Q*?BwQH*>s7HVo-+$kH;nsjE9
z#!zw4{4YMEXtK4aFao+AUP^)Y88r5*Od~1`lDA1-FV0{mW4;SY6CH=pOGkAb_fIA!
z4eMJLqE84N4^>S8-k`5Xg__o4-B0lbztGpyl4IZ_1g0R-?w@ZIo0K!4JC$$d{!!+e
zG^R<@nCTZnmO@FDM3({oB%VunN!;?fl$RAqU6AfabQiCsB50Blf5ZDdz!=85SQ!qh
zI)B_Ph@2pU8!yV`(R+R@(p_TuMlS=dw~%{#&~NxumF_^jXApMMf$p1y_Wy7K@8rS$
z)~UQ-ug+SwJ+1h-3@e#h3oja|%NU(8-lqjVvaMB_`vrAk9t^8ZzvF0q)Rj1_Py({O
zkd5p0804q<+&Nn(%?P{MW+VBY*2dI&z+wqwqsQD<q>D2Puu3A2lC+6KdSxxmN+a#0
zfz-0@Lz<~}G}f7=UFR!C`~}9hvLNs@7qbDv!z2b8>y!{4U?=C^%g?z8Umyyi251+8
z@}X)qH7ZMRA-5iR9w?S3cs->$A4ywUenY*9G-F?9Hgcj*tJCADx5Yg7T<!CqAkC67
zG;4V<-n>i-9i8cccoEjbP7vYL8x8!N?kTo{GJ){?ARyx;YbN2~)|}UT^rVGgQw`HR
zl$R~#bDJ}FY{2r;+RFajd=BpLERr|!+G$Z{7*-^q)-R2E%^I`Tt`BIKR}Sj~7?b3p
zbrXe2Pz?q#cOfcqkS}HGF8Yc(l^@-*Z9zM-@vOv40Z`7o14&|3rt*JA5*`W8IZ94N
zA<iWiPyK>s(003$gOHXT?&vN}PS!Q{gBMir-S2@sU0dz;nT<7gL|`=KAT-N`7%G(3
zzik%u<N~df=81V?f4cK=?bmQLb-Z=*myu3$V6SWdiAc^}gqa`J)2b8T>C|?C`|JR5
zoKW32@8Kgaba%3&>;6j$ku-q;&{caUU|u*B=xBoP68nY=zm&XO#ZzL)B&Y<;nim?Y
z4%NEqB2thdDPToAJIz(O8P<8X&8@T}(ZRW_T&Hg<=c!oPEQ9*@M_mWNWN%mY2oYJ~
zj+#fI+V>sguJF)ZVr^8SOUT7uB*V)2#;kxEDH%?{rHVq`=uGV_x75&DTbIYj>Mgi<
z5Ce%ulrm&$#?n|sU?;>!gszbx3^YjC&<U_KGY-#gP5*XF-_a}6%mGI)evy=&m&(Im
zH}}wqH7XR-oRvy0Q2X9~i~^Rv?xKMiRV@|*ET?9;779}!LIo=Q-+-3)pf6qy8Pwcy
zVc<A^d5KqrONI9IT!tM}5g)EW4^H{d`iXxkNXK<Lk2KlEZUu#UEKvl2YjWpAz9rQ~
z#23nSr!R`KjjhsTPQT9;r|N#Ko%Q0!s;6DuT>gYDwz!URwzOq@8but+<`JJQa#HAZ
zzuD5YG8CvXQ}@|mMzds&pW~iNP@>1sdQJncOl2jMl34K;(gv2<TZ=t_W&RlO>z>~i
z8L}?It3V`HxBpkg1CwbLIDOM09uLZwFCmVI;ybYU@lwVVhG@6q33LlOmTu`Kvz2$#
zLbOI(Aywu0oPRGb4WXB)UAGnh$J`3@u@#KTQPG!s$v_K4U_~Ik$B#gZl#JzAilC8)
zk}VmHXfD$^M~B@WvDQvi*}C>wp62e}xFq`3BeF-mVoJrQ2`k*m=~iEd^tejClpYrq
zh2g`s(jPPK03ttAqxgAq%1T?At84}gulqv!-C($CVhVKPxBCGUb||<%{xVS3p)cqd
zV;=h((0soezwaBr;Qyf>2nl+$H*f*~AmaWn>cKygQ2?r*|4u!C|Nl@AOfBeK+@S#g
zLH={||9etVh6Mn3FqW|_uKF(<*8lAwDbx1fO-ld2<F@}^W^G_-V(mn0<Y?h+;%H$&
z`#<@-8s`6RpVAmrsn{!4gzY{hgeKNKz{V-sad5~)0)AD2t->2tN=1S!U&O#|(^-1-
z`w>N%3B0M*eG?-s#uXhMos}9tUd*S%AJY%3G!1Q2&yUgW@5FZTn-2G$h_1&*3-F?2
z2Zu*C+O)MPE1c)1X!x_UBud}g9OGToF1OmP#aS&*WbjR}G6i2aTG7M9;pgO@Gw~4k
z1d4j=Y5sspcH&`Cq_^lM!saD0SY#ulq*;<u1jrl?5JpFjn}DhJ2X0Tk*pf1%wC4s*
zE_4~r+;I7Vrw~5A!kyK@g%m^h2*HM&t)oVzVm?MMwg7~g6m@y}MX{wnpjbrX?<fjW
zj)qNtVjpkKyHK=F_-0NdQRjSUL@lEU^2|{=`WKa~vtMu11<x8w494?`xa&3BrAXt%
z^s_6l;`GO#VVd7*r{6a*$UR$9J22$J$s()U?M-<in#dV}<&9}0y3DMZ>t%-G87~bn
z72axJ;}?cc;j1G0Po{zPm1pKj_i}-@Tv$Y0Tjo;<(;N`jvMZ*;d#nUm3^oS1*`GlI
z`LRe;9fJL>{5)_=79382VuXA)i2IVDd^ntN=<Ied9)2b2^5k(loK#b84b8Y{yRN|^
zxm-m6e+ni=Z8Bv2;R&#QlKr0vYbh=EnM8!Ph%&m(ugA2{-CWRO@Tq+ZVd0-EcPaCf
z%7JCRTa6}9d2kc3px+?w_hmRe0b!FLw@-8;L18Cb+k;*!)Rpl=-naojZh1&bhn+)D
z3Kp(nWR_o;x3%u)01%ZH!jjsl=t1K-9R8Uc$|DdB2J`r=Bwq@D?@G+%!*9BBq>_fL
ziLzuxa!J-?uz>{&sZFj%1F8YjWXLrAEpG68Yu~{zu#asvYs4~!dh<)a&4v>__rdq?
zTHh+R#F8KG(<NnL3Ruhv%k0<JW9jRIG|B}tmtubqyo1hDPm$A15_3W@^5vdV{3@F?
zN4Xw_9~e>Y@~9`t`Gcx)`vcC@P_*5lMBI&uESfrnE$^3%qPr1+s&>lTOCFl{DTYkJ
z!!Egb@dZ0XQ)KjI{}jy=MB)2cbHZ~}p6IFAwMj?$<s+__I{E1%y|A`_CAyY+TOR|+
z?>3HwgDnHT_ysaI1>~KPI%^4ARm{)P&cG}jb>dYdDpa0=b{QUZV8z%r;I}Hl3BN)F
z(*jld8B8x-FLt9|8l^QgUpIwanOvNG;xc=W5v@MiVsWUz6S{nYN{6vOkOAO&xhRlj
z#n+6OAG(QUF$%=PQx(`KmW5@7Z#?2Ynn=}(Ln*h>*Ms`-lUguR>^+ELL&sfyu^Eos
zV&ZbM&fH}es=I}-v|DJ~{FQto-!{LRaAeTYUy5f`pMgAFcm$$P(7oy*Jtt9z!QV49
zz7Ld9h>hy1sW#B<M{d&k3=ixnSo><_+V0vH;aHL}-`)#Nm2Q#D-25&5^c7ov<D<{h
zF=>~<@1?^dcQgEnvYMps3Tkv`B@x6W-_Ly>*1z66dkeJN$9(aIoJBxyFxyg7$D0+R
zV#&Esoo{BbbN%~$SQZz}b9)TKqkrQ4`L^WupETO@^obJjFA*9;|DT|NlaBwM`3V32
zY4m?(J`W@7|BG?1Z1I2Pz5n22X0&D!x7rbVzbMt6QcnRLok+v3IsZ*}xZL0p4-$v-
z?IZc)kfpROFik_Bk36yfBmzK29<NtSP7o`YI~R5J{d7Y9ehH=W<a8=ctTdr@9?SVn
z<oe!4DlWfiEvUR@`Er8vO>}U!6fOv^K2OO#W<RxZ9l3>YTalrxZPYV<y<f@oF;jh2
z>15&l(RG@U;_lqLJmbH8ieR}GNfvY)D^2O(uy~*o&BEDv5@?azY55abJLQpMLELgG
zXrXGb$Ej5OidTVbRK1}=DLl}El2UG^Y8J9rFAt=pJZj#C%ZripkDR7A@^{su_T{fD
z>bp*Alv)AipO8j;V8rKyH5N)b7Pd|Pk3X&*hhr?M*PO|t%`wWa>b>cmr9tDg)a<GJ
zLZ+z3Y6F5d>gCu^nFAJMLZuBK8d;GGdx2+)77=`Pg)7f0v&=;?>^!F-#wKHpPUKIu
zWKoTwDQdb{+$y52)Il!aEhfc3h>f7WUyG62*6d)b;VJn9F={~u3ezM|;_3q`10j6T
z^nutKXraB?A^3F@%8tOj)DPgZA%Ws?adf5B@r3T8wwCHsmp=!rLBL^Snz0clD9eJ%
z+Wk-K%9lU}gcA`c`QlSTrbei?=FpTBw9*K%uv5j*Kv#R>Om`wxi$-bR%%5HBNsU!p
zBu=b|X9%>XobA-Pp0-|+wUy}Y=V?zNC5rK+EJaI@hi5wz?>iTvX2x>iyplu4Kbs){
z)!%7>r07$c8If&cslOJ&Q;7MRxF&yzG_s;TQ%L^yboC)>Z`+|ePNp>1NDH8XTo^E@
z?Css!v1F4fW!1kri@xVJTYNN7X8cfXUH)UW#lwDWF<V6avjEx1P>oktO?;T&HZ7Em
zP-$ddEpiUOQFA?vuNbb1Y1{jrB!;xw0PToGhQUco42M8aOP(mQZimLJ+D4Cp7fqn>
zBqEe7Uj4O5e-WC(gp2#*Vl0W-KQ;lj$%iq8TiRccLf^qNgVq3hK<N?V0r;7B5Jp_L
zA!V^6l<4~kVS?-LzM^>eOll&Xuw0!;uhmK-p)4MLMR4h6OWi9X9~Lgl=?KzIu?mLZ
ziDC6mOkn$w!yy^GV9r1GfMFt{1g%>PGfX)TqJXK<jfc+RG%}E;k-#DjO|2ac)7m#Q
zuHQ1dT)fK=V1=(-2phR?NQI@nTYFwHAE~LH?Xenb0a4-F#tu9Ms-#Yi3iFK{w(ZZ-
zkK^R>qk9kT660S!nlqM46)gmVC$;Hn9rKqoG8O@QiEl-+EEoq>j~u?N!9a!5?XM8O
z7cGb4utyn8sGri^hHB9ntv8ROLF^k{#|PZ4ZefI&tj8YET-EhRREQSV1zw1FNhvvT
zh)e?&t8Y>Bz<B=%2>_PlbarK!ZA<d0O%#NfxF5<)L2b@uOFgH=Grl04Rd8gn!j^@X
zPw9CL>xE6|SQc{BdJSVD@PObd+OrXB)SjjeNLw%O)X(Km$6W{?3G)h{k{XfBW~nJ(
z=Ll1pFiYL$d=K}qxl8xydFi&E5r6fk<lg6Q3=m*-uiejnoD>!?RZpp*+9Z%Be!BnQ
zQg$+DQMqMPB@oAKDR}3=-lXOgTusMWetoWNh_IYyqDYWR*g8YjLgasc-2q!C;#v8D
zZ`-?8N8D>%rSZTq$etQRpwOV;R9AKyyOtSVJGA5y0I!-nvx$qkQ}YDbsW|0(8{5XO
zZJa4JC7d<}Nc{6dNt);n7-Q|P2P(VnXUX|BT*S&B4n|!YQ?Sc1`V{mfoER)*2zo0;
z2^;T~79%BXmI@U7Lp-^utD1~riySRzEHU{gq>AK3>drb_?5-_5?t*P8A>(m`yse%b
zUY)RKxy##!aZ*|N*F3{7d=qbe!`p!N51D0HtLHhlx`Z*B*2-pnc^Mj58T&P+?0#w+
z41~s#qew$lLT^NG+?lBWSlLgN1)>pg|7%Nu=sB!7<*608Io|Wn`Ndb`tbqz%+6&M4
zWao#kz*K!Vs|0acxzXTk0Gepj7cEPV;#1_Z%Tlx^ejiY3=)ep*8;WCpEq|z_4Z?t>
zOh4Fb;IzC#@4AMvUaZcEDTt2|Xd9&9kzuh^f%hU0xeH{*ulX!Kv5C4~$}xdJC_u~g
z^ySZKGO##c*m*E*HrYsJ6=z8WyIzGaw^`mT+sPG~1MKOgAOC{a)^+8hFV~SB)^dO;
zFvBgIH|VuB%mGlZBu&Wpr>|6=L?Z*_X({0fhVllXh2}H>9d$lc;E46;1F{5(&ftY;
zel5tfIKbXj!U`cA2rT<tEC3>T%{{i??CTq}s#1eaLw2H5*h>@=Ir%-CUb(`8nO1)R
z9DF+NVSsn~t0X?Zb^nRR71gGElY=;YUZq()Ag7HZbDD8@T&t`)u6`tWYTS%31<TDB
zK0{r1y{|T;tj8+S895y_RPr-rc7u^mGs>*W+rnd07Mqps{iIXB_v#caw5Br?Mg%3;
zrnz1SffW~ke<36je;`bX&s~5n)(W2^1r&jKKuIZc_FS;q3L81J`Pic?X&jCA>#)Os
zY$78l&%)yRW}>mpC;*_+5e;UDC$OC7SbiO6`|P@#iO<ibxF~93@J~{?j(1-}8P5;3
zy(POONOs;CIhG!G*(|!g#noi<v+&7;>2Nd6tx}TU80(04A1QX{&YbgPO&v;8LCIm=
zu~34!C$_~7;!B(DsKz=vcD?-7?5GO+q2tbgA+DfT0csog1KgO6MP$XzLaoS^l9_je
z89cTO(8WH&$iZnbTPPn*xX0Q^4}u2AV)$RxYPP}RwQj4dw!!hZz@hkEuQx57qH%a5
z(YM|82a8I}PN9_~Gk`hk_eVUYMVTk`KTPJCfJ5k?X_zsa`5}o!=Xu~r)i>RPF(BAQ
z(1kqFn^}J=d91@Mgq+njaX#Bi#)Y3Z-^$p}HeEx)LT=e8ia-}5iEnm+1+IGT?CF2y
zdhRM6xUzJAJGWZ8k`~@y!QKVxxY(hE;a8f{dlB?}t~&i{GcgKFcPA@_41u_4kb-+(
zNj*uFr|{o3KXjIq8tw;)ExW)9AM^_|GYf44H+^Eal-P#{vr>e-lMLMF7~yQ4U0Lt*
zu1*eRnJUTe*o=P>SjrJwndAipKr5DpRB)x$f}F%*)!i<890svaB97Zx62x5}E5D;Z
z#bor{G}`3tuDi-4YTp?d2{HVE)DlKdX>@W<l{NxU`LL#LrBYuulS7%*O3wr1-|^MT
z0b%i1DrZFRsx=b$*rW{)uD)cN4}Zv*eH_uSRGdZ3@=Bw$)t9NYBPmfID-zqAP4ni9
zK2%yR3Xe<3Ss}uwDpcllz_;BQY@ogey2$(lE+2eaDmoWNh7TAI6MOO8S{mAjS>QTp
zr7idr+9TTwmU>!yV>#T{9=;L-3OirTRoCbD*Ylt2oXJ;@YfHgQH#Djudst;%TpT$L
zpO|5;ZZ`F_a3U28eY@$`)tppiT3s@-x=#_$x0oA65TxrgyrnzzUkXL+A{3IK(GnB}
zdLlNqHc?&7+}aFvz9>B%)l(4OWLiho6n&xT4x-Q2#?+R7YsI5!&p;6CKU{?gth#X)
z9;^2EN*R3~C^5`sHEa?v_70#-V$NY$J6~*t2|PY5h1;i6vk;l0*M&BQwq|7h<Ri3{
zNpKVTiV^2^k_Y0wIo+O3FdO5Yd)?;GAi4_+9|dhJ(QpYq8P#EaxSKDS#_qygAP;H&
zDG^~zuB}=Mc4w!em#qJy_mE&LIghodpO+c9S-eTTHaxLTZ1O*gx~2jFg~QqL99G3<
zMXE;ZZi{okv*?i>7)n~mArYsDHlb%-H8+=tfd|I43wCUi5PaD|!OqF`8dxH%lr)^^
znMA(4%s&1;n_R>*a^3aDpo0-s%3d&@`E;~2D;MA;m>g4_3^_Xqr#1EFLG3~!oap3x
zSx56Q(BH{5-Llrn{Eb$6M4FIIK$FSEhxfx9{UU1k;chH!pMOD|Vm2UMpj%F_?(S1)
z<A8ZHWj6j6%%#&_&qE;F`tyxWp7zrhp-h1sK8}S3SBJ*7(UinArjPiv2k5EDhF!RX
zamFWrwS_HT8{)$b>FN7<p9lX7`kz9>B;E@9^IwsX%=~{A8n24S|BX_K^*<IG|C6!;
z&?0Wh@DEJctU+yI63-(G!T=NUm2e8Ty6gpnCENzfOz^KC%ZieW504Zt6ynC_l&k|o
zHoc@Edhbg&_b(3|fD#(<FoPUCJ&y^DXsHr9tCne^26$k_)Z8&+!1B&lXOM;I9jtw@
z|3pG^_2yB)6BRn#`as)C)0DehYj?|WOw!e()DESfC_*W}b9>|d;)$CO+OK{SwQkf%
z?3?{f(XVBUxW+0!BJpr1`hvv{JaqwE;2K9h$?N6CLR~VpjwJB7;?}X+@BS;destob
zw?uIo0TXn@m@nO(YO`9e+Yp`3Ro{&^FN?;!Bu9YO5i?wy!#m)AmXt|fVeIOkj^zjV
ze=aFW*MFD52>!<<wYISRzm#qz|JpnLL;U>DHAYz~c8eZnXO1$sx(Fw~OF(T2o-?Wg
zV9eA=v(Z>Q8L;Tw#xYd8AN|h>iA*tBkS&Y=%ETMt-z$lV7}79@v0*f}yya6a$9u;$
zV7t~e_oxO)W=4-RJ)XYaZ;YZ(ZZ@={#UU1pD$hBv<U3D)Nc9Yl%$N)_WXK&=2{O)=
zAfmB$cmTyj&5lS)4zX!-WNTEf(P2u)<2Ep^2<otaLT@)U{jN6@rrz?u?4SJ-R0yIy
zqd$(HqQ>z&u#3oG=bCmj5`CzNnhw8a6Oy5I7%>1@W+Ry1(<=hvg6Y93yk^hY-SeHo
zC3`~5|Ae{)O<}Xtq3Lu9x#QHKn&{eO{pNl?9}MPTQRBf-rGCi(v#gS2bkTdmF-p)%
z4?p>`QrKw#C`W}oGc_xw5Ep+u(T+KI<%Rb9%^k%A5SkwIJIn7nx=*r-P~9`0<_Z86
zI0FDot%m|SGlyY*q`4o&8V=7EQx5ijGn)zm{L@8{L)rs=Q?^sgYwc5KZz{ZYfe{*J
zq74t;p~JrF1$m{{+ed-3G-9-)Bt28<kh?u#YnJAJH!B1`NjFqLdunxPNvYF{p00m)
zlHsLzpYz`d%YT*;Oj;P4s5~3_9Ij4J)@N^@!Q)91j<W5i=A+bz!tyb@DZJ)_T#k%)
zEXmxI?!FWT?;KmCR08+}k}=O<Jnu#{!D|I{JRhIG;QteOyPcvoFhBqR9{&)9|64D`
z?fvhONAf>Lo}-DAor|N<|0VjkO#dtT{<E!n{_zQM*i!es{6zZYQWGu)BrkRO>0s+>
zZd|wUEJ#}dJc_9*Bu$0EoQN<skTI^ed?R}W_~iLo&jcC8!H!Z@QRmTBRM9-#-Q91~
zet(n{yqCsR-DYyWb+wm&Wb@{9YNY$pUV7To%rvrmtgsA@dlGNnL^C9PpDN!^!`k@n
zzKRkmeclz(YZyD3M6*?{da0+`x@M;EjlI^&qZB$vWq8e9R9g^BEM*J(X{N&FdKlpK
zs7j(Q<|J1`z99DJMb|>O%U8L*!Q_oMDhrdv-l@L7?>j2-c+ug`k-xh_{PxTAE_Dn#
z6;le))YP5Sw1r7IiM3R6x)iH`uYnPoJ5>ag>l?Wo-A?hZ5#O^8H&s&Je?p&zBJWW*
zY6t1<ToYjXjrYBtlgy7l3L}4D&TJrHTdM8+i&-88^}hq(fwgl)lu|2K?eQ)B`{!Hw
zM}OAv?mpe)eMI)FDigba=qZJDl>N<xGe%5e{9xS3Tt~(v_x=Qh|D=7FTM}ZK*bWpb
zz<k=(8;l{)E?5@KL1<N20ncNX?1R+wmRAKf{cA^5mRxpo{8eZ*^|KhxQE<C}?iidY
zcLE=;et53D;q;OcdxuTB9XjjueP?{oBx9A>owzFuSi;~h5LTqaatQ3Jvsxd#zk2uf
zd4~y8E&&0cD%NlM<Nt2pL|oMyW>tVLq9-IdmKLx_b&V+b{U(rxON1SsuX-<8Ti9v2
z9*PH^kCk8^&%Gag&*eg3so{x;YzDJ8xD{TV)k~9FFI6{ifZjet=}F~ZB~$;tcAqrH
zpRmyrGI!91Zc<FbteX^7f%;Gi6z@1MidEc!HowgJ_aV9t<oA4?&zs{J;Q0*Mw;9$7
zbCb^Zd5`u7-Mh>Es#oV)2x_`JV0#zbBPFGGz9_56$FSRHqqgiVBLz9o&xu>2cwcGU
z9(N)mwtR>ei1;3NhzC{eoe}ST```)verznL)lG~V+J3Jny1l>fb!LCe8KVY1ay`>W
zPBvRxfZZZd&i;eE{X7;gJ(<NPX-#36??7oCkPUFw{B4BJ`5uwDipBoLWkZG3yA|=R
z;#_=z@0WmeA{LY4TgapCfXkkor5>^P-QG+vtEaM-?E4WHu$kH%mKzSCmZqC>pSiyv
zoY5p^5U5TNBDJe9kR?1NtLA+YG6FPlhl*r&k@>QAC+ZX67gYtGi#+Z)dY_H@`C3g`
z<1}5#x8Yc)JIQ9PIn{Jac4$&Z>vb)+{*sw=pO?Ri!c767-%TCl+8+x08^mGijUT&Z
zcqCyjkC|Vq|G)|fwy*o|N6N!o<%*if9h687Nr0lH5EhOk#F9!T2rz|)O;%6MH)7fe
z0C7UQXRug8{r8KPC*#kIAq1s*Ye}&ad^nAl3b0;3?tRgr7XJj3p_KR+KpFuWJpU>v
zgd{*Av1SM<f`oq<V&*Wa1Qsh$bR9Um*bE#Eq$<E>O1ADAev3I=WpAF@a|BRt;+9-p
zF2c*!w$gA6sCm47c0dy-fAda77w0Me_Ft-Hg+uUrrd?TLspCG_@-lm-@#zH!e=Cy`
zygnfFB$jf)_SoGk=zI5L1?0-<=YUiR_NXBdTvKcm;=)ifI*T{{BmW$J<qRZ<rvoXw
z8;V7Z+I#`_&;|JHPU1$ifhP)<?|%;qJU8MgS4x@rZA+RPxtzxQzOKoe(RMQAIhQ>D
zz{m|_A;017<JlwyFaJ%uI)r%4&ZCB+bZ?c^X=1%w1go$FR#rVf)dkR07+O~4hmvOi
z6H1z&BR~k-&|<n?q|g@z9<#0H&!3_i>EAFqn4hdg>{hIh(jhSKC&xl*sK23cmwHK1
z^;cCot1tcar)mTd$vqWPkA{c{b!TflDPqqRfD9<3-3Hy?Yquf?(ZhnZ1HPVEZiTfo
zI7^5!U$dVx`}}6r#Bus~r_Mw<s)>~RbI0ku(qz5sJcH`CVLBvBlOz9^&shy<CjkdU
z)QCn3A@4oF9*o9{hQE{iVBIs)vk0)g(`tep^ks3MPwV-#|99<^2-01BZZb48Z>WT+
zL{O<<cFU!ZlICfSvA#m7G|u1t{pDY&a>Mgd=Yjy@wtc(dk4sGa3_&8=H-!9`pEn?g
zaZ1+T;uG8H_wBVyFX#=Ma`v44@^*jUG4X0>5BL<&f>e{B94INgt8goPcdN8S$=6PU
zhblf?;VTdu*4sb9T_oDI@G_kWs6>ZzXH)<Zs9mJ5v|4fle?DQtm#*<oSW7=e=j8z<
z7hQ;s4R)z02_8YzwSV2vc^P23sucuEvE;WOIKl;S@DAeEDLND@Two0(DY=2`ZV1dI
z;<s?DEO8uo>t^+3ZIib_Z2xGrw|`S=8-pXTouP!z*j>17l%A>KO10dmBS_HV-TVq1
z&#-blp3qhVI}B#gup3bS`VYRdo1!H5Qsvq?IWj+8)gh&??E{Id^{vDU@NGgkORCRt
z)@Dfbdi^N^5nQhOq&ws}S~`2;njnf{q9h{;ha7d*MH6D>XpMkNr`<3|3yF(b!LaCI
z-K>U<XSbkWXdNK#I6Cl}!U4trC|-Sc;DFhBJz<k5vuL6n@CtAI@BO5fcR<R;f>H?`
zdbEW$Gsg)8Wqna6Ie5F8ncK+t79#@dXT|WcPV_93<FSaif}ej#Y%A7zLJhmCID9IO
z0suFFOt$Tuu9ac}Y(XSOky8p#-gWdzVRV6xe^7Gp+5yp3u~fM6A6Q+JC7>GW28k~g
zIG5^^<RvR|<xk&mZrH3CTuf15x_VxV_cpgf9&f_U9`iq~G4;;T3pB;1s!#iz2Nysq
zLy+r##KHk_X=9l3``}3P_{BIveW{>8Pi!qdqyG@G8Wryj>Xr$N{{cqKYiWlYOt*)`
zK-PaF;jviqT!GSiM8Q&{l5;{~Q?>Vd+uN-?jBQ&@bNxM<`@;9z^jn<4;|-7ao++X6
z{r=eV{hpXob=IC#xgr7iD<$3PbwkX2E(K&g^(9&q7MxQM006EsnSuW`=xEd40=F?n
z;1jRga|eJ5uH>pF?5~xHgQrU<^oE@2tbuQN%KTJ3#U4mUd~XjA{hXoU2T}Hf`k3ey
zsGx3wDPevGH*=~s2$MYoSn`!`3JWJ&Dm<);u^CuK19EAI;R6JEaP00HM>fd$T^yWg
zI1E*Wma&Y&hi2p(?H~<_60s#;4oI&L@PXPr6`<&+up&|}nFHbn-5a{lEE5&;VW$?T
zUuaIKDTbOgMh<IyaTIZ{WsFV$^dOcRIwJurLKUD{5hPVrG}td{v|dHPj^#mu1{k+b
zp#o`m)jt|$9lubR28>WFTOP~pEn8>sN>A8g8n2{OudtI(Hhs%E{3;$Bb?`m3dM<0u
z@8zEpUjq-(h{@bi=;xulIgjuaPp*CrlrS8e5fBj{pd9h=!jaaG`wf?I^OI!hFVlp?
z6o23qOB_TG7WxvxEe6=7*`g{L5_GmsnP0+R7wv3N#B&P<Q&5)XgE;iY-YJcVGlE(z
z%8Zswp-q7L^Fed%@zd+>l)zH`OfAkF?}8HaYMKgLzp3sVOW_ojd6vW5h;3jM8+7U>
zK|D2Ddwo}=Qv6VEpLOoWK;;sj8*qrL6H(0~@?d@>xDrMPbW^x=1Tc*PI>KxT8DS_z
zFb(8BlFi)*e7kqc=kkKP7+3!4hIN0hz=lGau53yf0SAMC@&J}BVe<0A`3PGhZ{K#4
zw*)Up&eb?xR830@ds;b8MH(raL{c4z9V{86e+C#@$WVMi&CTdf$v`X(xM1w9?u7tC
z!b?z$^6#6rh@6S=!sZNCFF=H&Dhop457YXOB;3A@K3rrtKO2W9A&}Yz?WhC1bV2ah
z(IUPO*x*^=G{3xRK<{~Es1Q~&1c!mYVM}sF09;|q2M{fSZ~8Rm`X|Br{$2baKqnL&
zYkzK6zKNL_)PewjfiBkmnVZjQ&Nm>eA)G!ndqP?2WH`bUcPB+eo$ou0T9`(<p}T$R
z!9tW)G^o2gha7^uyy7N7)`#EM#Z8x5eR#P`4E4&UGltYaU7HV&G5D#Df)aVO?jnTV
zWmS7}*(;uiwD;gz1kVJk6PRA;g$nfN$bL0Riyi+~JWToYJ|5(~iE{aolB21_WKWcD
z4SAh<KMcJ(+hepc2Y^bIryu!#@2Fx?66s&V*Epoa@0gqB*jz<OEBd^Vk>WR6%u}Bl
zuS5PAe|TdA(T2Qt^E+frc=AfdDCwls^s)S{8tR2YKqy%8&*Nyh$datX#kOzW{y}t>
zPC13^;6>3Dqi(UWoHe(>rd%2_`5uf4j)y{zv621Ap>q1{>B~9(>zL1Vmrx^wY#C!}
zaA^9eiryCRxaIoFCEWunW$Vv>Mn}qn=!_R-ls&`AY4J0SNrJl<XwEVoyLzadJdCG%
zSBZT@49qZl6C1uuQ_}3aNH;r4RFhO3*6FZqB@V=rE_7W_Cq$Mah=o;P3a*zxk40y`
zX!@yL?OWp=tUjS0kx7ugqNjW5ucd8R=kds&Ap+<jD*FdWq+!z%X7!OJGCibq8vVJH
z5HRIfv)Y^7$%R~w)xNv8S;R5vm%3ecXnjmTyz6#oUV<Z;!E7q{0EeY}!2B-)%;2&O
zS<Z-R$uUEECu;42A-Zi6nLF@;I;;k!WzhWfYP(g^W`bk??0SK6T|u{D5qBJF89b<j
zMQneFc^z~?%|V4oG5t0;<AtD55iPBKN7R(v*94N|Y{FgEPKzU#RC)^16*8GC?N@K+
z6(lJ%vd9rXBUi*rt4rF18@JfnP7(fu<NZu8H*RPlN?1C{+WZ}1WW)T>YVy1qOoX)g
zy;c>n9KA-APOzE490Nt!r78}K&Xfjq#MX$n9VuB#F%b>w?Z22{1tcwZACT)-l!l}f
z`q>uko_;!F45H@VEnek3orC`J+Wcu*3LAiwrHYl4BtF%D=^JQn=npYn*$;R-aai?#
z8dxA1gJRI0GT++C$95_-xOo(sx=~JRe>M%b(-<)K7uFtG-{~$p#x)I5kE~h{Xbdc(
zqsv=m)|4@#pUe(D==LZNbWzLWxRo{=Ss<I<6S!$PzIr&tA^)2X4Fjv*4xBUdX0bG-
z&dV=;BZDTQ7tuf$lsGljcE&1@i=xS`?=XpkoPcmB{nr4a^p&L$A~~)fW`oB_${JQ>
zL^*qG+ckA(7x3#BqO0mti8yq-kh0JhK5SI;A2Z2&@J9wR-EwuLMa?!n{sW#>D)P0#
zt_3$t%IR^rgb=2o4#ieq^W9T2;57Tf%kIuU(snOibPr82m~P|KQ9!PMyTN)lt+2<n
z$V<m#9W?EYagwd<wGM<je1Ux{)ad|;UJ%13d8>fB+EJ)n*+m7tT|nR=BtIH<#D6qV
zM;g2%L;6Uq5y*v&8*@Y3pslCfj^s=^E@rx|5QuhTBVBNII9r3%#ed#lzQ)@HFynRG
zqDbd{)XDo<nYiOJ==Atd=iz4!UpFJi?71SSJVi`;EW%PWJA2puHr-!LtS`c6&N}VQ
zR(mk!<N5!g>ztNEi?%JBwr$(CZQI698#`^=wr$(CZQHDUZq&oAia1a659U~F%-(uy
zzxo8=e4%Gh+#D*eA9|=)7PxNY4O)vyO~Ru$-l_^G84&&#x~K%U;1rDhAc=*;y%hBR
z=s=lv$s}dLx&rc*TXq~#_14~QuauhR7m4w$lESo>sigl%yV+~nMg8j>R2R>6WD9_9
z%Vc)aAsl4V8Prr;lvD+5z1QhccA@ZejMCW$Xt~(vnDMC9A(eK)_Mp|Ts3^SAiGnic
z?I)jm-0Q3yf@iW)pi@w>FmuenglVpZEz0dIZH>%P=(LVVT(@FabMrS=RpD--pKRfC
zh!C9w0~C@qODd>m{>Mwuby*3f9T$AaoIw8$sSuAN4-8Q_)<O+DZQbV1Re?e1h|L}c
z4Y|RujpE6~!Gu+B$`8|URBhQ&CA0zVUSAwV`|oeGEJ#8dixQVZ-3*y)3AUc8_nfQ-
zJ1aJPD7ZbA4nVWUum$?7gz=7hB_Q^*oN_BSl-q-OobeJDi;T5KV=q1knr=7-(mvR`
z8bEN0)JZ~Isg}tY82_Yd109~D=o|1XInt8t^rKGDVB!}xGU)^;!PaG^^`Ae9jBTP1
z82H=Meh=Fe<f%q<H71Ti;~Ii-n5%klPMhn@WZ6pR%Re_1w^GhN!{gI6bXHd`+Vx5q
z_IApg)$sz5O!En2P78a?=Kgx3E^2A^IOg7tK<1LqMC9&#5-m<kFsmBr3YBc%;T#>*
zeAM^Kd90TS3u}ab$|Z<+pB)_^S(H+lGZwc;9L|by-$)GMkpHrKDd6i08#2O8$~G}h
z$St4W1`zeef6kIWj~??VKL=cvCB}ZjGhBoR1xzlAOVRAN=-EdwxM4U0R9u3G^`c@d
zu+F-s$rBF6X&5F`Cb+%a6hk^H<KW_vxR@avAapFwp{8>8kJgCVnRfDD23CpPJ56ju
zJ6TEykAp3is$;*a#F3(oFZAF+C6?>-D<nilM7S^OmO;3x-0e<$GK20);=PA8Msk=&
z0zBM_U9=DD2Z7`|=m(W+P6?>rGM#Zj0q3M_UGB%>R37P1K;@i;TplL-mX!^GCO@z_
z$|DB1T}&*cC))@F+95cxU2waUClDoiNtv|dICm*rsFysVtrZ2#BR=6@{Dl#@E-M}+
z{0jT#6RzPvh&?i*c&d(1m~&YfQKkY~JvC7fiC?E0*1Y>GX$g5(G3hLxct5{@M1g<X
z)o!TR5m=gk+w=MN4ULI2y|(AGrtZn!aVy-4{KW=-Ytn7H9yk9Wh|mgQGG8sJ!0l)l
z(j9?^-MRzN*`z(G>AkC?XSD4~#I2CgA^NiTO&id~hAvI$7m7*&oux-1bC$8we^`d8
zeLPsHTNAm_{Ek(pBKe7IxVo?+X&aW5lsi%&hKxxwBX7<vfr8vH+VR$3Q|ZS--<^ST
zoG^mITGI#OTCvN6<9_fI`ris8bseOo5Jvi%l}Xk*m$<DV{#K?Prd37seoHBvK5Zup
zsjrqW5!_$L$kRCmj!Z3M>Q7R>bQ&qA`bY;23I_whANm3JKvM(%lf<z}<+)+1IcKFP
zIRNbNc7TqkT<`6Gz*h(ZM2%c=v}_MmFZ*kkH(<4Th;HmX7q{OLQo$kAD;<ZO_;bUo
z8gwW!E3Rn#iEKZcIy+%0_})Hxt<33E(!eKr^P60q?S9XrC)6v^%0Xx7MOCEAKM9>L
zuahH<iR*y6nxUII9)F;2%OqBT%LaI|JhN6|bQ*3M=gka5btWbG=;o|_rWFT%&O8sW
zn#xEqh6e+ts)ZbVI9g$()JN1(&DXEw@0@5yK^RVGsnsP!{f)2k1|3`JrC`+w^+81a
zIElxBGnp>9<s9TBvMkx;u&Un)-@t$Y-{C#ukSCKyE{adzRAq2z%>|)G650PX<|W6L
zt_=h1s9k!hs4;t(&p26JhOK8cc=ON|tX$!{@UqoMZuDclxBOwu>~<5)9i^zokU(;O
z(liMt`pCpgG1#IK)?sQQKfqC|Qh;#csLnW91;7Pd12Fx`34(5OU}+ycBjbx*9}Ir|
z(B2D_=qG7pLs52${J{PJuX0ORi3?vS-F|SOI@Z{gupQWG34~2aG@sbKua>QbANBDk
zN?mdrH_LjDSTxD~6w`_M<zx%~4axn@)qh>5mjAIhS-57ZqBXZ`x}{I^(S9+=e?Dqq
zV7tuRU{oQZW<iD^+P|q3srO<7FsON;*R*r5NUA<~dauW{jp$MA`54Fm7W-=6<8O-4
zbP##4t4Xq^p3+afAvk%v6A(z#Hwo83462WOko`{RnI=XI*0XffH<R((6?DJQoTh(V
zwcO&d*>i$LGnG%Wikno#mz7Q8mitEJ3$m6uu*M0nlCz?5p`0~dRRJ4`k{>+ss{~$4
zQHPzVljsv2Am??ZxvBz;lU<(PlE0ek^SQcWx}P=x^^ggBb@C|e2L0lpS}gmBCof)L
zd#5A~eTBl@33^EVQPn$nM6L&X%cuzUUNXt$z|h*LQ8Swm<+*TAYqO=;5T|Wny4ge7
z(TE$w)b%W<PdYGB-o_0Ye>`%Ql!r$)$Ab$iv8_p;dZTjh|Gk6Ewq&x_(qQhhy3Dbb
zT3&vgd!Q_|WWy0-Q$lio{rC>$nT7A=8@vn5V$iu%R=+m>jlH(><J9By*uzcZraAa6
z(^(-&5tU9FOzk-hgHl@R6B29p0c_h}{x!DG+Hb690OLzdcUib{z6?9T7Pk`}f#;5V
zN}DZ2w8fS1{k_}2#=8QSeE+`dwEKPe7_4#sJmLMh<=^-9@%+BLgs;v0j`u*_{e?$M
zl@nypRkF#h)z)V`Fse}e<*Lik*40+n?TKMA*`FlQ#j-$3W*LkHK%?qo_Y**$vUqP^
z9LAJ{9UGb@^XDehstFPDo^;Udh6TgB-_b&uD(GLw661Mv2SMB)(q7sD`?eq8>?{jj
zrbVCJ<9FM;gl2o1?wjhZ+vW!_U?&WCt^w4U8&h$=b~$1Q<bRqIi=HT#`E`BMpUXUh
z?YR78Fo!DwTW4cADpqMAG$B(q(18S3Iwh~poM94xs)OM(=R?L4CCMKDhm7wxz$n6F
z@*m#FwdP)vN<weu^6K%}epN3Lsr|h=2y^k<ctIaQBA#JSvzX~IJA+#6G!~*guND>r
zY%USu<W?M&7aD)=ehU8bP(U*ap?NH94rHW}H@JLd)4)rHoQ9<_q<M?VE5dmXNw~`x
z^JZj|87Z)7=T_dHvduUNA_T5T*<w2<F;EO#gEl%~i3a{2`XMEeMVeL+H01Upsb?tV
z04uikk4du0ZemD34#yjdU?jZM8>^rsO0+YE#fW|7NGVAga`Si60oc@)9b#%~Y*0;5
z>AfxOvOh@S17PGlh$BaA=?KTN*Hlc1N+GoD&o(K`{DFOxJ|M>UW3~S*iddz$7>?pr
zSM$zjUuo9FtfQ$D8m>st<o7ls;F%^ZTTY0s_=k?9R7mlM{38~dnBVZ>Zfv!UXWE!F
z^d}mf(x(i57~U3<RoDr-lMk<b8U|^<QEUe`RRB#K7pULnnL40^nKmWT@R-1~Mn}~t
zDGB&D3Y8a2MP%j9J=oXxldp1Pw*NCL8y7@Bt;~8MMY4x4Vr=qZlHig~@QCO&3(xjJ
zB+JPoWK?QEm$Aqw+`Go__<qd8Fe<DYjvJd{w`48_QqzY-o+x`Y*~y=)IV13OExR1A
z*)hUef;bjyP{_uoXkdXeXOxhw)f6ZtJNTgFFgai8=y6(6j3k=y;ToIs0xK$a9qI#_
zFRa;^PwfKv&=M6;@GJgb*Ai(J7Gr|pJ$~mP<l*w?9wGqFW=TvCDUq!pb`=g;r-^yO
z7Lz_n(?>8z9p+_%c{I3Rw#^;BgEJjCYZIYp<LWg3eKrLVRZ&A;wzSDzj|BThNCye%
zsa|?p&yOEH(*4QrAClbwXDyr<L2vGU3L^YTx|V1m&Kv5Lv7eD%ziUCaEX-Hd?PKd}
zgEVp@2<gIqwW0xAEa|c%!$df-qljjs)g)r<uxxov{Hp-gW<szo64Ntf>+R+2^}Vs$
z=PK`#29E}O@cl3)kP^r-CJ-k(QzUzxX@n!>AtNJ8W{kf%3on#8SUNFs4YGW{4z|`)
z$lW2w?G#qK!c3pWdNeg_FZW}<K4s&Hgg&laqgqw9Y0r#KkdFjBC$KWH==+JCJzR#G
zq1R(X%Y5&1&z%rCwsBj0?~cUx;8@Tn0&*ovbOE@W4*^CpSh1P+Tkiq1+Kob47U;6u
zV<6t4TOrYbia8Ng<fHyoE^E;x!7_`tPkONu9q)uBXx#%Zl!tfWR`+(|bqI<^duUax
zD_#yQdd5rSIei&H*4CH8F;uRudUsDUS&(fSGDaFHBR-6dvLkiH<85O@<%8GBrwK_m
zqpJhod5rxj9k5W+IXhdX0V7qD!aMMMpu3ScUcx+Z;g3KOLkX04!nT8IHOJjTvcgNY
zU@#r&o;AZ0y#-eospOsllZ%pSd_~EHQe^t8Py%?j$<y*U9vPKs=?(n=acv%`Z?Osq
zAete_=!ebvG&~zE*M)>$e-6Znq6*h7Lad%-iCoJ&W~VO+;4m&$txl$8fF60&X|vzT
z2Bx4-g>3gZ^_T1Oms;JG7)!JRL^mi*;9FEyc?yNw@XPsV1nOzk=>4kfQ7&Ll-S=nq
zH&EX-z~Hyx0(N^Yxn-SN&YTrJh6_(rdb<7?K}{g@<fu0CW5n!=mN(Fop6#))A{q0z
z8BVvvK8B=#$KH8(4+t}9ktj$nPQh$4c{t)gLsZVheMpVan_XZ8m%Oiqws3?WNroBQ
zf{pU1nk3d)LnB;j9xkNW6AicWZ{SA$MsuU_&&SNR_&;l?FmqCp9L7bTdLDV#n2H<9
z&nRGh$Q^e$DB8St01{wAlcPA*QPp8Q^cqZ&<ZL!j`&fK_#E`YAtlcC6+ZET?xY^10
zR&iO1Lj{Mb5Tz}LHnP!WWH@QzN8(yF_=JorE4<1wv)jt>5ADO(khmF%gd(S;P%sla
z*aE-B?+l*!W60YVOaBw|oE@4?ql8tF^|ZYo>I`k=g_H_-xa#!>jKnqF<VrQ9X?(`t
zabU6CfvjoY49*ICi8JJf&14xl7cl;U7^z!-a!BZ5fEfT|8KS!whjwMp6F|tFn-hpE
z22do-+Kh5czGi%BT3sE{Ssw+K|HW-4Q@-GsLDB?z@kmnfZ4ri{TSFyH6X$#iQ=U29
z?@G6b8R<A?D6=K|XaiY|1fk<b@!wGU=tp!Fj$k{{VcaSmk;CT+w$Z&K(H8W?EU~{+
z5OPg=r=x8*`DcKvb+L(ahU*KGVu{v<Na!3tkJ6e^1Nh}p+JDF_y`_;Iv?!LoEF&Gw
zOn{=k7~gRCSx~UG{0?6-@Pj64yk9R?{xa>T8ICU`2Zy6?1)5ZvSB-Oy;}4e*h0Ikb
z;oSfFiXt~C+7uJtDjO0VM6jNim)f==_KF?!UY+%K55U&ud^HH3VB2o;<!WemeI0EN
zV`WCa>gRMJ!7A=!rU*enpfedCnw;hcM<TaN{60~h5mzp;^cYQ<|C($lKn+CA@e5m#
zM`^nsmxm$5=ziVY_r!tH=G^T&KR+MC<Z+pM-pEs}t!PxM@&@uqW*L}twauHcZN|P}
zeF7-aglH69XpIhcC%V{J%l{Qa(q0_!RqU|_eRe3bojmdj>y3`#J+U*?$75vQ%}=&f
z5uWP?*PelhxJ%(Jtu-f#zy^cl0ez-zUD7ASVb(n+7dgoI#tXMb>v)H6u2!xYE9(B`
zvMZ{^c>I1slBaAX#+=R60DAQpQ{mMFW2>mdBSz(+s3fpr<*qOo60#{X+?veR7K=%{
z7$68J%{!H~d8M_aXWhYP93ja5`D0bhvQ5lB7NI|iA9xp!H+a$WDQ|C1oiS5;Uw*Pt
z<8<Q^gIK-(<Y3=BC-nn~(9=QM0n7EQF?y5mP>MgiQ5Bk*?~(PXv6{w<?28QrSs-?4
z`3kgp#>fAct}b~)7ttiX)#~4?>Yu3}k##9$*%9><3ffoT-G<Y{Vq(+I%uVJ5Im!^9
z-LnBmF0WK0hA43tvQ?2R<9*$|(P%q!^pNJ)efw6!q>~J_W9AEyrEj7s(c^oP&I3G=
z&t8#U@Z|Hvj@!0Fpa3O*i6S!|u@YHHMO`TE&CZ#lJnQSM9gtR0ScdZ*9pBI7=<CrV
zyo3}*5qYBGAD-hy4u*Pt;g3h$Azkl$J6H51?rfyhNuAqHRPK3MvFwoVtb=wV+|z>g
zif}Y}XxORuAjL<^&9H1F%|XgjY;>QS?+@4Yn2of~t{UOC59iQ>cHFkw2&+X<DV{Eh
ziwq*i>d8|zPs~*PlMTG~)C`+QzSfuA(?hky{)*_$INx9Nh`6w#XxI@`i?2_L)jvI;
z-KaU|N7njk>W3=Ao$j5dywG_5(lm`s0s7I>A({9tjKE>0PD3VT0CLFEj$vJOkO*tQ
z>pupMx;yGnokg+lUj9>4wz2CDM4M(gv#;B3lD&0U5*w_WFn=Qc^00b^*qrVvw@tR6
zmT9*yVuQ0X$y}7o02Eb`aEi*M8x^wB^bQnI|C5n_X&n6Rk#hma;M#HG+xg^(ox%eg
z;^=B1IJkJopt#hb$lVU&cls6F)Eqos90hxxtG{JQs&=s09-S*umLi|M3z)rw{se%9
zl^}>_!b+c8C|>JFi?1uiAb(9(-eFgO<KZZ`E~VlZMA}Mi%UlC(2mMHe`JNS18jn?u
zn8y!9=)|ba+zzizAqrW-s1;40qoi9IJn3=mpvnOl9lVQ7jo9Pk^HPI-!GqPZBRBn`
z+I67eui7iG07~h2k7eST%Nvuy=9sE)JJ!Xy&EJ`&+_6vWDSd)ieks(On=}SyO2^uN
z3Nn1jtTaCPDL+zs46ypFnH83vjb-6Ak_O|>@%Qf0L1yl2^d^`4k|U#in}_ddw_?~Z
zoWuj<)w0ZaDl>l4Rb*SfA%yoH(M5tL!{TNqvWm)U7N^+ZX(L1%oEM3LL0m7tAuegx
z;I3o1@pC|ym|<Oc9idg)&k9jprA6OJofiRhCZM<om6gRfPtZe+PbK>3wo7mEToFnN
zX2~0!c7jmZ2KZalq6r$L6*1S!er<8tN5>*Ru1KL|0t7PC>!aE=a?dP03959sXjd|}
zA;9Rb^5MsJXOR(Xha9RGxj+PfFK<<QNo{a6d;juY84DIIvIg;s@bk}QmrqbQ0-lIv
zoY{;Z)j);Y;yioN;?#M+>A(imv6)1BCVoA@{<WCIxrv~C0)|uXjv8sqw-BUskrdLu
zfEAfx0R`R+SEwbztyC~&e>m=<9KL{^a$~Nb95wJVx+G|b|02ET3b`HE)xrWxY=Bhj
zu{6veWCHS8rbgDe_Q<k)xmG?|OzrQ#FCq*F${B*v=B`HjV|1j@4M;Anj@_kmfXH?l
zTe$CJ<KfgO#>8h3iLmfmcWg&#g@aqZ8bw!sCd!YQ0CEx84}tywvM%(}H$Qqv<M{oY
zGU6OHv~6O1I-E?@OmA`0gCC-#i5_<?-Rl@wzY^LWlviZ0iSIpdGFk$<?jKYZh~0Rp
zigjaiEfJrUI#zQy61gWW;0+;q*_+=Ud+n3V6Gdt08k;)59*W4QM~ls0v;O=uWd;zD
zOKm@7AnM+_g`rze&r<TcZu*;`8t)MkIQ{NCW*}bU(qz4H<ZDKqGcpJwP&KC1Ug?Lg
zc9U?;F)l252h9WQPpHn9n-U2*_S$!C=h%1<(XDSNo=sxi{##K`O=mtFV+J95cA%50
zdMRGp8h?;8ns6|r{07-+NWBqE#vk9!gXVI$PRHmZ659d#g0mB!JHXUaGL`VNAK}gc
z<DncdW!BMXBW%mW6xK8;<s|;k9eXs;FB&GC!9{YL6^1=sWau1pQP2IZ$_l%SPr=d`
z)E41nxHUKCf|+N`(O%uxg3K_ou`*<l_I9DczrW8+;$_oK31uz<(rKy;B18MlLv#|X
z$o6P;GCn1HhzUp&Ww|6yV6e0#sN1gynMA|?c67bF1~e=Xca1?7F&40JXKhF$D^V@S
zcSn-}bD*~mfb$Z)cjB)I;2S0nyE$2?q>ysPK{%Qsiu3&!m4?z#dkCE*;i8bDGn}z`
zeOa$$b|{_uv<4f@T7eK-cB|1XlDxVOCI0y-@^WkjmdpJMzNSwqy&JRwa(HDMo#T6%
zeLXa{`4OnP6AsDy7APb{qBYXdXpF4mb5a7UeZ-t?H&Q#do66^WuDk$z7=kz13lasU
z(H6A;zDZ9VH^gLrmyyJ_?n8LBSPadj1kbCw<6s2^5$tH6-x69WQ@fHSHNC_*{alK;
z=eRVI1F1l|k-f{T-`ZroHzwl<xL4ZbNxh~P@>4c;KL^t)>Cn_e7v#8=pqmiq*<`D8
zt>N@>Xk7}>ZZ%^Zex7k$PQbgF@b&3I&11)HAEHwg23VG2C4QvA)iJclyQ&f&e>!BM
z&>3_F=;i5e01<Y^Kn>5#9P?!T_BgLzht~|mC7s#bVW;m;lUw8R9e#$~RL`3U4*tSW
zH49T$`K!T(n%{ym<xH_X&N3JG_EmKQx8yFp>3}hFvz2FR`nge`#N0w3-F+K1n73ca
z0eoqg>$M6c-*;wY{|yBux&=$cpX-cxxXV)61tuQL4Ek|dDcnu=b$?aL$3Y9U@ZBPB
zCfV8pe-~+uF;#~aHkd!Oq(!%bgQ;7<6SXf!KvMD|SU<}97ndu4(+}q?r6&!(I#eaw
z_<*rvEEeytU@y#CT(2|;O0u;gq0cxNeHTd@_nW_SYEWJ$oumjr*H)Bv?<#iI_fP01
zqUfd8^Uc<xX2o|g<7+m(v;q?_hmsTZ6)(b+M+ep0&2$4kp9jhqGS_U_F=B^c)ZseU
z46v!8i>7}{S8|V@_4alTNps1SV#s{%hnQ0x@RwUmBJ=~VD!feB-PJu+_?MbBvP#j$
zG(rB*=nf78M@+$%VD5dLcIN7@mxefT3lJ&X-$L0~H0e&faYh~>WJa{yKzXBSnJa<L
z8$*T)=N`+@%ubKOfx(x~#9^<<hMaldrMp`*<_6EtAS)Lknsdu0c$&k_OKEo6lX}<|
z7*3Sd8DRR{Sd<XN*^WIRcnreqaL7q#<8ZDHs!=64ZoMWO<pe5*Y2Rh0FJtDhLsNVt
zm@+_c9l~wa-BXm)3oted+Ea`GmUtmwrDJU+Q$#5=ipMq%_|sUlrp<^>d)lV#*|p)m
z`s{$*JyM8(Zl1=Q0HGj;jhJE@fT?mUaU>3UL;F=@$GuUP=AMkN%or1#Ha&~N^3b~*
zW30w=Y{~8fRcGb$>hPtS#xFgY)BU(g<k$t6kQwf~B7}YS4i@pV-4qsq___v%Yia)Y
z^+I5Xh{@`YDx^#7yx8FLK+V3Cg#x+gf!i*QXf9X3^te?uqWNGcPiCE|xi<)>GwIp2
zKre?6VFO^WwxX<+VuHkrxJVmU!LJe32L%}_aV`%KXHMKsK@?IT$yAIdC`{1jNEGRl
zr%W$`IUen00jBra_0aD~*Ff$4kU!Jav$;w{p53<K=IbhB&iJo`YPK)H+_NV#Y2VOa
zgIP>BuD`=Lc~&(c^(#zV3<TRD3jMS>Yb7fFj^vl%7EYVl-yTd^EVdu9n|)Q?6M214
zV>tLne2K=%g%Xc@T5;A_AV^|TaSy2!UauaIPJ%CBtZ!y2|0@^gL_{8y3E(GYE0X@V
zdv=q7_3Ja7ZH8VeVP%T=g57O9j3k_6xzDoIc`H`m4*PrIr{k~@#e`!_LHW&2f&9>o
zWw*uNQ1Q+?f;Bo*BHICZ)F0O<^YaNi#euoU6BZ4b!h?igZqhgU2NdE0uN4A9eA>>T
z#pWK8rihZXBW4Fd7p9(534$UYV+hmH{)^9ytd(uPm48g<wt!o=6?Y`>*w=8RSA>WC
zfuDO>VO)<J$;cPqTrnx@VT?1}gR#XiRpj4~MRmIL-X3P$c@-#J0gT7cn-7uI84NY<
zar)L0V{c|tgjx<kf~W`Y_z-xyr2Ix(>126x*tn4xWoSB^J$QakhROivVi+PC$wynd
zB9887p?ia>;XNu0Cknt=|0i_W5#16_H!OE?Mm5NYG}TE{IiyMDyvb5Z%TgcM#1uo9
zY-UV>mZ9EB4FD<XBw6sJ?lvj`^XCtYdTV4>JnvUjH-l9U{KEQ)m|%)`#u?}I7<+$i
zhjW6-rtX?j(@wGM9BVRerwZI$k^sk|Uo!x>g^U#UQD;N+Bi<<uJ&~!Yd0^pwXCIB0
z-89Sy`b7*Py5K`nk;v|pZKF}eFrrE`#<}7aKYfrNvHejOJQdpy1cyuo{BJE$mWoOy
zlD1MOp#Z5X&b%G$jGdJ%vA?c8E>c2y{qS)OLb>vD!gQFVikS2hyU*`*?$2%R5C4Cn
z@Tz0FJn3`*0LsVzI|@(s|3Mh!|1}El<ZNhVYGG$>V(RGhU+Y84|1XR2pEFoPFy@dA
zq3f19h;#GPZwpNVE)ud1`pU=;ryb3Bu}H$-nhGJ{Ys4-M{>`|Yj8rp$a(WsoVY=q#
z;^O4%v%EqN2$Gh5W@*7!t;MM%F}mq#T|%+<ORc+0vSYXAb#v0t?seQ_yz{prnY0+|
zdEOPffH2+GeHvdb{%q*6U7wMHT9~85mxfO=UQ+$LJSl}^nZhc#TBp$d;-lVQD<n~!
zmePEE3g2bOOfkKf^9?9eVxV03co-DFtF|LzVmXFHaY#O5<UCL0`S^47P*kIulnyC3
zHyfdvt7Rv<+hRrFt*TR}*wWRIM_Yr?!)1o}OODh|>-5~tyiV=>vsxU9c6&E|O!)Xq
zQv)?<FHtpYJ|PTcaT=yhHHf$cNh<Qjhk1f5vg6jX`V-HOG-@KUfUoa{ZG$VPEGUJD
z=#6k;{Ty|{F12!u(Qc^Nb%er?U`FLK`H_ml%y1x~h6u3^68}MnS4g4xb@MyK9ssI`
z1mO>1*HoMhr7!t>g#HA;1J>LnLW<Un>FxO!)Iz2N%@VV5Hq->D7;8Ku4dVu*F*OL4
zgq{SYP(a3$u8hhxR{j-Z(?b!+fW+_zkpqfBJ1K)`@*HobX8$LqE~+OPaxKwGk-=X@
z7q4(cNWwLAu&$}qzV(KepPX2rT6A?fi6Z*z)7T;KC0eKM+seqGLYxI9I>qst_#TK)
zXum&*F%TUU&ej`f%|wY3D34lo&G`)Dy%tS_cycKEK{|xXq4z}N`sXKPCAq0TKYFhz
zq#DJjyA31`FjwCt{d*Qz&7>TXX6*hACbZLbgIf(PfG#F@+Po@b)j`&fM9$%?0|D5?
zQgSqw@z2nadGPl>fYXk3=FoN8!~}nPIH7z4;2&7Tt=G7#EUGo2pkyoTyUKWp(ld+)
znbIPNSgMM3qhR1HGi)R0g(c7@n1QU{VskL<NCJ6Oq6=^`p`fn!bDOsu6AB!f%c7%F
z6^Q%(#-)x<G&I%q3n;BSoYswBu1VE$^gF7Ms8GOYtL><<GBWN!#J?%tc|#EEYY*H#
zBOdcom{L<q@RQXRXO+UAYH$+MCTu`ZpcQ*6hu3}w7d1uw8LM~Q(8SRp#quuVfs{ef
zW*?C$&&F%u(v(~7oBFd--562RDTrkn$DXIMJ;ylmUYbQ>21TcOS{m|WAXLvw19www
zJdA})(lDRDrW@K5(gDSZuft*Sg{IA6%4kI~86+bVk4=Fdc}KyBM`O97Z3&#!WG)lo
zWWT$h69Um8xgb?|cW|f0pv1@7LPGpX^MZ;6_y@K^5a+Y0k4}G{2m?haOg{{cU9y0$
zJoiR;_lc8ElN(1^I%0fc{Jk*Wh&s^>9}K^Y0%JT}h1QCWZ)-DCV)c|AgA-F*E)HLg
zwQ|4Dt!7GkDx!1%c)!!lfYt1`J3;GTlSS?tdrYzJ$Ff{2&3)2@jXRyS$|`ZjERPq7
zNp2`8_N64vJVG1TPO-%6$d(<(XFL4#1FIB~D@gbQ7OQ<pY(*I97_taLqpjuL8>Tn;
z!xY}j=tM$#DbBl&ekfHkpV3zx9G@i`Gz5zWI}~RsDC84~8a7sl>^S0{IQ*oC&&?6|
z3~}$K9q?)s7>8U#*lRR!@{o0nx};A(@mGkkD+WZXv0{%2Z3z;+b>^bG=-Hp-BqG?&
zv~-4cnk5iA7IzL+-Iut`r!&JdvRd-;ajY&B<%B^Fc1bq}8tzUx&rZyOFRv4hEB@n2
zvljCdYbUCOe3tim-fovt4;Y6;TX(rCGbT>#F)}?KI3#|WOBwvMD%=te4W|k^aN^d%
z8EIvhk=sQN3Bv}C%69}t-?Hykv-KbG;K4PqRb@+KLW-$RVMx)zZ@0y40R?CewXNua
zl&Sda`5uI1L$rQkV`0`NE;(lDgq&}Rr0e8%A;pp@VNR~pQ+%(y4KXzPNnBN&f_&mv
zl{#_vq^dD2dOVi|;Ymge(j~r*dzGKdwY-crI#r27>GF9<dDlbES1uma*hOrA4!ZH#
zgWqMS5w_p_qRA1bm(#vnP$GxJdxbD)A*Vfz^U~j+|Ea;sV9OPO0s{buLiyk0rzG(I
zC9(c{bJf4`<7{bX``<?o<*&^DV1WMtv6laVSj6H9$DdxH^YRICRsBh3uKpgH7E1$C
zROQ90mO<O4{^|>=&SDG!lVJw%ZuP#(y9)mSv0R<p9;HD7)7PVIoq;P%$i9tiZEaJH
z&3<3;*)sXN_+J;#myLZ}HVs({FFW^_&qh{$_Vw9)-JQC1GEY3W*KLipS6N50_H$RW
zFQ*J*&AtW)w=lT5d2+TPef#2lnzC_i{(e0P`hFWaoozFuO`mPeM`!*xJEAk&hFD&3
zu@9i{)yllqVgCL4ws<S;w$x^ad+MC-x0XAx=K47{%W!S6slLvT$FC{G9hJwYyIBmC
zCDyhC`#P`8?QP_!;!OYMz{UOEyQ;w-`SIh|+0y)JX09tP4;|(p0hV#gI@7PgzW!|N
z{~q9Y8_l%3)U!;0S?q*THGBxlx-NzP`+9CHIe&DCDd;<=FT@oC8#kW?-z^B$V*B>A
zZykEh1M^~F;I=A{kG&{Y=Tow_(>8A%CS^}?SQ-mnGKn@jz?GM8Evj}mk+t>WeB-uw
z2vNy}z4py&dqL}aFcm>>s_kL?x(bK}80i{aTo|$#)U9Lv%wgDmAs`;fzg`0@74vOT
z>JTta-v@=hcpzXl&G*yQ`xA=&`!5N%@#t6iL5FvXCMi|~NCYRaHvQxI@dUUMaK!_=
z;?m}t)^I7m0#mpd)pEWCaJhpMuc`a`=kc->zV8Q{tA2WXzBT>6Q`R^X?Co<yb3;}r
zOnH~h9{&g_4XuQ8gZYc|u0a$IROp%ai@g{%>kM*iK6(a2r*E)?pDVB5FhguIN`}W`
z6M0MUJ#PH%X_FBPJhe6SvaEL0Tij5t6b-KMGnW7LG~_MN!`W$jkjB|NoMclXo)$Sj
zTh0vYtO*Hf0Ws_2yC0J)t>@ZbadswK4mrm?Ry&AwpdhA?=kB(|&eQ1#c<3^~98}tU
z&nZxpC6^BjZYcWI#>y<sWjg26((5WV1><(rF<3y5f8Czt6L%^^JOr725%i_YD8l>K
z{K%e!O7;<~$HEUg+Y$>U%iVd}nI~HY97YmFtR6_ow9OUwVG-Qr(xBpTTzRw!+`uz%
zX!|iokmz~)Z`><I=8L_RtNPn0z%PJY{hj<#I^LU`%F#DRmY?AMDry9807RDGb?Xbi
z{0q$Jvqj<6dkPr<=F5H_+(PV)-C$`f?ww_??UjxQA^(`z0MB|~UGKazx6=;iTAqux
zSub2Vd}=|;vmZ<6n(KwzH$`q1Y*%m&7o59W)(rZfiP*+`CVMnChejUG!{*p(t*}wf
zHA|49IP;T)TU-DGf7Bnk#IFq*_k8ZIj`4@j0Bh&UY5$`$h5#=O52|94Z^#-V`;B(M
zbWj*3S@TxIl^n-}0jY2ZiZVP$AiH3#FX?9WA3w|a0Xnh*EML!{<X7iXa1yGA+kffv
zVz?~!pJ$GJ-^J_C!2Wx+g}gQ^qW+$g-fb`BAJ@mo@7+Z1O=5`)!^h@xzl}^<C~9Q}
zoxB;iSv$Y%hlNgXL%<L6vHr{FFd%$V#=9xM%o`McSLITVsv}TB>^dQJq={V*vtqzt
z{2b^>SrjT7_FRDq^<NZFWrvqf;2eMk^H%?0fZstXT)B!e5F?PK@>unFA+3Knl+NI3
zU{6mU3^5)zrCcEK4aQsPH|kH9AYd3h@6~3LJJ1uiS~ee_WnnF=dfy%K%ppG8L9adb
z{`3O;bOOvk;N~;I5N%I$8`gn^i-D^>EzHKE@%8e_-x#YG2RS&v9QnUTg%h9*5LmuR
z&WCXB(`<rpww_!dn`|qHHr9!7F%jn>IcmP5<|@k@7thR};)E!3Mp%o-^!x;yb!!uq
z&`R&GKVDlIkB4|^kBD?>o@G4?O!kvsK_++bd%S@s^hsHPC)gPL5cDKW6Z>?iLq%Bg
zl=(ffRngYNlS*uf(Of#wsu$8UxdA}{JOr3>hai6z!Db*!K!0wDhLvUENEDe7@54R7
z+yv%H3VKL=0AOR-rs*Nd>g)^mL639kXLPHM!Tp8}6(Wv7+iv#%0DQwxYdm36JfB`=
zLkuwgKrFoU@h5m+Jj;2=W06>_jz2bM1PyzCPUk2tLTTkq>aE;++R$b=%EB+DZS9n&
zZr>~30$ncV59HP-6SczD(&B^m)K;ce(67!uxL~X&iR(2YRtnE_7yh!r<_*FOo^&3L
z^TfP2p6iboR?0`*VB>wP``3%gth%^k&;a;regHOY&)B9-YD}0<x_#D%;(HcZ1vB;G
z-FTzZf6<$f$ZbsM2KD-1i@%PraErKh?~28SVU_ad_Y2K}@;rBM#q{Ho;k=Z>6G&P*
zDXa5B%`FZZ#x8!POmu#c;m4N--><3R+y#teyS`zoP}3-~X(4HCH0*(kO|wJd_y6K2
zcz?`-t?k#J`X0W+nWVbq@;!*}EFN@ygbm_D9YZBa&e!a{J~~s-7ZK_w^-3nb2xZOH
z4Zs%3RZHS9+fLaUJ2bRw8~f;fyzD2q)}@x?#Hn%aV^?^S-aTIRIl0}%ej}RL`8)?e
zW=&l8xbRw4_wimS>?sTNB3nU9Arua6=pQVjFpc4%;9fpi2#(|?TV1F-;yv&hD(*zv
z?nkaKAJ%3PP(9x#eACPZ3#0pKZK*9y=)mw=3m^g?fX*suB)W|dUbfgQJ0YNH?u`1@
zdg34OCZgj(NYRt(56bCO3Th?}=fM+jNf_wIJR7a^l*QSr&nt>}w!NZYI>V&Th`1qo
z-NJC?&gT$q5;Ardj*;XP3?tLt>}=xM(kkd)_akTjem}eYzCGjrHvgU56w)Q%;M2m+
z?jDqml+s~uf{WBa8l#g-g8nN(_wy&?z;-2Pm|=2@*7_<3*MGZ8UcCgQuok64uq~+4
zl@Zng@{UF8z#IdAng2-4U3d$VH7m!*iDAd%d>ij68mfG%$;r4YhCdE)f=%wPv*Yfp
zI9E`+ow?fs^%nw2NlTQY=Rx33wE0rP*#6QTu<Csz37fKg)InlD^^@ZpL-SL{texX^
z^-{`t*eW7E#E~M#oUTIUA+#})Fz=U01=&xLSBjqb^Nj9ySG}(%2sLtdY1waH#M_@o
zY&&=mVPi1HJ_DD(oA0K2_ecLE;3g^rsf2o#bwr;Qva?9$E3PbF83cf>6Hm*TSVk0s
zj}eR(pnIQkBL*l=SGFPi@f?WT=DikXT?5K`?1vufE`^9SZRRnX#<Q@zZk4=(3Of7y
zbISzEMl<6wiog!u<@~o$jDwE#cSsiI3I}W%oCrNlUf$+H|E#kbKxN~%hs(cu6snI<
zAdz6Ah<ED;Vd)%k4(5ZR;aPd5mQOjMQyw5x1i`awp+h5auQ-IMl(~pL+eJA=vGd7d
zyQJtN{xAu+9Vq=jdL>JXN8sE-Yg+A3Pi+w+y?a=fG#H(uho$i5zmnH32D6GM6=+1L
zDuUp^e560&&-s2}X<|>@$T&)ZBY#dunOvX%k!E-)V%u5hv&O!V3@FaI+~p|T$_g3_
z4@c?Nj{yF@c3hU{)+ZbeG()@t&KRIKHF6D#S+;Ok)A0duO1a9TsKRgz94@@v(r(lX
z_~B(kRew2e-_`_DAflggusHJ$aQ06EW}fsOTr$J1L@}q9wLuy-Vm8O{mQ4{jb-ZfN
zk+j^n17Xu6;@Dk_^hn`e(+3Y-akMi=7p5OEfk(Rwfyo6xp5)&R%G>PDVQ2HKZ;TpG
zlmcXHQn`=%k^nJkU06vf*N--fAgJQU?i+|XPX0w_z}r0M(wVQ94awN;5N5?Cl>oLH
z@csPu+uNNCJ#GOpnvW0A2+IQBT6;GD2lJH}qw?evcZ7_p>-mD3zVT9vCI}kC)XlDo
zo@r9&z=*O*&}7E=Z2<|#RW<R}=V?#*K5VR9RR0#&h-d+ImC7Q>R)^y(CB5?*j>UPc
zgvH`*G#?0BcWZ%wDOau)frMXA4F5a>I(Nt+-g#qQ?;{{#?(pv_8@1mJtAm&iG;G|q
zsQqW@RV>=G0pvvuM(haKejr(Y{*6YJn7m-EjD2`<DGPDii6H+q-3&ymIuU(_aR;#j
z=rw-&o}s#%HULrUyCY#K#es$_rWwK*hecBDI+K99Je$AKeo%J};Berh8(8&w!&nh}
z8AhC^hJ@Vjw70`%gC1Dbv+2qHsF_vc%F_TZ?<HqO3ybA|$o#{P!vV^yA{59L+MO1j
zL>7RtKRoHD=RAftwRFi2@{@MZg091A_qZ2*A^id5P=o^97u-ujZbK;LGt4Z~Glx9+
zbI<i`z^N->yNFwO$Mi9Sp<Ilh7KXZDOVy+)Mj{sd4Dz}1yf||<S0H0+D790E#h9pH
zW<<1CX;Z5x7-d|yM?Q$44i+`NlM;c<T^fgGKIFQ74bccvF?i|ZY@ZX9NYp0tBXjDc
za-3O(!_foYUbaTl8F$}A%7hy@FW4!nMw8tkUYB&$=CZxFb1NP^`x)Q0K>#&J!9)-e
zXCbaqbthD*C=E)2&Gf337l*fphHDB|MDkvtkZPgxm#M}DJZ8qzri*{f$ug;wG@Q)+
z2=|iOcH36E9H|vn8L_cQo0iTlEO*a)oFx++1(7yqE?&_Qn2&Wj2tt04U?OCskUq5A
zS-3~}U|uDxE>D(DM@)gsXK7tIVF6um#O+H5?#Pj%MnJ9{lyJWkw6T*An6pX(w{(5M
zdbOX@P!Y!*fp&heo`Oyxu<)-O2I?MApj>-GJ;|3w7<kg>i#us5d^q*2XmBfYsd&M@
zJCI*-)1keXm=h9K&emZQk24*lkIebxj}-K!E0FS*CkTP<4^f>#gaNgj`&e3{hw%ow
zVBf<^SE9h-i?^K?DUnZDf3)B2!x_%osq16O?rqqMRQ=dqHQu?3qXFAx_678yZ)c#O
zflDQN22ofa*wvl9LTG<8l=0K)D;Nb)-?SBVto)nVeVJJ$E$Ae@)W1p|yMY+Bt+?nO
ze{}%wC<5ZHj(;Cu7~)wZYG<h!SN}Ys`40_M_D|@klDH%pr$7GFx-Kl(#|}JH5rqTj
zTXe>;Xo%Tvj$_&nqcn?Ff?XuWkiv;Zq<S7K?I);lj-<i1JtPK0@fK@APeH`bDFt*O
zjSx?dgz6p85Po9tk=I==rw@Jx!HB8jDilO+b#DiK!BgQR4bQC1R2Fr3z9nY_Iq(lp
zgv7D)+#xdIQ9bVmkw{tAY`LH^gRx^WNb27Qk+b?XJ-4Azs5sej^n~;g`>|83S~doU
zu#3=gwvV8a(kx#AMY{{A?*SU(G86PY6da+2A3mJxg#GbZG!mk2^<NYH+=bR$K2T)8
zKmIyH=Fq9ZbpC=!a7Xh6bqf*ur%4qZKO&_@FX-`K@R{A9#O<-Se!PdYCx2DDkSA+}
zT|7`nqvG~0BT$tn@G3-M&sk)FP~`gdjPGLn?|1&aI4bR`WHU98X2j3_Eh|q8-qtD}
zNeE7M2vy5TQqeAle|OQZSdg%J@bQND)ys5RtjM<Ve>RhAMlTcQ;5C%{8n?4h|6{WJ
z?#TI)QovDC5_;eQK0JvlZ=yjO`S<RYempXdftg9hr}!pO>nQ`<82=OS%Kh(F!Dy4Z
zM7bT-5A202_6Mm%q`rdW84_uQ;1d<Ew7tur8^w$)+e<X$BTGej>N?K=Vf;CX6|Wz-
z#;-wa(77UWBYhVmm!Bz#I;f_Wj)1Q3zTZwY=#J}aUd*N<n$+<6;$h?&dWO<j$e$u-
z;J+xrQQ?H6In?QtXp;xpH02Hxr_xNRUfth>;pDgjk5|T!=w`0Y@;6aj7TwVK%@kFH
zln{`#^=$GN^T$}Cf)}9sCeW@X*^^2fk&Px4r3P1^JcuA86ny-jIf}ez)Ix$^nX%gD
z3DWO<aTO60l)l8y+A0tZl}8nwS{PcpPmxIitrP{pE80T`hD*I&=|0hKCY#v8bQkJU
zNCTqE%=4-EW6}aRf-PDq?OoDNw9p}b!oF#X?4jZe#JkOCRr9;EXDaDTcQ4u+P^7#%
zckah_SaRm;4ZMq(EpGHBR(GJtCZ^%FnVHtX<>Gi<&YlFgA7<da0=F2X-}#J#!9}J{
zxMPA7t3j$uU~<DB3K-hz>Ym8zNakW1&)IXrSFHlE*86wyI%gvj-YLfs?Q<S1(g5CL
z37yX4odb(ktho0}wiM@R;HOU!VGb5GB%;`niE#H(onH0ZWb=SwVUVtWNT<<?W)`CQ
zkG&kPgBvhmL2;8SoB_u-3iFXz%0-jQ<-4bk`t(WsvQW?N4xg#;y287CjZReiP9!$+
z#!5`|CF?{e%B90HZ!r6`I#Dmd=$A`Kj*{RjAW1lkdcnTtH$5Ss(|Akb0ya`-l2&@y
zX@`Fm#(@VJAQQd~bi^mFW4wQzEGXl|e+DS(85`2k9rG~!tTrzZ9?({+PWarC;H;WT
z99Sx64~Io`yGa$-b<;=x>79heDSwyB;xX~zY7ELRz$%2O>+2Q#?gvEu5YGa=c^Yy8
z+}+#CZ)r5K+DQzp=c+}Rdo0s&RkF_e@+K#l>JuNU8O0I;CnS1jVy^P#U(W;sq}~>)
zp#0iGR-gxJ@+@Je$^vam$30Zp1>2uhUsq`?WW79oP|!e3pkj%Zn~8C4qW0NQGX9WT
z=Fs<YNrff0NT=ySO2;D~A@~ub@N0`|(W3cAP{+-QAG;=U$C%{@M^m4S6(80bZHo>^
zBSozdTO4PU9!abu+~HH$s68T^>9d}J+XGV*QmSk^1xQL{^%B0sC*)ZWlY`vxUC8(`
zV8G#$8&?6+`5zbcwA(*Xmryu@DKIj4yeMWNYQ(=p>9K8Q<8(S5r99d>8^~zr&_ju*
zFo<Cjy76d2ueb~E=eD>TR!rvpTSh6b#n|H~OwSeF34BP#F22jO^udx|!8zLZ(aqQ9
zh~(;c1(Wo*w>rVLqZMgw6*w-~t*Yuv<`D3Wtw{F==^SEw<2Je$ljA{FX($jVrDZL8
zFWNl>u%IX{DOs^#j(H&P=<R1zBuGnF_=2zGZ(qT7E|x|b?5~-fA32lTK-Q)e#;N>(
zeaI?@Ws}OmcP$gDpg=?=!`|fr|8W^Y(HJyE@&zaTE8Pu}qBxp$eFS9YymwSyo!UJ?
z`NNi9d8SL?JHSXZVz$aG>`F5QnE^T?4M)??dTx!hUxW|pY_|YAEF0<D+6Z`%u9KUF
z_t)5RN>huFD!19FyBOochm}^r{8GEAAJS}?ZU#bLE#&~%oHc7p&RaqU*ZFUGwGl&y
z_7F<93bvGEL`d(l=O!Hr%^mw<;MDkRGKlpWKP>n9=8N+MYLJ?L^SfaZ@7!$bnHHJc
zGACgPk!#^3G!*3(Ck2FeXmRkH$EswGATxLNUlr4>HmqkBdHJY!>P*peNFS~Qf+;Ln
z7PjRMqV|iN^8hm~i|^W?%T@c2=zjEUqu~weAj1i}_13h{aV~`WCi!HAun#_{HA@bp
zx$GQ%x1GmxI2@#ze{z!T8h*Rj66V`-0m&TYaZn|%4(@(Dtv4$YCH}O<pjXAJv$zBC
z*M8sQ6|Z!F&y=2(XAS*GgmD$C%JlRl^l0w8z`|8O{|^w5&a{&REtu979Y_E*G!3xm
z=uK_cajVV9L<V|1)!{jb>^wXoR4y_`D?Kn-nyg)hYthYzP$Q_YJE;o|eDVpSke>wg
zZ4*+!)TT=NqCeg9%&}!|Gex|GV%}))Boh(p11Y2nJC7LWvagNl<Y5wTAQrsBg9A=^
zrVV5}HXFskL+<xsU)@v@E+Pd4x##;yMa%6;&5i{+0pBcSl)4f9UyQ?$=?N%wC`vJ)
zwD<E*rJ5-LOyNjc@ZY>fFQpzhkp(bzkvxuZI^iIA98ZMt2Dz}Tbg}y3G$9TUtiBG2
ze#VS1S+MvOhBwncYlpdUnIgx!4umx%*x`ZFlhoR-?!(UXjBil15x|92uxO>u6x5Uk
zSK$XLV-peq)RZfdmdX1eeg{$r&Q@55lM4!U?Yz$*3`8zxH0R`Opi)6ue=<F;?G*k9
zJ|!)K4;5oy_7D<;=2d&&Nt$lV(V_&J0R2Ya$pRVn6(B|vAKnd>iDy<{NVcA|kU1OY
zPA}~@jD>g)<hZ>UZT=+vVYj2G^ihBSaSW~7#&fb1dWTZGJq6FXhoi(ba6JP)-9sji
zMBPVrQPX0a{D{;uQ<Za`&|j~&!qHQI^Ya;q;NS~E2LLfCm{Z@3yUgVaW={2;VRVED
zh7f7rYXBE^4qS>_CVARFj2~jc5F#;B_bQ~&h9j&FCG^5e&$FqKxR|%#HT3T>J;AaY
z#J8`i+mr7BhekAs(IQQh0?zZ!kH~~0w6U62_#hk+<6POeRe|Ed)QtZE8BIa%vC$J{
zvZ!yk7&`nccua!sjms&_P(C2Wtr!_DJ0)bv!topLa<EK}63$-ap)st1aADbW+aJ^c
z>%2aslOm!r2%w};VKQ@ua8^Ojd)by*JBmm@Vs}L>AQDv^pm!Eco3#MUwUb+1gJ6=w
z?Fp|;Fg_KxGq@IXH`WBWFOZ%e<j!@ufGIYq1RW|Oh*WG&Pj)aqY5*Sv+}Snl4oYbj
zb!@8$#F}OnMLP;1>Y!M2drPQ5EYhc%cPxZ17Hbg7xLYV-fRr<j?ac5na*S7kSnX5<
zi2%^hiBBg-q0Hq76ILw|?x+@%Nf$^a>BCO?rQ$^LYeUh%q69*XmEquEXv<{AwHOk`
zEO_hN^3Hp%JY2^tN7~N0AlfGd-Tv4^+LG>Y&howlUj>-d_t30=Ndkhj?*Sm|q=$DE
zZYtxAC!$HBu$me*Ib4{HQ^VIx!F~Urf{M~h&__5-EMvmY_sJns^D0v|pyPUyD_Rnq
zFikfi>QwS7AjzbykbM>0VEK_fg-$jhRRml^5I4$M!pPE~z63Ls9;7fYrEqJJN9DO+
zsEy<1>QXi4`HN8a3>H3uP0|svA&Ey8gE{}Ht5`=su9;Gwzz3KfG!=vM-8>mcKT(qY
zSHjg})S;IEEEuLIs);H}tvymjqAG>i1I!B6z4L<VMbww;nEXdg>DdC8ugP8F=`0g@
zYr*NOY(qIsis<e5=o>018(aM2(L|A*wrpZSic_SAgIPtLweskw?@YR8?K1ddVZ4c4
zKgbn_^hk$9@;%Cu5|SDHQ0Z>m#^$<YG7uhptv(SziL6m6tSJcrKV}UJtPuV^xB|ho
zpWkV0ou(uBFkuZ;!6W@}K`pd0#j`A_=mN&jS8eg49A!c2RC|}%ujaw<VZy>7J+rVH
z)b6snOgU!wRd^E5hRgu8b+Ht_Ced0@s!8Lp3FGSh0PlLGi(k7Y3x9ZeHcKxrD`S(S
z*`Fd0n{*3@%k3)Q;=l_{c$m95%ZMgMy-g<hP>MbpRJr<7$TYopj#Bcz^>A1AOq`~G
zX>#rsspj7e_kZ|$ryx;-XiKwB*|u%lwr$(CZQHi(s#CUY+cx^#?&+C(r{_*S{7)J2
zN94nb+$;C~R&e1xZkgLYQT!Mw*KGO4BPdhuo}Wkmzh~*oLQ=gqNIZISy!z%M*iLgc
z`<s%AcK`WbK|`YFwwWe;P30oEpkEaAx(jmNx;tbvt#*#(LgCD^v23gEUXwYU`wa6v
zr<SC3ais;@zN-%<OOFO57NpxvnJ@HZl<~t13Lo`Y-b2Ngfwt9hgYlfW1@n%C7-Dfl
z)5W0^0x=ge?<%dBP|Idq&Rdk4+X~z=%^UXwc-#JZqv^b+y~FTHb!(X^k}X}66iNo^
zuaFKC3m}+RRuRlk;<A?J;d!A#+zy-ao#Op#+LvmG;=Cl+_mw-^%T`Ajz7}mq+}LQ&
z7>XN-hXe9;1KBeRBU-cl28pIERr))jiC$pXzlk8H^GQ|Vi5m7PQH84|Pr1>CRwtCu
zoX!Ik8=1M=hfsoN@Gi&{OVmY(%MUdS>qvBT)IdiTv?s0FGSPpQg&BSW*xdr#tvC>j
zYZt80d61lT%_U0HYEL}Eo9y3|UG5+j8&M-&yGszs4vZRvgm`!%%MCj#Q80+p!EDAy
z%PCi;Jex=cRh6i;DoJ(WJ?MzLt2u3KHON6Q+QI!x6Xn*kqFP+KlX?APbB3b7M5LW4
zjdzJt|4k%zfh!q$)nBpe)}e2OA59b|Q&LWAG$#K^6TeBhv#f|ae}q1aW-%Zo!}^j?
z8}CqN-3!ay{2af^Of4TZ(Q1ZFFq=#{QD|{4=U`xQ10T@cUv0@6<xVO2cmc{m+Q}rM
zMht(2RXP!u_-yhy<)p^Rt}5+2Gy+pp$@i`B_C#tbQmOs}yj-_pYH^e(&Z8$(%Bm2n
zBAgGY%a*~~&mUQ^9HdU)un|tlj%j@a^@?Rwm5%t?#ZlGXTCTa7>d5mah@6UC&5T&u
zb+1sSyH=h4HMF4&ak1n~`3zYCCIIOE)g5Tj5r|s$I|3xn8zgJSgw5+#MxX3^DBoB0
ztFM(%pgYiBDnyFeja)Snw(QI_a}+lfa5yMi>;)zEgjH?lq%drH>BR^j$QXO5eN8@#
z&`-lQiK6A}!dW6d6#Xv4HjXRH9ktSWP5o9MdIHXDSIs@cYMF@WvDBzbo%&uOA(wv<
zN7NSa85HWTq7t?B_kat5pWCUymUUJI4vCr9dg9|@Do=cno^I$;QU>K1H%F(CrnB)q
z@w4DXr?d$S)5he7$dZzvsyUqt=OweG!LiFcm%Gy|SA`_TMX$?|Dc^uothAM3{l;jU
z9h&Q+vJN7iA!9+jIR%ZxIYID*7&M~gHC1?gRbW+<Mhj2%zU)rjXoZ4uYPi%-sYn9(
zr+=1#swAML<dH$WHyn2cfMaQcaiZ@&>an5W2yc8&=H_XQOB1!}01<X7<y7{*FLZJ$
zsF)`p)@+Yc4G@p|dzs()=SoU%sm)o>4WM9gby<$r)#>Tvk<_0mXq}xRrW<X&3^tg~
z?s9}*lxLZ!?{d4Li4!#KiGnsZRMy+6UZ-i^St$h2$3{ESrU8wLAkRIQ4O$)Z64Fjt
zBydfDbhvy%v$kZ(@IfT88u#Ol*S1<kcISZZD2ggyqMT<4k>-@($BRM>3SHAhe1U7?
z(aaz-*<Xm=NR0*v9!M(l0PGIs$kl>X+n4*!`j_RT?IHG0t2&LyXR%!7wpec(vC3GY
z9=Up)c0a_9$3VLo@^M4L@sBO@Oj#gPC$eu=U(D#+<amES5y^m(OM*(R3%bJQ8No}1
z!&BMI0~u_muCEhksLbIjMoNp)Xu(Z=kBg#NW)X2XQ%F6qzuhhOO(lra`tj{VpCl>-
z=>$()X+M5J_TGx)9-@TDn8V-9(Eyfl7l({c^qDiLT%b?Q1mQ_;H|A{5-0OJ-NFmDk
zfP;zGQGVhbMlr#PA<SVi)_(@R_RfRmWE;s}s3{XKvT`UTM=9d+Nr0{LYEB!>amvP&
z!i%xmtVMPzFnvby5&5~<Fz)We4~YewvAj$qbQvRn@*u8|E}DW>V2CE>mDgWN{A6E!
zKXE5p_vc~%we7jWnK)&J#LXH!+E`f;mT_9sMB^nv9x|UXn}SQ^oy@9Q-qm-}Nv*-P
z<NBRhvGTxSL}vLyDw9vHtp@SjU6>|vodUjPY7VTsxTgpTeG(!oS}+z9s6uXKayPOl
zd3ViP36zXuOVtkocxXCMmrN~elGVr^#t1&=OkFDpae;y_>qKB_+z6%|Xl5*k8+zmp
z3=II7x&T@loT*r-22WeAMojZwJVaHLQHA!Dh<rO^vg+yK2|x|zhdd?zb#Jz9-*pl9
zPoyRVUYEbeObqrqpn!8t%Q@0*{NetI{f@2DAItl;W5HzH0vjQH=fgm|i(l3_X*_l_
z?8$1iD18cC&a(J76JJ+Z?<+6La$MfRcG0P(#!L5YC`wlCtNABW`y5zvm(*Yw*3O8m
zX*sJCW=td04D7Z<+1FQJ;oxsT|3OjsTmQejwV|_0NKXjzOk=**uwGcua@-L`L~5HN
zVf9d!-Kn0xN>3!~Z%)$H;vND_XQ)VVCo@2#R{95_d9%c}wZ|sNIzwM|=)MZ#E2oeX
zGAiVx(OD|6W7CS$AaMI<D7&s8se9YaUUp)3tgnmj4X}j2Z5D3zL|*B`%yT68{NX=C
zO5ry?4M1#jIJcQ}qsdhaENb0d4VZXvC;Z{nCdfU)J^_XKId+omSDal94;~PaF}!5~
z)a5puzmouSA@n;0qwg1HO{W0+#Q~JivE2l;Xc3zU3Zi9=Gq-vg`;ZCodS0oOFs=5C
zTc;&E>n8W%s7IBi^v%>6phaG>#X1zqE%+%GQ1%I(1G=zb)bb4S%aftBWtZ*qY4mBC
z`g++yZvhft#I>^}7SZBklY$YZ!2z$tIUPWc6>My&_2dq>>CU>qX^CZol9hm+v5@OB
zaYb;)LkHe<KM_<q{lex2;vO-V@&4<e56<@iIBOQiT=w%;EcIln-fALLPe@l#gQVVJ
zHyT@3kcpMHr40UAC2eo9EL+t(pZp}+p%l_%#Z;v$rxVQ*vaFrb;wpY?{(C%KZi~!`
z%k<YBg=W^$I@C-{j8H!)+chjz{M{$SNhp6|H4N-g^|F!(?4D4J1-aIzXHS2Y1`P^o
zMr(XnwJKF~`UXMD`)i!$5d3)d_&#rZs;l*6+}av0KjI0H$2w5sf0V1BrBx8+vopAW
zXUho+4W6bG=6Qn<weW}1n1ah+v>=tiPe=R(L#+EenR5&Ri)$QFJR(U?8>mRgq~H2j
zyyfc}!|M2tz^H3F{RwNBuZ&Y+2$(w>pF+b1$k!mYNzP;bVECOH583FIxX}nN2U;?G
zBxbI7o;rfDx?KJ4^mnKo_CzK5jd#$Rd2x3Dn&s*1_sCn3GqFCRi6Gu1G~oKrR6$O*
zfI8nkI#|ubox#gMEi+yJqDN8~hLV-!MF$q+ZT08p?+`NOOz|K4or|duyb7d<?mR$Q
z&ythDFCs&DydLOMjli=(r1lM@fkIj3P2om;JU(^d>e|1Z4(Et{fpdu{AvMq}3-OSt
zJhv{9`}+B~x!xT)>LBJjqX6jW8BsWW4}TZ<71P1Ji}=_HBqD%u^@cR8IZthsOnNr-
z<$bTTb-|kP2d=Auh{6Sw(O3m4s4ff7UfUoCz9E#zwMN}+XbYX+I9PUsk#yUyQn}5o
z%c+CL8&3{*K!FgGqdI0|hZ^IxTi4u)nEPW|{^^G;1owQ&Ma<|dgn9S2BJhqEa~AN_
zAS>;9@URzS(xPCEu9}uqVOaI9n<OjNF$6X6_s}J)=4T36pM=(_qAE33JqA3n^2|xm
zzJ6eY6<P`C9cx$OVX>8aEy;w%wXnH&H;GXu7N9ggc$>9KS7T8*&Q*koyZtAv-|Cep
zyfpoIUYQwp`CZR*Rwjm2Fp@gyRxe3UZFL@4r>Hqw6MDTKpH;B>BoMSp`U_`K!q?D$
zgS#6X2aYDZodVnl<jt3z12j5H#32lGvflEZhkn1UWj}xK2e-3QZfmk1^q!I}E0F?j
zhj|Z+vFCE+Owonl=)YGlVogH3_5|g#3@zwx8ueSUAoTDD+>FeKE41sG&d6jetCpIy
zEVDl7v^f#6aMESU4aLk^Q;`&p()cVI+D7PgC1QlXOf_s6mV?H_FfOUW-w~_4YP662
zmWyAN&y->61TdGT*?&}IrWlrTXCO`E4KG{Q!z8T2mgvw^GQ)_`xv@N|uUkUYZnLwh
zmLF*03Qz&ava|25G2)Z%mgb-oQr6#ri3xoVH|brL`bIlwoq?p8SyZP3SpyVWJi-Kh
zI1%A@FWmx&3($p`Yj;;FeUceBRvDk9QEG>mRMwM-Wu$78;hls}(gH2ObHY(B&)C5F
z<IaAr@7@<YW~59wWNO5eDO2ki(Ig2?U4RoKN#QJbkOtD(y>CMM-)DkDYLiQ?Yj-3p
zT@-7`dk~r(IhQsJ|KyIfn5(~R-`;#X$L0i249Im(N!5@}ejOx|5g>}w#gAbkC6<>&
zG0)-fI1Uxrz%FRTA)9^ibCPU{HTZet9wj#K{$*$o`5ZG|smsP-4`uC5zFZz;8Tbjl
z0mrMqd;OB1A8d3u-}#c5p$sMvH=I_@iIs(nXf>J@QJi)jApU~E{+tG>hlp)KnFBpl
zgfb_?1iT1uDz^lG;C~F&+c`h~(*h9fKo5E)Ut?RG_ol9HU0eQg&84exWCh!Blwp+n
zf;;a)KOq1a+AF}o`61d@Sii)<={^e_3+G43Jba<YGHBxoCcI%qt#JY}kxjID6{z&g
zx%XWIE>s;|zlTscEoS^a;?=WegP@%sO*$Ea1%m&eEQB7}k^J3vYD)6*$vW+tN}azZ
zP;`>;lYbV?M=PtwXyJUn1d}E6d49OecbpM%s@B(WxZuT}!1r#^Fp6gv#N+qjzBtd<
zWUpZL!0b(TA#NVcVMKh3fMdCEIC*ogZM2Q($MRSRzOUZ&jO!)ODbVM7OEGm2Ti+lx
zKFTL$_b9ac+>1ss=v^utu3}^EyCtx5aC@7R8~$<&@z_^!bPT0r6AY`t5zba#V{~Tp
zq-GegY*%+K1*0wNU(hc*;qzW_p*G!{m(y_cSy#;Fv4{Bb$D<22K}zL9Yj!_kd*)cQ
z#DA%G&S<43N*3JeMyV3B7t=H!e}hzKbMKq5rqaFYZU7LB#=dhfG3%Qv{z5iAF85LB
z!vDe8(Cw(foPv$ZQ#ss8FckEq&v&(Ob}!lJ?v%9reMZ8$!V^PCQLG?7@qLY?D_Hf(
z(wjOvQfCb_-bDY{FTX7AIDXu-!Hm&m2CeubZ)|gz=V&Nol;>a9Gsl>&EK8YQy;<{#
zkmlCj<rB`Fm-WX8uE;hW7Mf?An5v;Rk2FTLrZyG`=wOh6j<Mi*y(mvH_pQR;;xEg7
zmWIO>7yQhZ%2*}L+vY=*E`Us15Ol}mw>qG&@lynm0u)P-E8D2*j{ArjzoP(X29-Me
zf~<!mZtxcF*+gOI>v4Y-3d~$V?9eIN7ynOYH{gE7!egLP6lR%Oi8Ots4qHr;=>bJJ
zv?)J;pl<gYw6xbw{?9t@iLAXmY#9ozJWNQ_H_y{~Lb~7!E{J~H-Ph9T4!R|T&k|iR
z>QYk`MW@y2L0^xy%dkfmzi5-J(sV%JOm)~94YrrGfqkRE5m|*5^;L&G$<3&s86gCD
z9~gdMo1#wJ)B0yP-t5DZCN@65R}XQ0fC@{)2SK^)eJCFUTLTCLt#M9m&1>w4p31`c
zZ;&+-8uGK*B6CegZjE-N8^bna-@r5mqY}HB8L+LS<Q#?%Mn~X}hw_rQiDd;pG~tCU
zCU%DzI9cw^)tk&6>O#f%gpeI|oGxR06}f<rVmHw@?7%a4=bdE5+!W~vgy6V@M{K#)
zl2|`4gE|)iU@y`A!JYQt3FMc6(OoH~lw%mFWx>US>x@+T24H?^HB&qd2X@>0^Q%XF
zLR~|-l-?-FBX$wxEPDGV5c^zr@_+_cLDsw?LL^FUVcBQ#f2e+{C9BaoDH7odc}8xB
z;DsW`4rOTWN%aM)>_wtD<fWz-n*!0B5+E_ah#BaT4r4v6HG-phD|CgNg?|%=*HCrS
z50Xv()hcosdI6l8nZcHm(aCW+Y%}7Ny5-BTA-ycz1Dl_<EqBVlzM!8++{^w%cI5qx
zHd>rV5zhLWFQ-I8)?7}f%!NqJshyTt`-~vn#iqA+&!PA{ZnA>iFIdm%ct&`tOAUQj
z7vCY!Dw>v&kDVA)(&WqZ5u%A+P!E-tMr?W@x#$W_{6sjbK_pQW3}`!iOBQF;orPi6
zp4ct2AX#kY>+(Ly!I2tX?s*=%0%7cUEPCT2D5zrCA>(RuB+<kzBgoJe2y#5?Q&yml
z@*gZtlJxcQ9rXsYq=ei$uTS-9Mo~3;=ep-Fdx*;AnTijL3Ek~xiiPuX^GPTZz?(CZ
zT1d+ME9+6$BbEkv#};pd%7CC6ZBBJFq&n_u(#*5J7EQO7pjI_qAurOB0)Mp(5FtP1
zp{_OO!mBQ&Xu(CG175G($t|IFcl2!SRsk6tHeHuUABCu$n8H_`PIu?;Am2w`G+<`E
zKC-L8N6xb5i-MB5vV!z`*57(p<ZV4BRu9Gqm}J?S#S>{SX+ywIM%gZNHU1uj5znL=
zP`3R!l1`%v)rq8XZmQryQZaiNB_lEz6yG9vF=O2F-JDGOGPK9-I{$!0z=Fn(;QhcP
ztJ@FDoY~i^O3A4Xg3`@S6EF)QA~}SzYKQ4X1T-~CZlp9G(*EkwlB-I;cAZxK>3<z0
zjD_Gtkn+Y+QLsJ!YRSzjJdlp_53BxLnsjDv&fe>aSmNW{i?6((jKu|4>>wy-=lR|7
zjUsOB)MVu|UUC+ed-+F=75<p&tc`tR4V?EH4UYs7I%#dBFuwYtt+m^GxWq#2#WtzQ
zq)&Za2zQ{`m6~p#_F<?kkGC_&4IqzrXz?kTzoB!tVKuvoCUZ2uv1wTT$q(wGF%V2E
zJt_S8@HvtN=4<7I@jO7hYV_ODmaY?{eevuBA9AUOPWZ|Z=~OdTYK%_G6a2_!xmd#K
zY$&4=j8d4jxF%KgfZUc^i>h;+QHn$j<x|avjMwXPP%V$I2Y5hxachrTecM0aynh{I
zsox-5+je7mrj$qo&xj-`(@2dXy=2qM)cuxSUf~?BFbZlD1%~Y`AQ6#uDz#PB+ogiQ
z9ufp&0TnA;fsC2r>yzp2=6?C4Ea_T50WPbq57Hyp&nNb(4XI$s-@D}}b&xKcs>DAb
ztcRm0a@!sNgmnSE2q3ddi<%zGPLA33`t^<;%~M;YnFhIAPD>NH#Ev9Yo>RJnXEM^Z
z`h7C*6)jblxS^|lK1Y33`mPgjdX{U;alPO@T+wB3VX=?EWD29I_w3O~H82hO9mfaA
zUijt19+RVJNh|G(HU!{xn5cp&StTmB&-jEC+}(9Q8jPqwg&6@g#HbeA`z78ih8(U^
z%`)xe&#ISs>VkYrT#0A{4%xXQP9Zm)p@aDP@pvW?DF^!$PahvKu4UaP6-Y}01nY#J
zErjEKzit!~asT~N8<m0kKlsuq@0%m)Re58Hxj$^YX<>ilfrEH|<PgNdUqu&YmE25h
zcn!9*sGVfC)pyM<Wa$OX7Srapuxe0FXmq!y?@FDiqP+)vBYFJn3Rxv!jMEK9O8}3x
z8J-vdhrKP_jGQYM+Cu)E401S5Y$`p7J-S#2&#_G9;u5}trEGZ@pX06jYuc`w$Z>kT
z9*2s1;}h!vkkW7dL9ddHAJA#5J>5JwPT9of?~-(G37d~qT$%PYqNfptG;C~J&5~Es
zi5P1ZYoKT;dBFs?yg5WhldfICwr<U=J@r?PI-D-wO!z|OZI<C-ya`(wqmtph4+?HQ
zn~Le(B<Vyf8n6s?53^Yf%NPL!Z0%E8TR&Qby7bCl@TQzPtPJljZi~op@a7Fx{pZSy
zv1=eY4EkL$39q_M2!U(#KD0pHA?5kGk*_&8ktPZ6YtAMI8dyu7ht4O}=~jEM%=N@(
zg{&r>RMY9LPItN_%~`}xIRDjWBC<GlYW-}`n?%a)g1`II5*N9799%?~vTZX<;5W|B
zgGwz61sfK3FA#t0RTQsVUbP2}JK)szWR}@(^R<@OwPH$8M|^QcX6{0R7zlQyK0eLW
z1GrVcNYo5HY^Ag6&DNW#!VGNZSx7O*Gd(V_Aqj~u*GV0d{1B?{JmvmeE}uBT_4zM4
zbr$JMA|hED6vsrbL2J4kp`1fxdVxG^T!M~jphQH@wEU3|e!IX?0Py~J^V-cTBl1Hl
zsWv<A5t%Li*XIDxr5t~!#g{&<wmf35VC&@WrQ%0AysNRxY*F&B?L_rOcG6o2c^s8C
zifZQ~3PufFVX+ES$8d`>S+?n60oo;1=jxbbD{9UzSP!8&{hglwY6@eTZ+L(SopAY-
z;O_2VUxj_SNGY5;cT~Kt4{K`5^xUlS6@s}#xJ(0y=!U?gz$o2$;qs`;^K;G%>-B6Z
zat?)B`y}V0u_+~$AZ7080C>uWJG>5nSO&5K3&E04$y#ZM9y*|;#Jz{hRHuI1=r^{E
z<)f03eA`t8nuL{SfC(+kT3f6pE$Jd6#Uy2!=kjQIV6&vuXRW+>YJ`}71x1_TQbTTK
zQsHQ;OSj=Ig>w%_vIIi&=||Q-<*Y4->MFi1{T>%Z&%KA=%wjx4=L1qrtqj~1W%LBF
z^nh-jaa2eE&1%t<w<XEYqxfR@-TiYQ7$uL(j0U5K<uDA{BBs9!G{_AwY=K;Fp<vu~
z^a&^4sF;jIyM~K&2r}kpKRLzgMZJ2?D@lOzraG&JtT7ZEG3dGh@+jHaD3Yg<7J3?*
z|94Jj@dmPZGIEFbKsSLgw*s2#V+~s4G4s>RtH+oe<awK@ka!kPS8O6Zy(M#HY6`@P
zdZLv!nU*jQt`vZ|nhE@i(1G-fm23D}XFa|IU@0t=PJ_;VcLkfPQJGT}RR%tBh61kN
z?UE@_3VM74gbX8_0jp?-c--LBBQEXFbO!g{_`XM<QlP)4-PE?NIf4!(rrcfqyx}Fh
zWcb0gEz*;h+_bqQglZP0f#JaT2i9a=0xh-so+-5l_|Xe7;F*xcZNLmQaW^U|SIzD=
zNb!N5&RJsM!CtTmnyqt?Y>4^-M#5$^cxAR`c^_!45XvA&+sx|4_#OCjV@Ra3zE!a?
zg=#o&+>P6e(l~WvD$ikrg&xQttt<W=i_9sfelU>6yp)LtVPW6mh61(!LF%cr^46Ni
zXMF4M0LHhkTD0%xcV{PuB<euH32uQj4bOuIMXBIm$^qP!Zls7nDxowdd`qaBsme}c
zZvBc;5-WMHrIu*Mf&V1=xnay(y5Ga<)v$bdCu_}>tbB(2EKh6v6U&kP$vboYF-4jN
zr?*>dkzMLg96p%sHxhy@ihL4d>)_9~naKnJie?0IyANu~z7yFpDu<dILdGyobY(Y3
z2M_LodIReNqTlbw4Tegumd3Kygz7Ni>H>!R^7JdB4x5PghW1rw!VjjBYOi<4!TTbq
zw0lnElM*W6jk!YlEPnhgxe~7*l(&ZiUf>Ahk6#E>!SU-CNxNCt2j`oN1r9|;onpSO
zx6D^G)Iyz?n$Ea?<BgcLXfc&?*RK%P`U4%Ko1x|arv;Y`iknd>w_EjVUwAH(n~;$f
zg)#P@^;r$k6}UsJ0V0;9B-obl3HHu;HRowe#s;cqg19nl#sC5q<L)JYzZ;rfDqx(@
zU*?fsV3A2s48E5f8Kp)67FXSu5}I*%z7x)1!t8xPW_4mb8ag+K;g<U(wJg1|R=l6h
z6Ro*|1d2Mvc*)O^`N#f@ACWyhPFZ|oCnDX%YK>6ffXTp4X?tZ~dfG9NV{vIm>bRRc
zx6rUp-B*V<S++<(2CDSRY7N_}VGX5p)2z^pJSS-=8Ajz%j<{^HbWw#*yw_UHZm3L4
zVt@;HMC`ag*^?<Z3*o0Pn6p%5@M1RgI*v?Si`_sgsg;>WGn!4V*qEX~Bj{zJe8YVo
z*IwqV0-zhr%H`NTzXM?SV8@-Sk|@%(6Bzj@>J4TOHEdw9uhgL{tq}(A7!3_EuN`kV
z$F3%|A$?^<Y`wrc4I(IdV$HVuZAZL?Y*4>82Fi4=dR=3hCs-ZnRedeqK+#2oF(NV>
z$Ft5KBTaWX%)1f&87YTRLpmtQhK5v6^)Um|hWwz28k&U*{NN^2)Jy9tkOP*?HCf;z
zScY&qob{Ko3K(coGkrbJMF|sy^b1$KXotcZk%~)<6R2<c;#5D9CyY#^@?7|0mf6;R
z_m+1gDUVF75-QJ9>fOzb7fg#oX~iN>>LJdaAsfo73{vVK!|Jt8cEqOD9Or;xSF8q3
z_h|4TfVnZ0`|Fdy7J8Y<o28(AXxzpw8>lk&P|n#Wj^%hZG|8``wnquY(iL~Y`Dw&s
zQN&dNp~Yd4H<Q>plS=5Z$wxw}$)y&|Ua(of%>$ngcNBfT5GY*2Mgs5B0xX!sbX!KF
z1*=G?cZdBS))xvm3md+YnU@;prBX!HY99k#J`z&NbJl!b7ojV5F@dyU%Z88_x@6%H
zqY*))yBCuh!S+7P$;LI6Zv&<ln8p6T1?ES4L<@s6b^1}xL>~>@j=>y&$Di;mWLc;h
zJ}vLHJel#oG7&68VhSn@ua^%jo~W9EbV+9S`+SKEyG|<MBp4j1^;nf=AY6jWfT~e<
zThm(jdXp^LWP+$mN93a#b1ai98CFLFM!68jTV3%S6$BU(KCy*!QX-^P%M=no(FZ_Y
z_+juK5W5>iBDpHHaL4_I2rX#bQOvUyb198!6@p$1?F)eqik?s6xhkc(M;8wJc~_uC
z9ku>z%4};HGgz4Ow+K9+mcf4kBo;LHs>J}4ptl;{mfF@pmc$r|`>Bv5L40H2^;gP)
zVdEj}dA!sbpB9_rH(G78n6bwSMCUyn#5VISJe!eogdC1yFcJl|8|I+MAef5#5Gjfg
zk?X+`Joj{Igf5mNT<G(P-Dz7aBr9bt;1IJ!3@f7PIL$;>N#u0lC%heWU1$CU!{X0N
zJDuSz9N=D5>$$@0w1v~OCobfii36ZO<lY}bj2x8bdF~-w@O~ctetn&<XtYGg7jiTN
zky*{Z3L?>v3sMFpFeXNkhEOIB3I+(1(Xf)9ld<2Y5z1BEbY~<YCQ3YzU@9tdgC9QU
zW~-~wcgGYGUAmif=v`ok)D@)cJ)eEc2D80RFd4$n@?0irr>A^lTs$Fri>0jdbRaNb
z2OruKdm199f#dGdzgnEwrlf}~eP`I*M1x6d$M7FNv=b6tB|=JO#pCt=2<#4jP@OBG
zXsc*^O2qyNTTKfp1IBQ#(6O?hTBbXD=e`x8S+JcBszVZtm02AKnzg1?smj`ypzX=}
z9<+Dp$Nho@o;NZNCH|R~pBJ`=Xn0F>bagzp9?~z4;gzQD!t)GqhsH2@)|cLZi9vDa
zyZ{yxbtpD5&~f#jT>@NXhWX;1ZhPK;pjB-&@FfoVqn@~YY}G~9j9e+%x4M=)b&rFc
zF)kC1$wNS1Uz(GDfpx@!qAo>XRSd~zMMsJ-Y-B(11HwKNggI;_@ken+@4Wr{Njg!<
znzX&<Wqz+(exwC`{EQ2u7F(?Xoh=JlON!K618|N3<r)k_Lf94W53Po0O1xCM)JL2G
zW%d(zzGz5jy#w+w*QPAv8;8Ci3||M$q&JH}$K;2?43kZNYIA{%yVHqjT(Haa7^V0I
zHfdV&{*K6VS6}t)-DllZVmf&q*lnt0YZ>H{6d@2r#iF?Jp=;bz+~ba7==Le6Sx|rc
zJGkG+`}OIoo#cfYu_dNoYDY7>m|!0eEd&aW%YwAYU^W~G26A_nvO$SAGYQ4Ln$z<?
z`hMy=?&MgJlZJzl!=+>W5J^q-iyXxD#Eay1EY42nVWtbOf0&gm){O7SYi!0wu6zm6
z<PB51<ykyd*sKqf$qEtc5rI@F4Wt{=Ly?+G_fQWRMMP%p*V~FcZm+&!`*l%`5FhKV
ztj{VL6{7do8EJf0GI)|I>%*Ug-W{BGPn=<ld3mMQ=9mZ4)?5*{67%s{<+Wqv%hE4t
zuq(@kI<Q#{$|NO8$Dtp;2`v8i<#`Ap-3XbTUXunZLth18WwCjfL_aUVT?G)(w$qDU
zHaQ>MLnl6kmKn$`sI7V_!~i%EJ{Z~n9IU-<KC{|b+E>>!`E<+sT0#TIe2qCPc>y}l
zBK8I8T-2j+@Ll)Byb4Wg%i7Z139{S=N5R=#jmn_vODZhcJC8Co8yBuc4K|>%{mJFs
zI>Q;%GD-BZE5FNBuH6|{ru{44PBrw)4P~X48f9bYM`ayygqd(2G%PYcr@^`;PjQb`
z?YMDyl(v=Lc@q#?S~d(S0+Ml&*<`koMAVmLm-S(=yIbF|-|VaUg+Fh%PFhx3&`DLH
zm@u~pAnrwr^jF_As)HH@Z`Jy#w#F5?Z#Nj3#_K8U4t9x3wyi#<$YPamYa6A1#cHL`
zI=|fLc7-1^j3qYkol>F9K&aUedZI92pAl73ihmq~<9jP3zDZl|`urbjSPWZ~K#f8z
z%RBRT7tLm&InFt$A?%$^iuGe;=u<s1l3>k)a*-PZF}usaEv2efAs83k(7+|MXY+L}
zDkL<nM_e)_B6Z#2aTf$n2eyeo^?c!V?mbcrprg@ZpRu0TFf1qAxRiH`tT6~Fd~g*O
z6<tr@wSv!%a*Cg5E{J6?rP4kGQvyBfFPnI9F)l)4$0Sg`y&!X>v?L*6LlQ$4%r)CG
zOr<2SWUnG$Q4oWucvBw_hD<7tNrF!jdY&`IVuV1N^h4ICzCWU6th7$k3eUyw9u-A^
zd38qe&q2IQJ}MeIEPs!+^-C#^mlYF~m-3ZbMcNd$2Z@H+U+b<2c;SuWR@z|YG$XwJ
z*bK(-Lj!DAWHJ(ZOlS-*ps|<B?-7iR1&vdURV+Bn#%G~KS(<Q+sc(OPn950g%pyAt
z1)HNf&Tc<@XL<TGn7LCsm%qk|O_&>vn3aE(1QOq>`ngwJ9(@YIQN-^=UJTvG7WW;U
zeI}8*uqby-Gvv14y7YKiP~?BCd?JcT#$)<Mp2^w?iF(xp7S#C~Cec3c{36`C*3yp7
zbeR18Oxrl%n-w5Br7T5N;kUZTv=vLj%UtCV@eLbzr=uNOC-=<dxO+7RwD)^K)<F!1
z&a?|ih81H(OXQkzQF1@nxbRP2BFalWmw7l(Y!0cZC14nuSdX51UdES^Y4f18sG5hm
z*Cn}w^(-U#j>cBwjmkf~4q44yxM{O!H#qkVd0JG<symq1ebsg_*a7>=ANZ3)imiQK
zl;s?taz!E8A5MI5m~s?Fxq~$a<U;?XRH1D?gbu6(e32|f!0MN_k_3HYJW6mIgU@p(
z+o!`VMI6li72A1LDU%dP!C?Sga^^-bSKMqvQX2^#Y=@WeLXiza%l!S`7b-Q<EJu>F
zQZ+eA91o0Y5Y5}?Td{w^?XaNj_u^BVBunwCa{96!zSfq~u`0GOpC45-k$7At+}tTO
zoCHBJeA|?2Y>bAYQ>^ZE-<b*d5B-%cr#E^jjHh$W3(<l9dO5TXC`@pJfGCmz)X{!J
zGXAvB*q@&;@b}ShboQVM88f$gCpoQRi7N6m<gYw~u(ZF>7v7kytQb$ab`o}))Nh!W
zL;B^(qq1)m#WX9G-|4008+&cq!O|FJ!eIGLTrWmVyXk655}AaATPiI2zMfoPp!Dq?
z_lr6z*}T9($k1iSw)gF~uJ(dZmtiiGS#B|paCwuWZjYLHqx2nFGFfsyiADLF+()$(
z9rtRT0_C@oK)=IuiQv7DAhmGAK$78|Y(l37F}6*^YVovV#+*DldC_PP(7l;NRqK(@
zXD=S&-y#=X`&ep&`|(?BHUd}N5fNVUU%42Td{BIz<Jh;#KMi3^i{?t@fA}c5>&~7c
z+R1wS54@+DTNXor&_<DX@AzZlcr&P!S-G?X0kZjgs3qqXv6$YbfUa<G2_*U|Z^Gji
z<n&|?aS77a?i9L&_~??9KtF%Z5Eh|pI!1E|vm&M=%;uZt;07{?G|@bIMVn^-<*%Dy
ze+1WoebD;800*aND%SFN=Xne(h$h%4(PtM;SgGyK-5(Tx+G{gaRS`5*oN_Nn9>ub<
z!31ObWpt-ORv^I$N|qO=xlf|7Fw>cW?BsO>7FTxH#Z|V`xuQ#J!baSMlYr!PM6bDI
z<z>wfhl}(x9zPrB&Z>9=HdOvVg9<PXb1N6mf0&yC**RA2n6=n*sfFrZWVW4m^sdQB
zRN;y4(qmVKm5{axC(`fhh&7v6h-~t>nwC@v9?V~galo_N5B($aUzC+ky4_aT#&8Yj
z=^=^)L@tTjhT0Ai+CqtH^8P{R;c_aabzfFA5I0g)92=3<)L{x`akM>)FMJqHOk8@c
z3~REg`ydbuN6NLTCgsPLRwXy18Ts0fxWN5zjLGKrKG&HK)jozd#nte>_j^C@N?Vt^
zUpgIrA(wzlh4KusD^GgH;WLJTKiC&Xd+@1V(j(^KJ%d=l7RF76Wje1<Bun51;pdTx
z>vorHoR+`J)<A)!=VaKBkJD3TBOG*Z+o11i99a3)8g|$%u2E0sv}?XHC2fvP3D&cA
zy#X9U1d55@qtE=hWSR>w+*hNOb;_f)_X26aLltdbPe_mO0$mthFn-ZRvO&R<@DUpy
zl=);VK0vQ}Gm%PW+Pp$gixjt@WV;l4xv|Y&?nDU_6*X@&q&9mZ0oF|7A>ah5{}HT5
z_`QJpz5D&y{{{LF*ju09@7uTNKiZDqpZ_cO9N^zVZTqjZ9k~BD?9GwR#T^RZ5Ac6%
z{+}NeWf%akFAW*X;wnYU{~+u9KOyQeZI{~rvG0Gc{{!9QNM~(eXkzU|YvgF*Y~pBP
z@ZVD74F6@>7ybLeh`Nkrj4D^+KWg0cDRQ|)a<~^jnJasR5t?u-@s&S73}|za<2!P%
zzmS#DF8{IDyGs!A`25tBa3FX-U!C6H5j?mN?uDqyzb)e?k~6$N#<+eXA0KjrtT-64
z6kMKL7vu4Z?>$9W>pi+7MTZ6Gy-&$WRvqg|E?k?uY%j(+ZCrAOduZAwZs4um;cYvm
zFYZ0*0edWcgm(8CGKJVuiga{?&xzO}snXP)=L5W@JErbNNG4jV0o`bq491HbxQ6yz
z@AQ3%9LTE*j5Np4T!a49QvCnApbA@pY>sEsR>!X(iKtIb;A>7xi+Fxq6UUIKN4M21
zn>L%y>(KI3MNe0uVmW%7Lap;C*!<&&Z%d;D1UxqOJO%KfgyC)dEyOY(7!7~ejb~mm
zV&{prM_`2_$u7(M!Kj9Z?F#jUMk-?fSV5K)R>=TpOz8ijeITeOHoJ=?)b2VF1}VOi
zC(|eI4-6ln|K1Qb2U(d`nf1-3;>wEYv)y_T&#>u>@+}^}Vv|r>yUh$HXtqH)g`-fP
zPd(cy1+F8Aq1l#L_qa$f6(q_`!=p)t(nv`4F%Q&z44Wbjz_L41zLxM2UWsl52(JDM
z=_u?EMIA2Z;4030K_#|}n{PlOtVb50K*(m!nRf(KzrRTkzXGG%rXDkn84h6$<dN72
zN#XD|b+-Pi8RM`t<DN61bG9c}Aj-|A-Z>*1(kRL+>bl^ANZx87py~_J#Nv<q*Hg=|
zjm&cSmIsgQY1G>v5x`^#ZIh({&Ilv~!&w|=Q9!+ax+cz6hs!3Qt!lyIcIK*+t=2iR
z_42x2IZzKMg9iodIblhOS_4fCY6sYjP)oG9<{T%erT^<yjYDGePKIVjpDq~Sk~IzZ
zjmDD!#8)M7`e9C$8yYvOFix3)*#|qs<hpYKdLpn`?RY<KqA3|_P18$Et(io|IUA^B
z653=4oZsq(=f=@VNuy+Asr0}yz5Eyrhtcs+lpggsqFTTLp~Xca5*pB>4C~AxpNY}A
zpAkd2<&jT-&cI)O%0V<N#}Az%*_S`G_+Btw$V^Gip(RXVd|pV$!J|r&O$*V2XpBDc
zA$1}y;mCM%E1waGU<tJM;Ds<&4TpT>I2KwrT)mO99TMc|NPgHTP94<<MGbI3)2|1v
z>PVf;>5-=Nv?p#?mmzhkxdDgk%RleBTsH&O0{coS#fsB^V(NWr7UY=Dq_Sd}9VNCc
zDh%l@AG~gtM9#|hK2y)7dNwIkt#QiaFPMq_@5*U}tjLFhk<@A9Nn?Zonu0GHtX*HI
z(wW0aR<q-iNCZApSV035=Bl4hjJ{!*quEVwgye#^5*y__{f%|VYYsSm8$KYLce4em
zw8Gv&6RJT%{18B%d;<DK7ICTYL@eZ*^y4hW1lQxH>nUgjv(S10Q(WJzZG2QLVb5(j
zz(@CtB@gZ5$x-zMzM;r)d)_j<*>eHAY&~U!-J@x>Pf6<tGibv`hW&ma4vG7;3Yy0s
zD-<~Ajqj^@Xx>bV<%@wHLX7zu?Ui0iqKo&2FL#<Jccm6r1$>vcaWnt2py!xg4s2c8
zrDoi^HHv5rw%)+toWaEqJML<s7RP7QY3bP%L96vt0og|dEv>CX6$)*Sx5s_I{}AGz
z*c-{oe^NRN{hzUCn4SMsI|=?zA^zXm>0xAT^4~+xT8jUdawh+i=pHSp*sXSqoloRI
zG~Egx|EuT*1m<}B5$Qx8Ekn1(B197fYBx7{{LSj730kRDUN-V0LJo-^Fug?b6y;VR
z=n)mli_>3UZ{y!%6@~8F+$zz`wjfN*_Ybz=OFk`&NKMqIFP9AJijoS?Wf;jegMxAq
zwrsh#abA?19xG)NNTbifgyDT}Ok9>Z&)54GxEu;!Lr#eKwv@A>9LuFU@5SfN*5!O%
z;2ZnFzhJFrI!BXqOwG`_>3|W+kZbf_;&Ma#Fq|;ea6RVJJvVTTa_56(LD<OL$u<ww
zE%mZKqBc(pu=Pa<ZZMWd<QoCX@8u~9)riVqUvBcEgcvl}4QXA<3+ug$p~;R~ldkfw
zLksXMOh#T@QLQ@q2sY}d59C@N{xXvXx+-z?4BqBfO5<5ng({b=DGSLU^p46Y!8*n&
zTfJ0J%digxZlOv&)u0;YTHL(5&y~1V0?rp$+<@uZ!qx{scp`cMK<N#Gs3_oDd2%x~
z=W4FW!iOdb=dFoiHG4)y{6=?l!$4SK{PfI{uQRN&I>J_2TM_F(S+sr5MR;?alhFrh
zkLOJ)INtt#kU*>glX-G^GryE~+tE%xr+CKiu;REj1k?UE`!GBv+zr=m5XXf-x4S<O
z!n0&zE~}=K{XN(u&trUlrKt6em>MqZXodjbQLiL&7ROtleOJYI5ZX=iO)M~(;^p_h
z&5|F`zMxrE7!$6&Clu#u`iEQ=rR>*p+gaE;dln1pR6hNWc)2UUAT}67lt%Cw=y#CE
z8=)=0^Tp&XSk`oRoMX`GH+PpB0hjx0#ou)rfzJer+wsPo_E98I2*tL~MiOHbY`%NS
ziQ`!>0(2aVwf`c!>HD3cIT~9*c!<2rvUMg|Lm583n(KfcXkyrt9G9Qpct1ojHuGu;
zl%AIW;7AzR1_x9V__HDI_))kM93`_QgK;vziOMB4=6C?7?2e)KAi{{gM{WS_vrG9-
z!gHLd!gPueUI5g(Lo53>T$Jzm<Vm2tiz}WbUXn;yM+n~Wz5`#VE?ArlB2lLHmeRI~
zQoN~MxG<q%c`RdgbW;U9R`(9p2HAbXMkdLhJV*_!L^A)v@>NTsQ}eOBPM}7Vh-h(H
zaUssHFs6G(1Tc@@NO4w?kV^TgiB^_rSafa=GpF3}NNVsZP4}25R}xf=O>0nXQybSu
zd05p!q9v+3Pbge$$oP8k3SAZ_H(4-V52N{T%UG0Wk+$@cgu0z{xwO*7z*=EAt}sSm
zW~rPx-4xGPJ~zpgz{TfTV__vJkPZC9-gzU#xchKG1tt1klPFiM(03tn8Eco_@&*u9
zebQT~#K?ccVU^GxeRfE4LN}sWmK_^rr#*35#qh9;a{PjN1+2`&Y#A~@H{!V8y(l4-
z7Z(K3C?G!%-`(MIuB&1MZR*fCw9?9${2)P)enw37X%hmwt)STiHKO87Yy=UZoww?4
z6tCkf52_B-f_fW}`O?#6GZlR_z+@O@fToF7AQ{bw7ml2+>MA2g+qP={yBQMf_R*D1
zK##&VtNTp=GP8(7HrCG1a$5!hv0*xoH3h>dMovm~a~e2V`rGHWes~2Jm>Pl-AWV}?
zlQk4#MI!$}k}zQqK-_0!fd-Df=G=xO4)RBp`!H<*Zz)ZIDIuRC)sfy`4U;E_WFqg6
z`5{8u62d&z@LIrdMh)s987VNfqKDWAr!S2dX$*jyBO&M)R7SA`YIgQl43iUmA678c
zn{$g-?`yNVTy{#Smg?D1wyf4j#}hFSo>XC-?|UC24dEDA0~McrDD^j3GUNP!l=?<w
zE}lfpByO+)h7=WXBrf~`<n;71gJ}bKLecnMKUD!!4s1B7TmAsRh?N@H+wgl+zH{R6
zBTz7REi1`b?ZNq!vez5*^-Y!r9;NeKf^AA<A`3Y#zV*BdO5YLNE+p<D&?mN7&lWC+
z(~x+WCjOi8g0_Dg_m!Uy_V0n#!|t%w19Cl<gXmRJZd_ULvrBk@PFxS?D4?APcVqtq
z_d%zx+x8s8EvitI+_u%_=KC0w7&PH^$1zp)O=5$}9%SUti~SGhljBNkJD|UV9R}b-
z`{*Wh-8nvT2@KQRv72cN3?j4n8wq3SjdeB%J0i>h4oqlIp<!q`DYBsEvecD4fz*D*
z(B?rLemYs$8wfSQz}nD3RCM|WDyUjaLT>nQN_iG4HM*W`s-Pv>;$RHEgR5)Qh3D<K
zJ*AXF;PsMeBsc&2qi68J4>OT2Hi}VLef=2-njH5Cgbi+Bz#Q%#m^gy7F92tFXDBDg
zih45U<WEbY+@KfGas=p3mumkxeuD}f)<o5O3@KLHQ;>LLjGv)@<aGx(#AKN98L5~^
zOre)eK@+-&yMIUro~{~f3&&~QwCBTysNcAP`px3Kx1s(Tu<@F7zQJLG0d%$_b1bMc
zx>sCm&rrb-m2c|mLQx2PZ$WR83&t$@U=tvk4COszfC*eb6T*#s8BQd<D8>a-yw6kW
zrW-9}W`te<uf3!~dhe+at+P<<dWe0+C;2}3lE<yI+81<3O&!{<E(8F=yK_x%@y|sP
zi@U#ih%Y9v?VKJvzn~AjdZV^%esaG@KbtW(-2Gc*{ctN$&9?mz)H$A93pXS}{1yOL
zUl2ghDsG5Aw!le$IJ{Oq!S)3ZZi&giRK+~wrb_v#Z;lSBKcB-p{+#@n{s(~|*+>})
zaLBpIkfKV!BK1;d-u&r6cz`Q=)@cA3+WJ7fIPz#?4?V4rUp_s;x&|*a=tFWx^~C^t
z8G}zI*?BovN!qfsKm00{Bu}$N&=P}4^CPK18zKw_FzJUmVb^IkFm`*mw9q~0^Kop4
z%*S3!0X628qmSqK-t3n4^2bokO!N54Ob>{+Bi3rlsL+lu@%KQ_EQ}`%k(>PLz3j<=
zKQ7CQdu9e;=!JLKFC-u|;&kKp(5w_s;x6?nQVA>W_3nIsFX@Br@9NwB;0zb~^%p7Z
zP|@K-@637z8(^om%pqGtB~7vqs#|I0gTDKPVA4*!%b)|Lfu#Mh+#cp%2W7PuMuq&N
z^rqHiJ{5KPy^4Pa5!mbvl%GxT9Gy3%@9LRuNU02GN#(bO6J{r{t~NV6VFU1P!tD#<
zt4D>htN(Fr5;tIfA6}=;x<De1gBrMG?r2`x89=rHfeg@qeZO2BuS@stg701K!I;W@
zzh$lv7C7pi2@<>mJv+_p&3N}EtI&G**sx&(csUyV190Y>mcL#oAy!!nBSjl3tyRmY
zsseUiO606*V1)QGI9$!*l;O*4UmNuPS?GwC$=9HuX<yQ1@ycWHo!-ipvN;`iOV?Ee
z&jVIwNu|OR>i_e{7o61frd~U#=X+6^hvz$&qpyA3-k{a}9G>DsK6{_6sV&V8q0;`5
z)$2Zq4%qm{$Mho#f$MUi*o{BQDjF(gGMxS-imvnbxp!VK8ctqYa@>R$byUzmQkL@6
zZ;=4|M1MF)?`&}L2^1Jy2Hiia1MVi5V!9sb-qIETkpsey4QXi?*^1RkxX-4_zK^M_
zZ&k)2ge5H<y_g+7<Z)LAzwT3Jj35HLAA6E5p&mh^y43-Ru8bwgOZ;$BOknLm#&Z4N
zm`APPjQv<~z*-IRtzT4I<X7N#@gv&S&QM1*j_Ys&<G<@up)PL9*MO``^UZ@JwI?s#
zbs=vr(L1ge;P5=-U-{;!yB{hMwDi2=0v;vlH>?n}A1shHRS)t@!v)61fL|eq`?QGq
zuW)b^`Oir)q(_HQ7G!8Ae!ep@oZnLl0^yaUn^!D7>#c=VftiZ8jNdb0xHd_!$&S8o
z{HwQkTE5mH0@~IkuBxf$pb7AVDl*;4*2X<(_iRAk?E+R@CLkHdb0bE#qcX-0_T-w0
zRs-Y+2nr%-MlfcrcmnAR9A?@Z?;#WUU3d_PcX-!)CkeED(w*kG1sKz%p~DU`Vxr=k
zlszhkrxc!nIygGg;p=?w#i2mF!-4_ymMkzk|05;^jk2#n$Zck~!jI+c*G*bcSLOih
zm?=}SBxB@$fFq^pbNm6P$ZPu2^1F_ptgCgfK=0E!r)0W3HMiiM1LlW-N+Ht0xdN<d
z>8BJeF7D+$rwvDD1#-q_zIKB%yqI(66m_x=^^jBA_`0It<sx&uvA8ygR=+Lr(y(qx
zrguli;_3na2HxnC>1nqZ-S6k+-+#6d7`Pi(PJ!IN%0+_XKUXg=ibwy&`N8~es~1Zr
zJKO&+M+u-s+>)W>e>qAf@jS9a^zfpeDKD@^OIIM~@%e>9`16`UOp~#9ax1u08U(O?
zH00wP-VCIq1p<-@?mMqvCOfZO{<Kh#qw!r<XSuDfRjinDXoH5_k@A*(Le%Hlgh3=c
zK`c<r4lA=+END?{XB8y4m)TKDwn@1M?c$^9JDB!pJ!SZo&fufySBB8e@jzXCMH^wF
zt8)DTtZ1-7i;)HEsrOFClk$J_Q>2rb-qFPJ<!Dz{ZfP=}SPORC6OnPkb{k*&I}-~=
z<6GoFN9#BPa{E>_`dO-77Khh{I#ET5sAD%ikVhG5y!B51Bv}VY{J!z|O(O4wQ){9L
z?Owa#{m)be#`@E_kAD_g@}K{F!VNwD)u_Y&Z%^3T!uJ2CJhU^B`M;UiG0IZ0oAl7z
zvlPM9nKIcx&T7z|<nsAIPr%Jn#^7U#qIvm2{n>?S<+BD)x+ExOgkTOyIU)*2pYgt4
z@|GrJhFhePplW%`7hKox)tt)T?8SSkSx$;!3SbWr*)>X!$(6m_KA-zVp5Du$hjbZB
zyh>rL6hM+(RSn(SV-02DkToBlTzG(f4l|zEurtOI`#%a6cli`CLR-m9X=&W=#FP6z
z0OK*6Od~c~Mf@=_k2@jBG$aFS$z2?yil^DbI*>2}_GTSWEWQT`g)-7)Cw<<KZW{@q
z5v}yVNs|ropvOU%jk3u5L9Z(El%3eiGa<V1Y8&PBu+<s+kTjFJQTs5&9`pQjv&r&h
z*ms?%mz*M);LN_UC5JvNbif|Y!x|VNw%E)f_ZN*y{Iz0WGXY;!7h|bX`X^1~tRM_m
z{IlbMWuXZ4IUsFS5Y)h{+;YDjev7&zS3nvvxKPXx%`+Q_W<zxE?P5)>4T64{C+sji
z;Yvug>n`T%C3l@eF?K-m#??}GsoNO^IkzR$xsvFMqS2G%&vy)!Am1JL)_0DRk8jeh
zyZ+ahXWHjpC|^lOxNO2cih4ED4zrBAS~sO~++!+HlXy`AGYRj=Jo(2w2XDx(tuFAK
zH(pO^LS;KFTBi!g#?C!P(`nQPllO4~y0;Ghrr_tdD4X^$%X$0^>id-0hKK#<AE9%|
zrHMRxE<^qYU+35)SkSH6a&_6ZZQHhO+qThV+qP}nwr#tn2N84cM7;AU|G>_(GxI!a
zZOF~#!O#Cyi7dd*8`wYq0MP#=?f>_ccaZ1ozwLG6|5%BRCQf!Pjz<5VYJ^+)zt!07
z)1E*q=9<T=hX7U#puRG<7LAc1kZ;hDsej7~#&b3zUMMW$sWObuNQfXNi?X^BMQI|r
zw4$nk3@WL-LY{Ij_D15Jn!ArHhD&1~J~Q!j_})4D`&>!=S*4=G)D-gJ(nDAK*R&Pu
zqQS3A^;yTa)V1QKwzFs2%SEl?X4Pk1?V_=^ah7+_Y*y~gpryM(Z>EK^@*!$<9Q+N^
z=RxoHjc&Kg?{nSsIaF&I#ispsvSh@@ud1;#KN#h;PS`aQFQes3Ia5XLy(QnS-&F_9
z%cNo^GXG*yNVfE1i^*kO=kv=CDw*dO?_FuT(({b<s}{TG8DMpyv*zlfix&BJzXT%^
zlCG*j_1Qh}T18`*^_sS{8pUp@Sbvd4BwekS7YKTKZct4*jQ&kFS*18sbwB#$`f;(l
zg3IU8M{7l-y;MjxYp9Qq&LBHcx9oB`XXg1!PQ`bz=?=57TBT)jGgnz}#qG=Svt^xS
zFrQ-o{HXf@@a6$3*NbmU*#wYIVW%&bZJkK3`RZ)5^R(0^-3@wX-#`d&M|oN&jL!e}
z?QaK#RhOn4blqnH-P1Jd?&}3!!#_WIkNc<<{sMMJ&K{ik<6Pws>1T!TR(p?vj$gOk
zV*wphYUq^EK_ej8H+P>O;07Tp&+ou3kQTmgveX}ndOdzYzaky2F3>H|7iKzu%WIW+
zB42oj&1@?7u`VD=0PD`mKl;J!05^#Ib1M@B<Zst46ks2SwjJYf8StvtkG+SwcT`_T
zacajYJ@fs&pJ27yJbWa()DGQ55=O0<Zy-e~VoXK%ntS=^+xtyT4t1b?$MD=U$rX3t
zI!c-qA%%oVe?mXIuBAExD*|RU_F#Q9l5zB(=4ygZHR}8-VJj?Ogf&X@eqY`rP&fYC
zOBDPLg#!NgNj(5-Ad16o-SYi<u=m-51E5(0t^&)-yS-7~!3#~NWj>w+U$=7j144w-
zqvO?t-j-jH-h$Y)e7zR5`}tblZ{KUUa{P46*u}-g$?A7&&o}}{)mVRgp6dO9BzJD{
z=oG03w%a0#a1r-@sA3Zoy<6>NzLslMc}%4Rs`>2NW??~8K?Wz)cNHk$98JU=_%MZ2
zhwg0hFCovp+}PyAOX<Q@ly0eg;0#1*FM|{If*b>-K-WV*8nGNYW%?DjL(iw)5PZtK
zm)J{#;pO||=&!E}Q{{9;C2#)IO(r@61uy}mCT~BR^JWPHm(Jp^=jH(iq$VQUt>gps
z@Pb(f`$JcYyFY|m%-Aa^zOTo1qGMrztY=p=*`7+)43Kl!QZ?xctOh7d8E3E|lkRb|
z520{a0d<S4`D6zO9?o+RWJMe9KVe|<0iW|-lQR56_Eo1g>@)oav|1DkIL<YP^O%za
zvsY(xRejj1EzQ~HIQcp84jkB#;6=By5jVU^v!~~wH9<4!sf9`n)leY#jJ6&bV)Vk%
zw-4nDlp;eT>2SoB2l!eO7>-D0_4wUmp)tqI<`?QlX&39iq(LmBw9DK_A<)PzFh_3(
zuw61e9Gb>|^ArOZ_)BXn2BN=1SSuMc=b^>?#_SH=$!-utHKHNKTL!eVc$Ek^_t;%v
zw*R|@kJ29qzTB`S5DK(Kxd~fFdIe9h_pQ7HE3tcRh`29Z*V>VC2Y<AP+SFABEE{|x
zTBU-fj}N(*``J|kXo|&cNih^0=)Y4L@Mw8lEk--ZOafhIy@@#FhKJIwwB`wB$Y0TA
z!=Km&*0GWT1CdlwrIX+uMh$-haFEBpurvnI*B0b7&jrxIOfI(MFUS5(>x3njaqm_}
z+`M84g1sJrumCgU8~kcrD?e?y(b=`4{f(*j$HRAq58%p5bD<=jV;*Y|?V-XF>>8Y&
zzL-p@nL%a>xDyd<%6kE>0!#w&DPlA*z=1s0GtlTPTvx(^`=7}+8p8Y%fri@lMdhc5
z4~}GBUJExV)L;|fsiXf_$6c4V%4}DU01eor_%e!byvri2g!f=5pV+cfFm+Z|exKcw
z9eCcQ0$uZoG|TYJKSs7vS~H_Odt?dJy~vd<xy3O0_`9w)qrvPmz+CQSxxxGiGmn3V
z>62<Gt#o$oy5tvzt10#~XN?5k43uu+^rIV)#&$yYQS_8N;2H{975D}J6_gmTX%t)&
z_!>%+nyfpTpc3v(mUwyMvE9GQ!ZL||sBTHfqqNEN@~ZL!Uf&43<hjOr{AoR<`&2yw
zvWWR1CxFp2`F5_J6`4odyByzA1r(gO&##_ooSOgD(-+9LF_(#dfeXCp!AHxIFPTi;
z(z)wRG(sH=a}4D#qB~FBs6aJ-E90JB>BI&f#kq~K4*=Da7CaM)#6|(ozeAG6;7&_q
zSLsN6)JJRY2j`z$p_#TgvKeVKNqGJba)#xq#=lzTmNR>Uw9dbQ<^jK=3<{A*Fud!q
z;nz<#nuGs_t+9R~lm))#Nh5b}*R2Pg^y7{-pLwBPoP8{tLT#b?v4wrlCj&3#&H)0i
z23c>Iw94rGadFO^3pd6+rl(1LmA+7zu~7xM2*l2{%XF0?ku`?@Ci135T=u7~ZGub$
z&*C{))-MV8x{cHcRy+EvzvUZUO&oK99kOxCGgQYugRN@G4r;u8PsA~*h>nseyfp6)
zFCCkA(DDztGX<Evd51veHsV&yf;;O_14{}`kGt=BmcF5)51AK&`XJpH%h(vt!2$(_
zY&OdV$Kb$-YKDcCRSM)jW7NluSp9tT=RFpB$g^B-=M)>84>JS>Z{ay$SO<r}0-ybj
zJS*0N;c>z0GmmtP(@pa7*OjJ{x_^Q`gPV<!v(FfXc*CVr+N|?<NM7Iq3qBA%j^LG)
zhf-i|@h?L3BOfo`pp+LRR;HT73LWjjjQRTqJf&a2`Vti<1%?nvTPO)pK}DXa*nDBk
zsu?yA?dW`;MlGAl78{(w_E#jGFXRHRlQZ1?<}rgtab-Q)qwgGvHtMlP{u%Yq%j*8#
z+1c)8`?<1pwN_UTcv@!=95!Qcx@XsIy|UHs`J&lvS7Z{T?GtiGG$Nen8(1b2k$JC%
zm^V}!1Sh0-t9fI5E(pRowoa}BX}x(=R-V#Udj-Z1ye(3fLe-4zMS@YNb^_Qw3HEnd
zwy*&=Md0dB6E9*Jm;%Yf5}2A(3JYcMPr_wGz-2x4(nCxWY^czY%h)7oi;S3q^3&2c
z_fe?CUT=VQ&TlTOnL8AuCY?wpQa#2#jCJiOC`E&!YaZG4i@q&om>b*XsUCc)^P33P
z8h!};V+Tv6EEOX_tdOp1%nE@e%sk&ipb)U?#I;Q&wNuHGzoa(#o7<^5gBwd<t-K-d
z_DPcbq6R__jh!8bsLsjA6W39AUS*#f^dWA84#<ioXdV@c!JX9uJlOm0)=r=dll+(N
z`CUG6SwfYU>4aKw?b#S0iP^9q>VC-GeXbEnOm<X1`V{TQ<z@q@EZiLk)=a?-)!+r=
zZ|2{Wh&@UXNgSy7H2NO%01HrQj52<<q0rx8pn%n{MKetZ`f)epP%`JOfaf%y7zC<k
z|2)9$qtEV&UIqqnHbJf#`~5g?6jMa%pk)QfP$D7mm9wNks;4z;v}>$!^}B$ut38KW
zfbjkYfC<yR*lCO@y|pl|2Wm`ns}exLe{nrH)Iju`XX@|bH&;r`R+&|uU07?3)8*#V
zZ%ziindd@>fiM?MWg^#x3u3^KF1E0`cA-{}fP?8WhqPK1_0k*(K715}pIVigODVy#
zHx)9fe9I^?*hb|jI^6p}zL;|<3b5vj5j2^a&OIp&3Hic&xDp?(mxh>EXWgM!{sXc!
z#>k~ZZpA=>VMdugbAALVUz-APg)7rXvK7S1h^F@GPwW*cIFI|bC8K{NB)mGthZ>9I
znRHeNR`8C5sS%DN_5D0p7JL8afV64>ZDR8TlnkEwLm2>0kI(lHI9nsiQc{WU5`tK^
z)wyVM%|n6vk4e#d32k>;PX)u$`n?a(5KO%HB?yTkJ%&jkJ_oSl@z7{h>6&S4hb|6r
zD7>=)KYVW^q<iV1XAp1vC1EXGd(eLE`Qa6c5BGZ_ecI5wN95B6S)vDP3?T%nn>p+A
z0qRK|nju+-S>IH(y4VR$vMC%^Sa%yN@C-A}*mc|Bs&E?<7u5rgILXd%5x;9fmrc|b
z!&-MGZt315rUnDtgnOKL5O_f3c{7&6z$0$>o~iw_BNX4YHN{+>Ard}&X`kO7J|6wu
z7px84<Tp_ulW+=>gB*&?>z~veouCK*DDMHp;v?hh$!@`GEWeMhNm}HDbCFRBplDH5
zy;A!|d%>ya7S}H7!aq1CxsKl<6#MY0tB<|Q6ZH(y@SqrK8RV8{ej2cyNYisn02_Pv
zaI<m=N23hkzH5{^kV*i}kwGhLyj~BF7+&4^+)~x<f2#On5WXW1C+Ne2$-E)wWry|~
zc3}PKVplo!vYEJ*K0a^fp9-y&zf{H#0Fe%fHVzcHWJuAC_WsaoG)nBwITyl0n~|+x
zu%AhI?Qzyu3)hZgbb)&_ID^n7wkleK5@MxbJpI+d0Kf*H9cI^M>S|3(<ahWMk8u#x
z;JeT-pNr2L%(J7evYBPiUx`Pd3MflZu~@#WN~_0mpzzEQ2OYZxh^SF$f*jOLb>f)u
ze^x*1xE2-osbS-VR&8dc48yhE4}36Lb#!TDrbrHKx}0fN*njoI-EgdIMCSIW8mvLq
z0;(b(v14(nTx`^sfix~XiBCXrsVQ>E69fLEK%-l#{Z>K|Kn-8~@0`a*FIPVvC0XbV
zle4ZF=BO7fd_j$vD^6^qRBi=VDeL^$_GU53I+vi{?IiuTl)SOUuFWzc8Gn2T_{J7v
ziyUTZC<&<2k7)+jh`Z<tn1Z_IVc}2m{6t#6Mj#_!N#47c?oztb$ZNRL>L27gup$G;
zp(9=~2>~u!{)4A9i2joDwrYt!qhiZ6LwL>vwt@&3A8G|_LNyDBm|SsDop`mhZYXEZ
z%@bC(Yj@3#2Q?s(=Q(9y!z%|Z@S!KoEq3H}77BMEso_ed1l&vdij(*>v;t&I$9{|X
zretQbc)1~t{<l!NWKcA^!{ho4Z?EH(Ac+IPO>v;f_`IHf2>qu4w2DGfxa2Jn0E>cX
zBUUF-4yQl1YJ+0YYV0-ous|B>ctMFJIo*L=E{Y11b*<Gwpx?)pc@%H5qq3KOa?N9>
zssm16QNK+fJwC&G>f|cc=0;X@v5vM(r^xw&gCf4l;{_sQ62p{Z-5FZ<ctV$CFX2hy
z;?Z<Js{@8HkM(8)TLj&eL1Sd86hcIJ|B#Ga%m*WV44@-7(P%*87prR4!C(sD$KDTV
z^3HW+hD#hLj^F1Onai%Smi$6i3kn&%Z>@zCag4(fAkfxtcy6P_-c2k11eFg-o9Ly$
zj~6m?KD5ASa+23L&qgB~NmHuMrK9!_VeMXU?+yD4N(cjA&<mknd%VP|YF-d%##Q~9
z2O&zHs%te;Dt|9fe7({dP`|*p+EvQBZaN5=)qT8btM_!9$==4q+2;E7gQwM+P?{=9
z`;lmo^$?Ov*y>7)!4zk4q?nEP8aIw`p3u7G=+YQ$TH8##x^@;^9vDM!P^z5@JV(a1
z_=6nsmX7nM*HZ(@-jz3I{b={@miP$O&#wx*8zFCy_y%jWR(4wp=Fp0<q3!hCiaG~J
z(|+cZEwZW6fzlbaSL<%D{rXUis2?-6ma`z;g77%4J~tBGlJCDL{sb)D$aPB>x1EXB
z-*m#Z<+-jrQ12SIaQQ#x@CoWTwG}YC{0|#%%k+lfEg%7U7{4K|U>AhRV@L~7I01EL
z;`OBm!<PrTD0~5~8=bsMHLrg)Ih2L??2EnvSqjf>3zzL2ttChz!*WfoxWZxkvWJO;
zNv0IrqpCqfqhX51;Yn>9jeBOf4vSp=N=yHvlGEhXnAwQdY5urGhR{Dj<bD^VpSLWP
zclL3CC+!(p3O7Cq@#Ca2iY51%c~#L@zvHb`&01g0LF=5nV|L}mKDv~T!$3NA3lkiO
zxhR3>g5{LDBRHtjE=A)xVaSAY%$|%rDm{M<Sr!50sp!|sos9d<;0Sfl6`3b&Efnn^
zrxmNG@hWAZO_mM1x9kQHugplB;$6wb0Z?+CI%B(JU>mk}V{kfiyRGI~lv^eh1k65h
zy-U8}_>$z*#OqSx|DO68nqpiFI*`jObQtwqkS6A-8hOnB?7051z{(Ci9qPas%l=1J
zz_s!rkS(DXCc@F7s7&S`B34v`Fuq$p5HFH|Mig(Cxw2g)$)Yr@hmscXNvxKeE$2{d
z8$l%oA!PCsLKL;z7?UhRXmj9P_l8hZtPVs{9xs!UGJ2N6a_iD9Pk^XV4-1DJD|>}y
zw@TVZ;^UZZa8qY8T5xIM5CFsk>Wn+bts4V*n3>WwlE}gj$c)n*D6`0}M7mKz*|~b!
zIwMw&WMV{pJV>$G;3(P4?{#E*_WV3dPPOPEy+ScDmh%HKT0h2U>Y8IVc_bfBu~dIu
z-nqva4tvv_EzGej_oJWNI4K#ZhJ(E^zU7pDz^^Yg3wbK+yor6OzU&ap5qn9~qT_$C
z#dMNVTf#OHX(vUIz!sQKd=u70+hhsLR6aDMpr*<?{8IY2oqchdbC!*$^$8b?KO7yQ
zf<-jzTAJ9XNG8sdlPX{Cuqm#YEHZ^%Ezbo+L;Ahpk;g0>eT~C_)4F+0UBT6liZ8c5
zy{h~LK{s09XGfOQySBzH<oz63jiwLjcAb>k-pjNZb>H<b5Rl}EOt8j!k%CqraWF=c
z*!jqZ=Ywvr=Aa^5k0W88i<S<o^vMSGU^M*75H*CZ3qhMdyLT<UltPrD>smo4ji9Ff
zK?>!T6g^d57)99VO5hv1C;2x%SG*r1JR!WeQH7}wmOF7-a}KZE*^-=hDn|P!ZB$~l
z6UWo0PjR7C*TRUm0f)cdHIP?&Z?>%f!D4kUh-e5$#TQnawxyf#mAJREnelo#P!gEC
zY%3-MMIPOVYYLESIfQ*n1c2l7fB=iJ*=u1P%Rm|IJZi(usGxeEcA&H7cdE-OO7Cx)
zmSuXp(`4CIA#PNWYidzGaHM-6RZ3lXF*d1^)%$UYxm0eDLQH<&;GRDtSf#)`0wW1+
ztF(>N5&SM)+s?rBfeq^B393^BxQ6HbA!cTvrj+>IjwgflB*9D7?m!HXTfO$6wwm(1
zXxn2bax3|OJ0Ch)kyMtp*Ws(l@)NP`Jny~{c22IP&afU<uViU6)+<yA3xatK3ps=)
z+B8#Ca$(OnOMhRT5oq*|#<tk+NQnx$n^28oGEp>R+V-+ydgjh^k<(RNv15VH9=LU&
zqA|m*N2=RZRuk3YrD00hB1*E*$-Y_;O+=_4ZYOxp@a*p$?axVntf`(39V#!Kg;%WC
zb+zsC?BHYX%SUdf02<bLs5RSooQyr8oMf9yE_weJ5{Jv-B2~ugH*kdHsBgL8bryFo
zIq@D%F&3}}AMgn9538395iq6PtMyUk6jWnxwpUR+Kt3%=l9FYEOu4EGReJ)Ofgm`*
zlR^buU2IqQhLGL$?!g~~cZam$qm?3dy|C7n?^O;tFeEVLQj^Au5e&b#$P2*ajRb1H
zQmL-{X?Hoq2}p|1tOS&JDvuL*MD<|~xDE)w_ApK_kk^cXv_jp4G1Zo}_CX9B%7#26
z`hs{f?j$Et#ix9u9ij=J@xdZGN-&WWBWQ?|)|b!Du5K!aAE`QrWpPQpaNXM@IEO7r
zKi0|!`2lf)C<o*X1YJf|DQH&?-6I$lbHdb`6^1Ta73J&T_%lYuZxq}ukzBmCF2ye;
z0UMGZ`>baSTC>J^`u=p)j2;g{4vQ~pObkk%=#eAE%miIBC7&ZtI44eq4iw&ZI6GeN
zD8AOuXN~>?k_C=xvb|pWu+97p;gFbT_{K7hvX>E2&EnEPVx+&)30{~#%#u1TGuiNb
zu$hkGYOtL3+LEn*zPHAZGG{E+6ig5K#D)k0N2YkzCH#Kx551Vgi9WwJ+3?ubKX3W=
zet-V_K7LGhvf=G|Bi#2<XAeJJ_NMs4F7@|Yi!fOShJ7PDrA^iA&eaFDxX;(b*s^PV
zsW7G<1uMuyr>JRrMeHMXaj1IT&yhi-fPV7@B68>tWil{cI)LcOV~)jSx&^t0lWOD#
zO4E~Y>pom0-VB<!dG7B(;5p|_a0Bc;F0%F-J@Z&w3PKV-ORiiq4$g~vBTbx#?Lsvm
zb3n2OYmC}8Lf9U50&~B!;wWpmuBNJ5bWq{Ea3~^aOqsHgpi<i-M&ri1RxZ7e()n)u
zyLWQ4&}yVaSPsPdU&D6JlmeFqqD8CE6_!z=wYp4Q&vlLXZD81!2JKT361hEubBPjx
zx|UXKu*xnyHW1F(Yf&uFQ81`;_C!V8Wn&}ih`Uq_m{&ZDd%va&Xanjkxo)RX`9>mW
z=Y~?rPX8L(3qNi<mj=Hlh?UzPo#<sxOWsk{$`HLw(R^)0angt<LL#lFVhYS)sk6~c
z8N}w4>qTF}vORzwQHyFpY-}`Kn<-gz!I#^xSagh75!V!g<~;_@(29{kg<4h1;~$7L
zo??_dLx>yOCZP!p9KFOn*fmg_yp-?}$jphQvR}q)r{~}j%xJoM%|y;SbxNy%uklYA
zCkSoCpx?T1IA`RrG=n8xEm2_R@3Zb`am-#K;m-_ZQT04pmC_=$mFDEKBd+#$QOU^>
zT|<%)o}0>fgtA~Y(^j8*U{+absb4}N<vcb47J9x({r-H1(WSr*Il9R32{2vZvfz^C
zIWHDcE0|jkmazueU_Bs}dKzwH*G?Mze2G^u-6>Re``EE^-4Lf12B(j!g<=Y02cw)X
zJ*=Z|^%pV3)S&xaiqDHx4_Y1+%$dHF+tpu+5S%+&C|TV=(hcC7*tS2l#5Z>jKGPgf
ztyYdX5X)obV(llLa;>5n2`<x+&*h1W71BK}cG8LgNtsDj;|II*)&GS~`2ZQJH*ZnF
zryuE>)%`JD+bQ3n7+4K%bYDQRq;3*N(-^+5*J|Old7|mu|EsXvmH21o9LknpRCRX6
z@xt2CGMg%tT(=)u^WKUD+wJf4S$r9Y8SHvoi<0_^i0w_umZ-~{Nva=5Lgu`Mk<tq4
zZ1d8!uVZ2xmbAsfb76ixCaH^?qT=b+ri|1Px5Co^Q7orp-Y&`e%vM!(qvi*h%=!li
zx2a>_DiG0bZ^0(E!*(1?HX}S%BPj-ZT2WpluLo?ig*Dmq;7Syble$!w<t)}kO2#jd
z_8iU!ZikyQWd?Jlo7b`&yVw&5*Y+XlI;^Gb*81_8xv%6Z2uZsOk3u`mzf3Y0=`|Ak
z(vy3&RL{r}dpVOj5@SBq@X!gYy+mB;sp@_AF6M4CO@~XVugFDC2N5|NeA!BLp_ph@
znnkjsfUNWs=4l!>Tghd3xe40H^$~OVF!qVGQxPvH>u8wTz0CK>?h7VkYY3TX<6A-j
zh+*}WHMR04S2gyyLQ3QYZ6^0I{`oG8Hq9sntYb}4y8g7|-~u4|k!`_FOS<x^PC0DT
z7%%!j-bbIi9yXec&c2Cz2uKe-e!pz3<mh(qovW;RY}iU{XzYFI&D+0;T=mC7{j_57
zkBv1m6(YGN6>DU9+voWzXkIZ9>(WriKk-iKv~UYc^kq%jufzvQ(5r}97hcgob{Z6V
zebQbTNq@(UN?@Y&r!=kCLT+7p`w=Ox`h|%Y>A&-QhBBB!OkVWRPv2qD`)7<{&o8jj
zTju9^K^&#E_#PDL+V7OzZ<l>wRX6I2|2>4i&lopaVJUbsmSBgfm(A=J(g%gHe*mV;
z&UQc>&}2ZfNa)2tBIZK6Jb~0eA?<u|Q?|EeiVJ4@d{M2p>*@CV#n}=0g&c8HXpDWa
zouf!x4;V-j!g(&5jw$Itc9fnr&?NnGOk71v?@jXgk!%_Jfo&brT|_mo+@0c}4Z$5Z
zkVkNPGPho|zU^S0f1b5C-ZP_|cCO3hyj>euV8MJ@Ms(_CU1!@i(piJh3y~?t(!oR}
zWF~|0Nkw}lsW@g<j}V~Qj@FvD9gfoC?Yt0l_g&I2UQFt}4jCoa$>3CtW$l<+oR&G|
zps8_9ITuIsjVMRpLJRb8?wAr3r^}slvS^DA9nc2Td_<B%Jv2Aoh`?}uXd0Yez4gJ^
zn}OCq7$oKBUd$G3ggI?5Ds9c5>h|!hP@p%uRwQz5`gN+K!qsq2W&`%Ic;7-1%K|H{
zeF*I6kl)~zix3cqR??+#EN9;Y^oIp%D87h`@k~0l4Oak5`hYyyIP8uBTn#wuId30o
zYHY{2!N9?Tg(+uYDl0%b*k@^bmS`%S+i3I~Hn7(L5RMME<|9@nbYYt=Ft$z(4AccB
z0i{fc;iIL456Ohxs=^)^B>RajgmPWjp=OB`Z)HlfW+59VnM&P9H!4?pzb7)}UD8Lw
zQ=pS@D|j3dGIJXJwJFfe7>M5@tyNjD-MSqZA8glt`2(lo#{QjVMsc8@#t0PRViZF=
zn7lfDsgW;2ot{>>B_UXfbH#Y&_5PMU*)=l|&sa*~hL*PHv~Q-txDjgb&_7!W)2J1w
z?Je^(0OF&uuUclvUh;&Q|4t$Jv_cJoU4vs#0cE<P4c3?vtI5HV<~`0pg*MU{;-rf%
z=!eW*_<@Q<kwPZna(J7uAbPkbzhF^5Dw+#Dza3rp<v@mzzMhe>;e}!q=DU@bI=Qzq
zQBQ0JO`Gk7KOS;#H?59buJP=2WAruiqz`|8322;jYd`!bvYf{ylxKtn%RSd5dWBgl
zEmeeM`mGJUd;;!=ZQzo__;k2H&ctLpM5QFz$u9(FW=uYw?w!>L?i+7f6R!jzbUc^j
zp6KMgxzGPPp%g?sa!kHYAEEtft;4}|EST19c{ZvM@@4|&tDQlQD)-tp<wcWbQGXXd
zM&;P!fr=LTIdv8>3E*{)9KvKQnPX)+5VC8qz7&dIAT~o(3fHUUZ4gcJyA!}Qx*<{T
zJ+x?Qpv`(s!6K}0fO(KU3ho^kTyi!9)Ki@UG7~cWB%*-$6b|bvMcsV_a+4>==P4#5
z!#!@tQ|>Rtn|#UaSn2SUzhVG-mOud<gL%JCnU=HH%(#A*Lu?vax4Eol-`s`8U3R#q
zw49JaEt-?vDj%>N8(mZc3dB-tR!(8N0AnRmP^yo4RJfw}_HM4*zn}mq0O1Mr3;lqh
z7p5d;dv=nSX@w)ezF7VJohD|G9+9YCUS*h%L%*bN@og$iqZ)5y%d-2iiOMlvjb@j9
zP&i%=L8TT0suTFspl{1U(74IyaU7$a%xd{q;&q@;T~LUR_za=d`l4pgUlsdjK~<^%
zg*Dn5hm{>L(xjdhnq-Q+*{Sn;Wft@an6Xe)T;%Z!kEqzjb3=G2VUfe#)&x}_I2Ggp
z*U#i2(C}(EbxfiDyF&Kb^6YXg#|$RwT->^ng9T#E&8h68%S~QkklQj$1WUE3gq!*W
zy1105D&yZ@<c%odQt3OH-miz(X<5o4SLG858ylD3SlCnPxjih)T-tjjXj4SCxk2J)
zzD+V#RKG340sInISo6oV@&3{~^p*)!vAzZfL|CNHhsjkFtpN{bEZXtH0t1Zq9z16y
z>dl9&IB~`XdjD#th9V48lZ>*c5vPnJZ(9P2`z}iQyp^qelHCA`IT*0uM8!Ma8*c)+
zbM$BKB+`-{0Jz@$?jm(X1zLDE_)LoPy9`We<(HzHCzRcDo7u!N26j6X*A8%(ccb3&
zbJ&ve2o|)7xuG<gk63g87fHSb+grn7AKhID)Kz64=vv>PR)B8HEowmJ%9xKtx?EMq
z{)X`Oa-4yjk>tbjc0w^5LW$E33(f-vx6DoI>N=E>44DN9%EKfex0EdvC!>EkBW&bl
zf(=sPi77zcs6}bARx%iIoTNps_i&v=OS!h@B>4OA)N{||@^Nwlz?NFZs3g^?R{)?O
z9j<J3tI=5iD-c+L^3?}6&yeIrcSA%UXILTL!;?tgsU@iRnk*Z_dF@$`JyF}^hIs3t
z_K?B?ZVi%lYlqgH9uH*}jtftAvuY31PUDtHGu|{z?`}n9T^Zc)8qCa#gNHY2<q@*p
zUd!K9D1d|1T|b(~T<1x}(J2E!zTS}vBwv<L_;mIT8E?m(Xz6qnxH0!~ZZLBDuM*pp
ztBRm+QwCblQ=eM1bm9Hcg)A1THyzJn6eMq;&fvvX$PA8!_|~DJ)Cpv27tNhW89n=C
zM3+E^O;G??`otML5rHE>@0QWOIj&|^lflEen8AauKDRR=MXq<Iw$RZ}3NuTY#ZZlt
z6D-#zu%Xoih5OOwpW>w%;$qS1+t|9#yu7cb*Y7x{hteVgVKh*zeeMU(V>%-_AYr<w
zHcyUM77@ss*--L&40(vs;}qA0%DtcJ?}Emd3Po`xzy_+P{&NQJleB*1{Zl$k)Sr<T
z1q(bZ#+q-*d?1lfWKOsTmr1wvPPAL*rlGMC!gHc6vV|gz+!PXKYR3yWS@!12I&MHA
z5{6ukxbn*5EWj3n@ofG~VJ8fNkcnF6EU0OUmF%pFc<su9Y{~J0t_qde`~HYL>2c#R
zzulIbwS@c)l4KMo-0qgk6}|C)f}~AYNQ3Sbup7_p#H{=I`!FU<nHsAKBR|qt4TlFa
z>9RqGKYwJb^|+Xa&W1yBJfi4Y?8AcHU1nmok~@;A-g?9}Zb+6kk}SSYahZ09CCd0V
zNgr0pBEt%WvZ2MC%17|hgX3ahq7mW73Um@;*!?3=&d6hR<bb<qP0h#77R#d*O=5Vt
z?(mkh9eno@#KM7tI|<qsOV;#Eop$RLc>Y|y<LFrm=nc(<O}zw6iM_x8?I4>t+b)|c
zr|^%r;<^jMwO&8!<pi{?YK~l81Q2jS;QGaQ+hU%9WD=XI-iz?^-c*kqBU5FrO$-db
zMJ!kBYdS!N!wf|ZrJLuZX1|$4R(ZkB=PC3NHFf;+qa?0K@})448jxJYsy5j&VygtN
z`(ZK9&pqD{Z!J-`vfPO~uE!<Aa6K6G%;-iKE&8sUd+1n~$Gr-eUPHz*2|-+ar8&AS
zDn`=$3*QtXR(r1zRkIW6JvojXU2b}}kTQ1ss1>$0iuYHZqDQ|J7RA`Sf~Omr;x6DY
zNgeY)8NqNqO8u(LOHu9HRd*Jwt<U+xN5Lks9~mL^iO2aJ?lJKG@ose8=$RiL>82pn
zaCC0u?~CPxm$b7l1t$ooIx<$p#=C1ejvB~~!1nh${OS8ZA4T0xEBY2wIV87sw&T18
zDTm^MTEZT6IFAv`dsg9bby*OaBP<!4a_%PX%*M<zwzulvK;lSc5zT9XB}o|w^pIbw
z4lZ@(w^Wu-#J(u;(w)C^zTw%hx1Y=CuE}#r(X5B~?7QOktVN5uDY#`MQ1i;%C0j3U
zrHIG1wV>X-UlnIgPXUhIE0J9zp7;W>z4CTZ*a~zw{}}qpau8;{KKU1_H%!^B#Pjv;
z9)AGus4pj|2V#AbB4~(g4EXMCj~om{2u^w8P3p`~7>osn@vOpBM`UY2f4zDnL#N&1
z3k9fek9OD_ho=k$yVHqz1Jf!sJ-y%V1()1y=O~46<M_LeYo_b=k>rLTDS3km(mD{)
zH!-qceEeP>MjOG2Kg2uY>bXnq$ja74mz~L!K`Va$P8b_9by(R0J?j}F@K$owc=G=H
zS>Us2pNWzOT)|@%nQM5n`Nk`pfMjDSU|PV*FY#L*CV~+P7BT@Y3mfiyA94GWNxyJ(
zn545(=2`;M;Rai0+);pRUA;cJMVI1%ynPt*VtKcv!8Qv^ZOtf~9FvQsdQlX9#2u<w
zMoqmN3C)!xEn_Ae7@s);nHFa{PjZfEhg~gb=_|U3UM$~nfcv0G&QLG3<ay5t0B4&D
zPDVm~E{IL{OGr3qyg(eSY7EqRAAaA*-g$dvT3C}{$*?9Yxj0Yy;vmmfk@5XDxJe(c
zxWv?kp>FOpv2IQmn47s<lNi*(8X=Oh6}dox_LseMy!4kH#WrQWsCFu~k?$at1Z)hp
z+`Ko5WYX?ip@h$n8{pSp$i4|r@O7%RDHhC!;Xs{M^rb@jbGxq6@zDLBO0-1@1X4=^
zJ|SzIhEmcp>&xKu9raaaU7-ekZm_WF+wE_om`?%f)-F!O2k*uH;g@j_{WCLta^Mb$
z?3$LNgXmsiL{JXaIxw`EoRT2=@)V)mPU5O%?I8V4Vm1(t=(}5m)=Q`}BhHBP!$lwm
z3iIiFy1m~N#5DAVTiW6^L4MTriYzy{E9dk!#fNZnzEC@i^~IT!a3M*3lVvBv2T@s`
zd{U)3@5BS}5OeiAaM6QF4Bx0!O1qm4)0NU_-r6BID~{729)9#9UczB$y3fbCZ*F{B
zPs2eleFxk$+ylxgvfYzUan#|3Mo<z6>`eZeNle)D&6@5w!?&e{B^s=91-)B#8F<*;
zxaJ)FRDAgPY95C$Wywc%!f)B0bf2)@EEKW(ki-UatG`hUAIfY?Qxg!u8qAn_3xkz1
zBNSy@o{De*5Q|N$3(GdUK(7asXc?yklSI#3GSafEx?Y+5xJJX|?1tMm^T+5`E9~Hu
zYSunvdH0e24MGuUyaLuV6lxx5ffmr>#Z-iEy+MvZeAh~FdaNM=G~=-psC7j%$Jwvy
zJ3{-soC;cGQeJY|96*${s(3@;WLTrqWP}kh;+(dXWgwC%YiW#7TqEl{Ut_>;66GMO
zO1TXXk?Eo#(qcCh27cL?xt=#fYG$d}M1?;5;HTq$8fc*`=*%mioStRKkh-NGw_}eW
zxPXJ0g&3uRF6e(LyV&qjKkUfDglXZSqRuCaHI>cP<5>w>>%3$CQpR$UDvh^#bPjv+
zW826>mt>yyyV667FPvs!AvR>2){eR0t+7CP!iMA#`dCGPYgdBHN0JMiVs<ww{;WlV
zR(;`n8TrP2?|tDDn4#GwqPC8KN4*#+yRp@dsgwY-@@5bSRmThiipgZPm4Q~Zhs8t0
z1vJQJMri@lcBfEb?xtzAfx9jX+-JE%?nhv0In9W-0C+mVLs4@n4FxIG30T#&^c*RR
zYfwZeB~M!?&2P@tHw6u5xNJWv6(8MQcSUyH*^4@QdT+1f#?Z%MhhF5Xu@XHNbr;49
zrzU?&q+?}SeSg^{eKd^IN85){4{*w}-JpYxvR$|35Nf+EM;HOZzYf`MyB1j7lQtI0
zv&p)`d;12#=vc1;iH(trVApVcNy*7XVi|JL?pJzMej+u9#Gx=(xqojv(q<)@DJz~N
zw>fDu%bhtcEE-6ii~Qxrqna6W|M0rTE5t1%PcI88LmJuC@4C+U0GD^K#&C9l{iFfK
zNnejL&`U&S4W*x1Kjv0VxWeZR+1aP<{n+jOu=}4dhWPB`1RV_kfd9jP4QMz1Kd1oN
ze++0lIU87+nA=$!n>hYwpxp8Q5CbGHqZY~PQVE-^@Y|orRT{!r)7bc2so9bq`x8k{
zK;hOFd;feKa7;DIvhh&HXjZvcb&j=NV12RVkp*f@K>eb<H><T+UxzXZ-0XC|g=mG8
z4RVUDqRq;QFLIH>&v!=mcM;k~O-SG(aG%X+l134F?k$R`4G0%IuGfJN$Z#I1zRstY
zZm|6lGBZ3GyDYw*=P1)(lovNwB<r1YYDbb(Sai{{q?nu8I9>UI@l;d$Ov$>qI(GK4
z#|Pxib0*Fm_;_p&TJ~!0YJYAe)cR3StgnhvbRp@q4t9&pg((6q&NrCm$3{mo5>cKp
z8z_-I)MSP?PvNwnr{#N?MpQ*FgX`<<Z>9SDtT)u<#2^*R&2ik_1jiF)&7*lBXtMRC
zGL!}Nl(*YSOfpDqE`Df}=1T_>t1+6f47gf6u)I(t`9^=NWsFD)=!&lA)dW6Nu8@S7
zu4WZ6*um8A(DZ{$dl{7h4;R*;>t<>8k{1jB+hIaPDeuh=!rA&C6aQdd9<M46Tel{l
z);ZF{DoXsiuuLO0Sl2lWA3{k1tcZeqro{v-e}37=a5ADvuuu*aH(A}8g{DD<@wmyW
zm7pr}b%aVn2y*ZZ{G2xvTyi*CECyC+_woRLv63c60w@ZJHO0+1M57i6WW<Q7C6JOu
z9b=zc)HUAIem88lB9-!t5b!>s-nxIqQVQtzp{xlU(BPn4_4S58gPzLBxFXz>GXXs-
zQes#^MIrX(rJrp=>n^isCxf$(lY}=V98XJl4;*m#gX7d&!#Cqmr!wWFysZugnuicl
zmkQR(Ec;9zF-t}S)yFfjQF20lw4nQ&MM8|3ZBt*7c)5Xm@z01~8<L8pNAATf+(5@4
zG2w`bfY{aB96;_wtp6Yy>z)9Zg5i4>%Vl3~Y>PtpF}L^%Q|lFt&LF&R`j*$q>_~Tc
z5nMxsn#TFnJNk3QQ%X^`;H)MZup7e_)e?E{bjN0fCfFGzD<wQ^+dI}tB~Pboh<PyO
zvoTCRUk-#3uc%n-IMm^%qGMFL6B+<T0861ys*mR+P8?gu7HAI)&N^z}nAoww9H>gI
zifn!lS`NJb)BhEI99cRwIza}mWu)F%Q$T7<9dq+9!$#GSgTlK;XI*}qA<?ik<^KKQ
zGyCef#Y=QeTp0cPv_U>(Dr2mlJDLa)_3ClVdK>Cyds<*7l><$>kvc{siT6qII?RAU
zo!Ci@U(fftgar&BKH_5L$aWXUn=c@9?>$#~Q$-?0BqrBlE@m5HhgLg_Rb+H->}Hdj
z)z62kbO}}+H7xzcO-5f1qzQ|<Rd+_e%#oX6L>>bvI3NuHPBJ+p3j;CWJv}{qoB|Yk
zID}$?6hHK5-KUXTj7ccvAZ}J<yGqIV<^W8|t*pa>6?4N7m#9XZ*U73JteWC>%YePk
zLe2ga+8eK8yK9Y>mfoUC=Je&yYGTvG`t8^p&4X`nqI~!752XGAuOj`5W(s(Q#VPlf
zh3CGj@B9-gJqKmbak;03;d}G`4JKN|wgAfLwiNJ3LVif3Fv3uJ0usJXNAUd69WQUB
z;?j3!nBq^NG0pefi@X>$?;OaivrD<q63mu%XC^Tvwcgm93(B-DBq$dk%k60B>|M_R
z*RkrL6OQV@M4@y*zM6-jgG=GM@L_mYpz-+Dk&=t7&wjrQcI;NQhkfRb0sUS1GRK~=
zX2XZ+pAr&R#{AvR<(ceu7e@**a#yT2g}{~MCybM$DPMOgJ@Mxb_U>{sjGQQ;q(FuU
zWUIdGP7e`sZWlJ#TN#W{T*WW>uF@AI8t-QfRu8*yfNqILx8&@3a3X7x=W;cRo{>Gu
zTrc^Ih!djU1NAY!N~qS<LVf#m$%cCLkjh$Q+950px>_*M#NAy>uVjKkADyFHoNso=
zK+X~=u1g&Zs^D8kE+>2A&HP(3*g6I6H^irTscC6V%YRc+FR<7;au@s0bv5RXQZQ=O
z)Hwpf@QV+vtsA;O_9?gR56seecNd8Q>^yasfXW#f>e7f=?78>z3B)Jn%NXcmvrT`t
z56}0fbN{zY3fjfN0puSQM2PZV8;?`Ve`nPGv;XN|<8ijIv;EIaXX2mtiSZu}_&?Wc
zAE{X4afcI~UP5|s)UeFuz>a5trZAC4GiJ<d`9&rk;um^<_+*S^6k}syM%?im-7B~`
zkKaB)G+8MCxejV~BZJ@7jmhn4J%o4-4sF<`(wdnlXg4-Cw$@X#-|yMTgF>HOnNhRN
znp)eidhE*@oSf+AHD$bSoBMgJ_o6k`>$OxF7Ua(IwVq8@mHNs^rRd+j*5mrEmBYiZ
z{X&_W?7OX&+SoTd??<$|MuPVjA3a>Wv*)l;xI-auzb^0Z_tepR_mD%_%mS~kT~OYy
zxBXQmpJ2X;!}{6{)E!0cpIXDs=FN+x<?oWV+mfDPzL#z1ijS6yzn0XJ?hZ<WS0DN>
zBEN42n3pBE6I|GP%BfEvQN024vaxs@7XXEQ*f*EgLORcHYE0eR$fG@*GSBRLU2Zy?
zyuSXs`|68pgL+}GyN#XYTIk@a;g`N85iHVfPETR2usG7ymW_Onf3n^z0FMw8pn(yg
zPMwFwzdQvyaJkZOYxnL4TX6SI+d$Izy7G2a5qw-pdU|_${l4aiG$M`G?e^#UcNsLw
zrk*rBs_Y`PHxW$X2Gu^@Jjd@K=EBt{ucsr`KtSF=R_0bqFL>@G9n@gz*bm6pSoGru
z^C?SIVfJdP$>m58%GP+D`6F=k0yD+EHQ-bLkG}YRoj9MDGnT(k_P6<#5BYE=96)jy
zzVuq3)dy>35v=gn-Prhr^T_R%{h^_MV|?5|da$XEp2~~QyJ<!&Kj#i;d8u?&=tDU)
zhx3D1SKbCsL}Q?G;n?l_3Wn+DC$4%R0$AVnYX<ey?%Xu8_MBzE?(4Cryv>4&?1cyS
z&lL1iiSBef!10K53@Gl-eKa~_2@iBV`#Q?+##$;rExBqo5aTdltR+9?de1-f_G7-X
zRsgRC81s3Og+vN54y@hH2_Ss|z2;$9VznWn%`d~%aC@yNCmqDxff+a1^Vj+ZmAb26
zRXRy{{U2ScHgr7L@9Kpk=W|?T!pH!3Bg7oRdvPqkR_?EBDg~~-slqXGLssDdkASd4
zBH15K?J+wJ>n}&kkI^m{_fOVhRJaFGjCh=T`<eWYO73-AOdf6b4lUm8HsKowdIrS$
z%t)-svp|yGV)0;AdTW;~R**oz(k=0iVLcvuN>*Wq-`?mp!I5oTc2|ugqMF0LgZz#_
z`t*RQ+f6O9<NP5Q2LLfi)23{mU(}yjYzq?gayM*PzzYXLzRS)w{=sW*E}eR>Bm7z2
zhC3d3cQdr;e`5Bcu`Gn-2F2^_zHQe)_-q3lZUr#+&~29Ijw9vr(gJNxItwr4o?8y+
z^mFR6S$xIJd;lnAcouu}CyTH;ZC1xtUwz)+xYqn5=ro<I-`Cmnx{Ahk_Wy`7hl6mu
z*dyL=I<DeG^AF*H4uq`Q)iSI9PFzd=IcjJVqD1bCgu~Zs6~7it%LzTd@rB4;d8H`0
z<*xAH^4Dv|Kb$<T7L(%@>dl!DmCYoL!>+3d$ZQUV2*L#%Xs~`I#(n<`ch2L6LCV%g
z72NUNZ;h0vI!DIUq$1u&?nyZPD|h`kyo$2Lz%zMwfC8a_>eFe<wO@MIR%paOi22&m
zGU>3@NFl2O%qNCZd~w_P<IlW)6kgh{cpFTFPZ^JUFRr4bO-Jnxn4I%1B2LyOMOidx
z8+n8sFFMJ$p(cVl2tghr9)d&Fu7AfHhGll}7cMDaWD%crjA5+XWHZI<1A(W|*6JXp
zBb!$9_|ZPu6@pyX3ZD+%=>U|{hbxPiR)&4h+YuO3E}GCvD_zNNRc2F^73^lQhf2a2
z;+?r$m6pWs{cjut<n0ZZFQ{2uyB5q4X2v0H4wQL6R~+VDW=W_Ogf4ve;+|@pk!JwF
zBAeUE#J#$v+_DUvgALnpIQW(7Ujety?xlfyv6~cQ5eQ$c{aB?7{)g^<oYU*T&JukB
z&A56>lcfi&Z^8EBEP>PM$Tb;ifl*yml}r0Vsdgx(4JAj2dzpV}=tdx7<SO$rG1e@W
z@2(JJ{I!>=!-mM3bA+wedzL87#+5|2b(2U}*hJ-oC50%_;YRk7>NaAL8FuZR1dW>Z
zev`sZ;BeIWbPWu2Ln3Gy7e)z%h(x9ElWZpA03Tex%*DTnmvdrQNS`^y5<${6220Cg
z`X`~!;m?Z}0G&qYk+T7~TJnIp41c>fk?klqzTMa{ZvA}~$BQBoy!G-x?`{37dF!_2
zP{E^B;I6>t%wSB!nGQS%m{<h3^wIZ}$q01wT|Ags=K)?>zrTrE?Dt=2TOl^av;?zL
zxjDRhi=yq~frs|~jY@+X8Wmvoqu;%|HgG=lB{USt$qb!6RbPSmQPj(_?j6u^WoI={
z89PocmDLol>uGlZ;Yzl*8nnY~s}RsK?;HfYwdGFiTd>aJrs4$^!Kp%@g9<py16J{_
ze2DyOi4H|(Z_kFe#s%z`dq>(?nixpcBv!z`ofJ)Z3DgJPls8Ui`|a_Hs&&&>KwubD
z(ooll56F+G!fz|jz~}QgUGfIq9jxaQ|BA^yuZM5-2y=w|Hyzl{rG35F7#woAud?JS
z8|N?O<C%w9UrY5zP<`>o=<Q3i(dL+>BP`nCziVI`F$pI7N4MkrH?&$PbtGix8=vn#
z!9lR5fgWPkU2cBsMK@t00e&JBsjiI=Tk!!_)+;V+uV`^NvkAP0HTF3c0`Uv8EBOuB
zv9=INS*00ljr3dBXLnOi1Xh<XEQI9zSt4tf1ju7O_FP%JfD*PaS(a^28o1-K3zB7|
z`)Hh1+{!rHceLN1yI<?eIieTwx=Bbm5qEN++rzDT_y*yy9};hWtS4P;K-12G#67#E
z%GuwqWwK0tz9Uta%r<hulM+nM_N|?M;3LqGApc+!1=$kUpR8GEX0K!~<bc<#iV`kd
zk6Q`nw#lN2Y*{L+GxfNV)zq*^uq|Y_XB>5n!@)y0X6U&&PTz2nwa>q7nB1uer^ii|
zV#Swmd7cS5*4I~f{fu)Z#=PU*1nh^sds<>q`&%S3dfY!=NamGeU{{M{?0>l*6_zx3
z#>w@E8}8Tv5n9?8XD`LQt{?XcXc!ZNRfIDinr*Z-WggJws#Rv@>0guGe?Zm~a57Ag
zd||IFzfg@=&8C*jhS8kyvV!lqC;E2rp}`6P25b`-2er|}#l=XFk$OG>X7boQPQ%?}
zSp50o8f#a@M}?fx*s+T4&EekaGorw=NTb9$Ft=~^eiiJKY`))g^fXk1W*Zk*1P}kg
zNdtCoiaifLj2c0b@sw=hs`_!aH~AYskUw0At9u3keDb!i*hz&nFycl@Jlx6?mz5e)
z9CJf;tj@9+qHT5ifHfLqsJfNIKY!8yJn$eGKQH--=eUAFEi?R~R6BfVZZA{ZxSVbB
zYIEOPhQj}Wf>@Ubm19<5R9o?b<y*FRy+VZOXn*)7Z;g0TvsChsIKVHsX=a+<sZyX1
zCKBlpYM_KT<`*bopU#u>VW>rIP7L9P>CW3?%?UntQeu0t-jhdcrh2$I^bP)fGm9RH
zBV)R^AI^p?==9Nt`c#7US<5c*@yhewPKN@8Cw&Q!u&afpdC>^Rz7!umg4|8KjO5#8
za(xWkuU50cAX^%}tf(_>=?Fe^pqF64BfTIG^2%y9l(w;s6PSoO<8GYa(~MlKOY%ue
zCUI#e$5qZWd7N!{TzRTaQQIz2n^JqYJOU4<m2)lO5k|f<;X~F_gU6wfz#r@e^qDND
zBmXi20<y;QLMs6uivBPe){O4P?wi=OiGYhl!)-i*^%Z|?(-$fjtF@Qu1I$+Ho9RVk
zbL;nh>wC`tTSl$;_Lax00(Pytf?pm2_QUm7L}`)D>15R4DHga6?iAdPEiK(3ToZ$|
zZw74H2-T<Sym{Z@OmFErDoVy6{xy;-pL<nl?xbq%jTD3?t(a#%*i@_-*myrD`Yo{*
znJ4Vm+LaOL^Fu2my6cP(oTLJW8tx~H#oG%$z<?g#@BHUTc{NkdWycyTJ1Aqk_Fgi^
zY^c9>rao$MH~EH4pcC0J02S<k0g}7>`ZCXdmS3(*<RNiYQN`***i+y88K~j@NrBG!
z3g@TTBZB@wn^s2K{^s$V9TTcTF>6!Z1ni!s30vRu1vSDDo&^e6I7L5QE7*<+s}25J
znGsB~o=@;Yk=Ys4NfPS?=gbZn0W1#|ioc_>7wt@5sw83RU>YPYR6^W2x@&-lP5aeT
zHExv89>nq9lS^&^tcF>Hl>A)tpmgiplfCWrb_CMUYh6_q@QKSL#w})q4x@$dNX+yT
zllXbYgH9vRLpCY`r|Ca*RDG#NXp{D56~1y0M{4DN@O4f>qQzjkZ5yX;+qP}nw%w;~
z+qP}nwr$()Idki3rf%Il<SDiDlE1Pm`LY&2?~vJ&=W!G9>|`V1bW#dAu&$bckIvo?
zGle?h-hErL#_fHlx1BYUq&hHY*^QEca3y9Qz*+Xg+?@64_=O0^*3UYT$(Ay+rS0WO
z=vW#@x51<5?%<4MSopVk_i8jQRVN_NU6Y)hkb&MyZ^ek#lKm@up=5&>BvSCPqTi2S
zJ;t8`^7*D2Z|Ysxs|d4#nO@F61_|d&k(;P;Kp0)FZPCdV2~B`2m}JTmidsEp^SlD1
z*t+hoN5(-?Jpv{8yg1qyMYDShXhBRdB<iN$F~SlW`j53A>Mn$@pk+|c<h!^A|Cn}}
zcd#Pd=U5W>&GB-L9&pZA@|?>GB}Aih-AXeV{fPI~8Q`e_^obk(pdHgtB<Wx`3+&;K
z3)XF9S$%N(8kjl*QN7hsdx|j$e$*+1Wgm2rq;1ER<H<F{mlTyV2xNamdV&QLMvb~n
zOcx1Hi*?+6fI6S{)9{FqIrSRJbc*0^$MRZ)v+8(%H!y4vQ~d5=$Bq+DrUciF!!k6$
zo7xiTZ?1c&ut<V>l*diZW&$VumE!o3yPL=c`OtK3*cyd$D)olbA=Vw56ST)|ZgEHC
zVRhxQG67J1dg-+0O-{?1EA_59d#n|P4axGldzuz&ap}`*D1V&#SsUIlPDT<RL%)un
z4J<2yRcaI?9u}s$S8*{_fA~#v?U{uAi?`eM$5V#flgp~gSoMR%k>4Lu>p-+IxdOJi
z%`7;n+FMA*zW<^?8KctN_i?h9k$s~w^Nzn5A(g28&?2d_jv7kHtJqBfr&neL`Uy1`
zN#2x({F6e`svqps;aD~&f5FWtk`^OmJ3yH3@|a!H;L_lin4IdAs@i#nu=7pMRx3p8
zW#)c?ybYJceN}C$L>HO;9FfgNu(>!~+#Ttg4uw~VPjOU&(=xTGWeNC;J+O3_mVL>I
zzdZ`{m3N(l@!yLs^!N_UTnyIliwp>t)ex|u<$9C>s1l{?w|a@JXgVZz4sJs_Lk0|e
zMQwFCt7p_~%NdvK>Z==BS>Z-)rK(h;yUSKfQP`DZf!@e^X4iqThPeeY7ucd(CU0Iv
zShcuF%9570tEN7VwMb@LP0++S-!LXk#tsF#ej;#TDY(a9pqdX?1q*xFdF_)*Gzr>B
zLG$tHCM#{A24{XT63rD9=M?+a=dF2Is8a~hOQdC4j#yhgs^A<_ChDDFe{?4t207j>
zetJ%6Br<84!nL6D0ICIe1sysFcMB@m5`CF2dB~>A1H!c+Uw3R}0CB2p!s+BK@4pOz
z5~%)s2{Hn4U}WM6$x&#=x{GmzLexJlq3$T@zr%@by#?P76tR0fdloE?%iwom%4Tav
zu|;@?X%$#7BQ?nP*0S;kDXl(63vh!>jAe85qnLCx+qg+e6qv7EdKu;vLN7XN9`RNd
zZ9h7x=MG9RrKi^_j#nuX&L9_OI%w|c9^hs<I};UWPW)bzjKq-c5hEmL2fdrJW<b-Y
zk1QurbO{C?wy9-EY4maQ3yl9;<y%yE#nt@{VtlSmpgmx<11=J92_>`<ZS5laF6`u1
z$zl|&kF#hvY9)pVN}CGYqLzSCOE86Af~>B!MJM!8A%)U}{F3ouBk9WklUKG9MZHL{
zS2&*|7X-ZTUXCzguR1yTf%LNc`3737=vY9BA3bz7IaNr$xt_UbqVK#UN4xa(`n^=(
z6ObW??Y4DA^&h(RNSD<=wdzNT$csTGL+MmGXFUnhn2^zf{nvZvid#RTY87=|EkzlF
z4ekIJDgx09k`c!u`3!>9+Yx*P9SB18`X=7sV8deu`&=<rw+ej3`M_fDJv$x4_7w)<
z7TS*Wq-YF<(Im2-0~E9+;kl`!kZ~?4V)Dp{`QD6~<DFSx$#sUy(aAx4OvZ7}Z;guz
zy{vOEz2D}W&WkrGN=Lol<V}g=dw&Lff-T+4#;U8yIpoBKAqQcPM;<zXt<;@5m#Bxd
zah15rIZno^Mb1v|!<7?H^5*1~P_`r${+Nhw)+q(>Yjfw~I2>w?Qpo6`u#I|R|0ybe
zF%eSGNt%$+@laUwP5bZ&<;}t0g&I1-^5kqjgncxco8I-9@ohq8_Yr?xkHDaYnq^O*
zoPfPpsM#s=k5{3Vn>93Y!K3~TzOB#|Zg{y-SZdFVej!1tqh^OK=Z<}w@}kSVX_(Gf
zjT5hdv3k)&bG6c44;s%P?R`oOX*c&OhpIp4YMYn{zLnPO!`!Hyr~U39#9(3wnWqhT
z^aOqvZ;JnmwQnUirfHTB0u|j!pOVjOv)mO8crDCpr1u87p^^lf*%OwK^ki+xn!L=Q
zb+V2k6x49<v@59Vl5{Q#Mw-m+<0_~X>}1@$AiooQ#7N!3aFvIYR@n7(XBaQYs)=jf
zTIyICZ=lWL2cdYo-FoI(#Pq$R*&80%WjG`pEqPnc>MR3aVs3qRlB~&k-<HU}vcSO0
zG+q&Lu;y$^NjE{<%dxC8NSnt(JT<AnI3%Ye<c}c<B9zlaP;Kw<R*cmluR@Gw8K1wP
zo-L-XO33AG?@oFIWWXjXuc!#c5iC8>z0AX-&=fL71?yPLO3}d!M|>UzLhCXVH(4rP
zAgtd!6eVJuQz@24pgNpK#pC}w%vm5nDc`}gsV?Byh0JB1><(%nghAPeW$tMf6TWZl
zP+p5pfn02s<wHX>zviP)(ACT_eYSU@^Fg_heH&BQ#{{5~@u5$d=NhzQuNKR(k3h$n
zM}&sDv%v^JCjL7QW!J2M%)Bq<{!po?16qzP)Iz8-U_ePmipd*S5&J9s5A?#Wd8wpz
zX!I~CE|R~==kQVhxutw9k292)5v?EwJ*5nq#e{;O2b?9fu)lU)J*6mH+4w#KavMy7
z4rMjD;ay5{*&}l=-~%temO^ZOfXu(U?WAXW8PdzJeuy=L+~h!>0>b#qImI7so{3Ve
zd~}=aH>@GlV>`NG7@ELWvByXo+9Q+{GH&eY>Ers^B0`YKdPL}PXdk<KEquIDU+spd
z4S|C1xDr{cHFj<NDq7VntV^S-M}pz{&7gr!dHAbM0iJ-Hu|_tL3ZxmPD);xxZ~V^Y
ze9dpr+%&eHaCmH=CyW2_qT&|mgtE(H^|>{)0mZjHu_m`1&q^OHsqTX6nhbBN#~@~?
zj#(97lFtZU-zC;<dSw`)d;TwoN4J5KFH}6iNy8-Ca=v@S-(;jxek}?KX!Qhk`{hd7
zEM(leGAB_Wmn4wD<%VO|qQM!ku2bq%=54jp^TGoOlE)54&Kjy_m8C6Xh-Qf-GgeN8
zk!dv%YbD4G29bZh+E19z`kHnTnPV=vFw3v9pjpJ5SP{V1QMY{5_LS$b`xA=Y(?vRI
z$n5q)BT7q&S0)DD7}%7#dKxOnU25}`A}OO|6$vIo`{g4r$Mv3;p828mik)@QE4_0w
zHhf8-z5>5%cKAa>zavp(!<@dB+(gNU`UdikTlhFAQ}Egam*_7^?E@U3HOancl73kL
zT`fKwFC(Z(ZwMG8q=kI6F%=c*M*dXkVpYotV@0iJn&Umo3EtsNTI=*R?(`qc)T4{N
z5t!xno2GKn@z^@fY^6igGFGYv?H8xy^hHrPAiYKRBMj(4UAT+8E&U$-X2OFi%ctKW
z4qEx~2Bc;rWc4P*)T}YH$6emaV3Kpk=jTwQ7-wb2zK@P&vL3CJiy3m`jZH5rH-l1c
zig$(;_HSaIe$W`l!L}{?pBde`_~wcT)m2UBcb1|e<+F*F2yQ?T|7UxzzC3P9Fyz7n
zZ&7E0DZ^EfW)*v_&NqEgM4EW9FvGaSf%FEg@kP|HGL+FO?I~=ZElaM0dm*K4>HZ3t
z64nSZ@a^C|#!BFQJ@Gf^PyUluRa?_AKB_BhSt*46-nz8Nc`ZRC@6ecnuEQpdN@g2d
zD@utGCVA2s^y9zE5?svf-c-^GV*PXDW_sdU;+cZsIvQ*idx9)5DR>Soj52LXx|mn7
z{`32=96<{O45H`KioL=*Mrc7DmJ(#*f5ls#uU$)*Sb`J=6cGZQhtumJ?3Gsn8xxf1
zG>G0~`naQsUp(X$N;Wo<VmAP<(fCT*y{Rd>p&yk5q+e{*_l3Z5n4A-W#E-a<M7Y&7
z^CCnVg!l6N4kwB3(nT~|-c{f@V`(w$d_-5YY5p9D&qxuxW|HV--YJJuBRdb`6k3mu
z<l$@s46bkW2n*6HIJ)SJMbv@HZBZ-Outrv}e;N>Q?~5Bk`bUIFkXRn0k!F(&VY-4?
z00pQE2XjnJWyYMBPb=cHh^rE^?0hVHb`!Z!NDaBRk8Yv->H!d4?g@v8lEgSzl@ueD
z=zXwzWtlR?sk|$)_k-VygQ5<!)*|Y4KxB&Nxt2?=ndiu&vJX_aXejP;FOm}1?jEN9
z1y+=z0VfdW-a@j>l~9k<7E=m6Wrp-b(vwjPUXsa@8yII$jLcQY1`h#fnlCD&sG`g^
z?BqXJ$!Yk5yuf&vE}+qw<uV6g(ccncPBM%*L!zab7mO?w-tzpJIqL&An!enc^~k`T
z4|WPO4`1yoRo2&qeW0J~B>!1a-Up)Td_wdAX3^g&GIMB)ClOgQByJ{E>uo6-uW{}@
znepb$wA?w7U(N)eOWuj3Bt6P9%?$(lMUY4^B_1MjWVjB#$`){}yr{olX424tx<obX
zT!!4}(m{2smC$Dx*|JT};~_s?b`%HX^jzIb2u*t(K?Rg76pYExDA)B0b01_!_nDJ4
zbNt<oPrp~vPP=pSl044VSXZi*XFyGQkU+nLHYcC6TO{s75I&fo&s7}9F-@T5{bPpX
z0GMvFr0PF{Dboi9AjZ0UJwykBk9W5Zq15o*7E<l(8sX?rHgMju^@`FfN#Ue5$L@+v
zeK6{5?-#(Vu$l>@gE%;45}9;AcF>$4nNj4+$dGAiqC_zG!t_2FPEv%@Gj#NOL<ANl
zNOKPQcjJ_2@RGuAF-t`gHzK^Df0bY^{GEhb@AfdG*d0xE1RoLlvu6+<Qc)M%%N@!|
z%atQ{Sg1WsZ=r);#4t<)@crBIP%vn~YT8JDDanhu&r-ErpeyK3JYedJi^61yT>rz(
zN>ry%^kVZ!87r&Hlci(ThK3sK8DZ46VQ0FmYAApn-l^v4slyQC<1Z5Xv#W{+tb}DI
zCBHwA;~g=p9V;CH%Qxz^AgL}la6x)ffIa^qSTwFqpZ-K5j-Z3N>Db?4$@PrRwT|Q}
z!pkc8CkD8dO-R&s1M!l0`-hAJ2*r*qH&3NyWD2T`zf}bXdLn2T6CQtbq_<-%FWGn>
z9oL}Xm+kdBB!h!bNEzl&qK$puk1GayO_zec63M0Tv;`@`pk~!(Zv?FbJ;4WOXS9a{
z&cO;pXV3y`r^RBB(M#4cMZvWnu7bH%AqCh}@xRQ6Br>whpV8CXZ$X|mu-uTMG^72A
zIqC=p+OO=jA*l>g0LI}G#YCdgwe@)9kYxdbliC*fYuGLEd)kC-yqu+_p`*jaopEr!
z6B0_Z(C^&Q5Qvd(3;|bLiWjCuf-KrcrKTYn#MU+TQPQNNphmsfc>qm!NO|T80t=78
zaYM>!$S4y#0=6C;Cu8pK_xR!Q{>a9C`fxnMw5Md;ZdD5HKfld_EXq&cstko#vCq0e
zV($f1AUL&du8_3ElJY4mURML&XI|9E5(?p)3PU5J6K#V1!~f!v|CL;n|AUbhvycY5
z!HoPo^uX^={>c>u!lY|DmrsVi0l~g((Flb_z^Xbc#xLm~NC_#(dlM9&p<NT%o;s%e
z_mQz3)d{I_pl>>2-tDh0+FI47J{IGWBSjJ_B&i0*$n$ZX=}0JB0=sbJ3(YYl&4i+}
z4vwP?$3;STX9?2<_G}e-1qx*dWDmuP?yP?%^KbfwJam7W*nq^my@{^f+S$d{W4pZh
zWxWp@W~eM;m7D^Ul`={(;hk=cQSlFJdCDW?xlh^VwtPAN2%5N)B_@!ltzIQJy^WtD
z%lMK#_(JQFOVk@V#mO|ffh64*?xz6*Oaj|UYubvFr{3$}+qKwaGVw}fx-pbiQeK{~
zDS3Q^VbJ3s$!3{gQTBcQLd(gQah<Va*~Lp%TTl<8MiPf*M|HijwuL`Z+98~AYLXN#
zTymS7A-19-A4Em6(r2@c#gJsO(83Z(Zn9<HsC^L}Vtk9AYo<Jc)F_rZ5tB%9e~Y<b
zdsADwHj*4TEDjJmFr;MoRxQlgcg%vU(H&0*(tcP<)>8+_aJ9t=$#(@y-Z4Odpyqxz
z3OkBpxZ0_z@%ep$EVJZk1jRgRVH@>~DfY6mv)c6dOAqjef<TS?q56Grv|GcKl_ioG
z2VDLrZ5aRCwhq=N2wlw7Q7G(CrZ*o^VEaqEtD;72<srMYe8Plt{6IS63IJ}*obPgF
zG=e^L#Pd+p@IKiNp=-HF7#$l%ZJT+Iq%h?Jbur3pxliZQi`~q2VU}@l^`>lfBF3=1
z=9m@2hh6t!t`z5(-E@1I%Am2lJnUP1D;$&<qe@f+uI*EnyUqw>wNAku<_+YQYwCS8
zpcdJ6T8Jm+bn{*|0^P;bCm?Jr;i-74wL8%ty<{>I*M9r(Fm{&D23R5NF;bpwdbu#7
z`Ii2M=<#j8ib}gR@gw#xDD*+A_vgn#uOQx@K19Fs_>I~<j3}kBMW=#DMlM}*l1pLF
z&}ghqmjP7;w3$omG60t6AlT?Qt{?|4bam4ykz{5SY5fZ4+`Xc^XctVE!8h|CB*JY;
z8=K`;MfIBb8CD<B?rVSgQ|+lUr`=s#>#v(Q+RmWV@L42LaJkVzI=U1~#3ff9rEryN
ze(nA1<gt21NvU5k0St(_5hky&hm2%jYxbF$Y0ymSiM?s0waRyhKZ8b+S2YgojZPZ$
zH>s^An?=)Z5fYyAxu&BSlv2Q>Ao9jk37AU#X>d6d^Qj)4qd~-ym})bA>fv{qcnA2c
z!PD*io9=Se;#%VrGVLG<LNmqp#LDUBsH}^EX8aZ9Z{>`MGg8=t9|(aa@yqZDRAa_`
z6&&suaqDTamI;~0Dcv=`uV&ro1wCLAX8O7>=}oJ{lBHOieMIDY@E62`f2VgU#;-Zm
z{=$tnD#)(JF+%E93e`)V#O7$lpQ74TeHQgthluYrzS+nVZNZ&(>V)UT5kCYpvJ9%5
zg+;Fy<+4cosKMz*&<mu@`*{78E>Y4zyEmor9Qn*fraar}x#eG>J4#K&>*}a2(bP;M
zp3V4G7L<~OYt;%wOLTWB(B=RgVc2aVt()e~oyXLymf_1)gjP=tmHlv_F3hQ`amqJi
z#w$i`Sef5U3RGrJ_MU&{QtBg^8D!7I1s(<00S*3UJW65g>3pz>#z?bby}Z(PwyQ=E
zjZW`?c0CQ$IhERh@sNr6Vl}($5~@o#Ls3$hm1fj9dV&t~4N;%D+u(Fyq{?O*ru<=d
z0&=(Y=_LRD9YHpPN8Raj{OqgV3l}4o6HMcAncbG@^k%`tgT=6Y1oEVOBZEYGZFx%o
zM;y$zm3yN~FL2NuZtygK^G8-Qavvb#qPZ+v=t_%!a3rRtHfRGm9HoP#?8C6OZF@ZH
z)EzTRZIxY`6*XOJ7c5_06KvVWq>#Wt0=qnQ4s7Wgy5oZ^%cXegWOB2=K~&dVC8@^#
zt_geuvM}(S?Lxb=Iq3FU$o|9hc^qfjC5Xc_w`nLW#WjQd4pZZ9Z<nqdaWf;p%^Uvq
zq3fRA4%RR_fk7ydP?G!+45?%9KQ(3lY;s_CfO(!ae@-$Ei-ofTw{SM6_`a?u?g*H*
zz{9mbpJf>75=E8cZ~_@4@y5?#FpF{99;Np3IiA-(_!nOs_2~|<)@c$4x@mAA`sH92
z%kk62EnVD!xoU??w*sw!|K4iByKXbqVh}7KThQ3i=Z+|}ek>iX<ge;*>*rx;XvHzE
z^wpnC^{Uiw^_${t3Tddw1L>RTmPA7uZWEeceGa3)rrxtE@eiIcY|YE%%m~TsD5Idx
z?F)Gu1$c@RLwLU?pYpJ*sIrc(@_r~C9NYZWcvjNJe?-9Y$pyNSJk3%=MCM5OgkBTO
zUi%O2xDt)2WY*^B$&@hIhePu?G9~F0y{po&ThFh2mGlcTu&La0$Cpe{Dr&2o?9p9B
z9G8jMWwdw7am`=Z2I!IjZ4In(EN$?YkB$%^J3-K|9OH=Km!{X{jYv)OT)JLO{5kPs
zq~3eHJ&S^jonxoeK8kc@x85;_qTb4cx)K@rMNh&KmU<0IvtTu{IPRdYt6wW^UwG^}
z=2L5Ew718aMk5x%*K&T5t1{zfY{(nl?#X_y4?(~Ks`}1%HqeW2*oT~BDsluzn;%kP
ziz{|WIH*bLM1Yspvw8ea0nJG*EfedHx84hG$y1w5d<ng8_d8LRwLUzqkq!O7pww}R
zlt#ff0gm`x@h=G#pmVctol+PrgpX-T4ZYj-7qps&J=dsi(*_ZA+b2$eY+fUrNOvVZ
z^(~O5X}N-FCBi$j-<inc4I2cNH~)f7`I8BU=XULV;$JrrYgbe*Z$|`nXZh!^#c?aT
z2CS~Dq%%r#2=I*R*PnywNv{!20&NzMTI#rBwClMGR$*4}Zf>-4VK*Yym+XuAMER6m
z&^+X_3-WLF)ipb)7=8A;Qtd`7r~Vy`+r;Cd%k=0@Wd5oAy?@S(MXKC<*Uxa|ReVcf
zfWgxFqp%pZq!l>GM+`$V9lJoh?vbj4!02YPRU+cZPH8jAhD*FiyB#nnH!#`5kwPr7
zEH=w%`-<yE{%S0|mD(`=$wuL2>>p*$@Pr8brVxF@q;!;N7N8!~m82_nk4k~)^L?Ia
z#|^6zFb65D>eQX~BAJn2)`{q{iO}+}csAa5QGR=V!P0fNS~ppnKiHYVEF6asi>KKR
z`9rMsoLcF2!qj!p^Kl^OgyD-)*y@mbVUAIiqVN=nM76_0n=<uI;9TpF?bid?wF;9^
zvB~Gtn(7=3>}oaoDs>T3Cfp?6PGmb_p%yF2q}krpyVCiT14hb~K%K?+rDXsZN+H+%
zHh4Qf<2U=RbEBl^gI+F$%=CF?P08p-f4DG;uf=iPdrzV{K7Ae(AqtP|;eN#DvMBF<
zemMSfAu12LjfA3`s!dJv4*pyU*bo=8bKfcQo*|6Fx-F$x(Es5-$9K=^hiGgr1*Wdp
zr)9MxR`8Swu|QL=s72lKFirQBe#6{Tb_rmDU)@%|Gv$et(U1p@B($}ZC&}$&|B|q+
z-exQg^AAfY*`_EgvL&%(@LePD(#&yA8pqHYdXEy~?2AZ@`PkmjV`pl=raF5)43E;u
z*h}1z$_T6FT_#c+Zq^W<&Cs0HY<){Z7n%_?Z@-TEwT$U7nmys#flE#F@Z(H^J<aFb
z?j8fbIker$yZ#$ytGkl$O_k0!*=J2B8!&T%)l6@Ltm1>Ek3dW@kJ9xFT3YJ6CZlzT
za_Y))5Zh%{RO_h~HcD$Dey7#A(KFr<&e@tlsJv8;m|W`2o$fi;KFC|XP=Q)r6Jfxq
z=;~(FpGw)hf<i2CfXYDH(I8KgRRzhqn4bF7Z}j_CYjm8zjIE(m!kkhB56@Yx(l(D|
z1BNh8CqiN-zx=X{3$eSY?^-j&%dqqqcF&e`awSz@w7Nt(L-@Uyi40vL>S2H?@-RRY
zA25Boma-YL?nX8M)sSErt-<kvqqeMy+7yJy!f5Vag04Piqd1hiyPJl$XfVwD{STS%
z!S^h?3h)9XTIC_d>nIzak;jSJsf_0j#l*|{P~)ec1K1*<E@LgQenY_u4kfpnZRqoD
z!DeH!fPe4b0>wH?g;kG1dI~2*{AqbGhFun%U}1A`ZLc9!P68*Nzg0yDr->W<_VhS^
z1V$+&_{9VXG0zc{a}~z$+5<v!wH@aeN3w5YKaUxsPydIz#E)!f_rRU8Yomr1t6H1Q
z3XW7<y12dHan*s)`%nJ$#Y)=2!g~_kNg*t6n&Uwt4e4FNy9}FO-5>q5$V@NWC^x%%
z@zU}XX>gl%II3NnuF-OSacPULrK;rwbF>_Uh4uOFwQ$}~T>j+gS_gJTrzngV)W^fw
z3RPD~xThwioN;tK8bFZb=R<~q*lvGNh1rzNiX1Qf-%WWe7L47L5h6NTH`!>3W%1dX
z+rREw${mO8xiE#mav7yXX=Bb|>Bc(RRrvr{rZ2uSweYzvNH&Utg;H_st>|bweB@ms
z9C(B*DpDTxlvY6#*q<AdZ+bVONjNdf8hk?;sre91OLqI}HC~_4iMPY``mDF=Qll*~
z?(_TXS&KFkIxff47X)ZW%xIwqVgoYURCwiF2v;^>{`JRi2;a3un{H*wu7Ur~f(q>m
z(hiqO5^~H=-?$Y*n@XI4CM#MCgRSrSjN7BiR|qKeDCAO+w`G7cZU_I}duGO=`0l5^
zkGeE0bKjZW9AA~}_K(03qJlHCQ-W_FyqgwYTrLB5)7y*E$=F?g*d_#w8yqyW2TL~W
zEi=@DewH-@)nG#hn*BaMpW<bL388jk=&a`5oac0*Ltb)d#gfNOUu5nsq&@Pgkf$)z
zuLm2+7xU;FI$B&-LoMEYh2zVq4ki41UFuGFi84T2rdLI75@IvWS<m+vSR}mVy?WC?
zINISap%^rA{-sa17Vr#DSnwkwnuYn-6z(vhm5xz6a1JyXb<VhSFSyD-eD4^4+C!9*
zq+aWS`}NbaFrJd3-IUMh#nIkg>C$Z|`Zd9jS=l$@aUjK*t7BL~jh11_5AAc0EzJo-
ziO^F5-HigZN?oNKu665*+F&5k-2JOMP_oG(8R9FHF{>%K*R|~w(sr~<3@=)ZNJgY%
zWh1{qFm}N$AZ6lKlOEVF1e#9oNDwkGKPy8g=vnPwNRwk9&fj#;bbY{z>yQ%idD_iZ
z;cadqrZh{s&k!W^5H#q^Uh`}u9D#;eacgf-@SGyleRH#+KX1w=Zg8LJWLJr#(_z1j
z8_PQ$=4|?yc#tX7-PV2AS07>qP+-?Zl-Y4(DxFBAN5;_yJH}Y*<;;jsPt2J8z1_G`
zRnZoX!iwVRbkrcDr00^MIJF3GKCzH`M5c?T6+U4VbkoouMKN7)jO4y%etreceskbK
z<K9JNrlRC!`MLs@wG?7rplc=EU|~tJL@Eb%+n&>TlSm3(yi=J{@yg@a8on*q`nF<+
z6!C`Ao#~?>c(Q=qMd^An<O^%5sg2giZD19}MV|1%_)6%ZAU65IwLjS|k{^U6?FxA-
z(aDsb_*2tklgcjV(W{=$4#crp2^lZ@U+{1}F4STD%|8j{R?mU<=`+>qoK<*oq<#Zr
zR|Goq>xMnU$kbKe=nhpnEUK%uEG5%Z5C|1}R&x+HQa6bCm|TkB?&ZU@2Y~$BgK&j`
zE!#I-<uIWUm73idt+&vEXfk<|KH@jnbbic*1R)BpmP`v7(>`eQw(*OHFZ)#DY0t}~
z7fO`ai!#|_{>+V5)_mZx(E}mJ(~PT<THRI1q%eUBEJ|*|EN6Io=aHkej@)Tebd7~b
z;JO%IQ&;+3o{-ICv-uXTLXpxbXoX(aOMR_4%sC5_Fmsy(Qj4r$H_6Ym&kk(RQEAaq
zUk7;h@=3HuL4$Q-{ix53-9>_KVD0B$ST-NQqUlX13_zIE<j;s68q!$om@p$?UPS*4
zS6A1-5)B`g&Gn}eCQ{i7>sH1Xlaa^mSVTj{_<(zO6-KIM>iATnJdbO?!hnvvt67xX
z+(|~vpIW4tO8mGi8w#FQpl~PoQF_$9DtP@*+(d<o$2z)<17f$33TR?!Y53_`VFoyX
zLL#5M)0;Q(5C8#!NZ@o=o!pAsMg=6Zn6{W<TD=JpG{d=`8o`(xj6QOo85Q>P1HZia
zv#dsI(>P?kNeenm#UyeWY`999EjrkV*NS86q`GoVCHRU-h3VR`yC$@48rEb#7Pap>
z`bCjyF3M$kP`(&0l|ka0Kw&}64gBx7X*4=MxW`4*I|J(+GseZAVq%lUV9&oq70E&k
zP+}@8+T9qgl3^b@X&+_mpQK#k5nO>k##tmn-{Vl{aN~6dlhHB*251S+iqqp?9bt6)
zaq{*T$9FZ`Jxy@O#m?s?DN#UPn}AcAe^jt=>JvITbcIWbu4(N@H<}>1NL0FJ49tzl
z3~KJ33o=F-Pjhp`YU3Bjs-Fv}f{<r}oTn}S;5v*Q&Ma?gM^BIl+;8WgpZwJ|duBef
zX+69+kpAL&e-H*sXV*|{KCfH?Ws@ZAI6)z6199kb-@&Oo*o?J~d4=tmblvp{^5Obe
z8&SJv!vJO)?=@icwZNR3Dv2>uD`XpnA8gM~gC0x2fna<thb^~hRXD>fD@|X5>t*0s
z{Gv*J%aHPDW=*{i&uyp)c;&Loo8aVN#ee>IFwcON>NkoQ414kMGIH&*t`R=6Eakq`
zUQxvKG%)Rl#A}(JHt0R7Fm_|Alki?ipS9o{cbt70KIfhNuxQ#p)iBj9wIL{}L<rx)
zJEe<+D^%qFj`~jS9{)>pz!`Xqd-fg>a-}|7sFfq&KtEuqsIz~J<QAJ?E5jRVxKrpd
zia1(@%{BQf+vq&Nk?`j+u*&%yLpTLXinA1m>9Mfex|5V0B5;JauJM@*>)Rsf>EatG
zhQ1s2S4TfmI79d#%A<;Bv`v=L^I3t^jz;YIxw?=?Xb_QUd!Iw$sLlu5W>2;u(uRv+
zMHFi0_^agEEW@$`$pxsvKA-9ZCUfRl?R8myT)SBhKF`R{gKPVM;QNKhrw<Y62|i6q
z&-ZhFR5cuATS>rUUBs0KixGU_0buzyHCqr+!!(v--KK6+)j6Eao``IL<DK<o?;LJ>
zCL|HVX{aDAt-}9tg>ey<z2#dmyN~GW%Y~<Eb#~ywI%iqJvZ;cxL4tDSAK5+(160JV
ztbT!WPRsi9#_Q5AIA)B>W?=3}>Pe<2roWYW8zYl$9sN7j_I<k52W1AX_S0IjwMZ|0
zD!MVm!xo6!K{^yEB^sV2{adipx>4^Tn3xHPok|I#IT44~@&HTj+zG2aJv2OF6Rh^$
z{_G-8%XdK9tq>&yf*mh$BY@WQtGkFr>}b-D#vdfwOA=$f%`iC2*41c3_;M!2N09a2
z-9ardnG`dD#S!uS66OSG6&ldOPf@9G*sQKnfmIq@36mB_X4@jXK^tWzV0WGF#;&Vk
z(EQ|0n8xpYuw}3tB$%Xf+f;OaK%G=z4^Z0GR1{eCfm#t%{vIGb5rH{d7CYrQF#aa{
z0x!&(X!DIb&Di$<s$47uJSu-`ya+Gzs{_AtCLmN8!{wZMKb-|)(kQw4El3(6@>neX
zz6$nFWk(j3(>JpQtVy7|6{(2mfm}^U2%XR7j`cK0juo>-UW)aq=tQ`h4UV)!?fELI
z@pU#s!gTW0E9NQdRkp-G+aLH;3Y=u5$zBhw5R<d(krOt(4^iAh!AmQ{tS1gpgEx2e
zB2Q!uj<c!s)J!PKi>{q_Zsq{tpO1A4pOHr>R>>?F;EE^SOu6IZv&g4}Al2SS^FJKV
zIN&+7#3USmK|33~!Gv>05@)SJ68BNQoT@M;*|EBoT5~D)>TKD{Q90|$4#O~xhI*AL
zs>ON$v9aCpQZ}lGjrSIj@&VMyLJtjO+NpbHQ?M(peX0ZmDHo`WrG~rc<{5E4M=x4H
z7&-fOZ(dpJ$5Q;pUtpxp@3rPKlcX`F@HBefR2!2RO9*oAnD&?Kq8YZa=v?xuFkfHP
zQY_O8p%?aOEeqVfr1i67V=dz!Jtc;p^4XGY6Ir#qQFyhufA<x~ncuOx0!aG#?&ztD
z)MA9)1G(d6yhh%O5H#H@x^-79njB4-N}dIGC)usy;U>d04%@xi-XqO6b|$0yrVtdm
zTiWPJC*~H1W`gN}&99H=A5Vu!nW#7dERa#f)n4Zw3z{bjd%|v5Yd?!GXBalUJqS?a
z&Yed<^tM;wU{Xs|-|(nFYj5nuK<yNmSbm&)Cbv64d1C3r)b?z6K1eZC`3tpHa6xT*
zF2t^Bal8*_8gpkY(umvhYed$qJsX^~)~Dfl64mHa%RJxxG!6-xUdZsmUa@&>>OGaw
zdFFVZ8FvAu2P9OSXj%()Dk+oYWueUwHoU}f{HMtRXlf~wp<A|A24_J#1smI(Iu_pE
znao-WAXZPC=Qzv|h1+^-9n!<xF1dv|*rL`ojnNB*7OUnE4!#IZ5<dXc2Hj_<X}K`V
zP1&hLb>@5>&tnoo5fdoIGX9vj5{2N;lNPIGc>5|k)ddU1TSBrXmhNHZoT1nZG(|0l
zwghbC_Zjn*7O$D$@C^N^%D8u#CSBOhG?VmNs~0?_?uY-oSV^2bslUK>XocP>F1|dW
z$d;~gYEc#|7I^K)_<19{$!aE>$+22P<ka$>`Qq)6tF}B9lp%2Ojr`#0zD((b(BAL?
zhS~fhEdVBNgoa4cI?Sg2B!wXhr#%Glm@gaGHju-ZpS_E7bsWAg4jVy=3jE`7(bf$S
zs@jjgU0#C26~%XNAyO!NzdFObj&B3bb8A2s+mB>35UZBwxP^L!)YLYIooy~%oWU3;
z-<|j)6LN$MOm8|(SN|H@xF}uML^3SPBgXYq^%k&+FAduf@gsFF(dIZs(>%AaHMJU&
z>Ic!;vDq+{{wL3wose}dM?Z`_(c1mR=F{fV?a^dUhI(0Kwwp$(jbX_Io*8J~Cep_H
z)bF4RP6JmoY@^e8)*0FjnN>2ipe)}?7S*lqI8r~U5TmAU^7Q431vRpq$C2bL7VnBg
zzqc6{ucS4K?&9OcekOV4R9Hoy&^0Z<3Uu7%DCA~%I8LmbR&a{3VOnT<pA%5MNo`4~
z1i^Lh19`H>1MH(!OIpoDs3+f+@Ocpo1BBh!P{=0;4>4EzjH<aG#j^DU63PTDZ~I`@
zhJE4@(<X}X`qiNUZ^MZFEjmC~W^gS(=o{QP{Q_sCM@Qk4h4muhx~qmUyVC8m0~PC=
zKhs~w=KVL`Ggv1&?Dt+XJX@ecS&p_c^gvl}9C*0&1rR?JxZZ)HSN#d$j8RgdZDI;2
z_z4Yh(={HF3!9=a=p8(2h3GHaPC1$fS4*IXg9!XF@Jm4(tLTJIXhZ$Yd+;r3aiRZs
zgt43=;9eL+&lNLUyxPz_qBR6Oz`uX{<YIr`Kw;=w-Y^0=hM|8ssXm>71q$gQzB*Gb
zNd)CZ`X*6@2BJ<=xSbvSeV~+2^CfJHym0x!v0U2D$frd%^I^Fo4jW()nTRA5-%lG)
zEn@RUBP$@yM&LQ-*ouzZoG;22=`ci9*&sHnJ~3GKlEXB!6Q1@AJli9y3K`C+G)rF|
zhP~f_1sSs8dsF-Ru1aal$GCwTcf#3WOALYAo>b2RG!tO%M@=2lg|{f}Ko%@7vU1hA
zgl*?;Z@K}9lYLFm>NXp48knS8aD<8S&mfO8dB;_68e81Oy|f5Dr@6`?y`gc|7SGGW
zP}|Pz7*_fWYi75>l2nS)+2`SWErcB5o~|F->8J6GEL1|xrunfi(l|>CR;y$agW!(_
z2Uqi7gl&7D)=@{p$!?os)cBlvpHzUre}`LP&Ul@ID@tX__r!pL*<zf#^^SoJW0M9p
zrZZkubJ}LbW*Mc}Z}BY<Bg(<w!eYTe%86r(fOFJWW&S1AqPgZD#O1mPC#-SO{Lu@z
z24K3Oj2mg+TS8U}HPe(U>ouHjB0Q?KEHBMkb-Gr%zD01=r)S^eyos{jD!CDVhV+z=
z_)%gjd`8}tZFa-!ZcQ<sbh;Okgv6+Z<99-t)`ku<`$C~uq#jDZz!Zy#VgS(6G{)P>
zoHuIlx)isuCMNK+VIC<mEy~s-5Tb2}I^s97aVn~CkuBG}NC-ijce|}PZSO<xGZ40g
zXQA{MxSWqn7$Wr3%>bZ<qF^?huW_B${^E&O!foj1@9YP_tP<KeD+T=phe5mO$LF*U
ziw>PHq%6wbE?FEN>ulMhXkPX$KZ4_H9?%*~KFhxiWm`m8lEi^IuhbEvNu>fFYbm4$
z<+8!^wVO{xuI$g+EZ@@Glh?9#nncyTSLz?4<vnH3FkhS6u~HZ>dP`2W!8>*`QnrsJ
zdT-<}b%i55ETum$<I>xA!GHIi()rHGu+_8k*;SLfschJWZ#H>#3BUX0^5Cm3e06a<
z1Yf!Pj2ec9OIG31v&bS?VKkbud$KN43Z%v1n<G#uuG~R(vRAP^Bb_hR?m#YLJdYA8
zePHBmUBGxVd>~m8?<JXuevD>)20WZQLkpIwDQ=utA?K`mV@^Db*AL4<K}ROZV*M86
zh&GC%EHtmbPcWZ1&lzV>PI3^-72``<EUyB`>qCf_#`Rr2cn-lB6oWcSd<7KpbvLj_
zN(-8qO{XA2J;9g`X+%2+$cl6`UJ;82Jb&V_NIdw%<h^>NU{I)zz>2L9((Y_AvrK!S
zTmHVYti$zTZEN{+uExr6Y>TO8do`T2#Cb`!oM&ngbC?Z}rck^Ym(Ax`7RAexWC`6l
z8(qRV(?u?yF%;mH9AJSoSIJ+1vDHEbk8SQJ6yWr<Pp>1OGu-Pn%tWigw@fA-VY_O_
zZOp0#Yyt<e3GCyu%kpM9qEo$!-ejV8(`&KOuRsSU3!rfpZklLmQBAPr_dRvAp*s~+
zpK;C)Iry!Hb@yCq*P{`dWFgm6Z|I$M$QeMWTs*1^H|3J@MmVA~MLlm?lV1(YTD6AB
zHze|VeBu2KV^dYz^CnQE==SvDaV}hG%*KQgD_`g6waUI^_L3^GP1}L@xcWd$lJGBU
zh$9O;Y2FJSqX=CD7}$YO+xXGD;`x=6YywUG5$a1ty+Vz0kLvrz6XLz^<dgcjgl2Qn
zvY%uUDte)(kYz(3^xaq6Sl4?m;@F|kdA(5cLT|f}V=et&y4d_pEhr)9X;tC9pC>u2
zxX4M10RlKc9GI(DATqX=pKhvD&IUp^b^>f-p=yiDPlkX*YNEOawl1fy=I<`(ed&d8
z4#cf5JU6z1NyIIeXJ}pjeRZz~uflF$b!EtP8&j7MvH>1-JkoZN1m5F0Ys$oPB29!|
zK%@d)IOU8!A+CBJv9Aord18Ldm;`+I)*Xp^c)gR>VSQL%ow9Fv&NRjMr>0uPW|L$o
zr+MV&^Fe-ooUWk4gmvJiFRrTde*c~;`h=t;UBZ=js9SaHLK29C6P0*Oio&rOKbKsv
z=&4>AUwY;y(w?6TUgjRMXyF8vajf4sXY8tbMTOA_mF^|LEa&e413WBUG4AQ5q0m<h
zmYQ|nYt7R&3|4qC9mYJt*D<B+J_&dffqIUR=445|_B+sV@?T1r9^`ABDM-IxT?3@`
z4)<%OOoYKG^go36ycTVz7Q%Z&I;?HDJFDn#!M(C_HJw^xp&UJMzM5JY#N-SV1eQEL
z5crTJZqdr~JE+|zYqTAW*q77cMg2|c1gk8Eg6Jh)KwQJ5n`~a2B@Z)-GOUKbUQ6J&
zBkfHPQyNYu%_TpCE31Kp{S|E(8<fvbIm$PZnhzs0EfIJA5@2f;&x#c*&D^8Er+0g`
z%?G{4VXY{0C$jL{By*iE)|23jN+eIotJW8vYkj?%h3QHIRph6fxqK@#zI7AqZc9$>
zoK2eJ{{X77gYi%?#%<(}5uvb;V+=IsJt5!fU^A=1^*t`wfH-Av2->d256#l65XJ&g
z$4)ob#m3U7$y&$iYWN9#7aKfa)ulOHYzl$A#P(`R3OQEE9BLUi%vae?R_f~V)7Zmk
z1JgVQT~i&`Y>+%j6$~I+l?BqeZT@K~fYa0AtTJ##a@?V9`tQU;?B2>|s$-(bt6K@i
zJ8<@C6Px#S;K1PE{}@F%S|)0>H+cxq(BP0?Q6%kldp;xM>98-$x=I@q&yj1C(^*!z
z9)pd75A(JXUui^!oW4%50X7^F6OV_zu?JfN`fa3joZzX5s#dSKshzrc7j2SoBY6oL
zv#S~Id-BDny1^G6X;uRSHo8NzG>MDFBciyKMSy7y7Z(%E%-vgIaZ7`*;l@eItJ;NX
zF0ve8LDmEDAbKD7X7QkZ4IC`!#lRYs(Gq0g?V%X9VG4Y8yQZDIqt*5A!s}TkO8|Zw
z#AT<nAithPKjtV&42bmbeaQ?fiWcf;@Kd!qcJoWJo>^KuLMIki9<&3IG8|cJ6}{9%
z%Cp6lrTK9s!qOo&6q(Y9Sf5mPU|K2Ah@1BAF>(KZO;wQBF5}p41=kvh;Yb*sKKz}S
z^UruV*J?{rZYXqBhK=n#%~YJR<uDitq<A&0NKF8V7snfg3R6volq*nYOct`@FHP7s
z(l<vx1L&O}u~A@aTmIZ&g=tLoYF6UJT&_v~wSwl#L9w$`v!?9sq&FCXl3gpnZPbh|
z7ox;EPJKGjP%|oVG?so&y~RKc%bMg?i*SwKxZ4;Jrap6W2W6LTMFNw8g`)FdkA-lR
zJtBw>*$3^OKzLKpyY{#29%N@WCeei=xNnWdSF($s(~~_M3_+X#yD29P^u-34^h=Sy
z2JI`2khH<rr(Wdto{8~9EEb|O5SNw2p!CZ4N$XU%Q(m7GW&aGg0A)*+Z>BdK&T$U3
zgwux1JnKL6V8UK%>C}b|zC$;e#sj_nqGvJkh6%h=%dZo%aDu9>Qw4J3G9HU`30soR
z5u2D9iM;sOa=rS4oZQ`*VDBw)MaF^<IU`YZx~<KIj%VO}T-SD}$$diQy_{hkg}_x5
z<`;LMLD>&82L)_~B#9_ID|daB=x#+LZR6p@))M^T^FZIT_0Bj7jRd)mR~&|Au63gS
z#4qLQL{u_*41NYc9Rf?a!9!rY%)fYZL_uIz@}Ycr!ISe{z3c&m9d-$WM^2dYJMSDf
zo0=bf0>+dIQfFMiG>FGeuIcNaijrZ9mZYqZfsYwA(I>OMxKHd2kVFX%Auo^6Ic`X6
z^HZ;4tzeQ2cl30qe7r?k0$zq169bHLVO7+y9#_W5CZ=>8Ga-dOoZ?k3K#541sjmWC
zA>s`seODf&M{V{{7^YprIm@3MTl87=HWV_i&M=Go>LJo>ON|vO@4d$?e|x+qqfy}g
zo?nrPXEJ{H_q6NRI)EE3O<O%VEnB55NqDaAl<X=I`r_An<>x^3?)z;~`*D?$G6eOe
z`+@pQ_tVl)d9vTFL1igitwVY54F$26Q%yoW2gHIhchef2>>stLQpVFI;SjQTy>d-~
zUQ&j^bBeP4#G?87)WUIA`df+Fs?_;X8UC?>ib1<-q>FW%z_tz+(p8ht4|(7!j8>cW
zELqUuLD;sq#9V&6c>wEa_GdKrTkk*FVaK3mJc=R!0Hr#B|Cii(Oys{JTu}cTJM8~2
z7cWbY{@-%(=9Ep_e{ymDUGOWsfSYDny7L8-+QA+}bTAD=oq`U5glN#=AMYd_vigEG
z*+?Ltx}iw%d+~$IQ@P0DWMSB!i_Zg=7;|iT@jM4Ib=Sem?77K~jmekB5lDMx@6CVv
zugc|N$Y1#WU2=$-FNG;uZ>8&N5ciuoFy@cCz5AmbJpdG=ujObo@49Sx;lqZP`7N{&
z%|pRz2K+a|kE`vhl2+_`OjF)5pBv5Zo-G_XM<SW5t`EmvTD8_pe-TqLQKKnqRWu8I
z2irQcYJLnxHaHg*dKxI@mGltN(UqbRYE)tb7WiQJ7|^noaLMa_l)Kdcp*d{Ca>E-?
zLH`Y-XKXLR?NVh7QY8Ym2_PF@R(=M?_UE(;05+dX$cO>~JSRSJ-`C#Xn%O}^5@@-R
z@&Jw>Y5RM5t~A5ru6YPbCbbKR_SwV+jcVML#iA%-cLs7Mh%m}5YbzE}!Ao*9^@3B5
z#Hu9zDQ*r?sTB?yNR&jH4g{p|D`x@tE?4xH>J*nX`W#W&PXFYRF7aTF_=9CX)De`3
zvr2w{xYP#}r=4mBK$QXx!G*M0+*}o0JO$ecE#7cB%*oBPbcKsSK@I<+#9PO@dd<Dz
z=Cf}Z6~jC>#n8u}4@&N?N~l5h9pykKEpfACIL7SLs~u=_e$35-oV9rdv~g_!yfWN=
z@{|!#MR3HlP`506tyIKsr(anHgAJavu0pY?5!>_j%4d?F47&U6!`SCpjMpdiB)bZC
zH%3OZTc6@5@0?ZeIjmj$Qnxn8xfO<PN^m>=T=AZCc~YXrDNvb`vU7h294WK{!?S$?
zp$TCO!hbJAvOXX%6L&m`SIpw{E2mpWC5Rgoyq5~A<)JMn7lo{do0H?gz;_ZnsTEqf
zO*h^(eghP9797P3Dj0MHKZaOc>*PcWIC`)aPUMxBIB$R$nhz7vBwiO|&U1Ty|Fd3z
zn4;{b{>jicVg48L2;g7y@BFXz0{`FY#on3D#T^;|5ad4x|Bp^Z85RIs$w0=ks8Z3g
zNrT$r|CrTfS}*^LS^dBBlm30o+Q87n+KJZ4(Zbop(ZYb%(#g*D|22VOo}y*p|C}IN
zRVs#v4QBh5B1o5ne-#_QQ&d$$CJq}vk7PqtGsUu~;^GF<F--t95RSeQpR6qMI6h(W
zcM1SZ8xQ6EZHK6s?<T7K6pio8v=NWpv*Wk_pXKfHo#s<H%1Ful=iux|Aa#VG_h(k~
zuiWRbjYh<+E4Q(oRI8~gRf8Ok%n@)kkW`qSH*sz5ExVTExG@~J0(KjB+BX|%^vLJ|
z+h%^+k`rm<+yg<X!4DP2sZ{R4mx&?wB}JmdI`AJ84gXHwV}qz21jhZ>w@10#8ULD*
z1ESOg8^quR4&B2Q$gx-Pj*o0`zGX=wyAxkO{c&2UZmHt}*9kdp=X7YLmd%;sG8Mjp
z3`o3B*y&uWpkkj}zs=fi9uXbPt4HLroA6c&_8FXKZ&@TznS5?Pk)i>`B~Y6QgwBx?
zb0ya%COpv|i9`WzR%4GCW2nH{R9<3)jk<F{g3s8tcKt+;-Qu2MEM0{T9JjJ6#t-$G
zh{yT&@y_~m0Yo%{lfIC=e|wIoZEf)sH>&2lUsAGpv~VDu)ra{AjsQ0_qh&a2n2Ibi
z%OjRJCV0>ryKe?N`X2M*mxK-6%tTw@(t8QM7XQsq6SfYx-o_M<$Ynb=06{3yd*K{}
ztrMm@uq_?qpBp!C{!~icCAooQ>W90X-LOb-`)F5GM%^=jchQ@;{9F5QdQVVdt6X6h
zkP#~7aOVKqY;N+juC7J31nqeAkBUma<1lGA)p^ja55ygsE(9H^Ry8k+?w6959TdPR
zw+Ir_d+^?+$y>UsMB2nk1H^Wm=h5pQ=%u^%lS2ADd<^RRX%vN+!=!;Dl$CIu;z(8e
z!H>#!dSH8-PzE7HOb|<s<m2u?R}WuyG_en%2zq<KHm&@?)k-0enabMM|8TTm%Z!@s
z<;6|DiP~fwxIxxmqwkLvJ&}t10lUIYo0!9b%_i;@yA}P$efF7lur>G%OGaL+Eu-`Z
z&``u6nC@y?ir}DSwk_P}a@4$*`vs_#*OIF=q?D~8`{sIf28k0^PaqjfEl7b7$%5)n
z29;MVSb5%C5bs(#VhDBweJ|#ra8<X>tj`9|ag<G@lb-zOhz+VQAiPm^#M%ON2gO7y
zM%u1|YskykIobmNTQ~<rYdoc2O>pP$Q(mSxBWNPP>QqphPx{JPG9?A60f=m@;qErN
z7LdnHAw-ecSc$JDI;l_@2LiS9axqY`(HD$6j0)vi<z95H0Lq!gQE33WJjDm+_Jf+r
z%$#>&hf(|97Hq^x!Ds7=FNcj1!X3wg4PjA8sFQUTHRX?z^yCYTH=2&S;vwF^T*l`U
zDG!X;`gaWEe+?6j-Zbk(bfiwQG6$1WhX-~!v1($aNMASdi)!%H`ctc8Gl?AP$h;F~
z`oMI`Q;>vsvffp$6&5IT+;9V2O5Uqk@4;BTO4Jx2u2m_~@J*#bvtVsIOnh<Wd&xVX
z%>Fto99=7)VRk%zw;b@T70={%fZkFqbl5<DqO4-OwkpI5g8MQ42Vd{N9$K^o3C6aa
z8{4*R+qP}nwr$(F@r`ZUb|!CTdZwr6d;J&oS-Z|&wW?~JI3+Tua)Hx?zJZ7tlAukf
z#x=9!(PW$}D0RpjaeitZf=2dZL*=OMIUwy#gW-sw3(*V-FMBk1ECg*WzE9qE#MRx(
z%f=3%au;hQcYQou^Zf^Va}4w1dw<c>?*GAF2mlBGmd^h#ToU~MvG;$#rH7HV$$t-<
zJ1PFZz;Z-a#<E58U+g9;Qtt-^MBb9Ge-CW-z#ufWp*vfLnp8HPEU^M<iR(y|4~7wZ
z0PriyVWL&vswyf)!lIs(&BwB(1j+J_njY#~9=c%nRNjN)x>}8;)Z4w?{?W`ttG)<<
zNbS91-&A23l!a4Krs^4|r}Db!aT*;w<!F>B_MG-NXDa2&;CWGkVAT12$5IHIo88Xm
zs`_1KiAbW}(QLm$N~I4kvnaaGc4ZuY9!LAf(7EnHrn!UNSwpH{??{@H3jgosMe&S0
z%CdU%et&b=#b<#msOYgE?{{q)ximh<l91|ot@C0{c~y+Hme;MgG&!?~H2Jn`5h|&O
zn<a82z1CM4Iz1H`3M!2@`?srmzAwu-I2ki6n>9u|D3pRRNYSyQr#N)TZc*iuJ22eT
zsN=b#BId#>Q?)E$E@tHW=rm5`UmryU%y(l=g1kwPv^P9o9nE&av2;Shg=BZfWbj~J
z4$LHFasmy+R)m-fbEP;9U`!_gv%ODNaJ1o`EVqS{5TM0yBzVq3o;l5@9~Swmne_xr
zOSO|n_opv8po<t4W^|6+b>$hk*d{7xb>dMG>$PLne!|Vqo>~-zs>F12M#{uXj^(Y^
z4Hrc&zdHNAPG>s2sG~#>UV=+NZ$GLlfvCJ`qv(x@?xrtUkAt1l<4vNc6_}WS8xL%)
zDNW>>S@f6#AC?GVGypnPHn`)1XP;fI?X*laP_b^bDmm)ym6_uGwjMc*e7JKKYJt^;
z$~+ECNY&obMo?`WmUO{6^0=2+TeT(2kxaV?)yoJ)vxJoZ9iH@exn@RNPC{5|a4OKD
ze0~tkb}R80cxU_P*(DU%@88QC=Rs^1x}SiBY~#Gqh%RYs3iuESRLf<5)mvu!2!afI
zw&*%AnkE$eco?lw*~}srzB7Tg(mmq^hP0XT8^7d>qwf9#Zk6cNq&czq8DP1Pw;eC>
z!EFk)8k>LpzUUBhe#!i^3!}uCE_q;*w{Qu*F|;U(5$PpWA;t)-Bv^}yky57!9(KH+
zpXHq!;;pRj0nw9)!&$k>H4ea$^pZADPPPN0E43JAfXq)M%g~e)dFx^6=!H`ars0}F
z8i+_cL|t12U*BQX!6#x6N+h^lGpQ9tx~i^yH3Hc53-%Q1FK>GhzVW>kCtLzT$ItpY
z;fj!s`->Oiz#DD2=Sp386rvkykT?DCAC$d|Vt{`WJJ9kC_9M>(o)CumE2GG-=L%Lx
z@)84oK<_xNZmn?#_T^yBU2%t8HSOW^uUKZm;-ULnMck$PPY8WroD-zGU2Hnq_;=SU
z>sp|#;yFx}URY9t2I<)<Ok!Da??Ji#$iN~by2nHlNtA`>Cr{na$Xh0nq;Md=3(>%?
zHxjtv=g}7~X>16)LW<s4<c=^~$I+Pj`&q}jC1RjKAUk49C?@{XuqNY@je^k=(V{|M
z9UHz?;;7k!(G|FirtM3px*GsHy1(zC{!FIRcYiSDF@v5D7Uh!5P**ua&qMxIMQrcG
zKQi$~GZdF;L#5y~Y?ecDasi2cTy=78Vo{A^xF$E7JL86Y`|C~hgTzrW8!Er<wEXgX
zj%Cd0MeRILUi#S@OzU`2GNkmF^;%=`aZ17EMK8&t(zZl`l&)w|RokuR%U;`rW@1ow
zD^VPOja`Qo(ZBo)jJ9xf6zK$qsc!cBp=29%ie#i}gYdQ#I9egB)Sk(Kde6Qot07GE
zs}t!UiRkQi?Xzr<5sLp>!rV*7W5np7zN3z<9_m-uQmSoYDpI~`2u29_SAw@P?4B1K
zPIw4EJUzEd43U_!F1wV=89PI#^|jkXKbnFUX6mddvT*>X`pcXGI5=}8$Mzl)h?*;w
zQ~^sqn$XY1PL5X@ndw}eNP(}z6f=iY9n5V#ZV9U8TZaAA5Jf}GK=lNq?&YehrO`cY
zRwY=R@NJGcR$M(H0hL+LGNT--qZK1B{sa+lGwdrT7lT+vH!|vbOCwlVN+3aMO`cr{
z1*p#%=L&Vc7#TK@3(`FqCPeF8q^B`SWh-e_)2opg=?_c-f#G#qn7aW37r_(}<eF&(
z-GyuK*?}OU7v!3kNTA6##`)wv{^q#soF)OD&*nTnbTkz@n<BN^;B+L(ef_~#mSNr(
z&cANoX=mAwK!qCPGJ1k3kR(r*F3&(=yj};#@}OohWEiwWjPtlJXj-egAeD8o!}WSx
zN~Tgl>J9co6eyfTZUrul9iS(TSMX6<MlPKsGnD30xpQdLD`GhYiDE8zSxM&gutSV#
zHvfz)-RV|R*6nTXwiy1~5KogFH%*}Pr?0@h&L-Jf**aIh=L}S8w4V4xoGNb&-u(Ag
zdMD?aNF?m00W|-8yU(D^Hb)^uUj7ryw=#3BcSNZZXfCb>lMsYgAbw6ofrYZ5rg-R-
zlS3wA?fePWDc+H+p)a;EzspG@dDS`=_1JbK;+cZ3vvfrTsgSoG0;f@*gQ~N~50p8H
zFHD@|s-KCY=0<Fr13eWxC%S=R(#p>Nr#_qv5E1mSBeKMtX4mWb?<PB_I`+N^^cR;Y
zd4|D4xxNoOy&g#K;E|T(YG2@0l46P{ua*VdN|tY+uBDoV8txvH;J`tF(0ba(`m4%y
zuMIzar4e&lz=@*JUKPf_-x!Fq`P)Cm6Z41qWwcph;6ef$++yM@A3SAHUCy~RNp5JE
zCT4{S04GWlrH$>;^PqjeV}S<RGCH%094^w1!(E~k`0W#HB8NH1VT*b~IV3!vi2im=
zo*4b_>$e6?t!$_p?Ygr0?%XQ7(JH4BoHRp8=8b^Q!;QY(nmIc3(FtCzgmY$V6OiFt
zzQ*gEu{+v4NBM&ldEf03%wGz~-*E?pM~ALdCHowvC<x1qwW7|hdpmQ0Q7i$$r|>2(
zRR`%1pkl>uopR!42bRrz2or(-_8Ii&VLVBKVuw`6%^!?wV?=Iuf$%L(%g4-D{UxRs
zz|`+k(}EH*;hV}l2&VivN@{D0Q+{L081m{XM9f|ciFmMXVxD+rSIw|_XQ@`#=8jLy
zN1Grlq1YNaJ;{lveH@92vd8QnBFe3{O_Jc(Kkwzw;h{G&)<w*b^1BXau9`nACr-@X
z0W?=pqKQLjq=QVveC>~Uz@dph(l*r6a~IspCKcVTjBgw-DDAd7w55v>r!UXM-;?5$
z565^XR6<px3yms$^<87jW<?DIvZKc+htpim#hc58qU(l^Vy;By;l&_RBEo8~*$}n>
z*(|sj3Q7YGGVDlo0=2KnLYFJ+aDiIUgRn>SKNC8HpTC06W^+)Hnb<9r`XyA8Xo=Qw
zC9wnDl}B=h4C9(BXO^z@LFwO7bLDZiZ*2mvN3)}C9wAl*$gbKUMA&cnnK{E&E}(2M
z0y&Xv;w|%XptqR8DMPqNX87LN_wZuWydW@4jTqWWr1}`p!Hgv!V4W=U<P><&88sO8
zaZ{)N2KF>QuBieDDDe&yBZi0fT`%}B3J_sQQ4CgjTvC=3V6y=YeO}&o;OEO|{6IXo
z9xf1`xs7gZJk}fOS#N@7Y$|wJXpV_yt2gkOkwR$f$JW<G?jwkW8R?wvHsZ#fS}UD_
znc_1&Bw#94OSK}3J@S;K@WjWB<WG7<(|v#J|DR-psEI0bArt@r3B&&&BmVOsPVD^u
zk`Y+{^+EjKXoF-u8B2!W*yaE55;pNXvLFmFAs-weDVfN#^3~+02snQlk?KYWk!MI_
zLs9qXsi1@f#vzXl-F;UhN%`(Sw!Ox+z;`PP8xPNI2evj$zO((xJF`q!pUh^?!IeuI
zDe+3Ou>gA<RW_viXu*8Ow!kD7{s7n9lU34Ch_1nUWuOg7OiXg}js3B==1>RTBtGV{
zRZzdc4?9S&med`mV)qN+w+WDjz%-zK5aGBK4MCz5;fqI;$Zivb=O||N69Z1&N41_m
zz!TD#Tnig~))uX+jzBxjU~&u*r#DoH^$Pq7{4U}hV;SNFl7&qo0NbDtbJ+5Ff&NdE
zu_hIic=^lHcmn?K&h*cJJ=6a^HTs{E{ZF9ve@-?=na6gE9%g%o0%GQgi@z;jDF8;t
z6M#43j_6NRBr!I5Bo65qg7fJj(W_y>Vi>z@&7(}J^!*2c#Sb@tb1YAZ(eY*Z2h0}D
z2UF?w0#;+P^kKY)x5O(iA%;UUH=P_%YX4HCW9Qp5>NOcqgf#B~1WE4L%)Tk!Qwjj!
zAU}nkWeXv$TH}F*WC+s}Qs6MR$Fy`sT|<p<yi}mb5xIJ9=uw<O2hw#;4IL$&VIB&2
zK+X1REbO;SMWs-3hPsRjw&cnoxN^S7Tgo#GSlFBF{;CnP*|hOJip5GEno)NivzXFj
zq`YMV%7Kgj4bFBp;k!TxSw9MS+KFU8rCM3LV{zeEjWf(96)}8o$x1leg|7J<_|nyL
zRV~6=){&b&PttbkXmyi#7f#l*rX#n~=bWOtx_Q5;NS6txUs2X$T|V^Tb$waVfwL*!
z<Ec%YDy5^8wv1nsqw4vcW`7)-C$NtK6boa%=9D%%wan`TR6us-l53fTF;xQVGO_%y
zc5rkdjkQLlKtN_qUZ~g$U-UAFYyO||=aoLlfqXslN9?50>sxzw!2i^R!L*5T<!?=#
z{5GKfFIQLizuYzA|5_K0CQf!Pjz<5R{<GnKs*N6=$wcBd2R9!PP&vY)EV!9O#b2}b
z(`EcNy-4iq>^QnJYH3;OlFC2NXxEiJKg54Qfw8+01yQwMM$_Q_lKJv=xw#zb$Is40
z$PvQ5Om{ndQi<@ETgo~)=W$C6JEco|vnd`QwpEio>lZ<^8#W8el}jJmZ1`;+TBq>5
zQoQX2@N#{ZPD{iYvd(YvsPG)VeUgkR{etzfrMq%;c6xsG8n6@#GMXo&taXyXFJA;4
z<&8=rj>;{Pu`Vv<c+NTH!X`^+H)VNM!2&E<#8;85e)1-&kj$CF1N-o0dJtR9lv+OT
zW~zHDDix0J%D7eCf$;au<)=YhHBC8^e&YH;O4zoQ%xZr}&8(ZwHD4ob?c@CB|N5v9
zO^<3`G#1DJ5{`1xEiBZH;v@i_CY8T7hxz4*`9`gb{zRttY^u0~?nq8l@|F|&)#)GA
z5@7MMiK_9`IEGvtg&7Ixsf8k<%wIk#WtBz40Z3cwl%u3WBG^s)Z#Tb-hdoNNb#v+W
z+HZiX{N!(RZ-z;)BbbreaTbQj#+LbAM{?I>)==X4AMAQZ(TW)^V`-$kQh;x7qAv9Y
z!8_lp^-M~su$|Cj63mc!z%o|>&Z(|I1UL|P_VfArfjlqRvCJaJ2X47w?f~Z#Z6|+p
zTgde-nYPKKotIYdO8Z_i@76@3ycS8~DF;;TmhQo|`pb@6M-j8*e^g;Sb6zNdy7fRg
z*mbp5W&~@bxbisBx4vIBjP3Ekg_}T`r3^-v>0$4u$HaBY-a=JY^L_~}^meh1LhF0L
zzPNn1>h8Ac2GLh8@s@SP?ecT8Y!S><VhJEY=y}5uFY-qNZoAp5;v(wl@*B!f88IGD
zmj?Y%u;i8@ruI)c4<*wX;&*JwiKi$3;l~p3|NV;V>$(dN27vJG*eX86(v`Y@h>S9C
zm{KIwiNqKOXMXm|UEwNirrEw!S7bukdsnPXaH4QPBL&?2&-Wg!GStip2Vb7O)~mJ?
zU)zNUU;v;&9WmeZ09kEh%(q=i3IHT0Igh*&n>lH!_8&L!B5+4RYJ(}2dbS2++r+w&
zJt$Sa`_u}wL0LtVk3m1i<^y7XfY_U?_t17xTNsgP>Fm!3!c<OsC|UnFKkF2nI<5>;
z*ngMY+eZ3*uob^vK+(mCN`OvcT2jPg{81NgiixO5u*ohOaziIOCXD&VHezlwg8J-B
zb=TgDf+tr}Cbs*GwT{Ojg^_cl5j@DbCgoZbv`>{yczXEAmi+DleMry?G$)=1Yz7A8
ziQ5FB^SM4(<Z7Piye+2#q7G+Y`4p$KeMnPzwCy=dvPE_TW4KD0(H?uDz!Se78iON{
z!(^hIc2rD1vo@(hm#0q@qO}OL)o&&)P`s5>Yt>u-n1aSO<ORk>(FeR<)GKgaSaIh^
z5>8j#?&n-ite{6=R9E~h-^!Fm-2p`v{0{PXf_ReQJ1gQs?9-^7Yqs3lqG>bbk)_TX
zf2Oz6(Q!NC2^9i>%L{SYNWi!#;if;W5Dm~UjeA?&0-<gR+?0kZZ&QZFnfdsrm3l)n
zks1U5v;A0F^uzrHqHb4=uz92(s>UyEBF(LgIK5oO;)m)drrbx>+2$Pv(31m{8leDt
zOLcR%{a4*7&@oMcD2;vSsq!%5&K*gG5peY^G3}C!nEZ<bM1{s!Q5k)_LEZ%QcQMqx
zI~Aq+?ju$HgsZV=V0>>wVo0zf0}^S6kjKYL<u_oD#K86Xg9Uefx#6NLI_JNLliSc^
zLA5upwt1_|!J5s$lvy;td4v{OE`(Kg{K{fS!lM&%g*k3vX2#Dgq3zicuxp>$8;`1b
zFbK@WE4Oy=+3ff5T7>WN^`$r6gf#4=E2eP1ID0<x$BaxGZQfTtm2O~=VC|ozhYA33
zk9SDsM!Y`XyT74xY+fM4uo=CRlii}wIIgaB<2!A(IwEdA0K`4$wm6W~$g;OMJeu()
zrZGG3a?Gy%Gm=s;@#=9H_SccAXr~saMm4X#s*|c$+6!Xx4k8Fw_5ng(nhuy@XT(QV
z-Fzc~LD(Ux%vj1BkGeeORR}OjpLjE`LcAW#-U(*X%;OAG0k;f>NV3K2J##o`0WFd}
zd|zPgv}OPVn0gEkhT%n&<Ci}8kfP$wJ+nyGr}@_0(AHWemy0s<m2ITV@+(VWI6x1}
z&JHMkf9q`fzU;4LU&DPq4b=R>BQXvbU#Ert(gsJVGYcjb!c@j~s<NV#hjBNKs+*3B
zH40Mxg}sLK)zdeO8}h`1)K1aAUDVLMR#RUwC%&{INkXkkg)?>p@SpA+h_c-(C-qQT
za?T2yrP>=<rwU7KUG|#YCr`ekrTqTE?uM~wS#XJ(pIzu93GE0dafG3~{}<kH|5{6H
z^u(LmdNGeH2k|2z{KBrCu&iGIAqKzV&+L;d;g2jIFA>|HZ|?YxU3pr0iUS$z(gHli
zkekc3<qy&fo{3KZ2v}--v=8d9W<q%V*`X2gjQvt>%4%lfo7WORBC!MmKaH7r%vr&v
zGa?#+AJ1ku5mnfvVNvu)6^QGu$l>K?X5fc1+JYm%wH&PcEK%k`Xuq1e-Wd@clQgpw
zK*HZ8JyzmP1l=T{J1_K;n-O2x)k`hlr<uopf}!Ev2fQ1$wJQ0u?jCDt!Rt7gXV>Z;
zlcE!cocv(k0Iq+QG>nh3=+Gr+!@GC{7iTp~;M!h8Y%&3Zt>V0gG6(i|h$ImT(g=>t
zT3P<u+sU;DL)tqsFC0ijU72`5XCvZQf`j_~K@fKl-0@Yr1S3k<QJhiK?V4;iP5j0A
z6#o|!K$tL)<4g5$$z9)vfl{uJ;y54vF~p8Q)E&2oY`EiH09XAPdJp*n)QIvZ#f3e@
zR=~DInuNZx{-6d07|iY==xZ0}I*J`;u1EFh>;`9!775vje#K;O+NBR<i$M=mA}bft
z>D#ncdJk^YRo-lg<Mf)-?Hz7NHCa-qWd%7Skw9a~3(9tegX<I}gvRDtkKG*m69r@8
z^l4sHYz>?tz`J9VcQSLt=wq_=-EbE#<dY@El0i%;vz1tKZX|wbHH7e}bO+C6{n?CY
zn1C@K(!v_s#t0)yXVpUmS*@-2_^t4yena<`TB%)%-W{)HW7nl0=FL&8YVHG07S-KZ
zdn%TOOSw@o=-GoAsgRUGKgx&y0jR3}8D+3)NWMI##+H2UQg~@ZZq1<bGCpdRGz_JA
zGWN*>g^maeTr=0#XBHIeYV=dQ4CSD@!A5Tc+6!inF2SiC;*)Hy%1AzkH>cXC+_;x*
z)qD)H@R>j#E8$p2{+d3*A-->!agx@a2;Bts$LNyR74Q?AG@DAE_;$<5)gIM!H%v|X
za+pX>ofBz$q_Hn({OQ84!<VJN^3;_fKXe+&*(6Gh18)m2Ep#rk<cz9u@go!Hom(=0
z>D=E%L1*2yCHJWlB?A%HJB^lJH|HRo8$-{NIY~wpze~>fNJi$qU-F7AN>#@RL`>)E
zeo%SUU;xYLI5>QU)S|%hOV<X6!V7&%k7|VcV8gRo%LQ`27XA7AZd)A37B6Bb3F6bC
z9T<HAG1&>c8+)8*7>&0IWDbX&ZY$TfQsx|rcbv0`@^tcc;CC|-H6CI3E*4r4*C-tL
z-!IHXPFYRE(AfJ)pbjS3w+>>tg<9wbCz%Cv7<c0V{#6JhtTje`N#Jp%Bh;&fLwi=>
zGU8baT2o{YD^g1{vHHH~H+Q@vS_5`oq<dtEcyf6%-rgZfSSau;WHS?g*-A4!urv3p
zHWcCrw4;Am;YzQVAMr*#EhdY(EDR|A&WL%{44Kh7)=~h7XZTz!B`{?2Pm|~;76ucj
zkei<Ob=~SwSDfPmQNkDG?PiHpEkH-$7#K^$!sj&#sy@%bbaP`{IMgT=Iu-QyN^60@
z8!P<e_$}i*S=*FFrVPeLOa`SDh07*j)b%G=+RGN?tGhb@j5}%AbRxZXCO7@Jv5o`!
zOjRUQqnP+2{V7OGTy-<}fY%norvSRm#v&dP5_xpaK&2_F%X3{T7CTP?82RRb$Py2t
zxay<JsgsN%ODm^f2Xaa_IlB+R!rpYM>!s~E;Mc1On~@4s2p~B-m<CClVZlHt{-w2A
ze7f}8`;A~+oXayd#45K3;+-m+f|fj%733Inv|wvG46W$7tRkjCBc&#|=0@p#xAgcO
zs#(F6R5w)z^q%+|3CVnmZm5h|#tfW!L51XBoCAm~(`6w;NIi%l58RZ%!dAd9-Z?C`
zM6INF%i-JgDt~}V_FMR}gk_?1SG=ktx%GAIWHtdxp+{4(uqhegFgIT^y^>QR-Vc}a
z$c_$t1+9*<x7czJI_8L=u@pw!oEvIOqGn$jK-tkp4<wT3*f-6U`CG9?*~SD%s-71}
zxk{ksU??(k_BTTd9mni1Ff2U~#Xsv)*J~FrxTC0nH2QjcdwP6ZLR#8x1L6hhBkBZD
zA@ITE%;vC^5XF=|IYz!tcdbjYW#E+*ll*fR-6}DiPLgVvl*Tn~YgAsTHd!wM{z3(X
z8+$EjAu~LOTc1bIUpSe!3HozezLmv8Bf87tvClN~VF&o#WGn|k0V~7qmSPZv;0_D4
z4Ub5I5yNO|OecswmFNT31Q*-O;6cOt5n}Cz)f{j7EtP5e)&`4YNkog$oG46zY2?da
zie6{yb>sR1ij3EuKDx%?#6Inr=xrq!RxpWL*xYf2zX$PjbK2Ga>QvhDOR&Um+KNVY
zPLFld6Ch9ZHuHSfkFtlav01P*D&lYj0OX5i!93pe=TS0pK;omS`e33Gc0nnqc#Z07
zPC&oMCgkW&*XT#1DbO>3Z|t<VU6(B9Y?Vwp>4RHbE-x=tT>hzkWx9aRL01b>T#vuX
z8GJQUQ6l=ue{qA8<V2psSvlo=65!qtg_xczbVX{@wt+&mrV}9K`McIkp+r-Msjz&n
zq7Et=NRPoKVQb^hiNmFl+)ccWEDZFu(`JBNC{O&$vE@2Yj<X$eXCV|;1SLRvXFLP4
z{ng}eQH~&V3dTb0Df^*tom~RE{t*R>zFcjqWAgLIFF$;oVN_M%bviNPeL{LpPjGCK
z&l6fT*m7UDy}8GVwq!*$kzZ!@XeUp#K*$%J6^RlN&Z0?S`J3qGo*Kc()>u4r!g3hW
z%#U3<pl?67BBnD4&-bVWt>T><WHkVbl^Pa}xG|48QbU|?p4(9*`kaEIll76<Z=<Vc
zpmCp}pU3b2ch}=;6{Y5i<FJqS*6%?NpI8Mv?_O@pY{(c1Tn>iF<aaYNC;!IS6^2Ru
zs7W*u1zB$BwHiG5QE8SqPXyfgbeK#l`zkSQ$|wU|qtTd}%@PC{cJwx5n_W`3^>&Jd
zAG}iL7E8~W;7!MKg!{ey``IWhT}Np5oSi?MTUnmsKc(7R#*@E1DO6e3n~gCd|K|B?
zb+YtG^O9~elD3WXa|NtdR2Hlmz}FO!9HFT;N~#=H@|Dpr@5WcBj*Ilc6n~a))Ponm
z_nS>Gq2qQM5W)M@Hx(p`PeEeZ4YXNYw}IXn{y=Dhx=}y(*%GBerSl@@&?$i5J&x(<
z8dVP#&3uhpXY^eG$HKd8uzI7X>UC5UVsQXSs|<xPAQLeQh4SDI!2xz$9;~_!L*r+;
z6I0x+8~Jlkv}0A3rNw4gq5_1N%)3E*KD}nq4vBmE?L`J8ca4Z^kd`7^B75u5??zSj
zT<LSE&90pD!dZuT8UUN$|3h!9W7RcPOHo;4<0EObA!s`26U@chSm6+qTP1LJ$e5G!
zdl<Jm38)@E=#Er?)xO5Ps&eAj({_y!z;OjFXTJ+IqW9trPlbu({Bp=u6oP9Ux%ZH6
zuGXV)6=q^IgW6>hPlL*yam=bj!st$;Sb4NtAB0%mzA*&kQwtU~`_<W6jGEc{N3^65
zzN0GJEK||{I!(+<<fL(&ttRBFoybS7S>Em6^(;5(g(EfOzg4Fpt~9ifbPeb3qYhlD
z<n|%yI>F7-FI+~K^7ckVns+5nx~5sfI)_kXRowbX>UT$<RRUcWG7ZiSiA|RFg>WDp
zVJ$e^*ublJzhV|Gmb!uO@mk?Ij>E}@p184KG7$VkBWi>&MsfA*pVu3a4ZYKPt618H
z@NNZ6`halm*JB{T!F98`lXDt%49ZHGM1!hr+-DEEJe1|X9fGwJ+G`TOAHVngx4FSi
z|JJ>;OS@h5%^j;oKwgaPQdWg3xOFd=vRWf&yY768o+-(%tFN+Xp0NgHjL*k{ed02$
zOH9IdPPN43?(c_2RFDFSS&(w+>~AJz>o_p};ZHOm<GEJ+Hm9joLsBym9!hW~Sr}AY
z_zYo0)+Pe}bP^A*Tkz7c6MpHG)&-gSXj$!nXy6L0P-z6X7*BV#^K8bd#>Gtqt1M~=
z$GI@5hWZxO;ZqqZB+U%Y61qpWqm3=Jjvw=Ny5Bhdc(+V~*?@!585)1{$HC?J*Jy1W
z8G<p7JD|zT=Mst3rC(S$k|MzI=ld3dflh3}-tc&OGp}=}#hu(#A_>-RNymBY7H8g%
zo>#xpjr7r2Q{Ba9Y%W*K5d4Y77Xhf(qwFDdP2<vqgS2V9lAWe3<(;{`Ozqab5cl@9
zizeGBqk{7Q)85Enx~`p17+z4PeZ0BmyeSnQKQ^Nv1k6p8ltO1$EHvFhFygH10-uYY
z7iG(z{qwP0Nh7Hyetpw1riiUVo;?X0>dj~^)^w@w+{=c#SeP!{ofj(WsMptGh68EI
zdr^TeC#N3fTfJ^D5q9SH*<Z{wqthTH7g&ZieNd)8)qqr2E_^2%k)HDnSv7M!nPznN
zNC>G@t+=8^G)=L}fo}<OlF!kkzjYo!{yq=8gT4UcTMGs-v^T?eLpTx6@EwQ*;WOh)
zNXOTg@Zf?DM<Geal?KR6Wk+_Hm+{5TxarO@$jiF@%E^E5oM5i4{XGS69ThU%U0%@<
z@J+3ulslw0#bb3iJ=iwWonlRBC$u2O;kgHtoQ*Pk5~F&ba%;b-T%Lbrc{>%H<G%K>
z7nHf!)lC-*`;emT7*^`3uOh~H+r(%r@#&m=WEy-1^vey3TvX0Ja}+!KTx&wrOHawF
z!;&DB=S8{h{&~)PBH}nBX;`3ZB@Y_eRstQ0+dBJsHK`Psn4#)s?aas<s6Qrp`3Mfd
zD@6bb3xfGdeEZU&jPPLy)FZX=@o=W4wLdWsGr6vx4U5xFe!R8ytM#s++>ilZvO&>d
z4S5~*G=vxv$NUof{KxTYgks_<Gy9#x>nSpeGz(C}zt>k)iAuv~j5S6XoCu=T?M$q@
z1p<A4Y+ku)KGF&uo|V`oQL01Qk56)0zS9$_EyJ*d;XfDYGS`Yb-g1j8<;a_Q%6PrQ
zMzEe7J+7p#f51ndskX1-<WH6(Vs*LfK`F6EZCPW1^cz&?m%@F6ZAcy*6+*vwRGgg*
zq~g3iFv-0u#*Ozpuk9ZvSl>C%dk_H03U}@1LTT)z$8g8x;YGA~na+U=3ys{9)<cY@
z*I9^siIsS4prlfFf%~v0jT?^Gy~;vs^wF+QO}Dqz?ER)IQXWMM%s&jPBVE3po!NP_
zoq`pt08nK|d{*9<D7a=N3{ly8fEiR@fCIFttO|$*sg*UR-&2sjAD!I<ZN<>B!<b|u
z>CxW%Tgere3we;1P%Mqg^7N6uZP4k(Dw76f@{SE6W&!M9KUoe_W%hq4yh%zhRyQI)
zF{B1kO&|VR2^*TY!0(Sr_Soh7+yyX6Ee_F+Ems<RH<LXk_2zsq9pUFKitT;i{_T=9
zo8P^w+jI(D46>XxvFpKJnPswZ6Eit*@;HqAC4eHn0=9#)NpDeQya2%C>;Sr0<5r5E
zJUP5$Za0e`sCgIIQ4=Y(dSiZY^kT=zLFS2W(g#EO_~mKYXG#9a9sf0k`sr)=@c`JV
zqSXlP3_OgfV!tZ|dwdcxvOQ?j(HVjBWh|`Al0|Bhu@yYD#q3x?7rMT;)JOc}wKmXO
z<&b(#@2Bly*$tV*8&Iu^9wh;1CTl}8dU_;;DdN)NGA^KO`x46U+3d79JYDl86rwkD
zew#qvQ%Z0eTzmrTvi~K$oT#PMCC%YH&v4`Xx2{*Q1z&s1F#W6Gy0|$D4S{Z)4&!>6
z?^HDt<-mXT1C4>q^Y-9M?WtF>#Ju<|?N@}O9lGO&l2bmhpTmqo5Wjv<vzgE+v^zsA
z0vLf`&q^RzC)HZKL5(|LiF4Z-Y}^-%>d^#^A2T5&9_^Oxr!@r`MPsmY_kS~oKV35{
z6`<7bs8jU=Pn0!=FG*>QcD2I`)5bcqu~MQYvo&TPD6SKDJfqths8M;zFTMuzxl}M4
zV0Q9Dybl4%umNY>MFWR~Ov8n*J(<4q$1JJUGPL(23TH?<N<;PuadOQ_NqWi~Wo}&F
zg#c~c>0m36$TY(b@C-2V<uGco&REFzFN!_~H?%^TcHPZe-e_NvR90OGE8+j*7%^Sg
zB;j=F5ODr3oP{{Jg}{4s1;57NcWp|EFlu^5&fW7}fu798b8OwkEY>|Zi@_ZvBH$Z8
z97oWk*ORSVm!UpEn_?+&RJAmR)uqeC0;2n?M3<mizBiY1@8Eb4@&cDg$BOK`kUG!4
z2Rpz2&dkZcB*-7l>~`Lxwv|5qa?@R?_cr|OxEVoE>%qx1>p4kh!nCA=8u{;$jr87B
zFoXy3->Ld%e@w?}mFka5kJO+LBdD)=L8l?IY*?pPH)4^(>lPup_b|PJ-&5M<0%eR<
zx2}g&qPYDQaJ`6{{vbg0dk*Dw)!yBwZrgczCOq2!boQp?ZzEmhq(y%*NrLRUYk}gb
z39@{W_3pmT9d`~%d_14?W?-JezIB^+TiA0+m&t^YYC$vL<cr1-cu;Fq-&nPVR2KbQ
zH(^^<H?@ASPu**t-=V8%#N%C#R<V`F4tP2b$h@RztDa-yeYUYX=6#lR^aY-<C2Y%%
z@`R9r;jmbOgmjRb<0FqTot{p_+2pwDU{Y7I;!2{sgG*(i0}zn}MYtWxX*}CYw2n}j
za6*Y5gtletjx}<4tChO!s5A_O$McpFrTZqvfCGYs!nr`85?09rjK(J$`8j15MKvFa
z35$IM$FU!rQl-e3MlOkCLd3A;L=rBS<_0k>wteFNHSk#0GQpo%W5S(~KQz1o1!yM4
z2A3Z%qrwQ~d9D<N$x4gc3Kfd-0>u>C*I%&zR0zi`$mwCui}t}#QZmHm*5f<lB90*R
z^S4`3XuanwQq_cXwqP(x%U;v8IP*=1Ac(I`iRpS@&AWYl4EUs7ecN9|{mSy5)3XiL
z4>0ez5Ml%0Fg_#K@;R!!3sh)aQr38Hts?t(f*p`4&JqeJ4b{2qEKv34@G&IA<0`nj
znsjs!pNd8}B~7Xg`z-O9O2A#F&ij7aDTYyFP@hoQOh+}KR9JA#ZP*|g31|CkhVNrM
zFU7Kg%FZ+oV>@~%>`(_A5sXwlT#Sm%bKHo=FcN6nNG&+Lg`y4ycy6dBZ$;6tz<7;_
zbyF1ATUoxf(YX(f0$011pEni5rEDrs=>47lmn$%K5>l=TrGKwZ!@3I#@}28AK!o{B
zyantaE-ALa@9(Lf4Sr(t7D4Gc(4EXuLy03eNhnZZHsb<FgWu*f@+BEVsR}7f8U3D(
znCn^Zm1;=9E6axaz{YED0uMfS-?U6Lp+~UHVLQc%%&ROG$%chG;fkY{WtJrTO^qlS
z72|F`R{i9Aqw;8+3*&ig^wkma_N3LNzp2P-S7dl675a*6Ew?r>mK4}9h%iGboYZn=
z4Bd56n;eIAx7IF?utMgxDf=ZZnT@yA*VVB5TlqJp*P*F$J&lhEA>3t#Zl?k}f9}7d
z?0a4#-ps+3wrqv3G>aln=e1d>i<|hL_M8)fU`a+C5fW|I2gbjmWBlF;#ocYyGt{Qr
z)VL<c3ZEshK1Xbv#GA1DHi4a$a(&x1CBFIkL%MaCp4p%l`ARbV5^(yhm9}3UTq=@?
zkev2+;o&~t(<|OpEBMo>5goaop;*7E6UxL`Fk!n6O9>t}(ENHH<B15QeN|f9OVb8{
zPD*ZX9P!0+=-`JK-bVx)m?t<;okZN9G-pOEZTro&9mC!<C>I)8fcUPJqL0<Pj68?h
zo8yJpD9wf>WYe}RV7V(uK{noYa#q4Y^ST}i{$Wm8{epixdJd2`br;Ynr^>uh<NTwm
zS+c>$uYj1Hc9`qs(>10s_n4zE(e-Pl{+2!;SN&1P&I;n1YKq>a5HXYIxglz@<uEO=
z8*Pl-_ZUvO(AB`Sy9abFKuj|+?%-uN+19?p^Av#LlPVr&lxv#3;249Ks-ObdJ-M#X
zWEOe(PNGA+Rke(Wi1{2U-{OS)nb@hQe@s-<?H<ct=rU$i|Kr;Pbsq)Fm3A7>fIPfC
zCB%``rya6LmWZR8{(iC*#878<(KZqMEiesgwnWzm6(eV6v2fsO1*QoPIg~gr{`WQv
z`mO=%SXBLU0Qrt_U1DfNIwROlhYlQlcx-lL+C4Sh{o0-$S|)mKzor&oEYJwU@L;Yh
zUq9Fva1yoGh|UZD4!+-^Px-@E&`-N7wK8KTRB8T7N?Jfkbw|S#DNfr4+IL~wv^kg)
z;F3!f+D$w1m?bBRR>m(-AkPw4ItPwEHFIc&TG*Zy2I>=Ze`H3L24o1wNy}=pH-;cS
zY*572P*yh&3S+7qPwSI%?7lq^G>I@+>s>dkRrL*kOZp~3Uj*(&b@8#HEhx<&DBkBM
zn#|KEx#6VESVRm@$q$z-tYo<mwT_sm5TstG-X8VEGM)*KvOz>%R~(r~x-<GW9y#lg
z`r9ZH%nm>|yfPXqW@rO%^=O}g#OQXxAec;{D|ZhRAkgu5aaJ5r6T@<Hx3Pq*i$XyN
zbt_!3fJI*M9cf1Bg%Kn0@V{r+&#uLTMEeLo##Z$|SRca~?s++a7N%H7{5I~k9bS+V
z!-V8GF^JSg5^&q&4ND5fpa5f=rD(-!+z6>eUYMr9t2OY7K(0(wY9_Xb3JzwbqcsO>
zPr|PTh7ZtcxY0bSK2{YnA9WiqubcB+%9||}2xa=DGt)fwB?G$nssZ)7ViRguQDpGq
z^GvCU0YHnJ$}RgLTINuHMn(kQKBbCe`$X}2(n0Pdm}RVp?Cxu;HJ_C-{@n~Qnbp03
zk3*x#@w(Q)7GiRUNrJ5=d>bmJR{?%00PR=gky2hvQA~i$X;7!yms%CX<*V5a(r5{o
zYC>XDa?d<GzDVMIK&kt}CgjchJGEHB=So>aRN?4YXLe01&Ai`vXCs<&W9n%p1zzpV
zj!fF*mdDdSS2IFHWbEHEGG?WG(Z7eX4pr!i`Vuc0;W&E7Ll$Gp64;J__qmI|i&jI7
zMT{$iWX@)2H<sY7pqum1my;}v@?5T#AW0)?rwe2Xhm~s5dKtn{zD0W_7%<hm#KCiC
z#>+pwl<3<Znk$nOCAEh~d!)gNW8Wv`ol+p6{M|a1d8zz9ghtJ9qkRI{t>4!#YXD0{
zQCW*WWH}K(5~6G$26Umo#x5f5K`q$c`N%`Xnw5Xm#|j=wK}#8Q9eGW|pkEr->(J>e
z($`M>r)3o&QslO>YJ`OwRO-gcrTfRB8SD=F^C7P<`+KffpMeU30|;ARLVaGK;OKXv
z8^USPiAy{B17{)*pdp#?%YK>*M2&i;(TsvW<L<AmY#>=m!fk4|ucjb~MX~bq)Fwgs
z9Y@FfJ8>Wy{ljcGUvmoD!c7n=DE*V#y$@wNZHxikqY~z)1+axq;GE0T5X8pBEA=f+
z5I>?%7L5LbFtr|eO!iub@w`mqDwOWJ6eF|m-45}O%HTZWUSJvy`EkbHSv{l(Smr*@
z!O|H&h=*9`Y#vWE=OJ2`SHhl?;Tb5?2~id}V42QXFh?DQkW^_jZy>VvD}ozsK+kk9
zNUg>IeFS)Z`;{Yi+P078UgsNfZVJx(wbJMe;v|?LKyhhOHf(Awt>2}@(I&HVO@%$^
zZ+>=W3%dC<ImFDM3hp-GoODnLd5g<t1PpklP$-il<GiWzVlkZ9GV?HYRO_=CQT!_;
zqovyJ1XQ)}5Yj@g`DgjFhea0n^*zugTs0=J{li^Kz%3q#u;b-lKvQH;PE+bgMC(F$
zWH&Z={ro9yikKKj)J^N{hn+x?117bJbN&0*V@*a1dBsezcYwlLqg;3|%roOFFgfd*
zqJXTi8(<c;;~DE}PqEB(+lXx}=d;HFZZOXuf%n(KQtEQ%@I^CWgw*xB2LjoQYX|U7
z#pLwLg4DX-Fm@wvljN^Uny6hHJEdc*@GGksJMD3DCpsf)t7~^lDA;iGZlVnEBNR(~
zl-p@#(XTI{m^p|k3=}<w^|bki`DB1RA@YK=&vmDRe^w_wX786r;F49bc;U~*8}ol9
ztaKIt$mcjnG#1(y_oZw5-oBSicbh56{6qbU>fz#S!ar%wZ-h<6^#*OBh;uxy{*@MM
zR9^qHq?r%?^!Y-wjvq?wT87@Tdk|79=ilE=tj@uHZ^}9~IQo>wq6x;lPqrKhNe@Fp
zLks*=15IzCFq;96S108r%IpiSixycL$`b=x<meM$q`Qabxg3#oUR1|>{4+KfVQ=1n
zz-3QypT2-pi0w}EwVr)`vxCRdE!?HvUP?vK2%*ZK3JggxXUfg*adtiwKf0TO)Mx8A
z)04_{A%!U25G0uUeY@Fs+CF$%8TuzMhA2wT1$9^rx0y<1pr}C^U>aFJt>%?*N+LA_
zt;F<C!I=A0lXv`OINj^`Y-wZ2;fO}DM!adOZZy@czm-e@4wfU^B}t6X_hOuE_=O=l
z_sRNWqgt=!pYy35XBKt*W8CT~I(N-_R;LN#^^%>IrrYPo`A6&npCW829sSmi#=9>d
zCJ_Me+4oH>{z3eh@mV|D-Y?tzizI=pJ6crjr&=mw?RGmu|D3Bz(bN^9n|!cxEDIp`
zkpSp!Q9;gJnkmPr{6>A64R70|6a#UyLEUKD(Z5g&Ud$#+%A-hjhDlO%5Kqsr!L0g$
zLZn0$fdica!)<Y4Z%P`t{^mf2?dK}Q%vS8Xe7zsnt!=S9*aJK-%Qxm|i8Y1?rm>jE
zNTJLIOdcjcVVGK=7MDCW{>P92H(%dTSvRcXS1UXFKfdrk59h~|SvR)4*%}<I;rOZF
z-`Gs(BXe1!#c4Kd7fW#bvzYpjArN1RWD3iDaRXGjzLWPpOJl>r#j1c+@at}IH-72V
zU75g))<TDTyAR4J^lggyc8zUqF*xiiSN)LlGW*dycbP^t8GITdL?Fz{T3LB1rUgvD
zo5B@>!C?DdH~N8s%5n@<w4AV08E;(U;Zbz1bt5IN|EOZNp;Sh=eh3%6s953_fVoCC
z^c5(4II?0Hp%)Rss}c+~v7+HB>lw~_`7`h2=Vi^Cq0RJ<Urf)=zpUs!vlYi<juIvX
zz?WN;>)5MTG@>B)O#=l8X9j^NTN31taIur~E<G5)Z+qp0*>Is0sy;c65r67kUtE_P
z!73;xwfbvK3-q6d@fCoO-=M<zX2c7qkD)CdQe>K{8|h=NEl9*THQZGplwbDq`a}S;
zKY6VsF>YstK7nhSiHsAhChbr2Z}x}l54|^6wu9s4@qZ^I$)uLYh&ai5<^-f{!KGqb
z8d`(gIOy3m@!}h_I;thLSb^n^LCa}S)Gso>41dgg-bM%S8t77Riu@~ek%+rPxS>Yu
z-e=u*=DRHy$8&t3U+$<h9%oL`l7PyStk}m?a+D6)X)r4(CM_8)<k8IUh9OucY528k
zE~<8@nFh`i*kOG*ZxUWL7{5khW%bPC51cpQDL^U(xht}r2sfT)#D7flqIkRJj+1iI
zlJUNo5#*zf{NXPR$2rQVa-7Y`m}=$aZ2c=^05+m+Fq!o2ge|Pk0eB%T{jMKzUG}V$
z&yK>7{(77g4f`_vIeu#fVd00j744XTA#2hySx#yY5+qQbXKxY$`*A{Gjkm<`j(H(i
z)jU`p!S>Hmd)Y?)Dg{@@d6Vl+%W&Vr9}yQq7OjjrhgPYFL}y0l^`9{F2ev|KU1C;#
z;>&u@V+KN5b6&luHeCt;KFVfDtM#7(DL>u(ifbQx3RF0{{G5EC4=#Z-u^5q)L={Um
zi5UbFivpJ3h-dM!DH}ad%1NRV{o=yAwB%W4k8z<eMvdcd^~F_wKAfoUn)_V<ZOY#?
z&e<ZDnoDo38R25T^eEvLoDD{O3hIR=I}UAvCesr~QQ}#?<Rt;SXd3OkpW|zMj#I}V
zMe0jBm{DvVxV<Wi;G;|NSs8dye;aO%NEhRbH^r7AGp$2;gR=JS%)(KFFTr${6j)10
zf+Qw*tT=Gno=JKHuMlgG-uR~_6|X!c)`A}Jhy3X#9!<zAy%yRe-6Y~e?E#r7fRM-B
zcd9Nd5p}3lwIic=hQWfD<f%g{S(+k+gzX|0kkR>NO@)X!h4Wf8s$;=G_My|t(pK?n
z5Cyw_1R$?-x1WcuAMpPuVBvhP1mh_I00d9}X9aBY|Du2;`>zUECuajI6LULjV-v^!
zZo*vrzeTVl&!ZMG>i=RlSP^<pD8hNXUI0CzS)=p=ni<x60cc`+tSMpz6|Y%E@blvk
z9}$ZAWd-PZ&i}r{N@%rG*SItl?@f6>e9ZZEE1r`Ie^K!?)Qs<7wwZO6g=%*<6<=iC
zEdJ~IrsCbI)=jKgO&Y81aY(Uf=^?!qG$SJUdU+FA@%AuZ06icN*82Xp$B=2Bl!H&v
z%)acmo}|K3fp5OzR|OMRMQI6@!e+yK*;u%&<S(b`Am9BKQn+@2?%WwPowANq79bV%
zP%XYE{>)C!F39_3*|H)@bpS(LAX2q*G1?^+=4@rFHN#bx#ZcXHvWy-1MP{eIRK2W0
zTcKHK5qzDywsN?Ow)yZ?W=@$?-*S1-`eSMUnyDtKb&w0i{mgYWB?fyctCe3v!k@^U
z1Zv+qPt&`Cl_wm~-FWE=L-kHH6I9zpNeigsmY_H6U1%Qs)?mSfJ?ust1ZsYgScXX<
z-2mSC?exP&W}gE2)t9Wa?MDN;goe+Iu76v_m?CrfGRqdA5ZK7DJiIfCa1*Du==IjP
zdkL|06p@K-vq>`ne`G2X9@G)GSE9OD&bIlemy>Z?Cq+Wk#aCn*DA>m<Kv;%fu;yAT
zOHdJYtkB2bONe|_MwV<g#)I4=uu8Iw&#Bm{JgwVnLxVLV2igLifPJ6DA9n4MFr4RQ
zCGP83w!A(B&Ijlzc_ebc&fawflh1sM!b3Y)QB{Hj#$?0bgciUJtsbkA1K+LaWwS;E
z1-p_QRc=_tcIiYg?JS*{G&w+Kp)@pWeIad;jUOSNT?94M)a;o<YLo#6A`}dRoxU>;
zF`OhE+;z&aBz-3ecWf-R-WAUHQ=TRC9aEN03NHgv(86iE#?}^opA<3H@Bh>CGrN}p
zLtL|rut->ePJt=ldm}T*1ryYdO-Hhh_k<Tv8eBvFN@b%oQ@RJVw=WmA2t5n742TRm
z3~Kd5B0};GM}?XbaYx)`WSJ^nTS_l9c`<ZhRaP4t4<rs!8qEWjr^m=yb5wa}q^hfV
zMYFbmqrK#~R4EK0XzFJAAmdSVpW5zdZG7luVR7~>85%kbtr)o9)>)|dPUVg7$>+m^
zk|-+@AbR<O7)y{++)1yj8biyy)%Li_=nc)JB4i8R>lArCa0T(u1ycdeF3}YspNrd@
z4tY?VUfL2dg=?U%!x|PAZa`OSsDYrSQ#H9cn!LV#&B0;Va>0i_olq7{51<oDX2SO6
zAXBakm~S{9L2)}Cpd6|ubw0cX8d<y2cw!k?Qu}bxk>lrk?s*1ht2240=<amZ%Z&mN
zCA~V1)O&|~MGr#KHHi{a-6!&GQZkP4m++2MIU^ygXj{dWwRNz6Y54$fm8tD-T8)Gv
zCB$e_t~7{G>SPLDjv;<DV_0J(8sI2cDkYC~up9YqMAmHcyaEEAph=6ERxtvCsuY4?
z3AHnp_13V0fY`mVICoW3MOL$1j#{Y#_?dKDYopl`&OGkTc$Y?T8jUjC6v|q2r$?!S
zE7x5!TLDZ8R=H1RWEmLAYQlx^-J}aipIp;{P+6Q-2d7L#v|@iAcFt~L?xo--%ket>
zPid_L<7$@Uo4TbvO2IeX-aoU{hunhizV~)XFvUdfN!6<Tbc9t$32K~}##MxpcOaSL
zx;_47S&2>IOQaaYw4uV)2B@6P$<u!Sdq?%kmk{jFe2gOjnJhx#84L~*UK1>wn}&Nk
z5t>b=F}!1$KYe@$&Pbf-GBg4b*N0knC@M?5otTy1XczIwUF_QENJ^px6Z=wgI>omk
z7d+>u^~OpgajvJB+CwFN46;)ZZ#*5H+~fZAa8()eJ2?F`Z7jGSbX|ku6TG}=166!_
zU-18dc?9rf21if;0A8g38Rq|2qr-m>CHaMUXA3*q{|@p0v(I74M=FkZ+~HWKkFXy(
zENf{{H3{htZm{Z1eEOD!tCOerDZT%0%3ccUP;|JluxNuB8uV=~-=8h^`2Y++AFR_s
zt8e7*#Fj9=DLupljWum3^=fvNrM>Ip<LB0y?-@OnC3sgMKHOZJ4}qO%F&FE1TW?qE
zSg)_3zAE2a$j{Tqum!)fhV}Dn_Hxte^WJsV4IjOwPETt~m4P3xyW<6XYe~JTr*_;-
z;BRo>hrjA)pJsbhOH@8M?=nknw=ST5Z&?)_{Xaa9Ew)rH7|frB<;tLX%0eYoIe3|X
zKS$vo9XDaBD(}5(m3Fyzu~V$M6+%u<81J6zcm`HMoab9B0|I+uWjC%dgEzDIcpnL^
z&PqNE<+j6iR=SX_``?0HejQh%s8S<~r?Hu>y`YM?VUTbSSrS)%Oal~cK1`LcpZC3I
z%1df-mOJp`*A9e<z!@W!oU9+m*ebx|228I>-`7+=)_7j;)@5#GH*K)n%Md?nLnB$L
zY`~xS3RdEe8)0=n9UR|IRk30`(d|cSN>0I4XJI+#`X){Z;9D`3HJmJrF|9sPQBU>g
ztK$lGUA}(rx#b`mm$E-|U3>(Byj8kt_Q4i@!A+k+Pe@}7zsbDN=1zPuU+opw;4Lbs
zpP<!Hdb9k#?P&}6r{3T^i~r8xZ#T^JT=iVXx>J{S?UvM(YHW9Z7zF}mdx%uT7tihA
z54P}JJ&T^>c#u)AVQ4+f(<={}mkuDjJ>`S`4*+05pTB|&i+FWJO2EE4z14;}@o(TL
z{r*uA^W5!q3x7Lk;Qck%pbm#UTtxTJzwL)#<1PHue!gx7cr(p6bp0*7lRfN__QkJ+
zPhb1r0onDiZD8RI?gX}r*NLy0_zU*gACW`oXR!G-+v}$zewO&-m+%DbcjafNHX<ww
zj%sY$!(Oj>J9d?4{}b2wtm$@>+TmkV1H6I<1s_Cl!fZ}#wLv2E-Bw$EQHB+Jc<JY?
zc*`fN)UcacSfsDU)AxJe&#IsBWLq`%Om%#$9gvs)>aRg$^^bf9E0%lce~XU|@0dvW
z$-4v4&YXu>hQ#l_fp2SE8CKlVYexQ}7oZHAk^E>Y^BkX5uhc;|#HUCtV3r0x0e?CI
z)kcyeqn_{?58G)Ndm~HSi*$mftMLiFRNbQ@q5a1E1N`4Fd1GrBMxK<f^JDWW@g;Rf
zP%Je{m7xJz9*9@%78P*&9m`(W-`)uzBtEMJxDVV%S2uiB!~sVTtDaMO!zo|EGeQbf
zdQ<5~_!;~a{v-HLqT9JgVLl;J;k8*hsp^e*5x=s69NC}utq#X&P;~mE8uYyiq&J*=
zI`qSlcUlqU;c7M&h~Ni92y<;U9oNWCy9RPc+wW_TJtU2~9(M)&Gibin)3=X$ogfNM
z``lfe*H1TmqEs~*nWS6L;-iAUBmNYu^oj%&p8MxcYY7@1@v2bwqomfM!p1*(Y~UCB
zjlE+$(jJz*KYhDx_C^o^Tk*TF%(Rty#(b!gYGc&9smU`n|64uW=y&jJfc3XpSQPZL
z(|@8U$Y070Dmg2evNR*@Aav8ZEkqW^OAX|>Z-51EMvX@#b!9(UoxX#g9rcmOwL#jz
z^?)uvy=U@y{@BBg6`3penM2P;+g^2`a_OC|BvEQnyf8L{ez(<oO-qo0a6bX{`c9$c
zr_r*wso=fC&EYTMQos;tfOno%zd&;-pz)}`QlxQ)emAHV3Ca?$1D!CnUU2Gn^g|=Y
zL7kvv1uA{|Vq;k?xJjVZ&?3KkGlZ;-w;g^Js6h-I{G07w4gKGJ+1*q>149zU8l4uc
z)D||{R$$xUZ(j%-0!$hB#StD$PdckRBJ0=9W79n_3-^{+27jCQmDeNN=WGybUEitg
zuaTjVXmIy;1Br7uubM_8_Pn+9sKo*(eAVOWJG^@M#{Qw_|CPL@mAnuuycZq3(Q&2Z
z)bE<{NcT1Ncd$qJDrmqh@<jH<p%O&3@Ss+S+40CyvHH{R{ssOYTxvJqGXi#J)o3Ix
zy{A3gOkmk*vICntxS}Kc!U$@klHrN<+v#9cS8lVywj`c6R%MTbJF=pv^|l%L16o=+
z_Y>-pORj)5ajL$uYTgQTqe2U(V7~(|Z`}5GAd3_#Fcig>(?E*D@9}ZMOQoM}*oK*$
z=_<(zj|JB`p5AxUT9H#$(SG~J)Nu!EHE=hn<Y;er(k&T*_9wmJ8*O}r^!c%P&#>gW
z{jah9!8y{yK$4i~)aotxXJeb&iIwu;OT&5S&5<`P&KyWEmYjHVEG`v2dLdh_f+v}}
zmh+_3@M(=kAE_x+FQ@-R(+`*(&A>{{XzTNq3Qf)4nY(x$!HLiRGO^VgPym{>A$~Gs
zoRDoQe<^3KL{`@;e^t&M_QF}CnFXIy6)3a`o{FmeM-`hSZ-j3A;m7~<QO5e)t0Tre
zZs2Ag8t|Mzum~IH#Q^FGYzL4wcv}2x#UU8BZ|v`tae|5WKn|$ALb*tHtDOy6^pdih
zh^(BS!KZ<;Rs4N?uHgdY1n&ArWMd;>yn55b*!Vp9jt!CETsZ?dySvoJ`NhPplTrR;
z!q8TG<A0DlV)VZ?Jp@H-@J^6jTd;YC_yjsVCE68t`ySpC@d%i2{gx>5tcp}UNQfiL
z1lV5g#$by({b<OE_V7S9A4&tTVGKj9CQTyCa65Nk_n|nOT6{G3gF^eB)EE=VSf{*r
zrRj!1agdE_bZU>zuT`iVxTu_%G-}iQ8q9@(yr{dLl=11?BiLf}&y;8B)hCj2>?NrI
zqTQhDsjIEUjQ{lw84lZNMCY}RuD9x@N8O&gCJVGrF@n;vVSpqIm;+^rGnCLuy{A2*
z4juYEY4jslSXQ0isZpQ3i(5W>=*~nODU?Vg0$8W4T{N~CUpq4etaf0FEy!N5!krIE
zrYvf4qhhwK>fjyi;D4bd*Nj^-==O@-joKP&pj}501dSIa0ry+?#2iEVstVjA_;_HU
z3D!a$$7`>%R@(Bh`PMO{!<HbtZMFBY*a3FAXG?&h1Z*DSC#}q_i6L3qnLwr0;yI6)
z&a@*DOTtHC__Gl*Tm=hUcBb3-GG8jVOk)A;(eJ4!vRMyIQMBPPFt4^YmmmV0_)D;F
zST?x;`_vlixaTN}F*5NVgB7~%ND9P<O%xUdn?b*VC(%1Q*H95<d`%n#6w)2-#;`<W
zuxCDdh^+@H2rnb*b7}8j5U6X8APm1@zG+Y2f$?ZWpE%SH4;Zn12miSTyJh>Jh*e3f
zZNTF{GFdm^L%rjF3zld95z{pIrZY{#FaG?^+mABmfgLov&f6D4poB4#I~i7|So44{
z5mX+<po(9PLn9O|w4Re!9Q0X?Ahc3=j+-c42Ioa#Nw?jxvDZ15#ru?+@<o<yNpsmC
zWbXBwt)>=4c=C>wJh?5cwgD0alCMRf0E`GCs5_3&s$YU3(6=@hV>nyetOZ*mbXIw`
zO>pwczCh#x6F$qQnY4XKJ+Ew6Z9uGoaf5-^y?#V-jM0{Df7ly-A5QOgAapiB(&k;p
zW<xhe-Kjl3IgrX2-0epj#r4^jGC}h`6iRY0QncG|c+;EG{gDyxy)GAI6j~6Y@>^0n
zk#S;8R&x=7aIo9RGvQ-HQG1HUVRXEv^>uPfMV>5EDYRw$^W%4M2b}D@n3@eSJ>c4l
zA7qvF5{(XZWTqj5;2v~|ecj3PVq(_0#A^KcTNZSqrZ|hCgHhx*^F<1;1#gHLRbD%7
zrR0FbOOZ_dT!CQLUVhg>qDi@It*3hN!?8i*#Py#q4N}N;WHwj|5rOUHX~?^<c~)ie
z^5kLkkr&?#&NfuL#w4v+r5YWKDwWe)@K{FJ+<33PA?-cE|A$H!Y!Rjt2VS>$g2y>o
zklGzD4tp{TB~ys|{QQ%*Ur5q!XZbi1oe^7;a>0)}?sj3pG&8sI49{1b!T3P6O%GGL
zs~`W8kM-jf$NJfz4iCTh>@WEkKM9_UdCsTz2UAU8g*`r}-NXqkVD@Go=D%2`4b1jg
zZGjsdFyIubDUL?l&;j~~Qc0neHq~SmDoLA_XZss_MWn{=`k}@g3dM|%4S1D*`rW_U
z>u|LvfBN0OVg3Pr#a|455#~dE)~<Kgn!QzJqcx55g*iF1?iha?28BOsY{EegR(BgU
z=x8PH#<>feT-zpwtC3qScL3JP*dT{mC$e#6G5#kTIOcXgkp%Rf=SEuUp=Xyp?7n%_
zgRFHziN90cr2c78slp49Wz+DRnE7bVpa!=9MK#_XCkM@kr;#FHhvoqPx-(9Y*$Zmu
zp(9<E#$<H2!=%lS4Klf{WD1q^$O?zU+FVE!oBH=)Qc@bOQf@c*lq{5QA&!};(S)Lm
z@kVdb2lh-c*Xg~r#IUBzgb;{0^d{e_X+%Y3jW^G^wG!oQd<~d=HE$TH*c^Sdt3~Dk
zf*l%u>hRw^3Bmh@=s!oba%RCfo<`u-{vCjk-rVh*9;{DVu)}@2qNC^mI(t_JsRAZ=
z`RQN3{CE>BXkL`!jJ0xJa%65Ruz=vooug0(L7Q)8WPl-nG<fL(!&?wlFJgbfc;xHM
zTd2_zY&yM3j_w{>CC{_+n`FIw0h`eCvc%>hR(|%mvDWM9sDhX3#e)$%xymi~z1XyM
z5_YU!*+=<CzIC$TAN&2Iv02S4Wz*3Gajk{f2$mB1!K!Y0diTgKv;h<@l5cI?87$E;
zu{L{O`^3cr(oVp_h;bs>K>s<%V5#x^lBGlTtr%s-7W!avs?n*8AoT}}-=m0;8NWC@
z?CR}0=As-z81JMUg$##AVKEyn5-%uvyZCehjxQKgxt%?i+~lPRzb6(%?z;oqTs_rn
z%3@n1%y=I<zKnn+&}x!mXo%cDX;iL0#E*UE%9;+gdUnDDZ5!DNSa~Wb9t3q|^6$}G
zE&s*Q8*8<U7t;GDp?$Qs_R(W(AE`C=5j|--;-A?XqTPuErr)f#Im_rr);|j4=Z+Oh
zOGJjzukg<`SsB(&FpjKlgP^t#7i_}9RZ4GJ+BjqPFkwBd3zC8N+mB62=kd<U<yU07
zxWabW3MT%54%6Tkz$_#<Lq{&dKmC3T9PU6@y9lC5I7fF=y$Ib7{K!mE%O)c%k&|G%
z7$qV9)=_9*1wlQGLXe23931ga&q*Io$TgHJW-jqHa;+JOn4(L?+>dfR+PW=hYO7;U
zfjyw>Q5{sK+rkKcUyqJ;tBp%^=*+>BP~%>0CyW+zbkXO<@-aoOCvNO76TU0bD=@7>
z!8Tf((If>&Us{qeC&JH}8ji4-0&DD4RnJsKCGtIJT$x#pl;GPn0%tB>8GV#vh`^6#
zE0!UHVy8~=b1cLq`IE7U^|@B2D$vXPj0`T^hwbWcGS}zDKpubrSdu<PE+_>LVTYte
z>^)I3dILX0j>rVoSxeJNtkM}Ol?a(gRGZihpKjeAO)h(n!3^c9=xt>tx+Y=i1qb+*
zISkf++8A@0?4}%(M1Z{?f7Q8EACh`}Xu6%(UT>uEcM6Ptifh?69N`Jhem7ECpMXR(
zrIKNLl`q1eH>Z5ROa*?U2}8w2a+MB^ux&pK*cmi`)QqkQRo>}4_I{1go^$?yBxpY?
zQ~kX4NoCG?nySPNC$)RB?5UXVS@qUm7~3K}+GJ(}?AqfglxY|+DLD#g+d6I~vWE0e
zuxSGuY<5lH<d=KaJT(&i^Tx*X(p;X{Bygl^@3>@h(3pK=xeg?iMS@hNJaT2g4tSaL
zE0ZKi2S2*_$)<Y!Vmdx-xb)dHN8KSK5%E7lX^F`?PK;CTV%Kuqxz5)ba8bfat9PDY
ziEm$^ieW}L=Ky9*&3#=|%D8d7ovV&ZS28ZXXLCnXSqfNr8kclX?%TJi-rKm`7S<c@
zPw$;0El9?10*j?`vAo<$&ppMYgyNEgDwKe;UyPNL5m`2e4g21KG5K5dH90BfK0w2m
zT(ONQaWzen6-KsvJbg=Dc^OukXO2t<k|pgz%1U?aleextLb;rkcToa|Gk^PMZ16U5
z6)~>q^P18jVinlzoZXJ98q3<rrf+sqB4alL{2!y)O}d$x);xda8>+#bDe$+2CEe}@
z?9&@CwTAvN&{nTp>4{yQ!?KOCEkm3!O`b#X(~-h*W`(aniR+#fr9~)<k}2Y;$o6V`
z?s#y!v&H6d9JRQwoYvA|(4ADp0azCcHi8}+P&%zB)3MHvH$eEGQa^N?)&Ot9gMqf`
ztIuD5ngp<ORUjB%R#XzvR;NE6sqVpt`}AXPINRD(GV=;QwvOvsG9~Ja%W?4GBl}@l
zI>|F91qzpkktZ25eCC6Q*aVpr<8P7}a(DWcx=yrgD>G3~5sRc<WHRN&6H5K_s!(d>
zM2I!x$Z4|yRy2xHU7fk0i8H2s2rQRe)i)MQHM_WAYWefGT+xhHEIL}D2dUZKV*3cg
zXA>Jp=Pp7@=u=-)U}K}E#HGN7VGG^LHDfjP>MyoTZq*U^`d`?-j(D|@;jHMxgx7E&
zanehMiFy*zSC`4BY#+<IUEZ2Uj}Q3a^zB{4@qX8j(qnj_My|3ACR85@2f`jNd*iw+
zsTqv|?9mLg#asBPz@bRuED@wd@R3OIz^BBQP@<Y*(AGDJDL999slz^<DBsD3mUlK&
z;!fkrmQ#OkN!=vX@X0?QZIV3Fc&P-+gVjUifS3#@EJuRuNVdOSAY2wZhxZ#%!l`Vq
zJ?=l^UQhJSum%m?HWDq&1q&1^hdkM3ql_*WP`dD^D`WioC@%Wg4Bj%8hrxPBFdI(a
zMjfNUfl+Z&1>`^_kjj)h3Pg+3@2mS^LOsN>fF$+I<?P-dFy#h8O)ML7*!qmNn}72|
z#VX&IBjjc1jHMS7x12!^nl7ZL66xPLav2<pxDxSMmGGV=2mY7<T0~aSl$kKtjPd>?
z^LydfhQd$&)hfvsQzvmj#luhxn!;Z`LyeWzFufqQGDhCJX@52i)1q#3?Wajr|1?h+
zM?5qFGsQ0}m*BQGs$FpGX~O*WbsU%_j`~ar<<rot8nJ7*?^H_kq*XF`DLTr2#2-NE
z7Q5VYTjLAl04~|0Q{6|mXt&khVfe<hk%Vncv(=VdXQ^8cf-pQbr#~=ogx+Gy@_0m?
z5%3(0fkm|~>ah3uM0|1hS-7@##T!VKzVNi8SWnz;pGpHN`R8Wn5j)20ug5I!C3*b-
zJAkE8DkWocMh(B#$D5`DDe`a>M#QHX`u7!fq2OCUrR$joqoW-KD{OLnevt$y%3E_m
zXNy~J<3qJfh<+G+SlmVUsj;L!{Sh=wqf8kEAA_4+VqA>{TIBi^<e|Z1L$RvFMsq4m
zHfNzNaGW}RWR%{bkPP-qVLhYoMi|1<t02}No-@&+#zG5J5i6TTIx{u<dyE=8ZAl@-
zO!7Y_S6N#|O7Wmad=-ifTyw!9;NzUu%w>Bp7+0G`IrHrit&|zfS%Lo#UP~+b(|ogJ
zks4BY5-}e1wlP88?gEwybf!P%%noYD`O$5xTgWI*$AVUXI9^Jt5-mAbE^wOxnOot^
z+9R%9g*50FeM@KzT4X}Sb>c$UwN#M~kXN;KxnjamC@gz5EMCOh7FW0lA36nqHJYSk
zo_V=p?skD`=KbHiSWFbWL&55aBGf2rQ0GjD-DWNx;UB2#^hfS=I%8|MA*&6Q<T91E
zBwI$CNhTVHt3BwWv+qoTkuSNFF1edVteP5ccD>pQwf6e%D}qt!Wlts6#(1ggy~si*
z*z8KH{77?z)s1HqE^F>4282`LpGJA@YPaw2Qs}*Cn+tv;7sHH%v?l6(n~`F6<n8`F
zgSVKn8BSwRA;PpDaVJCZKx_OyqXl)F>cQZ%0Y>G<6)#(ph;<=$hCk{7*#vQslJ=!}
zQmv^Yo^b*BB(_b7S#BS85oNaIaDCz$I!mGf=>8SuX=nio$Y5*qz@dmWd`y80pnRr~
zIwC>h>aFA4Ro`TZ_N#;dl&W!+KDKuv=XRAo%-v7$AdRa9Jj$vs)9ykAU$7Ef4$GO<
zt2_^CfZ~U0@ifC%x}W`YscCLTKm?wVOL`b&*}ge_d$aF@itiu&sIUIfEX(M0rrqsF
zKceCQl+BZ0;q+Yy`iW^|cxqtE?N#+7|B_)>kty(ogG<IL_z@+dKqYM-6zw4gjK}ta
z+s<lQ#kS5MW2`rn+mEB%{~ONokp)Gn=_%R^^Mz}s1(A9mOCoLkCfQ!HIh+DFh8nRC
zga}>^^K#6y*|3e*p85tofUm&~7G<K=2o*{e`(~)jhT?T3PC9Rr)){P~>>4v(Ue=&Z
zEvm>?vHxjJme9t+n{Dnf^s{ZUbz9j@F8O%QvGxCY(aAG4h^Y|>U(za!>vvMUUEs>a
zG}LE#yjha0^5dk!lRjC|cbjp}%wZx8mOI&MXH2Kzk~K$9^ju<Bo4w*2{mrECIigGm
z7!^$bV$m}eEVyaQJbum^B~Oi!9uU5?5OoVkaL$UX8z%?*;s2V;)GiS#36StTHhy#S
zXE}0^$QIkHO0DMsr)`|c=>j3Pd@Jijx%*zjVP$<46)+3ZB#n5i*o_`VoIB_Fc5>J8
z3p{sw9(Mqh73Xv!krHtuZM8=EW%dk|R$Gv)r}yL0l&#$9PT!y26Ml$sGRY|OQZU>n
zMsB~x!0pXrgN}vQUB7BZQ(!EkyEhdVTlfYC1Pc&<03PV~2q)bytdll?YVI&L%W7wB
zi55w$tJq@RtF5|dUFu!j$WBMRAg;yrRsT(ALA96YuqO5AQhRDTp1$v3zvJIm)S6+F
z4LT+dZF7x_X1$k`3Q;J2I%3g_`Tn>O*kB_iJ#Cmi!gt7BnMK9HN~R~0Z*6<%V~)!<
z^W`+PK#ar~p2x9|3g*iGok@JQGN~;|;*!pe9&Jhx0>CI?S0)sZ+K+t>r-lUIn|6e7
zHx>pe5#hx}Odu=D8*;U{hXTx9u&3VIr5L}`T}ZTdQQ||lWo|NQbtr#-)&-1Mxo*1C
zzqcUu7CxSJ0x@Bn<wth`?h(p*&A>a<RLh^kCW#&@SEbmOy2L#5j##K|<=dbwJnGJr
z$C_iAQ{kK7os!l-PiNrt9n-iOtefrs(ODby;C`;gAY?&CZ44@0L!N}cyw{Csj}SK!
zZG#cf_WFj9&rrZbfTN$5pdq=y#SBnkB|~NzS6GbNOlwf<)?1ID9${4)8;FWLMndNW
z@k4>WT3Jj)ti|T$IS}Kp5JM>s{g#_53<5P1m8$i_mi9~-w{(oM?khwtyA1s1(1V|T
z6lvE=fart9G_t&}j>GBOd%eTUcRu;t8A@)P&;x1pN2ZBO&x3|?($~N<_e}D}#|V-l
z;FYvpHIF51KqIXNAGwhcQP-{4DHAVI3<R3SNTZ_Q8DG)Us9i%G%?t~dbU?=AuFhuX
zS_*vtRPyKLv<q;b!>y4A;kQT4hYiDxpZ9H+uAk(2uL|N@2p$jOceheFgbMT1=tdJg
z9kLvQPoB9@+AGL&0f?cL^AknDWVVcA-RiMwb@D$IdZN#JB+D>+e*qGJV|y*;@uZJn
zB|~M@Y5)v@?_z&?e>ZU8lr9?!<*}sT8{OHEAx`lDR}tj`D0x-J1f3CU0c$<0J_lvD
zf6z&pi%y9+Mpd7ZTzwW5^#bDD#?{SHCA|vz<C3dRbC3kehDrph?kZFaq~Y+VIRzJ8
zD7KyKsYDnZ?R}$yde+bIx3H;~vZ3=PaR#z|tRV#Mid74E;>(~6rgcUqsJq<er`fhd
zV?j(zv+Xw&D3R4&YY4QY*J+=P%q$o7==x4^pF??<!3NiaUsEkU*L<8l4w<tK+V&k-
zvpbO}?=nYm+P2OhtY!(i%FA^tCj0Yk%pn>^CL}Fjg@ZO_o5(DxbYG>=21ZbU8-r3f
z?pT+uw+_2#vtjQnrIOfhRA3O*U={f8jD<`m3vskHHDhkc+&Ve@&0|(j&aX!j@^fag
zuciSEV+y{-{x3pcOlhb8{I{Ra0vBLz&GZCIlCD@F*3~jvx=L7CJCLh9TQUKKlYHdp
zFHdWXNxhMju6)6n>`7e1TJuWW5@%VMFcg+Qv-I(GM>1Z;C$R7XoSm_K;0O1v9hAb^
z2Z_sF%l9n(CReBmpPf3>SB007OM~jA-pmnGPtEab+9+R^fCGFhd#mMD-e6k#h|pI-
z+%m7XR;(Cl*xc>Lt=@7wk*<=v;U}MzUvrnPuPVbZWp9CU*U)GID(7+9cX}|;ZDO7H
z6k=7cmP%?goK#VU)LTO`69-0$wQDH03AL%mjYx1c)=+P4>{zxgFSkai@^KfHs8pK;
z`Vj&T8r-=V$9|fXgnGvLRbcBzP)xD6zJg#WT!9CQ$nY|8pF<#9^8zCT9m4}bg}qs^
z9|JrwL9C)$onMjU;6EnNo`Uot?qU~(ePRnHmkFKUfkiYd*(y>e#y#~b)=6}*Jx=MV
zaz<!EU?`8PiQsIa?K{+0*u391LI!YOX<jhazMOUq@1@%JXWmo|9$8u5dX8C=SXncI
z2~w#JUQQc2AQ}C9_MvWN9$a7}g|}j=E4UolPN_43J9=?xy4;$DVyaBEO>RWPPSOs1
z<yzDj{oI*Ng71a1JGGfMxBy&Cb0OtX02MAQ9wYvYeh`y;6k#~i;x$L%5c~5LTe2W$
zRpe<d5h~TiziiJZ2-fJ?!7O{LP^M9g3u{$3xtR&^l$N5_o+lTnA<PZ8VRCrubMVgM
z%XA}cg!e~7ToAb-?omnzHWQ%^JrK^6bQ%8Rh3zD?WI98Da6(flOd*l~!g8Oc7r=D{
z*EVopL2Ewk2OGJ_1rwt1G?KetB3NPch2*FZr!QvVmERXh-IPB?bM80#TzrG_lDD>K
z&t7IY{z6bMyydmuk3-aGY*_&9a0Zi5>0nl!-jjJ{1FZ|om1=$quTQL2>LZrUA^h@@
z9=-+Qgp<K96&k7=P7WU}ubU93fx2)e3F12}iu?>9Fv)?!h3L6Q7`-Xe7wMY4Gcl(K
zEN}JeDC<)HJawd3;|mbAx?361Da!z<T}@%ApUfI<8C!Dt;Rb{PR@K12^UC#SrkAAF
z;j}Z*uNotzK6&kt;pzW^c;O`c(o%8wm_Ey(Zmv=@8nmXy?7G3S$qj--ws!1Vy2-h~
zv0RfX=NdG*Fz`Cqm@AF_7A<(heD~P@+?rDOpoYUV>aR@m?z9P6i&-|NZ9>v5a#002
zHgQZ<M<wA5OPC)Xzeu{Z&g?GFX&V99N>X18Kz>4^7l?)tuNgMW@YGXDSi%Zjq@h%>
z&ejygV9uQ21L-+}u3alsww}i=8a`7z9JF8^g4Ju>Caz`Oi`~wXZS^Wi8rUU66i^Lb
zBzf)88$CycB}K!+9|&x{!kri`ORPO?EQ#Z>gG=nW$VM69K3inz-<aG=&`c4&O0WHc
zXRsD;a$$4x+1AYL%}6ieeQx`~^wf4d?zZ;Tpw$oGe)i%c)Bn8cQF0h*dz>A$Xj&=B
z+PSG5ap#9B5oX~0Vx{Sei=U-}=(ciz*0zFr3#NzhsRRzk#uQn3uP!wWB?Q(2iBhHc
zdR*AG8SWg;|CDAJ`Y_+9M7(k-YKATH@Rk=<PzAS}+q{^4NyG=Ga0ffzS-(LzsKPB>
zAYxg4%GrGEEz2DWyPNpiLVXmR&$$FDa9jIiZqpx{+af1)d9!|-GtHl+RZNwX1hLVX
z^LS7~+gQCkGkE0&c<67C^N0wR17C0xC>JD7QFmexWq+f2IwCXF9(2e19qJC-(UZZ+
zn_sTvpDsVRs|mA^3l^Ad2AVzp>_T|L*PzG9hkh}B-EHB2eYAcE-(K$wuq=MEJ$(z$
zv{QNPGCRmlOoKb;V7Dp6K)*_YlT_gWn+gF88TO4D`p<7iby7cZv_Yx&htOY*ryvFG
zI>wp|A4U12Gig`)oG3F(zRExn*1d_<m>Bh;B3$(-iW(2mo}ocT-4>ER7|X@b-#ylM
zZwJP{Hm?a`jkyy*4($ouXPYi8Xwfyq=nGp*$4M!fI1Y-gDWic#9$l<2jHLQPR(0f$
zV`(J@JPkN36Lc9vUeb206B`|>Fz&66rot7I)e9gEJ`kMHI}-xNRZrj7&90APz$GqO
zjstrFrLC>*o6#`1dG1(VVJ--~k;2cMPy4dkG%B0<yc=5LiQ%H8K?XLwLJ{m<v&u|m
za$0h>BHrtlC?fU+Q}_zw-0bsgB3TzgpKvTF88j|M*9@y<@P^EsS}_Fm%O5z+bl(i)
z@yj1zW6qa9Fws@}v$Uvbor3ZsYFAD_EgrzL%MfQ|>Y$=A<@;PNFh9a?HZvD%^yX$;
z3-^@fy5V##Kh#Y{pz65~%qYKL1ZB{@<Y0s=Klaf7?1!|MkJ2G?Vn4POI;a@;nn;i$
zd+Z#5JX0V|U*-{^81;s>Ghx<1;cQSdro`zBs_(HOFS07a8(HsPX0rY1giqd~BUqbG
z<r^AX_+Ur!WyZPG*=glWxOFH*vqeU3x8`W!otCwjtS$0q55{?lRwNo2A(?K&!x%>P
zu~Uj#{_DqC0!Rh+CYp*E?j;xqnLq5@0xa@=v2r3JAy2ITHc6wo3AaO5<!t+XZzWY%
z0JDo$V$505HWT;K68=hxqu-S*zuao2A*fdxTbaI*$ojl!YGt~04=+qn-Q$Xxvz;IJ
zEYG-V5?QSmltTtqPl)$u1ZG&}6U@MLUZwxjAPI8LAxJID5xMO_9of;1&Vb~*vHOsK
z4PM3hIxi-*s0NbSB&Yr2ug~d0Df%)aS?AooFdMnl4;XJM8(B4H4TTkZO~aH6r%Li$
z*26%bpUj09F~?j_({r=rGtM6eP}}s)Y$C>tvA0SiM`BX0_3V;y*_OH1l-`=%TTQsC
z%r<+S0ZkN+&kJY2E>Wcb2^te6P=-rf9+savy02S-MPo9Bd+8iA!@i3v-6k%V9)V#o
z8{|%gE(~?fDTykCWA3Qc&{-NQmrRso^z6?SMn&Ilc|Noo6h%Gg=Z>UaA(Q62P*y%B
zX7EGbaBrJ`H`b@ygg=h36N29%iV}(*`oHIF{x+wr!*{r(*_2m|fm@Wh@n~l_XHboL
zsTc>8G)Hx8A&x9%03y5J=h!N<##%Ke64+w)R;*cqUm2fnBuptgpjFIhN)p$Z?dAMB
zyA?ipvZDou4_ms@U5;T4eIs{SS+G?`7M!2twO%upC|W0FcJ@wFbf9#;Gg-fN<G+O|
zxM55K8yR9>P_g5;mJ||F`FX&y>9DXk_Ohn-HQ(a0o|*}T41G2kYMwznsX9N)JcE#-
zf=99X+p>1U3DB6PX2)4KXZ=cyZB%5YoHM*{Xe?|{nzw$zRkb?U(5LpvM481^N@>QJ
zc3HL+AXIVXU9cA&){UYc(+Iz@4a76WsGCgd;ll3o8djbm695X6kntbjcJB6*zS&`A
z!X|t_Tg5=74$ijWRuj>%LF4XCC0*w2oq0ZsCK=XI<(bgn1Hpe{z+Z&y(z`*ViZL1%
zUfg#UnguI}w)#dPmGBQG+O01+a)m~|49Lup4St(@9hnto+D%kuP0r*YpjRd<j@C<N
zCz>lrlLCfSB@4?m%6hE1y<fKi$i<W6KHoDcfNX5l=Nk*u#)8s-)Ok85M3y)WNpS_f
z(&?CKMN3G$s!}M(jo3|{T`N>X6--No+`%s^5&HkbtwA<3bLHn$5Y2o(TSSx>6Tw2~
z))38Y!Fa`KrA%=32Hf7255-RR+zOdUF}LQ6c9tBlq~NQShbn;@79VY~bm&aB)1|th
zg-y!RAzgTcrNSV$sp}R5E$uj86I7Jsf0jxh9RJOaKo2*t!Xb(ayCHZu3&6h?n-RXL
zJ{4m{R#dO$*PC&n1KZ4Y9ouo)VuEEK;k@R{SJOEpK@i<`xv5bG1y+$P=VmKOz3hI-
z*X9_r>kP%ZS<s}OjBW^tS^%RDXjK^UYR4Ot=o6I?fvGfBtW`-pwY_ijQofHz)&k*W
z(4as&I%S`z;5-S-T3F)PhY3ueH#h;52&$*8vg7rZM`|bMKL^Jl_`Co<Zlj^-Q89`N
zXH2F%nv;WhT19Ow!C`0Fj^Aw%cs^%6Q+47)yip-b9lyiXG9YPeNjGf<iuGbXTn5Jc
z5i!)L66S)%6O9{91%;o0^R>7AHbNq<Tq#wwer$YTH$?GS_XJo<U}Jab5m(`Su~m<D
z71NcPNVAVH^q7x?F~RAHpcDKf7BlY-dqj?Eb9YLx|Nd4<Ys$XWjM6#(I4*K6P?z&>
zM`DzuS^5q7`>GM9A9gQ%KTOPzY`}RW2YFG-ARa~IUTx>8)OW>Gk{}9o_#6C@{AX0s
zWSo2it!{$m&Q&VhFB7TmH%>XrXpeG8RKa?icsU*DbnBKLPJcv{n|{1e`^Pwr815#g
zg%9%lqtm)EB7@%|R_H}!X#y(;{~&0uc!EN9)=ZRzplyCN**3+11gRCni58loxfRn_
z{DEcPjBT7H{X9#~`Ea(>IXr%_>2^{j(}#SahScJ*lJM{15)~|aHxCKBa|xLFcORMq
z=M;0gwFNz#ewM{953G)OG`jeuha2kKF9_8q7N)|MFsg-$q6`e}x(!DfH8F}}9b2%9
z=GL0isYOPOor$F<=hGj9u4x3%mi5`)zNdOeUHw+yf%`b*tlj)(^GY;$HlZ37(@rrM
z3#&gMw8HleRES5Uu~NlC_AR}3w#0R)M+*fFGrP6Z8bEx(dmI>tvlU~soT4+3^orqo
zjo%DPeNrM~Zt=|qi&yL_-L!P_meo5h(Sc?+CR3>XK9zP<EysT#d_Tud2Ga(S?OD!!
zJ<@tVRa@Ajfm%%P75s{3oSoI@qiA4p<^>r;AlQu)za@Cb<sD^V7Us4>{T=7*1yzRK
z&)OL9HXv{>2TXL)_=aH8P~eB!Ne@GR2#~PMd<Twh$WU`mvE^vCHe1`2SSZNZE<-Am
zC(1CDLR5u>Vk@|3lVP63d?`-i$<ZjRXDaz80c!<`&Gjo7VJOZ-3Wv{&+#wBb(`0kT
zlMVG9Yfw+2WSW~B8!r~6)lk%)vD$L6ue^}t(wA47!{I&jN0AIN*R!3za>hAB_eh?i
zCm1l6%>%LB3xb(ph|YLtsmd#&Jj7K=DKKeSq=bWYf-l+LAGG(ZLZVEsN!FOTo#&n<
z#9Gi9VEYtryW)|#wB-e)or|GlP=~ibhf#|Xs8>iy^KJG5owG(@X4BqI!?^h=_6U_f
z8DlEIzib}O^q4kWh1-ov;AO63Dl46;WRTd*F>_FTrQM|7pD;J()-U1+u5tjGeI>CZ
z&1q}p7EVe>JTf>mgH~=cbGGT<>@=#9rCHjNcx6QhgaOVs)ysAQB?dR0GnWQi!z5Km
zUwLZsh(HV*ki_3F1Yko4HVlbZZutBIJs>WqrT52ZQt=Q{70>4_+QODb0Z2l8Z$TsA
zI;g(fx21O%@L|Y>ks@62T`ma;M}1sKskKWceqXlapfomnU8{>+IM#zsxFx)D+4Dg&
zs$@8o_F=nMa2yFe`dFT{C=Faau^~&Cy4_UX!NLbHDidlgX91bgL;mWl+Vqr{pIv*f
z+dxWq!BC1+i+4-`mSaX;<m7>o!9kF8(S;rQy&ega*Cd=NOmb|rC^-7*WKkD$;3K~D
zNR5Frpv*BcHFM=fBYkN<eLuSen$h4(=b|}1>1?3bu9RPN@f;H;TTic4t<Dq9>^fVD
zw6sgMdTc1KOAdWT<xwpQJcBFTERfyZa2jMqkoHgwIeXboJ(PxOqGEETd}Yd)b#iDF
zTi}>rHkLhtql5AP<=JP|_KY5;DDx`bjWVOr-P>fb%Cc(rMDj^>y^3WcyrG2>niVS>
zfA)-L8Swl?OWrOP3>EZntJ}Mw7wmuj+6f#lc|Vh_q*lzS;5_=m>*O+4uR2$b>;pGO
zR!hF;Du_tK2BqzwgY=Orc1_Tp2Q}M2wkEMb^HT$S?8x0@7)Njwv+H?v-anpK4OBhF
z$NP^y^nfL%c4ALOz2BqU`Pq+csmw`@3j!mVJEM%W&9Ua3>60&jicT^e#$Pvk`1Q`)
z1HW`X1Lglp2H9vDyPHcHq*<scx>bb#m~S!{OT{tc6~<FLvky*_h^??9cu|H5FH<2~
zyaZaVtKr}Bv~Z730pIm;d<*U;_m)-u22v)qWL#E&CytO(<<@(><vxBftZ@@y-yA*W
zXwfz(IIveDb<SV6=d(Rl^q-DF@9nkcVR*`S^fVtm3QbEW;Pa24GX0XdV8&aiG|pOJ
zGyKT@0p&H#dj^MWHcGV687Rmo?E;}F&wuCZy!_0{(#eOb!`aye8+~zro@mjUlQc8t
zKmeE~le<XI;Hg!j&3t*K=Q6;+tB9uNv+l0ASSixIWwsS#%;UQ>DDHJONp8$k_$kK1
zxeQmN9o&o<c{OLZ{1%SEys-R|>5m`!!<fjeoPV9h^Uvh%m7Bj!q8o+R9F$BMk<?bC
zpMktQ>D-}a%oc})8zY+qlleEhsi_&)L;xCkw~+qOrqpk$pbMzlVVJ0!sd&mRGt*d9
z7Z#3y8-jIHhu$^m=0ThaR$6wi*&blIx@`pJ2QkzCD>k+XP+qp-kgIf?E1dV$#463U
zab1PE635V?xB2XqIP+Bog=`JwSB-3!=O(Jw+#(a*(L#PX)5klnnSDdBFseixJ8|Ic
zm(%Gqn*{W7TON8gj~1RKV-Zy&^LE2Cobhopf^6NhTc`f#*GnP%&*s5%mP=C6Q2`m(
zGn?++DEzWcCYHSN(i^{1qvpwb!0#`)mKIieeTbXedI3tc3FhY|6e&D|Gk2d$Q_o2w
z7LXv1lAaQjNdaQ2V5Y!d?@r(Dn~_2aexQxcU`ox*23S5<G9Dnk=+u>t2j_$l$VhD0
z!EHpuiW2PL4BYqoreDJBpg%l)4}Y0O?datn<c#C&LW|>b&|V&nx*43!Ki6cH<W<7t
zQAB5vcS<x#cDFf<;uyyxLx)8)567$qqeJr~=2n|bvmUl4--JIdA7O29zV|OPx7~#d
zI46j{VZ+=gK!c~&AE~WA^|X8J?0eU=<=U_uy)S_Bu-uYN-m$y>K#Dvwktd~WK-l%1
zyP0KNQuWyF)wy0ZOY7ByUYyXA$Ix-aUisQHAjk%j#>AaU54U*ua~3sVAR!wVj+F)0
zycN`o2$W>&cHw`53$3=tHS+U9eILuZ6)Tn0eg4YC3SkSeRPLpJkw)sHB%jP3qY6zP
z6>+K{_!`!nw+Kp;e^3PuVJdqp-EHvF{5A8P$8YpW`eVTgh)F$%cxdiNh*&xdA@Y-@
zFvM-)RBIQO#+f38n^DiopXg|JQ@ztin}z77VVlSMdOcV$k}z!Mf+siC>!XKZX}U-F
z8xasm9>BuFkuBlBUG;J&D!Z3ly4W~X_YH-l+%-fS#mI`uJ4fFvr1}?*u?8$GIugMQ
z*;SWqjZ8rbYj(u8K+FOBx2({yO2k;sc7gR)hP?nK&5h#5vwh*2ty<0x6-U|VqiWf~
zz=O`~#)X?X*Bo(2Rr|a(ay-)>NvUz}j6hF)lU4B4$BxX_OgTuNV+QwFW2`*1kIcPO
z=lPQ;U5+)Rq^)%L=z{1;;aOj_8Dq8FYlp0cGce(k!TPa<e(`E1vMX=FUQu1Tk-6l=
z+I8nm78Vbrq|S_1EUbT)AydBom1d2OUP7n`GVko-vpmseK>=)ie0S*P$!5$Mp71$m
zwb3-f2+U~Su#Ze?tx!=#D%RHKkj>)X-`ukc0`uFiw|i~7>gs8Wau?5b!@r2y?(h$8
zh#-3RwKr!z2`m0xO$yiXe*rs3Jl@t=Zj6k`e-YHTK7B`#o%5peAhW23NYAT1JOpgd
zXhvItrbHDkwJ?x*(}#1#tC@;mShps(7Q;~3IZ-$23ItB=omW$H6ropJHKaRC4t7eG
z5X0ACtG&&dp1$WAVuMI;|AemLS@jyLUZy<)K>b4%pj&X26pbAm)HVRM5h%;!K@T<9
zdGOn3Uv^)1ksU<YkQ?t65&s)XhBSALt<=|Q())pZV46rb{4Vm-zQZyG?lv7k8z_lX
zJ7^!?f66VbN}_0o)s{n_v%m8Jt&MAC8eLong>ir6HmN}NK4tgPp1_`zq=O1po!aPH
z?8F^v5Wm8^4ef}}nr=5yj@C9q)ymcaTAtm6BRo<3`RafxZs?ZjQmJ8QP-R98TcII1
zAzcV`k^_3iJD|V%YsSP9LFK3HCYeI~?f@5Ks6pIJ_Qt+pTXymtT#UYe5peSYv>Uxl
zmFd+hb<hnxp-j;l$-q%hROjM~bx1cEVG#}ht6r*(G)!N;G5-Mn_e<W`6_~X==U5RA
zlquZtwHE#a?21~G#?4a~AZ$}>prjgW3;=s!^_OQuTax+}yl{2{H<f;bpTS?XoH7vw
z|5rQdtpt<n9hDWf$hpV*E33eqx3N`+<75ggj%v{ND$rV^9lTT9RFxYi-#vt;U!6l&
zL*8opJ*K%y%yNwmaG#wY#*^8uO^oLP0MM%K8;6<|X>2>hhkHoi@3>9T^XV&+yhxUx
zJ7q3Nc*Kjgpeku&BRT*Ry0C^r?Bpl}=4<vwgc2^l@x+N0bD&6_RF~+sHW$4Z2P1^x
zElh)LwJ_7@XQrAfd!>ju;ACo+q@*;3%D&1D<Bm-(xdHyd@LR1}$=ek%ii6WEk3{T^
z>v$M>7P!R-;j6eYW8m;JhrXdJ7f`_0A#fJlfKA<ZTkvdn+!Muv+%OgpyJ)W6RD_sF
zsaUviu<p=Ae^&isqBw!LAq+#2BKGy&EUP=vg_DPefHmodMn9<?*Fos&(-#}d#{nOR
z!JyW*BNOgzhhGI^F$lT*H-wV<cVBil)z2^_rR}I0@I_ieJ_mylfBQlhW?&!Ev=<yq
zg}R#2jOyl*o53O&FnihfmDkyEQ^s8d*0>u;5y5%YG!n7rO;B#6wcO;3zwjITho1je
z@=&kCDzPSifpa>>l|o&=vt=z~e}}E&z-<Q`XURNg)b6Oz9@HugFdkW8SAY85zrg>)
zLbm}QAr=uzf0SP19xhIWb05(5=AwJ}h0!6#)_@1vZ>NK+63A>;*z*h`%9gyz<&zGp
zu?SL>8CXGe&+*0U-%yC++RvLeR@WHYpm0d`6cq(xX#5P-tc!YQR4~aPJhI&;kxTMa
zho|OB8LuSI%C?6;ov{GjxdjYdxOEjF>Y<OvT&In9m%eS2iBB2&D#u&nuf?;UTD=8_
zdu($X75$%ZTzb$HvJxZ-q$f*lnxy%T|5weyIN!HZ3G9&T99p`05`zO&!|6X|WKGRj
zDOcS|XutQ)#h^|aNw2Ff%-L?xY+AV@-jHcSmaY7aUw0!So*V)w%8F!7b0#pK&`t2j
zRrNor*pPc8Y=R$t{7)a9Z*lL{5hHXrz;qAPE;bFqaD2f{WVU@1|5|ai7#ofD_jZ0d
zcd-TI&B>dPG0rRPF|Ly0Lbobjep6+}8mG0@)+jJTF5zMKohz&K$G*U&$!<P19Dgy{
zQQE#lk51AXe^a*LTYFC22Tn6KO({)MJg!qBps{wh??DnU{3ZB8+x!GT5Pe4$cD-#X
z4DTDZxYLh@+Cl$;_Dv+$qFf@wWfp-Ex$Xz$n~vS2@V(tzB}Y;2t)UXM8JaZWd}nh~
z;E6KSzn5zrIKcNH<w=ys`4U}ieH@xL!Qj!;Xa=1G%u#jIqi(OfrF3EqmElXylO@?B
z`W5$d1fL=6!P7pt(lX56Tziu?{}On&(Q6QzITBv1sIRoA*a>*;3`>oG^^}?duge7_
z$aO)(N^}%~c>zy+7mVq_uok(OZjPB81(bQ1;i$kM@PU9+Y6wkk!PXA#`VzBynJTsk
z?V#E6$05c7nh{5M@7Xw`fK^m=Z1bMAUO6`;0lK1wzz}#iQ`UUlBj3iX;IZaRjxt1+
zMwbpVYiet#B9jOBOW%HKQ(#kToF!B7Yn+PzB5+=YAWP@+Bzip4PPVZ`M&)Ht%c2h3
z*ni7>_7Iz7QiOjHnm?B&sH`j@u4_-<fj6*C>cc|N)9r(zcVOy+VNs^~20U(qS_`g3
z{}Gcs_@=Y>!Y}^(&D)R8KQ3&r*$HG(A?w2E-kr>g`4S*)P=zjCI1b|3!6vi`uTRDJ
z64|%1iK50pEpET)9TsQj{9hlx(3DNKZ-NxM4b@*Dn9NC1vn-@r$CeZMz^%5SJOwhl
zMR^5}0E8#bSE+sp)>YryRIGVbI#W0<kG=^Tdi45wF7t?cUfHhNfI`sNwuKXA9#N5C
zTyWbT_U5e(r}sOMhZ~@H^Dbj2qf@Nz)E=KZ=o8G4^kX{A=VE&29dcAr5=Y-2C*+e&
z>GspQF*&%^cqj*uNMZL1S$x)uF!vP5ExV083qLlD_JG&CrN(-$FN-g+$k7)QF*FeU
z)8|J=qq*FWCpLcdfLnX&dKO1U3@{=y>RxS~MUgyhzKZ&Sl8<=xTZgEP;l^-`tC)^f
z_bvF&T=Xb-igtRTKN|0Z0cI5FEA7=<9b~ChrXcCkb&C))f4(f}WvR~0{!4LIFo*pG
z@g{Bkh;r>}ZJ&(7Xa;A^yKxyR3y6XKtp#}hrZnP0mWp5JybMBf*pn$Q8B#FI=bya&
zqBtWgd18^uh+Z7&T>PkecrG%ZX8o^o#OEuHXdG%c42@Fh{rKPb)IVNv>Yokj@bHVz
z{u`h2C&6<ylIHaO;4!I4MdDN5O`I&pn#FyXTemon^yIQS7SAzYST<DdoNcl}E(|tE
z)sA+x?NF7ZyUx-7#$GVl26z2X8?48^IyQ&C`qS_J)n2Bn2K>|S{tdH}@GJge@Qbig
z!xs$njw!M{p=?w#p0ItDQ~qt3^!co@=}6!0YitWgX?e3@SB2z#TR5i7NDY%&1Oswx
zko|2$qH%?a{wK1%%7-yFVdu`%+;r?oe$<03ZADGDQ{IL8X;50o`ygYp;rDp?nmGq*
zLm+6x7+khs)}2O*6CaubcTv+5Gh0QoXXr@9r=dyR?JyxcToQ_PJI&Ok>XG#@C%w3C
zH1_=N!G)j#fl9f}-cuQae5P^W*|xq|Yurs?u&``Y+IxC$O>2jXU}#6;;+>jC)Zf+`
z4<_4CN{_4wzC<h=G2#V@+=wyL4E=Tb_Rz2tY6&L^nXaMhc>+<_w$N<*+P^{Y*_yk3
z(}TA``!T=+CXO1<ySM(0jMWA#^zzfce);hx?%Cnjthf@#qiDpSU0_xMN61+y>7?=}
z&?gw(i`O6Cp{PR?+ZX0OGs8tLN3;VrSKlOrb26Zk)VR))JO+sY5$A-YO=MnY)#t{y
ztEZz1WQ>=4M&Mph1?-lKT^Xl%Mgw&SXAWAOKF)$~8(+XBY5v0l_&aVFTGg6MBsA`k
zlW7AeHRY4?JyU(!{ongaST4|#wi(u<jT1>V`p+luer75Yi@oeCHx>drY=dh>3Jz@)
zh(C8MNkpL80b5F1T<bKBu_*x=W+ax7%xuh6y!}Wh5rn9GjF*|fxs5-Utm>sGO9B?a
zZrLGex3X%Bg*b0h$5)xm8It06h(Zn0OSsk<f9!MWQIj=wQZw|8FyF8}L*7@Am61ga
z5p0Z>pfVriwtf;?w0mpOKE@WUT4T|Yv>^)oW!bN^c~Q6F&tiwF#6NOlYl8Hd<FgBQ
z5Sg;S!mnvE{H*C_LN2-ua$2%aFX-+FKzy9<bC|Fv#l@-hI|tu<De20kyku-jv}LS!
z04h#mRuX|hsUwd9z_z;>WI))a=DC_8p6KGM7oiV}ADO9u++?%>vMFpAqk$A^aRl5~
zL0p|+#d``~<Ae={U!jDur}GsETP)Z>LBVCs48mG+-}&XC{)$c(0-lYOkT|LX*J)C5
zA-!{)d}5TI?<d3Vji&a<lPO)2WWZi+CrtNn{NJbK^HG0px@qh$6Ry3KoPjYMie!gA
zW~v!RUubx~jTWwEO7_CyID-4G>Y4i7M6U%fmY45_Ooz8?B<T|p4$+!1jJ$m-K~-+2
zSW;Y;Sl|_7qxf^JOl`c^lw}N*m=_|fzKzKDgCqlsz9d#JWzbT19}ci@Y*(YL|Jfke
zDhk}xt7OZF4r*03&#4Ke=NzKrRgQ2grzN-^Isq0QRoZcGQJJ%14~5M@Edtk&Y_qrP
z`RIZI2)xJfApnwpBUPre3h1Y}6^8@lLmE$6Hb$WZJz}~MLI_k}l1IWs`8Hs}-?h`_
zlCs>us^0d)fDO-2B2;!nx1`zWI}QR_AeKy!0|<)VmNMN-A*!`6{NGsIacv9YpH*)?
zH*^L-1`8Z`103PPLn_m3XetpX-DTUfl&Gbke}es>*f+cjfgTw;;7P<vl=>SRl+Qrp
z`7<EsLVL$e69Y|aW@ULKWNTMwPhCa^UuOsJh-@0BSW<!W=%S39>h+81_^{#DCDSo}
zhipi9^ATzZEMeeMCCZEL446WlFAlR<JgdB%C($zraTSPWI336^fMr>8FFbV%Y}~`S
zpa?wOh>3LhC+4msnuKX@=t9MwTlzM&H8w7#kKIQ5(|Z>Y68FLH5vzJH2*&3&^4wpC
zl+0YfR^<RhFIzAf5yzKri;m#bJMb-jtG*_G+3*6WZByK1qrP0YnUwM1i+MD2V=`R+
zB)-kGW!rmO$kgkOLsPBm+f*)9AB?>z&R{j1cfFlmWmpwj);@GfH%NDvba!`3cQ*)#
zNSD&x-5?FpQqtYsAuTN+@EvC6ek0zib7$az!^4mDzI*NcuC;sLt&lSz%2<6<LfLJs
zo*O$L=O<6jr0Z*1X6G&{tQbPMk6@~kxkma#K{AtQRs^<lIxMW!IeQ4507-kC<pnR}
ztqyapZ$%U)L+}E#DD^h-J&m}UHw(BYo$;bl9_5ns+?q_S1v<RGYl^G)y*jbRFxsdA
zSLFFIh%P$D14P*8%)SMzB5M*^vHOCtL??CRMwpRj)Xn95UTGbZJJhgDE_sD-%Rb0?
z@hC;5MgT7nT5hJcA{{Wq{N?~|^G$`CoDCE+@FkY}K>`Wq(Wd&^9@94(zx$Cl7yu@^
zXz~u(=nQ7)X;m&QdI|DT`e6neY7|1OU8O?GY2@!QxR={+NL4d-TNsXdHj&4Vq%rEt
zvf%f9Q<jok+6PKj9Gg&Yc(9nD!Kjj-nX|bu-Sbv{_SoW$G<}#<Pn;VJp_-y?jzmIU
z1J2pHJd`|?#eFG}GhYR@DY0%&`bwt}6`=~+>9c9fkn{qyFtabTr=z021b=;6f+bc4
zvB2&aXIP{WL0{-yX;hAlG{XfuJkR3HNa9Nc{V#k<>UT5hzUEEyJsI!n>OzLvpNYS6
z=*qHzr6MltvrwGLQAg-r#{5LlO)<l~7F-kWGlze{F5;&a_G~NOWohB03Qs4{%WU9$
z0$+M`tKfJPz=l0@n+{3&3RIQQm$_@64kHCEv_>&M42(bb!3A)Yp=h^XkLYTY9q0Sy
zIjGi6S9aAEm(o!}w{fLE(?v3_$h}*psY?YbBh?)9+oXZGNsKI#OoG}4y{I`<<<9Nf
zIu-drm*F!0%vX$ZxPo=UkoTo7Sc2hqGFPj0EBvGIGMKpDn06g-<cWKVeU!rB@C)$T
zpy*uz`0f?z3jFrG{au816^QUP4V0Ow9+&~8n?4<9+Mcd;RqgB7_8>tJ-X*981{|UH
z?0LA>&SGk}37ii%x1V$XV*`vz92dg@tK$8k*mo2+^yPIsU8{^7_8@O0K@<?I;wzW>
zQbfm?BFEc4^&1Xb3mI2FYf!{1!b4X-T9ch4#M_C=4!)X_qp_z@!DbtNA!RL+(M66D
zo6n}XTu|f|md+L)3vr~<3B@(;4sgh>oKz+7lW|QjvFn?sGf*7H!psbEwNvcuD0s&K
zmd{I%6e5wy`WAn01W}}V$2~cYa1ABf2k>H-vK@^N<vp{cLs?kL3Hwyq(fQr(T|CMN
zJ{Sc(3bfNSkxO|FfvMs;-&H?tm2395Z!gp%Wco%VtBWbW;M<a~F%4hZZ1PJ{+Z(?0
z8}_u8^U@E_+Zdg7#czCLFp3yM#d}cxaYL`+t#1$TsuYSZ5I4IEBf9#xQ_ty1M<tMC
z_A?<`V|WU@XJyS4aZ3qvzLoWZ&T$T8?|7APR!MFHHh^y~@H8NlH6ipp&pB9q<}k`q
z|DMaC(PXPKlYXA$P8YGjtAOY0?v;MfOdXa$o^d(ZC0ZG=-JNiBoyt13$5L0PUrP@b
zKYlDH(tI^Lk{`bt#*zvaq;+j+((I-MttNjnzx;miD0UVG<98?$n@I^uX&<9&gGLy4
z|CPuQIi7J6Rw~%9x!rG9RyXx$;wza@pM%dcZ1kI3PAQ;_eT6;R%hR`Uh|7kulkR@6
z2hu`k+C_7{SCY9XrA`2NH&jv!_=bMJg#Y4l3@!e1F;}mNC*>MZ3p*8QwDEjtGy2`i
zovMrLmsZc#%u42_8hBB@-JrSo4|B<wmt|kuTm~dmF^yjv(WW9+2@f-C4IM+iG0R$o
zhZh<C&h&!y1{Zzo&XD9aKF-kwia;brukwrzcZ%GkQtPflIj-VJR>E??TJ|%iEaZUh
zmYVfflK`QC={@Z$g}DwRT69nrjx0J%99$|nbI_{LIG?_Q&=^8}taZvY2`GIheC6Kp
z!O1r^;4r=-zUN*6VMwtXHubX{L7V{u-s*PzcvFK>8O|n+`Mctlq;=2wU@Qo1;1b-8
ze5Sh=%(1k(V3p~x`ag?Xy|0DR<<B~M8?Y2~HJ999K){4>gk2UQzkR8ocg-tyno-fK
zq!t6OsvrDqX_{*@x5T{S1*5|QO+CGGtod07+reSZGTWC!;%NHKmOhAPru2B2*F34q
zD@2g{E{JvAC%p#44m+uUR2D2JgEn$Ms-CR3@P03r?%rmvmiVZh&%6YcXg+cus36V=
zaC02bg5|I;@X#}>>suQp>c@jXEdBo3O;fP=ZEp?+v3Dcdfzg#6X+p&sA;EfwK`^iz
zz8`R}29jYE_G$q-<|fmM1kT7KoMwY>(;{PJ?xw1=7u^$ll?mPuN2F9d{_tI~#V7PQ
z?oB>Ur-OCjp`2=WXFHqrV3@<Tkdn{Ap#FyW??zF2Irv10Dxzo!KSG@JLfQmedQitH
z8GSKgY4J&)0CUO2pldK^MS@t3cm<gRG6*k37mYX%iZReV;WwFtFW8l2pCb#36~#|5
z0zvGTxZ+Ovy*Fedx~)Kok;!8@c>#u83+FYL8@0M*F~-q6Ujkp1|LL1r*pf|O;lMz7
z1BaQDH{^(V7Ith4#x1#kfgX*$`z#wgL=)!yOxcx_w1#)!6{MiA!lc+Ts*V@X?M+#W
z^)ETezI%Q+<V_GlgTY<j*MYx#)t){s_kk)Wh#%p`tCv#W!nsHJ29!U{Dj>~z%x7gQ
zJqFG3{*d=VRR?|$!(S=qoS^E>KntZ{ZG5{qN#%krg~ZD)tur6r(sPpL+7+ztE<^&&
zGWs>ieQnDdD|#+5Bho47Di2+N+z+$)pVe}FooVFD8dnI)35!2-X;m7W6{s(*gDL<|
zof0O3hiR&U>zm}^tAnVjwNY{7<{T6SF$l(0X3pZ<34n%)pNj43r98yzb}-}31&tp%
z*&AE6;bPeL!n<{5Ks2m1Pb2_(Yf@#uZjKbBgJkt#kwz1`d<$c<5)YuuPkP%Tsv1Wp
zVwKCAW?QuHO;o7_0fCV3do>6hz$wHnK_L@vNxj%P7+LqSE$}S|q?L8u#;DzHOo!Wh
z65$#8K-$h=O_)dtcE0ik$JuO<hv))CoP9NJ2zh=Hyzy9aG8>QR$bP&M9sLg_haooE
z4De%)&i0;%c>7g4DWVb;1vWti*phCvRM{O1=P++K_Nh)UN(l~azrJp&e$`kI<Yk6E
z&s3=RF4t|0T&i*e4ZSiP@Oj(5^K{t+npn+yOA9RTVl#$*-Ot3Qy{cfIw$uMkQ~nh<
z=A{u6hOlUtx8WQLCO&v<n0XKcGuF=1EweA8@@5sNEiIo1h%+r1b3D3cN`2T1LCmI8
zgSR}cSXqv=;E-P=@kV++<_&(oqU&BB3XWp@qMJH(ah|5<O%l%{>e+V1FohD9+4WWp
z0K&^bm|sALc7?Kr`2I562G20B3Z`S4oHs&nHTOG%A0dj6<Phcxm!28O%=z~Tv+9Q`
zSR(3%ZrJbB`J1F{^I~0D?=7yN4?Z~Tekwf1+qn`G@T_fi2!x-Y8-0^`Jx^xNMsUGo
zY$sjMwi8pP0ZLASa?d1IuMkxyQG8`VSylwe>`*poenJO)ozdvDt5cHuTUddI1<A>t
z<7STwTSxb2Gf1!@1S0M^5S7$qs+0D(IsvsditN?TXcpHfgIwTS(44yQ%X;m3!|Q&?
zq*!2kQzu=zeYf&jHNh!OQgjZ981x4--)6G3BT|h~D~Dm$>v?JlV~LqOc+pkE)tfrQ
zc0faid|0B3G6XR^)`!X3u*xejv}LwAstn3G9bQ3jHbb+R-oix4A2iXdzvKMI%n~>1
zpYA5GBlEQf0WZR-qF;`{tfDLn#_E&oqUr3nQ(GI@_6%)2j`t#LR;Zx`$6-2c&x6P}
z(^JD9aD^#9l-gh_mts#ROU?A>fo{p+h*SC4<=eaAm<}TI53$xJN((d%NpFHZ^Fquy
z7$<FlG*O;q9^e<GP^X>m=y%J7OO`d#caAUW_;S|p+WUhgZnExY#PQgvNsNO79E$Xi
zf&lsKY4IWREp_d<yi<y3R_(p#356aj!z})Jt1qsEt1gwPXqabEVjH<+n985|HQqKC
zwr;1}5X!2&!^+yr{N&H-_)34)-7(;qiDLhBudX8l8skjsilPXfLlurC`-?);Rp1LB
z(+4=^`S4cxBSI`OdF2Uy$vPWIpbIi-&usErc;wdxt<w(N%}uRF&e0UAOUf{@@oiNP
zJz7FZo9skZiEv$<b4VOpJXGKaGG7HzJ|kboYKCy(@Z>i|mMoV(7aiy_o}#4Lp6{S-
zl(oCS%Zjym0h)S4iyN4J8@0dZW-Atx<Q^E7UPzG?a#l-@%N?u%4ko^*X<aTIZU{~+
z!Bk&7DeEl~Z~R<@CLNyl!k>L4X1u+q@ia{8cJ%|-UDUcz1O|h^L5|7(rXTGv@g;$e
zx_~fJ-yj_RQjJ6WRd`;<jzgGIbzHrP9WLw$xxD@L+yYwyAb-+_9D3ke)%O{x!D@Aw
z%}M4jbHL6>rRds0qisBlCOlJ-UxFx$&X^e6`k7I$kCyfoS-k%EIlM@6k66ln#}FWg
zw{jjhvSZ~uBodI`h!%9OMIf_5COs^_Ki0eBf4oVsaISiGP96ZLNB{vSNP~f+0ic23
z%GLYYfFHhae!4K$(ZtEl#nH&**B1yLB`R6wlqgx&Xwq7IPLsD=Y()Qj1#<How48*!
z@~m8k?Qk8PQo(sl_T(#})t5?L)^Q%mjV|bA*K$@P;2L1_4!%;tVYd1H*F|Z|Z``D0
zQ8y<+>g9TRwPjYXY}Oh}_&?o`d`p-q_rklk`qtz4;`;^lO1$QnHCt2TK?bvW`C08k
zed9=D>yXDsdZ?3>oP37c{;;Zq-WmV<n@ldz-QuO!IJvh*8g%{HMdB@5ah`RS@0ME4
ztM^N)(zi8huRZxO4i=Wqk7b)255Hcy+SySA=&09h)iEGe`r&X)$rU$XzYDL-FLJ#@
zvcB;<c)*K2#M&4dhn_ixH(b<i@&9%`IUKaTz+mz)@G<|6tL~zQRC=cAQ1n*Vi9o1X
z6Kl2k!hy&(KB!&?fBkNXs$*nAuZAH(chA!w0v+$7Ga!BPc+2bl?H=7{jYf+MF^%aa
z$E{03g8S>dM1Adr;=%n66W6l+YMT^HPfh#yE%j5=Jkz@BqN^HNm@sB`N+LuP*>`G8
zWU^`9;r^we$V5e!f(mb{p*<=edg>^t_GqrY6q`1QQ%1UIN_EI><y)xhd%1SDBfR`P
zu{^c)YX4?J^r+v3SA=>$dr_@ypgY6-`-gJ&5`h@N#e|M85=n~wCd?bqT-7k4iF7}7
zNN#Y##+PvR3Eg~4kZfgk1K9(ouU~wpC{GV;{DQEm8uir*d#L^awWsA1T^(36e^5Bx
zH1Ki)6HtviY*jfQc*JdqdVRu###b^l_Y5NJ7dkN?OR98(!uPYINmKf)*@8Z~_pH&e
z_hUG4Muaz%i58;nf!7acs&1lFb?c%s2oPL6%wmwGb=sxWeX=XA>SOcU<yoQOfE@Kv
zKPSC>LwB%Bam-@*tfm$~mtqTU4Q>qO915PFxuy2O2iE(UFC54*izAWkMw%Fu-JFTk
z9#<O8t3x+GX8YGfUnCO7s*@WA4z-4Lav|p$-^Gf$qRNJ7i%bC@m!K-x!%+xc0+q&;
zA>UlapNY?vxT0SPMZ|t3`pHVC7fnbdT7xC&u#Maf0@(IMwT5##KUg6z`*VS;I!^m>
z;IK`?G1+P)A=Q^fXk^`*uv$vVaS!+IHjLs~^)^dlbz~xK1msE1p609c$mMnlQ>f5m
zaekJ=pNg!(`sl71A^Fj!+V<?3;MY9g08Hbmjrce8e0Kg!Rn_0XKV(DtQkN((at-8f
z>?Tke!xGnji4%c~Z)hFHpI^-V&evFn+i2Y-K}#)}o;3JM+iSZ%9@k{xW2*R$_6+ed
zj0@<|Rw>+0OChG=XazI6{ZQRN>-SjCYpYi)HFIB~&}$le!Qf4q!S;Dw3wkG@l{0xx
zR3p710sbnNt8P^mVELpzVEL3nz@K*nj4f%rH4S~=p6jVNfxR)xK0$U>f7O}mQT-uM
z1IdV#)SUcmUQo7F*C6I#Hqe4`JywM{4HXv*F-GXf#pGZ?S867#R7pr=|1Dl`^=;L2
z$cxVXAlMXq2ne!aWAP2~Krua%?3H<*K&O?nHB6@&`Rjbx>}mDq&(w3HI0LAi1U%=^
zm_<W)h)EPTJ;{nvf~I+%H`q+L%-xmIci$(g3saO9e=oB*J9!8ymGdKJ$`zj;90uV-
zMnIZ0?*!qZEH?yEtQ4^des5}nEm*5jfrD^(0r<WuAqj5~cXeIwu*$@cJ_}Xl8|bY)
zVj9Haz#?TC{JdTXGPE#1T3^Mbdsgxq13-R7hfS6%2_{?JH*h1Z%fAgvb?d8H$<X(e
ziS9VdFwPb6R$YKs1kd9hYW>3R?A`V4trOkmWpUaAZOHgmi^=EkBL<tLmXRvj-AT+P
zfb*7SUnT<ZmZ-Jm{df5uI4`UF@CQz|X<c1KRgjmG`^-(h69gB$cQiUE)f@Ja9CblK
z_a9G0;v~^7qhfaN%ZK@lTa>J@I9Lv|(gVxi1<T*<j<n9cogl?lAAeyvb8)CVec|4M
z)7{wls=zys3f-sT!)WrXCRQcd7LJ9PnKqxbjR6yB3S6k6wY&BuL<~gTRsZNIax|cM
zXrc9$joLKuX?ITPGTO>mf%svY?mcnC#w^wW1SK-${1`N8jVebY{J0u>{0?&?g55$L
z&c>I0Z8j<WEqL%M;44UKQ{b&cFDgh9v1~57=LAc4I`Gb3!)$p&ceCy%5sl{Z#9QRQ
zXDHHUu4*DKKW!rN)Li*^Z9yOeSk{L2Jy~s>^^sddAy2Uo=T1T*A;1z@=VJ|J`fmLC
z3xJ5p(8gQLz~RLNwyzaI5WHrq?UI2OgA1xcJku%*=aBw`$RY&P5EHnzT(-amIMGO$
zq8H7MQt+kOF?Nu}{k;hs`V<kC5?rCT-%C8qi?c@LM^50er<0)J7kyq-Zlt<}MO)<(
zovQE!+-G8CBm0Y1UV>BK`g)jHA45!z1Kq=OL_T<`vto?^=WD=R;SfX<Rv2djUaTU=
z%@=ZOl*#!@!Iv~qM2K>&M<Of<j0)2mk~>u<fmqsiGN(jcmYcVdT%TjI3tSiE`jC)B
zt<G}dKtWmAVAZ_A|2aV$7T*h|R9L6ISyh^`T1*wX-TS#W?4U|K_3KuuuXsskmD3k#
zXw2N#oFDAwbk3f)ycNZla?tGgVgsJw^Y(C<m=V{6LHNsp5gEih8jU52bwJBto~`#4
z?AJ@zPsZ&bXlJ&#YCB(NK8Jhin0#euvVHSy@-7FvkZk!4-oEQqX&+louos-tq*yDm
zB+71i*`;mnYa1-UU6BiXB|>{4B`V?WNTDx`F_t{3KZOb*(f2QKDDRF#EQC&YnPjo9
z)3HE-4e&Kv9><bwa1zsT>$cX&42lX#3e^`xh2Esuh6f8_upPs*MzImv#`~hzd?mD|
zYE0!Jw&qokUhG0DWY^kVCT#08$ht7wLMVb~(ITVuq+`Cv%GZ%FEn-wNXb;0BX}4wz
z)+uFpeS`(95joa8FTRLkvXw+_Mxo-Krb<?hcP)yw$W03JC_w}}xv^651d5{<a0G};
z6*q#b8CEOQjIy8|`o=T>=%W&ZGUW7&u0z*NE>9;+Q!sfANP2eV8q~i+u49V5gknlT
zqApGfbQEO$gj8i%pdb=0Zq97viZm{$CxDX#R*2F9DDHv*R|y%wFT6q8;ULy*Prz(~
zM@hPsjzZ+@zYnpGPsnc0)21YD@#o}N%eG7o3I3oaFI6v*n;JkEiy_Y)*{_vhW*-Gb
z@OGUBKAiUi15>tLPum&H>!cU>bgb~1Ita-Doz2Km*?!Q`*uAI3OK#XTGttX^K@{&Q
zJ?s$HlPQ{_V(R&RQAHTcQ|eqA>L@o^GuhTiL~Z~I2y~{*D{#t~G?4zT5YYG#SMkaN
zqtpZC+^`UZpoiR$aBw&07uB!k5;k}(Uh+%_2YcX|)s7$Ztf;uKJg^2-d9A3cELI)U
zS+__7Z~Czt%!mW`IN34TI=nioigHD#e@!@t#)F-R`62_Rbm7hISKPDJ^9EAHxduWc
zmWv@`Lt=YHqh|uUO6JhIx$Q`>0c7xb>)nL9xxnXj`}=ifwO)3OX}!d&Z^`?7G7tPC
zANa@EoEDd(Lb`+41KO<2n}DH1<3;RduZwrD?U|^C7W%c(IDJu9dM;HIoRFO%&U0u@
zcWazzM10;z1kf_^M;XS$a=lm4J(|cCa>i05Y78w5ZgyQgJQu`-aH5A9)GSZ#G+hfP
zyvw7FxDFtWc3A(qIZ$ljJuo!=wRO;cE?!Dn|NT~2QR^UB)FnpzZP}-K=;}}P5>=n-
zISjsHM!W%Mg!2Amp6F_4;WQiMJjnHiwwr~I>Uk3^1)l)(hZx9@ACvYPuwuabVX)Gp
z*EKO)tELNH$~dl`(a^*7-#O^2Y`W^QI-YngAJ&`d7n_pB@bEX$lvH`WbKBY>)ji!t
zL?(+KNU_=$;~j(EcE@u^Poi*s>2hB1${PHfG$K4|bvHd;%X3{Eq7AXF9_eczAtv#-
zEyqo~PCo0^gnW|lm8{GjUX!N~9P;jqk3PDnAJcqW96{(&s~dddQSVPbEm>xfo2HRj
zZa@^7@sL^KLKY=tusPoJPQid&`DS$Y_S2_YYxo?qmEA2|eXx>N$2`(I`lvH^#O{MX
zv)wk5ev!lt**h=k5762m7Hz^k$&9iIwRD^m-D(LhjW=}nQEcnU?pUAo;(OO0;mJq}
z{k=;?0Ba82ucK?Y&Ri)$kIh)Mtw>i^O8eX7dFf<lYu>PG8An>$I~ghTPqQ%xav;}n
zX?o(QTwbi)O=M@+hqy!K=daQ@rz(95J{a)9oidhFaJi2VUkA@u0oc{WtD~B`jb1D-
zmzjB9CX(${WAuEn!`QPcC%0v0kLjI-!qg<hFB>S*9p#a0>hSi0m+mx7RSZj8ZMAG|
zu@+Zu0fTi}Av}BO-pxJ5V($_99hAaHw_Oq<gYa`8z7Gqr7h!BRJLAhfOe~vF3iC`6
z-C%It3dhfDMif0RYE32D1s))1d%6PKwWq$gQ*b~7%>bZ*Hc1EupaETP7GegV0ZhjE
z6zKHYVf?v7a2|Pt%>4z&7W`=nME4fUqvIeKskORAVxNfY7<^?Cngcu41F)Btn;;<A
zSwtdT$csee(OIhCx#F$JIAW|(s{-Q(#2gBPDkRXV@82iP)@aWpTyPC$=O;4?pPE%y
zWn2kfI!(U=H+90usKY3K$B6QYJ_>l~#z@wXKAX0k#0b8PMC;wH=to35=a;c5AGjCi
zdP_>L)tc%&C_f77`#}pPD!-`oy%&Z)FATWE@UE&1Z0j05^m!NEO{-uz&NYb?8udlc
zP>q_ES9&37ntMLK_~>-qYWlEl<0E<FsL6Xg!d}kA*BaP8JxCjX!|JPNk)gHEi2aXn
zWFlGfL6~FGvqbf2g~J48L?*G|%*c?M12Cy8ck17`)QhulVy3X9G%ydED45z4vfI#Q
z_?CX2NCpQ!vMZDVGm1j*I~j7&854c+Oi~IvkkT|&2#ui@nt{F&lVlK0&ie#4D$B{Z
z44>cNBf*?-0TG}3S5okqc1ze(PG{J48?9uRV0P8sb1=wNasm#K#-bp0yS6Uj>FNmt
zB%f4gZ)iwm1du9GO!GPCjVa1+cT-*<k3;H&Zj^?71OQ;W`^U@qdqsDi45^?0G^GAp
zFRv6v%UCk!DOo<gypk3#YuU+&BzEPq*zWdx2hbw5D-=}_UPuQcDMyv%S{~LH@qsEy
zp2p{{WsN8VTj#2&xY$TZ&-s<7G|{x()b01m;<5qeJNCo#TE4I`jdzs}EAc{}^$&97
z7pxTNdw4Uu8`18JbfV8g<-6xFH=P{Yy%3u-PxDXOT?C&o_rMFVI$^Qdh^G-wKq=_o
zfDg#lp6(gHj(KaGy}+}cROvW0{j7hM{Pnol1$n-DI<|N4He*GWk&JC7pq?4J<^z1V
zj_RQ`9@CB&<N3TJ+2&EJ`tC$PmZD&WEb*NZHwBVWU^m;#g9g}~l$VBP*4af<Ly`?-
zaKMXqe0<>u_jLB1$J!I%eW`4?*5K<+#z;OnCF0E4;(TVV)xuD1a`K+%cu}*Z)|<aW
zj!0#zxq1mv@cB4T6|2#MrotTcb5ANsfR?8Hm#A~B?T<chpqZf82iDp$UHy*3s*)oW
zM+8SJ%;0)IaJy#d3tC|am0p9I<F<hBwNpqzu7$a13D_R;&{flcPSg5poI!Y(<qK7f
zYB5q|-p5ab9yGr>aGkjM$8$W;o3)=ZK>&aWU~~BQ?8>Fm=98vC^yjAV_&Nifk)wsP
ziKB%9y`__#t&1BR00jJTPUauKR8^h<pa8WJ|7Z@6lPp8Ag0_o{@S;~BjzR6Eop77f
zq8K$I3thd@gi3x`f=9ajFnFI?Am+=esz2N9c_wczY;^8AcMnENpH5K)W2hugpPlWh
z!@YDPqB{T=Bj(R+0_aA8A@~f-XGCYgilg{Y86bUSoiADGgo}rxLPP0TH~mWW)|2KP
zX0q~E6+pFvHdCtB!InjV6P1*Xj6iu3tg`bY2%Bg>C;Epdm)i5;E=6u%aw-)FC<OAk
z5wlD1Av96M^v~%1SkGe)P&$hy_hQ=d=ZrF3p-_|O<3QsXsUzMr^JM8U9_Mjl4T8AH
znE0p>s5!nI7+aU$z9QxMj9-5Sf~{I4(g5}q6Ozv{<&H^%&!=UM&1{7-<vB*}y@nkO
zm|jsSe-d(u*&Sk=SN&3MnZ26a$uJ(lHNs9EuC*v-$nx$g7kGTq#w4zJV5oMkUBTg~
zr8yW4AxnIUpy(&xFyV~zl#mgSo}q5?V~2QSD?;>J*wK3|2Ad+hw)@DfSM+;z8VG9w
zsE{SS(O_B>NcH+Dhkk1(Yj^CAfq*c8Zzlp+`|7}#I{sbzKL-M`U)28J4hT&D3J8Zf
zL$;_)NUbC%2&yAPaQ4=pK}bo#Q7|X{_FoizE^C=xj#ao=a$sBfUISy?e0gxtoj@JZ
zjBR#c_m;mY!fr)dTl-~C>f~OD5&!2FdN_lFi&N7+X@~2hb%z&Si0h@Mu2r$NoF!rO
zI7gcqmzCHn1iL*|FJJkYPGfI(z1f9&a}23%-BY)5s8&T#M<c~g`7k%NY+i)Xs2wat
z`4LA4R;?M!!2d&SRn;8|)j{il`e~Dyvr+wQMjN{t+j{j_ZJpzVkzL|T#wG^ayLwv}
zdyAB7Z4HWd*vglJi931~{P(-m)@(CjaZ(z$l9<_{tZ_>pKQ6F0DSzKFT;d(sjm=x1
z51y5t(kP%Y;JcBJ)j&~{%Az5k8l3i(R+HKvy{JkDL3VL|53VfXooUv|!d}W{!%w{s
zdp{G@TP(f()?9fgaqVgx=6+>mQW$GSRYxkn9`NO>ck|KK;r5uC+2QOIXvj(}qf+53
z)HLhztbv8(10*_cJmC!48pU33q@(SxZ>!1my2{0p)$++e50Ru376;A&^Oh%Ym5kX3
zP&LY17N6>DuuNhAx3y80@Zj?bBngCAG%xgMf_uXe8HF6s#|_qmRauUL%}uHmAz{Jp
zvh6>SiqsfD*bQ0+<<`9ybZCc`u}|R5k0*;8k)468SI2Yh`i{}j-vBzha41ZX*J5l$
znOi}~qaqCR&4Y|7XZ``^840*eo;Gkt$cqp7sFp|1w5Xd64wEwlm}St?UBTvymmMCc
z0uvnZN0NoO+AcG!A}}G6<tP#Iu~62gNRaBbck}IeOsXg6T%2}3ebp^?pFa}&nh!F~
zB!=Wq)W})mUtroz6?sG{rXQy^Zn4q6s=RMVPD9X151jp3tjunaRa^_w!56*2aL8oR
zpsas8*0&-{663PxQ)KD8SCIh{fZviKW;^_8T*`KsV0z%1Z3hf*Y7X03WyOuOdRH78
z+5s*m^o<1O$k=I$h9-wn`zACgq(vUo{cDBWRUVv48+SAX--wdvSyD&^d#O^+aO35C
z4f}jOwM;$lqr=PaZ&1E1_ekmjn4^Vj%V-~<ESa9c49!CHIZyi$x`LocOl(hPwqwr;
z8=d%9Sm74w$HSl$;#0JM_|#+HFyfMN8k);MRWc$;$4aPnN}>Q9WYH~|+;fX;!IPm-
zF27((_qq~~d#J-R%h`g7p+eGM0HA4_%#f8()j@}OGslM3U*R)DZB*!*J1_?FDJR?U
zNV-kF7(K}*OJn-d14aCqg9pW4BW|59lWDOF$vHN{xf3cZi49&5B1$w3Y3(`?hFK!K
z1U;HI{moF<<i5Q!&nm=v`m-4)e#5o)E{v{CE>Axgs_FJ-Z9_|wBZuj$@a!-`WN@aB
zy;mlyH489=-a<D*iAcWCjd&8KhGZsnkgr8JUvxtriCXA;q}?`h073<p1^m}lPNLFP
zea5mon(!%BKv1NL^us1pi<|iCR?;H7wkUd0C;XTNH@uaAzh+H)nn~<vd$_{8ZtfZ%
z0AHY>ZV7S4S|em{2~9uR5vPnW*|Su@K!!Lx|FDz6Y~N;Cn3)&}c!;6#5zdNO<VW|m
z#qVh6LRd6sv{$QU3>7zCLx@5Lhs1*REREW^VfX;rY!_;RX)hq%xF)=a>qpCew>@=z
zp8|nbNW^hN1({v1N_tSizU7%~VD`O0DND@O-{3jDm?+rGChDx?5Qj@XBT!n{58r%O
zlw|45H>sv?L~oZL+;89>BXTewfRz9kjTwA?jL7B^+fVW__FqTjUoUo$iAw)}9^TTC
zF3;&jUyfjX$a0yHHQT=AiKd<CGb9#$7fYE!i4&J)o%5bb$=jn;?cM{HaTaYyF(`;v
zDp&X0{LYDB=T%y^9J*fX{oYbj!mP&gxVU1am;{DTURQb7)1G>Hs`*PR3{X~k>z%y^
z!dDx&B^F6jLEVmc#SbsWOspreuTkJ!?Z%t1Q_T1AS`R--Y|smss3wc&msPQTGLWG0
zv|N3tzP;7)!dr@v+$em<N?j_sSMON#q4<1l{5Asd8ukEelZo$g>?Fh4g|*Lamghbz
z459q$YXlNk0;$|;ZXFXJ0Rw-*)Ch&D>U_L4*2o)YJQwto82q%$BYy=DsPZev48)b;
z)7PF2oOk>8(Ba!oPWBmLo+)^r6K?tERT}k2rYToF7<{Mlifk5j4IOmU5K``{Z^>s8
z<f-{fPPdlV_>a{^H!`>o<qhSI>Rtmv)lmY^9)kKU@6@eemGfl>q4aNh4Q_;W8nr5E
z9}H2_1id5orO`#VZ8MsOIt_8OR(krzTf!L}@*mWS{8|e_n2=q@_%(Y1*;He0$B|=Y
zH<;(G(hgL<V-!_OvDD(8C9y2(M6h#V#l<ORUmcBfv2an{=9l!QQGc+06N(aZ>wuTZ
z?#Y_8(bW4q?S)yK!BzHs-l#)f41d~$$WG;b6PHZV=ct#jdr3@6oXgkyr4thC`F5MR
z;g;=qWge_@qGPC!1TP5e)Uiv+!YiZ`hQ*#arm!WtbAqIHpal#}zwf6Zr4FHIb{Y$L
z9}V2UU0HM{Rm_NV?oJFQ`m&fsVGvN1wJ1?b^jvR;>n&+4wN#0DosyuY-)Bo2wQT{W
z<l2D1sz{BycQUOk{p1#JgI_h4;*D_UOBuEJ8Vh`3QxCgLeAh8sJUp?7azV?D?B6}Q
z*QnCO>J+$KE-t>Wn8U>-pH1r0oCO!xv%7i8!=CUmCtP%sFFz#N6lYkt2=Q4gvn6Y%
zg%GUYp2XYH${os4Kx4uRXST9&@jR}_I~+Qv2LlJy1;8B05@-;!b+_(oKB4gm>S218
z6D=zIabTtmw`$XP55=xO8HtRrD}m@_K6BX3rN6BIY*)HJLoT4nW}0eGQzX>8zNE?n
z^n{Y5#;vPA4M#jRLZ}nLBl~SzCZ0)&wh3l|kyYp$0c#W@;RZ^P!TX&Td-n(R-VQJ2
zrh=7<*B*MFck=Om+h{$?PR!9wb31jMnhV%PMXJWkJth=%<jVqe4q%dZC>xe0+r}Xm
zQ09?V5_zL#*|xr*WE3k3>m-XtOGU$14XVU4AJqt2Pj{e>11AV=-e8|GGp0!S;={9>
zgG8h1#g(WAL^bptFF*M;wZ41al6Nyi0tU(y&qTKo57Y!tz;vh*n=R>E%`;xIcQh-l
z-cY_Z9tkLpsd=}a6TVVaQyM=5sg4zG2v7jj!Pl$zW^Zjbi{$at)7I-^s~xjoHiZW6
z6xy@^3g0S|)=zB5ey@@^kv3!bz&~#V9*D*IHZAX~=Id!TeZvnQ;Z@xUZOhMAjKD_h
zvpyLn(OjrsZ5et!LnFOPrz82+`hxDd^&&9aOP0(XXSaEni$&C_C>n9jw1N;2L<Nx!
z2=;>2<V0E|>5Xfv*pN_;9V^JlmiG!>EF^Z+v-a~V!^Qce)KhDdZos!%`qiZia^4++
zSXtg%^I_$jg|~qV;W<J<fNi=~N9WqMm{V}d&IVu3rTW6f47TIEE^%{wovDEkSJ-UH
z7sSkWZ0cq;ET1F@mS06~?^^6MsmL@@f=F?(k(x}h<gre&EXfEo@ep5-hKS2}DFZ-W
z@5)I<<%NTvH)_LsyX(l6>Zrh!U|bBR&F3huK66)<NpSs0GJm@^LH*5&{l>b`Za1g@
zQVD$b><9%WTRk=242j|N0ZP8?S)C7yrTsyAke9!k+hRLWnnV*wDyPRQxC*!a0}N{8
zbZbjl`EZa+G)dvh6s8LuW*D7vU0xCnPz~;iT7wrN-x<v=aBdL#fzAxjE38VDgI!`W
z!j2O+i3)^^)1IdR3mj#6xbsUJwm`NcNX7G1!>lK5MF_0z+-xh6VZ1PQ$yc3Ye0%Us
zp?{GgrXa3z=wePrv$1$NnPp%t5p!f)@cOmx104tM)JU-u$8!i;GgsD0lyq@F=FpLw
zti=%zL+UmU+iWQFmx@FLjQkAi>x3!>Q+GvH7!%j+Ovbkw2lH>@>6P9y`j^_;CsV5;
zpv8*_>)$}{ntRWBGUM7GiWM%X@r_bWK*cQ~4&iZ`VD5^n(0XTLzg+A7#ExnuTMe!~
zugtr!6m)rf)bW~XU#IOR--E{3eS%Wqfuz3C0xk6A;<@aDC<D~3%=7FS&XSZprO}Wh
z>@y*8QHlhX+Hg5x>&B9$NSSO$K8c3<Yvg$IWP<lm%!7EUjFTX!^pggtEvMDIHd&|;
zo9%b&q-gn55kbUpgakvgjD@d{FwS$`lkme;C6$BC@DylJ$NE0g*skU*Ld$E8y+bEh
z2_2t(Ur|VWY3LBZXc#{8DG}`Dr6IzCN|SD#{-u3R+v$3CTDH?d7gj@rtZTNek`RhM
z2c$z@R9UiAInBp`nngThSyGF14(iH;{N-L$lNejZitP?mg0xhP?g1DJUF?O^8lf)o
z88Y~{4%M-rr3yd$QJP^ew4oTD2r)JLYUI@T&KZ^Z&e;i3>oWJXCFzXNG<w1if*5Vp
z_IyRdNtW(!nrd|2xO~yj1x8U2o$fPHjZc|Kj@Ii}fX;?EXQZpCj3=ta;Z3<U2pXu_
z!Jsb?Xd*!nYh}(5>R?_j>jou*&4)jq@2@Y&BvT`r_1P%<ni44{)=xmgk^FRQjCND&
z3|^$0f?E$UX>QltY*5QsHjQG#og@^vDP-$_1*X#9oxB}uTJTV@yPcP@uAP_7AX&1p
zAUs8aRX!6FXGFQs1XNOv#-wz<43B+zUTZ7xl}j6nT~`Q2Qlz!Bm%iy<?$V8@(xJZF
zR;-`s%MKn5nLuw2_Shf|@z8LM9$5{T0UQ}Q3Ga)SQbI_M@~@{~zJKl?fSoYJp{KOn
zq2CWvnj&H?R{b$VB)NqUF}-n?$C!UfFwKRWDncOAu@$tFmWYOtuu~-$QA)W6vs<xd
zh8!FsAMHZbdMs@)`?b;xYsCBG4!ABdGBTw3(CA`2G+SbHHr|p%%?xOFa5QCY{3_Ja
zlHBAlN0B%*e`hglhyYC$VL^}v(08ZpB^2XubZHXhHhbihdBO41dad1t>vhjm<M!^d
zh119ng^FyD$DC^_;C-tGuy-06jS^#W=DI&_Ck2MCR1Y2##_#gh^0Fs{`&*JTZm~W(
z(-7#)*Fa}l0-gC1=*+BGNv<{Gy^G6A!YD@4D$RK)27*NIDAXR!osh~g$*q|=_GC`-
zZ623V>_FXCJHk_rMlhO)J=yb8vv-QaxD!~?!A3Y?1_+BFc?ca48wedHsHchBaHbI<
z`>)Yq!rmD~@2q7Pi3Ljcb1R!WZBLb3aS7L%pM?sWPMmxJ+w#8aye)e!*tj<)&S6IG
ziDxiJdc%Ri?S+tns=N~n#%C4IVa;m5H%y*Lqvx7J0}H)yeI-DNSf=%c)~TDj^N4*>
z!Hf|ed#g<msvCNCUzfGD!61dDroo*7cWQCH0xY?RiYXo>^uz#OzZtk{5WjoPEnr}d
zFM~h{pN=IY|Nf1&lOJnNqeKpef#thy(#+^Y5u90o_1W`kK^@iw^I+HzjOozRtP3p_
z)*9q`B?DuBOlTvP8d|Ir8)f(!&h)y6c2>`}nt?r!A`r@NTHIfD%QbGbNKd&Nmvlv^
z;y8=?beI}G@*3UK7i1$|anHK%x9pNnRH+K{DP4yhi)#phyrm6<XLO3iP=E?0R0xtS
z>=+?0MpXM`M#Va^ii9%KiP?5*z8N}x{2lq`z{zst3^v9n6Qkn8baK5WR9q2PL<EWw
zNMye|1ay`EOK*GlCM0~yb_G7H9tFOXQTRxOE><(wQ=L>*J6lN95%v-cS-fOAGh?4c
zCoX~c-C>F6rM5<lELF<4kw=KkJ#BRMxHkO0Xti%;1coiXCxUBEUoye;uz6<Uiwr;=
z`LVxQ<-@J@kU<G_?Y(KWIv-&1#*%Y~CCz7GLyC@d1gJRn?|vM!{@9=xlC&Iqek<sK
zxwatKE(3Pu{h?xM8rFs)!d|bBYBt~)?D=}>CEF;GVVh}8z4B~|K!L5`F-TgYO&!=4
zYeC`ooaL=J&b0CsE}S>!Bt9;Je7_oFhr7S3h7+@a$cseCBX>A4{9u@a;H9}&vfs^2
zT$)U^8}|>r?YHwk`aP`k+674vX)VizHhf&Z-QEoRsC;&K+4S5|GUb@PImtjleg_MD
zy4+jKws$jCslK1swPv!J_D~-z9SsbD=aaoAWIPDB;c;^^ukC!C{84qVE#a)=xKB21
z7Ct4uus|%FlyEMpm{{%vc`Ufen>}Ak1SDZ8?^`aqZ?yEuaisOR{@{Ws>U*i<JX9`i
zO{!&q1||q-F0+dW2Ss%K(r;LkID_lnH$btKH}1A1OtX2WdiQs;lkF#mFsV+-gtC`d
z+{nn2A;3e=<Qs;SWM8=~!)iB8*u@v6H7w_pAnXdbf!NViQ`=<ZHWha+trVc|CE)jk
zVpGNJ+Un6mRh#REjJLARd)S~evIN{f3@QX{;c-A%Cm*KAiBpHmE;YNoWL6I_%3v}J
zfYM@h4G7xWu5gooLr>F&nKl9Yb;;BgPM$VZR=wa$-B}y8i5MYU;AAr89U-M|Qm+s)
z^RY!dQLG~#h?1PUi(+e@W_K&|hAC!+D+iuaCS%3>kIte|eIg41D}+O{RNuFo&11f5
zVcB|pEh1}u!J+^D2o_=1wwmZ0T~w%~c>v~826SMgZ7Nizn_I0Dl*rp1_VRs2o1pRM
z4Ka8C_pjD%+t_X(2Rk-u+#=MdvcRmdg$Dx6G8n)t!w$?cg1{^z4a_nc5Hi?<3~;uF
zY$va*60awDV!*A5X-!a(rbETsy45^l^2qBe5l^Arpa-|G-5?Hd!&Rvko`HyPZX_|F
znT`qTQ4(HFCY-ht+(zquanc*NN`d;MAf-44Dyp%oNfShundnZ=m7Xl}C6^QeH1*8a
zcQdo(Ez(p6Vm{40`z8crdjk|K*lmnFaC~Q8fKcU%9r<OadBGdL{y+!H*gS9(v?auq
z$p3odSPc4X<%<rC@u?mRHmm|)90nOjhD;>9ia&J|;*!>R>wW*-EyLpw9;+S^S{o4n
zpw0bp2><h>D#{;2czXj!XWQRBX8*XP0+Ov{`S=;2(r!B;fYhSC#}ChGFO>@RQ5Wf*
zl#f&m9+FUSrzvlpy5_M4w^0!E$?@Q<oU~|+l%nxrYntcna>})XJIL3CdjJLs>H0b>
zhU<ZLu|;Jndva*p2X^A;dLL$P?^-iql-(=|?4!;j*Qe74q8ZO#i+!jYyVhwJzVoJw
z@<d1jmwII^96J!1O6bQ5?UMW9{nw-W4V|6}&Toaduhka{2%+qY{4w&fP^9n}m1Yd1
zL62CTW#MIo+)@%vNk<+CjhB1LJFK|GnzT~j$B$A&o33YObgx%OoodsDo@Z=T8#Y8U
z6JXiSA40i3!=+xm+|G4onK#zT7(0aK&Y3;Y)j@DE)Iay^CaZ8Avmp_}-Xkm~daabI
zKcJw<CaG?M07jmv-Gnx)DM`PIo7}Mwc}{Bx<=ZORt`(y9+!Q9X0&yH5O&+IAGgt6h
z4Qi8Yl2u=h-rdAN$%q->6uw5qP{j-eCsb{YD#eDtkP|swK2kSltCSf`4gIxZ_ICKW
zdyRsQ#nf{;=jJ&-BeBX^4xbYfSP9n95u5?Xk?bQr#k}E~gnVzOX`HYtqUzK`@EM3Q
z_zNKhp7r7S8yW8&ibTW4?Keg=+eTr`M+o$n(5m^bYS@faG^OJ71u#%EdO%I%$%zz8
zd~}6Is*`&H6-3jnuqeQ8RH#kH{KP@C4pV0knv!r>a+H$Bk@|?0qK>a;+4bxSxII{?
zAg{6q?RmeXwqXsMf4Er#+xrZ;*RhA(!rW%L@Ls=c-5{?Ng=X4REI}^$Bo@ox0u+MD
zbB8j82WsyOZ&wl`S*1`#)C_?mj8E05IHAJMw_70r`ZCs4O+Qw#L}P6FP{D)KqI?$_
z*bNS&*Vo)I!k%zl(XUf-@TKOzo623SM&0MWu#+#QWqSsf@1pyO^G(B1<AZ3~A`+|Q
zj^X!^ZPHY{)#Uz-8c&E6tnb6R<#t1o1)|;Ai7WQ*CugVY|Bw!1Za(G$C;(6h`6wL_
zP&6>Kf9&!7Sv(K`tpDHp`ylxEr?G*v0mGkGpdbJskE;2dDflO*g#R#QWMKQs!0A6)
zeB6rsNX}bwZ`KS70BBSO0C0b>SmzV=lf{1;76H=z>qWD_psWb<bYYhC2Y?4b9q50R
z{$G?WZ0zkEo#{;6{_){#Vq<S@;B4~OMVY7gw{sqg^0@97E}qIN1_A&S1B)Z}15%yO
zr@x6L{14yh8Q5D0xj0$anm9Sh+8LWz|MTC!EcN43;U5+C2NyX#)e?9hmnAR&K=KKf
zB-p=K>VI=lGq83sQE;@gw{x<1T)g}r=*$hC7eNE*xBw?;MV`>%f&Z`Q82-yIk~a1R
zM$Z2OlQEBXWOP6#Q9veqPnb+U`>&W782}krIJ^H39QfgC7&w6(j)7toeZnCEnEn1C
zNTYwM=vPhhpP+h1E>6JnW+skOz#aRxCjSc+orK&b6(E&QKzHywp`wNSUr{l(voWyv
zUz$b)+u3_KAcJXOOXYsTfD`q<Vqo&h#P)w_5h}-V1`<F5`aqHLJ|Qp!jG_NUZJ0S4
z*qb~2FKR6%Z>OaPQiua;Q}79eOpO1Ef`u(`R{>BM|C>r@vYkfnfl-$f7{K_S(9i*9
zjsL<E)^<h)j~tx-2XWA)Dt<o(lIQ`p2d*b1zF_}XB!CB5{+H&!^l;U}3(TZRz<nKZ
zPw@3{{~rE76NsLvi?#JHLb;xa?ca{(?|Hvyzurh|9<l@gz9E4E@Skwvz<<i=(eu_8
zuT6}9n<opVWdA>70A2l$MEv;q$Jf);?hx`X3>y<?b35a|mD&kE?rWzbCT0)<ceH>2
z11t6u)=fWI{QYhiU}A^QRQi9yk138CXr4+Np71>|g6i=A0GLnA3xz)=Y~*fa{j2j#
zK;wiz7=QEtQ|;4U1L6<H9|W1>o*Fkc`Adh`sr}o<kBnu3j9W%s7UqEtK?UYKk{^uL
z`FQ==sI`HiiM12`e{_xE59}X-zBlY^Yjqh=F92i70|Nj+^aQ9s`A_Ws0Q$X?JaeDc
zz+;E!g0Tv21L!bkVCcem0)v+SE119B?*y!bpF1%k%{$tAYGUj>Kq*cElM~?+`+5bx
zvTyy^ZTh9S+6|x9%3}{SYnv064d|$pZD8bkf&x?gE0q6mNbaYu=wr12kG*Nvxgy)&
z1Isc9Ol%ZSkSgbXh4i1d3IV~oek#^M&5rhUZy3k5C;*@-1M*X2BVGLs*gwMdFa39*
z`fvX|O69cb>0!dBQVAyq`DfPnSKu(Q{Y$BE0M8Tt*nedMO2s+rtJEkk1C#?>@l&ZR
z{MqOqE%>*4>VR(I_(>}IKp^9GseLpU06>HGXQ|-P{E7V^K);ttz)vubQX#<`Qyd36
z%;ry0$zc5z%-@yD81O{rOf+TF1<-c)pQJMP;#c;6FO`L)r?p}WMA5j)m<(eC0J1<p
zev%3g$FETSvs4IwLV6UXxXj3;9<VH#C_hVu+u~P9e@iMqj%puuxd<$lu#kIwB^LmI
z{QPIBAlm%~?DtYR`Jq&gQlW17T~=W#ehOr2@t0C@F#fmx{y(dn-Jpd4vx+g?&r*5&
zXQO|#;Qu6*pR>vqFsqnETH)RRL1I~dmWo^XpV<Ea^n0nu{Y6$`(O2x*2Rh8_Pf}TH
z`W4LIl?rLoj`ngR@WDu6R&oE6R9IVnW&ih5$<u#YE6-bZv{id`c#`M=0OhTpvr5^g
zU!nYGsc@S<MIr~5Cz&ln1Qys23I&c<o@SMXqhBHYEvXd!RIGfz9ql%+hi`XcKro@7
zrNRLWKmQma{43Z4TkyZy01)i=QlWbI_hibWR4_jNPAd7pF2NHZ$G?=ycg?4+dhCGR
zhaX7|0HreWrw-WJpN;;}g8y5o;56=QyK<*x$pb+oIe(T4gV3MY{{i%Ssnq_3RG2Gv
zMsI))i~W;S4&{CY^LM3E35-`Sz?|ptfKq`6Hm|20FnNVv+5f#%>`b24N+)o1BQbK;
z&p-zNc%S|(l{uwfq5Nm5AWlC;ss@$^-o?QI99R}&^q-~j+WS{Xe@iNkKNZWVZby3y
z!i-l*6aXmD`B^GwfxiL!y;S-&o|ft{SAw#H+7AM2X#v>aFrIWP>wy3MQ7XT$n;%o-
zqYQn3!R7JukFTelyX}#uw(Xt&QijR~PYFNDFwHO{vK1&pyFba0W%N%*|4_$&E5jE+
z8H$;xv1S8%kYr3h%g}J@mq5Rl;m%JojBeb~o|E>AJ^*^@^`B(uwE8QUU&%05@2S5Y
z?Hdf6r~p$rU<c^4r!wqW`<4CQSM|>**+3M8w}(QJ)Bu3cm!D<0vhgdF|187GpUP7M
zL_&g^W^x2(U%o$e?$!{%o-|lsqxyFeu`)5Yvo`+af*-JhKlu~bW3hg`1?A~Tq8IHq
zV855)&!u|2ROQFBVNXZHC?-#V{<GH}uUPqUNc1T49}gToe<E`e=co4nR>=BM?T=l_
z$5G0Ur&^xQ8vtJlcv3O{%IW{%922lgeje99mgL8++GI~kV(a$TF#l7D9`}C#xTO4a
z4hr!0FQI-tcks9q{O3CPaoG*!Nl7}x{$>96tJFXb{j(w<fN2Q;5C(o%1E(49BY|UI
G!2bcIMC%Cv

literal 0
HcmV?d00001

diff --git a/src/data/method/criteria.json b/src/data/method/criteria.json
index b3d2820..8ae8826 100644
--- a/src/data/method/criteria.json
+++ b/src/data/method/criteria.json
@@ -55,6 +55,10 @@
     "id": "api-contract-tested",
     "description": "The API contract is tested and meets functional and non-functional requirements."
   },
+  {
+    "id": "automation-workflow-validated",
+    "description": "The workflow, rules, integrations, and relevant interface contracts have been validated and tested."
+  },
   {
     "id": "api-description-available",
     "description": "The API and its exposed capabilities are described clearly enough for review, audit, and onboarding."
diff --git a/src/data/method/cycles.json b/src/data/method/cycles.json
index ee1b679..b30a973 100644
--- a/src/data/method/cycles.json
+++ b/src/data/method/cycles.json
@@ -224,11 +224,12 @@
             "businessImpactCanvas",
             "locationsCanvas",
             "capacityCanvas",
-            "api-metrics-and-analytics"
+            "partner-integration-guidelines"
           ],
           "api-design": [
             "domainCanvas",
             "interactionCanvas",
+            "integration-style-selection-guide",
             "restCanvas",
             "eventCanvas",
             "graphqlCanvas",
@@ -238,7 +239,8 @@
             "api-development-best-practices",
             "api-testing-best-practices",
             "apiops-CI-CD-for-apis",
-            "api-security-best-practices"
+            "api-security-best-practices",
+            "partner-integration-guidelines"
           ],
           "api-audit": [
             "api-audit-checklist",
@@ -311,29 +313,31 @@
           "api-platform-architecture": [
             "businessImpactCanvas",
             "locationsCanvas",
-            "capacityCanvas"
+            "capacityCanvas",
+            "automation-operational-ownership-guide"
           ],
           "api-design": [
             "domainCanvas",
             "interactionCanvas",
-            "restCanvas",
-            "eventCanvas",
-            "graphqlCanvas",
-            "contract-first-design"
+            "process-workflow-design-guide",
+            "decision-business-rules-guide",
+            "automation-trigger-handoff-exception-guide"
           ],
           "api-delivery": [
-            "api-development-best-practices",
-            "api-testing-best-practices",
-            "apiops-CI-CD-for-apis"
+            "automation-testing-guide",
+            "automation-operational-ownership-guide",
+            "automation-rollback-supervision-guide"
           ],
           "api-audit": [
-            "api-audit-checklist",
+            "automation-readiness-checklist",
             "api-compliance-best-practices"
           ],
           "api-publishing": [
-            "api-onboarding-best-practices"
+            "automation-rollout-enablement-guide",
+            "service-agreement-template"
           ],
           "monitoring-and-improving": [
+            "automation-operational-ownership-guide",
             "api-metrics-and-analytics"
           ]
         },
@@ -344,7 +348,7 @@
         ],
         "exitCriteria": [
           "design-reflects-business-value",
-          "api-contract-tested",
+          "automation-workflow-validated",
           "audit-passed"
         ],
         "stationDescriptions": {
diff --git a/src/data/method/de/labels.criteria.json b/src/data/method/de/labels.criteria.json
index 60fdeaf..5583af0 100644
--- a/src/data/method/de/labels.criteria.json
+++ b/src/data/method/de/labels.criteria.json
@@ -15,6 +15,7 @@
   "criterion.design-reflects-business-value": "Das Schnittstellendesign und die offengelegten Fähigkeiten lassen sich klar auf Geschäftswert und Nutzerbedürfnisse zurückführen.",
   "criterion.api-consistency": "Das Schnittstellendesign folgt den vereinbarten Produkt-, Design- und Qualitätsstandards.",
   "criterion.api-contract-tested": "Der Schnittstellenvertrag wurde validiert und gegen funktionale und nicht-funktionale Anforderungen getestet.",
+  "criterion.automation-workflow-validated": "Workflow, Regeln, Integrationen und relevante Schnittstellenvertraege wurden validiert und getestet.",
   "criterion.api-description-available": "Die Schnittstelle und ihre Fähigkeiten sind ausreichend für Review, Auditierung und Onboarding dokumentiert.",
   "criterion.audit-passed": "Die Lösung besteht Qualitäts-, Sicherheits-, Compliance- und Bereitschaftsprüfungen.",
   "criterion.audit-reports-shared": "Audit-Ergebnisse und Maßnahmenentscheidungen wurden mit den relevanten Stakeholdern geteilt.",
diff --git a/src/data/method/de/labels.cycles.json b/src/data/method/de/labels.cycles.json
index c3213c8..983a00e 100644
--- a/src/data/method/de/labels.cycles.json
+++ b/src/data/method/de/labels.cycles.json
@@ -3,20 +3,20 @@
   "cycles.description": "Zielgruppenspezifische Ansichten auf den APIOps-Cycles-Methoden.",
   "cycle.capability-productization-cycle.title": "Capability-Produktisierungszyklus",
   "cycle.capability-productization-cycle.description": "Ein Zyklus, um Geschäftsfähigkeiten in wiederverwendbare digitale Capabilities zu überführen, bevor die Umsetzungsweise gewählt wird.",
-  "cycle.capability-productization-cycle.purpose": "Identifizieren und produktisieren Sie wiederverwendbare digitale Capabilities, bevor entschieden wird, ob die Umsetzungsweise APIs, Events, Dateien, Streams, Datenprodukte, KI-gestützte Services, direkte Integration oder ein Hybridmuster sein soll.",
+  "cycle.capability-productization-cycle.purpose": "Identifizieren und produktisieren Sie wiederverwendbare digitale Capabilities, bevor Sie einen API-, Event-, Datei-, Stream-, Datenprodukt-, KI-Service-, direkte Integrations- oder hybriden Implementierungsstil waehlen.",
   "cycle.api-productization-cycle.title": "API-Produktisierungszyklus",
   "cycle.api-productization-cycle.description": "Die API-fokussierte APIOps-Cycles-Journey für Produktisierung, Design, Bereitstellung, Veröffentlichung und Verbesserung von APIs.",
   "cycle.api-productization-cycle.purpose": "API-fokussierte Method Journey für Teams, die bereits wissen, dass die vorgesehene Umsetzungsweise ein API-Produkt ist.",
   "cycle.integration-productization-cycle.title": "Integrationszyklus",
-  "cycle.integration-productization-cycle.description": "Ein Zyklus zur Produktisierung wiederverwendbarer Integrations-Capabilities, bevor ein konkretes Integrationsmuster gewählt wird.",
-  "cycle.integration-productization-cycle.purpose": "Unterstützt das Design wiederverwendbarer Integrations-Capabilities, bevor APIs, Events, Dateien, Streams, Datenprodukte, direkte Integration oder Hybridmuster gewählt werden.",
-  "cycle.station.capability-strategy": "Strategie",
+  "cycle.integration-productization-cycle.description": "Ein Zyklus zur Produktisierung wiederverwendbarer Integrations-Capabilities, bevor der Implementierungsstil gewaehlt wird.",
+  "cycle.integration-productization-cycle.purpose": "Unterstuetzt das Design wiederverwendbarer Integrations-Capabilities, bevor ein API-, Event-, Datei-, Stream-, Datenprodukt-, direkte Integrations- oder hybrider Implementierungsstil gewaehlt wird.",
+  "cycle.station.capability-strategy": "Capability-Strategie",
   "cycle.station.consumer-requirements-onboarding": "Nutzeranforderungen & Onboarding",
   "cycle.station.architecture-platform-decisions": "Architektur & Plattformentscheidungen",
   "cycle.station.solution-interface-design": "Lösungs- & Schnittstellendesign",
   "cycle.station.delivery-operations": "Bereitstellung & Betrieb",
   "cycle.station.quality-readiness-assurance": "Qualitäts- & Bereitschaftssicherung",
-  "cycle.station.publishing-enablement": "Veröffentlichung & Adoption Enablement",
+  "cycle.station.publishing-enablement": "Veroeffentlichung & Enablement",
   "cycle.station.monitoring-improvement": "Monitoring & Verbesserung",
   "cycle.station.api-product-strategy": "API-Produktstrategie",
   "cycle.station.api-consumer-experience": "API Consumer Experience",
@@ -25,22 +25,22 @@
   "cycle.station.api-delivery": "API-Bereitstellung",
   "cycle.station.api-audit": "API-Audit",
   "cycle.station.api-publishing": "API-Veröffentlichung",
-  "cycle.station.monitoring-and-improving": "Monitoring & Verbesserung",
+  "cycle.station.monitoring-and-improving": "API-Monitoring & Verbesserung",
   "cycle.station.integration-capability-strategy": "Integrations-Capability-Strategie",
   "cycle.station.integration-consumer-requirements-onboarding": "Integrationsnutzeranforderungen & Onboarding",
-  "cycle.station.integration-architecture-decision": "Integrationsarchitekturentscheidung",
+  "cycle.station.integration-architecture-decision": "Integrationsarchitektur & Plattformentscheidungen",
   "cycle.station.integration-solution-design": "Integrationsdesign",
   "cycle.station.integration-delivery-operations": "Integrationsbereitstellung & Betrieb",
   "cycle.station.integration-readiness-assurance": "Integrationsbereitschaftssicherung",
-  "cycle.station.capability-publishing": "Capability-Veröffentlichung",
+  "cycle.station.capability-publishing": "Integrationsveroeffentlichung & Enablement",
   "cycle.station.integration-monitoring-improvement": "Integrationsmonitoring & Verbesserung",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Definieren Sie Wert, Nutzer, Ownership und Geschäftsziele der Capability, bevor etwas gebaut wird.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Rahmen Sie den Geschaeftsbedarf als wiederverwendbare Capability mit klarem Wert, Nutzern, Ownership und Geschaeftszielen, bevor der Implementierungsstil gewaehlt wird.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Erfassen Sie Nutzeranforderungen, Onboarding-Bedarf, Einschränkungen, Serviceerwartungen und Verantwortlichkeiten der Anbieter.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Nutzen Sie Anforderungen und Einschränkungen, um Architektur und Plattformfähigkeiten auszuwählen.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Nutzen Sie Anforderungen und Einschraenkungen, um Implementierungsstil, Architekturpattern und ermoeglichende Plattformfaehigkeiten auszuwaehlen.",
   "cycle.capability-productization-cycle.station.api-design.description": "Entwerfen Sie den Schnittstellenvertrag und das Interaktionsmodell für die gewählte Umsetzungsweise.",
   "cycle.capability-productization-cycle.station.api-delivery.description": "Bauen, testen, veröffentlichen und betreiben Sie die Capability mit der gewählten Umsetzungsweise und dem validierten Schnittstellenvertrag.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Sichern Sie Qualität, Governance und Bereitschaft vor der Veröffentlichung ab.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie Capability-Informationen so, dass Nutzer sie finden, Zugriff beantragen, onboarden und Support erhalten können.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Validieren Sie Schnittstellenvertrag, Kontrollen, Dokumentation, Supportmodell und operative Bereitschaft vor der Veroeffentlichung.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Veroeffentlichen Sie die Capability, damit Nutzer sie finden, bewerten, Zugriff beantragen, das Onboarding abschliessen, sie nutzen und Support erhalten koennen.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie Capability-Gesundheit, Nutzerergebnisse, Zuverlässigkeit, Wiederverwendung und Verbesserungsmöglichkeiten.",
   "cycle.owner.business-owner": "Business Owner",
   "cycle.owner.domain-expert": "Domänenexperte",
@@ -57,16 +57,16 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Wählen und validieren Sie API-Plattform, Architektur, Governance und betriebliche Einschränkungen, die für das Produkt benötigt werden.",
   "cycle.api-productization-cycle.station.api-design.description": "Entwerfen Sie API-Schnittstellenvertrag, Interaktionsmodell, Schemas, Policies und Usability-Details vor der Implementierung.",
   "cycle.api-productization-cycle.station.api-delivery.description": "Implementieren, testen, sichern, automatisieren und betreiben Sie das API-Produkt über die Bereitstellungspipeline.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validieren Sie API-Qualität, Compliance, Bereitschaft, Nachweise und Freigabekriterien vor der Veröffentlichung.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie das API-Produkt so, dass Nutzer es finden, bewerten, Zugriff beantragen, onboarden und Support erhalten können.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validieren Sie API-Qualitaet, Compliance, Nachweise, operative Bereitschaft und Freigabekriterien.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Veroeffentlichen Sie das API-Produkt, damit Nutzer es finden, bewerten, Zugriff beantragen, das Onboarding abschliessen, es nutzen und Support erhalten koennen.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie API-Gesundheit, Adoption, Nutzerergebnisse, Zuverlässigkeit und Verbesserungsmöglichkeiten nach der Veröffentlichung.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Rahmen Sie die wiederverwendbare Integrations-Capability, den Geschäftsbedarf, Ownership und erwartete Wiederverwendung, bevor ein Muster gewählt wird.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Rahmen Sie die wiederverwendbare Integrations-Capability, den Geschaeftsbedarf, Ownership und erwartete Wiederverwendung, bevor der Implementierungsstil gewaehlt wird.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Erfassen Sie Integrationsnutzer, Anbieter-Verantwortlichkeiten, Onboarding-Bedarf, Serviceerwartungen und operative Einschränkungen.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Entscheiden Sie Integrationsarchitektur, Plattformfähigkeiten, Einschränkungen und Governance-Modell für die Capability.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Entwerfen Sie Schnittstellenvertrag, Payloads, Events, APIs, Dateien oder Interaktionsmuster, die für die Integrations-Capability gewählt wurden.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Bauen, testen, automatisieren, veröffentlichen und betreiben Sie die Integrations-Capability mit dem gewählten Bereitstellungsmuster und dem validierten Schnittstellenvertrag.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Waehlen Sie Integrationsarchitektur, Implementierungsstil und Plattformfaehigkeiten unter Beruecksichtigung von Einschraenkungen und Governance-Modell.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Entwerfen Sie Schnittstellenvertrag, Schemas, Payloads und Interaktionsmuster fuer den gewaehlten Integrationsstil.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Bauen, testen, automatisieren, deployen und betreiben Sie die Integrations-Capability mit dem gewaehlten Implementierungsstil und dem validierten Schnittstellenvertrag.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Sichern Sie Integrationsbereitschaft, Governance, Qualität, Sicherheit, Compliance und operative Nachweise vor der Veröffentlichung ab.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Veröffentlichen Sie die Integrations-Capability so, dass Teams sie finden, anfragen, wiederverwenden, onboarden und Support erhalten können.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Veroeffentlichen Sie die Integrations-Capability, damit Teams sie finden, bewerten, Zugriff beantragen, das Onboarding abschliessen, wiederverwenden und Support erhalten koennen.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Überwachen Sie Integrationszuverlässigkeit, Wiederverwendung, Incidents, Performance, Nutzerergebnisse und Verbesserungsbedarf.",
   "cycle.automation-cycle.title": "Automatisierungszyklus",
   "cycle.automation-cycle.description": "Ein Zyklus zum Identifizieren, Entwerfen, Bereitstellen, Enablement und Verbessern von Automatisierungsmöglichkeiten.",
@@ -78,14 +78,14 @@
   "cycle.station.process-user-requirements": "Prozess-/Nutzeranforderungen",
   "cycle.station.automation-platform-decision": "Automatisierungsplattformentscheidung",
   "cycle.station.automation-workflow-design": "Automatisierungs-Workflow-Design",
-  "cycle.station.automation-delivery": "Automatisierungsbereitstellung",
+  "cycle.station.automation-delivery": "Automatisierungsbereitstellung & Betrieb",
   "cycle.station.automation-readiness-review": "Automatisierungsbereitschaftsprüfung",
-  "cycle.station.automation-enablement": "Automatisierungs-Enablement",
+  "cycle.station.automation-enablement": "Automatisierungs-Rollout & Enablement",
   "cycle.station.automation-monitoring-improvement": "Automatisierungsmonitoring & Verbesserung",
   "cycle.automation-cycle.station.api-product-strategy.description": "Identifizieren und priorisieren Sie Automatisierungsmöglichkeiten nach Wert, Machbarkeit, Risiko, Ownership und erwarteter Prozesswirkung.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Erfassen Sie Prozessnutzer, Rollen, Übergaben, Ausnahmen, Einschränkungen und Serviceerwartungen, bevor die Automatisierung entworfen wird.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Wählen Sie Automatisierungsplattform, Runtime, Integrationsmodell, Governance-Kontrollen und operative Einschränkungen.",
-  "cycle.automation-cycle.station.api-design.description": "Entwerfen Sie Automatisierungsworkflow, Trigger, Entscheidungspunkte, Integrationen, Datenverarbeitung, Schnittstellenverträge und Ausnahmefälle.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Waehlen Sie Automatisierungsplattform, Runtime, Integrationsansatz, Governance-Kontrollen und operative Einschraenkungen.",
+  "cycle.automation-cycle.station.api-design.description": "Entwerfen Sie Automatisierungsworkflow, Trigger, Entscheidungspunkte, Integrationen, Datenverarbeitung, relevante Schnittstellenvertraege und Ausnahmefaelle.",
   "cycle.automation-cycle.station.api-delivery.description": "Bauen, testen, deployen, dokumentieren und betreiben Sie die Automatisierung mit klarer Ownership, Kontrollen und Rollback-Pfaden.",
   "cycle.automation-cycle.station.api-audit.description": "Prüfen Sie Automatisierungsbereitschaft, Qualität, Risiko, Compliance, menschliche Aufsicht, Nachweise und Freigabekriterien.",
   "cycle.automation-cycle.station.api-publishing.description": "Befähigen Sie Nutzer und Betreiber mit Auffindbarkeit, Onboarding, Betriebsanweisungen, Supportpfaden und Änderungs kommunikation.",
diff --git a/src/data/method/en/labels.criteria.json b/src/data/method/en/labels.criteria.json
index 41ae368..ab563fa 100644
--- a/src/data/method/en/labels.criteria.json
+++ b/src/data/method/en/labels.criteria.json
@@ -15,6 +15,7 @@
   "criterion.design-reflects-business-value": "The interface design and exposed capabilities trace back to business value and consumer needs.",
   "criterion.api-consistency": "The interface design follows agreed design standards and conventions.",
   "criterion.api-contract-tested": "The interface contract has been validated and tested against functional and non-functional requirements.",
+  "criterion.automation-workflow-validated": "The workflow, rules, integrations, and relevant interface contracts have been validated and tested.",
   "criterion.api-description-available": "The interface and its capabilities are documented clearly enough for review, audit, and onboarding.",
   "criterion.audit-passed": "The solution passes quality, security, compliance, and readiness checks.",
   "criterion.audit-reports-shared": "Audit findings and remediation decisions are shared with the relevant stakeholders.",
diff --git a/src/data/method/en/labels.cycles.json b/src/data/method/en/labels.cycles.json
index 23d5f16..9cef79f 100644
--- a/src/data/method/en/labels.cycles.json
+++ b/src/data/method/en/labels.cycles.json
@@ -3,20 +3,20 @@
   "cycles.description": "Audience-specific views over the APIOps Cycles method",
   "cycle.capability-productization-cycle.title": "Capability Productization Cycle",
   "cycle.capability-productization-cycle.description": "A cycle for turning business capabilities into reusable digital capabilities before selecting the implementation style.",
-  "cycle.capability-productization-cycle.purpose": "Identify and productize reusable digital capabilities before deciding whether the delivery style should be APIs, events, files, streams, data products, AI-enabled services, direct integration, or a hybrid pattern.",
+  "cycle.capability-productization-cycle.purpose": "Identify and productize reusable digital capabilities before choosing an API, event, file, stream, data product, AI-enabled service, direct integration, or hybrid implementation style.",
   "cycle.api-productization-cycle.title": "API Productization Cycle",
   "cycle.api-productization-cycle.description": "The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.",
-  "cycle.api-productization-cycle.purpose": "API-focused method journey for teams that already know the intended delivery style is an API product.",
+  "cycle.api-productization-cycle.purpose": "API-focused method journey for teams that already know the intended implementation style is an API product.",
   "cycle.integration-productization-cycle.title": "Integration Productization Cycle",
-  "cycle.integration-productization-cycle.description": "A cycle for productizing reusable integration capabilities before selecting a concrete integration pattern.",
-  "cycle.integration-productization-cycle.purpose": "Guide reusable integration capability design before choosing APIs, events, files, streams, data products, direct integration, or hybrid patterns.",
-  "cycle.station.capability-strategy": "Strategy",
+  "cycle.integration-productization-cycle.description": "A cycle for productizing reusable integration capabilities before selecting the implementation style.",
+  "cycle.integration-productization-cycle.purpose": "Guide reusable integration capability design before choosing an API, event, file, stream, data product, direct integration, or hybrid implementation style.",
+  "cycle.station.capability-strategy": "Capability Strategy",
   "cycle.station.consumer-requirements-onboarding": "Consumer Requirements & Onboarding",
   "cycle.station.architecture-platform-decisions": "Architecture & Platform Decisions",
   "cycle.station.solution-interface-design": "Solution & Interface Design",
   "cycle.station.delivery-operations": "Delivery & Operations",
   "cycle.station.quality-readiness-assurance": "Quality & Readiness Assurance",
-  "cycle.station.publishing-enablement": "Publishing & Adoption Enablement",
+  "cycle.station.publishing-enablement": "Publishing & Enablement",
   "cycle.station.monitoring-improvement": "Monitoring & Improvement",
   "cycle.station.api-product-strategy": "API Product Strategy",
   "cycle.station.api-consumer-experience": "API Consumer Experience",
@@ -25,22 +25,22 @@
   "cycle.station.api-delivery": "API Delivery",
   "cycle.station.api-audit": "API Audit",
   "cycle.station.api-publishing": "API Publishing",
-  "cycle.station.monitoring-and-improving": "Monitoring & Improving",
+  "cycle.station.monitoring-and-improving": "API Monitoring & Improvement",
   "cycle.station.integration-capability-strategy": "Integration Capability Strategy",
   "cycle.station.integration-consumer-requirements-onboarding": "Integration Consumer Requirements & Onboarding",
-  "cycle.station.integration-architecture-decision": "Integration Architecture Decision",
+  "cycle.station.integration-architecture-decision": "Integration Architecture & Platform Decisions",
   "cycle.station.integration-solution-design": "Integration Solution Design",
   "cycle.station.integration-delivery-operations": "Integration Delivery & Operations",
   "cycle.station.integration-readiness-assurance": "Integration Readiness Assurance",
-  "cycle.station.capability-publishing": "Capability Publishing",
+  "cycle.station.capability-publishing": "Integration Publishing & Enablement",
   "cycle.station.integration-monitoring-improvement": "Integration Monitoring & Improvement",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define the capability’s value, consumers, ownership, and business goals.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Frame the business need as a reusable capability with clear value, consumers, ownership, and business goals before selecting the implementation style.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer requirements, onboarding needs, constraints, service expectations, and producer responsibilities.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to choose architecture and platform capabilities.",
-  "cycle.capability-productization-cycle.station.api-design.description": "Design the interface contract and interaction model for the selected delivery style.",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Build, test, deploy, and operate the capability using the selected delivery style and validated interface contract.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Assure quality, governance, and readiness before release.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish capability information so consumers can discover, request, onboard, and get support.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to select the implementation style, architecture pattern, and enabling platform capabilities.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Design the interface contract and interaction model for the selected implementation style.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Build, test, deploy, and operate the capability using the selected implementation style and validated interface contract.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Validate the interface contract, controls, documentation, support model, and operational readiness before release.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish the capability so consumers can discover it, evaluate it, request access, complete onboarding, use it, and get support.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor capability health, consumer outcomes, reliability, reuse, and improvement opportunities.",
   "cycle.owner.business-owner": "Business owner",
   "cycle.owner.domain-expert": "Domain expert",
@@ -57,16 +57,16 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choose and validate the API platform, architecture, governance, and operational constraints needed for the product.",
   "cycle.api-productization-cycle.station.api-design.description": "Design the API contract, interaction model, schemas, policies, and usability details before implementation.",
   "cycle.api-productization-cycle.station.api-delivery.description": "Implement, test, secure, automate, and operate the API product through the delivery pipeline.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validate API quality, compliance, readiness, evidence, and release criteria before publication.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Publish the API product so consumers can discover, evaluate, request access, onboard, and get support.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validate API quality, compliance, evidence, operational readiness, and release criteria.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publish the API product so consumers can discover it, evaluate it, request access, complete onboarding, use it, and get support.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitor API health, adoption, consumer outcomes, reliability, and improvement opportunities after release.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting a pattern.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Frame the reusable integration capability, business need, ownership, and expected reuse before selecting the implementation style.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capture integration consumers, provider responsibilities, onboarding needs, service expectations, and operational constraints.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decide the integration architecture, platform capabilities, constraints, and governance model for the capability.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Design the interface contract, payloads, events, APIs, files, or interaction patterns selected for the integration capability.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability using its selected delivery pattern and validated interface contract.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Select the integration architecture, implementation style, and platform capabilities, taking account of constraints and the governance model.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Design the interface contract, schemas, payloads, and interaction patterns for the selected integration style.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Build, test, automate, deploy, and operate the integration capability using its selected implementation style and validated interface contract.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Assure integration readiness, governance, quality, security, compliance, and operational evidence before release.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover, request, reuse, onboard, and get support.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publish the integration capability so teams can discover it, evaluate it, request access, complete onboarding, reuse it, and get support.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitor integration reliability, reuse, incidents, performance, consumer outcomes, and improvement needs.",
   "cycle.automation-cycle.title": "Automation Cycle",
   "cycle.automation-cycle.description": "A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.",
@@ -75,19 +75,19 @@
   "cycle.audience.process-owners": "Process owners",
   "cycle.audience.automation-teams": "Automation teams",
   "cycle.station.automation-opportunity-strategy": "Automation Opportunity Strategy",
-  "cycle.station.process-user-requirements": "Process/User Requirements",
+  "cycle.station.process-user-requirements": "Process & User Requirements",
   "cycle.station.automation-platform-decision": "Automation Platform Decision",
   "cycle.station.automation-workflow-design": "Automation Workflow Design",
-  "cycle.station.automation-delivery": "Automation Delivery",
+  "cycle.station.automation-delivery": "Automation Delivery & Operations",
   "cycle.station.automation-readiness-review": "Automation Readiness Review",
-  "cycle.station.automation-enablement": "Automation Enablement",
+  "cycle.station.automation-enablement": "Automation Rollout & Enablement",
   "cycle.station.automation-monitoring-improvement": "Automation Monitoring & Improvement",
   "cycle.automation-cycle.station.api-product-strategy.description": "Identify and prioritize automation opportunities by value, feasibility, risk, ownership, and expected process impact.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Capture process users, roles, handoffs, exceptions, constraints, and service expectations before designing the automation.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration model, governance controls, and operational constraints.",
-  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, interface contracts, and exception paths.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Choose the automation platform, runtime, integration approach, governance controls, and operating constraints.",
+  "cycle.automation-cycle.station.api-design.description": "Design the automation workflow, triggers, decision points, integrations, data handling, relevant interface contracts, and exception paths.",
   "cycle.automation-cycle.station.api-delivery.description": "Build, test, deploy, document, and operate the automation using clear ownership, controls, and rollback paths.",
   "cycle.automation-cycle.station.api-audit.description": "Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.",
-  "cycle.automation-cycle.station.api-publishing.description": "Enable users and operators with discovery, onboarding, operating instructions, support paths, and change communication.",
+  "cycle.automation-cycle.station.api-publishing.description": "Roll out the automation with discovery, onboarding, operating instructions, support paths, and change communication for users and operators.",
   "cycle.automation-cycle.station.monitoring-and-improving.description": "Monitor automation performance, exceptions, reliability, user outcomes, operational impact, and improvement opportunities."
-}
\ No newline at end of file
+}
diff --git a/src/data/method/en/labels.lines.json b/src/data/method/en/labels.lines.json
index 31ef36b..dda0025 100644
--- a/src/data/method/en/labels.lines.json
+++ b/src/data/method/en/labels.lines.json
@@ -4,9 +4,9 @@
   "line.business-opportunities-line.title": "Business Opportunities Line",
   "line.business-opportunities-line.description": "Focuses on identifying and shaping business opportunities as reusable digital capabilities.",
   "line.platform-architecture-line.title": "Platform Architecture Line",
-  "line.platform-architecture-line.description": "Covers architecture and platform decisions for reusable capabilities across delivery styles.",
+  "line.platform-architecture-line.description": "Covers architecture and platform decisions for reusable capabilities across implementation styles.",
   "line.api-design-line.title": "Design Line",
-  "line.api-design-line.description": "Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other delivery styles.",
+  "line.api-design-line.description": "Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.",
   "line.delivery-line.title": "Delivery Line",
   "line.delivery-line.description": "Covers delivery and operational practices for reusable capabilities across implementation styles.",
   "line.publishing-and-adoption-line.title": "Publishing and Adoption Line",
diff --git a/src/data/method/en/labels.resources.json b/src/data/method/en/labels.resources.json
index be023d4..415d146 100644
--- a/src/data/method/en/labels.resources.json
+++ b/src/data/method/en/labels.resources.json
@@ -438,5 +438,102 @@
   "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
   "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
   "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit.",
+  "resource.integration-style-selection-guide.title": "Integration Style Selection Guide",
+  "resource.integration-style-selection-guide.description": "Guidance for choosing between API, event, file, stream, data product, direct integration, or hybrid implementation styles based on requirements and constraints.",
+  "resource.integration-style-selection-guide.outcomes": "Justified integration implementation style",
+  "resource.integration-style-selection-guide.outcomes.1": "Tradeoffs documented across integration style options",
+  "resource.integration-style-selection-guide.outcomes.2": "Selected style traceable to consumer, platform, data, and operational requirements",
+  "resource.integration-style-selection-guide.steps": "Compare viable integration styles against latency, volume, coupling, data ownership, freshness, governance, and operability needs.",
+  "resource.integration-style-selection-guide.steps.1": "Identify when API, event, file, stream, data product, direct integration, or hybrid approaches fit the use case.",
+  "resource.integration-style-selection-guide.steps.2": "Document constraints, risks, and platform dependencies for the selected implementation style.",
+  "resource.integration-style-selection-guide.steps.3": "Record why rejected alternatives were not selected.",
+  "resource.integration-style-selection-guide.tips": "Use after requirements are explicit and before detailed contract design starts.",
+  "resource.integration-style-selection-guide.tips.1": "Keep REST, event, GraphQL, file, stream, and data product resources as optional follow-on design resources.",
+  "resource.process-workflow-design-guide.title": "Process Workflow Design Guide",
+  "resource.process-workflow-design-guide.description": "Guidance for modeling the process steps, roles, handoffs, decision points, states, inputs, outputs, and exceptions that shape an automation workflow.",
+  "resource.process-workflow-design-guide.outcomes": "Clear automation workflow design",
+  "resource.process-workflow-design-guide.outcomes.1": "Process steps and handoffs documented before implementation",
+  "resource.process-workflow-design-guide.outcomes.2": "Workflow states, inputs, outputs, and exception paths understood",
+  "resource.process-workflow-design-guide.steps": "Map the current and target process flow, including human and system responsibilities.",
+  "resource.process-workflow-design-guide.steps.1": "Identify workflow triggers, states, decisions, data inputs, outputs, and completion criteria.",
+  "resource.process-workflow-design-guide.steps.2": "Document handoffs between users, systems, operations, and support roles.",
+  "resource.process-workflow-design-guide.steps.3": "Confirm which steps should be automated and which require human judgment.",
+  "resource.process-workflow-design-guide.tips": "Keep process design separate from API or integration contract design until the workflow is clear.",
+  "resource.process-workflow-design-guide.tips.1": "Use this as the primary design resource for automation workflows.",
+  "resource.decision-business-rules-guide.title": "Decision And Business Rules Guide",
+  "resource.decision-business-rules-guide.description": "Guidance for capturing rules, thresholds, decisions, approvals, eligibility checks, and rule ownership for automation design.",
+  "resource.decision-business-rules-guide.outcomes": "Explicit decisions and business rules",
+  "resource.decision-business-rules-guide.outcomes.1": "Rules and thresholds documented with owners",
+  "resource.decision-business-rules-guide.outcomes.2": "Automation decisions traceable to policy, process, or business intent",
+  "resource.decision-business-rules-guide.steps": "List decisions the automation must make or support.",
+  "resource.decision-business-rules-guide.steps.1": "Document rule conditions, thresholds, exceptions, approvals, and escalation points.",
+  "resource.decision-business-rules-guide.steps.2": "Identify rule owners and change governance for each decision area.",
+  "resource.decision-business-rules-guide.tips": "Separate stable business rules from configurable operational parameters.",
+  "resource.decision-business-rules-guide.tips.1": "Use examples and edge cases to validate rule interpretation.",
+  "resource.automation-trigger-handoff-exception-guide.title": "Automation Trigger, Handoff And Exception Guide",
+  "resource.automation-trigger-handoff-exception-guide.description": "Guidance for defining automation triggers, human handoffs, exception handling, retries, compensating actions, and support escalation paths.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes": "Defined automation triggers and exception paths",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.1": "Human handoffs and support escalations are explicit",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.2": "Exceptions, retries, and compensating actions are designed before delivery",
+  "resource.automation-trigger-handoff-exception-guide.steps": "Define the events, schedules, user actions, or system states that trigger the automation.",
+  "resource.automation-trigger-handoff-exception-guide.steps.1": "Map handoffs from automation to users, operators, or support teams.",
+  "resource.automation-trigger-handoff-exception-guide.steps.2": "Document exceptions, retry rules, timeout behavior, and fallback paths.",
+  "resource.automation-trigger-handoff-exception-guide.steps.3": "Define alerts and escalation thresholds for failed or ambiguous automation outcomes.",
+  "resource.automation-trigger-handoff-exception-guide.tips": "Design exception paths as first-class workflow behavior, not as afterthoughts.",
+  "resource.automation-trigger-handoff-exception-guide.tips.1": "Include business and operations roles when validating handoffs.",
+  "resource.automation-testing-guide.title": "Automation Testing Guide",
+  "resource.automation-testing-guide.description": "Guidance for testing automated workflows, decisions, integrations, exceptions, rollback behavior, supervision, and user impact before release.",
+  "resource.automation-testing-guide.outcomes": "Validated automation behavior",
+  "resource.automation-testing-guide.outcomes.1": "Workflow, rule, exception, and integration tests defined",
+  "resource.automation-testing-guide.outcomes.2": "Release confidence for automated and human-assisted paths",
+  "resource.automation-testing-guide.steps": "Create tests for happy paths, edge cases, exceptions, retries, and handoffs.",
+  "resource.automation-testing-guide.steps.1": "Validate business rules and decision outcomes with representative data.",
+  "resource.automation-testing-guide.steps.2": "Test rollback, recovery, observability, and manual intervention paths.",
+  "resource.automation-testing-guide.steps.3": "Include users and operators in acceptance testing where the automation changes work practices.",
+  "resource.automation-testing-guide.tips": "Use production-like scenarios and data shapes without exposing sensitive data.",
+  "resource.automation-testing-guide.tips.1": "Keep test evidence available for readiness review.",
+  "resource.automation-operational-ownership-guide.title": "Automation Operational Ownership Guide",
+  "resource.automation-operational-ownership-guide.description": "Guidance for defining ownership, runbooks, supervision, support, monitoring, change control, and continuous improvement responsibilities for automations.",
+  "resource.automation-operational-ownership-guide.outcomes": "Clear automation operating model",
+  "resource.automation-operational-ownership-guide.outcomes.1": "Ownership, support, and escalation responsibilities assigned",
+  "resource.automation-operational-ownership-guide.outcomes.2": "Monitoring and change practices ready for live operation",
+  "resource.automation-operational-ownership-guide.steps": "Define business, technical, and operational owners for the automation.",
+  "resource.automation-operational-ownership-guide.steps.1": "Document runbooks, support paths, monitoring signals, service expectations, and escalation rules.",
+  "resource.automation-operational-ownership-guide.steps.2": "Set change control and review practices for workflow, platform, and rule updates.",
+  "resource.automation-operational-ownership-guide.tips": "Do not release an automation without a named owner for exceptions and ongoing improvement.",
+  "resource.automation-operational-ownership-guide.tips.1": "Make supervision needs visible before delivery planning finishes.",
+  "resource.automation-rollback-supervision-guide.title": "Automation Rollback And Supervision Guide",
+  "resource.automation-rollback-supervision-guide.description": "Guidance for designing rollback, pause, manual override, monitoring, supervision, and recovery paths for automations.",
+  "resource.automation-rollback-supervision-guide.outcomes": "Controlled automation recovery paths",
+  "resource.automation-rollback-supervision-guide.outcomes.1": "Rollback, pause, and override behavior documented",
+  "resource.automation-rollback-supervision-guide.outcomes.2": "Supervision needs and recovery responsibilities defined",
+  "resource.automation-rollback-supervision-guide.steps": "Identify actions that must be reversible, paused, or manually overridden.",
+  "resource.automation-rollback-supervision-guide.steps.1": "Define rollback, compensation, and recovery procedures for failed or incorrect automation outcomes.",
+  "resource.automation-rollback-supervision-guide.steps.2": "Document supervision thresholds, alerts, and manual decision points.",
+  "resource.automation-rollback-supervision-guide.steps.3": "Validate recovery procedures before release.",
+  "resource.automation-rollback-supervision-guide.tips": "Treat rollback and supervision as part of the workflow design and delivery plan.",
+  "resource.automation-rollback-supervision-guide.tips.1": "Use operational incidents and near misses to refine supervision criteria.",
+  "resource.automation-readiness-checklist.title": "Automation Readiness Checklist",
+  "resource.automation-readiness-checklist.description": "A checklist for validating automation workflow, controls, risk, compliance, human oversight, testing evidence, rollback, operations, and release readiness.",
+  "resource.automation-readiness-checklist.outcomes": "Documented automation readiness",
+  "resource.automation-readiness-checklist.outcomes.1": "Known readiness gaps and mitigations before release",
+  "resource.automation-readiness-checklist.outcomes.2": "Evidence for quality, risk, compliance, oversight, and operational approval",
+  "resource.automation-readiness-checklist.steps": "Review workflow design, business rules, controls, access, data handling, and exception paths.",
+  "resource.automation-readiness-checklist.steps.1": "Verify testing evidence, rollback procedures, supervision model, and support readiness.",
+  "resource.automation-readiness-checklist.steps.2": "Confirm ownership, runbooks, monitoring, change controls, and release approval.",
+  "resource.automation-readiness-checklist.steps.3": "Record unresolved gaps, decisions, and accepted risks before release.",
+  "resource.automation-readiness-checklist.tips": "Use before release and again after material workflow or rule changes.",
+  "resource.automation-readiness-checklist.tips.1": "Make human oversight and exception handling explicit in the evidence.",
+  "resource.automation-rollout-enablement-guide.title": "Automation Rollout And Enablement Guide",
+  "resource.automation-rollout-enablement-guide.description": "Guidance for rolling out automations with user communication, onboarding, operating instructions, support paths, change management, and feedback loops.",
+  "resource.automation-rollout-enablement-guide.outcomes": "Enabled automation users and operators",
+  "resource.automation-rollout-enablement-guide.outcomes.1": "Rollout communication, onboarding, and support paths prepared",
+  "resource.automation-rollout-enablement-guide.outcomes.2": "Users and operators understand how work changes after automation release",
+  "resource.automation-rollout-enablement-guide.steps": "Define rollout audiences, timing, communication channels, and training needs.",
+  "resource.automation-rollout-enablement-guide.steps.1": "Publish operating instructions, support paths, exception handling guidance, and escalation contacts.",
+  "resource.automation-rollout-enablement-guide.steps.2": "Plan transition support for users, operators, and process owners.",
+  "resource.automation-rollout-enablement-guide.steps.3": "Collect feedback after rollout and feed improvements into the backlog.",
+  "resource.automation-rollout-enablement-guide.tips": "Use rollout language for automations instead of treating enablement as API publication.",
+  "resource.automation-rollout-enablement-guide.tips.1": "Include both users affected by the process and operators responsible for the automation."
 }
diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json
index e4be48c..021d5c7 100644
--- a/src/data/method/en/labels.stations.json
+++ b/src/data/method/en/labels.stations.json
@@ -29,7 +29,7 @@
   "station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
   "station.api-platform-architecture.outcomes": "A justified architecture choice",
   "station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
-  "station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
+  "station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid implementation style",
   "station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
   "station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
   "station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
@@ -37,8 +37,8 @@
   "station.api-design.title": "Solution & Interface Design",
   "station.api-design.description": "Design the interface contract and interaction model after the architecture choice is justified.",
   "station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-  "station.api-design.apply_in_work": "Select the design resources that fit the chosen delivery style and document the interface contract before implementation.",
-  "station.api-design.outcomes": "A validated interface contract for the selected delivery style",
+  "station.api-design.apply_in_work": "Select the design resources that fit the chosen implementation style and document the interface contract before implementation.",
+  "station.api-design.outcomes": "A validated interface contract for the selected implementation style",
   "station.api-design.outcomes.1": "Consistent interaction, data, event, file, workflow, or API contract decisions",
   "station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
   "station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
@@ -51,9 +51,9 @@
   "station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the interface contract before implementation.",
   "station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
   "station.api-delivery.title": "Delivery & Operations",
-  "station.api-delivery.description": "Deliver the selected delivery style with appropriate engineering, testing, security, automation, and operational practices.",
+  "station.api-delivery.description": "Deliver the selected implementation style with appropriate engineering, testing, security, automation, and operational practices.",
   "station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-  "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the chosen delivery style.",
+  "station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the chosen implementation style.",
   "station.api-delivery.outcomes": "A delivered capability aligned with the validated interface contract",
   "station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
   "station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
@@ -66,10 +66,10 @@
   "station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
   "station.api-audit.title": "Quality & Readiness Assurance",
   "station.api-audit.description": "Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
-  "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
+  "station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before release or production use.",
   "station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
   "station.api-audit.outcomes": "Documented readiness for release and reuse",
-  "station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
+  "station.api-audit.outcomes.1": "Known gaps and mitigations before release",
   "station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
   "station.api-audit.outcomes.3": "Reduced risk of issues in production",
   "station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for interface contract, documentation, security, performance, and compliance readiness.",
@@ -376,7 +376,7 @@
   "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
-  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
+  "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
   "cycle.api-productization-cycle.station.api-product-strategy.apply_in_work": "Provide guidelines and templates for creating API business models, value propositions, and roadmaps.",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes": "A straightforward API value proposition and audience",
   "cycle.api-productization-cycle.station.api-product-strategy.outcomes.1": "Shared language between product, design, and tech",
@@ -384,10 +384,10 @@
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works": "Explore the customer or partner problem you expect to solve with APIs. Map the stakeholders, ther journeys and outcomes using the Customer Journey canvas.",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.1": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across journeys and eventually APIs.",
   "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the API Value Proposition Canvas to capture the supported business tasks and the API consumer pains, gains, and features that shape new or reusable APIs.",
-  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
-  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
-  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
+  "cycle.api-productization-cycle.station.api-product-strategy.how_it_works.3": "Define the value — for users and the business with the API Business Model canvas to make your API strategy visual, shareable, and easy to validate with your API consumers at the next station.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.title": "API Consumer Experience - Design for Your API’s Real Users",
+  "cycle.api-productization-cycle.station.api-consumer-experience.description": "Ensure your API is discoverable, understandable, and usable — before and after launch.",
+  "cycle.api-productization-cycle.station.api-consumer-experience.why_it_matters": "Great APIs don’t just work — they feel intuitive. Whether your consumer is an internal developer, external partner, or AI agent, their experience determines adoption.\n\nWithout a clear experience plan:\n- Great APIs go unused\n- Teams waste time guessing how to use your API\n- Feedback loops are broken or missing.\n\nThis station helps you see your API through the eyes of its consumers.",
   "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works": "Review the existing API Value Proposition Canvas from the API consumer perspective. Keep the supported business tasks stable, and enrich the pain-relieving and gain-enabling features with API consumer concerns so they can guide later design decisions.",
   "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use the Customer Journey Canvas for the API consumer journey from discovery and evaluation to onboarding, integration, troubleshooting, and ongoing use.",
   "cycle.api-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey to improve onboarding, documentation, support, and feedback loops for the API consumer.",
@@ -425,7 +425,7 @@
   "cycle.api-productization-cycle.station.api-design.how_it_works.7": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
   "cycle.api-productization-cycle.station.api-delivery.title": "API Delivery - Deliver Secure and Reliable APIs",
   "cycle.api-productization-cycle.station.api-delivery.description": "Build, test, and release APIs using modern delivery pipelines and engineering best practices.",
-  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
+  "cycle.api-productization-cycle.station.api-delivery.why_it_matters": "Even the best API designs fail if delivery is inconsistent. This station ensures your APIs are built with quality, tested thoroughly, and deployed reliably — enabling faster iterations and greater confidence.",
   "cycle.api-productization-cycle.station.api-delivery.apply_in_work": "Deliver coding frameworks, libraries, and standards for API implementation. Implement CI/CD pipelines, quality assurance frameworks, and deployment automation tools.",
   "cycle.api-productization-cycle.station.api-delivery.outcomes": "APIs implemented using tested frameworks and patterns",
   "cycle.api-productization-cycle.station.api-delivery.outcomes.1": "Reliable and automated CI/CD pipelines",
@@ -438,19 +438,19 @@
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.4": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
   "cycle.api-productization-cycle.station.api-delivery.how_it_works.5": "Use the API Audit Checklist to ensure the API meets functional and non-functional requirements, including security, performance, and compliance.",
   "cycle.api-productization-cycle.station.api-audit.title": "API Audit - Audit APIs for Compliance and Quality",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validate that APIs meet business, design, and operational standards before publishing and exposure.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validate that APIs meet business, design, and operational standards before release.",
   "cycle.api-productization-cycle.station.api-audit.why_it_matters": "APIs are long-lived products and must meet expectations for quality, consistency, and compliance. The audit connects design decisions, implementation, and operational readiness to defined standards, reducing risk before exposure.",
-  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before publishing.",
+  "cycle.api-productization-cycle.station.api-audit.apply_in_work": "Establish a consistent audit process that evaluates API readiness across lifecycle stages using defined criteria, evidence, and standards. Ensure gaps are identified early and resolved before release.",
   "cycle.api-productization-cycle.station.api-audit.outcomes": "APIs meet internal and external standards",
   "cycle.api-productization-cycle.station.api-audit.outcomes.1": "Clear documentation of API design and implementation decisions",
   "cycle.api-productization-cycle.station.api-audit.outcomes.2": "Security, performance, and compliance validated",
   "cycle.api-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
-  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before publishing.",
+  "cycle.api-productization-cycle.station.api-audit.how_it_works": "Conduct audits to ensure APIs meet organizational, technical, and legal standards before release.",
   "cycle.api-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
   "cycle.api-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure APIs are ready for production.",
   "cycle.api-productization-cycle.station.api-publishing.title": "API Publishing - Publish APIs with Confidence",
   "cycle.api-productization-cycle.station.api-publishing.description": "Expose APIs securely and clearly to the right audience with the right documentation and processes.",
-  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
+  "cycle.api-productization-cycle.station.api-publishing.why_it_matters": "Publishing is more than deploying — it’s about discoverability, access, and support. If APIs aren't published correctly, they won’t be used, reused, or secured effectively.",
   "cycle.api-productization-cycle.station.api-publishing.apply_in_work": "Enable APIs to be published to the relevant environment and have clear registration and access mechanisms (e.g., API keys, OAuth, subscription plans) depending on the API consumer segments and security and compliance requirements.",
   "cycle.api-productization-cycle.station.api-publishing.outcomes": "APIs published in the right environment (private, partner, public)",
   "cycle.api-productization-cycle.station.api-publishing.outcomes.1": "Clear API onboarding and registration processes",
@@ -461,7 +461,7 @@
   "cycle.api-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, gateway configuration, and legal terms are clear and accessible to consumers.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.title": "Monitoring and Improving - for API Value",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Use metrics and feedback to track API performance and drive continuous improvement.",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
+  "cycle.api-productization-cycle.station.monitoring-and-improving.why_it_matters": "API delivery doesn’t stop at launch. Without monitoring, teams can’t improve adoption, performance, or ROI. This station ensures APIs remain useful, secure, and evolving with business needs.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.apply_in_work": "Set up analytics frameworks to track performance and engagement. Develop feedback loops, analytics tools, and engagement strategies for APIs.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes": "Performance and usage metrics defined and tracked",
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.1": "Developer feedback loops in place",
@@ -469,101 +469,5 @@
   "cycle.api-productization-cycle.station.monitoring-and-improving.outcomes.3": "API iteration aligned with user needs",
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works": "Monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
   "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze API usage metrics and incorporate user feedback into API iterations.",
-  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.title": "Strategy",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Before building anything, define the capability’s value, consumers, ownership, and business goals.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.why_it_matters": "Integration and API work often jumps too quickly to a technical pattern. This station keeps the team focused on the business journey, domain meaning, value, reuse potential, ownership, and viability before selecting APIs, events, files, streams, data products, or direct integration.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.apply_in_work": "Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes": "A technology-agnostic capability opportunity statement",
-  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.1": "Shared understanding of consumers, producers, domain concepts, and reuse potential",
-  "cycle.capability-productization-cycle.station.api-product-strategy.outcomes.2": "A capability value proposition and business model before architecture selection",
-  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works": "Map the customer or partner journey that creates the capability need and reveals tasks, pains, gains, inputs, outputs, and decision points.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.1": "Define the core entities, attributes, relationships, ownership, and business rules that the capability must respect.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.2": "Use the Capability Value Proposition Canvas to capture consumer tasks, gains, pains, and reusable capability features without naming the delivery technology too early.",
-  "cycle.capability-productization-cycle.station.api-product-strategy.how_it_works.3": "Use the Capability Business Model Canvas to clarify ownership, partners, channels, costs, benefits, support, and lifecycle expectations for the reusable capability.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.title": "Consumer Requirements & Onboarding",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capture consumer onboarding, standards, non-functional requirements, service expectations, constraints, security needs, allowed protocols, data freshness, SLAs, observability, recovery, adoption requirements, and producer responsibilities.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.why_it_matters": "The right architecture depends on consumer goals, onboarding expectations, service levels, data quality needs, change tolerance, observability, support, and producer constraints.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works": "Use the Consumer Experience Requirements Canvas to capture consumer goals, availability, freshness, volume, performance, data quality, security, onboarding, change, observability, and recovery expectations.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.1": "Use onboarding guidance to describe how consumers will find, request, test, get approved for, and start using the capability.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.how_it_works.2": "Use the resulting journey and requirements to improve onboarding, documentation, support, and feedback loops for capability consumers.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.apply_in_work": "Use consumer experience and onboarding guidance to make expectations explicit for both consumers and producers.",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes": "Documented consumer requirements and onboarding expectations",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.1": "Clear producer responsibilities and support expectations",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.2": "Architecture-relevant constraints ready for decision making",
-  "cycle.capability-productization-cycle.station.api-consumer-experience.outcomes.3": "Improved adoption through consumer empathy, standards, and producer clarity",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.title": "Architecture & Platform Decisions",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Use requirements and constraints to decide the right architecture pattern and enabling platform capabilities.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.why_it_matters": "Architecture choices should follow from evidence about business impact, locations, trust boundaries, capacity, latency, data ownership, consistency, operability, security, privacy, governance, and cost.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.apply_in_work": "Compare viable architecture styles against the gathered requirements and document the selected pattern and rationale.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes": "A justified architecture choice",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.1": "Documented risks, locations, capacity, security, privacy, and operability constraints",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.outcomes.2": "Clear rationale for API, event, file, stream, data product, direct integration, or hybrid delivery",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works": "Use the Business Impact Canvas to identify availability, security, and data risks that influence architecture options.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.1": "Use the Locations Canvas to capture geopolitical, regulatory, network, residency, and trust-boundary constraints.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.2": "Use the Capacity Canvas to capture current and future volumes, peaks, latency, caching, rate limiting, and scaling expectations.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.how_it_works.3": "Use metrics and analytics guidance to define how the chosen capability will be monitored and improved.",
-  "cycle.capability-productization-cycle.station.api-design.title": "Solution & Interface Design",
-  "cycle.capability-productization-cycle.station.api-design.description": "Design the interface contract and interaction model for the selected delivery style.",
-  "cycle.capability-productization-cycle.station.api-design.why_it_matters": "Once the architecture pattern is known, the design must turn capability requirements into clear interface contracts, interactions, schemas, data rules, lifecycle expectations, and consumer obligations.",
-  "cycle.capability-productization-cycle.station.api-design.apply_in_work": "Select the design resources that fit the chosen delivery style and document the interface contract before implementation.",
-  "cycle.capability-productization-cycle.station.api-design.outcomes": "A validated interface contract for the selected delivery style",
-  "cycle.capability-productization-cycle.station.api-design.outcomes.1": "Consistent interaction, data, event, file, workflow, or API contract decisions",
-  "cycle.capability-productization-cycle.station.api-design.outcomes.2": "Design traceability back to capability and consumer requirements",
-  "cycle.capability-productization-cycle.station.api-design.outcomes.3": "Designs aligned with domain models and interaction patterns",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works": "Reuse the Domain Canvas to confirm business objects, terms, rules, and ownership before contract design.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.1": "Use the Interaction Canvas to describe how consumers, systems, or users interact with the capability.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.2": "Use REST design resources when the selected interface is a REST API.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.3": "Use Event Canvas resources when the selected interface is event-driven.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.4": "Use GraphQL design resources when the selected interface is GraphQL.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.5": "Use the design principles and style guidance to align design decisions with shared rules and enable consistent audit validation.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.6": "Apply contract-first or design-first approaches to capture and validate the interface contract before implementation.",
-  "cycle.capability-productization-cycle.station.api-design.how_it_works.7": "Use the audit checklist to ensure the design meets functional and non-functional requirements, including security, performance, and compliance.",
-  "cycle.capability-productization-cycle.station.api-delivery.title": "Delivery & Operations",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Build, test, deploy, and operate the capability using the selected delivery style and validated interface contract.",
-  "cycle.capability-productization-cycle.station.api-delivery.why_it_matters": "A reusable capability needs reliable delivery and operations regardless of whether it becomes an API, event stream, file exchange, data product, or direct integration.",
-  "cycle.capability-productization-cycle.station.api-delivery.apply_in_work": "Apply delivery, testing, CI/CD, operations, and security guidance to the chosen delivery style.",
-  "cycle.capability-productization-cycle.station.api-delivery.outcomes": "A delivered capability aligned with the validated interface contract",
-  "cycle.capability-productization-cycle.station.api-delivery.outcomes.1": "Automated testing, deployment, and environment controls",
-  "cycle.capability-productization-cycle.station.api-delivery.outcomes.2": "Security, operations, and quality practices appropriate to the chosen pattern",
-  "cycle.capability-productization-cycle.station.api-delivery.outcomes.3": "Traceable delivery and release controls",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works": "Use development best practices to implement the validated interface contract with established frameworks, libraries, and team standards.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.1": "Build the implementation from the validated interface contract using established frameworks, libraries, and team standards.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.2": "Use testing guidance to verify functionality, data quality, compatibility, security, performance, resilience, and recovery expectations.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.3": "Use CI/CD guidance to automate build, test, deployment, configuration, and traceability.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.4": "Use security guidance to protect data, access, credentials, and platform boundaries.",
-  "cycle.capability-productization-cycle.station.api-delivery.how_it_works.5": "Use the audit checklist to ensure the solution meets functional and non-functional requirements, including security, performance, and compliance.",
-  "cycle.capability-productization-cycle.station.api-audit.title": "Quality & Readiness Assurance",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Audit the capability interface contract, controls, support model, observability, documentation, and lifecycle readiness before release.",
-  "cycle.capability-productization-cycle.station.api-audit.why_it_matters": "Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before publishing or production use.",
-  "cycle.capability-productization-cycle.station.api-audit.apply_in_work": "Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.",
-  "cycle.capability-productization-cycle.station.api-audit.outcomes": "Documented readiness for release and reuse",
-  "cycle.capability-productization-cycle.station.api-audit.outcomes.1": "Known gaps and mitigations before publishing",
-  "cycle.capability-productization-cycle.station.api-audit.outcomes.2": "Evidence for governance, compliance, support, and operational approval",
-  "cycle.capability-productization-cycle.station.api-audit.outcomes.3": "Reduced risk of issues in production",
-  "cycle.capability-productization-cycle.station.api-audit.how_it_works": "Use the audit checklist as a reusable quality checklist for interface contract, documentation, security, performance, and compliance readiness.",
-  "cycle.capability-productization-cycle.station.api-audit.how_it_works.1": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-  "cycle.capability-productization-cycle.station.api-audit.how_it_works.2": "Collaborate with governance teams and domain experts to ensure the capability is ready for production.",
-  "cycle.capability-productization-cycle.station.api-publishing.title": "Publishing & Enablement",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Publish reusable capability information so consumers can discover, request, onboard, use, and get support.",
-  "cycle.capability-productization-cycle.station.api-publishing.why_it_matters": "Reusable capabilities only create value when consumers can find them, understand their interface contract and service expectations, request access, and know who owns support and lifecycle decisions.",
-  "cycle.capability-productization-cycle.station.api-publishing.apply_in_work": "Publish ownership, documentation, onboarding, support contacts, service expectations, lifecycle status, and access request paths.",
-  "cycle.capability-productization-cycle.station.api-publishing.outcomes": "A discoverable reusable capability",
-  "cycle.capability-productization-cycle.station.api-publishing.outcomes.1": "Clear onboarding, access, support, and service expectations",
-  "cycle.capability-productization-cycle.station.api-publishing.outcomes.2": "Lifecycle and ownership information available to consumers and governance teams",
-  "cycle.capability-productization-cycle.station.api-publishing.outcomes.3": "Consumers enabled to use and reuse the capability",
-  "cycle.capability-productization-cycle.station.api-publishing.how_it_works": "Publish capability information to the appropriate catalogs, portals, gateways, or environments to support reuse by multiple consumers.",
-  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.1": "Document how consumers find and use the capability, including onboarding processes and registration.",
-  "cycle.capability-productization-cycle.station.api-publishing.how_it_works.2": "Ensure security models, access configuration, and legal terms are clear and accessible to consumers.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.title": "Monitoring & Improvement",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitor usage, reliability, data quality, consumer outcomes, operational cost, and reuse opportunities after release.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.why_it_matters": "Capabilities need continuous feedback to stay reliable, valuable, cost-effective, and reusable as consumers, systems, data, and platforms change.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.apply_in_work": "Use metrics, analytics, and engagement practices to improve the capability over time.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes": "Measured capability health and value",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.1": "Improvement backlog informed by operational and consumer feedback",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.2": "Reuse, reliability, data quality, and cost signals available to owners",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.outcomes.3": "Continuous improvement aligned with consumer needs",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works": "Use metrics and analytics guidance to define capability usage, reliability, data quality, cost, adoption, and consumer-value measures.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.1": "Analyze usage metrics and incorporate consumer feedback into capability iterations.",
-  "cycle.capability-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
-}
\ No newline at end of file
+  "cycle.api-productization-cycle.station.monitoring-and-improving.how_it_works.2": "Establish a habit of reviewing metrics and planning continuous improvement activities."
+}
diff --git a/src/data/method/fi/labels.criteria.json b/src/data/method/fi/labels.criteria.json
index 0bb354e..8b60a38 100644
--- a/src/data/method/fi/labels.criteria.json
+++ b/src/data/method/fi/labels.criteria.json
@@ -15,6 +15,7 @@
   "criterion.design-reflects-business-value": "Rajapintasuunnittelu ja tarjottavat kyvykkyydet ovat jäljitettävissä liiketoiminta-arvoon ja hyödyntäjien tarpeisiin.",
   "criterion.api-consistency": "Rajapintasuunnittelu noudattaa sovittuja suunnittelustandardeja ja käytäntöjä.",
   "criterion.api-contract-tested": "Rajapintasopimus on validoitu ja testattu toiminnallisia ja ei-toiminnallisia vaatimuksia vasten.",
+  "criterion.automation-workflow-validated": "Tyonkulku, saannot, integraatiot ja olennaiset rajapintasopimukset on validoitu ja testattu.",
   "criterion.api-description-available": "Rajapinta ja sen kyvykkyydet on dokumentoitu riittävän selkeästi katselmointia, auditointia ja käyttöönottoa varten.",
   "criterion.audit-passed": "Ratkaisu läpäisee laatu-, tietoturva-, vaatimustenmukaisuus- ja valmiustarkastukset.",
   "criterion.audit-reports-shared": "Auditointihavainnot ja korjauspäätökset on jaettu olennaisille sidosryhmille.",
diff --git a/src/data/method/fi/labels.cycles.json b/src/data/method/fi/labels.cycles.json
index 845ff69..d54e7f4 100644
--- a/src/data/method/fi/labels.cycles.json
+++ b/src/data/method/fi/labels.cycles.json
@@ -3,20 +3,20 @@
   "cycles.description": "Kohderyhmäkohtaiset näkymät APIOps Cycles -menetelmään.",
   "cycle.capability-productization-cycle.title": "Kyvykkyyden tuotteistamisen sykli",
   "cycle.capability-productization-cycle.description": "Sykli liiketoiminnan kyvykkyyksien muuttamiseen uudelleenkäytettäviksi digitaalisiksi kyvykkyyksiksi ennen toteutustavan valintaa.",
-  "cycle.capability-productization-cycle.purpose": "Tunnista ja tuotteista uudelleenkäytettäviä digitaalisia kyvykkyyksiä ennen kuin päätetään, onko toteutustapa API, tapahtumat, tiedostot, virrat, datatuotteet, tekoälyä hyödyntävät palvelut, suora integraatio vai hybridimalli.",
+  "cycle.capability-productization-cycle.purpose": "Tunnista ja tuotteista uudelleenkaytettavia digitaalisia kyvykkyyksia ennen API-, tapahtuma-, tiedosto-, virta-, datatuote-, tekoalya hyodyntava palvelu-, suora integraatio- tai hybriditoteutustavan valintaa.",
   "cycle.api-productization-cycle.title": "API-tuotteistamisen sykli",
   "cycle.api-productization-cycle.description": "API-keskeinen APIOps Cycles -polku APIen tuotteistamiseen, suunnitteluun, toimittamiseen, julkaisuun ja parantamiseen.",
   "cycle.api-productization-cycle.purpose": "API-keskeinen menetelmäpolku tiimeille, jotka jo tietävät, että tarkoitettu toteutustapa on API-tuote.",
   "cycle.integration-productization-cycle.title": "Integraatiokyvykkyyden tuotteistamisen sykli",
-  "cycle.integration-productization-cycle.description": "Sykli uudelleenkäytettävien integraatiokyvykkyyksien tuotteistamiseen ennen konkreettisen integraatiomallin valintaa.",
-  "cycle.integration-productization-cycle.purpose": "Ohjaa uudelleenkäytettävän integraatiokyvykkyyden suunnittelua ennen APIen, tapahtumien, tiedostojen, virtojen, datatuotteiden, suoran integraation tai hybridimallien valintaa.",
-  "cycle.station.capability-strategy": "Strategia",
+  "cycle.integration-productization-cycle.description": "Sykli uudelleenkaytettavien integraatiokyvykkyyksien tuotteistamiseen ennen toteutustavan valintaa.",
+  "cycle.integration-productization-cycle.purpose": "Ohjaa uudelleenkaytettavan integraatiokyvykkyyden suunnittelua ennen API-, tapahtuma-, tiedosto-, virta-, datatuote-, suora integraatio- tai hybriditoteutustavan valintaa.",
+  "cycle.station.capability-strategy": "Kyvykkyysstrategia",
   "cycle.station.consumer-requirements-onboarding": "Hyödyntäjien vaatimukset ja käyttöönotto",
   "cycle.station.architecture-platform-decisions": "Arkkitehtuuri ja alustaratkaisut",
   "cycle.station.solution-interface-design": "Ratkaisu- ja rajapintasuunnittelu",
   "cycle.station.delivery-operations": "Toimitus ja operointi",
   "cycle.station.quality-readiness-assurance": "Laadun ja valmiuden varmistus",
-  "cycle.station.publishing-enablement": "Julkaisu ja käyttöönoton mahdollistaminen",
+  "cycle.station.publishing-enablement": "Julkaisu ja kayttoonoton tuki",
   "cycle.station.monitoring-improvement": "Seuranta ja parantaminen",
   "cycle.station.api-product-strategy": "API-tuotestrategia",
   "cycle.station.api-consumer-experience": "API-hyödyntäjäkokemus",
@@ -25,22 +25,22 @@
   "cycle.station.api-delivery": "API-toteutus",
   "cycle.station.api-audit": "API-auditointi",
   "cycle.station.api-publishing": "API-julkaisu",
-  "cycle.station.monitoring-and-improving": "Seuranta & parantaminen",
+  "cycle.station.monitoring-and-improving": "APIen seuranta ja parantaminen",
   "cycle.station.integration-capability-strategy": "Integraatiokyvykkyyden strategia",
   "cycle.station.integration-consumer-requirements-onboarding": "Integraation hyödyntäjien vaatimukset ja käyttöönotto",
-  "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuriratkaisu",
+  "cycle.station.integration-architecture-decision": "Integraatioarkkitehtuuri ja alustapaatokset",
   "cycle.station.integration-solution-design": "Integraation ratkaisusuunnittelu",
   "cycle.station.integration-delivery-operations": "Integraation toimitus ja operointi",
   "cycle.station.integration-readiness-assurance": "Integraation valmiuden varmistus",
-  "cycle.station.capability-publishing": "Kyvykkyyksien julkaisu",
+  "cycle.station.capability-publishing": "Integraation julkaisu ja kayttoonoton tuki",
   "cycle.station.integration-monitoring-improvement": "Integraation seuranta ja parantaminen",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Määrittele kyvykkyyden arvo, hyödyntäjät, omistajuus ja liiketoimintatavoitteet ennen kuin mitään rakennetaan.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Kuvaa liiketoimintatarve uudelleenkaytettavana kyvykkyytena, jolla on selkea arvo, hyodyntajat, omistajuus ja liiketoimintatavoitteet ennen toteutustavan valintaa.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Kokoa hyödyntäjien vaatimukset, käyttöönoton tarpeet, rajoitteet, palveluodotukset ja tuottajan vastuut.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Käytä vaatimuksia ja rajoitteita arkkitehtuurin ja alustakyvykkyyksien valintaan.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Kayta vaatimuksia ja rajoitteita toteutustavan, arkkitehtuurimallin ja mahdollistavien alustakyvykkyyksien valintaan.",
   "cycle.capability-productization-cycle.station.api-design.description": "Suunnittele rajapintasopimus ja vuorovaikutusmalli valitulle toteutustavalle.",
   "cycle.capability-productization-cycle.station.api-delivery.description": "Rakenna, testaa, julkaise ja operoi kyvykkyyttä valitulla toteutustavalla ja validoidulla rajapintasopimuksella.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Varmista laatu, hallintamalli ja julkaisukelpoisuus ennen julkaisua.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Julkaise kyvykkyyden tiedot, jotta hyödyntäjät voivat löytää sen, pyytää käyttöoikeutta, ottaa sen käyttöön ja saada tukea.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Validoi rajapintasopimus, kontrollit, dokumentaatio, tukimalli ja operatiivinen valmius ennen julkaisua.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Julkaise kyvykkyys, jotta hyodyntajat voivat loytaa sen, arvioida sen, pyytaa kayttooikeutta, suorittaa kayttoonoton, kayttaa sita ja saada tukea.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Seuraa kyvykkyyden tilaa, hyödyntäjien tuloksia, luotettavuutta, uudelleenkäyttöä ja parannusmahdollisuuksia.",
   "cycle.owner.business-owner": "Liiketoimintaomistaja",
   "cycle.owner.domain-expert": "Toimialan asiantuntija",
@@ -71,16 +71,16 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Valitse ja validoi API-tuotteen tarvitsema API-alusta, arkkitehtuuri, hallintamalli ja operatiiviset rajoitteet.",
   "cycle.api-productization-cycle.station.api-design.description": "Suunnittele API-rajapintasopimus, vuorovaikutusmalli, skeemat, käytännöt ja käytettävyyden yksityiskohdat ennen toteutusta.",
   "cycle.api-productization-cycle.station.api-delivery.description": "Toteuta, testaa, suojaa, automatisoi ja operoi API-tuotetta toimitusputken kautta.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validoi API-laatu, vaatimustenmukaisuus, valmius, näyttö ja julkaisukriteerit ennen julkaisua.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Julkaise API-tuote, jotta hyödyntäjät voivat löytää sen, arvioida sen, pyytää käyttöoikeutta, ottaa sen käyttöön ja saada tukea.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validoi API-laatu, vaatimustenmukaisuus, naytto, operatiivinen valmius ja julkaisukriteerit.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Julkaise API-tuote, jotta hyodyntajat voivat loytaa sen, arvioida sen, pyytaa kayttooikeutta, suorittaa kayttoonoton, kayttaa sita ja saada tukea.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Seuraa APIen tilaa, käyttöönottoa, hyödyntäjien tuloksia, luotettavuutta ja parannusmahdollisuuksia julkaisun jälkeen.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Rajaa uudelleenkäytettävä integraatiokyvykkyys, liiketoimintatarve, omistajuus ja odotettu uudelleenkäyttö ennen mallin valintaa.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Kuvaa uudelleenkaytettava integraatiokyvykkyys, liiketoimintatarve, omistajuus ja odotettu uudelleenkaytto ennen toteutustavan valintaa.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Kokoa integraation hyödyntäjät, tuottajan vastuut, käyttöönoton tarpeet, palveluodotukset ja operatiiviset rajoitteet.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Päätä integraatioarkkitehtuuri, alustakyvykkyydet, rajoitteet ja kyvykkyyden hallintamalli.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Suunnittele integraatiokyvykkyydelle valittu rajapintasopimus, tietosisällöt, tapahtumat, APIt, tiedostot tai vuorovaikutusmallit.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Valitse integraatioarkkitehtuuri, toteutustapa ja alustakyvykkyydet huomioiden rajoitteet ja hallintamalli.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Suunnittele rajapintasopimus, skeemat, tietosisallot ja vuorovaikutusmallit valitulle integraatiotavalle.",
   "cycle.integration-productization-cycle.station.api-delivery.description": "Rakenna, testaa, automatisoi, julkaise ja operoi integraatiokyvykkyyttä sen valitulla toteutustavalla ja validoidulla rajapintasopimuksella.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Varmista integraation valmius, hallintamalli, laatu, tietoturva, vaatimustenmukaisuus ja operatiivinen näyttö ennen julkaisua.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat löytää sen, pyytää käyttöoikeutta, käyttää sitä uudelleen, ottaa sen käyttöön ja saada tukea.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Julkaise integraatiokyvykkyys, jotta tiimit voivat loytaa sen, arvioida sen, pyytaa kayttooikeutta, suorittaa kayttoonoton, kayttaa sita uudelleen ja saada tukea.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Seuraa integraation luotettavuutta, uudelleenkäyttöä, häiriöitä, suorituskykyä, hyödyntäjien tuloksia ja parannustarpeita.",
   "cycle.automation-cycle.title": "Automaatiosykli",
   "cycle.automation-cycle.description": "Sykli automaatiomahdollisuuksien tunnistamiseen, suunnitteluun, toimittamiseen, käyttöönoton mahdollistamiseen ja parantamiseen.",
@@ -92,14 +92,14 @@
   "cycle.station.process-user-requirements": "Prosessin ja käyttäjien vaatimukset",
   "cycle.station.automation-platform-decision": "Automaatioalustan päätös",
   "cycle.station.automation-workflow-design": "Automaatiotyönkulun suunnittelu",
-  "cycle.station.automation-delivery": "Automaation toimitus",
+  "cycle.station.automation-delivery": "Automaation toimitus ja operointi",
   "cycle.station.automation-readiness-review": "Automaation valmiuskatselmointi",
-  "cycle.station.automation-enablement": "Automaation käyttöönoton mahdollistaminen",
+  "cycle.station.automation-enablement": "Automaation kayttoonotto ja kayttoonoton tuki",
   "cycle.station.automation-monitoring-improvement": "Automaation seuranta ja parantaminen",
   "cycle.automation-cycle.station.api-product-strategy.description": "Tunnista ja priorisoi automaatiomahdollisuudet arvon, toteutettavuuden, riskin, omistajuuden ja odotetun prosessivaikutuksen perusteella.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Kokoa prosessin käyttäjät, roolit, luovutukset, poikkeukset, rajoitteet ja palveluodotukset ennen automaation suunnittelua.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Valitse automaatioalusta, ajoympäristö, integraatiomalli, hallintakontrollit ja operatiiviset rajoitteet.",
-  "cycle.automation-cycle.station.api-design.description": "Suunnittele automaation työnkulku, käynnistimet, päätöspisteet, integraatiot, datankäsittely, rajapintasopimukset ja poikkeuspolut.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Valitse automaatioalusta, ajoymparisto, integraatiotapa, hallintakontrollit ja operatiiviset rajoitteet.",
+  "cycle.automation-cycle.station.api-design.description": "Suunnittele automaation tyonkulku, kaynnistimet, paatospisteet, integraatiot, datankasittely, olennaiset rajapintasopimukset ja poikkeuspolut.",
   "cycle.automation-cycle.station.api-delivery.description": "Rakenna, testaa, julkaise, dokumentoi ja operoi automaatiota selkeällä omistajuudella, kontrolleilla ja palautuspoluilla.",
   "cycle.automation-cycle.station.api-audit.description": "Katselmoi automaation valmius, laatu, riski, vaatimustenmukaisuus, ihmisen valvonta, näyttö ja julkaisukriteerit.",
   "cycle.automation-cycle.station.api-publishing.description": "Mahdollista käyttäjien ja operaattorien työ löydettävyyden, käyttöönoton, käyttöohjeiden, tukipolkujen ja muutosviestinnän avulla.",
diff --git a/src/data/method/fr/labels.criteria.json b/src/data/method/fr/labels.criteria.json
index 1270c1d..60a2d95 100644
--- a/src/data/method/fr/labels.criteria.json
+++ b/src/data/method/fr/labels.criteria.json
@@ -15,6 +15,7 @@
   "criterion.design-reflects-business-value": "La conception de l'interface et les capacités exposées sont clairement reliées à la valeur métier et aux besoins des utilisateurs.",
   "criterion.api-consistency": "La conception de l'interface respecte les standards partagés de produit, de conception et de qualité.",
   "criterion.api-contract-tested": "Le contrat d'interface a été validé et testé par rapport aux exigences fonctionnelles et non fonctionnelles.",
+  "criterion.automation-workflow-validated": "Le workflow, les regles, les integrations et les contrats d interface pertinents ont ete valides et testes.",
   "criterion.api-description-available": "L'interface et ses capacités sont documentées de manière suffisante pour la revue, l'audit et l'onboarding.",
   "criterion.audit-passed": "La solution réussit les contrôles de qualité, de sécurité, de conformité et de préparation.",
   "criterion.audit-reports-shared": "Les résultats d'audit et les décisions de correction sont partagés avec les parties prenantes concernées.",
diff --git a/src/data/method/fr/labels.cycles.json b/src/data/method/fr/labels.cycles.json
index ec6b41a..80b6d17 100644
--- a/src/data/method/fr/labels.cycles.json
+++ b/src/data/method/fr/labels.cycles.json
@@ -2,14 +2,14 @@
   "cycles.title": "Vues de cycle",
   "cycles.description": "Vues adaptées aux publics sur le méthode APIOps Cycles.",
   "cycle.capability-productization-cycle.title": "Cycle de productisation des capacités",
-  "cycle.capability-productization-cycle.description": "Productisez des capacités numériques réutilisables avant de décider si la mise en œuvre doit prendre la forme d’API, d’événements, de fichiers, de flux, de produits de données, de services basés sur l’IA, d’intégration directe ou d’un modèle hybride.",
-  "cycle.capability-productization-cycle.purpose": "Identifier et productiser des capacités numériques réutilisables avant de choisir le mode de mise en œuvre.",
+  "cycle.capability-productization-cycle.description": "Cycle pour transformer des capacites metier en capacites numeriques reutilisables avant de choisir le mode de mise en oeuvre.",
+  "cycle.capability-productization-cycle.purpose": "Identifier et productiser des capacites numeriques reutilisables avant de choisir un mode de mise en oeuvre API, evenement, fichier, flux, produit de donnees, service avec IA, integration directe ou hybride.",
   "cycle.api-productization-cycle.title": "Cycle de productisation des API",
   "cycle.api-productization-cycle.description": "Parcours APIOps Cycles centré sur les API pour productiser, concevoir, livrer, publier et améliorer des produits API.",
   "cycle.api-productization-cycle.purpose": "Parcours méthodologique centré sur les API pour les équipes qui savent déjà que le mode de mise en œuvre prévu est un produit API.",
   "cycle.integration-productization-cycle.title": "Cycle de productisation des capacités d’intégration",
-  "cycle.integration-productization-cycle.description": "Cycle pour productiser des capacités d’intégration réutilisables avant de choisir le modèle d’intégration concret.",
-  "cycle.integration-productization-cycle.purpose": "Guider la conception de capacités d’intégration réutilisables avant de choisir entre API, événements, fichiers, flux, produits de données, intégration directe ou modèles hybrides.",
+  "cycle.integration-productization-cycle.description": "Cycle pour productiser des capacites d integration reutilisables avant de choisir le mode de mise en oeuvre.",
+  "cycle.integration-productization-cycle.purpose": "Guider la conception de capacites d integration reutilisables avant de choisir un mode de mise en oeuvre API, evenement, fichier, flux, produit de donnees, integration directe ou hybride.",
   "cycle.station.capability-strategy": "Stratégie de capacité",
   "cycle.station.consumer-requirements-onboarding": "Exigences utilisateurs & onboarding",
   "cycle.station.architecture-platform-decisions": "Architecture & décisions de plateforme",
@@ -25,22 +25,22 @@
   "cycle.station.api-delivery": "Livraison d’API",
   "cycle.station.api-audit": "Audit API",
   "cycle.station.api-publishing": "Publication d’API",
-  "cycle.station.monitoring-and-improving": "Suivi & amélioration",
+  "cycle.station.monitoring-and-improving": "Suivi & amelioration API",
   "cycle.station.integration-capability-strategy": "Stratégie de capacité d’intégration",
   "cycle.station.integration-consumer-requirements-onboarding": "Exigences des utilisateurs d’intégration & onboarding",
-  "cycle.station.integration-architecture-decision": "Décision d’architecture d’intégration",
+  "cycle.station.integration-architecture-decision": "Architecture d integration & decisions de plateforme",
   "cycle.station.integration-solution-design": "Conception de solution d’intégration",
   "cycle.station.integration-delivery-operations": "Livraison & opérations d’intégration",
   "cycle.station.integration-readiness-assurance": "Assurance qualité des intégrations",
-  "cycle.station.capability-publishing": "Publication de capacité",
+  "cycle.station.capability-publishing": "Publication & enablement de l integration",
   "cycle.station.integration-monitoring-improvement": "Suivi & amélioration des intégrations",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Décrivez le besoin métier comme une stratégie de capacité réutilisable avant de choisir le mode de mise en œuvre.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Cadrer le besoin metier comme une capacite reutilisable avec une valeur, des utilisateurs, une responsabilite et des objectifs metier clairs avant de choisir le mode de mise en oeuvre.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Capturez les exigences des utilisateurs, les besoins d’onboarding, les contraintes, les attentes de service et les responsabilités des fournisseurs.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilisez les exigences et contraintes pour choisir l’architecture et les capacités de plateforme.",
-  "cycle.capability-productization-cycle.station.api-design.description": "Concevez le mode de mise en œuvre choisi et le contrat d’interface.",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Livrez et exploitez le mode de mise en œuvre choisi.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Assurez la qualité, la gouvernance et la préparation avant publication.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Publiez les informations de capacité afin que les utilisateurs puissent la découvrir, demander l’accès, s’onboarder et obtenir du support.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utiliser les exigences et contraintes pour choisir le mode de mise en oeuvre, le pattern d architecture et les capacites de plateforme necessaires.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Concevoir le contrat d interface et le modele d interaction pour le mode de mise en oeuvre choisi.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Construire, tester, deployer et exploiter la capacite avec le mode de mise en oeuvre choisi et le contrat d interface valide.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Valider le contrat d interface, les controles, la documentation, le modele de support et la preparation operationnelle avant publication.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publier la capacite afin que les utilisateurs puissent la decouvrir, l evaluer, demander l acces, terminer l onboarding, l utiliser et obtenir du support.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de la capacité, les résultats utilisateurs, la fiabilité, la réutilisation et les opportunités d’amélioration.",
   "cycle.owner.business-owner": "Responsable métier",
   "cycle.owner.domain-expert": "Expert domaine",
@@ -71,16 +71,16 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Choisissez et validez la plateforme API, l’architecture, la gouvernance et les contraintes opérationnelles nécessaires au produit.",
   "cycle.api-productization-cycle.station.api-design.description": "Concevez le contrat d’interface API, le modèle d’interaction, les schémas, les politiques et les détails d’utilisabilité avant l’implémentation.",
   "cycle.api-productization-cycle.station.api-delivery.description": "Implémentez, testez, sécurisez, automatisez et exploitez le produit API via le pipeline de livraison.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Validez la qualité, la conformité, la préparation, les preuves et les critères de publication de l’API avant publication.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Publiez le produit API afin que les utilisateurs puissent le découvrir, l’évaluer, demander l’accès, s’onboarder et obtenir du support.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Valider la qualite API, la conformite, les preuves, la preparation operationnelle et les criteres de publication.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publier le produit API afin que les utilisateurs puissent le decouvrir, l evaluer, demander l acces, terminer l onboarding, l utiliser et obtenir du support.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Suivez la santé de l’API, l’adoption, les résultats utilisateurs, la fiabilité et les opportunités d’amélioration après publication.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Cadrez la capacité d’intégration réutilisable, le besoin métier, la responsabilité et la réutilisation attendue avant de choisir un modèle.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Cadrer la capacite d integration reutilisable, le besoin metier, la responsabilite et la reutilisation attendue avant de choisir le mode de mise en oeuvre.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Capturez les utilisateurs d’intégration, les responsabilités des fournisseurs, les besoins d’onboarding, les attentes de service et les contraintes opérationnelles.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Décidez de l’architecture d’intégration, des capacités de plateforme, des contraintes et du modèle de gouvernance de la capacité.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Concevez la solution d’intégration, les contrats, les payloads, les événements, les API, les fichiers ou les modèles d’interaction choisis pour la capacité.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Construisez, testez, automatisez, déployez et exploitez la capacité d’intégration selon son modèle de livraison choisi.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Choisir l architecture d integration, le mode de mise en oeuvre et les capacites de plateforme en tenant compte des contraintes et du modele de gouvernance.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Concevoir le contrat d interface, les schemas, les payloads et les modeles d interaction pour le style d integration choisi.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Construire, tester, automatiser, deployer et exploiter la capacite d integration avec le mode de mise en oeuvre choisi et le contrat d interface valide.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Assurez la préparation, la gouvernance, la qualité, la sécurité, la conformité et les preuves opérationnelles de l’intégration avant publication.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Publiez la capacité d’intégration afin que les équipes puissent la découvrir, la demander, la réutiliser, s’onboarder et obtenir du support.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publier la capacite d integration afin que les equipes puissent la decouvrir, l evaluer, demander l acces, terminer l onboarding, la reutiliser et obtenir du support.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Suivez la fiabilité, la réutilisation, les incidents, la performance, les résultats utilisateurs et les besoins d’amélioration de l’intégration.",
   "cycle.automation-cycle.title": "Cycle d’automatisation",
   "cycle.automation-cycle.description": "Cycle pour identifier, concevoir, livrer, enable et améliorer des opportunités d’automatisation.",
@@ -89,17 +89,17 @@
   "cycle.audience.process-owners": "Responsables de processus",
   "cycle.audience.automation-teams": "Équipes d’automatisation",
   "cycle.station.automation-opportunity-strategy": "Stratégie d’opportunité d’automatisation",
-  "cycle.station.process-user-requirements": "Exigences processus/utilisateur",
+  "cycle.station.process-user-requirements": "Exigences processus & utilisateur",
   "cycle.station.automation-platform-decision": "Décision de plateforme d’automatisation",
   "cycle.station.automation-workflow-design": "Conception de workflow d’automatisation",
-  "cycle.station.automation-delivery": "Livraison de l’automatisation",
+  "cycle.station.automation-delivery": "Livraison & operations de l automatisation",
   "cycle.station.automation-readiness-review": "Revue de préparation de l’automatisation",
-  "cycle.station.automation-enablement": "Enablement de l’automatisation",
+  "cycle.station.automation-enablement": "Deploiement & enablement de l automatisation",
   "cycle.station.automation-monitoring-improvement": "Suivi & amélioration de l’automatisation",
   "cycle.automation-cycle.station.api-product-strategy.description": "Identifiez et priorisez les opportunités d’automatisation selon la valeur, la faisabilité, le risque, la responsabilité et l’impact attendu sur le processus.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Capturez les utilisateurs du processus, les rôles, les transferts, les exceptions, les contraintes et les attentes de service avant de concevoir l’automatisation.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Choisissez la plateforme d’automatisation, le runtime, le modèle d’intégration, les contrôles de gouvernance et les contraintes opérationnelles.",
-  "cycle.automation-cycle.station.api-design.description": "Concevez le workflow d’automatisation, les déclencheurs, les points de décision, les intégrations, le traitement des données et les chemins d’exception.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Choisir la plateforme d automatisation, le runtime, l approche d integration, les controles de gouvernance et les contraintes operationnelles.",
+  "cycle.automation-cycle.station.api-design.description": "Concevoir le workflow d automatisation, les declencheurs, les points de decision, les integrations, le traitement des donnees, les contrats d interface pertinents et les chemins d exception.",
   "cycle.automation-cycle.station.api-delivery.description": "Construisez, testez, déployez, documentez et exploitez l’automatisation avec une responsabilité et des chemins de rollback clairs.",
   "cycle.automation-cycle.station.api-audit.description": "Revoyez la préparation, la qualité, les risques, la conformité, la supervision humaine, les preuves et les critères de publication de l’automatisation.",
   "cycle.automation-cycle.station.api-publishing.description": "Enablez les utilisateurs et opérateurs avec découverte, onboarding, instructions d’exploitation, chemins de support et communication de changement.",
diff --git a/src/data/method/pt/labels.criteria.json b/src/data/method/pt/labels.criteria.json
index d4f434d..597ecdf 100644
--- a/src/data/method/pt/labels.criteria.json
+++ b/src/data/method/pt/labels.criteria.json
@@ -15,6 +15,7 @@
   "criterion.design-reflects-business-value": "A conceção da API e as capacidades expostas refletem claramente o valor de negócio e as necessidades dos utilizadores.",
   "criterion.api-consistency": "A conceção da API segue as nossas convenções partilhadas para o produto API e a conceção.",
   "criterion.api-contract-tested": "O contrato de interface da API é testado e satisfaz os requisitos funcionais e não funcionais.",
+  "criterion.automation-workflow-validated": "O fluxo de trabalho, as regras, as integracoes e os contratos de interface relevantes foram validados e testados.",
   "criterion.api-description-available": "A API e suas capacidades expostas são descritas de forma suficiente para revisão, auditoria e integração.",
   "criterion.audit-passed": "A API é aprovada nas verificações de conformidade, segurança e auditoria.",
   "criterion.audit-reports-shared": "Os resultados da auditoria e as decisões de correção são partilhados com as partes interessadas relevantes.",
diff --git a/src/data/method/pt/labels.cycles.json b/src/data/method/pt/labels.cycles.json
index c3677ab..fa21ade 100644
--- a/src/data/method/pt/labels.cycles.json
+++ b/src/data/method/pt/labels.cycles.json
@@ -3,20 +3,20 @@
   "cycles.description": "Vistas específicas por público sobre o método APIOps Cycles",
   "cycle.capability-productization-cycle.title": "Ciclo de Produto de Capacidades",
   "cycle.capability-productization-cycle.description": "Um ciclo para transformar capacidades de negócio em capacidades digitais reutilizáveis antes de selecionar o estilo de implementação.",
-  "cycle.capability-productization-cycle.purpose": "Identificar e transformar capacidades digitais reutilizáveis em produto antes de decidir se o estilo de disponibilização deve ser API, eventos, ficheiros, streams, produtos de dados, serviços com IA, integração direta ou um padrão híbrido.",
+  "cycle.capability-productization-cycle.purpose": "Identificar e transformar capacidades digitais reutilizaveis em produto antes de escolher um estilo de implementacao API, evento, ficheiro, stream, produto de dados, servico com IA, integracao direta ou hibrido.",
   "cycle.api-productization-cycle.title": "Ciclo de Produto de API",
   "cycle.api-productization-cycle.description": "A jornada APIOps Cycles focada em API para transformar APIs em produto, concebê-las, entregá-las, publicá-las e melhorá-las.",
-  "cycle.api-productization-cycle.purpose": "Jornada do método focada em API para equipas que já sabem que o estilo de disponibilização pretendido é um produto API.",
+  "cycle.api-productization-cycle.purpose": "Jornada do metodo focada em API para equipas que ja sabem que o estilo de implementacao pretendido e um produto API.",
   "cycle.integration-productization-cycle.title": "Ciclo de Produto de Integração",
-  "cycle.integration-productization-cycle.description": "Um ciclo para transformar capacidades de integração reutilizáveis em produto antes de selecionar um padrão de integração concreto.",
-  "cycle.integration-productization-cycle.purpose": "Orientar a conceção de capacidades de integração reutilizáveis antes de escolher APIs, eventos, ficheiros, streams, produtos de dados, integração direta ou padrões híbridos.",
-  "cycle.station.capability-strategy": "Estratégia",
-  "cycle.station.consumer-requirements-onboarding": "Requisitos e integração de consumidores",
+  "cycle.integration-productization-cycle.description": "Um ciclo para transformar capacidades de integracao reutilizaveis em produto antes de selecionar o estilo de implementacao.",
+  "cycle.integration-productization-cycle.purpose": "Orientar a concecao de capacidades de integracao reutilizaveis antes de escolher um estilo de implementacao API, evento, ficheiro, stream, produto de dados, integracao direta ou hibrido.",
+  "cycle.station.capability-strategy": "Estrategia da capacidade",
+  "cycle.station.consumer-requirements-onboarding": "Requisitos e onboarding de utilizadores",
   "cycle.station.architecture-platform-decisions": "Decisões de arquitetura e plataforma",
   "cycle.station.solution-interface-design": "Conceção da solução e da interface",
   "cycle.station.delivery-operations": "Entrega e operações",
   "cycle.station.quality-readiness-assurance": "Garantia de qualidade e prontidão",
-  "cycle.station.publishing-enablement": "Publicação e promoção da adoção",
+  "cycle.station.publishing-enablement": "Publicacao e enablement",
   "cycle.station.monitoring-improvement": "Monitorização e melhoria",
   "cycle.station.api-product-strategy": "Estratégia de produto API",
   "cycle.station.api-consumer-experience": "Experiência do consumidor da API",
@@ -25,22 +25,22 @@
   "cycle.station.api-delivery": "Entrega da API",
   "cycle.station.api-audit": "Auditoria da API",
   "cycle.station.api-publishing": "Publicação da API",
-  "cycle.station.monitoring-and-improving": "Monitorização e melhoria",
+  "cycle.station.monitoring-and-improving": "Monitorizacao e melhoria da API",
   "cycle.station.integration-capability-strategy": "Estratégia da capacidade de integração",
   "cycle.station.integration-consumer-requirements-onboarding": "Requisitos e integração de consumidores da integração",
-  "cycle.station.integration-architecture-decision": "Decisão de arquitetura da integração",
+  "cycle.station.integration-architecture-decision": "Arquitetura de integracao e decisoes de plataforma",
   "cycle.station.integration-solution-design": "Conceção da solução de integração",
   "cycle.station.integration-delivery-operations": "Entrega e operações da integração",
   "cycle.station.integration-readiness-assurance": "Garantia de prontidão da integração",
-  "cycle.station.capability-publishing": "Publicação da capacidade",
+  "cycle.station.capability-publishing": "Publicacao e enablement da integracao",
   "cycle.station.integration-monitoring-improvement": "Monitorização e melhoria da integração",
-  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor, os consumidores, a propriedade e os objetivos de negócio da capacidade.",
+  "cycle.capability-productization-cycle.station.api-product-strategy.description": "Enquadrar a necessidade de negocio como uma capacidade reutilizavel com valor, utilizadores, ownership e objectivos de negocio claros antes de selecionar o estilo de implementacao.",
   "cycle.capability-productization-cycle.station.api-consumer-experience.description": "Recolha requisitos dos consumidores, necessidades de integração, restrições, expectativas de serviço e responsabilidades dos produtores.",
-  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilize requisitos e restrições para escolher a arquitetura e as capacidades de plataforma.",
-  "cycle.capability-productization-cycle.station.api-design.description": "Conceba o contrato de interface e o modelo de interação para o estilo de disponibilização selecionado.",
-  "cycle.capability-productization-cycle.station.api-delivery.description": "Construa, teste, disponibilize e opere a capacidade usando o estilo de disponibilização selecionado e o contrato de interface validado.",
-  "cycle.capability-productization-cycle.station.api-audit.description": "Assegure a qualidade, a governação e a prontidão antes da disponibilização.",
-  "cycle.capability-productization-cycle.station.api-publishing.description": "Publique informação sobre a capacidade para que os consumidores a possam descobrir, solicitar, integrar e obter suporte.",
+  "cycle.capability-productization-cycle.station.api-platform-architecture.description": "Utilizar requisitos e restricoes para selecionar o estilo de implementacao, o padrao de arquitetura e as capacidades de plataforma necessarias.",
+  "cycle.capability-productization-cycle.station.api-design.description": "Conceber o contrato de interface e o modelo de interacao para o estilo de implementacao selecionado.",
+  "cycle.capability-productization-cycle.station.api-delivery.description": "Construir, testar, disponibilizar e operar a capacidade usando o estilo de implementacao selecionado e o contrato de interface validado.",
+  "cycle.capability-productization-cycle.station.api-audit.description": "Validar o contrato de interface, os controlos, a documentacao, o modelo de suporte e a prontidao operacional antes da publicacao.",
+  "cycle.capability-productization-cycle.station.api-publishing.description": "Publicar a capacidade para que os utilizadores a possam descobrir, avaliar, solicitar acesso, concluir o onboarding, utiliza-la e obter suporte.",
   "cycle.capability-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da capacidade, os resultados dos consumidores, a fiabilidade, a reutilização e as oportunidades de melhoria.",
   "cycle.owner.business-owner": "Responsável de negócio",
   "cycle.owner.domain-expert": "Especialista de domínio",
@@ -57,16 +57,16 @@
   "cycle.api-productization-cycle.station.api-platform-architecture.description": "Escolha e valide a plataforma API, a arquitetura, a governação e as restrições operacionais necessárias para o produto.",
   "cycle.api-productization-cycle.station.api-design.description": "Conceba o contrato de interface da API, o modelo de interação, os esquemas, as políticas e os detalhes de usabilidade antes da implementação.",
   "cycle.api-productization-cycle.station.api-delivery.description": "Implemente, teste, proteja, automatize e opere o produto API através do pipeline de entrega.",
-  "cycle.api-productization-cycle.station.api-audit.description": "Valide a qualidade, a conformidade, a prontidão, as evidências e os critérios de disponibilização da API antes da publicação.",
-  "cycle.api-productization-cycle.station.api-publishing.description": "Publique o produto API para que os consumidores o possam descobrir, avaliar, solicitar acesso, integrar e obter suporte.",
+  "cycle.api-productization-cycle.station.api-audit.description": "Validar a qualidade da API, a conformidade, as evidencias, a prontidao operacional e os criterios de publicacao.",
+  "cycle.api-productization-cycle.station.api-publishing.description": "Publicar o produto API para que os utilizadores o possam descobrir, avaliar, solicitar acesso, concluir o onboarding, utiliza-lo e obter suporte.",
   "cycle.api-productization-cycle.station.monitoring-and-improving.description": "Monitorize a saúde da API, a adoção, os resultados dos consumidores, a fiabilidade e as oportunidades de melhoria após a disponibilização.",
-  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Enquadre a capacidade de integração reutilizável, a necessidade de negócio, a propriedade e a reutilização esperada antes de selecionar um padrão.",
+  "cycle.integration-productization-cycle.station.api-product-strategy.description": "Enquadrar a capacidade de integracao reutilizavel, a necessidade de negocio, o ownership e a reutilizacao esperada antes de selecionar o estilo de implementacao.",
   "cycle.integration-productization-cycle.station.api-consumer-experience.description": "Recolha consumidores da integração, responsabilidades dos fornecedores, necessidades de integração, expectativas de serviço e restrições operacionais.",
-  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Decida a arquitetura de integração, as capacidades de plataforma, as restrições e o modelo de governação da capacidade.",
-  "cycle.integration-productization-cycle.station.api-design.description": "Conceba o contrato de interface, payloads, eventos, APIs, ficheiros ou padrões de interação selecionados para a capacidade de integração.",
-  "cycle.integration-productization-cycle.station.api-delivery.description": "Construa, teste, automatize, disponibilize e opere a capacidade de integração usando o padrão de disponibilização selecionado e o contrato de interface validado.",
+  "cycle.integration-productization-cycle.station.api-platform-architecture.description": "Selecionar a arquitetura de integracao, o estilo de implementacao e as capacidades de plataforma, tendo em conta as restricoes e o modelo de governacao.",
+  "cycle.integration-productization-cycle.station.api-design.description": "Conceber o contrato de interface, os esquemas, os payloads e os padroes de interacao para o estilo de integracao selecionado.",
+  "cycle.integration-productization-cycle.station.api-delivery.description": "Construir, testar, automatizar, disponibilizar e operar a capacidade de integracao usando o estilo de implementacao selecionado e o contrato de interface validado.",
   "cycle.integration-productization-cycle.station.api-audit.description": "Assegure a prontidão, a governação, a qualidade, a segurança, a conformidade e as evidências operacionais da integração antes da disponibilização.",
-  "cycle.integration-productization-cycle.station.api-publishing.description": "Publique a capacidade de integração para que as equipas a possam descobrir, solicitar, reutilizar, integrar e obter suporte.",
+  "cycle.integration-productization-cycle.station.api-publishing.description": "Publicar a capacidade de integracao para que as equipas a possam descobrir, avaliar, solicitar acesso, concluir o onboarding, reutiliza-la e obter suporte.",
   "cycle.integration-productization-cycle.station.monitoring-and-improving.description": "Monitorize a fiabilidade da integração, a reutilização, os incidentes, o desempenho, os resultados dos consumidores e as necessidades de melhoria.",
   "cycle.automation-cycle.title": "Ciclo de Automação",
   "cycle.automation-cycle.description": "Um ciclo para identificar, conceber, entregar, capacitar e melhorar oportunidades de automação.",
@@ -75,17 +75,17 @@
   "cycle.audience.process-owners": "Responsáveis pelo processo",
   "cycle.audience.automation-teams": "Equipas de automação",
   "cycle.station.automation-opportunity-strategy": "Estratégia da oportunidade de automação",
-  "cycle.station.process-user-requirements": "Requisitos do processo/utilizador",
+  "cycle.station.process-user-requirements": "Requisitos do processo e dos utilizadores",
   "cycle.station.automation-platform-decision": "Decisão de plataforma de automação",
   "cycle.station.automation-workflow-design": "Conceção do fluxo de trabalho de automação",
-  "cycle.station.automation-delivery": "Entrega da automação",
+  "cycle.station.automation-delivery": "Entrega e operacao da automacao",
   "cycle.station.automation-readiness-review": "Revisão de prontidão da automação",
-  "cycle.station.automation-enablement": "Capacitação da automação",
+  "cycle.station.automation-enablement": "Rollout e enablement da automacao",
   "cycle.station.automation-monitoring-improvement": "Monitorização e melhoria da automação",
   "cycle.automation-cycle.station.api-product-strategy.description": "Identifique e priorize oportunidades de automação por valor, viabilidade, risco, propriedade e impacto esperado no processo.",
   "cycle.automation-cycle.station.api-consumer-experience.description": "Recolha utilizadores do processo, funções, transferências, exceções, restrições e expectativas de serviço antes de conceber a automação.",
-  "cycle.automation-cycle.station.api-platform-architecture.description": "Escolha a plataforma de automação, o runtime, o modelo de integração, os controlos de governação e as restrições operacionais.",
-  "cycle.automation-cycle.station.api-design.description": "Conceba o fluxo de trabalho de automação, gatilhos, pontos de decisão, integrações, tratamento de dados, contratos de interface e caminhos de exceção.",
+  "cycle.automation-cycle.station.api-platform-architecture.description": "Escolher a plataforma de automacao, o runtime, a abordagem de integracao, os controlos de governacao e as restricoes operacionais.",
+  "cycle.automation-cycle.station.api-design.description": "Conceber o fluxo de trabalho de automacao, os gatilhos, os pontos de decisao, as integracoes, o tratamento de dados, os contratos de interface relevantes e os caminhos de excecao.",
   "cycle.automation-cycle.station.api-delivery.description": "Construa, teste, disponibilize, documente e opere a automação com propriedade, controlos e caminhos de reversão claros.",
   "cycle.automation-cycle.station.api-audit.description": "Reveja a prontidão, a qualidade, o risco, a conformidade, a supervisão humana, as evidências e os critérios de disponibilização da automação.",
   "cycle.automation-cycle.station.api-publishing.description": "Capacite utilizadores e operadores com descoberta, integração, instruções operacionais, caminhos de suporte e comunicação de alterações.",
diff --git a/src/data/method/resources.json b/src/data/method/resources.json
index b85c152..1c4da32 100644
--- a/src/data/method/resources.json
+++ b/src/data/method/resources.json
@@ -1127,6 +1127,256 @@
         ]
       },
       "category": "canvas"
+    },
+    {
+      "id": "integration-style-selection-guide",
+      "title": "resource.integration-style-selection-guide.title",
+      "slug": "resources/integration-style-selection-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 180,
+      "description": "resource.integration-style-selection-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.integration-style-selection-guide.outcomes",
+        "resource.integration-style-selection-guide.outcomes.1",
+        "resource.integration-style-selection-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.integration-style-selection-guide.steps",
+          "resource.integration-style-selection-guide.steps.1",
+          "resource.integration-style-selection-guide.steps.2",
+          "resource.integration-style-selection-guide.steps.3"
+        ],
+        "tips": [
+          "resource.integration-style-selection-guide.tips",
+          "resource.integration-style-selection-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "process-workflow-design-guide",
+      "title": "resource.process-workflow-design-guide.title",
+      "slug": "resources/process-workflow-design-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 181,
+      "description": "resource.process-workflow-design-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.process-workflow-design-guide.outcomes",
+        "resource.process-workflow-design-guide.outcomes.1",
+        "resource.process-workflow-design-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.process-workflow-design-guide.steps",
+          "resource.process-workflow-design-guide.steps.1",
+          "resource.process-workflow-design-guide.steps.2",
+          "resource.process-workflow-design-guide.steps.3"
+        ],
+        "tips": [
+          "resource.process-workflow-design-guide.tips",
+          "resource.process-workflow-design-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "decision-business-rules-guide",
+      "title": "resource.decision-business-rules-guide.title",
+      "slug": "resources/decision-business-rules-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 182,
+      "description": "resource.decision-business-rules-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.decision-business-rules-guide.outcomes",
+        "resource.decision-business-rules-guide.outcomes.1",
+        "resource.decision-business-rules-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.decision-business-rules-guide.steps",
+          "resource.decision-business-rules-guide.steps.1",
+          "resource.decision-business-rules-guide.steps.2"
+        ],
+        "tips": [
+          "resource.decision-business-rules-guide.tips",
+          "resource.decision-business-rules-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "automation-trigger-handoff-exception-guide",
+      "title": "resource.automation-trigger-handoff-exception-guide.title",
+      "slug": "resources/automation-trigger-handoff-exception-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 183,
+      "description": "resource.automation-trigger-handoff-exception-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-trigger-handoff-exception-guide.outcomes",
+        "resource.automation-trigger-handoff-exception-guide.outcomes.1",
+        "resource.automation-trigger-handoff-exception-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-trigger-handoff-exception-guide.steps",
+          "resource.automation-trigger-handoff-exception-guide.steps.1",
+          "resource.automation-trigger-handoff-exception-guide.steps.2",
+          "resource.automation-trigger-handoff-exception-guide.steps.3"
+        ],
+        "tips": [
+          "resource.automation-trigger-handoff-exception-guide.tips",
+          "resource.automation-trigger-handoff-exception-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "automation-testing-guide",
+      "title": "resource.automation-testing-guide.title",
+      "slug": "resources/automation-testing-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 184,
+      "description": "resource.automation-testing-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-testing-guide.outcomes",
+        "resource.automation-testing-guide.outcomes.1",
+        "resource.automation-testing-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-testing-guide.steps",
+          "resource.automation-testing-guide.steps.1",
+          "resource.automation-testing-guide.steps.2",
+          "resource.automation-testing-guide.steps.3"
+        ],
+        "tips": [
+          "resource.automation-testing-guide.tips",
+          "resource.automation-testing-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "automation-operational-ownership-guide",
+      "title": "resource.automation-operational-ownership-guide.title",
+      "slug": "resources/automation-operational-ownership-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 185,
+      "description": "resource.automation-operational-ownership-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-operational-ownership-guide.outcomes",
+        "resource.automation-operational-ownership-guide.outcomes.1",
+        "resource.automation-operational-ownership-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-operational-ownership-guide.steps",
+          "resource.automation-operational-ownership-guide.steps.1",
+          "resource.automation-operational-ownership-guide.steps.2"
+        ],
+        "tips": [
+          "resource.automation-operational-ownership-guide.tips",
+          "resource.automation-operational-ownership-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "automation-rollback-supervision-guide",
+      "title": "resource.automation-rollback-supervision-guide.title",
+      "slug": "resources/automation-rollback-supervision-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 186,
+      "description": "resource.automation-rollback-supervision-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-rollback-supervision-guide.outcomes",
+        "resource.automation-rollback-supervision-guide.outcomes.1",
+        "resource.automation-rollback-supervision-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-rollback-supervision-guide.steps",
+          "resource.automation-rollback-supervision-guide.steps.1",
+          "resource.automation-rollback-supervision-guide.steps.2",
+          "resource.automation-rollback-supervision-guide.steps.3"
+        ],
+        "tips": [
+          "resource.automation-rollback-supervision-guide.tips",
+          "resource.automation-rollback-supervision-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
+    },
+    {
+      "id": "automation-readiness-checklist",
+      "title": "resource.automation-readiness-checklist.title",
+      "slug": "resources/automation-readiness-checklist",
+      "icon": "check-box-outline",
+      "draft": "true",
+      "order": 187,
+      "description": "resource.automation-readiness-checklist.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-readiness-checklist.outcomes",
+        "resource.automation-readiness-checklist.outcomes.1",
+        "resource.automation-readiness-checklist.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-readiness-checklist.steps",
+          "resource.automation-readiness-checklist.steps.1",
+          "resource.automation-readiness-checklist.steps.2",
+          "resource.automation-readiness-checklist.steps.3"
+        ],
+        "tips": [
+          "resource.automation-readiness-checklist.tips",
+          "resource.automation-readiness-checklist.tips.1"
+        ]
+      },
+      "category": "checklist"
+    },
+    {
+      "id": "automation-rollout-enablement-guide",
+      "title": "resource.automation-rollout-enablement-guide.title",
+      "slug": "resources/automation-rollout-enablement-guide",
+      "icon": "edit-document-outline",
+      "draft": "true",
+      "order": 188,
+      "description": "resource.automation-rollout-enablement-guide.description",
+      "image": "",
+      "outcomes": [
+        "resource.automation-rollout-enablement-guide.outcomes",
+        "resource.automation-rollout-enablement-guide.outcomes.1",
+        "resource.automation-rollout-enablement-guide.outcomes.2"
+      ],
+      "how_it_works": {
+        "steps": [
+          "resource.automation-rollout-enablement-guide.steps",
+          "resource.automation-rollout-enablement-guide.steps.1",
+          "resource.automation-rollout-enablement-guide.steps.2",
+          "resource.automation-rollout-enablement-guide.steps.3"
+        ],
+        "tips": [
+          "resource.automation-rollout-enablement-guide.tips",
+          "resource.automation-rollout-enablement-guide.tips.1"
+        ]
+      },
+      "category": "guideline"
     }
   ]
 }

From 762476e2de61a75a8cd65e4b979459e241c01cd0 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Sun, 12 Jul 2026 02:04:50 +0300
Subject: [PATCH 08/12] improved consistency of cycle specific resources and
 localization

---
 src/data/canvas/localizedData.json          | 128 ++--
 src/data/method/de/labels.criteria.json     |  20 +-
 src/data/method/de/labels.resources.json    | 167 ++++-
 src/data/method/de/labels.stakeholders.json |  34 +-
 src/data/method/en/labels.criteria.json     |   6 +-
 src/data/method/en/labels.resources.json    | 386 ++++++------
 src/data/method/en/labels.stakeholders.json |  44 +-
 src/data/method/fi/labels.criteria.json     |  10 +-
 src/data/method/fi/labels.resources.json    | 457 ++++++++------
 src/data/method/fi/labels.stakeholders.json |  38 +-
 src/data/method/fr/labels.criteria.json     |  12 +-
 src/data/method/fr/labels.resources.json    | 653 +++++++++++---------
 src/data/method/fr/labels.stakeholders.json |  38 +-
 src/data/method/pt/labels.criteria.json     |  44 +-
 src/data/method/pt/labels.resources.json    | 253 +++++---
 src/data/method/pt/labels.stakeholders.json |  84 +--
 src/data/method/resources.json              |  20 +-
 17 files changed, 1408 insertions(+), 986 deletions(-)

diff --git a/src/data/canvas/localizedData.json b/src/data/canvas/localizedData.json
index 9e12603..b63c1cb 100644
--- a/src/data/canvas/localizedData.json
+++ b/src/data/canvas/localizedData.json
@@ -69,7 +69,7 @@
     "businessImpactCanvas": {
       "title": "Business Impact Canvas",
       "purpose": "Welche geschäftlichen Auswirkungen kann ein Ausfall oder Fehlverhalten der Capability oder Schnittstelle haben?",
-      "howToUse": "Bewerten Sie mögliche Auswirkungen auf Verfügbarkeit, Sicherheit und Daten, bevor der Umsetzungsstil endgültig festgelegt wird.",
+      "howToUse": "Bewerten Sie mögliche Auswirkungen auf Verfügbarkeit, Sicherheit und Daten, bevor der Implementierungsstil endgültig festgelegt wird.",
       "sections": {
         "availabilityRisks": {
           "section": "Risiken der Verfügbarkeit",
@@ -387,7 +387,7 @@
     },
     "capabilityValuePropositionCanvas": {
       "title": "Capability Value Proposition Canvas",
-      "purpose": "Welche wiederverwendbare Capability würde Nutzern Wert liefern, ohne bereits zu entscheiden, ob sie als API, Event, Datei, Stream, Datenprodukt oder ein anderer Integrationsstil bereitgestellt werden soll?",
+      "purpose": "Welche wiederverwendbare Capability würde Nutzern Wert liefern, ohne bereits zu entscheiden, ob sie als API, Event, Datei, Stream, Datenprodukt oder ein anderer Implementierungsstil bereitgestellt werden soll?",
       "howToUse": "Starten Sie mit Nutzeraufgaben und Ergebnissen. Erfassen Sie nutzenstiftende und Pain-Point-reduzierende Capability-Funktionen und beschreiben Sie mögliche wiederverwendbare Capabilities, ohne die Technologie zu früh festzulegen.",
       "sections": {
         "consumerTasks": {
@@ -724,7 +724,7 @@
     "interactionCanvas": {
       "title": "Interaction Canvas",
       "purpose": "What kinds of interactions should this capability support before choosing a protocol-specific design?",
-      "howToUse": "Identify which interaction styles are actually needed for this capability, and which are out of scope. Use this canvas to clarify intent before mapping the result to REST, events, GraphQL, or another selected pattern.",
+      "howToUse": "Identify which interaction styles are actually needed for this capability, and which are out of scope. Use this canvas to clarify intent before mapping the result to REST, events, GraphQL, or another selected implementation style.",
       "sections": {
         "crudInteractions": {
           "section": "CRUD Interactions",
@@ -887,7 +887,7 @@
     },
     "capabilityValuePropositionCanvas": {
       "title": "Capability Value Proposition Canvas",
-      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another integration style?",
+      "purpose": "Which reusable capability would create value for consumers without deciding yet whether it should be delivered as an API, event, file, stream, data product, or another implementation style?",
       "howToUse": "Start from consumer tasks and outcomes. Capture gain-enabling and pain-relieving capability features, then describe candidate reusable capabilities without naming the technology too early.",
       "sections": {
         "consumerTasks": {
@@ -954,7 +954,7 @@
     "consumerExperienceRequirementsCanvas": {
       "title": "Consumer Experience Requirements Canvas",
       "purpose": "What experience and non-functional requirements do consumers need before deciding the best integration architecture?",
-      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another pattern.",
+      "howToUse": "Use this as a technology-agnostic requirements table. Capture consumer expectations and constraints, then use the architecture implications to choose APIs, events, files, streams, data products, or another implementation style.",
       "sections": {
         "consumerGoals": {
           "section": "Consumer goals",
@@ -1887,7 +1887,7 @@
     },
     "capabilityValuePropositionCanvas": {
       "title": "Capability Value Proposition Canvas",
-      "purpose": "Quelle capacité réutilisable créerait de la valeur pour les utilisateurs sans décider encore si elle doit être mise à disposition sous forme d’API, d’événement, de fichier, de flux, de produit de données ou d’un autre style d’intégration ?",
+      "purpose": "Quelle capacité réutilisable créerait de la valeur pour les utilisateurs sans décider encore si elle doit être mise à disposition sous forme d’API, d’événement, de fichier, de flux, de produit de données ou d’un autre mode de mise en œuvre ?",
       "howToUse": "Partir des tâches et résultats attendus des utilisateurs. Capturer les fonctionnalités de capacité qui créent des gains et réduisent les irritants, puis décrire les capacités réutilisables candidates sans nommer la technologie trop tôt.",
       "sections": {
         "consumerTasks": {
@@ -1954,7 +1954,7 @@
     "consumerExperienceRequirementsCanvas": {
       "title": "Consumer Experience Requirements Canvas",
       "purpose": "Quelles exigences d’expérience et non fonctionnelles les utilisateurs doivent-ils préciser avant de décider de la meilleure architecture d’intégration ?",
-      "howToUse": "Utiliser ce canvas comme tableau d’exigences indépendant de la technologie. Capturer les attentes et contraintes des utilisateurs, puis utiliser les implications d’architecture pour choisir API, événements, fichiers, flux, produits de données ou un autre pattern.",
+      "howToUse": "Utiliser ce canvas comme tableau d’exigences indépendant de la technologie. Capturer les attentes et contraintes des utilisateurs, puis utiliser les implications d’architecture pour choisir API, événements, fichiers, flux, produits de données ou un autre mode de mise en œuvre.",
       "sections": {
         "consumerGoals": {
           "section": "Objectifs des utilisateurs",
@@ -2019,18 +2019,18 @@
         },
         "apiValueProposition": {
           "section": "Proposta de valor da API",
-          "description": "Comece com uma nota adesiva que nomeie a API ou a família de APIs e, em seguida, anote o valor que a API oferece aos seus consumidores."
+          "description": "Comece com uma nota adesiva que nomeie a API ou a família de APIs e, em seguida, anote o valor que a API oferece aos seus utilizadores."
         },
         "developerRelations": {
           "section": "Relações com programadores",
-          "description": "Como o fornecedor da API alcança e oferece apoio aos consumidores da API?"
+          "description": "Como o fornecedor da API alcança e oferece apoio aos utilizadores da API?"
         },
         "channels": {
           "section": "Canais",
-          "description": "Através de quais mecanismos os consumidores da API interagem com a API?"
+          "description": "Através de quais mecanismos os utilizadores da API interagem com a API?"
         },
         "apiConsumerSegments": {
-          "section": "Segmentos de consumidores da API",
+          "section": "Segmentos de utilizadores da API",
           "description": "Quem é o público-alvo da API?"
         },
         "costs": {
@@ -2045,8 +2045,8 @@
     },
     "apiValuePropositionCanvas": {
       "title": "Canvas da Proposta de Valor da API",
-      "purpose": "Como a jornada do cliente se relaciona com as APIs? Quais dificuldades e benefícios dos utilizadores finais e consumidores de API precisam ser abordados?",
-      "howToUse": "Descreva a perspetiva dos utilizadores finais, começando pelas suas tarefas, depois as suas dificuldades e benefícios e os dos consumidores de API e, finalmente, os produtos e funcionalidades da API.",
+      "purpose": "Como a percurso do cliente se relaciona com as APIs? Quais dificuldades e benefícios dos utilizadores finais e utilizadores de API precisam /de ser abordados?",
+      "howToUse": "Descreva a perspetiva dos utilizadores finais, começando pelas suas tarefas, depois as suas dificuldades e benefícios e os dos utilizadores de API e, finalmente, os produtos e funcionalidades da API.",
       "sections": {
         "tasks": {
           "section": "Tarefas",
@@ -2054,11 +2054,11 @@
         },
         "gainEnablingFeatures": {
           "section": "Recursos que possibilitam ganhos",
-          "description": "Que funcionalidades permitem que os utilizadores finais e consumidores de API alcancem ganhos?"
+          "description": "Que funcionalidades permitem que os utilizadores finais e utilizadores de API alcancem ganhos?"
         },
         "painRelievingFeatures": {
           "section": "Recursos que aliviam dificuldades",
-          "description": "Que funcionalidades ajudam os utilizadores finais e os consumidores da API a superar dificuldades?"
+          "description": "Que funcionalidades ajudam os utilizadores finais e os utilizadores da API a superar dificuldades?"
         },
         "apiProducts": {
           "section": "Produtos API",
@@ -2103,8 +2103,8 @@
       "howToUse": "Analise os requisitos de capacidade atuais e futuros para cada API.",
       "sections": {
         "currentBusinessVolumes": {
-          "section": "Volumes comerciais atuais",
-          "description": "Quais são os volumes comerciais e as taxas de transação atuais?"
+          "section": "Volumes de negócio atuais",
+          "description": "Quais são os volumes de negócio e as taxas de transação atuais?"
         },
         "futureConsumptionTrends": {
           "section": "Tendências de consumo futuro",
@@ -2130,8 +2130,8 @@
     },
     "customerJourneyCanvas": {
       "title": "Canvas do Percurso do Cliente",
-      "purpose": "Qual é a jornada do cliente ou parceiro que a API pretende apoiar?",
-      "howToUse": "Descreva uma jornada real de um cliente ou utilizador — não o uso da API — para revelar pontos fracos, objetivos e contexto. Esta informação ajuda a definir que tipo de apoio de API será realmente necessário mais tarde.",
+      "purpose": "Qual é a percurso do cliente ou parceiro que a API pretende apoiar?",
+      "howToUse": "Descreva uma percurso real de um cliente ou utilizador — não o uso da API — para revelar pontos fracos, objetivos e contexto. Esta informação ajuda a definir que tipo de apoio de API será realmente necessário mais tarde.",
       "sections": {
         "customerDiscoversNeed": {
           "section": "O cliente descobre a necessidade",
@@ -2139,15 +2139,15 @@
         },
         "persona": {
           "section": "Persona",
-          "description": "Quem é o cliente típico que passa por esta jornada?"
+          "description": "Quem é o cliente típico que passa por esta percurso?"
         },
         "pains": {
           "section": "Dores",
           "description": "Quais são os pontos fracos ou desafios do cliente?"
         },
         "journeySteps": {
-          "section": "Etapas da jornada",
-          "description": "Quais são as etapas que o cliente percorre em sua jornada?"
+          "section": "Etapas da percurso",
+          "description": "Quais são as etapas que o cliente percorre em sua percurso?"
         },
         "customerNeedIsResolved": {
           "section": "Necessidade do cliente resolvida",
@@ -2173,16 +2173,16 @@
       "howToUse": "Defina o modelo de domínio para cada API, incluindo entidades, atributos e relações.",
       "sections": {
         "selectedCustomerJourneySteps": {
-          "section": "Etapas selecionadas da jornada do cliente",
-          "description": "Quais etapas da jornada do cliente são relevantes para este domínio?"
+          "section": "Etapas selecionadas da percurso do cliente",
+          "description": "Quais etapas da percurso do cliente são relevantes para este domínio?"
         },
         "coreEntitiesAndBusinessMeaning": {
-          "section": "Entidades principais e significado comercial",
-          "description": "Quais são as entidades principais e seu significado comercial?"
+          "section": "Entidades principais e significado de negócio",
+          "description": "Quais são as entidades principais e seu significado de negócio?"
         },
         "attributesAndBusinessImportance": {
-          "section": "Atributos e importância comercial",
-          "description": "Quais são os principais atributos de cada entidade e sua importância comercial?"
+          "section": "Atributos e importância de negócio",
+          "description": "Quais são os principais atributos de cada entidade e sua importância de negócio?"
         },
         "relationshipsBetweenEntities": {
           "section": "Relações entre entidades",
@@ -2213,7 +2213,7 @@
         },
         "processingLogic": {
           "section": "Processamento/Lógica",
-          "description": "Descreva a lógica de processamento de back-end, incluindo validações, transformações ou decisões de roteamento."
+          "description": "Descreva a lógica de processamento de back-end, incluindo validações, transformações ou decisões de encaminhamento."
         },
         "outputEventResult": {
           "section": "Saída/Resultado do evento",
@@ -2228,7 +2228,7 @@
       "sections": {
         "crudInteractions": {
           "section": "Interações CRUD",
-          "description": "As interações do tipo CRUD (Criar, Ler, Atualizar, Excluir) são necessárias aqui?"
+          "description": "As interações do tipo CRUD (Criar, Ler, Atualizar, Eliminar) são necessárias aqui?"
         },
         "crudInputOutputModels": {
           "section": "Modelos de entrada e saída CRUD",
@@ -2264,7 +2264,7 @@
         },
         "eventDrivenInteractions": {
           "section": "Interações orientadas por eventos",
-          "description": "Quais eventos precisam ser publicados ou consumidos, se houver?"
+          "description": "Quais eventos precisam /de ser publicados ou consumidos, se houver?"
         },
         "eventDrivenInputOutputModels": {
           "section": "Modelos de entrada e saída orientados por eventos",
@@ -2279,7 +2279,7 @@
     "locationsCanvas": {
       "title": "Canvas de Localizações",
       "purpose": "Que fronteiras geopolíticas, regulamentares, de rede e de confiança afetam esta API?",
-      "howToUse": "Identifique onde os consumidores, fornecedores e sistemas dependentes da API operam em redes internas, redes de parceiros, internet pública e regiões regulamentadas. Descreva as implicações de latência, confiança, conformidade e conectividade entre eles.",
+      "howToUse": "Identifique onde os utilizadores, fornecedores e sistemas dependentes da API operam em redes internas, redes de parceiros, internet pública e regiões regulamentadas. Descreva as implicações de latência, confiança, conformidade e conectividade entre eles.",
       "sections": {
         "locationGroups": {
           "section": "Grupos de Localização / Confiança",
@@ -2291,7 +2291,7 @@
         },
         "locations": {
           "section": "Locais / Zonas Relevantes",
-          "description": "QQuais são os locais, zonas ou ambientes relevantes dentro de cada grupo?"
+          "description": "Quais são os locais, zonas ou ambientes relevantes dentro de cada grupo?"
         },
         "locationCharacteristics": {
           "section": "Características de localização / zona",
@@ -2317,7 +2317,7 @@
     },
     "restCanvas": {
       "title": "Canvas REST",
-      "purpose": "Como a API pode ser concebida usando os princípios RESTful?",
+      "purpose": "Como a API pode ser concebida utilizando os princípios RESTful?",
       "howToUse": "Defina os recursos, verbos e exemplos de pedidos e respostas da API.",
       "sections": {
         "apiResources": {
@@ -2340,7 +2340,7 @@
     },
     "graphqlCanvas": {
       "title": "Canvas GraphQL",
-      "purpose": "Como a API pode ser concebida usando os princípios do GraphQL?",
+      "purpose": "Como a API pode ser concebida utilizando os princípios do GraphQL?",
       "howToUse": "Defina os tipos-chave, consultas, mutações e restrições para a sua API GraphQL.",
       "sections": {
         "apiName": {
@@ -2348,8 +2348,8 @@
           "description": "Qual é o nome da API GraphQL ou do endpoint?"
         },
         "consumerGoals": {
-          "section": "Objetivos do consumidor",
-          "description": "Que problemas os consumidores da API estão a tentar resolver? De que dados precisam?"
+          "section": "Objetivos do utilizador",
+          "description": "Que problemas os utilizadores da API estão a tentar resolver? De que dados precisam?"
         },
         "keyTypes": {
           "section": "Tipos de chave",
@@ -2365,18 +2365,18 @@
         },
         "mutations": {
           "section": "Mutações",
-          "description": "Quais operações modificarão os dados (por exemplo, criar, atualizar, excluir)?"
+          "description": "Quais operações modificarão os dados (por exemplo, criar, atualizar, eliminar)?"
         },
         "subscriptions": {
           "section": "Assinaturas",
-          "description": "Existem atualizações em tempo real ou eventos que os consumidores podem assinar?"
+          "description": "Existem atualizações em tempo real ou eventos que os utilizadores podem assinar?"
         },
         "authorizationRules": {
           "section": "Regras de autorização",
-          "description": "Quem pode acessar quais campos ou tipos?"
+          "description": "Quem pode aceder quais campos ou tipos?"
         },
         "consumerConstraints": {
-          "section": "Restrições do consumidor",
+          "section": "Restrições do utilizador",
           "description": "Existem restrições de paginação, filtragem ou limitação de pedidos?"
         },
         "openQuestions": {
@@ -2387,31 +2387,31 @@
     },
     "capabilityValuePropositionCanvas": {
       "title": "Canvas da Proposta de Valor da Capacidade",
-      "purpose": "Que capacidade reutilizável criaria valor para os consumidores sem decidir ainda se deve ser disponibilizada como API, evento, ficheiro, stream, produto de dados ou outro estilo de integração?",
-      "howToUse": "Comece pelas tarefas e resultados dos consumidores. Capte funcionalidades da capacidade que permitem ganhos e aliviam dores; depois descreva capacidades reutilizáveis candidatas sem nomear a tecnologia demasiado cedo.",
+      "purpose": "Que capacidade reutilizável criaria valor para os utilizadores sem decidir ainda se deve ser disponibilizada como API, evento, ficheiro, stream, produto de dados ou outro estilo de implementação?",
+      "howToUse": "Comece pelas tarefas e resultados dos utilizadores. Capte funcionalidades da capacidade que permitem ganhos e aliviam dores; depois descreva capacidades reutilizáveis candidatas sem nomear a tecnologia demasiado cedo.",
       "sections": {
         "consumerTasks": {
-          "section": "Tarefas e resultados dos consumidores",
-          "description": "O que os consumidores, parceiros, utilizadores, sistemas ou equipas estão a tentar alcançar?"
+          "section": "Tarefas e resultados dos utilizadores",
+          "description": "O que os utilizadores, parceiros, utilizadores, sistemas ou equipas estão a tentar alcançar?"
         },
         "gainEnablingCapabilities": {
           "section": "Funcionalidades da capacidade que permitem ganhos",
-          "description": "Que funcionalidades da capacidade ajudariam os consumidores a alcançar melhores resultados, rapidez, automação, conhecimento, alcance ou conformidade?"
+          "description": "Que funcionalidades da capacidade ajudariam os utilizadores a alcançar melhores resultados, rapidez, automação, conhecimento, alcance ou conformidade?"
         },
         "painRelievingCapabilities": {
           "section": "Funcionalidades da capacidade que aliviam dores",
-          "description": "Que funcionalidades da capacidade removeriam atrito, trabalho manual, erros, atrasos, risco ou incerteza para os consumidores?"
+          "description": "Que funcionalidades da capacidade removeriam atrito, trabalho manual, erros, atrasos, risco ou incerteza para os utilizadores?"
         },
         "reusableCapabilities": {
           "section": "Capacidades reutilizáveis",
-          "description": "Que capacidades de negócio ou de dados reutilizáveis poderiam servir estas tarefas, ganhos e dores em mais do que um consumidor ou caso de utilização?"
+          "description": "Que capacidades de negócio ou de dados reutilizáveis poderiam servir estas tarefas, ganhos e dores em mais do que um utilizador ou caso de utilização?"
         }
       }
     },
     "capabilityBusinessModelCanvas": {
       "title": "Canvas do Modelo de Negócio da Capacidade",
       "purpose": "Quão viável, reutilizável, financiada, atribuída, apoiada e detetável deve ser esta capacidade de integração?",
-      "howToUse": "Resuma a proposta de valor da capacidade, identifique consumidores e canais de envolvimento, e depois mapeie propriedade, atividades, recursos, parceiros, benefícios e custos.",
+      "howToUse": "Resuma a proposta de valor da capacidade, identifique utilizadores e canais de envolvimento, e depois mapeie propriedade, atividades, recursos, parceiros, benefícios e custos.",
       "sections": {
         "keyPartners": {
           "section": "Parceiros-chave",
@@ -2427,19 +2427,19 @@
         },
         "capabilityValueProposition": {
           "section": "Proposta de valor da capacidade",
-          "description": "Que valor esta capacidade reutilizável oferece aos consumidores e à organização ou ecossistema?"
+          "description": "Que valor esta capacidade reutilizável oferece aos utilizadores e à organização ou ecossistema?"
         },
         "consumerEngagement": {
-          "section": "Envolvimento dos consumidores",
-          "description": "Como irão os consumidores descobrir, avaliar, solicitar, integrar-se, obter apoio e dar feedback sobre a capacidade?"
+          "section": "Envolvimento dos utilizadores",
+          "description": "Como irão os utilizadores descobrir, avaliar, solicitar, integrar-se, obter apoio e dar feedback sobre a capacidade?"
         },
         "channels": {
           "section": "Canais",
-          "description": "Através de que catálogos, portais, marketplaces, sites de documentação, caminhos de apoio ou processos de governação os consumidores irão interagir com a capacidade?"
+          "description": "Através de que catálogos, portais, marketplaces, sites de documentação, caminhos de apoio ou processos de governação os utilizadores irão interagir com a capacidade?"
         },
         "capabilityConsumerSegments": {
-          "section": "Segmentos de consumidores da capacidade",
-          "description": "Quem são os consumidores atuais e potenciais da capacidade, incluindo equipas, parceiros, sistemas, produtos ou utilizadores de dados?"
+          "section": "Segmentos de utilizadores da capacidade",
+          "description": "Quem são os utilizadores atuais e potenciais da capacidade, incluindo equipas, parceiros, sistemas, produtos ou utilizadores de dados?"
         },
         "costs": {
           "section": "Custos",
@@ -2452,13 +2452,13 @@
       }
     },
     "consumerExperienceRequirementsCanvas": {
-      "title": "Canvas de Requisitos da Experiência do Consumidor",
-      "purpose": "Que requisitos de experiência e requisitos não funcionais os consumidores precisam de esclarecer antes de decidir a melhor arquitetura de integração?",
-      "howToUse": "Utilize isto como uma tabela de requisitos independente da tecnologia. Capte expectativas e restrições dos consumidores; depois utilize as implicações de arquitetura para escolher APIs, eventos, ficheiros, streams, produtos de dados ou outro padrão.",
+      "title": "Canvas de Requisitos da Experiência do Utilizador",
+      "purpose": "Que requisitos de experiência e requisitos não funcionais os utilizadores precisam /de esclarecer antes de decidir a melhor arquitetura de integração?",
+      "howToUse": "Utilize isto como uma tabela de requisitos independente da tecnologia. Capte expectativas e restrições dos utilizadores; depois utilize as implicações de arquitetura para escolher APIs, eventos, ficheiros, streams, produtos de dados ou outro estilo de implementação.",
       "sections": {
         "consumerGoals": {
-          "section": "Objetivos dos consumidores",
-          "description": "Quais são os objetivos de negócio, de fluxo de trabalho, de decisão, de automação ou de utilização de dados dos consumidores?"
+          "section": "Objetivos dos utilizadores",
+          "description": "Quais são os objetivos de negócio, de fluxo de trabalho, de decisão, de automação ou de utilização de dados dos utilizadores?"
         },
         "availabilityAndTimeliness": {
           "section": "Disponibilidade e atualidade",
@@ -2470,7 +2470,7 @@
         },
         "dataQualityAndConsistency": {
           "section": "Qualidade e consistência dos dados",
-          "description": "Que expectativas de exatidão, completude, consistência, ordenação, deduplicação, reconciliação ou validação têm os consumidores?"
+          "description": "Que expectativas de exatidão, completude, consistência, ordenação, deduplicação, reconciliação ou validação têm os utilizadores?"
         },
         "securityPrivacyAndCompliance": {
           "section": "Segurança, privacidade e conformidade",
@@ -2478,15 +2478,15 @@
         },
         "onboardingAndAccess": {
           "section": "Integração e acesso",
-          "description": "Como devem os consumidores encontrar, solicitar, testar, obter aprovação e começar a utilizar a capacidade?"
+          "description": "Como devem os utilizadores encontrar, solicitar, testar, obter aprovação e começar a utilizar a capacidade?"
         },
         "changeAndVersioning": {
           "section": "Mudança e controlo de versões",
-          "description": "Que tolerância à mudança têm os consumidores e que expectativas de aviso prévio, compatibilidade, migração ou controlo de versões se aplicam?"
+          "description": "Que tolerância à mudança têm os utilizadores e que expectativas de aviso prévio, compatibilidade, migração ou controlo de versões se aplicam?"
         },
         "observabilityAndSupport": {
           "section": "Observabilidade e apoio",
-          "description": "Que monitorização, estado, rastreabilidade, visibilidade da qualidade dos dados, apoio, propriedade e comunicação de incidentes os consumidores precisam?"
+          "description": "Que monitorização, estado, rastreabilidade, visibilidade da qualidade dos dados, apoio, propriedade e comunicação de incidentes os utilizadores precisam?"
         },
         "recoveryAndContinuity": {
           "section": "Recuperação e continuidade",
diff --git a/src/data/method/de/labels.criteria.json b/src/data/method/de/labels.criteria.json
index 5583af0..52311bb 100644
--- a/src/data/method/de/labels.criteria.json
+++ b/src/data/method/de/labels.criteria.json
@@ -1,26 +1,26 @@
 {
   "exit_criteria": "Austrittskriterien",
-  "entry_criteria": "Eintrittskriterien",
+  "entry_criteria": "Einstiegskriterien",
   "criterion.metrics-feedback-available": "Relevante Marktsignale, Feedback oder operative Erkenntnisse liegen vor, um diese Capability-Möglichkeit zu bewerten.",
   "criterion.business-goals-defined": "Die Geschäftsziele sind definiert.",
   "criterion.market-research-done": "Die Marktrecherche identifiziert relevante Capability-Möglichkeiten.",
   "criterion.stakeholder-approval": "Die relevanten Stakeholder stimmen zu, dass diese Capability-Möglichkeit weiter untersucht und priorisiert werden sollte.",
   "criterion.api-opportunity-documented": "Die Capability-Möglichkeit wurde identifiziert und dokumentiert.",
   "criterion.api-reusability": "Die Capability erfüllt einen klaren Geschäftsbedarf und kann von den vorgesehenen Nutzern wiederverwendet werden.",
-  "criterion.hide-backend-discrepancies": "Die gewählte Schnittstelle kapselt die Komplexität und Inkonsistenzen der Backend-Systeme angemessen vor den Nutzern.",
-  "criterion.value-prop-validated": "Das Wertversprechen der Capability wurde mit den relevanten Geschäfts- und Nutzervertretern validiert.",
+  "criterion.hide-backend-discrepancies": "Die gewählte Schnittstelle bietet Nutzern eine angemessene Abstraktion.",
+  "criterion.value-prop-validated": "Das Wertversprechen der Capability wurde mit Geschäfts- und Nutzer-Stakeholdern validiert.",
   "criterion.consumer-segments-identified": "Die Nutzersegmente sind identifiziert.",
   "criterion.api-roadmap-defined": "Eine übergeordnete Roadmap für die Umsetzung ist definiert.",
-  "criterion.architecture-patterns-validated": "Die gewählte Architektur, Plattform und Umsetzungsweise wurden mit den relevanten Architektur-, Sicherheits- und Plattform-Stakeholdern validiert.",
-  "criterion.design-reflects-business-value": "Das Schnittstellendesign und die offengelegten Fähigkeiten lassen sich klar auf Geschäftswert und Nutzerbedürfnisse zurückführen.",
-  "criterion.api-consistency": "Das Schnittstellendesign folgt den vereinbarten Produkt-, Design- und Qualitätsstandards.",
+  "criterion.architecture-patterns-validated": "Die gewählte Architektur, Plattform und der Implementierungsstil wurden mit den relevanten Architektur-, Sicherheits- und Plattform-Stakeholdern validiert.",
+  "criterion.design-reflects-business-value": "Das Schnittstellendesign und die offengelegten Capabilities lassen sich klar auf Geschäftswert und Nutzerbedürfnisse zurückführen.",
+  "criterion.api-consistency": "Das Schnittstellendesign folgt den vereinbarten Designstandards und Konventionen.",
   "criterion.api-contract-tested": "Der Schnittstellenvertrag wurde validiert und gegen funktionale und nicht-funktionale Anforderungen getestet.",
-  "criterion.automation-workflow-validated": "Workflow, Regeln, Integrationen und relevante Schnittstellenvertraege wurden validiert und getestet.",
-  "criterion.api-description-available": "Die Schnittstelle und ihre Fähigkeiten sind ausreichend für Review, Auditierung und Onboarding dokumentiert.",
+  "criterion.automation-workflow-validated": "Workflow, Regeln, Integrationen und relevante Schnittstellenverträge wurden validiert und getestet.",
+  "criterion.api-description-available": "Die Schnittstelle und ihre Capabilities sind ausreichend klar für Review, Auditierung und Onboarding dokumentiert.",
   "criterion.audit-passed": "Die Lösung besteht Qualitäts-, Sicherheits-, Compliance- und Bereitschaftsprüfungen.",
   "criterion.audit-reports-shared": "Audit-Ergebnisse und Maßnahmenentscheidungen wurden mit den relevanten Stakeholdern geteilt.",
-  "criterion.api-ready-for-publishing": "Die Capability ist bereit, über den gewählten Bereitstellungsmechanismus veröffentlicht zu werden.",
+  "criterion.api-ready-for-publishing": "Die Capability ist bereit, über den gewählten Bereitstellungsmechanismus veröffentlicht oder ausgeliefert zu werden.",
   "criterion.api-documentation-ready": "Nutzerorientierte Dokumentation und Onboarding-Materialien sind bereit.",
   "criterion.consumer-support-ready": "Onboarding-, Support- und Kommunikationsprozesse für Nutzer sind bereit.",
-  "criterion.legal-compliance-clear": "Rechtliche, Datenschutz- und Compliance-Anforderungen für die Veröffentlichung sind definiert und verstanden."
+  "criterion.legal-compliance-clear": "Rechtliche, Datenschutz- und Compliance-Anforderungen für Veröffentlichung oder Release sind definiert und verstanden."
 }
diff --git a/src/data/method/de/labels.resources.json b/src/data/method/de/labels.resources.json
index 0877e95..bb18bc3 100644
--- a/src/data/method/de/labels.resources.json
+++ b/src/data/method/de/labels.resources.json
@@ -405,38 +405,141 @@
   "resource.rest-canvas.tips.1": "Sicherstellen, dass Ressourcen-URIs intuitiv und konsistent sind",
   "resource.rest-canvas.tips.2": "Fehlerbehandlung und Antwortcodes dokumentieren",
   "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
-  "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
-  "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
-  "resource.capability-value-proposition-canvas.steps": "List the consumer tasks and outcomes the capability should support.",
-  "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
-  "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
-  "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
-  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
-  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-value-proposition-canvas.description": "Ein technologieunabhängiges Canvas zur Zuordnung von Nutzeraufgaben, Gewinnen, Problemen und möglichen wiederverwendbaren Capabilities, bevor ein Implementierungsstil ausgewählt wird.",
+  "resource.capability-value-proposition-canvas.outcomes": "Klare Wertpositionierung der wiederverwendbaren Capability",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Nutzeraufgaben, Gewinne und Probleme ohne technologische Vorannahme erfasst",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Mögliche wiederverwendbare Capabilities für die Architekturbewertung identifiziert",
+  "resource.capability-value-proposition-canvas.steps": "Listen Sie die Nutzeraufgaben und Ergebnisse auf, die die Capability unterstützen soll.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identifizieren Sie Capability-Merkmale, die Gewinne ermöglichen.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identifizieren Sie Capability-Merkmale, die Probleme reduzieren.",
+  "resource.capability-value-proposition-canvas.steps.3": "Gruppieren Sie die Merkmale zu möglichen wiederverwendbaren Capabilities.",
+  "resource.capability-value-proposition-canvas.tips": "Bleiben Sie technologieunabhängig, bis die Anforderungen auf einen Stil hinweisen.",
+  "resource.capability-value-proposition-canvas.tips.1": "Verwenden Sie dies anstelle des API Value Proposition Canvas, wenn API noch nicht der gewählte Implementierungsstil ist.",
   "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
-  "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
-  "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
-  "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
-  "resource.capability-business-model-canvas.steps": "Summarize the capability value proposition.",
-  "resource.capability-business-model-canvas.steps.1": "Identify consumer segments and engagement channels.",
-  "resource.capability-business-model-canvas.steps.2": "Define key activities, resources, and partners.",
-  "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
-  "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
-  "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
-  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
-  "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
+  "resource.capability-business-model-canvas.description": "Ein Business Model Canvas für wiederverwendbare Integrations-Capabilities, das Wert, Nutzer, Verantwortung, Einbindung, Kosten und Nutzen abdeckt, ohne API-Bereitstellung vorauszusetzen.",
+  "resource.capability-business-model-canvas.outcomes": "Tragfähiges Betriebsmodell für die wiederverwendbare Capability",
+  "resource.capability-business-model-canvas.outcomes.1": "Verantwortung, Nutzer, Kanäle, Partner und Supportbedarf geklärt",
+  "resource.capability-business-model-canvas.outcomes.2": "Kosten und Nutzen vor der Architekturfestlegung sichtbar",
+  "resource.capability-business-model-canvas.steps": "Fassen Sie die Wertpositionierung der Capability zusammen.",
+  "resource.capability-business-model-canvas.steps.1": "Identifizieren Sie Nutzersegmente und Einbindungskanäle.",
+  "resource.capability-business-model-canvas.steps.2": "Definieren Sie Schlüsselaktivitäten, Ressourcen und Partner.",
+  "resource.capability-business-model-canvas.steps.3": "Erfassen Sie Kosten und Nutzen.",
+  "resource.capability-business-model-canvas.steps.4": "Klären Sie Verantwortung, Finanzierung, Support und Lifecycle-Erwartungen.",
+  "resource.capability-business-model-canvas.steps.5": "Validieren Sie das Modell mit Nutzern, Produzenten und Governance-Stakeholdern.",
+  "resource.capability-business-model-canvas.tips": "Verwenden Sie dies anstelle des API Business Model Canvas, wenn der Implementierungsstil noch offen ist.",
+  "resource.capability-business-model-canvas.tips.1": "Fokussieren Sie auf die Tragfähigkeit der wiederverwendbaren Capability, nicht auf eine einmalige Verbindung.",
   "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
-  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
-  "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
-  "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
-  "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit."
+  "resource.consumer-experience-requirements-canvas.description": "Ein Anforderungen-Canvas für nutzerbezogene Experience- und nichtfunktionale Anforderungen, die die spätere Architekturentscheidung steuern sollen.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technologieunabhängige Nutzeranforderungen",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience- und nichtfunktionale Anforderungen vor Designbeginn erfasst",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architekturauswirkungen für die Stilauswahl dokumentiert",
+  "resource.consumer-experience-requirements-canvas.steps": "Erfassen Sie Nutzerziele und Nutzungskontext.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Dokumentieren Sie Erwartungen an Verfügbarkeit, Aktualität, Volumen, Performance, Datenqualität und Konsistenz.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Dokumentieren Sie Erwartungen an Sicherheit, Datenschutz, Onboarding, Änderung, Beobachtbarkeit, Support und Wiederherstellung.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Fassen Sie zusammen, was die Anforderungen für mögliche Architekturstile bedeuten.",
+  "resource.consumer-experience-requirements-canvas.tips": "Verwenden Sie dies als Brücke zwischen Capability-Wert und Architekturentscheidung.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Wählen Sie API, Event, Datei, Stream oder Datenprodukt erst aus, wenn die Anforderungen die Passung erkennen lassen.",
+  "resource.integration-style-selection-guide.title": "Leitfaden zur Auswahl des Implementierungsstils",
+  "resource.integration-style-selection-guide.description": "Orientierung zur Auswahl zwischen API, Event, Datei, Stream, Datenprodukt, direkter Integration oder hybriden Implementierungsstilen auf Grundlage von Anforderungen und Rahmenbedingungen.",
+  "resource.integration-style-selection-guide.outcomes": "Begründeter Implementierungsstil für die Integration",
+  "resource.integration-style-selection-guide.outcomes.1": "Abwägungen zwischen den Optionen für den Implementierungsstil dokumentiert",
+  "resource.integration-style-selection-guide.outcomes.2": "Ausgewählter Stil auf Anforderungen von Nutzern, Plattform, Daten und Betrieb zurückführbar",
+  "resource.integration-style-selection-guide.steps": "Vergleichen Sie tragfähige Implementierungsstile anhand von Latenz, Volumen, Kopplung, Datenverantwortung, Aktualität, Governance und Betriebsfähigkeit.",
+  "resource.integration-style-selection-guide.steps.1": "Identifizieren Sie, wann API, Event, Datei, Stream, Datenprodukt, direkte Integration oder hybride Ansätze zum Anwendungsfall passen.",
+  "resource.integration-style-selection-guide.steps.2": "Dokumentieren Sie Einschränkungen, Risiken und Plattformabhängigkeiten für den ausgewählten Implementierungsstil.",
+  "resource.integration-style-selection-guide.steps.3": "Halten Sie fest, warum verworfene Alternativen nicht ausgewählt wurden.",
+  "resource.integration-style-selection-guide.tips": "Verwenden Sie diese Ressource, nachdem die Anforderungen explizit sind und bevor das detaillierte Vertragsdesign beginnt.",
+  "resource.integration-style-selection-guide.tips.1": "Behalten Sie REST-, Event-, GraphQL-, Datei-, Stream- und Datenprodukt-Ressourcen als optionale nachgelagerte Designressourcen bei.",
+  "resource.process-workflow-design-guide.title": "Leitfaden für Prozess- und Workflow-Design",
+  "resource.process-workflow-design-guide.description": "Orientierung zur Modellierung von Prozessschritten, Rollen, Übergaben, Entscheidungspunkten, Zuständen, Eingaben, Ausgaben und Ausnahmen, die einen Automatisierungs-Workflow prägen.",
+  "resource.process-workflow-design-guide.outcomes": "Klares Design des Automatisierungs-Workflows",
+  "resource.process-workflow-design-guide.outcomes.1": "Prozessschritte und Übergaben vor der Implementierung dokumentiert",
+  "resource.process-workflow-design-guide.outcomes.2": "Workflow-Zustände, Eingaben, Ausgaben und Ausnahmewege verstanden",
+  "resource.process-workflow-design-guide.steps": "Modellieren Sie den aktuellen und den Ziel-Prozessfluss einschließlich menschlicher und systemseitiger Verantwortlichkeiten.",
+  "resource.process-workflow-design-guide.steps.1": "Identifizieren Sie Workflow-Auslöser, Zustände, Entscheidungen, Dateneingaben, Ausgaben und Abschlusskriterien.",
+  "resource.process-workflow-design-guide.steps.2": "Dokumentieren Sie Übergaben zwischen Nutzern, Systemen, Betrieb und Supportrollen.",
+  "resource.process-workflow-design-guide.steps.3": "Bestätigen Sie, welche Schritte automatisiert werden sollen und welche menschliches Urteilsvermögen erfordern.",
+  "resource.process-workflow-design-guide.tips": "Halten Sie Prozessdesign vom API- oder Integrationsvertragsdesign getrennt, bis der Workflow klar ist.",
+  "resource.process-workflow-design-guide.tips.1": "Verwenden Sie diese Ressource als primäre Designressource für Automatisierungs-Workflows.",
+  "resource.decision-business-rules-guide.title": "Leitfaden für Entscheidungen und Geschäftsregeln",
+  "resource.decision-business-rules-guide.description": "Orientierung zur Erfassung von Regeln, Schwellenwerten, Entscheidungen, Genehmigungen, Eignungsprüfungen und Regelverantwortung für das Automatisierungsdesign.",
+  "resource.decision-business-rules-guide.outcomes": "Explizite Entscheidungen und Geschäftsregeln",
+  "resource.decision-business-rules-guide.outcomes.1": "Regeln und Schwellenwerte mit Verantwortlichen dokumentiert",
+  "resource.decision-business-rules-guide.outcomes.2": "Automatisierungsentscheidungen auf Richtlinien, Prozesse oder Geschäftsabsicht zurückführbar",
+  "resource.decision-business-rules-guide.steps": "Listen Sie Entscheidungen auf, die die Automatisierung treffen oder unterstützen muss.",
+  "resource.decision-business-rules-guide.steps.1": "Dokumentieren Sie Regelbedingungen, Schwellenwerte, Ausnahmen, Genehmigungen und Eskalationspunkte.",
+  "resource.decision-business-rules-guide.steps.2": "Identifizieren Sie Regelverantwortliche und Änderungsgovernance für jeden Entscheidungsbereich.",
+  "resource.decision-business-rules-guide.tips": "Trennen Sie stabile Geschäftsregeln von konfigurierbaren betrieblichen Parametern.",
+  "resource.decision-business-rules-guide.tips.1": "Nutzen Sie Beispiele und Grenzfälle, um die Regelauslegung zu validieren.",
+  "resource.automation-trigger-handoff-exception-guide.title": "Leitfaden für Automatisierungsauslöser, Übergaben und Ausnahmen",
+  "resource.automation-trigger-handoff-exception-guide.description": "Orientierung zur Definition von Automatisierungsauslösern, menschlichen Übergaben, Ausnahmebehandlung, Wiederholungen, Ausgleichsmaßnahmen und Support-Eskalationswegen.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes": "Definierte Automatisierungsauslöser und Ausnahmewege",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.1": "Menschliche Übergaben und Support-Eskalationen sind explizit",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.2": "Ausnahmen, Wiederholungen und Ausgleichsmaßnahmen sind vor der Bereitstellung entworfen",
+  "resource.automation-trigger-handoff-exception-guide.steps": "Definieren Sie Ereignisse, Zeitpläne, Nutzeraktionen oder Systemzustände, die die Automatisierung auslösen.",
+  "resource.automation-trigger-handoff-exception-guide.steps.1": "Modellieren Sie Übergaben von der Automatisierung an Nutzer, Betreiber oder Supportteams.",
+  "resource.automation-trigger-handoff-exception-guide.steps.2": "Dokumentieren Sie Ausnahmen, Wiederholungsregeln, Timeout-Verhalten und Rückfallwege.",
+  "resource.automation-trigger-handoff-exception-guide.steps.3": "Definieren Sie Warnungen und Eskalationsschwellen für fehlgeschlagene oder uneindeutige Automatisierungsergebnisse.",
+  "resource.automation-trigger-handoff-exception-guide.tips": "Gestalten Sie Ausnahmewege als vollwertiges Workflow-Verhalten, nicht als nachträgliche Ergänzung.",
+  "resource.automation-trigger-handoff-exception-guide.tips.1": "Beziehen Sie Geschäfts- und Betriebsrollen ein, wenn Übergaben validiert werden.",
+  "resource.automation-testing-guide.title": "Leitfaden für Automatisierungstests",
+  "resource.automation-testing-guide.description": "Orientierung zum Testen automatisierter Workflows, Entscheidungen, Integrationen, Ausnahmen, Rollback-Verhalten, Überwachung und Nutzerauswirkungen vor der Veröffentlichung.",
+  "resource.automation-testing-guide.outcomes": "Validiertes Automatisierungsverhalten",
+  "resource.automation-testing-guide.outcomes.1": "Workflow-, Regel-, Ausnahme- und Integrationstests definiert",
+  "resource.automation-testing-guide.outcomes.2": "Veröffentlichungssicherheit für automatisierte und menschlich unterstützte Pfade",
+  "resource.automation-testing-guide.steps": "Erstellen Sie Tests für Standardabläufe, Grenzfälle, Ausnahmen, Wiederholungen und Übergaben.",
+  "resource.automation-testing-guide.steps.1": "Validieren Sie Geschäftsregeln und Entscheidungsergebnisse mit repräsentativen Daten.",
+  "resource.automation-testing-guide.steps.2": "Testen Sie Rollback, Wiederherstellung, Beobachtbarkeit und manuelle Eingriffspfade.",
+  "resource.automation-testing-guide.steps.3": "Beziehen Sie Nutzer und Betreiber in Abnahmetests ein, wenn die Automatisierung Arbeitsweisen verändert.",
+  "resource.automation-testing-guide.tips": "Verwenden Sie produktionsnahe Szenarien und Datenstrukturen, ohne sensible Daten offenzulegen.",
+  "resource.automation-testing-guide.tips.1": "Halten Sie Testnachweise für die Bereitschaftsprüfung verfügbar.",
+  "resource.automation-operational-ownership-guide.title": "Leitfaden für die betriebliche Verantwortung von Automatisierungen",
+  "resource.automation-operational-ownership-guide.description": "Orientierung zur Definition von Verantwortung, Runbooks, Überwachung, Support, Monitoring, Änderungskontrolle und kontinuierlicher Verbesserung für Automatisierungen.",
+  "resource.automation-operational-ownership-guide.outcomes": "Klares Betriebsmodell für die Automatisierung",
+  "resource.automation-operational-ownership-guide.outcomes.1": "Verantwortlichkeiten für Eigentum, Support und Eskalation zugewiesen",
+  "resource.automation-operational-ownership-guide.outcomes.2": "Monitoring- und Änderungspraktiken für den Live-Betrieb bereit",
+  "resource.automation-operational-ownership-guide.steps": "Definieren Sie fachliche, technische und betriebliche Verantwortliche für die Automatisierung.",
+  "resource.automation-operational-ownership-guide.steps.1": "Dokumentieren Sie Runbooks, Supportwege, Monitoring-Signale, Serviceerwartungen und Eskalationsregeln.",
+  "resource.automation-operational-ownership-guide.steps.2": "Legen Sie Änderungskontrolle und Review-Praktiken für Workflow-, Plattform- und Regeländerungen fest.",
+  "resource.automation-operational-ownership-guide.tips": "Veröffentlichen Sie keine Automatisierung ohne benannte verantwortliche Person für Ausnahmen und laufende Verbesserung.",
+  "resource.automation-operational-ownership-guide.tips.1": "Machen Sie Überwachungsbedarf sichtbar, bevor die Bereitstellungsplanung abgeschlossen ist.",
+  "resource.automation-rollback-supervision-guide.title": "Leitfaden für Rollback und Überwachung von Automatisierungen",
+  "resource.automation-rollback-supervision-guide.description": "Orientierung zur Gestaltung von Rollback-, Pausen-, manuellen Übersteuerungs-, Monitoring-, Überwachungs- und Wiederherstellungspfaden für Automatisierungen.",
+  "resource.automation-rollback-supervision-guide.outcomes": "Kontrollierte Wiederherstellungspfade für Automatisierungen",
+  "resource.automation-rollback-supervision-guide.outcomes.1": "Rollback-, Pausen- und Übersteuerungsverhalten dokumentiert",
+  "resource.automation-rollback-supervision-guide.outcomes.2": "Überwachungsbedarf und Wiederherstellungsverantwortlichkeiten definiert",
+  "resource.automation-rollback-supervision-guide.steps": "Identifizieren Sie Aktionen, die rückgängig gemacht, pausiert oder manuell übersteuert werden können müssen.",
+  "resource.automation-rollback-supervision-guide.steps.1": "Definieren Sie Rollback-, Kompensations- und Wiederherstellungsverfahren für fehlgeschlagene oder falsche Automatisierungsergebnisse.",
+  "resource.automation-rollback-supervision-guide.steps.2": "Dokumentieren Sie Überwachungsschwellen, Warnungen und manuelle Entscheidungspunkte.",
+  "resource.automation-rollback-supervision-guide.steps.3": "Validieren Sie Wiederherstellungsverfahren vor der Veröffentlichung.",
+  "resource.automation-rollback-supervision-guide.tips": "Behandeln Sie Rollback und Überwachung als Teil des Workflow-Designs und des Bereitstellungsplans.",
+  "resource.automation-rollback-supervision-guide.tips.1": "Nutzen Sie betriebliche Vorfälle und Beinahe-Vorfälle, um Überwachungskriterien zu verfeinern.",
+  "resource.automation-readiness-checklist.title": "Checkliste zur Automatisierungsbereitschaft",
+  "resource.automation-readiness-checklist.description": "Eine Checkliste zur Validierung von Automatisierungs-Workflow, Kontrollen, Risiko, Compliance, menschlicher Aufsicht, Testnachweisen, Rollback, Betrieb und Veröffentlichungsbereitschaft.",
+  "resource.automation-readiness-checklist.outcomes": "Dokumentierte Automatisierungsbereitschaft",
+  "resource.automation-readiness-checklist.outcomes.1": "Bekannte Bereitschaftslücken und Gegenmaßnahmen vor der Veröffentlichung",
+  "resource.automation-readiness-checklist.outcomes.2": "Nachweise für Qualität, Risiko, Compliance, Aufsicht und betriebliche Freigabe",
+  "resource.automation-readiness-checklist.steps": "Prüfen Sie Workflow-Design, Geschäftsregeln, Kontrollen, Zugriff, Datenverarbeitung und Ausnahmewege.",
+  "resource.automation-readiness-checklist.steps.1": "Überprüfen Sie Testnachweise, Rollback-Verfahren, Überwachungsmodell und Supportbereitschaft.",
+  "resource.automation-readiness-checklist.steps.2": "Bestätigen Sie Verantwortung, Runbooks, Monitoring, Änderungskontrollen und Veröffentlichungsfreigabe.",
+  "resource.automation-readiness-checklist.steps.3": "Dokumentieren Sie ungelöste Lücken, Entscheidungen und akzeptierte Risiken vor der Veröffentlichung.",
+  "resource.automation-readiness-checklist.tips": "Verwenden Sie die Checkliste vor der Veröffentlichung und erneut nach wesentlichen Workflow- oder Regeländerungen.",
+  "resource.automation-readiness-checklist.tips.1": "Machen Sie menschliche Aufsicht und Ausnahmebehandlung in den Nachweisen explizit.",
+  "resource.automation-rollout-enablement-guide.title": "Leitfaden für Rollout und Enablement von Automatisierungen",
+  "resource.automation-rollout-enablement-guide.description": "Orientierung für die Einführung von Automatisierungen mit Nutzerkommunikation, Onboarding, Betriebsanweisungen, Supportwegen, Change Management und Feedback-Schleifen.",
+  "resource.automation-rollout-enablement-guide.outcomes": "Befähigte Automatisierungsnutzer und Betreiber",
+  "resource.automation-rollout-enablement-guide.outcomes.1": "Rollout-Kommunikation, Onboarding und Supportwege vorbereitet",
+  "resource.automation-rollout-enablement-guide.outcomes.2": "Nutzer und Betreiber verstehen, wie sich die Arbeit nach der Veröffentlichung der Automatisierung verändert",
+  "resource.automation-rollout-enablement-guide.steps": "Definieren Sie Rollout-Zielgruppen, Zeitplan, Kommunikationskanäle und Schulungsbedarf.",
+  "resource.automation-rollout-enablement-guide.steps.1": "Veröffentlichen Sie Betriebsanweisungen, Supportwege, Hinweise zur Ausnahmebehandlung und Eskalationskontakte.",
+  "resource.automation-rollout-enablement-guide.steps.2": "Planen Sie Übergangsunterstützung für Nutzer, Betreiber und Prozessverantwortliche.",
+  "resource.automation-rollout-enablement-guide.steps.3": "Sammeln Sie Feedback nach dem Rollout und überführen Sie Verbesserungen in den Backlog.",
+  "resource.automation-rollout-enablement-guide.tips": "Verwenden Sie für Automatisierungen Rollout-Sprache, statt Enablement wie API-Veröffentlichung zu behandeln.",
+  "resource.automation-rollout-enablement-guide.tips.1": "Beziehen Sie sowohl die vom Prozess betroffenen Nutzer als auch die für die Automatisierung verantwortlichen Betreiber ein.",
+  "resource.api-community-engagement-strategies.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.",
+  "resource.api-development-best-practices.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.",
+  "resource.api-metrics-and-analytics.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.",
+  "resource.api-testing-best-practices.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.",
+  "resource.apiops-CI-CD-for-apis.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist.",
+  "resource.api-audit-checklist.tips.2": "Verwenden Sie diese Ressource, wenn eine API der ausgewählte Implementierungsstil ist."
 }
diff --git a/src/data/method/de/labels.stakeholders.json b/src/data/method/de/labels.stakeholders.json
index 5794f9a..2c42cf8 100644
--- a/src/data/method/de/labels.stakeholders.json
+++ b/src/data/method/de/labels.stakeholders.json
@@ -3,47 +3,47 @@
   "stakeholder.involvement.core": "Kern",
   "stakeholder.involvement.consulted": "Konsultiert",
   "stakeholder.business-owner.title": "Business Owner",
-  "stakeholder.business-owner.description": "Vertritt Geschäftsziele, Finanzierung und erwartete Ergebnisse der Capability-Initiative.",
+  "stakeholder.business-owner.description": "Vertritt Geschäftsziele, Finanzierung und erwartete Ergebnisse der Capability-, API- oder Automatisierungsinitiative.",
   "stakeholder.api-program-owner.title": "API-Programmverantwortlicher",
-  "stakeholder.api-program-owner.description": "Koordiniert API-Portfolio-Praktiken, organisatorische Ausrichtung und langfristige API-Fähigkeitsentwicklung.",
+  "stakeholder.api-program-owner.description": "Koordiniert API-Portfolio-Praktiken, organisatorische Ausrichtung und langfristige Entwicklung von API-Capabilities.",
   "stakeholder.api-product-owner.title": "API Product Owner",
-  "stakeholder.api-product-owner.description": "Führt die API-Möglichkeit, Priorisierung und produktniveaubezogene Entscheidungen über den gesamten Lebenszyklus hinweg durch.",
+  "stakeholder.api-product-owner.description": "Steuert API-Chance, Priorisierung und produktbezogene Entscheidungen über den gesamten Lebenszyklus hinweg.",
   "stakeholder.capability-owner.title": "Capability Owner",
-  "stakeholder.capability-owner.description": "Verantwortet Vision, Ziele, Priorisierung und Weiterentwicklung der Capability über ihren gesamten Lebenszyklus.",
+  "stakeholder.capability-owner.description": "Verantwortet Vision, Wert, Prioritäten, Lebenszyklus und Wiederverwendung der Capability über Nutzer hinweg.",
   "stakeholder.domain-specialist.title": "Domain-Experte",
-  "stakeholder.domain-specialist.description": "Bringt tiefe Kenntnisse des Geschäftsbereichs, Konzepte, Regeln und Einschränkungen mit, die die API widerspiegeln muss.",
+  "stakeholder.domain-specialist.description": "Bringt tiefes Wissen über Geschäftsdomäne, Konzepte, Regeln und Einschränkungen ein, die die Capability oder Schnittstelle widerspiegeln muss.",
   "stakeholder.customer-specialist.title": "Kunden- oder Partnervertreter",
   "stakeholder.customer-specialist.description": "Vertritt die Perspektive von Kunden oder Partnern hinsichtlich Journey, Wert und Zusammenarbeitsmodell.",
   "stakeholder.api-consumer-specialist.title": "Vertreter der API-Nutzer",
   "stakeholder.api-consumer-specialist.description": "Vertritt die Anforderungen von Entwicklern, Integratoren und anderen Nutzern der API.",
   "stakeholder.platform-architect.title": "Plattform-Architekt",
-  "stakeholder.platform-architect.description": "Leitet Entscheidungen über Plattform, Integration, Skalierbarkeit und Architektur, die beeinflussen, wie die API erstellt und betrieben wird.",
+  "stakeholder.platform-architect.description": "Leitet Entscheidungen zu Plattform, Integration, Skalierbarkeit und Architektur, die beeinflussen, wie die Capability oder API erstellt und betrieben wird.",
   "stakeholder.api-architect.title": "API-Architekt",
   "stakeholder.api-architect.description": "Verantwortet API-Architektur, Entwurfsprinzipien und die Qualität der Schnittstellenverträge.",
   "stakeholder.integration-architect.title": "Integrationsarchitekt",
-  "stakeholder.integration-architect.description": "Entwirft Integrationslösungen und Integrationsmuster im Einklang mit der Gesamtarchitektur.",
+  "stakeholder.integration-architect.description": "Entwirft Integrationsansätze und Implementierungsstile, die die Capability oder API mit anderen Systemen verbinden.",
   "stakeholder.platform-owner.title": "Plattformverantwortlicher",
-  "stakeholder.platform-owner.description": "Verantwortet Plattformfähigkeiten, Weiterentwicklung und Betrieb.",
+  "stakeholder.platform-owner.description": "Verantwortet Plattform-Capabilities, Roadmap, Betriebsmodell und Serviceerwartungen.",
   "stakeholder.api-designer.title": "API-Designer",
   "stakeholder.api-designer.description": "Gestaltet Schnittstellenvertrag, Interaktionsmodell, Konsistenz, Benutzerfreundlichkeit und bereitgestellte Capabilities.",
   "stakeholder.api-engineer.title": "API-Entwickler",
-  "stakeholder.api-engineer.description": "Verantwortet Implementierung, Automatisierung, Tests und Release-Prozesse für eine zuverlässige Bereitstellung.",
+  "stakeholder.api-engineer.description": "Verantwortet Implementierung, Automatisierung, Tests und Release-Abläufe, die für die zuverlässige Bereitstellung der Capability, API oder Automatisierung erforderlich sind.",
   "stakeholder.automation-owner.title": "Automatisierungsverantwortlicher",
-  "stakeholder.automation-owner.description": "Verantwortet Ziele, Priorisierung und Geschäftswert der Automatisierung.",
+  "stakeholder.automation-owner.description": "Verantwortet Ziele, Geschäftswert, Prioritäten, Kontrollen und Lebenszyklusergebnisse der Automatisierung.",
   "stakeholder.process-owner.title": "Prozessverantwortlicher",
-  "stakeholder.process-owner.description": "Verantwortet Ziele, Weiterentwicklung und Ergebnisse des Geschäftsprozesses.",
+  "stakeholder.process-owner.description": "Verantwortet den zu automatisierenden Geschäftsprozess, einschließlich Ziele, Regeln, Ergebnisse und Verbesserungsprioritäten.",
   "stakeholder.automation-engineer.title": "Automatisierungsingenieur",
-  "stakeholder.automation-engineer.description": "Implementiert, testet und betreibt Automatisierungslösungen und deren Integrationen.",
+  "stakeholder.automation-engineer.description": "Implementiert, testet, integriert und betreibt Automatisierungslösungen und unterstützende Workflows.",
   "stakeholder.security-specialist.title": "Sicherheitsspezialist",
-  "stakeholder.security-specialist.description": "Stellt sicher, dass Sicherheitsrisiken, Kontrollen und Vertrauensgrenzen im gesamten API-Lifecycle berücksichtigt werden.",
+  "stakeholder.security-specialist.description": "Stellt sicher, dass Sicherheitsrisiken, Kontrollen und Vertrauensgrenzen über den gesamten Lebenszyklus hinweg berücksichtigt werden.",
   "stakeholder.compliance-specialist.title": "Compliance- und Rechtsexperte",
-  "stakeholder.compliance-specialist.description": "Klärt rechtliche, Datenschutz- und Compliance-Anforderungen, die die Capability oder Schnittstelle betreffen.",
+  "stakeholder.compliance-specialist.description": "Klärt rechtliche, Datenschutz-, regulatorische und vertragliche Anforderungen, die Capability, API, Schnittstelle oder Automatisierung betreffen.",
   "stakeholder.governance-specialist.title": "Governance-Verantwortlicher",
   "stakeholder.governance-specialist.description": "Repräsentiert Überprüfung, Auditierung und organisationsweite Governance-Praktiken für API-Qualität und Konformität.",
   "stakeholder.api-devrel-specialist.title": "Verantwortlicher für Dokumentation und DevRel",
   "stakeholder.api-devrel-specialist.description": "Verantwortet Onboarding-Inhalte, Entwicklerkommunikation und Dokumentationsqualität für API-Nutzer.",
   "stakeholder.operations-specialist.title": "Verantwortlicher für Support und Betrieb",
-  "stakeholder.operations-specialist.description": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft.",
+  "stakeholder.operations-specialist.description": "Repräsentiert Runtime-Support, Vorfallbehandlung, Beobachtbarkeit und operative Bereitschaft für Capability, API oder Automatisierung.",
   "stakeholder.partner-specialist.title": "Partner- und Lieferantenmanager",
-  "stakeholder.partner-specialist.description": "Koordiniert Partner- und Lieferantenbeziehungen, die die Capability-Strategie und Umsetzung beeinflussen."
-}
\ No newline at end of file
+  "stakeholder.partner-specialist.description": "Koordiniert externe Partner-, Lieferanten- oder Anbieterbeziehungen, die Capability- oder API-Strategie und Umsetzung beeinflussen."
+}
diff --git a/src/data/method/en/labels.criteria.json b/src/data/method/en/labels.criteria.json
index ab563fa..bb988ba 100644
--- a/src/data/method/en/labels.criteria.json
+++ b/src/data/method/en/labels.criteria.json
@@ -11,7 +11,7 @@
   "criterion.value-prop-validated": "The capability value proposition has been validated with business and consumer stakeholders.",
   "criterion.consumer-segments-identified": "Consumer segments are identified.",
   "criterion.api-roadmap-defined": "A high-level implementation roadmap is defined.",
-  "criterion.architecture-patterns-validated": "The chosen architecture, platform, and delivery approach have been validated with the relevant architecture, security, and platform stakeholders.",
+  "criterion.architecture-patterns-validated": "The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.",
   "criterion.design-reflects-business-value": "The interface design and exposed capabilities trace back to business value and consumer needs.",
   "criterion.api-consistency": "The interface design follows agreed design standards and conventions.",
   "criterion.api-contract-tested": "The interface contract has been validated and tested against functional and non-functional requirements.",
@@ -19,8 +19,8 @@
   "criterion.api-description-available": "The interface and its capabilities are documented clearly enough for review, audit, and onboarding.",
   "criterion.audit-passed": "The solution passes quality, security, compliance, and readiness checks.",
   "criterion.audit-reports-shared": "Audit findings and remediation decisions are shared with the relevant stakeholders.",
-  "criterion.api-ready-for-publishing": "The capability is ready for release through the selected delivery mechanism.",
+  "criterion.api-ready-for-publishing": "The capability is ready to be published or released through the selected delivery mechanism.",
   "criterion.api-documentation-ready": "Consumer-facing documentation and onboarding materials are ready.",
   "criterion.consumer-support-ready": "Consumer onboarding, support, and communication processes are ready.",
-  "criterion.legal-compliance-clear": "Legal, privacy, and compliance requirements for release are defined and understood."
+  "criterion.legal-compliance-clear": "Legal, privacy, and compliance requirements for publishing or release are defined and understood."
 }
diff --git a/src/data/method/en/labels.resources.json b/src/data/method/en/labels.resources.json
index 415d146..ee95e17 100644
--- a/src/data/method/en/labels.resources.json
+++ b/src/data/method/en/labels.resources.json
@@ -1,172 +1,172 @@
 {
   "resource.api-community-engagement-strategies.title": "API Community Engagement Strategies",
   "resource.api-community-engagement-strategies.description": "A playbook for fostering API adoption by cultivating communities through content, support channels, feedback loops, and social engagement strategies.",
-  "resource.api-community-engagement-strategies.outcomes": "Better understanding of API community engagement strategies principles",
-  "resource.api-community-engagement-strategies.outcomes.1": "Standardized approach using API Community Engagement Strategies",
-  "resource.api-community-engagement-strategies.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-community-engagement-strategies.outcomes": "Shared understanding of the purpose and use of API Community Engagement Strategies",
+  "resource.api-community-engagement-strategies.outcomes.1": "A consistent approach to applying API Community Engagement Strategies",
+  "resource.api-community-engagement-strategies.outcomes.2": "Improved application of the related practices",
   "resource.api-community-engagement-strategies.steps": "Develop marketing strategies to promote APIs to target audiences, including social media, blogs, and webinars.",
   "resource.api-community-engagement-strategies.steps.1": "Create promotional materials (e.g., case studies, success stories) that highlight the value and benefits of APIs.",
   "resource.api-community-engagement-strategies.steps.2": "Create educational materials (e.g., tutorials, documentation) that explain API features, benefits, and usage patterns.",
   "resource.api-community-engagement-strategies.steps.3": "Engage with API consumers through feedback loops, support channels, and community forums to understand their needs and improve API adoption.",
   "resource.api-community-engagement-strategies.steps.4": "Analyze API usage metrics and incorporate user feedback into API iterations.",
-  "resource.api-community-engagement-strategies.tips": "Customize the API Community Engagement Strategies for your domain",
-  "resource.api-community-engagement-strategies.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-community-engagement-strategies.tips": "Adapt this resource to your context.",
+  "resource.api-community-engagement-strategies.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-compliance-best-practices.title": "API Compliance Best Practices",
   "resource.api-compliance-best-practices.description": "Ensure APIs meet legal, regulatory, and internal compliance through documentation, controls, and automated validations.",
-  "resource.api-compliance-best-practices.outcomes": "Better understanding of API compliance best practices principles",
-  "resource.api-compliance-best-practices.outcomes.1": "Standardized approach using API Compliance Best Practices",
-  "resource.api-compliance-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-compliance-best-practices.outcomes": "Shared understanding of the purpose and use of API Compliance Best Practices",
+  "resource.api-compliance-best-practices.outcomes.1": "A consistent approach to applying API Compliance Best Practices",
+  "resource.api-compliance-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.api-compliance-best-practices.steps": "Document compliance measures and ensure they are communicated to stakeholders and consumers.",
   "resource.api-compliance-best-practices.steps.1": "Implement measures to ensure APIs comply with these requirements, including data encryption, access controls, and audit trails.",
   "resource.api-compliance-best-practices.steps.2": "Use checklists, linters, and testing tools to verify consistency and conformance with standards.",
-  "resource.api-compliance-best-practices.tips": "Customize the API Compliance Best Practices for your domain",
-  "resource.api-compliance-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-compliance-best-practices.tips": "Adapt this resource to your context.",
+  "resource.api-compliance-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-development-best-practices.title": "API Development Best Practices",
-  "resource.api-development-best-practices.description": "Implementation guidance for turning a validated API contract into a consistent, maintainable API codebase using standard libraries, reusable patterns, and aligned development workflows.",
-  "resource.api-development-best-practices.outcomes": "Better understanding of API development best practices principles",
-  "resource.api-development-best-practices.outcomes.1": "Standardized approach using API Development Best Practices",
-  "resource.api-development-best-practices.outcomes.2": "Improved implementation of related API practices",
-  "resource.api-development-best-practices.steps": "Apply these practices to the validated API contract and implementation plan before coding begins.",
+  "resource.api-development-best-practices.description": "Implementation guidance for turning a validated API interface contract into a consistent, maintainable API codebase using standard libraries, reusable patterns, and aligned development workflows.",
+  "resource.api-development-best-practices.outcomes": "Shared understanding of the purpose and use of API Development Best Practices",
+  "resource.api-development-best-practices.outcomes.1": "A consistent approach to applying API Development Best Practices",
+  "resource.api-development-best-practices.outcomes.2": "Improved application of the related practices",
+  "resource.api-development-best-practices.steps": "Apply these practices to the validated API interface contract and implementation plan before coding begins.",
   "resource.api-development-best-practices.steps.1": "Use established frameworks, libraries, and coding standards to implement the contract consistently and maintainably.",
   "resource.api-development-best-practices.tips": "Use this resource as implementation guidance and a review lens rather than as a required standalone artifact",
-  "resource.api-development-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-development-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-metrics-and-analytics.title": "API Metrics And Analytics",
   "resource.api-metrics-and-analytics.description": "A resource for defining, collecting, and analyzing API performance and usage data to align technical KPIs with business outcomes.",
-  "resource.api-metrics-and-analytics.outcomes": "Better understanding of API metrics and analytics principles",
-  "resource.api-metrics-and-analytics.outcomes.1": "Standardized approach using API Metrics And Analytics",
-  "resource.api-metrics-and-analytics.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-metrics-and-analytics.outcomes": "Shared understanding of the purpose and use of API Metrics And Analytics",
+  "resource.api-metrics-and-analytics.outcomes.1": "A consistent approach to applying API Metrics And Analytics",
+  "resource.api-metrics-and-analytics.outcomes.2": "Improved application of the related practices",
   "resource.api-metrics-and-analytics.steps": "Identify key performance indicators (KPIs) to measure API success against business goals.",
   "resource.api-metrics-and-analytics.steps.1": "Define and monitor performance metrics (e.g., API calls, latency, error rates) and adoption metrics (e.g., NPS).",
   "resource.api-metrics-and-analytics.steps.2": "Monitor API initiatives to ensure adherence to operating guidelines and governance practices",
-  "resource.api-metrics-and-analytics.tips": "Customize the API Metrics And Analytics for your domain",
-  "resource.api-metrics-and-analytics.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-metrics-and-analytics.tips": "Adapt this resource to your context.",
+  "resource.api-metrics-and-analytics.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-onboarding-best-practices.title": "API Onboarding Best Practices",
   "resource.api-onboarding-best-practices.description": "Best practices to streamline API consumer onboarding journeys with step-by-step registration, discovery, and first-call guidance.",
-  "resource.api-onboarding-best-practices.outcomes": "Better understanding of API onboarding best practices principles",
-  "resource.api-onboarding-best-practices.outcomes.1": "Standardized approach using API Onboarding Best Practices",
-  "resource.api-onboarding-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-onboarding-best-practices.outcomes": "Shared understanding of the purpose and use of API Onboarding Best Practices",
+  "resource.api-onboarding-best-practices.outcomes.1": "A consistent approach to applying API Onboarding Best Practices",
+  "resource.api-onboarding-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.api-onboarding-best-practices.steps": "Define the API consumer journey from discovery to troubleshooting, identifying key touchpoints and pain points.",
   "resource.api-onboarding-best-practices.steps.1": "Develop onboarding processes and resources to help API consumers understand how to use APIs effectively.",
   "resource.api-onboarding-best-practices.steps.2": "Document how consumers find and use the API, including onboarding processes and registration.",
-  "resource.api-onboarding-best-practices.tips": "Customize the API Onboarding Best Practices for your domain",
-  "resource.api-onboarding-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-onboarding-best-practices.tips": "Adapt this resource to your context.",
+  "resource.api-onboarding-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-portfolio-management-guidelines.title": "API Portfolio Management Guidelines",
   "resource.api-portfolio-management-guidelines.description": "A guide to strategically manage an organization's API suite—prioritizing APIs, allocating resources, and monitoring performance across lifecycles.",
-  "resource.api-portfolio-management-guidelines.outcomes": "Better understanding of API portfolio management guidelines principles",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Standardized approach using API Portfolio Management Guidelines",
-  "resource.api-portfolio-management-guidelines.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-portfolio-management-guidelines.outcomes": "Shared understanding of the purpose and use of API Portfolio Management Guidelines",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "A consistent approach to applying API Portfolio Management Guidelines",
+  "resource.api-portfolio-management-guidelines.outcomes.2": "Improved application of the related practices",
   "resource.api-portfolio-management-guidelines.steps": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
   "resource.api-portfolio-management-guidelines.steps.1": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
   "resource.api-portfolio-management-guidelines.steps.2": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
   "resource.api-portfolio-management-guidelines.steps.3": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
-  "resource.api-portfolio-management-guidelines.tips": "Customize the API Portfolio Management Guidelines for your domain",
-  "resource.api-portfolio-management-guidelines.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-portfolio-management-guidelines.tips": "Adapt this resource to your context.",
+  "resource.api-portfolio-management-guidelines.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-security-best-practices.title": "API Security Best Practices",
   "resource.api-security-best-practices.description": "A set of actionable controls for securing APIs, including authentication, authorization, encryption, rate-limiting, and pipeline-level compliance checks.",
-  "resource.api-security-best-practices.outcomes": "Better understanding of API security best practices principles",
-  "resource.api-security-best-practices.outcomes.1": "Standardized approach using API Security Best Practices",
-  "resource.api-security-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-security-best-practices.outcomes": "Shared understanding of the purpose and use of API Security Best Practices",
+  "resource.api-security-best-practices.outcomes.1": "A consistent approach to applying API Security Best Practices",
+  "resource.api-security-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.api-security-best-practices.steps": "Ensure APIs meet security and compliance requirements through automated checks and audits.",
   "resource.api-security-best-practices.steps.1": "Implement security measures such as authentication, authorization, encryption, and rate limiting to protect APIs from threats.",
   "resource.api-security-best-practices.steps.2": "Implement automated security checks and compliance validations in the CI/CD pipeline to ensure APIs are secure and compliant.",
-  "resource.api-security-best-practices.tips": "Customize the API Security Best Practices for your domain",
-  "resource.api-security-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-security-best-practices.tips": "Adapt this resource to your context.",
+  "resource.api-security-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-team-structure-guidelines.title": "API Team Structure Guidelines",
   "resource.api-team-structure-guidelines.description": "Organizational guidance for defining roles and responsibilities within API teams to ensure clarity, collaboration, and accountability.",
-  "resource.api-team-structure-guidelines.outcomes": "Better understanding of API team structure guidelines principles",
-  "resource.api-team-structure-guidelines.outcomes.1": "Standardized approach using API Team Structure Guidelines",
-  "resource.api-team-structure-guidelines.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-team-structure-guidelines.outcomes": "Shared understanding of the purpose and use of API Team Structure Guidelines",
+  "resource.api-team-structure-guidelines.outcomes.1": "A consistent approach to applying API Team Structure Guidelines",
+  "resource.api-team-structure-guidelines.outcomes.2": "Improved application of the related practices",
   "resource.api-team-structure-guidelines.steps": "Define team structures and roles for API teams, including API product owners, developers, architects, and operations.",
-  "resource.api-team-structure-guidelines.tips": "Customize the API Team Structure Guidelines for your domain",
-  "resource.api-team-structure-guidelines.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-team-structure-guidelines.tips": "Adapt this resource to your context.",
+  "resource.api-team-structure-guidelines.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-testing-best-practices.title": "API Testing Best Practices",
   "resource.api-testing-best-practices.description": "Guidelines for implementing automated functional, performance, and security testing throughout the API lifecycle.",
-  "resource.api-testing-best-practices.outcomes": "Better understanding of API testing best practices principles",
-  "resource.api-testing-best-practices.outcomes.1": "Standardized approach using API Testing Best Practices",
-  "resource.api-testing-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-testing-best-practices.outcomes": "Shared understanding of the purpose and use of API Testing Best Practices",
+  "resource.api-testing-best-practices.outcomes.1": "A consistent approach to applying API Testing Best Practices",
+  "resource.api-testing-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.api-testing-best-practices.steps": "Test APIs for functionality, security, and performance using automated testing tools.",
   "resource.api-testing-best-practices.steps.1": "Integrate functional and non-functional testing into the CI/CD pipeline to ensure APIs meet quality standards.",
   "resource.api-testing-best-practices.steps.2": "Use automated testing tools to validate API functionality, security, and performance.",
-  "resource.api-testing-best-practices.tips": "Customize the API Testing Best Practices for your domain",
-  "resource.api-testing-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-testing-best-practices.tips": "Adapt this resource to your context.",
+  "resource.api-testing-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-training-programs.title": "API Training Programs",
   "resource.api-training-programs.description": "A roadmap for upskilling teams with structured learning paths in API design, governance, performance, and security.",
-  "resource.api-training-programs.outcomes": "Better understanding of API training programs principles",
-  "resource.api-training-programs.outcomes.1": "Standardized approach using API Training Programs",
-  "resource.api-training-programs.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-training-programs.outcomes": "Shared understanding of the purpose and use of API Training Programs",
+  "resource.api-training-programs.outcomes.1": "A consistent approach to applying API Training Programs",
+  "resource.api-training-programs.outcomes.2": "Improved application of the related practices",
   "resource.api-training-programs.steps": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
   "resource.api-training-programs.steps.1": "Encourage continuous learning through online courses, certifications, and community engagement.",
   "resource.api-training-programs.steps.2": "Provide training and resources to help teams adopt an API-first mindset and understand the benefits of APIs.",
   "resource.api-training-programs.steps.3": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
-  "resource.api-training-programs.tips": "Customize the API Training Programs for your domain",
-  "resource.api-training-programs.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-training-programs.tips": "Adapt this resource to your context.",
+  "resource.api-training-programs.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-versioning-best-practices.title": "API Versioning Best Practices",
   "resource.api-versioning-best-practices.description": "Strategies for introducing, maintaining, and retiring API versions while preserving backward compatibility and consumer trust.",
-  "resource.api-versioning-best-practices.outcomes": "Better understanding of API versioning best practices principles",
-  "resource.api-versioning-best-practices.outcomes.1": "Standardized approach using API Versioning Best Practices",
-  "resource.api-versioning-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-versioning-best-practices.outcomes": "Shared understanding of the purpose and use of API Versioning Best Practices",
+  "resource.api-versioning-best-practices.outcomes.1": "A consistent approach to applying API Versioning Best Practices",
+  "resource.api-versioning-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.api-versioning-best-practices.steps": "Define versioning strategies for APIs to manage changes and ensure backward compatibility.",
-  "resource.api-versioning-best-practices.tips": "Customize the API Versioning Best Practices for your domain",
-  "resource.api-versioning-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-versioning-best-practices.tips": "Adapt this resource to your context.",
+  "resource.api-versioning-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD For APIs",
   "resource.apiops-CI-CD-for-apis.description": "Deployment guidance that integrates API lifecycle tasks—design, testing, governance—into continuous integration and delivery pipelines.",
-  "resource.apiops-CI-CD-for-apis.outcomes": "Better understanding of CI/CDfor APIs principles",
-  "resource.apiops-CI-CD-for-apis.outcomes.1": "Standardized approach using CI/CD For APIs",
-  "resource.apiops-CI-CD-for-apis.outcomes.2": "Improved implementation of related API practices",
+  "resource.apiops-CI-CD-for-apis.outcomes": "Shared understanding of the purpose and use of APIOps CI/CD For APIs",
+  "resource.apiops-CI-CD-for-apis.outcomes.1": "A consistent approach to applying APIOps CI/CD For APIs",
+  "resource.apiops-CI-CD-for-apis.outcomes.2": "Improved application of the related practices",
   "resource.apiops-CI-CD-for-apis.steps": "Use CI/CD pipelines to automate build, test, and deployment processes, ensuring consistent quality and traceability.",
   "resource.apiops-CI-CD-for-apis.steps.1": "Integrate automated tests into the CI/CD pipeline to ensure continuous validation of API quality.",
   "resource.apiops-CI-CD-for-apis.steps.2": "Implement deployment strategies (e.g., blue-green deployments, canary releases) to minimize risks during API releases.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Establish a habit of reviewing metrics and planning continuous improvement activities.",
-  "resource.apiops-CI-CD-for-apis.tips": "Customize the CI/CD For APIs for your domain",
-  "resource.apiops-CI-CD-for-apis.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.apiops-CI-CD-for-apis.tips": "Adapt this resource to your context.",
+  "resource.apiops-CI-CD-for-apis.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.competitor-analysis-template.title": "Competitor Analysis Template",
   "resource.competitor-analysis-template.description": "A structured worksheet to benchmark your API offerings against competitors by mapping strengths, weaknesses, and value differentiators.",
-  "resource.competitor-analysis-template.outcomes": "Better understanding of competitor analysis template principles",
-  "resource.competitor-analysis-template.outcomes.1": "Standardized approach using Competitor Analysis Template",
-  "resource.competitor-analysis-template.outcomes.2": "Improved implementation of related API practices",
+  "resource.competitor-analysis-template.outcomes": "Shared understanding of the purpose and use of Competitor Analysis Template",
+  "resource.competitor-analysis-template.outcomes.1": "A consistent approach to applying Competitor Analysis Template",
+  "resource.competitor-analysis-template.outcomes.2": "Improved application of the related practices",
   "resource.competitor-analysis-template.steps": "Conduct a competitive analysis to identify key competitors, and their API offerings.",
   "resource.competitor-analysis-template.steps.1": "Analyze competitor APIs to understand their strengths, weaknesses, and unique selling points.",
-  "resource.competitor-analysis-template.tips": "Customize the Competitor Analysis Template for your domain",
-  "resource.competitor-analysis-template.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.competitor-analysis-template.tips": "Adapt this resource to your context.",
+  "resource.competitor-analysis-template.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.contract-first-design.title": "Contract First Design",
   "resource.contract-first-design.description": "A guideline advocating for API-first approaches using formal contracts (e.g., OpenAPI) to align stakeholders before development.",
-  "resource.contract-first-design.outcomes": "Better understanding of contract first design principles",
-  "resource.contract-first-design.outcomes.1": "Standardized approach using Contract First Design",
-  "resource.contract-first-design.outcomes.2": "Improved implementation of related API practices",
-  "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to ensure API contracts are validated before implementation.",
-  "resource.contract-first-design.steps.1": "Define API contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
-  "resource.contract-first-design.steps.2": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API contracts that are easy to share and validate.",
-  "resource.contract-first-design.tips": "Customize the Contract First Design for your domain",
-  "resource.contract-first-design.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.contract-first-design.outcomes": "Shared understanding of the purpose and use of Contract First Design",
+  "resource.contract-first-design.outcomes.1": "A consistent approach to applying Contract First Design",
+  "resource.contract-first-design.outcomes.2": "Improved application of the related practices",
+  "resource.contract-first-design.steps": "Apply contract-first or design-first approaches to ensure API interface contracts are validated before implementation.",
+  "resource.contract-first-design.steps.1": "Define API interface contracts that outline the expectations, responsibilities, and usage guidelines for each API.",
+  "resource.contract-first-design.steps.2": "Use standardized formats (e.g., OpenAPI, AsyncAPI) to create machine-readable API interface contracts that are easy to share and validate.",
+  "resource.contract-first-design.tips": "Adapt this resource to your context.",
+  "resource.contract-first-design.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.cross-functional-collaboration-best-practices.title": "Cross Functional Collaboration Best Practices",
   "resource.cross-functional-collaboration-best-practices.description": "Practices to facilitate communication and alignment between business and tech teams when planning or delivering APIs.",
-  "resource.cross-functional-collaboration-best-practices.outcomes": "Better understanding of cross functional collaboration best practices principles",
-  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Standardized approach using Cross Functional Collaboration Best Practices",
-  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.cross-functional-collaboration-best-practices.outcomes": "Shared understanding of the purpose and use of Cross Functional Collaboration Best Practices",
+  "resource.cross-functional-collaboration-best-practices.outcomes.1": "A consistent approach to applying Cross Functional Collaboration Best Practices",
+  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.cross-functional-collaboration-best-practices.steps": "Encourage cross-functional collaboration between API teams, business units, and stakeholders to align API initiatives with business goals.",
-  "resource.cross-functional-collaboration-best-practices.tips": "Customize the Cross Functional Collaboration Best Practices for your domain",
-  "resource.cross-functional-collaboration-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.cross-functional-collaboration-best-practices.tips": "Adapt this resource to your context.",
+  "resource.cross-functional-collaboration-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.data-privacy-guidelines.title": "Data Privacy Guidelines",
   "resource.data-privacy-guidelines.description": "Design considerations to ensure APIs meet data protection regulations like GDPR through anonymization and access controls.",
-  "resource.data-privacy-guidelines.outcomes": "Better understanding of data privacy guidelines principles",
-  "resource.data-privacy-guidelines.outcomes.1": "Standardized approach using Data Privacy Guidelines",
-  "resource.data-privacy-guidelines.outcomes.2": "Improved implementation of related API practices",
+  "resource.data-privacy-guidelines.outcomes": "Shared understanding of the purpose and use of Data Privacy Guidelines",
+  "resource.data-privacy-guidelines.outcomes.1": "A consistent approach to applying Data Privacy Guidelines",
+  "resource.data-privacy-guidelines.outcomes.2": "Improved application of the related practices",
   "resource.data-privacy-guidelines.steps": "Ensure user data privacy by implementing data protection measures, such as anonymization and access controls.",
-  "resource.data-privacy-guidelines.tips": "Customize the Data Privacy Guidelines for your domain",
-  "resource.data-privacy-guidelines.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.data-privacy-guidelines.tips": "Adapt this resource to your context.",
+  "resource.data-privacy-guidelines.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.domain-canvas.title": "Domain Canvas",
   "resource.domain-canvas.description": "A modeling tool to define and communicate the key entities and relationships in your domain, ensuring semantic consistency across capabilities, integrations, APIs, data products, and services.",
-  "resource.domain-canvas.outcomes": "Better understanding of domain canvas principles",
-  "resource.domain-canvas.outcomes.1": "Standardized approach using Domain Canvas",
-  "resource.domain-canvas.outcomes.2": "Improved implementation of related capability and interface practices",
+  "resource.domain-canvas.outcomes": "Shared domain model and terminology",
+  "resource.domain-canvas.outcomes.1": "Core entities, relationships, rules, and ownership clarified",
+  "resource.domain-canvas.outcomes.2": "Semantic consistency across capabilities, integrations, APIs, data products, and services",
   "resource.domain-canvas.steps": "Define core entities, their attributes, and relationships to create a shared conceptual understanding across capabilities, integrations, APIs, data products, and services.",
-  "resource.domain-canvas.tips": "Customize the Domain Canvas for your domain",
-  "resource.domain-canvas.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.domain-canvas.tips": "Use business language first; map it to technical models only after the domain is understood.",
+  "resource.domain-canvas.tips.1": "Validate the model with domain experts, producers, and consumers.",
   "resource.ecosystem-vision-template.title": "Ecosystem Vision Template",
   "resource.ecosystem-vision-template.description": "A strategic planning tool to define the API ecosystem, including target partners, value chains, and integration opportunities.",
-  "resource.ecosystem-vision-template.outcomes": "Better understanding of ecosystem vision template principles",
-  "resource.ecosystem-vision-template.outcomes.1": "Standardized approach using Ecosystem Vision Template",
-  "resource.ecosystem-vision-template.outcomes.2": "Improved implementation of related API practices",
+  "resource.ecosystem-vision-template.outcomes": "Shared understanding of the purpose and use of Ecosystem Vision Template",
+  "resource.ecosystem-vision-template.outcomes.1": "A consistent approach to applying Ecosystem Vision Template",
+  "resource.ecosystem-vision-template.outcomes.2": "Improved application of the related practices",
   "resource.ecosystem-vision-template.steps": "Conduct market research to identify trends, opportunities, and threats in the API landscape.",
   "resource.ecosystem-vision-template.steps.1": "Identify key ecosystem partners and stakeholders who will benefit from or contribute to the ecosystem.",
   "resource.ecosystem-vision-template.steps.2": "Identify gaps in the market that your APIs can fill, based on competitor offerings.",
@@ -174,83 +174,83 @@
   "resource.ecosystem-vision-template.steps.4": "Develop a differentiation strategy that highlights unique features and benefits of your APIs.",
   "resource.ecosystem-vision-template.steps.5": "Define the ecosystem vision for your APIs, including how they will interact with other systems and platforms.",
   "resource.ecosystem-vision-template.steps.6": "Design APIs to enable seamless integration and collaboration within the ecosystem.",
-  "resource.ecosystem-vision-template.tips": "Customize the Ecosystem Vision Template for your domain",
-  "resource.ecosystem-vision-template.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.ecosystem-vision-template.tips": "Adapt this resource to your context.",
+  "resource.ecosystem-vision-template.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.industry-standards-and-best-practices.title": "Industry Standards And Best Practices",
   "resource.industry-standards-and-best-practices.description": "A reference resource for aligning API design and operation with widely recognized industry frameworks and specifications.",
-  "resource.industry-standards-and-best-practices.outcomes": "Better understanding of industry standards and best practices principles",
-  "resource.industry-standards-and-best-practices.outcomes.1": "Standardized approach using Industry Standards And Best Practices",
-  "resource.industry-standards-and-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.industry-standards-and-best-practices.outcomes": "Shared understanding of the purpose and use of Industry Standards And Best Practices",
+  "resource.industry-standards-and-best-practices.outcomes.1": "A consistent approach to applying Industry Standards And Best Practices",
+  "resource.industry-standards-and-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.industry-standards-and-best-practices.steps": "Identify industry standards and best practices to ensure APIs are competitive and compliant.",
-  "resource.industry-standards-and-best-practices.tips": "Customize the Industry Standards And Best Practices for your domain",
-  "resource.industry-standards-and-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.industry-standards-and-best-practices.tips": "Adapt this resource to your context.",
+  "resource.industry-standards-and-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.partner-integration-guidelines.title": "Partner Integration Guidelines",
   "resource.partner-integration-guidelines.description": "Integration checklists and communication patterns to manage technical and legal aspects of third-party API relationships.",
-  "resource.partner-integration-guidelines.outcomes": "Better understanding of partner integration guidelines principles",
-  "resource.partner-integration-guidelines.outcomes.1": "Standardized approach using Partner Integration Guidelines",
-  "resource.partner-integration-guidelines.outcomes.2": "Improved implementation of related API practices",
+  "resource.partner-integration-guidelines.outcomes": "Shared understanding of the purpose and use of Partner Integration Guidelines",
+  "resource.partner-integration-guidelines.outcomes.1": "A consistent approach to applying Partner Integration Guidelines",
+  "resource.partner-integration-guidelines.outcomes.2": "Improved application of the related practices",
   "resource.partner-integration-guidelines.steps": "Establish integration processes and guidelines for collaborating with partners, including technical integration, data sharing, and support.",
   "resource.partner-integration-guidelines.steps.1": "Monitor partner API performance and compliance to ensure reliability and alignment with your API strategy.",
-  "resource.partner-integration-guidelines.tips": "Customize the Partner Integration Guidelines for your domain",
-  "resource.partner-integration-guidelines.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.partner-integration-guidelines.tips": "Adapt this resource to your context.",
+  "resource.partner-integration-guidelines.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.role-communication-best-practices.title": "Role Communication Best Practices",
   "resource.role-communication-best-practices.description": "Tools to define and document who is responsible for what within API initiatives, ensuring handoffs and accountability are clear.",
-  "resource.role-communication-best-practices.outcomes": "Better understanding of role communication best practices principles",
-  "resource.role-communication-best-practices.outcomes.1": "Standardized approach using Role Communication Best Practices",
-  "resource.role-communication-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.role-communication-best-practices.outcomes": "Shared understanding of the purpose and use of Role Communication Best Practices",
+  "resource.role-communication-best-practices.outcomes.1": "A consistent approach to applying Role Communication Best Practices",
+  "resource.role-communication-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.role-communication-best-practices.steps": "Establish clear responsibilities for each role, including API design, development, testing, and operations.",
   "resource.role-communication-best-practices.steps.1": "Ensure roles and responsibilities are communicated to all team members and stakeholders to ensure alignment.",
-  "resource.role-communication-best-practices.tips": "Customize the Role Communication Best Practices for your domain",
-  "resource.role-communication-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.role-communication-best-practices.tips": "Adapt this resource to your context.",
+  "resource.role-communication-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.scalable-infrastructure-best-practices.title": "Scalable Infrastructure Best Practices",
   "resource.scalable-infrastructure-best-practices.description": "Architectural guidance to ensure APIs are deployed on infrastructure that can elastically handle usage spikes and growth.",
-  "resource.scalable-infrastructure-best-practices.outcomes": "Better understanding of scalable infrastructure best practices principles",
-  "resource.scalable-infrastructure-best-practices.outcomes.1": "Standardized approach using Scalable Infrastructure Best Practices",
-  "resource.scalable-infrastructure-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.scalable-infrastructure-best-practices.outcomes": "Shared understanding of the purpose and use of Scalable Infrastructure Best Practices",
+  "resource.scalable-infrastructure-best-practices.outcomes.1": "A consistent approach to applying Scalable Infrastructure Best Practices",
+  "resource.scalable-infrastructure-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.scalable-infrastructure-best-practices.steps": "Design API infrastructure to be scalable and resilient, using cloud-native patterns and technologies.",
   "resource.scalable-infrastructure-best-practices.steps.1": "Monitor infrastructure performance and capacity to ensure it can handle growing demand.",
-  "resource.scalable-infrastructure-best-practices.tips": "Customize the Scalable Infrastructure Best Practices for your domain",
-  "resource.scalable-infrastructure-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.scalable-infrastructure-best-practices.tips": "Adapt this resource to your context.",
+  "resource.scalable-infrastructure-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.service-agreement-template.title": "Service Agreement Template",
   "resource.service-agreement-template.description": "A customizable agreement format that defines expectations, SLAs, responsibilities, and access terms for API consumption.",
-  "resource.service-agreement-template.outcomes": "Better understanding of service agreement template principles",
-  "resource.service-agreement-template.outcomes.1": "Standardized approach using Service Agreement Template",
-  "resource.service-agreement-template.outcomes.2": "Improved implementation of related API practices",
+  "resource.service-agreement-template.outcomes": "Shared understanding of the purpose and use of Service Agreement Template",
+  "resource.service-agreement-template.outcomes.1": "A consistent approach to applying Service Agreement Template",
+  "resource.service-agreement-template.outcomes.2": "Improved application of the related practices",
   "resource.service-agreement-template.steps": "Define service agreements that outline the expectations, service levels, and responsibilities for each API.",
   "resource.service-agreement-template.steps.1": "Use standardized formats to create machine-readable service agreements that are easy to share and validate.",
   "resource.service-agreement-template.steps.2": "Ensure service agreements are reviewed and approved by stakeholders to ensure alignment and clarity.",
-  "resource.service-agreement-template.tips": "Customize the Service Agreement Template for your domain",
-  "resource.service-agreement-template.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.service-agreement-template.tips": "Adapt this resource to your context.",
+  "resource.service-agreement-template.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.stakeholder-engagement-best-practices.title": "Stakeholder Engagement Best Practices",
   "resource.stakeholder-engagement-best-practices.description": "Engagement tactics for aligning internal and external stakeholders around shared API goals, value, and governance.",
-  "resource.stakeholder-engagement-best-practices.outcomes": "Better understanding of stakeholder engagement best practices principles",
-  "resource.stakeholder-engagement-best-practices.outcomes.1": "Standardized approach using Stakeholder Engagement Best Practices",
-  "resource.stakeholder-engagement-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.stakeholder-engagement-best-practices.outcomes": "Shared understanding of the purpose and use of Stakeholder Engagement Best Practices",
+  "resource.stakeholder-engagement-best-practices.outcomes.1": "A consistent approach to applying Stakeholder Engagement Best Practices",
+  "resource.stakeholder-engagement-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.stakeholder-engagement-best-practices.steps": "Engage stakeholders to ensure alignment and support for API initiatives.",
-  "resource.stakeholder-engagement-best-practices.tips": "Customize the Stakeholder Engagement Best Practices for your domain",
-  "resource.stakeholder-engagement-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.stakeholder-engagement-best-practices.tips": "Adapt this resource to your context.",
+  "resource.stakeholder-engagement-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.test-automation-frameworks.title": "Test Automation Frameworks",
-  "resource.test-automation-frameworks.description": "Recommended tools and patterns for automating API contract, regression, and integration testing across environments.",
-  "resource.test-automation-frameworks.outcomes": "Better understanding of test automation frameworks principles",
-  "resource.test-automation-frameworks.outcomes.1": "Standardized approach using Test Automation Frameworks",
-  "resource.test-automation-frameworks.outcomes.2": "Improved implementation of related API practices",
+  "resource.test-automation-frameworks.description": "Recommended tools and patterns for automating API interface contract, regression, and integration testing across environments.",
+  "resource.test-automation-frameworks.outcomes": "Shared understanding of the purpose and use of Test Automation Frameworks",
+  "resource.test-automation-frameworks.outcomes.1": "A consistent approach to applying Test Automation Frameworks",
+  "resource.test-automation-frameworks.outcomes.2": "Improved application of the related practices",
   "resource.test-automation-frameworks.steps": "Implement test automation frameworks that support contract testing, integration testing, and end-to-end testing.",
-  "resource.test-automation-frameworks.tips": "Customize the Test Automation Frameworks for your domain",
-  "resource.test-automation-frameworks.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.test-automation-frameworks.tips": "Adapt this resource to your context.",
+  "resource.test-automation-frameworks.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.vendor-management-best-practices.title": "Vendor Management Best Practices",
   "resource.vendor-management-best-practices.description": "Framework for evaluating and managing external API vendors and third-party integrations based on risk, performance, and compliance.",
-  "resource.vendor-management-best-practices.outcomes": "Better understanding of vendor management best practices principles",
-  "resource.vendor-management-best-practices.outcomes.1": "Standardized approach using Vendor Management Best Practices",
-  "resource.vendor-management-best-practices.outcomes.2": "Improved implementation of related API practices",
+  "resource.vendor-management-best-practices.outcomes": "Shared understanding of the purpose and use of Vendor Management Best Practices",
+  "resource.vendor-management-best-practices.outcomes.1": "A consistent approach to applying Vendor Management Best Practices",
+  "resource.vendor-management-best-practices.outcomes.2": "Improved application of the related practices",
   "resource.vendor-management-best-practices.steps": "Establish vendor management processes to evaluate, onboard, and monitor third-party API vendors.",
   "resource.vendor-management-best-practices.steps.1": "Define criteria for evaluating vendor APIs, including reliability, security, and compliance.",
-  "resource.vendor-management-best-practices.tips": "Customize the Vendor Management Best Practices for your domain",
-  "resource.vendor-management-best-practices.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.vendor-management-best-practices.tips": "Adapt this resource to your context.",
+  "resource.vendor-management-best-practices.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-audit-checklist.title": "API Audit Checklist",
   "resource.api-audit-checklist.description": "A lifecycle-based checklist to verify API readiness across design, delivery, publishing, and compliance using defined audit criteria and evidence.",
-  "resource.api-audit-checklist.outcomes": "Better understanding of API audit checklist principles",
-  "resource.api-audit-checklist.outcomes.1": "Standardized approach using API Audit Checklist",
-  "resource.api-audit-checklist.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-audit-checklist.outcomes": "Shared understanding of the purpose and use of API Audit Checklist",
+  "resource.api-audit-checklist.outcomes.1": "A consistent approach to applying API Audit Checklist",
+  "resource.api-audit-checklist.outcomes.2": "Improved application of the related practices",
   "resource.api-audit-checklist.steps": "Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.",
   "resource.api-audit-checklist.steps.1": "Conduct audits to assess lifecycle coverage and verify that the API meets business, design, and operational standards.",
   "resource.api-audit-checklist.steps.2": "Ensure that documentation, security models, gateway configuration, and legal requirements are clearly defined, validated, and supported by evidence.",
@@ -265,7 +265,7 @@
   "resource.api-business-model-canvas.steps.1": "Define consumer segments",
   "resource.api-business-model-canvas.steps.2": "Identify developer relations strategies",
   "resource.api-business-model-canvas.steps.3": "Map distribution channels",
-  "resource.api-business-model-canvas.steps.4": "document key resources and activities",
+  "resource.api-business-model-canvas.steps.4": "Document key resources and activities",
   "resource.api-business-model-canvas.steps.5": "Identify key partners and stakeholders",
   "resource.api-business-model-canvas.steps.6": "Highlight benefits and costs",
   "resource.api-business-model-canvas.tips": "Start with a single API to ensure clarity",
@@ -273,16 +273,16 @@
   "resource.api-business-model-canvas.tips.2": "Validate outputs with key stakeholders",
   "resource.api-design-principles.title": "API Design Principles",
   "resource.api-design-principles.description": "A concise guide to API usability, discoverability, and consistency grounded in shared design rules and real consumer needs.",
-  "resource.api-design-principles.outcomes": "Better understanding of API design principles principles",
-  "resource.api-design-principles.outcomes.1": "Standardized approach using API Design Principles",
-  "resource.api-design-principles.outcomes.2": "Improved implementation of related API practices",
+  "resource.api-design-principles.outcomes": "Shared understanding of the purpose and use of API Design Principles",
+  "resource.api-design-principles.outcomes.1": "A consistent approach to applying API Design Principles",
+  "resource.api-design-principles.outcomes.2": "Improved application of the related practices",
   "resource.api-design-principles.steps": "**Consumer-first design:** start every APIOps cycle by gathering user goals and domain terms so APIs solve real problems.",
   "resource.api-design-principles.steps.1": "**Consistent naming and behavior:** apply shared conventions for resources, errors and formats to make APIs predictable.",
   "resource.api-design-principles.steps.2": "**Contract driven:** capture the interface with OpenAPI or AsyncAPI before coding to align teams and enable automation.",
   "resource.api-design-principles.steps.3": "**Usability and discoverability:** provide clear documentation and examples so developers quickly understand how to use the API.",
   "resource.api-design-principles.steps.4": "**Iterate safely:** evolve designs in small, versioned increments so changes do not disrupt existing consumers.",
-  "resource.api-design-principles.tips": "Customize the API Design Principles for your domain",
-  "resource.api-design-principles.tips.1": "Use it collaboratively across business and tech roles",
+  "resource.api-design-principles.tips": "Adapt this resource to your context.",
+  "resource.api-design-principles.tips.1": "Use this resource collaboratively across relevant business and technical roles.",
   "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas",
   "resource.api-value-proposition-canvas.description": "Align API features with user needs by mapping tasks, pains, and gains to API products.",
   "resource.api-value-proposition-canvas.outcomes": "Focused feature development",
@@ -296,37 +296,37 @@
   "resource.api-value-proposition-canvas.tips.1": "Highlight features that relieve pains or enhance gains",
   "resource.api-value-proposition-canvas.tips.2": "Validate features with API consumers to ensure alignment",
   "resource.business-impact-canvas.title": "Business Impact Canvas",
-  "resource.business-impact-canvas.description": "Identify availability, security, data, and business-impact risks that shape architecture and platform decisions.",
-  "resource.business-impact-canvas.outcomes": "Scalable and resilient capability architecture",
-  "resource.business-impact-canvas.outcomes.1": "Enhanced security and compliance",
-  "resource.business-impact-canvas.outcomes.2": "Improved capability performance and reliability",
+  "resource.business-impact-canvas.description": "Identify business, availability, security, data, compliance, and operational risks that should shape architecture and platform decisions.",
+  "resource.business-impact-canvas.outcomes": "Documented business and operational impact assessment",
+  "resource.business-impact-canvas.outcomes.1": "Prioritized risks and mitigation actions",
+  "resource.business-impact-canvas.outcomes.2": "Evidence for architecture and platform decisions",
   "resource.business-impact-canvas.steps": "Availability Risks: Identify risks and impacts.",
   "resource.business-impact-canvas.steps.1": "Ways to Mitigate Availability Risks: Define mitigation measures.",
   "resource.business-impact-canvas.steps.2": "Security Risks: Document security-related risks.",
   "resource.business-impact-canvas.steps.3": "Ways to Mitigate Security Risks: Propose strategies to mitigate security risks.",
   "resource.business-impact-canvas.steps.4": "Data Risks: Identify risks to data accuracy or availability.",
   "resource.business-impact-canvas.steps.5": "Ways to Mitigate Data Risks: Plan strategies to address data risks.",
-  "resource.business-impact-canvas.tips": "Involve architects and developers in the design process",
-  "resource.business-impact-canvas.tips.1": "Use past incidents to identify potential risks",
-  "resource.business-impact-canvas.tips.2": "Prioritize capabilities with the highest business impact",
+  "resource.business-impact-canvas.tips": "Complete this before selecting or confirming the implementation style.",
+  "resource.business-impact-canvas.tips.1": "Review the risks with both business and technical stakeholders.",
+  "resource.business-impact-canvas.tips.2": "Use past incidents and operational evidence to challenge assumptions.",
   "resource.capacity-canvas.title": "Capacity Canvas",
-  "resource.capacity-canvas.description": "Plan capacity to meet current and future business demand, ensuring scalability and performance for the selected capability or solution pattern.",
-  "resource.capacity-canvas.outcomes": "Aligned capacity with business volumes",
-  "resource.capacity-canvas.outcomes.1": "Prepared for future consumption trends",
-  "resource.capacity-canvas.outcomes.2": "Defined caching and rate-limiting strategies",
+  "resource.capacity-canvas.description": "Plan capacity for current and future demand, including volumes, peaks, latency, availability, scaling, caching, and rate limits for the selected capability and implementation style.",
+  "resource.capacity-canvas.outcomes": "Capacity requirements aligned with expected business demand",
+  "resource.capacity-canvas.outcomes.1": "Peak-load, availability, and growth assumptions documented",
+  "resource.capacity-canvas.outcomes.2": "Scaling, caching, and rate-limiting decisions defined",
   "resource.capacity-canvas.steps": "Document current business volumes",
   "resource.capacity-canvas.steps.1": "Forecast future consumption trends",
   "resource.capacity-canvas.steps.2": "Plan for peak load and availability requirements",
   "resource.capacity-canvas.steps.3": "Define caching and rate-limiting strategies",
   "resource.capacity-canvas.steps.4": "Propose scaling strategies",
-  "resource.capacity-canvas.tips": "Use analytics to forecast growth trends",
-  "resource.capacity-canvas.tips.1": "Define peak usage scenarios",
-  "resource.capacity-canvas.tips.2": "Include scalability testing in the planning phase",
+  "resource.capacity-canvas.tips": "Complete this before finalizing architecture and platform decisions.",
+  "resource.capacity-canvas.tips.1": "Use measured data where available and state assumptions explicitly.",
+  "resource.capacity-canvas.tips.2": "Revisit the canvas after pilots or material changes in demand.",
   "resource.customer-journey-canvas.title": "Customer Journey Canvas",
   "resource.customer-journey-canvas.description": "Map customer, partner, or consumer journeys to identify needs, pain points, gains, inputs, outputs, and experience expectations.",
-  "resource.customer-journey-canvas.outcomes": "Improved customer understanding",
-  "resource.customer-journey-canvas.outcomes.1": "Enhanced capability and solution design",
-  "resource.customer-journey-canvas.outcomes.2": "Better user experience",
+  "resource.customer-journey-canvas.outcomes": "Shared understanding of the customer, partner, or consumer journey",
+  "resource.customer-journey-canvas.outcomes.1": "Needs, pain points, gains, inputs, and outputs documented",
+  "resource.customer-journey-canvas.outcomes.2": "Journey evidence available for capability, requirements, and architecture decisions",
   "resource.customer-journey-canvas.steps": "Define customer persona",
   "resource.customer-journey-canvas.steps.1": "Identify triggers for the journey",
   "resource.customer-journey-canvas.steps.2": "Describe the journey's end",
@@ -335,19 +335,19 @@
   "resource.customer-journey-canvas.steps.5": "Summarize customer gains",
   "resource.customer-journey-canvas.steps.6": "Define necessary inputs and resulting outputs",
   "resource.customer-journey-canvas.steps.7": "Define interactions and processing expectations for each step",
-  "resource.customer-journey-canvas.tips": "Iterate with team input to refine steps",
-  "resource.customer-journey-canvas.tips.1": "Use outputs from this canvas to inform value proposition, domain, requirements, and architecture decisions",
+  "resource.customer-journey-canvas.tips": "Validate the journey with people who perform or experience it.",
+  "resource.customer-journey-canvas.tips.1": "Use the results to inform value proposition, domain, requirements, and architecture work.",
   "resource.event-canvas.title": "Event Canvas",
-  "resource.event-canvas.description": "Design event-driven APIs by defining events, triggers, and processing logic.",
-  "resource.event-canvas.outcomes": "Defined event-driven architecture",
-  "resource.event-canvas.outcomes.1": "Clear event triggers and processing logic",
-  "resource.event-canvas.outcomes.2": "Improved responsiveness to real-time changes",
+  "resource.event-canvas.description": "Design event-driven interfaces and integrations by defining events, triggers, schemas, producers, consumers, and processing logic.",
+  "resource.event-canvas.outcomes": "Defined event-driven interaction model",
+  "resource.event-canvas.outcomes.1": "Events, triggers, schemas, producers, and consumers clarified",
+  "resource.event-canvas.outcomes.2": "Processing, acknowledgement, and failure expectations documented",
   "resource.event-canvas.steps": "Identify key events in the system",
   "resource.event-canvas.steps.1": "Define triggers for each event",
-  "resource.event-canvas.steps.2": "Describe backend processing logic for events",
+  "resource.event-canvas.steps.2": "Describe event processing, state changes, and failure handling.",
   "resource.event-canvas.steps.3": "Specify resulting outputs or acknowledgments",
   "resource.event-canvas.tips": "Use event schemas to standardize event formats",
-  "resource.event-canvas.tips.1": "document event flows and dependencies",
+  "resource.event-canvas.tips.1": "Document event flows, ownership, ordering assumptions, and dependencies.",
   "resource.event-canvas.tips.2": "Validate event processing with test cases",
   "resource.graphql-canvas.title": "GraphQL Canvas",
   "resource.graphql-canvas.description": "Design GraphQL APIs by defining types, queries, mutations, and subscriptions.",
@@ -363,26 +363,26 @@
   "resource.graphql-canvas.steps.6": "Define authentication and authorization: Who can access which fields or types?",
   "resource.graphql-canvas.steps.7": "Consider if there are any pagination, filtering, or rate-limiting constraints",
   "resource.graphql-canvas.tips": "Use introspection to validate type definitions",
-  "resource.graphql-canvas.tips.1": "document example queries and mutations",
+  "resource.graphql-canvas.tips.1": "Document example queries and mutations",
   "resource.graphql-canvas.tips.2": "Ensure type names are descriptive and consistent",
   "resource.interaction-canvas.title": "Interaction Canvas",
   "resource.interaction-canvas.description": "Define interactions, workflows, inputs, outputs, commands, queries, events, and expected responses to ensure a consistent consumer experience.",
-  "resource.interaction-canvas.outcomes": "Clear interaction workflows",
-  "resource.interaction-canvas.outcomes.1": "Defined inputs and outputs for each interaction",
-  "resource.interaction-canvas.outcomes.2": "Consistent validation rules across interactions",
+  "resource.interaction-canvas.outcomes": "Defined interaction model for the selected capability",
+  "resource.interaction-canvas.outcomes.1": "Inputs, outputs, commands, queries, events, and responses clarified",
+  "resource.interaction-canvas.outcomes.2": "Validation rules and interaction expectations agreed",
   "resource.interaction-canvas.steps": "Map interactions to user, consumer, or system tasks",
   "resource.interaction-canvas.steps.1": "Define access points, operations, commands, queries, or events for each interaction",
-  "resource.interaction-canvas.steps.2": "document inputs and outputs for each interaction",
+  "resource.interaction-canvas.steps.2": "Document inputs and outputs for each interaction.",
   "resource.interaction-canvas.steps.3": "Specify validation rules and constraints",
   "resource.interaction-canvas.steps.4": "Create interaction models for CRUD, query-driven, command-driven, and event-driven interactions",
   "resource.interaction-canvas.tips": "Start with common use cases before handling edge cases",
   "resource.interaction-canvas.tips.1": "Simulate interactions with mock data to validate workflows",
-  "resource.interaction-canvas.tips.2": "document expected responses for successful and unsuccessful interactions",
+  "resource.interaction-canvas.tips.2": "Document expected responses for successful, unsuccessful, and exceptional interactions.",
   "resource.location-canvas.title": "Location Canvas",
   "resource.location-canvas.description": "Map consumer, producer, system, data, network, regulatory, and trust-boundary locations to ensure compliance and performance across regions.",
-  "resource.location-canvas.outcomes": "Compliance with local regulations",
-  "resource.location-canvas.outcomes.1": "Optimized performance across regions",
-  "resource.location-canvas.outcomes.2": "Enhanced understanding of regional requirements",
+  "resource.location-canvas.outcomes": "Documented location, residency, network, and regulatory requirements",
+  "resource.location-canvas.outcomes.1": "Regional performance and accessibility constraints identified",
+  "resource.location-canvas.outcomes.2": "Data residency, trust boundaries, and applicable regulations clarified",
   "resource.location-canvas.steps": "Map locations of producers, source systems, platforms, and consumers.",
   "resource.location-canvas.steps.1": "Document where consumers are located.",
   "resource.location-canvas.steps.2": "Identify applicable regulations.",
@@ -403,9 +403,9 @@
   "resource.rest-canvas.steps.3": "Provide example requests and responses for each verb",
   "resource.rest-canvas.tips": "Use standard HTTP methods (GET, POST, PUT, DELETE)",
   "resource.rest-canvas.tips.1": "Ensure resource URIs are intuitive and consistent",
-  "resource.rest-canvas.tips.2": "document error handling and response codes",
+  "resource.rest-canvas.tips.2": "Document error handling and response codes",
   "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an integration style.",
+  "resource.capability-value-proposition-canvas.description": "A technology-agnostic canvas for mapping consumer tasks, gains, pains, and candidate reusable capabilities before selecting an implementation style.",
   "resource.capability-value-proposition-canvas.outcomes": "Clear reusable capability value proposition",
   "resource.capability-value-proposition-canvas.outcomes.1": "Consumer tasks, gains, and pains captured without assuming a technology",
   "resource.capability-value-proposition-canvas.outcomes.2": "Candidate reusable capabilities identified for architecture evaluation",
@@ -413,10 +413,10 @@
   "resource.capability-value-proposition-canvas.steps.1": "Identify gain-enabling capability features.",
   "resource.capability-value-proposition-canvas.steps.2": "Identify pain-relieving capability features.",
   "resource.capability-value-proposition-canvas.steps.3": "Group the features into candidate reusable capabilities.",
-  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements point to a style.",
-  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when API is not yet the chosen integration style.",
+  "resource.capability-value-proposition-canvas.tips": "Stay technology agnostic until the requirements indicate a suitable implementation style.",
+  "resource.capability-value-proposition-canvas.tips.1": "Use this instead of the API Value Proposition Canvas when an API is not yet the selected implementation style.",
   "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "A business model canvas for reusable integration capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming API delivery.",
+  "resource.capability-business-model-canvas.description": "A business model canvas for reusable capabilities, covering value, consumers, ownership, engagement, costs, and benefits without assuming an implementation style.",
   "resource.capability-business-model-canvas.outcomes": "Viable reusable capability operating model",
   "resource.capability-business-model-canvas.outcomes.1": "Ownership, consumers, channels, partners, and support needs clarified",
   "resource.capability-business-model-canvas.outcomes.2": "Costs and benefits visible before architecture commitment",
@@ -426,19 +426,19 @@
   "resource.capability-business-model-canvas.steps.3": "Capture costs and benefits.",
   "resource.capability-business-model-canvas.steps.4": "Clarify ownership, funding, support, and lifecycle expectations.",
   "resource.capability-business-model-canvas.steps.5": "Validate the model with consumers, producers, and governance stakeholders.",
-  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas when the integration style is still open.",
+  "resource.capability-business-model-canvas.tips": "Use this instead of the API Business Model Canvas while the implementation style remains open.",
   "resource.capability-business-model-canvas.tips.1": "Keep the focus on reusable capability viability, not a one-off connection.",
   "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer-facing experience and non-functional needs that should guide the later architecture choice.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer requirements",
+  "resource.consumer-experience-requirements-canvas.description": "A requirements canvas for consumer experience and non-functional needs that should guide the later architecture and implementation-style decision.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Technology-agnostic consumer and service requirements",
   "resource.consumer-experience-requirements-canvas.outcomes.1": "Experience and non-functional needs captured before design starts",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for style selection",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Architecture implications documented for implementation-style selection",
   "resource.consumer-experience-requirements-canvas.steps": "Capture consumer goals and usage context.",
   "resource.consumer-experience-requirements-canvas.steps.1": "Document availability, timeliness, volume, performance, data quality, and consistency expectations.",
   "resource.consumer-experience-requirements-canvas.steps.2": "Document security, privacy, onboarding, change, observability, support, and recovery expectations.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible architecture styles.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Summarize what the requirements imply for possible implementation styles.",
   "resource.consumer-experience-requirements-canvas.tips": "Use this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose API, event, file, stream, or data product until the requirements indicate the fit.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Do not choose an API, event, file, stream, data product, direct integration, or hybrid style until the requirements indicate the fit.",
   "resource.integration-style-selection-guide.title": "Integration Style Selection Guide",
   "resource.integration-style-selection-guide.description": "Guidance for choosing between API, event, file, stream, data product, direct integration, or hybrid implementation styles based on requirements and constraints.",
   "resource.integration-style-selection-guide.outcomes": "Justified integration implementation style",
@@ -535,5 +535,11 @@
   "resource.automation-rollout-enablement-guide.steps.2": "Plan transition support for users, operators, and process owners.",
   "resource.automation-rollout-enablement-guide.steps.3": "Collect feedback after rollout and feed improvements into the backlog.",
   "resource.automation-rollout-enablement-guide.tips": "Use rollout language for automations instead of treating enablement as API publication.",
-  "resource.automation-rollout-enablement-guide.tips.1": "Include both users affected by the process and operators responsible for the automation."
+  "resource.automation-rollout-enablement-guide.tips.1": "Include both users affected by the process and operators responsible for the automation.",
+  "resource.api-community-engagement-strategies.tips.2": "Use this resource when an API is the selected implementation style.",
+  "resource.api-development-best-practices.tips.2": "Use this resource when an API is the selected implementation style.",
+  "resource.api-metrics-and-analytics.tips.2": "Use this resource when an API is the selected implementation style.",
+  "resource.api-testing-best-practices.tips.2": "Use this resource when an API is the selected implementation style.",
+  "resource.apiops-CI-CD-for-apis.tips.2": "Use this resource when an API is the selected implementation style.",
+  "resource.api-audit-checklist.tips.2": "Use this resource when an API is the selected implementation style."
 }
diff --git a/src/data/method/en/labels.stakeholders.json b/src/data/method/en/labels.stakeholders.json
index 283fc16..fd2ec34 100644
--- a/src/data/method/en/labels.stakeholders.json
+++ b/src/data/method/en/labels.stakeholders.json
@@ -3,47 +3,47 @@
   "stakeholder.involvement.core": "Core",
   "stakeholder.involvement.consulted": "Consulted",
   "stakeholder.business-owner.title": "Business Owner",
-  "stakeholder.business-owner.description": "Represents business goals, funding, and expected outcomes for the API initiative.",
+  "stakeholder.business-owner.description": "Represents business goals, funding, and expected outcomes for the capability, API, or automation initiative.",
   "stakeholder.api-program-owner.title": "API Program Owner",
   "stakeholder.api-program-owner.description": "Coordinates API portfolio practices, organizational alignment, and long-term API capability development.",
   "stakeholder.api-product-owner.title": "API Product Owner",
   "stakeholder.api-product-owner.description": "Drives the API opportunity, prioritization, and product-level decisions across the lifecycle.",
-  "stakeholder.capability-owner.title": "Capability owners",
-  "stakeholder.capability-owner.description": "Responsible for defining, maintaining, and evolving the capabilities.",
+  "stakeholder.capability-owner.title": "Capability Owner",
+  "stakeholder.capability-owner.description": "Owns the capability vision, value, priorities, lifecycle, and reuse across consumers.",
   "stakeholder.domain-specialist.title": "Domain Expert",
-  "stakeholder.domain-specialist.description": "Brings deep knowledge of the business domain, concepts, rules, and constraints the API must reflect.",
+  "stakeholder.domain-specialist.description": "Brings deep knowledge of the business domain, concepts, rules, and constraints the capability or interface must reflect.",
   "stakeholder.customer-specialist.title": "Customer or Partner Representative",
   "stakeholder.customer-specialist.description": "Contributes the business customer or partner perspective for the journey, value, and collaboration model.",
   "stakeholder.api-consumer-specialist.title": "API Consumer Representative",
   "stakeholder.api-consumer-specialist.description": "Represents the needs of developers, integrators, or other API consumers who use the API directly.",
   "stakeholder.platform-architect.title": "Platform Architect",
-  "stakeholder.platform-architect.description": "Guides platform, integration, scalability, and architecture decisions that shape how the API is built and operated.",
-  "stakeholder.api-architect.title": "API platform teams",
-  "stakeholder.api-architect.description": "Responsible for designing and maintaining the API platform.",
-  "stakeholder.integration-architect.title": "Solution architects",
-  "stakeholder.integration-architect.description": "Designs and implements integration solutions that connect the API with other systems.",
-  "stakeholder.platform-owner.title": "Platform owners",
-  "stakeholder.platform-owner.description": "Responsible for the overall management and strategic direction of the platform.",
+  "stakeholder.platform-architect.description": "Guides platform, integration, scalability, and architecture decisions that shape how the capability or API is built and operated.",
+  "stakeholder.api-architect.title": "API Architect",
+  "stakeholder.api-architect.description": "Owns API architecture, design principles, and interface contract quality.",
+  "stakeholder.integration-architect.title": "Integration Architect",
+  "stakeholder.integration-architect.description": "Designs integration approaches and implementation styles that connect the capability or API with other systems.",
+  "stakeholder.platform-owner.title": "Platform Owner",
+  "stakeholder.platform-owner.description": "Owns platform capabilities, roadmap, operational model, and service expectations.",
   "stakeholder.api-designer.title": "API Designer",
-  "stakeholder.api-designer.description": "Shapes the API contract, interaction model, consistency, and usability of the exposed capabilities.",
+  "stakeholder.api-designer.description": "Shapes the interface contract, interaction model, consistency, and usability of the exposed capabilities.",
   "stakeholder.api-engineer.title": "Delivery Engineer",
-  "stakeholder.api-engineer.description": "Owns implementation, automation, testing, and release flow concerns needed to deliver the API reliably.",
-  "stakeholder.automation-owner.title": "Automation owners",
-  "stakeholder.automation-owner.description": "Responsible for the automation of processes and workflows related to business operations.",
-  "stakeholder.process-owner.title": "Process owners",
-  "stakeholder.process-owner.description": "Responsible for managing and improving the processes and workflows related to business operations.",
-  "stakeholder.automation-engineer.title": "Automation teams",
-  "stakeholder.automation-engineer.description": "Responsible for implementing and maintaining automation solutions.",
+  "stakeholder.api-engineer.description": "Owns implementation, automation, testing, and release flow concerns needed to deliver the capability, API, or automation reliably.",
+  "stakeholder.automation-owner.title": "Automation Owner",
+  "stakeholder.automation-owner.description": "Owns automation goals, business value, priorities, controls, and lifecycle outcomes.",
+  "stakeholder.process-owner.title": "Process Owner",
+  "stakeholder.process-owner.description": "Owns the business process being automated, including objectives, rules, outcomes, and improvement priorities.",
+  "stakeholder.automation-engineer.title": "Automation Engineer",
+  "stakeholder.automation-engineer.description": "Implements, tests, integrates, and maintains automation solutions and supporting workflows.",
   "stakeholder.security-specialist.title": "Security Specialist",
   "stakeholder.security-specialist.description": "Ensures security risks, controls, and trust boundaries are addressed throughout the API lifecycle.",
   "stakeholder.compliance-specialist.title": "Compliance and Legal Specialist",
-  "stakeholder.compliance-specialist.description": "Clarifies legal, privacy, regulatory, and contractual requirements that affect the API.",
+  "stakeholder.compliance-specialist.description": "Clarifies legal, privacy, regulatory, and contractual requirements that affect the capability, API, interface, or automation.",
   "stakeholder.governance-specialist.title": "API Governance Owner",
   "stakeholder.governance-specialist.description": "Represents review, audit, and organization-wide governance practices for API quality and conformity.",
   "stakeholder.api-devrel-specialist.title": "Documentation and DevRel Owner",
   "stakeholder.api-devrel-specialist.description": "Owns onboarding content, developer communication, and documentation quality for API consumers.",
   "stakeholder.operations-specialist.title": "Support and Operations Owner",
-  "stakeholder.operations-specialist.description": "Represents runtime support, incident handling, observability, and operational readiness.",
+  "stakeholder.operations-specialist.description": "Represents runtime support, incident handling, observability, and operational readiness for the capability, API, or automation.",
   "stakeholder.partner-specialist.title": "Partner or Vendor Manager",
-  "stakeholder.partner-specialist.description": "Coordinates external partner, supplier, or vendor relationships that influence API strategy and delivery."
+  "stakeholder.partner-specialist.description": "Coordinates external partner, supplier, or vendor relationships that influence capability or API strategy and delivery."
 }
diff --git a/src/data/method/fi/labels.criteria.json b/src/data/method/fi/labels.criteria.json
index 8b60a38..3db3788 100644
--- a/src/data/method/fi/labels.criteria.json
+++ b/src/data/method/fi/labels.criteria.json
@@ -1,6 +1,6 @@
 {
-  "exit_criteria": "Poistumiskriteerit",
-  "entry_criteria": "Sisäänpääsykriteerit",
+  "exit_criteria": "Valmistumiskriteerit",
+  "entry_criteria": "Aloituskriteerit",
   "criterion.metrics-feedback-available": "Olennaiset markkinasignaalit, palaute tai toiminnalliset havainnot ovat saatavilla tämän kyvykkyysmahdollisuuden ohjaamiseksi.",
   "criterion.business-goals-defined": "Liiketoimintatavoitteet on määritelty.",
   "criterion.market-research-done": "Markkinatutkimus tunnistaa kyvykkyysmahdollisuuksia.",
@@ -15,12 +15,12 @@
   "criterion.design-reflects-business-value": "Rajapintasuunnittelu ja tarjottavat kyvykkyydet ovat jäljitettävissä liiketoiminta-arvoon ja hyödyntäjien tarpeisiin.",
   "criterion.api-consistency": "Rajapintasuunnittelu noudattaa sovittuja suunnittelustandardeja ja käytäntöjä.",
   "criterion.api-contract-tested": "Rajapintasopimus on validoitu ja testattu toiminnallisia ja ei-toiminnallisia vaatimuksia vasten.",
-  "criterion.automation-workflow-validated": "Tyonkulku, saannot, integraatiot ja olennaiset rajapintasopimukset on validoitu ja testattu.",
+  "criterion.automation-workflow-validated": "Työnkulku, säännöt, integraatiot ja olennaiset rajapintasopimukset on validoitu ja testattu.",
   "criterion.api-description-available": "Rajapinta ja sen kyvykkyydet on dokumentoitu riittävän selkeästi katselmointia, auditointia ja käyttöönottoa varten.",
   "criterion.audit-passed": "Ratkaisu läpäisee laatu-, tietoturva-, vaatimustenmukaisuus- ja valmiustarkastukset.",
   "criterion.audit-reports-shared": "Auditointihavainnot ja korjauspäätökset on jaettu olennaisille sidosryhmille.",
-  "criterion.api-ready-for-publishing": "Kyvykkyys on valmis julkaistavaksi valitun toimitusmekanismin kautta.",
+  "criterion.api-ready-for-publishing": "Kyvykkyys on valmis julkaistavaksi tai toimitettavaksi valitun toimitusmekanismin kautta.",
   "criterion.api-documentation-ready": "Hyödyntäjille suunnattu dokumentaatio ja käyttöönottomateriaalit ovat valmiit.",
   "criterion.consumer-support-ready": "Hyödyntäjien käyttöönotto-, tuki- ja viestintäprosessit ovat valmiit.",
-  "criterion.legal-compliance-clear": "Julkaisun oikeudelliset, tietosuoja- ja vaatimustenmukaisuusvaatimukset on määritelty ja ymmärretty."
+  "criterion.legal-compliance-clear": "Julkaisun tai toimituksen oikeudelliset, tietosuoja- ja vaatimustenmukaisuusvaatimukset on määritelty ja ymmärretty."
 }
diff --git a/src/data/method/fi/labels.resources.json b/src/data/method/fi/labels.resources.json
index 61e6985..178eaf7 100644
--- a/src/data/method/fi/labels.resources.json
+++ b/src/data/method/fi/labels.resources.json
@@ -1,84 +1,84 @@
 {
   "resource.api-community-engagement-strategies.title": "API-yhteisön sitouttamisstrategiat",
   "resource.api-community-engagement-strategies.description": "Toimintakirja API-käyttöliittymien käyttöönoton edistämiseksi kehittämällä yhteisöjä sisällön, tukikanavien, palautesilmukoiden ja sosiaalisen sitoutumisen strategioiden avulla.",
-  "resource.api-community-engagement-strategies.outcomes": "API-yhteisön sitouttamisstrategioiden periaatteiden parempi ymmärtäminen",
+  "resource.api-community-engagement-strategies.outcomes": "Yhteinen ymmärrys resurssin API-yhteisön sitouttamisstrategiat tarkoituksesta ja käytöstä",
   "resource.api-community-engagement-strategies.steps": "Kehitä markkinointistrategioita APIen markkinoimiseksi kohdeyleisöille, mukaan lukien sosiaalinen media, blogit ja webinaarit.",
-  "resource.api-community-engagement-strategies.tips": "Mukauta API-yhteisön sitouttamisstrategiat omaan kontekstiisi sopiviksi",
+  "resource.api-community-engagement-strategies.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-compliance-best-practices.title": "API-vaatimustenmukaisuuden parhaat käytännöt",
   "resource.api-compliance-best-practices.description": "Varmista, että rajapinnat täyttävät oikeudelliset, sääntelyyn liittyvät ja sisäiset vaatimukset dokumentoinnin, valvonnan ja automaattisten validointien avulla.",
-  "resource.api-compliance-best-practices.outcomes": "Parempi ymmärrys API-vaatimustenmukaisuuden parhaiden käytäntöjen periaatteista",
+  "resource.api-compliance-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-vaatimustenmukaisuuden parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.api-compliance-best-practices.steps": "Dokumentoi vaatimustenmukaisuustoimenpiteet ja varmista, että niistä tiedotetaan sidosryhmille ja hyödyntäjille.",
-  "resource.api-compliance-best-practices.tips": "Mukauta API Compliance Best Practices -käytännöt omaan kontekstiisi.",
+  "resource.api-compliance-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-development-best-practices.title": "API-kehityksen parhaat käytännöt",
-  "resource.api-development-best-practices.description": "Ohjeet, joiden avulla validoitu API-rajapintasopimus voidaan muuttaa johdonmukaiseksi ja ylläpidettäväksi API-koodiksi käyttämällä vakiokirjastoja, uudelleenkäytettäviä malleja ja yhdenmukaistettuja kehitystyönkulkuja.",
-  "resource.api-development-best-practices.outcomes": "API-kehityksen parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
-  "resource.api-development-best-practices.steps": "Sovella näitä käytäntöjä validoituun API-sopimukseen ja toteutussuunnitelmaan ennen koodaamisen aloittamista.",
+  "resource.api-development-best-practices.description": "Toteutusohje, jonka avulla validoitu API-rajapintasopimus muutetaan johdonmukaiseksi ja ylläpidettäväksi API-koodipohjaksi vakiokirjastojen, uudelleenkäytettävien mallien ja yhteensovitettujen kehitystyönkulkujen avulla.",
+  "resource.api-development-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-kehityksen parhaat käytännöt tarkoituksesta ja käytöstä",
+  "resource.api-development-best-practices.steps": "Sovella näitä käytäntöjä validoituun API-rajapintasopimukseen ja toteutussuunnitelmaan ennen koodaamisen aloittamista.",
   "resource.api-development-best-practices.tips": "Mukauta API-kehityksen parhaat käytännöt omaan kontekstiisi sopiviksi",
   "resource.api-metrics-and-analytics.title": "API-mittarit ja analytiikka",
   "resource.api-metrics-and-analytics.description": "Resurssi API-suorituskyvyn ja käyttötietojen määrittelyyn, keräämiseen ja analysointiin, jotta tekniset KPI:t voidaan sovittaa yhteen liiketoiminnan tulosten kanssa.",
-  "resource.api-metrics-and-analytics.outcomes": "Parempi ymmärrys API-mittareista ja analytiikan periaatteista.",
+  "resource.api-metrics-and-analytics.outcomes": "Yhteinen ymmärrys resurssin API-mittarit ja analytiikka tarkoituksesta ja käytöstä",
   "resource.api-metrics-and-analytics.steps": "Määritä keskeiset suorituskykyindikaattorit (KPI), joilla mitataan APIn onnistumista suhteessa liiketoiminnan tavoitteisiin.",
-  "resource.api-metrics-and-analytics.tips": "Mukauta API-mittareita ja analytiikkaa omaan kontekstiisi.",
+  "resource.api-metrics-and-analytics.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-onboarding-best-practices.title": "API-käyttöönoton parhaat käytännöt",
   "resource.api-onboarding-best-practices.description": "Parhaat käytännöt API-asiakkaiden käyttöönoton sujuvoittamiseksi vaiheittaisella rekisteröinnillä, tutustumisella ja ensisoitto-opastuksella.",
-  "resource.api-onboarding-best-practices.outcomes": "Parempi ymmärrys API-käyttöönoton parhaiden käytäntöjen periaatteista.",
+  "resource.api-onboarding-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-käyttöönoton parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.api-onboarding-best-practices.steps": "Määrittele API-hyödyntäjän matka löytämisestä vianmääritykseen ja tunnista keskeiset kosketuspisteet ja kipupisteet.",
-  "resource.api-onboarding-best-practices.tips": "Mukauta API Onboarding Best Practices -käytännöt omaan kontekstiisi.",
+  "resource.api-onboarding-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-portfolio-management-guidelines.title": "API-portfolion hallinnan suuntaviivat",
   "resource.api-portfolio-management-guidelines.description": "Opas organisaation API-sarjan strategiseen hallintaan - APIen priorisointiin, resurssien jakamiseen ja suorituskyvyn seurantaan koko elinkaaren ajan.",
-  "resource.api-portfolio-management-guidelines.outcomes": "API-salkunhallinnan suuntaviivojen periaatteiden parempi ymmärtäminen",
+  "resource.api-portfolio-management-guidelines.outcomes": "Yhteinen ymmärrys resurssin API-portfolion hallinnan suuntaviivat tarkoituksesta ja käytöstä",
   "resource.api-portfolio-management-guidelines.steps": "Määrittele salkunhallintakäytännöt, joissa hahmotellaan API-salkun hallinnointiprosessit, mukaan lukien priorisointi, seuranta ja optimointi.",
-  "resource.api-portfolio-management-guidelines.tips": "Mukauta API-salkunhallintaohjeet omaan kontekstiisi sopiviksi",
+  "resource.api-portfolio-management-guidelines.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-security-best-practices.title": "API-turvallisuuden parhaat käytännöt",
   "resource.api-security-best-practices.description": "Joukko toimivia valvontatoimia rajapintojen suojaamiseksi, mukaan lukien todennus, valtuutus, salaus, nopeuden rajoittaminen ja putkitason vaatimustenmukaisuustarkastukset.",
-  "resource.api-security-best-practices.outcomes": "API-turvan parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
+  "resource.api-security-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-turvallisuuden parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.api-security-best-practices.steps": "Varmista, että rajapinnat täyttävät turvallisuus- ja vaatimustenmukaisuusvaatimukset automaattisten tarkastusten ja auditointien avulla.",
-  "resource.api-security-best-practices.tips": "Mukauta API Security Best Practices -käytännöt omaan kontekstiisi.",
+  "resource.api-security-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-team-structure-guidelines.title": "API-tiimin rakennetta koskevat ohjeet",
   "resource.api-team-structure-guidelines.description": "Organisatoriset ohjeet roolien ja vastuualueiden määrittelemiseksi API-tiimeissä selkeyden, yhteistyön ja vastuuvelvollisuuden varmistamiseksi.",
-  "resource.api-team-structure-guidelines.outcomes": "API-tiimin rakenteen suuntaviivojen periaatteiden parempi ymmärtäminen",
+  "resource.api-team-structure-guidelines.outcomes": "Yhteinen ymmärrys resurssin API-tiimin rakennetta koskevat ohjeet tarkoituksesta ja käytöstä",
   "resource.api-team-structure-guidelines.steps": "Määrittele API-tiimien tiimirakenteet ja roolit, mukaan lukien API-tuotteen omistajat, kehittäjät, arkkitehdit ja toiminnot.",
-  "resource.api-team-structure-guidelines.tips": "Mukauta API-tiimirakenneohjeet omaan kontekstiisi sopiviksi",
+  "resource.api-team-structure-guidelines.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-testing-best-practices.title": "API-testauksen parhaat käytännöt",
   "resource.api-testing-best-practices.description": "Ohjeet automatisoidun toiminnallisen, suorituskyky- ja tietoturvatestauksen toteuttamiseksi koko rajapinnan elinkaaren ajan.",
-  "resource.api-testing-best-practices.outcomes": "Parempi ymmärrys API-testauksen parhaiden käytäntöjen periaatteista",
+  "resource.api-testing-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-testauksen parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.api-testing-best-practices.steps": "Testaa rajapintojen toimivuutta, turvallisuutta ja suorituskykyä automaattisten testausvälineiden avulla.",
-  "resource.api-testing-best-practices.tips": "Mukauta API-testauksen parhaat käytännöt omaan kontekstiisi sopiviksi",
+  "resource.api-testing-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-training-programs.title": "API-koulutusohjelmat",
   "resource.api-training-programs.description": "Etenemissuunnitelma tiimien pätevöittämistä varten, jossa on jäsenneltyjä oppimispolkuja API-designin, hallinnan, suorituskyvyn ja tietoturvan alalla.",
-  "resource.api-training-programs.outcomes": "API-koulutusohjelmien periaatteiden parempi ymmärtäminen",
+  "resource.api-training-programs.outcomes": "Yhteinen ymmärrys resurssin API-koulutusohjelmat tarkoituksesta ja käytöstä",
   "resource.api-training-programs.steps": "Tunnistetaan keskeiset API-taidot ja -tiedot, joita on kehitettävä, kuten API-design, tietoturva ja suorituskyky.",
-  "resource.api-training-programs.tips": "Mukauta API-koulutusohjelmat omaan kontekstiisi sopiviksi",
+  "resource.api-training-programs.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-versioning-best-practices.title": "API-versionoinnin parhaat käytännöt",
   "resource.api-versioning-best-practices.description": "Strategiat API-versioiden käyttöönottoa, ylläpitoa ja käytöstä poistamista varten siten, että taaksepäin yhteensopivuus ja hyödyntäjien luottamus säilyvät.",
-  "resource.api-versioning-best-practices.outcomes": "Parempi ymmärrys API-versionoinnin parhaiden käytäntöjen periaatteista",
+  "resource.api-versioning-best-practices.outcomes": "Yhteinen ymmärrys resurssin API-versionoinnin parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.api-versioning-best-practices.steps": "Määrittele rajapintojen versiointistrategiat muutosten hallitsemiseksi ja taaksepäin yhteensopivuuden varmistamiseksi.",
-  "resource.api-versioning-best-practices.tips": "Mukauta API Versioning Best Practices -käytännöt omaan kontekstiisi",
+  "resource.api-versioning-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD rajapinnoille",
   "resource.apiops-CI-CD-for-apis.description": "Käyttöönotto-ohjeet, jotka integroivat APIn elinkaaren tehtävät - suunnittelun, testauksen ja hallinnan - jatkuvaan integrointiin ja toimitusputkiin.",
-  "resource.apiops-CI-CD-for-apis.outcomes": "Parempi ymmärrys CI/CD for APIs -periaatteista",
+  "resource.apiops-CI-CD-for-apis.outcomes": "Yhteinen ymmärrys resurssin APIOps CI/CD rajapinnoille tarkoituksesta ja käytöstä",
   "resource.apiops-CI-CD-for-apis.steps": "Käytä CI/CD-putkia rakentamis-, testaus- ja käyttöönottoprosessien automatisoimiseksi varmistaen johdonmukaisen laadun ja jäljitettävyyden.",
-  "resource.apiops-CI-CD-for-apis.tips": "Mukauta CI/CD for APIs -ohjelmistoa omaan kontekstiisi sopivaksi",
+  "resource.apiops-CI-CD-for-apis.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.competitor-analysis-template.title": "Kilpailija-analyysimalli",
   "resource.competitor-analysis-template.description": "Strukturoitu työlista, jonka avulla voit vertailla API-tarjouksiasi kilpailijoihin kartoittamalla vahvuudet, heikkoudet ja erottavia tekijöitä.",
-  "resource.competitor-analysis-template.outcomes": "Kilpailija-analyysin malliperiaatteiden parempi ymmärtäminen",
+  "resource.competitor-analysis-template.outcomes": "Yhteinen ymmärrys resurssin Kilpailija-analyysimalli tarkoituksesta ja käytöstä",
   "resource.competitor-analysis-template.steps": "Suorita kilpailija-analyysi tärkeimpien kilpailijoiden ja niiden API-tarjonnan tunnistamiseksi.",
-  "resource.competitor-analysis-template.tips": "Mukauta kilpailija-analyysimalli omalle kontekstiisi.",
+  "resource.competitor-analysis-template.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.contract-first-design.title": "Sopimuslähtöinen suunnittelu",
   "resource.contract-first-design.description": "Suuntaviiva, jossa kannatetaan API-lähestymistapaa, jossa käytetään virallisia sopimuksia (esim. OpenAPI) sidosryhmien yhdenmukaistamiseksi ennen kehitystä.",
-  "resource.contract-first-design.outcomes": "Parempi ymmärrys sopimuksen suunnitteluperiaatteista",
+  "resource.contract-first-design.outcomes": "Yhteinen ymmärrys resurssin Sopimuslähtöinen suunnittelu tarkoituksesta ja käytöstä",
   "resource.contract-first-design.steps": "Sovellat sopimuslähtöisiä tai suunnittelulähtöisiä lähestymistapoja varmistaaksesi, että API-sopimukset validoidaan ennen toteutusta.",
-  "resource.contract-first-design.tips": "Mukauta Sopimus ensin -suunnittelua kontekstiisi",
+  "resource.contract-first-design.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.cross-functional-collaboration-best-practices.title": "Toimialarajat ylittävän yhteistyön parhaat käytännöt",
   "resource.cross-functional-collaboration-best-practices.description": "Käytännöt, joilla helpotetaan viestintää ja yhdenmukaistamista liiketoiminta- ja tekniikkatiimien välillä API-rajapintoja suunniteltaessa tai toimitettaessa.",
-  "resource.cross-functional-collaboration-best-practices.outcomes": "Toimialojen välisen yhteistyön parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
+  "resource.cross-functional-collaboration-best-practices.outcomes": "Yhteinen ymmärrys resurssin Toimialarajat ylittävän yhteistyön parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.cross-functional-collaboration-best-practices.steps": "Kannustaa API-tiimien, liiketoimintayksiköiden ja sidosryhmien välistä monialaista yhteistyötä, jotta API-aloitteet voidaan sovittaa yhteen liiketoiminnan tavoitteiden kanssa.",
-  "resource.cross-functional-collaboration-best-practices.tips": "Räätälöi monialaisen yhteistyön parhaat käytännöt omaan kontekstiisi.",
+  "resource.cross-functional-collaboration-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.data-privacy-guidelines.title": "Tietosuojaa koskevat ohjeet",
   "resource.data-privacy-guidelines.description": "Suunnitteluun liittyvät näkökohdat, joilla varmistetaan, että rajapinnat täyttävät tietosuojasäännökset, kuten GDPR:n, anonymisoinnin ja pääsynvalvonnan avulla.",
-  "resource.data-privacy-guidelines.outcomes": "Tietosuojaa koskevien suuntaviivojen periaatteiden parempi ymmärtäminen",
+  "resource.data-privacy-guidelines.outcomes": "Yhteinen ymmärrys resurssin Tietosuojaa koskevat ohjeet tarkoituksesta ja käytöstä",
   "resource.data-privacy-guidelines.steps": "Varmista käyttäjien tietojen yksityisyys toteuttamalla tietosuojatoimenpiteitä, kuten anonymisointi ja käyttöoikeuksien valvonta.",
-  "resource.data-privacy-guidelines.tips": "Mukauta tietosuojaohjeet kontekstiisi",
+  "resource.data-privacy-guidelines.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.domain-canvas.title": "Toimialuekanvas",
   "resource.domain-canvas.description": "Mallinnustyökalu toimialueen keskeisten käsitteiden, entiteettien, suhteiden ja sääntöjen määrittelyyn, jotta kyvykkyydet, rajapinnat ja integraatiot pysyvät semanttisesti yhdenmukaisina.",
   "resource.domain-canvas.outcomes": "Parempi ymmärrys toimialueen mallinnuksesta",
@@ -86,52 +86,52 @@
   "resource.domain-canvas.tips": "Mukauta Toimialuekanvas omaan kontekstiisi",
   "resource.ecosystem-vision-template.title": "Ekosysteemivisiomalli",
   "resource.ecosystem-vision-template.description": "Strateginen suunnittelutyökalu API-ekosysteemin määrittelemiseksi, mukaan lukien kohdekumppanit, arvoketjut ja integrointimahdollisuudet.",
-  "resource.ecosystem-vision-template.outcomes": "Parempi ymmärrys ekosysteemivision malliperiaatteista",
+  "resource.ecosystem-vision-template.outcomes": "Yhteinen ymmärrys resurssin Ekosysteemivisiomalli tarkoituksesta ja käytöstä",
   "resource.ecosystem-vision-template.steps": "Markkinatutkimuksen tekeminen API-toimialalla vallitsevien suuntausten, mahdollisuuksien ja uhkien tunnistamiseksi.",
-  "resource.ecosystem-vision-template.tips": "Mukauta Ecosystem Vision Template -mallia omaan kontekstiisi.",
+  "resource.ecosystem-vision-template.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.industry-standards-and-best-practices.title": "Alan standardit ja parhaat käytännöt",
   "resource.industry-standards-and-best-practices.description": "Viiteresurssi API-designin ja -toiminnan mukauttamiseksi laajalti tunnustettuihin alan kehyksiin ja eritelmiin.",
-  "resource.industry-standards-and-best-practices.outcomes": "alan standardien ja parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
+  "resource.industry-standards-and-best-practices.outcomes": "Yhteinen ymmärrys resurssin Alan standardit ja parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.industry-standards-and-best-practices.steps": "Tunnistetaan alan standardit ja parhaat käytännöt, jotta voidaan varmistaa, että rajapinnat ovat kilpailukykyisiä ja yhteensopivia.",
-  "resource.industry-standards-and-best-practices.tips": "Mukauta toimialan standardit ja parhaat käytännöt omaan kontekstiisi.",
+  "resource.industry-standards-and-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.partner-integration-guidelines.title": "Kumppanien integrointiohjeet",
   "resource.partner-integration-guidelines.description": "Integroinnin tarkistuslistat ja viestintämallit kolmannen osapuolen API-suhteiden teknisten ja oikeudellisten näkökohtien hallintaan.",
-  "resource.partner-integration-guidelines.outcomes": "Parempi ymmärrys kumppanien integroinnin suuntaviivojen periaatteista",
+  "resource.partner-integration-guidelines.outcomes": "Yhteinen ymmärrys resurssin Kumppanien integrointiohjeet tarkoituksesta ja käytöstä",
   "resource.partner-integration-guidelines.steps": "Luodaan integraatioprosessit ja -ohjeet yhteistyökumppaneiden kanssa tehtävää yhteistyötä varten, mukaan lukien tekninen integraatio, tietojen jakaminen ja tuki.",
-  "resource.partner-integration-guidelines.tips": "Mukauta kumppanien integrointiohjeet omaan kontekstiisi",
+  "resource.partner-integration-guidelines.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.role-communication-best-practices.title": "Rooliviestinnän parhaat käytännöt",
   "resource.role-communication-best-practices.description": "Työkalut, joilla määritetään ja kuvataan API-aloitteiden vastuut sekä varmistetaan selkeä työnjako ja vastuuvelvollisuus.",
-  "resource.role-communication-best-practices.outcomes": "rooliviestinnän parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
+  "resource.role-communication-best-practices.outcomes": "Yhteinen ymmärrys resurssin Rooliviestinnän parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.role-communication-best-practices.steps": "Määritä selkeät vastuualueet kullekin roolille, mukaan lukien API-design, kehittäminen, testaus ja toiminta.",
-  "resource.role-communication-best-practices.tips": "Mukauta rooliviestinnän parhaat käytännöt omaan kontekstiisi.",
+  "resource.role-communication-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.scalable-infrastructure-best-practices.title": "Skaalautuvan infrastruktuurin parhaat käytännöt",
   "resource.scalable-infrastructure-best-practices.description": "Arkkitehtuuriohjeet sen varmistamiseksi, että rajapinnat otetaan käyttöön infrastruktuurissa, joka pystyy käsittelemään joustavasti käyttöpiikkejä ja -kasvua.",
-  "resource.scalable-infrastructure-best-practices.outcomes": "Parempi ymmärrys skaalautuvan infrastruktuurin parhaiden käytäntöjen periaatteista.",
+  "resource.scalable-infrastructure-best-practices.outcomes": "Yhteinen ymmärrys resurssin Skaalautuvan infrastruktuurin parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.scalable-infrastructure-best-practices.steps": "Suunnittele API-infrastruktuuri skaalautuvaksi ja joustavaksi käyttäen pilvipohjaisia malleja ja teknologioita.",
-  "resource.scalable-infrastructure-best-practices.tips": "Mukauta skaalautuvan infrastruktuurin parhaat käytännöt omaan kontekstiisi.",
+  "resource.scalable-infrastructure-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.service-agreement-template.title": "Palvelusopimusmalli",
   "resource.service-agreement-template.description": "Mukautettava sopimusmuoto, jossa määritellään odotukset, SLA:t, vastuut ja käyttöoikeusehdot API-käyttöä varten.",
-  "resource.service-agreement-template.outcomes": "Palvelusopimusmallin periaatteiden parempi ymmärtäminen",
+  "resource.service-agreement-template.outcomes": "Yhteinen ymmärrys resurssin Palvelusopimusmalli tarkoituksesta ja käytöstä",
   "resource.service-agreement-template.steps": "Määrittele palvelusopimukset, joissa hahmotellaan odotukset, palvelutasot ja vastuualueet kutakin rajapintaa varten.",
-  "resource.service-agreement-template.tips": "Mukauta palvelusopimusmalli omalle kontekstiisi.",
+  "resource.service-agreement-template.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.stakeholder-engagement-best-practices.title": "Sidosryhmien sitouttamisen parhaat käytännöt",
   "resource.stakeholder-engagement-best-practices.description": "sitouttamistaktiikat sisäisten ja ulkoisten sidosryhmien saattamiseksi yhteisten API-tavoitteiden, -arvon ja -hallinnan piiriin.",
-  "resource.stakeholder-engagement-best-practices.outcomes": "Sidosryhmien sitouttamisen parhaiden käytäntöjen periaatteiden parempi ymmärtäminen",
+  "resource.stakeholder-engagement-best-practices.outcomes": "Yhteinen ymmärrys resurssin Sidosryhmien sitouttamisen parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.stakeholder-engagement-best-practices.steps": "Sidosryhmien sitouttaminen varmistamaan API-aloitteiden yhdenmukaisuus ja tuki.",
-  "resource.stakeholder-engagement-best-practices.tips": "Mukauta sidosryhmien sitouttamisen parhaat käytännöt omaan kontekstiisi.",
+  "resource.stakeholder-engagement-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.test-automation-frameworks.title": "Testausautomaation kehykset",
   "resource.test-automation-frameworks.description": "Suositellut työkalut ja mallit API-rajapintasopimus-, regressio- ja integrointitestauksen automatisointiin eri ympäristöissä.",
-  "resource.test-automation-frameworks.outcomes": "Parempi ymmärrys testiautomaatiokehysten periaatteista.",
+  "resource.test-automation-frameworks.outcomes": "Yhteinen ymmärrys resurssin Testausautomaation kehykset tarkoituksesta ja käytöstä",
   "resource.test-automation-frameworks.steps": "Toteuta testiautomaatiokehykset, jotka tukevat sopimustestausta, integrointitestausta ja päästä päähän -testausta.",
-  "resource.test-automation-frameworks.tips": "Mukauta testausautomaatiokehykset omaan kontekstiisi sopiviksi.",
+  "resource.test-automation-frameworks.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.vendor-management-best-practices.title": "Toimittajien hallinnan parhaat käytännöt",
   "resource.vendor-management-best-practices.description": "Kehys ulkoisten API-toimittajien ja kolmansien osapuolten integraatioiden arviointia ja hallintaa varten riskien, suorituskyvyn ja vaatimustenmukaisuuden perusteella.",
-  "resource.vendor-management-best-practices.outcomes": "Parempi ymmärrys toimittajahallinnan parhaiden käytäntöjen periaatteista",
+  "resource.vendor-management-best-practices.outcomes": "Yhteinen ymmärrys resurssin Toimittajien hallinnan parhaat käytännöt tarkoituksesta ja käytöstä",
   "resource.vendor-management-best-practices.steps": "Ota käyttöön toimittajagovernance-prosessit kolmansien osapuolten API-toimittajien arviointia, käyttöönottoa ja seurantaa varten.",
-  "resource.vendor-management-best-practices.tips": "Mukauta toimittajahallinnan parhaat käytännöt omaan kontekstiisi.",
+  "resource.vendor-management-best-practices.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-audit-checklist.title": "API-auditoinnin tarkistuslista",
   "resource.api-audit-checklist.description": "Elinkaaripohjainen tarkistuslista, jolla varmistetaan APIn valmius suunnittelun, toimituksen, julkaisun ja vaatimustenmukaisuuden osalta määriteltyjen auditointikriteerien ja todisteiden avulla.",
-  "resource.api-audit-checklist.outcomes": "Parempi ymmärrys API-auditoinnin tarkistuslistan periaatteista",
+  "resource.api-audit-checklist.outcomes": "Yhteinen ymmärrys resurssin API-auditoinnin tarkistuslista tarkoituksesta ja käytöstä",
   "resource.api-audit-checklist.steps": "Varmista API-auditoinnin tarkistuslistan avulla, että API-design täyttää toiminnalliset ja muut kuin toiminnalliset vaatimukset, mukaan lukien tietoturva, suorituskyky ja vaatimustenmukaisuus.",
   "resource.api-audit-checklist.tips": "Jokainen auditointikohta yhdistää elinkaaren työvaiheet (asemat), ohjaavat ohjeet ja tukevat todisteet, jotta APIn valmiudesta saadaan selkeä kuva.",
   "resource.api-business-model-canvas.title": "API-liiketoimintamallikanvas",
@@ -139,34 +139,34 @@
   "resource.api-business-model-canvas.outcomes": "Selkeä liiketoimintastrategia rajapintoja varten",
   "resource.api-business-model-canvas.steps": "Tiivistä APIn arvolupauksen tiivistelmä",
   "resource.api-business-model-canvas.tips": "Aloita yhdestä rajapinnasta selkeyden varmistamiseksi",
-  "resource.api-design-principles.title": "APIn suunnitteluperiaatteet",
+  "resource.api-design-principles.title": "API-suunnitteluperiaatteet",
   "resource.api-design-principles.description": "Tiivis opas APIn käytettävyyteen, löydettävyyteen ja johdonmukaisuuteen, joka perustuu yhteisiin suunnittelusääntöihin ja todellisiin hyödyntäjien tarpeisiin.",
-  "resource.api-design-principles.outcomes": "API-designin periaatteiden parempi ymmärtäminen",
+  "resource.api-design-principles.outcomes": "Yhteinen ymmärrys resurssin APIn suunnitteluperiaatteet tarkoituksesta ja käytöstä",
   "resource.api-design-principles.steps": "**Hyödyntäjä ensin -suunnittelu:** Aloita jokainen APIOps-sykli keräämällä käyttäjien tavoitteet ja toimialan ehdot, jotta APIt ratkaisevat todellisia ongelmia.",
-  "resource.api-design-principles.tips": "Mukauta API-designperiaatteet omaan kontekstiisi sopiviksi",
+  "resource.api-design-principles.tips": "Mukauta resurssi omaan toimintaympäristöösi.",
   "resource.api-value-proposition-canvas.title": "API-arvolupauskanvas",
   "resource.api-value-proposition-canvas.description": "Kohdista API-ominaisuudet käyttäjien tarpeisiin kartoittamalla tehtävät, ongelmat ja hyödyt API-tuotteisiin.",
   "resource.api-value-proposition-canvas.outcomes": "Keskitetty ominaisuuksien kehittäminen",
   "resource.api-value-proposition-canvas.steps": "Listaa käyttäjäpolun tehtävät.",
   "resource.api-value-proposition-canvas.tips": "Hyödynnä Asiakaspolkukanvasin tietoja",
   "resource.business-impact-canvas.title": "Liiketoimintavaikutuskanvas",
-  "resource.business-impact-canvas.description": "Suunnittele skaalautuva ja turvallinen API-alusta-arkkitehtuuri, joka täyttää liiketoiminnan ja tekniset vaatimukset.",
-  "resource.business-impact-canvas.outcomes": "Skaalautuva API-infrastruktuuri",
+  "resource.business-impact-canvas.description": "Tunnista liiketoimintaan, saatavuuteen, tietoturvaan, dataan, vaatimustenmukaisuuteen ja operointiin liittyvät riskit, joiden tulee ohjata arkkitehtuuri- ja alustapäätöksiä.",
+  "resource.business-impact-canvas.outcomes": "Dokumentoitu arvio liiketoiminta- ja operatiivisista vaikutuksista",
   "resource.business-impact-canvas.steps": "Saatavuusriskit: Tunnista riskit ja vaikutukset.",
-  "resource.business-impact-canvas.tips": "Otetaan arkkitehdit ja rakennuttajat mukaan suunnitteluprosessiin.",
+  "resource.business-impact-canvas.tips": "Täytä tämä ennen toteutustavan valintaa tai vahvistamista.",
   "resource.capacity-canvas.title": "Kapasiteettikanvas",
-  "resource.capacity-canvas.description": "Suunnittele API-kapasiteetti vastaamaan nykyisiä ja tulevia liiketoiminnan vaatimuksia ja varmista skaalautuvuus ja suorituskyky.",
-  "resource.capacity-canvas.outcomes": "API-kapasiteetin mukauttaminen liiketoiminnan volyymiin",
+  "resource.capacity-canvas.description": "Suunnittele kapasiteetti nykyistä ja tulevaa kysyntää varten. Huomioi volyymit, kuormitushuiput, viive, saatavuus, skaalaus, välimuistit ja kutsurajoitukset valitulle kyvykkyydelle ja toteutustavalle.",
+  "resource.capacity-canvas.outcomes": "Liiketoiminnan odotettuun kysyntään sovitetut kapasiteettivaatimukset",
   "resource.capacity-canvas.steps": "Dokumentoi nykyiset liiketoiminnan volyymit",
-  "resource.capacity-canvas.tips": "Käytä analytiikkaa kasvusuuntausten ennustamiseen",
+  "resource.capacity-canvas.tips": "Täytä tämä ennen arkkitehtuuri- ja alustapäätösten viimeistelyä.",
   "resource.customer-journey-canvas.title": "Asiakaspolkukanvas",
   "resource.customer-journey-canvas.description": "Kartoittaa asiakkaan tai käyttäjän polun tarpeiden ja kipupisteiden tunnistamiseksi, jotta kyvykkyyden ja rajapinnan suunnittelu perustuu todelliseen kontekstiin.",
-  "resource.customer-journey-canvas.outcomes": "Parempi asiakasymmärrys",
+  "resource.customer-journey-canvas.outcomes": "Yhteinen ymmärrys asiakkaan, kumppanin tai hyödyntäjän polusta",
   "resource.customer-journey-canvas.steps": "Määrittele asiakaspersoona",
-  "resource.customer-journey-canvas.tips": "Toista vaiheet tiimin panoksen avulla vaiheiden tarkentamiseksi.",
+  "resource.customer-journey-canvas.tips": "Validoi polku niiden ihmisten kanssa, jotka toteuttavat sen tai kokevat sen.",
   "resource.event-canvas.title": "Tapahtumakanvas",
-  "resource.event-canvas.description": "Suunnittele tapahtumapohjaisia rajapintoja ja kyvykkyyksiä määrittelemällä tapahtumat, laukaisijat ja käsittelylogiikka.",
-  "resource.event-canvas.outcomes": "Määritelty tapahtumapohjainen arkkitehtuuri",
+  "resource.event-canvas.description": "Suunnittele tapahtumapohjaiset rajapinnat ja integraatiot määrittelemällä tapahtumat, laukaisimet, skeemat, tuottajat, hyödyntäjät ja käsittelylogiikka.",
+  "resource.event-canvas.outcomes": "Määritelty tapahtumapohjainen vuorovaikutusmalli",
   "resource.event-canvas.steps": "Järjestelmän keskeisten tapahtumien tunnistaminen",
   "resource.event-canvas.tips": "Tapahtumaskeemojen käyttäminen tapahtumamuotojen standardoimiseksi",
   "resource.graphql-canvas.title": "GraphQL-kanvas",
@@ -176,12 +176,12 @@
   "resource.graphql-canvas.tips": "Käytä introspektiota tyyppimääritysten validointiin",
   "resource.interaction-canvas.title": "Vuorovaikutuskanvas",
   "resource.interaction-canvas.description": "Määrittele API-vuorovaikutukset, työnkulut ja odotetut vastaukset, jotta varmistetaan yhdenmukainen API-kokemus.",
-  "resource.interaction-canvas.outcomes": "Selkeät API-vuorovaikutuksen työnkulut",
+  "resource.interaction-canvas.outcomes": "Valitun kyvykkyyden määritelty vuorovaikutusmalli",
   "resource.interaction-canvas.steps": "Kartoita rajapinnan vuorovaikutukset käyttäjän tehtäviin.",
   "resource.interaction-canvas.tips": "Aloita yleisistä käyttötapauksista ennen ääritapausten käsittelyä",
   "resource.location-canvas.title": "Sijaintikanvas",
   "resource.location-canvas.description": "Kartoita API-palveluntarjoajien ja -hyödyntäjien sijainnit vaatimustenmukaisuuden ja suorituskyvyn varmistamiseksi eri alueilla.",
-  "resource.location-canvas.outcomes": "Paikallisten säännösten noudattaminen",
+  "resource.location-canvas.outcomes": "Dokumentoidut sijainti-, tiedon sijainti-, verkko- ja sääntelyvaatimukset",
   "resource.location-canvas.steps": "API-palveluntarjoajien sijainnit kartalla.",
   "resource.location-canvas.tips": "Yhteistyö oikeudellisten ja sääntöjen noudattamista käsittelevien tiimien kanssa",
   "resource.rest-canvas.title": "REST-kanvas",
@@ -189,125 +189,125 @@
   "resource.rest-canvas.outcomes": "Johdonmukainen RESTful API-design",
   "resource.rest-canvas.steps": "Tunnista APIn tarjoamat keskeiset resurssit",
   "resource.rest-canvas.tips": "Käytä tavallisia HTTP-menetelmiä (GET, POST, PUT, DELETE).",
-  "resource.api-community-engagement-strategies.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään API-yhteisön sitouttamisstrategioita",
-  "resource.api-community-engagement-strategies.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-community-engagement-strategies.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-yhteisön sitouttamisstrategiat",
+  "resource.api-community-engagement-strategies.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-community-engagement-strategies.steps.1": "Luo myynninedistämismateriaalia (esim. tapaustutkimuksia, menestystarinoita), jossa korostetaan rajapintojen arvoa ja hyötyjä.",
   "resource.api-community-engagement-strategies.steps.2": "Luo opetusmateriaalia (esim. opetusohjelmia, dokumentaatiota), jossa selitetään APIn ominaisuuksia, hyötyjä ja käyttötapoja.",
   "resource.api-community-engagement-strategies.steps.3": "Kytkeydy API-käyttäjiin palautekierrosten, tukikanavien ja yhteisöfoorumien kautta ymmärtämään heidän tarpeitaan ja parantamaan APIn käyttöönottoa.",
   "resource.api-community-engagement-strategies.steps.4": "Analysoi APIn käyttömittareita ja ota käyttäjien palaute huomioon API-iteraatioissa.",
-  "resource.api-community-engagement-strategies.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-compliance-best-practices.outcomes.1": "Standardoitu lähestymistapa API Compliance Best Practices -käytäntöjen avulla",
-  "resource.api-compliance-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-community-engagement-strategies.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-compliance-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-vaatimustenmukaisuuden parhaat käytännöt",
+  "resource.api-compliance-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-compliance-best-practices.steps.1": "Toteuta toimenpiteitä, joilla varmistetaan, että rajapinnat täyttävät nämä vaatimukset, mukaan lukien tietojen salaus, käyttöoikeuksien valvonta ja kirjausketjut.",
   "resource.api-compliance-best-practices.steps.2": "Käytä tarkistuslistoja, linereita ja testausvälineitä varmistaaksesi johdonmukaisuuden ja standardien noudattamisen.",
-  "resource.api-compliance-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-development-best-practices.outcomes.1": "Standardoitu lähestymistapa API-kehityksen parhaiden käytäntöjen avulla",
-  "resource.api-development-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-compliance-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-development-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-kehityksen parhaat käytännöt",
+  "resource.api-development-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-development-best-practices.steps.1": "Käytä vakiintuneita ohjelmistokehyksiä, kirjastoja ja koodausstandardeja sopimuksen johdonmukaiseen ja ylläpidettävään toteutukseen.",
-  "resource.api-development-best-practices.tips.1": "Käytä tätä resurssia toteutuksen ohjeistuksena ja tarkastelun näkökulmana pikemminkin kuin pakollisena erillisenä artefaktina",
-  "resource.api-metrics-and-analytics.outcomes.1": "Standardoitu lähestymistapa API Metrics And Analyticsin avulla",
-  "resource.api-metrics-and-analytics.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-development-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-metrics-and-analytics.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-mittarit ja analytiikka",
+  "resource.api-metrics-and-analytics.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-metrics-and-analytics.steps.1": "Määrittele ja seuraa suorituskykymittareita (esim. API-kutsut, viiveet, virhetasot) ja hyväksyntämittareita (esim. NPS).",
   "resource.api-metrics-and-analytics.steps.2": "Seuraa API-aloitteita varmistaaksesi toimintaohjeiden ja governance-käytäntöjen noudattamisen.",
-  "resource.api-metrics-and-analytics.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-onboarding-best-practices.outcomes.1": "Standardoitu lähestymistapa API Onboarding Best Practices -käytäntöjen avulla",
-  "resource.api-onboarding-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-metrics-and-analytics.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-onboarding-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-käyttöönoton parhaat käytännöt",
+  "resource.api-onboarding-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-onboarding-best-practices.steps.1": "Kehitä käyttöönottoprosesseja ja resursseja, joiden avulla API-hyödyntäjät ymmärtävät, miten API-rajapintoja käytetään tehokkaasti.",
   "resource.api-onboarding-best-practices.steps.2": "Dokumentoi, miten hyödyntäjät löytävät ja käyttävät rajapintaä, mukaan lukien käyttöönottoprosessit ja rekisteröinti.",
-  "resource.api-onboarding-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Standardoitu lähestymistapa API-salkunhallintaohjeiden avulla",
-  "resource.api-portfolio-management-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-onboarding-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-portfolion hallinnan suuntaviivat",
+  "resource.api-portfolio-management-guidelines.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-portfolio-management-guidelines.steps.1": "Määrittele budjetti- ja resurssienhallintakäytännöt, joissa hahmotellaan API-aloitteiden budjettien ja resurssien hallinnointiprosessit.",
   "resource.api-portfolio-management-guidelines.steps.2": "Laaditaan kriteerit budjettimäärärahojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden mukaisuuden perusteella.",
   "resource.api-portfolio-management-guidelines.steps.3": "Seuraa API-portfoliota varmistaaksesi, että APIt tuottavat arvoa, täyttävät suorituskykyodotukset ja ovat linjassa liiketoiminnan tavoitteiden kanssa.",
-  "resource.api-portfolio-management-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-security-best-practices.outcomes.1": "Standardoitu lähestymistapa API-turvallisuuden parhaiden käytäntöjen avulla",
-  "resource.api-security-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-portfolio-management-guidelines.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-security-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-turvallisuuden parhaat käytännöt",
+  "resource.api-security-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-security-best-practices.steps.1": "Toteuta turvatoimia, kuten todennus, valtuutus, salaus ja nopeuden rajoittaminen, suojaamaan rajapintoja uhkilta.",
   "resource.api-security-best-practices.steps.2": "Toteuta automaattiset tietoturvatarkastukset ja vaatimustenmukaisuuden validoinnit CI/CD-putkessa varmistaaksesi, että rajapinnat ovat turvallisia ja vaatimustenmukaisia.",
-  "resource.api-security-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-team-structure-guidelines.outcomes.1": "Standardoitu lähestymistapa API-tiimirakenneohjeiden avulla",
-  "resource.api-team-structure-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-team-structure-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-testing-best-practices.outcomes.1": "Standardoitu lähestymistapa API-testauksen parhaiden käytäntöjen avulla",
-  "resource.api-testing-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-security-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-team-structure-guidelines.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-tiimin rakennetta koskevat ohjeet",
+  "resource.api-team-structure-guidelines.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.api-team-structure-guidelines.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-testing-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-testauksen parhaat käytännöt",
+  "resource.api-testing-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-testing-best-practices.steps.1": "Integroi toiminnallinen ja ei-toiminnallinen testaus CI/CD-putkeen varmistaaksesi, että rajapinnat täyttävät laatuvaatimukset.",
   "resource.api-testing-best-practices.steps.2": "Käytä automatisoituja testausvälineitä API-toiminnallisuuden, tietoturvan ja suorituskyvyn validointiin.",
-  "resource.api-testing-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-training-programs.outcomes.1": "Standardoitu lähestymistapa API-koulutusohjelmien avulla",
-  "resource.api-training-programs.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-testing-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-training-programs.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-koulutusohjelmat",
+  "resource.api-training-programs.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-training-programs.steps.1": "Kannustetaan jatkuvaan oppimiseen verkkokurssien, sertifikaattien ja yhteisöllisen sitoutumisen avulla.",
   "resource.api-training-programs.steps.2": "Tarjota koulutusta ja resursseja, jotta tiimit voivat omaksua API-first-ajattelutavan ja ymmärtää APIen edut.",
   "resource.api-training-programs.steps.3": "Tarjota koulutusohjelmia, työpajoja ja resursseja, joiden avulla tiimit voivat parantaa API-taitojaan ja -tietämystään.",
-  "resource.api-training-programs.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-versioning-best-practices.outcomes.1": "Standardoitu lähestymistapa API-versionoinnin parhaiden käytäntöjen avulla",
-  "resource.api-versioning-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.api-versioning-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.apiops-CI-CD-for-apis.outcomes.1": "CI/CD:tä käyttävä standardoitu lähestymistapa API-rajapintoihin",
-  "resource.apiops-CI-CD-for-apis.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-training-programs.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-versioning-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-versionoinnin parhaat käytännöt",
+  "resource.api-versioning-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.api-versioning-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.apiops-CI-CD-for-apis.outcomes.1": "Johdonmukainen tapa soveltaa resurssia APIOps CI/CD rajapinnoille",
+  "resource.apiops-CI-CD-for-apis.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.apiops-CI-CD-for-apis.steps.1": "Integroi automatisoidut testit CI/CD-putkeen API-laadun jatkuvan validoinnin varmistamiseksi.",
   "resource.apiops-CI-CD-for-apis.steps.2": "Ota käyttöön käyttöönottostrategioita (esim. sinivihreät käyttöönotot, kanarian julkaisut) API-julkaisuihin liittyvien riskien minimoimiseksi.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Ota tavaksi tarkastella mittareita ja suunnitella jatkuvan parantamisen toimia.",
-  "resource.apiops-CI-CD-for-apis.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.competitor-analysis-template.outcomes.1": "Vakioitu lähestymistapa käyttäen kilpailija-analyysimallia",
-  "resource.competitor-analysis-template.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.apiops-CI-CD-for-apis.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.competitor-analysis-template.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Kilpailija-analyysimalli",
+  "resource.competitor-analysis-template.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.competitor-analysis-template.steps.1": "Analysoi kilpailijoiden rajapinnat ymmärtämään niiden vahvuudet, heikkoudet ja ainutlaatuiset myyntivaltit.",
-  "resource.competitor-analysis-template.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.contract-first-design.outcomes.1": "Vakioitu lähestymistapa, jossa käytetään sopimusperusteista suunnittelua (Contract First Design)",
-  "resource.contract-first-design.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.competitor-analysis-template.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.contract-first-design.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Sopimuslähtöinen suunnittelu",
+  "resource.contract-first-design.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.contract-first-design.steps.1": "Määrittele API-sopimukset, joissa hahmotellaan kunkin APIn odotukset, vastuut ja käyttöohjeet.",
   "resource.contract-first-design.steps.2": "Käytä standardoituja formaatteja (esim. OpenAPI, AsyncAPI) luodaksesi koneellisesti luettavia API-sopimuksia, joita on helppo jakaa ja validoida.",
-  "resource.contract-first-design.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään monitoimialaisen yhteistyön parhaita käytäntöjä.",
-  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.cross-functional-collaboration-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.data-privacy-guidelines.outcomes.1": "Standardoitu lähestymistapa tietosuojaa koskevien suuntaviivojen avulla",
-  "resource.data-privacy-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.data-privacy-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
+  "resource.contract-first-design.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Toimialarajat ylittävän yhteistyön parhaat käytännöt",
+  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.cross-functional-collaboration-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.data-privacy-guidelines.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Tietosuojaa koskevat ohjeet",
+  "resource.data-privacy-guidelines.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.data-privacy-guidelines.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
   "resource.domain-canvas.outcomes.1": "Vakioitu lähestymistapa Toimialuekanvasin avulla",
   "resource.domain-canvas.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
   "resource.domain-canvas.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.ecosystem-vision-template.outcomes.1": "Yhdenmukaistettu lähestymistapa ekosysteemivision mallin avulla",
-  "resource.ecosystem-vision-template.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.ecosystem-vision-template.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Ekosysteemivisiomalli",
+  "resource.ecosystem-vision-template.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.ecosystem-vision-template.steps.1": "Tunnistetaan tärkeimmät ekosysteemikumppanit ja sidosryhmät, jotka hyötyvät ekosysteemistä tai osallistuvat siihen.",
   "resource.ecosystem-vision-template.steps.2": "Tunnista markkinapuutteet, jotka rajapintasi voivat täyttää kilpailijoiden tarjonnan perusteella.",
   "resource.ecosystem-vision-template.steps.3": "Tunnista mahdolliset kumppanit, joiden APIt voivat parantaa API-valmiuksiasi ja arvolupaustasi.",
   "resource.ecosystem-vision-template.steps.4": "Kehitä erottautumisstrategia, jossa korostetaan sovellusrajapintojesi ainutlaatuisia ominaisuuksia ja etuja.",
   "resource.ecosystem-vision-template.steps.5": "Määrittele sovellusrajapintojesi ekosysteemivisio, mukaan lukien se, miten ne ovat vuorovaikutuksessa muiden järjestelmien ja alustojen kanssa.",
   "resource.ecosystem-vision-template.steps.6": "Suunnittele rajapinnat, jotka mahdollistavat saumattoman integroinnin ja yhteistyön ekosysteemissä.",
-  "resource.ecosystem-vision-template.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.industry-standards-and-best-practices.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään alan standardeja ja parhaita käytäntöjä.",
-  "resource.industry-standards-and-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.industry-standards-and-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.partner-integration-guidelines.outcomes.1": "Standardoitu lähestymistapa kumppanien integrointiohjeiden avulla",
-  "resource.partner-integration-guidelines.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.ecosystem-vision-template.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.industry-standards-and-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Alan standardit ja parhaat käytännöt",
+  "resource.industry-standards-and-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.industry-standards-and-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.partner-integration-guidelines.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Kumppanien integrointiohjeet",
+  "resource.partner-integration-guidelines.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.partner-integration-guidelines.steps.1": "Seuraa kumppaneiden API-suorituskykyä ja vaatimustenmukaisuutta varmistaaksesi luotettavuuden ja yhteensopivuuden API-strategiasi kanssa.",
-  "resource.partner-integration-guidelines.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.role-communication-best-practices.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään rooliviestinnän parhaita käytäntöjä",
-  "resource.role-communication-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.partner-integration-guidelines.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.role-communication-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Rooliviestinnän parhaat käytännöt",
+  "resource.role-communication-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.role-communication-best-practices.steps.1": "Varmistaa, että roolit ja vastuut on ilmoitettu kaikille tiimin jäsenille ja sidosryhmille, jotta varmistetaan yhdenmukaisuus.",
-  "resource.role-communication-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.scalable-infrastructure-best-practices.outcomes.1": "Standardoitu lähestymistapa, jossa käytetään skaalautuvan infrastruktuurin parhaita käytäntöjä.",
-  "resource.scalable-infrastructure-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.role-communication-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.scalable-infrastructure-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Skaalautuvan infrastruktuurin parhaat käytännöt",
+  "resource.scalable-infrastructure-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.scalable-infrastructure-best-practices.steps.1": "Seuraa infrastruktuurin suorituskykyä ja kapasiteettia sen varmistamiseksi, että se pystyy vastaamaan kasvavaan kysyntään.",
-  "resource.scalable-infrastructure-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.service-agreement-template.outcomes.1": "Standardoitu lähestymistapa palvelusopimusmallin avulla",
-  "resource.service-agreement-template.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.scalable-infrastructure-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.service-agreement-template.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Palvelusopimusmalli",
+  "resource.service-agreement-template.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.service-agreement-template.steps.1": "Luo koneellisesti luettavia palvelusopimuksia, joita on helppo jakaa ja validoida, käyttämällä standardoituja muotoja.",
   "resource.service-agreement-template.steps.2": "Varmista, että sidosryhmät tarkistavat ja hyväksyvät palvelusopimukset, jotta varmistetaan niiden yhdenmukaisuus ja selkeys.",
-  "resource.service-agreement-template.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.stakeholder-engagement-best-practices.outcomes.1": "Sidosryhmien sitouttamisen parhaita käytäntöjä hyödyntävä vakiomuotoinen lähestymistapa",
-  "resource.stakeholder-engagement-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.stakeholder-engagement-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.test-automation-frameworks.outcomes.1": "Standardoitu lähestymistapa testausautomaatiokehysten avulla",
-  "resource.test-automation-frameworks.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
-  "resource.test-automation-frameworks.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.vendor-management-best-practices.outcomes.1": "Myyjähallinnon parhaita käytäntöjä käyttävä standardoitu lähestymistapa",
-  "resource.vendor-management-best-practices.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.service-agreement-template.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.stakeholder-engagement-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Sidosryhmien sitouttamisen parhaat käytännöt",
+  "resource.stakeholder-engagement-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.stakeholder-engagement-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.test-automation-frameworks.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Testausautomaation kehykset",
+  "resource.test-automation-frameworks.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
+  "resource.test-automation-frameworks.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.vendor-management-best-practices.outcomes.1": "Johdonmukainen tapa soveltaa resurssia Toimittajien hallinnan parhaat käytännöt",
+  "resource.vendor-management-best-practices.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.vendor-management-best-practices.steps.1": "Määrittele kriteerit toimittajien rajapintojen arviointia varten, mukaan lukien luotettavuus, turvallisuus ja vaatimustenmukaisuus.",
-  "resource.vendor-management-best-practices.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
-  "resource.api-audit-checklist.outcomes.1": "Standardoitu lähestymistapa API-auditoinnin tarkistuslistan avulla",
-  "resource.api-audit-checklist.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.vendor-management-best-practices.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
+  "resource.api-audit-checklist.outcomes.1": "Johdonmukainen tapa soveltaa resurssia API-auditoinnin tarkistuslista",
+  "resource.api-audit-checklist.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-audit-checklist.steps.1": "Suorita auditointeja elinkaaren kattavuuden arvioimiseksi ja varmista, että API täyttää liiketoiminta-, suunnittelu- ja toimintastandardit.",
   "resource.api-audit-checklist.steps.2": "Varmista, että dokumentaatio, tietoturvamallit, gateway-konfiguraatio ja lakisääteiset vaatimukset on määritelty selkeästi, validoitu ja tuettu todisteilla.",
   "resource.api-audit-checklist.tips.1": "Käytä API-auditointilistaa yhteistyössä liiketoiminta- ja teknologia-roolien välillä",
@@ -321,13 +321,13 @@
   "resource.api-business-model-canvas.steps.6": "Korosta hyötyjä ja kustannuksia",
   "resource.api-business-model-canvas.tips.1": "Mahdollisuuksien priorisointi kustannus-hyöty -suhteen kaltaisten mittareiden avulla.",
   "resource.api-business-model-canvas.tips.2": "Validoi tuotokset tärkeimpien sidosryhmien kanssa",
-  "resource.api-design-principles.outcomes.1": "Standardoitu lähestymistapa API-designperiaatteiden avulla",
-  "resource.api-design-principles.outcomes.2": "Parannettu asiaan liittyvien API-käytäntöjen täytäntöönpano",
+  "resource.api-design-principles.outcomes.1": "Johdonmukainen tapa soveltaa resurssia APIn suunnitteluperiaatteet",
+  "resource.api-design-principles.outcomes.2": "Asiaan liittyvien käytäntöjen parempi soveltaminen",
   "resource.api-design-principles.steps.1": "**Johdonmukainen nimeäminen ja käyttäytyminen:** Sovelletaan yhteisiä käytäntöjä resursseja, virheitä ja formaatteja varten, jotta rajapinnat olisivat ennakoitavissa.",
   "resource.api-design-principles.steps.2": "**Sopimusperusteinen:** kaappaa rajapinta OpenAPIlla tai AsyncAPIlla ennen koodausta tiimien yhdenmukaistamiseksi ja automaation mahdollistamiseksi.",
   "resource.api-design-principles.steps.3": "**Käytettävyys ja löydettävyys:** Selkeä dokumentaatio ja esimerkit, jotta kehittäjät ymmärtävät nopeasti, miten APIta käytetään.",
   "resource.api-design-principles.steps.4": "**Iteroi turvallisesti:** Kehitä malleja pienissä, versioiduissa vaiheissa, jotta muutokset eivät häiritse nykyisiä API-hyödyntäjiä.",
-  "resource.api-design-principles.tips.1": "Käytä sitä yhteistyössä eri liiketoiminta- ja teknisten roolien välillä",
+  "resource.api-design-principles.tips.1": "Käytä resurssia yhteistyössä olennaisten liiketoiminta- ja teknisten roolien kanssa.",
   "resource.api-value-proposition-canvas.outcomes.1": "Yhdenmukaisuus käyttäjien tarpeiden kanssa",
   "resource.api-value-proposition-canvas.outcomes.2": "Parempi API-hyödyntäjien tyytyväisyys",
   "resource.api-value-proposition-canvas.steps.1": "Tunnistetaan ominaisuudet, jotka tuottavat odotettuja hyötyjä",
@@ -335,25 +335,25 @@
   "resource.api-value-proposition-canvas.steps.3": "Ominaisuuksien kartoittaminen API-tuotteisiin",
   "resource.api-value-proposition-canvas.tips.1": "Korosta ominaisuuksia, jotka vähentävät kipupisteitä tai vahvistavat tavoiteltuja hyötyjä.",
   "resource.api-value-proposition-canvas.tips.2": "Validoi ominaisuudet API-hyödyntäjien kanssa yhdenmukaistamisen varmistamiseksi.",
-  "resource.business-impact-canvas.outcomes.1": "Parannettu turvallisuus ja vaatimustenmukaisuus",
-  "resource.business-impact-canvas.outcomes.2": "Parannettu API-suorituskyky",
+  "resource.business-impact-canvas.outcomes.1": "Priorisoidut riskit ja lieventämistoimenpiteet",
+  "resource.business-impact-canvas.outcomes.2": "Arkkitehtuuri- ja alustapäätöksiä tukeva näyttö",
   "resource.business-impact-canvas.steps.1": "Saatavuusriskien lieventämistavat: Määrittele lieventämistoimenpiteet.",
   "resource.business-impact-canvas.steps.2": "Turvallisuusriskit: Dokumentoi turvallisuuteen liittyvät riskit.",
   "resource.business-impact-canvas.steps.3": "Tapoja vähentää turvallisuusriskejä: Ehdota strategioita turvallisuusriskien lieventämiseksi.",
   "resource.business-impact-canvas.steps.4": "Tietoriskit: Tunnista tietojen tarkkuuteen tai saatavuuteen liittyvät riskit.",
   "resource.business-impact-canvas.steps.5": "Tietoriskien lieventämistavat: Suunnittele strategioita tietoriskien torjumiseksi.",
-  "resource.business-impact-canvas.tips.1": "Mahdollisten riskien tunnistaminen aiempien tapahtumien avulla",
-  "resource.business-impact-canvas.tips.2": "Priorisoi kriittiset APIt, joilla on suurin vaikutus liiketoimintaan.",
-  "resource.capacity-canvas.outcomes.1": "Valmistautunut tuleviin kulutussuuntauksiin",
-  "resource.capacity-canvas.outcomes.2": "Määritellyt välimuistitallennus- ja nopeudenrajoitusstrategiat",
+  "resource.business-impact-canvas.tips.1": "Käy riskit läpi sekä liiketoiminnan että teknisten sidosryhmien kanssa.",
+  "resource.business-impact-canvas.tips.2": "Haasta oletuksia aiempien häiriöiden ja operatiivisen näytön avulla.",
+  "resource.capacity-canvas.outcomes.1": "Dokumentoidut oletukset kuormitushuipuista, saatavuudesta ja kasvusta",
+  "resource.capacity-canvas.outcomes.2": "Määritellyt skaalaus-, välimuisti- ja kutsurajoitusratkaisut",
   "resource.capacity-canvas.steps.1": "Ennustaa tulevia kulutussuuntauksia",
   "resource.capacity-canvas.steps.2": "Suunnittele huippukuormitus ja saatavuusvaatimukset",
   "resource.capacity-canvas.steps.3": "Määrittele välimuistitallennus- ja nopeudenrajoitusstrategiat.",
   "resource.capacity-canvas.steps.4": "Ehdotetaan skaalausstrategioita",
-  "resource.capacity-canvas.tips.1": "Määrittele huippukäytön skenaariot",
-  "resource.capacity-canvas.tips.2": "Sisällytä skaalautuvuuden testaus suunnitteluvaiheeseen.",
-  "resource.customer-journey-canvas.outcomes.1": "Parannettu API-design",
-  "resource.customer-journey-canvas.outcomes.2": "Parempi käyttäjä- ja hyödyntäjäkokemus",
+  "resource.capacity-canvas.tips.1": "Käytä mitattua tietoa aina kun sitä on saatavilla ja kirjaa oletukset näkyviin.",
+  "resource.capacity-canvas.tips.2": "Päivitä kanvas pilotin tai kysynnän olennaisten muutosten jälkeen.",
+  "resource.customer-journey-canvas.outcomes.1": "Dokumentoidut tarpeet, kipupisteet, hyödyt, syötteet ja tuotokset",
+  "resource.customer-journey-canvas.outcomes.2": "Polkua koskeva näyttö kyvykkyys-, vaatimus- ja arkkitehtuuripäätösten tueksi",
   "resource.customer-journey-canvas.steps.1": "Tunnista matkan käynnistäjät",
   "resource.customer-journey-canvas.steps.2": "Kuvaile matkan loppua",
   "resource.customer-journey-canvas.steps.3": "Kartoita matkan vaiheet ja syötteet/lähtötiedot",
@@ -361,13 +361,13 @@
   "resource.customer-journey-canvas.steps.5": "Yhteenveto asiakkaan saamista eduista",
   "resource.customer-journey-canvas.steps.6": "Määritellään tarvittavat syötteet ja tuotokset",
   "resource.customer-journey-canvas.steps.7": "Määrittele API-vuorovaikutukset kullekin vaiheelle",
-  "resource.customer-journey-canvas.tips.1": "Käytä tämän kanvaksen tuotoksia muiden kanvasten, kuten API-arvolupauskanvas -kanvaksen, laatimiseen.",
-  "resource.event-canvas.outcomes.1": "Selkeät tapahtumien laukaisijat ja käsittelylogiikka",
-  "resource.event-canvas.outcomes.2": "Parempi reagointikyky reaaliaikaisiin muutoksiin",
+  "resource.customer-journey-canvas.tips.1": "Hyödynnä tuloksia arvolupauksen, toimialueen, vaatimusten ja arkkitehtuurin työstämisessä.",
+  "resource.event-canvas.outcomes.1": "Selkeytetyt tapahtumat, laukaisimet, skeemat, tuottajat ja hyödyntäjät",
+  "resource.event-canvas.outcomes.2": "Dokumentoidut käsittely-, kuittaus- ja virhetilanneodotukset",
   "resource.event-canvas.steps.1": "Määritä laukaisimet kullekin tapahtumalle",
-  "resource.event-canvas.steps.2": "Kuvaa tapahtumien taustajärjestelmän käsittelylogiikka.",
+  "resource.event-canvas.steps.2": "Kuvaa tapahtumien käsittely, tilamuutokset ja virhetilanteiden käsittely.",
   "resource.event-canvas.steps.3": "Määritä tuloksena olevat tuotokset tai kuittaukset",
-  "resource.event-canvas.tips.1": "Dokumentoi tapahtumavirrat ja riippuvuudet.",
+  "resource.event-canvas.tips.1": "Dokumentoi tapahtumavirrat, omistajuus, järjestysoletukset ja riippuvuudet.",
   "resource.event-canvas.tips.2": "Validoi tapahtumien käsittely testitapauksilla",
   "resource.graphql-canvas.outcomes.1": "Määritellyt tyypit ja niiden väliset suhteet",
   "resource.graphql-canvas.outcomes.2": "Selkeät kyselyt, mutaatiot ja tilaukset",
@@ -380,16 +380,16 @@
   "resource.graphql-canvas.steps.7": "Harkitse, onko olemassa sivutus-, suodatus- tai nopeusrajoituksia.",
   "resource.graphql-canvas.tips.1": "Dokumentoi esimerkkikyselyt ja mutaatiot.",
   "resource.graphql-canvas.tips.2": "Varmista, että tyyppien nimet ovat kuvaavia ja johdonmukaisia.",
-  "resource.interaction-canvas.outcomes.1": "Määritellyt syötteet ja tuotokset kutakin vuorovaikutusta varten.",
-  "resource.interaction-canvas.outcomes.2": "Yhdenmukaiset validointisäännöt vuorovaikutustilanteissa",
+  "resource.interaction-canvas.outcomes.1": "Selkeytetyt syötteet, tuotokset, komennot, kyselyt, tapahtumat ja vastaukset",
+  "resource.interaction-canvas.outcomes.2": "Sovitut validointisäännöt ja vuorovaikutusodotukset",
   "resource.interaction-canvas.steps.1": "Määritä päätepisteet kullekin vuorovaikutukselle",
   "resource.interaction-canvas.steps.2": "Dokumentoi kunkin vuorovaikutuksen syötteet ja tuotokset.",
   "resource.interaction-canvas.steps.3": "Validointisääntöjen ja -rajoitusten määrittäminen",
   "resource.interaction-canvas.steps.4": "Luo vuorovaikutusmalleja CRUD-, kysely-, komento- ja tapahtumapohjaista vuorovaikutusta varten.",
   "resource.interaction-canvas.tips.1": "Simuloi vuorovaikutusta mallitietojen kanssa työnkulkujen validoimiseksi.",
-  "resource.interaction-canvas.tips.2": "Dokumentoi odotetut vastaukset onnistuneissa ja epäonnistuneissa vuorovaikutustilanteissa.",
-  "resource.location-canvas.outcomes.1": "Optimoitu API-suorituskyky eri alueilla",
-  "resource.location-canvas.outcomes.2": "Parempi ymmärrys alueellisista vaatimuksista",
+  "resource.interaction-canvas.tips.2": "Dokumentoi odotetut vastaukset onnistuneissa, epäonnistuneissa ja poikkeuksellisissa tilanteissa.",
+  "resource.location-canvas.outcomes.1": "Tunnistetut alueelliset suorituskyky- ja saavutettavuusrajoitteet",
+  "resource.location-canvas.outcomes.2": "Selkeytetyt tiedon sijaintivaatimukset, luottamusrajat ja sovellettava sääntely",
   "resource.location-canvas.steps.1": "Dokumentoi, missä hyödyntäjät sijaitsevat.",
   "resource.location-canvas.steps.2": "Tunnista sovellettavat säädökset.",
   "resource.location-canvas.steps.3": "Dokumentoi, missä tietojen on oltava.",
@@ -405,7 +405,7 @@
   "resource.rest-canvas.tips.1": "Varmistetaan, että resurssien URI:t ovat intuitiivisia ja johdonmukaisia.",
   "resource.rest-canvas.tips.2": "Dokumentoi virheiden käsittely ja vastauskoodit.",
   "resource.capability-value-proposition-canvas.title": "Kyvykkyyden arvolupauskanvas",
-  "resource.capability-value-proposition-canvas.description": "Teknologiariippumaton kanvas hyödyntäjien tehtävien, tavoiteltujen hyötyjen, kipupisteiden ja mahdollisten uudelleenkäytettävien kyvykkyyksien kartoittamiseen ennen integraatiotyylin valintaa.",
+  "resource.capability-value-proposition-canvas.description": "Teknologiariippumaton kanvas hyödyntäjien tehtävien, hyötyjen, kipupisteiden ja mahdollisten uudelleenkäytettävien kyvykkyyksien kartoittamiseen ennen toteutustavan valintaa.",
   "resource.capability-value-proposition-canvas.outcomes": "Selkeä arvolupaus uudelleenkäytettävälle kyvykkyydelle",
   "resource.capability-value-proposition-canvas.outcomes.1": "Hyödyntäjien tehtävät, tavoitellut hyödyt ja kipupisteet on kuvattu ilman oletusta tietystä teknologiasta.",
   "resource.capability-value-proposition-canvas.outcomes.2": "Mahdolliset uudelleenkäytettävät kyvykkyydet on tunnistettu arkkitehtuurin arviointia varten.",
@@ -413,10 +413,10 @@
   "resource.capability-value-proposition-canvas.steps.1": "Tunnista kyvykkyyden ominaisuudet, jotka mahdollistavat tavoitellut hyödyt.",
   "resource.capability-value-proposition-canvas.steps.2": "Tunnista kyvykkyyden ominaisuudet, jotka vähentävät kipupisteitä.",
   "resource.capability-value-proposition-canvas.steps.3": "Ryhmittele ominaisuudet mahdollisiksi uudelleenkäytettäviksi kyvykkyyksiksi.",
-  "resource.capability-value-proposition-canvas.tips": "Pysy teknologiariippumattomana, kunnes vaatimukset osoittavat sopivan toteutustyylin.",
-  "resource.capability-value-proposition-canvas.tips.1": "Käytä tätä API-arvolupauskanvaksen sijaan, kun API-rajapintaa ei vielä ole valittu integraatiotyyliä varten.",
+  "resource.capability-value-proposition-canvas.tips": "Pysy teknologiariippumattomana, kunnes vaatimukset osoittavat sopivan toteutustavan.",
+  "resource.capability-value-proposition-canvas.tips.1": "Käytä tätä API Value Proposition Canvasin sijaan, kun APIa ei ole vielä valittu toteutustavaksi.",
   "resource.capability-business-model-canvas.title": "Kyvykkyyden liiketoimintamallikanvas",
-  "resource.capability-business-model-canvas.description": "Liiketoimintamallikanvas uudelleenkäytettäville integraatiokyvykkyyksille. Se kattaa arvon, hyödyntäjät, omistajuuden, osallistamisen, kustannukset ja hyödyt ilman oletusta API-toteutuksesta.",
+  "resource.capability-business-model-canvas.description": "Uudelleenkäytettävien kyvykkyyksien liiketoimintamallikanvas, joka käsittelee arvoa, hyödyntäjiä, omistajuutta, vuorovaikutusta, kustannuksia ja hyötyjä olettamatta toteutustapaa.",
   "resource.capability-business-model-canvas.outcomes": "Toteuttamiskelpoinen toimintamalli uudelleenkäytettävälle kyvykkyydelle",
   "resource.capability-business-model-canvas.outcomes.1": "Omistajuus, hyödyntäjät, kanavat, kumppanit ja tuen tarpeet on selkeytetty.",
   "resource.capability-business-model-canvas.outcomes.2": "Kustannukset ja hyödyt ovat näkyvissä ennen arkkitehtuurisitoumusta.",
@@ -426,17 +426,120 @@
   "resource.capability-business-model-canvas.steps.3": "Kuvaa kustannukset ja hyödyt.",
   "resource.capability-business-model-canvas.steps.4": "Selkeytä omistajuus, rahoitus, tuki ja elinkaaren odotukset.",
   "resource.capability-business-model-canvas.steps.5": "Validoi malli hyödyntäjien, tuottajien ja governance-sidosryhmien kanssa.",
-  "resource.capability-business-model-canvas.tips": "Käytä tätä API-liiketoimintamallikanvaksen sijaan, kun integraatiotyyli on vielä avoin.",
+  "resource.capability-business-model-canvas.tips": "Käytä tätä API Business Model Canvasin sijaan niin kauan kuin toteutustapa on avoin.",
   "resource.capability-business-model-canvas.tips.1": "Pidä fokus uudelleenkäytettävän kyvykkyyden elinkelpoisuudessa, ei yksittäisessä yhteydessä.",
   "resource.consumer-experience-requirements-canvas.title": "Hyödyntäjäkokemuksen vaatimuskanvas",
-  "resource.consumer-experience-requirements-canvas.description": "Vaatimuskanvas hyödyntäjäkokemuksen ja ei-toiminnallisten tarpeiden kuvaamiseen ennen myöhempää arkkitehtuurivalintaa.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Teknologiariippumattomat hyödyntäjävaatimukset",
+  "resource.consumer-experience-requirements-canvas.description": "Vaatimuskanvas hyödyntäjäkokemukselle ja ei-toiminnallisille tarpeille, joiden tulee ohjata myöhempää arkkitehtuuri- ja toteutustapapäätöstä.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Teknologiariippumattomat hyödyntäjä- ja palveluvaatimukset",
   "resource.consumer-experience-requirements-canvas.outcomes.1": "Kokemukseen ja ei-toiminnallisiin tarpeisiin liittyvät vaatimukset on kuvattu ennen suunnittelun aloittamista.",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Arkkitehtuurivaikutukset on dokumentoitu toteutustyylin valintaa varten.",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Dokumentoidut arkkitehtuurivaikutukset toteutustavan valintaa varten",
   "resource.consumer-experience-requirements-canvas.steps": "Kuvaa hyödyntäjien tavoitteet ja käyttökonteksti.",
   "resource.consumer-experience-requirements-canvas.steps.1": "Dokumentoi saatavuuteen, ajantasaisuuteen, volyymiin, suorituskykyyn, datan laatuun ja yhdenmukaisuuteen liittyvät odotukset.",
   "resource.consumer-experience-requirements-canvas.steps.2": "Dokumentoi turvallisuuteen, tietosuojaan, käyttöönottoon, muutoksiin, havainnoitavuuteen, tukeen ja palautumiseen liittyvät odotukset.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Tiivistä, mitä vaatimukset tarkoittavat mahdollisille arkkitehtuurityyleille.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Tiivistä, mitä vaatimukset merkitsevät mahdollisten toteutustapojen kannalta.",
   "resource.consumer-experience-requirements-canvas.tips": "Käytä tätä siltana kyvykkyyden arvon ja arkkitehtuuripäätöksen välillä.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Älä valitse API-rajapintaa, tapahtumaa, tiedostoa, streamia tai datatuotetta ennen kuin vaatimukset osoittavat sopivan vaihtoehdon."
+  "resource.consumer-experience-requirements-canvas.tips.1": "Älä valitse APIa, tapahtumaa, tiedostoa, tietovirtaa, datatuotetta, suoraa integraatiota tai hybriditapaa ennen kuin vaatimukset osoittavat sopivan vaihtoehdon.",
+  "resource.integration-style-selection-guide.title": "Integraatiotavan valintaopas",
+  "resource.integration-style-selection-guide.description": "Ohje API-, tapahtuma-, tiedosto-, tietovirta-, datatuote-, suora integraatio- tai hybriditoteutustavan valintaan vaatimusten ja rajoitteiden perusteella.",
+  "resource.integration-style-selection-guide.outcomes": "Perusteltu integraation toteutustapa",
+  "resource.integration-style-selection-guide.outcomes.1": "Integraatiotapojen keskeiset vaihtoehdot ja kompromissit on dokumentoitu.",
+  "resource.integration-style-selection-guide.outcomes.2": "Valittu tapa on jäljitettävissä hyödyntäjä-, alusta-, data- ja operatiivisiin vaatimuksiin.",
+  "resource.integration-style-selection-guide.steps": "Vertaa mahdollisia integraatiotapoja viiveen, volyymin, kytkeytymisen, datan omistajuuden, ajantasaisuuden, hallinnan ja operoitavuuden tarpeisiin.",
+  "resource.integration-style-selection-guide.steps.1": "Tunnista, milloin API, tapahtuma, tiedosto, tietovirta, datatuote, suora integraatio tai hybridiratkaisu sopii käyttötapaukseen.",
+  "resource.integration-style-selection-guide.steps.2": "Dokumentoi valitun toteutustavan rajoitteet, riskit ja alustariippuvuudet.",
+  "resource.integration-style-selection-guide.steps.3": "Kirjaa, miksi hylättyjä vaihtoehtoja ei valittu.",
+  "resource.integration-style-selection-guide.tips": "Käytä tätä sen jälkeen, kun vaatimukset ovat selkeät, mutta ennen yksityiskohtaista sopimussuunnittelua.",
+  "resource.integration-style-selection-guide.tips.1": "Pidä REST-, tapahtuma-, GraphQL-, tiedosto-, tietovirta- ja datatuoteresurssit valinnaisina jatkosuunnittelun resursseina.",
+  "resource.process-workflow-design-guide.title": "Prosessin ja työnkulun suunnitteluopas",
+  "resource.process-workflow-design-guide.description": "Ohje prosessivaiheiden, roolien, luovutusten, päätöspisteiden, tilojen, syötteiden, tuotosten ja poikkeusten mallintamiseen automaatiotyönkulun suunnittelua varten.",
+  "resource.process-workflow-design-guide.outcomes": "Selkeä automaatiotyönkulun suunnitelma",
+  "resource.process-workflow-design-guide.outcomes.1": "Prosessivaiheet ja luovutukset on dokumentoitu ennen toteutusta.",
+  "resource.process-workflow-design-guide.outcomes.2": "Työnkulun tilat, syötteet, tuotokset ja poikkeuspolut on ymmärretty.",
+  "resource.process-workflow-design-guide.steps": "Kuvaa nykyinen ja tavoiteltu prosessivirta, mukaan lukien ihmisten ja järjestelmien vastuut.",
+  "resource.process-workflow-design-guide.steps.1": "Tunnista työnkulun käynnistimet, tilat, päätökset, datasyötteet, tuotokset ja valmistumisen kriteerit.",
+  "resource.process-workflow-design-guide.steps.2": "Dokumentoi luovutukset käyttäjien, järjestelmien, operoinnin ja tukiroolien välillä.",
+  "resource.process-workflow-design-guide.steps.3": "Vahvista, mitkä vaiheet kannattaa automatisoida ja mitkä edellyttävät ihmisen harkintaa.",
+  "resource.process-workflow-design-guide.tips": "Pidä prosessisuunnittelu erillään API- tai integraatiosopimuksen suunnittelusta, kunnes työnkulku on selkeä.",
+  "resource.process-workflow-design-guide.tips.1": "Käytä tätä ensisijaisena suunnitteluresurssina automaatiotyönkuluille.",
+  "resource.decision-business-rules-guide.title": "Päätösten ja liiketoimintasääntöjen opas",
+  "resource.decision-business-rules-guide.description": "Ohje sääntöjen, kynnysarvojen, päätösten, hyväksyntöjen, kelpoisuustarkistusten ja sääntöjen omistajuuden kuvaamiseen automaation suunnittelua varten.",
+  "resource.decision-business-rules-guide.outcomes": "Selkeästi kuvatut päätökset ja liiketoimintasäännöt",
+  "resource.decision-business-rules-guide.outcomes.1": "Säännöt ja kynnysarvot on dokumentoitu omistajineen.",
+  "resource.decision-business-rules-guide.outcomes.2": "Automaation päätökset ovat jäljitettävissä käytäntöihin, prosessiin tai liiketoimintatarkoitukseen.",
+  "resource.decision-business-rules-guide.steps": "Listaa päätökset, jotka automaation täytyy tehdä tai joita sen täytyy tukea.",
+  "resource.decision-business-rules-guide.steps.1": "Dokumentoi sääntöjen ehdot, kynnysarvot, poikkeukset, hyväksynnät ja eskalointipisteet.",
+  "resource.decision-business-rules-guide.steps.2": "Tunnista sääntöjen omistajat ja muutosten hallintatapa jokaiselle päätösalueelle.",
+  "resource.decision-business-rules-guide.tips": "Erota vakaat liiketoimintasäännöt konfiguroitavista operatiivisista parametreista.",
+  "resource.decision-business-rules-guide.tips.1": "Käytä esimerkkejä ja reunatapauksia sääntöjen tulkinnan validointiin.",
+  "resource.automation-trigger-handoff-exception-guide.title": "Automaation käynnistinten, luovutusten ja poikkeusten opas",
+  "resource.automation-trigger-handoff-exception-guide.description": "Ohje automaation käynnistinten, ihmisten välisten luovutusten, poikkeusten käsittelyn, uudelleenyritysten, kompensoivien toimien ja tuen eskalointipolkujen määrittelyyn.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes": "Määritellyt automaation käynnistimet ja poikkeuspolut",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.1": "Ihmisten väliset luovutukset ja tuen eskaloinnit ovat selkeitä.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.2": "Poikkeukset, uudelleenyritykset ja kompensoivat toimet on suunniteltu ennen toimitusta.",
+  "resource.automation-trigger-handoff-exception-guide.steps": "Määritä tapahtumat, aikataulut, käyttäjätoimet tai järjestelmätilat, jotka käynnistävät automaation.",
+  "resource.automation-trigger-handoff-exception-guide.steps.1": "Kuvaa luovutukset automaatiolta käyttäjille, operaattoreille tai tukitiimeille.",
+  "resource.automation-trigger-handoff-exception-guide.steps.2": "Dokumentoi poikkeukset, uudelleenyrityssäännöt, aikakatkaisujen toiminta ja varapolut.",
+  "resource.automation-trigger-handoff-exception-guide.steps.3": "Määritä hälytykset ja eskalointikynnykset epäonnistuneille tai epäselville automaation tuloksille.",
+  "resource.automation-trigger-handoff-exception-guide.tips": "Suunnittele poikkeuspolut työnkulun olennaisena osana, ei jälkikäteen.",
+  "resource.automation-trigger-handoff-exception-guide.tips.1": "Ota liiketoiminta- ja operointiroolit mukaan luovutusten validointiin.",
+  "resource.automation-testing-guide.title": "Automaation testausopas",
+  "resource.automation-testing-guide.description": "Ohje automatisoitujen työnkulkujen, päätösten, integraatioiden, poikkeusten, palautuksen, valvonnan ja käyttäjävaikutusten testaamiseen ennen julkaisua.",
+  "resource.automation-testing-guide.outcomes": "Validoitu automaation toiminta",
+  "resource.automation-testing-guide.outcomes.1": "Työnkulun, sääntöjen, poikkeusten ja integraatioiden testit on määritelty.",
+  "resource.automation-testing-guide.outcomes.2": "Julkaisuluottamus automatisoituihin ja ihmistä tukeviin polkuihin.",
+  "resource.automation-testing-guide.steps": "Luo testit onnistuneille poluille, reunatapauksille, poikkeuksille, uudelleenyrityksille ja luovutuksille.",
+  "resource.automation-testing-guide.steps.1": "Validoi liiketoimintasäännöt ja päätösten tulokset edustavalla datalla.",
+  "resource.automation-testing-guide.steps.2": "Testaa palautus, toipuminen, havainnoitavuus ja manuaalisen puuttumisen polut.",
+  "resource.automation-testing-guide.steps.3": "Ota käyttäjät ja operaattorit mukaan hyväksyntätestaukseen, kun automaatio muuttaa työtapoja.",
+  "resource.automation-testing-guide.tips": "Käytä tuotantoa vastaavia skenaarioita ja datamuotoja paljastamatta arkaluonteista dataa.",
+  "resource.automation-testing-guide.tips.1": "Pidä testausnäyttö saatavilla valmiuskatselmointia varten.",
+  "resource.automation-operational-ownership-guide.title": "Automaation operatiivisen omistajuuden opas",
+  "resource.automation-operational-ownership-guide.description": "Ohje automaatioiden omistajuuden, runbookien, valvonnan, tuen, seurannan, muutosten hallinnan ja jatkuvan parantamisen vastuiden määrittelyyn.",
+  "resource.automation-operational-ownership-guide.outcomes": "Selkeä automaation toimintamalli",
+  "resource.automation-operational-ownership-guide.outcomes.1": "Omistajuus-, tuki- ja eskalointivastuut on määritetty.",
+  "resource.automation-operational-ownership-guide.outcomes.2": "Seuranta- ja muutostavat ovat valmiit tuotantokäyttöä varten.",
+  "resource.automation-operational-ownership-guide.steps": "Määritä automaation liiketoiminta-, tekniset ja operatiiviset omistajat.",
+  "resource.automation-operational-ownership-guide.steps.1": "Dokumentoi runbookit, tukipolut, seurantasignaalit, palveluodotukset ja eskalointisäännöt.",
+  "resource.automation-operational-ownership-guide.steps.2": "Määritä muutosten hallinta- ja katselmointikäytännöt työnkulun, alustan ja sääntöjen päivityksille.",
+  "resource.automation-operational-ownership-guide.tips": "Älä julkaise automaatiota ilman nimettyä omistajaa poikkeuksille ja jatkuvalle parantamiselle.",
+  "resource.automation-operational-ownership-guide.tips.1": "Tee valvonnan tarpeet näkyviksi ennen toimitussuunnittelun valmistumista.",
+  "resource.automation-rollback-supervision-guide.title": "Automaation palautuksen ja valvonnan opas",
+  "resource.automation-rollback-supervision-guide.description": "Ohje automaatioiden palautuksen, keskeytyksen, manuaalisen ohituksen, seurannan, valvonnan ja toipumispolkujen suunnitteluun.",
+  "resource.automation-rollback-supervision-guide.outcomes": "Hallittavat automaation toipumispolut",
+  "resource.automation-rollback-supervision-guide.outcomes.1": "Palautus, keskeytys ja ohitus on dokumentoitu.",
+  "resource.automation-rollback-supervision-guide.outcomes.2": "Valvontatarpeet ja toipumisvastuut on määritelty.",
+  "resource.automation-rollback-supervision-guide.steps": "Tunnista toimet, jotka täytyy voida palauttaa, keskeyttää tai ohittaa manuaalisesti.",
+  "resource.automation-rollback-supervision-guide.steps.1": "Määritä palautus-, kompensaatio- ja toipumismenettelyt epäonnistuneille tai virheellisille automaation tuloksille.",
+  "resource.automation-rollback-supervision-guide.steps.2": "Dokumentoi valvontakynnykset, hälytykset ja manuaaliset päätöspisteet.",
+  "resource.automation-rollback-supervision-guide.steps.3": "Validoi toipumismenettelyt ennen julkaisua.",
+  "resource.automation-rollback-supervision-guide.tips": "Käsittele palautusta ja valvontaa osana työnkulun suunnittelua ja toimitussuunnitelmaa.",
+  "resource.automation-rollback-supervision-guide.tips.1": "Hyödynnä operatiivisia häiriöitä ja läheltä piti -tilanteita valvontakriteerien tarkentamiseen.",
+  "resource.automation-readiness-checklist.title": "Automaation valmiuden tarkistuslista",
+  "resource.automation-readiness-checklist.description": "Tarkistuslista automaation työnkulun, kontrollien, riskien, vaatimustenmukaisuuden, ihmisen valvonnan, testausnäytön, palautuksen, operoinnin ja julkaisuvalmiuden validointiin.",
+  "resource.automation-readiness-checklist.outcomes": "Dokumentoitu automaation valmius",
+  "resource.automation-readiness-checklist.outcomes.1": "Tunnetut valmiuspuutteet ja lievennykset on tunnistettu ennen julkaisua.",
+  "resource.automation-readiness-checklist.outcomes.2": "Näyttö laadusta, riskistä, vaatimustenmukaisuudesta, valvonnasta ja operatiivisesta hyväksynnästä.",
+  "resource.automation-readiness-checklist.steps": "Katselmoi työnkulun suunnittelu, liiketoimintasäännöt, kontrollit, pääsy, datankäsittely ja poikkeuspolut.",
+  "resource.automation-readiness-checklist.steps.1": "Varmista testausnäyttö, palautusmenettelyt, valvontamalli ja tuen valmius.",
+  "resource.automation-readiness-checklist.steps.2": "Vahvista omistajuus, runbookit, seuranta, muutosten hallinta ja julkaisuhyväksyntä.",
+  "resource.automation-readiness-checklist.steps.3": "Kirjaa avoimet puutteet, päätökset ja hyväksytyt riskit ennen julkaisua.",
+  "resource.automation-readiness-checklist.tips": "Käytä ennen julkaisua ja uudelleen olennaisten työnkulku- tai sääntömuutosten jälkeen.",
+  "resource.automation-readiness-checklist.tips.1": "Tee ihmisen valvonta ja poikkeusten käsittely näkyväksi näytössä.",
+  "resource.automation-rollout-enablement-guide.title": "Automaation käyttöönoton ja tuen opas",
+  "resource.automation-rollout-enablement-guide.description": "Ohje automaatioiden käyttöönottoon käyttäjäviestinnän, onboardingin, käyttöohjeiden, tukipolkujen, muutoksenhallinnan ja palautesilmukoiden avulla.",
+  "resource.automation-rollout-enablement-guide.outcomes": "Käyttäjät ja operaattorit on tuettu automaation käyttöön",
+  "resource.automation-rollout-enablement-guide.outcomes.1": "Käyttöönoton viestintä, onboarding ja tukipolut on valmisteltu.",
+  "resource.automation-rollout-enablement-guide.outcomes.2": "Käyttäjät ja operaattorit ymmärtävät, miten työ muuttuu automaation julkaisun jälkeen.",
+  "resource.automation-rollout-enablement-guide.steps": "Määritä käyttöönoton kohderyhmät, ajoitus, viestintäkanavat ja koulutustarpeet.",
+  "resource.automation-rollout-enablement-guide.steps.1": "Julkaise käyttöohjeet, tukipolut, poikkeusten käsittelyn ohjeet ja eskalointikontaktit.",
+  "resource.automation-rollout-enablement-guide.steps.2": "Suunnittele siirtymän tuki käyttäjille, operaattoreille ja prosessinomistajille.",
+  "resource.automation-rollout-enablement-guide.steps.3": "Kerää palautetta käyttöönoton jälkeen ja vie parannukset kehitysjonoon.",
+  "resource.automation-rollout-enablement-guide.tips": "Käytä automaatioille käyttöönoton kieltä sen sijaan, että käsittelet tukea API-julkaisuna.",
+  "resource.automation-rollout-enablement-guide.tips.1": "Ota mukaan sekä prosessin käyttäjät että automaatiosta vastaavat operaattorit.",
+  "resource.api-community-engagement-strategies.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.",
+  "resource.api-development-best-practices.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.",
+  "resource.api-metrics-and-analytics.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.",
+  "resource.api-testing-best-practices.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.",
+  "resource.apiops-CI-CD-for-apis.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API.",
+  "resource.api-audit-checklist.tips.2": "Käytä tätä resurssia, kun valittu toteutustapa on API."
 }
diff --git a/src/data/method/fi/labels.stakeholders.json b/src/data/method/fi/labels.stakeholders.json
index 046d0b7..550f9a1 100644
--- a/src/data/method/fi/labels.stakeholders.json
+++ b/src/data/method/fi/labels.stakeholders.json
@@ -3,47 +3,47 @@
   "stakeholder.involvement.core": "Ydintiimi",
   "stakeholder.involvement.consulted": "Konsultoitava",
   "stakeholder.business-owner.title": "Liiketoiminnan omistaja",
-  "stakeholder.business-owner.description": "Edustaa liiketoiminnan tavoitteita, rahoitusta ja odotettuja tuloksia API-hankkeessa.",
+  "stakeholder.business-owner.description": "Edustaa liiketoimintatavoitteita, rahoitusta ja odotettuja tuloksia kyvykkyys-, API- tai automaatiohankkeessa.",
   "stakeholder.api-program-owner.title": "API-ohjelman omistaja",
   "stakeholder.api-program-owner.description": "Koordinoi API-portfolion käytäntöjä, organisaation suuntautumista ja pitkän aikavälin API-kyvykkyyksien kehitystä.",
   "stakeholder.api-product-owner.title": "API-tuoteomistaja",
   "stakeholder.api-product-owner.description": "Ohjaa API-mahdollisuutta, priorisointia ja tuotetasolla tehtyjä päätöksiä elinkaaren aikana.",
   "stakeholder.capability-owner.title": "Kyvykkyyden omistaja",
-  "stakeholder.capability-owner.description": "Vastaa kyvykkyyden visiosta, tavoitteista, priorisoinnista ja elinkaaren aikaisesta kehittämisestä.",
+  "stakeholder.capability-owner.description": "Vastaa kyvykkyyden visiosta, arvosta, priorisoinnista, elinkaaresta ja uudelleenkäytöstä eri hyödyntäjille.",
   "stakeholder.domain-specialist.title": "Liiketoiminta-asiantuntija",
-  "stakeholder.domain-specialist.description": "Tuo syvällistä tietoa liiketoiminta-alasta, käsitteistä, säännöistä ja rajoituksista, joita APIn täytyy heijastaa.",
+  "stakeholder.domain-specialist.description": "Tuo syvällistä tietoa liiketoiminta-alueesta, käsitteistä, säännöistä ja rajoituksista, joita kyvykkyyden tai rajapinnan täytyy heijastaa.",
   "stakeholder.customer-specialist.title": "Asiakas- tai kumppaniedustaja",
-  "stakeholder.customer-specialist.description": "Edustaa APIn ulkoisten asiakkaiden, kumppaneiden tai muiden hyödyntäjien tarpeita ja näkökulmia.",
+  "stakeholder.customer-specialist.description": "Edustaa asiakkaan tai kumppanin näkökulmaa polkuun, arvoon ja yhteistyömalliin.",
   "stakeholder.api-consumer-specialist.title": "API-hyödyntäjien edustaja",
   "stakeholder.api-consumer-specialist.description": "Edustaa kehittäjien, integraattoreiden tai muiden API-hyödyntäjien tarpeita, jotka käyttävät APIa suoraan.",
   "stakeholder.platform-architect.title": "Alusta-arkkitehti",
-  "stakeholder.platform-architect.description": "Ohjaa alustan, integraation, skaalautuvuuden ja arkkitehtuurin päätöksiä, jotka määrittelevät, miten API on rakennettu ja toimii.",
+  "stakeholder.platform-architect.description": "Ohjaa alustan, integraation, skaalautuvuuden ja arkkitehtuurin päätöksiä, jotka määrittelevät, miten kyvykkyys tai API rakennetaan ja operoidaan.",
   "stakeholder.api-architect.title": "API-arkkitehti",
   "stakeholder.api-architect.description": "Vastaa API-arkkitehtuurista, suunnitteluperiaatteista ja rajapintasopimusten laadusta.",
   "stakeholder.integration-architect.title": "Integraatioarkkitehti",
-  "stakeholder.integration-architect.description": "Suunnittelee integraatioratkaisut, integraatiomallit ja niiden yhteensopivuuden kokonaisarkkitehtuurin kanssa.",
+  "stakeholder.integration-architect.description": "Suunnittelee integraatiotavat ja toteutustavat, joilla kyvykkyys tai API yhdistetään muihin järjestelmiin.",
   "stakeholder.platform-owner.title": "Alustan omistaja",
-  "stakeholder.platform-owner.description": "Vastaa alustan kyvykkyyksistä, kehittämisestä ja operatiivisesta toiminnasta.",
+  "stakeholder.platform-owner.description": "Vastaa alustan kyvykkyyksistä, tiekartasta, operatiivisesta mallista ja palveluodotuksista.",
   "stakeholder.api-designer.title": "API-suunnittelija",
-  "stakeholder.api-designer.description": "Suunnittelee rajapintasopimukset, vuorovaikutusmallit, johdonmukaisuuden, käytettävyyden ja tarjottavat kyvykkyydet.",
-  "stakeholder.api-engineer.title": "Ohjelmistokehittäjä",
-  "stakeholder.api-engineer.description": "Omistaa toteutuksen, automaation, testauksen ja julkaisun kulkuun liittyvät kysymykset, jotka ovat tarpeen toimittaa API luotettavasti.",
+  "stakeholder.api-designer.description": "Suunnittelee rajapintasopimuksen, vuorovaikutusmallin, johdonmukaisuuden, käytettävyyden ja tarjottavat kyvykkyydet.",
+  "stakeholder.api-engineer.title": "Toimituskehittäjä",
+  "stakeholder.api-engineer.description": "Vastaa toteutuksesta, automaatiosta, testauksesta ja julkaisun kulusta, joita kyvykkyyden, APIn tai automaation luotettava toimittaminen edellyttää.",
   "stakeholder.automation-owner.title": "Automaation omistaja",
-  "stakeholder.automation-owner.description": "Vastaa automaatiokyvykkyyksien tavoitteista, priorisoinnista ja liiketoiminta-arvosta.",
+  "stakeholder.automation-owner.description": "Vastaa automaation tavoitteista, liiketoiminta-arvosta, priorisoinnista, kontrolleista ja elinkaaren tuloksista.",
   "stakeholder.process-owner.title": "Prosessin omistaja",
-  "stakeholder.process-owner.description": "Vastaa automatisoitavan liiketoimintaprosessin tavoitteista, kehittämisestä ja tuloksista.",
+  "stakeholder.process-owner.description": "Vastaa automatisoitavasta liiketoimintaprosessista, mukaan lukien tavoitteet, säännöt, tulokset ja kehittämisen prioriteetit.",
   "stakeholder.automation-engineer.title": "Automaatiokehittäjä",
-  "stakeholder.automation-engineer.description": "Toteuttaa, testaa ja ylläpitää automaatioratkaisuja sekä niiden integraatioita.",
+  "stakeholder.automation-engineer.description": "Toteuttaa, testaa, integroi ja ylläpitää automaatioratkaisuja ja niitä tukevia työnkulkuja.",
   "stakeholder.security-specialist.title": "Turvallisuusasiantuntija",
-  "stakeholder.security-specialist.description": "Varmistaa, että turvallisuusriskit, kontrollit ja luottamusrajat käsitellään koko API-kehitysprosessin aikana.",
-  "stakeholder.compliance-specialist.title": "Vaatimuksenmukaisuuden ja oikeudellinen asiantuntija",
-  "stakeholder.compliance-specialist.description": "Selventää juridiset, tietosuojaan liittyvät ja muut vaatimustenmukaisuusvaatimukset, jotka vaikuttavat kyvykkyyteen tai rajapintaan.",
+  "stakeholder.security-specialist.description": "Varmistaa, että turvallisuusriskit, kontrollit ja luottamusrajat käsitellään koko elinkaaren aikana.",
+  "stakeholder.compliance-specialist.title": "Vaatimustenmukaisuus- ja lakiasiantuntija",
+  "stakeholder.compliance-specialist.description": "Selventää juridiset, tietosuojaan liittyvät, sääntelyyn liittyvät ja sopimukselliset vaatimukset, jotka vaikuttavat kyvykkyyteen, APIin, rajapintaan tai automaatioon.",
   "stakeholder.governance-specialist.title": "API-hallinnan omistaja",
   "stakeholder.governance-specialist.description": "Vastaa API-hallintaprosesseista, ohjeista ja päätöksenteosta, joka määrittelee, miten API-kehityspäätökset tehdään ja dokumentoidaan.",
   "stakeholder.api-devrel-specialist.title": "Dokumentoinnin ja kehittäjäsuhteiden omistaja",
   "stakeholder.api-devrel-specialist.description": "Varmistaa, että API-dokumentaatio, esimerkit, koulutus ja kehittäjäsuhteiden strategiat tukevat API-hyödyntäjien tarpeita.",
   "stakeholder.operations-specialist.title": "Tuki- ja operaatioiden omistaja",
-  "stakeholder.operations-specialist.description": "Vastaa tuesta, valvonnasta, vianmäärityksestä ja jatkuvasta parantamisesta, jotka varmistavat ratkaisun luotettavuuden ja hyödyntäjien tyytyväisyyden.",
+  "stakeholder.operations-specialist.description": "Edustaa tuotannon tukea, häiriönhallintaa, havainnoitavuutta ja operatiivista valmiutta kyvykkyydelle, APIlle tai automaatiolle.",
   "stakeholder.partner-specialist.title": "Kumppani- ja toimittajavastaava",
-  "stakeholder.partner-specialist.description": "Koordinoi kumppani- ja toimittajasuhteita, jotka vaikuttavat kyvykkyyden suunnitteluun ja kehittämiseen."
-}
\ No newline at end of file
+  "stakeholder.partner-specialist.description": "Koordinoi ulkoisia kumppani-, toimittaja- ja alihankkijasuhteita, jotka vaikuttavat kyvykkyys- tai API-strategiaan ja toimitukseen."
+}
diff --git a/src/data/method/fr/labels.criteria.json b/src/data/method/fr/labels.criteria.json
index 60a2d95..c40e9cd 100644
--- a/src/data/method/fr/labels.criteria.json
+++ b/src/data/method/fr/labels.criteria.json
@@ -7,20 +7,20 @@
   "criterion.stakeholder-approval": "Les parties prenantes concernées conviennent que cette opportunité de capacité mérite d'être explorée et priorisée.",
   "criterion.api-opportunity-documented": "L'opportunité de capacité est identifiée et documentée.",
   "criterion.api-reusability": "La capacité répond à un besoin métier clair et peut être réutilisée par les utilisateurs prévus.",
-  "criterion.hide-backend-discrepancies": "L'interface choisie masque de manière appropriée la complexité et les incohérences des systèmes systèmes backend pour les utilisateurs.",
-  "criterion.value-prop-validated": "La proposition de valeur de la capacité a été validée avec les parties prenantes métier et les représentants des utilisateurs.",
+  "criterion.hide-backend-discrepancies": "L’interface choisie fournit une abstraction appropriée aux utilisateurs.",
+  "criterion.value-prop-validated": "La proposition de valeur de la capacité a été validée avec les parties prenantes métier et utilisateurs.",
   "criterion.consumer-segments-identified": "Les segments d'utilisateurs sont identifiés.",
   "criterion.api-roadmap-defined": "Une feuille de route de haut niveau pour la mise en œuvre est définie.",
   "criterion.architecture-patterns-validated": "L'architecture, la plateforme et le mode de mise en œuvre choisis ont été validés avec les parties prenantes concernées en architecture, sécurité et plateforme.",
   "criterion.design-reflects-business-value": "La conception de l'interface et les capacités exposées sont clairement reliées à la valeur métier et aux besoins des utilisateurs.",
   "criterion.api-consistency": "La conception de l'interface respecte les standards partagés de produit, de conception et de qualité.",
   "criterion.api-contract-tested": "Le contrat d'interface a été validé et testé par rapport aux exigences fonctionnelles et non fonctionnelles.",
-  "criterion.automation-workflow-validated": "Le workflow, les regles, les integrations et les contrats d interface pertinents ont ete valides et testes.",
-  "criterion.api-description-available": "L'interface et ses capacités sont documentées de manière suffisante pour la revue, l'audit et l'onboarding.",
+  "criterion.automation-workflow-validated": "Le workflow, les règles, les intégrations et les contrats d’interface pertinents ont été validés et testés.",
+  "criterion.api-description-available": "L’interface et ses capacités sont documentées de manière suffisamment claire pour la revue, l’audit et l’onboarding.",
   "criterion.audit-passed": "La solution réussit les contrôles de qualité, de sécurité, de conformité et de préparation.",
   "criterion.audit-reports-shared": "Les résultats d'audit et les décisions de correction sont partagés avec les parties prenantes concernées.",
-  "criterion.api-ready-for-publishing": "La capacité est prête à être publiée via le mécanisme de mise à disposition choisi.",
+  "criterion.api-ready-for-publishing": "La capacité est prête à être publiée ou mise à disposition via le mécanisme de livraison choisi.",
   "criterion.api-documentation-ready": "La documentation et les supports d'onboarding destinés aux utilisateurs sont prêts.",
   "criterion.consumer-support-ready": "Les processus d'onboarding, de support et de communication sont prêts pour les utilisateurs.",
-  "criterion.legal-compliance-clear": "Les exigences juridiques, de confidentialité et de conformité liées à la publication sont définies et comprises."
+  "criterion.legal-compliance-clear": "Les exigences juridiques, de confidentialité et de conformité liées à la publication ou à la mise à disposition sont définies et comprises."
 }
diff --git a/src/data/method/fr/labels.resources.json b/src/data/method/fr/labels.resources.json
index a280efd..cb5ca85 100644
--- a/src/data/method/fr/labels.resources.json
+++ b/src/data/method/fr/labels.resources.json
@@ -1,373 +1,373 @@
 {
-  "resource.api-community-engagement-strategies.title": "Stratégies d'engagement de la communauté de l’API",
+  "resource.api-community-engagement-strategies.title": "Stratégies d'engagement de la communauté de l'API",
   "resource.api-community-engagement-strategies.description": "Un guide pour favoriser l'adoption des API en cultivant des communautés grâce à des contenus, des canaux d'assistance, des boucles de retour d'information et des stratégies d'engagement social.",
-  "resource.api-community-engagement-strategies.outcomes": "Meilleure compréhension des principes des stratégies d'engagement communautaire de l’API",
+  "resource.api-community-engagement-strategies.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Stratégies d'engagement de la communauté de l'API »",
   "resource.api-community-engagement-strategies.steps": "Élaborer des stratégies de marketing pour promouvoir les API auprès des publics cibles, y compris les médias sociaux, les blogs et les webinaires.",
   "resource.api-community-engagement-strategies.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-compliance-best-practices.title": "Meilleures pratiques en matière de conformité de l’API",
+  "resource.api-compliance-best-practices.title": "Meilleures pratiques en matière de conformité de l'API",
   "resource.api-compliance-best-practices.description": "Veiller à ce que les API respectent la conformité légale, réglementaire et interne grâce à la documentation, aux contrôles et aux validations automatisées.",
-  "resource.api-compliance-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de conformité des API",
-  "resource.api-compliance-best-practices.steps": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux utilisateurs.",
+  "resource.api-compliance-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de conformité de l'API »",
+  "resource.api-compliance-best-practices.steps": "Documenter les mesures de conformité et veiller à ce qu'elles soient communiquées aux parties prenantes et aux consommateurs.",
   "resource.api-compliance-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-development-best-practices.title": "Meilleures pratiques en matière de développement d’API",
-  "resource.api-development-best-practices.description": "Guide de mise en œuvre visant à transformer un contrat d’interface API validé en une base de code API cohérente et maintenable, à l’aide de bibliothèques standard, de patterns réutilisables et de workflows de développement harmonisés.",
-  "resource.api-development-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de développement d’API",
-  "resource.api-development-best-practices.steps": "Appliquer ces bonnes pratiques au contrat d’interface API validé et au plan de mise en œuvre avant de commencer le codage.",
+  "resource.api-development-best-practices.title": "Meilleures pratiques en matière de développement d'API",
+  "resource.api-development-best-practices.description": "Guide de mise en œuvre pour transformer un contrat d’interface API validé en une base de code API cohérente et maintenable, à l’aide de bibliothèques standard, de modèles réutilisables et de workflows de développement harmonisés.",
+  "resource.api-development-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de développement d'API »",
+  "resource.api-development-best-practices.steps": "Appliquez ces pratiques au contrat d’interface API validé et au plan de mise en œuvre avant de commencer le développement.",
   "resource.api-development-best-practices.tips": "Utilisez cette ressource comme guide de mise en œuvre et outil d'évaluation plutôt que comme un artefact autonome obligatoire",
-  "resource.api-metrics-and-analytics.title": "Mesures et analyses de l’API",
-  "resource.api-metrics-and-analytics.description": "Une ressource pour définir, collecter et analyser les performances de l’API et les données d’utilisation afin d’aligner les KPI techniques sur les résultats métier.",
-  "resource.api-metrics-and-analytics.outcomes": "Meilleure compréhension des métriques API et des principes d'analyse",
-  "resource.api-metrics-and-analytics.steps": "Identifier les indicateurs clés de performance (KPI) pour mesurer la réussite de l’API par rapport aux objectifs métier.",
+  "resource.api-metrics-and-analytics.title": "Mesures et analyses de l'API",
+  "resource.api-metrics-and-analytics.description": "Une ressource pour définir, collecter et analyser les performances de l'API et les données d'utilisation afin d'aligner les KPI techniques sur les résultats de l'entreprise.",
+  "resource.api-metrics-and-analytics.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Mesures et analyses de l'API »",
+  "resource.api-metrics-and-analytics.steps": "Identifier les indicateurs clés de performance (KPI) pour mesurer la réussite de l'API par rapport aux objectifs de l'entreprise.",
   "resource.api-metrics-and-analytics.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-onboarding-best-practices.title": "Meilleures pratiques en matière d’intégration de l’API",
-  "resource.api-onboarding-best-practices.description": "Bonnes pratiques pour rationaliser les parcours d’onboarding des utilisateurs API avec inscription étape par étape, découverte et guidage du premier appel.",
-  "resource.api-onboarding-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d’intégration de l’API",
-  "resource.api-onboarding-best-practices.steps": "Définir le parcours de l’utilisateur API, de la découverte au dépannage, en identifiant les points de contact clés et les irritants.",
+  "resource.api-onboarding-best-practices.title": "Meilleures pratiques en matière d'intégration de l'API",
+  "resource.api-onboarding-best-practices.description": "Meilleures pratiques pour rationaliser les parcours d'accueil des consommateurs d'API avec une inscription étape par étape, une découverte et des conseils pour le premier appel.",
+  "resource.api-onboarding-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière d'intégration de l'API »",
+  "resource.api-onboarding-best-practices.steps": "Définir le parcours du consommateur d'API, de la découverte au dépannage, en identifiant les points de contact clés et les points douloureux.",
   "resource.api-onboarding-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-portfolio-management-guidelines.title": "Lignes directrices pour la gestion du portefeuille de l’API",
-  "resource.api-portfolio-management-guidelines.description": "Un guide pour gérer stratégiquement la suite d’API d'une organisation - en donnant la priorité aux API, en allouant des ressources et en contrôlant les performances tout au long du cycle de vie.",
-  "resource.api-portfolio-management-guidelines.outcomes": "Meilleure compréhension des principes directeurs de la gestion du portefeuille de l’API",
-  "resource.api-portfolio-management-guidelines.steps": "Définir des pratiques de gestion de portefeuille qui décrivent les processus de gestion du portefeuille d’API, y compris l'établissement de priorités, le suivi et l'optimisation.",
+  "resource.api-portfolio-management-guidelines.title": "Lignes directrices pour la gestion du portefeuille de l'API",
+  "resource.api-portfolio-management-guidelines.description": "Un guide pour gérer stratégiquement la suite d'API d'une organisation - en donnant la priorité aux API, en allouant des ressources et en contrôlant les performances tout au long du cycle de vie.",
+  "resource.api-portfolio-management-guidelines.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Lignes directrices pour la gestion du portefeuille de l'API »",
+  "resource.api-portfolio-management-guidelines.steps": "Définir des pratiques de gestion de portefeuille qui décrivent les processus de gestion du portefeuille d'API, y compris l'établissement de priorités, le suivi et l'optimisation.",
   "resource.api-portfolio-management-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.api-security-best-practices.title": "Meilleures pratiques en matière de sécurité des API",
   "resource.api-security-best-practices.description": "Un ensemble de contrôles exploitables pour sécuriser les API, y compris l'authentification, l'autorisation, le cryptage, la limitation du débit et les contrôles de conformité au niveau du pipeline.",
-  "resource.api-security-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de sécurité des API",
+  "resource.api-security-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de sécurité des API »",
   "resource.api-security-best-practices.steps": "S'assurer que les API répondent aux exigences de sécurité et de conformité grâce à des contrôles et des audits automatisés.",
   "resource.api-security-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-team-structure-guidelines.title": "Lignes directrices relatives à la structure des équipes de l’API",
+  "resource.api-team-structure-guidelines.title": "Lignes directrices relatives à la structure des équipes de l'API",
   "resource.api-team-structure-guidelines.description": "Orientation organisationnelle pour définir les rôles et les responsabilités au sein des équipes API afin de garantir la clarté, la collaboration et la responsabilité.",
-  "resource.api-team-structure-guidelines.outcomes": "Meilleure compréhension des principes directeurs de la structure de l'équipe API",
+  "resource.api-team-structure-guidelines.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Lignes directrices relatives à la structure des équipes de l'API »",
   "resource.api-team-structure-guidelines.steps": "Définir les structures et les rôles des équipes API, y compris les propriétaires de produits API, les développeurs, les architectes et les opérations.",
   "resource.api-team-structure-guidelines.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-testing-best-practices.title": "Meilleures pratiques de test de l’API",
-  "resource.api-testing-best-practices.description": "Lignes directrices pour la mise en œuvre de tests fonctionnels, de performance et de sécurité automatisés tout au long du cycle de vie de l’API.",
-  "resource.api-testing-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de tests d’API",
+  "resource.api-testing-best-practices.title": "Meilleures pratiques de test de l'API",
+  "resource.api-testing-best-practices.description": "Lignes directrices pour la mise en œuvre de tests fonctionnels, de performance et de sécurité automatisés tout au long du cycle de vie de l'API.",
+  "resource.api-testing-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques de test de l'API »",
   "resource.api-testing-best-practices.steps": "Tester les fonctionnalités, la sécurité et les performances des API à l'aide d'outils de test automatisés.",
   "resource.api-testing-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-training-programs.title": "Programmes de formation de l’API",
+  "resource.api-training-programs.title": "Programmes de formation de l'API",
   "resource.api-training-programs.description": "Une feuille de route pour l'amélioration des compétences des équipes avec des parcours d'apprentissage structurés en matière de conception, de gouvernance, de performance et de sécurité des API.",
-  "resource.api-training-programs.outcomes": "Meilleure compréhension des principes des programmes de formation de l’API",
-  "resource.api-training-programs.steps": "Identifier les compétences et les connaissances clés en matière d’API qui doivent être améliorées, telles que la conception, la sécurité et les performances des API.",
+  "resource.api-training-programs.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Programmes de formation de l'API »",
+  "resource.api-training-programs.steps": "Identifier les compétences et les connaissances clés en matière d'API qui doivent être améliorées, telles que la conception, la sécurité et les performances des API.",
   "resource.api-training-programs.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-versioning-best-practices.title": "Meilleures pratiques en matière de versionnement de l’API",
-  "resource.api-versioning-best-practices.description": "Stratégies pour introduire, maintenir et retirer des versions d’API tout en préservant la rétrocompatibilité et la confiance des utilisateurs.",
-  "resource.api-versioning-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de versions d’API",
+  "resource.api-versioning-best-practices.title": "Meilleures pratiques en matière de versionnement de l'API",
+  "resource.api-versioning-best-practices.description": "Stratégies d'introduction, de maintenance et de retrait des versions de l'API tout en préservant la compatibilité ascendante et la confiance des consommateurs.",
+  "resource.api-versioning-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de versionnement de l'API »",
   "resource.api-versioning-best-practices.steps": "Définir des stratégies de versionnement pour les API afin de gérer les changements et d'assurer la compatibilité ascendante.",
   "resource.api-versioning-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.description": "Conseils de mise à disposition qui intègrent les tâches du cycle de vie de l’API - conception, test, gouvernance - dans les pipelines d’intégration et de livraison en continu.",
-  "resource.apiops-CI-CD-for-apis.outcomes": "Meilleure compréhension des principes CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.steps": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de mise à disposition, en garantissant une qualité et une traçabilité constantes.",
+  "resource.apiops-CI-CD-for-apis.description": "Des conseils de déploiement qui intègrent les tâches du cycle de vie de l'API - conception, test, gouvernance - dans les pipelines d'intégration et de livraison en continu.",
+  "resource.apiops-CI-CD-for-apis.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « APIOps CI/CD pour les API »",
+  "resource.apiops-CI-CD-for-apis.steps": "Utiliser les pipelines CI/CD pour automatiser les processus de construction, de test et de déploiement, en garantissant une qualité et une traçabilité constantes.",
   "resource.apiops-CI-CD-for-apis.tips": "Adaptez cette ressource à votre contexte.",
   "resource.competitor-analysis-template.title": "Modèle d'analyse des concurrents",
-  "resource.competitor-analysis-template.description": "Une feuille de travail structurée pour comparer vos offres d’API à celles de vos concurrents en identifiant les forces, les faiblesses et les différentiateurs de valeur.",
-  "resource.competitor-analysis-template.outcomes": "Meilleure compréhension des principes du modèle d'analyse de la concurrence",
-  "resource.competitor-analysis-template.steps": "Effectuer une analyse concurrentielle afin d'identifier les principaux concurrents et leurs offres d’API.",
+  "resource.competitor-analysis-template.description": "Une feuille de travail structurée pour comparer vos offres d'API à celles de vos concurrents en identifiant les forces, les faiblesses et les différentiateurs de valeur.",
+  "resource.competitor-analysis-template.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Modèle d'analyse des concurrents »",
+  "resource.competitor-analysis-template.steps": "Effectuer une analyse concurrentielle afin d'identifier les principaux concurrents et leurs offres d'API.",
   "resource.competitor-analysis-template.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.contract-first-design.title": "Conception contract-first",
+  "resource.contract-first-design.title": "Contrat de première conception",
   "resource.contract-first-design.description": "Une ligne directrice qui préconise des approches \"API-first\" utilisant des contrats formels (par exemple, OpenAPI) pour aligner les parties prenantes avant le développement.",
-  "resource.contract-first-design.outcomes": "Meilleure compréhension des principes de conception du contrat d'abord",
-  "resource.contract-first-design.steps": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d’API sont validés avant leur mise en œuvre.",
+  "resource.contract-first-design.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Contrat de première conception »",
+  "resource.contract-first-design.steps": "Appliquer des approches de type \"contrat d'abord\" ou \"conception d'abord\" pour s'assurer que les contrats d'API sont validés avant leur mise en œuvre.",
   "resource.contract-first-design.tips": "Adaptez cette ressource à votre contexte.",
   "resource.cross-functional-collaboration-best-practices.title": "Meilleures pratiques en matière de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.description": "Pratiques visant à faciliter la communication et l’alignement entre les rôles métier et techniques lors de la planification ou de la mise à disposition d’API.",
-  "resource.cross-functional-collaboration-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.steps": "Encourager la collaboration interfonctionnelle entre les équipes API, les unités métier et les parties prenantes afin d’aligner les initiatives API sur les objectifs métier.",
+  "resource.cross-functional-collaboration-best-practices.description": "Pratiques visant à faciliter la communication et l'alignement entre les équipes commerciales et techniques lors de la planification ou de la fourniture d'API.",
+  "resource.cross-functional-collaboration-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de collaboration interfonctionnelle »",
+  "resource.cross-functional-collaboration-best-practices.steps": "Encourager la collaboration interfonctionnelle entre les équipes API, les unités opérationnelles et les parties prenantes afin d'aligner les initiatives API sur les objectifs de l'entreprise.",
   "resource.cross-functional-collaboration-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.data-privacy-guidelines.title": "Lignes directrices sur la protection des données",
   "resource.data-privacy-guidelines.description": "Les considérations de conception pour s'assurer que les API respectent les réglementations sur la protection des données comme le GDPR grâce à l'anonymisation et aux contrôles d'accès.",
-  "resource.data-privacy-guidelines.outcomes": "Meilleure compréhension des lignes directrices de protection des données",
-  "resource.data-privacy-guidelines.steps": "Garantir la protection des données des utilisateurs en mettant en œuvre des mesures telles que l’anonymisation et les contrôles d’accès.",
+  "resource.data-privacy-guidelines.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Lignes directrices sur la protection des données »",
+  "resource.data-privacy-guidelines.steps": "Garantir la confidentialité des données des utilisateurs en mettant en œuvre des mesures de protection des données, telles que l'anonymisation et les contrôles d'accès.",
   "resource.data-privacy-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.domain-canvas.title": "Domain Canvas",
-  "resource.domain-canvas.description": "Outil de modélisation pour définir les concepts, entités, relations et règles du domaine métier, afin d’assurer la cohérence sémantique entre capacités, interfaces et intégrations.",
-  "resource.domain-canvas.outcomes": "Meilleure compréhension des principes du domain canvas",
+  "resource.domain-canvas.description": "Un outil de modélisation pour définir et communiquer les entités et les relations clés de votre domaine, en assurant la cohérence sémantique entre les API.",
+  "resource.domain-canvas.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Domain Canvas »",
   "resource.domain-canvas.steps": "Définir les entités de base, leurs attributs et leurs relations afin de créer une compréhension conceptuelle partagée entre les API.",
   "resource.domain-canvas.tips": "Adaptez cette ressource à votre contexte.",
   "resource.ecosystem-vision-template.title": "Modèle de vision de l'écosystème",
-  "resource.ecosystem-vision-template.description": "Un outil de planification stratégique pour définir l'écosystème de l’API, y compris les partenaires cibles, les chaînes de valeur et les possibilités d’intégration.",
-  "resource.ecosystem-vision-template.outcomes": "Meilleure compréhension des principes du modèle de vision de l'écosystème",
+  "resource.ecosystem-vision-template.description": "Un outil de planification stratégique pour définir l'écosystème de l'API, y compris les partenaires cibles, les chaînes de valeur et les possibilités d'intégration.",
+  "resource.ecosystem-vision-template.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Modèle de vision de l'écosystème »",
   "resource.ecosystem-vision-template.steps": "Réaliser des études de marché pour identifier les tendances, les opportunités et les menaces dans le domaine des API.",
   "resource.ecosystem-vision-template.tips": "Adaptez cette ressource à votre contexte.",
   "resource.industry-standards-and-best-practices.title": "Normes industrielles et meilleures pratiques",
-  "resource.industry-standards-and-best-practices.description": "Une ressource de référence pour aligner la conception et le fonctionnement de l’API sur des cadres et des spécifications largement reconnus dans l'industrie.",
-  "resource.industry-standards-and-best-practices.outcomes": "Meilleure compréhension des normes du secteur et des principes des meilleures pratiques",
+  "resource.industry-standards-and-best-practices.description": "Une ressource de référence pour aligner la conception et le fonctionnement de l'API sur des cadres et des spécifications largement reconnus dans l'industrie.",
+  "resource.industry-standards-and-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Normes industrielles et meilleures pratiques »",
   "resource.industry-standards-and-best-practices.steps": "Identifier les normes et les meilleures pratiques du secteur pour s'assurer que les API sont compétitives et conformes.",
   "resource.industry-standards-and-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.partner-integration-guidelines.title": "Lignes directrices pour l’intégration des partenaires",
-  "resource.partner-integration-guidelines.description": "Listes de contrôle de l’intégration et modèles de communication pour gérer les aspects techniques et juridiques des relations avec des API tierces.",
-  "resource.partner-integration-guidelines.outcomes": "Meilleure compréhension des principes directeurs de l’intégration des partenaires",
-  "resource.partner-integration-guidelines.steps": "Établir des processus d’intégration et des lignes directrices pour la collaboration avec les partenaires, y compris l’intégration technique, le partage des données et le soutien.",
+  "resource.partner-integration-guidelines.title": "Lignes directrices pour l'intégration des partenaires",
+  "resource.partner-integration-guidelines.description": "Listes de contrôle de l'intégration et modèles de communication pour gérer les aspects techniques et juridiques des relations avec des API tierces.",
+  "resource.partner-integration-guidelines.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Lignes directrices pour l'intégration des partenaires »",
+  "resource.partner-integration-guidelines.steps": "Établir des processus d'intégration et des lignes directrices pour la collaboration avec les partenaires, y compris l'intégration technique, le partage des données et le soutien.",
   "resource.partner-integration-guidelines.tips": "Adaptez cette ressource à votre contexte.",
   "resource.role-communication-best-practices.title": "Meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.description": "Outils permettant de définir et de clarifier les responsabilités dans les initiatives API, afin de garantir des passages de relais et des responsabilités explicites.",
-  "resource.role-communication-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.steps": "Établir des responsabilités claires pour chaque rôle, notamment en ce qui concerne la conception, le développement, les tests et les opérations de l’API.",
+  "resource.role-communication-best-practices.description": "Outils permettant de définir et de documenter les responsabilités de chacun dans le cadre des initiatives API, afin de garantir la clarté des transferts et des responsabilités.",
+  "resource.role-communication-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière de communication sur les rôles »",
+  "resource.role-communication-best-practices.steps": "Établir des responsabilités claires pour chaque rôle, notamment en ce qui concerne la conception, le développement, les tests et les opérations de l'API.",
   "resource.role-communication-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.scalable-infrastructure-best-practices.title": "Meilleures pratiques en matière d'infrastructure évolutive",
   "resource.scalable-infrastructure-best-practices.description": "Des conseils architecturaux pour s'assurer que les API sont déployées sur une infrastructure capable de gérer avec élasticité les pics d'utilisation et la croissance.",
-  "resource.scalable-infrastructure-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d'infrastructure évolutive",
-  "resource.scalable-infrastructure-best-practices.steps": "Concevoir une infrastructure d’API évolutive et résiliente, en utilisant des modèles et des technologies \"cloud-native\".",
+  "resource.scalable-infrastructure-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière d'infrastructure évolutive »",
+  "resource.scalable-infrastructure-best-practices.steps": "Concevoir une infrastructure d'API évolutive et résiliente, en utilisant des modèles et des technologies \"cloud-native\".",
   "resource.scalable-infrastructure-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.service-agreement-template.title": "Modèle de contrat de service",
-  "resource.service-agreement-template.description": "Un format d’accord personnalisable qui définit les attentes, les accords de niveau de service, les responsabilités et les conditions d’accès pour l’utilisation d’API.",
-  "resource.service-agreement-template.outcomes": "Meilleure compréhension des principes du modèle d'accord de service",
+  "resource.service-agreement-template.description": "Un format d'accord personnalisable qui définit les attentes, les accords de niveau de service, les responsabilités et les conditions d'accès pour la consommation d'API.",
+  "resource.service-agreement-template.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Modèle de contrat de service »",
   "resource.service-agreement-template.steps": "Définir des accords de service qui décrivent les attentes, les niveaux de service et les responsabilités pour chaque API.",
   "resource.service-agreement-template.tips": "Adaptez cette ressource à votre contexte.",
   "resource.stakeholder-engagement-best-practices.title": "Meilleures pratiques en matière d'engagement des parties prenantes",
-  "resource.stakeholder-engagement-best-practices.description": "Tactiques d'engagement pour aligner les parties prenantes internes et externes sur les objectifs, la valeur et la gouvernance partagés de l’API.",
-  "resource.stakeholder-engagement-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière d'engagement des parties prenantes",
+  "resource.stakeholder-engagement-best-practices.description": "Tactiques d'engagement pour aligner les parties prenantes internes et externes sur les objectifs, la valeur et la gouvernance partagés de l'API.",
+  "resource.stakeholder-engagement-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques en matière d'engagement des parties prenantes »",
   "resource.stakeholder-engagement-best-practices.steps": "Engager les parties prenantes pour assurer l'alignement et le soutien des initiatives API.",
   "resource.stakeholder-engagement-best-practices.tips": "Adaptez cette ressource à votre contexte.",
   "resource.test-automation-frameworks.title": "Cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.description": "Outils et modèles recommandés pour automatiser les tests de contrat, de régression et d’intégration des API dans les différents environnements.",
-  "resource.test-automation-frameworks.outcomes": "Meilleure compréhension des principes des cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.steps": "Mettre en œuvre des cadres d'automatisation des tests qui prennent en charge les tests de contrat, les tests d’intégration et les tests de bout en bout.",
+  "resource.test-automation-frameworks.description": "Outils et modèles recommandés pour automatiser les tests de contrat, de régression et d'intégration des API dans les différents environnements.",
+  "resource.test-automation-frameworks.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Cadres d'automatisation des tests »",
+  "resource.test-automation-frameworks.steps": "Mettre en œuvre des cadres d'automatisation des tests qui prennent en charge les tests de contrat, les tests d'intégration et les tests de bout en bout.",
   "resource.test-automation-frameworks.tips": "Adaptez cette ressource à votre contexte.",
   "resource.vendor-management-best-practices.title": "Meilleures pratiques de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.description": "Cadre pour l'évaluation et la gestion des fournisseurs d’API externes et des intégrations de tiers en fonction des risques, des performances et de la conformité.",
-  "resource.vendor-management-best-practices.outcomes": "Meilleure compréhension des principes des meilleures pratiques en matière de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.steps": "Mettre en place des processus de gestion des fournisseurs afin d'évaluer, d'intégrer et de contrôler les fournisseurs d’API tiers.",
+  "resource.vendor-management-best-practices.description": "Cadre pour l'évaluation et la gestion des fournisseurs d'API externes et des intégrations de tiers en fonction des risques, des performances et de la conformité.",
+  "resource.vendor-management-best-practices.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Meilleures pratiques de gestion des fournisseurs »",
+  "resource.vendor-management-best-practices.steps": "Mettre en place des processus de gestion des fournisseurs afin d'évaluer, d'intégrer et de contrôler les fournisseurs d'API tiers.",
   "resource.vendor-management-best-practices.tips": "Adaptez cette ressource à votre contexte.",
-  "resource.api-audit-checklist.title": "Liste de contrôle de l'audit de l’API",
-  "resource.api-audit-checklist.description": "Une liste de contrôle basée sur le cycle de vie permettant de vérifier l'état de préparation de l’API à travers les phases de conception, de livraison, de publication et de conformité à l'aide de critères d'audit et de preuves définis.",
-  "resource.api-audit-checklist.outcomes": "Meilleure compréhension des principes de la liste de contrôle de l'audit de l’API",
-  "resource.api-audit-checklist.steps": "Utilisez la liste de contrôle de l'audit de l’API pour vous assurer que la conception de l’API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
-  "resource.api-audit-checklist.tips": "Chaque élément d'audit relie les tâches du cycle de vie (étapes), les directives applicables et les preuves à l'appui afin de fournir une vision claire de l'état de préparation de l’API.",
+  "resource.api-audit-checklist.title": "Liste de contrôle de l'audit de l'API",
+  "resource.api-audit-checklist.description": "Une liste de contrôle basée sur le cycle de vie permettant de vérifier l'état de préparation de l'API à travers les phases de conception, de livraison, de publication et de conformité à l'aide de critères d'audit et de preuves définis.",
+  "resource.api-audit-checklist.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Liste de contrôle de l'audit de l'API »",
+  "resource.api-audit-checklist.steps": "Utilisez la liste de contrôle de l'audit de l'API pour vous assurer que la conception de l'API répond aux exigences fonctionnelles et non fonctionnelles, notamment en matière de sécurité, de performances et de conformité.",
+  "resource.api-audit-checklist.tips": "Chaque élément d'audit relie les tâches du cycle de vie (étapes), les directives applicables et les preuves à l'appui afin de fournir une vision claire de l'état de préparation de l'API.",
   "resource.api-business-model-canvas.title": "API Business Model Canvas",
-  "resource.api-business-model-canvas.description": "Évaluer stratégiquement la viabilité du modèle API en cartographiant les propositions de valeur, les segments d’utilisateurs et les ressources clés.",
-  "resource.api-business-model-canvas.outcomes": "Stratégie métier claire pour les API",
-  "resource.api-business-model-canvas.steps": "Résumer la proposition de valeur de l’API",
+  "resource.api-business-model-canvas.description": "Évaluer stratégiquement la viabilité de l'activité API en établissant une cartographie des propositions de valeur, des segments de consommateurs et des ressources clés.",
+  "resource.api-business-model-canvas.outcomes": "Une stratégie commerciale claire pour les API",
+  "resource.api-business-model-canvas.steps": "Résumer la proposition de valeur de l'API",
   "resource.api-business-model-canvas.tips": "Commencer par une seule API pour plus de clarté",
-  "resource.api-design-principles.title": "Principes de conception de l’API",
-  "resource.api-design-principles.description": "Un guide concis sur l’ergonomie, la découvrabilité et la cohérence des API, fondé sur des règles de conception communes et les besoins réels des utilisateurs.",
-  "resource.api-design-principles.outcomes": "Meilleure compréhension des principes de conception des API",
-  "resource.api-design-principles.steps": "**Conception centrée utilisateur :** commencer chaque cycle APIOps en rassemblant les objectifs des utilisateurs et les termes du domaine métier afin que les API résolvent des problèmes réels.",
+  "resource.api-design-principles.title": "Principes de conception de l'API",
+  "resource.api-design-principles.description": "Un guide concis sur l'ergonomie, la facilité de découverte et la cohérence des API, fondé sur des règles de conception communes et les besoins réels des consommateurs.",
+  "resource.api-design-principles.outcomes": "Compréhension partagée de l’objectif et de l’utilisation de « Principes de conception de l'API »",
+  "resource.api-design-principles.steps": "**Consumer-first design:** commencer chaque cycle APIOps en rassemblant les objectifs des utilisateurs et les termes du domaine afin que les APIs résolvent des problèmes réels.",
   "resource.api-design-principles.tips": "Adaptez cette ressource à votre contexte.",
   "resource.api-value-proposition-canvas.title": "API Value Proposition Canvas",
-  "resource.api-value-proposition-canvas.description": "Aligner les fonctionnalités de l’API sur les besoins des utilisateurs en reliant les tâches, irritants et gains aux produits API.",
+  "resource.api-value-proposition-canvas.description": "Aligner les fonctionnalités de l'API sur les besoins des utilisateurs en établissant une correspondance entre les tâches, les douleurs et les gains et les produits de l'API.",
   "resource.api-value-proposition-canvas.outcomes": "Développement de fonctionnalités ciblées",
-  "resource.api-value-proposition-canvas.steps": "Liste des tâches liées au parcours de l’utilisateur",
+  "resource.api-value-proposition-canvas.steps": "Liste des tâches liées au parcours de l'utilisateur",
   "resource.api-value-proposition-canvas.tips": "Utiliser les données du Customer Journey Canvas",
   "resource.business-impact-canvas.title": "Business Impact Canvas",
-  "resource.business-impact-canvas.description": "Identifie les impacts métier, données, sécurité, disponibilité et opérations avant de choisir le mode de mise en œuvre.",
-  "resource.business-impact-canvas.outcomes": "Infrastructure API évolutive",
+  "resource.business-impact-canvas.description": "Identifiez les risques métier, de disponibilité, de sécurité, de données, de conformité et d’exploitation qui doivent orienter les décisions d’architecture et de plateforme.",
+  "resource.business-impact-canvas.outcomes": "Évaluation documentée des impacts métier et opérationnels",
   "resource.business-impact-canvas.steps": "Risques liés à la disponibilité : Identifier les risques et les impacts.",
-  "resource.business-impact-canvas.tips": "Impliquer les architectes et les développeurs dans le processus de conception.",
+  "resource.business-impact-canvas.tips": "Complétez ce canvas avant de sélectionner ou de confirmer le mode de mise en œuvre.",
   "resource.capacity-canvas.title": "Capacity Canvas",
-  "resource.capacity-canvas.description": "Planifier la capacité nécessaire pour soutenir les volumes actuels et futurs d’une capacité, d’une interface ou d’un mode de mise en œuvre, en garantissant l’évolutivité et la performance.",
-  "resource.capacity-canvas.outcomes": "Capacité alignée sur les volumes métier et les modes d’usage attendus",
-  "resource.capacity-canvas.steps": "Documenter les volumes métier actuels",
-  "resource.capacity-canvas.tips": "Utiliser l'analyse pour prévoir les tendances de la croissance",
+  "resource.capacity-canvas.description": "Planifiez la capacité pour la demande actuelle et future, notamment les volumes, les pics, la latence, la disponibilité, la mise à l’échelle, la mise en cache et la limitation de débit pour la capacité et le mode de mise en œuvre choisis.",
+  "resource.capacity-canvas.outcomes": "Exigences de capacité alignées sur la demande métier attendue",
+  "resource.capacity-canvas.steps": "Documenter les volumes d'affaires actuels",
+  "resource.capacity-canvas.tips": "Complétez ce canvas avant de finaliser les décisions d’architecture et de plateforme.",
   "resource.customer-journey-canvas.title": "Customer Journey Canvas",
-  "resource.customer-journey-canvas.description": "Cartographier les parcours des clients ou utilisateurs pour identifier les besoins et irritants, afin d’améliorer la conception de la capacité et de l’interface.",
-  "resource.customer-journey-canvas.outcomes": "Meilleure compréhension du parcours client ou utilisateur",
+  "resource.customer-journey-canvas.description": "Cartographier les parcours des clients pour identifier les besoins et les points de douleur, afin d'améliorer la conception de l'API et l'expérience de l'utilisateur.",
+  "resource.customer-journey-canvas.outcomes": "Compréhension partagée du parcours client, partenaire ou utilisateur",
   "resource.customer-journey-canvas.steps": "Définir le profil du client",
-  "resource.customer-journey-canvas.tips": "Répéter avec l'aide de l'équipe pour affiner les étapes",
+  "resource.customer-journey-canvas.tips": "Validez le parcours avec les personnes qui le réalisent ou le vivent.",
   "resource.event-canvas.title": "Event Canvas",
-  "resource.event-canvas.description": "Concevoir des API pilotées par les événements en définissant les événements, les déclencheurs et la logique de traitement.",
-  "resource.event-canvas.outcomes": "Architecture événementielle définie",
+  "resource.event-canvas.description": "Concevez des interfaces et intégrations événementielles en définissant les événements, déclencheurs, schémas, producteurs, utilisateurs et logiques de traitement.",
+  "resource.event-canvas.outcomes": "Modèle d’interaction événementiel défini",
   "resource.event-canvas.steps": "Identifier les événements clés du système",
   "resource.event-canvas.tips": "Utiliser des schémas d'événements pour normaliser les formats d'événements",
   "resource.graphql-canvas.title": "GraphQL Canvas",
   "resource.graphql-canvas.description": "Concevoir des API GraphQL en définissant des types, des requêtes, des mutations et des abonnements.",
   "resource.graphql-canvas.outcomes": "Conception d'une API GraphQL structurée",
-  "resource.graphql-canvas.steps": "Quels problèmes les utilisateurs API tentent-ils de résoudre ? De quelles données ont-ils besoin ?",
+  "resource.graphql-canvas.steps": "Quels sont les problèmes que les consommateurs d'API tentent de résoudre ? De quelles données ont-ils besoin ?",
   "resource.graphql-canvas.tips": "Utiliser l'introspection pour valider les définitions de type",
   "resource.interaction-canvas.title": "Interaction Canvas",
-  "resource.interaction-canvas.description": "Définir les interactions, workflows et réponses attendues afin de garantir une expérience cohérente pour les utilisateurs de la capacité ou de l’interface.",
-  "resource.interaction-canvas.outcomes": "Des flux de travail clairs pour les interactions avec l’API",
-  "resource.interaction-canvas.steps": "Associer les interactions de l’API aux tâches de l’utilisateur",
+  "resource.interaction-canvas.description": "Définir les interactions API, les flux de travail et les réponses attendues afin de garantir une expérience cohérente pour les consommateurs d'API.",
+  "resource.interaction-canvas.outcomes": "Modèle d’interaction défini pour la capacité choisie",
+  "resource.interaction-canvas.steps": "Associer les interactions de l'API aux tâches de l'utilisateur",
   "resource.interaction-canvas.tips": "Commencer par les cas d'utilisation courants avant de traiter les cas marginaux",
   "resource.location-canvas.title": "Location Canvas",
-  "resource.location-canvas.description": "Cartographier les emplacements des fournisseurs et des utilisateurs pour garantir conformité, connectivité et performance entre régions.",
-  "resource.location-canvas.outcomes": "Respect des réglementations locales",
-  "resource.location-canvas.steps": "Carte des emplacements des fournisseurs d’API.",
+  "resource.location-canvas.description": "Cartographier les emplacements des fournisseurs d'API et des consommateurs pour garantir la conformité et les performances dans toutes les régions.",
+  "resource.location-canvas.outcomes": "Exigences de localisation, de résidence des données, de réseau et de réglementation documentées",
+  "resource.location-canvas.steps": "Carte des emplacements des fournisseurs d'API.",
   "resource.location-canvas.tips": "Collaborer avec les équipes juridiques et de conformité",
   "resource.rest-canvas.title": "REST Canvas",
   "resource.rest-canvas.description": "Concevoir des API en utilisant les principes RESTful, en définissant des ressources, des verbes et des exemples de requêtes et de réponses.",
-  "resource.rest-canvas.outcomes": "Conception cohérente de l’API RESTful",
-  "resource.rest-canvas.steps": "Identifier les ressources clés exposées par l’API",
+  "resource.rest-canvas.outcomes": "Conception cohérente de l'API RESTful",
+  "resource.rest-canvas.steps": "Identifier les ressources clés exposées par l'API",
   "resource.rest-canvas.tips": "Utiliser les méthodes HTTP standard (GET, POST, PUT, DELETE)",
-  "resource.api-community-engagement-strategies.outcomes.1": "Approche standardisée utilisant les stratégies d'engagement communautaire de l’API",
-  "resource.api-community-engagement-strategies.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-community-engagement-strategies.outcomes.1": "Approche cohérente pour appliquer « Stratégies d'engagement de la communauté de l'API »",
+  "resource.api-community-engagement-strategies.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-community-engagement-strategies.steps.1": "Créer du matériel promotionnel (par exemple, des études de cas, des exemples de réussite) qui met en évidence la valeur et les avantages des API.",
-  "resource.api-community-engagement-strategies.steps.2": "Créer des supports pédagogiques (par exemple, des tutoriels, de la documentation) qui expliquent les caractéristiques, les avantages et les modes d'utilisation de l’API.",
-  "resource.api-community-engagement-strategies.steps.3": "Interagir avec les utilisateurs API par le biais de boucles de feedback, de canaux d’assistance et de forums communautaires afin de comprendre leurs besoins et d’améliorer l’adoption de l’API.",
-  "resource.api-community-engagement-strategies.steps.4": "Analyser les indicateurs d'utilisation de l’API et intégrer les commentaires des utilisateurs dans les itérations de l’API.",
-  "resource.api-community-engagement-strategies.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-compliance-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de conformité des API",
-  "resource.api-compliance-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-community-engagement-strategies.steps.2": "Créer des supports pédagogiques (par exemple, des tutoriels, de la documentation) qui expliquent les caractéristiques, les avantages et les modes d'utilisation de l'API.",
+  "resource.api-community-engagement-strategies.steps.3": "S'engager auprès des consommateurs d'API par le biais de boucles de retour d'information, de canaux d'assistance et de forums communautaires afin de comprendre leurs besoins et d'améliorer l'adoption de l'API.",
+  "resource.api-community-engagement-strategies.steps.4": "Analyser les indicateurs d'utilisation de l'API et intégrer les commentaires des utilisateurs dans les itérations de l'API.",
+  "resource.api-community-engagement-strategies.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-compliance-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de conformité de l'API »",
+  "resource.api-compliance-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-compliance-best-practices.steps.1": "Mettre en œuvre des mesures pour s'assurer que les API sont conformes à ces exigences, y compris le cryptage des données, les contrôles d'accès et les pistes d'audit.",
   "resource.api-compliance-best-practices.steps.2": "Utiliser des listes de contrôle, des linters et des outils de test pour vérifier la cohérence et la conformité avec les normes.",
-  "resource.api-compliance-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-development-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de développement d’API",
-  "resource.api-development-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-compliance-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-development-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de développement d'API »",
+  "resource.api-development-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-development-best-practices.steps.1": "Utilisez des frameworks, des bibliothèques et des normes de codage établis pour implémenter le contrat de manière cohérente et maintenable.",
-  "resource.api-development-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-metrics-and-analytics.outcomes.1": "Approche standardisée utilisant les métriques et l'analyse de l’API",
-  "resource.api-metrics-and-analytics.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-development-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-metrics-and-analytics.outcomes.1": "Approche cohérente pour appliquer « Mesures et analyses de l'API »",
+  "resource.api-metrics-and-analytics.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-metrics-and-analytics.steps.1": "Définir et surveiller les indicateurs de performance (par exemple, les appels API, la latence, les taux d'erreur) et les indicateurs d'adoption (par exemple, NPS).",
   "resource.api-metrics-and-analytics.steps.2": "Contrôler les initiatives API afin de garantir le respect des lignes directrices opérationnelles et des pratiques de gouvernance.",
-  "resource.api-metrics-and-analytics.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-onboarding-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de l’API Onboarding",
-  "resource.api-onboarding-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.api-onboarding-best-practices.steps.1": "Développer des processus et ressources d’onboarding pour aider les utilisateurs API à comprendre comment utiliser efficacement les API.",
-  "resource.api-onboarding-best-practices.steps.2": "Documenter la manière dont les utilisateurs trouvent et utilisent l’API, y compris les processus d’onboarding et d’enregistrement.",
-  "resource.api-onboarding-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices de gestion du portefeuille de l’API",
-  "resource.api-portfolio-management-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.api-portfolio-management-guidelines.steps.1": "Définir des pratiques de gestion du budget et des ressources qui décrivent les processus de gestion des budgets et des ressources pour les initiatives de l’API.",
-  "resource.api-portfolio-management-guidelines.steps.2": "Établir des critères d’évaluation et de priorisation des affectations budgétaires en fonction de la valeur métier, de l’impact et de l’alignement sur les initiatives stratégiques.",
-  "resource.api-portfolio-management-guidelines.steps.3": "Contrôler le portefeuille d’API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l’entreprise.",
-  "resource.api-portfolio-management-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-security-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de sécurité des API",
-  "resource.api-security-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-metrics-and-analytics.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-onboarding-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière d'intégration de l'API »",
+  "resource.api-onboarding-best-practices.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.api-onboarding-best-practices.steps.1": "Développer des processus et des ressources d'intégration pour aider les consommateurs d'API à comprendre comment utiliser efficacement les API.",
+  "resource.api-onboarding-best-practices.steps.2": "Documenter la manière dont les consommateurs trouvent et utilisent l'API, y compris les processus d'accueil et d'enregistrement.",
+  "resource.api-onboarding-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "Approche cohérente pour appliquer « Lignes directrices pour la gestion du portefeuille de l'API »",
+  "resource.api-portfolio-management-guidelines.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.api-portfolio-management-guidelines.steps.1": "Définir des pratiques de gestion du budget et des ressources qui décrivent les processus de gestion des budgets et des ressources pour les initiatives de l'API.",
+  "resource.api-portfolio-management-guidelines.steps.2": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur commerciale, de l'impact et de l'alignement sur les initiatives stratégiques.",
+  "resource.api-portfolio-management-guidelines.steps.3": "Contrôler le portefeuille d'API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l'entreprise.",
+  "resource.api-portfolio-management-guidelines.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-security-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de sécurité des API »",
+  "resource.api-security-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-security-best-practices.steps.1": "Mettre en œuvre des mesures de sécurité telles que l'authentification, l'autorisation, le cryptage et la limitation du débit pour protéger les API contre les menaces.",
   "resource.api-security-best-practices.steps.2": "Mettre en œuvre des contrôles de sécurité automatisés et des validations de conformité dans le pipeline CI/CD pour s'assurer que les API sont sécurisées et conformes.",
-  "resource.api-security-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-team-structure-guidelines.outcomes.1": "Approche normalisée à l'aide des lignes directrices sur la structure des équipes de l’API",
-  "resource.api-team-structure-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.api-team-structure-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-testing-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de test des API",
-  "resource.api-testing-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-security-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-team-structure-guidelines.outcomes.1": "Approche cohérente pour appliquer « Lignes directrices relatives à la structure des équipes de l'API »",
+  "resource.api-team-structure-guidelines.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.api-team-structure-guidelines.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-testing-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques de test de l'API »",
+  "resource.api-testing-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-testing-best-practices.steps.1": "Intégrer des tests fonctionnels et non fonctionnels dans le pipeline CI/CD pour s'assurer que les API répondent aux normes de qualité.",
-  "resource.api-testing-best-practices.steps.2": "Utiliser des outils de test automatisés pour valider les fonctionnalités, la sécurité et les performances de l’API.",
-  "resource.api-testing-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-training-programs.outcomes.1": "Approche normalisée à l'aide des programmes de formation de l’API",
-  "resource.api-training-programs.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-testing-best-practices.steps.2": "Utiliser des outils de test automatisés pour valider les fonctionnalités, la sécurité et les performances de l'API.",
+  "resource.api-testing-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-training-programs.outcomes.1": "Approche cohérente pour appliquer « Programmes de formation de l'API »",
+  "resource.api-training-programs.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-training-programs.steps.1": "Encourager la formation continue par des cours en ligne, des certifications et l'engagement communautaire.",
   "resource.api-training-programs.steps.2": "Fournir des formations et des ressources pour aider les équipes à adopter un état d'esprit \"API-first\" et à comprendre les avantages des API.",
-  "resource.api-training-programs.steps.3": "Fournir des programmes de formation, des ateliers et des ressources pour aider les équipes à améliorer leurs compétences et leurs connaissances en matière d’API.",
-  "resource.api-training-programs.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-versioning-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière de versionnement de l’API",
-  "resource.api-versioning-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.api-versioning-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.apiops-CI-CD-for-apis.outcomes.1": "Approche standardisée utilisant CI/CD pour les API",
-  "resource.apiops-CI-CD-for-apis.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.apiops-CI-CD-for-apis.steps.1": "Intégrer des tests automatisés dans le pipeline CI/CD pour assurer une validation continue de la qualité de l’API.",
-  "resource.apiops-CI-CD-for-apis.steps.2": "Mettre en œuvre des stratégies de mise à disposition (par exemple, blue-green ou canary releases) afin de minimiser les risques lors des mises à jour de l’API.",
+  "resource.api-training-programs.steps.3": "Fournir des programmes de formation, des ateliers et des ressources pour aider les équipes à améliorer leurs compétences et leurs connaissances en matière d'API.",
+  "resource.api-training-programs.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-versioning-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de versionnement de l'API »",
+  "resource.api-versioning-best-practices.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.api-versioning-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.apiops-CI-CD-for-apis.outcomes.1": "Approche cohérente pour appliquer « APIOps CI/CD pour les API »",
+  "resource.apiops-CI-CD-for-apis.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.apiops-CI-CD-for-apis.steps.1": "Intégrer des tests automatisés dans le pipeline CI/CD pour assurer une validation continue de la qualité de l'API.",
+  "resource.apiops-CI-CD-for-apis.steps.2": "Mettre en œuvre des stratégies de déploiement (par exemple, des déploiements \"bleu-vert\", des versions \"canari\") afin de minimiser les risques lors des mises à jour de l'API.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Prendre l'habitude d'examiner les mesures et de planifier des activités d'amélioration continue.",
-  "resource.apiops-CI-CD-for-apis.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.competitor-analysis-template.outcomes.1": "Approche standardisée à l'aide du modèle d'analyse des concurrents",
-  "resource.competitor-analysis-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.apiops-CI-CD-for-apis.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.competitor-analysis-template.outcomes.1": "Approche cohérente pour appliquer « Modèle d'analyse des concurrents »",
+  "resource.competitor-analysis-template.outcomes.2": "Meilleure application des pratiques associées",
   "resource.competitor-analysis-template.steps.1": "Analyser les API des concurrents pour comprendre leurs forces, leurs faiblesses et leurs arguments de vente uniques.",
-  "resource.competitor-analysis-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.contract-first-design.outcomes.1": "Approche normalisée utilisant la méthode du contrat d'abord (Contract First Design)",
-  "resource.contract-first-design.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.contract-first-design.steps.1": "Définir des contrats d’API qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
-  "resource.contract-first-design.steps.2": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d’API lisibles par machine, faciles à partager et à valider.",
-  "resource.contract-first-design.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques de collaboration interfonctionnelle",
-  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.cross-functional-collaboration-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.data-privacy-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices sur la protection des données",
-  "resource.data-privacy-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.data-privacy-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.domain-canvas.outcomes.1": "Approche standardisée utilisant Domain Canvas",
-  "resource.domain-canvas.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.domain-canvas.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.ecosystem-vision-template.outcomes.1": "Approche standardisée utilisant le modèle de vision écosystémique",
-  "resource.ecosystem-vision-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.competitor-analysis-template.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.contract-first-design.outcomes.1": "Approche cohérente pour appliquer « Contrat de première conception »",
+  "resource.contract-first-design.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.contract-first-design.steps.1": "Définir des contrats d'API qui décrivent les attentes, les responsabilités et les directives d'utilisation pour chaque API.",
+  "resource.contract-first-design.steps.2": "Utiliser des formats normalisés (par exemple, OpenAPI, AsyncAPI) pour créer des contrats d'API lisibles par machine, faciles à partager et à valider.",
+  "resource.contract-first-design.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.cross-functional-collaboration-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de collaboration interfonctionnelle »",
+  "resource.cross-functional-collaboration-best-practices.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.cross-functional-collaboration-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.data-privacy-guidelines.outcomes.1": "Approche cohérente pour appliquer « Lignes directrices sur la protection des données »",
+  "resource.data-privacy-guidelines.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.data-privacy-guidelines.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.domain-canvas.outcomes.1": "Approche cohérente pour appliquer « Domain Canvas »",
+  "resource.domain-canvas.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.domain-canvas.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.ecosystem-vision-template.outcomes.1": "Approche cohérente pour appliquer « Modèle de vision de l'écosystème »",
+  "resource.ecosystem-vision-template.outcomes.2": "Meilleure application des pratiques associées",
   "resource.ecosystem-vision-template.steps.1": "Identifier les principaux partenaires de l'écosystème et les parties prenantes qui bénéficieront de l'écosystème ou y contribueront.",
   "resource.ecosystem-vision-template.steps.2": "Identifier les lacunes du marché que vos API peuvent combler, en se basant sur les offres des concurrents.",
-  "resource.ecosystem-vision-template.steps.3": "Identifier les partenaires potentiels dont les API peuvent améliorer vos capacités en matière d’API et votre proposition de valeur.",
+  "resource.ecosystem-vision-template.steps.3": "Identifier les partenaires potentiels dont les API peuvent améliorer vos capacités en matière d'API et votre proposition de valeur.",
   "resource.ecosystem-vision-template.steps.4": "Élaborer une stratégie de différenciation qui mette en évidence les caractéristiques et les avantages uniques de vos API.",
   "resource.ecosystem-vision-template.steps.5": "Définissez la vision de l'écosystème pour vos API, y compris la manière dont elles interagiront avec d'autres systèmes et plateformes.",
   "resource.ecosystem-vision-template.steps.6": "Concevoir des API pour permettre une intégration et une collaboration transparentes au sein de l'écosystème.",
-  "resource.ecosystem-vision-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.industry-standards-and-best-practices.outcomes.1": "Approche standardisée utilisant les normes et les meilleures pratiques de l'industrie",
-  "resource.industry-standards-and-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.industry-standards-and-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.partner-integration-guidelines.outcomes.1": "Approche standardisée utilisant les lignes directrices pour l’intégration des partenaires",
-  "resource.partner-integration-guidelines.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.partner-integration-guidelines.steps.1": "Surveiller les performances et la conformité des API de vos partenaires pour garantir la fiabilité et l’alignement avec votre stratégie API.",
-  "resource.partner-integration-guidelines.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.role-communication-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques en matière de communication sur les rôles",
-  "resource.role-communication-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.ecosystem-vision-template.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.industry-standards-and-best-practices.outcomes.1": "Approche cohérente pour appliquer « Normes industrielles et meilleures pratiques »",
+  "resource.industry-standards-and-best-practices.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.industry-standards-and-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.partner-integration-guidelines.outcomes.1": "Approche cohérente pour appliquer « Lignes directrices pour l'intégration des partenaires »",
+  "resource.partner-integration-guidelines.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.partner-integration-guidelines.steps.1": "Surveillez les performances et la conformité de l'API de vos partenaires pour garantir la fiabilité et l'alignement avec votre stratégie d'API.",
+  "resource.partner-integration-guidelines.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.role-communication-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière de communication sur les rôles »",
+  "resource.role-communication-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.role-communication-best-practices.steps.1": "Veiller à ce que les rôles et les responsabilités soient communiqués à tous les membres de l'équipe et aux parties prenantes afin d'assurer l'alignement.",
-  "resource.role-communication-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.scalable-infrastructure-best-practices.outcomes.1": "Approche normalisée utilisant les meilleures pratiques en matière d'infrastructure évolutive",
-  "resource.scalable-infrastructure-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.role-communication-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.scalable-infrastructure-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière d'infrastructure évolutive »",
+  "resource.scalable-infrastructure-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.scalable-infrastructure-best-practices.steps.1": "Contrôler les performances et la capacité de l'infrastructure pour s'assurer qu'elle peut répondre à une demande croissante.",
-  "resource.scalable-infrastructure-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.service-agreement-template.outcomes.1": "Approche standardisée utilisant le modèle d'accord de service",
-  "resource.service-agreement-template.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.scalable-infrastructure-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.service-agreement-template.outcomes.1": "Approche cohérente pour appliquer « Modèle de contrat de service »",
+  "resource.service-agreement-template.outcomes.2": "Meilleure application des pratiques associées",
   "resource.service-agreement-template.steps.1": "Utiliser des formats normalisés pour créer des accords de service lisibles par machine, faciles à partager et à valider.",
   "resource.service-agreement-template.steps.2": "Veiller à ce que les accords de service soient examinés et approuvés par les parties prenantes afin de garantir l'alignement et la clarté.",
-  "resource.service-agreement-template.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.stakeholder-engagement-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques en matière d'engagement des parties prenantes",
-  "resource.stakeholder-engagement-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.stakeholder-engagement-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.test-automation-frameworks.outcomes.1": "Approche standardisée utilisant des cadres d'automatisation des tests",
-  "resource.test-automation-frameworks.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.test-automation-frameworks.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.vendor-management-best-practices.outcomes.1": "Approche standardisée utilisant les meilleures pratiques de gestion des fournisseurs",
-  "resource.vendor-management-best-practices.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.service-agreement-template.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.stakeholder-engagement-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques en matière d'engagement des parties prenantes »",
+  "resource.stakeholder-engagement-best-practices.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.stakeholder-engagement-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.test-automation-frameworks.outcomes.1": "Approche cohérente pour appliquer « Cadres d'automatisation des tests »",
+  "resource.test-automation-frameworks.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.test-automation-frameworks.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.vendor-management-best-practices.outcomes.1": "Approche cohérente pour appliquer « Meilleures pratiques de gestion des fournisseurs »",
+  "resource.vendor-management-best-practices.outcomes.2": "Meilleure application des pratiques associées",
   "resource.vendor-management-best-practices.steps.1": "Définir les critères d'évaluation des API des fournisseurs, y compris la fiabilité, la sécurité et la conformité.",
-  "resource.vendor-management-best-practices.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
-  "resource.api-audit-checklist.outcomes.1": "Approche normalisée à l'aide de la liste de contrôle de l'audit de l’API",
-  "resource.api-audit-checklist.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
-  "resource.api-audit-checklist.steps.1": "Réalisez des audits pour évaluer la couverture du cycle de vie et vérifier que l’API respecte les normes métier, de conception et opérationnelles.",
+  "resource.vendor-management-best-practices.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-audit-checklist.outcomes.1": "Approche cohérente pour appliquer « Liste de contrôle de l'audit de l'API »",
+  "resource.api-audit-checklist.outcomes.2": "Meilleure application des pratiques associées",
+  "resource.api-audit-checklist.steps.1": "Réalisez des audits pour évaluer la couverture du cycle de vie et vérifier que l'API respecte les normes métier, de conception et opérationnelles.",
   "resource.api-audit-checklist.steps.2": "S'assurer que la documentation, les modèles de sécurité, la configuration de la passerelle et les exigences légales sont clairement définis, validés et étayés par des preuves.",
   "resource.api-audit-checklist.tips.1": "Utilisez la liste de contrôle d'audit des API de manière collaborative entre les rôles métier et techniques",
   "resource.api-business-model-canvas.outcomes.1": "Identification des ressources et des partenaires clés",
-  "resource.api-business-model-canvas.outcomes.2": "Alignement des fonctionnalités de l’API sur les objectifs métier",
-  "resource.api-business-model-canvas.steps.1": "Définir les segments d’utilisateurs",
+  "resource.api-business-model-canvas.outcomes.2": "Alignement des fonctionnalités de l'API sur les objectifs de l'entreprise",
+  "resource.api-business-model-canvas.steps.1": "Définir les segments de consommateurs",
   "resource.api-business-model-canvas.steps.2": "Identifier les stratégies de relations avec les développeurs",
   "resource.api-business-model-canvas.steps.3": "Cartographier les canaux de distribution",
-  "resource.api-business-model-canvas.steps.4": "Documenter les ressources clés et les activités clés",
+  "resource.api-business-model-canvas.steps.4": "Documentez les ressources et activités clés.",
   "resource.api-business-model-canvas.steps.5": "Identifier les principaux partenaires et parties prenantes",
   "resource.api-business-model-canvas.steps.6": "Mettre en évidence les avantages et les coûts",
   "resource.api-business-model-canvas.tips.1": "Utiliser des mesures telles que le rapport coût/bénéfice pour hiérarchiser les opportunités",
   "resource.api-business-model-canvas.tips.2": "Valider les résultats avec les principales parties prenantes",
-  "resource.api-design-principles.outcomes.1": "Approche normalisée utilisant les principes de conception de l’API",
-  "resource.api-design-principles.outcomes.2": "Amélioration de la mise en œuvre des pratiques liées à l’API",
+  "resource.api-design-principles.outcomes.1": "Approche cohérente pour appliquer « Principes de conception de l'API »",
+  "resource.api-design-principles.outcomes.2": "Meilleure application des pratiques associées",
   "resource.api-design-principles.steps.1": "**Noms et comportements cohérents:** appliquer des conventions partagées pour les ressources, les erreurs et les formats afin de rendre les API prévisibles.",
-  "resource.api-design-principles.steps.2": "**Dirigé par le contrat:** capturer l’interface avec OpenAPI ou AsyncAPI avant le codage pour aligner les équipes et permettre l'automatisation.",
-  "resource.api-design-principles.steps.3": "**Utilisabilité et découvrabilité:** fournir une documentation et des exemples clairs afin que les développeurs comprennent rapidement comment utiliser l’API.",
-  "resource.api-design-principles.steps.4": "**Itérer en sécurité :** faire évoluer les conceptions par petits incréments versionnés afin que les changements ne perturbent pas les utilisateurs existants.",
-  "resource.api-design-principles.tips.1": "L'utiliser en collaboration avec les rôles métier et techniques",
+  "resource.api-design-principles.steps.2": "**Dirigé par le contrat:** capturer l'interface avec OpenAPI ou AsyncAPI avant le codage pour aligner les équipes et permettre l'automatisation.",
+  "resource.api-design-principles.steps.3": "**Utilisabilité et facilité de découverte:** fournir une documentation et des exemples clairs afin que les développeurs comprennent rapidement comment utiliser l'API.",
+  "resource.api-design-principles.steps.4": "**Itérer en sécurité :** faites évoluer les conceptions par petits incréments versionnés afin que les changements ne perturbent pas les utilisateurs existants.",
+  "resource.api-design-principles.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
   "resource.api-value-proposition-canvas.outcomes.1": "Alignement sur les besoins des utilisateurs",
-  "resource.api-value-proposition-canvas.outcomes.2": "Meilleure satisfaction des utilisateurs API",
+  "resource.api-value-proposition-canvas.outcomes.2": "Amélioration de la satisfaction des consommateurs d'API",
   "resource.api-value-proposition-canvas.steps.1": "Identifier les caractéristiques permettant d'obtenir les gains escomptés",
   "resource.api-value-proposition-canvas.steps.2": "Définir des caractéristiques permettant de relever les défis",
-  "resource.api-value-proposition-canvas.steps.3": "Cartographier les caractéristiques des produits de l’API",
-  "resource.api-value-proposition-canvas.tips.1": "Mettre en évidence les fonctionnalités qui réduisent les irritants ou renforcent les gains.",
-  "resource.api-value-proposition-canvas.tips.2": "Valider les fonctionnalités avec les utilisateurs API pour garantir l’alignement.",
-  "resource.business-impact-canvas.outcomes.1": "Sécurité et conformité renforcées",
-  "resource.business-impact-canvas.outcomes.2": "Amélioration des performances de l’API",
+  "resource.api-value-proposition-canvas.steps.3": "Cartographier les caractéristiques des produits de l'API",
+  "resource.api-value-proposition-canvas.tips.1": "Mettre en évidence les caractéristiques qui soulagent les douleurs ou améliorent les gains",
+  "resource.api-value-proposition-canvas.tips.2": "Valider les caractéristiques avec les consommateurs d'API pour garantir l'alignement",
+  "resource.business-impact-canvas.outcomes.1": "Risques et mesures d’atténuation priorisés",
+  "resource.business-impact-canvas.outcomes.2": "Éléments probants pour les décisions d’architecture et de plateforme",
   "resource.business-impact-canvas.steps.1": "Moyens d'atténuer les risques liés à la disponibilité : Définir les mesures d'atténuation.",
   "resource.business-impact-canvas.steps.2": "Risques liés à la sécurité : Documenter les risques liés à la sécurité.",
   "resource.business-impact-canvas.steps.3": "Moyens d'atténuer les risques de sécurité : Proposer des stratégies pour atténuer les risques de sécurité.",
   "resource.business-impact-canvas.steps.4": "Risques liés aux données : Identifier les risques pour l'exactitude ou la disponibilité des données.",
   "resource.business-impact-canvas.steps.5": "Moyens d'atténuer les risques liés aux données : Prévoir des stratégies pour faire face aux risques liés aux données.",
-  "resource.business-impact-canvas.tips.1": "Utiliser les incidents passés pour identifier les risques potentiels",
-  "resource.business-impact-canvas.tips.2": "Prioriser les API critiques ayant le plus d’impact sur l’activité métier",
-  "resource.capacity-canvas.outcomes.1": "Préparation aux tendances futures d’usage",
-  "resource.capacity-canvas.outcomes.2": "Stratégies définies de mise en cache et de limitation du débit",
-  "resource.capacity-canvas.steps.1": "Prévoir les tendances futures d’usage",
+  "resource.business-impact-canvas.tips.1": "Examinez les risques avec les parties prenantes métier et techniques.",
+  "resource.business-impact-canvas.tips.2": "Utilisez les incidents passés et les données opérationnelles pour remettre en question les hypothèses.",
+  "resource.capacity-canvas.outcomes.1": "Hypothèses de pics de charge, de disponibilité et de croissance documentées",
+  "resource.capacity-canvas.outcomes.2": "Décisions de mise à l’échelle, de mise en cache et de limitation de débit définies",
+  "resource.capacity-canvas.steps.1": "Prévoir les tendances futures de la consommation",
   "resource.capacity-canvas.steps.2": "Planifier les pics de charge et les exigences de disponibilité",
   "resource.capacity-canvas.steps.3": "Définir les stratégies de mise en cache et de limitation du débit",
   "resource.capacity-canvas.steps.4": "Proposer des stratégies de mise à l'échelle",
-  "resource.capacity-canvas.tips.1": "Définir des scénarios d'utilisation maximale",
-  "resource.capacity-canvas.tips.2": "Inclure des tests d'évolutivité dans la phase de planification",
-  "resource.customer-journey-canvas.outcomes.1": "Conception améliorée de l’API",
-  "resource.customer-journey-canvas.outcomes.2": "Une meilleure expérience pour l’utilisateur",
+  "resource.capacity-canvas.tips.1": "Utilisez des données mesurées lorsqu’elles sont disponibles et explicitez les hypothèses.",
+  "resource.capacity-canvas.tips.2": "Réexaminez le canvas après les pilotes ou tout changement significatif de la demande.",
+  "resource.customer-journey-canvas.outcomes.1": "Besoins, irritants, gains, entrées et sorties documentés",
+  "resource.customer-journey-canvas.outcomes.2": "Éléments du parcours disponibles pour les décisions de capacité, d’exigences et d’architecture",
   "resource.customer-journey-canvas.steps.1": "Identifier les éléments déclencheurs du voyage",
   "resource.customer-journey-canvas.steps.2": "Décrire la fin du voyage",
   "resource.customer-journey-canvas.steps.3": "Cartographier les étapes du voyage avec les intrants et les extrants",
-  "resource.customer-journey-canvas.steps.4": "Identifier les irritants des clients",
+  "resource.customer-journey-canvas.steps.4": "Identifier les problèmes des clients",
   "resource.customer-journey-canvas.steps.5": "Résumer les gains pour les clients",
   "resource.customer-journey-canvas.steps.6": "Définir les intrants nécessaires et les résultats qui en découlent",
   "resource.customer-journey-canvas.steps.7": "Définir les interactions API pour chaque étape",
-  "resource.customer-journey-canvas.tips.1": "Utiliser les résultats de ce canevas pour informer d'autres canevas tels que le canevas de proposition de valeur de l’API.",
-  "resource.event-canvas.outcomes.1": "Déclencheurs d'événements et logique de traitement clairs",
-  "resource.event-canvas.outcomes.2": "Amélioration de la réactivité aux changements en temps réel",
+  "resource.customer-journey-canvas.tips.1": "Utilisez les résultats pour alimenter le travail sur la proposition de valeur, le domaine, les exigences et l’architecture.",
+  "resource.event-canvas.outcomes.1": "Événements, déclencheurs, schémas, producteurs et utilisateurs clarifiés",
+  "resource.event-canvas.outcomes.2": "Attentes de traitement, d’accusé de réception et de gestion des échecs documentées",
   "resource.event-canvas.steps.1": "Définir des déclencheurs pour chaque événement",
-  "resource.event-canvas.steps.2": "Décrire la logique de traitement des événements par le systèmes backend",
+  "resource.event-canvas.steps.2": "Décrivez le traitement des événements, les changements d’état et la gestion des échecs.",
   "resource.event-canvas.steps.3": "Préciser les résultats obtenus ou les remerciements",
-  "resource.event-canvas.tips.1": "Documenter les flux d’événements et les dépendances",
+  "resource.event-canvas.tips.1": "Documentez les flux d’événements, les responsabilités, les hypothèses d’ordre et les dépendances.",
   "resource.event-canvas.tips.2": "Valider le traitement des événements à l'aide de cas de test",
   "resource.graphql-canvas.outcomes.1": "Types définis et leurs relations",
   "resource.graphql-canvas.outcomes.2": "Des requêtes, des mutations et des abonnements clairs",
@@ -378,19 +378,19 @@
   "resource.graphql-canvas.steps.5": "Abonnements aux grandes lignes pour des mises à jour en temps réel",
   "resource.graphql-canvas.steps.6": "Définir l'authentification et l'autorisation : Qui peut accéder à quels champs ou types ?",
   "resource.graphql-canvas.steps.7": "Tenez compte des contraintes de pagination, de filtrage ou de limitation du débit.",
-  "resource.graphql-canvas.tips.1": "Documenter les exemples de requêtes et de mutations",
+  "resource.graphql-canvas.tips.1": "Documentez des exemples de requêtes et de mutations.",
   "resource.graphql-canvas.tips.2": "Veiller à ce que les noms des types soient descriptifs et cohérents",
-  "resource.interaction-canvas.outcomes.1": "Entrées et sorties définies pour chaque interaction",
-  "resource.interaction-canvas.outcomes.2": "Règles de validation cohérentes entre les interactions",
+  "resource.interaction-canvas.outcomes.1": "Entrées, sorties, commandes, requêtes, événements et réponses clarifiés",
+  "resource.interaction-canvas.outcomes.2": "Règles de validation et attentes d’interaction convenues",
   "resource.interaction-canvas.steps.1": "Définir des points finaux pour chaque interaction",
-  "resource.interaction-canvas.steps.2": "Documenter les entrées et sorties de chaque interaction",
+  "resource.interaction-canvas.steps.2": "Documentez les entrées et les sorties de chaque interaction.",
   "resource.interaction-canvas.steps.3": "Spécifier les règles et contraintes de validation",
   "resource.interaction-canvas.steps.4": "Créer des modèles d'interaction pour les interactions CRUD, axées sur les requêtes, axées sur les commandes et axées sur les événements.",
   "resource.interaction-canvas.tips.1": "Simuler des interactions avec des données fictives pour valider les flux de travail",
-  "resource.interaction-canvas.tips.2": "Documenter les réponses attendues pour les interactions réussies et en erreur",
-  "resource.location-canvas.outcomes.1": "Optimisation des performances de l’API dans toutes les régions",
-  "resource.location-canvas.outcomes.2": "Meilleure compréhension des besoins régionaux",
-  "resource.location-canvas.steps.1": "Documenter l’emplacement des utilisateurs.",
+  "resource.interaction-canvas.tips.2": "Documentez les réponses attendues pour les interactions réussies, échouées et exceptionnelles.",
+  "resource.location-canvas.outcomes.1": "Contraintes régionales de performance et d’accessibilité identifiées",
+  "resource.location-canvas.outcomes.2": "Résidence des données, limites de confiance et réglementations applicables clarifiées",
+  "resource.location-canvas.steps.1": "Documenter l'emplacement des consommateurs.",
   "resource.location-canvas.steps.2": "Identifier les réglementations applicables.",
   "resource.location-canvas.steps.3": "Documenter l'endroit où les données doivent être stockées.",
   "resource.location-canvas.steps.4": "s'assurer que les API sont accessibles dans toutes les régions du réseau prévues.",
@@ -399,44 +399,147 @@
   "resource.location-canvas.tips.2": "Résoudre de manière proactive les contraintes liées à la localisation",
   "resource.rest-canvas.outcomes.1": "Ressources définies et leurs interactions",
   "resource.rest-canvas.outcomes.2": "Exemples de demandes et de réponses pour plus de clarté",
-  "resource.rest-canvas.steps.1": "Définir la structure du modèle de ressources de l’API",
+  "resource.rest-canvas.steps.1": "Définir la structure du modèle de ressources de l'API",
   "resource.rest-canvas.steps.2": "Spécifier les verbes HTTP utilisés pour interagir avec les ressources",
   "resource.rest-canvas.steps.3": "Fournir des exemples de demandes et de réponses pour chaque verbe",
   "resource.rest-canvas.tips.1": "Veiller à ce que les URI des ressources soient intuitifs et cohérents",
-  "resource.rest-canvas.tips.2": "gestion des erreurs de documents et codes de réponse",
+  "resource.rest-canvas.tips.2": "Documentez la gestion des erreurs et les codes de réponse.",
   "resource.capability-value-proposition-canvas.title": "Capability Value Proposition Canvas",
-  "resource.capability-value-proposition-canvas.description": "Un canvas indépendant de la technologie pour cartographier les tâches, gains, irritants et capacités réutilisables candidates des utilisateurs avant de choisir un style d’intégration.",
+  "resource.capability-value-proposition-canvas.description": "Un canvas indépendant de la technologie pour cartographier les tâches, gains, irritants et capacités réutilisables candidates des utilisateurs avant de sélectionner un mode de mise en œuvre.",
   "resource.capability-value-proposition-canvas.outcomes": "Proposition de valeur claire pour une capacité réutilisable",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Les tâches, gains et irritants des utilisateurs sont capturés sans présupposer de technologie.",
-  "resource.capability-value-proposition-canvas.outcomes.2": "Les capacités réutilisables candidates sont identifiées pour l’évaluation d’architecture.",
-  "resource.capability-value-proposition-canvas.steps": "Lister les tâches et résultats utilisateur que la capacité doit soutenir.",
-  "resource.capability-value-proposition-canvas.steps.1": "Identifier les fonctionnalités de capacité qui créent des gains.",
-  "resource.capability-value-proposition-canvas.steps.2": "Identifier les fonctionnalités de capacité qui réduisent les irritants.",
-  "resource.capability-value-proposition-canvas.steps.3": "Regrouper les fonctionnalités en capacités réutilisables candidates.",
-  "resource.capability-value-proposition-canvas.tips": "Rester indépendant de la technologie jusqu’à ce que les exigences indiquent le style adapté.",
-  "resource.capability-value-proposition-canvas.tips.1": "Utilisez ce canvas à la place de l’API Value Proposition Canvas lorsque l’API n’est pas encore le style d’intégration retenu.",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Tâches, gains et irritants des utilisateurs capturés sans présupposer de technologie",
+  "resource.capability-value-proposition-canvas.outcomes.2": "Capacités réutilisables candidates identifiées pour l’évaluation d’architecture",
+  "resource.capability-value-proposition-canvas.steps": "Listez les tâches et résultats utilisateurs que la capacité doit prendre en charge.",
+  "resource.capability-value-proposition-canvas.steps.1": "Identifiez les caractéristiques de capacité qui permettent les gains.",
+  "resource.capability-value-proposition-canvas.steps.2": "Identifiez les caractéristiques de capacité qui réduisent les irritants.",
+  "resource.capability-value-proposition-canvas.steps.3": "Regroupez les caractéristiques en capacités réutilisables candidates.",
+  "resource.capability-value-proposition-canvas.tips": "Restez indépendant de la technologie jusqu’à ce que les exigences indiquent un mode de mise en œuvre adapté.",
+  "resource.capability-value-proposition-canvas.tips.1": "Utilisez ce canvas à la place de l’API Value Proposition Canvas lorsqu’une API n’est pas encore le mode de mise en œuvre retenu.",
   "resource.capability-business-model-canvas.title": "Capability Business Model Canvas",
-  "resource.capability-business-model-canvas.description": "Un canvas de modèle économique pour les capacités d’intégration réutilisables, couvrant la valeur, les utilisateurs, la propriété, l’engagement, les coûts et les bénéfices sans présupposer une mise à disposition par API.",
+  "resource.capability-business-model-canvas.description": "Un business model canvas pour les capacités réutilisables, couvrant la valeur, les utilisateurs, la responsabilité, l’engagement, les coûts et les bénéfices sans présupposer de mode de mise en œuvre.",
   "resource.capability-business-model-canvas.outcomes": "Modèle opérationnel viable pour une capacité réutilisable",
-  "resource.capability-business-model-canvas.outcomes.1": "La propriété, les utilisateurs, les canaux, les partenaires et les besoins de support sont clarifiés.",
-  "resource.capability-business-model-canvas.outcomes.2": "Les coûts et bénéfices sont visibles avant l’engagement architectural.",
-  "resource.capability-business-model-canvas.steps": "Résumer la proposition de valeur de la capacité.",
-  "resource.capability-business-model-canvas.steps.1": "Identifier les segments d’utilisateurs et les canaux d’engagement.",
-  "resource.capability-business-model-canvas.steps.2": "Définir les activités, ressources et partenaires clés.",
-  "resource.capability-business-model-canvas.steps.3": "Capturer les coûts et bénéfices.",
-  "resource.capability-business-model-canvas.steps.4": "Clarifier la propriété, le financement, le support et les attentes de cycle de vie.",
-  "resource.capability-business-model-canvas.steps.5": "Valider le modèle avec les utilisateurs, les producteurs et les parties prenantes de gouvernance.",
-  "resource.capability-business-model-canvas.tips": "Utilisez ce canvas à la place de l’API Business Model Canvas lorsque le style d’intégration reste ouvert.",
-  "resource.capability-business-model-canvas.tips.1": "Gardez le focus sur la viabilité de la capacité réutilisable, pas sur une connexion ponctuelle.",
+  "resource.capability-business-model-canvas.outcomes.1": "Responsabilité, utilisateurs, canaux, partenaires et besoins de support clarifiés",
+  "resource.capability-business-model-canvas.outcomes.2": "Coûts et bénéfices visibles avant l’engagement architectural",
+  "resource.capability-business-model-canvas.steps": "Résumez la proposition de valeur de la capacité.",
+  "resource.capability-business-model-canvas.steps.1": "Identifiez les segments d’utilisateurs et les canaux d’engagement.",
+  "resource.capability-business-model-canvas.steps.2": "Définissez les activités, ressources et partenaires clés.",
+  "resource.capability-business-model-canvas.steps.3": "Documentez les coûts et les bénéfices.",
+  "resource.capability-business-model-canvas.steps.4": "Clarifiez la responsabilité, le financement, le support et les attentes de cycle de vie.",
+  "resource.capability-business-model-canvas.steps.5": "Validez le modèle avec les utilisateurs, producteurs et parties prenantes de gouvernance.",
+  "resource.capability-business-model-canvas.tips": "Utilisez ce canvas à la place de l’API Business Model Canvas tant que le mode de mise en œuvre reste ouvert.",
+  "resource.capability-business-model-canvas.tips.1": "Concentrez-vous sur la viabilité d’une capacité réutilisable, et non sur une connexion ponctuelle.",
   "resource.consumer-experience-requirements-canvas.title": "Consumer Experience Requirements Canvas",
-  "resource.consumer-experience-requirements-canvas.description": "Un canvas d’exigences pour l’expérience utilisateur et les besoins non fonctionnels qui doivent guider le choix d’architecture ultérieur.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Exigences utilisateur indépendantes de la technologie",
-  "resource.consumer-experience-requirements-canvas.outcomes.1": "Les besoins d’expérience et les besoins non fonctionnels sont capturés avant le début de la conception.",
-  "resource.consumer-experience-requirements-canvas.outcomes.2": "Les implications d’architecture sont documentées pour sélectionner le style adapté.",
-  "resource.consumer-experience-requirements-canvas.steps": "Capturer les objectifs utilisateur et le contexte d’usage.",
-  "resource.consumer-experience-requirements-canvas.steps.1": "Documenter les attentes de disponibilité, fraîcheur, volume, performance, qualité des données et cohérence.",
-  "resource.consumer-experience-requirements-canvas.steps.2": "Documenter les attentes de sécurité, protection des données, onboarding, changement, observabilité, support et reprise.",
-  "resource.consumer-experience-requirements-canvas.steps.3": "Résumer ce que les exigences impliquent pour les styles d’architecture possibles.",
-  "resource.consumer-experience-requirements-canvas.tips": "Utilisez ce canvas comme passerelle entre la valeur de la capacité et la décision d’architecture.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Ne choisissez pas API, événement, fichier, flux ou produit de données avant que les exigences n’indiquent l’option la plus adaptée."
-}
+  "resource.consumer-experience-requirements-canvas.description": "Un canvas d’exigences pour l’expérience utilisateur et les besoins non fonctionnels, destiné à guider les décisions ultérieures d’architecture et de mode de mise en œuvre.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Exigences utilisateurs et de service indépendantes de la technologie",
+  "resource.consumer-experience-requirements-canvas.outcomes.1": "Besoins d’expérience et exigences non fonctionnelles capturés avant le début de la conception",
+  "resource.consumer-experience-requirements-canvas.outcomes.2": "Impacts architecturaux documentés pour le choix du mode de mise en œuvre",
+  "resource.consumer-experience-requirements-canvas.steps": "Capturez les objectifs des utilisateurs et leur contexte d’usage.",
+  "resource.consumer-experience-requirements-canvas.steps.1": "Documentez les attentes de disponibilité, de fraîcheur, de volume, de performance, de qualité et de cohérence des données.",
+  "resource.consumer-experience-requirements-canvas.steps.2": "Documentez les attentes de sécurité, de confidentialité, d’onboarding, de changement, d’observabilité, de support et de reprise.",
+  "resource.consumer-experience-requirements-canvas.steps.3": "Résumez ce que les exigences impliquent pour les modes de mise en œuvre possibles.",
+  "resource.consumer-experience-requirements-canvas.tips": "Utilisez ce canvas comme lien entre la valeur de la capacité et la décision d’architecture.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Ne choisissez pas API, événement, fichier, flux, produit de données, intégration directe ou style hybride avant que les exigences n’indiquent l’option la plus adaptée.",
+  "resource.integration-style-selection-guide.title": "Guide de sélection du mode d’intégration",
+  "resource.integration-style-selection-guide.description": "Guide pour choisir entre API, événement, fichier, flux, produit de données, intégration directe ou mode hybride selon les exigences et contraintes.",
+  "resource.integration-style-selection-guide.outcomes": "Mode de mise en œuvre de l’intégration justifié",
+  "resource.integration-style-selection-guide.outcomes.1": "Compromis documentés entre les différentes options",
+  "resource.integration-style-selection-guide.outcomes.2": "Choix traçable aux exigences utilisateurs, plateforme, données et opérations",
+  "resource.integration-style-selection-guide.steps": "Comparez les modes viables selon la latence, le volume, le couplage, la responsabilité des données, la fraîcheur, la gouvernance et l’exploitabilité.",
+  "resource.integration-style-selection-guide.steps.1": "Identifiez les options adaptées au cas d’usage.",
+  "resource.integration-style-selection-guide.steps.2": "Documentez contraintes, risques et dépendances de plateforme.",
+  "resource.integration-style-selection-guide.steps.3": "Consignez les raisons du rejet des alternatives.",
+  "resource.process-workflow-design-guide.title": "Guide de conception des processus et workflows",
+  "resource.process-workflow-design-guide.description": "Guide pour modéliser étapes, rôles, transferts, décisions, états, entrées, sorties et exceptions d’un workflow automatisé.",
+  "resource.process-workflow-design-guide.outcomes": "Conception claire du workflow automatisé",
+  "resource.process-workflow-design-guide.outcomes.1": "Étapes et transferts documentés avant mise en œuvre",
+  "resource.process-workflow-design-guide.outcomes.2": "États, entrées, sorties et exceptions compris",
+  "resource.process-workflow-design-guide.steps": "Cartographiez le processus actuel et cible, avec les responsabilités humaines et système.",
+  "resource.process-workflow-design-guide.steps.1": "Identifiez déclencheurs, états, décisions, données, sorties et critères de fin.",
+  "resource.process-workflow-design-guide.steps.2": "Documentez les transferts entre utilisateurs, systèmes, opérations et support.",
+  "resource.process-workflow-design-guide.steps.3": "Confirmez les étapes automatisées et celles nécessitant un jugement humain.",
+  "resource.decision-business-rules-guide.title": "Guide des décisions et règles métier",
+  "resource.decision-business-rules-guide.description": "Guide pour capturer règles, seuils, décisions, validations, critères d’éligibilité et responsabilités.",
+  "resource.decision-business-rules-guide.outcomes": "Décisions et règles métier explicites",
+  "resource.decision-business-rules-guide.outcomes.1": "Règles et seuils documentés avec leurs responsables",
+  "resource.decision-business-rules-guide.outcomes.2": "Décisions traçables aux politiques, processus ou objectifs métier",
+  "resource.decision-business-rules-guide.steps": "Listez les décisions que l’automatisation doit prendre ou soutenir.",
+  "resource.decision-business-rules-guide.steps.1": "Documentez conditions, seuils, exceptions, validations et escalades.",
+  "resource.decision-business-rules-guide.steps.2": "Identifiez les responsables et la gouvernance des changements.",
+  "resource.automation-trigger-handoff-exception-guide.title": "Guide des déclencheurs, transferts et exceptions",
+  "resource.automation-trigger-handoff-exception-guide.description": "Guide pour définir déclencheurs, transferts humains, exceptions, reprises, actions compensatoires et escalades.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes": "Déclencheurs et chemins d’exception définis",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.1": "Transferts humains et escalades explicites",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.2": "Exceptions, reprises et compensations conçues avant livraison",
+  "resource.automation-trigger-handoff-exception-guide.steps": "Définissez événements, horaires, actions utilisateur ou états système déclencheurs.",
+  "resource.automation-trigger-handoff-exception-guide.steps.1": "Cartographiez les transferts vers utilisateurs, opérateurs ou support.",
+  "resource.automation-trigger-handoff-exception-guide.steps.2": "Documentez exceptions, reprises, délais et solutions de repli.",
+  "resource.automation-trigger-handoff-exception-guide.steps.3": "Définissez alertes et seuils d’escalade.",
+  "resource.automation-testing-guide.title": "Guide de test des automatisations",
+  "resource.automation-testing-guide.description": "Guide pour tester workflows, décisions, intégrations, exceptions, rollback, supervision et impact utilisateur.",
+  "resource.automation-testing-guide.outcomes": "Comportement de l’automatisation validé",
+  "resource.automation-testing-guide.outcomes.1": "Tests des workflows, règles, exceptions et intégrations définis",
+  "resource.automation-testing-guide.outcomes.2": "Confiance avant publication pour les parcours automatisés et assistés",
+  "resource.automation-testing-guide.steps": "Créez des tests pour parcours nominaux, cas limites, exceptions, reprises et transferts.",
+  "resource.automation-testing-guide.steps.1": "Validez règles métier et décisions avec des données représentatives.",
+  "resource.automation-testing-guide.steps.2": "Testez rollback, reprise, observabilité et intervention manuelle.",
+  "resource.automation-testing-guide.steps.3": "Impliquez utilisateurs et opérateurs dans les tests d’acceptation.",
+  "resource.automation-operational-ownership-guide.title": "Guide de responsabilité opérationnelle",
+  "resource.automation-operational-ownership-guide.description": "Guide pour définir responsabilité, runbooks, supervision, support, suivi, contrôle des changements et amélioration continue.",
+  "resource.automation-operational-ownership-guide.outcomes": "Modèle opérationnel clair",
+  "resource.automation-operational-ownership-guide.outcomes.1": "Responsabilités de propriété, support et escalade attribuées",
+  "resource.automation-operational-ownership-guide.outcomes.2": "Pratiques de suivi et changement prêtes pour exploitation",
+  "resource.automation-operational-ownership-guide.steps": "Définissez les responsables métier, techniques et opérationnels.",
+  "resource.automation-operational-ownership-guide.steps.1": "Documentez runbooks, support, signaux de suivi, attentes de service et escalades.",
+  "resource.automation-operational-ownership-guide.steps.2": "Définissez le contrôle des changements pour workflows, plateforme et règles.",
+  "resource.automation-rollback-supervision-guide.title": "Guide de rollback et supervision",
+  "resource.automation-rollback-supervision-guide.description": "Guide pour concevoir rollback, pause, dérogation manuelle, suivi, supervision et reprise.",
+  "resource.automation-rollback-supervision-guide.outcomes": "Chemins de reprise contrôlés",
+  "resource.automation-rollback-supervision-guide.outcomes.1": "Rollback, pause et dérogation documentés",
+  "resource.automation-rollback-supervision-guide.outcomes.2": "Besoins de supervision et responsabilités de reprise définis",
+  "resource.automation-rollback-supervision-guide.steps": "Identifiez les actions réversibles, suspendables ou remplaçables manuellement.",
+  "resource.automation-rollback-supervision-guide.steps.1": "Définissez rollback, compensation et reprise.",
+  "resource.automation-rollback-supervision-guide.steps.2": "Documentez seuils de supervision, alertes et décisions manuelles.",
+  "resource.automation-rollback-supervision-guide.steps.3": "Validez les procédures de reprise avant publication.",
+  "resource.automation-readiness-checklist.title": "Checklist de préparation des automatisations",
+  "resource.automation-readiness-checklist.description": "Checklist pour valider workflow, contrôles, risques, conformité, supervision humaine, preuves de test, rollback, opérations et préparation.",
+  "resource.automation-readiness-checklist.outcomes": "Préparation de l’automatisation documentée",
+  "resource.automation-readiness-checklist.outcomes.1": "Écarts et mesures d’atténuation connus avant publication",
+  "resource.automation-readiness-checklist.outcomes.2": "Preuves pour qualité, risques, conformité, supervision et approbation",
+  "resource.automation-readiness-checklist.steps": "Examinez workflow, règles métier, contrôles, accès, données et exceptions.",
+  "resource.automation-readiness-checklist.steps.1": "Vérifiez preuves de test, rollback, supervision et support.",
+  "resource.automation-readiness-checklist.steps.2": "Confirmez responsabilités, runbooks, suivi et contrôle des changements.",
+  "resource.automation-readiness-checklist.steps.3": "Consignez les écarts, décisions et risques acceptés.",
+  "resource.automation-rollout-enablement-guide.title": "Guide de déploiement et d’enablement",
+  "resource.automation-rollout-enablement-guide.description": "Guide pour déployer les automatisations avec communication, onboarding, instructions d’exploitation, support, conduite du changement et feedback.",
+  "resource.automation-rollout-enablement-guide.outcomes": "Utilisateurs et opérateurs préparés",
+  "resource.automation-rollout-enablement-guide.outcomes.1": "Communication, onboarding et support préparés",
+  "resource.automation-rollout-enablement-guide.outcomes.2": "Compréhension des changements de travail après publication",
+  "resource.automation-rollout-enablement-guide.steps": "Définissez publics, calendrier, canaux et besoins de formation.",
+  "resource.automation-rollout-enablement-guide.steps.1": "Publiez instructions, support, gestion des exceptions et contacts.",
+  "resource.automation-rollout-enablement-guide.steps.2": "Planifiez l’accompagnement de transition.",
+  "resource.automation-rollout-enablement-guide.steps.3": "Collectez les retours et alimentez le backlog.",
+  "resource.integration-style-selection-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.integration-style-selection-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.process-workflow-design-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.process-workflow-design-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.decision-business-rules-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.decision-business-rules-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-trigger-handoff-exception-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-trigger-handoff-exception-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-testing-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-testing-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-operational-ownership-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-operational-ownership-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-rollback-supervision-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-rollback-supervision-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-readiness-checklist.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-readiness-checklist.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.automation-rollout-enablement-guide.tips": "Adaptez cette ressource à votre contexte.",
+  "resource.automation-rollout-enablement-guide.tips.1": "Utilisez cette ressource avec les rôles métier et techniques concernés.",
+  "resource.api-community-engagement-strategies.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.",
+  "resource.api-development-best-practices.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.",
+  "resource.api-metrics-and-analytics.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.",
+  "resource.api-testing-best-practices.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.",
+  "resource.apiops-CI-CD-for-apis.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu.",
+  "resource.api-audit-checklist.tips.2": "Utilisez cette ressource lorsque l’API est le mode de mise en œuvre retenu."
+}
\ No newline at end of file
diff --git a/src/data/method/fr/labels.stakeholders.json b/src/data/method/fr/labels.stakeholders.json
index 72499b7..003943a 100644
--- a/src/data/method/fr/labels.stakeholders.json
+++ b/src/data/method/fr/labels.stakeholders.json
@@ -3,47 +3,47 @@
   "stakeholder.involvement.core": "Principal",
   "stakeholder.involvement.consulted": "Consulté",
   "stakeholder.business-owner.title": "Responsable métier",
-  "stakeholder.business-owner.description": "Représente les objectifs métier, le financement et les résultats attendus de l'initiative de capacité.",
+  "stakeholder.business-owner.description": "Représente les objectifs métier, le financement et les résultats attendus de l’initiative de capacité, d’API ou d’automatisation.",
   "stakeholder.api-program-owner.title": "Responsable du programme API",
   "stakeholder.api-program-owner.description": "Coordonne les pratiques du portefeuille API, l'alignement organisationnel et le développement à long terme des capacités API.",
   "stakeholder.api-product-owner.title": "Propriétaire du produit API",
-  "stakeholder.api-product-owner.description": "Piloter l'opportunité API, la priorisation et les décisions au niveau du produit tout au long du cycle de vie.",
+  "stakeholder.api-product-owner.description": "Pilote l’opportunité API, la priorisation et les décisions au niveau produit tout au long du cycle de vie.",
   "stakeholder.capability-owner.title": "Responsable de capacité",
-  "stakeholder.capability-owner.description": "Responsable de la vision, des objectifs, de la priorisation et de l'évolution de la capacité tout au long de son cycle de vie.",
+  "stakeholder.capability-owner.description": "Responsable de la vision, de la valeur, des priorités, du cycle de vie et de la réutilisation de la capacité auprès des utilisateurs.",
   "stakeholder.domain-specialist.title": "Expert du domaine",
-  "stakeholder.domain-specialist.description": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que l'API doit refléter.",
+  "stakeholder.domain-specialist.description": "Apporte une connaissance approfondie du domaine métier, des concepts, des règles et des contraintes que la capacité ou l’interface doit refléter.",
   "stakeholder.customer-specialist.title": "Représentant client ou partenaire",
-  "stakeholder.customer-specialist.description": "Contribue à la perspective du client ou partenaire commercial pour le parcours, la valeur et le modèle de collaboration.",
+  "stakeholder.customer-specialist.description": "Contribue à la perspective du client ou partenaire pour le parcours, la valeur et le modèle de collaboration.",
   "stakeholder.api-consumer-specialist.title": "Représentant utilisateur API",
   "stakeholder.api-consumer-specialist.description": "Représente les besoins des développeurs, intégrateurs ou autres utilisateurs d'API qui utilisent l'API directement.",
   "stakeholder.platform-architect.title": "Architecte de la plateforme",
-  "stakeholder.platform-architect.description": "Oriente les décisions relatives à la plateforme, aux intégrations, à l'évolutivité et à l'architecture.",
+  "stakeholder.platform-architect.description": "Oriente les décisions relatives à la plateforme, à l’intégration, à l’évolutivité et à l’architecture qui déterminent comment la capacité ou l’API est construite et exploitée.",
   "stakeholder.api-architect.title": "Architecte API",
   "stakeholder.api-architect.description": "Responsable de l'architecture API, des principes de conception et de la qualité des contrats d'interface.",
   "stakeholder.integration-architect.title": "Architecte d'intégration",
-  "stakeholder.integration-architect.description": "Conçoit les solutions et modèles d'intégration en cohérence avec l'architecture d'entreprise.",
+  "stakeholder.integration-architect.description": "Conçoit les approches d’intégration et les modes de mise en œuvre qui relient la capacité ou l’API aux autres systèmes.",
   "stakeholder.platform-owner.title": "Responsable de plateforme",
-  "stakeholder.platform-owner.description": "Responsable des capacités de la plateforme, de son évolution et de son exploitation.",
+  "stakeholder.platform-owner.description": "Responsable des capacités de la plateforme, de la feuille de route, du modèle opérationnel et des attentes de service.",
   "stakeholder.api-designer.title": "Designer API",
-  "stakeholder.api-designer.description": "Conçoit le contrat API, le modèle d'interaction, la cohérence et l'utilisabilité des capacités exposées.",
+  "stakeholder.api-designer.description": "Conçoit le contrat d’interface, le modèle d’interaction, la cohérence et l’utilisabilité des capacités exposées.",
   "stakeholder.api-engineer.title": "Ingénieur de livraison",
-  "stakeholder.api-engineer.description": "Assume la responsabilité de l'implémentation, de l'automatisation, des tests et du flux de publication nécessaires pour livrer l'API de manière fiable.",
+  "stakeholder.api-engineer.description": "Assume la responsabilité de la mise en œuvre, de l’automatisation, des tests et du flux de publication nécessaires pour livrer la capacité, l’API ou l’automatisation de manière fiable.",
   "stakeholder.automation-owner.title": "Responsable de l'automatisation",
-  "stakeholder.automation-owner.description": "Responsable des objectifs, de la priorisation et de la valeur métier des capacités d'automatisation.",
+  "stakeholder.automation-owner.description": "Responsable des objectifs, de la valeur métier, des priorités, des contrôles et des résultats du cycle de vie de l’automatisation.",
   "stakeholder.process-owner.title": "Responsable de processus",
-  "stakeholder.process-owner.description": "Responsable des objectifs, de l'évolution et des résultats du processus métier.",
+  "stakeholder.process-owner.description": "Responsable du processus métier à automatiser, y compris les objectifs, les règles, les résultats et les priorités d’amélioration.",
   "stakeholder.automation-engineer.title": "Ingénieur automatisation",
-  "stakeholder.automation-engineer.description": "Met en œuvre, teste et exploite les solutions d'automatisation et leurs intégrations.",
+  "stakeholder.automation-engineer.description": "Met en œuvre, teste, intègre et exploite les solutions d’automatisation et les workflows associés.",
   "stakeholder.security-specialist.title": "Spécialiste en sécurité",
-  "stakeholder.security-specialist.description": "Assure que les risques de sécurité, les contrôles et les limites de confiance sont pris en compte tout au long du cycle de vie de l'API.",
+  "stakeholder.security-specialist.description": "Assure que les risques de sécurité, les contrôles et les limites de confiance sont pris en compte tout au long du cycle de vie.",
   "stakeholder.compliance-specialist.title": "Spécialiste en conformité et juridique",
-  "stakeholder.compliance-specialist.description": "Clarifie les exigences juridiques, de confidentialité et de conformité qui affectent la capacité ou l'interface.",
+  "stakeholder.compliance-specialist.description": "Clarifie les exigences juridiques, de confidentialité, réglementaires et contractuelles qui affectent la capacité, l’API, l’interface ou l’automatisation.",
   "stakeholder.governance-specialist.title": "Responsable gouvernance",
   "stakeholder.governance-specialist.description": "Représente les pratiques de revue, d'audit et de gouvernance à l'échelle de l'organisation pour la qualité et la conformité des API.",
   "stakeholder.api-devrel-specialist.title": "Responsable Documentation & DevRel",
   "stakeholder.api-devrel-specialist.description": "Responsable des contenus d'onboarding, de la communication avec les développeurs et de la qualité de la documentation API.",
-  "stakeholder.operations-specialist.title": "Propriétaire du support et des opérations",
-  "stakeholder.operations-specialist.description": "Représente le support en production, la gestion des incidents, l'observabilité et la préparation opérationnelle.",
+  "stakeholder.operations-specialist.title": "Responsable support et opérations",
+  "stakeholder.operations-specialist.description": "Représente le support en production, la gestion des incidents, l’observabilité et la préparation opérationnelle pour la capacité, l’API ou l’automatisation.",
   "stakeholder.partner-specialist.title": "Gestionnaire de partenaires ou de fournisseurs",
-  "stakeholder.partner-specialist.description": "Coordonne les relations avec les partenaires et fournisseurs qui influencent la stratégie et la mise en œuvre de la capacité."
-}
\ No newline at end of file
+  "stakeholder.partner-specialist.description": "Coordonne les relations avec les partenaires, fournisseurs ou prestataires externes qui influencent la stratégie et la mise en œuvre de la capacité ou de l’API."
+}
diff --git a/src/data/method/pt/labels.criteria.json b/src/data/method/pt/labels.criteria.json
index 597ecdf..2e21d47 100644
--- a/src/data/method/pt/labels.criteria.json
+++ b/src/data/method/pt/labels.criteria.json
@@ -1,26 +1,26 @@
 {
   "exit_criteria": "Critérios de saída",
   "entry_criteria": "Critérios de entrada",
-  "criterion.metrics-feedback-available": "Sinais de mercado relevantes, feedback ou insights operacionais estão disponíveis para orientar esta oportunidade de API.",
-  "criterion.business-goals-defined": "Os objetivos de negócio estão definidos",
-  "criterion.market-research-done": "A investigação de mercado identifica oportunidades de API",
-  "criterion.stakeholder-approval": "As partes interessadas relevantes concordam que esta oportunidade de API vale a pena ser explorada e priorizada.",
-  "criterion.api-opportunity-documented": "As oportunidades individuais de API são identificadas e documentadas",
-  "criterion.api-reusability": "A API satisfaz uma necessidade clara de negócio e é reutilizável por vários consumidores de API",
-  "criterion.hide-backend-discrepancies": "A API é destinada a proteger os consumidores da complexidade e das inconsistências do back-end.",
-  "criterion.value-prop-validated": "A proposta de valor da API foi revista e validada com as partes interessadas relevantes do negócio e dos consumidores.",
-  "criterion.consumer-segments-identified": "Os segmentos de consumidores de API (internos e externos) são identificados.",
-  "criterion.api-roadmap-defined": "Roteiros de alto nível para o desenvolvimento de API são estabelecidos.",
-  "criterion.architecture-patterns-validated": "Os padrões de arquitetura e plataforma da API escolhidos foram validados com as partes interessadas relevantes de arquitetura, segurança e plataforma.",
-  "criterion.design-reflects-business-value": "A conceção da API e as capacidades expostas refletem claramente o valor de negócio e as necessidades dos utilizadores.",
-  "criterion.api-consistency": "A conceção da API segue as nossas convenções partilhadas para o produto API e a conceção.",
-  "criterion.api-contract-tested": "O contrato de interface da API é testado e satisfaz os requisitos funcionais e não funcionais.",
-  "criterion.automation-workflow-validated": "O fluxo de trabalho, as regras, as integracoes e os contratos de interface relevantes foram validados e testados.",
-  "criterion.api-description-available": "A API e suas capacidades expostas são descritas de forma suficiente para revisão, auditoria e integração.",
-  "criterion.audit-passed": "A API é aprovada nas verificações de conformidade, segurança e auditoria.",
-  "criterion.audit-reports-shared": "Os resultados da auditoria e as decisões de correção são partilhados com as partes interessadas relevantes.",
-  "criterion.api-ready-for-publishing": "A API está pronta para ser disponibilizada e exposta através dos gateways e ambientes pretendidos.",
-  "criterion.api-documentation-ready": "A documentação da API orientada para os consumidores está suficientemente completa para publicação e integração.",
-  "criterion.consumer-support-ready": "Os processos de registo, suporte e comunicação estão prontos para os consumidores da API.",
-  "criterion.legal-compliance-clear": "Os requisitos legais, de privacidade e de conformidade para publicação são definidos e compreendidos."
+  "criterion.metrics-feedback-available": "Sinais de mercado relevantes, feedback ou conhecimento operacional estão disponíveis para orientar esta oportunidade de capacidade.",
+  "criterion.business-goals-defined": "Os objetivos de negócio estão definidos.",
+  "criterion.market-research-done": "A investigação de mercado identifica oportunidades de capacidade.",
+  "criterion.stakeholder-approval": "As partes interessadas relevantes concordam que vale a pena explorar e priorizar esta oportunidade de capacidade.",
+  "criterion.api-opportunity-documented": "A oportunidade de capacidade está identificada e documentada.",
+  "criterion.api-reusability": "A capacidade responde a uma necessidade clara de negócio e é reutilizável pelos utilizadores previstos.",
+  "criterion.hide-backend-discrepancies": "A interface selecionada fornece uma abstração adequada aos utilizadores.",
+  "criterion.value-prop-validated": "A proposta de valor da capacidade foi validada com partes interessadas de negócio e utilizadores.",
+  "criterion.consumer-segments-identified": "Os segmentos de utilizadores estão identificados.",
+  "criterion.api-roadmap-defined": "Está definido um roadmap de implementação de alto nível.",
+  "criterion.architecture-patterns-validated": "A arquitetura, plataforma e estilo de implementação escolhidos foram validados com as partes interessadas relevantes de arquitetura, segurança e plataforma.",
+  "criterion.design-reflects-business-value": "O desenho da interface e as capacidades expostas são rastreáveis ao valor de negócio e às necessidades dos utilizadores.",
+  "criterion.api-consistency": "O desenho da interface segue os standards e convenções de desenho acordados.",
+  "criterion.api-contract-tested": "O contrato de interface foi validado e testado face aos requisitos funcionais e não funcionais.",
+  "criterion.automation-workflow-validated": "O workflow, as regras, as integrações e os contratos de interface relevantes foram validados e testados.",
+  "criterion.api-description-available": "A interface e as suas capacidades estão documentadas de forma suficientemente clara para revisão, auditoria e onboarding.",
+  "criterion.audit-passed": "A solução passa as verificações de qualidade, segurança, conformidade e prontidão.",
+  "criterion.audit-reports-shared": "As conclusões da auditoria e as decisões de correção são partilhadas com as partes interessadas relevantes.",
+  "criterion.api-ready-for-publishing": "A capacidade está pronta para ser publicada ou disponibilizada através do mecanismo de entrega selecionado.",
+  "criterion.api-documentation-ready": "A documentação orientada para os utilizadores e os materiais de onboarding estão prontos.",
+  "criterion.consumer-support-ready": "Os processos de onboarding, suporte e comunicação para utilizadores estão prontos.",
+  "criterion.legal-compliance-clear": "Os requisitos legais, de privacidade e de conformidade para publicação ou disponibilização estão definidos e compreendidos."
 }
diff --git a/src/data/method/pt/labels.resources.json b/src/data/method/pt/labels.resources.json
index 3786cc0..5b646a1 100644
--- a/src/data/method/pt/labels.resources.json
+++ b/src/data/method/pt/labels.resources.json
@@ -2,25 +2,25 @@
   "resource.api-community-engagement-strategies.title": "Estratégias de envolvimento da comunidade API",
   "resource.api-community-engagement-strategies.description": "Um manual para promover a adoção de APIs, cultivando comunidades através de conteúdos, canais de apoio, ciclos de feedback e estratégias de envolvimento social.",
   "resource.api-community-engagement-strategies.outcomes": "Melhor compreensão dos princípios das estratégias de envolvimento da comunidade da API",
-  "resource.api-community-engagement-strategies.outcomes.1": "Abordagem normalizada usando as estratégias de envolvimento da comunidade da API",
+  "resource.api-community-engagement-strategies.outcomes.1": "Abordagem normalizada utilizando as estratégias de envolvimento da comunidade da API",
   "resource.api-community-engagement-strategies.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-community-engagement-strategies.steps": "Desenvolver estratégias de marketing para promover as APIs junto de públicos-alvo, incluindo redes sociais, blogues e webinars.",
   "resource.api-community-engagement-strategies.steps.1": "Criar materiais promocionais (por exemplo, estudos de casos, histórias de sucesso) que realcem o valor e as vantagens das APIs.",
   "resource.api-community-engagement-strategies.steps.2": "Criar materiais educativos (por exemplo, tutoriais, documentação) que expliquem as características, as vantagens e os padrões de utilização da API.",
-  "resource.api-community-engagement-strategies.steps.3": "Interagir com os consumidores da API através de ciclos de feedback, canais de apoio e fóruns da comunidade para compreender as suas necessidades e melhorar a adoção da API.",
+  "resource.api-community-engagement-strategies.steps.3": "Interagir com os utilizadores da API através de ciclos de feedback, canais de apoio e fóruns da comunidade para compreender as suas necessidades e melhorar a adoção da API.",
   "resource.api-community-engagement-strategies.steps.4": "Analisar as métricas de utilização da API e incorporar o feedback dos utilizadores nas iterações da API.",
   "resource.api-community-engagement-strategies.tips": "Personalize as estratégias de envolvimento da comunidade de API ao seu domínio",
-  "resource.api-community-engagement-strategies.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-community-engagement-strategies.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-compliance-best-practices.title": "Boas práticas de conformidade da API",
   "resource.api-compliance-best-practices.description": "Garantir que as APIs cumprem conformidade legal, regulamentar e interna através de documentação, controlos e validações automatizadas.",
   "resource.api-compliance-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de conformidade da API",
   "resource.api-compliance-best-practices.outcomes.1": "Abordagem normalizada utilizando as Melhores Práticas de Conformidade da API",
   "resource.api-compliance-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-compliance-best-practices.steps": "Documentar as medidas de conformidade e garantir que são comunicadas às partes interessadas e aos consumidores.",
+  "resource.api-compliance-best-practices.steps": "Documentar as medidas de conformidade e garantir que são comunicadas às partes interessadas e aos utilizadores.",
   "resource.api-compliance-best-practices.steps.1": "Implementar medidas para garantir que as APIs cumprem estes requisitos, incluindo encriptação de dados, controlos de acesso e pistas de auditoria.",
   "resource.api-compliance-best-practices.steps.2": "Utilizar listas de controlo, linters e ferramentas de teste para verificar a consistência e a conformidade com as normas.",
   "resource.api-compliance-best-practices.tips": "Personalizar as Melhores Práticas de Conformidade de API ao seu domínio",
-  "resource.api-compliance-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-compliance-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-development-best-practices.title": "Boas práticas de desenvolvimento de API",
   "resource.api-development-best-practices.description": "Orientações de implementação para transformar um contrato de interface da API validado numa base de código de API consistente e sustentável, utilizando bibliotecas padrão, padrões reutilizáveis e fluxos de trabalho de desenvolvimento alinhados.",
   "resource.api-development-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de desenvolvimento de API",
@@ -29,38 +29,38 @@
   "resource.api-development-best-practices.steps": "Aplique essas práticas ao contrato de interface da API validado e ao plano de implementação antes do início da codificação.",
   "resource.api-development-best-practices.steps.1": "Utilize frameworks, bibliotecas e padrões de codificação estabelecidos para implementar o contrato de forma consistente e sustentável.",
   "resource.api-development-best-practices.tips": "Utilize este recurso como orientação de implementação e lente de revisão, em vez de como um artefato independente obrigatório",
-  "resource.api-development-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-development-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-metrics-and-analytics.title": "Métricas e análise de API",
-  "resource.api-metrics-and-analytics.description": "Um recurso para definir, recolher e analisar o desempenho da API e os dados de utilização para alinhar os KPIs técnicos com os resultados comerciais.",
+  "resource.api-metrics-and-analytics.description": "Um recurso para definir, recolher e analisar o desempenho da API e os dados de utilização para alinhar os KPIs técnicos com os resultados de negócio.",
   "resource.api-metrics-and-analytics.outcomes": "Melhor compreensão dos princípios de métrica e análise de API",
-  "resource.api-metrics-and-analytics.outcomes.1": "Abordagem normalizada usando métricas e análise de API",
+  "resource.api-metrics-and-analytics.outcomes.1": "Abordagem normalizada utilizando métricas e análise de API",
   "resource.api-metrics-and-analytics.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-metrics-and-analytics.steps": "Identificar indicadores-chave de desempenho (KPIs) para medir o sucesso da API em relação aos objetivos de negócio.",
   "resource.api-metrics-and-analytics.steps.1": "Definir e monitorizar as métricas de desempenho (por exemplo, chamadas APIs, latência, taxas de erro) e as métricas de adoção (por exemplo, NPS).",
   "resource.api-metrics-and-analytics.steps.2": "Monitorizar as iniciativas APIs para garantir o cumprimento das orientações operacionais e das práticas de governação",
   "resource.api-metrics-and-analytics.tips": "Personalizar as métricas e análise de API ao seu domínio",
-  "resource.api-metrics-and-analytics.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-metrics-and-analytics.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-onboarding-best-practices.title": "Boas práticas de integração de API",
-  "resource.api-onboarding-best-practices.description": "Boas práticas para simplificar as jornadas de integração do consumidor da API com registo passo a passo, descoberta e orientação na primeira chamada.",
+  "resource.api-onboarding-best-practices.description": "Boas práticas para simplificar as jornadas de integração do utilizador da API com registo passo a passo, descoberta e orientação na primeira chamada.",
   "resource.api-onboarding-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de integração de API",
-  "resource.api-onboarding-best-practices.outcomes.1": "Abordagem normalizada usando as boas práticas de integração de API",
+  "resource.api-onboarding-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de integração de API",
   "resource.api-onboarding-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-onboarding-best-practices.steps": "Definir o percurso do consumidor da API desde a descoberta até à resolução de problemas, identificando os principais pontos de contacto e os pontos problemáticos.",
-  "resource.api-onboarding-best-practices.steps.1": "Desenvolver processos de integração e recursos para ajudar os consumidores de API a compreender como utilizar as APIs de forma eficaz.",
-  "resource.api-onboarding-best-practices.steps.2": "Documentar a forma como os consumidores encontram e utilizam a API, incluindo processos de integração e registo.",
+  "resource.api-onboarding-best-practices.steps": "Definir o percurso do utilizador da API desde a descoberta até à resolução de problemas, identificando os principais pontos de contacto e os pontos problemáticos.",
+  "resource.api-onboarding-best-practices.steps.1": "Desenvolver processos de integração e recursos para ajudar os utilizadores de API a compreender como utilizar as APIs de forma eficaz.",
+  "resource.api-onboarding-best-practices.steps.2": "Documentar a forma como os utilizadores encontram e utilizam a API, incluindo processos de integração e registo.",
   "resource.api-onboarding-best-practices.tips": "Personalizar as boas práticas de integração de API ao seu domínio",
-  "resource.api-onboarding-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-onboarding-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-portfolio-management-guidelines.title": "Diretrizes de gestão da carteira API",
   "resource.api-portfolio-management-guidelines.description": "Um guia para gerir estrategicamente o conjunto de APIs de uma organização - priorizando APIs, alocando recursos e monitorando o desempenho ao longo de todo o ciclo de vida.",
   "resource.api-portfolio-management-guidelines.outcomes": "Melhor compreensão dos princípios orientadores da gestão de carteiras API",
-  "resource.api-portfolio-management-guidelines.outcomes.1": "Abordagem normalizada usando as diretrizes de gestão de portfólio da API",
+  "resource.api-portfolio-management-guidelines.outcomes.1": "Abordagem normalizada utilizando as diretrizes de gestão de portfólio da API",
   "resource.api-portfolio-management-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-portfolio-management-guidelines.steps": "Definir práticas de gestão da carteira que descrevam os processos de gestão da carteira de API, incluindo a definição de prioridades, a monitorização e a otimização.",
   "resource.api-portfolio-management-guidelines.steps.1": "Definir práticas de gestão orçamental e de recursos que descrevam os processos de gestão de orçamentos e recursos para iniciativas de API.",
   "resource.api-portfolio-management-guidelines.steps.2": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor de negócio, no impacto e no alinhamento com as iniciativas estratégicas.",
   "resource.api-portfolio-management-guidelines.steps.3": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objetivos de negócio.",
   "resource.api-portfolio-management-guidelines.tips": "Personalizar as Diretrizes de Gestão de Portfólio API ao seu domínio",
-  "resource.api-portfolio-management-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-portfolio-management-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-security-best-practices.title": "Boas práticas de segurança da API",
   "resource.api-security-best-practices.description": "Um conjunto de controlos acionáveis para proteger APIs, incluindo autenticação, autorização, encriptação, limitação de taxas e verificações de conformidade ao nível do pipeline.",
   "resource.api-security-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de segurança da API",
@@ -70,7 +70,7 @@
   "resource.api-security-best-practices.steps.1": "Implemente medidas de segurança como autenticação, autorização, encriptação e limitação de taxas para proteger as APIs de ameaças.",
   "resource.api-security-best-practices.steps.2": "Implementar verificações de segurança automatizadas e validações de conformidade no pipeline CI/CD para garantir que as APIs são seguras e compatíveis.",
   "resource.api-security-best-practices.tips": "Personalize as boas práticas de segurança de API ao seu domínio",
-  "resource.api-security-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-security-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-team-structure-guidelines.title": "Diretrizes da estrutura da equipa API",
   "resource.api-team-structure-guidelines.description": "Orientação organizacional para a definição de funções e responsabilidades nas equipas de API para garantir clareza, colaboração e responsabilidade.",
   "resource.api-team-structure-guidelines.outcomes": "Melhor compreensão dos princípios orientadores da estrutura da equipa API",
@@ -78,7 +78,7 @@
   "resource.api-team-structure-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-team-structure-guidelines.steps": "Definir estruturas de equipa e funções para equipas de API, incluindo proprietários de produtos de API, programadores, arquitectos e operações.",
   "resource.api-team-structure-guidelines.tips": "Personalizar as Diretrizes da estrutura da equipa API ao seu domínio",
-  "resource.api-team-structure-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-team-structure-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-testing-best-practices.title": "Boas práticas de teste de API",
   "resource.api-testing-best-practices.description": "Diretrizes para a implementação de testes automatizados funcionais, de desempenho e de segurança ao longo do ciclo de vida da API.",
   "resource.api-testing-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de teste de API",
@@ -88,7 +88,7 @@
   "resource.api-testing-best-practices.steps.1": "Integrar testes funcionais e não funcionais no pipeline CI/CD para garantir que as APIs cumprems normas de qualidade.",
   "resource.api-testing-best-practices.steps.2": "Utilizar ferramentas de teste automatizadas para validar a funcionalidade, a segurança e o desempenho da API.",
   "resource.api-testing-best-practices.tips": "Personalize as boas práticas de teste de API ao seu domínio",
-  "resource.api-testing-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-testing-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-training-programs.title": "Programas de formação API",
   "resource.api-training-programs.description": "Um roteiro para melhorar as competências das equipas com percursos de aprendizagem estruturados em design, governação, desempenho e segurança de API.",
   "resource.api-training-programs.outcomes": "Melhor compreensão dos princípios dos programas de formação API",
@@ -99,26 +99,26 @@
   "resource.api-training-programs.steps.2": "Fornecer formação e recursos para ajudar as equipas a adotar uma mentalidade de prioridade à API e a compreender as vantagens das APIs.",
   "resource.api-training-programs.steps.3": "Fornecer programas de formação, workshops e recursos para ajudar as equipas a melhorar as suas competências e conhecimentos em matéria de API.",
   "resource.api-training-programs.tips": "Personalizar os programas de formação API ao seu domínio",
-  "resource.api-training-programs.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-training-programs.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-versioning-best-practices.title": "Boas práticas de controlo de versões da API",
-  "resource.api-versioning-best-practices.description": "Estratégias para introduzir, manter e retirar versões de API, preservando a compatibilidade com versões anteriores e a confiança dos consumidores.",
+  "resource.api-versioning-best-practices.description": "Estratégias para introduzir, manter e retirar versões de API, preservando a compatibilidade com versões anteriores e a confiança dos utilizadores.",
   "resource.api-versioning-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de controlo de versões da API",
-  "resource.api-versioning-best-practices.outcomes.1": "Abordagem normalizada usando as boas práticas de controlo de versões da API",
+  "resource.api-versioning-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de controlo de versões da API",
   "resource.api-versioning-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-versioning-best-practices.steps": "Definir estratégias de controlo de versões para as APIs para gerir as alterações e garantir a compatibilidade com as versões anteriores.",
   "resource.api-versioning-best-practices.tips": "Personalizar as boas práticas de controlo de versões de API ao seu domínio",
-  "resource.api-versioning-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-versioning-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.apiops-CI-CD-for-apis.title": "APIOps CI/CD para APIs",
   "resource.apiops-CI-CD-for-apis.description": "Orientação de disponibilização que integra tarefas do ciclo de vida da API - design, teste, governação - em pipelines de integração e entrega contínuas.",
   "resource.apiops-CI-CD-for-apis.outcomes": "Melhor compreensão dos princípios de CI/CD para APIs",
-  "resource.apiops-CI-CD-for-apis.outcomes.1": "Abordagem normalizada usando CI/CD para APIs",
+  "resource.apiops-CI-CD-for-apis.outcomes.1": "Abordagem normalizada utilizando CI/CD para APIs",
   "resource.apiops-CI-CD-for-apis.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.apiops-CI-CD-for-apis.steps": "Utilizar pipelines CI/CD para automatizar os processos de construção, teste e implementação, garantindo uma qualidade e rastreabilidade consistentes.",
   "resource.apiops-CI-CD-for-apis.steps.1": "Integrar testes automatizados no pipeline CI/CD para garantir a validação contínua da qualidade da API.",
   "resource.apiops-CI-CD-for-apis.steps.2": "Implementar estratégias de disponibilização (por exemplo, disponibilizações blue-green, lançamentos canários) para minimizar os riscos durante os lançamentos de API.",
   "resource.apiops-CI-CD-for-apis.steps.3": "Crie o hábito de analisar os indicadores e planear actividades de melhoria contínua.",
   "resource.apiops-CI-CD-for-apis.tips": "Personalize as APIs CI/CD For ao seu domínio",
-  "resource.apiops-CI-CD-for-apis.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.apiops-CI-CD-for-apis.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.competitor-analysis-template.title": "Modelo de análise da concorrência",
   "resource.competitor-analysis-template.description": "Uma folha de cálculo estruturada para comparar as suas ofertas de API com a concorrência, mapeando os pontos fortes, os pontos fracos e os diferenciadores de valor.",
   "resource.competitor-analysis-template.outcomes": "Melhor compreensão dos princípios do modelo de análise da concorrência",
@@ -127,7 +127,7 @@
   "resource.competitor-analysis-template.steps": "Efetuar uma análise da concorrência para identificar os principais concorrentes e as suas ofertas de API.",
   "resource.competitor-analysis-template.steps.1": "Analisar as APIs da concorrência para compreender os seus pontos fortes, fracos e pontos de venda únicos.",
   "resource.competitor-analysis-template.tips": "Personalizar o modelo de análise da concorrência ao seu domínio",
-  "resource.competitor-analysis-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.competitor-analysis-template.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.contract-first-design.title": "Primeira conceção do contrato",
   "resource.contract-first-design.description": "Uma diretriz que defende abordagens API-first utilizando contratos formais (por exemplo, OpenAPI) para alinhar as partes interessadas antes do desenvolvimento.",
   "resource.contract-first-design.outcomes": "Melhor compreensão dos princípios de conceção da primeira fase do contrato",
@@ -137,15 +137,15 @@
   "resource.contract-first-design.steps.1": "Definir contratos de interface da API que descrevam as expectativas, responsabilidades e diretrizes de utilização para cada API.",
   "resource.contract-first-design.steps.2": "Utilizar formatos normalizados (por exemplo, OpenAPI, AsyncAPI) para criar contratos de interface da API legíveis por máquina que sejam fáceis de partilhar e validar.",
   "resource.contract-first-design.tips": "Personalize a conceção do Contract First ao seu domínio",
-  "resource.contract-first-design.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.contract-first-design.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.cross-functional-collaboration-best-practices.title": "Boas práticas de colaboração interfuncional",
-  "resource.cross-functional-collaboration-best-practices.description": "Práticas para facilitar a comunicação e o alinhamento entre as equipas comerciais e técnicas ao planear ou fornecer APIs.",
+  "resource.cross-functional-collaboration-best-practices.description": "Práticas para facilitar a comunicação e o alinhamento entre as equipas de negócio e técnicas ao planear ou fornecer APIs.",
   "resource.cross-functional-collaboration-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de colaboração interfuncional",
   "resource.cross-functional-collaboration-best-practices.outcomes.1": "Abordagem normalizada utilizando as boas práticas de colaboração interfuncional",
   "resource.cross-functional-collaboration-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.cross-functional-collaboration-best-practices.steps": "Incentivar a colaboração multifuncional entre equipas de API, unidades empresariais e partes interessadas para alinhar as iniciativas de API com os objetivos empresariais.",
   "resource.cross-functional-collaboration-best-practices.tips": "Personalize as Melhores Práticas de Colaboração Interfuncional ao seu domínio",
-  "resource.cross-functional-collaboration-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.cross-functional-collaboration-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.data-privacy-guidelines.title": "Diretrizes de privacidade de dados",
   "resource.data-privacy-guidelines.description": "Considerações de design para garantir que as APIs cumprem os regulamentos de proteção de dados, como o RGPD, através de anonimização e controlos de acesso.",
   "resource.data-privacy-guidelines.outcomes": "Melhor compreensão dos princípios das diretrizes relativas à privacidade dos dados",
@@ -153,7 +153,7 @@
   "resource.data-privacy-guidelines.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.data-privacy-guidelines.steps": "Garantir a privacidade dos dados dos utilizadores através da implementação de medidas de proteção de dados, como a anonimização e os controlos de acesso.",
   "resource.data-privacy-guidelines.tips": "Personalizar as Diretrizes de Privacidade de Dados ao seu domínio",
-  "resource.data-privacy-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.data-privacy-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.domain-canvas.title": "Canvas de Domínio",
   "resource.domain-canvas.description": "Uma ferramenta de modelação para definir e comunicar as principais entidades e relações no seu domínio, assegurando a consistência semântica entre APIs.",
   "resource.domain-canvas.outcomes": "Melhor compreensão dos princípios do domínio canvas",
@@ -161,11 +161,11 @@
   "resource.domain-canvas.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.domain-canvas.steps": "Definir entidades principais, os seus atributos e relações para criar um entendimento concetual partilhado entre APIs.",
   "resource.domain-canvas.tips": "Personalizar o Canvas de Domínio ao seu domínio",
-  "resource.domain-canvas.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.domain-canvas.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.ecosystem-vision-template.title": "Modelo de visão do ecossistema",
   "resource.ecosystem-vision-template.description": "Uma ferramenta de planeamento estratégico para definir o ecossistema API, incluindo parceiros-alvo, cadeias de valor e oportunidades de integração.",
   "resource.ecosystem-vision-template.outcomes": "Melhor compreensão dos princípios do modelo de visão do ecossistema",
-  "resource.ecosystem-vision-template.outcomes.1": "Abordagem normalizada usando o Modelo de Visão do Ecossistema",
+  "resource.ecosystem-vision-template.outcomes.1": "Abordagem normalizada utilizando o Modelo de Visão do Ecossistema",
   "resource.ecosystem-vision-template.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.ecosystem-vision-template.steps": "Realizar estudos de mercado para identificar tendências, oportunidades e ameaças no panorama das APIs.",
   "resource.ecosystem-vision-template.steps.1": "Identificar os principais parceiros e intervenientes do ecosistema que irão beneficiar ou contribuir para o ecosistema.",
@@ -175,7 +175,7 @@
   "resource.ecosystem-vision-template.steps.5": "Defina a visão do ecossistema para as suas APIs, incluindo a forma como estas irão interagir com outros sistemas e plataformas.",
   "resource.ecosystem-vision-template.steps.6": "Conceber APIs para permitir uma integração e colaboração perfeitas no ecossistema.",
   "resource.ecosystem-vision-template.tips": "Personalizar o modelo de visão do ecossistema ao seu domínio",
-  "resource.ecosystem-vision-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.ecosystem-vision-template.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.industry-standards-and-best-practices.title": "Normas e boas práticas do sector",
   "resource.industry-standards-and-best-practices.description": "Um recurso de referência para alinhar a conceção e a operação da API com estruturas e especificações amplamente reconhecidas do sector.",
   "resource.industry-standards-and-best-practices.outcomes": "Melhor compreensão das normas do sector e dos princípios das boas práticas",
@@ -183,7 +183,7 @@
   "resource.industry-standards-and-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.industry-standards-and-best-practices.steps": "Identificar as normas e as boas práticas do sector para garantir que as APIs são competitivas e estão em conformidade.",
   "resource.industry-standards-and-best-practices.tips": "Personalize os padrões e as boas práticas da indústria ao seu domínio",
-  "resource.industry-standards-and-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.industry-standards-and-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.partner-integration-guidelines.title": "Diretrizes de integração de parceiros",
   "resource.partner-integration-guidelines.description": "Listas de verificação de integração e padrões de comunicação para gerir os aspectos técnicos e legais das relações com APIs de terceiros.",
   "resource.partner-integration-guidelines.outcomes": "Melhor compreensão dos princípios das diretrizes de integração de parceiros",
@@ -192,7 +192,7 @@
   "resource.partner-integration-guidelines.steps": "Estabelecer processos de integração e orientações para colaborar com os parceiros, incluindo a integração técnica, a partilha de dados e o apoio.",
   "resource.partner-integration-guidelines.steps.1": "Monitorize o desempenho e a conformidade da API do parceiro para garantir a fiabilidade e o alinhamento com a sua estratégia de API.",
   "resource.partner-integration-guidelines.tips": "Personalizar as Diretrizes de Integração de Parceiros ao seu domínio",
-  "resource.partner-integration-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.partner-integration-guidelines.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.role-communication-best-practices.title": "Boas práticas de comunicação de funções",
   "resource.role-communication-best-practices.description": "Ferramentas para definir e documentar quem é responsável por quê nas iniciativas de API, garantindo que as transferências e a responsabilidade sejam claras.",
   "resource.role-communication-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de comunicação de funções",
@@ -201,7 +201,7 @@
   "resource.role-communication-best-practices.steps": "Estabelecer responsabilidades claras para cada função, incluindo a conceção, o desenvolvimento, os testes e as operações da API.",
   "resource.role-communication-best-practices.steps.1": "Assegurar que as funções e responsabilidades são comunicadas a todos os membros da equipa e partes interessadas para garantir o alinhamento.",
   "resource.role-communication-best-practices.tips": "Personalizar as Melhores Práticas de Comunicação de Funções ao seu domínio",
-  "resource.role-communication-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.role-communication-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.scalable-infrastructure-best-practices.title": "Boas práticas de infraestrutura escalável",
   "resource.scalable-infrastructure-best-practices.description": "Orientação arquitetónica para garantir que as APIs são implementadas em infra-estruturas que podem lidar elasticamente com picos de utilização e crescimento.",
   "resource.scalable-infrastructure-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de infra-estruturas escaláveis",
@@ -210,7 +210,7 @@
   "resource.scalable-infrastructure-best-practices.steps": "Conceber a infraestrutura da API para ser escalável e resiliente, utilizando padrões e tecnologias nativos da nuvem.",
   "resource.scalable-infrastructure-best-practices.steps.1": "Monitorizar o desempenho e a capacidade da infraestrutura para garantir que esta consegue dar resposta à crescente procura.",
   "resource.scalable-infrastructure-best-practices.tips": "Personalize as Melhores Práticas de Infraestrutura Escalável ao seu domínio",
-  "resource.scalable-infrastructure-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.scalable-infrastructure-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.service-agreement-template.title": "Modelo de contrato de serviço",
   "resource.service-agreement-template.description": "Um formato de acordo personalizável que define expectativas, SLAs, responsabilidades e termos de acesso para o consumo de API.",
   "resource.service-agreement-template.outcomes": "Melhor compreensão dos princípios do modelo de contrato de prestação de serviços",
@@ -220,15 +220,15 @@
   "resource.service-agreement-template.steps.1": "Utilize formatos normalizados para criar contratos de serviço legíveis por máquina que sejam fáceis de partilhar e validar.",
   "resource.service-agreement-template.steps.2": "Assegurar que os acordos de serviço são revistos e aprovados pelas partes interessadas para garantir o alinhamento e a clareza.",
   "resource.service-agreement-template.tips": "Personalizar o modelo de contrato de serviço ao seu domínio",
-  "resource.service-agreement-template.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.service-agreement-template.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.stakeholder-engagement-best-practices.title": "Boas práticas de envolvimento das partes interessadas",
   "resource.stakeholder-engagement-best-practices.description": "Tácticas de envolvimento para alinhar as partes interessadas internas e externas em torno dos objetivos, valor e governação partilhados da API.",
   "resource.stakeholder-engagement-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de envolvimento das partes interessadas",
-  "resource.stakeholder-engagement-best-practices.outcomes.1": "Abordagem normalizada usando as Melhores Práticas de Envolvimento das Partes Interessadas",
+  "resource.stakeholder-engagement-best-practices.outcomes.1": "Abordagem normalizada utilizando as Melhores Práticas de Envolvimento das Partes Interessadas",
   "resource.stakeholder-engagement-best-practices.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.stakeholder-engagement-best-practices.steps": "Envolver as partes interessadas para garantir o alinhamento e o apoio às iniciativas da API.",
   "resource.stakeholder-engagement-best-practices.tips": "Personalize as Melhores Práticas de Envolvimento das Partes Interessadas ao seu domínio",
-  "resource.stakeholder-engagement-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.stakeholder-engagement-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.test-automation-frameworks.title": "Estruturas de automatização de testes",
   "resource.test-automation-frameworks.description": "Ferramentas e padrões recomendados para automatizar testes de contrato, regressão e integração de API em vários ambientes.",
   "resource.test-automation-frameworks.outcomes": "Melhor compreensão dos princípios das estruturas de automatização de testes",
@@ -236,7 +236,7 @@
   "resource.test-automation-frameworks.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.test-automation-frameworks.steps": "Implementar estruturas de automatização de testes que apoiem os testes de contrato, os testes de integração e os testes de ponta a ponta.",
   "resource.test-automation-frameworks.tips": "Personalizar as estruturas de automatização de testes ao seu domínio",
-  "resource.test-automation-frameworks.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.test-automation-frameworks.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.vendor-management-best-practices.title": "Boas práticas de gestão de fornecedores",
   "resource.vendor-management-best-practices.description": "Estrutura para avaliar e gerir fornecedores externos de API e integrações de terceiros com base no risco, desempenho e conformidade.",
   "resource.vendor-management-best-practices.outcomes": "Melhor compreensão dos princípios das boas práticas de gestão de fornecedores",
@@ -245,24 +245,24 @@
   "resource.vendor-management-best-practices.steps": "Estabelecer processos de gestão de fornecedores para avaliar, integrar e monitorizar fornecedores de API de terceiros.",
   "resource.vendor-management-best-practices.steps.1": "Definir critérios para avaliar as APIs dos fornecedores, incluindo fiabilidade, segurança e conformidade.",
   "resource.vendor-management-best-practices.tips": "Personalize as Melhores Práticas de Gestão de Fornecedores ao seu domínio",
-  "resource.vendor-management-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.vendor-management-best-practices.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-audit-checklist.title": "Lista de verificação de auditoria da API",
-  "resource.api-audit-checklist.description": "Uma lista de verificação baseada no ciclo de vida para verificar a prontidão da API em design, entrega, publicação e conformidade usando critérios de auditoria e evidências definidos.",
+  "resource.api-audit-checklist.description": "Uma lista de verificação baseada no ciclo de vida para verificar a prontidão da API em design, entrega, publicação e conformidade utilizando critérios de auditoria e evidências definidos.",
   "resource.api-audit-checklist.outcomes": "Melhor compreensão dos princípios da lista de controlo de auditoria da API",
-  "resource.api-audit-checklist.outcomes.1": "Abordagem normalizada usando a lista de verificação de auditoria da API",
+  "resource.api-audit-checklist.outcomes.1": "Abordagem normalizada utilizando a lista de verificação de auditoria da API",
   "resource.api-audit-checklist.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
   "resource.api-audit-checklist.steps": "Utilize a lista de verificação de auditoria da API para garantir que a conceção da API cumpre os requisitos funcionais e não funcionais, incluindo segurança, desempenho e conformidade.",
   "resource.api-audit-checklist.steps.1": "Realize auditorias para avaliar a cobertura do ciclo de vida e verificar se a API satisfaz os padrões de negócio, conceção e operacionais.",
   "resource.api-audit-checklist.steps.2": "Certifique-se de que a documentação, os modelos de segurança, a configuração do gateway e os requisitos legais estejam claramente definidos, validados e comprovados por evidências.",
-  "resource.api-audit-checklist.tips": "Cada item de auditoria vincula o trabalho do ciclo de vida (etapas), as diretrizes regulatórias e as evidências de apoio para fornecer uma visão clara da prontidão da API.",
+  "resource.api-audit-checklist.tips": "Cada item de auditoria associa o trabalho do ciclo de vida (etapas), as diretrizes regulatórias e as evidências de apoio para fornecer uma visão clara da prontidão da API.",
   "resource.api-audit-checklist.tips.1": "Utilize a Lista de Verificação de Auditoria de API de forma colaborativa entre as funções de negócios e tecnologia",
   "resource.api-business-model-canvas.title": "Canvas do Modelo de Negócio da API",
-  "resource.api-business-model-canvas.description": "Avaliar estrategicamente a viabilidade do negócio de API, mapeando propostas de valor, segmentos de consumidores e recursos-chave.",
+  "resource.api-business-model-canvas.description": "Avaliar estrategicamente a viabilidade do negócio de API, mapeando propostas de valor, segmentos de utilizadores e recursos-chave.",
   "resource.api-business-model-canvas.outcomes": "Estratégia comercial clara para APIs",
   "resource.api-business-model-canvas.outcomes.1": "Identificação dos principais recursos e parceiros",
   "resource.api-business-model-canvas.outcomes.2": "Alinhamento das características da API com os objetivos de negócio",
   "resource.api-business-model-canvas.steps": "Resumir a proposta de valor da API",
-  "resource.api-business-model-canvas.steps.1": "Definir segmentos de consumidores",
+  "resource.api-business-model-canvas.steps.1": "Definir segmentos de utilizadores",
   "resource.api-business-model-canvas.steps.2": "Identificar estratégias de relações com os promotores",
   "resource.api-business-model-canvas.steps.3": "Mapear os canais de distribuição",
   "resource.api-business-model-canvas.steps.4": "documentar os principais recursos e actividades",
@@ -272,31 +272,31 @@
   "resource.api-business-model-canvas.tips.1": "Utilizar métricas como custo vs. benefício para dar prioridade às oportunidades",
   "resource.api-business-model-canvas.tips.2": "Validar os resultados com as principais partes interessadas",
   "resource.api-design-principles.title": "Princípios de conceção da API",
-  "resource.api-design-principles.description": "Um guia conciso sobre usabilidade, descobribilidade e consistência da API, baseado em regras de design compartilhadas e nas necessidades reais dos consumidores.",
+  "resource.api-design-principles.description": "Um guia conciso sobre usabilidade, descobribilidade e consistência da API, baseado em regras de design partilhadas e nas necessidades reais dos utilizadores.",
   "resource.api-design-principles.outcomes": "Melhor compreensão dos princípios de conceção das API",
   "resource.api-design-principles.outcomes.1": "Abordagem normalizada utilizando os princípios de conceção da API",
   "resource.api-design-principles.outcomes.2": "Melhoria da implementação das práticas de API relacionadas",
-  "resource.api-design-principles.steps": "**Conceção que coloca o consumidor em primeiro lugar:** iniciar cada ciclo de APIOps recolhendo os objetivos do utilizador e os termos do domínio para que as APIs resolvam problemas reais.",
+  "resource.api-design-principles.steps": "**Conceção que coloca o utilizador em primeiro lugar:** iniciar cada ciclo de APIOps recolhendo os objetivos do utilizador e os termos do domínio para que as APIs resolvam problemas reais.",
   "resource.api-design-principles.steps.1": "**Nomeação e comportamento consistentes:** aplicar convenções partilhadas para recursos, erros e formatos para tornar as APIs previsíveis.",
   "resource.api-design-principles.steps.2": "**Orientado para contratos:** capturar a interface com OpenAPI ou AsyncAPI antes da codificação para alinhar as equipas e permitir a automatização.",
   "resource.api-design-principles.steps.3": "**Usabilidade e facilidade de descoberta:** fornecer documentação e exemplos claros para que os programadores compreendam rapidamente como utilizar a API.",
-  "resource.api-design-principles.steps.4": "**Iterar com segurança:** desenvolver os projetos em pequenos incrementos, com versões, para que as alterações não perturbem os consumidores existentes.",
+  "resource.api-design-principles.steps.4": "**Iterar com segurança:** desenvolver os projetos em pequenos incrementos, com versões, para que as alterações não perturbem os utilizadores existentes.",
   "resource.api-design-principles.tips": "Personalizar os princípios de conceção de API ao seu domínio",
-  "resource.api-design-principles.tips.1": "Utilize-o de forma colaborativa entre as funções comerciais e tecnológicas",
+  "resource.api-design-principles.tips.1": "Utilize-o de forma colaborativa entre as funções de negócio e tecnológicas",
   "resource.api-value-proposition-canvas.title": "Canvas da Proposta de Valor da API",
   "resource.api-value-proposition-canvas.description": "Alinhar as funcionalidades da API com as necessidades dos utilizadores, mapeando tarefas, problemas e ganhos para os produtos da API.",
   "resource.api-value-proposition-canvas.outcomes": "Desenvolvimento de funcionalidades específicas",
   "resource.api-value-proposition-canvas.outcomes.1": "Alinhamento com as necessidades dos utilizadores",
-  "resource.api-value-proposition-canvas.outcomes.2": "Melhoria da satisfação do consumidor da API",
+  "resource.api-value-proposition-canvas.outcomes.2": "Melhoria da satisfação do utilizador da API",
   "resource.api-value-proposition-canvas.steps": "Listar as tarefas do percurso do utilizador",
   "resource.api-value-proposition-canvas.steps.1": "Identificar as características que proporcionam os ganhos esperados",
   "resource.api-value-proposition-canvas.steps.2": "Definir características para enfrentar os desafios",
   "resource.api-value-proposition-canvas.steps.3": "Mapear características para produtos API",
   "resource.api-value-proposition-canvas.tips": "Utilizar os dados do Canvas do Percurso do Cliente",
   "resource.api-value-proposition-canvas.tips.1": "Destaque para as características que aliviam as dores ou aumentam os ganhos",
-  "resource.api-value-proposition-canvas.tips.2": "Validar as características com os consumidores da API para garantir o alinhamento",
+  "resource.api-value-proposition-canvas.tips.2": "Validar as características com os utilizadores da API para garantir o alinhamento",
   "resource.business-impact-canvas.title": "Canvas de Impacto no Negócio",
-  "resource.business-impact-canvas.description": "Conceber uma arquitetura de plataforma API escalável e segura que satisfaça os requisitos comerciais e técnicos.",
+  "resource.business-impact-canvas.description": "Conceber uma arquitetura de plataforma API escalável e segura que satisfaça os requisitos de negócio e técnicos.",
   "resource.business-impact-canvas.outcomes": "Infraestrutura API escalável",
   "resource.business-impact-canvas.outcomes.1": "Segurança e conformidade melhoradas",
   "resource.business-impact-canvas.outcomes.2": "Desempenho melhorado da API",
@@ -310,7 +310,7 @@
   "resource.business-impact-canvas.tips.1": "Utilizar incidentes anteriores para identificar potenciais riscos",
   "resource.business-impact-canvas.tips.2": "Dar prioridade às APIs críticas com o maior impacto comercial",
   "resource.capacity-canvas.title": "Canvas de Capacidade",
-  "resource.capacity-canvas.description": "Planear a capacidade da API para satisfazer as exigências comerciais actuais e futuras, garantindo a escalabilidade e o desempenho.",
+  "resource.capacity-canvas.description": "Planear a capacidade da API para satisfazer as exigências de negócio actuais e futuras, garantindo a escalabilidade e o desempenho.",
   "resource.capacity-canvas.outcomes": "Alinhamento da capacidade da API com os volumes de negócios",
   "resource.capacity-canvas.outcomes.1": "Preparado para as futuras tendências de consumo",
   "resource.capacity-canvas.outcomes.2": "Estratégias definidas de armazenamento em cache e limitação de taxa",
@@ -354,7 +354,7 @@
   "resource.graphql-canvas.outcomes": "Conceção da API GraphQL estruturada",
   "resource.graphql-canvas.outcomes.1": "Tipos definidos e suas relações",
   "resource.graphql-canvas.outcomes.2": "Limpar consultas, mutações e subscrições",
-  "resource.graphql-canvas.steps": "Que problemas estão os consumidores de API a tentar resolver? De que dados necessitam?",
+  "resource.graphql-canvas.steps": "Que problemas estão os utilizadores de API a tentar resolver? De que dados necessitam?",
   "resource.graphql-canvas.steps.1": "Definir tipos GraphQL e seus atributos: Quais são os principais tipos expostos (por exemplo, utilizador, encomenda, produto)?",
   "resource.graphql-canvas.steps.2": "Mapear relações entre tipos: Como é que os tipos se relacionam uns com os outros em consultas aninhadas?",
   "resource.graphql-canvas.steps.3": "Especificar consultas para a recuperação de dados",
@@ -366,7 +366,7 @@
   "resource.graphql-canvas.tips.1": "documentar exemplos de consultas e mutações",
   "resource.graphql-canvas.tips.2": "Assegurar que os nomes dos tipos são descritivos e coerentes",
   "resource.interaction-canvas.title": "Canvas de Interação",
-  "resource.interaction-canvas.description": "Definir interações API, fluxos de trabalho e respostas esperadas para garantir uma experiência consistente do consumidor API.",
+  "resource.interaction-canvas.description": "Definir interações API, fluxos de trabalho e respostas esperadas para garantir uma experiência consistente do utilizador API.",
   "resource.interaction-canvas.outcomes": "Fluxos de trabalho de interação API claros",
   "resource.interaction-canvas.outcomes.1": "Entradas e saídas definidas para cada interação",
   "resource.interaction-canvas.outcomes.2": "Regras de validação consistentes em todas as interações",
@@ -379,12 +379,12 @@
   "resource.interaction-canvas.tips.1": "Simular interações com dados simulados para validar fluxos de trabalho",
   "resource.interaction-canvas.tips.2": "documentar as respostas esperadas para interações bem e mal sucedidas",
   "resource.location-canvas.title": "Canvas de Localização",
-  "resource.location-canvas.description": "Mapeie as localizações dos fornecedores e consumidores de API para garantir a conformidade e o desempenho em todas as regiões.",
+  "resource.location-canvas.description": "Mapeie as localizações dos fornecedores e utilizadores de API para garantir a conformidade e o desempenho em todas as regiões.",
   "resource.location-canvas.outcomes": "Conformidade com a regulamentação local",
   "resource.location-canvas.outcomes.1": "Desempenho optimizado da API em todas as regiões",
   "resource.location-canvas.outcomes.2": "Melhoria da compreensão das necessidades regionais",
   "resource.location-canvas.steps": "Mapa de localização dos fornecedores de API.",
-  "resource.location-canvas.steps.1": "Documentar a localização dos consumidores.",
+  "resource.location-canvas.steps.1": "Documentar a localização dos utilizadores.",
   "resource.location-canvas.steps.2": "Identificar os regulamentos aplicáveis.",
   "resource.location-canvas.steps.3": "Documentar onde os dados devem residir.",
   "resource.location-canvas.steps.4": "Assegurar que as APIs estão acessíveis em todas as regiões da rede previstas.",
@@ -405,38 +405,141 @@
   "resource.rest-canvas.tips.1": "Assegurar que os URIs dos recursos são intuitivos e coerentes",
   "resource.rest-canvas.tips.2": "tratamento de erros de documentos e códigos de resposta",
   "resource.capability-value-proposition-canvas.title": "Canvas da Proposta de Valor da Capacidade",
-  "resource.capability-value-proposition-canvas.description": "Um canvas independente da tecnologia para mapear tarefas, ganhos, dores e capacidades reutilizáveis candidatas dos consumidores antes de selecionar um estilo de integração.",
+  "resource.capability-value-proposition-canvas.description": "Um canvas independente da tecnologia para mapear tarefas, ganhos, dores e capacidades reutilizáveis candidatas dos utilizadores antes de selecionar um estilo de implementação.",
   "resource.capability-value-proposition-canvas.outcomes": "Proposta de valor clara para a capacidade reutilizável",
-  "resource.capability-value-proposition-canvas.outcomes.1": "Tarefas, ganhos e dores dos consumidores captados sem assumir uma tecnologia",
+  "resource.capability-value-proposition-canvas.outcomes.1": "Tarefas, ganhos e dores dos utilizadores captados sem assumir uma tecnologia",
   "resource.capability-value-proposition-canvas.outcomes.2": "Capacidades reutilizáveis candidatas identificadas para avaliação de arquitetura",
-  "resource.capability-value-proposition-canvas.steps": "Liste as tarefas e resultados dos consumidores que a capacidade deve suportar.",
+  "resource.capability-value-proposition-canvas.steps": "Liste as tarefas e resultados dos utilizadores que a capacidade deve suportar.",
   "resource.capability-value-proposition-canvas.steps.1": "Identifique funcionalidades da capacidade que permitem ganhos.",
   "resource.capability-value-proposition-canvas.steps.2": "Identifique funcionalidades da capacidade que aliviam dores.",
   "resource.capability-value-proposition-canvas.steps.3": "Agrupe as funcionalidades em capacidades reutilizáveis candidatas.",
   "resource.capability-value-proposition-canvas.tips": "Mantenha-se independente da tecnologia até os requisitos apontarem para um estilo.",
-  "resource.capability-value-proposition-canvas.tips.1": "Utilize este recurso em vez do Canvas da Proposta de Valor da API quando a API ainda não é o estilo de integração escolhido.",
+  "resource.capability-value-proposition-canvas.tips.1": "Utilize este recurso em vez do Canvas da Proposta de Valor da API quando a API ainda não é o estilo de implementação escolhido.",
   "resource.capability-business-model-canvas.title": "Canvas do Modelo de Negócio da Capacidade",
-  "resource.capability-business-model-canvas.description": "Um canvas de modelo de negócio para capacidades de integração reutilizáveis, cobrindo valor, consumidores, propriedade, envolvimento, custos e benefícios sem assumir disponibilização por API.",
+  "resource.capability-business-model-canvas.description": "Um canvas de modelo de negócio para capacidades de integração reutilizáveis, cobrindo valor, utilizadores, propriedade, envolvimento, custos e benefícios sem assumir disponibilização por API.",
   "resource.capability-business-model-canvas.outcomes": "Modelo operacional viável para a capacidade reutilizável",
-  "resource.capability-business-model-canvas.outcomes.1": "Propriedade, consumidores, canais, parceiros e necessidades de suporte clarificados",
+  "resource.capability-business-model-canvas.outcomes.1": "Propriedade, utilizadores, canais, parceiros e necessidades de suporte clarificados",
   "resource.capability-business-model-canvas.outcomes.2": "Custos e benefícios visíveis antes do compromisso com a arquitetura",
   "resource.capability-business-model-canvas.steps": "Resuma a proposta de valor da capacidade.",
-  "resource.capability-business-model-canvas.steps.1": "Identifique segmentos de consumidores e canais de envolvimento.",
+  "resource.capability-business-model-canvas.steps.1": "Identifique segmentos de utilizadores e canais de envolvimento.",
   "resource.capability-business-model-canvas.steps.2": "Defina atividades, recursos e parceiros-chave.",
   "resource.capability-business-model-canvas.steps.3": "Capte custos e benefícios.",
   "resource.capability-business-model-canvas.steps.4": "Clarifique propriedade, financiamento, suporte e expectativas de ciclo de vida.",
-  "resource.capability-business-model-canvas.steps.5": "Valide o modelo com consumidores, produtores e partes interessadas de governação.",
-  "resource.capability-business-model-canvas.tips": "Utilize este recurso em vez do Canvas do Modelo de Negócio da API quando o estilo de integração ainda está em aberto.",
+  "resource.capability-business-model-canvas.steps.5": "Valide o modelo com utilizadores, produtores e partes interessadas de governação.",
+  "resource.capability-business-model-canvas.tips": "Utilize este recurso em vez do Canvas do Modelo de Negócio da API quando o estilo de implementação ainda está em aberto.",
   "resource.capability-business-model-canvas.tips.1": "Mantenha o foco na viabilidade da capacidade reutilizável, não numa ligação pontual.",
-  "resource.consumer-experience-requirements-canvas.title": "Canvas de Requisitos da Experiência do Consumidor",
-  "resource.consumer-experience-requirements-canvas.description": "Um canvas de requisitos para a experiência orientada para os consumidores e necessidades não funcionais que deve orientar a escolha de arquitetura posterior.",
-  "resource.consumer-experience-requirements-canvas.outcomes": "Requisitos dos consumidores independentes da tecnologia",
+  "resource.consumer-experience-requirements-canvas.title": "Canvas de Requisitos da Experiência do Utilizador",
+  "resource.consumer-experience-requirements-canvas.description": "Um canvas de requisitos para a experiência orientada para os utilizadores e necessidades não funcionais que deve orientar a escolha de arquitetura posterior.",
+  "resource.consumer-experience-requirements-canvas.outcomes": "Requisitos dos utilizadores independentes da tecnologia",
   "resource.consumer-experience-requirements-canvas.outcomes.1": "Necessidades de experiência e não funcionais captadas antes do início da conceção",
   "resource.consumer-experience-requirements-canvas.outcomes.2": "Implicações de arquitetura documentadas para a seleção do estilo",
-  "resource.consumer-experience-requirements-canvas.steps": "Capte objetivos dos consumidores e contexto de utilização.",
+  "resource.consumer-experience-requirements-canvas.steps": "Capte objetivos dos utilizadores e contexto de utilização.",
   "resource.consumer-experience-requirements-canvas.steps.1": "Documente expectativas de disponibilidade, atualidade, volume, desempenho, qualidade dos dados e consistência.",
   "resource.consumer-experience-requirements-canvas.steps.2": "Documente expectativas de segurança, privacidade, integração, mudança, observabilidade, suporte e recuperação.",
   "resource.consumer-experience-requirements-canvas.steps.3": "Resuma o que os requisitos implicam para possíveis estilos de arquitetura.",
-  "resource.consumer-experience-requirements-canvas.tips": "Utilize this as the bridge between capability value and architecture decision.",
-  "resource.consumer-experience-requirements-canvas.tips.1": "Não escolha API, evento, ficheiro, stream ou produto de dados até os requisitos indicarem o melhor ajuste."
+  "resource.consumer-experience-requirements-canvas.tips": "Utilize isto como ponte entre o valor da capacidade e a decisão de arquitetura.",
+  "resource.consumer-experience-requirements-canvas.tips.1": "Não escolha API, evento, ficheiro, stream ou produto de dados até os requisitos indicarem o melhor ajuste.",
+  "resource.integration-style-selection-guide.title": "Guia de seleção do estilo de implementação",
+  "resource.integration-style-selection-guide.description": "Orientação para escolher entre API, evento, ficheiro, stream, produto de dados, integração direta ou estilos de implementação híbridos com base nos requisitos e restrições.",
+  "resource.integration-style-selection-guide.outcomes": "Estilo de implementação de integração justificado",
+  "resource.integration-style-selection-guide.outcomes.1": "Compromissos documentados entre opções de estilo de implementação",
+  "resource.integration-style-selection-guide.outcomes.2": "Estilo selecionado rastreável aos requisitos dos utilizadores, da plataforma, dos dados e da operação",
+  "resource.integration-style-selection-guide.steps": "Compare estilos de implementação viáveis face a necessidades de latência, volume, acoplamento, propriedade dos dados, atualidade, governação e operabilidade.",
+  "resource.integration-style-selection-guide.steps.1": "Identifique quando API, evento, ficheiro, stream, produto de dados, integração direta ou abordagens híbridas se ajustam ao caso de utilização.",
+  "resource.integration-style-selection-guide.steps.2": "Documente restrições, riscos e dependências da plataforma para o estilo de implementação selecionado.",
+  "resource.integration-style-selection-guide.steps.3": "Registe por que motivo as alternativas rejeitadas não foram selecionadas.",
+  "resource.integration-style-selection-guide.tips": "Utilize depois de os requisitos estarem explícitos e antes de iniciar o desenho detalhado do contrato.",
+  "resource.integration-style-selection-guide.tips.1": "Mantenha os recursos de REST, evento, GraphQL, ficheiro, stream e produto de dados como recursos opcionais de desenho subsequentes.",
+  "resource.process-workflow-design-guide.title": "Guia de desenho do processo e workflow",
+  "resource.process-workflow-design-guide.description": "Orientação para modelar passos do processo, papéis, passagens de responsabilidade, pontos de decisão, estados, entradas, saídas e exceções que moldam um workflow de automatização.",
+  "resource.process-workflow-design-guide.outcomes": "Desenho claro do workflow de automatização",
+  "resource.process-workflow-design-guide.outcomes.1": "Passos do processo e passagens de responsabilidade documentados antes da implementação",
+  "resource.process-workflow-design-guide.outcomes.2": "Estados do workflow, entradas, saídas e caminhos de exceção compreendidos",
+  "resource.process-workflow-design-guide.steps": "Mapeie o fluxo do processo atual e alvo, incluindo responsabilidades humanas e dos sistemas.",
+  "resource.process-workflow-design-guide.steps.1": "Identifique gatilhos do workflow, estados, decisões, entradas de dados, saídas e critérios de conclusão.",
+  "resource.process-workflow-design-guide.steps.2": "Documente passagens de responsabilidade entre utilizadores, sistemas, operações e papéis de suporte.",
+  "resource.process-workflow-design-guide.steps.3": "Confirme que passos devem ser automatizados e quais exigem julgamento humano.",
+  "resource.process-workflow-design-guide.tips": "Mantenha o desenho do processo separado do desenho de contratos de API ou de integração até o workflow estar claro.",
+  "resource.process-workflow-design-guide.tips.1": "Utilize este como o recurso principal de desenho para workflows de automatização.",
+  "resource.decision-business-rules-guide.title": "Guia de decisões e regras de negócio",
+  "resource.decision-business-rules-guide.description": "Orientação para captar regras, limiares, decisões, aprovações, verificações de elegibilidade e responsabilidade pelas regras no desenho de automatizações.",
+  "resource.decision-business-rules-guide.outcomes": "Decisões e regras de negócio explícitas",
+  "resource.decision-business-rules-guide.outcomes.1": "Regras e limiares documentados com responsáveis",
+  "resource.decision-business-rules-guide.outcomes.2": "Decisões da automatização rastreáveis a políticas, processos ou intenção de negócio",
+  "resource.decision-business-rules-guide.steps": "Liste as decisões que a automatização deve tomar ou apoiar.",
+  "resource.decision-business-rules-guide.steps.1": "Documente condições das regras, limiares, exceções, aprovações e pontos de escalamento.",
+  "resource.decision-business-rules-guide.steps.2": "Identifique responsáveis pelas regras e governação de alterações para cada área de decisão.",
+  "resource.decision-business-rules-guide.tips": "Separe regras de negócio estáveis de parâmetros operacionais configuráveis.",
+  "resource.decision-business-rules-guide.tips.1": "Utilize exemplos e casos-limite para validar a interpretação das regras.",
+  "resource.automation-trigger-handoff-exception-guide.title": "Guia de gatilhos, passagens de responsabilidade e exceções da automatização",
+  "resource.automation-trigger-handoff-exception-guide.description": "Orientação para definir gatilhos de automatização, passagens para intervenção humana, tratamento de exceções, tentativas repetidas, ações compensatórias e caminhos de escalamento de suporte.",
+  "resource.automation-trigger-handoff-exception-guide.outcomes": "Gatilhos de automatização e caminhos de exceção definidos",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.1": "Passagens para intervenção humana e escalamentos de suporte estão explícitos",
+  "resource.automation-trigger-handoff-exception-guide.outcomes.2": "Exceções, tentativas repetidas e ações compensatórias desenhadas antes da entrega",
+  "resource.automation-trigger-handoff-exception-guide.steps": "Defina os eventos, calendários, ações de utilizadores ou estados de sistema que acionam a automatização.",
+  "resource.automation-trigger-handoff-exception-guide.steps.1": "Mapeie passagens da automatização para utilizadores, operadores ou equipas de suporte.",
+  "resource.automation-trigger-handoff-exception-guide.steps.2": "Documente exceções, regras de nova tentativa, comportamento de timeout e caminhos alternativos.",
+  "resource.automation-trigger-handoff-exception-guide.steps.3": "Defina alertas e limiares de escalamento para resultados de automatização falhados ou ambíguos.",
+  "resource.automation-trigger-handoff-exception-guide.tips": "Desenhe caminhos de exceção como comportamento essencial do workflow, não como reflexão tardia.",
+  "resource.automation-trigger-handoff-exception-guide.tips.1": "Inclua papéis de negócio e operações ao validar passagens de responsabilidade.",
+  "resource.automation-testing-guide.title": "Guia de testes de automatização",
+  "resource.automation-testing-guide.description": "Orientação para testar workflows automatizados, decisões, integrações, exceções, comportamento de rollback, supervisão e impacto nos utilizadores antes da publicação.",
+  "resource.automation-testing-guide.outcomes": "Comportamento da automatização validado",
+  "resource.automation-testing-guide.outcomes.1": "Testes de workflow, regras, exceções e integração definidos",
+  "resource.automation-testing-guide.outcomes.2": "Confiança na publicação para caminhos automatizados e assistidos por pessoas",
+  "resource.automation-testing-guide.steps": "Crie testes para caminhos esperados, casos-limite, exceções, tentativas repetidas e passagens de responsabilidade.",
+  "resource.automation-testing-guide.steps.1": "Valide regras de negócio e resultados de decisão com dados representativos.",
+  "resource.automation-testing-guide.steps.2": "Teste rollback, recuperação, observabilidade e caminhos de intervenção manual.",
+  "resource.automation-testing-guide.steps.3": "Inclua utilizadores e operadores em testes de aceitação quando a automatização altera práticas de trabalho.",
+  "resource.automation-testing-guide.tips": "Utilize cenários e formatos de dados semelhantes aos de produção sem expor dados sensíveis.",
+  "resource.automation-testing-guide.tips.1": "Mantenha as evidências de teste disponíveis para a revisão de prontidão.",
+  "resource.automation-operational-ownership-guide.title": "Guia de responsabilidade operacional da automatização",
+  "resource.automation-operational-ownership-guide.description": "Orientação para definir responsabilidade, runbooks, supervisão, suporte, monitorização, controlo de alterações e responsabilidades de melhoria contínua para automatizações.",
+  "resource.automation-operational-ownership-guide.outcomes": "Modelo operacional claro para a automatização",
+  "resource.automation-operational-ownership-guide.outcomes.1": "Responsabilidades de propriedade, suporte e escalamento atribuídas",
+  "resource.automation-operational-ownership-guide.outcomes.2": "Práticas de monitorização e alteração prontas para operação em produção",
+  "resource.automation-operational-ownership-guide.steps": "Defina responsáveis de negócio, técnicos e operacionais pela automatização.",
+  "resource.automation-operational-ownership-guide.steps.1": "Documente runbooks, caminhos de suporte, sinais de monitorização, expectativas de serviço e regras de escalamento.",
+  "resource.automation-operational-ownership-guide.steps.2": "Defina controlo de alterações e práticas de revisão para atualizações de workflow, plataforma e regras.",
+  "resource.automation-operational-ownership-guide.tips": "Não publique uma automatização sem um responsável nomeado por exceções e melhoria contínua.",
+  "resource.automation-operational-ownership-guide.tips.1": "Torne visíveis as necessidades de supervisão antes de terminar o planeamento da entrega.",
+  "resource.automation-rollback-supervision-guide.title": "Guia de rollback e supervisão da automatização",
+  "resource.automation-rollback-supervision-guide.description": "Orientação para desenhar caminhos de rollback, pausa, substituição manual, monitorização, supervisão e recuperação para automatizações.",
+  "resource.automation-rollback-supervision-guide.outcomes": "Caminhos controlados de recuperação da automatização",
+  "resource.automation-rollback-supervision-guide.outcomes.1": "Comportamento de rollback, pausa e substituição manual documentado",
+  "resource.automation-rollback-supervision-guide.outcomes.2": "Necessidades de supervisão e responsabilidades de recuperação definidas",
+  "resource.automation-rollback-supervision-guide.steps": "Identifique ações que devem poder ser revertidas, pausadas ou substituídas manualmente.",
+  "resource.automation-rollback-supervision-guide.steps.1": "Defina procedimentos de rollback, compensação e recuperação para resultados de automatização falhados ou incorretos.",
+  "resource.automation-rollback-supervision-guide.steps.2": "Documente limiares de supervisão, alertas e pontos de decisão manual.",
+  "resource.automation-rollback-supervision-guide.steps.3": "Valide os procedimentos de recuperação antes da publicação.",
+  "resource.automation-rollback-supervision-guide.tips": "Trate rollback e supervisão como parte do desenho do workflow e do plano de entrega.",
+  "resource.automation-rollback-supervision-guide.tips.1": "Utilize incidentes operacionais e quase incidentes para refinar critérios de supervisão.",
+  "resource.automation-readiness-checklist.title": "Checklist de prontidão da automatização",
+  "resource.automation-readiness-checklist.description": "Uma checklist para validar workflow de automatização, controlos, risco, conformidade, supervisão humana, evidências de teste, rollback, operações e prontidão para publicação.",
+  "resource.automation-readiness-checklist.outcomes": "Prontidão da automatização documentada",
+  "resource.automation-readiness-checklist.outcomes.1": "Lacunas de prontidão conhecidas e mitigações antes da publicação",
+  "resource.automation-readiness-checklist.outcomes.2": "Evidências para qualidade, risco, conformidade, supervisão e aprovação operacional",
+  "resource.automation-readiness-checklist.steps": "Reveja desenho do workflow, regras de negócio, controlos, acesso, tratamento de dados e caminhos de exceção.",
+  "resource.automation-readiness-checklist.steps.1": "Verifique evidências de teste, procedimentos de rollback, modelo de supervisão e prontidão do suporte.",
+  "resource.automation-readiness-checklist.steps.2": "Confirme responsabilidade, runbooks, monitorização, controlos de alteração e aprovação de publicação.",
+  "resource.automation-readiness-checklist.steps.3": "Registe lacunas por resolver, decisões e riscos aceites antes da publicação.",
+  "resource.automation-readiness-checklist.tips": "Utilize antes da publicação e novamente após alterações materiais ao workflow ou às regras.",
+  "resource.automation-readiness-checklist.tips.1": "Torne explícitas nas evidências a supervisão humana e a gestão de exceções.",
+  "resource.automation-rollout-enablement-guide.title": "Guia de rollout e enablement da automatização",
+  "resource.automation-rollout-enablement-guide.description": "Orientação para implementar automatizações com comunicação aos utilizadores, onboarding, instruções operacionais, caminhos de suporte, gestão da mudança e ciclos de feedback.",
+  "resource.automation-rollout-enablement-guide.outcomes": "Utilizadores e operadores da automatização preparados",
+  "resource.automation-rollout-enablement-guide.outcomes.1": "Comunicação de rollout, onboarding e caminhos de suporte preparados",
+  "resource.automation-rollout-enablement-guide.outcomes.2": "Utilizadores e operadores compreendem como o trabalho muda após a publicação da automatização",
+  "resource.automation-rollout-enablement-guide.steps": "Defina públicos do rollout, calendário, canais de comunicação e necessidades de formação.",
+  "resource.automation-rollout-enablement-guide.steps.1": "Publique instruções operacionais, caminhos de suporte, orientação para exceções e contactos de escalamento.",
+  "resource.automation-rollout-enablement-guide.steps.2": "Planeie suporte de transição para utilizadores, operadores e responsáveis pelo processo.",
+  "resource.automation-rollout-enablement-guide.steps.3": "Recolha feedback após o rollout e alimente o backlog com melhorias.",
+  "resource.automation-rollout-enablement-guide.tips": "Utilize linguagem de rollout para automatizações em vez de tratar enablement como publicação de API.",
+  "resource.automation-rollout-enablement-guide.tips.1": "Inclua tanto os utilizadores afetados pelo processo como os operadores responsáveis pela automatização.",
+  "resource.api-community-engagement-strategies.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.",
+  "resource.api-development-best-practices.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.",
+  "resource.api-metrics-and-analytics.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.",
+  "resource.api-testing-best-practices.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.",
+  "resource.apiops-CI-CD-for-apis.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado.",
+  "resource.api-audit-checklist.tips.2": "Utilize este recurso quando uma API for o estilo de implementação selecionado."
 }
diff --git a/src/data/method/pt/labels.stakeholders.json b/src/data/method/pt/labels.stakeholders.json
index 3d250b7..0001b05 100644
--- a/src/data/method/pt/labels.stakeholders.json
+++ b/src/data/method/pt/labels.stakeholders.json
@@ -1,49 +1,49 @@
 {
   "stakeholder.involvement.lead": "Líder",
-  "stakeholder.involvement.core": "Principal",
+  "stakeholder.involvement.core": "Núcleo",
   "stakeholder.involvement.consulted": "Consultado",
-  "stakeholder.business-owner.title": "Responsável de Negócios",
-  "stakeholder.business-owner.description": "Representa os objetivos de negócios, financiamento e resultados esperados para a iniciativa API.",
-  "stakeholder.api-program-owner.title": "Proprietário do Programa API",
-  "stakeholder.api-program-owner.description": "Coordena as práticas de portfólio API, alinhamento organizacional e desenvolvimento de capacidades API de longo prazo.",
-  "stakeholder.api-product-owner.title": "Proprietário do Produto API",
-  "stakeholder.api-product-owner.description": "Impulsiona a oportunidade API, priorização e decisões de nível de produto ao longo do ciclo de vida.",
-  "stakeholder.capability-owner.title": "Capability Owner",
-  "stakeholder.capability-owner.description": "",
-  "stakeholder.domain-specialist.title": "Especialista em Domínio",
-  "stakeholder.domain-specialist.description": "Trás conhecimento profundo do domínio de negócios, conceitos, regras e restrições que a API deve refletir.",
-  "stakeholder.customer-specialist.title": "Representante do Cliente ou Parceiro",
-  "stakeholder.customer-specialist.description": "Contribui com a perspectiva do cliente ou parceiro de negócios para o percurso, valor e modelo de colaboração.",
-  "stakeholder.api-consumer-specialist.title": "Representante do Consumidor API",
-  "stakeholder.api-consumer-specialist.description": "Representa as necessidades dos desenvolvedores, integradores ou outros consumidores da API que utilizam a API diretamente.",
-  "stakeholder.platform-architect.title": "Arquiteto da Plataforma",
-  "stakeholder.platform-architect.description": "Orienta decisões sobre a plataforma, integração, escalabilidade e arquitetura que moldam como a API é construída e operada.",
-  "stakeholder.api-architect.title": "API Architect",
-  "stakeholder.api-architect.description": "",
-  "stakeholder.integration-architect.title": "Integration Architect",
-  "stakeholder.integration-architect.description": "",
+  "stakeholder.business-owner.title": "Responsável de negócio",
+  "stakeholder.business-owner.description": "Representa os objetivos de negócio, o financiamento e os resultados esperados da iniciativa de capacidade, API ou automatização.",
+  "stakeholder.api-program-owner.title": "Responsável pelo programa API",
+  "stakeholder.api-program-owner.description": "Coordena as práticas do portefólio de APIs, o alinhamento organizacional e o desenvolvimento de capacidades API a longo prazo.",
+  "stakeholder.api-product-owner.title": "Responsável pelo produto API",
+  "stakeholder.api-product-owner.description": "Conduz a oportunidade API, a priorização e as decisões ao nível do produto ao longo do ciclo de vida.",
+  "stakeholder.capability-owner.title": "Responsável pela capacidade",
+  "stakeholder.capability-owner.description": "Responsável pela visão, valor, prioridades, ciclo de vida e reutilização da capacidade junto dos utilizadores.",
+  "stakeholder.domain-specialist.title": "Especialista de domínio",
+  "stakeholder.domain-specialist.description": "Traz conhecimento profundo do domínio de negócio, conceitos, regras e restrições que a capacidade ou interface deve refletir.",
+  "stakeholder.customer-specialist.title": "Representante de cliente ou parceiro",
+  "stakeholder.customer-specialist.description": "Contribui com a perspetiva do cliente ou parceiro para o percurso, valor e modelo de colaboração.",
+  "stakeholder.api-consumer-specialist.title": "Representante dos utilizadores da API",
+  "stakeholder.api-consumer-specialist.description": "Representa as necessidades de programadores, integradores ou outros utilizadores que utilizam a API diretamente.",
+  "stakeholder.platform-architect.title": "Arquiteto de plataforma",
+  "stakeholder.platform-architect.description": "Orienta decisões de plataforma, integração, escalabilidade e arquitetura que moldam como a capacidade ou API é construída e operada.",
+  "stakeholder.api-architect.title": "Arquiteto API",
+  "stakeholder.api-architect.description": "Responsável pela arquitetura API, pelos princípios de desenho e pela qualidade dos contratos de interface.",
+  "stakeholder.integration-architect.title": "Arquiteto de integração",
+  "stakeholder.integration-architect.description": "Desenha abordagens de integração e estilos de implementação que ligam a capacidade ou API a outros sistemas.",
   "stakeholder.platform-owner.title": "Responsável pela plataforma",
-  "stakeholder.platform-owner.description": "",
-  "stakeholder.api-designer.title": "Designer de API",
-  "stakeholder.api-designer.description": "Modela o contrato de interface da API, o modelo de interação, a consistência e a usabilidade das capacidades expostas.",
-  "stakeholder.api-engineer.title": "Engenheiro de Entrega",
-  "stakeholder.api-engineer.description": "Responsável pela implementação, automação, testes e preocupações do fluxo de lançamento necessárias para entregar a API de forma fiável.",
-  "stakeholder.automation-owner.title": "Responsável pela automação",
-  "stakeholder.automation-owner.description": "",
-  "stakeholder.process-owner.title": "Process Owner",
-  "stakeholder.process-owner.description": "",
-  "stakeholder.automation-engineer.title": "Engenheiro de automação",
-  "stakeholder.automation-engineer.description": "",
-  "stakeholder.security-specialist.title": "Especialista em Segurança",
-  "stakeholder.security-specialist.description": "Garante que os riscos de segurança, controlos e fronteiras de confiança são tratados ao longo do ciclo de vida da API.",
-  "stakeholder.compliance-specialist.title": "Especialista em Conformidade e Legal",
-  "stakeholder.compliance-specialist.description": "Esclarece os requisitos legais, de privacidade, regulamentares e contratuais que afetam a API.",
-  "stakeholder.governance-specialist.title": "Responsável pela governação",
+  "stakeholder.platform-owner.description": "Responsável pelas capacidades da plataforma, roadmap, modelo operacional e expectativas de serviço.",
+  "stakeholder.api-designer.title": "Designer API",
+  "stakeholder.api-designer.description": "Modela o contrato de interface, o modelo de interação, a consistência e a usabilidade das capacidades expostas.",
+  "stakeholder.api-engineer.title": "Engenheiro de entrega",
+  "stakeholder.api-engineer.description": "Responsável pela implementação, automatização, testes e fluxo de publicação necessários para entregar a capacidade, API ou automatização de forma fiável.",
+  "stakeholder.automation-owner.title": "Responsável pela automatização",
+  "stakeholder.automation-owner.description": "Responsável pelos objetivos, valor de negócio, prioridades, controlos e resultados do ciclo de vida da automatização.",
+  "stakeholder.process-owner.title": "Responsável pelo processo",
+  "stakeholder.process-owner.description": "Responsável pelo processo de negócio a automatizar, incluindo objetivos, regras, resultados e prioridades de melhoria.",
+  "stakeholder.automation-engineer.title": "Engenheiro de automatização",
+  "stakeholder.automation-engineer.description": "Implementa, testa, integra e mantém soluções de automatização e workflows de suporte.",
+  "stakeholder.security-specialist.title": "Especialista em segurança",
+  "stakeholder.security-specialist.description": "Garante que os riscos de segurança, controlos e fronteiras de confiança são tratados ao longo de todo o ciclo de vida.",
+  "stakeholder.compliance-specialist.title": "Especialista em conformidade e jurídico",
+  "stakeholder.compliance-specialist.description": "Esclarece requisitos legais, de privacidade, regulamentares e contratuais que afetam a capacidade, API, interface ou automatização.",
+  "stakeholder.governance-specialist.title": "Responsável pela governação API",
   "stakeholder.governance-specialist.description": "Representa práticas de revisão, auditoria e governação em toda a organização para qualidade e conformidade das APIs.",
-  "stakeholder.api-devrel-specialist.title": "Responsável pela documentação e desenvolvimento da comunidade",
-  "stakeholder.api-devrel-specialist.description": "É responsável pelo conteúdo de integração, pela comunicação com programadores e pela qualidade da documentação para os utilizadores da API.",
-  "stakeholder.operations-specialist.title": "Responsável pelo suporte e operações",
-  "stakeholder.operations-specialist.description": "Representa o suporte em tempo de execução, o tratamento de incidentes, a observabilidade e a prontidão operacional.",
+  "stakeholder.api-devrel-specialist.title": "Responsável por documentação e DevRel",
+  "stakeholder.api-devrel-specialist.description": "Responsável por conteúdos de onboarding, comunicação com programadores e qualidade da documentação para utilizadores da API.",
+  "stakeholder.operations-specialist.title": "Responsável por suporte e operações",
+  "stakeholder.operations-specialist.description": "Representa o suporte em execução, tratamento de incidentes, observabilidade e prontidão operacional da capacidade, API ou automatização.",
   "stakeholder.partner-specialist.title": "Gestor de parceiros ou fornecedores",
-  "stakeholder.partner-specialist.description": "Coordena as relações com parceiros externos, fornecedores ou vendedores que influenciam a estratégia e a entrega da API."
+  "stakeholder.partner-specialist.description": "Coordena relações com parceiros, fornecedores ou prestadores externos que influenciam a estratégia e entrega da capacidade ou API."
 }
diff --git a/src/data/method/resources.json b/src/data/method/resources.json
index 1c4da32..191ca29 100644
--- a/src/data/method/resources.json
+++ b/src/data/method/resources.json
@@ -24,7 +24,8 @@
         ],
         "tips": [
           "resource.api-community-engagement-strategies.tips",
-          "resource.api-community-engagement-strategies.tips.1"
+          "resource.api-community-engagement-strategies.tips.1",
+          "resource.api-community-engagement-strategies.tips.2"
         ]
       },
       "category": "guideline"
@@ -61,7 +62,6 @@
       "title": "resource.api-development-best-practices.title",
       "slug": "resources/api-development-best-practices",
       "icon": "edit-document-outline",
-      "daft": "true",
       "order": 112,
       "description": "resource.api-development-best-practices.description",
       "image": "",
@@ -78,7 +78,8 @@
         ],
         "tips": [
           "resource.api-development-best-practices.tips",
-          "resource.api-development-best-practices.tips.1"
+          "resource.api-development-best-practices.tips.1",
+          "resource.api-development-best-practices.tips.2"
         ]
       },
       "category": "guideline",
@@ -89,7 +90,6 @@
       "title": "resource.api-metrics-and-analytics.title",
       "slug": "resources/api-metrics-and-analytics",
       "icon": "edit-document-outline",
-      "daft": "true",
       "order": 119,
       "description": "resource.api-metrics-and-analytics.description",
       "image": "",
@@ -106,7 +106,8 @@
         ],
         "tips": [
           "resource.api-metrics-and-analytics.tips",
-          "resource.api-metrics-and-analytics.tips.1"
+          "resource.api-metrics-and-analytics.tips.1",
+          "resource.api-metrics-and-analytics.tips.2"
         ]
       },
       "category": "guideline",
@@ -241,7 +242,8 @@
         ],
         "tips": [
           "resource.api-testing-best-practices.tips",
-          "resource.api-testing-best-practices.tips.1"
+          "resource.api-testing-best-practices.tips.1",
+          "resource.api-testing-best-practices.tips.2"
         ]
       },
       "category": "guideline"
@@ -322,7 +324,8 @@
         ],
         "tips": [
           "resource.apiops-CI-CD-for-apis.tips",
-          "resource.apiops-CI-CD-for-apis.tips.1"
+          "resource.apiops-CI-CD-for-apis.tips.1",
+          "resource.apiops-CI-CD-for-apis.tips.2"
         ]
       },
       "category": "guideline"
@@ -714,7 +717,8 @@
         ],
         "tips": [
           "resource.api-audit-checklist.tips",
-          "resource.api-audit-checklist.tips.1"
+          "resource.api-audit-checklist.tips.1",
+          "resource.api-audit-checklist.tips.2"
         ]
       },
       "category": "checklist"

From d4113b1fae70ef0a7fb57fd7f734031f3867458e Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Sun, 12 Jul 2026 09:08:58 +0300
Subject: [PATCH 09/12] removed extra zip file

---
 src/data.zip | Bin 240839 -> 0 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)
 delete mode 100644 src/data.zip

diff --git a/src/data.zip b/src/data.zip
deleted file mode 100644
index f66aa88fce6089cd758795434ff268716e6a903e..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 240839
zcmb5VV|?UIyYHK1!ijAg9ox1uv2EM7ZQB!PVmlMtw(UK$p0&@}YoEQIv+sUU-Jg0<
zeRX{={Hm`0%S(L&MFINz8WB0t`i~F)Ie-BX02%2!>C-v8K?4DU{+<1gLHP$P5JXvm
zv_(;+qD7-Rjk)}Py9CVtT*6S_#zo)p|8gZrAjtoZG1&jxO8;6=_>XzC7LK+y|DB19
z#s4z#LQC6rjTOb4Zu(1ap96L`wnlqPk(`>*C>k3AIHUl+(TUhGUOX9Jw!`4dyU1w8
z0m)posE|F|AJm>igR`xJ`|0{tkx!@l)ag-NlFvc{Q~U)2o)8a-mDu4*=qQxO8f$v`
zU1`C}cZPz@v1Z{^^H9FWFq_`9xaDm;Fkowy_~X5YZ*U1&o`fW#N}JyS0P>TK4=X#T
zw4Nyof`R7B{7Ukh9-}2APS?xxQRa<;shypgg+OD5gTC#H^A$x1SDzq4wqrT}dcv~T
z=GxVHwv?dS0GBD%`djnsB|w@)d1b-Y))qbr%#A7#reB~ZvD0&kfKWck6#l)bb?8<<
z#ihglB@A+qKM8LjD;gA5Y<+!7t4|~UXYPwvYwn8m%_t6D=>Xo<;V}BwLyCC)nf4qz
zFZv@epVKDluqpr#%*6;#&jbMoO9LIOS`+pHoum<Zq_Y=TeF=6&6NYgQS(Rjw9*G-Z
zM*#fj<=Ldk%TPSS%-Zb&NtF-$jW-B$fE&ynm|;{KJ-qX3?ZO+TOHUFba2Yt+Fcm&d
zo0qv{7AlNE7>Yg^oc;RZ7H`Z-YnQOPwYUYm-1QpGvPqXAkE~}qW7i&VbrpF2fu#Pq
zllhU@;$yY1BGwg=Qnt;u4Axyti5kzgsc-9d@u?9&llwNloYCu5MUV{p%tVxwP0tuk
z8R_$_ps^>kwEug}sXjiO2w1s**+_QZ1hByrI#I-av|+kG>S<4I!*opD?n`I~y?WUC
z90{p^MP85?cK&kSmmjRhR4=$SoChN@GZ`|L5=(a;HUW?m_mhhFA#jt~_ccxACvSbt
zCv#BDQjxQPdb<6Ao`|pjVqa5x6kiHKfL_c8&K~81Iq=Q$1{BUt^`Qg2ISWAuWppnU
z<in=97?n4g{sLJtRw=Scp8|<NO%*_kdD!vhq^bEkNiJ_O+D@^1)^w&i8%>7adX_yB
zUY%WZ^mcm*2$sxqg?M@QiaR4ziRe~zGJQX<MO<e&l42$)N#tpihK57$^21=**xrcW
zfb6wL*R_R&lGGqFLif>KBGsi=W3r)v%k`a-nN77J)i>U6gnZwEsu?H}{DStQp6iJ+
zj5^FWWSQ7#<}DKR%78mri=XCAy=m$NUV;o2^RMO3Qc7n_I`=R)1?(|JxBQS<POkiI
zeG5|{DWsYbjx<*I%v5PeG2d(=K$;o_(?J9nU9h0=Fb+%%CWB+JgD`!IoJXhQ$V;TC
zcgI&HeyE*%eDy^HEjI?*wc<r#-^eLD3Ao-Uk#m2e-3}_Z3Z5?8JMf@KFv0O?H#rri
z6d>2ACghP(q(#vm8fWD+t<|SP$&WAqwvkkNL7WEwQNwg<8+46$!MP_4&1=l2J<VTh
zCKU^1*sbb=6<VvU&@r-rABs<7LLIuiN=%|=0Nh=?XBMHn)6&(A!9G%^@|Rtu(6UyI
zbO8cdNbZi5W+*Gh)hYWOEe^kp#=|dm5YvaV*e8T>+@aWz)hm*j@Md~anLV*dWpcth
zC)`BI&eW`%W%Fc@mS7GN7ArBP;Wf`g9`<-}AhQQkf}3>Y3z)=g)|qnSjZhsmo0Iej
zYfOk$NlFOK6}$JV+2jM?+rb(5SpBinBFWuq2VuQ<^e=#Ma0{|EnvoRoyRT)J3l85x
zl#u!aU8k;fZoQ5s5zk_`kFhr^U9PYVA8z2Tyf`XWY33#_yLPlUmwE1;W17hAoM5j!
zMr>LLf8b9Yzj=tdqCVn{)u%zcc-0CfZSY-DjQYG9<n+nrf-ZfgS3iQTU|sGcsYwC}
z6c_ZSoYWVScV&4Lg47pkua!qq^5bFKvDz*e*e5}Ai)q^Y41)lE3<{<!h5b&{K}>DY
zdBFQ;+GBXCjT9ZYo@!5(vuPZLd$a$LD%us4#}|Pr|98^53+dZAF9bp&I*Kb=nB1j!
z!qBD^=d<x=hCVJ-f^4^{b%7RNJNA0=#%nss@#noR>)^A-&*i&^aOBj{7bP^B&7OCM
zoYyO!6{|xVYZ=G(qP$5bj)i9)<5$4Um^1RBk|a+#IU@qIvvd#F?*j!!x+C&eSCeK@
zsi{p4NuybsQkeGbDp2!+#5IY;8<b^q>-mz*wO@zkaF)BJ8<25Jn#8WApGW8}3eB5b
zbiS)R>HU2ySruj)YpEw74cVRPAdSo=pnO8Sy=0RMdBYuTMO`cr_|5yUWbNq5Udx?j
z`@D=vZB=lIbVuH#A_JWIh~f3oYVA+S%qK4!mQp&OmQpE(+q6xNYH0lKx(3QX177B(
ziIwlOgf|UfzYb>?7l_exW(SUCD!nx#)5;Y1#+&KacC8SWv`Azu?mE#A<*RJ6Un0q%
zxl9K46w?`)Z2`}DW?f~Dx+uR)<s*?k7LfueDEn4|kP$P|V>k41L1lSgk|^o0hl$S;
zRYl*h5MUph-AcbJd{2`j30twSi*>emYU1v1Gr8DjSkrCCV2)t4?(rCYiWYSx3Mdap
z_xGmkEytySrKYQ>cY02S(8^X*2k-DP_W1;pmx6%wlQ>;Ag#ZF-Qvw3|f0cm()PEHh
zB>!7IH@CL4b#MY0yZy(Tld-j(mA;el|5-7tlK)G4H2pu?<F8_PRNVhB@<sIj@*9Ny
zLz?L7+nEbGJDS@VJ37kP8W~&tYx=(x7eGzo77TyH#a|m1lw{;U7!W!$pYcaL27@9C
zHucbv;ITkvB5&l|<jjwoGhNUEgT5}EpanYOw)GoUgi38Uy*jdgAKn(sNkEE}gY7WL
z;c<pjEd0D3>v<#36e{hj3X*GMQP!kn27x_%HEtGyjvE1k8e#+18(AA0&A{LwRFS~&
zjS7!ITXY}V+<aO_Kh#m!2Q$NtbQ4!xoL?VVU*LQ$@FQJB-Wln6@y_NaBuzatm3mIz
zp^%bETtt8g=0*mPps5_$g>o~bzQSE>Jhb^5G&vLAQem5_dnDp?taZNNMO!~51p(`-
zMxbCJ&rHp}DSYV?m4sd8H3e=PyP>xA4Xn)GRvL*ZDb8-1xpA@UO2(iz0(MHajceJ;
zi-qE$^<kVW(F5_7$GW?zwoRUCTJs-c`d$w+@M9s~v$x)H!0{`7eahK7u`eIqLHzZd
z7_ls7QD7jTia-AIFW>n;k(KzzWL5O7oQ>rjZ0&3v&7I6`ZT<n=4W&BSetLwB_~+1(
zDuGi$Xsfs)Bq?QoJptUB-{noGuS9QJpvs@PTsA0U)BeRsbJ?4nu2-9OZ{v|P$Wd#e
z-}aOMmrTIX9^WqPZOREt)#538&U?Z;3@sD#7#L@?y1Q_u0gUrK2-n`AAp0YlD~QPC
z7RkbUF$~uoWM?3cUB`9sTHr?mk@A_+IAd<I!!i?rOY~Bh80$k1aP}jTHoT?-&qAI>
zS7r$?g*&bKH3GXCPSGyQi7w@}Zp#-GU&RYXg|`-pXs!#wFmuhe=;h{jiNm%0>0>>L
z)D0O#KU>_IX$H$YaQNPNq>$^m3sqX*AoTl8gG$Rf_ZvhgN{!Xmvmy|rj)gwJ|00sr
zRj!2jgJ|R1ze6Pa&kz~>XXHs(+vyuR{R27+O1+Zb{)8U%XFpOcwVUOGiUxFNSfg74
zo=HO>ZibAcNwebkXZvW$xCXq3yqOdnle_z!37+)hlB#+MXk|2TuX;Hiqw>5oTDs{1
zcw<zrjlc3HQuLf2eZur+7Y&?QFbF9ms29FJP+euGO?Wu6r9|O@A&iAO#}u%qw#zaX
znskC2qJ<)|C}7`eTxLS3_7e~duSxI?3^QRP%WYD-MI2@JY$Fl*y}+?(VYaa$K&4={
z0XUl4RPw%4cD5jvegB&FOT{uPHkobigaT)wn^n6_S|ahwj6}=A_k?U$N2}34B51R3
z3nP161D0&>ZMb&}7VulY^K*P+f8O%3Jsv|4Z<qWpnU#tAa>zeqoWcGb8Qy<J#!&wc
z5pyT^f52qphm2f5JxnL@4St0K012IWn^hw&jw}enPJqj;T)nzjLLw`l;h{V6UTA~e
zZaZLXbn))4A$Q-%)eA+0!BAa7uVZ|#k^)WMpJ1~jk5zB4C|?}FZ$MGV>7C<h77oKf
z@8*RL1h0M(Wfle?zfa&dhG($TGBf0PZ2KE48oMdzd2P4`3iRd+cA6$^mSxV7T!!*D
zO$|lUtLOmj@Me6>Wod)X&ZQ_%1Bd`v8M8qha&ca91U0ktLQE$Oz$;9qP8R8wM=@*u
z9ZCCS{XI8cg>x?LYLTpu)7{}RrgW#hstT~r?cwdrYB|Cp6YR^6gE`o^AW{imquA%m
z5xo<1oN5-}0)nQDh8tTm5noq_M4HZy^!H8iWnWR!n{GS9k60EYV#4S3VY<KIW;`QE
z0e`^7|66b({}7zBqm!+*v4f<ovxANCKjHT$reyp0|CTfOA|1;<5e3`jSx|U!f*hDo
zV=n)N3)u#yL4uR+_O)UGZnqvGQl5$Zi%hmF((H``ky>;HlwvfPJ#LR<k$R#bkaJ{}
z#U55f6Jm-8>=IE*W;e97v(y(nfS(Ah8oSpKFho3d3M_-&dsTwoF$OYf?My<y4m#iw
zSV|Gc4X>gf31sxUOh4?zM@|1)-Pe!!0a&#Rp#2L`ITO;Y7G$I666d0&X%Z~(ejWRY
z;2@S$oO1zkvvN7x`x^YOv<0(|edUZ|a|dKxowH``ppqD0SS8Lcvw@XW^f7tW!v?G4
zuDQwX;BRS6N!i92MWY{Pb{-**81JxA=HNjda~muqA2WLw*Z0how7#X?8LA~!X*tx7
z2U_qN9LOrnJ@W;iM8+x&lKp(L`;lkbA0U5O@<BJ!ar|L<1^(}Xko%vpG_tkUH~%L^
zYvG5C<zGdD{)%tp*)%OxcQJWMrDhf{DK{uI0msSArJfL8kNV|Fj*V^!kLQ87B9y>p
z%Zo>sdGVlJo67K`NdYF2(eu=}xEe*V#;n?F(H3gR!k7Tu--ge`vk^q4*nsqz6$Hc`
zJL_*wbX55EVkix!qkaVTmgTw(j)uo^L)0iG!)+!i1z=-%>V&IfZiXNhqqy5%QQ6ip
zLJ2S#l7FkQpU|Jzoy;_TR=zE>lA24w2s7L%SHMzPOxlKXRs_7q-0`kIeC=bM85~aL
zjo^y~o+E5Hueq<Dzml_<pXmulMQw-v;Dv|<-Ruq^DmwV}19h)p<m#(dl7UMLly{c7
z+~Q0vemw^|`GEg3-%VLn?ag!>7RdQfyP{-pGkbju+J6SO&Wb1zfa`FFH*p}DC=^B{
zJUzdoaYBZEB~K<nn<KU4#+`JPRMR@5vxxtfu6Als`;R|#yZ>#Za{V*9#xBM-|ET6E
z$Vm17iBIUyP=s1UkC_TK86rp`kuwPo3^t)Qr*>o)Q|hMu?sj}wYo7b<Vz-Q)PBz;^
zhRnMLnsLn3Y>=T+vhHyQt^7lz`|nmd!aDIl!SQpcSGJl?;V`g&ax3zm-0C1ItUnv1
zPAR`81cNg*sut@#0e%k6SG`{ZEuWjBhC(ADX02%BdeQ3C)L>Skhpt4thBo<=dPFT^
z@HH6YNeeEkKswF@pW96a1u`qq;?X-H^&O6UGb%#2AwoK>14H$|n&-Ex6<=e+{Qckz
zhN5fC*|k4Z6{>(^1;K)$a<Zx~{46GtS@rw{Q<LKR62`up+X%Hr>GKbPF@+C1Z(ka5
zims=J|Im!Ftap*nf0!)(TS3C}&zP7x=-Zju|D!{I^8ZrxaA!$C4cA56iD;2?$r}Sx
zHJCLrjKaUImVCG-n9N~7#0}+Fc-Y;)Tk(zC)bsL4BqaS@1cAI7zbBK}f<3k%WQ@bt
zo73q>i16>(7IFW4?GUjfq44k7I|FhXp)yqyipoM5$CUI8^DmUdJgaLtfqNTBKR|H@
zUL7Dp!?Y*GwlT7?yzo|FGvoEga%Bm~WY44{kGR&n7YGR%N+L-@ao~p3Q=?QUSUC#+
z^-Lw+e);4x@ZDH&UtIwOy<flW$;M^aoZHHyd+dp-s&ZzX5}~=8tp4-)(Zb0K*-@*D
zhNZcLkM5Scom;0{;0r&<y0Z1s3K=>yq=hX|AP06haPMF#W*4Sy)z6t}9A+uohG=uz
zYawcPH2m?goI>>T?Q1Z@T?)Ll=y!7g^O#s@^TOooTR!wqZs)&}=#Q&peepj?^&tOU
z5*7GoNX>1Wj2-@{%YP{U75|ICjIUVI4#t}gI2Q51NbCh~kdPru)_B~KVbykNA@2=j
zPBn77JDlWpYoALj&<mQ>0N&C1nHeA<W9Fa8+y>GKJUkXt3<D7y@BjM#VjjyXPT)td
z-3|#lf@$k6CY{Aj&0)bd*fTe#hW>NOIM#b7GcoCpx|~A_-Qd9elStb`blS2t=??op
zYIM=uNnVB@dl6!c$P{s-GwEw6BLFCNT9~BMaGVlSKEv3xv}1wl##UL}nF|XK7g4Yq
z&2*{dX5+fgYMvhVD4U+d@*kP$uQfH5<K5}%YW*`D<y*S^qX=o!JSu#-co)sh4uPDZ
zRWj#BNWbDsvl517=KRoJjIMg*$xbp`$0&U<-sO2uGM7h5Jc;FolRKV+Ip6vI=Ey3t
zUK-jz@RGm(J9vEm44##(q5fZTj{ii5#>+?z&?AIg1$^ZXSc1_(@5*RU>lg`ekKzqE
z<>@!1CrG1eziv%3Yg+KQBNUN_!c2AC-7pUS$&*S^p^G4ULe(~m#uDGK9rA&mzy%Hh
zMax7+3){VXIA^~7J+Qqf@C*BM)<WpdidWAZ_hktT!@eM_jN2GpJ!8R;XXo+4LY0Mj
z3uh*ksw>%ay>yn=!0u5f)XlubiW$5w8ZDZ|nL9+q6fZ0W424)l`<y0vq|2>bzfyfE
zSdK~^h^QwU*C{A9<M(TSe|>+VjR5~sPHhMJcX<GtJ!6*&qS)KapPBI$ZP8a(QB~)>
zt~EBJ>^jl$gX>~l7{g!Ce^D$II8J~5Y1@$e+v7CnKSSYQ?D&tWmC}Dok#~5h4x9Yc
z-C^e?L3lv%tWHEI1DBrJggB#$=E|3i$zJ`cQa;23bHAtUW+tK0Qu`?5V5^q8o>$d8
zyAs|v^zAN!vW|R!`A-UzwzZZMU~M8HFc`!wD1>}|%UW#x*^#P05GcVdb>iR=-_n|v
z!H;_FW}$wR#`$Hy{u0eh3ayHflIkDpFc^ckjx$?6p1LwM;I3z{GdIe>DKup8sLQh#
zXcpXhA)&h?euKTb)on=WkbWEwt*5zE9$vKOl9I{(dI%w}nAW+$y*fTJ^$ZnIk0J~7
zz2aLDd`ENpr79loUFG?A+W}b$?^l1eefZy2B-#JVZU5Jmn68PlmDPW9Nu_IS^Z$EK
z)$;eADn%xC^>08Vzv9z)z*6k@%eL0($9tGHt=9Y*AQGk95yPVmLIn}OIuk+FTt-!#
z3$1^!FT3+##^T2guXK6~jqnR~jkSh6jp_-4dnM~6Q=#U~L!|Sg+1DLf=q;3_N4bM1
zV}=DL1s*~z;S6e%<`o&K4>To%7h|`d9x#LF(>m*%La0;Bce8%yz+jep5^Kl*DPL}5
zvSk;ADOxunXG0(6F;R!>YX%{-){Wf|E<?_W9X$V~*uKUlKpo~xHMo-1J~tm)7czv@
z%+@gt^4&SBjB&=iW8EhS<G_91RL7!0?K`ZXs*g#%mJxkad~brd0J9bIOagzxDPp)q
zdSnpAh@A)0xHK9B-6C=>bvO)thuC^)KCHz=Lr%HokKr1}n#<g_A171awe&Qn3WhN%
zmbWGk8`SsV@x-2nFTLkDIK41;QSg^A*x$kT@VVN9$@*Vc6S|ktL+hKP?J+JK4X>+w
z57nXAg1HB`h!urO@NiqmJoQ}lu~wE;ojiWedpsm#*JS=8j^G=H$9$+WFWgq-{LX{6
zIuG4hXX-lEAVp^4p3;NG_$y!+?Yf{G+E&ioL^R{|;$YtXjl1dQ8#+imUS%$!NNQJH
zzBWa@I*Lw%Y!h9dFpVPxZ|@UM-95zobqu`5RYHt&t)q(M0<r*;#~!^|;Za>4bmxm#
z#Fww5Wm@%;adqjGD_3^c_(O*AI0&eh)ElRR38?q5`DEJl*UN8un&m3z-Y)E}OEKXE
zJ^VG@zmCoD_0-7&0tA!}_rIq0NS@>Wa`B4yzd82b+-+s<VQlnoyS1eYG8X@{TRYh)
z6-y$PK;~Aft6wIhin=YZ=?O2)$fQ0fQ=c|DVUT}jvQvX+b8=`R>nS{INY9V|$asWH
z^RowJE*7+8nSZj_74qC_1LsZbHMPo%sKCPF@KOHmr}*#u2uws13!;L8TSfQxP+j2}
zI<~`9U+fQvSM(1qUb5UJ<An73ch0S}d-tr3;o>(g9tBe62y~y9^M}-UZ`R#VVs8)Q
zT%N^22D+CMJ~A>+w3{x;#~T2ThH2)pw*hNOE8C!FqP5LlfRBPzfsBD9vi`#?$%^UB
z)$t3AZ^ZE*d)^N3(sClt7(J3xlSgfQbXDQ+bJ<2cRJ|90>c+RaC%*{fy%1AL0XHFj
zD+9*&VoE>mUvAaX9%6iA;ZferY1$beKA&9eH8PK#<B@44lK0bhF?r^Vz1XKc`AsrQ
zU2RTi3R@y6Do>_F1a<Sfy)2Pl!TBB~zG<5;s?Cx!e7M-k*6tM$nXUSo=>W0XF1Fvl
ztM*awjP={7`#2bmImhE%%mrBqCmDhubA*eJ;vS=IWQ>uRJB0dnm+yA298d~;t<Y^4
zeAzF6Twn^=$tBV2_vp`^+}uID_J9UaS_?rpn{Kwx<kL!(P+yEqHk`8(_CQ-LJiae!
z>(`?ye8&BVB4GWElINmt#zP>1-J4|;0sCPpm&qKp+fp)dW`G-}FK|8*3$dfBBBGVv
zUSyQ>w%Ez#w*>&yN498s5Ny$Rt*y1P3iZrEnS?w%JA;N^LQU7k7Tj?3<`|Ei<*~&~
z`u{#j`K_y*?gWPM@_cPRy`i`L5SmG6R;c*OW*ye6LCq`FsQ(E(dAxL$ZlX>Sx&{cr
z9pHRF3vk0|tl&K%A01lHWai7*)if9ypIa;$fqt`_=jLfE2aTsp8>JF0_-(c{cKW__
zn%}lABLxKPr3Y``9ZqqAkyg8V{_YQYgJE{`b(YdaffCils>VV|Sc~L`u@$dp5g*T{
zM2L4-b0i#}F|dm5C}yc_$j>U3dV9^@0f2fa9hhFJjuium|J_o!jxZ_?5j7j>EFAYt
z_>ib<-e*N#E7H@z=*53rc3EKR1+F@CB-{(?D>=v6zIXAZ1v&|e+xxU;gtB{e3*z7&
zU{n->m47K@qnqmZlpt%>!IgGp36e}oDvPma5Q}0?H=|5N=sn`Q^QC%ooXCuP*cV5J
z+lb+E1iz9Ed4J@relXxN^CdaU$V6_UqS2_(pDWT9Si46OsdF@NKx!L47UTK4Ic}9$
zKGLJ>h3KHCo+EMtzS|)ZrlYy*IAXl|sYzXX>|0AH3G0-i4{n$HrWt^wNGN%X`g01m
zDkC}V`+GZZ-uQcGjkQR44>d?40Rg4QC*86mxkgx5riU(O=nlGbGenaNtGU|``(OAx
zGv8lGl<<D@#q$q95m8i~I_&>Ma+HtUKxEM|xv|bLa@9?1t%y`mrWv5BG?L0)Pb=$X
z-ydL;6XQx0oPlc?jZmJ-cK7|XRQVp#rUd^$q9WE8(I{zf**|>?<XM&<_p_FrRnIt9
zKSgZzNK~*YkB;wW8^$8^gv*(Px85%%&_igOt~z1j%x||5zaiMSPD5w;H12n;E#O3p
zZ$olc5<aOXi}c!+;rGV-8FW;M87F@c-R_q$BS&2lF#pDHR*~eZl)ANgEaILg31$f1
zve{!!7P<>wDK;v&*lkq&cH!<7WjpFsA$tpoS)i^MjzyFXbq`^@=xHyy?8NouG_2Q{
z?|1Qtt8Q@Ay%{gpO#aavv8{v%d2d^C2wkrm-q&)-ONUXwha;)PGyO)I-J3LjaCrH?
zloa)BW;u5HyC|fHy`x<M7-ef%qGH)QGYXpc)w5nTqmdA9=}!k+o^UZlCF(q&tJ8i?
z$KCG>s-g`N=og`p`pB^0Zvp6$aZ*t1DYwXxh~M}~$3KDH*z8f|ddJ$m07)rH`<-Ds
z`(|U~eIT9G%XP?j;OV1u6}@r9PGlsBTpHUeIIIdgV9>AucN)!v%S!fgYR8Sb&YldE
zRDkccAnGOYuU?C$jPel2c!yBn&murmjsCDld2nf;k>7wGB`;YdhFE5tgiZLC#6W@`
zs6Fll+?WaHV0S?4A)tR!r0YT)nwUw`FE(nCv7G)22_$+|M=LE=)M64panr4v{2lO=
zznQpESNw6EPrWBifDC*oyGp^Gn2^?*s8?1M^F}K-dWOAl`Q04zW6|Q*ZO&H4=DW6R
zJFQ@PQA7WW0bvP<ou}r2Iwn(PGGr+X!&P%gCjl?D?+t*k2~%iKjyL+HQ&I<Nk+Q@M
zKQSdZ$63m_x+&yb2>GgeY;Ur`Y7WV6znL^R{kC}v2l*N`yYMvRWIkRVKnpc&vRE&)
z>E5v!Kl&z0tXpVxua(nj4-Y|^JKhrZ$Y;Fh<TDxigkWl!I9Caw3}IvyFJgjF{>#aO
z=eh1s6$(_J00|Gn>Q|tUt;Ak@K+#nQ0drS?P>h)l+qP~PDH5mC`sf2rUzOJINwRq7
z%3P)NF!i;$j!T)ARft|7JCC)E`V4$3qmv||**t$BxS>Zrwr<)YJbLZVq=lZ&w_-{>
z>1YD*OWFxC+Ge7BL>6518GnBWoicic(Q#WD#W6Zb=MGi097W!|oz`QrF?NHKVd6T>
zVhP*v)5K#iPo?@z!lA^)Tn&3O*?Yv%#<6$#y4f1Lz(C#01Sct8A$Q?<yqTC3mk1_!
zb3_V25!5l`FGE+4+#Eg>U;*g%QMv?&Y~qX$PeWG2I)3?($Ka^Qs#zYWu$!?xf&!ZD
znZ(ZKq2V8*2m!ETuLTngZlDuOuLD0uP@18-RI_8eO6{OFsb-hk*A(jwCNARQqv;3J
zaDHYXIGksr*O(SUQA0w0+~WY9XXBK!C3D1B#9jU(0VkH?qB+#dO+Kcu*Xw-n?_h!Y
z8Zg3{b$Rvvxsys-lQ80+Yb2g<NrUr@l%#BxA?r!vU@Qq#Znn~zxW#)#xla`ebumjE
z-*O_a2}H_Nzqv`C4ljmwVGx`44S{5(u4c^k^!pd4|GtzD?Q7-;FP7Epab_IPEA7=8
zSHG)DA5dV=&S{W7!J-baV%CPYW@%x>os^G6l(MPNAeeW9;6xF<D;cbP+^J-3PXHRu
zaJj0s&Fwequdo!aUU<;sp+)V1@v2!aEv@vpt?rG8&u5|#GDE$CTgNd=LLPEp7kdcL
zhdt;9nff9B0AT+s1e+sxBU7BXia2l&32O02m86Z~19fH8QNUFMDCVflMqNhcyn2!8
z$&<-lhjpHGc(bW<`0`z-w#LIUzT^J-_PB#|N8BkiAx=Cm%ac8;6XT-0ej58d5(hnP
z^uPcnZaiX^k5o!887Zxwm-UDgL_01ZIE={|)x;J~JJS8kaQyjnu)0!hI0u3Y<*J$M
zs_^w-Ck-9dE2<8+(N<^oNld~kEk@Xx;obqTeu`ZuiFa%To5%D1Ku9;D6Lytg`0}fK
z6FYGQ7r*yU4{oO4Q^wN_=)1m(FBH0hlclxB8SF;uDH+cc{4jGb+01Y6a{ZCHBv4z>
z1u6>_Jq@3gAjZH;eXMwLSI<cYwv7i)|7^{YfarMp7!iXKhL$?>z9;AS_2Dz*K0+t}
zS2|2DCa4p$^WEuYB+x3T;w53LYbtfy8Bbj7Q8nfUsSzPkDS7CzoX2>3<Vlufm8aQ~
zr*h^mazgro6`kEH;D`%ScO6%+*m<<1L=UN;QW>uXb8*s-yUkM@rlgid1#?&!>h+DH
zqg+WPtqfpupVafz?+}ak;Vt&Rd^Jg2T}#sH5hB%ScMIgOA%)b0byF}H17CECH!_h0
zJm@1lf=H<s<Wum(*YtBl6_?YTM>9V-d5hh-O;Q`O#WAk;*dAYiXwpK1`4T1~cDb^&
z4>f!__ESbSHcgA1-;Dxz%kfOVamb39M)`=eci{<)nIiVV#$J)%cG4o_dOSyE$GOSq
z+#ZTPoz8l^(#j^v6o6QhDrmt?oGdV3J-4_=^RK~X+dw`W6_P2_?Q&pWODo<sS~#SK
zD4-i|Ss#z@{$58~1EtiA|8s&$P^2RCL<(!T)l>8{?_`5}abmkqFU^vA;HJS&%C5dh
z*3Y?PAR6tm%K08=I`zzp@nn#rq>ts<k(FRo?U&VwBFb%)Yx>p~7al~wpL})4ys#X@
zqMxqujp#~>lTx`}1}|&5Vbl+B1@Sa_4tAv^aX0asZzg3Kp&(4t9Z)m%6?`>goBrv`
zZY7Z%M<Ai+;bXw_W20&|Ns=2~$=hXIpO%jCpr&WkpmAcr<7F+?cC#kPm>J`KjfnU1
z^Rkknt9TfRNO;@(xvh+CGbAR2r|Y9X@{uft@i8;V&>2+Ib5CN)pg5DwEAeW>9d_jd
zhOn-lp4l`2!VhZGwd)PGn}vMof)ol;k<Ngzm%0Fdpn)l8=o=p3Tm=z{I;k!^(Z6t*
zX(A?2jTMeBvd)dDB?Zx1Vy*k;K$pD+pkI0E(-8CUm<w`tWvP^<6E|a4&rjy%(hk_=
z3J|ZsrD6&sRwnWm;olr7pIJyi3uM%$r8OM1+a6v~>?G}O@Q5WDA#86A)?)v9)PH73
z<GA!`A+9T}%Np%Y4f}+d@FHD2d$$W~n50?!Sht#_1>pC$)d%S>h2W$_@Ka3TGu~_m
zf%gPAY#xY*KrXY=?qscoP7iO-uU)!wdAf8WJW?_wX3~Y<FxlNDDui^dsjvSY8Z~s=
za163ObqZ}6t>yU&>O+m8FTXkGXy0?a1SIvPe<Ib!_TDZ6vYQ${SB3$b%!DSlUa4q&
z--dNX()3fVoFiww0P$6brN`87(((y5J`<xG@z=XlL|GQMy?1?|yH6z^1e+V}mFPya
z8CCn|Fy&>`FsfEy?DCH9x$D};Z2?652wM*Mpo}T=ccRPw)npjbXj*jG1b03n;N7m$
z7oXF}NL0T;eN_kD$W_!@@-7q0=w$8U)!$Kxh~X<k%+PP<RozoCRUg?-2v#P)tmBso
zRmpAhqDS#MUgo#xY3aWsx+Y5NOL$n~IgHA*+{*GTzVEbXEDeNO>}nJTZ{2Cb%-9?k
zD%a!ntMJ(q_`%)a*grLO>BAS%Htyyfe7m?Mk1sB2iQEre()0|rbw7j9JY@1;brUR?
zA8xHBDtaz8Cq39RlCY{bNlvCABKX?jkB~}3DUL=W=~*Zr^aTmL_BL;g<NJF4Fdykl
zdzUb>Xi%q%_flI3MPdOxf;TU=H{=-6NJVZ_qDx4)Y7s>S&9Zw(!7pc-gm$&lM4|>>
z2|Wd`FKWF>KQ~#>P{<x=?lJQ=-L4;*p+VWY{_sBO(&6>7)%7TQ_M|Fe2;EEBY{a~4
z{l08L|7*WsCm<;xVpA(|V=cl0<SljOkm5na&^Z}**EWWN`FmRco=1zAM6(6XJ8Y0w
z=Ydx$ztN#panGH+<B;GeshCzIuAAk{tgrvPks@d0c5#1ll7UpS1zGla8FW^&q}_fV
z^^ffA9OjhooQT9ONJObh%IR9AM&qIlX;G>jP1SRmOCkw8B*Q`8z?_`rwg;i>RxAtG
zUYEAoVEaeHoy14D_2%J8B1Ix|Vv?$zqICEYnQ0DfW5;PhKc3GD1e!kVue`l>b^^QC
zk7|Z;jF2NjSLkKupiD=;rQxRO<qayOPXMTp3rF*8D+)GMoqHK>yPC%0$61m<=W3#7
z?p<xSy1HIgf3$lU_PxR$n_G03?RX!Vy72}lB3U03TQeJgJ92_Pr}7OL#l{rdH4^-)
z%i@R-azq?J=x;P5EP^VkPe{e5>HNkHN(L4;MN)?8py?D!9eOpa(Yh=ZzH+3k>-FwV
zPAW_lF8i>CjGgYQS_s~$C8E2O{A$VnMygBf@j7wQ9vs9E&GFD33tu?OF%lG0%BX2g
zn^VNN`!dqL`^!8-dwW$L>|;7y-I6VM>+r@*O~|2Ujb*#x);1npTWZpL?s_Nx(9@~b
zMaQP5`Wr3O_kL@|pO*Rn#R{doTw@L*<dmNfoy0W0fYn)#{#@*}K!0a4i)kO^gaMS4
zCT0Ln6Ps{>7fdPUJ=sDml0EJEf*I!}*|E{^id|^-)d7sO*kRzYc|#u$q$DE+3G&3*
z55@`~xJTv~AY(Zz47IK0AFzlMNF-B9A7-xRj=-5NmHYx~S!9Z6Ee1JYl0u$Zi!GO#
zh36|CHa~nUiDso%ryvXlGWl@W7;2gaeQ$5=tsY=GAJ!B6sq1AewL+NXWF+&%@zMyC
z%FU)M;5Zw1trJ;5van;GBR7M6^{00w^3YR)lPwc2MxrAisrF-LfV1tOU%_1bmg|Fj
zaJTAm^!RL1z2gyv(N3?OE%LzyenZuE2Zpovf_G0<g6g-+71|<z6Q4@w(n6bt^bKn1
zSRPeERwYc5haSDF(tQBRQj`NinA)n`;)mQPRjkgcUBsGIj&FIacZL{UhbHIZxa$r=
z5MOASsEU3W2Guq8xKG-0Ohq%}B*l`6Rz3eDr~dQnc}HSb6pC69;6)Lo#^4C0ppc%@
zrfAl{rQsd0GB+WNh?;NbNt6c2?32PwyYAZ+jI-g0-LMvD*t8}c=H@AEy)xXZRiC5R
zWWyTGd+7z;n?uvOs`Ox9200XKT8rE?v%cE)XrbX*j^yP`la2*^xMog`lel+2bgLp3
zd+x?W%0wQgf2TII^*$S=2W+m@Zt_4;(_E}cTj%e-7EceQlsQ{cG$!EOKJ6n*DzfY{
zDaS~&C2u&v6_reg?1zD0*)x$f-t6u=dX9r4nWKHvm8&wb-gX-=!{3#b?8v<_o{d<`
z^5Yo+^UPD)Q3SPa0S})uF-8Wz`7xGPt(rQ(LKcVPi^CJBUk%MgZKMO$Zb66U$o4sA
zfct}%eg6LEOcpb>mDLFjb;7Zp3)uLNlgM(>(CKix?Bg#NiO0?LNkE2kJH{&X{2bDq
zMnD3oeG8B8GO24N^lo(l0LIu3?grvAnkBzfqe(`!3#76IGNb?;m5QJ8ggP1<Ui^~A
zLpgF<HWy;e(+ZUo{mI!y%u2CaMtxoCtZO_bv~E0^C1VT#xdus>isKH;pjvI0j{FmE
zPW-Jcw|t}Q(IC;njQK}XRo!j!@|X*<1xQv;WD-Pv(1d9bL?y>{ppKc3(t3V!{sVqi
zWLe9Q55Bx@Z8KH8=;|)Fv7?eoL<0E^@WbSrw0h8oid*+RzcO3#JHW<KA8nC?-Y@K1
zb?Q9ITP-csK~qOS|3OuyPsw2^Ez^52#*KJBS@PZm%N=7XFOw?4EIxWB60hH%KgZSj
z$C14!a$tJ*DhkJpf{DR27h^Ei4L1&y2}4pvJxH5s_R(9oduGUbz^)yq`XVqN3R}5+
z@;$nbI^|p+=$N?fALrGM6yY8h>&Y&WKtG^v!@<uDvzm0GgQwUS?QdCTBYOp(v&I&`
z_2XlKADZAcLtv@KU<ny%ToM0fe+~2gp*!gGdCO%-6Y(KW^y;j2UTG-FxD6bYeKk`q
z`i-o3?1Jq9anPU5mjqjzsc)u&V6TnNpaTMD%*Aj~R%tOLBypX)P{gvG=ZxFrv8`z}
zhNqsRT2?OwR)bnsCFCdh^nNKjAE6^6k0ogR{`BwQuSDm-gQT?NmL{9MbXs3fro8gm
zH=|BDx;0VlEgIHVs_x???;0%3wus++7wVL$@1ZH;f;dBDKdUrYB0V5<S7rP=<yNul
z0l&_ucFfo2B1-UM!UAT|-!H`s$;!GgSZqZ<D+P+Z*W6T@-L2ON2Q^@E5_}fRhn*B0
z&JHYiAWJ<`l-Gcw!&S|`UL0ilhzaaiRX~}3B=(v3E?_7)9~S$$^Cwi>jW2j#=nYBP
z$S;)5M4DwUt$_Nru$g+BP;Ei8q><`Hd0RQYS=i+3u4-UJzl0h5d79)+AAc_TEe;#_
zE#zW2G@~-aB#6C)RvA<TvLeq5Y${n(#CIa{gLQIij_;!t|8xH4PBTWA%-cosv+Vx#
zUT{e0M!yzwxxwm=l_RbYUdjWs#U+*Y7jY`Zt5Y%K<=g8k!+JZ*N?<|<80yFG)(^%z
z=-2Bk-JoK19>I8*w{wR`zvu-jWOMsjcsSBY8Pi$@3%85CcQz20Y+ceh<m^bRF@en7
zh6H8bL;I&A`{0V+<j54s#!7Py(^tw4rl#h$rtG~CZ`W8Xv!fT+j+SkB+N%(5om^4z
zzBpf7%)Szxu}Fc1^)8ff#N(0O)sVI@v+}gZN4CjTYF`xanF%Y41Wb5VipTTjs)T;v
zRfYPLjB^7Xx<b=Im3GT=uEc(-N(SGdJKm4)PH}^p1b#H=7d0e_=)!0-^31?JvU5rw
z%;7x3$YJs%X<OvxW27ZnTOwo)Wfbp?b-(y^6miO*oY-q+qR&X$g(7<&JhXzm_Hs-Z
z&4y;~t<5&;-#BI6h_pw!BfA4igz?yIX4vHfHT@TLR5jOf&s9R@qSW495uk-vkh(t2
zj^gjWQmnmPXS-11kYcs)iY!`5$Ef5G>)g#4%IRJ?j}F?ia)v0kjvu>-Sc&UKgA7bw
zI2Go4i?3LwWzO#a?$1xrL-NE<R<$2&Mbw#H$UV2`1f8)<Ttk6ckKg0*<Y41)in<df
zWbMm0EvT&%H!?!%WXYU)dX#OYrS~i?;d(X@5G9<-z#Po;VZkGQ*=K#9q8hbu<1<tr
zz3s3J7`6p<0Xn(vZ8=OEB8METV1L=Q9Xz;yut)VqETzoaP(IV_L#2(QojJ?i%m@^z
z5{2tNQbl%-&MDUwJeDChgJ1DU?ER^E*)|8-N$0uj0Xvo%yBuKa7_I+{&{l7Ybv%?O
zL6^eX$2`MsdJcBvRr`~7HKSG9Mk#HX-f#bwC;&XHLR-;daocnzGOIa$e}abxb7hEi
z1`GI)!p1*Nweu^?6z3TZW6~}3f=++%IreDe#n~ltr@sdv*?4(+-P^>TTxc=Q?h_|7
zALDnJ>g<HWIM$6w9+oz|`lTI&L<uq$if7ZJr1==j){GypuU*_i=Cc3^Nr@RVT~tIR
zoaemV^Dr{Q=ygC0_l8qLOaXJHm_bm!HpTTTq`U0$?%c_K%7eBRQmJlb|FD^C^U^Fm
zkw+k;uYtbKJR-{{SCG;?5!I-kao>z<0LZ)O$1a`6itQ6^ElO|-pSlxQdAQqk+yNs2
zAFC;I9h&X?U&$$?AQLt`133;0=17%XqRmyvj!mCEL*8I?LVP+%ukWn^*uz=D`PAte
z-#La91+uIh=KA?baA$bF&lxf^FMvG0%AY#EjbLcmx{By*U4(f+zT%$CQ#k~23P)Ns
zAg@q}7?#)lh=)f1btD7^!7!Db|4s6c%}7lGsU{7`mI~)3>kE&DYFdbNCBcS_qgRS+
zC3rxHR~>316jmMWCHxDMEtM43Qy1UneVx|<b>i_GyAD`|rbvJt6{K7~k$Qc&jhwgL
zBRFiX8<O%F&B|fT3>Q}@74K;{9bY7dsT03oJ55R3)I6f=V)Di|Z>53>q>{&53iC?{
zgj{;Q+BS5_Wp&(~Pr<vg(|)>=W%zaqf;H3=VS-R1f-TXESa9ll2{gKjz8#Jp2=V2X
zMB%dcvoa>G^GNKwdgu+eM@3Q*5!hYAMgZe$Q(?a?QGHH&%SjPYy$4@XGq+>oyluRz
zes1hKbYhRqMo~djH9N!!=>tz%@GEq5>~0d`Qy<IED`}5&{!L(9o9PTzA&ld?xqPCh
zWs<0hIoe+{cqFKc6K@-iPj^v%x9(}RBNZgF*l#>LsK?!!I}TU%H0JNgs6}L64@NSJ
zK3PQvejPt$@VIglYlV;Fk3^Cs9L(0G%Yyufs99OjK={?2ekSt06D5QO1`7q6`=i@8
zV_j>q^SLA?^1AZ)JxYD23}LNCUiALGuP(O%3l8THflfet7lga+)VG<4u`Ic%#0|2`
z!j##y=vt6o1*9y)DjMpd@LQb~4dJtL3Mybv@Gb-Am<fXf=bUwlhQ4mpAA5v!Cy%jP
z%Ws9+20dd9bQ!McJB<%JBC=Ez&Dm8Ne$2Y(TBz@aG$a=G#JwH>At#!|Ba|G5C70%1
z>PST7_&i*C3RSwa=$x8K8lc`wN%_kaIa>3^IfXeRXp(mz=FXJfn~?cICwvneM*o(O
zT#Q(qTnw$$C9>ln#}01J(u1q-%;2O6G_6~(m1ZcQT>B@WwF4|QvlGP~UQV$5tQ{kc
zQk^%hP*8MFwBSct>phV0`sA5nV2V66$_krF@1%djd>01{kALLpT8iH>8_r>rVuGnD
zaMf9?A6D%QAwbMn!%21js&b=o-#Y_XVgln8WWrWP1}#&-OaF|I+*mc0pV!1X9d{Sm
z5Oh{1!%Aj5RTc6jT#+<?NHL$bZb3ph!>PUR2r-8M8}c&{bY?WNRY+y@`?&ri;s6I(
z*fhCOQW(Z`$*3TbGciN^peg1rZF@T5cTqd5=|Ltt2$xjzcRorIW&tBEpC|^=_Vruf
zQ|0g(>{c97QU{UPlTU4~&af|Du4TV%v3{@#xpoZn4c9;qIy<d+?4I7KV6pjYH&1AL
zfS+F8<u-e^i5#UvRR~)F-S|i+)1Z~a3Mna*YIcGSfqJrF?4L(s>6C=ReLNp>Br)L7
zk+729%Y?$c^7f&T$`|s5!$|ww22|+yV#Q%vy2CS`h}`YLM<zM_+RX*=QPs>5{B@KY
z2d?uMX^+7AY#4Kcb{tiz_=l^3geQM$-E5>2A=wSBs+DCD%iBAmPy{+_IF3bqFrIv4
zqcK5kT7|C~u<q+t<pJVdK*(o%)tG|G140b)%#0*xg(Q~Wgl+rzqsi$UU2q8w)+1)J
z$rcHj4gKQPqLsc?4>>-^h7PWNcTNVxqW7v3D+=VY9-G}xX{t0Pp7S9;sWp~{>-0$T
zt4VyzaSbI#{_M_-W%O)hFtqA{M9C)ugr)ZJ(RN)pXHM(I?QBuA{b4_kO}`OOfjRtu
znC!JR4`rXX8_RhUmW}^hk?7U9&e^gKp~J(ucdzu}S|kfbuN6f~^c4ZfF5widFi}~L
z*ws$<9D9;$mWwq#qHu_h>mr&~IO4Mn3M{yh>U(bU9fTJ1?#%Jr2ro}|b8kyxK`Wx)
zt|GR;Xg<-brq2=h84b@5^6yv`{Yu0fuUZuW$(1&B0>@T$T?Y>_^_!+M*bZ$87v;p*
z_&hwrOesb#zdcayQvyAx=j>_K`dhFrwRKIeRV=w>M|G?S`|S&0^Hn3HRw8E~9PNp`
zeK-U9rdS%MdX?U2d~-8k$(8lG_hVvYQ5=}-9C2m9`XH-Zu6S=TaP;cs>S2ZU0NSDl
zw6$}S!PaK|BP}M-bNZd*j+^5cttu~^a<-Btyqx!p*Cri<cM^&EUY2cDvQ~U^ulJc5
zwmU3wfD<x6obc%gm0R#Jl+hSV_L^KPre9Z2lTa(7)E)@_p?GBfJ_3F$E06Fa+SC{g
zHuYuWC}x8})&VNjSQVxuwpza6TX@K7Rq4ZAgWyoEaJP?6TI+5J){P0OL<`wGR#6FK
zx4CV@Y%)D2&avl181@mQ=<6)E>+~J?V6Rzy^fNXu9`!Hw5^s}3^BP{X9J4(MerrOy
z+ThTJOfWwk;+uIi4VeCyIm>CEYbWB`Ajj<Q{b~Ki?=!4{z&D3z5yG#Ydm_Z$Ew~ja
zxJq*Z2NLe_0v#(OEnf5Jxe{}Ir-k;rTJJUKymwlgzhYj-A_mrA(Yt{#Kf0#ey<B#!
z=rP<bqSB#%<|fUcOmtPJ0Y32<q)Gzs#rFEaX1X2pCY;a9ebQ3T-KuQoiq=PA10(t<
z@w_Ma(_#m5VRrl0949AIV}GZ|3Uw@v>Dp94BRK4FE!v;LUa{Y-$2_^$sZMqB@AO&g
z6rR8ge{0b!u-5fj9^XxCzKWLO+a~bm6k*l*$sk5sTRV?Tr>!s6L3^v{xYNMi)RS^)
zGWP}hdww;>yIe&>WFQUe6TLlBVVrz$tDeOI+wa9V&mtP{L-Dsm1X3-@MC=%DO6IJA
zYf>TRGPJj$?6Euu4=@+p;X&;BjaW)fk6^6W#!-L&>;?LuGFgm@nrhh#p)EWiYYm!<
zCq^*^s{TI8Oc;6HeBk9|76*-j<GvBhIE&^UZ)*hJPtb3c^>0NZOrx2CAVvui9Z`rn
zRzQ)%dO%-LtRwmmRVaMz>YLuNSz-b_R=yymwbv<U=ctFzW$yM!?KRxjQ_*FoqBvIP
z^+Eg~bti)-xQJ-EKMl6r0<s+;S+Gm)!z2^)<@a+60hc3n(n~fYIqc^5!yw2iId3Gk
zI%&VhZ?~8pc`AQJSa&o7m*jNpO<%OzRD4%0lzj6iUls|qY>0gHtJVtpE$4RBO8PBu
zheE{RWbFZqA~vgNmwZ-Izg84F9+R-;hEW;Jm3oDfqr`+_VXHl*M>4p2YriJFg_bz{
zNW*T7AXWzPPVXh2((zR616vxR*=k7-YPkZv%&(3Dj=t`#G=HuGbvHaiYS+4BmAt+c
zXlY7l$Aa0%1PKQQCLY(gZKbMvQ*bmSBR1Q`066Nr(9o_cg-Yq3<>z}!f2mSj+MPz!
zl2#;eT`bd_(d+(-$YB=uPx=zAY5TWLSq6JY<SYj3Ca^v40$hhJ4XXeNW}e;w!%LVw
zsiayS`2iwif!C24(wcb{yev>@WVql_u3(3nq1d^>#?6FUaJFAsJALgPK6+4NTL<ax
zFT@=;vNj*9UJg&A-_hv?sb0ag0V>V)7j=db8klIn>N(%j*ZTwQycYL2LtxHfI$c>)
z^lS0N3k*F4qZ0c4t!%YtHh*qld6u)bx;m1@f%fdsHcFY-3JBuFa5^SjZfe-ZS#)x(
zj%>_`VRPI{KSP6SxFqZ!Qsp;jtc?-}M^~~OeN&Vn^!LrBW40}FXQ%i^X39Qal%P3k
zZ7>VlKk?o=5`{>v`aaxG;W6NZ2<Tb4HAAdP7=GXcIjN!QL0*o{WiZ%g^bJ&}o`f#k
zo^2+koo~Ci63*d#Vf{*kMct`(^|tD`Uh(98bm(gg9a<cpM*qTZS?<Y%vg^~U%SQaA
z>>dypW9%@cZ9I*}lsJG#{7ux%@)w!TVdVABV#3biN0XdfjA9HdLi{1y<zozVl(jHM
z@bm$>nd{IZkwc_y6ae>#hVs3{4s``j#Ok4b@x<0DDn@peY$qT_ic>H^L(n~1N=sM1
zUd#dVornj(in{+ozpGC*7aL$Pm4kXj+^d~<T<SKv4!4_8@Y!Py-)(&%JEano#H-y=
zR5clV2g|i~`l%TR3MIzS_iSc&g=je}KT;S3cfS!MM0cMds%<6ja<YS8*zt@3f^rzQ
zRfwDHHph5PEK3a4kx?*Gx8vlthg@HfsMuG>vZM9`p|!MGSk0twxW(I)V&6tr*Ac35
z1U{7AJbRGEFvdc5k*U~{Z@X!Jnim^sk?-e8D{*<Scu^u{o{)KK?$Q@c1E-$!CV5`(
zn1W$&_;;_SsIo(og=IUB%6wD_X%4>BisEi8GaHBln@Xniry-F<Mz)Z>eSBU}KCRNX
z5f?^9iO5HQ4_cSyM$_#cMRZxcGtpupb>+#jgd28)p&B;R@dDYeR>bFm{r6=Ri%Yu?
zdy+f+@E|Ok#Wj+*CfSfN|MtiWPOSE2x@pX6!mImoN1g%Nv5BTd;hO2?(b0uKU3E_&
zV~?kGogcpx?`q(W0~ZD_Zvb-<J#px)zs)&P2xjT4R|wzd_Qe>q*3Y4{8f}Ql?@4T-
z2_&2jBer`RLoG#hxbZn0=H4i3&3g3}AF+Z~v!fi5H6c{znjG<*@_8ZE+&Z^|piSqP
z6%A$^Ols?Z7sfc#a)M~NqOdL<hyh`wqhU=eg^f$p<0Db8i?WR)?USgy7E;Yk6D>g4
zw_eb~b<_DxMBx7eH9*S0Wl^}v*Ufy3h?qdGO9ZQ9T<yeuyK^%TTvmPArP^iWavJGt
zhFp03>y&Icx9^+Z^P%aE;&npmYujVfx+`f(+NcpH1Z)qZm9r_>82-6B$q^P!13A|*
z&Pr4Mr|z{AM+Uv;tn)Fsfs1yRYjmI|6IYFN5M#x((;C>UEWI{#@9L6GhGF>oO)o2B
zKI*6n&ZlbL!v<t|c0&qcttz3_fMnwfR8GLsWN+tLb7ca;^1fN-Hv%58%3NAG{BF+%
zxry(x99ME}Kq`p*#y587(65f~2FcY#t4nR^;Q`goMS<Et8oq4`Y_ru704Qw)plpW#
z%2o^@ICXt)(EBbd=-ot<<-K2(jkBQ*2j1(%3H!5+3E7_;C({0=ktk?uz`tB@!bGdH
z3G3?St#N#1_`!v7ck8+`!TLdA)|Tw5ojmLH6Q>7l#Y2;^z{ra2N7ibRZSwczVDYXl
zIYL6jf9M1WaURtS(4Z9hEWj9$;M6S!MMwZd69}4~I=0tNAFZsy%}~BZAb|=)h+a7z
zB95dJ`^g<k``R=&uSr|RNF!mvYv?sCgLI1k+l|IuH!=cZtq~AVC|eVrO^YNi@vtQ@
zTH*~2u@{~S;ruAAZ?s-t*gy!rW|Qd;CqAD|Abr(sp5|qh2%VH!*wDc9XgDiz%O)qM
zb)y&`kAvNxuO9rs9f#!kDU(=T{ANEe>%lXFEB=4(oqJ?2Y||LQ+_zLOUxSU`@IepH
z`DsaEZJwV(NLq=>t2*6bZ7x~PlSQOVlC_!}c9a8c=OOXieKintl;7C?J#wIf*X}vM
z@h0Ffri6_>9_GNMh->2v+l?<B?nw)|E|S*S?ld+?bUp)L0M?lv^-Jqy>G=#Qx$GMO
z!diwg6f%sVD~WD(Aj8%TWM~%Wz11kEg}1%IEXM=xI<KF?aA_I^6xQY%tZbQUSVKav
zWO?dP0{<IQpx9(s&9%EQiD6x}lc<O6?O!N)ez{E?31$vrxJi?QeAqlW&==zaZC|n<
zHnLyUNw$w87&Cj5A_syjmUm=F)f<f3Fxme6;Z&KbI)Au7e~9Qm2l@|ZO=O=%-(>ro
zJS)uP*w={RWOaG7JDq>3PTBdx{`}LvP7iSjikO0@w^ns@3EzO({WeMHz*X|Sn<9Qk
zgvc`7w-&G$ju^CyzcfDzqR|cicVA+FERbQPjF}9k$dgT7mh{{6hvFUm{e-8=^M}O(
zo8{glB?<n0eK;Otk}jic`N~v8;3&T*?j%Gp9_Dbsz!TDsd0Cux_~FsPNDGq?oh0`t
zOkXDhFyVD1+rP^zVi{1LRN1?n_9f#;PF`WkNmY?$8y#Q<RVQMC(hSaE3645i1W>A5
z&>5XXfZ!)fp{~-HWI74$*tL?wzjYb&t_KU!f%`;osNy8r8wdhr|D}dF_#8ZbFP`QJ
zvG8e!!-(S-7e$=L$2v`8>;pJCqfNo?@VWpQC>=2#2P0zkxPL<E3gc%ELKylsBOVFj
zLIj-J%_*Y?-r+niG05RfO>heZdD&z<g8DU&IPy1y0KCt!8GMSXdT)%N$wG<O9Nd(!
zfw;8IQ@jKT813<BLg4Mmw5{R}6g;5_$K}4x$=ZvPeNDhZu-GTb(<$SnCOY_gb^f5y
zy-7jCd(Th`NI7i|DYm2}X?^W%S(W*OYPd)tH22I9_bOKQ-YNoH5$_RoJtRy*V)Q!Q
z$Ml2#0?cs2c{oBy4$?Is{PsI0WH{_{#_GI+;_^`e9<nPHpTVk5^ZSGjYc&~Ln?2Ft
zLf`c&b~#NkiMxGV9`kh1inppxCtsVANZ%!-$Q4OC+Q+&%Tw)4zr2|eua;%T=ZfVEd
zF~uk@j|y0YKDMj#Lqb|N9#HbH>U%ogmml`*hbT^23cyx~BTOGXf1qtJJ7yvn2=w!+
z0m}Xgpb0qkH=jgb5x>*FP~-p`Al)04IUNk|VYS4p0^{NcJWI1zON1FfQOD0{%0lc3
zlc{?AfCxcrYQUQ6IBf4ej)m#kL<CEoiiSN)LI<*I=(x-r7V$f_^5`q%2<$dFS#f2>
z^zx|@bg;bVBbKgMrNa>PTn{H=9~G-Zj4bC%K3r(N#4E>JAUn}>XEICJkBhMT_Ca`j
z??d+3p%g0IOc)~Fv(P#S{t42PnzRoo{cKNYbz(8J*r<xHd>2FY@r1B+GJb!$KkfIY
z6J|i;RC#`fIi5e{Sw`U3P(@k8`h;)V^G&F<p&skSJ&DE0dl0-#Z`Nc(!*U~*yoYmC
z+F!u4jG1IGz>uvD3L1<ERoj~s>FGr0H%jY0I{O}QCKnx7@x}vD^$DK=WHn7&<!wD$
z4y@%9Rn~pv_=>j)?F*B0KA28Xg7gDGR-N@9F~5RAoeAY7y#Ub$@#CF2u^TVyLF^Xr
zny?lBX~9VrmN`m>0!q}$s$^<RW{>fIkK<ui5K(`@FOZ1%nt3-U{N@g|=y1#8XtcQ{
z0Pv8}77gD#4ZMAz_KN6$@fNS>5#&;kR~-<UI>za{93E8jQamQ3S%sc|%Gh0G0z?Lk
z&UzIH^h;w*yeJ9t?6g1eNn(c+Mch^E+hnX($wB0G1BE?e4i5I9r|wth&batJV9SL0
zJynyZr_&(`78ee~zEuQoH@lr}jAA$hHGka2TT9bAWqpO`XUICzcJUrDysFuq)=Ez@
z=HhpCLdF@HF*&PWD~LAiCpdlxMq<ay?d!ZCg5%Y(RTmg_@g4a&v>J+sZ4_)W>Y-+C
z_dO0r-NT)WoA?K0Ga-|}#-byU$rKDQ7WqtNvef*GS9Mj^8QDHeB06e0zBmh`{pb=y
z$O(t>KA{i37z0a8#vsovjc1}zc3v6;Ixg>PD+RkT*nZI+JRjqk7gZRws`s9cDw5iU
z#W7s~F^Te&Wfo-dw6h7hIvPi)a6gi=kaXW&c^_pE8V^~aSVbo3-ZAJ?Kb=2(61`?n
z$<^Vg#0j2^9|Bp~IHmeQdyLE2)2Yd9tlW8dB2d{WxBi=_%IIAW0#67mK1)M)5SO|!
zJOyKkA7CxS_T4%^faLPxU>I(hu^F$3(fE>q3Fim4YQ!@4$-BYtPYhIe)of&l1mDH6
z#J#{ud3I+~L;{l(7ar^x2uLwZn<0<_r)50zaio3P1%L>#jVBY%x0a0pD@PnIU1~nY
z+n5VK_=udw@0x{YDt;l&k9A6b*%zaK|A+tVxi55LKuD=<8w*n{5Yoj?a^QjGPNJ70
zmSUw1Ng|F5!9N5|=&X!4_?8Qo(xSoq29PS=LJmA=%n9~_sSAm(m?CkTzU1tT@4VZL
z@`feb`2$}ik*&<qD<iBzkSKDrr&_sNS2{F&p-6;p7SdRV2ujkq`?{W1T9cDB-og$+
ze0@6nvu`eM6;H@^zFVPxscmeRBc}F1A8|-R1L0q*Y5+spkMQmIgg!*;1y-*J`oP<9
z@VapvwE|z(JN)IThHaqhUWKNCSI8}ADRkZwi#bnW`19Q@(TAzv_F*`NarMNFzu%DS
zneXg*^&F)vR_j8peoo`px2>?EW3DzsWeKu{M!)e?<2Wo^EQ4R2?GumtG7sYp8(xp{
zm9sitDo~Y1M<iCJr(uTgIkL)=4C!cvv2Ru?a3FqJ8Y8?{UgLl|Obo*AepoY|_r>Lh
zb~Mp9{@{uH$Lf@nr&FmHg86O}<R>*@Hi?-xD|O?C%}pbTmtN9L7f4JE@pu~_<6TuB
z;%O~Z*+(yB-?$<GmIt=BGNT%dvqoqG15}Rt>dKwZxW=tJS=Los_hXVnLax<g17P8k
zKVJDRTV-!ZF_yx?IKdLE-&?B)ljjU}+b*%BuoN)HxgG9rON<9$qtKxJr{fO9gr-n&
z+$}+)W6h~btremY*W9T@JR`f!gr4b_%8#BE^2#xX&I$p4OgMCi!+~p%{?XcitdG~)
zMh+**=fr5Rat>rDX8B&Dwgs8NP$5TPO%A;H&%OA~865H!M!UaPS>qv0Y01{H)-VVX
z8tM}956GA34R2U_5(kbbBJrkyJ?fP~VY5P7M*XNX;>0Hc?nvG--#oXHo5rK?*62m}
zDb_nm?nk&MS1*Qb74rpZiLK+Eu4Pj*PEhDi2d&uyidUM)=EK7mpSYmV2oQ%Q?h|`q
zdJxh24lE(}l?19#nEVX#N=e8<Vnr-yB;Sj70n6-j8>J<?cyCyQNJvc)qs`>0(2x~%
z#5Ozqp1+O0hBvEb^KY0?+I;LrZ*BJ+CS7`z$W131ZCq)-wdC68I#wjD^A#O8G?F}j
zK$hwG0}5ra1HXxG_@cR&EfyRsa#K3D8N2AtMYyGNK?qdjM5XVIH>+|+C0Mr-#!nLo
zN(y0?oh@?Hh&Ta4<XIJdkJFD@v+PZK-NsqH3eEWgMqZuhxSaAGnGf|vW@Ly3N20!#
z^RnlqF62*h#3k2+bAY;;YNzsafbBOpm+{J>BW?5sI4azGYF4Z2cTjMFJiGYVkv3id
z?6e?`0bg5i49Tk;_kQ`!BUrRb(io-*N3Ea{WyyCQZ^~&Sle!8KCfCj;>EiNee)QLy
z$C1}b(MOCZdDVtBdbDH>LH?=a?EGOR&LBMkUbgJ#a&p)0%xuQBD}zv}n%PPS!3~K-
z;+YPPOT2QDNe@z8cAL%9RcFoWshRrv$tE52vlhc$$<;yVFUr=vUP{QUlQ#*F9?cF?
z%yjYvft>IzHSwyGAJ^jU;QM{fNZCBN5>7z-)`3vk`IoXBD)L+#!En+$K|xv6D$>9m
zF@IKrDMf-55PY(GC4#U7e$O5}peBnOH4yd=+xry`sa8bTNhtDZ1O{Zkkoc5v=@4S&
z^sktF9KI>{6HmFXKv{Bvu9qc<q*D#{fjJHw4AJ~MMAUYb5zA`1nJ9MWZ$52yNs8cR
z)|Z?#%h6OLJaW_Ug`XffQFnLckd$wE(QJOYI45n93&trcv<S>ve-ZEoi!P;Ivxmfv
zr3APH%{Z+jcR3p@$qN~f@^!21MLtVTeDrB_PdvY)lQSo*t``S|lIPIB_{v|KQ92!t
zh-#J9uvIvJWXc=;Ue-e9%1wj8D{|IujY<=@GVf{MUgn&-{jNqmI`<UgJL>T53z?tt
zowEL?-ia_oc*Mvz<Lw?a(I6pdbmOsG=fZ$@2|}W@%kDX1;8BCGQCL0=S`gQdPkHH(
zdE}|{z#rHzCdCc}J)y~`#ZWWMSje^|3>3iv6I1@4$t$5wGb4-T)bn0DhFAI5LW+;+
zR%wht9llMkJt&ymHudUJdv@%u+P7`~iCTF9%2xG7>1U1o<ZbB^V^eM>OZZTzYxDaw
zT*?7XejClPVs!pt6h%WLk7nY+hi?L;)Y4W|%K(+c*14H7fh681N3x_i#Q_CAjX}KN
z5S1*vth?tn-9z9V=R$&BNE+vm&?3WB8UQ)AI{_qIA{gv>7G1upwXNAu%0k!_l}z_4
zKt^Mb$_<|8;J7w(kj%ptbjB7b_tY>iFjj>@Kze{>tMRgTl0VI(QqV4J$lV}XoQNR(
zzD`pEBZ9xusb23rnZd(Vu0Nl4fh&(F;b~XsW~Mg%98RYr7+)f5l?-8l6s|OtRFhJd
z8Mcz4)xZ?@^9jv-(EnC!o|dkWr5-tK<&|G9++^Se912O>OjuU@ZKsakFPYUlohs%6
zX?l@M@S>ejf44*d!eb_|v^Vk!=_fBnzs6zt<VmKmya~&a!4?QCp4mXoEZoCV@1ys7
zm{H=Q3d{1puO7uBq3Vzg=ROBX^I81vn6Oos$Q|V)XR+|13ktK@7A!VutV4ZbyN6^V
zvJa=1Zl_W&-SWqdV|kmT0Rc1a=u?<DP7|asb8ydsBGx;%H_%v85?if{sxd^v2QyG-
z4PyC@46_<BslaOn&JG6%UI7GO67M+=EhE?8LXP|Fk)peKb6LE+6wfZ4CUBYDi*_~K
zwL2#cke?VvE>J0XK`%XvOC43D4=4JD4r%!vXQRSre|FDpecVl12>dL7GE?vY!dY^;
z7M9N1?Fze{w@}bD*fs*aI{K;sF0Z_tgup%-IF<wLu528zj8cd)%@Xgl%8{J)Rm5+R
zCumYf5o>DM)<|-{F1=fu%Hk~cG6eVsl<(4!$G@eqSb~2-PH4S-CSiGGzQjJQrT%-k
z%u)IYb?!+0P8u8_Z8G1vfLtSnwzEg4-vd&^M!F;TNg}OA8Ifn{w7PNl_00YI;;&k1
z10)3OI3jKK+?+RwIk7dCQViO>@P@ZjgJFKxOFm7@_sa%Cs}TG!vFjVQYS|^dx${+m
z`njvSd<0Gs8SL~iw6!66aOhnrm7?w9LdlU{AIG>bhhrku6i5eHiQKFZf|vfld?4tj
zJb^1;%R~FPk}C2_j!<8Kdr-PwGkj*Ob;y%YP;zvXgnN28j&&wY%v(n~kTw)|c=t)M
zGl~8)xz~T%T5l!~T3+18g%~Ss$v50@Wag-vKTIF;5P}TJigr#jV+Bd-i;(+V$#sm=
zd-mQCMiOx%vJr&Yxr1;a^Xig>G;#tt7YzN{vi8Ytl^*^CX)h^dTs@a`(^Dq&VQ4o<
zUl~5SE97c`z{D`|F6SnB^-2QQ^3STqe_1A;e*&2+zlUVztF2ZhVU5JH2w}L%zL5J~
zZI4gOWn4$Pa_^Kf770dx?xg{ohP?K1QL%dTgYV8>U-^+HPe@y>2$t{~nf*-tBsFu&
zudF~T8K)DqjZC|}%m$nLt}c>I0;b>_2VlZ1i~LAQJ{JJEvapri0>RK2O8nU&*Zv7x
zR$fX(?4hK8>eVYNYnzyAcAL&CO)jd@%5~lTN?OtJFSr0)TI=W&T3}5-;8UcQ;><n&
zbM(FR>;#rt*zX&JB;iE9i*<MTU&-#k_Iopb$Kcm;o@;HMs^cbb<h-0;Yw1s<^;|Q8
zr{9DR>4wJExrmo(i(Z)G(wY}xAX9ismQJ>~!R%$$2JQD)(b<e~JRM8YlTBfbTRP$m
za#pq83e-qo`OrU)r<2pEwygc9ti;CWw%)S&{fZ4OWJ7TBHnBjQ$wNnU9^ekI-oYt{
z?SQ3waPqjGgs*B)<VNO<$z)~^`T4|Z$$p=|<5pSuUIzDI``~PY;iak8K5@M~v8T=K
zo||KlBi!wE`RtH)sKuu*L`FM(UNzCjKMq$l{_JmUCT(D}&zv*tlelAacdJXq<!EWZ
zwqvq#E##b~)sC=!%wD5D!d_F+Y-L-hWk`8xcz`)XvRiE1T5a^!%1ZDR{YPm&+AWpj
zJQhzdbDeS{ostV<&7SO`bRMZmu~;STqCjin*dE@dL)xbsAM`t)-}gCbTCtif8snEU
zkQw%!cF7+~8Iv2Iph?{H+eo@fLGCoPiX|>~I1irn%JK(}LQOW*WEqPsF|iqR&Nh>r
zFwAku5e8}_$xR5_k(fqpY;w&pXx;i~(cVc^qX(j&L*MEJD<aaycKHX5MDbrV6lHr6
z$~jML^$%iETKwWju-uTLZp<b4x~J*7)Lx-m=?bSf<E{fYD=(gD(8?vh@k0uY3z;?k
zoCRmWp+l~n9;@JYP{Jjj*eP2mP4lGPSjJktaH_P?RKjTvdvWxd)nVLA^T5_STtmeN
z!R87I6~sO!cXYq6vm9&Uq}VF%Vas6tKq7P}lO6`P)6{;l@d)CuCv5potr{$5Ym)Of
z4S(NYQ1AHzot>Lj+)c4`4bh}c8XCv<kyi|+OuWGZlDy2}FqkoO?W`hH=EmY!bD+Tr
z@(>dl<!pP`VU)n;c1c<ky=t!~zw!qq@X40}Mtki)%Bz$ICO~t8(c}%c?=MtR^$XZ#
z=NY~A5_n|8b7Gx$v7|L$Xu%NT>3kz@0g$jVm0K#M%te3ArfqAJ0hq{z50Z}D{m=PB
zlAauadH9i~UDF|@ozvX842sGeVJkD@ip?8~^r|r$2&tSsTYyo9H2djZFGxT~ofEDi
zJlTI?P?C)CjpGft;vN$t_+6HIskZ-bnb->3BIA<2rfqVi!!oXDGONDbnerejBp2=i
zc@o~efYhvV|3W%D=|L_FnIDjhM=~`(Ca(D}k5SUgGtJ*s$c7G700+z-tn@pmtt>-O
z%<3UHPyt6p=PEJ8e4&M813H2+3zYPoovCqRL2C~Q$+b<LX_GbkCl;!!CMZ`)SYk(~
zrbx~|ktc^vYjWq?*@5XSjk(j7Ub6=*34;*}lWJezhlvkokym`5pZi8Su5eDu4jq9C
zIfM9nxhDp3QkQ-gqvaUaYT%l9<zR6Jy^Hx9wp$hQt}WcKP)m(1Ik2hE_6)il%OsZL
zH(k|&Y;C9K{MMAGHhCZ7g7Ad<BT25OpGB3+ADpQxKdCJsKZ&ucD|qIv4F<su;jSB=
zBhZNowSA#qM0T`O)9GU7Xr~!d?EkJd63i;l#)1dh<J_NrjJVz-D$YOFbSjh5{eEMj
zHQ0$0+CGb3{s3#_rn*Ve2!?&WIscg!Je+?dIu$xdHo<#!#0kGx;J(IK&-4FV-Q1pk
z%+5b<leLKk{Ge~oKg!t9H1>yV^D=R2>LS|w`#=1jbtV9v|B)vOCzyO0rSu2<l7oto
z7gbb>kcO#~lC~(hFAUZ%&p&=&^AOprCJc(45T5Q&5*DJzBjlTrH(N&Ql#m+b>%Xgs
zbx6`gDLsBHFf5KvCjJfV_;<7zv6RduOTMoO(xG-pq2Y9Wh+qqX5S&vsP-+RHK%CYL
z826Y0kVIDcL$pPQu%s;QwqbY30OVFfg#k_*+KD4Q#hgd}!_WlJz}PrFqYnk5BzSB~
z83c9y@h-uvMq+LG?+6Y!0r46eQ4ss(b+kGE$WxGxgJVeNO@w;g&;5?iM{y%#_yEp+
z00%`lE@ZKhEZppfD#<<M(}qxtc{Ay62mb&889pG}n1!IlTMrOcdSLM(Ad$gY<K)P$
z+cmaZ+S<7OAyR=-(W5+=ZHXCD?ir8jw0r<bs-ZpQT-=Pe6=kJ_5?QJIBRIT^#3Lrs
z#~D#&6jG8Mpd~RUNu@O|91f=J1w#kO-vJi}miYPJtnDr=GFr+$B7(OAz)YDzP7Jt`
zPA3K`mU8sRft?=sPKqVupgSm76?yWCNSi<ik}@HtUXvu!VV5x<>LYm@9FhcI;F({U
zAC8<cWsl}K0s%4KXZHxS+?iQu#P+3Th&@X(I=w=4k%Jq|wY)bON$5M)z6EfFROkV_
zH%>cy6xE;x?zKt0b4gIGb8yxgcQ{1wQVt*t3WyT1L4*!TLDn4a9*Q~9{*_SeoRDpT
zvxWyQ{-k0Ywb;@5Un>kBFJe)K1D44PI*TOgSumn|G3J^=k`8<oEkb$NtI5v)6>^qI
z&JR@Qe_rp5wMXQ4J?P;75*Dg!Ls;~ofb>H8&KB+;TM7AwToqnpn`g{lS)2-5EP5ww
zo5?X$0{Il1M)VMQ1Wen1#Pnni%@lI_cx#zW`}S&?F;ri4kyqA_t0K`uAsvH5#McES
zW0~Z8A&?t(>y_0+iu{(0LM4Q5GDa|N>T(G2xg)7AF#n!ROFHtz7o`Q-@!H2mU*NzI
z@}U?)J#0SJYs>Q?+GzTS0LEjUF^0gVIjaUfmOGuxO{H?)n>;z?zOmw>=St^v!MY<o
zwT%&Ihc|<xg-aLo(kposH-;^<kQKX5$FY!9Ra1{N0b3H=m|jP^BwM%lIkD=1G(7*O
zdkA@9Wed?U=V9%vrfPQKHc3g;Ow^lPsn^A!TmBJekv0I{jAfks$Oo0JJJxZ4aGTum
zx8QL?<f5H|frS14{`Z=^xkaa0(cjtl$A?<r&(Y3>F5;0yjGZn`rVWVDfmR;e4UMmX
zxwU|gK}_D&+Sy8@K!=RAvH*+uh0|tv;d)B9iTx{t0DrtIEU!yYp%M^SquMVnIPmIO
zMPJM8*(k2!rU_@o9nr8)Ei?mb5V1gZdn{7TXBL=^)sM_fR(upjm)}}qj@EO1Bp?jf
zr~xvxBZ2_eKL}aL>46U{)(RZIl3a}-^)Wh2OG#jUAbFmtCDtrQN<@tgXlI@x)rig3
zS6iQ4ex{Z_5p8}I+aQ?&H%m0#H_L3d5)0&5HCyv~e=MR%7hi6m7X3YT1g00!NsYgx
zWS!@@SA)xueoofOaYTeZZphZl7N_jug1GPy|A4xABaYo%CEY^I%w2wg!CP-^s8POZ
zEg38^-e1K*Ke7O1j_1^h70%`rpCg{ZmDpo=Y|<<Sd+X1g$JN0u#k($2LT2hzgMtAh
z`_`Gjm3+QJE)sl>U1CC4hyHoS;ZJM<bI^SJes%s4vcig*alFKzj_)!>uHeRBw1*4M
z^0G5NB7Jm9n_Pr$NJbys6$l5__(tH?l*mGANqs1h5Dnr2Fm={^4hyHe9)EY`f3+QA
z;8;n9veTA2Q&o*kxjCHw^<X}Uo}1SC_k6|Ga#>g8$-gslb3m)EG1}_~x%fz|e@rGa
zyt2gl`vW=;LT08in>W<!D@z-ILrC%Em)(g_>qb|=#W=ak=l{lL4M|bEp+su@M8@@P
zdj9iaC=Gs@sb9D)gT>OoRh^E8X;0@TS~uHw<?yc;d7Vz)Cv<du6V8ykpe?!Hn_2;U
z+{CZ*f2!i6;pHr1^R(RgM_B+@pNY}vZ^IU3hRE)XQ*HJ<u&<i)UV9;3oGE&@4&}YR
zHNbv|H>DER&=s#74))uiP@qRo3Ej~?H}~1rPBr5@9y%H9WmXk7C{pHp2RzfT@fMIj
z$VD<qB~nrdDhpFAIT`HR^PlfHqVp^7b+w{6x-Nw;v+yW_)*MBvR~1f92z$W~Oh@BL
zAg;|3DuL4g;nJZr%Yscxh8JpbBt~5sxmsrLjEr<#F_^&++>1uLxI~Pe?@jwptLVg0
zLUK$U5^hSEgi2jsn5UW&)+6KWaVOI!l?TIOL%zi8TMn#6il{=iR%H+F+7WK)v0*PQ
zTlje$IM&Ur9r6Wbw`L#m-lh3kzIXkn8X6{ClDId5@$oM--BO&pp&l8|wBqSdyZp|w
zlfjzw0!~zE(R!x%8d>Q{hJ#rdtaMpHK5coVw9wBBh+Zd%-NF(H@Ymk7!mS8z8HsOA
zVEl-|VDeydVbBg;i<$tGlB6A95g}M#@r5bedo|M3urMA-G_8-|ul$%vT%{xHLSktv
z@n^*N!t0z=5^y)(I66KAE4|)^>yeW8v*Vv6*%0MTINfbczCgGye1e$VXZv1a^l9|M
zgEfFxG!w412!ZTTAwmTnydsYbnpN3cc1aMxzOuj^F*P9xq306U0)XQ4`d<n<4epMP
z8H#jGN;EFTbHHAWeSjq&IYysFZwT2nsU&2NUCR4MPaAvNFp*3fBjy^#P67(|lFZi6
zjdthC=r&&OO}6oEB@Xer#{H-#K}44$Y9cGd6I>^yl^jK0BV}iS!DDaOo+m^(VK%Me
zYW~i)c$8p`*W}{Kjbwq#fTP&j<gw|k`Df9W*!qk8(`$ha7l_NT(10>;?8USUL^z;q
z!YVdZRgPRsu=E+;HZRr1^O|eu^$uMx<jP$Q|3tzbN6vPXX2I(`9SmZ9$!cPoXau&b
zPU$7664g@Q*1MOHU=xyozPAa(yPV`Hgh+BY|Cua|Poh7t95QUuu9;G5;ihq+AJ(sB
z62Z5~9b)9J!kZ`@Pa(d<J%v|o#X_XhW}Zt9DDxlVNmfC^De1ly{rY)fND!~0Z%s@m
z_7BGm|MY@flgj)?)SA58B5txCY(6@3Oxf4sj=^nJM_erhITK;Hc}B=#Vm*yL^w0ub
z$H58AXczZ<%S|uygfBWLxmN;E9rpQKqF502R$dtC`LoPg?0QU6t{;%-T4BDg&;MEl
zdaEr2AWWr_Mz2@xT0)=}$J*3+WGrdA_4l^T<7L9&vZKzXcw7l$qmAVZnmn5G+ndq)
zcmNfaV*N)@V7c>f1u3o>n>KP5bh$vR-P725(pOxf@GHb~s>=hg;(%)mpJTl{|A=Ro
zo}o62%`NaBo5SsQuaowVn6ehm`}4Tqsd(Q(aTTTJk6{}*7F}04fM;4JSUY?DSl>!M
z5$O!Q?&c_N==r#EBHL^w5RCETR-VG~$=H0>jy@%)x1%s!W`_<)+6ti8ISZM~_LY5R
zI_0d4wgn2R&wqyXa(DibXK+<qY`20Tb0<!Z3U~M+hP)~-%Em$8c)P_NLspHubki<a
ze*S+hlGRs!DxXB^T@V1}K%5Fyah~#@3wM7iJILVvVCSwi82sR+CD3ob)VXYOYS(gM
z^y3}Vupt7r^OLA4J26`PX{oI#*4%mpfjdcb5fZtdyzs32CNnmpZMpeu{D9`^<Vd6`
zg;zgqZQHCHR$XzDMI=_iTq4$T!zEtabJ>|~&-p?4+@-+9rnZ7SiseOcxo4$l-7JPy
z82kp8R>m#rvTVoXzqo@p;-#ojv$a>2K988~_LBIHPLwE~PoqEOD1~U~J7;H&x6~?n
z;FSnslieo;xKqC2?Hxg08qFD!>mVV{6h4pLPt(SkA)R@3Ftod^r3ranySvvMR3epb
z>n2n}Tx{<GGvC}Zj#obIp0s(GZ`^|13B5R|aIm7v=U01%?bj+rQl4qVm4Acg({J$s
zasBLIQCf%v9EG~uUYe|QwINcH+DLf0kCF)#vKBTBS5JEGO(~g@rfkcE1%}GK<_Fk3
zp$+BE;*yNn+NC+7;MlvOufoeqE@)~{_;zguC(NHg*TV_Fir4G&pXKAd@Grz4y=%95
z#S;Ro3ta5EQ)Xou19Rt!#73DcB1?>`3n}mAa5-0$*_6xDq`9qI<@5z3q2_I!PTVt+
zY4%`I^6H#Z+opgoW-#5%r9YV;z$toUT>L}qt|QUIOeeMkj;`}sP|U86FFNfjBHrP~
zte>jt51n53b(1aRJ{btDBwofyU#=xcxvBl^quw34eyrVhvWsE0ox0^1ZYMOgnbR65
zwapR=ZIUp=K#!el_fnXR9XEh93H}$>;dnr9vuR#;p<nTUEVIfqL%!4zi-<q7+<3d?
z&a+)GByT`&?U?ab%^{WXb(%v{wbY;AJtFuzYI>;M?_1qarf*R-6}i(y#bORi#_NUT
zYr02Hy8FhZpm!tvVRg`wsom39#KXcB@^c!9lyK95!DWLqVrXRtNZ#4SEyeY-@ZL5o
zF~_hFPO?dHFcU<MmeH@x5B7#sivpgz(5Y6E|7Hl@(AjuR1Dmh}XA7^(wvj+y6IO8g
zDmmO1+WTqj8e=NCZO$b`^Km3mN_VGD<gviyO7FJ(kwf#QNoQg6E5+}z_i|&PSL==|
zdC$25g|_=(DgaHKjO2TC-8>QkblL{DJ#>=Zvs>rBjzaIZP~&S3CZ7T%{?g%S3tQL^
z>I8m?p`|;}#lf|8L*=hx2BsKntuSZoUX#|1ZpVd&A0{g_Q2dINlJk!n0)+4rpovL<
z9w8=NzsSVB=PjpbhA{m5C~kJ5<60fbRLC^c!Yv3=`s<y&mGukKYFm)@$nkr>&++L`
zBlj$Qi&Xp6S#2TVB^+T=M#V+(mX9uy86^`0Ih*lCFrn9mxN7{KoA`8^*Ba=ePTA{E
zm}*rSLgku(r2WWTguHb&$~aTvfE~$U&PfcE2^W4zQ#ui6Tuq7EEtGvKh@|n*2c<Z8
zt<dlf?^r5}tammycAKIH(8k!@DM`&&k)$PWWbDzADr{iBXE%DSrq{ORp=%|io{S{z
zcui%xXW<i~_7PUQ5a^--N~<yrIYvz4O!_BD)r)+ox1EeOG}`zPYqwn4-aPyz+u%~e
z=-y;dh#b+b%z7u??{O899|_C<dwO(I=$yW{y(F7!LXEXJYTqWbBLB@*0;h-)iAQAM
z6;t^x+W)k6bkQzI?aF=5)=ql+0(pIpkY&crQnj>FslSpAlJIcIJl{xf7@P)auV1-{
zx15kNx!Y9|`$ruBt_GXfzrFBSa8}<qQI~J9)LPydC=GSDHj2YxA5uyvtLMJHCY9ia
zDGFgeG2yDX*w`Pm`GiZVUL(?8)f+P)H<uaa_k2hUgyn=ZZ`-OSY`B%C9l-)Tlv+({
z6bi(Q*Luwfv!-s7@dqO&jChL*xK)p}1tOOYKfzo+PfLb(^nC%*`Mv1L1LlF5i#yQ^
zwbG=zipoP9U_=dDbX;+LWk%+k!C<A5+@}ry+m)Z&D|xLdW|e$>SKoGLk(IX9ch-Ds
zHxLKlHkyo^aWl140j)8zkAodt|K{JLxON^KVz9BFj*#}NIyvNkevv;@Utspty?0#s
zji)46?kKEU-L+(RA2A2yE0Int7+kjfAotTl8HL=dq>)SAqQ#Hgci8!x0+yCW68)Lu
zx-DspZKBMb<HRlENSTdS`97d$<YC|wjO`4>^;;}p`YcgBP4Xg~5Kq*s*qIM2+qc-W
zD*avNhIOc<=Zi%<$FH=9T0KcVM^3ah?sVqGr9&b)R}J(V?r-doI3yyiZ+69A+gFHr
zssY??soCi^Cf44rBu?y%KYI_UzlM}^bv#Q<`D-4UXMFmBqjuO%1u^c?IgrFT``o3^
z{bFM{*wy?(2Y~p$xkcyWjr|3@+frsiu(W4+;QeiD%m%eFHXUX1bS&K?c`X9~IX#5S
zLKzE;|1%X|4s!aF`t+N8UAtT6RZ|;`yfQ^H=PC~HyqKga7Wf+Vg68f@A#b%`4k5!e
zQ~!p0G0!_UUbp$yD%yrB;(5`om)?bLZc3o63p3>AteS?K-G;BeKm4(KKesz3Yfme_
z(Q<Bv-{g7K;e(aWFWSJxcJR@b&;c9}&=~sj#u5p@(zjcjozRl%ED}_X{dmxvD!Ev)
zdt=e{eJSf*5$)`V2bMrXNcJ1V*N*$M=Ob#~jQm$a(hj}mJF>U9a_5z_DNtkV@bj0#
zRcsJG<Hv$yY^G>xr(9r3_TD<Vm_E`>MhOn^^ptRMNp4g@m&LUrVNpu5CNEI|@T|j5
z%ts@F7nf;W9i+B&Z9%z6KV<*h$4)OKr9zHlWbGVOjgH}892;|zp%WQ%QL!UnEtZ=W
z_^1mrCqkOePkt%<`@Gn1)BOF)aYN}uNjr++f`8hA%Dbrut=PF{Zs3b{*I6`JEaLNj
z3#oD@i=lniyAGsnkq56)ebHud<$6~Zdy#BUpnPvbAtvJ${cJInK7DanXdzAmUTmHq
zJ<iI{dp;oVz_xib{<U?R`At@sy9DEdE>1(5<L7R;!RroL4pCoK5Cl<;+apkVhvrxn
z8+ys$74tPi2IYBSopruLb3N>i&%i;!94CM-WURHJFj+U2Byp8=paWu5E8cQ)mh2A}
z4AOJOrhsBbB+f}GOf5gcn%lV|XD^k0+0lY;JkNWe$*{^?t5*Z-p*$IlleE!}5{+yr
zx_aC1Md4DUB}>pg!y`=H#RdPOxc8#0Ja5nzAa;^7OZ@%FV~9o$-@MU+-?*pQ;pW`5
zE8QSZQ&$BWZH?a}vjy2Mx^0@<GLPJ<bh7O))^cmvD8NA9CVa}^bAH-YmB=f>T^XV(
zPhr||K|~#`o5h9>*2)*P?ilhF)%nNxJ}KpR5glB=cAhwBwN?wlP%fA~Uho_54Usk~
z=Ei$D7^`{654|_q3V#*(iU&qJCbm`Fsp0%zV}~Z;?lhzNvEN&9=O5seg=OW36)n%y
zneDbDDsMe7D8b4(ZEUyD5W;T_XJS~pj-L;dF+ML8hMeXTqN7!D>c~$F<fQX-hkyZT
zusBWO`LF!%flmsBL~bNfb7jKF6+;ET95YZS<BaMRN?nofGq{@(uU$jO^es!CXv7)1
zlArqs3%DJvCmU&9jomo>Lh1I)V{@+N%n+165d?DGkOQ3Go4fPBtrPlp+)7_;J6Cav
zS%T+(irg&0O-wJ7Kq4k!o`0ZocK#PEi6PQRu8iKALry2+fEyM5R_4By6D6~Xe|gVS
zr=gqBNbZK6<?~<Ysi7+dLq0$p+4}`~my~_ZJ{kVRQ@-51z&x^O$C{2HuY4!3$m7ft
zShQrjj!txpS%IdAH}P^80&9~Ld3i&p;eL`y4^atn#!Y%#q89`jjDl6YiE+HhEWM}w
zc=VV+JcDfwgAnjo5V80F9l;3vvO6CzM@B_v)@IYt8$;lTb7JsK0kq->BjKdNnPe}F
zi2Sipce2vTP;!%KOzw$WjceDu#!o+>0TTa#A?`yZ-XKCDqX9L#G&tSxn!$iA29GCG
zjLBRwh$avjaTc<i-p8JjiOai@(ccrCTO9z%!~f2IA*&akp<fc#WIxa*n7f+TVHL$Z
zQ7~5!u!g?8B_@PTLewcuElEf9AtBnBp(anWhyN*K0UbK;Bq|RvuRleDynnCKb&M%p
zblx5G$D9NbaPYy`7akYcPR5~ph6{a71Nfeg6YU%i0VH7h;jv+8+8$73492Tw|K%=5
z+WGLbw1Pzt9nb#*b*}kMoZjaXG@J_gLK{punob6RT>OF`@#XWZ(vkj|#rAx%rds(8
z|E=~iB8F6zjlmxh)OD(C4jzpHyg-JIE9{9}?YA}0e!qi~%8?VAUclQMpPe`6Z(4Z{
zRS(dqir&!?#AJ8U!qSx$Gl{ubCgH~$a)ADT*g={(=zz@Lb)B*zicE_fKvRtkVa_dQ
z*hgKK)w&6y5SikTWJMI;=EVkd8Y)o0mY93CD|qH#1%Wy6L3W=Erv1T?A!JaaP5)QL
zh1td&X(y?IF-r3L5tK}%c=chRxfv;rCL$kt+g<T{+d5+!iYaCf>f<N>2@azS`;F*z
z+i4f6*F9AF4U{Px2pB6uv~l8hNIlLR{%18jLnD?sTszwFyExlT9=b~s9#OMVkuX#A
z!g-A`TO0f3g=YM<5F{wc^ggthX*P!OyLv-w4B|GRc4D~0Y@YdFfBZN<aPqWvVavB+
z{K8U2rumv|1NHNd{_$&{x63{0m5afH{H#bcI>|35qssYFLk^TD;W^3bFZU*~1NESs
za?d-0O_uIrr+|7TmTjF2(@d9<yIk^JQYbr5y@3)dw&)6L|7=8Q!17+lfwE)faJ{uC
zstz18RAC`&SgaC-_X4$XO+90*o<iIZ>QTV9R?>QAruz9GN5BmnsAq|b1(zUcB8{h+
zoZ`uFbQ#Q~G{y%-gZ9FG%>=!#`JKW-HIrEe&HQ7|_eipKgY@O{3(d>BL?e)cuE3yK
zd4bt@J@lXCr)#L*Wt(348#MFIN?yq`Zm~#5;F86maeQW9@=pLSN#1`dl32K&lo}!x
z1g&bld|c#Wv>oD|d8vJs66-NF-yx+gs+8xi%@(m&Pq2eUTF8kO5M~I4`^z;<#P;kD
zvF%fpmFgAA>WdDrlYpD&d*({L86l`@Y#sOl9A|u**>&HxnBhncurNh&$C~zf{WoXb
z1qRl=bipqrV!)(2W|qG9SRRP;RZFB&!hD!Z_rPb4)-s2qA>(YRnRHzQq;}5+rpdnF
zB-85BT;S8c%m9Mqk0+i)SzruZ7pqNjK<^kb>p5mK8=cPk19-$F4f2f$M{)($2|v8#
z=s9;A@tUL#OnMI1i%U6t4}l`2zPN%6qT>*|7o?<v&mIED`QUhtd;bWT+O-j$mMaDS
z8;#!-{rf-s=P2W&N`$kjgMZ5eED-BNbUWw3+O{By>OeV-P1$*J`6tm!1XlD8Q{^mN
zHQ2gFIwt_9DmgL-O3+e$Pq~-@v>Ye!)LbqBc~k{0KW^?DM-{MKev2G9{dTbFW>?^G
zb324%%eu9QCh6X$<}hUMEH!G*#xN~R)%h<haXGj^#(RvU<A`s!ltZo_Iyc>BtL-j&
z{G$cF@mAtt7TU+noqJi4{ld<^Vm3qX8hKYPdMxc|Pu6*Xl&=Ht=s3Y<&zt+b#~>S@
zi%Pi(n`XT>lX+{Pp1>{xr<~(&SC5+uh(h^0ErAN2H`j`KPVDlWS#xq_7?Cmem(4_!
zud~k=FJp7ru4NWjbiN#UqN1wgbsL-4bp0T;=fhrvtT&8Kub!KnE7$lcFY?3rFWGcx
zNT_UMk<G2IY2)DHL@tcJk-Xt(%y)SKHA3bWdS~d>|3=|zyC^Fe`;s8G?ZCm5IGzEb
z5jcA>_f%8jR3h=)7Q;=S+7Gc#yV9+78v()-KIUF7teF(Z9COrpiZO9LTkNiS0G#?^
z>AdsVyR51Emwti)aSek=3c&fFIgesCHhBw&hVj_5zyVcMBQY2HKeqg!IK7IN?v#$)
zv&2wm5r5mBW=PzH&}inwDFwZ_-&GPdWZ@o3HI4bBhsBAY|L<Ji2<x;J{yy@ObJ1SU
zS~wi-UJWxfC$3R2JV`1aDvV)4AW!s*JDUOphfkicigE0|RMd%Eny)804Mb7q`y==S
z>G|L8Ncd=r6i?yKi;T?}_Qv->kn)YQ_URpQO}d+QmaUubzs#l7j3$21DfGxdlPhfY
z2>h%8qt7lh+70yiG<wcKpY#8y(ETUZFH9Fy^L2w>!?Ic@%S}@u`WED*g4<-1e?|`J
z(O`y~UWGPNxDm~d9_04gXNOO}5<Z#8{&m;%gKR~=K(^`)4{>X38L0=5gX>Rl)1%CO
z)jBEp2b|r!GP2+jL)_S6{#2fW8V=t=-57f%<H7@ltff8+UynZU#_{B~*jJmK&9(;o
zLIc~p+t9|i9;(sf2u9lyXLYDKqmpIk!t$}rRYrgz-624Ah^4?^O?WWr`7f|-G`i@T
z;|`^d+Mxj8>+dBvmZbTGbD)B<C#KTah*oZXZ-bzChj@xb&-tGZw+SLUT;um(#Hh4$
z+GGVxYBMN5kn6Wh13wn)LwqzGe=8i{@QX60&5HD=oY1D*GdbGpS=ruCf|Ns5c1T+i
z7pv$iRAW4=YDxNBMK6(DnH0YfT6>o>ByGO07o5;$bbr-_bslWUbT;28J&Y_RinK!p
z8BxaB&xD)hHPVvrVxOay8_xE+?a($d?_cs+$hIuJ<H({<fcCZH*{mE#xo;(5?7WaD
zJe{2Y%-bA{9so&IL#EVjl^#~rP%o}xr2QeM5#7}U!)3zS;)B@+`O%UgpG}6VxqX20
zi;rO&WAaC${W!j#M}X^xuMK?;%Y}r+^hriCPOFyXTC$qyusN)II>$S%v3r8KYvEiR
zisEui%wK$j5P!tXwONcli!uxI`6Fp`?X<Oia7@P;9wvpgpjwH-GO39PYXv`&Ap=gp
z^^?^?`9B=BCHOyXT>Axf_UU+kCRG;Y{p%>y>urThU~7D>uXsSzgMu~aZt)a0lK|U0
zg8^ITzf{EC+!XJwP8sjm&DSy<xU;q8nzpz#$f$NzebZhQ454l!@yg2=GZOCRAPR6n
zLldn^)xshKQx3R~0Yth1nE<`fLS|b`x3V+XDqDOK^999S!rSFxNn7?w)Wi>5lM~P2
ziz~?>T6qMxh-=c1GNeX+mS}Jqa1}CR%37^XvbW2`ke^1+9awX26=gYZ|MQXkZw*%i
z12oaXrx>ngit}GeW=S}W4C<VC?8O>5f)?eKL^KJ#WMelrL*jMXL6JKpq87&4K_JB=
z#;9T65*?sMP<`u2IF4I;-%?(LN2kTCjN-$smRoocTpXPucXuO<`N9L!TJ+V?bPZ2F
zOs7^%ZdqLV%W61|@m@uhnyk52;u}e3=Og|vd1vnynvo`#NsR8dI251Ke{fu?^S{CA
zn~uA-*BB5ig}-KV@O<gQBLogAWgJgD(Ihl~Q{t$h!veeO5kya=8-FI*x&P=BNd{Oo
zg4sL4+|T%8@Y!%S^t{1mwgS@pfc`z29Maj8kYbhIh5F{5`FpL!Qcama9J=Ax4m@ig
z?3jzL`K!GMEFhPA*Y%IMca&F6D7RI*!hI*&{1IQ2i}zYs69dlFxI%PwtfbMUx^v$)
z#G-GJD^!<U4QMY&kUW;VF=vyPXtt(l#S@<R4qc{0Y3i?LoN7nhvWkQ2{eq{NX;D>B
zz3;$Py{pXPZL9{0Qdhme1&lJ&v=#kIAf%cw3XZ8coVW2)VA^XvZhYAs;^{8S1Tzq_
zE}MF+W_%g$j6LoM0yA`MnKa)393fzT0rMTluRd7LY#7tyOIHly?soYT3ydt&<EeKY
zi=9yVjV?KPNcrwc+DWWjbWi7&*^8{UY|`s>WT`AZy3EWu06F)4u$$wLEJKo)XpaS^
zlu2ImCii^5Nn6RL_YU?v=vEO+ex@lti=-EnEoIaw&Lf79*}KVE?N2OYwDPX3{QETr
z3FN%2^ePZn0juaWpBx=VR^`80U=~>?7SIQ`<Xu~c{Zf2uWMWdzq2cZb>1?}rxVy~s
z9J1$jt)S4f{Vs{VI+M055}4Cl;bBNZ=Z*!CNr16Q9o*T5CytR_qgyUK*WTW>+;hgw
z6{pcF&c{w1L);A2;uAD{sqTV>zzU@Uj~bKv>?W6`bXENRp_5{en7=sK#%9)3F&Au;
z7KRU<41s?76AUcE*|g&p;LIMR+9WW`47|ulv2R<(WU%P6wC>uXGE7V@SUXDW;M|sr
zDx$|v5{t`E`ANIi@vSK)5=)+?cgUoWgcpQ5H3Vlv-j_LUlFb)iIN80*{L0y3qm4!;
z3qD&_n6@d|`JWK&;e(mP+QCQ?MLKL>ngf$#gQ2lWwm~N_%|=19XTMX-CKg|XbEV}d
zNyj$?Br$`5j@e;lI~KV5SI{=E5v$P%@uo}FUh_lyIZ2lh?QkGwhNOgCb`Oz0(7g>p
zJPL7Hi|u!zg$G`f2`u!#*ghs38#Qg-FIyx|nkiqg&=TebGI-FSTKZFCJ4wqYoP}&Q
z`Eql<LWmOB&!iQy_JYj*CH|@jUPG3mFMeEJSSfRQorI33n!BO1+k>=M<O;MRk$xeq
z(-Jr6MF*4a_?Hd!S2EtqJgg#ViLK&LioB$daAkX@*wi)~VqbEe*CfGO{QgLC73P4t
zIV^|dJD^Cy|28J_aEHt|U145VF2xivd;44?FOeb4=Q0m*uXtK=Hdo*2oy6Qf_<jkB
z1T96rbp!&`HxmP0UK6RD^Ln&6k)t<42dP!uNWoow@bK56Tr4sDUXxEUnrpm6=A;&a
z47g8N?X22b$d2S80T|nI8r;LKq%@UpW;doXmFO&|d-&$fW3w=|G1ev1U#^+I1+upe
zIcF<s9}{h(rYF}}#efXO#IytRv1=o_^1@o4EN!>HlD2I>Pmj$8s&*wqqqA1R+kOC&
z$8FKZCF@)UF~yul+>G0@Y4(>nqf(aa?WGEoA({6iojX<8+1XmcZ5*fb05e{*F==xJ
zH*6a}7`2}ytb&YAb{p^D?cC)&H>FUHCe~Huz=lAx`bX{SX?69=cKEdN%HKSmqE(hT
z{*mb~>}j>B0lo-i&yZC?(zDsi56>DrzLV(7J6##lHjn*Ao*fB*k)Avz%ii~a%hzbN
z##CKqJXRxG=9z6A%t)+9-f7FmCFvLf7bB+wOj+h>vL+9#SXlvD+>}Nd#1~pp58f!e
zQCC{lKFPaJ(Ge6ZN6LWYQ0^vP1q{5hwpM&dSi`z@0nNNC`K=yT-PaBQg{<vJbO;?D
zG3+Y$8n-kNz;IqaG_62ewyJH&<9FujsKBP+Rjm1zzG@_hYeLuR17Z4m9JS8FN9lFC
zapSELo(F}7eZ5lIpy5vvB$O9zbK2?V>8o5{qH;2dCuJH#%5x-|lpI)xpog7UwT_2b
zwckv<dSI1H$MQP>#X7%AFRani<T9kxja{@`{TP3N)*myjF;PDxxr~{+Tt=yyaRnx}
zro_cKR5eF&L2HxM$yZ}Rrll=tNkDUsguv3Q;#=4dn-;Wmrd)a#2-6r=Hb?<X*NEHR
z#}~IJU1i|n5w$|lm&E1cW6Nx$b_h*oS53yAjo6enWaA(3%b?9M-asTSI-|;7m(0+4
zZ8^~Nl4%{LjZCFy@5Q>HE4%xp^n|@*kZn<xg`2i*+qP}nwr$(C?VGl3<EG7<w)5S3
z-5pU?ud832i2dut`mti}vBsWQA0Jz<b)BD1d17Bu0rc+DbXDU62!{)9k{y8KjB*Dz
z8!NXQgNM!UIObl4Uz2Y1O9Xi@2IWt27W(N4Ko{N7%yIqeDSh19?tC8mF2^!e73Wc`
zwp*+Z6)ahocWp6+7Y<%o593v7_fE_ej|jR-O_bwZ!mio-qZC^jw&xAXvT>w44oJ-~
z7tZU6WHjREyV$Cj?Wk>sCEdrKMJbMiAF&G!O7F~VWLn4_S;+_FkV{19`wgLEvYvV6
z`Z{)6S`JAp+ul%)A1kIW^k!=5J^bodI8wP(rp16;hSK`SmP($97Flu9j4MS_8ASzG
z^O>3KQWw(l>Y{AW78}M0`p<)F6D9!an~D`0d@OuIiMw4lmhcV|@VxSZXe-?diu!BV
zo0<XpQ@T51m=4hsO~o>WJ&fa-+`o_CU)7HFUJwioRA!5duamo3Ii);;#l<^@7QjvW
zNBPaXQdDtooyZ`a2%_5Bb*1tU8qJss2Bv1C8gaw=+<_(`Ng662Qt<(iXZH{l<q|g#
z70rGdXxnfsciMR&Vz4(*N{G3*_cELX|8kj(csh0h_U}W88OAvE=bl7C<kxWH<e9{}
z5`|WYOqlDq>GQKu`PG7fz#<IkUQJ!Dl@H#)($l-6r`qunncBtCJ&EvS>zs$C8rxj?
z4*LCq?|=6L{10%J*I{n=j1>UDD+17ebM61);Q+=(PyYp+1@k}PEL&3-3wslKR}W|a
zK#+g@^Z$LQs=xw(S0u?;l~gNPHUH(gDM$l@pa4Mp{SmbN`InV2|7|5>C(FO^OH0H5
zh>3$KP_ioi?`31vWaAInV0z#gegwxWL5scsds=#20?{bYytN+-Bw}bq(sX=H$Y|ep
zKPc8C&6(X!m@ue`-X!?=E;b*M5q|FR3EfsN{gAo>otn8Oh!Z&}e3LF}YLvmnyS`i&
z6c!ia*1_h`^v4%8-)O*4<x@l(bJgjtMlOx$g-{GjDt`ZM`QW{N<b*_()cK0W5mB!h
z;O~(=IOXRbvVdVkw|_WZiYxwU>l62(nDCO4bOSUjEhOff!P?L-+br6tgCL83f}mx@
zq)d$JOecF?vHDzyV%S9;A2auEe)JXN(EQt+z@><vQ%JGGG3uapZTN*QCQ%dp=tl|~
zr+2#m?S-owvFa}5Njz$Cmw3g`p&?!-MvXqJ0IdsF(yn(mxAVJ+6*RW5TA=o)MWpPY
z-E&I}v695K9*$yF$p5Nx6el9XR*0KLbUFkvuPmWL;^8k2S#Y(m-9~&Z#`P95;6SX)
ztArr);wY8{4Z}i3k9a_Q9ATYE)jj~^Q@)4P+>UUBF-%Y<&yfdUnfj%^=-FqEEaQ(X
zTOdy;i3W?*r*-Vc*(yxU21G05#C?2`x+G2nkCbccBU9@2g+jN60@V=DY)Chn)|<AR
zy+vo7XD=PH>vR~2J&Wd0?`2xX)nC`YH{LnKaMt4c`HK65=RixrTydA!{t2d;ERmO!
zL8Ekx49x6<BQ~lcjC|qX!1k2gKuE}zJWE;>NX7j8*g$r{N5T><OyAS2=uQQ^Mqrk1
zah<8<-iFob(kve88fc*NZ13w=(<cza8%W5<^(uW|b&%>2|9icrJS?bCpnB!^a)4<m
zTxVAVPHGt!KaZ|DADdH?t7HMxpMEeEvVPk|yr`LwD~udyddUzVy63a@%08nanS~BY
z-7d&o^D;uAZooS@uvzjcm}`dzcEjm5O`|Nq*!7ZIjqbcOM*R1^;{%Gt-4U^>!v{-s
z!0mlXP8ipG>C2=g#7a8LjwqYnZuAC@LE^yhCTsfO<p>v3?c7abc8A$x-@Hb}DF;}Z
zsJ8w_pGBLr`Y4*9Ug?HsCxb5F9~Q(o9|~Rl@ZJd$C#untG_Bk4g1>aW=cq^8wO1xG
z-oIoBUHj5jRGQV9Z3#7V1fa!oTCcT)-x?ZIl5ACVR5ni#utzwH%XNV<wXh<*&9Yk)
zTDg%=FHHB0p%&bFnb9Jw#~M`{M3>-dR;<;?bG(DZr%Veb*CyA-SI9%1*Sl~wUW(~y
zXm3ri1M<xEp^kpPnk_2|*9gA3=vnKt@^w||(oSG{ZQo?1>9!mD4i^qVwJxHqvDeWr
z2<&a)1dGiY^U+=y_BzV21<umTCb{h#sUN!!_->V)mMO{YQ&L?WRu#Tx+g?7Ic&U9m
z1~YAT&z5yF?chJi9`n}IgfrT%9+vdy<o`?1^58S_3I3`QAnZSr0IB{>hS2|AhCGdJ
zOr8Iu2oe0Z2>nCjuC%1%H`x$+(a-!fE;(Vmt{bxPlu85=h3Q4%nnk9Dm5PLvcG?Ah
zyu-bekn$UIF2SH_>RUN-*u@_lKc7zXudlD0q(>vVf1a+ZzoFn!RAc&I{Els3zGVBT
zG?itd4~^-Zi1yy-hk|p)W#+XM^)S1q%YjK%OP23{&U<%Zqg<jryRg?@1u#|7RiN|O
zGmCzVW<Xkez}3*6cEMU_YqPa82$s!k6`DsdX`4C`S<@leV6e^9D$<Nje!Bs#x$Fg%
zAZa8X7+qgVGX3665h1uQB@0TTB1WsqGITvE645XrhcGF_GAssGwp7$a$KXXaTmoR{
zRAtMY2~_kfQf<(n@f1ZxuMcoYCDsbcG?!&l^lfZE1Li|8!vV<8A5D1lo|z}%a-Ojw
zKss_32BnlNB{^6LG*0|g>)Pc%vaXZ+d_+>*D2r&`t(HS#E}QMqtR#ZtC`KgIb-+|Z
z0Jn3tw2b<*axw>Nw@nKH_6va$F|85tcVdBZV-1I_b%e@mzgGO%$#PV-;JTvgC7Ioi
zrqj)~3Xl>rg9^&%o_2e?l)Ox5*?0>BR0N!fOVR?H8sObjw|wH-6)cnnUK9)B_H{tQ
z$b@9#ydCVwxKmjY5cBm51QdR^Mk1XY^M0H$mBgqt#~9}XKhgwtV&a)Im-p3$Sassx
zwu4vT-zrD<0oBZU%e>o?w@6Eq4IG)D>}IfU(heRs%C-UyL-w&Y)yMfbNfqU6k^CcR
zfvK9jD>uXo;)h?y^U_WEJ2qzmB|zv#5QT0I0`%&!8dh#+vVQuj{p*F0hng>7_Z|$u
zKO-GBHTcrH-G;XMWg8yuIG&{}pj=9Tbr&NbshHL?O1XA#G8n&HGtvO-L!|*DN!8Gl
z^rRne@p!w15lBJcgY2-O(qw1cU`@%Bc!gFJ)VB8$R%0&E2v}36mCTZ_<rYivk|LOC
z2y`G8Pxw4)mMf)vq&y~bWOI`!1ew<t51^W$&y3*H>$GJ{qlqh_bX>5WRwC(e4=eoY
zMRo8%a2N&epd?_%piyy{A<tbxe!UgN2qXHDkk10(3XxeHGB`gS9zm<hS(@wKx@6WO
z`jl|~Zb)IZcWwX@OLb9h^HddnfRGLo8ycHHw&t-?`LrOo*f<m{P&BHUU!tVJa^~Xf
z4w`Yh^A4Dy?zTL3jorMOEEOG}GzQL#iK=x~7x{e^MphmQPv41j#@SXxK-mZmI+@Ly
zf2TE^`Dyf_luh_-w$JTa52SOh5yaQ*REr9<Rz5dvY+BAB5~+q+n_0^2eLm9^TS%fw
z?BbrDRy5bT5XZvZi`%C8X#BiitACLNy)rT3xoSaK9p_F{nS`=^%rvu)&%5Xej<cQo
z;@Zir!!@!d%cgJ^y&;XQcB<XPtJt%l`)l0}>QPBuCy%RZQ+qp0407wMlVx`L?<Gma
zAhz8Eu}3|}W-L)ptJDh|r#H^%SShJqkXXS%Pttv7C+rgz9L;ONQOUzv3yumNEK+bz
zUZPXqFujCYY{pH88E&J`X2jaclb3qd85=u&k)SJN)sB8$fTr0#by<5^F?IO|S;hp!
zU#)>o$}P=-*UZ7EzmkdQiQ)l|0C}#%4<A;rpj89Cryr@Xs^k&Jd-5^&!H#-w!S`RY
z3~C@R1|bZ9#2O_Vj=_+7z302oyT=Od1E|Sl^1vnz5j|0uV#f~ENd~6?Z+<B^QkR?H
zLG(eUm%|Qr5;3!ML*z4>zMm>20yp_4de#^Bq6*0)b#p7pGkb#%=aD!NJISXsfDVvH
z{*F3Y3TlEcicj-|Hi^eR<2OFtfY#dO*&JKt8`EQo&)27S?<I2dKiNiz#BN~Nby_2G
zM94X3w<bo1_>3ZaE;+w&U!-)tjGRG6j~5@!XPapuXH$j}39>Q1326Z3RK8E)y2<0X
zx@EQu-i(K>@543mBP8%p1AW&fo<{Ho5&)@Gf9ZeN4Bjt{qlv4+g@9iHh>h*Bz({m6
z8Zr?e5e3}m8+h9rBM#vuZV7B_1JV~3inkEXdd<1nA>}Xz&*3FnU&b1mkXR9)zc}GZ
zBM0s+D^UOS$?5i#HHK}f!qFwp^SV+Q2H$gyL`r_ds@kZoO3@j#FTDvk19-yxer4{D
z2g-TDO~r}Z^DJH%tzLAzVojh=UckD%fjnEcF`o^a;T!afPvbqaVO(&DT<@B2dD>wa
zaB1A(>2T?KEeC9z9y8<6_%W}SG+_Svf&UK!PpJb#5Df+ZpwII^=iNVSIb+Me8hH4B
zJMT<P|5p!huO|DyczD@=J3NX1zl+%z8kyQS)BXRtd82=F^Py_ePT1@S+aD+twUGD(
z-0O|Xl;V-Zst2Y}IFHi>V8Al_!eTPVH0!T0dY)s^$E*yWF(OpdNe0FIH$B&*yY?aN
zg?%#bO^{@Y3>PQhj?US}gL5e1UJ}=4sxZ1x^3YT8qq@yGw%y*`NHAFx+C)8SGXyJQ
znANLkuiwC$8x-jhTh$CD7F^{twZmiUS{|~3uaQAgX2J);7~>sBGBG4Ig>gB*U+a-P
zQ8p0ZcB>_8V_DB7cW(MzS6RLU$Rc&otT&V-j&}Iw9CM2uQHn3S8x^gr?v$PV+{1?B
zQL_DhT4Wu~6Y2tL(MCr5x1r66p$bWWlN1ZjOP}N5>ZB3_v+{1?A&UbmEN9|yBOQhh
zq+rpR;w531y`fV|vdZ?@C-H)Czc}wan2;GW9f#NHeubzpe#6^o!{La8<s&#Rk^8I|
z2|XGZO<)%k!6EjvMCzGTkP&~eyd^aLeYe;#_m?1ds}q?&`Gz8lt@%;l(HBk~0-bVr
zdt(SGnm=wNR1qZHjOwZO4n^*>nxSkXSt!QtorKggT>+}dd!MA`xS`~1U;&q4Luol>
z!D;kNR*In}yuwnK$=CwPj<EpzCF+Z>zOCT_MvRxZuPa2*jIftcASZ%I?k3`skIlCI
zYb8F9z;22HD>o6%F^9W2#}AR^#E~XlUj^DyfTReWuj!LQT$m&+ERtTWnz<ZGie7<g
z6isuYJgh62WvEq&B@O}12e}8Rq(@oVcnYDBfHjD8O&SF)_c+HTaF=k81)<2#Rot5f
zwlbjybXLRFy;PPw^Nr&YfBWkrb36-jlaS+8Wd`U74g9<?Ds7mqK?;0Ng6y@9y^tLP
z@TeXL9Wu+Hr|hmm1Jl(En@3~U!W#o#VlWpWE|h^<x<g(tlRJ^(!NO<a`LYoEyHL-C
z4OqWgA6UkiS<y;G-gA&d%fSt5RIIFUw@51%+G_`W)41mBiK|$5a*c<miY6mkrlFxw
zwV7M3<7M?Q#pHoN+Twn6;XLnV12#YI3;kjonkl5sDpyCg?YW{#NFX^G(7N+O$PZrg
zlnA)13sO*eqXnkE?un@U!$9KFjm87ILXt^=cP7?FgG@nN(AnV}N0TC;t7&cPCLAPx
zIplN!pqg}A-UjCrBw7Ld{P)&Q^rMVqd{q4;ZTzs+_ba6s{gb6s4*`=uY8W(;oeI|q
zr4P+HbSr_@;HG@^$687NP$YW>RGGATpj)_8jN`p9XL?Z;k6n|9%Xcb^Evony#t<W0
zX0{%Z4ny}}`r8}9EW!D|ej)UR_lB;<^}IiPYn$*}*MV{0mV}!3v?ASjN@2^mS2cQ$
zO-doO2Gx;Ew9)$LLPn1SsA8I4Hl(@u#@xMu!<4zM@N@U5fB5HKi0g@6X2;Y~we#Vl
z+0J!ic-#6?eUT8-avry^Hh>$UKU2*0yH?t&lAA+%;8<NNa3GIASP!2lR2WPrcG>>K
zh6^9q>f@QKvzaeUe412X(VaW;xw3fpxu6kAZp}2K4VmXmd8_Kxda%q6R!;Oax;uHc
z<^bh!0-rzhk;1S&M4Zkj00o=$9j0m@Yb^P&l7N*oW?+l&v!L0Jz4L+b#31eryHoTB
zTEA8+&ZV^CfR4pJjRBdX-QM46ZQbgf29BQfy`9eZ|3jC1=3O^8{(grb!~Bmf|05mp
z+3~OG5W@c~rT_OAiEqh&rA7Xs*ezN!PFwAWy&sece6K7n*BujSNluM%sMbAo8`vB+
zP71<7IsiDLQpagy;|p_p$@ULMo3OXw1Ou7-7RsemlAo53H*5O9pD)y-diMFPq-Skn
z8Ay6RnLXc6minz((zLDI!1qt1-W0$+szr=NY0rv)riB}2fR)%DXdUyLxb@lJx}%#p
zrmr6--$UhM<Tte`N5mPrvFW>Bjk|W9L&}O!4=F5Fvm3RDb2(^ITVH~GFNeV|k9#{1
zv;r-S^K)uXtV-ly+mI7EU)ZZ^m%lvR-9OW?bMgDGL>j;a)%Jzsf&PMc72*k+Qm73w
zDMI#1>jn7%vv}JsUx`6e@%=AR#$l!R6{vkMey2+Xdy=)_3tAX}@*EJA3a(RWA7_=R
z%GTC8^A%{rj_zaf24%G}8ONTIbUy}2>sR>xqU`|^>f|89c609+y?vo&C%AnHR_w37
z4!T?&^8fiJ^z1hsM!U_Iq4<q$fL{_Qr1|7J$N-D7$y+L=kmXa6g+$fZKcbAS*eDLy
z<&;FzjcDE&!or)67wtsm=@^Yi5b4=t&l<_hFmc|uQk!%;%rGA%izYS}fCeh|gBvD*
zVOv0R^`tL=+jq*TrDHU*M~cnZofWkDtm{@$yZL1L>|M#QvZjg)jq-(gSjNtVt6YwC
z0#+AOWu{~84a{5s0Lz{5kTX(akXN2LPd2X{Gr)&T&rf^e$VF}55Z3@?ewT6D2erhc
z29i>-@HyOB3KP40rCHl!;X7cS%0}C{mT=RR(jm3NN0qLA@phnN+s&pH1FyGHU_p^b
zM)AEz2OZHHm(`3~Au?c3Yb6PFR+45pqe^BX*!aDWWv-xe(lS|N2SIB8yZkOQLZ_~k
z8|0zZ5|u=D0=8F&6w`)L(m_&N;5w0)FX-U<4)X(nGC)_(#H}#HMmN1SmWecAlJh{{
ztXNXXpUZFUs29YP&&FK|BODw<??pz$0Iakh#Y5@>tn)0P0zp<`hnqo401Np}d#bjH
z@%s!(Bpu{WmuR`I?fci#4xb;h+Aq0Vx3PvNMfx_q*ht%rW)!b*IXQv*Wl{)85twR1
zfmZfQJ0BvVs;UL_79z!>!DSwpMm{)qg$Ve#h5opC43Zph<#(0Ag%9Dyfxh{DATIJk
zi09s}k?T=yX{|@i<I{}-seCz~=|)mP<NNvSwrI<PJlD!ae%zDsMeXjHkaPWxh94SC
zR*-IgpVgsRko2h<=z4M!)d*i5-GFosvAlsSfostALwcfL{RI9!0P$WJS#*QHL`nQh
z0dq&2@7FZM2=&K-h~9!0QO}N|^#m#+&Y*86%4Y>n-Vfla8z$G>G21>_tE7=WaTfSP
z9hIRTGjFQmu8~_>i($YY)uAxeIS)(YrU8vB>!mPS>F<n2dWizJ7}m@ZvHbqt*rn=L
z)L`S95+f{rKEv^ca|r8$7=zb1@V9s5v=+ID#NcSPJcyJNv=SNN0-oz9*~_-@HcYVI
z!DRd7wFX!ENrM`jb>~9D-`1Q;0Gm(sY&2UO<-;1@+2(8jSBbV+2)JNGj+xP*21C3l
zO9Xj_el?(qs<0p$Vk0Ia*|<V%FvFdTQ#Q8z+J;rYSsJ%9ts^--uy7N|WHjX68EKL9
z%2kwI_m;3*l}^ZTvJAh*ycv4>`SpQal|Sy?q~_QHw0AFr7O}cEN+E&>miCz$sJO@T
z1&ui~I;%!BlfX=^({XOly&W4|Q($FfUyHPB=eW9v;@?_Ws_AH8c8;$lE=@rVF&kwA
zM(07oYA!v80D$`@ydKjOM^B)v0zcDL2C)`07AR%)8~}zK!i_oxvKj^6&ELEA`kO+L
zJY&=mkY|y0LC*kTcPLlXpzU{A!xHL)M^Uq!8gATn#l61-C#kEgB5h=2`M>E&6|gU#
zJ&=O9szP&&`h68ZOOn{Y$F*QQJU_#F)`SMae4n@_ZSaNF$8JU-QUY~ZpOV`wt93Wq
zem1Nw>e|DY{fVoo=}N2tTK9KWQ4iQ8+(A$5J@9bU?yBq!apR%cpqi!6fn$oxW&MLb
z-?{|amnmqr5NEi3{?xrdbhAFRh08Hmc<<_JF0Pb=4N0@KZ*@hJ?`GGU>GL!hrHsg(
z%~4{5^I>&=&g;hZb+rGu(h56$c&DK}d21qn2Q#i>_)?+8L&b6r!>yGaoslO7uh0<M
zOH^-K3DXsDwFP9b6fwuD$ce*(8Zv<BobsJw>UCr@WI2||+6m<yVdQ4>3|R&r|NaAY
z<O_Pwsj#H`H3j4fx%(#dRj>Sr@LXh&2ZsR*2JzOO#3BMSgKmxh{ft;8?zv|HjE@Yc
z{dCubNY8MK6eTQ1!?MEJwyy9K8ubUZ>(>GXmleT7?-|~X-GD>jdUyZuuLeRnPoDw4
z7e`~v?*Z+<1o0ex5ekI&ja`vea56TO{gY5TkzgqajbERnF<~kWn+7=b#XY|k7z87O
zkK=e3lYY%0nG;rj2mPS)g!T+x7ISqLA*msy&O0NQ1##YiBcP@<rj_TgK4}FBwZ2au
zkyT@h)6F@jILCxY>Xe`6?uV^*%6_3Y7rgQG*2lL*&OR=k9FnOWkurNd|L`n(OeFB_
zDsI9Yx*%b<7ZZOD_VcA(qrB=P>_uy(XD67WIrS-u4hdL|iQlAo0U0VlZ}#xop^N(K
zaO8e(v(3yyB*(Xg>)1b%UfC3;#@a^nr?SrJY(in_R8KT^m*NEszRQ#x8qT>N<)v#l
zEPUd%(ouDm)#Rg{zJ?lIg}qZTm{M;1A^%Vf6UW{Uwq9xad~DP7C2KJpazqqc?!CPA
zxXerr!p5rL-;$T>^?VOv(&68uC$7FKd^Y)v$9e|V(O;6JcN=WMW#w?==UzcZ-Cj(`
z3Zue^&Yk^*Bb@cP>)GZ?OLYXP>nYm1a|>m^KNWl4Ro)9wq4BB<6UWD^0lI6_&iys&
zZxQUGZzO}l-B8WAG|zqY!Y^^wF(WzgNT?`SvCO6Ms#Wc)w;Jz-qkPPf>P0TRpSG2v
zu!O_W=E)P2jgis;cdcnA?r{|klgqM6fw41OvjwNk)A=yWtj7t`gF8!WUBP7>d0;m@
zOUIjQyWisEWyX;j+Ac2f9G1(&aw%)|bW}gzME9nA^td0B)?|-lM8(!X+|L|@-?e-f
zpGt0&%-17_%NCCm%zPSI!CD@WH-3kpFd*1}2)S^LQm;6M|K@o(6pv!&=0D0+sqOsy
zIhWk-^T}R)CLIT0UeREd6XEwo?l3XsI4UQ2-F-v+9Vr}P4Vr%!>f6I%_}jjQV#QJK
z_uMnO+<LQ{$l2<7dGH)=<NB!B68pFBl9eTR^_yj$bx+e<{|}w>0Rb3Vdc@kSS>e)v
z7B?0R8oO4ci@r)d<QVuT;~XEOv{+5NJkOAXLkA}Mm98wy4WZePpIQ+Gg`7K{z<F7!
zH?o#7e9T!f%LRxA)}TgjVL=G6TiB}rU??$`Z@;6^V79eQmj%q3CI9ydt|hIVsp!4A
z#k>^_ULUnKW6EFl+x7P9Wz?+*<QH$?zL1TO(hcHU@8DM~ee=q_#)qnV_9o}jCR~@v
z<{y(tn#E`Lz20^>xSK1d8?JEbKN>1guWta##Gt#6xnO@nQm)`1aIf5^$Dnw=)jQK_
z5`)xH?}K>rZ<gpY9iP-zNoYu`&Xjh9f4y;T`s7>JIQldQ@7_U&9zV3H|9C!e|HDaZ
z4;xZ#LID8$(EqcOepWjAm%<{}e{|AT&h~cyTfq{bMZ$`)^uG$0w(*R1LkuvYF903D
z`|IRqN(BP*mC9j2x-g@Kv_wp%3Mg9y<1Jo+dNqwS_S+EmKVv`mW55E)u(83zC!ksE
zE(d=8U{)JW+FL!wf5=#fX`|$qSq4%mk#g9{=h?-LmAq?P6Kdd*QHLbOJ0Zr}nRPYP
zPLLkeKu!UKlQyNaFcWNTVZ|QG&T^gP6ka&y_{NfgDniDOVC1+!_<_oB3y&7gHe^k(
zc&5<Ksck_)_%8Auc$DnwNLHkbyl&n<Gg2Cu+2oHi3$>0E=Wha?{6ECs@@Ry~FLPV!
z6C|8@cz*s?cflc^7#g7u|E7mr0RMR_MY{hrSw!$3x6;Pa?*FKg3>e8;G5z<3#;Qo$
zZ89KipQ41I>q>G8xVtHUh%Jo@WV^{m5?dQYk#LyAw4d2}f&FS+8sRG0+EBV&<qpi6
z^S0laj>jf6!-Ac+?JqEV)|=)NylwRn2sSVqVH5yd!P6D6R{HJJ;^RVct!D+Razc{p
zJWS_xX9DB_^=18Av<VHWTf@@wwF^NWci<K$7HJod6Gi5?QP0Bp(>j(Td2Wq@u|R>4
z1O4QHG+oy-lOce!w}`v8s1!kE^Q<O*(L|={_e;9w3CVS)_~wrlkn5LUZG#;<WKc)r
zhDcca>Lo_E_^luUIx-WRkYj%7fxC^vSRd03s0|@1w#Tn-RY&B6u-(ijQVSs~ByEti
zJIqhCn5vTSM2T`E4q9PjUv(+{wjBNNv;7)0p5z2!_(bfu?z(xAFwo{jih055_|y#k
z2SAnScuAJ8YJN8m<(RQd)i<R!8n*%ft$1=8+_Wu}HM7Bx8AU&X50PC3w>|!(I;@?1
zquJv1!Xe;hP=&q92`&RzmU_&gT&)zBzVhj>6o~2&o{@COSWtRExKxf~*ks35(Wms>
zrFqgrT$z_t#d6rF0k`|J*1-9S;)kTGcFbVchDC|LsM-l!sY)9=uT`1d{+Exk{ga7~
z$|>$uB{kpz>u9|mefv#W_;7+L>Et;0IWxR$u!n<^T&m&X%9=+gcq5;<H<DbZHn>F`
zOjC2st)?9GgaXwR;>VvP`nao|dz)AmR+Pwe6Y%?OPEG*Gq9m4c_6!FfFgw3*uzy7A
zg_;;U4-f#r3g|ya>c96Tko?C;bux9fcXcxUKce*?wY>j{))wE1xUJE&vu~gme28B(
z#OGpD&$j*9Vv<yqD@iq0sWyN+qGn=djmeTH#|p01csq4{`?Xl@*#5z4J1g-$%)`S5
zAmKGNp|q5eqYekdnc+VVYkedW?5Q<Vty&W|BaG7O$NTeWn$GEyM%1nM1kq%**-|V{
z*%R*{WY$h^GjkK{YwvAD>pY*Dq}Gb$=_ko1wADuk7q;(U-<haSR^)6m?9p!zwWd8)
zjmF8TptD|?s1x3qtk?}~$mUF*U$-qmn43n{WW5wn4cy}<u*z3wrPZ=@ZA=}M(Zjl^
zF+(@qv~EQ9M?@WV@nelvi|$1puf*Z_deR+wQ7e2sdRI=FwtLB~8svNs7x#R~9WMK~
zUzFZ-n_zm0tah)VHP(>&<b4xWc6i?utD<U4WV`)tYfnS?GrTtwnlrxIqyUwsYBjnE
zJkK;2VtAH{>7vfre`kooH394KMOxBj)of<EMu;roIm~luOw;x>zw#!0v;j@_Z=^fW
zK?x>&vvG#4!hbys-plZPGSBTXpwLtw1?wz%(BC_0BmeG`_?=O4Bw26Ev@@6r(0+f9
z$Zk+MA^lb9>{sbOYVVHv`2>msS*L`O$cpnIgF>B2XS!W7CRLMVbG(y>e*e55ue$=E
zre?Hj;_YhXA>-f_5#iwU0QOQh$x4IZD0ad*2!CxpLq7QXyK1YgT{!TDKFQs5L4~we
ziUG}58E;Q9S5oK5o@fq0#$(_w7NMW2V}sR0iNlSw&6X~!ankBDP;5L(Obzt&u;_Qn
zh0|c438=xarBONh`qn46;8+VxzotI;Z>E~dgaL?#KM0yJ9S~R%09fFed=cUPNOz3v
zin-*nU)q|0DOE8P@Iq3!h`xGDg_TQHjy!{{VrHJLEBO7b>8TcXGem(;_UE3-TT%fJ
zI{l;cBJYcSAO!XZA)kpoPyu4#8~~Udkk+2W5BC!6mb0q!;w2EWcpcEdL*D88w3i}P
z$w31bTek>2h5GO<HrICn0Wbs4b|{_1{f?Lb4g|mgegPkQ*b}`p7cjH60&b4fRc4Tn
z5(750=|FgclB^yZjh(47VVM%qMzmE=Oxh=!>z7A(H*>aRhGXoXRB);!_#0R^@trZ)
z8K`_Acf(H5*fVh8I@!Q^S~L&g{Cgv}Z}0+E-!n|<QLSx=B1o|Gep?-x)lZ-ThIb8V
z9`>zB71F-c%)=@HP}_0ihKNVE9sZAFI{jk+Po>?I)ZP5e1JzYqY6lK`ZF~EzGzmW2
zW-DHF5>L5G;k)aj<N%DYNfF)Gw6h1KxIEo}Yrt$Fa{<C^sEOEK8UU3RXQ@aIme%9;
zuoO@!Y4PyiU@G_qO@Y;@8zX{js;yPZ{dBMLNAC5&r%pry{Cm{iEhGumd!zwBj|1;S
zInbfr2q=0JvT6vhp!?9X0HDx0F{efcQElMrz>E5_dlH_!ea$Y;e^~1+(YUb;WI+Ro
zJi|ZZ<S|0|Ua$7!Wq~PrQ>8sX7a;0bYAoO-8bm!!G)>3LgUIoAc3!_0q;CL}1{|$#
zR$vmcwC~+w+nXk?X~8>1y91o%VM+vGrk^A5Z%5l8lFUKMTRIuiSIVZ_97x@Q>R{%D
zPqxPgtS~s!Nh<euP5{JqgQ5?{yG50s7=%ENs^@h~8)yOp1}SF_C<wxm1hV{CcIU9S
zhYm6TUJ!TYSwQ$CFI^}VGQ2|yjq*u?nniFCgeA!=u!!t#>jk9dk>u1Iv|AlgP~p2I
z=&F6EXg~oY&?Am`P+F?oka-GUduJ&$c(F#+>X<+RDak+IM41F|>-T#GM*!P2r&jXD
z*=o=UpS6OD)Mx|sX;^a_zg0Ci{|MazH+#Q2kLeWAKG$<9J*YV#R(XG$lDU8{!$Oyk
zkm<%!VpWt5ZqH0U0<6hd(rlu+WfkKX+k;e1a|$ght|BI=n+3p|1t^ncm6ckv#z-*V
zi-}W>uIRL32IPn`q=S%B0+0(om(isWRXh>B^^8Cl`!nl=N=^;^&^acp$jKK`8r|QL
z^AI)zeN#xJdC{j!TwM!TR0fChfCayyOWthe48{gdP(t6@!Q+7mj=<RScP$ug2Em2Z
z5Jzz>Je}jjg;TleYu@C{7D2o7K!j5eodTx#y_$!l#uU4#=t2@Yzf=CbUoE4wf6Zw{
z%|bY1$dC(&fqIv_9oTskURnxsD~(tlScq>grnvgh@J?sjdq00(6uL8v(BB2_Hrd-E
zqVjfRC?8-g$L}o!33Yq`;Fq^=Qr)Z$exR0}My<HvCl&W1VQIQU@?Z#4>z(*Hfv(4z
zxG#}2n!)v~s|=?366EKF%m`6MF`2t9u8jp_8A{3DVQv!=kXCC9vtbIPvC%zMh6Ku@
zgv^>gb|sv7uhqJ&)}$qk=uW`=edSLlc>P)IjV@69>RJF8hWA)<Y|r8A<Q7A~Z-{x}
zK&m~|-$U#q*XRJSiS&On0MMj?uex*)3gc>4D#B2JL?WvqV#0+UQ~k4~n!rJ0=(}g<
zIEOBKqarl!BB1=BQp7b>0#6dqNjp_KL*?wa7!#q43VXDj0aF0t^=oQ1=oO&jq?O%`
zS&*Ftb_>N%ggQADW-Jz_nU%&I302u%qZN3g;4k}{P(0AI65SMeg8;6b5<Ix;gn;b<
zT!p35O3zl*fDLZEM4+N>w-!Kg1k6ekF_Ex*hX7FNkt)REiwuaIj5VRakU%ks;EI5M
zfSM&7`n5H$ZcMS6Aw&{M0&?Iq;|!-&mTN%vz+}8ll2gs=09{K-qYJ!z5|+Rqq3}yJ
z@P`+S_R%|QrfAsFWIMHM2CA^j_FnLgUW$tW_crt<xHg04-@rt-fi%lR)!<c!0B&mE
zS@bnA<P5w2$Z}4+1~GSs0nfEY-6fnx$;dq=&8aos`UZPZ(dl5{CIdqn+Mvr__sQ$|
z>;me6M3Mv92n1XUn{<xDbX5R4pCrl5%=;<lBim-P_uf3;e=XK?_8-S8U7~Nm${egE
z<rHFzyRA|eA`2fpieA>}dqQ$oWO>0O;VVG3gNdl8RA%17nb|9v>NYv*d{_pBBkwL1
z$1<(b`GY}>nSimH=z0^Fqk@1`{T)G$VSpJ-QnGLP3voJOskDOF4Xd<=#}IaMG`P6e
zD5u{oqt`Db_)~r>oc`^{vpO-=_H%!q8amP}=mj<!h3S^(jspz60k6C6)`Tj(VX$qy
zBPlhgu5F7pJYki7HaHZs-L7R`ePy~H?3Rg2+aDIvenhJSTmVL5*tB&*7xUSzUG!Gy
z40ZXy66K2|0ej$v%gCZ;)hbu<UIdz###FP|&zDGM^&ugyGB3Ba=n6&lvjP>)_DQ7H
zg`H3qsCb!%LBpu(32~qm@5gMTmkyI<$%2hLh;)k<Zb~l=djK<@;gC$r=RclB`ko(P
zY{||0zVFm<wH-462>d({*Brn{wcLC`+P#w?`4LK^)&&dz4O`NltrhxYbKD4`Ny$yH
zXyd$r50Gp-9IHvMlL906nV>VosB&Zm`V9uajtHec{%bX1TiA?Zei=OB1&#<jje_d2
zX>eV9`yv>dFEL=LMa@C1=ElZi6$s{{Pi(XtA=GEhZCb0Ma$I46k8qCYnogjhLux_6
z70HE=Br60!i@6XbQ4}RiGohP0+E=>}SL&AsQ5-sKW2j3q;NBAJggjbDOYtjGF1hRA
z!Adh@*yXlNLG1X{t}e<&M*Q0l{!y*o**Jv>x2dRxIJMU+aO*d1v@d>qV}M{DDHWT5
zl?_Yy@n~29xAvQG^UHQLZo56D8$rZOp>Lj9;ru?5NATdu<*g0j?vM1>iM1Cqr6Uj@
z)l)KHtwBZo3Y`0eC|@aBH<nVblC2TsK{{WIk}nThi>9{_v}*PBBnCllI6@oMA1=@a
zmyr$YPM{OQG*ah%K)|jWF(I6FizR>#-d0pmhPqPoW3MfuZtMluC_OciGHmR^w>aag
zXSEstO&rDKX|Fb_xM{D;Oj3Wcxo<p9FsfXiz^WrEbWlI>_Welm4U!%H3C&IJD<Tdh
z^COt3CcGfwM@qcaq-9GA1Hzl%A361rHNQ1Y(T)eBjDYNJ^(MkR=)!%=>=#I&t-BR>
zY`GyukWq%3Ey&)%Gsh3<hFHLw&|(8pP1ucG+0AguInW;~00=ft{4NxBdW^7yq`_&^
zSgH++%7=LAqZ-?}G2p52_HJm$ud-!(+OA2=1Eni(h(QG>j%KQ><$?2}euK$%an1@k
z0S{FwXIbBlBG$LiFJZ2WLc<UX^-PLHZ)OOP5YDQDV{dy(A80|;1BFNeuT9iP6*Mw?
zvaaQJkl`iQi8vDD46D?fl78`g$_lK$0i>|ar9N+^m|lAu{Z>6o^59WXuLr>leI!1F
z5!jAMgeB|ORn-C~H#q?S@<a%|FX>s@Snat#L2kThJW#Xi%2L&5yt2DRfvHW#M2K0J
zzb2goCwS2`2v`hC8W3GlS#MMYq=0icYXruXYsHzOH`uQ5*pcQU=>FW<fRqOLoCN?f
z%(c}kq`usjnu|NQ>Lj0h1)fyZ+#R@vKbH-AP74ToyZw2-$US2BA}`Y)9fP7yCtEC8
zy${3|INz^sE%?0xf}@);;DDm4j8H6mh3L7lMw|uzhnGSM&R7L3`Th3R)w(C1H)4$4
z6>Giuk3449xs3%Fs`&J+1sh7coXhfAbpAptNWE8wa92|A)Ss$mcTH@9-C(4_4)TbQ
zZHpSrfXMmrDOL2?#W*BRF;YfFFo#3BT2&vmF{V+FtF})svY9{4cLFk7mdK%p0&EbK
zACn@pTxh`Eg>{J9l~^eHm7g{B)(TdQX5v`kH59<$wcb|Ls0}PG9*hf;e~1%uV~chJ
ziL+W$Ej@4m&r<pymeNd>Gsm3_RYDt*X)lM3oz`kwnry}qMToCB1IPvnwvYukNT;=m
zvGm_mcc*cmn5nqZ&C=3j<GvkWM^XICEKa65KVjg)tAM7}KXTgr^_MH)Q@9r5jjMCU
z9lmEJjil%Rb{P+p^$FF91Yu85#ZJNM2FB^+iVx)>)TDO-l{LZ@GVJ%OZMUi5NKoST
zDy1O`sfVzAXD#>jIv!{=8c`keZt=Urn-urR1y1FWdQXG62XU7dmE4mB6}jw^0VVY=
zE(cdKaLF#ujsmiJqH7+^@9IX-aSH{GA};sDMvu;JO|Hl)Y3Cb9K6+4H32-J?wz}?k
zAa&XSi^LW4FB77~^sk&1LnU`#NAXdO?m@r}=@z{^R4c+ZllOCxhkvx|NagcvNPw78
zq)WFy<51JLmA2a}kqJ1Kl#l`zSuCscB5{aS_mk|X3=iAP#*`BKigut?SSg3DYw;LR
zUfCSAZh$iDn;UNjp~p14rNC=C|432v7T<k}LmQh3xEAu6W!w$<Q8a9<z+Sj=#so$i
zOwTYTfLy~sSoI9$wXcb1)Aj&I=85XVWw#H?$#F)g)s;`?#{PEg7*<v=nGE${Si3jX
zYyH!#&^#?$LBj2nnU2xuKxJXBQwCU3sKV!!YvKwVTxz5(31@Xvy?|>Q9`Hgngd<@4
zUS;p_3Y3O$I|?I%FkcHAncJSZ;o&tNxKdwu(l{8R;p$(vtG^u0AnGEUARXz+Kx5-d
z#J=Los8ee{g{kowxkHVf0;~X2;NwHdh&<2gzliHTV8!eOCfRZYkitLC_{K78PTMvh
zLwv-l{c5rq;(0?51lq7gmmT*ry4G@Ngc9N9-9haf(5zi(XqO98-We)Yy;_{dVT`}9
z^7`75zqinMTQQ_xCB!*)%)iWEV=t24-S41c-9)@4=8Y6#OR1Hlaomc?^~Idk9PNDS
zM2yjl=Rzi+9kk0kh&LV+y?F=oj2cp~b<uE%9LOoI1JrpMK;{ayFO!tPkifB`C`!-{
z7|$WmzT|yMRRD1YhNtNBV*PLsL+Go+kHdZpw?~pZXPVix9k5;+{g9iv?I1}6cn;L0
zatA;O)?*HF-2V{c0+rxUzX!P3rVp<@IS+%g*bgQLO$ZH`U>oME#K+J9`|}hGPUOrH
zJ}guara9#3>B~TPOBe0BkwW=>r}<@Z>xb7&<iXRpY#9OFW~-}aSGR*Bm4}=3g1NyO
z7(8)+AS;NQJ0f3T@RB2_rz|Y!EMto@NUSWP4bDo-Y<VPdYC?joI}SxMEv*wQREX6e
zFewP+aV<^XxNR2sG;8PLZ9cughdr*#W!Fx)UK(>Z-qepcF<(G@u@hJZxl+Ic<6>0B
zu<RQhGl<19zUwX>T6{9(M5YQ4WbLKV-4D{Y{F|CPaWLmAy_;opni4of2e<?ICA!7D
z!Xz0tZ8ormnagnL)kLKp#@kfmY#Dpd0>Cu#ENnS}<L4HYH-g0J8F4EuNkNEvR_wz=
z-SAzaEDmYNsB%Y;VQ_QzZDQSte1H>)t0wv7ix8X!)Q+~eb;Bh{A!Jsy#E8!F^weOx
zCSYc~ELf(T!*KZs_NQDY`=N6XlyGVX9o`=gP<#vFL1pB!Y7&*{?YUF2`F@>ffB|yv
z3P<=lE5XqcR}V}pY5?SFSFKg(H5dUseEm<2Zz-0W1G*%bQldj+e`D<emrgl2jLsRT
z@LpiA!Y>CK;o(|*eCnhSAu!S@UmHR`T-X*yN+GJpqZc%|p7|prRp7z{n+6H&m7a=Y
zw8#XY;}*#cw!8sO0SEgPZYKSWk<9M6f%cE_{?)m8*r;LJLKqK`)94xbK;)WYPK|~K
zZYrbtnF<wTxxhGx)(OHx0${9|9myM4V}ilZT#C*|4bu@SV8pp0lw<9lDu+*F0vbvl
zvHm2dVS{C%gsaK4selzmFLaco=1P)DG^w_+<}X-<l@>W-1<5xmlrZD?uFkTu!_=*d
zPN}o!pk2(|G$+{dF2&;nl%EKd?t6CDSTgDq^@jcy<$H?_8nD#fk84t!7T$m`(YrRt
zzK;j@T~d9f6n7M&g5%)Xufqm8|5G0f-P1ovDLQ{>))dqfBO!9u1fuIN1jAkfS#bJD
zIzsxx?q`sWze)UGv8W?ZgbF1XNk-5viU-OiH6_kt$F(CZea9Nh2+{~NKVWwUN&mEg
zQE0miD|j`sRJK;mHkw+KMI+EjIjYbNVLCLiMPkaqEeWZwD~8{S?Hni~QE@|_+zufn
z%Nt7?HsH2<ymxN3wIC(QEH>lNX`ti&E+|WmF?H7_lpf-(|K)YU2zCq~nU-W6eLm^Y
z0XHFyz;0lzdY{i=L3l$1ZX;pg#$oi?8BY`T(^Go-Aa-Y&o#c`M$GvKwN+k*ut<+w}
zupd4>wgJDSRz(q8a=|klosx{l@1Fab7o%bj3q3rG=O%)7eK68uTzcb)K^Au^73&b)
z7A3VtSsBv!$_aS{Q*B;FAmN*B==m!_l*B6x3bY3Zy7e^(?TWUR5ET|aV#eEdO9wIo
zC_3&n;$De2!XV-&Hy=F#dZw}k=LN2}UH$E?iVByax|YS2=X&#ND1RiZ$54$6F}G<~
z3hG4Q+LFm+Z__RcH+yS_6B`Umw(!~g@IadVv#bl5D1_kh_sUL+Cw79}CuA7a)Sw3z
z!vpy9c;w2M>K*SgVgrbo;>9xaacT&50HI&c9qPK|PxgcyzI@q2>2D6aozFO`%4p8-
zTb0{DW=`CbrC+<N@x06D*_~ur$lPOLfMv%vIHy(2Z07t4-3aRm(Oi9*DgFrQ8c<!1
zA!U`qSSI^~i_{pvDdOZHChwJ$$z+zNSce)WTohr!jDH7S;XDJI55^GI5qfUG0e1^f
zN5$i%KUss2bLoM)M;wuX!?%Hk$Jcg{q)(5WsSS0i)D_x5E~JFCO?k{q29*3<J7%8Y
zj@}U~uZy;Zd`xR_297ma**J{qD?;u%F>vLxwi76CvZmLF5#aTFfYJ7f!T;v4NXmr3
zxz+r>$UZziI9h6l9baC0)xN;|e}26rGC%iX@tCqIUEp7xayudG(gZ3dJ3k6n!y-_X
z!braoq1J}Wt!hh&lQ|@(P`eXq+2LbOOIl8Me5Whn-S)QC09f;li_-4XH5lF9M81aw
z9SL+$;`K7Yhb+ClEGR4d4xyw#S&wMs$275}bbr>^!d)Xn$TRNM*trBR2Z9);s<7&A
znIk&IeeF!&SiXyCf(XN>JT@wH9(FCYRx_R8q`NC?K;N23RCu!@;a;s;wv`L@CpXyz
zN84&k^@wJX&SuCMh^ZSXZ?n~@IuR72#7vGOGr~dioNWa}%14zH;6}-&>7Zz>^Ap$C
zNzdS|*$F^rE9rl?9+yUSIXN8lej*6M_;$xr>keMJLbD+y3I(^_TXEeevGep9s?H($
zWX~~Kq#caE!T4i2CmRXsan3NxGxcq!lXCYCz~fWftaVstW+O87h<IaJ0vHiPr*J6w
zci<KoYWWK*oCNqW2!3JWApf&`>d#!FvioklMf@l(3e5Fj1G{aW7V}n-I@J7c;R(}1
zU}gP&%ApTWb$^0s#H^6VVCvkbcXKPr7_AgyF}PS{(>K4moG!#F3{|ZrONLd4SC^ps
z0JE=if1hukP}EL$Qm113T^&C?5_SAvcRziDKYF^oeV;yWG$xZ78>=TD{-&!J<5)+8
zK=<og<dYj|aBWSVHq_WnX{UKS*GIkwJT^)M(k*o9cr#a-TSDQ04wc?b2&NxF(gJT)
zlM1}FE}#)>0>1(&9N}^5mi3ZVLt-7~YHEi=5G#?eG|+`Mv_VXuDL&x7*vVOE_fz@Z
z)#?;ad$v@)j=k3NE8A<v1@->0WO<q;bJngq7^X|x38E5L-*d2(O+k5DBQwj%YyZH@
z818{islXIF&s>Mzvz@QXw_JZNTf>*07iWFBRyqe$BsUeuHs*m)uXE~zpFQCrbBH?f
z7wO3Dp2gb~)qf#3%a|7YLEC2+%~_5feJgN_$4MkXPGKf`Gf?iLXMFB!XmB7KO~x@u
z%!0=brcLw|e+P?2&h=PsI=6B%GA<)0VH1Xp@|dzqNm^dd;R?>J6vw?n5yh1zg3Wo)
zvrtm8^KvZ#b_KgNs6=5xjmTMV7%vpj)1}WwYn9kZR?wlwagy@HN}Qh{c#+m_+OkGE
zcbSG9k<VE+Jf}?X6OzwwGWeS4@yUa_8QTEAtLthf#Gao?SsH^J^WJ|nR0{E_6$XB~
z!)|J(!!U*JSs<_aLDod$PQOZN6_gL881l6yi!`19#{>3LtF?BBK_=s7rh;i6+xP9c
zC>!D|G!8*4Q))B}-`xnRM!zZpGR3oqG&tpQM-{YF<1vO_>f~{nt$cZ-S6`bmYo2tJ
z&?@&7B53C<TexuANJY0YHl9>w57}Y%m(jmaCOr2D&oUH&wTcY(Rg=>h$z=2>!H!!*
z&55#W|0SSKSUTwDB8uB-fOTTApDYc%)~VLIWiv12k({usPVy1{OH^hUTl?mr;3bM&
zWngZD%ed&AjjcObeLkHQi2LNoq>XhEa>g?cD7D-zDzgj%d^4*%9!)f>C4l+xz66ey
zw^Ig6ylY2F)nlco{wmzq`Vow46~l1^n(ai;+Fn6BYe5#%Q%4;O{Hdqe3;PZ$QtZZ^
z?Z9;R&#V{|idoz&M|3ua-b{nO9YA1Z;XWD7zDBN?3>*qx!wWuF_mrciyMhOW%qjvg
zldOM27gSs75lTR9+;+XSrSn0Jn9#?S`-gIa?(q9vnt0W$>=oZ53W{+J{VWaVH_n$s
zUX&2b^KK+n&8*$$g>};h79;CfD_i4s)xz8UD*b`Ng2e31YgnE*+fj@9b&guOV1lvx
z&9i}8XliF^&Dj0Q+kyvfRzsbzyd&u7=FxP@k5G@(mYV@N-N7`vQTxcu5`b5I@RSS%
zxV25r7R2d!0ggRhaYdXtpsNz&AS9NKs{YzSzB|0*OqozOD@*%k){;G$6~e<fOdUow
z>uQ<IpCd3%i!`-Ib3ghV@__>j@{GvqQsu5b9?Yn)kLg>x&L<zyZR^F`JY@{b0(@wz
zp_jT^hO={bjhy3nGPY$B3Tn9nuVu2<B*$Ai1y@aBjhQp5G7XLdDvn>Es}5jC8xuao
z%Y5f4vOfWS#GB|MqLzPH!s?5sTpOo1#^H&v9TiLyeFQ)D>v-NbLYp{s^EUP%LeUgV
zmkits9&>4;Mm?g!9()gHeDe-kW8JGb!%N=~X|3`u)Zp4OJ%JS9S!6K5?<8fF@*rFq
z+-MBlu=iAiyHm$Q<bk)x*=Rr4`Dlz2xrL>#BkxwvHqH?bS%j3__DtzET%ehJ3478L
zRk}e)n>wZW1O2G1H2I4q!r>jt;b+-gya1Arx03w4SK%UBee1J2OiTmFe2DF*bO#_y
zAa39tzEga!K6;uD=0iJ$w{@;ydU=)Ve`0#sPJ88(wVHDZ)Bwa0rf|$$un*V8D61qV
zEUP&WX>sfkhP+>fKw>Dt$X&DmD8(^)(5$PR0n?#v|5jBq!nlHUJewt_-w=%}HYY%Y
zurDqdos*jIT$*#G<~KGh!<bZTskGXq#S<T+Ead38Ses7*sFdC1fxC1KrxVvG%oBB%
z-AACbPY@dMK*Xd5R-H7nhyPZ1!?@5jzhuUM9GjAcmq}H<TcH$^lp!u-t{Ke5_mVr)
zV~E|FWhHAQjyN~dc_vmewxy4@#93D{j6W3yzwpiGoW&~OSnD~sKZ9nl$OLS?g2TuG
z6@O(8b^tQ(@EG7o_^tb7q>gbIHZlX*m+%HI624b9`+ab2!V9j%syXg_h_$A=6j#E}
zc0rykWy@s#sjNf^d%lFD2x3pMLa~NtYrQ^AbXE2b{oJ2Rb#zdA{|U7-x#Ir0g;9Os
z{S+^k&UXtN$$2%l{v>Q1C0->E)Ytld=sE`;QJ^l%7GBx5U)i>8+qP}nwr$(CZQFKL
zznM%j-JN`Y;U+id=AOOQwz)8;wc_mCsA{ua^CRtUz+)MEJ_`Oh6B5Z2A6ts{4lc%`
z(6CyTpRBq~iwxAW8BfWImXIiJ;<J|bsFY@wxpUfOVriMk1$scksCnzjCt5w{I9T%8
zvts3i1&aM-KFEXF&-*7_96zqe!RbtKw&8w{q;pag=FSc4_Js;AxMNtwe98M}W<P=d
zv^MPigQV%U73x>zw3xK+%|9cpf7;xJUfL3m3p1!M&WL6&Lc!IIGu#fyTVFl^QPHUx
z9^tU#PGVZ1xauI%Cu_dn=XoovMRr}I2u}6PFbn+*3UmJY5`sv1p^=<lKsNsCEI@om
zDWGH6&Qi{fv_MAsWXZ<*AZ1HzCm^&RW$+%Wwu)hIZa@SK62V8}x2@f^)08)Q_5vUU
zxIw*Y12H{ui5Py?RNT{??b34fX}{qYL%7<M0(Lr5o8J72cZk96+x=b2SI=Jjb7)j4
z*pQ__VcFaJuUNHvg#!SUmOdGzoU3o$gMte}A{wn8PqeT+_)<3gD{GBGftWX`8=?Lu
z*xIW<<HNM|Iojs%9iAWOiZV}Wp<r=qlfwX0dA%&I6PW9fGvGCib(^&GWglD~=N#0|
zWhqyA?I#NR6T)JXcicH$tMX@ylrbORlTDsOclo0f;6`lu$x+bBA^%oXSaGOACATMo
zQNT+>`#x{gf-Y%?nkFYinzW~4G1A3TD*UB1qAOgvKPRQxRpR)v6tWmXWo>2Ox@DP)
zy4^)%$^j~l*=vMxHJfnBrrxcz!{~1(zLJuIKd+v(MjtgL02O<-42oI%ivUv~Gs$75
zk$hkIOJAgt<t4J1np41b`7BEqyRF~nPDCfNV^X8_W!kddwH*m|#Ju!UiH>K<pU;6X
zrV6n?`9<ZOFrU$#7KY0M?{_}?S@f$PeZzy<kWVF;^dA}O>e!Um;}oW5<b%OgpFM!l
zb^8evR^-N%!w`-0^BfYDuv`w22Q6Ap->Nn!LG$!ki45KyxbjTGHd#&_ifCRpZ53sr
zr3f{OKEwGfEyNUBoSM2$FHuK^bs$k=M6u(Qo;2n3u51r~-g@wE!)WRH<y*5}I}K*C
z??~Yccs#V(cS>{&3)>UFr`wIS%KT0MnmSU|^I+EPhM!_Qie*0oWpsOrJHVT<PV!-j
zySbQ`A3aZ=rj)znx+g6po!2eQA6m8SWPtR$INq6b+zqr}ODP@TsRCy_-)}e-y9)9x
zs2j+dDqgYPmG>Z0gjrE`vI6c<Qabt&<E3)WJURiVvW{n(=Ww_+Pel=m*UJOILhaB}
z@?p46Va`azN>oT_QX?BVw~jC|1P1vNqp&CzLcbe0HbNg-$nYdmZRrYtM-2vz{kIcS
zsSqTSV96llmbGqLS_mck{opLj9C`0f28KVEt!%!1wwll!W|SM1Un66z`cfbi%-e&~
zr5{`@xL4K4SZBYDY^ee5@pBrg@kw(VyYbvTsS5t4*Pu#@f>HKKh$5<g@sv`{fb?O`
zwiYvZc4$$(=8xVsU8>w3?E69z_3U}bkEC1-lp(uJ42oZz>|1vAiIlzkBnl13CTFVd
zC+oaWH!74;ArlhIZ{z_m@JPl!eC^m!P-u%)M3c*IhfH|Hq_)CIDowGh+15Z?w4j#K
z?A9i@%BCg0JoSsj8fcU>>|U(@0z(<B)Qn-#dU5HCbaZSRWSRJOkcZj`()A|s0?%8G
zm5;Q{1<5q?j@6?J6a&dJ;p>O@U6=|mOxfBS#yD9>2-%rN7s!A8L>m$>aZRyOe^g?W
zH`ofn1(xLi-K6McaJt+gw%N>u2eP02@Xz}m?+JwYCDj^aGoyD?{3g>p+=gz_xT^QW
zv#|MC82{!FxUX81%+Vt1Zmv>TAx4tmXY<q9s&v5W9;t}D+)#~OWnQM82yE7MW5y_g
zrnib6h$7>%mk$Qa8|{n<G)?SlQ@{+di`zVt3as4sAAd0cF=8(8O`ZqOEw=n^9zmXX
zzVTr#r4*9o2b+lvG^mtiqog^POh~}mD$ZZ7OyV^)5zwe)EPH>&2PmVtB$KvK_toU~
z@_r*-rm>q;g>Q7~Bzp?*B)Y~x&L^j=iJ`#4oH!?nr)!REVhM}>*kYD2h~)N<DYeF=
zAm2LzijKbZ=vM0zq0LdZG<N<{qYc^f^8!L01+U+U?6CKo^+c{xL~`9=5+X(Z+qNz6
zy5MPtVIc#Lom<m(vA%z-wyoyC$db|xv-*l2XkwEgV>HK?-oq7nvK>R%Z0;;6Y_SJG
z=ITUh!M<i^Tx2U0>)x?VVFFi@;8Jdwn!qg`7+D?&6MC?r1H~c&N*(<uvU>SvncqaR
z8r>k(-RVY=Z}p4cS1%KXC4m75!K%AFIzWIzS*56hboO7+X)hW*D}=6f*U&ns3^w*X
z5y!DoNN}5tRx8EZt*zG`RhU6ZNeVbgJ0-(+sU&GmBX2Id@6CF~0Sxgj);iF3I`eCn
zFkO86;gzIvj4V#k^jy6YyEDMhu7I$#c>+mHNQX0ig^7K1<pRw{x&4@ZdpV$6&<Vxt
zriNfdBXMt0+0Q0u^hSIzx5z?%&nZi&<g8+guYrbNwj1v6!;@!n5Yl8vDsF5w3ycs+
z6h_ZY87&lav~DS2-<(v-<YbWg+Yj2BgumT}ph?&5(nR%<j?G$X=<*E0nPw1U=|xKg
z05iaN7(_H)6W=RX47!Ya0Tvj|$Zd@V%bTF+N467Oll--E8yAym1Ix;9IT6L_SkMa<
z{S|DpB7{MX&GZ5FM}c{T)jG?==}~0ac=xg-;=ZgBVSdXN_1T{DsA2IdFP3HJLchVN
zx<h4_23PWpKDcGU8cF$P-<{#2w}4*wYu1nfh#>yUMijd>Id2=Oo->pJ*-*oPhMlOI
zSri7y=odYJ&#BqJ-3@7<i%LX`UyX!Ii>8hF<GtBMSmhn@@-ZmOj4tyBAC2|X(r{0|
zlg|n%>bPexBa-YfDUw^51Vc-F{n;p!(0tF+>LDg7<4Qx>C_fIx8459@iOC_~I|h<L
zT)IsdBxPM!3i`>QQ>guZk1~7O;>(+@No@O;gtB|1mO;lav9KV%(`(2Ea7>F;Vi)3O
z)m+NsDh9`({dN<gZosaIKT{gtFF{Xf$##f{Ku~ZXO`sATlLb>v48Dro=w`7ofu(jc
zU#gV|=G?4P7|Z8*ys#*~f<bKJ`_&kY<4GQOI}J|g%xZ-_?IdAYp6j0?h{d6D60!LT
z>YZ{;yT=U@Ad{s}%<K{4EhFDc!SDy1w>OvyS=?O42`OFJtbyyBq5=9P`L3_0%SvQ!
z?4VWh7MYDP?Hd-~Lr~@J96QI^S$UmC!Az*buUm-;rAFKukiFJ97RlYa%jUTZu208n
zeO8vAfv}_r1)_3xabj}hVAmMlG^08h(aQeESY~+xbT2LzCA?wA`wAbN62(OtN*iO@
z)M(gis40Jz6%-ih8^1^bPVqX!#10?-jxk~|!q4XT)PzdHSQopCVY@ReF>HIu2Vj(1
zR}U#^?8nfz1oDvdI_SF(F;ks$v7;ltVV2UFheNq6rgRADsX1wN{jSBB2<0!r%uk72
zmOJ{SYVsLc^g-mD&(b)lXkf$EFs~+@wW1ph36Osw4Vk@At}}9y>Aa|F;+;Ay@qqZA
zyXFg+mLxSmEKwhNDeOwV(n?&oCj(2dCEOy5e)-(a2f&r=LU<NR;<OkasR{UY4M;R7
z^zto;gD;!u78ePkd^rJ{vLe>OKR$Kp>5iM&B0|!QO0o2YHxBB!uZoM0QL=Zyo|Vmz
zR@grkZK~)JF*DJY;zM?LjH%U6wz=BYAD5&ZLDHG}(Qgn3O17xV7+8lADGp%h<`nl8
z%e4|(&-ki*pOk0PX8t&LZXDVb@5kdJ8RUna)fY5u2K7^u*V+_yt`3RSh(4@<u<_VK
z_hBygD4eR5MF`9-IO~vcBWUCCzW{D~qL<L`EOqJsOhHmp0Sw{8fAqQJPyxYI)J%~$
zr8wD>?PhNueAXV4xZAI<bWRkM{86@upWF|;e$vX(FLgrv1LpAi_MX!Gnn4HFt|YG9
zbqB$k+`;Z*HO3r8QuNm>1F5V2z$rUdlpfUy9bor6&5~c1IYafm+GQfnVRB0m=$#Ee
zIC}nN?)$4t%G^rCd4Bat^2Ny!f?N&Eu3wXFO9W!muIpy=AvMd%xKCc1JjLkl_*0%1
zpknO#x9uF^ej&-Q^}5L1*>Lz$WQ+YQ9lc|2pvF-{iuiZOB)NebTT)E{C=xNYZ73z>
z7xKWRani03037hFF`qs3YI*!xM!jjjv%o5Wv%Jn;RiX5pJ%|MLbG>wmb}4fl%*!#0
zDpd4l-soFHptk*J4ZEe2;B^np?$@Rc^WQUNXJAXzO=$=9?v#d;1~D@%*mfzJP_wUw
zf5+^Cr~hCp5WA@H!iMLLqx+C?gFj3p)k;|qiq6OTfk|SvVbj^K4(LXEEGrFdn60v!
zk|GINp~m0gw16<c{R1<Nfyk;eZ@2@m&2|``a|m6rzmX*Al8K`>e`xi3A0V<fm8bpM
zzVH1Mov<}zuky}&r$(3#_+GKJQ67q6T{2IU5;BO?YSj><Wm44RLWu%(uMBpOw^K3n
zJ6;$`sGRc^)rQY+YEG{_E|xXk6sx^M6EI@T7aNfNEG3t#bs0Wh6JLT(xgYChCz8km
zT;+trN_w?=NPLe=A0?v_I{q0S$2cRV_Nk0j!Tn#-G6wnZ4^zw3Np@01cS>c8j9x(A
zRa$v3byz#Nn{3IkN#Gsj5rtPOvY8^65cI0r_>ys^cTd6XeDOPg6ME>Z$lBzPyN6cE
z;2;jJA?Q{ZN`e6=4S|TidPxapK4I##43kDy;Q`qnMXC0eBI&(Rb$m|y3lc4!2lk?N
zGxQETUKfUAglqs%qFc(1nfNU?{|ZK`KxY@UjJ0a{Wf=Z#$Km~2s-s6?`3n`kwp_MO
zeaaLH3V2&dXl6dOCgj`TX2D}#AcL>0^rqza)`T#u_~Vls=5_zd8-VBzaz{6iF;rns
z>^Qmno!zjbTP6BW8S`R|S>5euxkdF#uO0Q`8>T>^BnpXuGGmXH`k{JaR#X)dy3X^t
zFNuULmlffkxnxkA`<Ry?SD}1P0rWUXHM(;xHG#rK)rG>JfaX5q<m&PwaYsty`BVjX
zl5FRy<A{r5ZVO_}&aenza)C)6l<i_YkiAh1k$?W#0=7PP<tVu+jLfu;L_j!Q^BqWq
zf!E!yXWHM_THp8I|C7_tKVgSt`3L4?p8WTmzR3R~N=W}>PT$c<-_qF3*2>7(;XmuQ
zhW;N|Li{pno~*|2aL5ARbxSG7Bk99u^RltyaAkzUX<y+GI7Sdm2tfxxHY{;W%Kic4
zxsl0}g6o&^FY=p>1q05wn3j{{|NHZIDE+aapt#(z;Z&kls=FYhiMLk##FRIz5o<uE
z{=28C=&^CVoG871Nc3jx;?<{ITh$X1_vQdEqKcQN`7CSUXltvA`R8e3wSUyOm!{|8
zqx00kAziszRpjy9^sQmS^B&}K^4fBLTSQ)((Y~;0>8&N3M!3|G--WuGRQ6yarD<-0
z9q|sIXHtbmsrqa3ONFwwNR^U<H%6$%Vn;(!V?Byri)(8J??9!Ikg{19>(Vlr`d<e$
zOtjoKhM{BeJE1TgjA3wjvOki#yK;OEgrOt^`~p^`U-ppjDHYcTYhUw{u|IdM1f+>g
zOReO;*I}37%?d@O#g_}F`HnG<zY^C_b$Jv{E^dFPKB7l_CHji&rY*593K&bE{jeWs
zI8+NoZ9K|4wV9#Bf>^;zl*aKJhWWpf;iGW$N<K0=ytkKyTCjNpN|K>U)=?yXm@%3B
zb6_>=kFdwhS#pP)&3$4f3;u9`F$dl7Dr$62zp-l%Wd!z)Vc#TL(H6C+hIHq!C{}!0
zQ!F)(nY4D;8KJrA+pLG>eRKxCQ>@(a1Z1om*G5$Rt!duQuS{qn5VI}CN6fP1;pbbF
zV1Xm2OBt=Zaa~zsz=L%H#8_k+u0|<zsDU!elr6bG#c?Vv$P)ep8zVLwybtB=hl;OC
zxdLY<Kv4~$sdzES&tvDNRPPp+JWtrcc~_Di5@VV4PUFLrz5K)=I3o}11>@^9MjE8N
z0itRiIOxnRpU3Y}TF2A74|%mu@!9^ES#BYn&H?f)fCgXIr;cw_x5};SZ%<;=Od5t2
z6mH-`Y!lFH2>n4_@~5sPMUG>0iueLKI1Yx6TaVU8XK0#Y-UJa;MC_)$&r5^Xh2{lc
zpqWRx4Y>izT)haWL>oFgT1Xq7Ts!XvyYkV4PaA%aDE59Uz%Ev+`Yn8#)FG2^mYvK0
z^KOY8goAFV-|>b+vkf)4OTMfwjVb0Q6}IjBWjQp7+gS2R6t6E1wz$!oTCrN;nwB=$
z*sfJZ#!x~NLmz6YF&K|zYI)O^<|H{D+7%yL3#CGTyu3}gVd;;XZa~_^_j1<3X_@3z
z*rU%YUOHQHMfS46YJ0loD0P6mj);LY9i)wtJ5!_9bLDLo#&B5VL&FIGQdFFARW@DO
zT`(97RKsl^Wf3c5P(>gjati#r=I!kyu=hY=ZE!@s_n~4Eq8DtUQ#gb@v~{i6Z5Bte
z-)2emU>+9M6Eq{L2T<D44yuoE5slDKSO^WyJ$4&`jbB=GwI4~`np0bb$L9rhtU)TE
z0RS7l&$A5Q=lzrO*^al~3ic)kh^qtH`s+P&Yen8}Xnv8!a0V6q-RtY4zW_ViuYcR3
zvpwB4oM=LetWtvNr={eaWfI7+L}3}H_qSpYmIE|ntm(zACP;ZO-tM#5j)5&s820%e
zLQ!>7cM<7mC|Lp!$r9ogR{Kvw77?=?gHp$Se9Xe3NgKUva}*ugIAB|tN|8SJ5vX<j
z5Nbe^KxMKgn~r0T9#s%yTJ`DZ6`NjD<+MU%5?MJ0S%Deo8Wr(udBmsFZx`J@x-&Bi
zco|Ks-YvOfGI+`FC@>WraXx_4Jh%DTzT1BM=3G~>#U6Hxu6R`8_#iFJrR1ETFXP_t
zFPraT>u3O8g-C+F=O>g+-*}uVFItcGsbsvfv770MZ2jqD3Q&S;+*WxG_RCMepx8jB
zEttUpqg+k(ic*sU;Gy}+<Z_Oh9(ct&2VqLHchTwGh2mNd{lC3Olke3!4wG3hB*zm>
z(xuAGcU)1!-|d4voiS{Dq<L6zEIA)|bGaQY%-@rRxwt$Q?@Um*oL)>!w>VQnjrGA*
zmmt*l$YsFHG~-l%D~#9_|E-8Sanq@d<0qW3b``~|zBMUVHn@8wFgVXeEYwLpr|RpG
zeq+-adi|^x92(+IW#?GQm{8yMY@>;K_Z!f8ux4g?z90Xu@v6lY!S3fD7B+?S-$%|>
z)Bl7R|Ffj(-^g(?x3&4t<K{~F|8tDj-s3iZ#Z%V0dk5x2`IRXN!4j8=01E^8PFUE*
zT}((D8G;7@VBkW8gIKw@47~_A$<In`=fwH6FMypY6t~}iKmK+Pr<g|4@{7zm#X6PU
z{Ke3Jxms^*rTx8DRe!m(R(uULU3D%@u}*ar)^48dD4<-f{U!K(=3G|#Xswu7shHL|
z3iVP>5`J}d&sV9ixb59Z^8UOWp3}H1zARzegKImO6fnN8FvZ*H;cc2k)2)?UrlD1C
ztz50xV0qUstq@k(E4^#XRqC;AMC^&}?V()K_;*9v6_-7dSts~a`wHNCtCRvITO+TQ
zt1CF(epB5`A-`^vSNAl&GB4(qE`LfC)pe^Iy8@JzUs^7Z`S?oBIt!H6YszkxSUPVR
z)vjciv9!Qn<b+*!TeB%7zd*h)ezt+5nl_}horRatD##-*aehz$bjn+T;kXjbEI*YG
zKzqQ*GFm*}iaSFEDf~1Kt?w!U2f)zARDuHvN$cM7$89?fK;a%C>s-1OhdXLpuJddE
z!Q=yg7d`DGvsL>N`yqNDZ)7wfk)Ny|^*8pF)fFE%J(B>gcjZ?n`=^jRmGyaWcT~K{
zk{z*^u&^L#c`dp)JT-5u!5R0(07$2Ihp;qIWh|XQX$V2AZ=IpJEZUt4mtE^d?&~r0
z%c@;>n;rWgd%d@>)d8DeS6k%;%IhM{0Ou|{<u@+6zj98#Yo|Cn2m@r{HsWcZLNv2}
zdJ#01aMJSDomD$dVxpNR`)Gt@%1Rcw&KDl4C~lg{F5yROT$6jv%`X#-Y-a1mmtDoK
zNypzJS-t#s`|L}fp}BhsHsNMI6)SZ|gr5Z&us^B?!QcfUn%(~hxcKhg$~~;k13o_8
zlT}W>Ef|6Ba@&s<YBP|LZF^ZnHh$nT8{{ASJK!a!*Sp0UrXwb>{r7!2povP}t>tN$
zgHKm(9;lA#>J4DRO|RMpU!aAWrPX4=(FA)xHFhRQ`>EE$yH+r^Nr!jBTAN3eesT|Q
zVrO;W_7~-z063LRgUW_R3q{~Dm_2xwQ7kJKcDp|(=u^6H>jXL%DDoMF{b78KsQ9xR
z9aNmmU@&)>wU^z55uPAJjNoN!kKg-ptlGN$y{1=nmA7#X2-8iI>dC3P@!(UNg7g5P
z!dwd=zGIoNWM<{^y#N<hj2-T8vf$Z{J|$s!GS_}Z@P=WfHEYPPHi3;kjnk@OJ#g%M
zCxY7W_1*q>d%rs>p}4+YyRL6=8h`sQ5Zk&!Lf3Br<(^9eE&Ob1lMQ8rq@{1RZ+4At
zE0wcZE!{dEQ=ryXC<U?Hs)k^p>H&EO;dSqTv1@?b7pYm@5Y;GXfja_cfnZQpA;-u@
zGmHO`!}zIxfZFJD1B{h`!|1sX<u;bIy@8KPo(w_U|C!Wy;duL_wY0McEL8FLZKzj`
zcIpLdfM$zC<z`oyaT4l&F=UqkyPe2L;_c%s0Hz8E*_WrfBGZZsM&|J;&W@S!3pn(M
zy%Q0VUDv7k`piHc$i2O2bj7#Kyo}K<RFXqvzau%{27k-Y+o`#xVeQ(OO~dExmlquk
zU~6U9{LaiGu&A>im#2_IWu@zwjGk$qR2x)ZDDk_0i@`!VMpcvOM+tq1=j!^f{&A%Z
z%U0Mmk~{aO9YMnP&i$nqCb@$R^a9xDZ$cIb!fPpM1VKVg3y_G!5T3iY4tvhzIlRFI
zroN$KA5&e52M|Ig(QXUaVu!@Q*i2KtgK&8V6X=%VVR0J%;Z@7bJUATV?Lg~6c7YAc
z1wUa^+6Dq+jlwS)*Ah!Gt`^3qYkPqJ{LytRO;}&Y^rb$y37|Ng{4`KbtEo8kGtOR8
zgwPNVl5wYE?3iZa<F&~^_D<f7T^%8b$XH#}0=W#bROP=iI7U(ySPwcJ4<_SOxc8Yo
zYK;B^@;c%Q0((q)55y*Q?hp$>OI6-62R<ZaIY!Hof7@Na3jrtzbSAq7Ra>Ugy|sZq
z5e-BcntR82`a;haCBU2BD?t}T^FF8ocu`UP^Z=&^02=|7tJfHG!RWPs5tQ6WKhgmX
z6)CF)2^Pc~B`=-C%M4p&J*Lx0a;yD5_^HJFyp!t9f#?1f*ThBk>xRMDOoZynS<wzG
z?)y_~@EsbPq~nN<&GOu>Wx|7Lglw`m!aV;&XCH>e1Vf4$C`<f0sJo09DC~%tm>VE<
zhN#7S;gLB7DwMMCH1o!6Swyi#dNOAH;+Qp{3{T@;nOqYQ*xh$p?P^-4cW&U`nZYTG
z5-d@dE;?+Z^f-_%jcJ#i=L<d_=0z_=->BDT#xei~%iJDX`3(T)T|v-!)IU*zu;M5&
zt-=~m#3TOB><Oc8PH?|QhURK^l@fEkP&U1H$Z+DlB?eLkMHJf`sQK$rRg6_>!$ZBY
z65)`pGDLBK+U;;-<a|K%oqPHyJNZy|Z!}*#6bPk{Z*b#x|J5$aLt~2ae~a%u=Y$`i
zJ)Z^O<}z{l*wdexhm$7|F0k`au2wItm4gmk^GxZsVB~;AUwKMGD+6nK(!MRi;Gp)K
zK|7l?hk7#(p1`$n0zmQ#1Vw+3=JNC~pT&0g`NZvU_68m>UEOolAKqt-?RGT5uq;N{
z!);a65V3jsQFr;F`h2^%K)N%0YWn^m)K8ji91h)wlbXI-;khM|mSxn#+oJM1z`OHc
zYKS7%t^Em`BhuVq0jVno;o7UFXcl6zfu5aZ6#ATjOB3RQpzTKJsdRKe!7N7AsZD_<
z+J(uvN`63Y<A*l(oYQWR08|(oeTAHQhlJ){VnSUfoy$wj0SL^U@sRtB!@H+kda^WH
z?Qi?zKNy|;Oz!a36AG6E$J<OjQ3#+8gx>UC9SgK`Wj!r}=$EzS`fqky2<S9OiYGF1
zeZc;7?z}5;U+G=EY6hEK1N@k9yIh?m``C{J&-0|$T?^kc_bGbbzu4+_HE96hENw&6
zC*N1jh=$WTJlFMN!irSQx>_HIh_PEXqro|cy@dl8Ojc38eA@g8K^Tu@C~NB>AiCY#
zn!y)A@Lr_DZ^D;RDgIfyB-y3h0H@RFtG%=-wP^w<IP<@c?ZbWbmb@kR@9ok>%l2&V
zWo4m;(3Z|v?ZkfLnv5yJ9f<rRtM*U?=>Jhu(@}C_7Qj-g<{GsHo<l8S+67Q~iJ5&P
z2~nKftoO?E71e>!uD-C4(jTMyka}+yX>p?*`%n#P8P<f2TxLg3>8v|=yFa>OpCyuf
z!BWfdNZ^N5T=jhxiP;oD*m{BuwGi;sSgcZ?^UlgYkS1(ZxYF$c%JW5=w?JZh-Xx~z
z3<Na=%p}NHfJ5Jm!Cm;l>J!laZ)dY4G!h(!rG6|}H-aS%A+}u>301a!@Pc0H5TD$I
zSz<Ac2n|?2a2*d_Ux}_b!+!__D99Pj^@YX>GMkfB4gyaNQqCl~1X!{uuwActkuBeO
z!~I+GL<7O9<makX1NU{J@FE7s1$4x{)#QD3pZ*K_hJ1&vpdh*mzSGg0z~1g?(pwE~
zW^L2lOagQr&*$DkUcoGivCgGt#QRj#(r3H(4A7Ye4)}?1my1%ERuuL!1rRf)&Vp*|
zDC+jrS?jS!&*#RW@h7)NK@?-91m0|+hp3kc1nr-2lBkc<T5~WH-f9k{#LrMFhsR@O
zoDx~XU=QX|>mC}RXFrQ+CaHHDFhaf~CtMe=p4;ldnIZ2GAm)gZ3_8rbgH%fri#Fj#
z1Pyxk%AN@tv!`C7;!1nx*jRe>3m|MPe7YOZ#y8d1I{nxOj$&nkP17Oi#IxCw?yH8}
zl<I+5Y~d5LtdhhUt!)^wNJMeh!}e>z2MG7o^e`?;ZGBImUyzi*F;(-+?A(9o!b!uW
zFqFrEr_=%fPI<m%;yu#F;>cY*Wb+2kXD5OW!o$d9{Iwr=cy`D0sH%`?pxX)bE%N>y
zu{4E(%fYWikQV`S#tpeSA6`2dUfT?;@L%!bU6%<i86mUJ-hJHQ&>su|SGkb<i?u>7
zw=Md6@9;NL=A?oYZToGHoohbXXyO;4j?uq%57NE<jE9~NJ6l-GKzv4c@Xi1^^!xy6
z`%^drqCX0Nvv&Q8fq<v@x#Cl|7N}=BX0f*L;RJjDWxMBW7wpI3eqy%BRC;GznkGGy
zkdNS1-3C30D4$n&;<;_*aGCcof|nV?2-P_4L02ZH0JAWg#zyM3&pi>+7{*A5MT1VO
z$<C9|7<!jbN(_uqS2vh3u;pv7XaZQg@&V=4ag&K6|Ei6O{q@pPwpjAqR-ZT+yoO#@
zXBG|YUZJ@^)Fb<`)L?O2-+{F_>q!-;;>%i(B>V2Jrn@=(WL#!ti_XbG0BUo-G|P&>
z#L0vqCWuKL0OvEx((8f7)kh%+!PhAY{_xbwqs%O0!qyYaq^HAU=zxyUOtJ;QA21yN
z`)>l~zlXI^-+L>ezgbCCI(k)HHbl>tZFN)RiA?S3!)-HGH;!=d9tQTpdVzxgP#k?R
zpL(g6OKWFrzn5W6C(At@$k=i&qnkqyfuSnrAG|4tfsH$0zeGRkgHOIgeuJBRFIGp{
z#>-JPF%ePu?i!$i@0HXzF>!393&;qN8!gb^#;Q|Wh67>^!Mn6l^+l}RaKvl5LinD+
zi@z12+@;Q%0A3mhCg}h?8Woy(ZTn>hvC}qbhRUn3;c;toy&BKQJM=O@1lj_Urh(^a
zm|g&|gvH}Cu>jBfB}7~d50V7X{Aa_qeedF!jGPmvOL^&fXbzC>5e$?drK)G?9@9BB
z4&NgLdWU>TY8~o=Wdp!tu5EY(?dch;^Rw?i^7h<Sv=Nyi4I_5>2=6adLmvbKH-}B;
zu!FilA}O5L?Jb+xcLJhyL<hJA^#J{Z-+<*u%<|jeT`Obt2L7kPfi^`s5`P#yn9M$a
zz@Cc(qY*nKN%dPvrQ-AwUR}6%?5|oUEW*GqlvXbb#WO5s?~58m9I>+{TNnI%+aREI
zn{F83MvA<)f?3;~hk7f@jUf<pfvC;Y@N|L9raS6ZD-!4Breb@M82w4v<e&wywTs7|
z2n9URJ7ar;l2}$jx<6aUZ=tul7N``zI%e0_9>DiO#U(tY8|Wp!Y*pywHZgl-Z4O}z
z_9LJUOn{=SHbcH6LeMLE`Z8^Je#QQT?FTaxW?<;|(KOsaGd+$ehrGnz(|v;$HpRNg
zTE)9ER?89KEW)v-?gc?k_>u>su&BVmwncJ`1yFTN3w;ucC5N-|6_ml2vSm=2fgs{g
z^*IOT92cZgXGTBY;Qe~KGpt8Jkb;RP;ArS<;!plN;8i?si_Lu~AuLpIcp+5x5(IK+
zxCD=fksTGzET178yOHkq3~DC7$I<&ft#JaTRe+^q8uER@n*J=v1$+V)alfg3=ra6N
z0hF69qf~5NXyISI$Pzbi+)GcTX?Y$pvd;S_><#8LxZZ_QFX$F}Abj5jFVl_|Y&jmI
z!N^}3eCL$Sy|NhNLWKE*he*ERdN6|8{u0Ad_Dm#2AU;r%Um)uj(kUqf`lj-7dwWop
z1?PCdHE_<dKaFNWKgO`30VrvEm_q?^E<GZFPris|KXaa95k%wz;SNB-z<c0&X$KHb
zZL^J3!*&P*yEpQ9jUF<QG_!e*&wA+NM(7}@lx~WD9h>EiTrLCX7(73`+$N&d{VGaf
zq8c^jIAGwUQuJwjt0W2Bnw(M*LPOlEh>5faLvZA()+NbGYA5W?^oqGeJbpaRZBnLK
z;Ln!54bwa3cdBWat@)DWwN~ja9FECRcll+;VopkH68kaw%;0Yqz3<1AxU%Hbp6+qC
zAZ#~SmE&5Hb77-0KX=P+)*5B}*HB2JVDgSf_MwWBP6)PkZ*M>u!6pkFFEBgP&dSEA
z^i%rxTr2y;NLHlFT2bYNrjLmq)-;5Gt=gaawBFMY0F^#EiWA8<+RJr);wYXsaTMb0
z8s|J!peGlpbHd?;F=df3L$NYyyK*h#tj6Vm$MJ)C{rd>9NG*qV7209Y>p5iw7#xSC
zXnqRB3pN8*I9|hu<-aPX?p_W{5;tRG&X^elaBxd07ytUB!)ALZDwOxLusS-1(cfxD
zD(!oU$xTun_)c(FvKadux&TaHT{YB25RCm7%KjPj6KcCD=}U^_2cC%I2EyjJq9MvM
z)x1IkQhNZb)v!9W@R`mAgj%Fw1&=Cf=O6STZJZM%#X9B1_!X==Myk4JB%`1L^*hZS
zq+FpH8f$GFni9!=URJz99-5-rAzH_dJ<a6ztGhty9HPh$cKrZDM2_cj9KF{;<t6cQ
zRs<s6!#IFT$LUIn3*CDIeQn^Q&%Tti>QLM}T$#;ie2&38Bk4WM$x(vuO%3e*ela!|
z@@mF2JeHAS?_>Yq0n{hIjxZTN8cH)nT*H2`2GiNxmj^!d2(V4otjT1L^TMBM7CqDN
zbGr<~lX-ub80MPC0aeZ(-~8pu<bmY+rFG-S*-BBr0OC)GaWX#&+Oh|K7VQ{*?gzkz
zlbD&%GNPU6(500=VO%X?@Uh-n`dBV$!`~L;e5-==7jrx`nmKt3icgW0N_&>Xc!)S=
z6=j7c9FH}Mdk4psupxg3$jrCYf`tJ~^u^;Ickc|cT8xboUK^Nxb`+-r<S<5MI|;SD
zO{~O(*>x&!aTn(wwag4ZTssgIE(%ncQTLQ9DZ>sTF{wz4=1qjFBWHOVND=RtL;P1$
z(8673Ge@G<v(7|NfxJxI$;g*ADSSPWMWE3E8J@h6&$irq4<X$rfQ|YMG5|BM0r+5w
zHDx3m_KoBy$JNgW(j*0myYYABjRF_!G)-UPU(tA3HMNDJsw9dIOE67eN%%c=!w5ps
z42;lahG5c%FqX<}c*r3ldH4o9*L=Uc@VT!*sn*yN>prv)<y$mB)YtAt@pVeZ;dP?l
zn_6L9Q3`J)*~dhg#PPSfy+NSW)4oscRKB#qzdz_BrRO~qnBLPqKpw-*IN_e?%3+Z2
zzd6EkEYW<Q9Hf1-wjj@vHI?v9A<qjSYUJ1YU?h!@3|*RN5Rhy=HCzRU*ml8|>tKV$
zVTtL)VxHkAZ7$|I?krTIQg7okYgBq6`3V8Y1eV|ed@t{Vu_*G~@GrRj0%t)Q1_EnI
z08-)Y3|WPh1N>({Sz#)~fVhomkC1<@)lobC=`<}~Sx`j#ywGG?@Qf_$F_Y#_PYNye
zwekr9r~;YG06QCF(WirIvIRD=XGro>31CK-XO%bgFVik-+EiwMv|tr4kcp5yAvFpX
z$qy9Y?)rL!kLp@ZFcF0__N=YfaZwD3YNbtCC5xS4Kfau(iwfeR=D9^YI4qF>n6jgs
z>s&@q5uhGnN1Okc8_9Ecv^rwPYSKOpZB51ImOI0tRcX-Q#XG*Xo=F$WK6@fvKI2`4
z#SEbKE!4A3_OA6`C;)PO&!q8Hm$faH9T_nyiS*L|HvyrJYdDItT>k+FRP~&O@r2F}
zwcF2`6rrHna1O>q#Md<CKN$VPRqY3cv_O?EL2WTX6N4{{sw$4$Ohop;Z_&wSJwDr_
z>1V#~G_pfX(c%*HlPm)|WD89<ip)ZEO*;l+$<-r>+^Tpy;)SXG&^}#tbhkMm`9n`{
zFNIuSW`eR}Bb=5!2-q!U+tah>79L}y`~u6y=(7V)=Q}#A)BaH2Q%W_<UZEYPNJ}au
zB82S7Ade~-<C~po3gHggjxAlzuhQX0mH^JKJJ=KbI?YlWk&=?7#(PcmcLK{}NZd6z
zki-RR<6|FH2VDheq1jM@uDN`FEM27YdJB*<rGCxNw)WDbeYVm|(n=FGb1%0+@{@E%
zpz|;S<{Kzwz_`ly6Vd2TR_v#;lHz7?KU`v1^^{J^*l~koWysrS=@jypLmD2o8A+lT
zhTQJKVTM>Y^9vc=cv8>>Jmm(;(T93G&KY~)2h4g?n8rTu?B`33nT>%moZsP&xwtVc
zU%olvKzizcN!Vg(@QMivoZ-fvgWI2_olJa*^YzI@GjFe<LG0s|9J_sujV4w*(xfen
z&Iibf?_H$TOoUanjS<T5&Jh(vwWQST3{(E9OZzpgPlh!N-9#>$k;>5{rnn?0>8>sM
zbSMep0gcfKZ>;rc6$ILw5|#)rFMOc;NR|$xp-??5Om7<$fs9ZMQeEL+h=ah_?}&)z
zsK3PK&Z!rHj?o|yY6%!D<$8}sn+77WKG>5~Vdq<N(B$$^FL#S7(YHv?VwS<BF{{FB
z``5=bA?q+UEpz991$30_aZ)Yy@Dc=hsASao#UXm5*fs$8E$Yr@Ig$ALaw}mGW}Bcd
zN0tU|?bA8|J+XDByKS0(4e4N-P8`F0{-kfN*w^qp$DK25DleEk$l_bU-ZB)GtaVu0
zI>(F?GS+5N;ZVS(3T!UMlsM6yC<ior*nnyqJEZ%fKt>ui3Fgfo|HxOfJ6qvPVbSm+
z6ytd5v;^KR*6j^OW$*EAD{s<NAMI8&@Vs55JUP=aj<Qfu3K7&FxGu<x1k-e*>v)Ew
zP6h7|>`Ck~?PFpdYGWuh`P@>}j6^pfBo$#16Mn|A2?)k3N^6NK^!<ct?^u+C|Ejw=
zJzL~~TA;BM3mCYZ0-R!u1}jQ<!IKh#D`A8qXwi}^osIA^cv&w&?<JVAJ*YcfSrr)9
z4_#u%5O?Y@ZCs-{SGvj9I#Z&S7P*Omf09U_sRMd&HzK?YfPyGF<TfEDH^C55q_@D~
z_$=`Io!PIkiuDeAP{35oDIH!t?pupi#A^M<i6COXGaVPpjU4q|;+mh&q1yjq!2&%l
zN=Nh?xOcl~MQRMmNn~Bl7Xr8OI2Ws6?8|0Y`jWv`{B^~eSCu=sY#k~eh&hoj&9MdF
zu(kHlhbCT-q=_L+q;A{Hs<Bj;TwxG4^4bu>VI+XVNLMOda2?(Uf;U*Q5>{cnT#z;(
zj`o|dEj3&S%0Z{Vk4t^gz%JyzjdZZ)U^B1n9I9G25CTexJ^#CKaz_<n-gC+8{cJd)
ze52S}IH9BfMxHSk6hY6ba)qcSQ8EIZH)5#D<JV6ejgwi;T_XX(OtoR+$9)clIS&kf
z=cORl+tQMfbI2F;J9B%-Mj2fx$Tuaz(2hnh^?hTovQ100g&K74T>7rgC)V~`9Z!%#
z4S_>(-Wu^(29!c?{}seY2`V{CQtZGyoNaRf%9(6jQrkLarz*gRED<=y;SOo|P`?pm
zR$SJ0$=nlmm<?KJElTQ&J&_iHgr2Qz0>8LXe=pIIO7w=jYZxIqEhJi_m`9a=OnF7X
z9UhCYa<m=Y*A(P%kRI(=^as{Sok|oUwf1_wP-pMwabPUk<`Fd;Ju}EZKi(<J_o(+h
z$MG}-D!Tz7;YWnCeH1!UrncFslQugegJH970D%^3laEOynxVU!35*F|rjP&!l8Ghi
zAb?nk4h>gS$-gUao2^p)f|#sx2B`PWGhv@!ia)nZ?`e_pyP?O>ZElQu1P}|R7QzDT
zpw3zS!$_nLqD;BHyT!bSH{XeGH^iw34reXfALc{IxgR^*V(u<8P|FerH~d(%aK%w`
zJT$*B<K~{u)qi)+Ep|MZ6kFxQU;|)sr39%EQfe$+&=K1qKy=6HTDqGT;LlRFX-xTo
z15urEk2SKaK76?LSF7g3ZNSa2rf82NB>1_p8}9HCY9Wtf%_99(#d9m(<F0(rpjS1}
zPU36BhY%X6d2ddBV^OHbR(2|z+(Iz3S41yeu1DNiT-R&Rs+w=j5GQN69t2p0JsOtw
zZ-bd8`=WTOVn1lRu<7mS^K{n857lbdDv{w{SnTsctg~gr*0Vf5+56NVB%G2rcUHY;
zajeZErGn7~kE>Nv4LDf3$?{w^pNZPsp7z8&vl7nT%(nQ;AA|Wb;>~D_^zM@i7IXcJ
zxPh$T)1w}abbn0Uw%k>8C`S}sWlid24SFZDi5(;#b9OFURF?&wAAUY<9EN7XKFQ_i
z95QJ9D5cS1o&x|V!{tNrdJJvLR7|}v)gA_xqWnL~NzhYjpIT4N5i0pDn}Yy|*0|yJ
zycgVMkzy)WWb4GsJe1Kl?AY>AUhy#gv`aB=I*LceWiJHw#Psy(yp(lSi%;2)Q#zcH
zcA{AV9=4d6r)`Y<*wQe-&jsd1ZpLyy`C-k91r_<JX%AL#FYKPh5&1^C?EYS<jQm#X
znWp02V$VN-%*_bG=OLYija0AAvsF&Ma6in$1g>zrlQo8JwK{6Djx?V&BP|d}THB7V
z1t|MGP@NFvEh&_C1|+Ym>nz{<c~0@XgIpd5;-E(AGH1D`xWI@o2C^<Ax0st|$s_uh
z6<$n}`+TL&1OTLk>{>J434FtDw6`iwEc+qms7^MCS7(;Uv5uWd<u!c28SLaR)mr3(
zYE{=*u#oq=y)%<ugO7CO_2Wj$CBm2qEY=$_^tq!8+f)UK*r%R@JWbnUOb2>cnx=l4
zX(<TeUYXeM$aj>%&&38MYF1jU%rc6@KDHLpm)WV$Dci}q$lw5Tp8<t<Pg_$0(1!J1
zBC2nZy?~7n8bJ89jM)GssWDb!GFSYaV|O$dG)diXU4D7?a2k~wtz*ptr$jZLp%w?=
zjpF=iChUTI_T#od74~sdT%yDgF?u?!hxUA^B-e@Q&DZ#ngDGYM0naRS&P-+5++SX6
zQxIdN@UB*jjP65D)UBNEQelql5@E#Q{LHZ>s6>B?8#ATR5FF(F@*Q?FQ=Asv60c4I
zBiot71v`}j&y7u$s4wm(nF=LrMNqOOCY3fX_M6drOe0(e-A57*LX*?E$@2STy_HW8
zD+!tCH994c^N_$nw3yX;jg{7EQl%?t`W1A1w=P0T_n?v2?cN(M5eMJJcNnp|?I5=L
ztP1txK%-0e05L;t_ly=TVzy!Hb+$aJiQ&(p+Y-nkD-v1AWRw%8Q5zZa5@Cz6Nx%%G
zI4$ZCniPYWBds@#=+3g0gTc3k|FrJsU!8{pa|rgdV{W?+!(8Lzbo$5N!0+4CPN3r?
zI<u*GOR5UjBDXr<-6OVQYW56QBxh+-PLT}db&Q+@#Acg?MTNMAb4Eh60&c!npzu$|
ziEt%SNTY}}M1bu*1H*KEI+truL|Q3%_HBVM=I{xDm|G>di}XCYmk)Nn<J$I1kvPHB
znB1b;l^dya0vK&^mtlcqFmaZOlWu4aQ%XyG#2XHMU1@`R1PMCimqr!4&t2die}$bO
z!;?Ih<!wZcdZa^XOXd3v83?KxB{p9{aGd(Ihw0PwBhn`0d8X-b23(FZFVTOExP0#y
zR$sr9s_ld&YH^H}nmMP|3Oyg+x5kXfg$)4WEr3HB!oAtsT8&}xG#m%1Zjo|feM)uR
z%*}8*!sys?k1Y?7fE_BYL$s|}_800)aOokvJn=TM3afiK+Vr&c60stk_vT1)DZr%O
zT18Iv9|ME35tbRo2G(@8X3LuLGiXq9M1}kbg&JMe%EMn0bOC3#dp|N+HY6Evf)JG{
z$*NN5F5sbQz*!hjhMn8k>fCaf>7FCn9#@zzyaIb_7dvE!5FizqyN3XKfH9(QGyKS9
zg6nMpw<UBSqB&CH$e|QSN)Cw?99FAXh2xIH2=~KZZ6X|iD4~Pk3HLE5{G%{WSI;Xu
z?TV3F7?InT!%Fg5Bx`0jiJ?;VvH`1>p=)<rp?zL65`|-FvB5XB11;%_<78z0!uO!&
zN5SpZutC%6U4Npb&aO0eFGFpdimqDUy^{TLHL^Inrq`7lwB8KSMQjsUe282=L?0sI
zl36C@k}|%NpV{(nhffY%Qgu7xjQ{aXh#1X**()Ckw@WBS^K#)-s@!Ktmu5kx52sAb
zkRxRaA(JS!=~bOUh9fhC6hNcwcw+=>E461pfPj!x8`XaF#ffPcP{Shv&YX&GvMi7;
z!y^O8(L$N|T};oJM@({$hKvgFfKr|wsJuE(O#0M|Y}^nOY6>0Y9^FnGvao}<aSW$x
zD}ez@e<MJ@qSOgz1$bb}8_C+!-aj!1%v??u$&t?U+5hFto6c()BC}T8#K@AdY)`1O
z&fx@B`C6!t{N&Irj=wOI_7qg=munPTXv)Si?_#tu`L-@V^4K=CF$CzQNnsYzse_v#
z@EUW0TEhsyYxU1rEZqGU$1C@@eC_Z~)+N0^x+t{rZ|y-md#igUF<BPJefx;2Ar95w
z)}?3zt(w;&PdYfc3^RlNC^}N|;8+c4Z}Dk#%+fzMleu!s?U5<Iz}G}NLvfSyf1NfG
zJD^QjXT3*0kYKzKT``h!#9S<{{ODPbG>&lfskk)ow|ZBTwjD{Em?pKKFRL%2X#KB}
z|2}e`&Vr<5jfM~V6hO^UlPokIo|a_;+gPEpVvzFHB;u>5hU9f7Z7Kj@P`T_HY8lD6
zIUF!04#OpevbP`$^e|t20Su)t24R?Zj`aoyXS{B`6g7h0BV?)Ta8V$hH;xGetjCo$
zt;N?H0Pf;ugfV+4$I_<nIZisxoNVXF;tRJXq98T7V(odwg`?pvS4zaBKxAG@Ojoze
z&hZpU=xLV{Dl}!(p0jO9=5Rj~9vINaI)E;pK){zEpFwQc!1d^#(!b|(r1(!t=2(Ws
zUkc?p`)*S=FFAYj<bLD0eiS{C)wMQM0*mk`Q=-q+YzJcy3E}c(OnN#_@yx<l9<IaR
z<z-smrqK&0zz_v2{$96t2)0hMq#s~g6WxZyB5%QhAowHB6G^vV6?-Yl@PmcSR;(_w
zpEk^=+fcMMujS+Bq%8)^0_$kfNk+;f7=jM+_6sXtQ0it4gm`j$?XZ+FJnEfnCAl`8
z+CLYp%r?xruOkWLT%-`A#!5A+gjs#wo}aR50(E-}JO&u65KEK&LVJWzJPonOCmWQS
zI}SQ|Ie1vXd*N)4sY^4m4v-{>+?L=<ist@yE-|4DE~UmKNex&JBh?v|E)-`sc(X7W
z&pd_06>hcS-<PKc6oXHsF>}*NvC1x<*EAFcuWPFBE0I6cV6C&O&|VmWkd|PPj&C_w
za36N`A4L<b5@R~94@32;lP&tEFM5$Z{!`R!?R7TIu98SP>@Y<)OzG&;Z@|ht<N5u{
zfgxK}TA)q$xWDW6O2f;iE6Pq9&(M?lhJhH~cuE{$KS)6O>UR&eBjK2cnUrM3auYD~
zU|LKB+EOO_vcrx#u5zi#ju~=H_l&6;7FB;B{m$P;Fu5+K3HD58%AA=THTRG5$gQ;`
zp+IE;whiMZvoJ*9VP<;J7n98fWygcYehB-F)kfY_`ZRTHLO$=Bj*LVz@i4P@DH&*9
z=YaZ9HDreBR=~W!$3tUf{oRcq?=!gi8XlajF8^{)Khb~OQwj|}YkOi>;o?LygExeN
zQC*%aoY7OP(Rzz#W}-j;v#W>An-)GDm!I%+&hZyfu^uJf^9iBA;4?bXBI`M`WY;gR
zt&gJhGuQ?%lB)3|r7_Q0Sn%n2*Sqb51<-l!D?0pH@~^0!`5;$l=881!?^coEp_R+=
zNJmfAE8k9@YJuL|LoA{Sw+3eJW5z}--4BAOc|ndwstYs{g>c6@?KJw`V<aeA44z9B
z9^KYzzDgW=IBC$SjuWS36kKMR)<FXR`$JB+<V@G839c{~kKLJ@ldA64I!{l>N7GXD
z-E}aX(SU!hnKAd8Sez0@?Q}jp(=5sb|8R<gFU&R!T3zwKW)1+n=~3#v5DuDWp%Gv1
z(06OQG*)S!weKH+Q1;)4{a;T_^K&KA5F9bYsklJ;(Nzv`w`K2PH8ONs8Qvq>KUy5A
zB)~1JYX<4UOp}~3jL(+^nm#L|^F73@hK?`eKZbUUv{Jj0GnyvDSp=)S9F-b$;Wx?c
zv>zs3<nJjb#CxlQm<swpbNeMso5)+g<o#VuJd<VifgvLbJY6bh4Yn|VB8<DK53S?;
zQrcI_&i0?eBqrt2P9Ud&DSFwg`NPzkO!Rv1W`Z^BP)M#`-0nKthoK9PhtLgA3q$Sb
zfF+>W6M1#nT+(S#m@d-*Tq#;USfTzqaeuRCA5%h9TLr-EwjCSGKny!*4GI*APy35Y
z(P0FCx1K;1TM9u)#ing=gcP~B5%)ml&Lp~2y*JckfFHHLVtyzxYG88D{^7x#9KACn
zj$tiIfrl$=LrtLq(!YUN)chKh4p}SH#+fjeySX8eC>@vl`^`HQ3$`2?)2;?2DMWjK
zV2jaMT)TZ6SP}CU_ZZ@leO2jOx9x{Kg>jrZbnQp3S1(899stZRx@FQ}9uMB@`M4Xv
zn8hjW#-&bn^aOBzq{bb~TOwU{mbyKRvll#EdGo$CMwPy-zQp1s5b(K;;1LvWLK)%W
zmb#jPVOs2m?5CzKE$uFZ7G38v1%lOdu-tU}E~JY<#L@ABlf&kkhlaaAF__ZwA*$1w
zS>E6YPTe^!3rC6e)ta2Ft~)Hd={<cXU;gfRMLy9q8FzM;Z`H4~4SUc?>urGGTKjm9
z!9uM5=#z)4Xo_oQs+s7!RR_J}oX)Af+5<#u$eTJ(7sI_1>T#zNf0xG8GI=;vfa_xQ
zDx`mVK)G8*Wcc!P4d9xbuoesM-D&vgLEoF{Jv)$HWg0<YFi8K4uXhX*CJ44f$L2S-
zZQHhO+qP%EvF({}Y}>YN+xDA#cVFz?eeZ7nsOX4}sEX*$&dQUOdCp0&wT)-$iGwVg
z<xgJF0l#Rrl!#Pn_QNb*2lU+GhAc~{QDQ((oG;7*upH)1fywYBj!_^Fu)<T*(}r*Q
z@ar<0Fb!ywt)<h#qdeV#>v9p>Gdki<COC@0=R8L{@{0&dS;bSep+nGUYcQFBl89i8
z6hhdRSCL!Clc|_xsz)07Rt(46j;fBHykKB6R#oA8K{1#=D+w67U_X}jdz%$Yqc@KJ
zvTTzi7G#jsd-d0J=df4JN5l%If%jh8UtK3Uw{|*RZy{MzN25YjvHdfY;T@TJb_mIK
z`YL}^6_(Shaz-{m3mKlWT{UAmCw}lYiU#?6DCPA|`Q#IV%+}3dE-vGv$@ZYW?RSOy
z5T~e2N66L@XtOgkFAqP{QteeD^KrM5v#ChSIc=Q5aLJhb4JGh!lE2A@9Z0{js0Lx)
zlco}#pq25;7Gz2yX4m(d#^degTL4&AWow`*UYsdxPKh^-0aZHFHNmJGw$5UO&ePO3
zXX1|g$_teXtcHD6w2?8SxK+-;wAC3sK=~sN=?;cuPGG*C_8Vy`1y!9qrMYQ^d(k*q
zt($3qcz%6K=ZD$nk9Uvm9s~AsH*p1n$#7@1EiSsD!Qz-ENXysL=ge%4w23(@1Xo^Y
zmM>1*+RdR>a3a$lmOKA4D<(IVDN;}G<+)SUO@$ns0X_Op0~zX~mxfl=5q5E`n5{ks
z*=_)$?5a-UfM**$bo2WKl`%;y6>iXzPm_7T@+64jVFw98+GR1RG97syG>1P54)AT4
z;>p3f0&|ST^;3N@P|E+%MNWY+lqqS|3+}REDlj+qAtXkwMkD)i;>ngsq_sFtHm|EL
z+rV>@q|C`BY;qOj#w|n!>`bj1q2A3Il88=9qxZ@H#?HuL(uhy0Y~8`bX<ELBZf6Bl
z<1f&!o9CP72*-TxCg|+dPdxV<I1jO|2>H^%?i3~HC7KwK5gRhd1vLk2hRiXzRIwx-
z+03E3pi}ZR1eyOqnX0FWg`t_;+VgN1JGKF}n=excGv+Ja!};SKP2V{qi5=cWdKfN{
zis%=ak|SblHF6|=775oYfxux7=VK)KGwQ!CW!^izimVw+)P<Nw=L%B9E6XU(0@pyy
zX?Gk(u700EIR?pQ0FH|9MK3>rQYHv@?@B$t_**OhcT8#yz<GzCtnk}%s>Qo5_UA;j
zR_z-ImEF-};K`-npUjSV108cj=Z;ej<FgiQJyFc&*bB5F$p9(cgqIqyCskDDW9^v-
z7wKQdxfB$K5VFF>6p?2jS*=s>uo!<)6;d=MsjjU>9O89uJp!Mk<dh;HH{S~{B3hfF
z*J^UMPl!O}EHQn5+f`EDNVc;!&z)ZpG;Cx1Olcr4gN4}-QNw%*Y4n`cT`%M0M&p#I
zuLYoS@Q87#djf4PaF1R)A*L&m<L*3(^*Yv9K=2*6D?sFFQH`BXh7SmojrYJ=&o#88
z4Dz|Qp-J>Tqm&=p)!dy?^zkAW<4JX&tllbfHY(Yu?t}Ry<0PV^>3>xGR$#soORL;E
zH(|aT{#mwDtKeV76pv1;hZpqE3_i7p4_}JyKA7p4VdhVY2iDP=;~MMd*lOty`~<Ai
zBLk_eMSQTt{EffWjJpo=9B|^1D+bK(5#dX3ugi<|SvJTw*dNl~%S4w(tUl9ANbBfH
z)w@CD<223})6GatdlU@rlgm363WN*DL*Lz9?VTts%tonc#{*FAlJ}0E0<3>oWxcG>
z+hJ5Ph_AXyup<^x+RH0yyf#`hLU^A&?VWkUi2pd-gpoZnKY@Z=e(#lp;gzX{@@r1l
zDQ=?sz!E2fr>PY;g?Io@OZnq<Q&Y}y$TC%%ZxSArwZ?guI=LrePr0{|KS?`#qZ0i)
zwteEx4n!xmiVp_j4fsC&s~d{O#;df<ap|&f5;-2adh^uaHdfZ&C2pu}T)U)PAd(f&
z;>%d_RZkmdD?F`4@hN}&3HkRROgye6T_i#uPqEJX0tG_1=S`7|n|EvFbGCE9`j`2G
z-7FBw)Dx>JozIp>7VOUyR`7?8R>z(2+Zq-R{3|Xm#2SkTww@C{dvn?|uU8>|&~go?
z)-#5baq5M4YQqv7(`Z*XrE}-m6)Cju_F4kx+?$va5h^xjh?FT-J{aQkTqL6#7!oO|
z{}YRj6N>M5YpQ#!9~>yE+`mzCby-(aF+Jm*-}2|CEZ6Mr&2*#|nQ&pH#!I6Vi;lxu
z@h5UAG&pk}ljGrh!J<rR`z(_4OhcS;A;6$MA8A_Jv3d_+lSaI$SnU`)wq*4A_XESp
zM)X92pYJ@%i0Pary$Y+>m6mo$fk@Z9a>*s!bbhHj869%KP!h~kR{GsPtPPAT1NM*h
zgkogV#+ZSzION@y9V&xeT-m07agElzkVn)*u9(HS)9=J$(|54X{y;O$ra|U6f#Ol-
z+mos-Qqp?%xkSgquCwB!tSrl%o@D~tfF*E&M5#{ib+bvI%ObUwnq$mk%pVlFJPj!&
zgfFnZ(M$Y8iXyA;1m8n@(I*}NxJT+7d;*C}k9plIkw$n4yE|`P)F(A5R~}pyZDpD`
zO+$Li<X$nwO|AlJ`nw1jQxXt2SXvJk6JbsD>=R9kEAoXDb0Yj6#U0YCXIT-<L@<h&
zKK;PzF*6wd8N6DCewby^n5fT(cN+i_zLUdnSytDNL=*v{owM&?HqUu1Oz&bYTjA>S
zmX~RK;>y9n;C4(K+z{&-howoFr}8A+@5y<640jNjRKl-w`}C=r!-<8su*(YxB^#yS
z3a^xS^?LrG-I=K5>!Jl9X-&3C^Dj2nuSkdJ!bFYk?uYkG4^9pQ5A@mNJfuhr6rPuC
zfc2}BTw(K1^mq<LcZ~EpGlr*biy#vmQ~CxkGmD8e66vrxe(A-qK3NQ0a~itVH~Ii1
zE7AZr*-M&O_<)dU6K6Z+gKryXv2w^0?x?12ukVyvWU$@XffHnV`z3&ptjRk0Ozxj7
zY2e$+pTQ-3h^iD%l*oCS%q%Y(Z-rXLNfA)zo@tqY7AeqNe>daNe23Q8XC?a0M6>9K
zzOC)NA?59()fm#Q4LdhnGyYbn*e3ec;~OLgnHo1Y%J<V~0+N%tL)%#9d@z`z!+(<t
z84^ln=uJt(Vco@-B&m^{hKwW~2)HJ!(eQ&z!qp<RzjBVojKFO%n##XY(mMqWeIj&!
z=z{uT9ZuP_T$J|Z4+>pnPJs-b&qcmeEP={iICvIk9tPL_YqGLS*RD%&mC~KC#cx7R
zx{oZvco_p@XjpqPaN3G<GMzJVeG|(&a{#o=h^%EeS|Qan#*F*-kDH^;cQB{$8VA1p
zs~%Er?$7tgV9%jVako~EF4k9d7xPD?c9S$BnkoI+i>G=Yz(}Vus!`+YnCot{O0uuq
z2W3$ze1Rwalz$_JF|qizf6U7T7TZELsA7xPvX-$O3g6aOji_cvKnnxEFbfp;gM2p@
z$8=?#tthU*R@;6rgBo;?j*;IXHBrbSDcv5=<xcCQHheQjvj-YVo_VsJCM!D5s(J6&
zp*(T7jNPu5Nt}p^OG-^yJm%wJRhgKib@em(ZKHMUJi%0&T-svle71>=8p@&%ZOk@<
zcPg*!v4UxdT{4fHqUr3%Vojxve!L`mSped6-j$5VRz&LjOlurR*J;^9ESCdAhFF4O
zOip+bjKoZOYk=iraS>MSl-Mj8&lqItkTZ&(Kz!S)D@hL=81<wr8!F0H+x&JTcE-CH
ze0=HY55sv<;4%bR4o@RWM1C4nw2^kK#kALkf+?g2qB5Y#rhGIL^9Y1fn|BU3Qg$KK
zTKF|E3IWQ5GIMBBuo|rylvkKKk9vogdX)cs?4C8AxO}st1dcM}hz3EQgv*P4gkYtO
z1Z^KC@h)!b2wvCLVwBmXF_ei-j1-y)w^>h^j-IABd^}hvQHfMq4Ka95B2rR}^Z7BV
zb1H`ptIe$nBN;Lo8)ROSxoTSL`%Q1N`4Xayzg~L`FWmYQm+$4ZiL8Nvh<d8WV+<1D
zQo9MrZ|fJlF*ELTW@g+cE#wAaVR`pEoTol?N?4}t-iDV^2MB(~-0vsj7)K#eFMux$
z6mn>=ryF_>{O#R(Ot$albWOGHgcLE|PzGUdT65zhA9RA1DcRI7E}(+H6V7~4gS-Cy
z+?#X!dbd;^?+C8mD3x=Y{ww@*va2|FnZQZ($4I!G{SV@@TQE^Mh5|p`f^@g{Iy<}U
zfAQ$0O(Q{>m63?reOg7uj0f);=E4~tOvPeu(2wVLUEmJqC#kHkcW4!*2tO8^ii{(<
z5H6TlrP2c1jbe^F2aqhmoLogFH(b+QqbLt2AA5BMtqeG8LE`BwixAuON@9`CwusAn
zLKz2Rvb>P(H+o6YGsSnI+~cGHq2k;$UF04)PAc~T7@$TjB}eZ#6P&;lHk<iW>_hzO
zUB6Qc!Ut>*I`HJS=fop0He@uD3L%X+qxJC3K?u?gF3{4Np_hN&pJVO{wJlTGsDYR7
zkEh3ZZ$@w#ZL~v6Gp_{}&rPpWEmt<fkKdqccnekP>k7vvOO)U+Q4WHNOkIOpBHGf&
z9)fVD_yzLss?TCK610dj-{@m6(tcXA3r7r#*>*4TR9nJ28P=M`!b6DKcXH3a?A^S$
zB!!AdWxp!8i;bpp#&;e|sO7U35_E>P1(zq45=98PR;N%Up5Nre#%g+WQzc#H>8{VL
zrM`uB)t<B}H#BI?Y?CUYzwb*eA|Aa~7ju=U*XyWco}9%C3@X#$L|K}*aO|s9wu#&<
z1Bzuzc&1ag4!JEyU$fA3YhW&rA=u*{!oqo5$$HJW7mk>0$Tns-93Bi0TSw=CFMpFN
zNA23A@4*7^4KQ5#J(kUjM_)bY71%OO-GomOfi#PPTXr(NA_|)*!MHFcv)msi=ebmV
z)zGTHBv^5VlE$+;0l)fq#Zpmw`r0mb@s+?pw#5>&rfD0=wG2cVM(MplRk(Tcs+<9k
z17=49GglI}r>ls|oc-#@x)o*kt|NWmLI&++D3~t%aoXa_^NYZ~*Dl@LCt=SZVUWif
zb&0`4+%~Xm)rpJj3K4&tM&tKwZ_ea{4-{6Jw!JdIkxFDSmuN46^=L;J?}9j^R?j!4
zuSd=9VJ=63zNDuWpprZbU0G82X`L4m=_K8hSmc6EbR3H)k46DEK(tv*1;Z?G;rsW4
z*&G7PD9Hd1#)Q;lMG*Xam^5Tv@BMO#v}8kbe!xlFu>&d=H<8P-4c>Wt_^0_bOdUi2
zqGTp7_*KsGLh=VBu&y4>?P8@<HID#Q(gwOl{o67RKEUoEIr>?!b1D}ooF_{>a>Mi<
zUSG>B_I+h=6ZyvqGD19duC~MmfQxEG#9pL2$drY%k6C<#U$UK7Zo<jBNF@vm&1<Ob
zIT(3~CDBdKv^_K~;v4mv>SmW}rp0pxkIa>@QzQM+GWk5O@+)!4D2Zp`dgBlbt93{G
zS|@}657BQM{Bt{lpFo5Sz|>c3A?l4b!F8up*#wDGFIcx(C)>h*UZRY8UA+<^`zyqP
zGe+2pTa8Kr<^V3U?^#hyDj=c0x+@)TDJjw9g%LKOA%~GI{26o8L<sOItO(_TdoqBW
z<y*vlT-p&?l>Ytmwo^5I4GhE|BC`=r-iYz|tU;=mq3TZ#W^z9ZHWV`TfGqJ--Y2cj
z@x@OXFA;8t%s@94Gq03A;+&^O?gnd3f784~Ggt}QOM|lx4E3F_07Wvw@M$YU*4daJ
zKp|vVa8x@7J}9yl8BA6^fzXI+v`IiEFYO8{0nK4PA;r4K!AX^um8_v3)F-H43}I!Y
z`0))R?%<Ic!@leh1Uas+{z!sWQ)xtvzyT8j*I?l%1S$}vLuR5B?k&fC5+Axl_#xbo
z$m36kax9N>r5g@8rFgcuMzP30xi&O6$V3CxsPatq6?AmTxwA3`xm78ALX!=KH}4A5
zZn$S^%iBx}x?jh*^CbL%$2E1Wyus_bx>ff4^Dx=ZCCVi?4e`Jec#HTR^$p>wC0LX9
zIwmS)9Oi`44@tJ34KdA+;&b3;!;g7ypz%-aBHY5y8NiC-Hj?S2$AN|(*8q$J9)YS*
zPr1lpEujAB$UmLa7)^NVMRcZ_e|+E{{mqky)~&P91y&c8bU&Pw?JPzet(w%e{o_Ly
zWi!r&=ZE&6UJ=~@pia!wEPX?k7h1atE)-s(Z{KA*RgW4o?g&m>=lFYWtc|`*ur&~x
z*(~Y(N!Mu@D6$2oW8b}^>~=@PJNZlVeWh%*d%McS%4H9e_K-uW`&2E!$7)-f0^~D#
zldYPq3$UTqb`KE0%p6AX%IxEMtA$S*`}&J%a+S(KrSYBq<gWZT&mAXpF*E1C#jcUo
z81hSu=uJY|Xhz|oGG=902p84*XJ@w4`zb&q&iGcx#%?bs*<zlY^m1&~kN*~*Qdy=R
z8^u0;24uy;vU5<^{0JK4W7(5z2lp+k-UDdI?0eHOYzZ+oNc4o^MvUBG9%*~5#ijlC
zadaM{+~0}vK|Q<~Yjmd-oS9-(JwC*L%E9=S+ov5I1Fu1jM?EWc!vhR%xc!&66by`a
zToJVJ<X`hbAB%4;vDL26R!#02>s1yxTnTEEddC>OEBNGv)7!W2<t2D@C_3f?^o(I~
ziZ&@K($6x?XFHmc2B63P6p>oHEO}%k?)Y!d;_CBRCPY*zah&Otw4Vkai3u}4*-X}r
z73Kw>#f@lJYr@1qy;W*21T+&lZ6B*><1F%=g0p3i@JuL%Z%E7}{X3HZF6}B&RZ!rl
zP8TFFWUE+SL;-huQ3sLyJ<Oh|I93(yc$znQdhossjdy&p!(8?91i5h_Dhc-=9+u?;
z4CEV8J}2{k_?N#VS6I{YoW3l_{iXLhdO?<RU1Lf3j5PC}%1i$dKJsyqUGg;;lxw>A
z>`(8pKYB%md$ltqd|h~(SMu(us*;yLD+HhSOv3t3I%t0*irmWs7Db>mL8ajx?Tyrd
z#=b#<84yhgOo9#*ef}Joj9CNs{cwPj`b=E6<We-QA{DP6lQ6LtWFyM$pZvk)9MQ0M
zl;2fj9FHi^e_9}`p>OLs+as@neykE18WS1<q@YkkHLcvoIf2UZbQ|dMPAO42k7}5)
zSmfGzw6A-GxwTs5_eb|+Rj!a}CcDkpXTa=k^U2IXPFA_Ae{8=%j*x)o)NCX@#yG^F
z>nMHaEe1Us{u>E_=!)><hd<ujR!L&gJ{G2#tU)kqN&EbO01}oow`3oG;}V#nVTH04
zL_;7DV;9}DR|2I!7Ec%Y{BT;jOmSVXy9kmteO|;DQdpcaUH_VNjrD4CF5CIch4+j0
zAm+>yJ7OoB9)AMqazdoGp(E-&NGZ4R!L7PL+oA?N6iV63P&Ekqiy0)-5|+7_XjGJE
zMgTNZDkMJ5k$5f2iN=u=)MqN!Te;nYMm>5X2@XX#wIHu}iSL;iO74%*QLKj_R7Grb
ziT<qjX!PDz&WlK!Zhd>)Wr#(?0Dn+YoE3LVQ;EvQR`?v2yH+X*r(=}dE=Yd-V}Ku5
zhOOl>$WWD;$XjiVrlV^J4-?upv8Y&U;II<T(T!Z82AZd##U2ZP^?Ya9dy7h?g=AEX
z%7TJ`3ZwW-h2@rMquZ?8-f8wpG0lYpR`gl@?JW~0io}3(x_3@s2-_+6{wUtm^-HmR
z6_HvNU!GCB8j;VxSYDk<?F-r&^f0C~^a9IRW_ir$AzJUVf%UySJs$bVd>=$OC&U*b
zc>W>_?}nDmbhyUjB!iy6%xH5yMN29Mi|~RS43FyDqkTJRU~{7t(m(-ieI=HOQQP7p
z-=#e8rU0c;5c1~?y!-Hz8h60jjh5T5ZQR&qHi=XpKsK$<-&ChwR|csq-WYC@((^3h
z=GsG7fvfbW(dGQPCxFuB4^Ck`jy=15<+=#K!YI#N#$hkJQtD+mCfMA|k%MWl$<7Mg
zw)fDT&OlDhVzy|O`;IxCrq8xfpW+{n291lwNa9m+egp%q($%i&x%z;ysr0<KLs=K*
z8G09ME5)iD?jZu$-(|aheZ>obhA1NCw&v{qZ83_K28B+yUqt=p8<BEk<;vtk5)b%!
z(S+yL!BRN$r<&1C>xL7(NJf;~%nuGA$(H?)w*H7zAXNhjoJ!M2{L$)AV46DuJ0Ay%
zcDds5F#dd)4WhPjATF;_8;o_t;8rf%K6o3=BhG(8#urtF=|ED{F|s81b2jWga(#nm
zZ70Q11BlxqRQy(3Ib>SN3z<KL9S)enmOw@jLZ^DIbdIAYlTL8e%o&CB(dvOcP1i`l
zFOWJlc{F+-!{)M3iZ#y$VoWQex)Ljo5Zhxg9^W5@EU(gfE$L>-&k}?1^Qs@-Yw=H{
zvwjZZ;4>oL%EfT1{u_d^Ygaq!=0&R-PN082SqHC90JvQK(t`*)qpieCp$-2&rTQ{y
zQRMl%@`nF4yUMZ`UGX@7knNks+RE}?+DEja*=yMqW^1~+GbdQ2j6u3^qKhQ5%Fg_d
zM7!&%fO6Sg7^(}HX72<`pOe!`lze)TknCnrr`jqBwzFW8a#8}{E0Z12Gcmbpid|&d
zGRnS8GtN#i3R3f&lr-Tr%4m<+%PVN_v~W8PBOQT&i*0kgaW9d7uXw?#4~6(w4+W&8
zfJ6ruX&NKu9xF-+0HfRiSYDj9`A%mpl0iw?J4B8!Q&?+~fQZ<B<8;E<uge!nN<Nx(
zs2Q#BO5$C^q@9qD^QANC+94YAPew6tL<K*u?%nE&N<cdgJ{%Spir4F7RY~Azu~w45
zY2>Q4NC%vY4~Oa&&L+1!k1+oCpXO~KEYDYkH&B_B3iqwzwo};|sf9M9Zx}p<s(<~o
z6J&xWmEN6?G-d~$2JusjTfcJeux)^msS!C{qB5ee`moQk8j+hRS}ILBUDk5~>j1hd
zBQJI)Ec;RHL{#LXel}Gds{7hDPwUaLw_5*>aw=lD7CTr+$ON4#W08}ua)+{$OGE1%
zj3)V*Z2p#`nN9v?HD;vO2u&^V5lKz?Pn)>3^v}9!Md8zxr-*nygTzwCgHH8}b1lxz
zH5=3CVA=A#wolY!eKGwLSPsc1+1VPu9-|&4vNF2u&-!)MM#ps}vOfKN24sW9^c37r
z7-+cCHMn@yB3x-j?8=aU1v~?zUo*1?LZl~|)BAvn9!g4Rw{((nvZa=jjU=d}@e{0J
z7DUTjrrXQHmL6DzbqB&vDO9m(x4h)J+vC#auw2w`C|#+lno5bn%ucb=k&Ul-{a))B
ztz}c+c|V?NzCUWd>HdS<>}@of{Y?Y_Ktmc3Kwb(M1R3BzuKW56?f<;_p9B2=L2hPZ
zOXuPa4FCx8AJ6}DP*H{j0B28AwES10XxXSiZSg-Qg8+a4U~T!|C;LBXYknuQHZU}?
zcA_<Mv~V_Yv@oExbh5Mk|6L$Y(X#M=F5sg&k#IqZur;IRJhi?FKT0cMl4`BER-!rE
zOinZlde|mQ`I7@IUeBCjW+t={>m=)TvBOs2_Ga*~!?{j9cmE;x_>J|OzGYXz%02M0
zQ<mk`nEDC)VHJ;2C38V#z`3Z{$I=?fPP~7Xb8!4^DB5*TmLAjP?r<&``V=NmL?>|!
zWpg#=v3}3`TR3|j>6kZR4D0*I8h;$mbz$9oaD{G|!|m($k)_2(azR4k0trzbm36n0
z)ajdUSGv8Z{&1C;n9>%J5L|ej4B4IXELLI8K}LMiz@z06k4u~5T{5Y57R2-iCDsUr
z&6R7F6>RkW&yf@W1RLJ#LgFX7&fjIdzg_u=eFzKRK|v+h?v0iQz)xou{1mXIdU{}*
z7c4Bp2Wtkw<VqPhC@p?Z^;H4UfH9D>3>M(r7WpxqlYj{I908b|#sJ~!!M{r3oUg&B
zcNlxP7UhJ@=#)l@F^u&q_(l>$fL76s6)o<jG|GQ_xr`6W=79h>gkp5Y<6RUev-3Ar
z4Ehd;%R7}{EnsKteakyClI@Meo7=BA6v*~1d_?h3gR9+<$x~XnJh+c))ys%e`=u4(
z$0?gCQs26p`v#8FMtV(m9X6!+lwxC4<SX-h!saCIR6o*99|X56zA2}Ib~xn_|2hoU
z$$^(X5dfxCJ%x*oU<kvMkP0|FlcuR8Gl|MQdnXF9GjR_WjXm=wo<fdoWzLZFugD8g
zp<5%owV6|tx!fuTrvAYNvU+9#;6w>Y52G9hpr91mkF&w>rh1W~<pNE5cAqYxSCO_B
z3_AUo0GaM<yJe6=ZOAH6wqwswv2G!RZ1qAZVGS8iVD;uPqyZCKrv+T+I_ypRN}o<#
zd7ve4;dO7~h`9HuucN%g&!z~=hmtdZ(VZ#1(h#4R3g15jsVFt}wD=%nnO8I6MvI4I
zc_KeRAl!`zsv~XIiuKAnPnxix3u(_-URy6N>_~j2*Lmj*DcG#c!_JACs`B6M004p?
z@u?HcHCV5X`?p)XUj4*A_Y$si<u68e>Ob6^mQ~L`SRAhSQcxqNoy4Bjyow=FgzM61
zp)d_um}i`7suzU*D};b(qhwHkx}Ag5c$vDj`V5=d0mN;Y#c8G#YYq<FN{gaC%@4Gx
z%xYb^dwk`p9yWpBZf3V&Fa0E~qGa&YmE8m-oLbe%^dXGVoqV3U{Hdep<IS*H(w>ql
zWWyaeYU+}~<%wQ9>;fI5P<FEQ!I+T<&Gj_vU(QH9=S#;{av$Pg<fHdB<J#f6WzhMy
zUv5XLS2{_M7qtED_3@v)SI+sjlC!`705wqmmG?^j|8O7#|6gzP|2hy4BWsiYp7ko^
zf4Yy-1Zm45&9Q_HR)nsPUy{XF;x}N&%vD)SI10H-b`Bw8VnQKAX25A-iKCr`=%zj$
z%nru{VgKmu+jo{cKV63B_EzMkS-WWFCigF3uP->ihMgk!<r+6*K?>)&v1Re4-NugY
zqymaT-IjtlF^yU>?~pRGIR+(2*BASrx~0j8g-dGbB1ytqn?5byxF+UQpN+D5x~R|0
z!pANwIjEuVOM=W(V?81#bKr*9HHCn2pOw+$LAb7z=-CVrjX#U2(F&DFUB}>QdgF=A
zozo@QAb%01BQ<;L@gcMEXKZMu3m9Y#Y-sa_STI|BRw!-0?DYb%Jv!;Plc;4;Hx?-=
zi<m8ku%aeo!pY*Ajl?t}aZZ;YeYfipuyBQMR=2)%naSHgD%#03dM6cK^>N>YvN$VF
zV**~vC-M`I+S@vlspi0rR0p`JOb~W<v@x$^%THO<<4X>6p#*7ZS>F{fTOp#5HFGe3
zno{ECp1n5kEX$}qaEt(!UC$x2p?>SBxg@yDOl`f4DKY;34JF<Wy~FHR(p@zw%+b*d
z_{db0=E{<|D#V@~S0>8Wf*kV6Xv0iUDTCIE<>WJAihreHT`vzLX5@RRN2bcq_D<<E
z4(hUJvS1Tr09oF{zhvy4n%TQs+$f*>(s2He^}Z4y&{nunagy((>cgiRpE1ZC#eNR;
zk!~O*eyA?}2MGNkd%2N;Wxwd5C)hSiUulCGM}dFSCuewb@DH+0bEyj!o3onBkz9}#
zmHe&&55(fd0DW+64^qR|Pw%-Lg%(7$=H;7VJq?U>`)A$h!hJKZ+4iz+*=Ho5u^>xt
zi~jE$GHGoGyMdr?KYDD}sb$h50yzI_7&9}$K_#XIvf=W!fHLyE6t=)iTwU2I3B<&F
z1i+)A?%oGO%b?z_$OKy8-!w(M`PnQ~0vB^Z5f#DlS>=qxq<Ij%>=`Jwl_LI(E5Dh^
z6aK%_Y2IdjlWRyq7}4T#DF=`yW_S~_?jISYis)H=uuvaZ48)1;fO7RDw*9E>hM`P=
zx}g)B!OYIde>o|_OF#c|J!ps&P3^)Zw_*g9Zem~;II<BUniOmFn>OlmQ7X`!AVxs#
zB&=9{dO%KvW*wHq<c63a)j^tr#8Ja}Q`Q0Y1LPEyp;z{EJr7>so_mY?!iIdd1<Xh`
z$54yLlMP+mEYVcz-^}W-Zn<&=mqpoX)Z$<BUw~gt0-s25U3vk9-b1(4ZpR-FjxW$~
zCkJ$FSx*{6qGvpaL{0)#Kr5sRz@K3AUf9g$?h8-A%KshKFu7phBqC3oo6nSSvS(}@
z$`>d8h#B^$(T6Iv>wx!$;gf%90OEGg5kg6@Eaq|#$bpLq&G=rOXx|j*D2ShnXjVl#
zp$oIN6^fTxxQM%s^wdPGtss^+Rgh)hGZnJV$JM;+(6bmm;Chi+irXW3v{ukq1@qY`
zpKe8$pD;kqxPurqm~hi)S!o#|2)LUCgC7<Ovr5*7%wd~#J?+O`5D&6}!bii5;j@3?
z$Ht(8nnjNu9_`f+48#GMl@XPa>jwefG@iw7!pJz50%WQ9)5)q5s9o#{{0<dux;QVl
zp|OkFXwZ@l#voYqVcO|IW8VYo-qpgVQ{V;SCMRl_bPhv*u)Dlm|MCp@05AFw9=nej
zY&TUYc&Y+@dwzc_VXU*RZ%!<v@7t2SNVrD<^@@;7hK}8XQ^#(JGqxBt-S|43I{G%a
z?^U>T8A(MYJ3m0sqh8C9&~<q<dPlmG#q-b>9h8@z;sHViy9Nf=C@BRl6zm~fzDHou
zD{Se3e0@8FOO$Q{uBN6K`LYkesZO*HwzSV|iYjkN<<3ZoDB-HR$P@Lxkm{ZRz<^k(
zI#ftr!)A`u<sL@H?V%G900rduT?<?f&c1;^gsTQNE*+;QkPMCDeZFa%NKj$i4?c+2
zgc#=UsH(g_NdQ(=ZbA?e3zo2Be`(Sx4Z~Wq)nd*qLv<ar$xqWrUMb~a2cQ;>o(K~`
zUVN_X=h#F~-KV+MzhZh2|L8jH5B(8@ug6pb-R7Q9RJ%h;5x~@k1O!$<fSIrp*PTfY
z=rZ%u2dOI4mI9L}5CD3s*u;S_eHS1?*!w!S3dDJAUI9MZ()T$|@j!bcBBp<Buap#X
z>|N7vhxIW&`A<35T74q?*}nWJ>xR*+_7PNILlKlW5zH|{N<AvWf~Jlo=Nt!c|Fy7-
ziyUgnNEWx@+@Eeguq=bUv3qL~D??Tj^R-B|^U)zsWRPvrvjB}`+S35c_FPygJ?%om
ztlCA}kFxJ-r<Sj4ynD>hXy)9pNCGFHn@E*Vi$RRVqSZw(TJv14W<xZyd@kxGpS~?}
z#!fy7o47i;XsTI9E9YK5noDsF`PAcZ009o<mn|?Hh_zA!73*RDe4fW5n|ASFbWr5|
zwkkwR^X$jB)>#NQW;FEWz#==O+v^`pTYU7&jG=1EM{MW@L@hzC%8PsDQbVy1((4u~
zK72nX*K#=ZoEz~S^M*!ZKi};77kp^>jpbwS+xOmL#cnYnE{nOH9bznIu^!>Y8V-~C
zG*4!G0HLSo&k-BH@Z<=y$sHJZnm_Ket#2ud-6|SS>#4?^y|Wd!yq$A&10kI;XcwgP
z{P%646kCvls;fX+uyuDcLBV{L4B4%nGI0Fa@NpuRZc2(Cwh~8qHK4L;jpg6Uw@gez
zw+WFcb2mMqRB%6^gxY0BRBYNk(PM}qY0<;vcZVFo4{Xs*%;g)As~Y`514wvbe{P5y
zl+yedF)tX!zspXWm-V11*#-S?4&wTs5?fcQ+D>2zH3G7HoccBQ)UF(Cwtd#R%1Olt
zyClINi@8Skk?l3}8U@z=0QeEv+}YOHK<%}v9BxQYO+PDeU}evp1z?QxX^``1Gu6N1
zs0?kxaa6P#{UU>D>wlbZvR#g1iG8nqUsdtk@7$}}6Q!37ke31wmVOT<RsRh(o(BM|
z{lp5cQVPk*EyqfrGI^!M5#ke0VIDy!hW7H(bwsHYD<`Lw`RpYUZvuO~>)+rKn8~JL
zpD+O^?HLoL)^Fqr%eY`=`_h0HWhOaFM=)WqiA+J<{fiC^8d}OsQv2zChyM>iXxt}x
zfeZ-%picc?L$GJX!~YEsV*a-w*nbDz0Gh-t8H)Y~HZ+lEupFdExP-rkkG${_$Y53@
zR*3*n#3Z0A8M?2YtDZ}b>k&(FCO|+i{FkmVb$a0qgua*+UkfKk-^q7dq{wkewARYb
zB&~9b;abZNwFT-<#^Q4gwl+BtsPg{Y8x55ZtD!NkeTFv14|e5!CSiZY05?m!)jpgM
zSn+_*7jrT(-iL8|%u_CioIWAT<f_$w3RB`BAoV9)t61&XA=4gcUlAB(4}K?VH061Y
zj52vFS`@X;Plj<Hi+pQ!NbjvH>Aj{KipV&sZcrF^y5#0RgI6N#IfeOOJZuB_U*FtZ
z!~c$c@&DU5XKi8oe~Dc;(*GCqEmEF{*`SB%1Rv!?;2nAM?<%5!LOwNoK{F0_{X3qJ
zH$uBv@S`i)j5H$K4C>kNkAQ<I>u|*vT;75aJtn?j_#Cp_ENZ*|#ajah6(B^w(=ons
ztQJYUf@RzrY(tP8Iu`0(QHK&gM<kdwUhp<8(409CS(f=91sphgmoFDU`rmA{wkbg2
zi00g$=s?z?L&T)NKv^x6cdfZcINMb}4%!IZtQ3c3`OVWBc!~Mq=;!yYh%XjEeG`9_
z7r(7)lHv8Lqyx0*Nl+~bn}E}+Yt5vzzjHeJWY`e)EF%kI3TD;3(CrJSEfBRXJ~Z7u
zibuN}7^oa-kbX6?Cq*~FvsLGLH`pF0oz`eBGPwK&B?9^YU){|{M2a3$ij;1cpD$-x
zyAZ&2kaf-LR9I$8rYn_wC{nR7tUeE#Kq{0lGTKgB-&Dn$y)Q4gF(jmI$19M*FhOWl
zncSu=S|KgfNt59xyh9n<SaarnbeaTZtnX{*xOMH6clK{?tcIhwv177+`yZjdzr;Ud
zU1$uGFlF{8->N-iX_9ETm*YG0pfVSN*F*0MZDZBEXuOES!V302`t@_RVLnex1kcy1
zu@n-uCJS1u4<siiKA~pbT!{8<pT2M$ICp`<fc$Ec06h(a)lw7=o!f#CMfdC0Z+vgu
z{C=}D;1DYb<Q-4H<~97w4g9|nEVloLi4p&|Cgy13War{&^nWok{QqKRT|Qg&ht2WF
zT}00~=-qWkrSpS1DQ1MuOayK%hdJ@8U0XD787d)4B5aY=cPH4%WUPj`hB@{*#t-oP
zfglpKvKF+)Qd`vc@uQz{>7&x0BR}stDPP?THd}074<^18%^&aH*A)dFwlXf0vB%cs
zwi~W8+v!FI>vSCjR8u!S)4o4bA8u<_9}dsUK3P7_ct5@kzMnxBFES2i5$y#U^-}42
zZZ2OOUX@s{C0Ei)$|Eo(Gw>`vX;;;2-E<xM6gRiO=UMc+%h?(2d^x)_<#5I8#x{O!
zi!!NKavmz_^;^cV!`QBG-%hH_PoUpiHE<eQH<6u_+|lU;cPTDQKH#|ka{3B>3^<j9
z7ZpJk>u|+F1s7tPiCAR3Zmt1KH<3~vSZ*{Zdf#^c4v40+*~0emj^mC}rIb!Sl$Kjk
zdV2bvIe~EF{N2pb9w15SrfUg5Sxde^beW5Tcd-A)NG0BM82W8Q;nSn-zhgZZkH05m
zKO8p@a41+`S*8{7u4MONob_~ca%9j>d<Yp(rg<j<o=oJhN(~-Z!-;f{xtjPOw|TI3
z6pUwX7zc|VRe5ZozbfTJss|<>k-vManffv7;r47Ae{{0cg8i!zY1;;lr}-4v>c#U0
zOvrUxD`U@*d@Tw3VO~?xeGWa{Odsb))uA$c`QwR)+;u#A^FZO*fh#ega0K_%?Y2Sl
zFGEjYDKf(K6H)X6OFM-mX>Fs0U(|I>!LK|O;R`C<v}`&j@|w6^t%+atK*0zC*65bM
zymJ~z^vNs%w`Ozntze82y}W1!I^`XpU$-`?27)Z$V8!n?ZSr5kS%x7Ulj=u1V827;
zJ8IrYRYj@4>ZbxAcF|UAbcIfz<a0at8y9e1TqlV?MBh6KDNs85!1E3#N5zy}9wMl<
zoKDIc+=`a}v|fYv&SD-WS1{`$;yMbj`pV)0zb8c`_M>kHlTC{Y0y8JTQNtzOt;Vx2
zU>WH!Hnyjo01OsjK?5KR<rD)Qn}7HSu6&*CZ%34>GO#=gUwz^x{{XA=XP=>nzSHa=
zQy&$+phMcu3uJ~Gws{IGc3;rjy+Sj+(>;M}EX}(NTy=QcXFN$}X}UWrha@<3oq+_P
z4lqHOAEL|}5@_C9Ek^EC8LfjJNIA&9>UA?`#`YSCm!dvtp>axR8)G$)MP6d`TM-@R
zyNZ2G;OWurf{#;IZPu~(U)Z5107=+)-K3VeFa0_LKgN$4lQ}{ZlCoIoxxSgWyy{R5
z2Oc?lS03GPy<3hr_oh$aUd{#C*>_FEo~Ga_AX9C9q<lxyey*Uy02<1`1CAu`gC42b
zzH|j}_BUGPZX<a4P-`LHfH(QQ&|}nnVG@aYeQw@2$DY1jOnfD-SF)XCQC{9O98C=v
zGS?ab=ifgyZfyyj-S*DQD(UZN;G9Zdk|o2M)0Vd{^~FhR=_EB5ish4WMJ=nrHFIs(
zhU^ZWtr@A4`^OZhLnOh(1Dp>aYmSj4F={p`^riZ(1nge|LdL6EIO^nZBG+*Gn#S8y
zd`l58AWYoMPiy%Ch_NhoMp2x`#(5y@kVa&&&eZROJDIXx7n&y2`MAYv<;L_cgOnB_
zR1O^ylK{G0s0SEVS<s&GfI%>yKq$Yoje!GvD#{Be-(}|^B57~na5pf4x`vipl22e&
z_DSa69=t*1A26_wVc!JaWpd*E*9d+$fES2(TOlikkC^Z5RY~3em8nRJ&9NgL3Qm7S
z2*eumB6FUkwVneGS@0~Q5T!BaaisvM56bHm=rk5SBTVfsd!uW3#XApd-Y%}*Qu7pV
zFfTbfbHK~ZLNkDAR@*JK))K><xk^^fI6Q$iz|^g3+zapi(v19&whu6p*pM^rATO}~
zQj7Xb%5A;?Q{4iYut|U*%f$5J0K9xWaO8#KjlbKwBR?l!BXp`r5*_zJ@}j)7!ypn1
zO=B5&0Jbo1vM#E6qp)Ca{K1SQjN#;5{mX$hA-P+%K?}>e${<SAU1#CfF!nA@6$)YH
z2bJ+Jg&)*=hq<^;0Iq(JQ|OKsn2EU#MuBNE$6=G-a7Zf0>zdG8+RYsos6Ti*r-6jv
zhc?&|uCX7K-;YLsqm3d2E+<OLr^RJ*pxh#tltMNh$IQDO3#MCm03|1i4%&e@75uUQ
zzl5=j<ukr!W1d#$xYCc$$}8TSsDXv8zQOa=*Dobfu*L9HgP;d-pF32b`2J!sY!zK#
z-}q3_|5gbkD&>khVFKeQgWbz>DN0u(!fbHy?*55IcZc_e;kWx2epm!_fY%{lr#8*-
zHsIE1QI%y3k4Q+!^o_nj-b5v$qx)7)6m0junH45|BSX&JcYU#c^!@HDC%oMzpYiG9
zeq?bH`HI5LR>M7^pe8O(lNI}TjRt<^L$c(Y4?90^dH_N$z$Ha2cymqU6P`0>g^8Qd
zyk8Q8jmcxw)X;HD7u{L4*r_SWP-V7Rld*;HcOLpOMTD@renDGZe2cVG>>!)uK}&N{
zZtVOf7JX|$z?PI>p@h~2tG4XXG_se6{?7?R38Bk-8sE>P7MPhe9pC&b-cWIR&HT9b
z5O=XgSdXC4_yq1&1ArK(JX=k3)L?dR>T+k)3mMjEROK*fxdz_Q=vp47g<Acv5vbHU
zAr0(*he(qF#<No%B(=_o05L*S8D^t<{Pv{*2+-&xLm`ZPyLuVMpjDvzW(0R!*P%5<
zpUM)g06`R|Ym&xpyd#=Sci7yQSj{f{l4Acvjg;MqmZ(5GLf(e>={bQc>jEK^xMRDa
zdyI~H>9ealc?H0H+99|{;=elrhPY}0`M;u%6}2MJwUB69z2}5fL+vv%G!-uvj(_`R
zU-d9st<O1!RdxI*Fta3b1&Xp2#DqBh*t*H+F}HQd`)!S7p3@~SU)eqWnN--f9niEV
zC3j4xO?Ot^z3NPsl@JHixpH4RT<Q&!_C=b5Cz#72it!%89FlY4gW(igeSY8K>+(H7
zCIg#hE`|&}SDoXAEl1kV1S)n)+`<s%O3Y;t$lozSo%n}z3&}g64DoH<$Dj3U`$c?|
z6})r<S`1j!rt?+dj(uAGItq@%ziIe{&>*LC`L*uJ_#mt)LaOdJU%i*SPiEOos%%|B
zO2>VObS#3cPQ4rsSe~0kqZhH+vo=wOME?*%U}D&1;Ub+CG3pszyj?PlFYURaHtqV`
z-^iQ~1wy5&Y2M5!{J7Cb@`el}x8UsoX<O%oB2j<Y_nmkRY{Kkz&>T1!uXbQ8epL+U
zDb{CbSfy=FwVt?BQ{N>W!P`Bsv|YwN=X0=GR6<70CdVyVrjg#PT(QTV%@^7wM)uGd
zLjtt}prK%E_z(L=6*9Ein^31I9iqVUM25^#iaclz{u*r#Oh#*YMb$eI7ut~y^#-Ex
z(bxP!0&0S_sfBYHA5ulJHeTD>$>M^rX*Gcf+=^j+Dwt)W(iYZSMphJ9T2W{=FMOZ$
zH|FR`k1UpvcZJSLn3HdQ(@W~JlR`?PlyT5%EwIol0hP@38&7H{SG>hIBt1>*3zmxp
zTafb|EcRS_lwJz#bE?!V3x^V+<<{`?4nT#d)8I|T*u#*HN&1KO(o7MDJ~3t%CS;94
z0&{OKq}v7c5$2`z*_BRNqQiUIgdJ6_CRS9KQDc7Td%Iniy#{!FHAKPf0&38<SI`;R
z{%UkWuTR1~rKh=&K2t8arJWm_ufm|DK+6&ODEP7U**zl{+ERY9y=hutPRc!>$Yuq(
z!*e0*QF9ZS8ZVPbopsf}K{*LwLKCJ^&c$eA{%BcyGip$6O99gqn8DmFGf363$28z5
z9OErCbY0-WoInHCy9tqD%mtL{dC6h`Y+jVK3y6oz<M7EQ@1HjeC&IY}@b20Vv_s6G
z&R#eXHkXV?<<%#m$_DIIGufa$uB*i_0}s#Ye6dpX)zCkNQu&AD2o<_92FD)WA8OZ6
zjf8TJY$Ew5WSupJ!1p$KJsaJ=4WRwax8V7LKkgPo+h3}y8LY$n0Xu0@8hTq(#rzhs
zW0TgwE%}8hE*>9kUpGIWbY9L8OQkZzuUhqEOMvEKLg@oV6E+h|8W(c|M1p=1s7QKQ
zjZ>CalQ0wOp3pxx)hY2DS)2vbp|Xe+xh~rLn34CrTCMRm4*R>;glv`Rpvisfhq@=?
z@z}r~rlitrBKxyj&^YC+eRWEIjt|CBM?(fxkYNkfBk-U`i9_two=v^1qskWD%qIYw
z1B?g20#Pi9o&HP<^ye1?JdMF!ACLJoM@*{i+1TV{`+wm?!XEP+>~eylK8#SU36vyI
zdtrBtEaE{elO`a7ugVkrL2xlV<RYZVA=GzsX6HU;4*U!(gvNr&JOg}c`iM{>-J`Pq
z_g0}o6hlYQ6*h)SBTB%J-|M=aTWg=jAxz;N8|(aY>16q(Or!cQh|VjX356TzR<Tc#
z_3cD*5gDWJsWl8JOi(VI(Ot}ovm+Qe_zBq9)qfI>9=KKFfpqt}%k`pLpPMUr;Bdu7
z#NcL=0dY{%q0Y4}`0#)dF|M8Q<doe*qooJR(<ZuRUDhfux;)w}7%pp3&$IL2!Rxqi
z#z7#d=$)}?Vd|`jLwiRcj9O3aM5oDucwr>+h_@8(6W04hBf~z0yED{r7+EF{S#ym0
zrK;BMKSQ5<ebF;Z=S{%pgCXVH20HIHQTZ*3C(-g(lKK*cf&~O&_kQLFI<tHu+hXL&
zRuA~==s$HFV4y~OVi;Qu`)&s~aDkhak$20RE2(3up~Pg@$LxJHSr$n{sK?^4c0n#1
zAx7>K#`Ychw<^JH_TCk4xx&80XPK9ozxoGNlQ(TcgBZm_!8orqL6nOy%VC!wOwkEF
z8%nfo5Gj4(AaViP!i=eNHkN^2{g}R$w%W~oBwxm@XDm~9RXwF1ResF~i|TAA0JvRD
z@Eeb5HwuULVLpf*PkcV_d(+M{=KZlAgfAduN**8S%yT4AqCq(qs&T=|gYqs9C{by+
zMeWh`Al6^G8@F6Wcjav=*J;pq@L=dyFcT@`0rrNW@je@vlDX~I)VRy3MTe=?ORMC#
zRclisS(-AlICs!e3I>n+6gzr_6iRlrs!u$A^ogEKEYsvEqN6eb2|-h8;oE{r(Ursp
z1ad{N&^~&oxiZgNnJ;+W^#&?xYMF($Ooh&Jk@4u#h*?0af>;m46gZX^%_aaId%T-y
z$i=1@#W9K-h5lN*1>oU~12)ZXS>JH?zFJr-N07s`7FV0ZFN<;+-W@X)CE8XbUk=Y1
z-|pXRL@%e>NL5)80qt(LB){xBungc^R+|*#3Wv~?3jIixNK638k;=%8EGO8B_5-T4
zo%cSzV_iiR1>0Am_mfrf`Ut)IeB0hvM0G9pbrS0nod<f8XV%V#ATlyLnM;~y?ru+A
zrM-VMDPrNsu(t)T=8o#HI^*d@w_RlFF1QY^lb>?DO7P8?a<8#pj_0535kfb=@mB93
zi<Z4=OUDZVZ%TVj^;*>QKRiB^cZbx8>))4s6TYN#rNPdNM<Rxli_}Ngj(}ZST6}Ef
zv%M*8(CIuD9F8f#WnRc&+TVH2pWDle!F=YwoEi-lj7v%@K3s--WFZS^XId+V-By!7
zaNB<sJ%LI#ZIBM2z!rjo{!$E+!`FuO<*c<*sBo@k0Jkp&^VtdbjeLIqaX2~@9W?rq
zRcS}de4Hr3s(Ndz4`R^v0elrL<j9XTgE<aVkzNttU#017CWJU3&(x;E{nb->h7h*#
z-pYXjmm5h-J#|N!btvO%k0Iyr^2cg^#kQyo=f36?2Cit|0O06Yv_XW`r<r?9t}d7f
zvigIp+LwHhH)ml5yxAOfTDntqaBLaz&3(#84+H{!GeF5gxjRDZL#*JeZio=xIhgT|
zbH{%TR6CHi>IwCu(Z>4h*lW+B6KTVAn}oi79rg=_{Wd9=?}Y6C^rgTJzJ*`Av!ep2
z;VZ0?3Oh!ZHH<4SUS@meXlx$C(LVGgHgXVN<=_?xMB{|F9!qNYSQ@MQ^vyp-eFJRU
z-B`V1%b`hyo)Zk8x-od=F0rpaFrO<;D~S2qDGYOFpkru>jorV!W7!`2%xpDsjGVPt
zz{D!whot5>9eJ0%BMF5Of720&a00ps!*bxZKq(gHSG;`cJj)8)I3F4tEE=FmvlQRh
zao*<N(b<GaCeNK<b?==lnzBzIg1`O?PR!%5j?b!?^1ZuW5eGpXl@$QPAY?B{D9{Xd
zqBH8#aXar`@1akRb#Id<ni{TEo7tt6vk16~-o>FkisW!mAc~xbf@_t+P2oMW5)n?n
zXvPXo{;LixwDr7hfL2>S8xSsV0cBRJ`QShk?EsO9mPv9cnRXwO7vk3nn`baT`38`?
z4tM>L^pSs52Y&iAhH6kYn|q}rON;)3cqDa}K$C06{Q8^tX?Ify;Io&9+eK)KKR4#x
zsGT%w{Fs0i?_<C=@$Vj6mf-}QFn`9n-0@+s@#u!AoSTk@UeQqmg5#{zYlfVq<P$X!
zqEn_JQ?!tZKo2XXx-`mOuRFs}HqD*#K#LYDjY&qGx5a0M(~ESh57xIp+WFlJ*h6Nk
zKqo=ihSA*Q2-d{ja1k{9dh+1H8(?%;wcvNy+5v?cqY+IBov_KW0t+#bEh+Zoirlaa
zH7$toO1hA9uN<})XSOVe;ld9~@H22M#Z4J2tNxi_Z1^tVbkU8I$d*?NYvw8;NP->{
zeoP^_1L_lS8x3DhwDVb0%~RPuYPpo3*T-}lHieGPiek;OGcMdqb(bsy$pS*5+8~-G
z>9z+9RkROO1rNp3$VjH_+JHj746=8-tskp5^LO<Ov$5j6WnN-^OdTHePMR0SE$F(B
z3Lb|ZbMu6fHm|G;eD99j^rTM`CQUdZj5OG>_KO7GvBjB^%LY;#M3?aGb(0!QgP6CE
z6mMb#7L#Fa55~MUr?FW23CJvZL*52^piW@u5YAYsFgrMt@;F<vP&o;sL3+zK>lsgH
zX)9GeGi>Ul3WKpZyXiDOpo_M>&0~&};yWmEq8a=@be#ilreWJ|YfNq1Zl|_w+wIi0
zZM#$3_EX!oZQJ<f-N{bAy_5Gp+&S;$%CXk^H$3tZ$~_79eYBcyf5^Qs8%CE2DB={e
za{|n9zZby;-CfJlQzw3@ev^2Il>@6k8Ze_PSW)rX8*^(O3wFHS`BEfggT+T$oi~p;
zC)uKrLD#))T<vG~u~^8Z1d83jl3M_L3>k~{tt%2m1PMb{qW<w&y?FV++0WIexdpjr
zcJ(~?_I{)<vd`5Ye}>FKr+y4(dsy>CAT97j)SH*P$x-7SNRJH`zR!;M((CE08+q{3
zo3FxyVM;uyGcv%8IuDo^ODK81c^>#zF#H#^au`n<EO$(WuPX<cQQmM^eyrzNE=IHL
z8G_c|5iztQFQ3G;C~;eK;UW*Tl&aTm+O*^!JS5XFO4<uS`1>L+#9CQ$xR(7&7+ii1
z-x>`Z4g;jPuLrTsIzqRvQBQnHI6`O@b>q%dgmN>3o(>YwRlfI)nhv6*CFY#)MOvBU
z`4*B+^q1c{Znk}%{2baP4m~C{{HjAKxTFy;8#;NAI^!7I<<K;>7(fq*d&=Q&g>D(~
zBy|(vHY~bC*bdU0NFk+1lUc5^KUfsqPOCfQ5IUHBgl`hMTm1gse<%hIHJh*f)@YMo
zIw<r$${`3g*9-0$-OZr|V&H`?<yK#8rlcVbv%KW4kW)E@?GM#c&Rz(OlDHZpeP~1b
zr%TDmAglhFhx2my(UTs)3QVPE^K%g>zX!U+NE{3i6~7W<pDKrR>7uXYbS7URjGNma
zhg$rdZCi<Wx41x$#oIDCGmcyJny72CG91-_-R59~yV+S^%Cm6JELQ~IWpDl4`*Xe3
ze8dwa{S#{AJxh7-+1TOI1;=VS0D672W5P%PS+O{#b{QTSpChYLs+{&uw<zGx6cwXl
z18v1j#(+u5XMIZg21ZK|ify|*8dNyZhNwh>@BLyoLmG^Vr=zmUa-YoaDSZ1<u+Jk(
zYyPeI;TWkn`}v;LIp1D+aw*-Ck&M&$kyabxBaRq9+##~GGIWMQofFrCj-BRXO3O%?
z;Y%lJ^{h1qA=c;ak}D@tfQb2qh}Bn_U}R?(FvJ{G8Jb_(LZEGW(BdNw#ueh2lf`;M
z<l3Vo?!NEk%t@yr@8S1sY^&K(TYfR?=1Ox=2-QzbT)TXY@>Jz=>=eS;A%^!)tQ9H;
z4Pz~JV@7tC|4pL9aKrA0LN(soOkrg77*}+&urkD_z74Ct{O1Wtoo=H(dPX0F1*s41
z%<O%94N74c(lXo?(jwbWfu#}YZ!gOpXBP^vt^4pK=qOV)If;Uo#w%C2NRKmaMV`$d
zvKDD|6uW7-Tn~zeqpyDDg8`=Dv^dsJRjbbr7Y>f@2Kw(vpN+XMLHa2%8<&#=kjvyV
z+rmpDE!Hmi@jZO*s)<!M_j8wPqOP;rdW4KaTE2chR^{`J3-<b-R(A^@jxga9{;#v<
zI`2wuXrHfA{`}j3L@Y~YDm>=3+ciU7)YQ>kq4Ma=X^1h@qJ61uC0i@GDvOKzv0I1%
zBiFj<#cEaanPjPtL2CYuvf1gZdkO_HQqIzA{_gun=)0;^jk+KykK=S`HH=g<1-6Zc
zdE7|eVa$E<1JrzkSOs`ad~C+1@V_6Q^O`gL>c@!%(oT4^CXH7v5OzzIC%q4iSI^^r
zf#`YKBB#}5PUNenC-BUflx*Ns*yKS;^lBFFnW>btD__KaGcNV*cgl69QUB?s4(u@s
z+%Zf+2Qtm%5B!Qm&7er6`^HN-Z$81TyenFvHJsk&f)^;U`Ri5I7j$7iC+i2y^wYeX
z*W=~Nn$Ufw1|WHow@ARr-QDJ`o%>v;exR`&{gDw{_xf3irsL<_zom7k))b;iQV3?$
z*S=e%aTAXFiL954!MlPsvFbmViYcX>FCA(noWs08GIFLrm;D!B?PcuSs=aDq8ZhoH
zJ<S_}`8~^b{6U4{>1ZGJvs0)qfx5nu5pi|_iL?0Fex-Vq!y!5}O25rG6x8tU!*sSM
z!0u7jL80IibnY{-JFVnKf-q=ZO#bGstQeqbwiCsSMFMXBxf6WAUX}t0Zl~eZ&a@v0
zY$|*fTE>JKlnS!<G#RH+k^gM@H(IX<q0|YTiQj@NkN`v2UEGhqFF!&tbV);v^r5tq
zl7z{XHr3D>3zl*!^o{K<SwGrOeWJU>>>^Nb@<j!n8=?@JnibY3`cE7L9Pi>F4MiR2
zZPQ0sxf}KhJa%AWfpfZ51w9+`$!!<zQm83`Jwx~OrtSUq>=N%6*WbHe)!(W5k~)4s
z4*c^@!U<U5cGI7-`R|C;nRfw6!XY27_7@W!t%%i%@)z3d1C^&4q009Gw$8$~mUVQw
z+;43GK-UQV&1QF7{RPCI8{P;`2GV4cvkJ8O>>Ig-6H5y{3=fuda-4MOv8vKd;omhz
zNeeyo6xBP~Z!|;i(_2L!qiBupRyT>QugSeR*v`RIF+So@T0<FoN4hu|y--}Dh<PM$
zt3AMW;MuxkBybcBfI|{kKbxe<gI(UwtvWO^+w5uO(qTJ7wwS32&r85&U*ZVhynO~W
zzv9J?<u~tm<8n3C8mS^ws2$FVX)TTONDK(%q7@6p!%P|N2V?B7`Gs7PE>sFJ6GQi%
zbQsR&&vqS(sSlfi78YAcd}S;p2@3Ml@d2@S!Q;PmC-x?}_13^swoB_SH16N%I=j4<
zy;CsDHyrr_L@)H@KUpa*^pZW;cTZ%>>$A1axbJ%2Cb%vfa7LZBh&EnIH?~rdL#Z{X
z`8wIjqap~B4GQ~tDm+)RDWHi(aQ$MSx-l67y#Ly_MJY9OOGnAA2dR%n{B}deSS0cp
z0lci!KoPTKb-A|ID&8bEVXJUSz(W4yadFw|7H8dt8(stOz%82l?zN=30d9+^&a7ol
zZzHqJf-RwhcIldGV8C<D!tgSqf`y!rsbTKQx5a$~&YS4GiZc<5^<vc*mkoD3HI?2=
z9H8<oR*?rtaV}neM(vhksKTQXo0&b+`3(Zk47UuXRh#*^znF5FX|;by3z}^=YXd{P
z$cK4`-x9uYw?6^-1=A;=3O`lP&A-j1_AVGZWiA+>$ofWPqrNd%yKO*4nT#8-R^1=w
zqBcj8%AFxbBp@m43CSYIO3+g=oq~a83ljnf5>L<uJd@_Oi6q<d&25;a2TLNom*%c6
zhFQ;G8#PY-7wKys9K)KhqMPFUU+KQjz}_Kx!refQ<vBv99p1K<_|xV5qI{@C`Pm2H
z1}etC+7wfB)QwA6!vZx=KCe$D5_5&`9N&8n#G^Z#n1szb61eDJlPg{<+cno*ht_zZ
z*txAgnH2t%@&*8gR_+-CbP);3EFixK4U-Y^?x49*3{#7ghN~J!)4>u6%7d0&qLB_g
zudhJU6r=127q(0GeQaJRZaKn#DnR7Em26Yc!%V&bI6iL<n*7?O_kl-nyFm1p7NjC0
z##H#fHVyC*`O;Z&Z&nY}78nk)a&B&Cer{e+EO}m4brP-+N${>~FgjyDibo#szmGOM
zeu>Ftt^@XlLuU=n3G<HiW0aiaF)2|F%;)$Ri_d}c^X`<+!x8Xt5>q=FYm^Ur41?#l
ztCU<f35hp!j<6GKjeb}Q2^63X6`U|cn$&(+O}hmS=$yhf?{ouujscE<_oAHsPu8qb
z*6prQ6p}m*1J$2Z+}odRr_rw{mPq_6&VPx8mRiVJXMHoj>RgLv7EbXsN|hLnAvgly
z4<JP*Y{HHtHXk6Cd+9*xSSCYq=wm;Mn5Pt@nj~2MRRCX`HRE2DU1EPW?O76yAAQx4
z(5CFNKK$bkq;keI>F+dJ073CAN4y+BrBxguE{C)+KsN2A*ZUH(CZlbDU@4}_WyEE9
zF-u^4DOVocdd=8y9JG()%6#4ETQt$^EFhq&*VnQn|E0!IPsW1_J*6mz58c$P%@3WP
z`SwJy@zi0TsXtCZMIY2fR<?SR(m!7hFoFg}S#s)gxw{+XPT{L^XmCVf+D2%MF;;%x
zSWl;DGNU^om>J51tMPZH(D*R>rz4_}^!{Sb;djIQTfP++6NxYDGUV~%-0EI6D^B%<
z>>NK+d0=W3z_(@r@V?C+!=i&b$3KmvO5icB9*vqKH4fwG+SA;%NN6?eXHVTvqka=8
zRfArNb1Ex=xs$CLz7UW(q)8MrGeZ`VblfyIaaz6?R4CcoFQ&&MBUapxmD+kQpDiLs
zb<@h75cH>$p&$dLmxYrWkFyq_9+WC4H$@St@ArBJ$9zE@n_yh<VOOK8ShFAn98u)D
zk17Cl44W`y*;r5}2?y{GD~!NtL_v|*)^oU?=yN3VbgX&FeY;$I?G#hw&7ii&?}K%0
zzLFFn@T#FWqj`dK`e%<gJ7Eo8y*Xkazjb--(8yXSC#2xr?OB5add=trDg4z|UvGE4
z7*pgmpLD;0ckE&0JuFv(q?#fKcVi5uVlZ1)&QHqQtIAJpL*%P{P7$C4X}tG}gy~ok
zJ#F!xDDDllUvf|q%(9u+ZfbE0B*~juuU>hH_3W3wvyOg@v(vMAay*>0S<nbw_f8&P
z!Zh9`Koa0<He6k>e-MK8lHLq`Oh7JBW+RPzt{TkJk|Kyt^>?3<ui`-1r`RShY0lxg
zAO*B|H`Zzq4>2XVAw!fZaY$Wrd0MyCxKn^ehq^!-v5C6RCKwV<iz$u8RAT!JRR};x
zBq{nR>MUytvx$<e9I~~d6v^pR#j4@X1=f#X$M2f~B>3gSqai5x%VHV&fDrq`dNL+X
zca=zcoOO#cDG|<L(R|?@iuK^Tjkk!H0*uwnUz4~56tiAXh<k3X!ut_GLe51Tw08O4
z=Hk%#C=`c<Am~YLV{PEpyw(&|7?LoWbjJ|pv|~-8>Jk`jvPFyVo+n$=<NN-Y^TJhF
zr5IUu;YP9vk_zcdRv>@2^dNK)BbMc*2i)0eVVo%QwB|1kcYROL<Mm;Y)b(>m@_i$J
z%Wt>s`}4f8!H_Bjhf}Ua{{1M}{s#o-ow!dB7mk}TnUQWM(=7ug{TD&c+n->$Q48Oz
zJs#F(PSa1t=IDzv_pRfR3fr@C=I$VmA~o==%}X7rF~`&n!<5TTap?fYRwfM_Wq2i*
zLEK|p^gkN28%0+&3GX4vtTA89OyDa=)ZMJgfc|4l<+f=g6wTt;eSu$)Jwu7JIaY$G
z2l^sVUcE4#X;$AtN{)frzc;S-*g}KL*Kk>uWa__3k+_?bwRR;rxBj7(-+g!-wgahB
zauSYT-fRf3;LIT{gxB|}PH8v%OEldxWgjqiQ)Em*^NZ5!t_w}$<z3WwleqMcb?1rU
z(7!gRECtUZ85H&nW!(c{z{L(BeTd}*iTF2V;AXTck^$HWV%~0+WV5u%F*GJ}75MtN
z9>HVuFfn`!_Lpqh43yr<@f8I+ssIEP!_Cuw5-<57)57;Bo3<(!lx`<h5L&j=HnUOB
zV~g-_0OE;7^c?a_;8_8>{5{J)?#B@|`Ksk{jAwz6+w?&@{%;s0M!Ql$qoida$Eu;U
zGW#t@LI{Is!J>jFG$Pt*ZpD5+H;|g05zNh4>h<Eo8CLKn+#VM$U5TL7)>@n$^B%EQ
zj5e1F^@807tbwi$7mZl0L<!wybiQX)-8GH9Bz)o;ixF>2-Sy4<137t6<O+$|`LmG7
zkzhQLp!RERd*zpghyhPjajXR!XiNX?@OyjW6f)vrIHOC1Oh0z9SasT(!W=86jXAfD
z{sFSEo5>bmZ;@|RZ&5b#el_Y3>GWzowvm&_rNUOe*83nnGm6->K@Z}a{_^@ItOE$|
z$rrX1nb8PmWTUp^3X<O^Mc4T5k%kum&Cn+fNPrkA-C#a(z9AlriGj7l)0CtL?!Ubd
zW;ZY`(u&|qB|TZNw*Ccx2-WB3K3?@(S}{JF$Tn@H13m}WAL2@3QNwzM!jnr&Yh4T9
znDjfVKiFV)1JoRy0ES{<REkrCcNIm-r!>B}7ngML1yvP3FqMiL&42Mzt6lNkX$#w1
zGj41DE30>w<AaaL#g5%rk?vpB0cIQWGz#9RM7Cd`YQQ+;0sV=XTXJJiUrx^;Zn6O@
zhHMw6CdD%3P9S9LC`KVs0=V%KIYlW}uHyy%HkKX3hi2`jOK~3Z9{k|Ad)Fx*jL4y2
z=i-3yzuKiqpAzcnE(SAzxT0=?tI|*G)$@GFyq|0z=}>!oEPo(7cEb#`41`qy@S<jz
z9s2=^RWx>&)wiG{@n#k{t-_Gj-V4prnIOLl?Fa{RFCww&sf9WqAItlo{L((u!wQk0
zS(S1d*Uf4tDXNlW-@Clkx`FtVz<MA*1ZoVkb{P$~5g7TQ6tK6XJU(L&3{6qfL9QU5
zVhIg#2!RlL^Eprbm$XEI1QDsseu1%w{H@F!OYlJWmW64$CWKFPoZoFh|Lj0qnBVl6
zCN}uJ)lH!k(MpMMX$rQXXj^<Qt~v~u%7NO@h05TWf7u}oh_-`1vnj@;&z)qtjvLK7
z*F@5rSvEnUDi|;8aWGvzfktZ0e^9eIER397447|uvmTr0)K+brDb0ZG+OkF^q|Ovv
zDRH!N@y?|x(L{h;ysIV}e7D<;it-xu1&T?<>}+hqt~!5n2y8!?t?e8#Z!D3yx=$i-
zy4lCmh*Gsv7%R5`piBmIb=a=&24lEeb!|~v@>mv3O}$9oGTIXai?vI&16S_My(JN`
z=5;l<8SChLR4?<$0B)p9hC~I}6-PFW$Z~C8a>n%NzjC!Q_Y_ycRFxsA@KBAET&DAk
z#Sf6*$~g$#N4oh>vRG-ToThgF=DK8Jhqz3@=vx{C_J0L}Z58Si6oC!|s9Lyq!zdE@
zaue0HppzrD;N;#HFn>F<BtD*{zUfO!?A7}(1SG|4k`GDm09<wM^AP<=5NU9pUUDjB
zm-~?>Ap43_z+n0{u;h3(>-MFwBf$GEfi1l%H*9FtBE}9XY09y67{eJr<TkJxdm#vM
zdB*Zl48k6?>hJr=#~pA3A8?|AA2|Rq?ml_WqnH9S2;5d{NtJRI1iXC?ZbBCo^a%OL
zw>V0Vu82VI^@uo8*iY+bZJsQK)qmMcpq;Go_*oEpnon9us86j24tH3%ZXO}itj;;}
z9MX;QI@>q??8Qg_3D*@j$k+cjNezLN5E^rS%%-N6<I`aBbHAt{=RG6$%2E;Y0ig<5
z*lwuFHb+b%N&sTzT~!;>YX1br568gcR}tRv(B4H?>i<wD%Z}bcwV127N{iXQM6AOR
z_wO$1bF4S2kJ@%(1Z6T6aiZ&UJAC(8f${TX!wZ{Lm%BEcXl5i0Z4cfj{7Fj}D(6cZ
zc5c}+Vl4J76_p#S&Qj2B4G?}+Qu>bYYaII?=O-5Nx~Pi6Os`INfM3($%S?3in|{bY
zvXQsDU8T*AQQ>gV<870v=2>ls%j(iHm^1JM#xO4KNFW=WY)X@-u3iB-mZ4>FuDoV!
zF52@@u>WjrS++;8Mnh;Vc96r{;n|U!t2+bf5~5mS)xh=IO-j`Imm<0?#<Lb0&jjOH
z0<zI3#Cw<3sVm>YM=CI9DzDxe9aUl%D!e2i8|zMwopodl>gwRiEa1SIM6AQJ@en6?
zXc&w<#ju)eGnUoM7}lfrno@z}cEK^)A(%>jfcI~^)}9iiNMisV+)X&jR}M)tU(Imu
zU~r=SX%wq8L)jv1!JY3VjXJRKMy)9l*C9MpMR`<HMN9iE;tA=p=7n!JA+~WMwI9d?
zpa^R1(+c`A&f?B?s9$Bp6;PifLs#xh{i;ULppz~*;W>rw7C7ITBe6+)jtFFl0bVh}
zZOPOTiC;4!c$y_PE7j-DWBE!_wUfA7{B?i;-0~cfu++$FuMvknqXx_WnNREMfO?j^
z6=;v4;?wCY0lx5t`8&;?X(}#R+zX)NQ5Vx-%|-&`7&c<rr^<M7PXxh++scF}Jy%R8
z)y|TxOb2O|(`IRWG>PDCwdE?u#(uqR=ggh{fa2&wf22B(>y4#Og3>d8DnJn)7@FY)
zWYjlWoTLS_%u6qi^@`d;!m6&?#@;mFHvs8E#t}&{HvwM5n--U=^!aZlrC7q-qpZ?A
z^zMUs?6a%aMqztc17K-U(ZQeIH%l`+R`~P13>arNcq?>-(TQD0cAl0^G-0ajNG+*#
zb%~+(^$))m(!$SDPFulEEthsHhnFdCY~JN#xWpXJxqOyRM@a-MO^MlxV+Aq%HB4s1
z)S06xG;UH7891Q5B%hk;BEo%XmcJm-7a2Rm@oI|r0`}Y36z*8%uNTGYeNCQw#aGm^
z^_odG0b@XB`o&C1ME0Nt56O^?^*ehX=6UGxR`+eM<|#qroch-hbqkJph>87dkcMw=
zJon7?>$7?zeHA$`rL7qH#y}#iRK0en8yQ<n8W$<9`vC{#zMYo2TcxoqFI*R2k3apz
z1Ywz1Z~|$$;CH3Vl{bMXSk*Jj1g4k2?b0oC_($J*AZFQX8KoA`)?bTbrq+~`%`ZW}
zvAx}`RT8|JPl!<HdRLR&_A0_>y7@cj&|ASh{Bb)ht*X5$h76JZI$`?wL1>t)fGUti
zhRmd9XHqv{VR5K#bM~1@9(qLQD`G}H0mD_icJ#-|5%?>2qrreqH}r^mOHM~dC&qRW
zF$K-jp&4<l;f4^wGtiXOV0>rAtBcTi{AG{XC{p-_lSR2Rh2I|^0c1RFGQQAowIJ+-
z!_g*T_UO?XjC}bW2f9ko-2l@QI@6ks<kLQvCU>%5<aQKd&3Y;)0K0YB@@jMAY?u$~
z`m6i0)9iN4C1;Hf&i7w6fq%@*D#bNcV7YvMCb|eC_N$2T5;{6#c>Bq!{}ftI+wcI$
zt9f(UV;-WbX6h8N**g20Asc+Lou=9Y<Lk$n7dYs8+HDLRf~h%rQ(B!S$?W?0i5OKv
za7qsp>YiHc?Q}}6)1M;Ggbx<<XsSsD3?Cs|79hA<utY$b4D1=e$FOeMp%XN|#_5)U
zp*<d4m3mQsgNK5A@CFqH;E2lQH%{S(d&Vq$?+H9#scngb$+29}eA>K;%-rcfw63O8
z%gn)iAP)UHjV(w<Pz(mWQ%T>Tgtov$wYpUWrI5ws%==J;PugT`ZpemwWsc|A(HPw>
zkmgo-^1a=p0*)M0ZTO^o?|h1u`}aH!ASha$o})UZHTz6><XuXw@yz%|bNDV5iQmuT
zMF7)#xKPsC$^rVLNV?nu$-s_bK$=*P;^L$Eo2~!`<~PnM187?;*tQ;HL~B)oI<wAP
zZ?Em3XpWit*d;;%QK7>AE*kGIl=bv~LoEA1Iy_3{VAuild!jD?n1&e)m1u<w_KMG>
z4}l|Gyr^R|3KU|1-xqw-Ych2hk}O{&eY6k;RPDX>Yz*qV8JWRU3aY$zq{7oMdlcZt
zlJ=zcYC)PyE26wvZ;7;e<vQCuA6`fTz?~A^%P{`#j#J?w(b@=16U)0y2iJL?$A>iK
z8mNKb#o2S}(>Jxv0N(Y73VU;X3B;j{A}&jb4$t(GJUHW6XLVkL#G&WIujk|EKlp>j
zOYUL}BM?wN@c)%n{KqdbDthw&ut^mE6@PGYHncJ|x3e}eb^Py;_<!K=-~T`*vgZ+t
zYK<w|4GzR^$Wd-Y&J7R$u4YLE+F8*ch|}y6F=Tes@_X@`j#alEtjGe?zYRXCNybUc
zS$4kNf5-S=+@g6oW_I#fD?mOdp9~g(@XUY8{M8Zs>cVOt0UhqDm@v*y5q!0}OZ1co
zOYVN}j`Yq@a+dbCcCpw!o@c7w2Tt$VK7~8AFlxKODP3t|Nw03FbR12C^=HIZu<EuW
z=Xo^cnRo~7Mz@ua0jW$Vos4)KYB&?#FqaD#xiXe#WG{~XBZ1(ZX&>7e!}qo}ywE+d
z;+a6xL+Y40(e>t3FXm`emoZPxit}~bj(f#GBF5GO&7V_};WWc3)-0k1!KKl*&-m6D
zXi(b^K`QgP8sMOm3nLmf8*1Qt?0Iu@tmZIxXia8Od@gG<B^1`cT|VnX92T_iK7%a#
z>B&^Tabhs$_x>8|XdH;~N-Y!0384wIlIRb3WcVP<Z_>@1jU9V7iQ%ITK9=VVPv)au
zv@Pb8GBE9wiQH<la9*VBN~x)b9=^aUs~8z%=T7;?ieG{+th{H6sI&RCn1=`}=bPQE
z<D#j+F)E7>IF3bIy24Iq3fwU5SSuvE28UQ~Y723QH^59Y!!-9-P(y&s)K6L?Eh=*j
z7X7K+^mJyO2*I7W6^k(oDe6iI+f^PnbvL>*$i){4OC<NCbL!h6*MLjU1XTwnf0Vil
zs%MhcG^19~PC*^Bhhg!!qS9@Pb(P*?`%3u2&T~ZFRC$JS2s=Cm9vi{Iu?WWMv=Gmc
zK;Uq-hJ%53bf>YHV?9?9TBnJ9H0j`NEl9~hCJgeHHM?AJcFhb#t6~t`XRvPPFb)^l
z15+=T8$mSX?duO@@t)vyqPq!bKITZ`ZT?m6jY>v9bf>0GL}w6<%Dea2+ku?oo!m7}
z0>75E8YrV>FWKVZS!;6K&rasF6a9<H<w0|7yCIP^Q=D73Ny)V<lEhydA`I}Tb<g)F
zT}%{fMDd-CERUNLK{o-xDX@xz$83c>sFt+$HM{CJD7nAVsmoL*6lFh2zp#o@krJVG
z1PjAZU_YOj)0R~3LhVYh8hMZ6`*agc_?|sECJnJ1Bnp-2z3V7ao@hnXuHyub><HB;
z2X0^uD`^9ibI>6m_zw2h*m%yWG*>%0pg&MKIP>Ap`8)7m&aarxD<{Zie-s)erRq9Y
zWBmq7IoL3u&c1?(Ws{X%pD_f}@eBgaOvn2%SEX#pop?3x{MM3sh%gRF<1^eC9}1ON
zYw~*{4uE=0v<R6BZH(fArfD?4K4mn5qdL%_R{ALv=pR{p({FxKnA)7ubz<5~Snc?p
zK$;W12ulp42~xF&jR2@ru|cIIKk2YbI)d#oBhz;n*FTq+*6rg}&NsH~$o`5JzaLVE
z>w@}Z!?Yy@`yfUu$Cbiw+nUK)=xTTXQuOjO5O}1VsahV^6C-zbwX?g#j!5R3d!Clc
z=3cVPH1n7kK>;XXn&yE8eMiZVbECe%JI%Mugv@Rh&wY9W7oKyLQm@#=UR@D!pATgE
zYdW6eS}l;wFhRj2OuA$X?JYXT&*E7wt5wc=??%&!iu_27M*{c2tOTF!TYeB#!!b5O
z!INEzTg<RK4h!u~yV(~sckOeK0~RqhM(O*1GD;Ob%P;J&P@+_8-wh_f90Ie%7m&yQ
zYK)6w?q^`>zopjN8qr#HAkO%M%>z6ATO&k*hay6Tq3f&E2mB2J<@Ux@dSGVq@Id2i
zkhnVtR0?LZkv=UZ$fNmurJ1H9(*ftj_`U<`;UUY*crMf(EG7L4nSnj9N;n=<t-e%V
zlhi$^5s8p?kak)~uPhfeF4^As^74E6Kh&hS%*>+xKb$QO`F|sAoBtou_TQaB|8Bao
zg`Mqxzvp-Vi)dT&*@z__Nm=daCeDYHEUNsoSJDJiMG$>_yRYdmIR`810SqkUs_Lrh
z*zh~b<4kRi(E#%suIIAxr{AwZf8Qx89Hn)#>Uvq~gYe%(lX`zJ0_DW_?S`KwGMC`p
zmaAvo#ito>*s-d^)tz<OSo!OdAS$<qe&$GbYw@7?wWPb&HBDC;t#+?*2=eW6h8-aK
zyi|8_!Tjwn?c-MU>r=pxPr><R2&#ui^`L&kE^@>e+z+qvo&~j|fi9!sa$|p$7u{IB
z*XSvKtJg2{J^!42C_m`u-yhahf3egFfgjz6748U6ppDsJWl15qqZ=o5|KC>8P+0{*
zmAl{X=AtC<2i7?5qp$r)1HEqCcYQC{VF}*<BB~v)Qdk~wpp@aZTHV`(bGY(e$L=V~
z-u2bQrHup3H-4w;RnEV*_WfQ3De$@^-<F0$NL%%zAQ**A&Xel8!b{}lde!Cj4b%sX
zaY2QGqk*dz`;{OrjeqGNSMG>I?aP0+Q_)@E5{N5mq~-^zl|#+uZoruf!Cq1K?m*>+
zj}4=<3E9@k&H6%j4b@Dm!bjEHtqM{YbZDfazZUOpJL<!h9nN0tHOlRlpuOC#5=KYa
zjrsyzqQrVHJaa$ay2MiWv@FsIGCta6%{ubB9=t8?>2K|QK72fjifl6ulC*k)=nBS1
zdzhVNgGSKIy|*n;;Z-i8Y54RGXy-uv<z8Li-l0O<1r|N>%Av4^brzR9_^Sy1c)m~(
zMp&YGO5GOg)?Nc0f(?806TAW_#ykofY|~`-`qIZQeH_1&Q=~cj%MyrZ$2g0ryLO9B
zm(ob6BR1&J^#bnP4&N-Tb$B(h)tc4ACBLGuq0!8BUY$oM$bkv4*apz)-`TrvH~{wd
z(pk7q2lebJP=vB$Y((4FqH~qG;^J$Wvf4|x5$rk^xmeV_IffgANyJ<-WTd_Ke{>B@
zRw&Z$d4j-<DL=>^PD5Z%nsGg-Cw?VSr_CSA;K;BF>)o59TO=mP(ZC<vSAG|-obdP3
zgdf9E^Iqc|Zg-f<^n%bFhP$Y9{Mi8oBBNX4c(VcYgVhzch47#2%1|<h&J!Zf4fLU}
z#aZaRwmv3#e|!y74$y*Hh{s_bbsd$lft$1bopKmISq9`Cl1o`PtMIv9RYdAjRu;_P
z_g-x@ug?lR%Y;~^_2v^vhNr|o^ydjkE8v=IIyHP7W`7%fZ0+AuN7eAEs6O7m3vL8X
z;ien8Q*E?aUm4sVZ*w~;LSTmd;81uy`J9YdBhF{s$qL|m7YI3!DJ5|y^IW5>9$ml@
zw9DxrZf;m#K1A<qyjD_p8zNm`Ac)^w+^e&75lkVn;C%fTT68<Qa<x2{2;W&?LT6OJ
zgu5PQy7S5QA}!xWZO^AZM1(9du95Vpb&glB+J~V^y#6VKw--uYZ>Q+^Vz_m5<3kb5
z!nBY-D>vPoBZ1I6;ReXg0)SAP6|>ZcdDYMq7A`IZ93HW@y1CS^d<FJwk=#$Ecwz>O
z{n3M}AYPMrpW~F*C@%@u@ce^2O3tPIDTRW>y`S5D9ni>QJL-SfPg-<0<vu~%g)%{b
zjE6PY()OO~5wt__LDp8C@A+iCdSk=HYO&#S{#GN_VVp5+xV8TR!(~Jer!D*7mU+U@
zM=i$7K{!P&8`SQDwXU`hSg?G-As(^xuf#h0K|q_G{G0s7dk-3lVQ@ZT)F5@W<V`d)
z13afJ?3ss@7ES2lVGnPtZ~l2LsM;LqB4GR?knVPLZ9M0^^%pDC=ms5$CSU$MHr0O<
za?M<FXR!Pe(_Z^EzufIfVs<N_x{zL?C#hM%673eI4^F2bgn3?=+3vf2D;-R~usq$&
zL`KA0aAqwkg>PuSCGW2af+@G<ACQf-519O=a|!?NrQajA;{9(^l6pZ$y9Y?tR|ATQ
zz0lT`2SZ5$e5Jzqyd^RUvz76c)~va%N-6|s!6)2r&UYcWGyy%2kpY;Z?=ho-#_<}E
znpDPG$>B_r`c+yA=<$)0+c{6UN)d^S!$y<bd>TuHVGzayTW*wz0g7%Eb$Gx^o_=m+
zRhmAiZDIh>*jZ<8lIdZ5R>fD$ZIm+r)I}@@vjBLdPH+beI1H0A!u<&R=^!-Q#M_L|
zm%{$e8eP9p;2amJ>NY7nvD`y@5OeR@oUg4=M@SZts3aF%<)(G0+DGsl6>b3EFgn6H
z^EvifD*eLqA7rha(@$VV?VXiZrG2jsSIK%gT$~H5`JE-z_9*F1kUMra<&3skh@)W#
zjwq6S`qrE6@PoiF^kJJlFFH2pIB?G2v1uLM+Z4PaR)&*QBFo<H!tw%V{I5!4EQH=6
zBl+>+;C&R)jjZaeF9w!#FbnDvpY~rc@|E;ZH|)n+C>iVdAfN~yWAI;6J}&77cknLf
zE!YlppGN|?0==c;-6`U}nzPL6{@7S~60TI)j^|$9MnwTKk2K5pbNf|N1^NTVu4I>?
zmatkO2JzYF3BII~&=hdR_X~ur$4BKLR=y)ud0-&j(XUCh)QJ@Son7LdEy7Ed)e*^J
z3S{!S+MwS<c0?I#e82==(J2(@_JX9}Q6N5lzkHy%{R9cdeK`?zJ}q3U*2#8#_dMOA
z-QHa!Lv!1_$3GN1t)aVB7K4m+-k1j)&a{QJ+sgJz>&{2eNk_$WAi!8T1$T|{)p*6=
zdJ9A1vdH=H-vTc8W?44yDwQp)e>-+t|1S9&mU3^&5Y!`Ra3(X0HJO7<#C{jKy%w<8
z!782c;k8_sWNOhsC%ab6a{hjK@P9Wt1>S}yELtyBW5b810a{_&F(8@qh*4ua_uAWl
z8U!)A#a~1-`Z#TE1-g33&}lo1@ddg)8uwhBn>A!J@jcpVA+JBO;d9ym>Hy-h0G2(4
zY^?F~Ruz6+4Ssy!4sJN-<@CE_>)s7P6TVviz<!jd9CLBwS9t_6fQkMERiBj1?wJAC
z!?8KvT?uqQ^v~x=52?DI9_r=}OwHk74-&hGfX)!zDjLNJ9+$#-)AM<&`?-xDr;4M{
zQ2dO2p!~>6*qpMVDR@UVU(NY={uRF7>NVS4(G2y|ymoid%|qb#GPPuud{e!7&HnCd
zN;8YTq3dHC9UuiOH6cRm_h9j%@}@@SI>={d1)(~v0p!7Q6+rS!IK$KszsyfQ8WvDn
zd_>0siHL79w~ujXcE9LPtmt70HM9{7(~TJQwEF=WBgIGJU-z-PNV&r$Fz9b!KBlfp
zxRor7E|~Q+*FVI90w7OztmU<z+ynZ=_LCEu_Vq0F^ETvp>7ncvT_8LNsMC*jMtJ{f
z_%wLW>j3^WAYHZ&dRt#X0f&HRb6M-k^}+%I;~X$N?H^{SZ6wlBL}Vi<yE;AA3&Cm4
zlr?Z%6l3b1xep0%+G7{~u)QH*8e<|X1j1JvO<?tuR|ncWz`^H3Vs3M|oI^Fw|0<c@
zLnG4d``}jFvswlkj%}0m`Yy?EO5p_b<{A2l&1)@nZRruAJ!L^c(_&QbJaGsdwMueR
z>9n9LS7gli;8FHbLslKRe3QXB|C|zuFzttzH_P!(hvaE;Rj7>W&)SjL^cL%q9uGTL
zs1CoBp<Gn8!#hmX&P=oqUso((#{XOYZU5*Ntsmrc13UH<Zp0aJ9j5uRL+?}E#NOyU
z*yVd_PNB-ln{R1~FNIpDrdpJ7jp`>YWMQpG#&<g?Fs_ih&%u$HlwTk)8k<eheTqd|
zoTi%y<I+Vjk!4n`km!0h%Ed!IPaou3_EeakN=X1gxz@cw4WJHcn36@x&~HxsTcibZ
zd@B}2j(e9X3&C)6bh!F_Gqn=<b;?td7xUq>mZ%z<g`&cb!utec=%Zq@5zd|)sO<G=
zvlZ0CN4gXa8EGG*sXl9XIDU07g4j*4cMPHE1zk?DIylaB20QBVW$chs4tI_^fQbpk
zRzA#lXMd-GCd<dO7F8(%Q(@OQ4`h00Kq-CxkRY%@OCz2nK!$llYIr>T)|+^C8gxQb
z2|&^ee>$qmnu3DLmOu%kO#b`0239>bRa+}&?Zs|xN*Q;Y83*`u7-dGve_-e+e8Sg4
z2n#9^p6oR9Nhn)O{czNVI)Qrig1Lmf)7iDUFh_j=v~t#6)h%0_>ckyhGdh>XViEeq
zjpxs~Y-ryWtM!nsc`EWec@KCPDY=mG5!pmX{ROsc2{oZf&R<}u=m9LOO#fgKSb^mu
zUGZ-NtwG(M!^4J~Xm2vqnnQtXqdkE7!8P-dSdN5~zZ2K@$MiS6#%-F(>K{k2tu)YQ
z8fnt0_>8$BOSjVf?R1yUTFAr?YIZ^5C7eSZZ|3w;!Wn~a39B{hl>)$2XDT!F*w=1Q
zC>2V$d7X>SI>~o|oMJsDQMm~T=iijKS4n5gff78=CJ35HZz^LS#D}oh^f~}6+9Ir8
zdYS~8*MZ>bT^3(R5X@fsA+9&Mmk4YOgFg<Yn&XeNIP|$@bF!TDtT;2&i-!5R^Mz}E
z*v0+5k6%%VV?+yUN*lXsj`-{3%GKxJ=?0v^x2BOL3c5j%7RC<O(FM3U6Z{$tzjeaR
z0KIu<NLV*uN67$iLk-?kjOSQtniP#RA{K}z_y>_pBs|APDlV+}uXu;}I}rwqdgKF<
z%35kN2)U3V;_0q#uEpd&z^JhC@HZK=xfMtq=+>;!__BEgsD#tK3kK%bNqoGQj*El@
zumo}esC~<AG2O^155&*1FG!&S?m!f$w`;cl%7mr==Dk3ujxu*OXC0U<loXW50Tp99
zZNBn=ZV8tuk|HTXwT78s40x~A)C(0b4wmkg+!jmQBopaOeW!*QmOA)t58|Yai(j0@
z0YVCBx)V#NiM>EHkLe6tB5~U@spOItNCyta5-WT@=q7kq@GPj%U*~}K*#xsjzG?`u
zhs#!b0_9z3ZZ*>&J%wjc`K6SJdt<d=Nk#fyy8b|e#*V1kkMsC6z>t+&SA9UaCN-M}
zFSutblhuy#4J~lZ);goJaCkFU$B9}~7^&IyxQ){L`*{|SOSP3A2d|-ID$Jz9a+RD6
zLnT0M^2iQpGnX1-gd6JizJ|XM9WNmWY&C@kC#L5?vX0S<y_>zxIkxWhUy4+pcX5fN
zK^+da^Amldgk|9F8tW}$I^&?C+pt|)1;W>0FJhut3b=~_{8P(kX&Gc5_(kfV!P*!l
zH3O>W!RV(9e@B&AYD^V664zcrDjeYRa;(i5uV0u5mSH%eN+x${X(;0W&Y&838b!Um
zZ5@+iOq-Fbgp3tbH&y|b=gA=MO>;(}5_FvP{K&-7tF3^2tPX!motUFW<Aw4)f9D^m
zim3H10=*jTHYfy5E#y&976rCaihUF{&Zx&>P7G@zV9}9)tm`b8r?T`#5qv3>TL9h{
zjszb5{aMi#;+3}AGVPj*tf<7rgt0(As`QO=Y!K0XsE&(Y2|)utR<K3$h=RpQXrJUW
z@XYE-3fkT3AF&F8d=HNha0#ETsjcYP2W{H;l$x}}5aCOnnHSIf=amd5#dRlN9lAI#
zhJGVmvNsJ1B9~$hUh@ws{&Zs+q6=U4+&%6Y3bl4?)~JrOYp9bni}t8m)u!Q52K)0?
zIjFYE<<{9tgh<_Gh3_9WLAGA?P%p`K!UXa|jvf;!#(B@%2w+qgr3`OleS2xGRJl{g
z76j6cV$}Gj%ykoDZ|i@?mgQdy<0^(0a4Ys4u__%0+H4LrlHkPYO>)Mo@aA5+{@R(F
zB(Ky=S<GsLRm1>|OP~Ctwtn>^(`LBrrwhI4tUTg_c2)KsL-Ew)bVlw9UM;ZdJz@x3
z%Ib-4V^&+Z#N@xiew5pomo`y5AL<bwexUrYgn>eMtQst^4B@}}3227#r7KtEwPQ@+
z91NNHzj+-8q8?xpspT?g0}P@-PXxo?K5n|swW*KI+_9Y~<960B^=In(&r53{^0ne#
zOpW{HvOfE#=_m*e3c)UQAH(}NWhYSo72nn3m-1_X%)(LYfxtC~=_@N+7g)c25OI5_
zg!ppX@G3XKK67Y=tOD!-g5I=K7gqz#(Y8mrUJ%Q;#~Opou`d_PELnV9>?sfLicUm-
zJ)hRuiBm5HeI7(-Q-13?()?~^*I*w%O||muWlRnQZ)kY?{@f?pVTa`)CwVcS#6ciH
zxI=cvOX~f1;k$c7qNcUk_sGN(q4da)x0}N5pzL|njz&^-)L>D7UJpb7Qaag5)F`>&
zp|<xioId-1Nk@mkNvqB+V)vYX#jXbDcqLr{iW6l<25p!IR$je!_gZ6W8#fTVr7a5T
zW*9r}1DCH8tl|SBt#F1U&JV^8#r<3s{IhtIt1-#)3?Ez@>r7N!%N>QPzhWOy<Ljb4
zPur07on57<R`Nll`ecB43xi9sx;nQ#&8SU$?r6^-Fik8seNA>|2skEsuZY1A%F($}
z$SSjvl7z4$g5zH|Gp)qmkBN@~$WGUrhe;&ei30nVW5mtg5%Fr(B_vqiXM?=LF70`^
zz>R^rE7fBb`o?edT&{5Ts2Xn|GQE`xETQr--Zh;dyEC*Pf#Uo8v4+I@&zBiQX{oMg
z0P%<nCOcTI5>CkB3sTwh1^KRh$}R1^1$limyK7BpSMcDVqBF#R20ph_Yv9w;(4`(@
zWdLJW=p^$;vaBI(7Vx33C4X-4?ow%P&2R{m{XhnPe~?OmgUM3aikkuc=Xop86NO5^
zq#paSAm&Sp>uioY_=prZ$LvaU7~5mfk-yh8%p#g~<>2sgnQePtFbZ|6Sp7x;#ii0F
z{v1ud2-Af;P3p|)s~jRiPgB8a1voSDYMee|>u<Swt|NdHNVC|*%5PV}rxBf$B6!e-
zS`)%%`G(~J!{(Y=Msn)A#Ofp-Pc@BKu8_G4%_9U-QMoj?c|wFoY~GwB+lpmU4^lcZ
zJ+mhFb}(tRrhvjKnr8#HyDMa*KQ5ndL&l=|BYz&@idFC5mPF4+lB4t2FOJe#J63$O
zKH8nQ{Qi<qyqL!iP~We%vG38U8$-KWdf0ndQJRF#Dd+sf-CE5))nb~)ODdUX!7;<A
zu4_o!i$7<Us(}a&K{b)|@8#^bVgJ+_gsR6&SvA?M5jkaQjE6+jq*#6qsNx-Y>uI{K
zzTu>-r{f6An2tNt1xW+p#q=ory6rzV%q5ZoqlWoru8tfJ8DL)KLZ+b%*m;I@_WR4q
zUPID9ee8@?YqHg{B^>!APDsb`u=dNUy+w-izMcZLfIZZ98K+j-KZbRe8xufL7-PAi
z(UK-Pa3lc{RtSJSNk4R)v&E!pJjaq4{{_{W1`slpPKURlmav_~J3)2aLf4HZL?rr9
zc^ti>-F8z0Ijh^#l*hw9p6{_btI9bf^djUcYJozmNTG?`=z}4P2cbZ-x%<*MtlHWe
z_G>?$lzJ>{3i(=Bbt-}2+w8#q=vSe^5*VJpWl(Vdoq%@6Ro07L9G~IA<wr0%+s9z}
zp&q9060MFk*2_n|MY%aTM@~|(xjV*tp{{dwX_$)-@wHY_?xA|lH}4msjWC}G@Q*>V
zmt<7k;~YrJ4h-caI0PNSxdH9|SC)%H&{e*Psx2!ZE;-l~vzSSMtA5S>L*uOOs0KB}
zh~OhG3H))c^2?YJ0%=^PmTF|Y(QFXRBed!wJa*H~?R5f30;h`~gauCYR`G~<pn&1#
z<|3O%hRYJxbePzlM>&f{0t?mIQgw;clrWuJ8kl@F|F|!hcZ^DD`C5v{luWd)`qmi_
zW1DrWX{W`cc%91)9fe*#xH?Wipv|*!O_}(8!pEZ|5%<F1i1;qkj0n4izatg*IU?Lf
zgiPHy(7RSU<89s#dW@u#*3|$*R{gqG=SM6M=uS7HGbxrvhE$#YdP(@QV+37!54OC5
zuo1?gW`i)5I#f{1d3MhVFEOnV=|wdWzF0xfGhw*d&`O|j%~hz%o!5Y$#ol;xe3qq>
zC^z)NIl7|D^+{xt$g>h$jnf{f&dr;_K&AoOVK6Qnf#7k=qo2smxx%uphg=a^_7A&T
z+q!WQ9|eNF+*?O7M@i&%Rs4HsgO@|vN{y?j_9^3_HY)m!O(lu5mBXm%5Fhg#-1}n4
zQ^K&&o)$H@sgF`__y{RdDP9}-UoIu>B*rP|a>p5)lMWUMz0pk-ndt!Li-Lk+FMXD^
zHi)3Xa<PgM3FF}N!`nt!>ekVQ{e)A&$n6noRl6h+Ikn%M-jx1Lc!e-&pLyYY$u*si
zLrIb3o<?i9GdHq_WL9NdR%4c~RJSzKxI<Fb3ihE~VKjPzvl7!iXb|a9<X_4;LgMqE
z`|Q`e%yeMK(aE5p5L2H8xtyRgH1m7M=c$M?=vR@&!b~PpVWQ-OnjVWDz}vYEo}m_Q
zgE}w%yFvKgEvJT~DuZ<WIOF6_myGjO9yk(ZMBeSwQY7Jmp)VLo1=cW3MeynPU}*?1
zgp)O4YcuguIvLC5)e8`OZW)a1P9`54jl0hHE~E$G6JSZZ`dFgJ@b(dILQmSTT1X6E
zW)}<nJwJTYdeSxc5?F5hLEBTEOg<K&VH<Rkjft-7i}(J@RHMqP>WkZdraa6(O%aqA
zqy(`FmITV&3cjvfFQTz`qW|)<^A&!Mxj1KYCBMt~P2Dvr4T2ntE^teq3W9_|PZm!n
zwc1+SBylqiNiYeHlMkkI0pRqTG_)j;Yc?0zE0%G2kjWmYOnO_GDmwlMLo0nd4c)is
zw7qEPHMj2V-p<!*Ze9!^7aL&lgmESzdp0D#X5jHN15@tFWIZC)ThZa3m(l+Qh?3g;
z86A{Ja0H>Y5FZmOj+GG4^UpmLkJE1T>aqAUsKSDyDJ)puhV(mk(dJ=mTlZ6)K!V?k
zk%C~N#fpKVx&&hX*b>Ul`BJJN{TxuR85x21?SEI=*R0YSV~~<V3`gu8UUZb6v|CY#
zu9)8}mxWfCL9+jTim{qef-lii-jX}VmrrI4V-x)DL##TvRt~{U0MDY(%1_NP$-NJ)
zI$GYOS|1!PVzbx&RcDH?1L@*H6dT3Lt^^eH^hNSHlZn|2aa}cHgG7b;w=$#g@9oeX
zR?oB0k;VnKn}aK~iM07xWC7G*9@Lhq7pVTZ7CZ64Gel7nopwfM&9DTq5k@D5p5^ZH
zr+3w+4ISP}-08-LK6!1*1=mUjgdBa$rK<W}y{n}5DJ5K6n~`Wo@+Ml9?t)tZbbf1%
zdMFmyE_M9#(pFoYCpmqi$ffU6?DDs1GJ=0d*M+6Uh`__IvWs6lf0TtbUNE0U{p716
zCqbw=y*_*2T{Kd$p;`YyXi^qcQiGF4SK$f+s_`EE172!D%wGTcD~>a59>h%R*`$(W
zh~Trp^DnwRyeZWpdf6;*Io~Rs&3+&b{rrR@7cU!brVI$mQ~fxp%Lv8cR2vY+3H;#c
zBTF-`E_wsaZLHi>Rb?Qn9=g1t6s$EP8@V?<Vpsm{zd0FD5N;Dn2ea1zwMj7oNBy6i
zD51OkFTM7mN!?Yd`)Hq`x+OZH1XKy==`tni(TP>Ph-I7Nyd)(Bk=|Scn~VmH^y;Ff
z6-%VIBCx@KYp{02qoL@eX!FVIb~BXArv0oi%&t+9vh$s7t3!AZ=%+(K%e1;aV>~B2
zdV5C=|2*w0o>Ty%ZP==#?CyU#P%JR~v4~Sx<nVF228pL&#8azKOepBbwV^{6cGb!y
za(#XrC$YEVn3TGuTp@V02j3VEQ!?403`Sl{wM@jsJn<o;AJ*SHZIb6`X}aE9Z5iDQ
z4_GOAO4K0N*p;O;cB3}h@g|iLdrXs|2nLAJ#;Gn?%eKeZp3z5RL7@Yz7hlE*qDe!z
z7Ka2(v8IAjot?|SB;#JHU?v7l5EXkHuPg5AD^}|X1Bo3u^l*;l^9EfT48PaZ4ek(H
z{34rqs^;qbL;r3X)B<--L$ZOXN+(t;KcmY;ZSBl{jd&P*e@~ba0nmot@}n}a*!wsb
zIJ2ghClsf~b&JI|#f8S%0j*Ow>NS^=QOdmT1D2wt6=BTJg}dk+?wIYdZ*afW#$fRj
zv=&gz`#Ofe`z74iW#+u^D$kepmLNXzS{LmPT-%zsUsouoogPFK{j%!SuE+exIxQX?
z%SrgSbBc`bSZ~kOG@1AhPN)=Fx$|zX8){BPR`pCMHAl)_EdbwhddryV*u=cu%#Z2%
z^f-9=#T@xWc{afdRITTfEsfI!#*_&1S|+D@Yb-1vXfU>Lj<k?tvg_)rVKO`tH6aua
z;AUWBlpdt>(PioUwalxkI%^11BzX2*ID}zJvLF};t>}#A$VT~Kon6asX16Q{0LQWn
zi@L6h=Xn+J-3C*+@4S$r9qItWgXTb&%4T{Rw~T+^Bc8}<T=GeiMApQ`Fg=ZIw`{RR
z8rDRHXv|H&`zo=uQ`xv^gS+KTWD4j?N{3Y@B->4sqjbr8L{UfMLPM(W=k;S%{|FqD
zP7>!)tn6g?j38;m_R0);xnuMiYpFi75-ALZ?v?r{eB%G`^-e*eM9sEt+qUi1wr$(C
zZQHhO+qP}nwpRCD|J`xooPBTX6H!t1QdJK#a%NPH%KXM!CJmF`>-`ztaP98x>!fQw
z@59!hv{pPjsGEwM57X4Ki(4JV$;QuwEYCaY&9{U@?HsMIf+a;aAml^Gk}p3PBVu8`
zlPDsDi1o=iMlH6}fBk+<i+O>&CnoC<-(L5B2;S!yDn{V%3=#Opg{V{Mdmk*;>0=y~
z*%3lQ)i|B)(nH5<yLojYd{~6Lfru^Xx*An39L)qN1A)xq$sC)z86{NZ;YG<dvRyIX
z%}@pERxoDe>@igEeI!j8X<t<<RHr8=yOlbmRX8}SJ9P_=lu`|hm`9tJzRp&YV|WTz
zc6uUl6s~;t{0=2fCadF0z&FWugLcA}7IUJ~DRM~Nbr>wBiloJyZ`@7CD8<er>}=B?
zT4r=7ut(|8&}f}@!0TURUd^$i2^`z)q?C%i@C&Q^TKyT28loZ5=jl^cg-SkH&ecvs
zDLe4W?R0FNCIlfaI1u|<J0DATWy0B$hazYk(~#->)s+U5(|>LfFHnSF9Ksz5#gn=*
zVU{v(_YE(k{>86A?II4mA_?Gc5JcD~&$FL)<Zl~@M+7*aTq-0OZIz{xOoKjEHI02*
zx%`8L1Ep$ff7D?!>8h9w4a2c?UD~>G;2gBg!t1<a%=SPEwrh;B{N*t7B{vbCKDh$|
z$&?Py1`|qVve0gS;&jpIu^HQf=$NVbB2-nID;p>SH)gBV^6I|U?{*Ybb?-tAO;*Cj
z;XoKiTm&UGb#J`<(KGEM5t8E|^6@2K-v4lTsZpR`I_+LitWE_}R+}Wr#_}L)p4_j&
zYe0>tEzAHo+9;s^W?CUdV2k2Sg@VPxbC_GBHd_3W%b5>4hXXBd<%giFJQyRNFez5K
z#=GFa8PHN4FP<+w1qq&{#)&}@05_~cn{TFngh>JMm;v*WFcx~D7}V&=aVovX#ckqX
zM1*mbW*UHq&ua0g4gV3D&*ULmp7Z<InQ<OKL>K~1oV5W*)JpPYZU>P2g_z9fx4iqP
zGZzv2yd!?RUz<@$GitB(!a*$&*isQ1>@b~EcG=3i!j~bP+EXR1IX83qSxa7y(}o%b
z`YH1#**>rZ>#Xj`8j|b55|bc8$4+NiGfmB2`)gIC*=8LxjoI%P%w~qdk5iK^>)G<~
zjLMM~?(>U%{v32mhnR#fx(%U6YgB;Rkaw8>2X$xxW&H3kn)!B7VUuNCsm1@vVZ?-b
zR@oLr{uevAQ4ddPj=YI|KgZvZ<C3Szk?j5k|1QGduES<z9uh%RD@ym)JF8>=ZTqu8
zZF)IvWdaW8^MF)Tfs}PpypfbBGU%WRk`ft8&)<d+ix>H67WbsG{|(9cC%v2m{I3*9
zzk_26?u_B)iPwZOxBUU@h6LZ=8*iO_B|`dy^v~tZ1i0OEh@F%QDQW+z5ugIR$B%Yf
ztX_3vAHtmqLwz7W%+}5tKSo^i4$wa_o)Q4*$nsFom}y8kx<kNqfK{x<dr7pLrM^Pk
z4>Lotvi2r4S@SalSsjZ8PC3lIje`;~l1;d1Y@n0ENj+hvK6j%S<XJWu1+}8pXWr(g
zl0bF^8Kx(zyY4{*%hU}jWw25l-k$RMf9^I|uCUB{9<&@<{|!=Ct#&QM!v*?Ue4UNr
zkapeaw8&A2gRm^j!_tFHlChZ4>vE;yZfo0{g5_ahNQX$<LWzDV6nl)dP!nryB#^k0
zNyppDXpqwx7}@cgd1q9{UlA_Sxc2}Wv_h~!_*MYs=_9qM?nZjjLq(}lxB$yd2Q}pn
z?+=2@=Fmy(X6ViMaAxC6`Hk=VoBrHa6V};~o)<n%N{DY}4C%a%SqFD0{zR)bm4Hia
zt{+w$#2dKfDv!ySdR-3B<ag)%O{)MSY!~?mXQU&yW49HT!B*l~|GPBfvZ4Z2_*%9>
zH|D()KO^GwuDzr)ws;eXDEAA!TXlMOE4udh;+_+q2aY1(wkj$!%Vf2ao?TI?7C3;1
zZlK*JAF5GxMF=hQaNA+x<jpBYtr*Mm>prBl1SfNuCBDQ@<E2;)nUh^Mdx>Jo?4rP<
z{NNt-Ex|3CTWqT}Fmt&=AhM&}#iQ?%U`0QZd(et)lTl;g|A#Xzwd+bCnw{(RS>90$
zajKHCtKh0^Y2P~GqT7rvAUci_h@VKxk!!lb+rBvDSXIOi1wXB~qVl_T9c^LX@ngNd
z+p+(tkIGG)*qO9ZMcdD<xS!}lO9%`?F^vwSx*hdQ(*9$)HeIdLcPk~A(##!r1bNl^
zNjA}jjQ14lp|TsXuE<nQNgj30Akk<~jif-yeS9)#nABY$j(*WWWM_w#1k2|er<Dz_
zl1=vVlnbnE_DUjP7*S1mZHC55Q+yutm0@Dtm$1<V$0JYYuc)?){ktSR;YI#3{5C!Z
z!nKG=j@orgvdYQ)t={1y+D5AKnJtQ1LrM6U5nDQ~+$BwCgzG`jF}lCgL|1{X1WE)M
z!Rkvc8QiwT-=<ZhSyJS&AlZa~E%`2r%eBC}lru`ktg3~nHC8>1-6$Z~EnWDO$i}0y
zy+=9$L+_E9dMQU1+rC2YqctUDH{2Dg5L6F#s-FNw2zN|btyH-)O<MN7B%+;hWKO3-
z;anBVFN)0BzkM1#6L#4)!j0Cl2p^EL?46bUn+%R@9n^b(JG~`Zc49k**1;3_R4GjK
zFp-ZQsy-7*nE<}|Tgd1Fm}?1*q=}p-Jz~te9gjA!JaRcVT_UqvOC4Ut!=_S5ndKop
zC!tH{PhcY`yym(fo+|k9%Zmj$3{pa&XJd|}9nH8$go2-(-PP;;=tK_LbNIZ%*wd${
zmokD3hTUKhUVWjRzz3{O9~HX_Tm%-8OGh?W*IOa>Q=<X_k6Y8q5IEni`Wd~U1UqCb
zqm<AuGLJE(JhqGsa5js~dnReAzW^`Yal&9mdjYgkH?@P|ag&RKbMu=D&C}4We&F{9
z7__!m*rkTYY*4{bl+9)OMs{zrp{$rRvcZ}%Yz0gyT={XX(r0dS{^{k%>Ogdeo_et9
z7h`sDZJi+6qYnpZP+JC=9y~yqQKesjkW8$!?3=?1iv*?dxa#`UgZre_V&~Gl^`YBM
zj`kcJM1b^ktw0^l)cC6N$rh**-q(>|mBgj>c&HA+K4AU&<Kk4x-G+Y*Qsv6VuH3pI
zt25}a@S?~HgOyx5qpUMozC0|9_}ku=^jim&PfEFuN<#MZdgN@4BYtnC@$|=Qnt6yi
zV3aL4c^X>`sRSSP*dg0S(ZXD-bxaliN}3CON$v`>?#4}p-jiV~czI0Dg(`-fptoDE
zccO<4SRP79KGG}W&+7BR<6C9!TpjP<-Q1Nck90`z?$>!_?X~V0DcuYSySHfLSZc)o
z-6Ujc&*9C?QDv1^CLqxw&+N7(0f!F%QWVVfsjh4)fKd3E^V)%e7$a1K>&8o{cVGaw
z$d*mYX{tFA>N@cRu>c&SLcu#3tKiKOSxWWjH27;N-USshSKp*fC$E-K?;M;=pQKuv
z&X?5QGmjb)m{S8iYkUtA-Crz0{#dmHuBw(v{pToH%fy3J6&{wZ|J<jisseORQOrB7
zr?WeTE;D*uNK~-WRg1?HgxdDo7(a6PktCwmIW<Q?Ep0wehvTYuC_veRRsa?#0)f8R
zx>oFwm1Minp|h2U3>b57ce*KG4wsUQ*X%C6>>!kv41b(6-4=+L;lVx{bgw0uHVnVy
zeyR4-p&g)#n(1H-00}Yp#-Pd*MkC>|=ELftW$9R;UHu~Z>@OB-YHKvu9!c74DgBmQ
zn2#@<>qiOJuNKz(#wEXLrV0sRR#n763M$TrXF4@Aw%Wu6mzq=HiKI6OthZdN_ylx~
zun+OL9{rXNT|!hnSk}jO{cs2Cr#xqPG8B%6ii!#V3AAam8%=*QLqTm{ZB-^a83Qs@
z*|CplkW`bD=*asAdV}oc%pDn|>6Ls^ev#GdBW{QQZOC#)2dj<-xv^tXbVIUtfU6^|
z_0x?9h3?UOpfFSu)kPacIt{AovN!2?!AP<hf`JS7U5DBnfJX2woP<sY>*5ESC$x6C
zA4|6`1eLR@X(zPa2wYG+21RB+(j~3N(Z}pJi`K~nZvxGev@K$IXIp6&b)9A3VMwo%
z#3tlhO?vdGNzU6937}S@GhB0(B|kWgtm=@L$&OiYul4rj_8RUh^%rE7oJe@Opt5up
zr$S~QW1Z|t-qn(`<Y;}O`}CP;F~T`4CTsme#Tge09dx(x(jj-Qsf1NhFS$~!WO?Ca
zsZ|5&WDiNAs(Am#$V&5}bHf7=hi+5KuxNLd^6*F>Jt5g2Hf5NIPba;mBTqsMo!>|s
zMnn69+{Z+_hXYQ5qrR{hPoOM_5-W3?)q?bk_-WIoegkaiO|PdQf9#GP<ET4wrqk}^
z=n~PwjTp}yAQDzH!tcs$xW4wuK)WPGQ{WIcWQ?Ywhqy$6?BvS4r88;ySl+X#HM<bt
zrHb8V|NI1~%-T)b_<GkFuC}g^%&`cw6*zR&3S9LcP11GrE))jZelBu%bbZ~0KmmO4
zi2zHsJ90_TrKwxBNo^13<wpm!_F#xue~rUYtKfSe*QP`Dd_M(^>k4|Q!E`_f?IG+K
zeHlxK--dpZc2x_F{xr1lyg4O3Md~v92NHlm`#djQ?WKGiJG#c57*n*bEBoJOT%Q40
zL)0?zAtB#J+^%{D(PX;&^s5lh#QG$=<B5Gf4ezWWO~cPA$S14VqllN~5NTqB;3;wM
zNaf59K&(b{C}{ffKUy{)@B$}*zWP>996ix9Zb-;K`iXt5BW_B2jjWGgTr58I=}B{N
zbKr#W?|Dvo8kaTW!uFVPi#MSZyClUwi@GeZfoO8kbfNC|#vXt`6}kXg4fWul=Z7C-
z_XR6AVmV=<2{_(1eD=aUH=@Ws<Vu)K_F)y6zf7~0?PXMED$w4yoN9?wH0lizr@EX)
zJ)cHjW2;Gj&l&L$qzDIp_WHiBen0#EbC^)fD*4^oA8W~{88yb67#5&r36+tlU^2K^
zg(br32+5SvM|9oQ3!agRGyVAjwo9-{Ja_{T2y9)pzkF3zM=^=q+EqCDQO?x^vYsO&
zQw<6c0Kj^=5-2AkNEe&H?ZyF_Hs#X~neR29e5Fq~B<i4jY>9#GWuSE%LkHOxjR#nT
zeI3DdJC{0j<xVEyQ2<WqJNf}LdHT*N%HZ|mWy77*rgdGScU8wIOFRzI{zn2s6cJGo
zo-3V0=3Z<&$w-~Y#LWtntnu|9TTw+P6LGS?sFd}&nXdgE#vdksmhS~AI5`77h*+rJ
zSLTW}1ez*j=2RIO{f3efRu+S)71zgWu9_u&HGJOONv8;Mv#%TtieuG98j8xf9c_N1
zXMK8m4&JRGf6knj1gD%Un%-aqMNL71F|rt~${4X8ImQHsFhbO^c@L~9Hsf`po<jva
ztKbP<=KLXr`_7QPZ|s<v?*BdeO+YLpn+yLknR>9sgUP*idfI9m{|$a_Z(1Lts=eml
zaVZ4L69=kw=(F%P%+mM_A*==HIlh>)c{y7MFS=qdy4rgXcpXOeVHt6?d|&kSZw$2f
zgfBeJBMx}OGfB#H`H{9C3}?G?LL(%IetYTvD*+jC3&>Fn^|H>D@()H1b=&Y*Kv}lB
z%EF7hukP@HmB%%8@3V#_9Ww&Y9*Yw(FCc1g@>N;*SW+Rn@}%+*W+d_*2WO*)5Q}P|
zBT^?rH7v>dkyF15+gq^31{zK>c}z@pLa^#2Zv6zP?D7Lp9HulXH9@4T2S}6ucZ{!f
zOEBlgKL%F5Y;ey{j1#6pZrkdce&C2dw=`2cU2B-m`@{{gEP}-64Y8P9Q<}xcO%@QF
zN(7Z`DyWlChe|STjQXRVX_cvt6D8oTg9qbHzY@F(+eD+>0t5M86ySdPbh7HOO~obm
ztj>4~^L63%C3Y?b$2AJnY$b@{K7Px#qCU%$3p@0xlNt*`oZx_9rNAgr*d*CmVDf|M
ziF%)}%TwMWpDtW(O^u3j6Ba1NX-$ysP>~wx0FLosV5Viby!<BY@Z~s!9OxLB9XD2|
zEKzq$D9qgn*G~7bJ$KvW4=5Xx*#RcmGJ&uVuCxal76Z_Vmjb17&oqasI=pV19rSv|
zATP*^z2Q0c4mh7CYg!)l=f}G)I&kL#Ul>fh4`!hY6}{eZ_2#jA(OGwwyM>@;-}!1T
zkfp8igDGJ~+D=lDOaIH+xSZbYlx-c4f301Z!4tt6*=2q>tY%!=As>pKx}kjJR9)}8
zU7mIwH_*_~{@kkRrIAYU-BdyxO4}td`|arW_#>jkcTg53*#ho986Aj{rjnx4v^!L{
zI8@3zp=v0p7Ll0~8Jp-AWTYF?thxXYs2H~%v*I+FngavqfXM+z!Q$|YL^o6OVsvyd
zrX`J=Ok0sJAAwX+KCJ!g*g!dviMJdqy;ppe!`1ucE(v8H3MbL+MRrR`&Jn4;vM(H>
z>vPAQl$x9gPFf{zk$Ah~JZzx^OGe)Nb&yAj+>*GCj=&$bqR;nHbC|c<3$nQ5&@y%|
zvj7M#`l@9S5s^^WSd|Zd#<%Vrx40Te>TYInw&}4N8j}+&<VNzHWhP%jdchOao}$%o
zpP`{SktstOY!w8W2U&s}IP*fsJBvq0dr1U_gnxb6j7<qW2QbH=iM1B|vjF5^+PK9e
zn|alyw0Sv{L+v@Am-GW_oxBW@-8G_(tJ=cCqQu6TE0@m9j!&NhmHNETQ+Su7+80+y
zwn%I#UB&Oy`PSjR*5DRQ=A0)s`=O#qxV$;S>xzVNPdbiiF$GrIJ>^*4Odx@>=osCY
zI`iAJBh_0^!yTaSD#u%|s~UfwIB>D@YqH`V8poGt2~kI1ANgfhAWBnhHfLuPv6LMi
zF#Wv&xVrBaJVJgPa|dit)Apx+Uv|ReYWc+33%*iAFE<XhgO(fN2|gwlqPL8+o-4dc
z#N4_Xk$7S^8P{W8_99LJC9zFZmZ=iMyXTzcjLOW@QGI!uBSM=!!(aVrQKAtN@JqXe
zM)y+5zyHX8Vp{XSVEOF0cp2R?`oPngjN?e*uYw5_Im7;**!#*q)HWRvHb|Px@obk5
zY}97W!d`5o$JIHrp~Nry<gF*HrshUhWgOrf@*rd2#zFkkQIvv=zLVjdE!v^5vtAHA
zk&uRoZ!)SH*^&^K-c7JP8KIhcAHglRZMOoodTXJ8gAen%u%q(cJU`2^zdfqL0(rg2
zOYA^Ca=zfmb0yDZ*J);9pGO9p0N<r4xp(b_2t4@8_A9hZ7}<Vo2ASoeWT#~@#8Qr9
zI-$@#6a1eNN;|Pajv8#Syj*m>1xYhjh)G#9YvF5wYh-P_Go0+@6HO0$e;<e32;mjP
zWh0>TzH`hS?t~PjwTtgf`hTVa{*sDrwJJ|<{CENWGXVUq`+D^L-eLRICHRdg^#W!>
zxT)pM!UMz+?qW8a?`-8cCJQfy1fINW%bO-T<eLYMZ4efNtV`pV+w00|w<K$hsIs)k
z&uQb9v$dsuW&->TqlfaAdiRJym6G9!mfT{?Ls(|A%D_+AH1hD(o6sgs8@sI*F0l|p
z&68u#he3f;Hp%$zZs~jgXS;pokuzKcUe0SYO1DRqZD4`5l_)xv216O_k@?$E?$IvY
z0shWrR>8MsV^knbqDtI#1f~>Jc8l_+zl#3S6I3TUGSySuzhJ6tdZe8^j<+vxoJ4~n
zQk?&_zn-A9R_@6S6t(H_Xl;#7?UGP^Tz&-1zz$`)Q*?BwQH*>s7HVo-+$kH;nsjE9
z#!zw4{4YMEXtK4aFao+AUP^)Y88r5*Od~1`lDA1-FV0{mW4;SY6CH=pOGkAb_fIA!
z4eMJLqE84N4^>S8-k`5Xg__o4-B0lbztGpyl4IZ_1g0R-?w@ZIo0K!4JC$$d{!!+e
zG^R<@nCTZnmO@FDM3({oB%VunN!;?fl$RAqU6AfabQiCsB50Blf5ZDdz!=85SQ!qh
zI)B_Ph@2pU8!yV`(R+R@(p_TuMlS=dw~%{#&~NxumF_^jXApMMf$p1y_Wy7K@8rS$
z)~UQ-ug+SwJ+1h-3@e#h3oja|%NU(8-lqjVvaMB_`vrAk9t^8ZzvF0q)Rj1_Py({O
zkd5p0804q<+&Nn(%?P{MW+VBY*2dI&z+wqwqsQD<q>D2Puu3A2lC+6KdSxxmN+a#0
zfz-0@Lz<~}G}f7=UFR!C`~}9hvLNs@7qbDv!z2b8>y!{4U?=C^%g?z8Umyyi251+8
z@}X)qH7ZMRA-5iR9w?S3cs->$A4ywUenY*9G-F?9Hgcj*tJCADx5Yg7T<!CqAkC67
zG;4V<-n>i-9i8cccoEjbP7vYL8x8!N?kTo{GJ){?ARyx;YbN2~)|}UT^rVGgQw`HR
zl$R~#bDJ}FY{2r;+RFajd=BpLERr|!+G$Z{7*-^q)-R2E%^I`Tt`BIKR}Sj~7?b3p
zbrXe2Pz?q#cOfcqkS}HGF8Yc(l^@-*Z9zM-@vOv40Z`7o14&|3rt*JA5*`W8IZ94N
zA<iWiPyK>s(003$gOHXT?&vN}PS!Q{gBMir-S2@sU0dz;nT<7gL|`=KAT-N`7%G(3
zzik%u<N~df=81V?f4cK=?bmQLb-Z=*myu3$V6SWdiAc^}gqa`J)2b8T>C|?C`|JR5
zoKW32@8Kgaba%3&>;6j$ku-q;&{caUU|u*B=xBoP68nY=zm&XO#ZzL)B&Y<;nim?Y
z4%NEqB2thdDPToAJIz(O8P<8X&8@T}(ZRW_T&Hg<=c!oPEQ9*@M_mWNWN%mY2oYJ~
zj+#fI+V>sguJF)ZVr^8SOUT7uB*V)2#;kxEDH%?{rHVq`=uGV_x75&DTbIYj>Mgi<
z5Ce%ulrm&$#?n|sU?;>!gszbx3^YjC&<U_KGY-#gP5*XF-_a}6%mGI)evy=&m&(Im
zH}}wqH7XR-oRvy0Q2X9~i~^Rv?xKMiRV@|*ET?9;779}!LIo=Q-+-3)pf6qy8Pwcy
zVc<A^d5KqrONI9IT!tM}5g)EW4^H{d`iXxkNXK<Lk2KlEZUu#UEKvl2YjWpAz9rQ~
z#23nSr!R`KjjhsTPQT9;r|N#Ko%Q0!s;6DuT>gYDwz!URwzOq@8but+<`JJQa#HAZ
zzuD5YG8CvXQ}@|mMzds&pW~iNP@>1sdQJncOl2jMl34K;(gv2<TZ=t_W&RlO>z>~i
z8L}?It3V`HxBpkg1CwbLIDOM09uLZwFCmVI;ybYU@lwVVhG@6q33LlOmTu`Kvz2$#
zLbOI(Aywu0oPRGb4WXB)UAGnh$J`3@u@#KTQPG!s$v_K4U_~Ik$B#gZl#JzAilC8)
zk}VmHXfD$^M~B@WvDQvi*}C>wp62e}xFq`3BeF-mVoJrQ2`k*m=~iEd^tejClpYrq
zh2g`s(jPPK03ttAqxgAq%1T?At84}gulqv!-C($CVhVKPxBCGUb||<%{xVS3p)cqd
zV;=h((0soezwaBr;Qyf>2nl+$H*f*~AmaWn>cKygQ2?r*|4u!C|Nl@AOfBeK+@S#g
zLH={||9etVh6Mn3FqW|_uKF(<*8lAwDbx1fO-ld2<F@}^W^G_-V(mn0<Y?h+;%H$&
z`#<@-8s`6RpVAmrsn{!4gzY{hgeKNKz{V-sad5~)0)AD2t->2tN=1S!U&O#|(^-1-
z`w>N%3B0M*eG?-s#uXhMos}9tUd*S%AJY%3G!1Q2&yUgW@5FZTn-2G$h_1&*3-F?2
z2Zu*C+O)MPE1c)1X!x_UBud}g9OGToF1OmP#aS&*WbjR}G6i2aTG7M9;pgO@Gw~4k
z1d4j=Y5sspcH&`Cq_^lM!saD0SY#ulq*;<u1jrl?5JpFjn}DhJ2X0Tk*pf1%wC4s*
zE_4~r+;I7Vrw~5A!kyK@g%m^h2*HM&t)oVzVm?MMwg7~g6m@y}MX{wnpjbrX?<fjW
zj)qNtVjpkKyHK=F_-0NdQRjSUL@lEU^2|{=`WKa~vtMu11<x8w494?`xa&3BrAXt%
z^s_6l;`GO#VVd7*r{6a*$UR$9J22$J$s()U?M-<in#dV}<&9}0y3DMZ>t%-G87~bn
z72axJ;}?cc;j1G0Po{zPm1pKj_i}-@Tv$Y0Tjo;<(;N`jvMZ*;d#nUm3^oS1*`GlI
z`LRe;9fJL>{5)_=79382VuXA)i2IVDd^ntN=<Ied9)2b2^5k(loK#b84b8Y{yRN|^
zxm-m6e+ni=Z8Bv2;R&#QlKr0vYbh=EnM8!Ph%&m(ugA2{-CWRO@Tq+ZVd0-EcPaCf
z%7JCRTa6}9d2kc3px+?w_hmRe0b!FLw@-8;L18Cb+k;*!)Rpl=-naojZh1&bhn+)D
z3Kp(nWR_o;x3%u)01%ZH!jjsl=t1K-9R8Uc$|DdB2J`r=Bwq@D?@G+%!*9BBq>_fL
ziLzuxa!J-?uz>{&sZFj%1F8YjWXLrAEpG68Yu~{zu#asvYs4~!dh<)a&4v>__rdq?
zTHh+R#F8KG(<NnL3Ruhv%k0<JW9jRIG|B}tmtubqyo1hDPm$A15_3W@^5vdV{3@F?
zN4Xw_9~e>Y@~9`t`Gcx)`vcC@P_*5lMBI&uESfrnE$^3%qPr1+s&>lTOCFl{DTYkJ
z!!Egb@dZ0XQ)KjI{}jy=MB)2cbHZ~}p6IFAwMj?$<s+__I{E1%y|A`_CAyY+TOR|+
z?>3HwgDnHT_ysaI1>~KPI%^4ARm{)P&cG}jb>dYdDpa0=b{QUZV8z%r;I}Hl3BN)F
z(*jld8B8x-FLt9|8l^QgUpIwanOvNG;xc=W5v@MiVsWUz6S{nYN{6vOkOAO&xhRlj
z#n+6OAG(QUF$%=PQx(`KmW5@7Z#?2Ynn=}(Ln*h>*Ms`-lUguR>^+ELL&sfyu^Eos
zV&ZbM&fH}es=I}-v|DJ~{FQto-!{LRaAeTYUy5f`pMgAFcm$$P(7oy*Jtt9z!QV49
zz7Ld9h>hy1sW#B<M{d&k3=ixnSo><_+V0vH;aHL}-`)#Nm2Q#D-25&5^c7ov<D<{h
zF=>~<@1?^dcQgEnvYMps3Tkv`B@x6W-_Ly>*1z66dkeJN$9(aIoJBxyFxyg7$D0+R
zV#&Esoo{BbbN%~$SQZz}b9)TKqkrQ4`L^WupETO@^obJjFA*9;|DT|NlaBwM`3V32
zY4m?(J`W@7|BG?1Z1I2Pz5n22X0&D!x7rbVzbMt6QcnRLok+v3IsZ*}xZL0p4-$v-
z?IZc)kfpROFik_Bk36yfBmzK29<NtSP7o`YI~R5J{d7Y9ehH=W<a8=ctTdr@9?SVn
z<oe!4DlWfiEvUR@`Er8vO>}U!6fOv^K2OO#W<RxZ9l3>YTalrxZPYV<y<f@oF;jh2
z>15&l(RG@U;_lqLJmbH8ieR}GNfvY)D^2O(uy~*o&BEDv5@?azY55abJLQpMLELgG
zXrXGb$Ej5OidTVbRK1}=DLl}El2UG^Y8J9rFAt=pJZj#C%ZripkDR7A@^{su_T{fD
z>bp*Alv)AipO8j;V8rKyH5N)b7Pd|Pk3X&*hhr?M*PO|t%`wWa>b>cmr9tDg)a<GJ
zLZ+z3Y6F5d>gCu^nFAJMLZuBK8d;GGdx2+)77=`Pg)7f0v&=;?>^!F-#wKHpPUKIu
zWKoTwDQdb{+$y52)Il!aEhfc3h>f7WUyG62*6d)b;VJn9F={~u3ezM|;_3q`10j6T
z^nutKXraB?A^3F@%8tOj)DPgZA%Ws?adf5B@r3T8wwCHsmp=!rLBL^Snz0clD9eJ%
z+Wk-K%9lU}gcA`c`QlSTrbei?=FpTBw9*K%uv5j*Kv#R>Om`wxi$-bR%%5HBNsU!p
zBu=b|X9%>XobA-Pp0-|+wUy}Y=V?zNC5rK+EJaI@hi5wz?>iTvX2x>iyplu4Kbs){
z)!%7>r07$c8If&cslOJ&Q;7MRxF&yzG_s;TQ%L^yboC)>Z`+|ePNp>1NDH8XTo^E@
z?Css!v1F4fW!1kri@xVJTYNN7X8cfXUH)UW#lwDWF<V6avjEx1P>oktO?;T&HZ7Em
zP-$ddEpiUOQFA?vuNbb1Y1{jrB!;xw0PToGhQUco42M8aOP(mQZimLJ+D4Cp7fqn>
zBqEe7Uj4O5e-WC(gp2#*Vl0W-KQ;lj$%iq8TiRccLf^qNgVq3hK<N?V0r;7B5Jp_L
zA!V^6l<4~kVS?-LzM^>eOll&Xuw0!;uhmK-p)4MLMR4h6OWi9X9~Lgl=?KzIu?mLZ
ziDC6mOkn$w!yy^GV9r1GfMFt{1g%>PGfX)TqJXK<jfc+RG%}E;k-#DjO|2ac)7m#Q
zuHQ1dT)fK=V1=(-2phR?NQI@nTYFwHAE~LH?Xenb0a4-F#tu9Ms-#Yi3iFK{w(ZZ-
zkK^R>qk9kT660S!nlqM46)gmVC$;Hn9rKqoG8O@QiEl-+EEoq>j~u?N!9a!5?XM8O
z7cGb4utyn8sGri^hHB9ntv8ROLF^k{#|PZ4ZefI&tj8YET-EhRREQSV1zw1FNhvvT
zh)e?&t8Y>Bz<B=%2>_PlbarK!ZA<d0O%#NfxF5<)L2b@uOFgH=Grl04Rd8gn!j^@X
zPw9CL>xE6|SQc{BdJSVD@PObd+OrXB)SjjeNLw%O)X(Km$6W{?3G)h{k{XfBW~nJ(
z=Ll1pFiYL$d=K}qxl8xydFi&E5r6fk<lg6Q3=m*-uiejnoD>!?RZpp*+9Z%Be!BnQ
zQg$+DQMqMPB@oAKDR}3=-lXOgTusMWetoWNh_IYyqDYWR*g8YjLgasc-2q!C;#v8D
zZ`-?8N8D>%rSZTq$etQRpwOV;R9AKyyOtSVJGA5y0I!-nvx$qkQ}YDbsW|0(8{5XO
zZJa4JC7d<}Nc{6dNt);n7-Q|P2P(VnXUX|BT*S&B4n|!YQ?Sc1`V{mfoER)*2zo0;
z2^;T~79%BXmI@U7Lp-^utD1~riySRzEHU{gq>AK3>drb_?5-_5?t*P8A>(m`yse%b
zUY)RKxy##!aZ*|N*F3{7d=qbe!`p!N51D0HtLHhlx`Z*B*2-pnc^Mj58T&P+?0#w+
z41~s#qew$lLT^NG+?lBWSlLgN1)>pg|7%Nu=sB!7<*608Io|Wn`Ndb`tbqz%+6&M4
zWao#kz*K!Vs|0acxzXTk0Gepj7cEPV;#1_Z%Tlx^ejiY3=)ep*8;WCpEq|z_4Z?t>
zOh4Fb;IzC#@4AMvUaZcEDTt2|Xd9&9kzuh^f%hU0xeH{*ulX!Kv5C4~$}xdJC_u~g
z^ySZKGO##c*m*E*HrYsJ6=z8WyIzGaw^`mT+sPG~1MKOgAOC{a)^+8hFV~SB)^dO;
zFvBgIH|VuB%mGlZBu&Wpr>|6=L?Z*_X({0fhVllXh2}H>9d$lc;E46;1F{5(&ftY;
zel5tfIKbXj!U`cA2rT<tEC3>T%{{i??CTq}s#1eaLw2H5*h>@=Ir%-CUb(`8nO1)R
z9DF+NVSsn~t0X?Zb^nRR71gGElY=;YUZq()Ag7HZbDD8@T&t`)u6`tWYTS%31<TDB
zK0{r1y{|T;tj8+S895y_RPr-rc7u^mGs>*W+rnd07Mqps{iIXB_v#caw5Br?Mg%3;
zrnz1SffW~ke<36je;`bX&s~5n)(W2^1r&jKKuIZc_FS;q3L81J`Pic?X&jCA>#)Os
zY$78l&%)yRW}>mpC;*_+5e;UDC$OC7SbiO6`|P@#iO<ibxF~93@J~{?j(1-}8P5;3
zy(POONOs;CIhG!G*(|!g#noi<v+&7;>2Nd6tx}TU80(04A1QX{&YbgPO&v;8LCIm=
zu~34!C$_~7;!B(DsKz=vcD?-7?5GO+q2tbgA+DfT0csog1KgO6MP$XzLaoS^l9_je
z89cTO(8WH&$iZnbTPPn*xX0Q^4}u2AV)$RxYPP}RwQj4dw!!hZz@hkEuQx57qH%a5
z(YM|82a8I}PN9_~Gk`hk_eVUYMVTk`KTPJCfJ5k?X_zsa`5}o!=Xu~r)i>RPF(BAQ
z(1kqFn^}J=d91@Mgq+njaX#Bi#)Y3Z-^$p}HeEx)LT=e8ia-}5iEnm+1+IGT?CF2y
zdhRM6xUzJAJGWZ8k`~@y!QKVxxY(hE;a8f{dlB?}t~&i{GcgKFcPA@_41u_4kb-+(
zNj*uFr|{o3KXjIq8tw;)ExW)9AM^_|GYf44H+^Eal-P#{vr>e-lMLMF7~yQ4U0Lt*
zu1*eRnJUTe*o=P>SjrJwndAipKr5DpRB)x$f}F%*)!i<890svaB97Zx62x5}E5D;Z
z#bor{G}`3tuDi-4YTp?d2{HVE)DlKdX>@W<l{NxU`LL#LrBYuulS7%*O3wr1-|^MT
z0b%i1DrZFRsx=b$*rW{)uD)cN4}Zv*eH_uSRGdZ3@=Bw$)t9NYBPmfID-zqAP4ni9
zK2%yR3Xe<3Ss}uwDpcllz_;BQY@ogey2$(lE+2eaDmoWNh7TAI6MOO8S{mAjS>QTp
zr7idr+9TTwmU>!yV>#T{9=;L-3OirTRoCbD*Ylt2oXJ;@YfHgQH#Djudst;%TpT$L
zpO|5;ZZ`F_a3U28eY@$`)tppiT3s@-x=#_$x0oA65TxrgyrnzzUkXL+A{3IK(GnB}
zdLlNqHc?&7+}aFvz9>B%)l(4OWLiho6n&xT4x-Q2#?+R7YsI5!&p;6CKU{?gth#X)
z9;^2EN*R3~C^5`sHEa?v_70#-V$NY$J6~*t2|PY5h1;i6vk;l0*M&BQwq|7h<Ri3{
zNpKVTiV^2^k_Y0wIo+O3FdO5Yd)?;GAi4_+9|dhJ(QpYq8P#EaxSKDS#_qygAP;H&
zDG^~zuB}=Mc4w!em#qJy_mE&LIghodpO+c9S-eTTHaxLTZ1O*gx~2jFg~QqL99G3<
zMXE;ZZi{okv*?i>7)n~mArYsDHlb%-H8+=tfd|I43wCUi5PaD|!OqF`8dxH%lr)^^
znMA(4%s&1;n_R>*a^3aDpo0-s%3d&@`E;~2D;MA;m>g4_3^_Xqr#1EFLG3~!oap3x
zSx56Q(BH{5-Llrn{Eb$6M4FIIK$FSEhxfx9{UU1k;chH!pMOD|Vm2UMpj%F_?(S1)
z<A8ZHWj6j6%%#&_&qE;F`tyxWp7zrhp-h1sK8}S3SBJ*7(UinArjPiv2k5EDhF!RX
zamFWrwS_HT8{)$b>FN7<p9lX7`kz9>B;E@9^IwsX%=~{A8n24S|BX_K^*<IG|C6!;
z&?0Wh@DEJctU+yI63-(G!T=NUm2e8Ty6gpnCENzfOz^KC%ZieW504Zt6ynC_l&k|o
zHoc@Edhbg&_b(3|fD#(<FoPUCJ&y^DXsHr9tCne^26$k_)Z8&+!1B&lXOM;I9jtw@
z|3pG^_2yB)6BRn#`as)C)0DehYj?|WOw!e()DESfC_*W}b9>|d;)$CO+OK{SwQkf%
z?3?{f(XVBUxW+0!BJpr1`hvv{JaqwE;2K9h$?N6CLR~VpjwJB7;?}X+@BS;destob
zw?uIo0TXn@m@nO(YO`9e+Yp`3Ro{&^FN?;!Bu9YO5i?wy!#m)AmXt|fVeIOkj^zjV
ze=aFW*MFD52>!<<wYISRzm#qz|JpnLL;U>DHAYz~c8eZnXO1$sx(Fw~OF(T2o-?Wg
zV9eA=v(Z>Q8L;Tw#xYd8AN|h>iA*tBkS&Y=%ETMt-z$lV7}79@v0*f}yya6a$9u;$
zV7t~e_oxO)W=4-RJ)XYaZ;YZ(ZZ@={#UU1pD$hBv<U3D)Nc9Yl%$N)_WXK&=2{O)=
zAfmB$cmTyj&5lS)4zX!-WNTEf(P2u)<2Ep^2<otaLT@)U{jN6@rrz?u?4SJ-R0yIy
zqd$(HqQ>z&u#3oG=bCmj5`CzNnhw8a6Oy5I7%>1@W+Ry1(<=hvg6Y93yk^hY-SeHo
zC3`~5|Ae{)O<}Xtq3Lu9x#QHKn&{eO{pNl?9}MPTQRBf-rGCi(v#gS2bkTdmF-p)%
z4?p>`QrKw#C`W}oGc_xw5Ep+u(T+KI<%Rb9%^k%A5SkwIJIn7nx=*r-P~9`0<_Z86
zI0FDot%m|SGlyY*q`4o&8V=7EQx5ijGn)zm{L@8{L)rs=Q?^sgYwc5KZz{ZYfe{*J
zq74t;p~JrF1$m{{+ed-3G-9-)Bt28<kh?u#YnJAJH!B1`NjFqLdunxPNvYF{p00m)
zlHsLzpYz`d%YT*;Oj;P4s5~3_9Ij4J)@N^@!Q)91j<W5i=A+bz!tyb@DZJ)_T#k%)
zEXmxI?!FWT?;KmCR08+}k}=O<Jnu#{!D|I{JRhIG;QteOyPcvoFhBqR9{&)9|64D`
z?fvhONAf>Lo}-DAor|N<|0VjkO#dtT{<E!n{_zQM*i!es{6zZYQWGu)BrkRO>0s+>
zZd|wUEJ#}dJc_9*Bu$0EoQN<skTI^ed?R}W_~iLo&jcC8!H!Z@QRmTBRM9-#-Q91~
zet(n{yqCsR-DYyWb+wm&Wb@{9YNY$pUV7To%rvrmtgsA@dlGNnL^C9PpDN!^!`k@n
zzKRkmeclz(YZyD3M6*?{da0+`x@M;EjlI^&qZB$vWq8e9R9g^BEM*J(X{N&FdKlpK
zs7j(Q<|J1`z99DJMb|>O%U8L*!Q_oMDhrdv-l@L7?>j2-c+ug`k-xh_{PxTAE_Dn#
z6;le))YP5Sw1r7IiM3R6x)iH`uYnPoJ5>ag>l?Wo-A?hZ5#O^8H&s&Je?p&zBJWW*
zY6t1<ToYjXjrYBtlgy7l3L}4D&TJrHTdM8+i&-88^}hq(fwgl)lu|2K?eQ)B`{!Hw
zM}OAv?mpe)eMI)FDigba=qZJDl>N<xGe%5e{9xS3Tt~(v_x=Qh|D=7FTM}ZK*bWpb
zz<k=(8;l{)E?5@KL1<N20ncNX?1R+wmRAKf{cA^5mRxpo{8eZ*^|KhxQE<C}?iidY
zcLE=;et53D;q;OcdxuTB9XjjueP?{oBx9A>owzFuSi;~h5LTqaatQ3Jvsxd#zk2uf
zd4~y8E&&0cD%NlM<Nt2pL|oMyW>tVLq9-IdmKLx_b&V+b{U(rxON1SsuX-<8Ti9v2
z9*PH^kCk8^&%Gag&*eg3so{x;YzDJ8xD{TV)k~9FFI6{ifZjet=}F~ZB~$;tcAqrH
zpRmyrGI!91Zc<FbteX^7f%;Gi6z@1MidEc!HowgJ_aV9t<oA4?&zs{J;Q0*Mw;9$7
zbCb^Zd5`u7-Mh>Es#oV)2x_`JV0#zbBPFGGz9_56$FSRHqqgiVBLz9o&xu>2cwcGU
z9(N)mwtR>ei1;3NhzC{eoe}ST```)verznL)lG~V+J3Jny1l>fb!LCe8KVY1ay`>W
zPBvRxfZZZd&i;eE{X7;gJ(<NPX-#36??7oCkPUFw{B4BJ`5uwDipBoLWkZG3yA|=R
z;#_=z@0WmeA{LY4TgapCfXkkor5>^P-QG+vtEaM-?E4WHu$kH%mKzSCmZqC>pSiyv
zoY5p^5U5TNBDJe9kR?1NtLA+YG6FPlhl*r&k@>QAC+ZX67gYtGi#+Z)dY_H@`C3g`
z<1}5#x8Yc)JIQ9PIn{Jac4$&Z>vb)+{*sw=pO?Ri!c767-%TCl+8+x08^mGijUT&Z
zcqCyjkC|Vq|G)|fwy*o|N6N!o<%*if9h687Nr0lH5EhOk#F9!T2rz|)O;%6MH)7fe
z0C7UQXRug8{r8KPC*#kIAq1s*Ye}&ad^nAl3b0;3?tRgr7XJj3p_KR+KpFuWJpU>v
zgd{*Av1SM<f`oq<V&*Wa1Qsh$bR9Um*bE#Eq$<E>O1ADAev3I=WpAF@a|BRt;+9-p
zF2c*!w$gA6sCm47c0dy-fAda77w0Me_Ft-Hg+uUrrd?TLspCG_@-lm-@#zH!e=Cy`
zygnfFB$jf)_SoGk=zI5L1?0-<=YUiR_NXBdTvKcm;=)ifI*T{{BmW$J<qRZ<rvoXw
z8;V7Z+I#`_&;|JHPU1$ifhP)<?|%;qJU8MgS4x@rZA+RPxtzxQzOKoe(RMQAIhQ>D
zz{m|_A;017<JlwyFaJ%uI)r%4&ZCB+bZ?c^X=1%w1go$FR#rVf)dkR07+O~4hmvOi
z6H1z&BR~k-&|<n?q|g@z9<#0H&!3_i>EAFqn4hdg>{hIh(jhSKC&xl*sK23cmwHK1
z^;cCot1tcar)mTd$vqWPkA{c{b!TflDPqqRfD9<3-3Hy?Yquf?(ZhnZ1HPVEZiTfo
zI7^5!U$dVx`}}6r#Bus~r_Mw<s)>~RbI0ku(qz5sJcH`CVLBvBlOz9^&shy<CjkdU
z)QCn3A@4oF9*o9{hQE{iVBIs)vk0)g(`tep^ks3MPwV-#|99<^2-01BZZb48Z>WT+
zL{O<<cFU!ZlICfSvA#m7G|u1t{pDY&a>Mgd=Yjy@wtc(dk4sGa3_&8=H-!9`pEn?g
zaZ1+T;uG8H_wBVyFX#=Ma`v44@^*jUG4X0>5BL<&f>e{B94INgt8goPcdN8S$=6PU
zhblf?;VTdu*4sb9T_oDI@G_kWs6>ZzXH)<Zs9mJ5v|4fle?DQtm#*<oSW7=e=j8z<
z7hQ;s4R)z02_8YzwSV2vc^P23sucuEvE;WOIKl;S@DAeEDLND@Two0(DY=2`ZV1dI
z;<s?DEO8uo>t^+3ZIib_Z2xGrw|`S=8-pXTouP!z*j>17l%A>KO10dmBS_HV-TVq1
z&#-blp3qhVI}B#gup3bS`VYRdo1!H5Qsvq?IWj+8)gh&??E{Id^{vDU@NGgkORCRt
z)@Dfbdi^N^5nQhOq&ws}S~`2;njnf{q9h{;ha7d*MH6D>XpMkNr`<3|3yF(b!LaCI
z-K>U<XSbkWXdNK#I6Cl}!U4trC|-Sc;DFhBJz<k5vuL6n@CtAI@BO5fcR<R;f>H?`
zdbEW$Gsg)8Wqna6Ie5F8ncK+t79#@dXT|WcPV_93<FSaif}ej#Y%A7zLJhmCID9IO
z0suFFOt$Tuu9ac}Y(XSOky8p#-gWdzVRV6xe^7Gp+5yp3u~fM6A6Q+JC7>GW28k~g
zIG5^^<RvR|<xk&mZrH3CTuf15x_VxV_cpgf9&f_U9`iq~G4;;T3pB;1s!#iz2Nysq
zLy+r##KHk_X=9l3``}3P_{BIveW{>8Pi!qdqyG@G8Wryj>Xr$N{{cqKYiWlYOt*)`
zK-PaF;jviqT!GSiM8Q&{l5;{~Q?>Vd+uN-?jBQ&@bNxM<`@;9z^jn<4;|-7ao++X6
z{r=eV{hpXob=IC#xgr7iD<$3PbwkX2E(K&g^(9&q7MxQM006EsnSuW`=xEd40=F?n
z;1jRga|eJ5uH>pF?5~xHgQrU<^oE@2tbuQN%KTJ3#U4mUd~XjA{hXoU2T}Hf`k3ey
zsGx3wDPevGH*=~s2$MYoSn`!`3JWJ&Dm<);u^CuK19EAI;R6JEaP00HM>fd$T^yWg
zI1E*Wma&Y&hi2p(?H~<_60s#;4oI&L@PXPr6`<&+up&|}nFHbn-5a{lEE5&;VW$?T
zUuaIKDTbOgMh<IyaTIZ{WsFV$^dOcRIwJurLKUD{5hPVrG}td{v|dHPj^#mu1{k+b
zp#o`m)jt|$9lubR28>WFTOP~pEn8>sN>A8g8n2{OudtI(Hhs%E{3;$Bb?`m3dM<0u
z@8zEpUjq-(h{@bi=;xulIgjuaPp*CrlrS8e5fBj{pd9h=!jaaG`wf?I^OI!hFVlp?
z6o23qOB_TG7WxvxEe6=7*`g{L5_GmsnP0+R7wv3N#B&P<Q&5)XgE;iY-YJcVGlE(z
z%8Zswp-q7L^Fed%@zd+>l)zH`OfAkF?}8HaYMKgLzp3sVOW_ojd6vW5h;3jM8+7U>
zK|D2Ddwo}=Qv6VEpLOoWK;;sj8*qrL6H(0~@?d@>xDrMPbW^x=1Tc*PI>KxT8DS_z
zFb(8BlFi)*e7kqc=kkKP7+3!4hIN0hz=lGau53yf0SAMC@&J}BVe<0A`3PGhZ{K#4
zw*)Up&eb?xR830@ds;b8MH(raL{c4z9V{86e+C#@$WVMi&CTdf$v`X(xM1w9?u7tC
z!b?z$^6#6rh@6S=!sZNCFF=H&Dhop457YXOB;3A@K3rrtKO2W9A&}Yz?WhC1bV2ah
z(IUPO*x*^=G{3xRK<{~Es1Q~&1c!mYVM}sF09;|q2M{fSZ~8Rm`X|Br{$2baKqnL&
zYkzK6zKNL_)PewjfiBkmnVZjQ&Nm>eA)G!ndqP?2WH`bUcPB+eo$ou0T9`(<p}T$R
z!9tW)G^o2gha7^uyy7N7)`#EM#Z8x5eR#P`4E4&UGltYaU7HV&G5D#Df)aVO?jnTV
zWmS7}*(;uiwD;gz1kVJk6PRA;g$nfN$bL0Riyi+~JWToYJ|5(~iE{aolB21_WKWcD
z4SAh<KMcJ(+hepc2Y^bIryu!#@2Fx?66s&V*Epoa@0gqB*jz<OEBd^Vk>WR6%u}Bl
zuS5PAe|TdA(T2Qt^E+frc=AfdDCwls^s)S{8tR2YKqy%8&*Nyh$datX#kOzW{y}t>
zPC13^;6>3Dqi(UWoHe(>rd%2_`5uf4j)y{zv621Ap>q1{>B~9(>zL1Vmrx^wY#C!}
zaA^9eiryCRxaIoFCEWunW$Vv>Mn}qn=!_R-ls&`AY4J0SNrJl<XwEVoyLzadJdCG%
zSBZT@49qZl6C1uuQ_}3aNH;r4RFhO3*6FZqB@V=rE_7W_Cq$Mah=o;P3a*zxk40y`
zX!@yL?OWp=tUjS0kx7ugqNjW5ucd8R=kds&Ap+<jD*FdWq+!z%X7!OJGCibq8vVJH
z5HRIfv)Y^7$%R~w)xNv8S;R5vm%3ecXnjmTyz6#oUV<Z;!E7q{0EeY}!2B-)%;2&O
zS<Z-R$uUEECu;42A-Zi6nLF@;I;;k!WzhWfYP(g^W`bk??0SK6T|u{D5qBJF89b<j
zMQneFc^z~?%|V4oG5t0;<AtD55iPBKN7R(v*94N|Y{FgEPKzU#RC)^16*8GC?N@K+
z6(lJ%vd9rXBUi*rt4rF18@JfnP7(fu<NZu8H*RPlN?1C{+WZ}1WW)T>YVy1qOoX)g
zy;c>n9KA-APOzE490Nt!r78}K&Xfjq#MX$n9VuB#F%b>w?Z22{1tcwZACT)-l!l}f
z`q>uko_;!F45H@VEnek3orC`J+Wcu*3LAiwrHYl4BtF%D=^JQn=npYn*$;R-aai?#
z8dxA1gJRI0GT++C$95_-xOo(sx=~JRe>M%b(-<)K7uFtG-{~$p#x)I5kE~h{Xbdc(
zqsv=m)|4@#pUe(D==LZNbWzLWxRo{=Ss<I<6S!$PzIr&tA^)2X4Fjv*4xBUdX0bG-
z&dV=;BZDTQ7tuf$lsGljcE&1@i=xS`?=XpkoPcmB{nr4a^p&L$A~~)fW`oB_${JQ>
zL^*qG+ckA(7x3#BqO0mti8yq-kh0JhK5SI;A2Z2&@J9wR-EwuLMa?!n{sW#>D)P0#
zt_3$t%IR^rgb=2o4#ieq^W9T2;57Tf%kIuU(snOibPr82m~P|KQ9!PMyTN)lt+2<n
z$V<m#9W?EYagwd<wGM<je1Ux{)ad|;UJ%13d8>fB+EJ)n*+m7tT|nR=BtIH<#D6qV
zM;g2%L;6Uq5y*v&8*@Y3pslCfj^s=^E@rx|5QuhTBVBNII9r3%#ed#lzQ)@HFynRG
zqDbd{)XDo<nYiOJ==Atd=iz4!UpFJi?71SSJVi`;EW%PWJA2puHr-!LtS`c6&N}VQ
zR(mk!<N5!g>ztNEi?%JBwr$(CZQI698#`^=wr$(CZQHDUZq&oAia1a659U~F%-(uy
zzxo8=e4%Gh+#D*eA9|=)7PxNY4O)vyO~Ru$-l_^G84&&#x~K%U;1rDhAc=*;y%hBR
z=s=lv$s}dLx&rc*TXq~#_14~QuauhR7m4w$lESo>sigl%yV+~nMg8j>R2R>6WD9_9
z%Vc)aAsl4V8Prr;lvD+5z1QhccA@ZejMCW$Xt~(vnDMC9A(eK)_Mp|Ts3^SAiGnic
z?I)jm-0Q3yf@iW)pi@w>FmuenglVpZEz0dIZH>%P=(LVVT(@FabMrS=RpD--pKRfC
zh!C9w0~C@qODd>m{>Mwuby*3f9T$AaoIw8$sSuAN4-8Q_)<O+DZQbV1Re?e1h|L}c
z4Y|RujpE6~!Gu+B$`8|URBhQ&CA0zVUSAwV`|oeGEJ#8dixQVZ-3*y)3AUc8_nfQ-
zJ1aJPD7ZbA4nVWUum$?7gz=7hB_Q^*oN_BSl-q-OobeJDi;T5KV=q1knr=7-(mvR`
z8bEN0)JZ~Isg}tY82_Yd109~D=o|1XInt8t^rKGDVB!}xGU)^;!PaG^^`Ae9jBTP1
z82H=Meh=Fe<f%q<H71Ti;~Ii-n5%klPMhn@WZ6pR%Re_1w^GhN!{gI6bXHd`+Vx5q
z_IApg)$sz5O!En2P78a?=Kgx3E^2A^IOg7tK<1LqMC9&#5-m<kFsmBr3YBc%;T#>*
zeAM^Kd90TS3u}ab$|Z<+pB)_^S(H+lGZwc;9L|by-$)GMkpHrKDd6i08#2O8$~G}h
z$St4W1`zeef6kIWj~??VKL=cvCB}ZjGhBoR1xzlAOVRAN=-EdwxM4U0R9u3G^`c@d
zu+F-s$rBF6X&5F`Cb+%a6hk^H<KW_vxR@avAapFwp{8>8kJgCVnRfDD23CpPJ56ju
zJ6TEykAp3is$;*a#F3(oFZAF+C6?>-D<nilM7S^OmO;3x-0e<$GK20);=PA8Msk=&
z0zBM_U9=DD2Z7`|=m(W+P6?>rGM#Zj0q3M_UGB%>R37P1K;@i;TplL-mX!^GCO@z_
z$|DB1T}&*cC))@F+95cxU2waUClDoiNtv|dICm*rsFysVtrZ2#BR=6@{Dl#@E-M}+
z{0jT#6RzPvh&?i*c&d(1m~&YfQKkY~JvC7fiC?E0*1Y>GX$g5(G3hLxct5{@M1g<X
z)o!TR5m=gk+w=MN4ULI2y|(AGrtZn!aVy-4{KW=-Ytn7H9yk9Wh|mgQGG8sJ!0l)l
z(j9?^-MRzN*`z(G>AkC?XSD4~#I2CgA^NiTO&id~hAvI$7m7*&oux-1bC$8we^`d8
zeLPsHTNAm_{Ek(pBKe7IxVo?+X&aW5lsi%&hKxxwBX7<vfr8vH+VR$3Q|ZS--<^ST
zoG^mITGI#OTCvN6<9_fI`ris8bseOo5Jvi%l}Xk*m$<DV{#K?Prd37seoHBvK5Zup
zsjrqW5!_$L$kRCmj!Z3M>Q7R>bQ&qA`bY;23I_whANm3JKvM(%lf<z}<+)+1IcKFP
zIRNbNc7TqkT<`6Gz*h(ZM2%c=v}_MmFZ*kkH(<4Th;HmX7q{OLQo$kAD;<ZO_;bUo
z8gwW!E3Rn#iEKZcIy+%0_})Hxt<33E(!eKr^P60q?S9XrC)6v^%0Xx7MOCEAKM9>L
zuahH<iR*y6nxUII9)F;2%OqBT%LaI|JhN6|bQ*3M=gka5btWbG=;o|_rWFT%&O8sW
zn#xEqh6e+ts)ZbVI9g$()JN1(&DXEw@0@5yK^RVGsnsP!{f)2k1|3`JrC`+w^+81a
zIElxBGnp>9<s9TBvMkx;u&Un)-@t$Y-{C#ukSCKyE{adzRAq2z%>|)G650PX<|W6L
zt_=h1s9k!hs4;t(&p26JhOK8cc=ON|tX$!{@UqoMZuDclxBOwu>~<5)9i^zokU(;O
z(liMt`pCpgG1#IK)?sQQKfqC|Qh;#csLnW91;7Pd12Fx`34(5OU}+ycBjbx*9}Ir|
z(B2D_=qG7pLs52${J{PJuX0ORi3?vS-F|SOI@Z{gupQWG34~2aG@sbKua>QbANBDk
zN?mdrH_LjDSTxD~6w`_M<zx%~4axn@)qh>5mjAIhS-57ZqBXZ`x}{I^(S9+=e?Dqq
zV7tuRU{oQZW<iD^+P|q3srO<7FsON;*R*r5NUA<~dauW{jp$MA`54Fm7W-=6<8O-4
zbP##4t4Xq^p3+afAvk%v6A(z#Hwo83462WOko`{RnI=XI*0XffH<R((6?DJQoTh(V
zwcO&d*>i$LGnG%Wikno#mz7Q8mitEJ3$m6uu*M0nlCz?5p`0~dRRJ4`k{>+ss{~$4
zQHPzVljsv2Am??ZxvBz;lU<(PlE0ek^SQcWx}P=x^^ggBb@C|e2L0lpS}gmBCof)L
zd#5A~eTBl@33^EVQPn$nM6L&X%cuzUUNXt$z|h*LQ8Swm<+*TAYqO=;5T|Wny4ge7
z(TE$w)b%W<PdYGB-o_0Ye>`%Ql!r$)$Ab$iv8_p;dZTjh|Gk6Ewq&x_(qQhhy3Dbb
zT3&vgd!Q_|WWy0-Q$lio{rC>$nT7A=8@vn5V$iu%R=+m>jlH(><J9By*uzcZraAa6
z(^(-&5tU9FOzk-hgHl@R6B29p0c_h}{x!DG+Hb690OLzdcUib{z6?9T7Pk`}f#;5V
zN}DZ2w8fS1{k_}2#=8QSeE+`dwEKPe7_4#sJmLMh<=^-9@%+BLgs;v0j`u*_{e?$M
zl@nypRkF#h)z)V`Fse}e<*Lik*40+n?TKMA*`FlQ#j-$3W*LkHK%?qo_Y**$vUqP^
z9LAJ{9UGb@^XDehstFPDo^;Udh6TgB-_b&uD(GLw661Mv2SMB)(q7sD`?eq8>?{jj
zrbVCJ<9FM;gl2o1?wjhZ+vW!_U?&WCt^w4U8&h$=b~$1Q<bRqIi=HT#`E`BMpUXUh
z?YR78Fo!DwTW4cADpqMAG$B(q(18S3Iwh~poM94xs)OM(=R?L4CCMKDhm7wxz$n6F
z@*m#FwdP)vN<weu^6K%}epN3Lsr|h=2y^k<ctIaQBA#JSvzX~IJA+#6G!~*guND>r
zY%USu<W?M&7aD)=ehU8bP(U*ap?NH94rHW}H@JLd)4)rHoQ9<_q<M?VE5dmXNw~`x
z^JZj|87Z)7=T_dHvduUNA_T5T*<w2<F;EO#gEl%~i3a{2`XMEeMVeL+H01Upsb?tV
z04uikk4du0ZemD34#yjdU?jZM8>^rsO0+YE#fW|7NGVAga`Si60oc@)9b#%~Y*0;5
z>AfxOvOh@S17PGlh$BaA=?KTN*Hlc1N+GoD&o(K`{DFOxJ|M>UW3~S*iddz$7>?pr
zSM$zjUuo9FtfQ$D8m>st<o7ls;F%^ZTTY0s_=k?9R7mlM{38~dnBVZ>Zfv!UXWE!F
z^d}mf(x(i57~U3<RoDr-lMk<b8U|^<QEUe`RRB#K7pULnnL40^nKmWT@R-1~Mn}~t
zDGB&D3Y8a2MP%j9J=oXxldp1Pw*NCL8y7@Bt;~8MMY4x4Vr=qZlHig~@QCO&3(xjJ
zB+JPoWK?QEm$Aqw+`Go__<qd8Fe<DYjvJd{w`48_QqzY-o+x`Y*~y=)IV13OExR1A
z*)hUef;bjyP{_uoXkdXeXOxhw)f6ZtJNTgFFgai8=y6(6j3k=y;ToIs0xK$a9qI#_
zFRa;^PwfKv&=M6;@GJgb*Ai(J7Gr|pJ$~mP<l*w?9wGqFW=TvCDUq!pb`=g;r-^yO
z7Lz_n(?>8z9p+_%c{I3Rw#^;BgEJjCYZIYp<LWg3eKrLVRZ&A;wzSDzj|BThNCye%
zsa|?p&yOEH(*4QrAClbwXDyr<L2vGU3L^YTx|V1m&Kv5Lv7eD%ziUCaEX-Hd?PKd}
zgEVp@2<gIqwW0xAEa|c%!$df-qljjs)g)r<uxxov{Hp-gW<szo64Ntf>+R+2^}Vs$
z=PK`#29E}O@cl3)kP^r-CJ-k(QzUzxX@n!>AtNJ8W{kf%3on#8SUNFs4YGW{4z|`)
z$lW2w?G#qK!c3pWdNeg_FZW}<K4s&Hgg&laqgqw9Y0r#KkdFjBC$KWH==+JCJzR#G
zq1R(X%Y5&1&z%rCwsBj0?~cUx;8@Tn0&*ovbOE@W4*^CpSh1P+Tkiq1+Kob47U;6u
zV<6t4TOrYbia8Ng<fHyoE^E;x!7_`tPkONu9q)uBXx#%Zl!tfWR`+(|bqI<^duUax
zD_#yQdd5rSIei&H*4CH8F;uRudUsDUS&(fSGDaFHBR-6dvLkiH<85O@<%8GBrwK_m
zqpJhod5rxj9k5W+IXhdX0V7qD!aMMMpu3ScUcx+Z;g3KOLkX04!nT8IHOJjTvcgNY
zU@#r&o;AZ0y#-eospOsllZ%pSd_~EHQe^t8Py%?j$<y*U9vPKs=?(n=acv%`Z?Osq
zAete_=!ebvG&~zE*M)>$e-6Znq6*h7Lad%-iCoJ&W~VO+;4m&$txl$8fF60&X|vzT
z2Bx4-g>3gZ^_T1Oms;JG7)!JRL^mi*;9FEyc?yNw@XPsV1nOzk=>4kfQ7&Ll-S=nq
zH&EX-z~Hyx0(N^Yxn-SN&YTrJh6_(rdb<7?K}{g@<fu0CW5n!=mN(Fop6#))A{q0z
z8BVvvK8B=#$KH8(4+t}9ktj$nPQh$4c{t)gLsZVheMpVan_XZ8m%Oiqws3?WNroBQ
zf{pU1nk3d)LnB;j9xkNW6AicWZ{SA$MsuU_&&SNR_&;l?FmqCp9L7bTdLDV#n2H<9
z&nRGh$Q^e$DB8St01{wAlcPA*QPp8Q^cqZ&<ZL!j`&fK_#E`YAtlcC6+ZET?xY^10
zR&iO1Lj{Mb5Tz}LHnP!WWH@QzN8(yF_=JorE4<1wv)jt>5ADO(khmF%gd(S;P%sla
z*aE-B?+l*!W60YVOaBw|oE@4?ql8tF^|ZYo>I`k=g_H_-xa#!>jKnqF<VrQ9X?(`t
zabU6CfvjoY49*ICi8JJf&14xl7cl;U7^z!-a!BZ5fEfT|8KS!whjwMp6F|tFn-hpE
z22do-+Kh5czGi%BT3sE{Ssw+K|HW-4Q@-GsLDB?z@kmnfZ4ri{TSFyH6X$#iQ=U29
z?@G6b8R<A?D6=K|XaiY|1fk<b@!wGU=tp!Fj$k{{VcaSmk;CT+w$Z&K(H8W?EU~{+
z5OPg=r=x8*`DcKvb+L(ahU*KGVu{v<Na!3tkJ6e^1Nh}p+JDF_y`_;Iv?!LoEF&Gw
zOn{=k7~gRCSx~UG{0?6-@Pj64yk9R?{xa>T8ICU`2Zy6?1)5ZvSB-Oy;}4e*h0Ikb
z;oSfFiXt~C+7uJtDjO0VM6jNim)f==_KF?!UY+%K55U&ud^HH3VB2o;<!WemeI0EN
zV`WCa>gRMJ!7A=!rU*enpfedCnw;hcM<TaN{60~h5mzp;^cYQ<|C($lKn+CA@e5m#
zM`^nsmxm$5=ziVY_r!tH=G^T&KR+MC<Z+pM-pEs}t!PxM@&@uqW*L}twauHcZN|P}
zeF7-aglH69XpIhcC%V{J%l{Qa(q0_!RqU|_eRe3bojmdj>y3`#J+U*?$75vQ%}=&f
z5uWP?*PelhxJ%(Jtu-f#zy^cl0ez-zUD7ASVb(n+7dgoI#tXMb>v)H6u2!xYE9(B`
zvMZ{^c>I1slBaAX#+=R60DAQpQ{mMFW2>mdBSz(+s3fpr<*qOo60#{X+?veR7K=%{
z7$68J%{!H~d8M_aXWhYP93ja5`D0bhvQ5lB7NI|iA9xp!H+a$WDQ|C1oiS5;Uw*Pt
z<8<Q^gIK-(<Y3=BC-nn~(9=QM0n7EQF?y5mP>MgiQ5Bk*?~(PXv6{w<?28QrSs-?4
z`3kgp#>fAct}b~)7ttiX)#~4?>Yu3}k##9$*%9><3ffoT-G<Y{Vq(+I%uVJ5Im!^9
z-LnBmF0WK0hA43tvQ?2R<9*$|(P%q!^pNJ)efw6!q>~J_W9AEyrEj7s(c^oP&I3G=
z&t8#U@Z|Hvj@!0Fpa3O*i6S!|u@YHHMO`TE&CZ#lJnQSM9gtR0ScdZ*9pBI7=<CrV
zyo3}*5qYBGAD-hy4u*Pt;g3h$Azkl$J6H51?rfyhNuAqHRPK3MvFwoVtb=wV+|z>g
zif}Y}XxORuAjL<^&9H1F%|XgjY;>QS?+@4Yn2of~t{UOC59iQ>cHFkw2&+X<DV{Eh
ziwq*i>d8|zPs~*PlMTG~)C`+QzSfuA(?hky{)*_$INx9Nh`6w#XxI@`i?2_L)jvI;
z-KaU|N7njk>W3=Ao$j5dywG_5(lm`s0s7I>A({9tjKE>0PD3VT0CLFEj$vJOkO*tQ
z>pupMx;yGnokg+lUj9>4wz2CDM4M(gv#;B3lD&0U5*w_WFn=Qc^00b^*qrVvw@tR6
zmT9*yVuQ0X$y}7o02Eb`aEi*M8x^wB^bQnI|C5n_X&n6Rk#hma;M#HG+xg^(ox%eg
z;^=B1IJkJopt#hb$lVU&cls6F)Eqos90hxxtG{JQs&=s09-S*umLi|M3z)rw{se%9
zl^}>_!b+c8C|>JFi?1uiAb(9(-eFgO<KZZ`E~VlZMA}Mi%UlC(2mMHe`JNS18jn?u
zn8y!9=)|ba+zzizAqrW-s1;40qoi9IJn3=mpvnOl9lVQ7jo9Pk^HPI-!GqPZBRBn`
z+I67eui7iG07~h2k7eST%Nvuy=9sE)JJ!Xy&EJ`&+_6vWDSd)ieks(On=}SyO2^uN
z3Nn1jtTaCPDL+zs46ypFnH83vjb-6Ak_O|>@%Qf0L1yl2^d^`4k|U#in}_ddw_?~Z
zoWuj<)w0ZaDl>l4Rb*SfA%yoH(M5tL!{TNqvWm)U7N^+ZX(L1%oEM3LL0m7tAuegx
z;I3o1@pC|ym|<Oc9idg)&k9jprA6OJofiRhCZM<om6gRfPtZe+PbK>3wo7mEToFnN
zX2~0!c7jmZ2KZalq6r$L6*1S!er<8tN5>*Ru1KL|0t7PC>!aE=a?dP03959sXjd|}
zA;9Rb^5MsJXOR(Xha9RGxj+PfFK<<QNo{a6d;juY84DIIvIg;s@bk}QmrqbQ0-lIv
zoY{;Z)j);Y;yioN;?#M+>A(imv6)1BCVoA@{<WCIxrv~C0)|uXjv8sqw-BUskrdLu
zfEAfx0R`R+SEwbztyC~&e>m=<9KL{^a$~Nb95wJVx+G|b|02ET3b`HE)xrWxY=Bhj
zu{6veWCHS8rbgDe_Q<k)xmG?|OzrQ#FCq*F${B*v=B`HjV|1j@4M;Anj@_kmfXH?l
zTe$CJ<KfgO#>8h3iLmfmcWg&#g@aqZ8bw!sCd!YQ0CEx84}tywvM%(}H$Qqv<M{oY
zGU6OHv~6O1I-E?@OmA`0gCC-#i5_<?-Rl@wzY^LWlviZ0iSIpdGFk$<?jKYZh~0Rp
zigjaiEfJrUI#zQy61gWW;0+;q*_+=Ud+n3V6Gdt08k;)59*W4QM~ls0v;O=uWd;zD
zOKm@7AnM+_g`rze&r<TcZu*;`8t)MkIQ{NCW*}bU(qz4H<ZDKqGcpJwP&KC1Ug?Lg
zc9U?;F)l252h9WQPpHn9n-U2*_S$!C=h%1<(XDSNo=sxi{##K`O=mtFV+J95cA%50
zdMRGp8h?;8ns6|r{07-+NWBqE#vk9!gXVI$PRHmZ659d#g0mB!JHXUaGL`VNAK}gc
z<DncdW!BMXBW%mW6xK8;<s|;k9eXs;FB&GC!9{YL6^1=sWau1pQP2IZ$_l%SPr=d`
z)E41nxHUKCf|+N`(O%uxg3K_ou`*<l_I9DczrW8+;$_oK31uz<(rKy;B18MlLv#|X
z$o6P;GCn1HhzUp&Ww|6yV6e0#sN1gynMA|?c67bF1~e=Xca1?7F&40JXKhF$D^V@S
zcSn-}bD*~mfb$Z)cjB)I;2S0nyE$2?q>ysPK{%Qsiu3&!m4?z#dkCE*;i8bDGn}z`
zeOa$$b|{_uv<4f@T7eK-cB|1XlDxVOCI0y-@^WkjmdpJMzNSwqy&JRwa(HDMo#T6%
zeLXa{`4OnP6AsDy7APb{qBYXdXpF4mb5a7UeZ-t?H&Q#do66^WuDk$z7=kz13lasU
z(H6A;zDZ9VH^gLrmyyJ_?n8LBSPadj1kbCw<6s2^5$tH6-x69WQ@fHSHNC_*{alK;
z=eRVI1F1l|k-f{T-`ZroHzwl<xL4ZbNxh~P@>4c;KL^t)>Cn_e7v#8=pqmiq*<`D8
zt>N@>Xk7}>ZZ%^Zex7k$PQbgF@b&3I&11)HAEHwg23VG2C4QvA)iJclyQ&f&e>!BM
z&>3_F=;i5e01<Y^Kn>5#9P?!T_BgLzht~|mC7s#bVW;m;lUw8R9e#$~RL`3U4*tSW
zH49T$`K!T(n%{ym<xH_X&N3JG_EmKQx8yFp>3}hFvz2FR`nge`#N0w3-F+K1n73ca
z0eoqg>$M6c-*;wY{|yBux&=$cpX-cxxXV)61tuQL4Ek|dDcnu=b$?aL$3Y9U@ZBPB
zCfV8pe-~+uF;#~aHkd!Oq(!%bgQ;7<6SXf!KvMD|SU<}97ndu4(+}q?r6&!(I#eaw
z_<*rvEEeytU@y#CT(2|;O0u;gq0cxNeHTd@_nW_SYEWJ$oumjr*H)Bv?<#iI_fP01
zqUfd8^Uc<xX2o|g<7+m(v;q?_hmsTZ6)(b+M+ep0&2$4kp9jhqGS_U_F=B^c)ZseU
z46v!8i>7}{S8|V@_4alTNps1SV#s{%hnQ0x@RwUmBJ=~VD!feB-PJu+_?MbBvP#j$
zG(rB*=nf78M@+$%VD5dLcIN7@mxefT3lJ&X-$L0~H0e&faYh~>WJa{yKzXBSnJa<L
z8$*T)=N`+@%ubKOfx(x~#9^<<hMaldrMp`*<_6EtAS)Lknsdu0c$&k_OKEo6lX}<|
z7*3Sd8DRR{Sd<XN*^WIRcnreqaL7q#<8ZDHs!=64ZoMWO<pe5*Y2Rh0FJtDhLsNVt
zm@+_c9l~wa-BXm)3oted+Ea`GmUtmwrDJU+Q$#5=ipMq%_|sUlrp<^>d)lV#*|p)m
z`s{$*JyM8(Zl1=Q0HGj;jhJE@fT?mUaU>3UL;F=@$GuUP=AMkN%or1#Ha&~N^3b~*
zW30w=Y{~8fRcGb$>hPtS#xFgY)BU(g<k$t6kQwf~B7}YS4i@pV-4qsq___v%Yia)Y
z^+I5Xh{@`YDx^#7yx8FLK+V3Cg#x+gf!i*QXf9X3^te?uqWNGcPiCE|xi<)>GwIp2
zKre?6VFO^WwxX<+VuHkrxJVmU!LJe32L%}_aV`%KXHMKsK@?IT$yAIdC`{1jNEGRl
zr%W$`IUen00jBra_0aD~*Ff$4kU!Jav$;w{p53<K=IbhB&iJo`YPK)H+_NV#Y2VOa
zgIP>BuD`=Lc~&(c^(#zV3<TRD3jMS>Yb7fFj^vl%7EYVl-yTd^EVdu9n|)Q?6M214
zV>tLne2K=%g%Xc@T5;A_AV^|TaSy2!UauaIPJ%CBtZ!y2|0@^gL_{8y3E(GYE0X@V
zdv=q7_3Ja7ZH8VeVP%T=g57O9j3k_6xzDoIc`H`m4*PrIr{k~@#e`!_LHW&2f&9>o
zWw*uNQ1Q+?f;Bo*BHICZ)F0O<^YaNi#euoU6BZ4b!h?igZqhgU2NdE0uN4A9eA>>T
z#pWK8rihZXBW4Fd7p9(534$UYV+hmH{)^9ytd(uPm48g<wt!o=6?Y`>*w=8RSA>WC
zfuDO>VO)<J$;cPqTrnx@VT?1}gR#XiRpj4~MRmIL-X3P$c@-#J0gT7cn-7uI84NY<
zar)L0V{c|tgjx<kf~W`Y_z-xyr2Ix(>126x*tn4xWoSB^J$QakhROivVi+PC$wynd
zB9887p?ia>;XNu0Cknt=|0i_W5#16_H!OE?Mm5NYG}TE{IiyMDyvb5Z%TgcM#1uo9
zY-UV>mZ9EB4FD<XBw6sJ?lvj`^XCtYdTV4>JnvUjH-l9U{KEQ)m|%)`#u?}I7<+$i
zhjW6-rtX?j(@wGM9BVRerwZI$k^sk|Uo!x>g^U#UQD;N+Bi<<uJ&~!Yd0^pwXCIB0
z-89Sy`b7*Py5K`nk;v|pZKF}eFrrE`#<}7aKYfrNvHejOJQdpy1cyuo{BJE$mWoOy
zlD1MOp#Z5X&b%G$jGdJ%vA?c8E>c2y{qS)OLb>vD!gQFVikS2hyU*`*?$2%R5C4Cn
z@Tz0FJn3`*0LsVzI|@(s|3Mh!|1}El<ZNhVYGG$>V(RGhU+Y84|1XR2pEFoPFy@dA
zq3f19h;#GPZwpNVE)ud1`pU=;ryb3Bu}H$-nhGJ{Ys4-M{>`|Yj8rp$a(WsoVY=q#
z;^O4%v%EqN2$Gh5W@*7!t;MM%F}mq#T|%+<ORc+0vSYXAb#v0t?seQ_yz{prnY0+|
zdEOPffH2+GeHvdb{%q*6U7wMHT9~85mxfO=UQ+$LJSl}^nZhc#TBp$d;-lVQD<n~!
zmePEE3g2bOOfkKf^9?9eVxV03co-DFtF|LzVmXFHaY#O5<UCL0`S^47P*kIulnyC3
zHyfdvt7Rv<+hRrFt*TR}*wWRIM_Yr?!)1o}OODh|>-5~tyiV=>vsxU9c6&E|O!)Xq
zQv)?<FHtpYJ|PTcaT=yhHHf$cNh<Qjhk1f5vg6jX`V-HOG-@KUfUoa{ZG$VPEGUJD
z=#6k;{Ty|{F12!u(Qc^Nb%er?U`FLK`H_ml%y1x~h6u3^68}MnS4g4xb@MyK9ssI`
z1mO>1*HoMhr7!t>g#HA;1J>LnLW<Un>FxO!)Iz2N%@VV5Hq->D7;8Ku4dVu*F*OL4
zgq{SYP(a3$u8hhxR{j-Z(?b!+fW+_zkpqfBJ1K)`@*HobX8$LqE~+OPaxKwGk-=X@
z7q4(cNWwLAu&$}qzV(KepPX2rT6A?fi6Z*z)7T;KC0eKM+seqGLYxI9I>qst_#TK)
zXum&*F%TUU&ej`f%|wY3D34lo&G`)Dy%tS_cycKEK{|xXq4z}N`sXKPCAq0TKYFhz
zq#DJjyA31`FjwCt{d*Qz&7>TXX6*hACbZLbgIf(PfG#F@+Po@b)j`&fM9$%?0|D5?
zQgSqw@z2nadGPl>fYXk3=FoN8!~}nPIH7z4;2&7Tt=G7#EUGo2pkyoTyUKWp(ld+)
znbIPNSgMM3qhR1HGi)R0g(c7@n1QU{VskL<NCJ6Oq6=^`p`fn!bDOsu6AB!f%c7%F
z6^Q%(#-)x<G&I%q3n;BSoYswBu1VE$^gF7Ms8GOYtL><<GBWN!#J?%tc|#EEYY*H#
zBOdcom{L<q@RQXRXO+UAYH$+MCTu`ZpcQ*6hu3}w7d1uw8LM~Q(8SRp#quuVfs{ef
zW*?C$&&F%u(v(~7oBFd--562RDTrkn$DXIMJ;ylmUYbQ>21TcOS{m|WAXLvw19www
zJdA})(lDRDrW@K5(gDSZuft*Sg{IA6%4kI~86+bVk4=Fdc}KyBM`O97Z3&#!WG)lo
zWWT$h69Um8xgb?|cW|f0pv1@7LPGpX^MZ;6_y@K^5a+Y0k4}G{2m?haOg{{cU9y0$
zJoiR;_lc8ElN(1^I%0fc{Jk*Wh&s^>9}K^Y0%JT}h1QCWZ)-DCV)c|AgA-F*E)HLg
zwQ|4Dt!7GkDx!1%c)!!lfYt1`J3;GTlSS?tdrYzJ$Ff{2&3)2@jXRyS$|`ZjERPq7
zNp2`8_N64vJVG1TPO-%6$d(<(XFL4#1FIB~D@gbQ7OQ<pY(*I97_taLqpjuL8>Tn;
z!xY}j=tM$#DbBl&ekfHkpV3zx9G@i`Gz5zWI}~RsDC84~8a7sl>^S0{IQ*oC&&?6|
z3~}$K9q?)s7>8U#*lRR!@{o0nx};A(@mGkkD+WZXv0{%2Z3z;+b>^bG=-Hp-BqG?&
zv~-4cnk5iA7IzL+-Iut`r!&JdvRd-;ajY&B<%B^Fc1bq}8tzUx&rZyOFRv4hEB@n2
zvljCdYbUCOe3tim-fovt4;Y6;TX(rCGbT>#F)}?KI3#|WOBwvMD%=te4W|k^aN^d%
z8EIvhk=sQN3Bv}C%69}t-?Hykv-KbG;K4PqRb@+KLW-$RVMx)zZ@0y40R?CewXNua
zl&Sda`5uI1L$rQkV`0`NE;(lDgq&}Rr0e8%A;pp@VNR~pQ+%(y4KXzPNnBN&f_&mv
zl{#_vq^dD2dOVi|;Ymge(j~r*dzGKdwY-crI#r27>GF9<dDlbES1uma*hOrA4!ZH#
zgWqMS5w_p_qRA1bm(#vnP$GxJdxbD)A*Vfz^U~j+|Ea;sV9OPO0s{buLiyk0rzG(I
zC9(c{bJf4`<7{bX``<?o<*&^DV1WMtv6laVSj6H9$DdxH^YRICRsBh3uKpgH7E1$C
zROQ90mO<O4{^|>=&SDG!lVJw%ZuP#(y9)mSv0R<p9;HD7)7PVIoq;P%$i9tiZEaJH
z&3<3;*)sXN_+J;#myLZ}HVs({FFW^_&qh{$_Vw9)-JQC1GEY3W*KLipS6N50_H$RW
zFQ*J*&AtW)w=lT5d2+TPef#2lnzC_i{(e0P`hFWaoozFuO`mPeM`!*xJEAk&hFD&3
zu@9i{)yllqVgCL4ws<S;w$x^ad+MC-x0XAx=K47{%W!S6slLvT$FC{G9hJwYyIBmC
zCDyhC`#P`8?QP_!;!OYMz{UOEyQ;w-`SIh|+0y)JX09tP4;|(p0hV#gI@7PgzW!|N
z{~q9Y8_l%3)U!;0S?q*THGBxlx-NzP`+9CHIe&DCDd;<=FT@oC8#kW?-z^B$V*B>A
zZykEh1M^~F;I=A{kG&{Y=Tow_(>8A%CS^}?SQ-mnGKn@jz?GM8Evj}mk+t>WeB-uw
z2vNy}z4py&dqL}aFcm>>s_kL?x(bK}80i{aTo|$#)U9Lv%wgDmAs`;fzg`0@74vOT
z>JTta-v@=hcpzXl&G*yQ`xA=&`!5N%@#t6iL5FvXCMi|~NCYRaHvQxI@dUUMaK!_=
z;?m}t)^I7m0#mpd)pEWCaJhpMuc`a`=kc->zV8Q{tA2WXzBT>6Q`R^X?Co<yb3;}r
zOnH~h9{&g_4XuQ8gZYc|u0a$IROp%ai@g{%>kM*iK6(a2r*E)?pDVB5FhguIN`}W`
z6M0MUJ#PH%X_FBPJhe6SvaEL0Tij5t6b-KMGnW7LG~_MN!`W$jkjB|NoMclXo)$Sj
zTh0vYtO*Hf0Ws_2yC0J)t>@ZbadswK4mrm?Ry&AwpdhA?=kB(|&eQ1#c<3^~98}tU
z&nZxpC6^BjZYcWI#>y<sWjg26((5WV1><(rF<3y5f8Czt6L%^^JOr725%i_YD8l>K
z{K%e!O7;<~$HEUg+Y$>U%iVd}nI~HY97YmFtR6_ow9OUwVG-Qr(xBpTTzRw!+`uz%
zX!|iokmz~)Z`><I=8L_RtNPn0z%PJY{hj<#I^LU`%F#DRmY?AMDry9807RDGb?Xbi
z{0q$Jvqj<6dkPr<=F5H_+(PV)-C$`f?ww_??UjxQA^(`z0MB|~UGKazx6=;iTAqux
zSub2Vd}=|;vmZ<6n(KwzH$`q1Y*%m&7o59W)(rZfiP*+`CVMnChejUG!{*p(t*}wf
zHA|49IP;T)TU-DGf7Bnk#IFq*_k8ZIj`4@j0Bh&UY5$`$h5#=O52|94Z^#-V`;B(M
zbWj*3S@TxIl^n-}0jY2ZiZVP$AiH3#FX?9WA3w|a0Xnh*EML!{<X7iXa1yGA+kffv
zVz?~!pJ$GJ-^J_C!2Wx+g}gQ^qW+$g-fb`BAJ@mo@7+Z1O=5`)!^h@xzl}^<C~9Q}
zoxB;iSv$Y%hlNgXL%<L6vHr{FFd%$V#=9xM%o`McSLITVsv}TB>^dQJq={V*vtqzt
z{2b^>SrjT7_FRDq^<NZFWrvqf;2eMk^H%?0fZstXT)B!e5F?PK@>unFA+3Knl+NI3
zU{6mU3^5)zrCcEK4aQsPH|kH9AYd3h@6~3LJJ1uiS~ee_WnnF=dfy%K%ppG8L9adb
z{`3O;bOOvk;N~;I5N%I$8`gn^i-D^>EzHKE@%8e_-x#YG2RS&v9QnUTg%h9*5LmuR
z&WCXB(`<rpww_!dn`|qHHr9!7F%jn>IcmP5<|@k@7thR};)E!3Mp%o-^!x;yb!!uq
z&`R&GKVDlIkB4|^kBD?>o@G4?O!kvsK_++bd%S@s^hsHPC)gPL5cDKW6Z>?iLq%Bg
zl=(ffRngYNlS*uf(Of#wsu$8UxdA}{JOr3>hai6z!Db*!K!0wDhLvUENEDe7@54R7
z+yv%H3VKL=0AOR-rs*Nd>g)^mL639kXLPHM!Tp8}6(Wv7+iv#%0DQwxYdm36JfB`=
zLkuwgKrFoU@h5m+Jj;2=W06>_jz2bM1PyzCPUk2tLTTkq>aE;++R$b=%EB+DZS9n&
zZr>~30$ncV59HP-6SczD(&B^m)K;ce(67!uxL~X&iR(2YRtnE_7yh!r<_*FOo^&3L
z^TfP2p6iboR?0`*VB>wP``3%gth%^k&;a;regHOY&)B9-YD}0<x_#D%;(HcZ1vB;G
z-FTzZf6<$f$ZbsM2KD-1i@%PraErKh?~28SVU_ad_Y2K}@;rBM#q{Ho;k=Z>6G&P*
zDXa5B%`FZZ#x8!POmu#c;m4N--><3R+y#teyS`zoP}3-~X(4HCH0*(kO|wJd_y6K2
zcz?`-t?k#J`X0W+nWVbq@;!*}EFN@ygbm_D9YZBa&e!a{J~~s-7ZK_w^-3nb2xZOH
z4Zs%3RZHS9+fLaUJ2bRw8~f;fyzD2q)}@x?#Hn%aV^?^S-aTIRIl0}%ej}RL`8)?e
zW=&l8xbRw4_wimS>?sTNB3nU9Arua6=pQVjFpc4%;9fpi2#(|?TV1F-;yv&hD(*zv
z?nkaKAJ%3PP(9x#eACPZ3#0pKZK*9y=)mw=3m^g?fX*suB)W|dUbfgQJ0YNH?u`1@
zdg34OCZgj(NYRt(56bCO3Th?}=fM+jNf_wIJR7a^l*QSr&nt>}w!NZYI>V&Th`1qo
z-NJC?&gT$q5;Ardj*;XP3?tLt>}=xM(kkd)_akTjem}eYzCGjrHvgU56w)Q%;M2m+
z?jDqml+s~uf{WBa8l#g-g8nN(_wy&?z;-2Pm|=2@*7_<3*MGZ8UcCgQuok64uq~+4
zl@Zng@{UF8z#IdAng2-4U3d$VH7m!*iDAd%d>ij68mfG%$;r4YhCdE)f=%wPv*Yfp
zI9E`+ow?fs^%nw2NlTQY=Rx33wE0rP*#6QTu<Csz37fKg)InlD^^@ZpL-SL{texX^
z^-{`t*eW7E#E~M#oUTIUA+#})Fz=U01=&xLSBjqb^Nj9ySG}(%2sLtdY1waH#M_@o
zY&&=mVPi1HJ_DD(oA0K2_ecLE;3g^rsf2o#bwr;Qva?9$E3PbF83cf>6Hm*TSVk0s
zj}eR(pnIQkBL*l=SGFPi@f?WT=DikXT?5K`?1vufE`^9SZRRnX#<Q@zZk4=(3Of7y
zbISzEMl<6wiog!u<@~o$jDwE#cSsiI3I}W%oCrNlUf$+H|E#kbKxN~%hs(cu6snI<
zAdz6Ah<ED;Vd)%k4(5ZR;aPd5mQOjMQyw5x1i`awp+h5auQ-IMl(~pL+eJA=vGd7d
zyQJtN{xAu+9Vq=jdL>JXN8sE-Yg+A3Pi+w+y?a=fG#H(uho$i5zmnH32D6GM6=+1L
zDuUp^e560&&-s2}X<|>@$T&)ZBY#dunOvX%k!E-)V%u5hv&O!V3@FaI+~p|T$_g3_
z4@c?Nj{yF@c3hU{)+ZbeG()@t&KRIKHF6D#S+;Ok)A0duO1a9TsKRgz94@@v(r(lX
z_~B(kRew2e-_`_DAflggusHJ$aQ06EW}fsOTr$J1L@}q9wLuy-Vm8O{mQ4{jb-ZfN
zk+j^n17Xu6;@Dk_^hn`e(+3Y-akMi=7p5OEfk(Rwfyo6xp5)&R%G>PDVQ2HKZ;TpG
zlmcXHQn`=%k^nJkU06vf*N--fAgJQU?i+|XPX0w_z}r0M(wVQ94awN;5N5?Cl>oLH
z@csPu+uNNCJ#GOpnvW0A2+IQBT6;GD2lJH}qw?evcZ7_p>-mD3zVT9vCI}kC)XlDo
zo@r9&z=*O*&}7E=Z2<|#RW<R}=V?#*K5VR9RR0#&h-d+ImC7Q>R)^y(CB5?*j>UPc
zgvH`*G#?0BcWZ%wDOau)frMXA4F5a>I(Nt+-g#qQ?;{{#?(pv_8@1mJtAm&iG;G|q
zsQqW@RV>=G0pvvuM(haKejr(Y{*6YJn7m-EjD2`<DGPDii6H+q-3&ymIuU(_aR;#j
z=rw-&o}s#%HULrUyCY#K#es$_rWwK*hecBDI+K99Je$AKeo%J};Berh8(8&w!&nh}
z8AhC^hJ@Vjw70`%gC1Dbv+2qHsF_vc%F_TZ?<HqO3ybA|$o#{P!vV^yA{59L+MO1j
zL>7RtKRoHD=RAftwRFi2@{@MZg091A_qZ2*A^id5P=o^97u-ujZbK;LGt4Z~Glx9+
zbI<i`z^N->yNFwO$Mi9Sp<Ilh7KXZDOVy+)Mj{sd4Dz}1yf||<S0H0+D790E#h9pH
zW<<1CX;Z5x7-d|yM?Q$44i+`NlM;c<T^fgGKIFQ74bccvF?i|ZY@ZX9NYp0tBXjDc
za-3O(!_foYUbaTl8F$}A%7hy@FW4!nMw8tkUYB&$=CZxFb1NP^`x)Q0K>#&J!9)-e
zXCbaqbthD*C=E)2&Gf337l*fphHDB|MDkvtkZPgxm#M}DJZ8qzri*{f$ug;wG@Q)+
z2=|iOcH36E9H|vn8L_cQo0iTlEO*a)oFx++1(7yqE?&_Qn2&Wj2tt04U?OCskUq5A
zS-3~}U|uDxE>D(DM@)gsXK7tIVF6um#O+H5?#Pj%MnJ9{lyJWkw6T*An6pX(w{(5M
zdbOX@P!Y!*fp&heo`Oyxu<)-O2I?MApj>-GJ;|3w7<kg>i#us5d^q*2XmBfYsd&M@
zJCI*-)1keXm=h9K&emZQk24*lkIebxj}-K!E0FS*CkTP<4^f>#gaNgj`&e3{hw%ow
zVBf<^SE9h-i?^K?DUnZDf3)B2!x_%osq16O?rqqMRQ=dqHQu?3qXFAx_678yZ)c#O
zflDQN22ofa*wvl9LTG<8l=0K)D;Nb)-?SBVto)nVeVJJ$E$Ae@)W1p|yMY+Bt+?nO
ze{}%wC<5ZHj(;Cu7~)wZYG<h!SN}Ys`40_M_D|@klDH%pr$7GFx-Kl(#|}JH5rqTj
zTXe>;Xo%Tvj$_&nqcn?Ff?XuWkiv;Zq<S7K?I);lj-<i1JtPK0@fK@APeH`bDFt*O
zjSx?dgz6p85Po9tk=I==rw@Jx!HB8jDilO+b#DiK!BgQR4bQC1R2Fr3z9nY_Iq(lp
zgv7D)+#xdIQ9bVmkw{tAY`LH^gRx^WNb27Qk+b?XJ-4Azs5sej^n~;g`>|83S~doU
zu#3=gwvV8a(kx#AMY{{A?*SU(G86PY6da+2A3mJxg#GbZG!mk2^<NYH+=bR$K2T)8
zKmIyH=Fq9ZbpC=!a7Xh6bqf*ur%4qZKO&_@FX-`K@R{A9#O<-Se!PdYCx2DDkSA+}
zT|7`nqvG~0BT$tn@G3-M&sk)FP~`gdjPGLn?|1&aI4bR`WHU98X2j3_Eh|q8-qtD}
zNeE7M2vy5TQqeAle|OQZSdg%J@bQND)ys5RtjM<Ve>RhAMlTcQ;5C%{8n?4h|6{WJ
z?#TI)QovDC5_;eQK0JvlZ=yjO`S<RYempXdftg9hr}!pO>nQ`<82=OS%Kh(F!Dy4Z
zM7bT-5A202_6Mm%q`rdW84_uQ;1d<Ew7tur8^w$)+e<X$BTGej>N?K=Vf;CX6|Wz-
z#;-wa(77UWBYhVmm!Bz#I;f_Wj)1Q3zTZwY=#J}aUd*N<n$+<6;$h?&dWO<j$e$u-
z;J+xrQQ?H6In?QtXp;xpH02Hxr_xNRUfth>;pDgjk5|T!=w`0Y@;6aj7TwVK%@kFH
zln{`#^=$GN^T$}Cf)}9sCeW@X*^^2fk&Px4r3P1^JcuA86ny-jIf}ez)Ix$^nX%gD
z3DWO<aTO60l)l8y+A0tZl}8nwS{PcpPmxIitrP{pE80T`hD*I&=|0hKCY#v8bQkJU
zNCTqE%=4-EW6}aRf-PDq?OoDNw9p}b!oF#X?4jZe#JkOCRr9;EXDaDTcQ4u+P^7#%
zckah_SaRm;4ZMq(EpGHBR(GJtCZ^%FnVHtX<>Gi<&YlFgA7<da0=F2X-}#J#!9}J{
zxMPA7t3j$uU~<DB3K-hz>Ym8zNakW1&)IXrSFHlE*86wyI%gvj-YLfs?Q<S1(g5CL
z37yX4odb(ktho0}wiM@R;HOU!VGb5GB%;`niE#H(onH0ZWb=SwVUVtWNT<<?W)`CQ
zkG&kPgBvhmL2;8SoB_u-3iFXz%0-jQ<-4bk`t(WsvQW?N4xg#;y287CjZReiP9!$+
z#!5`|CF?{e%B90HZ!r6`I#Dmd=$A`Kj*{RjAW1lkdcnTtH$5Ss(|Akb0ya`-l2&@y
zX@`Fm#(@VJAQQd~bi^mFW4wQzEGXl|e+DS(85`2k9rG~!tTrzZ9?({+PWarC;H;WT
z99Sx64~Io`yGa$-b<;=x>79heDSwyB;xX~zY7ELRz$%2O>+2Q#?gvEu5YGa=c^Yy8
z+}+#CZ)r5K+DQzp=c+}Rdo0s&RkF_e@+K#l>JuNU8O0I;CnS1jVy^P#U(W;sq}~>)
zp#0iGR-gxJ@+@Je$^vam$30Zp1>2uhUsq`?WW79oP|!e3pkj%Zn~8C4qW0NQGX9WT
z=Fs<YNrff0NT=ySO2;D~A@~ub@N0`|(W3cAP{+-QAG;=U$C%{@M^m4S6(80bZHo>^
zBSozdTO4PU9!abu+~HH$s68T^>9d}J+XGV*QmSk^1xQL{^%B0sC*)ZWlY`vxUC8(`
zV8G#$8&?6+`5zbcwA(*Xmryu@DKIj4yeMWNYQ(=p>9K8Q<8(S5r99d>8^~zr&_ju*
zFo<Cjy76d2ueb~E=eD>TR!rvpTSh6b#n|H~OwSeF34BP#F22jO^udx|!8zLZ(aqQ9
zh~(;c1(Wo*w>rVLqZMgw6*w-~t*Yuv<`D3Wtw{F==^SEw<2Je$ljA{FX($jVrDZL8
zFWNl>u%IX{DOs^#j(H&P=<R1zBuGnF_=2zGZ(qT7E|x|b?5~-fA32lTK-Q)e#;N>(
zeaI?@Ws}OmcP$gDpg=?=!`|fr|8W^Y(HJyE@&zaTE8Pu}qBxp$eFS9YymwSyo!UJ?
z`NNi9d8SL?JHSXZVz$aG>`F5QnE^T?4M)??dTx!hUxW|pY_|YAEF0<D+6Z`%u9KUF
z_t)5RN>huFD!19FyBOochm}^r{8GEAAJS}?ZU#bLE#&~%oHc7p&RaqU*ZFUGwGl&y
z_7F<93bvGEL`d(l=O!Hr%^mw<;MDkRGKlpWKP>n9=8N+MYLJ?L^SfaZ@7!$bnHHJc
zGACgPk!#^3G!*3(Ck2FeXmRkH$EswGATxLNUlr4>HmqkBdHJY!>P*peNFS~Qf+;Ln
z7PjRMqV|iN^8hm~i|^W?%T@c2=zjEUqu~weAj1i}_13h{aV~`WCi!HAun#_{HA@bp
zx$GQ%x1GmxI2@#ze{z!T8h*Rj66V`-0m&TYaZn|%4(@(Dtv4$YCH}O<pjXAJv$zBC
z*M8sQ6|Z!F&y=2(XAS*GgmD$C%JlRl^l0w8z`|8O{|^w5&a{&REtu979Y_E*G!3xm
z=uK_cajVV9L<V|1)!{jb>^wXoR4y_`D?Kn-nyg)hYthYzP$Q_YJE;o|eDVpSke>wg
zZ4*+!)TT=NqCeg9%&}!|Gex|GV%}))Boh(p11Y2nJC7LWvagNl<Y5wTAQrsBg9A=^
zrVV5}HXFskL+<xsU)@v@E+Pd4x##;yMa%6;&5i{+0pBcSl)4f9UyQ?$=?N%wC`vJ)
zwD<E*rJ5-LOyNjc@ZY>fFQpzhkp(bzkvxuZI^iIA98ZMt2Dz}Tbg}y3G$9TUtiBG2
ze#VS1S+MvOhBwncYlpdUnIgx!4umx%*x`ZFlhoR-?!(UXjBil15x|92uxO>u6x5Uk
zSK$XLV-peq)RZfdmdX1eeg{$r&Q@55lM4!U?Yz$*3`8zxH0R`Opi)6ue=<F;?G*k9
zJ|!)K4;5oy_7D<;=2d&&Nt$lV(V_&J0R2Ya$pRVn6(B|vAKnd>iDy<{NVcA|kU1OY
zPA}~@jD>g)<hZ>UZT=+vVYj2G^ihBSaSW~7#&fb1dWTZGJq6FXhoi(ba6JP)-9sji
zMBPVrQPX0a{D{;uQ<Za`&|j~&!qHQI^Ya;q;NS~E2LLfCm{Z@3yUgVaW={2;VRVED
zh7f7rYXBE^4qS>_CVARFj2~jc5F#;B_bQ~&h9j&FCG^5e&$FqKxR|%#HT3T>J;AaY
z#J8`i+mr7BhekAs(IQQh0?zZ!kH~~0w6U62_#hk+<6POeRe|Ed)QtZE8BIa%vC$J{
zvZ!yk7&`nccua!sjms&_P(C2Wtr!_DJ0)bv!topLa<EK}63$-ap)st1aADbW+aJ^c
z>%2aslOm!r2%w};VKQ@ua8^Ojd)by*JBmm@Vs}L>AQDv^pm!Eco3#MUwUb+1gJ6=w
z?Fp|;Fg_KxGq@IXH`WBWFOZ%e<j!@ufGIYq1RW|Oh*WG&Pj)aqY5*Sv+}Snl4oYbj
zb!@8$#F}OnMLP;1>Y!M2drPQ5EYhc%cPxZ17Hbg7xLYV-fRr<j?ac5na*S7kSnX5<
zi2%^hiBBg-q0Hq76ILw|?x+@%Nf$^a>BCO?rQ$^LYeUh%q69*XmEquEXv<{AwHOk`
zEO_hN^3Hp%JY2^tN7~N0AlfGd-Tv4^+LG>Y&howlUj>-d_t30=Ndkhj?*Sm|q=$DE
zZYtxAC!$HBu$me*Ib4{HQ^VIx!F~Urf{M~h&__5-EMvmY_sJns^D0v|pyPUyD_Rnq
zFikfi>QwS7AjzbykbM>0VEK_fg-$jhRRml^5I4$M!pPE~z63Ls9;7fYrEqJJN9DO+
zsEy<1>QXi4`HN8a3>H3uP0|svA&Ey8gE{}Ht5`=su9;Gwzz3KfG!=vM-8>mcKT(qY
zSHjg})S;IEEEuLIs);H}tvymjqAG>i1I!B6z4L<VMbww;nEXdg>DdC8ugP8F=`0g@
zYr*NOY(qIsis<e5=o>018(aM2(L|A*wrpZSic_SAgIPtLweskw?@YR8?K1ddVZ4c4
zKgbn_^hk$9@;%Cu5|SDHQ0Z>m#^$<YG7uhptv(SziL6m6tSJcrKV}UJtPuV^xB|ho
zpWkV0ou(uBFkuZ;!6W@}K`pd0#j`A_=mN&jS8eg49A!c2RC|}%ujaw<VZy>7J+rVH
z)b6snOgU!wRd^E5hRgu8b+Ht_Ced0@s!8Lp3FGSh0PlLGi(k7Y3x9ZeHcKxrD`S(S
z*`Fd0n{*3@%k3)Q;=l_{c$m95%ZMgMy-g<hP>MbpRJr<7$TYopj#Bcz^>A1AOq`~G
zX>#rsspj7e_kZ|$ryx;-XiKwB*|u%lwr$(CZQHi(s#CUY+cx^#?&+C(r{_*S{7)J2
zN94nb+$;C~R&e1xZkgLYQT!Mw*KGO4BPdhuo}Wkmzh~*oLQ=gqNIZISy!z%M*iLgc
z`<s%AcK`WbK|`YFwwWe;P30oEpkEaAx(jmNx;tbvt#*#(LgCD^v23gEUXwYU`wa6v
zr<SC3ais;@zN-%<OOFO57NpxvnJ@HZl<~t13Lo`Y-b2Ngfwt9hgYlfW1@n%C7-Dfl
z)5W0^0x=ge?<%dBP|Idq&Rdk4+X~z=%^UXwc-#JZqv^b+y~FTHb!(X^k}X}66iNo^
zuaFKC3m}+RRuRlk;<A?J;d!A#+zy-ao#Op#+LvmG;=Cl+_mw-^%T`Ajz7}mq+}LQ&
z7>XN-hXe9;1KBeRBU-cl28pIERr))jiC$pXzlk8H^GQ|Vi5m7PQH84|Pr1>CRwtCu
zoX!Ik8=1M=hfsoN@Gi&{OVmY(%MUdS>qvBT)IdiTv?s0FGSPpQg&BSW*xdr#tvC>j
zYZt80d61lT%_U0HYEL}Eo9y3|UG5+j8&M-&yGszs4vZRvgm`!%%MCj#Q80+p!EDAy
z%PCi;Jex=cRh6i;DoJ(WJ?MzLt2u3KHON6Q+QI!x6Xn*kqFP+KlX?APbB3b7M5LW4
zjdzJt|4k%zfh!q$)nBpe)}e2OA59b|Q&LWAG$#K^6TeBhv#f|ae}q1aW-%Zo!}^j?
z8}CqN-3!ay{2af^Of4TZ(Q1ZFFq=#{QD|{4=U`xQ10T@cUv0@6<xVO2cmc{m+Q}rM
zMht(2RXP!u_-yhy<)p^Rt}5+2Gy+pp$@i`B_C#tbQmOs}yj-_pYH^e(&Z8$(%Bm2n
zBAgGY%a*~~&mUQ^9HdU)un|tlj%j@a^@?Rwm5%t?#ZlGXTCTa7>d5mah@6UC&5T&u
zb+1sSyH=h4HMF4&ak1n~`3zYCCIIOE)g5Tj5r|s$I|3xn8zgJSgw5+#MxX3^DBoB0
ztFM(%pgYiBDnyFeja)Snw(QI_a}+lfa5yMi>;)zEgjH?lq%drH>BR^j$QXO5eN8@#
z&`-lQiK6A}!dW6d6#Xv4HjXRH9ktSWP5o9MdIHXDSIs@cYMF@WvDBzbo%&uOA(wv<
zN7NSa85HWTq7t?B_kat5pWCUymUUJI4vCr9dg9|@Do=cno^I$;QU>K1H%F(CrnB)q
z@w4DXr?d$S)5he7$dZzvsyUqt=OweG!LiFcm%Gy|SA`_TMX$?|Dc^uothAM3{l;jU
z9h&Q+vJN7iA!9+jIR%ZxIYID*7&M~gHC1?gRbW+<Mhj2%zU)rjXoZ4uYPi%-sYn9(
zr+=1#swAML<dH$WHyn2cfMaQcaiZ@&>an5W2yc8&=H_XQOB1!}01<X7<y7{*FLZJ$
zsF)`p)@+Yc4G@p|dzs()=SoU%sm)o>4WM9gby<$r)#>Tvk<_0mXq}xRrW<X&3^tg~
z?s9}*lxLZ!?{d4Li4!#KiGnsZRMy+6UZ-i^St$h2$3{ESrU8wLAkRIQ4O$)Z64Fjt
zBydfDbhvy%v$kZ(@IfT88u#Ol*S1<kcISZZD2ggyqMT<4k>-@($BRM>3SHAhe1U7?
z(aaz-*<Xm=NR0*v9!M(l0PGIs$kl>X+n4*!`j_RT?IHG0t2&LyXR%!7wpec(vC3GY
z9=Up)c0a_9$3VLo@^M4L@sBO@Oj#gPC$eu=U(D#+<amES5y^m(OM*(R3%bJQ8No}1
z!&BMI0~u_muCEhksLbIjMoNp)Xu(Z=kBg#NW)X2XQ%F6qzuhhOO(lra`tj{VpCl>-
z=>$()X+M5J_TGx)9-@TDn8V-9(Eyfl7l({c^qDiLT%b?Q1mQ_;H|A{5-0OJ-NFmDk
zfP;zGQGVhbMlr#PA<SVi)_(@R_RfRmWE;s}s3{XKvT`UTM=9d+Nr0{LYEB!>amvP&
z!i%xmtVMPzFnvby5&5~<Fz)We4~YewvAj$qbQvRn@*u8|E}DW>V2CE>mDgWN{A6E!
zKXE5p_vc~%we7jWnK)&J#LXH!+E`f;mT_9sMB^nv9x|UXn}SQ^oy@9Q-qm-}Nv*-P
z<NBRhvGTxSL}vLyDw9vHtp@SjU6>|vodUjPY7VTsxTgpTeG(!oS}+z9s6uXKayPOl
zd3ViP36zXuOVtkocxXCMmrN~elGVr^#t1&=OkFDpae;y_>qKB_+z6%|Xl5*k8+zmp
z3=II7x&T@loT*r-22WeAMojZwJVaHLQHA!Dh<rO^vg+yK2|x|zhdd?zb#Jz9-*pl9
zPoyRVUYEbeObqrqpn!8t%Q@0*{NetI{f@2DAItl;W5HzH0vjQH=fgm|i(l3_X*_l_
z?8$1iD18cC&a(J76JJ+Z?<+6La$MfRcG0P(#!L5YC`wlCtNABW`y5zvm(*Yw*3O8m
zX*sJCW=td04D7Z<+1FQJ;oxsT|3OjsTmQejwV|_0NKXjzOk=**uwGcua@-L`L~5HN
zVf9d!-Kn0xN>3!~Z%)$H;vND_XQ)VVCo@2#R{95_d9%c}wZ|sNIzwM|=)MZ#E2oeX
zGAiVx(OD|6W7CS$AaMI<D7&s8se9YaUUp)3tgnmj4X}j2Z5D3zL|*B`%yT68{NX=C
zO5ry?4M1#jIJcQ}qsdhaENb0d4VZXvC;Z{nCdfU)J^_XKId+omSDal94;~PaF}!5~
z)a5puzmouSA@n;0qwg1HO{W0+#Q~JivE2l;Xc3zU3Zi9=Gq-vg`;ZCodS0oOFs=5C
zTc;&E>n8W%s7IBi^v%>6phaG>#X1zqE%+%GQ1%I(1G=zb)bb4S%aftBWtZ*qY4mBC
z`g++yZvhft#I>^}7SZBklY$YZ!2z$tIUPWc6>My&_2dq>>CU>qX^CZol9hm+v5@OB
zaYb;)LkHe<KM_<q{lex2;vO-V@&4<e56<@iIBOQiT=w%;EcIln-fALLPe@l#gQVVJ
zHyT@3kcpMHr40UAC2eo9EL+t(pZp}+p%l_%#Z;v$rxVQ*vaFrb;wpY?{(C%KZi~!`
z%k<YBg=W^$I@C-{j8H!)+chjz{M{$SNhp6|H4N-g^|F!(?4D4J1-aIzXHS2Y1`P^o
zMr(XnwJKF~`UXMD`)i!$5d3)d_&#rZs;l*6+}av0KjI0H$2w5sf0V1BrBx8+vopAW
zXUho+4W6bG=6Qn<weW}1n1ah+v>=tiPe=R(L#+EenR5&Ri)$QFJR(U?8>mRgq~H2j
zyyfc}!|M2tz^H3F{RwNBuZ&Y+2$(w>pF+b1$k!mYNzP;bVECOH583FIxX}nN2U;?G
zBxbI7o;rfDx?KJ4^mnKo_CzK5jd#$Rd2x3Dn&s*1_sCn3GqFCRi6Gu1G~oKrR6$O*
zfI8nkI#|ubox#gMEi+yJqDN8~hLV-!MF$q+ZT08p?+`NOOz|K4or|duyb7d<?mR$Q
z&ythDFCs&DydLOMjli=(r1lM@fkIj3P2om;JU(^d>e|1Z4(Et{fpdu{AvMq}3-OSt
zJhv{9`}+B~x!xT)>LBJjqX6jW8BsWW4}TZ<71P1Ji}=_HBqD%u^@cR8IZthsOnNr-
z<$bTTb-|kP2d=Auh{6Sw(O3m4s4ff7UfUoCz9E#zwMN}+XbYX+I9PUsk#yUyQn}5o
z%c+CL8&3{*K!FgGqdI0|hZ^IxTi4u)nEPW|{^^G;1owQ&Ma<|dgn9S2BJhqEa~AN_
zAS>;9@URzS(xPCEu9}uqVOaI9n<OjNF$6X6_s}J)=4T36pM=(_qAE33JqA3n^2|xm
zzJ6eY6<P`C9cx$OVX>8aEy;w%wXnH&H;GXu7N9ggc$>9KS7T8*&Q*koyZtAv-|Cep
zyfpoIUYQwp`CZR*Rwjm2Fp@gyRxe3UZFL@4r>Hqw6MDTKpH;B>BoMSp`U_`K!q?D$
zgS#6X2aYDZodVnl<jt3z12j5H#32lGvflEZhkn1UWj}xK2e-3QZfmk1^q!I}E0F?j
zhj|Z+vFCE+Owonl=)YGlVogH3_5|g#3@zwx8ueSUAoTDD+>FeKE41sG&d6jetCpIy
zEVDl7v^f#6aMESU4aLk^Q;`&p()cVI+D7PgC1QlXOf_s6mV?H_FfOUW-w~_4YP662
zmWyAN&y->61TdGT*?&}IrWlrTXCO`E4KG{Q!z8T2mgvw^GQ)_`xv@N|uUkUYZnLwh
zmLF*03Qz&ava|25G2)Z%mgb-oQr6#ri3xoVH|brL`bIlwoq?p8SyZP3SpyVWJi-Kh
zI1%A@FWmx&3($p`Yj;;FeUceBRvDk9QEG>mRMwM-Wu$78;hls}(gH2ObHY(B&)C5F
z<IaAr@7@<YW~59wWNO5eDO2ki(Ig2?U4RoKN#QJbkOtD(y>CMM-)DkDYLiQ?Yj-3p
zT@-7`dk~r(IhQsJ|KyIfn5(~R-`;#X$L0i249Im(N!5@}ejOx|5g>}w#gAbkC6<>&
zG0)-fI1Uxrz%FRTA)9^ibCPU{HTZet9wj#K{$*$o`5ZG|smsP-4`uC5zFZz;8Tbjl
z0mrMqd;OB1A8d3u-}#c5p$sMvH=I_@iIs(nXf>J@QJi)jApU~E{+tG>hlp)KnFBpl
zgfb_?1iT1uDz^lG;C~F&+c`h~(*h9fKo5E)Ut?RG_ol9HU0eQg&84exWCh!Blwp+n
zf;;a)KOq1a+AF}o`61d@Sii)<={^e_3+G43Jba<YGHBxoCcI%qt#JY}kxjID6{z&g
zx%XWIE>s;|zlTscEoS^a;?=WegP@%sO*$Ea1%m&eEQB7}k^J3vYD)6*$vW+tN}azZ
zP;`>;lYbV?M=PtwXyJUn1d}E6d49OecbpM%s@B(WxZuT}!1r#^Fp6gv#N+qjzBtd<
zWUpZL!0b(TA#NVcVMKh3fMdCEIC*ogZM2Q($MRSRzOUZ&jO!)ODbVM7OEGm2Ti+lx
zKFTL$_b9ac+>1ss=v^utu3}^EyCtx5aC@7R8~$<&@z_^!bPT0r6AY`t5zba#V{~Tp
zq-GegY*%+K1*0wNU(hc*;qzW_p*G!{m(y_cSy#;Fv4{Bb$D<22K}zL9Yj!_kd*)cQ
z#DA%G&S<43N*3JeMyV3B7t=H!e}hzKbMKq5rqaFYZU7LB#=dhfG3%Qv{z5iAF85LB
z!vDe8(Cw(foPv$ZQ#ss8FckEq&v&(Ob}!lJ?v%9reMZ8$!V^PCQLG?7@qLY?D_Hf(
z(wjOvQfCb_-bDY{FTX7AIDXu-!Hm&m2CeubZ)|gz=V&Nol;>a9Gsl>&EK8YQy;<{#
zkmlCj<rB`Fm-WX8uE;hW7Mf?An5v;Rk2FTLrZyG`=wOh6j<Mi*y(mvH_pQR;;xEg7
zmWIO>7yQhZ%2*}L+vY=*E`Us15Ol}mw>qG&@lynm0u)P-E8D2*j{ArjzoP(X29-Me
zf~<!mZtxcF*+gOI>v4Y-3d~$V?9eIN7ynOYH{gE7!egLP6lR%Oi8Ots4qHr;=>bJJ
zv?)J;pl<gYw6xbw{?9t@iLAXmY#9ozJWNQ_H_y{~Lb~7!E{J~H-Ph9T4!R|T&k|iR
z>QYk`MW@y2L0^xy%dkfmzi5-J(sV%JOm)~94YrrGfqkRE5m|*5^;L&G$<3&s86gCD
z9~gdMo1#wJ)B0yP-t5DZCN@65R}XQ0fC@{)2SK^)eJCFUTLTCLt#M9m&1>w4p31`c
zZ;&+-8uGK*B6CegZjE-N8^bna-@r5mqY}HB8L+LS<Q#?%Mn~X}hw_rQiDd;pG~tCU
zCU%DzI9cw^)tk&6>O#f%gpeI|oGxR06}f<rVmHw@?7%a4=bdE5+!W~vgy6V@M{K#)
zl2|`4gE|)iU@y`A!JYQt3FMc6(OoH~lw%mFWx>US>x@+T24H?^HB&qd2X@>0^Q%XF
zLR~|-l-?-FBX$wxEPDGV5c^zr@_+_cLDsw?LL^FUVcBQ#f2e+{C9BaoDH7odc}8xB
z;DsW`4rOTWN%aM)>_wtD<fWz-n*!0B5+E_ah#BaT4r4v6HG-phD|CgNg?|%=*HCrS
z50Xv()hcosdI6l8nZcHm(aCW+Y%}7Ny5-BTA-ycz1Dl_<EqBVlzM!8++{^w%cI5qx
zHd>rV5zhLWFQ-I8)?7}f%!NqJshyTt`-~vn#iqA+&!PA{ZnA>iFIdm%ct&`tOAUQj
z7vCY!Dw>v&kDVA)(&WqZ5u%A+P!E-tMr?W@x#$W_{6sjbK_pQW3}`!iOBQF;orPi6
zp4ct2AX#kY>+(Ly!I2tX?s*=%0%7cUEPCT2D5zrCA>(RuB+<kzBgoJe2y#5?Q&yml
z@*gZtlJxcQ9rXsYq=ei$uTS-9Mo~3;=ep-Fdx*;AnTijL3Ek~xiiPuX^GPTZz?(CZ
zT1d+ME9+6$BbEkv#};pd%7CC6ZBBJFq&n_u(#*5J7EQO7pjI_qAurOB0)Mp(5FtP1
zp{_OO!mBQ&Xu(CG175G($t|IFcl2!SRsk6tHeHuUABCu$n8H_`PIu?;Am2w`G+<`E
zKC-L8N6xb5i-MB5vV!z`*57(p<ZV4BRu9Gqm}J?S#S>{SX+ywIM%gZNHU1uj5znL=
zP`3R!l1`%v)rq8XZmQryQZaiNB_lEz6yG9vF=O2F-JDGOGPK9-I{$!0z=Fn(;QhcP
ztJ@FDoY~i^O3A4Xg3`@S6EF)QA~}SzYKQ4X1T-~CZlp9G(*EkwlB-I;cAZxK>3<z0
zjD_Gtkn+Y+QLsJ!YRSzjJdlp_53BxLnsjDv&fe>aSmNW{i?6((jKu|4>>wy-=lR|7
zjUsOB)MVu|UUC+ed-+F=75<p&tc`tR4V?EH4UYs7I%#dBFuwYtt+m^GxWq#2#WtzQ
zq)&Za2zQ{`m6~p#_F<?kkGC_&4IqzrXz?kTzoB!tVKuvoCUZ2uv1wTT$q(wGF%V2E
zJt_S8@HvtN=4<7I@jO7hYV_ODmaY?{eevuBA9AUOPWZ|Z=~OdTYK%_G6a2_!xmd#K
zY$&4=j8d4jxF%KgfZUc^i>h;+QHn$j<x|avjMwXPP%V$I2Y5hxachrTecM0aynh{I
zsox-5+je7mrj$qo&xj-`(@2dXy=2qM)cuxSUf~?BFbZlD1%~Y`AQ6#uDz#PB+ogiQ
z9ufp&0TnA;fsC2r>yzp2=6?C4Ea_T50WPbq57Hyp&nNb(4XI$s-@D}}b&xKcs>DAb
ztcRm0a@!sNgmnSE2q3ddi<%zGPLA33`t^<;%~M;YnFhIAPD>NH#Ev9Yo>RJnXEM^Z
z`h7C*6)jblxS^|lK1Y33`mPgjdX{U;alPO@T+wB3VX=?EWD29I_w3O~H82hO9mfaA
zUijt19+RVJNh|G(HU!{xn5cp&StTmB&-jEC+}(9Q8jPqwg&6@g#HbeA`z78ih8(U^
z%`)xe&#ISs>VkYrT#0A{4%xXQP9Zm)p@aDP@pvW?DF^!$PahvKu4UaP6-Y}01nY#J
zErjEKzit!~asT~N8<m0kKlsuq@0%m)Re58Hxj$^YX<>ilfrEH|<PgNdUqu&YmE25h
zcn!9*sGVfC)pyM<Wa$OX7Srapuxe0FXmq!y?@FDiqP+)vBYFJn3Rxv!jMEK9O8}3x
z8J-vdhrKP_jGQYM+Cu)E401S5Y$`p7J-S#2&#_G9;u5}trEGZ@pX06jYuc`w$Z>kT
z9*2s1;}h!vkkW7dL9ddHAJA#5J>5JwPT9of?~-(G37d~qT$%PYqNfptG;C~J&5~Es
zi5P1ZYoKT;dBFs?yg5WhldfICwr<U=J@r?PI-D-wO!z|OZI<C-ya`(wqmtph4+?HQ
zn~Le(B<Vyf8n6s?53^Yf%NPL!Z0%E8TR&Qby7bCl@TQzPtPJljZi~op@a7Fx{pZSy
zv1=eY4EkL$39q_M2!U(#KD0pHA?5kGk*_&8ktPZ6YtAMI8dyu7ht4O}=~jEM%=N@(
zg{&r>RMY9LPItN_%~`}xIRDjWBC<GlYW-}`n?%a)g1`II5*N9799%?~vTZX<;5W|B
zgGwz61sfK3FA#t0RTQsVUbP2}JK)szWR}@(^R<@OwPH$8M|^QcX6{0R7zlQyK0eLW
z1GrVcNYo5HY^Ag6&DNW#!VGNZSx7O*Gd(V_Aqj~u*GV0d{1B?{JmvmeE}uBT_4zM4
zbr$JMA|hED6vsrbL2J4kp`1fxdVxG^T!M~jphQH@wEU3|e!IX?0Py~J^V-cTBl1Hl
zsWv<A5t%Li*XIDxr5t~!#g{&<wmf35VC&@WrQ%0AysNRxY*F&B?L_rOcG6o2c^s8C
zifZQ~3PufFVX+ES$8d`>S+?n60oo;1=jxbbD{9UzSP!8&{hglwY6@eTZ+L(SopAY-
z;O_2VUxj_SNGY5;cT~Kt4{K`5^xUlS6@s}#xJ(0y=!U?gz$o2$;qs`;^K;G%>-B6Z
zat?)B`y}V0u_+~$AZ7080C>uWJG>5nSO&5K3&E04$y#ZM9y*|;#Jz{hRHuI1=r^{E
z<)f03eA`t8nuL{SfC(+kT3f6pE$Jd6#Uy2!=kjQIV6&vuXRW+>YJ`}71x1_TQbTTK
zQsHQ;OSj=Ig>w%_vIIi&=||Q-<*Y4->MFi1{T>%Z&%KA=%wjx4=L1qrtqj~1W%LBF
z^nh-jaa2eE&1%t<w<XEYqxfR@-TiYQ7$uL(j0U5K<uDA{BBs9!G{_AwY=K;Fp<vu~
z^a&^4sF;jIyM~K&2r}kpKRLzgMZJ2?D@lOzraG&JtT7ZEG3dGh@+jHaD3Yg<7J3?*
z|94Jj@dmPZGIEFbKsSLgw*s2#V+~s4G4s>RtH+oe<awK@ka!kPS8O6Zy(M#HY6`@P
zdZLv!nU*jQt`vZ|nhE@i(1G-fm23D}XFa|IU@0t=PJ_;VcLkfPQJGT}RR%tBh61kN
z?UE@_3VM74gbX8_0jp?-c--LBBQEXFbO!g{_`XM<QlP)4-PE?NIf4!(rrcfqyx}Fh
zWcb0gEz*;h+_bqQglZP0f#JaT2i9a=0xh-so+-5l_|Xe7;F*xcZNLmQaW^U|SIzD=
zNb!N5&RJsM!CtTmnyqt?Y>4^-M#5$^cxAR`c^_!45XvA&+sx|4_#OCjV@Ra3zE!a?
zg=#o&+>P6e(l~WvD$ikrg&xQttt<W=i_9sfelU>6yp)LtVPW6mh61(!LF%cr^46Ni
zXMF4M0LHhkTD0%xcV{PuB<euH32uQj4bOuIMXBIm$^qP!Zls7nDxowdd`qaBsme}c
zZvBc;5-WMHrIu*Mf&V1=xnay(y5Ga<)v$bdCu_}>tbB(2EKh6v6U&kP$vboYF-4jN
zr?*>dkzMLg96p%sHxhy@ihL4d>)_9~naKnJie?0IyANu~z7yFpDu<dILdGyobY(Y3
z2M_LodIReNqTlbw4Tegumd3Kygz7Ni>H>!R^7JdB4x5PghW1rw!VjjBYOi<4!TTbq
zw0lnElM*W6jk!YlEPnhgxe~7*l(&ZiUf>Ahk6#E>!SU-CNxNCt2j`oN1r9|;onpSO
zx6D^G)Iyz?n$Ea?<BgcLXfc&?*RK%P`U4%Ko1x|arv;Y`iknd>w_EjVUwAH(n~;$f
zg)#P@^;r$k6}UsJ0V0;9B-obl3HHu;HRowe#s;cqg19nl#sC5q<L)JYzZ;rfDqx(@
zU*?fsV3A2s48E5f8Kp)67FXSu5}I*%z7x)1!t8xPW_4mb8ag+K;g<U(wJg1|R=l6h
z6Ro*|1d2Mvc*)O^`N#f@ACWyhPFZ|oCnDX%YK>6ffXTp4X?tZ~dfG9NV{vIm>bRRc
zx6rUp-B*V<S++<(2CDSRY7N_}VGX5p)2z^pJSS-=8Ajz%j<{^HbWw#*yw_UHZm3L4
zVt@;HMC`ag*^?<Z3*o0Pn6p%5@M1RgI*v?Si`_sgsg;>WGn!4V*qEX~Bj{zJe8YVo
z*IwqV0-zhr%H`NTzXM?SV8@-Sk|@%(6Bzj@>J4TOHEdw9uhgL{tq}(A7!3_EuN`kV
z$F3%|A$?^<Y`wrc4I(IdV$HVuZAZL?Y*4>82Fi4=dR=3hCs-ZnRedeqK+#2oF(NV>
z$Ft5KBTaWX%)1f&87YTRLpmtQhK5v6^)Um|hWwz28k&U*{NN^2)Jy9tkOP*?HCf;z
zScY&qob{Ko3K(coGkrbJMF|sy^b1$KXotcZk%~)<6R2<c;#5D9CyY#^@?7|0mf6;R
z_m+1gDUVF75-QJ9>fOzb7fg#oX~iN>>LJdaAsfo73{vVK!|Jt8cEqOD9Or;xSF8q3
z_h|4TfVnZ0`|Fdy7J8Y<o28(AXxzpw8>lk&P|n#Wj^%hZG|8``wnquY(iL~Y`Dw&s
zQN&dNp~Yd4H<Q>plS=5Z$wxw}$)y&|Ua(of%>$ngcNBfT5GY*2Mgs5B0xX!sbX!KF
z1*=G?cZdBS))xvm3md+YnU@;prBX!HY99k#J`z&NbJl!b7ojV5F@dyU%Z88_x@6%H
zqY*))yBCuh!S+7P$;LI6Zv&<ln8p6T1?ES4L<@s6b^1}xL>~>@j=>y&$Di;mWLc;h
zJ}vLHJel#oG7&68VhSn@ua^%jo~W9EbV+9S`+SKEyG|<MBp4j1^;nf=AY6jWfT~e<
zThm(jdXp^LWP+$mN93a#b1ai98CFLFM!68jTV3%S6$BU(KCy*!QX-^P%M=no(FZ_Y
z_+juK5W5>iBDpHHaL4_I2rX#bQOvUyb198!6@p$1?F)eqik?s6xhkc(M;8wJc~_uC
z9ku>z%4};HGgz4Ow+K9+mcf4kBo;LHs>J}4ptl;{mfF@pmc$r|`>Bv5L40H2^;gP)
zVdEj}dA!sbpB9_rH(G78n6bwSMCUyn#5VISJe!eogdC1yFcJl|8|I+MAef5#5Gjfg
zk?X+`Joj{Igf5mNT<G(P-Dz7aBr9bt;1IJ!3@f7PIL$;>N#u0lC%heWU1$CU!{X0N
zJDuSz9N=D5>$$@0w1v~OCobfii36ZO<lY}bj2x8bdF~-w@O~ctetn&<XtYGg7jiTN
zky*{Z3L?>v3sMFpFeXNkhEOIB3I+(1(Xf)9ld<2Y5z1BEbY~<YCQ3YzU@9tdgC9QU
zW~-~wcgGYGUAmif=v`ok)D@)cJ)eEc2D80RFd4$n@?0irr>A^lTs$Fri>0jdbRaNb
z2OruKdm199f#dGdzgnEwrlf}~eP`I*M1x6d$M7FNv=b6tB|=JO#pCt=2<#4jP@OBG
zXsc*^O2qyNTTKfp1IBQ#(6O?hTBbXD=e`x8S+JcBszVZtm02AKnzg1?smj`ypzX=}
z9<+Dp$Nho@o;NZNCH|R~pBJ`=Xn0F>bagzp9?~z4;gzQD!t)GqhsH2@)|cLZi9vDa
zyZ{yxbtpD5&~f#jT>@NXhWX;1ZhPK;pjB-&@FfoVqn@~YY}G~9j9e+%x4M=)b&rFc
zF)kC1$wNS1Uz(GDfpx@!qAo>XRSd~zMMsJ-Y-B(11HwKNggI;_@ken+@4Wr{Njg!<
znzX&<Wqz+(exwC`{EQ2u7F(?Xoh=JlON!K618|N3<r)k_Lf94W53Po0O1xCM)JL2G
zW%d(zzGz5jy#w+w*QPAv8;8Ci3||M$q&JH}$K;2?43kZNYIA{%yVHqjT(Haa7^V0I
zHfdV&{*K6VS6}t)-DllZVmf&q*lnt0YZ>H{6d@2r#iF?Jp=;bz+~ba7==Le6Sx|rc
zJGkG+`}OIoo#cfYu_dNoYDY7>m|!0eEd&aW%YwAYU^W~G26A_nvO$SAGYQ4Ln$z<?
z`hMy=?&MgJlZJzl!=+>W5J^q-iyXxD#Eay1EY42nVWtbOf0&gm){O7SYi!0wu6zm6
z<PB51<ykyd*sKqf$qEtc5rI@F4Wt{=Ly?+G_fQWRMMP%p*V~FcZm+&!`*l%`5FhKV
ztj{VL6{7do8EJf0GI)|I>%*Ug-W{BGPn=<ld3mMQ=9mZ4)?5*{67%s{<+Wqv%hE4t
zuq(@kI<Q#{$|NO8$Dtp;2`v8i<#`Ap-3XbTUXunZLth18WwCjfL_aUVT?G)(w$qDU
zHaQ>MLnl6kmKn$`sI7V_!~i%EJ{Z~n9IU-<KC{|b+E>>!`E<+sT0#TIe2qCPc>y}l
zBK8I8T-2j+@Ll)Byb4Wg%i7Z139{S=N5R=#jmn_vODZhcJC8Co8yBuc4K|>%{mJFs
zI>Q;%GD-BZE5FNBuH6|{ru{44PBrw)4P~X48f9bYM`ayygqd(2G%PYcr@^`;PjQb`
z?YMDyl(v=Lc@q#?S~d(S0+Ml&*<`koMAVmLm-S(=yIbF|-|VaUg+Fh%PFhx3&`DLH
zm@u~pAnrwr^jF_As)HH@Z`Jy#w#F5?Z#Nj3#_K8U4t9x3wyi#<$YPamYa6A1#cHL`
zI=|fLc7-1^j3qYkol>F9K&aUedZI92pAl73ihmq~<9jP3zDZl|`urbjSPWZ~K#f8z
z%RBRT7tLm&InFt$A?%$^iuGe;=u<s1l3>k)a*-PZF}usaEv2efAs83k(7+|MXY+L}
zDkL<nM_e)_B6Z#2aTf$n2eyeo^?c!V?mbcrprg@ZpRu0TFf1qAxRiH`tT6~Fd~g*O
z6<tr@wSv!%a*Cg5E{J6?rP4kGQvyBfFPnI9F)l)4$0Sg`y&!X>v?L*6LlQ$4%r)CG
zOr<2SWUnG$Q4oWucvBw_hD<7tNrF!jdY&`IVuV1N^h4ICzCWU6th7$k3eUyw9u-A^
zd38qe&q2IQJ}MeIEPs!+^-C#^mlYF~m-3ZbMcNd$2Z@H+U+b<2c;SuWR@z|YG$XwJ
z*bK(-Lj!DAWHJ(ZOlS-*ps|<B?-7iR1&vdURV+Bn#%G~KS(<Q+sc(OPn950g%pyAt
z1)HNf&Tc<@XL<TGn7LCsm%qk|O_&>vn3aE(1QOq>`ngwJ9(@YIQN-^=UJTvG7WW;U
zeI}8*uqby-Gvv14y7YKiP~?BCd?JcT#$)<Mp2^w?iF(xp7S#C~Cec3c{36`C*3yp7
zbeR18Oxrl%n-w5Br7T5N;kUZTv=vLj%UtCV@eLbzr=uNOC-=<dxO+7RwD)^K)<F!1
z&a?|ih81H(OXQkzQF1@nxbRP2BFalWmw7l(Y!0cZC14nuSdX51UdES^Y4f18sG5hm
z*Cn}w^(-U#j>cBwjmkf~4q44yxM{O!H#qkVd0JG<symq1ebsg_*a7>=ANZ3)imiQK
zl;s?taz!E8A5MI5m~s?Fxq~$a<U;?XRH1D?gbu6(e32|f!0MN_k_3HYJW6mIgU@p(
z+o!`VMI6li72A1LDU%dP!C?Sga^^-bSKMqvQX2^#Y=@WeLXiza%l!S`7b-Q<EJu>F
zQZ+eA91o0Y5Y5}?Td{w^?XaNj_u^BVBunwCa{96!zSfq~u`0GOpC45-k$7At+}tTO
zoCHBJeA|?2Y>bAYQ>^ZE-<b*d5B-%cr#E^jjHh$W3(<l9dO5TXC`@pJfGCmz)X{!J
zGXAvB*q@&;@b}ShboQVM88f$gCpoQRi7N6m<gYw~u(ZF>7v7kytQb$ab`o}))Nh!W
zL;B^(qq1)m#WX9G-|4008+&cq!O|FJ!eIGLTrWmVyXk655}AaATPiI2zMfoPp!Dq?
z_lr6z*}T9($k1iSw)gF~uJ(dZmtiiGS#B|paCwuWZjYLHqx2nFGFfsyiADLF+()$(
z9rtRT0_C@oK)=IuiQv7DAhmGAK$78|Y(l37F}6*^YVovV#+*DldC_PP(7l;NRqK(@
zXD=S&-y#=X`&ep&`|(?BHUd}N5fNVUU%42Td{BIz<Jh;#KMi3^i{?t@fA}c5>&~7c
z+R1wS54@+DTNXor&_<DX@AzZlcr&P!S-G?X0kZjgs3qqXv6$YbfUa<G2_*U|Z^Gji
z<n&|?aS77a?i9L&_~??9KtF%Z5Eh|pI!1E|vm&M=%;uZt;07{?G|@bIMVn^-<*%Dy
ze+1WoebD;800*aND%SFN=Xne(h$h%4(PtM;SgGyK-5(Tx+G{gaRS`5*oN_Nn9>ub<
z!31ObWpt-ORv^I$N|qO=xlf|7Fw>cW?BsO>7FTxH#Z|V`xuQ#J!baSMlYr!PM6bDI
z<z>wfhl}(x9zPrB&Z>9=HdOvVg9<PXb1N6mf0&yC**RA2n6=n*sfFrZWVW4m^sdQB
zRN;y4(qmVKm5{axC(`fhh&7v6h-~t>nwC@v9?V~galo_N5B($aUzC+ky4_aT#&8Yj
z=^=^)L@tTjhT0Ai+CqtH^8P{R;c_aabzfFA5I0g)92=3<)L{x`akM>)FMJqHOk8@c
z3~REg`ydbuN6NLTCgsPLRwXy18Ts0fxWN5zjLGKrKG&HK)jozd#nte>_j^C@N?Vt^
zUpgIrA(wzlh4KusD^GgH;WLJTKiC&Xd+@1V(j(^KJ%d=l7RF76Wje1<Bun51;pdTx
z>vorHoR+`J)<A)!=VaKBkJD3TBOG*Z+o11i99a3)8g|$%u2E0sv}?XHC2fvP3D&cA
zy#X9U1d55@qtE=hWSR>w+*hNOb;_f)_X26aLltdbPe_mO0$mthFn-ZRvO&R<@DUpy
zl=);VK0vQ}Gm%PW+Pp$gixjt@WV;l4xv|Y&?nDU_6*X@&q&9mZ0oF|7A>ah5{}HT5
z_`QJpz5D&y{{{LF*ju09@7uTNKiZDqpZ_cO9N^zVZTqjZ9k~BD?9GwR#T^RZ5Ac6%
z{+}NeWf%akFAW*X;wnYU{~+u9KOyQeZI{~rvG0Gc{{!9QNM~(eXkzU|YvgF*Y~pBP
z@ZVD74F6@>7ybLeh`Nkrj4D^+KWg0cDRQ|)a<~^jnJasR5t?u-@s&S73}|za<2!P%
zzmS#DF8{IDyGs!A`25tBa3FX-U!C6H5j?mN?uDqyzb)e?k~6$N#<+eXA0KjrtT-64
z6kMKL7vu4Z?>$9W>pi+7MTZ6Gy-&$WRvqg|E?k?uY%j(+ZCrAOduZAwZs4um;cYvm
zFYZ0*0edWcgm(8CGKJVuiga{?&xzO}snXP)=L5W@JErbNNG4jV0o`bq491HbxQ6yz
z@AQ3%9LTE*j5Np4T!a49QvCnApbA@pY>sEsR>!X(iKtIb;A>7xi+Fxq6UUIKN4M21
zn>L%y>(KI3MNe0uVmW%7Lap;C*!<&&Z%d;D1UxqOJO%KfgyC)dEyOY(7!7~ejb~mm
zV&{prM_`2_$u7(M!Kj9Z?F#jUMk-?fSV5K)R>=TpOz8ijeITeOHoJ=?)b2VF1}VOi
zC(|eI4-6ln|K1Qb2U(d`nf1-3;>wEYv)y_T&#>u>@+}^}Vv|r>yUh$HXtqH)g`-fP
zPd(cy1+F8Aq1l#L_qa$f6(q_`!=p)t(nv`4F%Q&z44Wbjz_L41zLxM2UWsl52(JDM
z=_u?EMIA2Z;4030K_#|}n{PlOtVb50K*(m!nRf(KzrRTkzXGG%rXDkn84h6$<dN72
zN#XD|b+-Pi8RM`t<DN61bG9c}Aj-|A-Z>*1(kRL+>bl^ANZx87py~_J#Nv<q*Hg=|
zjm&cSmIsgQY1G>v5x`^#ZIh({&Ilv~!&w|=Q9!+ax+cz6hs!3Qt!lyIcIK*+t=2iR
z_42x2IZzKMg9iodIblhOS_4fCY6sYjP)oG9<{T%erT^<yjYDGePKIVjpDq~Sk~IzZ
zjmDD!#8)M7`e9C$8yYvOFix3)*#|qs<hpYKdLpn`?RY<KqA3|_P18$Et(io|IUA^B
z653=4oZsq(=f=@VNuy+Asr0}yz5Eyrhtcs+lpggsqFTTLp~Xca5*pB>4C~AxpNY}A
zpAkd2<&jT-&cI)O%0V<N#}Az%*_S`G_+Btw$V^Gip(RXVd|pV$!J|r&O$*V2XpBDc
zA$1}y;mCM%E1waGU<tJM;Ds<&4TpT>I2KwrT)mO99TMc|NPgHTP94<<MGbI3)2|1v
z>PVf;>5-=Nv?p#?mmzhkxdDgk%RleBTsH&O0{coS#fsB^V(NWr7UY=Dq_Sd}9VNCc
zDh%l@AG~gtM9#|hK2y)7dNwIkt#QiaFPMq_@5*U}tjLFhk<@A9Nn?Zonu0GHtX*HI
z(wW0aR<q-iNCZApSV035=Bl4hjJ{!*quEVwgye#^5*y__{f%|VYYsSm8$KYLce4em
zw8Gv&6RJT%{18B%d;<DK7ICTYL@eZ*^y4hW1lQxH>nUgjv(S10Q(WJzZG2QLVb5(j
zz(@CtB@gZ5$x-zMzM;r)d)_j<*>eHAY&~U!-J@x>Pf6<tGibv`hW&ma4vG7;3Yy0s
zD-<~Ajqj^@Xx>bV<%@wHLX7zu?Ui0iqKo&2FL#<Jccm6r1$>vcaWnt2py!xg4s2c8
zrDoi^HHv5rw%)+toWaEqJML<s7RP7QY3bP%L96vt0og|dEv>CX6$)*Sx5s_I{}AGz
z*c-{oe^NRN{hzUCn4SMsI|=?zA^zXm>0xAT^4~+xT8jUdawh+i=pHSp*sXSqoloRI
zG~Egx|EuT*1m<}B5$Qx8Ekn1(B197fYBx7{{LSj730kRDUN-V0LJo-^Fug?b6y;VR
z=n)mli_>3UZ{y!%6@~8F+$zz`wjfN*_Ybz=OFk`&NKMqIFP9AJijoS?Wf;jegMxAq
zwrsh#abA?19xG)NNTbifgyDT}Ok9>Z&)54GxEu;!Lr#eKwv@A>9LuFU@5SfN*5!O%
z;2ZnFzhJFrI!BXqOwG`_>3|W+kZbf_;&Ma#Fq|;ea6RVJJvVTTa_56(LD<OL$u<ww
zE%mZKqBc(pu=Pa<ZZMWd<QoCX@8u~9)riVqUvBcEgcvl}4QXA<3+ug$p~;R~ldkfw
zLksXMOh#T@QLQ@q2sY}d59C@N{xXvXx+-z?4BqBfO5<5ng({b=DGSLU^p46Y!8*n&
zTfJ0J%digxZlOv&)u0;YTHL(5&y~1V0?rp$+<@uZ!qx{scp`cMK<N#Gs3_oDd2%x~
z=W4FW!iOdb=dFoiHG4)y{6=?l!$4SK{PfI{uQRN&I>J_2TM_F(S+sr5MR;?alhFrh
zkLOJ)INtt#kU*>glX-G^GryE~+tE%xr+CKiu;REj1k?UE`!GBv+zr=m5XXf-x4S<O
z!n0&zE~}=K{XN(u&trUlrKt6em>MqZXodjbQLiL&7ROtleOJYI5ZX=iO)M~(;^p_h
z&5|F`zMxrE7!$6&Clu#u`iEQ=rR>*p+gaE;dln1pR6hNWc)2UUAT}67lt%Cw=y#CE
z8=)=0^Tp&XSk`oRoMX`GH+PpB0hjx0#ou)rfzJer+wsPo_E98I2*tL~MiOHbY`%NS
ziQ`!>0(2aVwf`c!>HD3cIT~9*c!<2rvUMg|Lm583n(KfcXkyrt9G9Qpct1ojHuGu;
zl%AIW;7AzR1_x9V__HDI_))kM93`_QgK;vziOMB4=6C?7?2e)KAi{{gM{WS_vrG9-
z!gHLd!gPueUI5g(Lo53>T$Jzm<Vm2tiz}WbUXn;yM+n~Wz5`#VE?ArlB2lLHmeRI~
zQoN~MxG<q%c`RdgbW;U9R`(9p2HAbXMkdLhJV*_!L^A)v@>NTsQ}eOBPM}7Vh-h(H
zaUssHFs6G(1Tc@@NO4w?kV^TgiB^_rSafa=GpF3}NNVsZP4}25R}xf=O>0nXQybSu
zd05p!q9v+3Pbge$$oP8k3SAZ_H(4-V52N{T%UG0Wk+$@cgu0z{xwO*7z*=EAt}sSm
zW~rPx-4xGPJ~zpgz{TfTV__vJkPZC9-gzU#xchKG1tt1klPFiM(03tn8Eco_@&*u9
zebQT~#K?ccVU^GxeRfE4LN}sWmK_^rr#*35#qh9;a{PjN1+2`&Y#A~@H{!V8y(l4-
z7Z(K3C?G!%-`(MIuB&1MZR*fCw9?9${2)P)enw37X%hmwt)STiHKO87Yy=UZoww?4
z6tCkf52_B-f_fW}`O?#6GZlR_z+@O@fToF7AQ{bw7ml2+>MA2g+qP={yBQMf_R*D1
zK##&VtNTp=GP8(7HrCG1a$5!hv0*xoH3h>dMovm~a~e2V`rGHWes~2Jm>Pl-AWV}?
zlQk4#MI!$}k}zQqK-_0!fd-Df=G=xO4)RBp`!H<*Zz)ZIDIuRC)sfy`4U;E_WFqg6
z`5{8u62d&z@LIrdMh)s987VNfqKDWAr!S2dX$*jyBO&M)R7SA`YIgQl43iUmA678c
zn{$g-?`yNVTy{#Smg?D1wyf4j#}hFSo>XC-?|UC24dEDA0~McrDD^j3GUNP!l=?<w
zE}lfpByO+)h7=WXBrf~`<n;71gJ}bKLecnMKUD!!4s1B7TmAsRh?N@H+wgl+zH{R6
zBTz7REi1`b?ZNq!vez5*^-Y!r9;NeKf^AA<A`3Y#zV*BdO5YLNE+p<D&?mN7&lWC+
z(~x+WCjOi8g0_Dg_m!Uy_V0n#!|t%w19Cl<gXmRJZd_ULvrBk@PFxS?D4?APcVqtq
z_d%zx+x8s8EvitI+_u%_=KC0w7&PH^$1zp)O=5$}9%SUti~SGhljBNkJD|UV9R}b-
z`{*Wh-8nvT2@KQRv72cN3?j4n8wq3SjdeB%J0i>h4oqlIp<!q`DYBsEvecD4fz*D*
z(B?rLemYs$8wfSQz}nD3RCM|WDyUjaLT>nQN_iG4HM*W`s-Pv>;$RHEgR5)Qh3D<K
zJ*AXF;PsMeBsc&2qi68J4>OT2Hi}VLef=2-njH5Cgbi+Bz#Q%#m^gy7F92tFXDBDg
zih45U<WEbY+@KfGas=p3mumkxeuD}f)<o5O3@KLHQ;>LLjGv)@<aGx(#AKN98L5~^
zOre)eK@+-&yMIUro~{~f3&&~QwCBTysNcAP`px3Kx1s(Tu<@F7zQJLG0d%$_b1bMc
zx>sCm&rrb-m2c|mLQx2PZ$WR83&t$@U=tvk4COszfC*eb6T*#s8BQd<D8>a-yw6kW
zrW-9}W`te<uf3!~dhe+at+P<<dWe0+C;2}3lE<yI+81<3O&!{<E(8F=yK_x%@y|sP
zi@U#ih%Y9v?VKJvzn~AjdZV^%esaG@KbtW(-2Gc*{ctN$&9?mz)H$A93pXS}{1yOL
zUl2ghDsG5Aw!le$IJ{Oq!S)3ZZi&giRK+~wrb_v#Z;lSBKcB-p{+#@n{s(~|*+>})
zaLBpIkfKV!BK1;d-u&r6cz`Q=)@cA3+WJ7fIPz#?4?V4rUp_s;x&|*a=tFWx^~C^t
z8G}zI*?BovN!qfsKm00{Bu}$N&=P}4^CPK18zKw_FzJUmVb^IkFm`*mw9q~0^Kop4
z%*S3!0X628qmSqK-t3n4^2bokO!N54Ob>{+Bi3rlsL+lu@%KQ_EQ}`%k(>PLz3j<=
zKQ7CQdu9e;=!JLKFC-u|;&kKp(5w_s;x6?nQVA>W_3nIsFX@Br@9NwB;0zb~^%p7Z
zP|@K-@637z8(^om%pqGtB~7vqs#|I0gTDKPVA4*!%b)|Lfu#Mh+#cp%2W7PuMuq&N
z^rqHiJ{5KPy^4Pa5!mbvl%GxT9Gy3%@9LRuNU02GN#(bO6J{r{t~NV6VFU1P!tD#<
zt4D>htN(Fr5;tIfA6}=;x<De1gBrMG?r2`x89=rHfeg@qeZO2BuS@stg701K!I;W@
zzh$lv7C7pi2@<>mJv+_p&3N}EtI&G**sx&(csUyV190Y>mcL#oAy!!nBSjl3tyRmY
zsseUiO606*V1)QGI9$!*l;O*4UmNuPS?GwC$=9HuX<yQ1@ycWHo!-ipvN;`iOV?Ee
z&jVIwNu|OR>i_e{7o61frd~U#=X+6^hvz$&qpyA3-k{a}9G>DsK6{_6sV&V8q0;`5
z)$2Zq4%qm{$Mho#f$MUi*o{BQDjF(gGMxS-imvnbxp!VK8ctqYa@>R$byUzmQkL@6
zZ;=4|M1MF)?`&}L2^1Jy2Hiia1MVi5V!9sb-qIETkpsey4QXi?*^1RkxX-4_zK^M_
zZ&k)2ge5H<y_g+7<Z)LAzwT3Jj35HLAA6E5p&mh^y43-Ru8bwgOZ;$BOknLm#&Z4N
zm`APPjQv<~z*-IRtzT4I<X7N#@gv&S&QM1*j_Ys&<G<@up)PL9*MO``^UZ@JwI?s#
zbs=vr(L1ge;P5=-U-{;!yB{hMwDi2=0v;vlH>?n}A1shHRS)t@!v)61fL|eq`?QGq
zuW)b^`Oir)q(_HQ7G!8Ae!ep@oZnLl0^yaUn^!D7>#c=VftiZ8jNdb0xHd_!$&S8o
z{HwQkTE5mH0@~IkuBxf$pb7AVDl*;4*2X<(_iRAk?E+R@CLkHdb0bE#qcX-0_T-w0
zRs-Y+2nr%-MlfcrcmnAR9A?@Z?;#WUU3d_PcX-!)CkeED(w*kG1sKz%p~DU`Vxr=k
zlszhkrxc!nIygGg;p=?w#i2mF!-4_ymMkzk|05;^jk2#n$Zck~!jI+c*G*bcSLOih
zm?=}SBxB@$fFq^pbNm6P$ZPu2^1F_ptgCgfK=0E!r)0W3HMiiM1LlW-N+Ht0xdN<d
z>8BJeF7D+$rwvDD1#-q_zIKB%yqI(66m_x=^^jBA_`0It<sx&uvA8ygR=+Lr(y(qx
zrguli;_3na2HxnC>1nqZ-S6k+-+#6d7`Pi(PJ!IN%0+_XKUXg=ibwy&`N8~es~1Zr
zJKO&+M+u-s+>)W>e>qAf@jS9a^zfpeDKD@^OIIM~@%e>9`16`UOp~#9ax1u08U(O?
zH00wP-VCIq1p<-@?mMqvCOfZO{<Kh#qw!r<XSuDfRjinDXoH5_k@A*(Le%Hlgh3=c
zK`c<r4lA=+END?{XB8y4m)TKDwn@1M?c$^9JDB!pJ!SZo&fufySBB8e@jzXCMH^wF
zt8)DTtZ1-7i;)HEsrOFClk$J_Q>2rb-qFPJ<!Dz{ZfP=}SPORC6OnPkb{k*&I}-~=
z<6GoFN9#BPa{E>_`dO-77Khh{I#ET5sAD%ikVhG5y!B51Bv}VY{J!z|O(O4wQ){9L
z?Owa#{m)be#`@E_kAD_g@}K{F!VNwD)u_Y&Z%^3T!uJ2CJhU^B`M;UiG0IZ0oAl7z
zvlPM9nKIcx&T7z|<nsAIPr%Jn#^7U#qIvm2{n>?S<+BD)x+ExOgkTOyIU)*2pYgt4
z@|GrJhFhePplW%`7hKox)tt)T?8SSkSx$;!3SbWr*)>X!$(6m_KA-zVp5Du$hjbZB
zyh>rL6hM+(RSn(SV-02DkToBlTzG(f4l|zEurtOI`#%a6cli`CLR-m9X=&W=#FP6z
z0OK*6Od~c~Mf@=_k2@jBG$aFS$z2?yil^DbI*>2}_GTSWEWQT`g)-7)Cw<<KZW{@q
z5v}yVNs|ropvOU%jk3u5L9Z(El%3eiGa<V1Y8&PBu+<s+kTjFJQTs5&9`pQjv&r&h
z*ms?%mz*M);LN_UC5JvNbif|Y!x|VNw%E)f_ZN*y{Iz0WGXY;!7h|bX`X^1~tRM_m
z{IlbMWuXZ4IUsFS5Y)h{+;YDjev7&zS3nvvxKPXx%`+Q_W<zxE?P5)>4T64{C+sji
z;Yvug>n`T%C3l@eF?K-m#??}GsoNO^IkzR$xsvFMqS2G%&vy)!Am1JL)_0DRk8jeh
zyZ+ahXWHjpC|^lOxNO2cih4ED4zrBAS~sO~++!+HlXy`AGYRj=Jo(2w2XDx(tuFAK
zH(pO^LS;KFTBi!g#?C!P(`nQPllO4~y0;Ghrr_tdD4X^$%X$0^>id-0hKK#<AE9%|
zrHMRxE<^qYU+35)SkSH6a&_6ZZQHhO+qThV+qP}nwr#tn2N84cM7;AU|G>_(GxI!a
zZOF~#!O#Cyi7dd*8`wYq0MP#=?f>_ccaZ1ozwLG6|5%BRCQf!Pjz<5VYJ^+)zt!07
z)1E*q=9<T=hX7U#puRG<7LAc1kZ;hDsej7~#&b3zUMMW$sWObuNQfXNi?X^BMQI|r
zw4$nk3@WL-LY{Ij_D15Jn!ArHhD&1~J~Q!j_})4D`&>!=S*4=G)D-gJ(nDAK*R&Pu
zqQS3A^;yTa)V1QKwzFs2%SEl?X4Pk1?V_=^ah7+_Y*y~gpryM(Z>EK^@*!$<9Q+N^
z=RxoHjc&Kg?{nSsIaF&I#ispsvSh@@ud1;#KN#h;PS`aQFQes3Ia5XLy(QnS-&F_9
z%cNo^GXG*yNVfE1i^*kO=kv=CDw*dO?_FuT(({b<s}{TG8DMpyv*zlfix&BJzXT%^
zlCG*j_1Qh}T18`*^_sS{8pUp@Sbvd4BwekS7YKTKZct4*jQ&kFS*18sbwB#$`f;(l
zg3IU8M{7l-y;MjxYp9Qq&LBHcx9oB`XXg1!PQ`bz=?=57TBT)jGgnz}#qG=Svt^xS
zFrQ-o{HXf@@a6$3*NbmU*#wYIVW%&bZJkK3`RZ)5^R(0^-3@wX-#`d&M|oN&jL!e}
z?QaK#RhOn4blqnH-P1Jd?&}3!!#_WIkNc<<{sMMJ&K{ik<6Pws>1T!TR(p?vj$gOk
zV*wphYUq^EK_ej8H+P>O;07Tp&+ou3kQTmgveX}ndOdzYzaky2F3>H|7iKzu%WIW+
zB42oj&1@?7u`VD=0PD`mKl;J!05^#Ib1M@B<Zst46ks2SwjJYf8StvtkG+SwcT`_T
zacajYJ@fs&pJ27yJbWa()DGQ55=O0<Zy-e~VoXK%ntS=^+xtyT4t1b?$MD=U$rX3t
zI!c-qA%%oVe?mXIuBAExD*|RU_F#Q9l5zB(=4ygZHR}8-VJj?Ogf&X@eqY`rP&fYC
zOBDPLg#!NgNj(5-Ad16o-SYi<u=m-51E5(0t^&)-yS-7~!3#~NWj>w+U$=7j144w-
zqvO?t-j-jH-h$Y)e7zR5`}tblZ{KUUa{P46*u}-g$?A7&&o}}{)mVRgp6dO9BzJD{
z=oG03w%a0#a1r-@sA3Zoy<6>NzLslMc}%4Rs`>2NW??~8K?Wz)cNHk$98JU=_%MZ2
zhwg0hFCovp+}PyAOX<Q@ly0eg;0#1*FM|{If*b>-K-WV*8nGNYW%?DjL(iw)5PZtK
zm)J{#;pO||=&!E}Q{{9;C2#)IO(r@61uy}mCT~BR^JWPHm(Jp^=jH(iq$VQUt>gps
z@Pb(f`$JcYyFY|m%-Aa^zOTo1qGMrztY=p=*`7+)43Kl!QZ?xctOh7d8E3E|lkRb|
z520{a0d<S4`D6zO9?o+RWJMe9KVe|<0iW|-lQR56_Eo1g>@)oav|1DkIL<YP^O%za
zvsY(xRejj1EzQ~HIQcp84jkB#;6=By5jVU^v!~~wH9<4!sf9`n)leY#jJ6&bV)Vk%
zw-4nDlp;eT>2SoB2l!eO7>-D0_4wUmp)tqI<`?QlX&39iq(LmBw9DK_A<)PzFh_3(
zuw61e9Gb>|^ArOZ_)BXn2BN=1SSuMc=b^>?#_SH=$!-utHKHNKTL!eVc$Ek^_t;%v
zw*R|@kJ29qzTB`S5DK(Kxd~fFdIe9h_pQ7HE3tcRh`29Z*V>VC2Y<AP+SFABEE{|x
zTBU-fj}N(*``J|kXo|&cNih^0=)Y4L@Mw8lEk--ZOafhIy@@#FhKJIwwB`wB$Y0TA
z!=Km&*0GWT1CdlwrIX+uMh$-haFEBpurvnI*B0b7&jrxIOfI(MFUS5(>x3njaqm_}
z+`M84g1sJrumCgU8~kcrD?e?y(b=`4{f(*j$HRAq58%p5bD<=jV;*Y|?V-XF>>8Y&
zzL-p@nL%a>xDyd<%6kE>0!#w&DPlA*z=1s0GtlTPTvx(^`=7}+8p8Y%fri@lMdhc5
z4~}GBUJExV)L;|fsiXf_$6c4V%4}DU01eor_%e!byvri2g!f=5pV+cfFm+Z|exKcw
z9eCcQ0$uZoG|TYJKSs7vS~H_Odt?dJy~vd<xy3O0_`9w)qrvPmz+CQSxxxGiGmn3V
z>62<Gt#o$oy5tvzt10#~XN?5k43uu+^rIV)#&$yYQS_8N;2H{975D}J6_gmTX%t)&
z_!>%+nyfpTpc3v(mUwyMvE9GQ!ZL||sBTHfqqNEN@~ZL!Uf&43<hjOr{AoR<`&2yw
zvWWR1CxFp2`F5_J6`4odyByzA1r(gO&##_ooSOgD(-+9LF_(#dfeXCp!AHxIFPTi;
z(z)wRG(sH=a}4D#qB~FBs6aJ-E90JB>BI&f#kq~K4*=Da7CaM)#6|(ozeAG6;7&_q
zSLsN6)JJRY2j`z$p_#TgvKeVKNqGJba)#xq#=lzTmNR>Uw9dbQ<^jK=3<{A*Fud!q
z;nz<#nuGs_t+9R~lm))#Nh5b}*R2Pg^y7{-pLwBPoP8{tLT#b?v4wrlCj&3#&H)0i
z23c>Iw94rGadFO^3pd6+rl(1LmA+7zu~7xM2*l2{%XF0?ku`?@Ci135T=u7~ZGub$
z&*C{))-MV8x{cHcRy+EvzvUZUO&oK99kOxCGgQYugRN@G4r;u8PsA~*h>nseyfp6)
zFCCkA(DDztGX<Evd51veHsV&yf;;O_14{}`kGt=BmcF5)51AK&`XJpH%h(vt!2$(_
zY&OdV$Kb$-YKDcCRSM)jW7NluSp9tT=RFpB$g^B-=M)>84>JS>Z{ay$SO<r}0-ybj
zJS*0N;c>z0GmmtP(@pa7*OjJ{x_^Q`gPV<!v(FfXc*CVr+N|?<NM7Iq3qBA%j^LG)
zhf-i|@h?L3BOfo`pp+LRR;HT73LWjjjQRTqJf&a2`Vti<1%?nvTPO)pK}DXa*nDBk
zsu?yA?dW`;MlGAl78{(w_E#jGFXRHRlQZ1?<}rgtab-Q)qwgGvHtMlP{u%Yq%j*8#
z+1c)8`?<1pwN_UTcv@!=95!Qcx@XsIy|UHs`J&lvS7Z{T?GtiGG$Nen8(1b2k$JC%
zm^V}!1Sh0-t9fI5E(pRowoa}BX}x(=R-V#Udj-Z1ye(3fLe-4zMS@YNb^_Qw3HEnd
zwy*&=Md0dB6E9*Jm;%Yf5}2A(3JYcMPr_wGz-2x4(nCxWY^czY%h)7oi;S3q^3&2c
z_fe?CUT=VQ&TlTOnL8AuCY?wpQa#2#jCJiOC`E&!YaZG4i@q&om>b*XsUCc)^P33P
z8h!};V+Tv6EEOX_tdOp1%nE@e%sk&ipb)U?#I;Q&wNuHGzoa(#o7<^5gBwd<t-K-d
z_DPcbq6R__jh!8bsLsjA6W39AUS*#f^dWA84#<ioXdV@c!JX9uJlOm0)=r=dll+(N
z`CUG6SwfYU>4aKw?b#S0iP^9q>VC-GeXbEnOm<X1`V{TQ<z@q@EZiLk)=a?-)!+r=
zZ|2{Wh&@UXNgSy7H2NO%01HrQj52<<q0rx8pn%n{MKetZ`f)epP%`JOfaf%y7zC<k
z|2)9$qtEV&UIqqnHbJf#`~5g?6jMa%pk)QfP$D7mm9wNks;4z;v}>$!^}B$ut38KW
zfbjkYfC<yR*lCO@y|pl|2Wm`ns}exLe{nrH)Iju`XX@|bH&;r`R+&|uU07?3)8*#V
zZ%ziindd@>fiM?MWg^#x3u3^KF1E0`cA-{}fP?8WhqPK1_0k*(K715}pIVigODVy#
zHx)9fe9I^?*hb|jI^6p}zL;|<3b5vj5j2^a&OIp&3Hic&xDp?(mxh>EXWgM!{sXc!
z#>k~ZZpA=>VMdugbAALVUz-APg)7rXvK7S1h^F@GPwW*cIFI|bC8K{NB)mGthZ>9I
znRHeNR`8C5sS%DN_5D0p7JL8afV64>ZDR8TlnkEwLm2>0kI(lHI9nsiQc{WU5`tK^
z)wyVM%|n6vk4e#d32k>;PX)u$`n?a(5KO%HB?yTkJ%&jkJ_oSl@z7{h>6&S4hb|6r
zD7>=)KYVW^q<iV1XAp1vC1EXGd(eLE`Qa6c5BGZ_ecI5wN95B6S)vDP3?T%nn>p+A
z0qRK|nju+-S>IH(y4VR$vMC%^Sa%yN@C-A}*mc|Bs&E?<7u5rgILXd%5x;9fmrc|b
z!&-MGZt315rUnDtgnOKL5O_f3c{7&6z$0$>o~iw_BNX4YHN{+>Ard}&X`kO7J|6wu
z7px84<Tp_ulW+=>gB*&?>z~veouCK*DDMHp;v?hh$!@`GEWeMhNm}HDbCFRBplDH5
zy;A!|d%>ya7S}H7!aq1CxsKl<6#MY0tB<|Q6ZH(y@SqrK8RV8{ej2cyNYisn02_Pv
zaI<m=N23hkzH5{^kV*i}kwGhLyj~BF7+&4^+)~x<f2#On5WXW1C+Ne2$-E)wWry|~
zc3}PKVplo!vYEJ*K0a^fp9-y&zf{H#0Fe%fHVzcHWJuAC_WsaoG)nBwITyl0n~|+x
zu%AhI?Qzyu3)hZgbb)&_ID^n7wkleK5@MxbJpI+d0Kf*H9cI^M>S|3(<ahWMk8u#x
z;JeT-pNr2L%(J7evYBPiUx`Pd3MflZu~@#WN~_0mpzzEQ2OYZxh^SF$f*jOLb>f)u
ze^x*1xE2-osbS-VR&8dc48yhE4}36Lb#!TDrbrHKx}0fN*njoI-EgdIMCSIW8mvLq
z0;(b(v14(nTx`^sfix~XiBCXrsVQ>E69fLEK%-l#{Z>K|Kn-8~@0`a*FIPVvC0XbV
zle4ZF=BO7fd_j$vD^6^qRBi=VDeL^$_GU53I+vi{?IiuTl)SOUuFWzc8Gn2T_{J7v
ziyUTZC<&<2k7)+jh`Z<tn1Z_IVc}2m{6t#6Mj#_!N#47c?oztb$ZNRL>L27gup$G;
zp(9=~2>~u!{)4A9i2joDwrYt!qhiZ6LwL>vwt@&3A8G|_LNyDBm|SsDop`mhZYXEZ
z%@bC(Yj@3#2Q?s(=Q(9y!z%|Z@S!KoEq3H}77BMEso_ed1l&vdij(*>v;t&I$9{|X
zretQbc)1~t{<l!NWKcA^!{ho4Z?EH(Ac+IPO>v;f_`IHf2>qu4w2DGfxa2Jn0E>cX
zBUUF-4yQl1YJ+0YYV0-ous|B>ctMFJIo*L=E{Y11b*<Gwpx?)pc@%H5qq3KOa?N9>
zssm16QNK+fJwC&G>f|cc=0;X@v5vM(r^xw&gCf4l;{_sQ62p{Z-5FZ<ctV$CFX2hy
z;?Z<Js{@8HkM(8)TLj&eL1Sd86hcIJ|B#Ga%m*WV44@-7(P%*87prR4!C(sD$KDTV
z^3HW+hD#hLj^F1Onai%Smi$6i3kn&%Z>@zCag4(fAkfxtcy6P_-c2k11eFg-o9Ly$
zj~6m?KD5ASa+23L&qgB~NmHuMrK9!_VeMXU?+yD4N(cjA&<mknd%VP|YF-d%##Q~9
z2O&zHs%te;Dt|9fe7({dP`|*p+EvQBZaN5=)qT8btM_!9$==4q+2;E7gQwM+P?{=9
z`;lmo^$?Ov*y>7)!4zk4q?nEP8aIw`p3u7G=+YQ$TH8##x^@;^9vDM!P^z5@JV(a1
z_=6nsmX7nM*HZ(@-jz3I{b={@miP$O&#wx*8zFCy_y%jWR(4wp=Fp0<q3!hCiaG~J
z(|+cZEwZW6fzlbaSL<%D{rXUis2?-6ma`z;g77%4J~tBGlJCDL{sb)D$aPB>x1EXB
z-*m#Z<+-jrQ12SIaQQ#x@CoWTwG}YC{0|#%%k+lfEg%7U7{4K|U>AhRV@L~7I01EL
z;`OBm!<PrTD0~5~8=bsMHLrg)Ih2L??2EnvSqjf>3zzL2ttChz!*WfoxWZxkvWJO;
zNv0IrqpCqfqhX51;Yn>9jeBOf4vSp=N=yHvlGEhXnAwQdY5urGhR{Dj<bD^VpSLWP
zclL3CC+!(p3O7Cq@#Ca2iY51%c~#L@zvHb`&01g0LF=5nV|L}mKDv~T!$3NA3lkiO
zxhR3>g5{LDBRHtjE=A)xVaSAY%$|%rDm{M<Sr!50sp!|sos9d<;0Sfl6`3b&Efnn^
zrxmNG@hWAZO_mM1x9kQHugplB;$6wb0Z?+CI%B(JU>mk}V{kfiyRGI~lv^eh1k65h
zy-U8}_>$z*#OqSx|DO68nqpiFI*`jObQtwqkS6A-8hOnB?7051z{(Ci9qPas%l=1J
zz_s!rkS(DXCc@F7s7&S`B34v`Fuq$p5HFH|Mig(Cxw2g)$)Yr@hmscXNvxKeE$2{d
z8$l%oA!PCsLKL;z7?UhRXmj9P_l8hZtPVs{9xs!UGJ2N6a_iD9Pk^XV4-1DJD|>}y
zw@TVZ;^UZZa8qY8T5xIM5CFsk>Wn+bts4V*n3>WwlE}gj$c)n*D6`0}M7mKz*|~b!
zIwMw&WMV{pJV>$G;3(P4?{#E*_WV3dPPOPEy+ScDmh%HKT0h2U>Y8IVc_bfBu~dIu
z-nqva4tvv_EzGej_oJWNI4K#ZhJ(E^zU7pDz^^Yg3wbK+yor6OzU&ap5qn9~qT_$C
z#dMNVTf#OHX(vUIz!sQKd=u70+hhsLR6aDMpr*<?{8IY2oqchdbC!*$^$8b?KO7yQ
zf<-jzTAJ9XNG8sdlPX{Cuqm#YEHZ^%Ezbo+L;Ahpk;g0>eT~C_)4F+0UBT6liZ8c5
zy{h~LK{s09XGfOQySBzH<oz63jiwLjcAb>k-pjNZb>H<b5Rl}EOt8j!k%CqraWF=c
z*!jqZ=Ywvr=Aa^5k0W88i<S<o^vMSGU^M*75H*CZ3qhMdyLT<UltPrD>smo4ji9Ff
zK?>!T6g^d57)99VO5hv1C;2x%SG*r1JR!WeQH7}wmOF7-a}KZE*^-=hDn|P!ZB$~l
z6UWo0PjR7C*TRUm0f)cdHIP?&Z?>%f!D4kUh-e5$#TQnawxyf#mAJREnelo#P!gEC
zY%3-MMIPOVYYLESIfQ*n1c2l7fB=iJ*=u1P%Rm|IJZi(usGxeEcA&H7cdE-OO7Cx)
zmSuXp(`4CIA#PNWYidzGaHM-6RZ3lXF*d1^)%$UYxm0eDLQH<&;GRDtSf#)`0wW1+
ztF(>N5&SM)+s?rBfeq^B393^BxQ6HbA!cTvrj+>IjwgflB*9D7?m!HXTfO$6wwm(1
zXxn2bax3|OJ0Ch)kyMtp*Ws(l@)NP`Jny~{c22IP&afU<uViU6)+<yA3xatK3ps=)
z+B8#Ca$(OnOMhRT5oq*|#<tk+NQnx$n^28oGEp>R+V-+ydgjh^k<(RNv15VH9=LU&
zqA|m*N2=RZRuk3YrD00hB1*E*$-Y_;O+=_4ZYOxp@a*p$?axVntf`(39V#!Kg;%WC
zb+zsC?BHYX%SUdf02<bLs5RSooQyr8oMf9yE_weJ5{Jv-B2~ugH*kdHsBgL8bryFo
zIq@D%F&3}}AMgn9538395iq6PtMyUk6jWnxwpUR+Kt3%=l9FYEOu4EGReJ)Ofgm`*
zlR^buU2IqQhLGL$?!g~~cZam$qm?3dy|C7n?^O;tFeEVLQj^Au5e&b#$P2*ajRb1H
zQmL-{X?Hoq2}p|1tOS&JDvuL*MD<|~xDE)w_ApK_kk^cXv_jp4G1Zo}_CX9B%7#26
z`hs{f?j$Et#ix9u9ij=J@xdZGN-&WWBWQ?|)|b!Du5K!aAE`QrWpPQpaNXM@IEO7r
zKi0|!`2lf)C<o*X1YJf|DQH&?-6I$lbHdb`6^1Ta73J&T_%lYuZxq}ukzBmCF2ye;
z0UMGZ`>baSTC>J^`u=p)j2;g{4vQ~pObkk%=#eAE%miIBC7&ZtI44eq4iw&ZI6GeN
zD8AOuXN~>?k_C=xvb|pWu+97p;gFbT_{K7hvX>E2&EnEPVx+&)30{~#%#u1TGuiNb
zu$hkGYOtL3+LEn*zPHAZGG{E+6ig5K#D)k0N2YkzCH#Kx551Vgi9WwJ+3?ubKX3W=
zet-V_K7LGhvf=G|Bi#2<XAeJJ_NMs4F7@|Yi!fOShJ7PDrA^iA&eaFDxX;(b*s^PV
zsW7G<1uMuyr>JRrMeHMXaj1IT&yhi-fPV7@B68>tWil{cI)LcOV~)jSx&^t0lWOD#
zO4E~Y>pom0-VB<!dG7B(;5p|_a0Bc;F0%F-J@Z&w3PKV-ORiiq4$g~vBTbx#?Lsvm
zb3n2OYmC}8Lf9U50&~B!;wWpmuBNJ5bWq{Ea3~^aOqsHgpi<i-M&ri1RxZ7e()n)u
zyLWQ4&}yVaSPsPdU&D6JlmeFqqD8CE6_!z=wYp4Q&vlLXZD81!2JKT361hEubBPjx
zx|UXKu*xnyHW1F(Yf&uFQ81`;_C!V8Wn&}ih`Uq_m{&ZDd%va&Xanjkxo)RX`9>mW
z=Y~?rPX8L(3qNi<mj=Hlh?UzPo#<sxOWsk{$`HLw(R^)0angt<LL#lFVhYS)sk6~c
z8N}w4>qTF}vORzwQHyFpY-}`Kn<-gz!I#^xSagh75!V!g<~;_@(29{kg<4h1;~$7L
zo??_dLx>yOCZP!p9KFOn*fmg_yp-?}$jphQvR}q)r{~}j%xJoM%|y;SbxNy%uklYA
zCkSoCpx?T1IA`RrG=n8xEm2_R@3Zb`am-#K;m-_ZQT04pmC_=$mFDEKBd+#$QOU^>
zT|<%)o}0>fgtA~Y(^j8*U{+absb4}N<vcb47J9x({r-H1(WSr*Il9R32{2vZvfz^C
zIWHDcE0|jkmazueU_Bs}dKzwH*G?Mze2G^u-6>Re``EE^-4Lf12B(j!g<=Y02cw)X
zJ*=Z|^%pV3)S&xaiqDHx4_Y1+%$dHF+tpu+5S%+&C|TV=(hcC7*tS2l#5Z>jKGPgf
ztyYdX5X)obV(llLa;>5n2`<x+&*h1W71BK}cG8LgNtsDj;|II*)&GS~`2ZQJH*ZnF
zryuE>)%`JD+bQ3n7+4K%bYDQRq;3*N(-^+5*J|Old7|mu|EsXvmH21o9LknpRCRX6
z@xt2CGMg%tT(=)u^WKUD+wJf4S$r9Y8SHvoi<0_^i0w_umZ-~{Nva=5Lgu`Mk<tq4
zZ1d8!uVZ2xmbAsfb76ixCaH^?qT=b+ri|1Px5Co^Q7orp-Y&`e%vM!(qvi*h%=!li
zx2a>_DiG0bZ^0(E!*(1?HX}S%BPj-ZT2WpluLo?ig*Dmq;7Syble$!w<t)}kO2#jd
z_8iU!ZikyQWd?Jlo7b`&yVw&5*Y+XlI;^Gb*81_8xv%6Z2uZsOk3u`mzf3Y0=`|Ak
z(vy3&RL{r}dpVOj5@SBq@X!gYy+mB;sp@_AF6M4CO@~XVugFDC2N5|NeA!BLp_ph@
znnkjsfUNWs=4l!>Tghd3xe40H^$~OVF!qVGQxPvH>u8wTz0CK>?h7VkYY3TX<6A-j
zh+*}WHMR04S2gyyLQ3QYZ6^0I{`oG8Hq9sntYb}4y8g7|-~u4|k!`_FOS<x^PC0DT
z7%%!j-bbIi9yXec&c2Cz2uKe-e!pz3<mh(qovW;RY}iU{XzYFI&D+0;T=mC7{j_57
zkBv1m6(YGN6>DU9+voWzXkIZ9>(WriKk-iKv~UYc^kq%jufzvQ(5r}97hcgob{Z6V
zebQbTNq@(UN?@Y&r!=kCLT+7p`w=Ox`h|%Y>A&-QhBBB!OkVWRPv2qD`)7<{&o8jj
zTju9^K^&#E_#PDL+V7OzZ<l>wRX6I2|2>4i&lopaVJUbsmSBgfm(A=J(g%gHe*mV;
z&UQc>&}2ZfNa)2tBIZK6Jb~0eA?<u|Q?|EeiVJ4@d{M2p>*@CV#n}=0g&c8HXpDWa
zouf!x4;V-j!g(&5jw$Itc9fnr&?NnGOk71v?@jXgk!%_Jfo&brT|_mo+@0c}4Z$5Z
zkVkNPGPho|zU^S0f1b5C-ZP_|cCO3hyj>euV8MJ@Ms(_CU1!@i(piJh3y~?t(!oR}
zWF~|0Nkw}lsW@g<j}V~Qj@FvD9gfoC?Yt0l_g&I2UQFt}4jCoa$>3CtW$l<+oR&G|
zps8_9ITuIsjVMRpLJRb8?wAr3r^}slvS^DA9nc2Td_<B%Jv2Aoh`?}uXd0Yez4gJ^
zn}OCq7$oKBUd$G3ggI?5Ds9c5>h|!hP@p%uRwQz5`gN+K!qsq2W&`%Ic;7-1%K|H{
zeF*I6kl)~zix3cqR??+#EN9;Y^oIp%D87h`@k~0l4Oak5`hYyyIP8uBTn#wuId30o
zYHY{2!N9?Tg(+uYDl0%b*k@^bmS`%S+i3I~Hn7(L5RMME<|9@nbYYt=Ft$z(4AccB
z0i{fc;iIL456Ohxs=^)^B>RajgmPWjp=OB`Z)HlfW+59VnM&P9H!4?pzb7)}UD8Lw
zQ=pS@D|j3dGIJXJwJFfe7>M5@tyNjD-MSqZA8glt`2(lo#{QjVMsc8@#t0PRViZF=
zn7lfDsgW;2ot{>>B_UXfbH#Y&_5PMU*)=l|&sa*~hL*PHv~Q-txDjgb&_7!W)2J1w
z?Je^(0OF&uuUclvUh;&Q|4t$Jv_cJoU4vs#0cE<P4c3?vtI5HV<~`0pg*MU{;-rf%
z=!eW*_<@Q<kwPZna(J7uAbPkbzhF^5Dw+#Dza3rp<v@mzzMhe>;e}!q=DU@bI=Qzq
zQBQ0JO`Gk7KOS;#H?59buJP=2WAruiqz`|8322;jYd`!bvYf{ylxKtn%RSd5dWBgl
zEmeeM`mGJUd;;!=ZQzo__;k2H&ctLpM5QFz$u9(FW=uYw?w!>L?i+7f6R!jzbUc^j
zp6KMgxzGPPp%g?sa!kHYAEEtft;4}|EST19c{ZvM@@4|&tDQlQD)-tp<wcWbQGXXd
zM&;P!fr=LTIdv8>3E*{)9KvKQnPX)+5VC8qz7&dIAT~o(3fHUUZ4gcJyA!}Qx*<{T
zJ+x?Qpv`(s!6K}0fO(KU3ho^kTyi!9)Ki@UG7~cWB%*-$6b|bvMcsV_a+4>==P4#5
z!#!@tQ|>Rtn|#UaSn2SUzhVG-mOud<gL%JCnU=HH%(#A*Lu?vax4Eol-`s`8U3R#q
zw49JaEt-?vDj%>N8(mZc3dB-tR!(8N0AnRmP^yo4RJfw}_HM4*zn}mq0O1Mr3;lqh
z7p5d;dv=nSX@w)ezF7VJohD|G9+9YCUS*h%L%*bN@og$iqZ)5y%d-2iiOMlvjb@j9
zP&i%=L8TT0suTFspl{1U(74IyaU7$a%xd{q;&q@;T~LUR_za=d`l4pgUlsdjK~<^%
zg*Dn5hm{>L(xjdhnq-Q+*{Sn;Wft@an6Xe)T;%Z!kEqzjb3=G2VUfe#)&x}_I2Ggp
z*U#i2(C}(EbxfiDyF&Kb^6YXg#|$RwT->^ng9T#E&8h68%S~QkklQj$1WUE3gq!*W
zy1105D&yZ@<c%odQt3OH-miz(X<5o4SLG858ylD3SlCnPxjih)T-tjjXj4SCxk2J)
zzD+V#RKG340sInISo6oV@&3{~^p*)!vAzZfL|CNHhsjkFtpN{bEZXtH0t1Zq9z16y
z>dl9&IB~`XdjD#th9V48lZ>*c5vPnJZ(9P2`z}iQyp^qelHCA`IT*0uM8!Ma8*c)+
zbM$BKB+`-{0Jz@$?jm(X1zLDE_)LoPy9`We<(HzHCzRcDo7u!N26j6X*A8%(ccb3&
zbJ&ve2o|)7xuG<gk63g87fHSb+grn7AKhID)Kz64=vv>PR)B8HEowmJ%9xKtx?EMq
z{)X`Oa-4yjk>tbjc0w^5LW$E33(f-vx6DoI>N=E>44DN9%EKfex0EdvC!>EkBW&bl
zf(=sPi77zcs6}bARx%iIoTNps_i&v=OS!h@B>4OA)N{||@^Nwlz?NFZs3g^?R{)?O
z9j<J3tI=5iD-c+L^3?}6&yeIrcSA%UXILTL!;?tgsU@iRnk*Z_dF@$`JyF}^hIs3t
z_K?B?ZVi%lYlqgH9uH*}jtftAvuY31PUDtHGu|{z?`}n9T^Zc)8qCa#gNHY2<q@*p
zUd!K9D1d|1T|b(~T<1x}(J2E!zTS}vBwv<L_;mIT8E?m(Xz6qnxH0!~ZZLBDuM*pp
ztBRm+QwCblQ=eM1bm9Hcg)A1THyzJn6eMq;&fvvX$PA8!_|~DJ)Cpv27tNhW89n=C
zM3+E^O;G??`otML5rHE>@0QWOIj&|^lflEen8AauKDRR=MXq<Iw$RZ}3NuTY#ZZlt
z6D-#zu%Xoih5OOwpW>w%;$qS1+t|9#yu7cb*Y7x{hteVgVKh*zeeMU(V>%-_AYr<w
zHcyUM77@ss*--L&40(vs;}qA0%DtcJ?}Emd3Po`xzy_+P{&NQJleB*1{Zl$k)Sr<T
z1q(bZ#+q-*d?1lfWKOsTmr1wvPPAL*rlGMC!gHc6vV|gz+!PXKYR3yWS@!12I&MHA
z5{6ukxbn*5EWj3n@ofG~VJ8fNkcnF6EU0OUmF%pFc<su9Y{~J0t_qde`~HYL>2c#R
zzulIbwS@c)l4KMo-0qgk6}|C)f}~AYNQ3Sbup7_p#H{=I`!FU<nHsAKBR|qt4TlFa
z>9RqGKYwJb^|+Xa&W1yBJfi4Y?8AcHU1nmok~@;A-g?9}Zb+6kk}SSYahZ09CCd0V
zNgr0pBEt%WvZ2MC%17|hgX3ahq7mW73Um@;*!?3=&d6hR<bb<qP0h#77R#d*O=5Vt
z?(mkh9eno@#KM7tI|<qsOV;#Eop$RLc>Y|y<LFrm=nc(<O}zw6iM_x8?I4>t+b)|c
zr|^%r;<^jMwO&8!<pi{?YK~l81Q2jS;QGaQ+hU%9WD=XI-iz?^-c*kqBU5FrO$-db
zMJ!kBYdS!N!wf|ZrJLuZX1|$4R(ZkB=PC3NHFf;+qa?0K@})448jxJYsy5j&VygtN
z`(ZK9&pqD{Z!J-`vfPO~uE!<Aa6K6G%;-iKE&8sUd+1n~$Gr-eUPHz*2|-+ar8&AS
zDn`=$3*QtXR(r1zRkIW6JvojXU2b}}kTQ1ss1>$0iuYHZqDQ|J7RA`Sf~Omr;x6DY
zNgeY)8NqNqO8u(LOHu9HRd*Jwt<U+xN5Lks9~mL^iO2aJ?lJKG@ose8=$RiL>82pn
zaCC0u?~CPxm$b7l1t$ooIx<$p#=C1ejvB~~!1nh${OS8ZA4T0xEBY2wIV87sw&T18
zDTm^MTEZT6IFAv`dsg9bby*OaBP<!4a_%PX%*M<zwzulvK;lSc5zT9XB}o|w^pIbw
z4lZ@(w^Wu-#J(u;(w)C^zTw%hx1Y=CuE}#r(X5B~?7QOktVN5uDY#`MQ1i;%C0j3U
zrHIG1wV>X-UlnIgPXUhIE0J9zp7;W>z4CTZ*a~zw{}}qpau8;{KKU1_H%!^B#Pjv;
z9)AGus4pj|2V#AbB4~(g4EXMCj~om{2u^w8P3p`~7>osn@vOpBM`UY2f4zDnL#N&1
z3k9fek9OD_ho=k$yVHqz1Jf!sJ-y%V1()1y=O~46<M_LeYo_b=k>rLTDS3km(mD{)
zH!-qceEeP>MjOG2Kg2uY>bXnq$ja74mz~L!K`Va$P8b_9by(R0J?j}F@K$owc=G=H
zS>Us2pNWzOT)|@%nQM5n`Nk`pfMjDSU|PV*FY#L*CV~+P7BT@Y3mfiyA94GWNxyJ(
zn545(=2`;M;Rai0+);pRUA;cJMVI1%ynPt*VtKcv!8Qv^ZOtf~9FvQsdQlX9#2u<w
zMoqmN3C)!xEn_Ae7@s);nHFa{PjZfEhg~gb=_|U3UM$~nfcv0G&QLG3<ay5t0B4&D
zPDVm~E{IL{OGr3qyg(eSY7EqRAAaA*-g$dvT3C}{$*?9Yxj0Yy;vmmfk@5XDxJe(c
zxWv?kp>FOpv2IQmn47s<lNi*(8X=Oh6}dox_LseMy!4kH#WrQWsCFu~k?$at1Z)hp
z+`Ko5WYX?ip@h$n8{pSp$i4|r@O7%RDHhC!;Xs{M^rb@jbGxq6@zDLBO0-1@1X4=^
zJ|SzIhEmcp>&xKu9raaaU7-ekZm_WF+wE_om`?%f)-F!O2k*uH;g@j_{WCLta^Mb$
z?3$LNgXmsiL{JXaIxw`EoRT2=@)V)mPU5O%?I8V4Vm1(t=(}5m)=Q`}BhHBP!$lwm
z3iIiFy1m~N#5DAVTiW6^L4MTriYzy{E9dk!#fNZnzEC@i^~IT!a3M*3lVvBv2T@s`
zd{U)3@5BS}5OeiAaM6QF4Bx0!O1qm4)0NU_-r6BID~{729)9#9UczB$y3fbCZ*F{B
zPs2eleFxk$+ylxgvfYzUan#|3Mo<z6>`eZeNle)D&6@5w!?&e{B^s=91-)B#8F<*;
zxaJ)FRDAgPY95C$Wywc%!f)B0bf2)@EEKW(ki-UatG`hUAIfY?Qxg!u8qAn_3xkz1
zBNSy@o{De*5Q|N$3(GdUK(7asXc?yklSI#3GSafEx?Y+5xJJX|?1tMm^T+5`E9~Hu
zYSunvdH0e24MGuUyaLuV6lxx5ffmr>#Z-iEy+MvZeAh~FdaNM=G~=-psC7j%$Jwvy
zJ3{-soC;cGQeJY|96*${s(3@;WLTrqWP}kh;+(dXWgwC%YiW#7TqEl{Ut_>;66GMO
zO1TXXk?Eo#(qcCh27cL?xt=#fYG$d}M1?;5;HTq$8fc*`=*%mioStRKkh-NGw_}eW
zxPXJ0g&3uRF6e(LyV&qjKkUfDglXZSqRuCaHI>cP<5>w>>%3$CQpR$UDvh^#bPjv+
zW826>mt>yyyV667FPvs!AvR>2){eR0t+7CP!iMA#`dCGPYgdBHN0JMiVs<ww{;WlV
zR(;`n8TrP2?|tDDn4#GwqPC8KN4*#+yRp@dsgwY-@@5bSRmThiipgZPm4Q~Zhs8t0
z1vJQJMri@lcBfEb?xtzAfx9jX+-JE%?nhv0In9W-0C+mVLs4@n4FxIG30T#&^c*RR
zYfwZeB~M!?&2P@tHw6u5xNJWv6(8MQcSUyH*^4@QdT+1f#?Z%MhhF5Xu@XHNbr;49
zrzU?&q+?}SeSg^{eKd^IN85){4{*w}-JpYxvR$|35Nf+EM;HOZzYf`MyB1j7lQtI0
zv&p)`d;12#=vc1;iH(trVApVcNy*7XVi|JL?pJzMej+u9#Gx=(xqojv(q<)@DJz~N
zw>fDu%bhtcEE-6ii~Qxrqna6W|M0rTE5t1%PcI88LmJuC@4C+U0GD^K#&C9l{iFfK
zNnejL&`U&S4W*x1Kjv0VxWeZR+1aP<{n+jOu=}4dhWPB`1RV_kfd9jP4QMz1Kd1oN
ze++0lIU87+nA=$!n>hYwpxp8Q5CbGHqZY~PQVE-^@Y|orRT{!r)7bc2so9bq`x8k{
zK;hOFd;feKa7;DIvhh&HXjZvcb&j=NV12RVkp*f@K>eb<H><T+UxzXZ-0XC|g=mG8
z4RVUDqRq;QFLIH>&v!=mcM;k~O-SG(aG%X+l134F?k$R`4G0%IuGfJN$Z#I1zRstY
zZm|6lGBZ3GyDYw*=P1)(lovNwB<r1YYDbb(Sai{{q?nu8I9>UI@l;d$Ov$>qI(GK4
z#|Pxib0*Fm_;_p&TJ~!0YJYAe)cR3StgnhvbRp@q4t9&pg((6q&NrCm$3{mo5>cKp
z8z_-I)MSP?PvNwnr{#N?MpQ*FgX`<<Z>9SDtT)u<#2^*R&2ik_1jiF)&7*lBXtMRC
zGL!}Nl(*YSOfpDqE`Df}=1T_>t1+6f47gf6u)I(t`9^=NWsFD)=!&lA)dW6Nu8@S7
zu4WZ6*um8A(DZ{$dl{7h4;R*;>t<>8k{1jB+hIaPDeuh=!rA&C6aQdd9<M46Tel{l
z);ZF{DoXsiuuLO0Sl2lWA3{k1tcZeqro{v-e}37=a5ADvuuu*aH(A}8g{DD<@wmyW
zm7pr}b%aVn2y*ZZ{G2xvTyi*CECyC+_woRLv63c60w@ZJHO0+1M57i6WW<Q7C6JOu
z9b=zc)HUAIem88lB9-!t5b!>s-nxIqQVQtzp{xlU(BPn4_4S58gPzLBxFXz>GXXs-
zQes#^MIrX(rJrp=>n^isCxf$(lY}=V98XJl4;*m#gX7d&!#Cqmr!wWFysZugnuicl
zmkQR(Ec;9zF-t}S)yFfjQF20lw4nQ&MM8|3ZBt*7c)5Xm@z01~8<L8pNAATf+(5@4
zG2w`bfY{aB96;_wtp6Yy>z)9Zg5i4>%Vl3~Y>PtpF}L^%Q|lFt&LF&R`j*$q>_~Tc
z5nMxsn#TFnJNk3QQ%X^`;H)MZup7e_)e?E{bjN0fCfFGzD<wQ^+dI}tB~Pboh<PyO
zvoTCRUk-#3uc%n-IMm^%qGMFL6B+<T0861ys*mR+P8?gu7HAI)&N^z}nAoww9H>gI
zifn!lS`NJb)BhEI99cRwIza}mWu)F%Q$T7<9dq+9!$#GSgTlK;XI*}qA<?ik<^KKQ
zGyCef#Y=QeTp0cPv_U>(Dr2mlJDLa)_3ClVdK>Cyds<*7l><$>kvc{siT6qII?RAU
zo!Ci@U(fftgar&BKH_5L$aWXUn=c@9?>$#~Q$-?0BqrBlE@m5HhgLg_Rb+H->}Hdj
z)z62kbO}}+H7xzcO-5f1qzQ|<Rd+_e%#oX6L>>bvI3NuHPBJ+p3j;CWJv}{qoB|Yk
zID}$?6hHK5-KUXTj7ccvAZ}J<yGqIV<^W8|t*pa>6?4N7m#9XZ*U73JteWC>%YePk
zLe2ga+8eK8yK9Y>mfoUC=Je&yYGTvG`t8^p&4X`nqI~!752XGAuOj`5W(s(Q#VPlf
zh3CGj@B9-gJqKmbak;03;d}G`4JKN|wgAfLwiNJ3LVif3Fv3uJ0usJXNAUd69WQUB
z;?j3!nBq^NG0pefi@X>$?;OaivrD<q63mu%XC^Tvwcgm93(B-DBq$dk%k60B>|M_R
z*RkrL6OQV@M4@y*zM6-jgG=GM@L_mYpz-+Dk&=t7&wjrQcI;NQhkfRb0sUS1GRK~=
zX2XZ+pAr&R#{AvR<(ceu7e@**a#yT2g}{~MCybM$DPMOgJ@Mxb_U>{sjGQQ;q(FuU
zWUIdGP7e`sZWlJ#TN#W{T*WW>uF@AI8t-QfRu8*yfNqILx8&@3a3X7x=W;cRo{>Gu
zTrc^Ih!djU1NAY!N~qS<LVf#m$%cCLkjh$Q+950px>_*M#NAy>uVjKkADyFHoNso=
zK+X~=u1g&Zs^D8kE+>2A&HP(3*g6I6H^irTscC6V%YRc+FR<7;au@s0bv5RXQZQ=O
z)Hwpf@QV+vtsA;O_9?gR56seecNd8Q>^yasfXW#f>e7f=?78>z3B)Jn%NXcmvrT`t
z56}0fbN{zY3fjfN0puSQM2PZV8;?`Ve`nPGv;XN|<8ijIv;EIaXX2mtiSZu}_&?Wc
zAE{X4afcI~UP5|s)UeFuz>a5trZAC4GiJ<d`9&rk;um^<_+*S^6k}syM%?im-7B~`
zkKaB)G+8MCxejV~BZJ@7jmhn4J%o4-4sF<`(wdnlXg4-Cw$@X#-|yMTgF>HOnNhRN
znp)eidhE*@oSf+AHD$bSoBMgJ_o6k`>$OxF7Ua(IwVq8@mHNs^rRd+j*5mrEmBYiZ
z{X&_W?7OX&+SoTd??<$|MuPVjA3a>Wv*)l;xI-auzb^0Z_tepR_mD%_%mS~kT~OYy
zxBXQmpJ2X;!}{6{)E!0cpIXDs=FN+x<?oWV+mfDPzL#z1ijS6yzn0XJ?hZ<WS0DN>
zBEN42n3pBE6I|GP%BfEvQN024vaxs@7XXEQ*f*EgLORcHYE0eR$fG@*GSBRLU2Zy?
zyuSXs`|68pgL+}GyN#XYTIk@a;g`N85iHVfPETR2usG7ymW_Onf3n^z0FMw8pn(yg
zPMwFwzdQvyaJkZOYxnL4TX6SI+d$Izy7G2a5qw-pdU|_${l4aiG$M`G?e^#UcNsLw
zrk*rBs_Y`PHxW$X2Gu^@Jjd@K=EBt{ucsr`KtSF=R_0bqFL>@G9n@gz*bm6pSoGru
z^C?SIVfJdP$>m58%GP+D`6F=k0yD+EHQ-bLkG}YRoj9MDGnT(k_P6<#5BYE=96)jy
zzVuq3)dy>35v=gn-Prhr^T_R%{h^_MV|?5|da$XEp2~~QyJ<!&Kj#i;d8u?&=tDU)
zhx3D1SKbCsL}Q?G;n?l_3Wn+DC$4%R0$AVnYX<ey?%Xu8_MBzE?(4Cryv>4&?1cyS
z&lL1iiSBef!10K53@Gl-eKa~_2@iBV`#Q?+##$;rExBqo5aTdltR+9?de1-f_G7-X
zRsgRC81s3Og+vN54y@hH2_Ss|z2;$9VznWn%`d~%aC@yNCmqDxff+a1^Vj+ZmAb26
zRXRy{{U2ScHgr7L@9Kpk=W|?T!pH!3Bg7oRdvPqkR_?EBDg~~-slqXGLssDdkASd4
zBH15K?J+wJ>n}&kkI^m{_fOVhRJaFGjCh=T`<eWYO73-AOdf6b4lUm8HsKowdIrS$
z%t)-svp|yGV)0;AdTW;~R**oz(k=0iVLcvuN>*Wq-`?mp!I5oTc2|ugqMF0LgZz#_
z`t*RQ+f6O9<NP5Q2LLfi)23{mU(}yjYzq?gayM*PzzYXLzRS)w{=sW*E}eR>Bm7z2
zhC3d3cQdr;e`5Bcu`Gn-2F2^_zHQe)_-q3lZUr#+&~29Ijw9vr(gJNxItwr4o?8y+
z^mFR6S$xIJd;lnAcouu}CyTH;ZC1xtUwz)+xYqn5=ro<I-`Cmnx{Ahk_Wy`7hl6mu
z*dyL=I<DeG^AF*H4uq`Q)iSI9PFzd=IcjJVqD1bCgu~Zs6~7it%LzTd@rB4;d8H`0
z<*xAH^4Dv|Kb$<T7L(%@>dl!DmCYoL!>+3d$ZQUV2*L#%Xs~`I#(n<`ch2L6LCV%g
z72NUNZ;h0vI!DIUq$1u&?nyZPD|h`kyo$2Lz%zMwfC8a_>eFe<wO@MIR%paOi22&m
zGU>3@NFl2O%qNCZd~w_P<IlW)6kgh{cpFTFPZ^JUFRr4bO-Jnxn4I%1B2LyOMOidx
z8+n8sFFMJ$p(cVl2tghr9)d&Fu7AfHhGll}7cMDaWD%crjA5+XWHZI<1A(W|*6JXp
zBb!$9_|ZPu6@pyX3ZD+%=>U|{hbxPiR)&4h+YuO3E}GCvD_zNNRc2F^73^lQhf2a2
z;+?r$m6pWs{cjut<n0ZZFQ{2uyB5q4X2v0H4wQL6R~+VDW=W_Ogf4ve;+|@pk!JwF
zBAeUE#J#$v+_DUvgALnpIQW(7Ujety?xlfyv6~cQ5eQ$c{aB?7{)g^<oYU*T&JukB
z&A56>lcfi&Z^8EBEP>PM$Tb;ifl*yml}r0Vsdgx(4JAj2dzpV}=tdx7<SO$rG1e@W
z@2(JJ{I!>=!-mM3bA+wedzL87#+5|2b(2U}*hJ-oC50%_;YRk7>NaAL8FuZR1dW>Z
zev`sZ;BeIWbPWu2Ln3Gy7e)z%h(x9ElWZpA03Tex%*DTnmvdrQNS`^y5<${6220Cg
z`X`~!;m?Z}0G&qYk+T7~TJnIp41c>fk?klqzTMa{ZvA}~$BQBoy!G-x?`{37dF!_2
zP{E^B;I6>t%wSB!nGQS%m{<h3^wIZ}$q01wT|Ags=K)?>zrTrE?Dt=2TOl^av;?zL
zxjDRhi=yq~frs|~jY@+X8Wmvoqu;%|HgG=lB{USt$qb!6RbPSmQPj(_?j6u^WoI={
z89PocmDLol>uGlZ;Yzl*8nnY~s}RsK?;HfYwdGFiTd>aJrs4$^!Kp%@g9<py16J{_
ze2DyOi4H|(Z_kFe#s%z`dq>(?nixpcBv!z`ofJ)Z3DgJPls8Ui`|a_Hs&&&>KwubD
z(ooll56F+G!fz|jz~}QgUGfIq9jxaQ|BA^yuZM5-2y=w|Hyzl{rG35F7#woAud?JS
z8|N?O<C%w9UrY5zP<`>o=<Q3i(dL+>BP`nCziVI`F$pI7N4MkrH?&$PbtGix8=vn#
z!9lR5fgWPkU2cBsMK@t00e&JBsjiI=Tk!!_)+;V+uV`^NvkAP0HTF3c0`Uv8EBOuB
zv9=INS*00ljr3dBXLnOi1Xh<XEQI9zSt4tf1ju7O_FP%JfD*PaS(a^28o1-K3zB7|
z`)Hh1+{!rHceLN1yI<?eIieTwx=Bbm5qEN++rzDT_y*yy9};hWtS4P;K-12G#67#E
z%GuwqWwK0tz9Uta%r<hulM+nM_N|?M;3LqGApc+!1=$kUpR8GEX0K!~<bc<#iV`kd
zk6Q`nw#lN2Y*{L+GxfNV)zq*^uq|Y_XB>5n!@)y0X6U&&PTz2nwa>q7nB1uer^ii|
zV#Swmd7cS5*4I~f{fu)Z#=PU*1nh^sds<>q`&%S3dfY!=NamGeU{{M{?0>l*6_zx3
z#>w@E8}8Tv5n9?8XD`LQt{?XcXc!ZNRfIDinr*Z-WggJws#Rv@>0guGe?Zm~a57Ag
zd||IFzfg@=&8C*jhS8kyvV!lqC;E2rp}`6P25b`-2er|}#l=XFk$OG>X7boQPQ%?}
zSp50o8f#a@M}?fx*s+T4&EekaGorw=NTb9$Ft=~^eiiJKY`))g^fXk1W*Zk*1P}kg
zNdtCoiaifLj2c0b@sw=hs`_!aH~AYskUw0At9u3keDb!i*hz&nFycl@Jlx6?mz5e)
z9CJf;tj@9+qHT5ifHfLqsJfNIKY!8yJn$eGKQH--=eUAFEi?R~R6BfVZZA{ZxSVbB
zYIEOPhQj}Wf>@Ubm19<5R9o?b<y*FRy+VZOXn*)7Z;g0TvsChsIKVHsX=a+<sZyX1
zCKBlpYM_KT<`*bopU#u>VW>rIP7L9P>CW3?%?UntQeu0t-jhdcrh2$I^bP)fGm9RH
zBV)R^AI^p?==9Nt`c#7US<5c*@yhewPKN@8Cw&Q!u&afpdC>^Rz7!umg4|8KjO5#8
za(xWkuU50cAX^%}tf(_>=?Fe^pqF64BfTIG^2%y9l(w;s6PSoO<8GYa(~MlKOY%ue
zCUI#e$5qZWd7N!{TzRTaQQIz2n^JqYJOU4<m2)lO5k|f<;X~F_gU6wfz#r@e^qDND
zBmXi20<y;QLMs6uivBPe){O4P?wi=OiGYhl!)-i*^%Z|?(-$fjtF@Qu1I$+Ho9RVk
zbL;nh>wC`tTSl$;_Lax00(Pytf?pm2_QUm7L}`)D>15R4DHga6?iAdPEiK(3ToZ$|
zZw74H2-T<Sym{Z@OmFErDoVy6{xy;-pL<nl?xbq%jTD3?t(a#%*i@_-*myrD`Yo{*
znJ4Vm+LaOL^Fu2my6cP(oTLJW8tx~H#oG%$z<?g#@BHUTc{NkdWycyTJ1Aqk_Fgi^
zY^c9>rao$MH~EH4pcC0J02S<k0g}7>`ZCXdmS3(*<RNiYQN`***i+y88K~j@NrBG!
z3g@TTBZB@wn^s2K{^s$V9TTcTF>6!Z1ni!s30vRu1vSDDo&^e6I7L5QE7*<+s}25J
znGsB~o=@;Yk=Ys4NfPS?=gbZn0W1#|ioc_>7wt@5sw83RU>YPYR6^W2x@&-lP5aeT
zHExv89>nq9lS^&^tcF>Hl>A)tpmgiplfCWrb_CMUYh6_q@QKSL#w})q4x@$dNX+yT
zllXbYgH9vRLpCY`r|Ca*RDG#NXp{D56~1y0M{4DN@O4f>qQzjkZ5yX;+qP}nw%w;~
z+qP}nwr$()Idki3rf%Il<SDiDlE1Pm`LY&2?~vJ&=W!G9>|`V1bW#dAu&$bckIvo?
zGle?h-hErL#_fHlx1BYUq&hHY*^QEca3y9Qz*+Xg+?@64_=O0^*3UYT$(Ay+rS0WO
z=vW#@x51<5?%<4MSopVk_i8jQRVN_NU6Y)hkb&MyZ^ek#lKm@up=5&>BvSCPqTi2S
zJ;t8`^7*D2Z|Ysxs|d4#nO@F61_|d&k(;P;Kp0)FZPCdV2~B`2m}JTmidsEp^SlD1
z*t+hoN5(-?Jpv{8yg1qyMYDShXhBRdB<iN$F~SlW`j53A>Mn$@pk+|c<h!^A|Cn}}
zcd#Pd=U5W>&GB-L9&pZA@|?>GB}Aih-AXeV{fPI~8Q`e_^obk(pdHgtB<Wx`3+&;K
z3)XF9S$%N(8kjl*QN7hsdx|j$e$*+1Wgm2rq;1ER<H<F{mlTyV2xNamdV&QLMvb~n
zOcx1Hi*?+6fI6S{)9{FqIrSRJbc*0^$MRZ)v+8(%H!y4vQ~d5=$Bq+DrUciF!!k6$
zo7xiTZ?1c&ut<V>l*diZW&$VumE!o3yPL=c`OtK3*cyd$D)olbA=Vw56ST)|ZgEHC
zVRhxQG67J1dg-+0O-{?1EA_59d#n|P4axGldzuz&ap}`*D1V&#SsUIlPDT<RL%)un
z4J<2yRcaI?9u}s$S8*{_fA~#v?U{uAi?`eM$5V#flgp~gSoMR%k>4Lu>p-+IxdOJi
z%`7;n+FMA*zW<^?8KctN_i?h9k$s~w^Nzn5A(g28&?2d_jv7kHtJqBfr&neL`Uy1`
zN#2x({F6e`svqps;aD~&f5FWtk`^OmJ3yH3@|a!H;L_lin4IdAs@i#nu=7pMRx3p8
zW#)c?ybYJceN}C$L>HO;9FfgNu(>!~+#Ttg4uw~VPjOU&(=xTGWeNC;J+O3_mVL>I
zzdZ`{m3N(l@!yLs^!N_UTnyIliwp>t)ex|u<$9C>s1l{?w|a@JXgVZz4sJs_Lk0|e
zMQwFCt7p_~%NdvK>Z==BS>Z-)rK(h;yUSKfQP`DZf!@e^X4iqThPeeY7ucd(CU0Iv
zShcuF%9570tEN7VwMb@LP0++S-!LXk#tsF#ej;#TDY(a9pqdX?1q*xFdF_)*Gzr>B
zLG$tHCM#{A24{XT63rD9=M?+a=dF2Is8a~hOQdC4j#yhgs^A<_ChDDFe{?4t207j>
zetJ%6Br<84!nL6D0ICIe1sysFcMB@m5`CF2dB~>A1H!c+Uw3R}0CB2p!s+BK@4pOz
z5~%)s2{Hn4U}WM6$x&#=x{GmzLexJlq3$T@zr%@by#?P76tR0fdloE?%iwom%4Tav
zu|;@?X%$#7BQ?nP*0S;kDXl(63vh!>jAe85qnLCx+qg+e6qv7EdKu;vLN7XN9`RNd
zZ9h7x=MG9RrKi^_j#nuX&L9_OI%w|c9^hs<I};UWPW)bzjKq-c5hEmL2fdrJW<b-Y
zk1QurbO{C?wy9-EY4maQ3yl9;<y%yE#nt@{VtlSmpgmx<11=J92_>`<ZS5laF6`u1
z$zl|&kF#hvY9)pVN}CGYqLzSCOE86Af~>B!MJM!8A%)U}{F3ouBk9WklUKG9MZHL{
zS2&*|7X-ZTUXCzguR1yTf%LNc`3737=vY9BA3bz7IaNr$xt_UbqVK#UN4xa(`n^=(
z6ObW??Y4DA^&h(RNSD<=wdzNT$csTGL+MmGXFUnhn2^zf{nvZvid#RTY87=|EkzlF
z4ekIJDgx09k`c!u`3!>9+Yx*P9SB18`X=7sV8deu`&=<rw+ej3`M_fDJv$x4_7w)<
z7TS*Wq-YF<(Im2-0~E9+;kl`!kZ~?4V)Dp{`QD6~<DFSx$#sUy(aAx4OvZ7}Z;guz
zy{vOEz2D}W&WkrGN=Lol<V}g=dw&Lff-T+4#;U8yIpoBKAqQcPM;<zXt<;@5m#Bxd
zah15rIZno^Mb1v|!<7?H^5*1~P_`r${+Nhw)+q(>Yjfw~I2>w?Qpo6`u#I|R|0ybe
zF%eSGNt%$+@laUwP5bZ&<;}t0g&I1-^5kqjgncxco8I-9@ohq8_Yr?xkHDaYnq^O*
zoPfPpsM#s=k5{3Vn>93Y!K3~TzOB#|Zg{y-SZdFVej!1tqh^OK=Z<}w@}kSVX_(Gf
zjT5hdv3k)&bG6c44;s%P?R`oOX*c&OhpIp4YMYn{zLnPO!`!Hyr~U39#9(3wnWqhT
z^aOqvZ;JnmwQnUirfHTB0u|j!pOVjOv)mO8crDCpr1u87p^^lf*%OwK^ki+xn!L=Q
zb+V2k6x49<v@59Vl5{Q#Mw-m+<0_~X>}1@$AiooQ#7N!3aFvIYR@n7(XBaQYs)=jf
zTIyICZ=lWL2cdYo-FoI(#Pq$R*&80%WjG`pEqPnc>MR3aVs3qRlB~&k-<HU}vcSO0
zG+q&Lu;y$^NjE{<%dxC8NSnt(JT<AnI3%Ye<c}c<B9zlaP;Kw<R*cmluR@Gw8K1wP
zo-L-XO33AG?@oFIWWXjXuc!#c5iC8>z0AX-&=fL71?yPLO3}d!M|>UzLhCXVH(4rP
zAgtd!6eVJuQz@24pgNpK#pC}w%vm5nDc`}gsV?Byh0JB1><(%nghAPeW$tMf6TWZl
zP+p5pfn02s<wHX>zviP)(ACT_eYSU@^Fg_heH&BQ#{{5~@u5$d=NhzQuNKR(k3h$n
zM}&sDv%v^JCjL7QW!J2M%)Bq<{!po?16qzP)Iz8-U_ePmipd*S5&J9s5A?#Wd8wpz
zX!I~CE|R~==kQVhxutw9k292)5v?EwJ*5nq#e{;O2b?9fu)lU)J*6mH+4w#KavMy7
z4rMjD;ay5{*&}l=-~%temO^ZOfXu(U?WAXW8PdzJeuy=L+~h!>0>b#qImI7so{3Ve
zd~}=aH>@GlV>`NG7@ELWvByXo+9Q+{GH&eY>Ers^B0`YKdPL}PXdk<KEquIDU+spd
z4S|C1xDr{cHFj<NDq7VntV^S-M}pz{&7gr!dHAbM0iJ-Hu|_tL3ZxmPD);xxZ~V^Y
ze9dpr+%&eHaCmH=CyW2_qT&|mgtE(H^|>{)0mZjHu_m`1&q^OHsqTX6nhbBN#~@~?
zj#(97lFtZU-zC;<dSw`)d;TwoN4J5KFH}6iNy8-Ca=v@S-(;jxek}?KX!Qhk`{hd7
zEM(leGAB_Wmn4wD<%VO|qQM!ku2bq%=54jp^TGoOlE)54&Kjy_m8C6Xh-Qf-GgeN8
zk!dv%YbD4G29bZh+E19z`kHnTnPV=vFw3v9pjpJ5SP{V1QMY{5_LS$b`xA=Y(?vRI
z$n5q)BT7q&S0)DD7}%7#dKxOnU25}`A}OO|6$vIo`{g4r$Mv3;p828mik)@QE4_0w
zHhf8-z5>5%cKAa>zavp(!<@dB+(gNU`UdikTlhFAQ}Egam*_7^?E@U3HOancl73kL
zT`fKwFC(Z(ZwMG8q=kI6F%=c*M*dXkVpYotV@0iJn&Umo3EtsNTI=*R?(`qc)T4{N
z5t!xno2GKn@z^@fY^6igGFGYv?H8xy^hHrPAiYKRBMj(4UAT+8E&U$-X2OFi%ctKW
z4qEx~2Bc;rWc4P*)T}YH$6emaV3Kpk=jTwQ7-wb2zK@P&vL3CJiy3m`jZH5rH-l1c
zig$(;_HSaIe$W`l!L}{?pBde`_~wcT)m2UBcb1|e<+F*F2yQ?T|7UxzzC3P9Fyz7n
zZ&7E0DZ^EfW)*v_&NqEgM4EW9FvGaSf%FEg@kP|HGL+FO?I~=ZElaM0dm*K4>HZ3t
z64nSZ@a^C|#!BFQJ@Gf^PyUluRa?_AKB_BhSt*46-nz8Nc`ZRC@6ecnuEQpdN@g2d
zD@utGCVA2s^y9zE5?svf-c-^GV*PXDW_sdU;+cZsIvQ*idx9)5DR>Soj52LXx|mn7
z{`32=96<{O45H`KioL=*Mrc7DmJ(#*f5ls#uU$)*Sb`J=6cGZQhtumJ?3Gsn8xxf1
zG>G0~`naQsUp(X$N;Wo<VmAP<(fCT*y{Rd>p&yk5q+e{*_l3Z5n4A-W#E-a<M7Y&7
z^CCnVg!l6N4kwB3(nT~|-c{f@V`(w$d_-5YY5p9D&qxuxW|HV--YJJuBRdb`6k3mu
z<l$@s46bkW2n*6HIJ)SJMbv@HZBZ-Outrv}e;N>Q?~5Bk`bUIFkXRn0k!F(&VY-4?
z00pQE2XjnJWyYMBPb=cHh^rE^?0hVHb`!Z!NDaBRk8Yv->H!d4?g@v8lEgSzl@ueD
z=zXwzWtlR?sk|$)_k-VygQ5<!)*|Y4KxB&Nxt2?=ndiu&vJX_aXejP;FOm}1?jEN9
z1y+=z0VfdW-a@j>l~9k<7E=m6Wrp-b(vwjPUXsa@8yII$jLcQY1`h#fnlCD&sG`g^
z?BqXJ$!Yk5yuf&vE}+qw<uV6g(ccncPBM%*L!zab7mO?w-tzpJIqL&An!enc^~k`T
z4|WPO4`1yoRo2&qeW0J~B>!1a-Up)Td_wdAX3^g&GIMB)ClOgQByJ{E>uo6-uW{}@
znepb$wA?w7U(N)eOWuj3Bt6P9%?$(lMUY4^B_1MjWVjB#$`){}yr{olX424tx<obX
zT!!4}(m{2smC$Dx*|JT};~_s?b`%HX^jzIb2u*t(K?Rg76pYExDA)B0b01_!_nDJ4
zbNt<oPrp~vPP=pSl044VSXZi*XFyGQkU+nLHYcC6TO{s75I&fo&s7}9F-@T5{bPpX
z0GMvFr0PF{Dboi9AjZ0UJwykBk9W5Zq15o*7E<l(8sX?rHgMju^@`FfN#Ue5$L@+v
zeK6{5?-#(Vu$l>@gE%;45}9;AcF>$4nNj4+$dGAiqC_zG!t_2FPEv%@Gj#NOL<ANl
zNOKPQcjJ_2@RGuAF-t`gHzK^Df0bY^{GEhb@AfdG*d0xE1RoLlvu6+<Qc)M%%N@!|
z%atQ{Sg1WsZ=r);#4t<)@crBIP%vn~YT8JDDanhu&r-ErpeyK3JYedJi^61yT>rz(
zN>ry%^kVZ!87r&Hlci(ThK3sK8DZ46VQ0FmYAApn-l^v4slyQC<1Z5Xv#W{+tb}DI
zCBHwA;~g=p9V;CH%Qxz^AgL}la6x)ffIa^qSTwFqpZ-K5j-Z3N>Db?4$@PrRwT|Q}
z!pkc8CkD8dO-R&s1M!l0`-hAJ2*r*qH&3NyWD2T`zf}bXdLn2T6CQtbq_<-%FWGn>
z9oL}Xm+kdBB!h!bNEzl&qK$puk1GayO_zec63M0Tv;`@`pk~!(Zv?FbJ;4WOXS9a{
z&cO;pXV3y`r^RBB(M#4cMZvWnu7bH%AqCh}@xRQ6Br>whpV8CXZ$X|mu-uTMG^72A
zIqC=p+OO=jA*l>g0LI}G#YCdgwe@)9kYxdbliC*fYuGLEd)kC-yqu+_p`*jaopEr!
z6B0_Z(C^&Q5Qvd(3;|bLiWjCuf-KrcrKTYn#MU+TQPQNNphmsfc>qm!NO|T80t=78
zaYM>!$S4y#0=6C;Cu8pK_xR!Q{>a9C`fxnMw5Md;ZdD5HKfld_EXq&cstko#vCq0e
zV($f1AUL&du8_3ElJY4mURML&XI|9E5(?p)3PU5J6K#V1!~f!v|CL;n|AUbhvycY5
z!HoPo^uX^={>c>u!lY|DmrsVi0l~g((Flb_z^Xbc#xLm~NC_#(dlM9&p<NT%o;s%e
z_mQz3)d{I_pl>>2-tDh0+FI47J{IGWBSjJ_B&i0*$n$ZX=}0JB0=sbJ3(YYl&4i+}
z4vwP?$3;STX9?2<_G}e-1qx*dWDmuP?yP?%^KbfwJam7W*nq^my@{^f+S$d{W4pZh
zWxWp@W~eM;m7D^Ul`={(;hk=cQSlFJdCDW?xlh^VwtPAN2%5N)B_@!ltzIQJy^WtD
z%lMK#_(JQFOVk@V#mO|ffh64*?xz6*Oaj|UYubvFr{3$}+qKwaGVw}fx-pbiQeK{~
zDS3Q^VbJ3s$!3{gQTBcQLd(gQah<Va*~Lp%TTl<8MiPf*M|HijwuL`Z+98~AYLXN#
zTymS7A-19-A4Em6(r2@c#gJsO(83Z(Zn9<HsC^L}Vtk9AYo<Jc)F_rZ5tB%9e~Y<b
zdsADwHj*4TEDjJmFr;MoRxQlgcg%vU(H&0*(tcP<)>8+_aJ9t=$#(@y-Z4Odpyqxz
z3OkBpxZ0_z@%ep$EVJZk1jRgRVH@>~DfY6mv)c6dOAqjef<TS?q56Grv|GcKl_ioG
z2VDLrZ5aRCwhq=N2wlw7Q7G(CrZ*o^VEaqEtD;72<srMYe8Plt{6IS63IJ}*obPgF
zG=e^L#Pd+p@IKiNp=-HF7#$l%ZJT+Iq%h?Jbur3pxliZQi`~q2VU}@l^`>lfBF3=1
z=9m@2hh6t!t`z5(-E@1I%Am2lJnUP1D;$&<qe@f+uI*EnyUqw>wNAku<_+YQYwCS8
zpcdJ6T8Jm+bn{*|0^P;bCm?Jr;i-74wL8%ty<{>I*M9r(Fm{&D23R5NF;bpwdbu#7
z`Ii2M=<#j8ib}gR@gw#xDD*+A_vgn#uOQx@K19Fs_>I~<j3}kBMW=#DMlM}*l1pLF
z&}ghqmjP7;w3$omG60t6AlT?Qt{?|4bam4ykz{5SY5fZ4+`Xc^XctVE!8h|CB*JY;
z8=K`;MfIBb8CD<B?rVSgQ|+lUr`=s#>#v(Q+RmWV@L42LaJkVzI=U1~#3ff9rEryN
ze(nA1<gt21NvU5k0St(_5hky&hm2%jYxbF$Y0ymSiM?s0waRyhKZ8b+S2YgojZPZ$
zH>s^An?=)Z5fYyAxu&BSlv2Q>Ao9jk37AU#X>d6d^Qj)4qd~-ym})bA>fv{qcnA2c
z!PD*io9=Se;#%VrGVLG<LNmqp#LDUBsH}^EX8aZ9Z{>`MGg8=t9|(aa@yqZDRAa_`
z6&&suaqDTamI;~0Dcv=`uV&ro1wCLAX8O7>=}oJ{lBHOieMIDY@E62`f2VgU#;-Zm
z{=$tnD#)(JF+%E93e`)V#O7$lpQ74TeHQgthluYrzS+nVZNZ&(>V)UT5kCYpvJ9%5
zg+;Fy<+4cosKMz*&<mu@`*{78E>Y4zyEmor9Qn*fraar}x#eG>J4#K&>*}a2(bP;M
zp3V4G7L<~OYt;%wOLTWB(B=RgVc2aVt()e~oyXLymf_1)gjP=tmHlv_F3hQ`amqJi
z#w$i`Sef5U3RGrJ_MU&{QtBg^8D!7I1s(<00S*3UJW65g>3pz>#z?bby}Z(PwyQ=E
zjZW`?c0CQ$IhERh@sNr6Vl}($5~@o#Ls3$hm1fj9dV&t~4N;%D+u(Fyq{?O*ru<=d
z0&=(Y=_LRD9YHpPN8Raj{OqgV3l}4o6HMcAncbG@^k%`tgT=6Y1oEVOBZEYGZFx%o
zM;y$zm3yN~FL2NuZtygK^G8-Qavvb#qPZ+v=t_%!a3rRtHfRGm9HoP#?8C6OZF@ZH
z)EzTRZIxY`6*XOJ7c5_06KvVWq>#Wt0=qnQ4s7Wgy5oZ^%cXegWOB2=K~&dVC8@^#
zt_geuvM}(S?Lxb=Iq3FU$o|9hc^qfjC5Xc_w`nLW#WjQd4pZZ9Z<nqdaWf;p%^Uvq
zq3fRA4%RR_fk7ydP?G!+45?%9KQ(3lY;s_CfO(!ae@-$Ei-ofTw{SM6_`a?u?g*H*
zz{9mbpJf>75=E8cZ~_@4@y5?#FpF{99;Np3IiA-(_!nOs_2~|<)@c$4x@mAA`sH92
z%kk62EnVD!xoU??w*sw!|K4iByKXbqVh}7KThQ3i=Z+|}ek>iX<ge;*>*rx;XvHzE
z^wpnC^{Uiw^_${t3Tddw1L>RTmPA7uZWEeceGa3)rrxtE@eiIcY|YE%%m~TsD5Idx
z?F)Gu1$c@RLwLU?pYpJ*sIrc(@_r~C9NYZWcvjNJe?-9Y$pyNSJk3%=MCM5OgkBTO
zUi%O2xDt)2WY*^B$&@hIhePu?G9~F0y{po&ThFh2mGlcTu&La0$Cpe{Dr&2o?9p9B
z9G8jMWwdw7am`=Z2I!IjZ4In(EN$?YkB$%^J3-K|9OH=Km!{X{jYv)OT)JLO{5kPs
zq~3eHJ&S^jonxoeK8kc@x85;_qTb4cx)K@rMNh&KmU<0IvtTu{IPRdYt6wW^UwG^}
z=2L5Ew718aMk5x%*K&T5t1{zfY{(nl?#X_y4?(~Ks`}1%HqeW2*oT~BDsluzn;%kP
ziz{|WIH*bLM1Yspvw8ea0nJG*EfedHx84hG$y1w5d<ng8_d8LRwLUzqkq!O7pww}R
zlt#ff0gm`x@h=G#pmVctol+PrgpX-T4ZYj-7qps&J=dsi(*_ZA+b2$eY+fUrNOvVZ
z^(~O5X}N-FCBi$j-<inc4I2cNH~)f7`I8BU=XULV;$JrrYgbe*Z$|`nXZh!^#c?aT
z2CS~Dq%%r#2=I*R*PnywNv{!20&NzMTI#rBwClMGR$*4}Zf>-4VK*Yym+XuAMER6m
z&^+X_3-WLF)ipb)7=8A;Qtd`7r~Vy`+r;Cd%k=0@Wd5oAy?@S(MXKC<*Uxa|ReVcf
zfWgxFqp%pZq!l>GM+`$V9lJoh?vbj4!02YPRU+cZPH8jAhD*FiyB#nnH!#`5kwPr7
zEH=w%`-<yE{%S0|mD(`=$wuL2>>p*$@Pr8brVxF@q;!;N7N8!~m82_nk4k~)^L?Ia
z#|^6zFb65D>eQX~BAJn2)`{q{iO}+}csAa5QGR=V!P0fNS~ppnKiHYVEF6asi>KKR
z`9rMsoLcF2!qj!p^Kl^OgyD-)*y@mbVUAIiqVN=nM76_0n=<uI;9TpF?bid?wF;9^
zvB~Gtn(7=3>}oaoDs>T3Cfp?6PGmb_p%yF2q}krpyVCiT14hb~K%K?+rDXsZN+H+%
zHh4Qf<2U=RbEBl^gI+F$%=CF?P08p-f4DG;uf=iPdrzV{K7Ae(AqtP|;eN#DvMBF<
zemMSfAu12LjfA3`s!dJv4*pyU*bo=8bKfcQo*|6Fx-F$x(Es5-$9K=^hiGgr1*Wdp
zr)9MxR`8Swu|QL=s72lKFirQBe#6{Tb_rmDU)@%|Gv$et(U1p@B($}ZC&}$&|B|q+
z-exQg^AAfY*`_EgvL&%(@LePD(#&yA8pqHYdXEy~?2AZ@`PkmjV`pl=raF5)43E;u
z*h}1z$_T6FT_#c+Zq^W<&Cs0HY<){Z7n%_?Z@-TEwT$U7nmys#flE#F@Z(H^J<aFb
z?j8fbIker$yZ#$ytGkl$O_k0!*=J2B8!&T%)l6@Ltm1>Ek3dW@kJ9xFT3YJ6CZlzT
za_Y))5Zh%{RO_h~HcD$Dey7#A(KFr<&e@tlsJv8;m|W`2o$fi;KFC|XP=Q)r6Jfxq
z=;~(FpGw)hf<i2CfXYDH(I8KgRRzhqn4bF7Z}j_CYjm8zjIE(m!kkhB56@Yx(l(D|
z1BNh8CqiN-zx=X{3$eSY?^-j&%dqqqcF&e`awSz@w7Nt(L-@Uyi40vL>S2H?@-RRY
zA25Boma-YL?nX8M)sSErt-<kvqqeMy+7yJy!f5Vag04Piqd1hiyPJl$XfVwD{STS%
z!S^h?3h)9XTIC_d>nIzak;jSJsf_0j#l*|{P~)ec1K1*<E@LgQenY_u4kfpnZRqoD
z!DeH!fPe4b0>wH?g;kG1dI~2*{AqbGhFun%U}1A`ZLc9!P68*Nzg0yDr->W<_VhS^
z1V$+&_{9VXG0zc{a}~z$+5<v!wH@aeN3w5YKaUxsPydIz#E)!f_rRU8Yomr1t6H1Q
z3XW7<y12dHan*s)`%nJ$#Y)=2!g~_kNg*t6n&Uwt4e4FNy9}FO-5>q5$V@NWC^x%%
z@zU}XX>gl%II3NnuF-OSacPULrK;rwbF>_Uh4uOFwQ$}~T>j+gS_gJTrzngV)W^fw
z3RPD~xThwioN;tK8bFZb=R<~q*lvGNh1rzNiX1Qf-%WWe7L47L5h6NTH`!>3W%1dX
z+rREw${mO8xiE#mav7yXX=Bb|>Bc(RRrvr{rZ2uSweYzvNH&Utg;H_st>|bweB@ms
z9C(B*DpDTxlvY6#*q<AdZ+bVONjNdf8hk?;sre91OLqI}HC~_4iMPY``mDF=Qll*~
z?(_TXS&KFkIxff47X)ZW%xIwqVgoYURCwiF2v;^>{`JRi2;a3un{H*wu7Ur~f(q>m
z(hiqO5^~H=-?$Y*n@XI4CM#MCgRSrSjN7BiR|qKeDCAO+w`G7cZU_I}duGO=`0l5^
zkGeE0bKjZW9AA~}_K(03qJlHCQ-W_FyqgwYTrLB5)7y*E$=F?g*d_#w8yqyW2TL~W
zEi=@DewH-@)nG#hn*BaMpW<bL388jk=&a`5oac0*Ltb)d#gfNOUu5nsq&@Pgkf$)z
zuLm2+7xU;FI$B&-LoMEYh2zVq4ki41UFuGFi84T2rdLI75@IvWS<m+vSR}mVy?WC?
zINISap%^rA{-sa17Vr#DSnwkwnuYn-6z(vhm5xz6a1JyXb<VhSFSyD-eD4^4+C!9*
zq+aWS`}NbaFrJd3-IUMh#nIkg>C$Z|`Zd9jS=l$@aUjK*t7BL~jh11_5AAc0EzJo-
ziO^F5-HigZN?oNKu665*+F&5k-2JOMP_oG(8R9FHF{>%K*R|~w(sr~<3@=)ZNJgY%
zWh1{qFm}N$AZ6lKlOEVF1e#9oNDwkGKPy8g=vnPwNRwk9&fj#;bbY{z>yQ%idD_iZ
z;cadqrZh{s&k!W^5H#q^Uh`}u9D#;eacgf-@SGyleRH#+KX1w=Zg8LJWLJr#(_z1j
z8_PQ$=4|?yc#tX7-PV2AS07>qP+-?Zl-Y4(DxFBAN5;_yJH}Y*<;;jsPt2J8z1_G`
zRnZoX!iwVRbkrcDr00^MIJF3GKCzH`M5c?T6+U4VbkoouMKN7)jO4y%etreceskbK
z<K9JNrlRC!`MLs@wG?7rplc=EU|~tJL@Eb%+n&>TlSm3(yi=J{@yg@a8on*q`nF<+
z6!C`Ao#~?>c(Q=qMd^An<O^%5sg2giZD19}MV|1%_)6%ZAU65IwLjS|k{^U6?FxA-
z(aDsb_*2tklgcjV(W{=$4#crp2^lZ@U+{1}F4STD%|8j{R?mU<=`+>qoK<*oq<#Zr
zR|Goq>xMnU$kbKe=nhpnEUK%uEG5%Z5C|1}R&x+HQa6bCm|TkB?&ZU@2Y~$BgK&j`
zE!#I-<uIWUm73idt+&vEXfk<|KH@jnbbic*1R)BpmP`v7(>`eQw(*OHFZ)#DY0t}~
z7fO`ai!#|_{>+V5)_mZx(E}mJ(~PT<THRI1q%eUBEJ|*|EN6Io=aHkej@)Tebd7~b
z;JO%IQ&;+3o{-ICv-uXTLXpxbXoX(aOMR_4%sC5_Fmsy(Qj4r$H_6Ym&kk(RQEAaq
zUk7;h@=3HuL4$Q-{ix53-9>_KVD0B$ST-NQqUlX13_zIE<j;s68q!$om@p$?UPS*4
zS6A1-5)B`g&Gn}eCQ{i7>sH1Xlaa^mSVTj{_<(zO6-KIM>iATnJdbO?!hnvvt67xX
z+(|~vpIW4tO8mGi8w#FQpl~PoQF_$9DtP@*+(d<o$2z)<17f$33TR?!Y53_`VFoyX
zLL#5M)0;Q(5C8#!NZ@o=o!pAsMg=6Zn6{W<TD=JpG{d=`8o`(xj6QOo85Q>P1HZia
zv#dsI(>P?kNeenm#UyeWY`999EjrkV*NS86q`GoVCHRU-h3VR`yC$@48rEb#7Pap>
z`bCjyF3M$kP`(&0l|ka0Kw&}64gBx7X*4=MxW`4*I|J(+GseZAVq%lUV9&oq70E&k
zP+}@8+T9qgl3^b@X&+_mpQK#k5nO>k##tmn-{Vl{aN~6dlhHB*251S+iqqp?9bt6)
zaq{*T$9FZ`Jxy@O#m?s?DN#UPn}AcAe^jt=>JvITbcIWbu4(N@H<}>1NL0FJ49tzl
z3~KJ33o=F-Pjhp`YU3Bjs-Fv}f{<r}oTn}S;5v*Q&Ma?gM^BIl+;8WgpZwJ|duBef
zX+69+kpAL&e-H*sXV*|{KCfH?Ws@ZAI6)z6199kb-@&Oo*o?J~d4=tmblvp{^5Obe
z8&SJv!vJO)?=@icwZNR3Dv2>uD`XpnA8gM~gC0x2fna<thb^~hRXD>fD@|X5>t*0s
z{Gv*J%aHPDW=*{i&uyp)c;&Loo8aVN#ee>IFwcON>NkoQ414kMGIH&*t`R=6Eakq`
zUQxvKG%)Rl#A}(JHt0R7Fm_|Alki?ipS9o{cbt70KIfhNuxQ#p)iBj9wIL{}L<rx)
zJEe<+D^%qFj`~jS9{)>pz!`Xqd-fg>a-}|7sFfq&KtEuqsIz~J<QAJ?E5jRVxKrpd
zia1(@%{BQf+vq&Nk?`j+u*&%yLpTLXinA1m>9Mfex|5V0B5;JauJM@*>)Rsf>EatG
zhQ1s2S4TfmI79d#%A<;Bv`v=L^I3t^jz;YIxw?=?Xb_QUd!Iw$sLlu5W>2;u(uRv+
zMHFi0_^agEEW@$`$pxsvKA-9ZCUfRl?R8myT)SBhKF`R{gKPVM;QNKhrw<Y62|i6q
z&-ZhFR5cuATS>rUUBs0KixGU_0buzyHCqr+!!(v--KK6+)j6Eao``IL<DK<o?;LJ>
zCL|HVX{aDAt-}9tg>ey<z2#dmyN~GW%Y~<Eb#~ywI%iqJvZ;cxL4tDSAK5+(160JV
ztbT!WPRsi9#_Q5AIA)B>W?=3}>Pe<2roWYW8zYl$9sN7j_I<k52W1AX_S0IjwMZ|0
zD!MVm!xo6!K{^yEB^sV2{adipx>4^Tn3xHPok|I#IT44~@&HTj+zG2aJv2OF6Rh^$
z{_G-8%XdK9tq>&yf*mh$BY@WQtGkFr>}b-D#vdfwOA=$f%`iC2*41c3_;M!2N09a2
z-9ardnG`dD#S!uS66OSG6&ldOPf@9G*sQKnfmIq@36mB_X4@jXK^tWzV0WGF#;&Vk
z(EQ|0n8xpYuw}3tB$%Xf+f;OaK%G=z4^Z0GR1{eCfm#t%{vIGb5rH{d7CYrQF#aa{
z0x!&(X!DIb&Di$<s$47uJSu-`ya+Gzs{_AtCLmN8!{wZMKb-|)(kQw4El3(6@>neX
zz6$nFWk(j3(>JpQtVy7|6{(2mfm}^U2%XR7j`cK0juo>-UW)aq=tQ`h4UV)!?fELI
z@pU#s!gTW0E9NQdRkp-G+aLH;3Y=u5$zBhw5R<d(krOt(4^iAh!AmQ{tS1gpgEx2e
zB2Q!uj<c!s)J!PKi>{q_Zsq{tpO1A4pOHr>R>>?F;EE^SOu6IZv&g4}Al2SS^FJKV
zIN&+7#3USmK|33~!Gv>05@)SJ68BNQoT@M;*|EBoT5~D)>TKD{Q90|$4#O~xhI*AL
zs>ON$v9aCpQZ}lGjrSIj@&VMyLJtjO+NpbHQ?M(peX0ZmDHo`WrG~rc<{5E4M=x4H
z7&-fOZ(dpJ$5Q;pUtpxp@3rPKlcX`F@HBefR2!2RO9*oAnD&?Kq8YZa=v?xuFkfHP
zQY_O8p%?aOEeqVfr1i67V=dz!Jtc;p^4XGY6Ir#qQFyhufA<x~ncuOx0!aG#?&ztD
z)MA9)1G(d6yhh%O5H#H@x^-79njB4-N}dIGC)usy;U>d04%@xi-XqO6b|$0yrVtdm
zTiWPJC*~H1W`gN}&99H=A5Vu!nW#7dERa#f)n4Zw3z{bjd%|v5Yd?!GXBalUJqS?a
z&Yed<^tM;wU{Xs|-|(nFYj5nuK<yNmSbm&)Cbv64d1C3r)b?z6K1eZC`3tpHa6xT*
zF2t^Bal8*_8gpkY(umvhYed$qJsX^~)~Dfl64mHa%RJxxG!6-xUdZsmUa@&>>OGaw
zdFFVZ8FvAu2P9OSXj%()Dk+oYWueUwHoU}f{HMtRXlf~wp<A|A24_J#1smI(Iu_pE
znao-WAXZPC=Qzv|h1+^-9n!<xF1dv|*rL`ojnNB*7OUnE4!#IZ5<dXc2Hj_<X}K`V
zP1&hLb>@5>&tnoo5fdoIGX9vj5{2N;lNPIGc>5|k)ddU1TSBrXmhNHZoT1nZG(|0l
zwghbC_Zjn*7O$D$@C^N^%D8u#CSBOhG?VmNs~0?_?uY-oSV^2bslUK>XocP>F1|dW
z$d;~gYEc#|7I^K)_<19{$!aE>$+22P<ka$>`Qq)6tF}B9lp%2Ojr`#0zD((b(BAL?
zhS~fhEdVBNgoa4cI?Sg2B!wXhr#%Glm@gaGHju-ZpS_E7bsWAg4jVy=3jE`7(bf$S
zs@jjgU0#C26~%XNAyO!NzdFObj&B3bb8A2s+mB>35UZBwxP^L!)YLYIooy~%oWU3;
z-<|j)6LN$MOm8|(SN|H@xF}uML^3SPBgXYq^%k&+FAduf@gsFF(dIZs(>%AaHMJU&
z>Ic!;vDq+{{wL3wose}dM?Z`_(c1mR=F{fV?a^dUhI(0Kwwp$(jbX_Io*8J~Cep_H
z)bF4RP6JmoY@^e8)*0FjnN>2ipe)}?7S*lqI8r~U5TmAU^7Q431vRpq$C2bL7VnBg
zzqc6{ucS4K?&9OcekOV4R9Hoy&^0Z<3Uu7%DCA~%I8LmbR&a{3VOnT<pA%5MNo`4~
z1i^Lh19`H>1MH(!OIpoDs3+f+@Ocpo1BBh!P{=0;4>4EzjH<aG#j^DU63PTDZ~I`@
zhJE4@(<X}X`qiNUZ^MZFEjmC~W^gS(=o{QP{Q_sCM@Qk4h4muhx~qmUyVC8m0~PC=
zKhs~w=KVL`Ggv1&?Dt+XJX@ecS&p_c^gvl}9C*0&1rR?JxZZ)HSN#d$j8RgdZDI;2
z_z4Yh(={HF3!9=a=p8(2h3GHaPC1$fS4*IXg9!XF@Jm4(tLTJIXhZ$Yd+;r3aiRZs
zgt43=;9eL+&lNLUyxPz_qBR6Oz`uX{<YIr`Kw;=w-Y^0=hM|8ssXm>71q$gQzB*Gb
zNd)CZ`X*6@2BJ<=xSbvSeV~+2^CfJHym0x!v0U2D$frd%^I^Fo4jW()nTRA5-%lG)
zEn@RUBP$@yM&LQ-*ouzZoG;22=`ci9*&sHnJ~3GKlEXB!6Q1@AJli9y3K`C+G)rF|
zhP~f_1sSs8dsF-Ru1aal$GCwTcf#3WOALYAo>b2RG!tO%M@=2lg|{f}Ko%@7vU1hA
zgl*?;Z@K}9lYLFm>NXp48knS8aD<8S&mfO8dB;_68e81Oy|f5Dr@6`?y`gc|7SGGW
zP}|Pz7*_fWYi75>l2nS)+2`SWErcB5o~|F->8J6GEL1|xrunfi(l|>CR;y$agW!(_
z2Uqi7gl&7D)=@{p$!?os)cBlvpHzUre}`LP&Ul@ID@tX__r!pL*<zf#^^SoJW0M9p
zrZZkubJ}LbW*Mc}Z}BY<Bg(<w!eYTe%86r(fOFJWW&S1AqPgZD#O1mPC#-SO{Lu@z
z24K3Oj2mg+TS8U}HPe(U>ouHjB0Q?KEHBMkb-Gr%zD01=r)S^eyos{jD!CDVhV+z=
z_)%gjd`8}tZFa-!ZcQ<sbh;Okgv6+Z<99-t)`ku<`$C~uq#jDZz!Zy#VgS(6G{)P>
zoHuIlx)isuCMNK+VIC<mEy~s-5Tb2}I^s97aVn~CkuBG}NC-ijce|}PZSO<xGZ40g
zXQA{MxSWqn7$Wr3%>bZ<qF^?huW_B${^E&O!foj1@9YP_tP<KeD+T=phe5mO$LF*U
ziw>PHq%6wbE?FEN>ulMhXkPX$KZ4_H9?%*~KFhxiWm`m8lEi^IuhbEvNu>fFYbm4$
z<+8!^wVO{xuI$g+EZ@@Glh?9#nncyTSLz?4<vnH3FkhS6u~HZ>dP`2W!8>*`QnrsJ
zdT-<}b%i55ETum$<I>xA!GHIi()rHGu+_8k*;SLfschJWZ#H>#3BUX0^5Cm3e06a<
z1Yf!Pj2ec9OIG31v&bS?VKkbud$KN43Z%v1n<G#uuG~R(vRAP^Bb_hR?m#YLJdYA8
zePHBmUBGxVd>~m8?<JXuevD>)20WZQLkpIwDQ=utA?K`mV@^Db*AL4<K}ROZV*M86
zh&GC%EHtmbPcWZ1&lzV>PI3^-72``<EUyB`>qCf_#`Rr2cn-lB6oWcSd<7KpbvLj_
zN(-8qO{XA2J;9g`X+%2+$cl6`UJ;82Jb&V_NIdw%<h^>NU{I)zz>2L9((Y_AvrK!S
zTmHVYti$zTZEN{+uExr6Y>TO8do`T2#Cb`!oM&ngbC?Z}rck^Ym(Ax`7RAexWC`6l
z8(qRV(?u?yF%;mH9AJSoSIJ+1vDHEbk8SQJ6yWr<Pp>1OGu-Pn%tWigw@fA-VY_O_
zZOp0#Yyt<e3GCyu%kpM9qEo$!-ejV8(`&KOuRsSU3!rfpZklLmQBAPr_dRvAp*s~+
zpK;C)Iry!Hb@yCq*P{`dWFgm6Z|I$M$QeMWTs*1^H|3J@MmVA~MLlm?lV1(YTD6AB
zHze|VeBu2KV^dYz^CnQE==SvDaV}hG%*KQgD_`g6waUI^_L3^GP1}L@xcWd$lJGBU
zh$9O;Y2FJSqX=CD7}$YO+xXGD;`x=6YywUG5$a1ty+Vz0kLvrz6XLz^<dgcjgl2Qn
zvY%uUDte)(kYz(3^xaq6Sl4?m;@F|kdA(5cLT|f}V=et&y4d_pEhr)9X;tC9pC>u2
zxX4M10RlKc9GI(DATqX=pKhvD&IUp^b^>f-p=yiDPlkX*YNEOawl1fy=I<`(ed&d8
z4#cf5JU6z1NyIIeXJ}pjeRZz~uflF$b!EtP8&j7MvH>1-JkoZN1m5F0Ys$oPB29!|
zK%@d)IOU8!A+CBJv9Aord18Ldm;`+I)*Xp^c)gR>VSQL%ow9Fv&NRjMr>0uPW|L$o
zr+MV&^Fe-ooUWk4gmvJiFRrTde*c~;`h=t;UBZ=js9SaHLK29C6P0*Oio&rOKbKsv
z=&4>AUwY;y(w?6TUgjRMXyF8vajf4sXY8tbMTOA_mF^|LEa&e413WBUG4AQ5q0m<h
zmYQ|nYt7R&3|4qC9mYJt*D<B+J_&dffqIUR=445|_B+sV@?T1r9^`ABDM-IxT?3@`
z4)<%OOoYKG^go36ycTVz7Q%Z&I;?HDJFDn#!M(C_HJw^xp&UJMzM5JY#N-SV1eQEL
z5crTJZqdr~JE+|zYqTAW*q77cMg2|c1gk8Eg6Jh)KwQJ5n`~a2B@Z)-GOUKbUQ6J&
zBkfHPQyNYu%_TpCE31Kp{S|E(8<fvbIm$PZnhzs0EfIJA5@2f;&x#c*&D^8Er+0g`
z%?G{4VXY{0C$jL{By*iE)|23jN+eIotJW8vYkj?%h3QHIRph6fxqK@#zI7AqZc9$>
zoK2eJ{{X77gYi%?#%<(}5uvb;V+=IsJt5!fU^A=1^*t`wfH-Av2->d256#l65XJ&g
z$4)ob#m3U7$y&$iYWN9#7aKfa)ulOHYzl$A#P(`R3OQEE9BLUi%vae?R_f~V)7Zmk
z1JgVQT~i&`Y>+%j6$~I+l?BqeZT@K~fYa0AtTJ##a@?V9`tQU;?B2>|s$-(bt6K@i
zJ8<@C6Px#S;K1PE{}@F%S|)0>H+cxq(BP0?Q6%kldp;xM>98-$x=I@q&yj1C(^*!z
z9)pd75A(JXUui^!oW4%50X7^F6OV_zu?JfN`fa3joZzX5s#dSKshzrc7j2SoBY6oL
zv#S~Id-BDny1^G6X;uRSHo8NzG>MDFBciyKMSy7y7Z(%E%-vgIaZ7`*;l@eItJ;NX
zF0ve8LDmEDAbKD7X7QkZ4IC`!#lRYs(Gq0g?V%X9VG4Y8yQZDIqt*5A!s}TkO8|Zw
z#AT<nAithPKjtV&42bmbeaQ?fiWcf;@Kd!qcJoWJo>^KuLMIki9<&3IG8|cJ6}{9%
z%Cp6lrTK9s!qOo&6q(Y9Sf5mPU|K2Ah@1BAF>(KZO;wQBF5}p41=kvh;Yb*sKKz}S
z^UruV*J?{rZYXqBhK=n#%~YJR<uDitq<A&0NKF8V7snfg3R6volq*nYOct`@FHP7s
z(l<vx1L&O}u~A@aTmIZ&g=tLoYF6UJT&_v~wSwl#L9w$`v!?9sq&FCXl3gpnZPbh|
z7ox;EPJKGjP%|oVG?so&y~RKc%bMg?i*SwKxZ4;Jrap6W2W6LTMFNw8g`)FdkA-lR
zJtBw>*$3^OKzLKpyY{#29%N@WCeei=xNnWdSF($s(~~_M3_+X#yD29P^u-34^h=Sy
z2JI`2khH<rr(Wdto{8~9EEb|O5SNw2p!CZ4N$XU%Q(m7GW&aGg0A)*+Z>BdK&T$U3
zgwux1JnKL6V8UK%>C}b|zC$;e#sj_nqGvJkh6%h=%dZo%aDu9>Qw4J3G9HU`30soR
z5u2D9iM;sOa=rS4oZQ`*VDBw)MaF^<IU`YZx~<KIj%VO}T-SD}$$diQy_{hkg}_x5
z<`;LMLD>&82L)_~B#9_ID|daB=x#+LZR6p@))M^T^FZIT_0Bj7jRd)mR~&|Au63gS
z#4qLQL{u_*41NYc9Rf?a!9!rY%)fYZL_uIz@}Ycr!ISe{z3c&m9d-$WM^2dYJMSDf
zo0=bf0>+dIQfFMiG>FGeuIcNaijrZ9mZYqZfsYwA(I>OMxKHd2kVFX%Auo^6Ic`X6
z^HZ;4tzeQ2cl30qe7r?k0$zq169bHLVO7+y9#_W5CZ=>8Ga-dOoZ?k3K#541sjmWC
zA>s`seODf&M{V{{7^YprIm@3MTl87=HWV_i&M=Go>LJo>ON|vO@4d$?e|x+qqfy}g
zo?nrPXEJ{H_q6NRI)EE3O<O%VEnB55NqDaAl<X=I`r_An<>x^3?)z;~`*D?$G6eOe
z`+@pQ_tVl)d9vTFL1igitwVY54F$26Q%yoW2gHIhchef2>>stLQpVFI;SjQTy>d-~
zUQ&j^bBeP4#G?87)WUIA`df+Fs?_;X8UC?>ib1<-q>FW%z_tz+(p8ht4|(7!j8>cW
zELqUuLD;sq#9V&6c>wEa_GdKrTkk*FVaK3mJc=R!0Hr#B|Cii(Oys{JTu}cTJM8~2
z7cWbY{@-%(=9Ep_e{ymDUGOWsfSYDny7L8-+QA+}bTAD=oq`U5glN#=AMYd_vigEG
z*+?Ltx}iw%d+~$IQ@P0DWMSB!i_Zg=7;|iT@jM4Ib=Sem?77K~jmekB5lDMx@6CVv
zugc|N$Y1#WU2=$-FNG;uZ>8&N5ciuoFy@cCz5AmbJpdG=ujObo@49Sx;lqZP`7N{&
z%|pRz2K+a|kE`vhl2+_`OjF)5pBv5Zo-G_XM<SW5t`EmvTD8_pe-TqLQKKnqRWu8I
z2irQcYJLnxHaHg*dKxI@mGltN(UqbRYE)tb7WiQJ7|^noaLMa_l)Kdcp*d{Ca>E-?
zLH`Y-XKXLR?NVh7QY8Ym2_PF@R(=M?_UE(;05+dX$cO>~JSRSJ-`C#Xn%O}^5@@-R
z@&Jw>Y5RM5t~A5ru6YPbCbbKR_SwV+jcVML#iA%-cLs7Mh%m}5YbzE}!Ao*9^@3B5
z#Hu9zDQ*r?sTB?yNR&jH4g{p|D`x@tE?4xH>J*nX`W#W&PXFYRF7aTF_=9CX)De`3
zvr2w{xYP#}r=4mBK$QXx!G*M0+*}o0JO$ecE#7cB%*oBPbcKsSK@I<+#9PO@dd<Dz
z=Cf}Z6~jC>#n8u}4@&N?N~l5h9pykKEpfACIL7SLs~u=_e$35-oV9rdv~g_!yfWN=
z@{|!#MR3HlP`506tyIKsr(anHgAJavu0pY?5!>_j%4d?F47&U6!`SCpjMpdiB)bZC
zH%3OZTc6@5@0?ZeIjmj$Qnxn8xfO<PN^m>=T=AZCc~YXrDNvb`vU7h294WK{!?S$?
zp$TCO!hbJAvOXX%6L&m`SIpw{E2mpWC5Rgoyq5~A<)JMn7lo{do0H?gz;_ZnsTEqf
zO*h^(eghP9797P3Dj0MHKZaOc>*PcWIC`)aPUMxBIB$R$nhz7vBwiO|&U1Ty|Fd3z
zn4;{b{>jicVg48L2;g7y@BFXz0{`FY#on3D#T^;|5ad4x|Bp^Z85RIs$w0=ks8Z3g
zNrT$r|CrTfS}*^LS^dBBlm30o+Q87n+KJZ4(Zbop(ZYb%(#g*D|22VOo}y*p|C}IN
zRVs#v4QBh5B1o5ne-#_QQ&d$$CJq}vk7PqtGsUu~;^GF<F--t95RSeQpR6qMI6h(W
zcM1SZ8xQ6EZHK6s?<T7K6pio8v=NWpv*Wk_pXKfHo#s<H%1Ful=iux|Aa#VG_h(k~
zuiWRbjYh<+E4Q(oRI8~gRf8Ok%n@)kkW`qSH*sz5ExVTExG@~J0(KjB+BX|%^vLJ|
z+h%^+k`rm<+yg<X!4DP2sZ{R4mx&?wB}JmdI`AJ84gXHwV}qz21jhZ>w@10#8ULD*
z1ESOg8^quR4&B2Q$gx-Pj*o0`zGX=wyAxkO{c&2UZmHt}*9kdp=X7YLmd%;sG8Mjp
z3`o3B*y&uWpkkj}zs=fi9uXbPt4HLroA6c&_8FXKZ&@TznS5?Pk)i>`B~Y6QgwBx?
zb0ya%COpv|i9`WzR%4GCW2nH{R9<3)jk<F{g3s8tcKt+;-Qu2MEM0{T9JjJ6#t-$G
zh{yT&@y_~m0Yo%{lfIC=e|wIoZEf)sH>&2lUsAGpv~VDu)ra{AjsQ0_qh&a2n2Ibi
z%OjRJCV0>ryKe?N`X2M*mxK-6%tTw@(t8QM7XQsq6SfYx-o_M<$Ynb=06{3yd*K{}
ztrMm@uq_?qpBp!C{!~icCAooQ>W90X-LOb-`)F5GM%^=jchQ@;{9F5QdQVVdt6X6h
zkP#~7aOVKqY;N+juC7J31nqeAkBUma<1lGA)p^ja55ygsE(9H^Ry8k+?w6959TdPR
zw+Ir_d+^?+$y>UsMB2nk1H^Wm=h5pQ=%u^%lS2ADd<^RRX%vN+!=!;Dl$CIu;z(8e
z!H>#!dSH8-PzE7HOb|<s<m2u?R}WuyG_en%2zq<KHm&@?)k-0enabMM|8TTm%Z!@s
z<;6|DiP~fwxIxxmqwkLvJ&}t10lUIYo0!9b%_i;@yA}P$efF7lur>G%OGaL+Eu-`Z
z&``u6nC@y?ir}DSwk_P}a@4$*`vs_#*OIF=q?D~8`{sIf28k0^PaqjfEl7b7$%5)n
z29;MVSb5%C5bs(#VhDBweJ|#ra8<X>tj`9|ag<G@lb-zOhz+VQAiPm^#M%ON2gO7y
zM%u1|YskykIobmNTQ~<rYdoc2O>pP$Q(mSxBWNPP>QqphPx{JPG9?A60f=m@;qErN
z7LdnHAw-ecSc$JDI;l_@2LiS9axqY`(HD$6j0)vi<z95H0Lq!gQE33WJjDm+_Jf+r
z%$#>&hf(|97Hq^x!Ds7=FNcj1!X3wg4PjA8sFQUTHRX?z^yCYTH=2&S;vwF^T*l`U
zDG!X;`gaWEe+?6j-Zbk(bfiwQG6$1WhX-~!v1($aNMASdi)!%H`ctc8Gl?AP$h;F~
z`oMI`Q;>vsvffp$6&5IT+;9V2O5Uqk@4;BTO4Jx2u2m_~@J*#bvtVsIOnh<Wd&xVX
z%>Fto99=7)VRk%zw;b@T70={%fZkFqbl5<DqO4-OwkpI5g8MQ42Vd{N9$K^o3C6aa
z8{4*R+qP}nwr$(F@r`ZUb|!CTdZwr6d;J&oS-Z|&wW?~JI3+Tua)Hx?zJZ7tlAukf
z#x=9!(PW$}D0RpjaeitZf=2dZL*=OMIUwy#gW-sw3(*V-FMBk1ECg*WzE9qE#MRx(
z%f=3%au;hQcYQou^Zf^Va}4w1dw<c>?*GAF2mlBGmd^h#ToU~MvG;$#rH7HV$$t-<
zJ1PFZz;Z-a#<E58U+g9;Qtt-^MBb9Ge-CW-z#ufWp*vfLnp8HPEU^M<iR(y|4~7wZ
z0PriyVWL&vswyf)!lIs(&BwB(1j+J_njY#~9=c%nRNjN)x>}8;)Z4w?{?W`ttG)<<
zNbS91-&A23l!a4Krs^4|r}Db!aT*;w<!F>B_MG-NXDa2&;CWGkVAT12$5IHIo88Xm
zs`_1KiAbW}(QLm$N~I4kvnaaGc4ZuY9!LAf(7EnHrn!UNSwpH{??{@H3jgosMe&S0
z%CdU%et&b=#b<#msOYgE?{{q)ximh<l91|ot@C0{c~y+Hme;MgG&!?~H2Jn`5h|&O
zn<a82z1CM4Iz1H`3M!2@`?srmzAwu-I2ki6n>9u|D3pRRNYSyQr#N)TZc*iuJ22eT
zsN=b#BId#>Q?)E$E@tHW=rm5`UmryU%y(l=g1kwPv^P9o9nE&av2;Shg=BZfWbj~J
z4$LHFasmy+R)m-fbEP;9U`!_gv%ODNaJ1o`EVqS{5TM0yBzVq3o;l5@9~Swmne_xr
zOSO|n_opv8po<t4W^|6+b>$hk*d{7xb>dMG>$PLne!|Vqo>~-zs>F12M#{uXj^(Y^
z4Hrc&zdHNAPG>s2sG~#>UV=+NZ$GLlfvCJ`qv(x@?xrtUkAt1l<4vNc6_}WS8xL%)
zDNW>>S@f6#AC?GVGypnPHn`)1XP;fI?X*laP_b^bDmm)ym6_uGwjMc*e7JKKYJt^;
z$~+ECNY&obMo?`WmUO{6^0=2+TeT(2kxaV?)yoJ)vxJoZ9iH@exn@RNPC{5|a4OKD
ze0~tkb}R80cxU_P*(DU%@88QC=Rs^1x}SiBY~#Gqh%RYs3iuESRLf<5)mvu!2!afI
zw&*%AnkE$eco?lw*~}srzB7Tg(mmq^hP0XT8^7d>qwf9#Zk6cNq&czq8DP1Pw;eC>
z!EFk)8k>LpzUUBhe#!i^3!}uCE_q;*w{Qu*F|;U(5$PpWA;t)-Bv^}yky57!9(KH+
zpXHq!;;pRj0nw9)!&$k>H4ea$^pZADPPPN0E43JAfXq)M%g~e)dFx^6=!H`ars0}F
z8i+_cL|t12U*BQX!6#x6N+h^lGpQ9tx~i^yH3Hc53-%Q1FK>GhzVW>kCtLzT$ItpY
z;fj!s`->Oiz#DD2=Sp386rvkykT?DCAC$d|Vt{`WJJ9kC_9M>(o)CumE2GG-=L%Lx
z@)84oK<_xNZmn?#_T^yBU2%t8HSOW^uUKZm;-ULnMck$PPY8WroD-zGU2Hnq_;=SU
z>sp|#;yFx}URY9t2I<)<Ok!Da??Ji#$iN~by2nHlNtA`>Cr{na$Xh0nq;Md=3(>%?
zHxjtv=g}7~X>16)LW<s4<c=^~$I+Pj`&q}jC1RjKAUk49C?@{XuqNY@je^k=(V{|M
z9UHz?;;7k!(G|FirtM3px*GsHy1(zC{!FIRcYiSDF@v5D7Uh!5P**ua&qMxIMQrcG
zKQi$~GZdF;L#5y~Y?ecDasi2cTy=78Vo{A^xF$E7JL86Y`|C~hgTzrW8!Er<wEXgX
zj%Cd0MeRILUi#S@OzU`2GNkmF^;%=`aZ17EMK8&t(zZl`l&)w|RokuR%U;`rW@1ow
zD^VPOja`Qo(ZBo)jJ9xf6zK$qsc!cBp=29%ie#i}gYdQ#I9egB)Sk(Kde6Qot07GE
zs}t!UiRkQi?Xzr<5sLp>!rV*7W5np7zN3z<9_m-uQmSoYDpI~`2u29_SAw@P?4B1K
zPIw4EJUzEd43U_!F1wV=89PI#^|jkXKbnFUX6mddvT*>X`pcXGI5=}8$Mzl)h?*;w
zQ~^sqn$XY1PL5X@ndw}eNP(}z6f=iY9n5V#ZV9U8TZaAA5Jf}GK=lNq?&YehrO`cY
zRwY=R@NJGcR$M(H0hL+LGNT--qZK1B{sa+lGwdrT7lT+vH!|vbOCwlVN+3aMO`cr{
z1*p#%=L&Vc7#TK@3(`FqCPeF8q^B`SWh-e_)2opg=?_c-f#G#qn7aW37r_(}<eF&(
z-GyuK*?}OU7v!3kNTA6##`)wv{^q#soF)OD&*nTnbTkz@n<BN^;B+L(ef_~#mSNr(
z&cANoX=mAwK!qCPGJ1k3kR(r*F3&(=yj};#@}OohWEiwWjPtlJXj-egAeD8o!}WSx
zN~Tgl>J9co6eyfTZUrul9iS(TSMX6<MlPKsGnD30xpQdLD`GhYiDE8zSxM&gutSV#
zHvfz)-RV|R*6nTXwiy1~5KogFH%*}Pr?0@h&L-Jf**aIh=L}S8w4V4xoGNb&-u(Ag
zdMD?aNF?m00W|-8yU(D^Hb)^uUj7ryw=#3BcSNZZXfCb>lMsYgAbw6ofrYZ5rg-R-
zlS3wA?fePWDc+H+p)a;EzspG@dDS`=_1JbK;+cZ3vvfrTsgSoG0;f@*gQ~N~50p8H
zFHD@|s-KCY=0<Fr13eWxC%S=R(#p>Nr#_qv5E1mSBeKMtX4mWb?<PB_I`+N^^cR;Y
zd4|D4xxNoOy&g#K;E|T(YG2@0l46P{ua*VdN|tY+uBDoV8txvH;J`tF(0ba(`m4%y
zuMIzar4e&lz=@*JUKPf_-x!Fq`P)Cm6Z41qWwcph;6ef$++yM@A3SAHUCy~RNp5JE
zCT4{S04GWlrH$>;^PqjeV}S<RGCH%094^w1!(E~k`0W#HB8NH1VT*b~IV3!vi2im=
zo*4b_>$e6?t!$_p?Ygr0?%XQ7(JH4BoHRp8=8b^Q!;QY(nmIc3(FtCzgmY$V6OiFt
zzQ*gEu{+v4NBM&ldEf03%wGz~-*E?pM~ALdCHowvC<x1qwW7|hdpmQ0Q7i$$r|>2(
zRR`%1pkl>uopR!42bRrz2or(-_8Ii&VLVBKVuw`6%^!?wV?=Iuf$%L(%g4-D{UxRs
zz|`+k(}EH*;hV}l2&VivN@{D0Q+{L081m{XM9f|ciFmMXVxD+rSIw|_XQ@`#=8jLy
zN1Grlq1YNaJ;{lveH@92vd8QnBFe3{O_Jc(Kkwzw;h{G&)<w*b^1BXau9`nACr-@X
z0W?=pqKQLjq=QVveC>~Uz@dph(l*r6a~IspCKcVTjBgw-DDAd7w55v>r!UXM-;?5$
z565^XR6<px3yms$^<87jW<?DIvZKc+htpim#hc58qU(l^Vy;By;l&_RBEo8~*$}n>
z*(|sj3Q7YGGVDlo0=2KnLYFJ+aDiIUgRn>SKNC8HpTC06W^+)Hnb<9r`XyA8Xo=Qw
zC9wnDl}B=h4C9(BXO^z@LFwO7bLDZiZ*2mvN3)}C9wAl*$gbKUMA&cnnK{E&E}(2M
z0y&Xv;w|%XptqR8DMPqNX87LN_wZuWydW@4jTqWWr1}`p!Hgv!V4W=U<P><&88sO8
zaZ{)N2KF>QuBieDDDe&yBZi0fT`%}B3J_sQQ4CgjTvC=3V6y=YeO}&o;OEO|{6IXo
z9xf1`xs7gZJk}fOS#N@7Y$|wJXpV_yt2gkOkwR$f$JW<G?jwkW8R?wvHsZ#fS}UD_
znc_1&Bw#94OSK}3J@S;K@WjWB<WG7<(|v#J|DR-psEI0bArt@r3B&&&BmVOsPVD^u
zk`Y+{^+EjKXoF-u8B2!W*yaE55;pNXvLFmFAs-weDVfN#^3~+02snQlk?KYWk!MI_
zLs9qXsi1@f#vzXl-F;UhN%`(Sw!Ox+z;`PP8xPNI2evj$zO((xJF`q!pUh^?!IeuI
zDe+3Ou>gA<RW_viXu*8Ow!kD7{s7n9lU34Ch_1nUWuOg7OiXg}js3B==1>RTBtGV{
zRZzdc4?9S&med`mV)qN+w+WDjz%-zK5aGBK4MCz5;fqI;$Zivb=O||N69Z1&N41_m
zz!TD#Tnig~))uX+jzBxjU~&u*r#DoH^$Pq7{4U}hV;SNFl7&qo0NbDtbJ+5Ff&NdE
zu_hIic=^lHcmn?K&h*cJJ=6a^HTs{E{ZF9ve@-?=na6gE9%g%o0%GQgi@z;jDF8;t
z6M#43j_6NRBr!I5Bo65qg7fJj(W_y>Vi>z@&7(}J^!*2c#Sb@tb1YAZ(eY*Z2h0}D
z2UF?w0#;+P^kKY)x5O(iA%;UUH=P_%YX4HCW9Qp5>NOcqgf#B~1WE4L%)Tk!Qwjj!
zAU}nkWeXv$TH}F*WC+s}Qs6MR$Fy`sT|<p<yi}mb5xIJ9=uw<O2hw#;4IL$&VIB&2
zK+X1REbO;SMWs-3hPsRjw&cnoxN^S7Tgo#GSlFBF{;CnP*|hOJip5GEno)NivzXFj
zq`YMV%7Kgj4bFBp;k!TxSw9MS+KFU8rCM3LV{zeEjWf(96)}8o$x1leg|7J<_|nyL
zRV~6=){&b&PttbkXmyi#7f#l*rX#n~=bWOtx_Q5;NS6txUs2X$T|V^Tb$waVfwL*!
z<Ec%YDy5^8wv1nsqw4vcW`7)-C$NtK6boa%=9D%%wan`TR6us-l53fTF;xQVGO_%y
zc5rkdjkQLlKtN_qUZ~g$U-UAFYyO||=aoLlfqXslN9?50>sxzw!2i^R!L*5T<!?=#
z{5GKfFIQLizuYzA|5_K0CQf!Pjz<5R{<GnKs*N6=$wcBd2R9!PP&vY)EV!9O#b2}b
z(`EcNy-4iq>^QnJYH3;OlFC2NXxEiJKg54Qfw8+01yQwMM$_Q_lKJv=xw#zb$Is40
z$PvQ5Om{ndQi<@ETgo~)=W$C6JEco|vnd`QwpEio>lZ<^8#W8el}jJmZ1`;+TBq>5
zQoQX2@N#{ZPD{iYvd(YvsPG)VeUgkR{etzfrMq%;c6xsG8n6@#GMXo&taXyXFJA;4
z<&8=rj>;{Pu`Vv<c+NTH!X`^+H)VNM!2&E<#8;85e)1-&kj$CF1N-o0dJtR9lv+OT
zW~zHDDix0J%D7eCf$;au<)=YhHBC8^e&YH;O4zoQ%xZr}&8(ZwHD4ob?c@CB|N5v9
zO^<3`G#1DJ5{`1xEiBZH;v@i_CY8T7hxz4*`9`gb{zRttY^u0~?nq8l@|F|&)#)GA
z5@7MMiK_9`IEGvtg&7Ixsf8k<%wIk#WtBz40Z3cwl%u3WBG^s)Z#Tb-hdoNNb#v+W
z+HZiX{N!(RZ-z;)BbbreaTbQj#+LbAM{?I>)==X4AMAQZ(TW)^V`-$kQh;x7qAv9Y
z!8_lp^-M~su$|Cj63mc!z%o|>&Z(|I1UL|P_VfArfjlqRvCJaJ2X47w?f~Z#Z6|+p
zTgde-nYPKKotIYdO8Z_i@76@3ycS8~DF;;TmhQo|`pb@6M-j8*e^g;Sb6zNdy7fRg
z*mbp5W&~@bxbisBx4vIBjP3Ekg_}T`r3^-v>0$4u$HaBY-a=JY^L_~}^meh1LhF0L
zzPNn1>h8Ac2GLh8@s@SP?ecT8Y!S><VhJEY=y}5uFY-qNZoAp5;v(wl@*B!f88IGD
zmj?Y%u;i8@ruI)c4<*wX;&*JwiKi$3;l~p3|NV;V>$(dN27vJG*eX86(v`Y@h>S9C
zm{KIwiNqKOXMXm|UEwNirrEw!S7bukdsnPXaH4QPBL&?2&-Wg!GStip2Vb7O)~mJ?
zU)zNUU;v;&9WmeZ09kEh%(q=i3IHT0Igh*&n>lH!_8&L!B5+4RYJ(}2dbS2++r+w&
zJt$Sa`_u}wL0LtVk3m1i<^y7XfY_U?_t17xTNsgP>Fm!3!c<OsC|UnFKkF2nI<5>;
z*ngMY+eZ3*uob^vK+(mCN`OvcT2jPg{81NgiixO5u*ohOaziIOCXD&VHezlwg8J-B
zb=TgDf+tr}Cbs*GwT{Ojg^_cl5j@DbCgoZbv`>{yczXEAmi+DleMry?G$)=1Yz7A8
ziQ5FB^SM4(<Z7Piye+2#q7G+Y`4p$KeMnPzwCy=dvPE_TW4KD0(H?uDz!Se78iON{
z!(^hIc2rD1vo@(hm#0q@qO}OL)o&&)P`s5>Yt>u-n1aSO<ORk>(FeR<)GKgaSaIh^
z5>8j#?&n-ite{6=R9E~h-^!Fm-2p`v{0{PXf_ReQJ1gQs?9-^7Yqs3lqG>bbk)_TX
zf2Oz6(Q!NC2^9i>%L{SYNWi!#;if;W5Dm~UjeA?&0-<gR+?0kZZ&QZFnfdsrm3l)n
zks1U5v;A0F^uzrHqHb4=uz92(s>UyEBF(LgIK5oO;)m)drrbx>+2$Pv(31m{8leDt
zOLcR%{a4*7&@oMcD2;vSsq!%5&K*gG5peY^G3}C!nEZ<bM1{s!Q5k)_LEZ%QcQMqx
zI~Aq+?ju$HgsZV=V0>>wVo0zf0}^S6kjKYL<u_oD#K86Xg9Uefx#6NLI_JNLliSc^
zLA5upwt1_|!J5s$lvy;td4v{OE`(Kg{K{fS!lM&%g*k3vX2#Dgq3zicuxp>$8;`1b
zFbK@WE4Oy=+3ff5T7>WN^`$r6gf#4=E2eP1ID0<x$BaxGZQfTtm2O~=VC|ozhYA33
zk9SDsM!Y`XyT74xY+fM4uo=CRlii}wIIgaB<2!A(IwEdA0K`4$wm6W~$g;OMJeu()
zrZGG3a?Gy%Gm=s;@#=9H_SccAXr~saMm4X#s*|c$+6!Xx4k8Fw_5ng(nhuy@XT(QV
z-Fzc~LD(Ux%vj1BkGeeORR}OjpLjE`LcAW#-U(*X%;OAG0k;f>NV3K2J##o`0WFd}
zd|zPgv}OPVn0gEkhT%n&<Ci}8kfP$wJ+nyGr}@_0(AHWemy0s<m2ITV@+(VWI6x1}
z&JHMkf9q`fzU;4LU&DPq4b=R>BQXvbU#Ert(gsJVGYcjb!c@j~s<NV#hjBNKs+*3B
zH40Mxg}sLK)zdeO8}h`1)K1aAUDVLMR#RUwC%&{INkXkkg)?>p@SpA+h_c-(C-qQT
za?T2yrP>=<rwU7KUG|#YCr`ekrTqTE?uM~wS#XJ(pIzu93GE0dafG3~{}<kH|5{6H
z^u(LmdNGeH2k|2z{KBrCu&iGIAqKzV&+L;d;g2jIFA>|HZ|?YxU3pr0iUS$z(gHli
zkekc3<qy&fo{3KZ2v}--v=8d9W<q%V*`X2gjQvt>%4%lfo7WORBC!MmKaH7r%vr&v
zGa?#+AJ1ku5mnfvVNvu)6^QGu$l>K?X5fc1+JYm%wH&PcEK%k`Xuq1e-Wd@clQgpw
zK*HZ8JyzmP1l=T{J1_K;n-O2x)k`hlr<uopf}!Ev2fQ1$wJQ0u?jCDt!Rt7gXV>Z;
zlcE!cocv(k0Iq+QG>nh3=+Gr+!@GC{7iTp~;M!h8Y%&3Zt>V0gG6(i|h$ImT(g=>t
zT3P<u+sU;DL)tqsFC0ijU72`5XCvZQf`j_~K@fKl-0@Yr1S3k<QJhiK?V4;iP5j0A
z6#o|!K$tL)<4g5$$z9)vfl{uJ;y54vF~p8Q)E&2oY`EiH09XAPdJp*n)QIvZ#f3e@
zR=~DInuNZx{-6d07|iY==xZ0}I*J`;u1EFh>;`9!775vje#K;O+NBR<i$M=mA}bft
z>D#ncdJk^YRo-lg<Mf)-?Hz7NHCa-qWd%7Skw9a~3(9tegX<I}gvRDtkKG*m69r@8
z^l4sHYz>?tz`J9VcQSLt=wq_=-EbE#<dY@El0i%;vz1tKZX|wbHH7e}bO+C6{n?CY
zn1C@K(!v_s#t0)yXVpUmS*@-2_^t4yena<`TB%)%-W{)HW7nl0=FL&8YVHG07S-KZ
zdn%TOOSw@o=-GoAsgRUGKgx&y0jR3}8D+3)NWMI##+H2UQg~@ZZq1<bGCpdRGz_JA
zGWN*>g^maeTr=0#XBHIeYV=dQ4CSD@!A5Tc+6!inF2SiC;*)Hy%1AzkH>cXC+_;x*
z)qD)H@R>j#E8$p2{+d3*A-->!agx@a2;Bts$LNyR74Q?AG@DAE_;$<5)gIM!H%v|X
za+pX>ofBz$q_Hn({OQ84!<VJN^3;_fKXe+&*(6Gh18)m2Ep#rk<cz9u@go!Hom(=0
z>D=E%L1*2yCHJWlB?A%HJB^lJH|HRo8$-{NIY~wpze~>fNJi$qU-F7AN>#@RL`>)E
zeo%SUU;xYLI5>QU)S|%hOV<X6!V7&%k7|VcV8gRo%LQ`27XA7AZd)A37B6Bb3F6bC
z9T<HAG1&>c8+)8*7>&0IWDbX&ZY$TfQsx|rcbv0`@^tcc;CC|-H6CI3E*4r4*C-tL
z-!IHXPFYRE(AfJ)pbjS3w+>>tg<9wbCz%Cv7<c0V{#6JhtTje`N#Jp%Bh;&fLwi=>
zGU8baT2o{YD^g1{vHHH~H+Q@vS_5`oq<dtEcyf6%-rgZfSSau;WHS?g*-A4!urv3p
zHWcCrw4;Am;YzQVAMr*#EhdY(EDR|A&WL%{44Kh7)=~h7XZTz!B`{?2Pm|~;76ucj
zkei<Ob=~SwSDfPmQNkDG?PiHpEkH-$7#K^$!sj&#sy@%bbaP`{IMgT=Iu-QyN^60@
z8!P<e_$}i*S=*FFrVPeLOa`SDh07*j)b%G=+RGN?tGhb@j5}%AbRxZXCO7@Jv5o`!
zOjRUQqnP+2{V7OGTy-<}fY%norvSRm#v&dP5_xpaK&2_F%X3{T7CTP?82RRb$Py2t
zxay<JsgsN%ODm^f2Xaa_IlB+R!rpYM>!s~E;Mc1On~@4s2p~B-m<CClVZlHt{-w2A
ze7f}8`;A~+oXayd#45K3;+-m+f|fj%733Inv|wvG46W$7tRkjCBc&#|=0@p#xAgcO
zs#(F6R5w)z^q%+|3CVnmZm5h|#tfW!L51XBoCAm~(`6w;NIi%l58RZ%!dAd9-Z?C`
zM6INF%i-JgDt~}V_FMR}gk_?1SG=ktx%GAIWHtdxp+{4(uqhegFgIT^y^>QR-Vc}a
z$c_$t1+9*<x7czJI_8L=u@pw!oEvIOqGn$jK-tkp4<wT3*f-6U`CG9?*~SD%s-71}
zxk{ksU??(k_BTTd9mni1Ff2U~#Xsv)*J~FrxTC0nH2QjcdwP6ZLR#8x1L6hhBkBZD
zA@ITE%;vC^5XF=|IYz!tcdbjYW#E+*ll*fR-6}DiPLgVvl*Tn~YgAsTHd!wM{z3(X
z8+$EjAu~LOTc1bIUpSe!3HozezLmv8Bf87tvClN~VF&o#WGn|k0V~7qmSPZv;0_D4
z4Ub5I5yNO|OecswmFNT31Q*-O;6cOt5n}Cz)f{j7EtP5e)&`4YNkog$oG46zY2?da
zie6{yb>sR1ij3EuKDx%?#6Inr=xrq!RxpWL*xYf2zX$PjbK2Ga>QvhDOR&Um+KNVY
zPLFld6Ch9ZHuHSfkFtlav01P*D&lYj0OX5i!93pe=TS0pK;omS`e33Gc0nnqc#Z07
zPC&oMCgkW&*XT#1DbO>3Z|t<VU6(B9Y?Vwp>4RHbE-x=tT>hzkWx9aRL01b>T#vuX
z8GJQUQ6l=ue{qA8<V2psSvlo=65!qtg_xczbVX{@wt+&mrV}9K`McIkp+r-Msjz&n
zq7Et=NRPoKVQb^hiNmFl+)ccWEDZFu(`JBNC{O&$vE@2Yj<X$eXCV|;1SLRvXFLP4
z{ng}eQH~&V3dTb0Df^*tom~RE{t*R>zFcjqWAgLIFF$;oVN_M%bviNPeL{LpPjGCK
z&l6fT*m7UDy}8GVwq!*$kzZ!@XeUp#K*$%J6^RlN&Z0?S`J3qGo*Kc()>u4r!g3hW
z%#U3<pl?67BBnD4&-bVWt>T><WHkVbl^Pa}xG|48QbU|?p4(9*`kaEIll76<Z=<Vc
zpmCp}pU3b2ch}=;6{Y5i<FJqS*6%?NpI8Mv?_O@pY{(c1Tn>iF<aaYNC;!IS6^2Ru
zs7W*u1zB$BwHiG5QE8SqPXyfgbeK#l`zkSQ$|wU|qtTd}%@PC{cJwx5n_W`3^>&Jd
zAG}iL7E8~W;7!MKg!{ey``IWhT}Np5oSi?MTUnmsKc(7R#*@E1DO6e3n~gCd|K|B?
zb+YtG^O9~elD3WXa|NtdR2Hlmz}FO!9HFT;N~#=H@|Dpr@5WcBj*Ilc6n~a))Ponm
z_nS>Gq2qQM5W)M@Hx(p`PeEeZ4YXNYw}IXn{y=Dhx=}y(*%GBerSl@@&?$i5J&x(<
z8dVP#&3uhpXY^eG$HKd8uzI7X>UC5UVsQXSs|<xPAQLeQh4SDI!2xz$9;~_!L*r+;
z6I0x+8~Jlkv}0A3rNw4gq5_1N%)3E*KD}nq4vBmE?L`J8ca4Z^kd`7^B75u5??zSj
zT<LSE&90pD!dZuT8UUN$|3h!9W7RcPOHo;4<0EObA!s`26U@chSm6+qTP1LJ$e5G!
zdl<Jm38)@E=#Er?)xO5Ps&eAj({_y!z;OjFXTJ+IqW9trPlbu({Bp=u6oP9Ux%ZH6
zuGXV)6=q^IgW6>hPlL*yam=bj!st$;Sb4NtAB0%mzA*&kQwtU~`_<W6jGEc{N3^65
zzN0GJEK||{I!(+<<fL(&ttRBFoybS7S>Em6^(;5(g(EfOzg4Fpt~9ifbPeb3qYhlD
z<n|%yI>F7-FI+~K^7ckVns+5nx~5sfI)_kXRowbX>UT$<RRUcWG7ZiSiA|RFg>WDp
zVJ$e^*ublJzhV|Gmb!uO@mk?Ij>E}@p184KG7$VkBWi>&MsfA*pVu3a4ZYKPt618H
z@NNZ6`halm*JB{T!F98`lXDt%49ZHGM1!hr+-DEEJe1|X9fGwJ+G`TOAHVngx4FSi
z|JJ>;OS@h5%^j;oKwgaPQdWg3xOFd=vRWf&yY768o+-(%tFN+Xp0NgHjL*k{ed02$
zOH9IdPPN43?(c_2RFDFSS&(w+>~AJz>o_p};ZHOm<GEJ+Hm9joLsBym9!hW~Sr}AY
z_zYo0)+Pe}bP^A*Tkz7c6MpHG)&-gSXj$!nXy6L0P-z6X7*BV#^K8bd#>Gtqt1M~=
z$GI@5hWZxO;ZqqZB+U%Y61qpWqm3=Jjvw=Ny5Bhdc(+V~*?@!585)1{$HC?J*Jy1W
z8G<p7JD|zT=Mst3rC(S$k|MzI=ld3dflh3}-tc&OGp}=}#hu(#A_>-RNymBY7H8g%
zo>#xpjr7r2Q{Ba9Y%W*K5d4Y77Xhf(qwFDdP2<vqgS2V9lAWe3<(;{`Ozqab5cl@9
zizeGBqk{7Q)85Enx~`p17+z4PeZ0BmyeSnQKQ^Nv1k6p8ltO1$EHvFhFygH10-uYY
z7iG(z{qwP0Nh7Hyetpw1riiUVo;?X0>dj~^)^w@w+{=c#SeP!{ofj(WsMptGh68EI
zdr^TeC#N3fTfJ^D5q9SH*<Z{wqthTH7g&ZieNd)8)qqr2E_^2%k)HDnSv7M!nPznN
zNC>G@t+=8^G)=L}fo}<OlF!kkzjYo!{yq=8gT4UcTMGs-v^T?eLpTx6@EwQ*;WOh)
zNXOTg@Zf?DM<Geal?KR6Wk+_Hm+{5TxarO@$jiF@%E^E5oM5i4{XGS69ThU%U0%@<
z@J+3ulslw0#bb3iJ=iwWonlRBC$u2O;kgHtoQ*Pk5~F&ba%;b-T%Lbrc{>%H<G%K>
z7nHf!)lC-*`;emT7*^`3uOh~H+r(%r@#&m=WEy-1^vey3TvX0Ja}+!KTx&wrOHawF
z!;&DB=S8{h{&~)PBH}nBX;`3ZB@Y_eRstQ0+dBJsHK`Psn4#)s?aas<s6Qrp`3Mfd
zD@6bb3xfGdeEZU&jPPLy)FZX=@o=W4wLdWsGr6vx4U5xFe!R8ytM#s++>ilZvO&>d
z4S5~*G=vxv$NUof{KxTYgks_<Gy9#x>nSpeGz(C}zt>k)iAuv~j5S6XoCu=T?M$q@
z1p<A4Y+ku)KGF&uo|V`oQL01Qk56)0zS9$_EyJ*d;XfDYGS`Yb-g1j8<;a_Q%6PrQ
zMzEe7J+7p#f51ndskX1-<WH6(Vs*LfK`F6EZCPW1^cz&?m%@F6ZAcy*6+*vwRGgg*
zq~g3iFv-0u#*Ozpuk9ZvSl>C%dk_H03U}@1LTT)z$8g8x;YGA~na+U=3ys{9)<cY@
z*I9^siIsS4prlfFf%~v0jT?^Gy~;vs^wF+QO}Dqz?ER)IQXWMM%s&jPBVE3po!NP_
zoq`pt08nK|d{*9<D7a=N3{ly8fEiR@fCIFttO|$*sg*UR-&2sjAD!I<ZN<>B!<b|u
z>CxW%Tgere3we;1P%Mqg^7N6uZP4k(Dw76f@{SE6W&!M9KUoe_W%hq4yh%zhRyQI)
zF{B1kO&|VR2^*TY!0(Sr_Soh7+yyX6Ee_F+Ems<RH<LXk_2zsq9pUFKitT;i{_T=9
zo8P^w+jI(D46>XxvFpKJnPswZ6Eit*@;HqAC4eHn0=9#)NpDeQya2%C>;Sr0<5r5E
zJUP5$Za0e`sCgIIQ4=Y(dSiZY^kT=zLFS2W(g#EO_~mKYXG#9a9sf0k`sr)=@c`JV
zqSXlP3_OgfV!tZ|dwdcxvOQ?j(HVjBWh|`Al0|Bhu@yYD#q3x?7rMT;)JOc}wKmXO
z<&b(#@2Bly*$tV*8&Iu^9wh;1CTl}8dU_;;DdN)NGA^KO`x46U+3d79JYDl86rwkD
zew#qvQ%Z0eTzmrTvi~K$oT#PMCC%YH&v4`Xx2{*Q1z&s1F#W6Gy0|$D4S{Z)4&!>6
z?^HDt<-mXT1C4>q^Y-9M?WtF>#Ju<|?N@}O9lGO&l2bmhpTmqo5Wjv<vzgE+v^zsA
z0vLf`&q^RzC)HZKL5(|LiF4Z-Y}^-%>d^#^A2T5&9_^Oxr!@r`MPsmY_kS~oKV35{
z6`<7bs8jU=Pn0!=FG*>QcD2I`)5bcqu~MQYvo&TPD6SKDJfqths8M;zFTMuzxl}M4
zV0Q9Dybl4%umNY>MFWR~Ov8n*J(<4q$1JJUGPL(23TH?<N<;PuadOQ_NqWi~Wo}&F
zg#c~c>0m36$TY(b@C-2V<uGco&REFzFN!_~H?%^TcHPZe-e_NvR90OGE8+j*7%^Sg
zB;j=F5ODr3oP{{Jg}{4s1;57NcWp|EFlu^5&fW7}fu798b8OwkEY>|Zi@_ZvBH$Z8
z97oWk*ORSVm!UpEn_?+&RJAmR)uqeC0;2n?M3<mizBiY1@8Eb4@&cDg$BOK`kUG!4
z2Rpz2&dkZcB*-7l>~`Lxwv|5qa?@R?_cr|OxEVoE>%qx1>p4kh!nCA=8u{;$jr87B
zFoXy3->Ld%e@w?}mFka5kJO+LBdD)=L8l?IY*?pPH)4^(>lPup_b|PJ-&5M<0%eR<
zx2}g&qPYDQaJ`6{{vbg0dk*Dw)!yBwZrgczCOq2!boQp?ZzEmhq(y%*NrLRUYk}gb
z39@{W_3pmT9d`~%d_14?W?-JezIB^+TiA0+m&t^YYC$vL<cr1-cu;Fq-&nPVR2KbQ
zH(^^<H?@ASPu**t-=V8%#N%C#R<V`F4tP2b$h@RztDa-yeYUYX=6#lR^aY-<C2Y%%
z@`R9r;jmbOgmjRb<0FqTot{p_+2pwDU{Y7I;!2{sgG*(i0}zn}MYtWxX*}CYw2n}j
za6*Y5gtletjx}<4tChO!s5A_O$McpFrTZqvfCGYs!nr`85?09rjK(J$`8j15MKvFa
z35$IM$FU!rQl-e3MlOkCLd3A;L=rBS<_0k>wteFNHSk#0GQpo%W5S(~KQz1o1!yM4
z2A3Z%qrwQ~d9D<N$x4gc3Kfd-0>u>C*I%&zR0zi`$mwCui}t}#QZmHm*5f<lB90*R
z^S4`3XuanwQq_cXwqP(x%U;v8IP*=1Ac(I`iRpS@&AWYl4EUs7ecN9|{mSy5)3XiL
z4>0ez5Ml%0Fg_#K@;R!!3sh)aQr38Hts?t(f*p`4&JqeJ4b{2qEKv34@G&IA<0`nj
znsjs!pNd8}B~7Xg`z-O9O2A#F&ij7aDTYyFP@hoQOh+}KR9JA#ZP*|g31|CkhVNrM
zFU7Kg%FZ+oV>@~%>`(_A5sXwlT#Sm%bKHo=FcN6nNG&+Lg`y4ycy6dBZ$;6tz<7;_
zbyF1ATUoxf(YX(f0$011pEni5rEDrs=>47lmn$%K5>l=TrGKwZ!@3I#@}28AK!o{B
zyantaE-ALa@9(Lf4Sr(t7D4Gc(4EXuLy03eNhnZZHsb<FgWu*f@+BEVsR}7f8U3D(
znCn^Zm1;=9E6axaz{YED0uMfS-?U6Lp+~UHVLQc%%&ROG$%chG;fkY{WtJrTO^qlS
z72|F`R{i9Aqw;8+3*&ig^wkma_N3LNzp2P-S7dl675a*6Ew?r>mK4}9h%iGboYZn=
z4Bd56n;eIAx7IF?utMgxDf=ZZnT@yA*VVB5TlqJp*P*F$J&lhEA>3t#Zl?k}f9}7d
z?0a4#-ps+3wrqv3G>aln=e1d>i<|hL_M8)fU`a+C5fW|I2gbjmWBlF;#ocYyGt{Qr
z)VL<c3ZEshK1Xbv#GA1DHi4a$a(&x1CBFIkL%MaCp4p%l`ARbV5^(yhm9}3UTq=@?
zkev2+;o&~t(<|OpEBMo>5goaop;*7E6UxL`Fk!n6O9>t}(ENHH<B15QeN|f9OVb8{
zPD*ZX9P!0+=-`JK-bVx)m?t<;okZN9G-pOEZTro&9mC!<C>I)8fcUPJqL0<Pj68?h
zo8yJpD9wf>WYe}RV7V(uK{noYa#q4Y^ST}i{$Wm8{epixdJd2`br;Ynr^>uh<NTwm
zS+c>$uYj1Hc9`qs(>10s_n4zE(e-Pl{+2!;SN&1P&I;n1YKq>a5HXYIxglz@<uEO=
z8*Pl-_ZUvO(AB`Sy9abFKuj|+?%-uN+19?p^Av#LlPVr&lxv#3;249Ks-ObdJ-M#X
zWEOe(PNGA+Rke(Wi1{2U-{OS)nb@hQe@s-<?H<ct=rU$i|Kr;Pbsq)Fm3A7>fIPfC
zCB%``rya6LmWZR8{(iC*#878<(KZqMEiesgwnWzm6(eV6v2fsO1*QoPIg~gr{`WQv
z`mO=%SXBLU0Qrt_U1DfNIwROlhYlQlcx-lL+C4Sh{o0-$S|)mKzor&oEYJwU@L;Yh
zUq9Fva1yoGh|UZD4!+-^Px-@E&`-N7wK8KTRB8T7N?Jfkbw|S#DNfr4+IL~wv^kg)
z;F3!f+D$w1m?bBRR>m(-AkPw4ItPwEHFIc&TG*Zy2I>=Ze`H3L24o1wNy}=pH-;cS
zY*572P*yh&3S+7qPwSI%?7lq^G>I@+>s>dkRrL*kOZp~3Uj*(&b@8#HEhx<&DBkBM
zn#|KEx#6VESVRm@$q$z-tYo<mwT_sm5TstG-X8VEGM)*KvOz>%R~(r~x-<GW9y#lg
z`r9ZH%nm>|yfPXqW@rO%^=O}g#OQXxAec;{D|ZhRAkgu5aaJ5r6T@<Hx3Pq*i$XyN
zbt_!3fJI*M9cf1Bg%Kn0@V{r+&#uLTMEeLo##Z$|SRca~?s++a7N%H7{5I~k9bS+V
z!-V8GF^JSg5^&q&4ND5fpa5f=rD(-!+z6>eUYMr9t2OY7K(0(wY9_Xb3JzwbqcsO>
zPr|PTh7ZtcxY0bSK2{YnA9WiqubcB+%9||}2xa=DGt)fwB?G$nssZ)7ViRguQDpGq
z^GvCU0YHnJ$}RgLTINuHMn(kQKBbCe`$X}2(n0Pdm}RVp?Cxu;HJ_C-{@n~Qnbp03
zk3*x#@w(Q)7GiRUNrJ5=d>bmJR{?%00PR=gky2hvQA~i$X;7!yms%CX<*V5a(r5{o
zYC>XDa?d<GzDVMIK&kt}CgjchJGEHB=So>aRN?4YXLe01&Ai`vXCs<&W9n%p1zzpV
zj!fF*mdDdSS2IFHWbEHEGG?WG(Z7eX4pr!i`Vuc0;W&E7Ll$Gp64;J__qmI|i&jI7
zMT{$iWX@)2H<sY7pqum1my;}v@?5T#AW0)?rwe2Xhm~s5dKtn{zD0W_7%<hm#KCiC
z#>+pwl<3<Znk$nOCAEh~d!)gNW8Wv`ol+p6{M|a1d8zz9ghtJ9qkRI{t>4!#YXD0{
zQCW*WWH}K(5~6G$26Umo#x5f5K`q$c`N%`Xnw5Xm#|j=wK}#8Q9eGW|pkEr->(J>e
z($`M>r)3o&QslO>YJ`OwRO-gcrTfRB8SD=F^C7P<`+KffpMeU30|;ARLVaGK;OKXv
z8^USPiAy{B17{)*pdp#?%YK>*M2&i;(TsvW<L<AmY#>=m!fk4|ucjb~MX~bq)Fwgs
z9Y@FfJ8>Wy{ljcGUvmoD!c7n=DE*V#y$@wNZHxikqY~z)1+axq;GE0T5X8pBEA=f+
z5I>?%7L5LbFtr|eO!iub@w`mqDwOWJ6eF|m-45}O%HTZWUSJvy`EkbHSv{l(Smr*@
z!O|H&h=*9`Y#vWE=OJ2`SHhl?;Tb5?2~id}V42QXFh?DQkW^_jZy>VvD}ozsK+kk9
zNUg>IeFS)Z`;{Yi+P078UgsNfZVJx(wbJMe;v|?LKyhhOHf(Awt>2}@(I&HVO@%$^
zZ+>=W3%dC<ImFDM3hp-GoODnLd5g<t1PpklP$-il<GiWzVlkZ9GV?HYRO_=CQT!_;
zqovyJ1XQ)}5Yj@g`DgjFhea0n^*zugTs0=J{li^Kz%3q#u;b-lKvQH;PE+bgMC(F$
zWH&Z={ro9yikKKj)J^N{hn+x?117bJbN&0*V@*a1dBsezcYwlLqg;3|%roOFFgfd*
zqJXTi8(<c;;~DE}PqEB(+lXx}=d;HFZZOXuf%n(KQtEQ%@I^CWgw*xB2LjoQYX|U7
z#pLwLg4DX-Fm@wvljN^Uny6hHJEdc*@GGksJMD3DCpsf)t7~^lDA;iGZlVnEBNR(~
zl-p@#(XTI{m^p|k3=}<w^|bki`DB1RA@YK=&vmDRe^w_wX786r;F49bc;U~*8}ol9
ztaKIt$mcjnG#1(y_oZw5-oBSicbh56{6qbU>fz#S!ar%wZ-h<6^#*OBh;uxy{*@MM
zR9^qHq?r%?^!Y-wjvq?wT87@Tdk|79=ilE=tj@uHZ^}9~IQo>wq6x;lPqrKhNe@Fp
zLks*=15IzCFq;96S108r%IpiSixycL$`b=x<meM$q`Qabxg3#oUR1|>{4+KfVQ=1n
zz-3QypT2-pi0w}EwVr)`vxCRdE!?HvUP?vK2%*ZK3JggxXUfg*adtiwKf0TO)Mx8A
z)04_{A%!U25G0uUeY@Fs+CF$%8TuzMhA2wT1$9^rx0y<1pr}C^U>aFJt>%?*N+LA_
zt;F<C!I=A0lXv`OINj^`Y-wZ2;fO}DM!adOZZy@czm-e@4wfU^B}t6X_hOuE_=O=l
z_sRNWqgt=!pYy35XBKt*W8CT~I(N-_R;LN#^^%>IrrYPo`A6&npCW829sSmi#=9>d
zCJ_Me+4oH>{z3eh@mV|D-Y?tzizI=pJ6crjr&=mw?RGmu|D3Bz(bN^9n|!cxEDIp`
zkpSp!Q9;gJnkmPr{6>A64R70|6a#UyLEUKD(Z5g&Ud$#+%A-hjhDlO%5Kqsr!L0g$
zLZn0$fdica!)<Y4Z%P`t{^mf2?dK}Q%vS8Xe7zsnt!=S9*aJK-%Qxm|i8Y1?rm>jE
zNTJLIOdcjcVVGK=7MDCW{>P92H(%dTSvRcXS1UXFKfdrk59h~|SvR)4*%}<I;rOZF
z-`Gs(BXe1!#c4Kd7fW#bvzYpjArN1RWD3iDaRXGjzLWPpOJl>r#j1c+@at}IH-72V
zU75g))<TDTyAR4J^lggyc8zUqF*xiiSN)LlGW*dycbP^t8GITdL?Fz{T3LB1rUgvD
zo5B@>!C?DdH~N8s%5n@<w4AV08E;(U;Zbz1bt5IN|EOZNp;Sh=eh3%6s953_fVoCC
z^c5(4II?0Hp%)Rss}c+~v7+HB>lw~_`7`h2=Vi^Cq0RJ<Urf)=zpUs!vlYi<juIvX
zz?WN;>)5MTG@>B)O#=l8X9j^NTN31taIur~E<G5)Z+qp0*>Is0sy;c65r67kUtE_P
z!73;xwfbvK3-q6d@fCoO-=M<zX2c7qkD)CdQe>K{8|h=NEl9*THQZGplwbDq`a}S;
zKY6VsF>YstK7nhSiHsAhChbr2Z}x}l54|^6wu9s4@qZ^I$)uLYh&ai5<^-f{!KGqb
z8d`(gIOy3m@!}h_I;thLSb^n^LCa}S)Gso>41dgg-bM%S8t77Riu@~ek%+rPxS>Yu
z-e=u*=DRHy$8&t3U+$<h9%oL`l7PyStk}m?a+D6)X)r4(CM_8)<k8IUh9OucY528k
zE~<8@nFh`i*kOG*ZxUWL7{5khW%bPC51cpQDL^U(xht}r2sfT)#D7flqIkRJj+1iI
zlJUNo5#*zf{NXPR$2rQVa-7Y`m}=$aZ2c=^05+m+Fq!o2ge|Pk0eB%T{jMKzUG}V$
z&yK>7{(77g4f`_vIeu#fVd00j744XTA#2hySx#yY5+qQbXKxY$`*A{Gjkm<`j(H(i
z)jU`p!S>Hmd)Y?)Dg{@@d6Vl+%W&Vr9}yQq7OjjrhgPYFL}y0l^`9{F2ev|KU1C;#
z;>&u@V+KN5b6&luHeCt;KFVfDtM#7(DL>u(ifbQx3RF0{{G5EC4=#Z-u^5q)L={Um
zi5UbFivpJ3h-dM!DH}ad%1NRV{o=yAwB%W4k8z<eMvdcd^~F_wKAfoUn)_V<ZOY#?
z&e<ZDnoDo38R25T^eEvLoDD{O3hIR=I}UAvCesr~QQ}#?<Rt;SXd3OkpW|zMj#I}V
zMe0jBm{DvVxV<Wi;G;|NSs8dye;aO%NEhRbH^r7AGp$2;gR=JS%)(KFFTr${6j)10
zf+Qw*tT=Gno=JKHuMlgG-uR~_6|X!c)`A}Jhy3X#9!<zAy%yRe-6Y~e?E#r7fRM-B
zcd9Nd5p}3lwIic=hQWfD<f%g{S(+k+gzX|0kkR>NO@)X!h4Wf8s$;=G_My|t(pK?n
z5Cyw_1R$?-x1WcuAMpPuVBvhP1mh_I00d9}X9aBY|Du2;`>zUECuajI6LULjV-v^!
zZo*vrzeTVl&!ZMG>i=RlSP^<pD8hNXUI0CzS)=p=ni<x60cc`+tSMpz6|Y%E@blvk
z9}$ZAWd-PZ&i}r{N@%rG*SItl?@f6>e9ZZEE1r`Ie^K!?)Qs<7wwZO6g=%*<6<=iC
zEdJ~IrsCbI)=jKgO&Y81aY(Uf=^?!qG$SJUdU+FA@%AuZ06icN*82Xp$B=2Bl!H&v
z%)acmo}|K3fp5OzR|OMRMQI6@!e+yK*;u%&<S(b`Am9BKQn+@2?%WwPowANq79bV%
zP%XYE{>)C!F39_3*|H)@bpS(LAX2q*G1?^+=4@rFHN#bx#ZcXHvWy-1MP{eIRK2W0
zTcKHK5qzDywsN?Ow)yZ?W=@$?-*S1-`eSMUnyDtKb&w0i{mgYWB?fyctCe3v!k@^U
z1Zv+qPt&`Cl_wm~-FWE=L-kHH6I9zpNeigsmY_H6U1%Qs)?mSfJ?ust1ZsYgScXX<
z-2mSC?exP&W}gE2)t9Wa?MDN;goe+Iu76v_m?CrfGRqdA5ZK7DJiIfCa1*Du==IjP
zdkL|06p@K-vq>`ne`G2X9@G)GSE9OD&bIlemy>Z?Cq+Wk#aCn*DA>m<Kv;%fu;yAT
zOHdJYtkB2bONe|_MwV<g#)I4=uu8Iw&#Bm{JgwVnLxVLV2igLifPJ6DA9n4MFr4RQ
zCGP83w!A(B&Ijlzc_ebc&fawflh1sM!b3Y)QB{Hj#$?0bgciUJtsbkA1K+LaWwS;E
z1-p_QRc=_tcIiYg?JS*{G&w+Kp)@pWeIad;jUOSNT?94M)a;o<YLo#6A`}dRoxU>;
zF`OhE+;z&aBz-3ecWf-R-WAUHQ=TRC9aEN03NHgv(86iE#?}^opA<3H@Bh>CGrN}p
zLtL|rut->ePJt=ldm}T*1ryYdO-Hhh_k<Tv8eBvFN@b%oQ@RJVw=WmA2t5n742TRm
z3~Kd5B0};GM}?XbaYx)`WSJ^nTS_l9c`<ZhRaP4t4<rs!8qEWjr^m=yb5wa}q^hfV
zMYFbmqrK#~R4EK0XzFJAAmdSVpW5zdZG7luVR7~>85%kbtr)o9)>)|dPUVg7$>+m^
zk|-+@AbR<O7)y{++)1yj8biyy)%Li_=nc)JB4i8R>lArCa0T(u1ycdeF3}YspNrd@
z4tY?VUfL2dg=?U%!x|PAZa`OSsDYrSQ#H9cn!LV#&B0;Va>0i_olq7{51<oDX2SO6
zAXBakm~S{9L2)}Cpd6|ubw0cX8d<y2cw!k?Qu}bxk>lrk?s*1ht2240=<amZ%Z&mN
zCA~V1)O&|~MGr#KHHi{a-6!&GQZkP4m++2MIU^ygXj{dWwRNz6Y54$fm8tD-T8)Gv
zCB$e_t~7{G>SPLDjv;<DV_0J(8sI2cDkYC~up9YqMAmHcyaEEAph=6ERxtvCsuY4?
z3AHnp_13V0fY`mVICoW3MOL$1j#{Y#_?dKDYopl`&OGkTc$Y?T8jUjC6v|q2r$?!S
zE7x5!TLDZ8R=H1RWEmLAYQlx^-J}aipIp;{P+6Q-2d7L#v|@iAcFt~L?xo--%ket>
zPid_L<7$@Uo4TbvO2IeX-aoU{hunhizV~)XFvUdfN!6<Tbc9t$32K~}##MxpcOaSL
zx;_47S&2>IOQaaYw4uV)2B@6P$<u!Sdq?%kmk{jFe2gOjnJhx#84L~*UK1>wn}&Nk
z5t>b=F}!1$KYe@$&Pbf-GBg4b*N0knC@M?5otTy1XczIwUF_QENJ^px6Z=wgI>omk
z7d+>u^~OpgajvJB+CwFN46;)ZZ#*5H+~fZAa8()eJ2?F`Z7jGSbX|ku6TG}=166!_
zU-18dc?9rf21if;0A8g38Rq|2qr-m>CHaMUXA3*q{|@p0v(I74M=FkZ+~HWKkFXy(
zENf{{H3{htZm{Z1eEOD!tCOerDZT%0%3ccUP;|JluxNuB8uV=~-=8h^`2Y++AFR_s
zt8e7*#Fj9=DLupljWum3^=fvNrM>Ip<LB0y?-@OnC3sgMKHOZJ4}qO%F&FE1TW?qE
zSg)_3zAE2a$j{Tqum!)fhV}Dn_Hxte^WJsV4IjOwPETt~m4P3xyW<6XYe~JTr*_;-
z;BRo>hrjA)pJsbhOH@8M?=nknw=ST5Z&?)_{Xaa9Ew)rH7|frB<;tLX%0eYoIe3|X
zKS$vo9XDaBD(}5(m3Fyzu~V$M6+%u<81J6zcm`HMoab9B0|I+uWjC%dgEzDIcpnL^
z&PqNE<+j6iR=SX_``?0HejQh%s8S<~r?Hu>y`YM?VUTbSSrS)%Oal~cK1`LcpZC3I
z%1df-mOJp`*A9e<z!@W!oU9+m*ebx|228I>-`7+=)_7j;)@5#GH*K)n%Md?nLnB$L
zY`~xS3RdEe8)0=n9UR|IRk30`(d|cSN>0I4XJI+#`X){Z;9D`3HJmJrF|9sPQBU>g
ztK$lGUA}(rx#b`mm$E-|U3>(Byj8kt_Q4i@!A+k+Pe@}7zsbDN=1zPuU+opw;4Lbs
zpP<!Hdb9k#?P&}6r{3T^i~r8xZ#T^JT=iVXx>J{S?UvM(YHW9Z7zF}mdx%uT7tihA
z54P}JJ&T^>c#u)AVQ4+f(<={}mkuDjJ>`S`4*+05pTB|&i+FWJO2EE4z14;}@o(TL
z{r*uA^W5!q3x7Lk;Qck%pbm#UTtxTJzwL)#<1PHue!gx7cr(p6bp0*7lRfN__QkJ+
zPhb1r0onDiZD8RI?gX}r*NLy0_zU*gACW`oXR!G-+v}$zewO&-m+%DbcjafNHX<ww
zj%sY$!(Oj>J9d?4{}b2wtm$@>+TmkV1H6I<1s_Cl!fZ}#wLv2E-Bw$EQHB+Jc<JY?
zc*`fN)UcacSfsDU)AxJe&#IsBWLq`%Om%#$9gvs)>aRg$^^bf9E0%lce~XU|@0dvW
z$-4v4&YXu>hQ#l_fp2SE8CKlVYexQ}7oZHAk^E>Y^BkX5uhc;|#HUCtV3r0x0e?CI
z)kcyeqn_{?58G)Ndm~HSi*$mftMLiFRNbQ@q5a1E1N`4Fd1GrBMxK<f^JDWW@g;Rf
zP%Je{m7xJz9*9@%78P*&9m`(W-`)uzBtEMJxDVV%S2uiB!~sVTtDaMO!zo|EGeQbf
zdQ<5~_!;~a{v-HLqT9JgVLl;J;k8*hsp^e*5x=s69NC}utq#X&P;~mE8uYyiq&J*=
zI`qSlcUlqU;c7M&h~Ni92y<;U9oNWCy9RPc+wW_TJtU2~9(M)&Gibin)3=X$ogfNM
z``lfe*H1TmqEs~*nWS6L;-iAUBmNYu^oj%&p8MxcYY7@1@v2bwqomfM!p1*(Y~UCB
zjlE+$(jJz*KYhDx_C^o^Tk*TF%(Rty#(b!gYGc&9smU`n|64uW=y&jJfc3XpSQPZL
z(|@8U$Y070Dmg2evNR*@Aav8ZEkqW^OAX|>Z-51EMvX@#b!9(UoxX#g9rcmOwL#jz
z^?)uvy=U@y{@BBg6`3penM2P;+g^2`a_OC|BvEQnyf8L{ez(<oO-qo0a6bX{`c9$c
zr_r*wso=fC&EYTMQos;tfOno%zd&;-pz)}`QlxQ)emAHV3Ca?$1D!CnUU2Gn^g|=Y
zL7kvv1uA{|Vq;k?xJjVZ&?3KkGlZ;-w;g^Js6h-I{G07w4gKGJ+1*q>149zU8l4uc
z)D||{R$$xUZ(j%-0!$hB#StD$PdckRBJ0=9W79n_3-^{+27jCQmDeNN=WGybUEitg
zuaTjVXmIy;1Br7uubM_8_Pn+9sKo*(eAVOWJG^@M#{Qw_|CPL@mAnuuycZq3(Q&2Z
z)bE<{NcT1Ncd$qJDrmqh@<jH<p%O&3@Ss+S+40CyvHH{R{ssOYTxvJqGXi#J)o3Ix
zy{A3gOkmk*vICntxS}Kc!U$@klHrN<+v#9cS8lVywj`c6R%MTbJF=pv^|l%L16o=+
z_Y>-pORj)5ajL$uYTgQTqe2U(V7~(|Z`}5GAd3_#Fcig>(?E*D@9}ZMOQoM}*oK*$
z=_<(zj|JB`p5AxUT9H#$(SG~J)Nu!EHE=hn<Y;er(k&T*_9wmJ8*O}r^!c%P&#>gW
z{jah9!8y{yK$4i~)aotxXJeb&iIwu;OT&5S&5<`P&KyWEmYjHVEG`v2dLdh_f+v}}
zmh+_3@M(=kAE_x+FQ@-R(+`*(&A>{{XzTNq3Qf)4nY(x$!HLiRGO^VgPym{>A$~Gs
zoRDoQe<^3KL{`@;e^t&M_QF}CnFXIy6)3a`o{FmeM-`hSZ-j3A;m7~<QO5e)t0Tre
zZs2Ag8t|Mzum~IH#Q^FGYzL4wcv}2x#UU8BZ|v`tae|5WKn|$ALb*tHtDOy6^pdih
zh^(BS!KZ<;Rs4N?uHgdY1n&ArWMd;>yn55b*!Vp9jt!CETsZ?dySvoJ`NhPplTrR;
z!q8TG<A0DlV)VZ?Jp@H-@J^6jTd;YC_yjsVCE68t`ySpC@d%i2{gx>5tcp}UNQfiL
z1lV5g#$by({b<OE_V7S9A4&tTVGKj9CQTyCa65Nk_n|nOT6{G3gF^eB)EE=VSf{*r
zrRj!1agdE_bZU>zuT`iVxTu_%G-}iQ8q9@(yr{dLl=11?BiLf}&y;8B)hCj2>?NrI
zqTQhDsjIEUjQ{lw84lZNMCY}RuD9x@N8O&gCJVGrF@n;vVSpqIm;+^rGnCLuy{A2*
z4juYEY4jslSXQ0isZpQ3i(5W>=*~nODU?Vg0$8W4T{N~CUpq4etaf0FEy!N5!krIE
zrYvf4qhhwK>fjyi;D4bd*Nj^-==O@-joKP&pj}501dSIa0ry+?#2iEVstVjA_;_HU
z3D!a$$7`>%R@(Bh`PMO{!<HbtZMFBY*a3FAXG?&h1Z*DSC#}q_i6L3qnLwr0;yI6)
z&a@*DOTtHC__Gl*Tm=hUcBb3-GG8jVOk)A;(eJ4!vRMyIQMBPPFt4^YmmmV0_)D;F
zST?x;`_vlixaTN}F*5NVgB7~%ND9P<O%xUdn?b*VC(%1Q*H95<d`%n#6w)2-#;`<W
zuxCDdh^+@H2rnb*b7}8j5U6X8APm1@zG+Y2f$?ZWpE%SH4;Zn12miSTyJh>Jh*e3f
zZNTF{GFdm^L%rjF3zld95z{pIrZY{#FaG?^+mABmfgLov&f6D4poB4#I~i7|So44{
z5mX+<po(9PLn9O|w4Re!9Q0X?Ahc3=j+-c42Ioa#Nw?jxvDZ15#ru?+@<o<yNpsmC
zWbXBwt)>=4c=C>wJh?5cwgD0alCMRf0E`GCs5_3&s$YU3(6=@hV>nyetOZ*mbXIw`
zO>pwczCh#x6F$qQnY4XKJ+Ew6Z9uGoaf5-^y?#V-jM0{Df7ly-A5QOgAapiB(&k;p
zW<xhe-Kjl3IgrX2-0epj#r4^jGC}h`6iRY0QncG|c+;EG{gDyxy)GAI6j~6Y@>^0n
zk#S;8R&x=7aIo9RGvQ-HQG1HUVRXEv^>uPfMV>5EDYRw$^W%4M2b}D@n3@eSJ>c4l
zA7qvF5{(XZWTqj5;2v~|ecj3PVq(_0#A^KcTNZSqrZ|hCgHhx*^F<1;1#gHLRbD%7
zrR0FbOOZ_dT!CQLUVhg>qDi@It*3hN!?8i*#Py#q4N}N;WHwj|5rOUHX~?^<c~)ie
z^5kLkkr&?#&NfuL#w4v+r5YWKDwWe)@K{FJ+<33PA?-cE|A$H!Y!Rjt2VS>$g2y>o
zklGzD4tp{TB~ys|{QQ%*Ur5q!XZbi1oe^7;a>0)}?sj3pG&8sI49{1b!T3P6O%GGL
zs~`W8kM-jf$NJfz4iCTh>@WEkKM9_UdCsTz2UAU8g*`r}-NXqkVD@Go=D%2`4b1jg
zZGjsdFyIubDUL?l&;j~~Qc0neHq~SmDoLA_XZss_MWn{=`k}@g3dM|%4S1D*`rW_U
z>u|LvfBN0OVg3Pr#a|455#~dE)~<Kgn!QzJqcx55g*iF1?iha?28BOsY{EegR(BgU
z=x8PH#<>feT-zpwtC3qScL3JP*dT{mC$e#6G5#kTIOcXgkp%Rf=SEuUp=Xyp?7n%_
zgRFHziN90cr2c78slp49Wz+DRnE7bVpa!=9MK#_XCkM@kr;#FHhvoqPx-(9Y*$Zmu
zp(9<E#$<H2!=%lS4Klf{WD1q^$O?zU+FVE!oBH=)Qc@bOQf@c*lq{5QA&!};(S)Lm
z@kVdb2lh-c*Xg~r#IUBzgb;{0^d{e_X+%Y3jW^G^wG!oQd<~d=HE$TH*c^Sdt3~Dk
zf*l%u>hRw^3Bmh@=s!oba%RCfo<`u-{vCjk-rVh*9;{DVu)}@2qNC^mI(t_JsRAZ=
z`RQN3{CE>BXkL`!jJ0xJa%65Ruz=vooug0(L7Q)8WPl-nG<fL(!&?wlFJgbfc;xHM
zTd2_zY&yM3j_w{>CC{_+n`FIw0h`eCvc%>hR(|%mvDWM9sDhX3#e)$%xymi~z1XyM
z5_YU!*+=<CzIC$TAN&2Iv02S4Wz*3Gajk{f2$mB1!K!Y0diTgKv;h<@l5cI?87$E;
zu{L{O`^3cr(oVp_h;bs>K>s<%V5#x^lBGlTtr%s-7W!avs?n*8AoT}}-=m0;8NWC@
z?CR}0=As-z81JMUg$##AVKEyn5-%uvyZCehjxQKgxt%?i+~lPRzb6(%?z;oqTs_rn
z%3@n1%y=I<zKnn+&}x!mXo%cDX;iL0#E*UE%9;+gdUnDDZ5!DNSa~Wb9t3q|^6$}G
zE&s*Q8*8<U7t;GDp?$Qs_R(W(AE`C=5j|--;-A?XqTPuErr)f#Im_rr);|j4=Z+Oh
zOGJjzukg<`SsB(&FpjKlgP^t#7i_}9RZ4GJ+BjqPFkwBd3zC8N+mB62=kd<U<yU07
zxWabW3MT%54%6Tkz$_#<Lq{&dKmC3T9PU6@y9lC5I7fF=y$Ib7{K!mE%O)c%k&|G%
z7$qV9)=_9*1wlQGLXe23931ga&q*Io$TgHJW-jqHa;+JOn4(L?+>dfR+PW=hYO7;U
zfjyw>Q5{sK+rkKcUyqJ;tBp%^=*+>BP~%>0CyW+zbkXO<@-aoOCvNO76TU0bD=@7>
z!8Tf((If>&Us{qeC&JH}8ji4-0&DD4RnJsKCGtIJT$x#pl;GPn0%tB>8GV#vh`^6#
zE0!UHVy8~=b1cLq`IE7U^|@B2D$vXPj0`T^hwbWcGS}zDKpubrSdu<PE+_>LVTYte
z>^)I3dILX0j>rVoSxeJNtkM}Ol?a(gRGZihpKjeAO)h(n!3^c9=xt>tx+Y=i1qb+*
zISkf++8A@0?4}%(M1Z{?f7Q8EACh`}Xu6%(UT>uEcM6Ptifh?69N`Jhem7ECpMXR(
zrIKNLl`q1eH>Z5ROa*?U2}8w2a+MB^ux&pK*cmi`)QqkQRo>}4_I{1go^$?yBxpY?
zQ~kX4NoCG?nySPNC$)RB?5UXVS@qUm7~3K}+GJ(}?AqfglxY|+DLD#g+d6I~vWE0e
zuxSGuY<5lH<d=KaJT(&i^Tx*X(p;X{Bygl^@3>@h(3pK=xeg?iMS@hNJaT2g4tSaL
zE0ZKi2S2*_$)<Y!Vmdx-xb)dHN8KSK5%E7lX^F`?PK;CTV%Kuqxz5)ba8bfat9PDY
ziEm$^ieW}L=Ky9*&3#=|%D8d7ovV&ZS28ZXXLCnXSqfNr8kclX?%TJi-rKm`7S<c@
zPw$;0El9?10*j?`vAo<$&ppMYgyNEgDwKe;UyPNL5m`2e4g21KG5K5dH90BfK0w2m
zT(ONQaWzen6-KsvJbg=Dc^OukXO2t<k|pgz%1U?aleextLb;rkcToa|Gk^PMZ16U5
z6)~>q^P18jVinlzoZXJ98q3<rrf+sqB4alL{2!y)O}d$x);xda8>+#bDe$+2CEe}@
z?9&@CwTAvN&{nTp>4{yQ!?KOCEkm3!O`b#X(~-h*W`(aniR+#fr9~)<k}2Y;$o6V`
z?s#y!v&H6d9JRQwoYvA|(4ADp0azCcHi8}+P&%zB)3MHvH$eEGQa^N?)&Ot9gMqf`
ztIuD5ngp<ORUjB%R#XzvR;NE6sqVpt`}AXPINRD(GV=;QwvOvsG9~Ja%W?4GBl}@l
zI>|F91qzpkktZ25eCC6Q*aVpr<8P7}a(DWcx=yrgD>G3~5sRc<WHRN&6H5K_s!(d>
zM2I!x$Z4|yRy2xHU7fk0i8H2s2rQRe)i)MQHM_WAYWefGT+xhHEIL}D2dUZKV*3cg
zXA>Jp=Pp7@=u=-)U}K}E#HGN7VGG^LHDfjP>MyoTZq*U^`d`?-j(D|@;jHMxgx7E&
zanehMiFy*zSC`4BY#+<IUEZ2Uj}Q3a^zB{4@qX8j(qnj_My|3ACR85@2f`jNd*iw+
zsTqv|?9mLg#asBPz@bRuED@wd@R3OIz^BBQP@<Y*(AGDJDL999slz^<DBsD3mUlK&
z;!fkrmQ#OkN!=vX@X0?QZIV3Fc&P-+gVjUifS3#@EJuRuNVdOSAY2wZhxZ#%!l`Vq
zJ?=l^UQhJSum%m?HWDq&1q&1^hdkM3ql_*WP`dD^D`WioC@%Wg4Bj%8hrxPBFdI(a
zMjfNUfl+Z&1>`^_kjj)h3Pg+3@2mS^LOsN>fF$+I<?P-dFy#h8O)ML7*!qmNn}72|
z#VX&IBjjc1jHMS7x12!^nl7ZL66xPLav2<pxDxSMmGGV=2mY7<T0~aSl$kKtjPd>?
z^LydfhQd$&)hfvsQzvmj#luhxn!;Z`LyeWzFufqQGDhCJX@52i)1q#3?Wajr|1?h+
zM?5qFGsQ0}m*BQGs$FpGX~O*WbsU%_j`~ar<<rot8nJ7*?^H_kq*XF`DLTr2#2-NE
z7Q5VYTjLAl04~|0Q{6|mXt&khVfe<hk%Vncv(=VdXQ^8cf-pQbr#~=ogx+Gy@_0m?
z5%3(0fkm|~>ah3uM0|1hS-7@##T!VKzVNi8SWnz;pGpHN`R8Wn5j)20ug5I!C3*b-
zJAkE8DkWocMh(B#$D5`DDe`a>M#QHX`u7!fq2OCUrR$joqoW-KD{OLnevt$y%3E_m
zXNy~J<3qJfh<+G+SlmVUsj;L!{Sh=wqf8kEAA_4+VqA>{TIBi^<e|Z1L$RvFMsq4m
zHfNzNaGW}RWR%{bkPP-qVLhYoMi|1<t02}No-@&+#zG5J5i6TTIx{u<dyE=8ZAl@-
zO!7Y_S6N#|O7Wmad=-ifTyw!9;NzUu%w>Bp7+0G`IrHrit&|zfS%Lo#UP~+b(|ogJ
zks4BY5-}e1wlP88?gEwybf!P%%noYD`O$5xTgWI*$AVUXI9^Jt5-mAbE^wOxnOot^
z+9R%9g*50FeM@KzT4X}Sb>c$UwN#M~kXN;KxnjamC@gz5EMCOh7FW0lA36nqHJYSk
zo_V=p?skD`=KbHiSWFbWL&55aBGf2rQ0GjD-DWNx;UB2#^hfS=I%8|MA*&6Q<T91E
zBwI$CNhTVHt3BwWv+qoTkuSNFF1edVteP5ccD>pQwf6e%D}qt!Wlts6#(1ggy~si*
z*z8KH{77?z)s1HqE^F>4282`LpGJA@YPaw2Qs}*Cn+tv;7sHH%v?l6(n~`F6<n8`F
zgSVKn8BSwRA;PpDaVJCZKx_OyqXl)F>cQZ%0Y>G<6)#(ph;<=$hCk{7*#vQslJ=!}
zQmv^Yo^b*BB(_b7S#BS85oNaIaDCz$I!mGf=>8SuX=nio$Y5*qz@dmWd`y80pnRr~
zIwC>h>aFA4Ro`TZ_N#;dl&W!+KDKuv=XRAo%-v7$AdRa9Jj$vs)9ykAU$7Ef4$GO<
zt2_^CfZ~U0@ifC%x}W`YscCLTKm?wVOL`b&*}ge_d$aF@itiu&sIUIfEX(M0rrqsF
zKceCQl+BZ0;q+Yy`iW^|cxqtE?N#+7|B_)>kty(ogG<IL_z@+dKqYM-6zw4gjK}ta
z+s<lQ#kS5MW2`rn+mEB%{~ONokp)Gn=_%R^^Mz}s1(A9mOCoLkCfQ!HIh+DFh8nRC
zga}>^^K#6y*|3e*p85tofUm&~7G<K=2o*{e`(~)jhT?T3PC9Rr)){P~>>4v(Ue=&Z
zEvm>?vHxjJme9t+n{Dnf^s{ZUbz9j@F8O%QvGxCY(aAG4h^Y|>U(za!>vvMUUEs>a
zG}LE#yjha0^5dk!lRjC|cbjp}%wZx8mOI&MXH2Kzk~K$9^ju<Bo4w*2{mrECIigGm
z7!^$bV$m}eEVyaQJbum^B~Oi!9uU5?5OoVkaL$UX8z%?*;s2V;)GiS#36StTHhy#S
zXE}0^$QIkHO0DMsr)`|c=>j3Pd@Jijx%*zjVP$<46)+3ZB#n5i*o_`VoIB_Fc5>J8
z3p{sw9(Mqh73Xv!krHtuZM8=EW%dk|R$Gv)r}yL0l&#$9PT!y26Ml$sGRY|OQZU>n
zMsB~x!0pXrgN}vQUB7BZQ(!EkyEhdVTlfYC1Pc&<03PV~2q)bytdll?YVI&L%W7wB
zi55w$tJq@RtF5|dUFu!j$WBMRAg;yrRsT(ALA96YuqO5AQhRDTp1$v3zvJIm)S6+F
z4LT+dZF7x_X1$k`3Q;J2I%3g_`Tn>O*kB_iJ#Cmi!gt7BnMK9HN~R~0Z*6<%V~)!<
z^W`+PK#ar~p2x9|3g*iGok@JQGN~;|;*!pe9&Jhx0>CI?S0)sZ+K+t>r-lUIn|6e7
zHx>pe5#hx}Odu=D8*;U{hXTx9u&3VIr5L}`T}ZTdQQ||lWo|NQbtr#-)&-1Mxo*1C
zzqcUu7CxSJ0x@Bn<wth`?h(p*&A>a<RLh^kCW#&@SEbmOy2L#5j##K|<=dbwJnGJr
z$C_iAQ{kK7os!l-PiNrt9n-iOtefrs(ODby;C`;gAY?&CZ44@0L!N}cyw{Csj}SK!
zZG#cf_WFj9&rrZbfTN$5pdq=y#SBnkB|~NzS6GbNOlwf<)?1ID9${4)8;FWLMndNW
z@k4>WT3Jj)ti|T$IS}Kp5JM>s{g#_53<5P1m8$i_mi9~-w{(oM?khwtyA1s1(1V|T
z6lvE=fart9G_t&}j>GBOd%eTUcRu;t8A@)P&;x1pN2ZBO&x3|?($~N<_e}D}#|V-l
z;FYvpHIF51KqIXNAGwhcQP-{4DHAVI3<R3SNTZ_Q8DG)Us9i%G%?t~dbU?=AuFhuX
zS_*vtRPyKLv<q;b!>y4A;kQT4hYiDxpZ9H+uAk(2uL|N@2p$jOceheFgbMT1=tdJg
z9kLvQPoB9@+AGL&0f?cL^AknDWVVcA-RiMwb@D$IdZN#JB+D>+e*qGJV|y*;@uZJn
zB|~M@Y5)v@?_z&?e>ZU8lr9?!<*}sT8{OHEAx`lDR}tj`D0x-J1f3CU0c$<0J_lvD
zf6z&pi%y9+Mpd7ZTzwW5^#bDD#?{SHCA|vz<C3dRbC3kehDrph?kZFaq~Y+VIRzJ8
zD7KyKsYDnZ?R}$yde+bIx3H;~vZ3=PaR#z|tRV#Mid74E;>(~6rgcUqsJq<er`fhd
zV?j(zv+Xw&D3R4&YY4QY*J+=P%q$o7==x4^pF??<!3NiaUsEkU*L<8l4w<tK+V&k-
zvpbO}?=nYm+P2OhtY!(i%FA^tCj0Yk%pn>^CL}Fjg@ZO_o5(DxbYG>=21ZbU8-r3f
z?pT+uw+_2#vtjQnrIOfhRA3O*U={f8jD<`m3vskHHDhkc+&Ve@&0|(j&aX!j@^fag
zuciSEV+y{-{x3pcOlhb8{I{Ra0vBLz&GZCIlCD@F*3~jvx=L7CJCLh9TQUKKlYHdp
zFHdWXNxhMju6)6n>`7e1TJuWW5@%VMFcg+Qv-I(GM>1Z;C$R7XoSm_K;0O1v9hAb^
z2Z_sF%l9n(CReBmpPf3>SB007OM~jA-pmnGPtEab+9+R^fCGFhd#mMD-e6k#h|pI-
z+%m7XR;(Cl*xc>Lt=@7wk*<=v;U}MzUvrnPuPVbZWp9CU*U)GID(7+9cX}|;ZDO7H
z6k=7cmP%?goK#VU)LTO`69-0$wQDH03AL%mjYx1c)=+P4>{zxgFSkai@^KfHs8pK;
z`Vj&T8r-=V$9|fXgnGvLRbcBzP)xD6zJg#WT!9CQ$nY|8pF<#9^8zCT9m4}bg}qs^
z9|JrwL9C)$onMjU;6EnNo`Uot?qU~(ePRnHmkFKUfkiYd*(y>e#y#~b)=6}*Jx=MV
zaz<!EU?`8PiQsIa?K{+0*u391LI!YOX<jhazMOUq@1@%JXWmo|9$8u5dX8C=SXncI
z2~w#JUQQc2AQ}C9_MvWN9$a7}g|}j=E4UolPN_43J9=?xy4;$DVyaBEO>RWPPSOs1
z<yzDj{oI*Ng71a1JGGfMxBy&Cb0OtX02MAQ9wYvYeh`y;6k#~i;x$L%5c~5LTe2W$
zRpe<d5h~TiziiJZ2-fJ?!7O{LP^M9g3u{$3xtR&^l$N5_o+lTnA<PZ8VRCrubMVgM
z%XA}cg!e~7ToAb-?omnzHWQ%^JrK^6bQ%8Rh3zD?WI98Da6(flOd*l~!g8Oc7r=D{
z*EVopL2Ewk2OGJ_1rwt1G?KetB3NPch2*FZr!QvVmERXh-IPB?bM80#TzrG_lDD>K
z&t7IY{z6bMyydmuk3-aGY*_&9a0Zi5>0nl!-jjJ{1FZ|om1=$quTQL2>LZrUA^h@@
z9=-+Qgp<K96&k7=P7WU}ubU93fx2)e3F12}iu?>9Fv)?!h3L6Q7`-Xe7wMY4Gcl(K
zEN}JeDC<)HJawd3;|mbAx?361Da!z<T}@%ApUfI<8C!Dt;Rb{PR@K12^UC#SrkAAF
z;j}Z*uNotzK6&kt;pzW^c;O`c(o%8wm_Ey(Zmv=@8nmXy?7G3S$qj--ws!1Vy2-h~
zv0RfX=NdG*Fz`Cqm@AF_7A<(heD~P@+?rDOpoYUV>aR@m?z9P6i&-|NZ9>v5a#002
zHgQZ<M<wA5OPC)Xzeu{Z&g?GFX&V99N>X18Kz>4^7l?)tuNgMW@YGXDSi%Zjq@h%>
z&ejygV9uQ21L-+}u3alsww}i=8a`7z9JF8^g4Ju>Caz`Oi`~wXZS^Wi8rUU66i^Lb
zBzf)88$CycB}K!+9|&x{!kri`ORPO?EQ#Z>gG=nW$VM69K3inz-<aG=&`c4&O0WHc
zXRsD;a$$4x+1AYL%}6ieeQx`~^wf4d?zZ;Tpw$oGe)i%c)Bn8cQF0h*dz>A$Xj&=B
z+PSG5ap#9B5oX~0Vx{Sei=U-}=(ciz*0zFr3#NzhsRRzk#uQn3uP!wWB?Q(2iBhHc
zdR*AG8SWg;|CDAJ`Y_+9M7(k-YKATH@Rk=<PzAS}+q{^4NyG=Ga0ffzS-(LzsKPB>
zAYxg4%GrGEEz2DWyPNpiLVXmR&$$FDa9jIiZqpx{+af1)d9!|-GtHl+RZNwX1hLVX
z^LS7~+gQCkGkE0&c<67C^N0wR17C0xC>JD7QFmexWq+f2IwCXF9(2e19qJC-(UZZ+
zn_sTvpDsVRs|mA^3l^Ad2AVzp>_T|L*PzG9hkh}B-EHB2eYAcE-(K$wuq=MEJ$(z$
zv{QNPGCRmlOoKb;V7Dp6K)*_YlT_gWn+gF88TO4D`p<7iby7cZv_Yx&htOY*ryvFG
zI>wp|A4U12Gig`)oG3F(zRExn*1d_<m>Bh;B3$(-iW(2mo}ocT-4>ER7|X@b-#ylM
zZwJP{Hm?a`jkyy*4($ouXPYi8Xwfyq=nGp*$4M!fI1Y-gDWic#9$l<2jHLQPR(0f$
zV`(J@JPkN36Lc9vUeb206B`|>Fz&66rot7I)e9gEJ`kMHI}-xNRZrj7&90APz$GqO
zjstrFrLC>*o6#`1dG1(VVJ--~k;2cMPy4dkG%B0<yc=5LiQ%H8K?XLwLJ{m<v&u|m
za$0h>BHrtlC?fU+Q}_zw-0bsgB3TzgpKvTF88j|M*9@y<@P^EsS}_Fm%O5z+bl(i)
z@yj1zW6qa9Fws@}v$Uvbor3ZsYFAD_EgrzL%MfQ|>Y$=A<@;PNFh9a?HZvD%^yX$;
z3-^@fy5V##Kh#Y{pz65~%qYKL1ZB{@<Y0s=Klaf7?1!|MkJ2G?Vn4POI;a@;nn;i$
zd+Z#5JX0V|U*-{^81;s>Ghx<1;cQSdro`zBs_(HOFS07a8(HsPX0rY1giqd~BUqbG
z<r^AX_+Ur!WyZPG*=glWxOFH*vqeU3x8`W!otCwjtS$0q55{?lRwNo2A(?K&!x%>P
zu~Uj#{_DqC0!Rh+CYp*E?j;xqnLq5@0xa@=v2r3JAy2ITHc6wo3AaO5<!t+XZzWY%
z0JDo$V$505HWT;K68=hxqu-S*zuao2A*fdxTbaI*$ojl!YGt~04=+qn-Q$Xxvz;IJ
zEYG-V5?QSmltTtqPl)$u1ZG&}6U@MLUZwxjAPI8LAxJID5xMO_9of;1&Vb~*vHOsK
z4PM3hIxi-*s0NbSB&Yr2ug~d0Df%)aS?AooFdMnl4;XJM8(B4H4TTkZO~aH6r%Li$
z*26%bpUj09F~?j_({r=rGtM6eP}}s)Y$C>tvA0SiM`BX0_3V;y*_OH1l-`=%TTQsC
z%r<+S0ZkN+&kJY2E>Wcb2^te6P=-rf9+savy02S-MPo9Bd+8iA!@i3v-6k%V9)V#o
z8{|%gE(~?fDTykCWA3Qc&{-NQmrRso^z6?SMn&Ilc|Noo6h%Gg=Z>UaA(Q62P*y%B
zX7EGbaBrJ`H`b@ygg=h36N29%iV}(*`oHIF{x+wr!*{r(*_2m|fm@Wh@n~l_XHboL
zsTc>8G)Hx8A&x9%03y5J=h!N<##%Ke64+w)R;*cqUm2fnBuptgpjFIhN)p$Z?dAMB
zyA?ipvZDou4_ms@U5;T4eIs{SS+G?`7M!2twO%upC|W0FcJ@wFbf9#;Gg-fN<G+O|
zxM55K8yR9>P_g5;mJ||F`FX&y>9DXk_Ohn-HQ(a0o|*}T41G2kYMwznsX9N)JcE#-
zf=99X+p>1U3DB6PX2)4KXZ=cyZB%5YoHM*{Xe?|{nzw$zRkb?U(5LpvM481^N@>QJ
zc3HL+AXIVXU9cA&){UYc(+Iz@4a76WsGCgd;ll3o8djbm695X6kntbjcJB6*zS&`A
z!X|t_Tg5=74$ijWRuj>%LF4XCC0*w2oq0ZsCK=XI<(bgn1Hpe{z+Z&y(z`*ViZL1%
zUfg#UnguI}w)#dPmGBQG+O01+a)m~|49Lup4St(@9hnto+D%kuP0r*YpjRd<j@C<N
zCz>lrlLCfSB@4?m%6hE1y<fKi$i<W6KHoDcfNX5l=Nk*u#)8s-)Ok85M3y)WNpS_f
z(&?CKMN3G$s!}M(jo3|{T`N>X6--No+`%s^5&HkbtwA<3bLHn$5Y2o(TSSx>6Tw2~
z))38Y!Fa`KrA%=32Hf7255-RR+zOdUF}LQ6c9tBlq~NQShbn;@79VY~bm&aB)1|th
zg-y!RAzgTcrNSV$sp}R5E$uj86I7Jsf0jxh9RJOaKo2*t!Xb(ayCHZu3&6h?n-RXL
zJ{4m{R#dO$*PC&n1KZ4Y9ouo)VuEEK;k@R{SJOEpK@i<`xv5bG1y+$P=VmKOz3hI-
z*X9_r>kP%ZS<s}OjBW^tS^%RDXjK^UYR4Ot=o6I?fvGfBtW`-pwY_ijQofHz)&k*W
z(4as&I%S`z;5-S-T3F)PhY3ueH#h;52&$*8vg7rZM`|bMKL^Jl_`Co<Zlj^-Q89`N
zXH2F%nv;WhT19Ow!C`0Fj^Aw%cs^%6Q+47)yip-b9lyiXG9YPeNjGf<iuGbXTn5Jc
z5i!)L66S)%6O9{91%;o0^R>7AHbNq<Tq#wwer$YTH$?GS_XJo<U}Jab5m(`Su~m<D
z71NcPNVAVH^q7x?F~RAHpcDKf7BlY-dqj?Eb9YLx|Nd4<Ys$XWjM6#(I4*K6P?z&>
zM`DzuS^5q7`>GM9A9gQ%KTOPzY`}RW2YFG-ARa~IUTx>8)OW>Gk{}9o_#6C@{AX0s
zWSo2it!{$m&Q&VhFB7TmH%>XrXpeG8RKa?icsU*DbnBKLPJcv{n|{1e`^Pwr815#g
zg%9%lqtm)EB7@%|R_H}!X#y(;{~&0uc!EN9)=ZRzplyCN**3+11gRCni58loxfRn_
z{DEcPjBT7H{X9#~`Ea(>IXr%_>2^{j(}#SahScJ*lJM{15)~|aHxCKBa|xLFcORMq
z=M;0gwFNz#ewM{953G)OG`jeuha2kKF9_8q7N)|MFsg-$q6`e}x(!DfH8F}}9b2%9
z=GL0isYOPOor$F<=hGj9u4x3%mi5`)zNdOeUHw+yf%`b*tlj)(^GY;$HlZ37(@rrM
z3#&gMw8HleRES5Uu~NlC_AR}3w#0R)M+*fFGrP6Z8bEx(dmI>tvlU~soT4+3^orqo
zjo%DPeNrM~Zt=|qi&yL_-L!P_meo5h(Sc?+CR3>XK9zP<EysT#d_Tud2Ga(S?OD!!
zJ<@tVRa@Ajfm%%P75s{3oSoI@qiA4p<^>r;AlQu)za@Cb<sD^V7Us4>{T=7*1yzRK
z&)OL9HXv{>2TXL)_=aH8P~eB!Ne@GR2#~PMd<Twh$WU`mvE^vCHe1`2SSZNZE<-Am
zC(1CDLR5u>Vk@|3lVP63d?`-i$<ZjRXDaz80c!<`&Gjo7VJOZ-3Wv{&+#wBb(`0kT
zlMVG9Yfw+2WSW~B8!r~6)lk%)vD$L6ue^}t(wA47!{I&jN0AIN*R!3za>hAB_eh?i
zCm1l6%>%LB3xb(ph|YLtsmd#&Jj7K=DKKeSq=bWYf-l+LAGG(ZLZVEsN!FOTo#&n<
z#9Gi9VEYtryW)|#wB-e)or|GlP=~ibhf#|Xs8>iy^KJG5owG(@X4BqI!?^h=_6U_f
z8DlEIzib}O^q4kWh1-ov;AO63Dl46;WRTd*F>_FTrQM|7pD;J()-U1+u5tjGeI>CZ
z&1q}p7EVe>JTf>mgH~=cbGGT<>@=#9rCHjNcx6QhgaOVs)ysAQB?dR0GnWQi!z5Km
zUwLZsh(HV*ki_3F1Yko4HVlbZZutBIJs>WqrT52ZQt=Q{70>4_+QODb0Z2l8Z$TsA
zI;g(fx21O%@L|Y>ks@62T`ma;M}1sKskKWceqXlapfomnU8{>+IM#zsxFx)D+4Dg&
zs$@8o_F=nMa2yFe`dFT{C=Faau^~&Cy4_UX!NLbHDidlgX91bgL;mWl+Vqr{pIv*f
z+dxWq!BC1+i+4-`mSaX;<m7>o!9kF8(S;rQy&ega*Cd=NOmb|rC^-7*WKkD$;3K~D
zNR5Frpv*BcHFM=fBYkN<eLuSen$h4(=b|}1>1?3bu9RPN@f;H;TTic4t<Dq9>^fVD
zw6sgMdTc1KOAdWT<xwpQJcBFTERfyZa2jMqkoHgwIeXboJ(PxOqGEETd}Yd)b#iDF
zTi}>rHkLhtql5AP<=JP|_KY5;DDx`bjWVOr-P>fb%Cc(rMDj^>y^3WcyrG2>niVS>
zfA)-L8Swl?OWrOP3>EZntJ}Mw7wmuj+6f#lc|Vh_q*lzS;5_=m>*O+4uR2$b>;pGO
zR!hF;Du_tK2BqzwgY=Orc1_Tp2Q}M2wkEMb^HT$S?8x0@7)Njwv+H?v-anpK4OBhF
z$NP^y^nfL%c4ALOz2BqU`Pq+csmw`@3j!mVJEM%W&9Ua3>60&jicT^e#$Pvk`1Q`)
z1HW`X1Lglp2H9vDyPHcHq*<scx>bb#m~S!{OT{tc6~<FLvky*_h^??9cu|H5FH<2~
zyaZaVtKr}Bv~Z730pIm;d<*U;_m)-u22v)qWL#E&CytO(<<@(><vxBftZ@@y-yA*W
zXwfz(IIveDb<SV6=d(Rl^q-DF@9nkcVR*`S^fVtm3QbEW;Pa24GX0XdV8&aiG|pOJ
zGyKT@0p&H#dj^MWHcGV687Rmo?E;}F&wuCZy!_0{(#eOb!`aye8+~zro@mjUlQc8t
zKmeE~le<XI;Hg!j&3t*K=Q6;+tB9uNv+l0ASSixIWwsS#%;UQ>DDHJONp8$k_$kK1
zxeQmN9o&o<c{OLZ{1%SEys-R|>5m`!!<fjeoPV9h^Uvh%m7Bj!q8o+R9F$BMk<?bC
zpMktQ>D-}a%oc})8zY+qlleEhsi_&)L;xCkw~+qOrqpk$pbMzlVVJ0!sd&mRGt*d9
z7Z#3y8-jIHhu$^m=0ThaR$6wi*&blIx@`pJ2QkzCD>k+XP+qp-kgIf?E1dV$#463U
zab1PE635V?xB2XqIP+Bog=`JwSB-3!=O(Jw+#(a*(L#PX)5klnnSDdBFseixJ8|Ic
zm(%Gqn*{W7TON8gj~1RKV-Zy&^LE2Cobhopf^6NhTc`f#*GnP%&*s5%mP=C6Q2`m(
zGn?++DEzWcCYHSN(i^{1qvpwb!0#`)mKIieeTbXedI3tc3FhY|6e&D|Gk2d$Q_o2w
z7LXv1lAaQjNdaQ2V5Y!d?@r(Dn~_2aexQxcU`ox*23S5<G9Dnk=+u>t2j_$l$VhD0
z!EHpuiW2PL4BYqoreDJBpg%l)4}Y0O?datn<c#C&LW|>b&|V&nx*43!Ki6cH<W<7t
zQAB5vcS<x#cDFf<;uyyxLx)8)567$qqeJr~=2n|bvmUl4--JIdA7O29zV|OPx7~#d
zI46j{VZ+=gK!c~&AE~WA^|X8J?0eU=<=U_uy)S_Bu-uYN-m$y>K#Dvwktd~WK-l%1
zyP0KNQuWyF)wy0ZOY7ByUYyXA$Ix-aUisQHAjk%j#>AaU54U*ua~3sVAR!wVj+F)0
zycN`o2$W>&cHw`53$3=tHS+U9eILuZ6)Tn0eg4YC3SkSeRPLpJkw)sHB%jP3qY6zP
z6>+K{_!`!nw+Kp;e^3PuVJdqp-EHvF{5A8P$8YpW`eVTgh)F$%cxdiNh*&xdA@Y-@
zFvM-)RBIQO#+f38n^DiopXg|JQ@ztin}z77VVlSMdOcV$k}z!Mf+siC>!XKZX}U-F
z8xasm9>BuFkuBlBUG;J&D!Z3ly4W~X_YH-l+%-fS#mI`uJ4fFvr1}?*u?8$GIugMQ
z*;SWqjZ8rbYj(u8K+FOBx2({yO2k;sc7gR)hP?nK&5h#5vwh*2ty<0x6-U|VqiWf~
zz=O`~#)X?X*Bo(2Rr|a(ay-)>NvUz}j6hF)lU4B4$BxX_OgTuNV+QwFW2`*1kIcPO
z=lPQ;U5+)Rq^)%L=z{1;;aOj_8Dq8FYlp0cGce(k!TPa<e(`E1vMX=FUQu1Tk-6l=
z+I8nm78Vbrq|S_1EUbT)AydBom1d2OUP7n`GVko-vpmseK>=)ie0S*P$!5$Mp71$m
zwb3-f2+U~Su#Ze?tx!=#D%RHKkj>)X-`ukc0`uFiw|i~7>gs8Wau?5b!@r2y?(h$8
zh#-3RwKr!z2`m0xO$yiXe*rs3Jl@t=Zj6k`e-YHTK7B`#o%5peAhW23NYAT1JOpgd
zXhvItrbHDkwJ?x*(}#1#tC@;mShps(7Q;~3IZ-$23ItB=omW$H6ropJHKaRC4t7eG
z5X0ACtG&&dp1$WAVuMI;|AemLS@jyLUZy<)K>b4%pj&X26pbAm)HVRM5h%;!K@T<9
zdGOn3Uv^)1ksU<YkQ?t65&s)XhBSALt<=|Q())pZV46rb{4Vm-zQZyG?lv7k8z_lX
zJ7^!?f66VbN}_0o)s{n_v%m8Jt&MAC8eLong>ir6HmN}NK4tgPp1_`zq=O1po!aPH
z?8F^v5Wm8^4ef}}nr=5yj@C9q)ymcaTAtm6BRo<3`RafxZs?ZjQmJ8QP-R98TcII1
zAzcV`k^_3iJD|V%YsSP9LFK3HCYeI~?f@5Ks6pIJ_Qt+pTXymtT#UYe5peSYv>Uxl
zmFd+hb<hnxp-j;l$-q%hROjM~bx1cEVG#}ht6r*(G)!N;G5-Mn_e<W`6_~X==U5RA
zlquZtwHE#a?21~G#?4a~AZ$}>prjgW3;=s!^_OQuTax+}yl{2{H<f;bpTS?XoH7vw
z|5rQdtpt<n9hDWf$hpV*E33eqx3N`+<75ggj%v{ND$rV^9lTT9RFxYi-#vt;U!6l&
zL*8opJ*K%y%yNwmaG#wY#*^8uO^oLP0MM%K8;6<|X>2>hhkHoi@3>9T^XV&+yhxUx
zJ7q3Nc*Kjgpeku&BRT*Ry0C^r?Bpl}=4<vwgc2^l@x+N0bD&6_RF~+sHW$4Z2P1^x
zElh)LwJ_7@XQrAfd!>ju;ACo+q@*;3%D&1D<Bm-(xdHyd@LR1}$=ek%ii6WEk3{T^
z>v$M>7P!R-;j6eYW8m;JhrXdJ7f`_0A#fJlfKA<ZTkvdn+!Muv+%OgpyJ)W6RD_sF
zsaUviu<p=Ae^&isqBw!LAq+#2BKGy&EUP=vg_DPefHmodMn9<?*Fos&(-#}d#{nOR
z!JyW*BNOgzhhGI^F$lT*H-wV<cVBil)z2^_rR}I0@I_ieJ_mylfBQlhW?&!Ev=<yq
zg}R#2jOyl*o53O&FnihfmDkyEQ^s8d*0>u;5y5%YG!n7rO;B#6wcO;3zwjITho1je
z@=&kCDzPSifpa>>l|o&=vt=z~e}}E&z-<Q`XURNg)b6Oz9@HugFdkW8SAY85zrg>)
zLbm}QAr=uzf0SP19xhIWb05(5=AwJ}h0!6#)_@1vZ>NK+63A>;*z*h`%9gyz<&zGp
zu?SL>8CXGe&+*0U-%yC++RvLeR@WHYpm0d`6cq(xX#5P-tc!YQR4~aPJhI&;kxTMa
zho|OB8LuSI%C?6;ov{GjxdjYdxOEjF>Y<OvT&In9m%eS2iBB2&D#u&nuf?;UTD=8_
zdu($X75$%ZTzb$HvJxZ-q$f*lnxy%T|5weyIN!HZ3G9&T99p`05`zO&!|6X|WKGRj
zDOcS|XutQ)#h^|aNw2Ff%-L?xY+AV@-jHcSmaY7aUw0!So*V)w%8F!7b0#pK&`t2j
zRrNor*pPc8Y=R$t{7)a9Z*lL{5hHXrz;qAPE;bFqaD2f{WVU@1|5|ai7#ofD_jZ0d
zcd-TI&B>dPG0rRPF|Ly0Lbobjep6+}8mG0@)+jJTF5zMKohz&K$G*U&$!<P19Dgy{
zQQE#lk51AXe^a*LTYFC22Tn6KO({)MJg!qBps{wh??DnU{3ZB8+x!GT5Pe4$cD-#X
z4DTDZxYLh@+Cl$;_Dv+$qFf@wWfp-Ex$Xz$n~vS2@V(tzB}Y;2t)UXM8JaZWd}nh~
z;E6KSzn5zrIKcNH<w=ys`4U}ieH@xL!Qj!;Xa=1G%u#jIqi(OfrF3EqmElXylO@?B
z`W5$d1fL=6!P7pt(lX56Tziu?{}On&(Q6QzITBv1sIRoA*a>*;3`>oG^^}?duge7_
z$aO)(N^}%~c>zy+7mVq_uok(OZjPB81(bQ1;i$kM@PU9+Y6wkk!PXA#`VzBynJTsk
z?V#E6$05c7nh{5M@7Xw`fK^m=Z1bMAUO6`;0lK1wzz}#iQ`UUlBj3iX;IZaRjxt1+
zMwbpVYiet#B9jOBOW%HKQ(#kToF!B7Yn+PzB5+=YAWP@+Bzip4PPVZ`M&)Ht%c2h3
z*ni7>_7Iz7QiOjHnm?B&sH`j@u4_-<fj6*C>cc|N)9r(zcVOy+VNs^~20U(qS_`g3
z{}Gcs_@=Y>!Y}^(&D)R8KQ3&r*$HG(A?w2E-kr>g`4S*)P=zjCI1b|3!6vi`uTRDJ
z64|%1iK50pEpET)9TsQj{9hlx(3DNKZ-NxM4b@*Dn9NC1vn-@r$CeZMz^%5SJOwhl
zMR^5}0E8#bSE+sp)>YryRIGVbI#W0<kG=^Tdi45wF7t?cUfHhNfI`sNwuKXA9#N5C
zTyWbT_U5e(r}sOMhZ~@H^Dbj2qf@Nz)E=KZ=o8G4^kX{A=VE&29dcAr5=Y-2C*+e&
z>GspQF*&%^cqj*uNMZL1S$x)uF!vP5ExV083qLlD_JG&CrN(-$FN-g+$k7)QF*FeU
z)8|J=qq*FWCpLcdfLnX&dKO1U3@{=y>RxS~MUgyhzKZ&Sl8<=xTZgEP;l^-`tC)^f
z_bvF&T=Xb-igtRTKN|0Z0cI5FEA7=<9b~ChrXcCkb&C))f4(f}WvR~0{!4LIFo*pG
z@g{Bkh;r>}ZJ&(7Xa;A^yKxyR3y6XKtp#}hrZnP0mWp5JybMBf*pn$Q8B#FI=bya&
zqBtWgd18^uh+Z7&T>PkecrG%ZX8o^o#OEuHXdG%c42@Fh{rKPb)IVNv>Yokj@bHVz
z{u`h2C&6<ylIHaO;4!I4MdDN5O`I&pn#FyXTemon^yIQS7SAzYST<DdoNcl}E(|tE
z)sA+x?NF7ZyUx-7#$GVl26z2X8?48^IyQ&C`qS_J)n2Bn2K>|S{tdH}@GJge@Qbig
z!xs$njw!M{p=?w#p0ItDQ~qt3^!co@=}6!0YitWgX?e3@SB2z#TR5i7NDY%&1Oswx
zko|2$qH%?a{wK1%%7-yFVdu`%+;r?oe$<03ZADGDQ{IL8X;50o`ygYp;rDp?nmGq*
zLm+6x7+khs)}2O*6CaubcTv+5Gh0QoXXr@9r=dyR?JyxcToQ_PJI&Ok>XG#@C%w3C
zH1_=N!G)j#fl9f}-cuQae5P^W*|xq|Yurs?u&``Y+IxC$O>2jXU}#6;;+>jC)Zf+`
z4<_4CN{_4wzC<h=G2#V@+=wyL4E=Tb_Rz2tY6&L^nXaMhc>+<_w$N<*+P^{Y*_yk3
z(}TA``!T=+CXO1<ySM(0jMWA#^zzfce);hx?%Cnjthf@#qiDpSU0_xMN61+y>7?=}
z&?gw(i`O6Cp{PR?+ZX0OGs8tLN3;VrSKlOrb26Zk)VR))JO+sY5$A-YO=MnY)#t{y
ztEZz1WQ>=4M&Mph1?-lKT^Xl%Mgw&SXAWAOKF)$~8(+XBY5v0l_&aVFTGg6MBsA`k
zlW7AeHRY4?JyU(!{ongaST4|#wi(u<jT1>V`p+luer75Yi@oeCHx>drY=dh>3Jz@)
zh(C8MNkpL80b5F1T<bKBu_*x=W+ax7%xuh6y!}Wh5rn9GjF*|fxs5-Utm>sGO9B?a
zZrLGex3X%Bg*b0h$5)xm8It06h(Zn0OSsk<f9!MWQIj=wQZw|8FyF8}L*7@Am61ga
z5p0Z>pfVriwtf;?w0mpOKE@WUT4T|Yv>^)oW!bN^c~Q6F&tiwF#6NOlYl8Hd<FgBQ
z5Sg;S!mnvE{H*C_LN2-ua$2%aFX-+FKzy9<bC|Fv#l@-hI|tu<De20kyku-jv}LS!
z04h#mRuX|hsUwd9z_z;>WI))a=DC_8p6KGM7oiV}ADO9u++?%>vMFpAqk$A^aRl5~
zL0p|+#d``~<Ae={U!jDur}GsETP)Z>LBVCs48mG+-}&XC{)$c(0-lYOkT|LX*J)C5
zA-!{)d}5TI?<d3Vji&a<lPO)2WWZi+CrtNn{NJbK^HG0px@qh$6Ry3KoPjYMie!gA
zW~v!RUubx~jTWwEO7_CyID-4G>Y4i7M6U%fmY45_Ooz8?B<T|p4$+!1jJ$m-K~-+2
zSW;Y;Sl|_7qxf^JOl`c^lw}N*m=_|fzKzKDgCqlsz9d#JWzbT19}ci@Y*(YL|Jfke
zDhk}xt7OZF4r*03&#4Ke=NzKrRgQ2grzN-^Isq0QRoZcGQJJ%14~5M@Edtk&Y_qrP
z`RIZI2)xJfApnwpBUPre3h1Y}6^8@lLmE$6Hb$WZJz}~MLI_k}l1IWs`8Hs}-?h`_
zlCs>us^0d)fDO-2B2;!nx1`zWI}QR_AeKy!0|<)VmNMN-A*!`6{NGsIacv9YpH*)?
zH*^L-1`8Z`103PPLn_m3XetpX-DTUfl&Gbke}es>*f+cjfgTw;;7P<vl=>SRl+Qrp
z`7<EsLVL$e69Y|aW@ULKWNTMwPhCa^UuOsJh-@0BSW<!W=%S39>h+81_^{#DCDSo}
zhipi9^ATzZEMeeMCCZEL446WlFAlR<JgdB%C($zraTSPWI336^fMr>8FFbV%Y}~`S
zpa?wOh>3LhC+4msnuKX@=t9MwTlzM&H8w7#kKIQ5(|Z>Y68FLH5vzJH2*&3&^4wpC
zl+0YfR^<RhFIzAf5yzKri;m#bJMb-jtG*_G+3*6WZByK1qrP0YnUwM1i+MD2V=`R+
zB)-kGW!rmO$kgkOLsPBm+f*)9AB?>z&R{j1cfFlmWmpwj);@GfH%NDvba!`3cQ*)#
zNSD&x-5?FpQqtYsAuTN+@EvC6ek0zib7$az!^4mDzI*NcuC;sLt&lSz%2<6<LfLJs
zo*O$L=O<6jr0Z*1X6G&{tQbPMk6@~kxkma#K{AtQRs^<lIxMW!IeQ4507-kC<pnR}
ztqyapZ$%U)L+}E#DD^h-J&m}UHw(BYo$;bl9_5ns+?q_S1v<RGYl^G)y*jbRFxsdA
zSLFFIh%P$D14P*8%)SMzB5M*^vHOCtL??CRMwpRj)Xn95UTGbZJJhgDE_sD-%Rb0?
z@hC;5MgT7nT5hJcA{{Wq{N?~|^G$`CoDCE+@FkY}K>`Wq(Wd&^9@94(zx$Cl7yu@^
zXz~u(=nQ7)X;m&QdI|DT`e6neY7|1OU8O?GY2@!QxR={+NL4d-TNsXdHj&4Vq%rEt
zvf%f9Q<jok+6PKj9Gg&Yc(9nD!Kjj-nX|bu-Sbv{_SoW$G<}#<Pn;VJp_-y?jzmIU
z1J2pHJd`|?#eFG}GhYR@DY0%&`bwt}6`=~+>9c9fkn{qyFtabTr=z021b=;6f+bc4
zvB2&aXIP{WL0{-yX;hAlG{XfuJkR3HNa9Nc{V#k<>UT5hzUEEyJsI!n>OzLvpNYS6
z=*qHzr6MltvrwGLQAg-r#{5LlO)<l~7F-kWGlze{F5;&a_G~NOWohB03Qs4{%WU9$
z0$+M`tKfJPz=l0@n+{3&3RIQQm$_@64kHCEv_>&M42(bb!3A)Yp=h^XkLYTY9q0Sy
zIjGi6S9aAEm(o!}w{fLE(?v3_$h}*psY?YbBh?)9+oXZGNsKI#OoG}4y{I`<<<9Nf
zIu-drm*F!0%vX$ZxPo=UkoTo7Sc2hqGFPj0EBvGIGMKpDn06g-<cWKVeU!rB@C)$T
zpy*uz`0f?z3jFrG{au816^QUP4V0Ow9+&~8n?4<9+Mcd;RqgB7_8>tJ-X*981{|UH
z?0LA>&SGk}37ii%x1V$XV*`vz92dg@tK$8k*mo2+^yPIsU8{^7_8@O0K@<?I;wzW>
zQbfm?BFEc4^&1Xb3mI2FYf!{1!b4X-T9ch4#M_C=4!)X_qp_z@!DbtNA!RL+(M66D
zo6n}XTu|f|md+L)3vr~<3B@(;4sgh>oKz+7lW|QjvFn?sGf*7H!psbEwNvcuD0s&K
zmd{I%6e5wy`WAn01W}}V$2~cYa1ABf2k>H-vK@^N<vp{cLs?kL3Hwyq(fQr(T|CMN
zJ{Sc(3bfNSkxO|FfvMs;-&H?tm2395Z!gp%Wco%VtBWbW;M<a~F%4hZZ1PJ{+Z(?0
z8}_u8^U@E_+Zdg7#czCLFp3yM#d}cxaYL`+t#1$TsuYSZ5I4IEBf9#xQ_ty1M<tMC
z_A?<`V|WU@XJyS4aZ3qvzLoWZ&T$T8?|7APR!MFHHh^y~@H8NlH6ipp&pB9q<}k`q
z|DMaC(PXPKlYXA$P8YGjtAOY0?v;MfOdXa$o^d(ZC0ZG=-JNiBoyt13$5L0PUrP@b
zKYlDH(tI^Lk{`bt#*zvaq;+j+((I-MttNjnzx;miD0UVG<98?$n@I^uX&<9&gGLy4
z|CPuQIi7J6Rw~%9x!rG9RyXx$;wza@pM%dcZ1kI3PAQ;_eT6;R%hR`Uh|7kulkR@6
z2hu`k+C_7{SCY9XrA`2NH&jv!_=bMJg#Y4l3@!e1F;}mNC*>MZ3p*8QwDEjtGy2`i
zovMrLmsZc#%u42_8hBB@-JrSo4|B<wmt|kuTm~dmF^yjv(WW9+2@f-C4IM+iG0R$o
zhZh<C&h&!y1{Zzo&XD9aKF-kwia;brukwrzcZ%GkQtPflIj-VJR>E??TJ|%iEaZUh
zmYVfflK`QC={@Z$g}DwRT69nrjx0J%99$|nbI_{LIG?_Q&=^8}taZvY2`GIheC6Kp
z!O1r^;4r=-zUN*6VMwtXHubX{L7V{u-s*PzcvFK>8O|n+`Mctlq;=2wU@Qo1;1b-8
ze5Sh=%(1k(V3p~x`ag?Xy|0DR<<B~M8?Y2~HJ999K){4>gk2UQzkR8ocg-tyno-fK
zq!t6OsvrDqX_{*@x5T{S1*5|QO+CGGtod07+reSZGTWC!;%NHKmOhAPru2B2*F34q
zD@2g{E{JvAC%p#44m+uUR2D2JgEn$Ms-CR3@P03r?%rmvmiVZh&%6YcXg+cus36V=
zaC02bg5|I;@X#}>>suQp>c@jXEdBo3O;fP=ZEp?+v3Dcdfzg#6X+p&sA;EfwK`^iz
zz8`R}29jYE_G$q-<|fmM1kT7KoMwY>(;{PJ?xw1=7u^$ll?mPuN2F9d{_tI~#V7PQ
z?oB>Ur-OCjp`2=WXFHqrV3@<Tkdn{Ap#FyW??zF2Irv10Dxzo!KSG@JLfQmedQitH
z8GSKgY4J&)0CUO2pldK^MS@t3cm<gRG6*k37mYX%iZReV;WwFtFW8l2pCb#36~#|5
z0zvGTxZ+Ovy*Fedx~)Kok;!8@c>#u83+FYL8@0M*F~-q6Ujkp1|LL1r*pf|O;lMz7
z1BaQDH{^(V7Ith4#x1#kfgX*$`z#wgL=)!yOxcx_w1#)!6{MiA!lc+Ts*V@X?M+#W
z^)ETezI%Q+<V_GlgTY<j*MYx#)t){s_kk)Wh#%p`tCv#W!nsHJ29!U{Dj>~z%x7gQ
zJqFG3{*d=VRR?|$!(S=qoS^E>KntZ{ZG5{qN#%krg~ZD)tur6r(sPpL+7+ztE<^&&
zGWs>ieQnDdD|#+5Bho47Di2+N+z+$)pVe}FooVFD8dnI)35!2-X;m7W6{s(*gDL<|
zof0O3hiR&U>zm}^tAnVjwNY{7<{T6SF$l(0X3pZ<34n%)pNj43r98yzb}-}31&tp%
z*&AE6;bPeL!n<{5Ks2m1Pb2_(Yf@#uZjKbBgJkt#kwz1`d<$c<5)YuuPkP%Tsv1Wp
zVwKCAW?QuHO;o7_0fCV3do>6hz$wHnK_L@vNxj%P7+LqSE$}S|q?L8u#;DzHOo!Wh
z65$#8K-$h=O_)dtcE0ik$JuO<hv))CoP9NJ2zh=Hyzy9aG8>QR$bP&M9sLg_haooE
z4De%)&i0;%c>7g4DWVb;1vWti*phCvRM{O1=P++K_Nh)UN(l~azrJp&e$`kI<Yk6E
z&s3=RF4t|0T&i*e4ZSiP@Oj(5^K{t+npn+yOA9RTVl#$*-Ot3Qy{cfIw$uMkQ~nh<
z=A{u6hOlUtx8WQLCO&v<n0XKcGuF=1EweA8@@5sNEiIo1h%+r1b3D3cN`2T1LCmI8
zgSR}cSXqv=;E-P=@kV++<_&(oqU&BB3XWp@qMJH(ah|5<O%l%{>e+V1FohD9+4WWp
z0K&^bm|sALc7?Kr`2I562G20B3Z`S4oHs&nHTOG%A0dj6<Phcxm!28O%=z~Tv+9Q`
zSR(3%ZrJbB`J1F{^I~0D?=7yN4?Z~Tekwf1+qn`G@T_fi2!x-Y8-0^`Jx^xNMsUGo
zY$sjMwi8pP0ZLASa?d1IuMkxyQG8`VSylwe>`*poenJO)ozdvDt5cHuTUddI1<A>t
z<7STwTSxb2Gf1!@1S0M^5S7$qs+0D(IsvsditN?TXcpHfgIwTS(44yQ%X;m3!|Q&?
zq*!2kQzu=zeYf&jHNh!OQgjZ981x4--)6G3BT|h~D~Dm$>v?JlV~LqOc+pkE)tfrQ
zc0faid|0B3G6XR^)`!X3u*xejv}LwAstn3G9bQ3jHbb+R-oix4A2iXdzvKMI%n~>1
zpYA5GBlEQf0WZR-qF;`{tfDLn#_E&oqUr3nQ(GI@_6%)2j`t#LR;Zx`$6-2c&x6P}
z(^JD9aD^#9l-gh_mts#ROU?A>fo{p+h*SC4<=eaAm<}TI53$xJN((d%NpFHZ^Fquy
z7$<FlG*O;q9^e<GP^X>m=y%J7OO`d#caAUW_;S|p+WUhgZnExY#PQgvNsNO79E$Xi
zf&lsKY4IWREp_d<yi<y3R_(p#356aj!z})Jt1qsEt1gwPXqabEVjH<+n985|HQqKC
zwr;1}5X!2&!^+yr{N&H-_)34)-7(;qiDLhBudX8l8skjsilPXfLlurC`-?);Rp1LB
z(+4=^`S4cxBSI`OdF2Uy$vPWIpbIi-&usErc;wdxt<w(N%}uRF&e0UAOUf{@@oiNP
zJz7FZo9skZiEv$<b4VOpJXGKaGG7HzJ|kboYKCy(@Z>i|mMoV(7aiy_o}#4Lp6{S-
zl(oCS%Zjym0h)S4iyN4J8@0dZW-Atx<Q^E7UPzG?a#l-@%N?u%4ko^*X<aTIZU{~+
z!Bk&7DeEl~Z~R<@CLNyl!k>L4X1u+q@ia{8cJ%|-UDUcz1O|h^L5|7(rXTGv@g;$e
zx_~fJ-yj_RQjJ6WRd`;<jzgGIbzHrP9WLw$xxD@L+yYwyAb-+_9D3ke)%O{x!D@Aw
z%}M4jbHL6>rRds0qisBlCOlJ-UxFx$&X^e6`k7I$kCyfoS-k%EIlM@6k66ln#}FWg
zw{jjhvSZ~uBodI`h!%9OMIf_5COs^_Ki0eBf4oVsaISiGP96ZLNB{vSNP~f+0ic23
z%GLYYfFHhae!4K$(ZtEl#nH&**B1yLB`R6wlqgx&Xwq7IPLsD=Y()Qj1#<How48*!
z@~m8k?Qk8PQo(sl_T(#})t5?L)^Q%mjV|bA*K$@P;2L1_4!%;tVYd1H*F|Z|Z``D0
zQ8y<+>g9TRwPjYXY}Oh}_&?o`d`p-q_rklk`qtz4;`;^lO1$QnHCt2TK?bvW`C08k
zed9=D>yXDsdZ?3>oP37c{;;Zq-WmV<n@ldz-QuO!IJvh*8g%{HMdB@5ah`RS@0ME4
ztM^N)(zi8huRZxO4i=Wqk7b)255Hcy+SySA=&09h)iEGe`r&X)$rU$XzYDL-FLJ#@
zvcB;<c)*K2#M&4dhn_ixH(b<i@&9%`IUKaTz+mz)@G<|6tL~zQRC=cAQ1n*Vi9o1X
z6Kl2k!hy&(KB!&?fBkNXs$*nAuZAH(chA!w0v+$7Ga!BPc+2bl?H=7{jYf+MF^%aa
z$E{03g8S>dM1Adr;=%n66W6l+YMT^HPfh#yE%j5=Jkz@BqN^HNm@sB`N+LuP*>`G8
zWU^`9;r^we$V5e!f(mb{p*<=edg>^t_GqrY6q`1QQ%1UIN_EI><y)xhd%1SDBfR`P
zu{^c)YX4?J^r+v3SA=>$dr_@ypgY6-`-gJ&5`h@N#e|M85=n~wCd?bqT-7k4iF7}7
zNN#Y##+PvR3Eg~4kZfgk1K9(ouU~wpC{GV;{DQEm8uir*d#L^awWsA1T^(36e^5Bx
zH1Ki)6HtviY*jfQc*JdqdVRu###b^l_Y5NJ7dkN?OR98(!uPYINmKf)*@8Z~_pH&e
z_hUG4Muaz%i58;nf!7acs&1lFb?c%s2oPL6%wmwGb=sxWeX=XA>SOcU<yoQOfE@Kv
zKPSC>LwB%Bam-@*tfm$~mtqTU4Q>qO915PFxuy2O2iE(UFC54*izAWkMw%Fu-JFTk
z9#<O8t3x+GX8YGfUnCO7s*@WA4z-4Lav|p$-^Gf$qRNJ7i%bC@m!K-x!%+xc0+q&;
zA>UlapNY?vxT0SPMZ|t3`pHVC7fnbdT7xC&u#Maf0@(IMwT5##KUg6z`*VS;I!^m>
z;IK`?G1+P)A=Q^fXk^`*uv$vVaS!+IHjLs~^)^dlbz~xK1msE1p609c$mMnlQ>f5m
zaekJ=pNg!(`sl71A^Fj!+V<?3;MY9g08Hbmjrce8e0Kg!Rn_0XKV(DtQkN((at-8f
z>?Tke!xGnji4%c~Z)hFHpI^-V&evFn+i2Y-K}#)}o;3JM+iSZ%9@k{xW2*R$_6+ed
zj0@<|Rw>+0OChG=XazI6{ZQRN>-SjCYpYi)HFIB~&}$le!Qf4q!S;Dw3wkG@l{0xx
zR3p710sbnNt8P^mVELpzVEL3nz@K*nj4f%rH4S~=p6jVNfxR)xK0$U>f7O}mQT-uM
z1IdV#)SUcmUQo7F*C6I#Hqe4`JywM{4HXv*F-GXf#pGZ?S867#R7pr=|1Dl`^=;L2
z$cxVXAlMXq2ne!aWAP2~Krua%?3H<*K&O?nHB6@&`Rjbx>}mDq&(w3HI0LAi1U%=^
zm_<W)h)EPTJ;{nvf~I+%H`q+L%-xmIci$(g3saO9e=oB*J9!8ymGdKJ$`zj;90uV-
zMnIZ0?*!qZEH?yEtQ4^des5}nEm*5jfrD^(0r<WuAqj5~cXeIwu*$@cJ_}Xl8|bY)
zVj9Haz#?TC{JdTXGPE#1T3^Mbdsgxq13-R7hfS6%2_{?JH*h1Z%fAgvb?d8H$<X(e
ziS9VdFwPb6R$YKs1kd9hYW>3R?A`V4trOkmWpUaAZOHgmi^=EkBL<tLmXRvj-AT+P
zfb*7SUnT<ZmZ-Jm{df5uI4`UF@CQz|X<c1KRgjmG`^-(h69gB$cQiUE)f@Ja9CblK
z_a9G0;v~^7qhfaN%ZK@lTa>J@I9Lv|(gVxi1<T*<j<n9cogl?lAAeyvb8)CVec|4M
z)7{wls=zys3f-sT!)WrXCRQcd7LJ9PnKqxbjR6yB3S6k6wY&BuL<~gTRsZNIax|cM
zXrc9$joLKuX?ITPGTO>mf%svY?mcnC#w^wW1SK-${1`N8jVebY{J0u>{0?&?g55$L
z&c>I0Z8j<WEqL%M;44UKQ{b&cFDgh9v1~57=LAc4I`Gb3!)$p&ceCy%5sl{Z#9QRQ
zXDHHUu4*DKKW!rN)Li*^Z9yOeSk{L2Jy~s>^^sddAy2Uo=T1T*A;1z@=VJ|J`fmLC
z3xJ5p(8gQLz~RLNwyzaI5WHrq?UI2OgA1xcJku%*=aBw`$RY&P5EHnzT(-amIMGO$
zq8H7MQt+kOF?Nu}{k;hs`V<kC5?rCT-%C8qi?c@LM^50er<0)J7kyq-Zlt<}MO)<(
zovQE!+-G8CBm0Y1UV>BK`g)jHA45!z1Kq=OL_T<`vto?^=WD=R;SfX<Rv2djUaTU=
z%@=ZOl*#!@!Iv~qM2K>&M<Of<j0)2mk~>u<fmqsiGN(jcmYcVdT%TjI3tSiE`jC)B
zt<G}dKtWmAVAZ_A|2aV$7T*h|R9L6ISyh^`T1*wX-TS#W?4U|K_3KuuuXsskmD3k#
zXw2N#oFDAwbk3f)ycNZla?tGgVgsJw^Y(C<m=V{6LHNsp5gEih8jU52bwJBto~`#4
z?AJ@zPsZ&bXlJ&#YCB(NK8Jhin0#euvVHSy@-7FvkZk!4-oEQqX&+louos-tq*yDm
zB+71i*`;mnYa1-UU6BiXB|>{4B`V?WNTDx`F_t{3KZOb*(f2QKDDRF#EQC&YnPjo9
z)3HE-4e&Kv9><bwa1zsT>$cX&42lX#3e^`xh2Esuh6f8_upPs*MzImv#`~hzd?mD|
zYE0!Jw&qokUhG0DWY^kVCT#08$ht7wLMVb~(ITVuq+`Cv%GZ%FEn-wNXb;0BX}4wz
z)+uFpeS`(95joa8FTRLkvXw+_Mxo-Krb<?hcP)yw$W03JC_w}}xv^651d5{<a0G};
z6*q#b8CEOQjIy8|`o=T>=%W&ZGUW7&u0z*NE>9;+Q!sfANP2eV8q~i+u49V5gknlT
zqApGfbQEO$gj8i%pdb=0Zq97viZm{$CxDX#R*2F9DDHv*R|y%wFT6q8;ULy*Prz(~
zM@hPsjzZ+@zYnpGPsnc0)21YD@#o}N%eG7o3I3oaFI6v*n;JkEiy_Y)*{_vhW*-Gb
z@OGUBKAiUi15>tLPum&H>!cU>bgb~1Ita-Doz2Km*?!Q`*uAI3OK#XTGttX^K@{&Q
zJ?s$HlPQ{_V(R&RQAHTcQ|eqA>L@o^GuhTiL~Z~I2y~{*D{#t~G?4zT5YYG#SMkaN
zqtpZC+^`UZpoiR$aBw&07uB!k5;k}(Uh+%_2YcX|)s7$Ztf;uKJg^2-d9A3cELI)U
zS+__7Z~Czt%!mW`IN34TI=nioigHD#e@!@t#)F-R`62_Rbm7hISKPDJ^9EAHxduWc
zmWv@`Lt=YHqh|uUO6JhIx$Q`>0c7xb>)nL9xxnXj`}=ifwO)3OX}!d&Z^`?7G7tPC
zANa@EoEDd(Lb`+41KO<2n}DH1<3;RduZwrD?U|^C7W%c(IDJu9dM;HIoRFO%&U0u@
zcWazzM10;z1kf_^M;XS$a=lm4J(|cCa>i05Y78w5ZgyQgJQu`-aH5A9)GSZ#G+hfP
zyvw7FxDFtWc3A(qIZ$ljJuo!=wRO;cE?!Dn|NT~2QR^UB)FnpzZP}-K=;}}P5>=n-
zISjsHM!W%Mg!2Amp6F_4;WQiMJjnHiwwr~I>Uk3^1)l)(hZx9@ACvYPuwuabVX)Gp
z*EKO)tELNH$~dl`(a^*7-#O^2Y`W^QI-YngAJ&`d7n_pB@bEX$lvH`WbKBY>)ji!t
zL?(+KNU_=$;~j(EcE@u^Poi*s>2hB1${PHfG$K4|bvHd;%X3{Eq7AXF9_eczAtv#-
zEyqo~PCo0^gnW|lm8{GjUX!N~9P;jqk3PDnAJcqW96{(&s~dddQSVPbEm>xfo2HRj
zZa@^7@sL^KLKY=tusPoJPQid&`DS$Y_S2_YYxo?qmEA2|eXx>N$2`(I`lvH^#O{MX
zv)wk5ev!lt**h=k5762m7Hz^k$&9iIwRD^m-D(LhjW=}nQEcnU?pUAo;(OO0;mJq}
z{k=;?0Ba82ucK?Y&Ri)$kIh)Mtw>i^O8eX7dFf<lYu>PG8An>$I~ghTPqQ%xav;}n
zX?o(QTwbi)O=M@+hqy!K=daQ@rz(95J{a)9oidhFaJi2VUkA@u0oc{WtD~B`jb1D-
zmzjB9CX(${WAuEn!`QPcC%0v0kLjI-!qg<hFB>S*9p#a0>hSi0m+mx7RSZj8ZMAG|
zu@+Zu0fTi}Av}BO-pxJ5V($_99hAaHw_Oq<gYa`8z7Gqr7h!BRJLAhfOe~vF3iC`6
z-C%It3dhfDMif0RYE32D1s))1d%6PKwWq$gQ*b~7%>bZ*Hc1EupaETP7GegV0ZhjE
z6zKHYVf?v7a2|Pt%>4z&7W`=nME4fUqvIeKskORAVxNfY7<^?Cngcu41F)Btn;;<A
zSwtdT$csee(OIhCx#F$JIAW|(s{-Q(#2gBPDkRXV@82iP)@aWpTyPC$=O;4?pPE%y
zWn2kfI!(U=H+90usKY3K$B6QYJ_>l~#z@wXKAX0k#0b8PMC;wH=to35=a;c5AGjCi
zdP_>L)tc%&C_f77`#}pPD!-`oy%&Z)FATWE@UE&1Z0j05^m!NEO{-uz&NYb?8udlc
zP>q_ES9&37ntMLK_~>-qYWlEl<0E<FsL6Xg!d}kA*BaP8JxCjX!|JPNk)gHEi2aXn
zWFlGfL6~FGvqbf2g~J48L?*G|%*c?M12Cy8ck17`)QhulVy3X9G%ydED45z4vfI#Q
z_?CX2NCpQ!vMZDVGm1j*I~j7&854c+Oi~IvkkT|&2#ui@nt{F&lVlK0&ie#4D$B{Z
z44>cNBf*?-0TG}3S5okqc1ze(PG{J48?9uRV0P8sb1=wNasm#K#-bp0yS6Uj>FNmt
zB%f4gZ)iwm1du9GO!GPCjVa1+cT-*<k3;H&Zj^?71OQ;W`^U@qdqsDi45^?0G^GAp
zFRv6v%UCk!DOo<gypk3#YuU+&BzEPq*zWdx2hbw5D-=}_UPuQcDMyv%S{~LH@qsEy
zp2p{{WsN8VTj#2&xY$TZ&-s<7G|{x()b01m;<5qeJNCo#TE4I`jdzs}EAc{}^$&97
z7pxTNdw4Uu8`18JbfV8g<-6xFH=P{Yy%3u-PxDXOT?C&o_rMFVI$^Qdh^G-wKq=_o
zfDg#lp6(gHj(KaGy}+}cROvW0{j7hM{Pnol1$n-DI<|N4He*GWk&JC7pq?4J<^z1V
zj_RQ`9@CB&<N3TJ+2&EJ`tC$PmZD&WEb*NZHwBVWU^m;#g9g}~l$VBP*4af<Ly`?-
zaKMXqe0<>u_jLB1$J!I%eW`4?*5K<+#z;OnCF0E4;(TVV)xuD1a`K+%cu}*Z)|<aW
zj!0#zxq1mv@cB4T6|2#MrotTcb5ANsfR?8Hm#A~B?T<chpqZf82iDp$UHy*3s*)oW
zM+8SJ%;0)IaJy#d3tC|am0p9I<F<hBwNpqzu7$a13D_R;&{flcPSg5poI!Y(<qK7f
zYB5q|-p5ab9yGr>aGkjM$8$W;o3)=ZK>&aWU~~BQ?8>Fm=98vC^yjAV_&Nifk)wsP
ziKB%9y`__#t&1BR00jJTPUauKR8^h<pa8WJ|7Z@6lPp8Ag0_o{@S;~BjzR6Eop77f
zq8K$I3thd@gi3x`f=9ajFnFI?Am+=esz2N9c_wczY;^8AcMnENpH5K)W2hugpPlWh
z!@YDPqB{T=Bj(R+0_aA8A@~f-XGCYgilg{Y86bUSoiADGgo}rxLPP0TH~mWW)|2KP
zX0q~E6+pFvHdCtB!InjV6P1*Xj6iu3tg`bY2%Bg>C;Epdm)i5;E=6u%aw-)FC<OAk
z5wlD1Av96M^v~%1SkGe)P&$hy_hQ=d=ZrF3p-_|O<3QsXsUzMr^JM8U9_Mjl4T8AH
znE0p>s5!nI7+aU$z9QxMj9-5Sf~{I4(g5}q6Ozv{<&H^%&!=UM&1{7-<vB*}y@nkO
zm|jsSe-d(u*&Sk=SN&3MnZ26a$uJ(lHNs9EuC*v-$nx$g7kGTq#w4zJV5oMkUBTg~
zr8yW4AxnIUpy(&xFyV~zl#mgSo}q5?V~2QSD?;>J*wK3|2Ad+hw)@DfSM+;z8VG9w
zsE{SS(O_B>NcH+Dhkk1(Yj^CAfq*c8Zzlp+`|7}#I{sbzKL-M`U)28J4hT&D3J8Zf
zL$;_)NUbC%2&yAPaQ4=pK}bo#Q7|X{_FoizE^C=xj#ao=a$sBfUISy?e0gxtoj@JZ
zjBR#c_m;mY!fr)dTl-~C>f~OD5&!2FdN_lFi&N7+X@~2hb%z&Si0h@Mu2r$NoF!rO
zI7gcqmzCHn1iL*|FJJkYPGfI(z1f9&a}23%-BY)5s8&T#M<c~g`7k%NY+i)Xs2wat
z`4LA4R;?M!!2d&SRn;8|)j{il`e~Dyvr+wQMjN{t+j{j_ZJpzVkzL|T#wG^ayLwv}
zdyAB7Z4HWd*vglJi931~{P(-m)@(CjaZ(z$l9<_{tZ_>pKQ6F0DSzKFT;d(sjm=x1
z51y5t(kP%Y;JcBJ)j&~{%Az5k8l3i(R+HKvy{JkDL3VL|53VfXooUv|!d}W{!%w{s
zdp{G@TP(f()?9fgaqVgx=6+>mQW$GSRYxkn9`NO>ck|KK;r5uC+2QOIXvj(}qf+53
z)HLhztbv8(10*_cJmC!48pU33q@(SxZ>!1my2{0p)$++e50Ru376;A&^Oh%Ym5kX3
zP&LY17N6>DuuNhAx3y80@Zj?bBngCAG%xgMf_uXe8HF6s#|_qmRauUL%}uHmAz{Jp
zvh6>SiqsfD*bQ0+<<`9ybZCc`u}|R5k0*;8k)468SI2Yh`i{}j-vBzha41ZX*J5l$
znOi}~qaqCR&4Y|7XZ``^840*eo;Gkt$cqp7sFp|1w5Xd64wEwlm}St?UBTvymmMCc
z0uvnZN0NoO+AcG!A}}G6<tP#Iu~62gNRaBbck}IeOsXg6T%2}3ebp^?pFa}&nh!F~
zB!=Wq)W})mUtroz6?sG{rXQy^Zn4q6s=RMVPD9X151jp3tjunaRa^_w!56*2aL8oR
zpsas8*0&-{663PxQ)KD8SCIh{fZviKW;^_8T*`KsV0z%1Z3hf*Y7X03WyOuOdRH78
z+5s*m^o<1O$k=I$h9-wn`zACgq(vUo{cDBWRUVv48+SAX--wdvSyD&^d#O^+aO35C
z4f}jOwM;$lqr=PaZ&1E1_ekmjn4^Vj%V-~<ESa9c49!CHIZyi$x`LocOl(hPwqwr;
z8=d%9Sm74w$HSl$;#0JM_|#+HFyfMN8k);MRWc$;$4aPnN}>Q9WYH~|+;fX;!IPm-
zF27((_qq~~d#J-R%h`g7p+eGM0HA4_%#f8()j@}OGslM3U*R)DZB*!*J1_?FDJR?U
zNV-kF7(K}*OJn-d14aCqg9pW4BW|59lWDOF$vHN{xf3cZi49&5B1$w3Y3(`?hFK!K
z1U;HI{moF<<i5Q!&nm=v`m-4)e#5o)E{v{CE>Axgs_FJ-Z9_|wBZuj$@a!-`WN@aB
zy;mlyH489=-a<D*iAcWCjd&8KhGZsnkgr8JUvxtriCXA;q}?`h073<p1^m}lPNLFP
zea5mon(!%BKv1NL^us1pi<|iCR?;H7wkUd0C;XTNH@uaAzh+H)nn~<vd$_{8ZtfZ%
z0AHY>ZV7S4S|em{2~9uR5vPnW*|Su@K!!Lx|FDz6Y~N;Cn3)&}c!;6#5zdNO<VW|m
z#qVh6LRd6sv{$QU3>7zCLx@5Lhs1*REREW^VfX;rY!_;RX)hq%xF)=a>qpCew>@=z
zp8|nbNW^hN1({v1N_tSizU7%~VD`O0DND@O-{3jDm?+rGChDx?5Qj@XBT!n{58r%O
zlw|45H>sv?L~oZL+;89>BXTewfRz9kjTwA?jL7B^+fVW__FqTjUoUo$iAw)}9^TTC
zF3;&jUyfjX$a0yHHQT=AiKd<CGb9#$7fYE!i4&J)o%5bb$=jn;?cM{HaTaYyF(`;v
zDp&X0{LYDB=T%y^9J*fX{oYbj!mP&gxVU1am;{DTURQb7)1G>Hs`*PR3{X~k>z%y^
z!dDx&B^F6jLEVmc#SbsWOspreuTkJ!?Z%t1Q_T1AS`R--Y|smss3wc&msPQTGLWG0
zv|N3tzP;7)!dr@v+$em<N?j_sSMON#q4<1l{5Asd8ukEelZo$g>?Fh4g|*Lamghbz
z459q$YXlNk0;$|;ZXFXJ0Rw-*)Ch&D>U_L4*2o)YJQwto82q%$BYy=DsPZev48)b;
z)7PF2oOk>8(Ba!oPWBmLo+)^r6K?tERT}k2rYToF7<{Mlifk5j4IOmU5K``{Z^>s8
z<f-{fPPdlV_>a{^H!`>o<qhSI>Rtmv)lmY^9)kKU@6@eemGfl>q4aNh4Q_;W8nr5E
z9}H2_1id5orO`#VZ8MsOIt_8OR(krzTf!L}@*mWS{8|e_n2=q@_%(Y1*;He0$B|=Y
zH<;(G(hgL<V-!_OvDD(8C9y2(M6h#V#l<ORUmcBfv2an{=9l!QQGc+06N(aZ>wuTZ
z?#Y_8(bW4q?S)yK!BzHs-l#)f41d~$$WG;b6PHZV=ct#jdr3@6oXgkyr4thC`F5MR
z;g;=qWge_@qGPC!1TP5e)Uiv+!YiZ`hQ*#arm!WtbAqIHpal#}zwf6Zr4FHIb{Y$L
z9}V2UU0HM{Rm_NV?oJFQ`m&fsVGvN1wJ1?b^jvR;>n&+4wN#0DosyuY-)Bo2wQT{W
z<l2D1sz{BycQUOk{p1#JgI_h4;*D_UOBuEJ8Vh`3QxCgLeAh8sJUp?7azV?D?B6}Q
z*QnCO>J+$KE-t>Wn8U>-pH1r0oCO!xv%7i8!=CUmCtP%sFFz#N6lYkt2=Q4gvn6Y%
zg%GUYp2XYH${os4Kx4uRXST9&@jR}_I~+Qv2LlJy1;8B05@-;!b+_(oKB4gm>S218
z6D=zIabTtmw`$XP55=xO8HtRrD}m@_K6BX3rN6BIY*)HJLoT4nW}0eGQzX>8zNE?n
z^n{Y5#;vPA4M#jRLZ}nLBl~SzCZ0)&wh3l|kyYp$0c#W@;RZ^P!TX&Td-n(R-VQJ2
zrh=7<*B*MFck=Om+h{$?PR!9wb31jMnhV%PMXJWkJth=%<jVqe4q%dZC>xe0+r}Xm
zQ09?V5_zL#*|xr*WE3k3>m-XtOGU$14XVU4AJqt2Pj{e>11AV=-e8|GGp0!S;={9>
zgG8h1#g(WAL^bptFF*M;wZ41al6Nyi0tU(y&qTKo57Y!tz;vh*n=R>E%`;xIcQh-l
z-cY_Z9tkLpsd=}a6TVVaQyM=5sg4zG2v7jj!Pl$zW^Zjbi{$at)7I-^s~xjoHiZW6
z6xy@^3g0S|)=zB5ey@@^kv3!bz&~#V9*D*IHZAX~=Id!TeZvnQ;Z@xUZOhMAjKD_h
zvpyLn(OjrsZ5et!LnFOPrz82+`hxDd^&&9aOP0(XXSaEni$&C_C>n9jw1N;2L<Nx!
z2=;>2<V0E|>5Xfv*pN_;9V^JlmiG!>EF^Z+v-a~V!^Qce)KhDdZos!%`qiZia^4++
zSXtg%^I_$jg|~qV;W<J<fNi=~N9WqMm{V}d&IVu3rTW6f47TIEE^%{wovDEkSJ-UH
z7sSkWZ0cq;ET1F@mS06~?^^6MsmL@@f=F?(k(x}h<gre&EXfEo@ep5-hKS2}DFZ-W
z@5)I<<%NTvH)_LsyX(l6>Zrh!U|bBR&F3huK66)<NpSs0GJm@^LH*5&{l>b`Za1g@
zQVD$b><9%WTRk=242j|N0ZP8?S)C7yrTsyAke9!k+hRLWnnV*wDyPRQxC*!a0}N{8
zbZbjl`EZa+G)dvh6s8LuW*D7vU0xCnPz~;iT7wrN-x<v=aBdL#fzAxjE38VDgI!`W
z!j2O+i3)^^)1IdR3mj#6xbsUJwm`NcNX7G1!>lK5MF_0z+-xh6VZ1PQ$yc3Ye0%Us
zp?{GgrXa3z=wePrv$1$NnPp%t5p!f)@cOmx104tM)JU-u$8!i;GgsD0lyq@F=FpLw
zti=%zL+UmU+iWQFmx@FLjQkAi>x3!>Q+GvH7!%j+Ovbkw2lH>@>6P9y`j^_;CsV5;
zpv8*_>)$}{ntRWBGUM7GiWM%X@r_bWK*cQ~4&iZ`VD5^n(0XTLzg+A7#ExnuTMe!~
zugtr!6m)rf)bW~XU#IOR--E{3eS%Wqfuz3C0xk6A;<@aDC<D~3%=7FS&XSZprO}Wh
z>@y*8QHlhX+Hg5x>&B9$NSSO$K8c3<Yvg$IWP<lm%!7EUjFTX!^pggtEvMDIHd&|;
zo9%b&q-gn55kbUpgakvgjD@d{FwS$`lkme;C6$BC@DylJ$NE0g*skU*Ld$E8y+bEh
z2_2t(Ur|VWY3LBZXc#{8DG}`Dr6IzCN|SD#{-u3R+v$3CTDH?d7gj@rtZTNek`RhM
z2c$z@R9UiAInBp`nngThSyGF14(iH;{N-L$lNejZitP?mg0xhP?g1DJUF?O^8lf)o
z88Y~{4%M-rr3yd$QJP^ew4oTD2r)JLYUI@T&KZ^Z&e;i3>oWJXCFzXNG<w1if*5Vp
z_IyRdNtW(!nrd|2xO~yj1x8U2o$fPHjZc|Kj@Ii}fX;?EXQZpCj3=ta;Z3<U2pXu_
z!Jsb?Xd*!nYh}(5>R?_j>jou*&4)jq@2@Y&BvT`r_1P%<ni44{)=xmgk^FRQjCND&
z3|^$0f?E$UX>QltY*5QsHjQG#og@^vDP-$_1*X#9oxB}uTJTV@yPcP@uAP_7AX&1p
zAUs8aRX!6FXGFQs1XNOv#-wz<43B+zUTZ7xl}j6nT~`Q2Qlz!Bm%iy<?$V8@(xJZF
zR;-`s%MKn5nLuw2_Shf|@z8LM9$5{T0UQ}Q3Ga)SQbI_M@~@{~zJKl?fSoYJp{KOn
zq2CWvnj&H?R{b$VB)NqUF}-n?$C!UfFwKRWDncOAu@$tFmWYOtuu~-$QA)W6vs<xd
zh8!FsAMHZbdMs@)`?b;xYsCBG4!ABdGBTw3(CA`2G+SbHHr|p%%?xOFa5QCY{3_Ja
zlHBAlN0B%*e`hglhyYC$VL^}v(08ZpB^2XubZHXhHhbihdBO41dad1t>vhjm<M!^d
zh119ng^FyD$DC^_;C-tGuy-06jS^#W=DI&_Ck2MCR1Y2##_#gh^0Fs{`&*JTZm~W(
z(-7#)*Fa}l0-gC1=*+BGNv<{Gy^G6A!YD@4D$RK)27*NIDAXR!osh~g$*q|=_GC`-
zZ623V>_FXCJHk_rMlhO)J=yb8vv-QaxD!~?!A3Y?1_+BFc?ca48wedHsHchBaHbI<
z`>)Yq!rmD~@2q7Pi3Ljcb1R!WZBLb3aS7L%pM?sWPMmxJ+w#8aye)e!*tj<)&S6IG
ziDxiJdc%Ri?S+tns=N~n#%C4IVa;m5H%y*Lqvx7J0}H)yeI-DNSf=%c)~TDj^N4*>
z!Hf|ed#g<msvCNCUzfGD!61dDroo*7cWQCH0xY?RiYXo>^uz#OzZtk{5WjoPEnr}d
zFM~h{pN=IY|Nf1&lOJnNqeKpef#thy(#+^Y5u90o_1W`kK^@iw^I+HzjOozRtP3p_
z)*9q`B?DuBOlTvP8d|Ir8)f(!&h)y6c2>`}nt?r!A`r@NTHIfD%QbGbNKd&Nmvlv^
z;y8=?beI}G@*3UK7i1$|anHK%x9pNnRH+K{DP4yhi)#phyrm6<XLO3iP=E?0R0xtS
z>=+?0MpXM`M#Va^ii9%KiP?5*z8N}x{2lq`z{zst3^v9n6Qkn8baK5WR9q2PL<EWw
zNMye|1ay`EOK*GlCM0~yb_G7H9tFOXQTRxOE><(wQ=L>*J6lN95%v-cS-fOAGh?4c
zCoX~c-C>F6rM5<lELF<4kw=KkJ#BRMxHkO0Xti%;1coiXCxUBEUoye;uz6<Uiwr;=
z`LVxQ<-@J@kU<G_?Y(KWIv-&1#*%Y~CCz7GLyC@d1gJRn?|vM!{@9=xlC&Iqek<sK
zxwatKE(3Pu{h?xM8rFs)!d|bBYBt~)?D=}>CEF;GVVh}8z4B~|K!L5`F-TgYO&!=4
zYeC`ooaL=J&b0CsE}S>!Bt9;Je7_oFhr7S3h7+@a$cseCBX>A4{9u@a;H9}&vfs^2
zT$)U^8}|>r?YHwk`aP`k+674vX)VizHhf&Z-QEoRsC;&K+4S5|GUb@PImtjleg_MD
zy4+jKws$jCslK1swPv!J_D~-z9SsbD=aaoAWIPDB;c;^^ukC!C{84qVE#a)=xKB21
z7Ct4uus|%FlyEMpm{{%vc`Ufen>}Ak1SDZ8?^`aqZ?yEuaisOR{@{Ws>U*i<JX9`i
zO{!&q1||q-F0+dW2Ss%K(r;LkID_lnH$btKH}1A1OtX2WdiQs;lkF#mFsV+-gtC`d
z+{nn2A;3e=<Qs;SWM8=~!)iB8*u@v6H7w_pAnXdbf!NViQ`=<ZHWha+trVc|CE)jk
zVpGNJ+Un6mRh#REjJLARd)S~evIN{f3@QX{;c-A%Cm*KAiBpHmE;YNoWL6I_%3v}J
zfYM@h4G7xWu5gooLr>F&nKl9Yb;;BgPM$VZR=wa$-B}y8i5MYU;AAr89U-M|Qm+s)
z^RY!dQLG~#h?1PUi(+e@W_K&|hAC!+D+iuaCS%3>kIte|eIg41D}+O{RNuFo&11f5
zVcB|pEh1}u!J+^D2o_=1wwmZ0T~w%~c>v~826SMgZ7Nizn_I0Dl*rp1_VRs2o1pRM
z4Ka8C_pjD%+t_X(2Rk-u+#=MdvcRmdg$Dx6G8n)t!w$?cg1{^z4a_nc5Hi?<3~;uF
zY$va*60awDV!*A5X-!a(rbETsy45^l^2qBe5l^Arpa-|G-5?Hd!&Rvko`HyPZX_|F
znT`qTQ4(HFCY-ht+(zquanc*NN`d;MAf-44Dyp%oNfShundnZ=m7Xl}C6^QeH1*8a
zcQdo(Ez(p6Vm{40`z8crdjk|K*lmnFaC~Q8fKcU%9r<OadBGdL{y+!H*gS9(v?auq
z$p3odSPc4X<%<rC@u?mRHmm|)90nOjhD;>9ia&J|;*!>R>wW*-EyLpw9;+S^S{o4n
zpw0bp2><h>D#{;2czXj!XWQRBX8*XP0+Ov{`S=;2(r!B;fYhSC#}ChGFO>@RQ5Wf*
zl#f&m9+FUSrzvlpy5_M4w^0!E$?@Q<oU~|+l%nxrYntcna>})XJIL3CdjJLs>H0b>
zhU<ZLu|;Jndva*p2X^A;dLL$P?^-iql-(=|?4!;j*Qe74q8ZO#i+!jYyVhwJzVoJw
z@<d1jmwII^96J!1O6bQ5?UMW9{nw-W4V|6}&Toaduhka{2%+qY{4w&fP^9n}m1Yd1
zL62CTW#MIo+)@%vNk<+CjhB1LJFK|GnzT~j$B$A&o33YObgx%OoodsDo@Z=T8#Y8U
z6JXiSA40i3!=+xm+|G4onK#zT7(0aK&Y3;Y)j@DE)Iay^CaZ8Avmp_}-Xkm~daabI
zKcJw<CaG?M07jmv-Gnx)DM`PIo7}Mwc}{Bx<=ZORt`(y9+!Q9X0&yH5O&+IAGgt6h
z4Qi8Yl2u=h-rdAN$%q->6uw5qP{j-eCsb{YD#eDtkP|swK2kSltCSf`4gIxZ_ICKW
zdyRsQ#nf{;=jJ&-BeBX^4xbYfSP9n95u5?Xk?bQr#k}E~gnVzOX`HYtqUzK`@EM3Q
z_zNKhp7r7S8yW8&ibTW4?Keg=+eTr`M+o$n(5m^bYS@faG^OJ71u#%EdO%I%$%zz8
zd~}6Is*`&H6-3jnuqeQ8RH#kH{KP@C4pV0knv!r>a+H$Bk@|?0qK>a;+4bxSxII{?
zAg{6q?RmeXwqXsMf4Er#+xrZ;*RhA(!rW%L@Ls=c-5{?Ng=X4REI}^$Bo@ox0u+MD
zbB8j82WsyOZ&wl`S*1`#)C_?mj8E05IHAJMw_70r`ZCs4O+Qw#L}P6FP{D)KqI?$_
z*bNS&*Vo)I!k%zl(XUf-@TKOzo623SM&0MWu#+#QWqSsf@1pyO^G(B1<AZ3~A`+|Q
zj^X!^ZPHY{)#Uz-8c&E6tnb6R<#t1o1)|;Ai7WQ*CugVY|Bw!1Za(G$C;(6h`6wL_
zP&6>Kf9&!7Sv(K`tpDHp`ylxEr?G*v0mGkGpdbJskE;2dDflO*g#R#QWMKQs!0A6)
zeB6rsNX}bwZ`KS70BBSO0C0b>SmzV=lf{1;76H=z>qWD_psWb<bYYhC2Y?4b9q50R
z{$G?WZ0zkEo#{;6{_){#Vq<S@;B4~OMVY7gw{sqg^0@97E}qIN1_A&S1B)Z}15%yO
zr@x6L{14yh8Q5D0xj0$anm9Sh+8LWz|MTC!EcN43;U5+C2NyX#)e?9hmnAR&K=KKf
zB-p=K>VI=lGq83sQE;@gw{x<1T)g}r=*$hC7eNE*xBw?;MV`>%f&Z`Q82-yIk~a1R
zM$Z2OlQEBXWOP6#Q9veqPnb+U`>&W782}krIJ^H39QfgC7&w6(j)7toeZnCEnEn1C
zNTYwM=vPhhpP+h1E>6JnW+skOz#aRxCjSc+orK&b6(E&QKzHywp`wNSUr{l(voWyv
zUz$b)+u3_KAcJXOOXYsTfD`q<Vqo&h#P)w_5h}-V1`<F5`aqHLJ|Qp!jG_NUZJ0S4
z*qb~2FKR6%Z>OaPQiua;Q}79eOpO1Ef`u(`R{>BM|C>r@vYkfnfl-$f7{K_S(9i*9
zjsL<E)^<h)j~tx-2XWA)Dt<o(lIQ`p2d*b1zF_}XB!CB5{+H&!^l;U}3(TZRz<nKZ
zPw@3{{~rE76NsLvi?#JHLb;xa?ca{(?|Hvyzurh|9<l@gz9E4E@Skwvz<<i=(eu_8
zuT6}9n<opVWdA>70A2l$MEv;q$Jf);?hx`X3>y<?b35a|mD&kE?rWzbCT0)<ceH>2
z11t6u)=fWI{QYhiU}A^QRQi9yk138CXr4+Np71>|g6i=A0GLnA3xz)=Y~*fa{j2j#
zK;wiz7=QEtQ|;4U1L6<H9|W1>o*Fkc`Adh`sr}o<kBnu3j9W%s7UqEtK?UYKk{^uL
z`FQ==sI`HiiM12`e{_xE59}X-zBlY^Yjqh=F92i70|Nj+^aQ9s`A_Ws0Q$X?JaeDc
zz+;E!g0Tv21L!bkVCcem0)v+SE119B?*y!bpF1%k%{$tAYGUj>Kq*cElM~?+`+5bx
zvTyy^ZTh9S+6|x9%3}{SYnv064d|$pZD8bkf&x?gE0q6mNbaYu=wr12kG*Nvxgy)&
z1Isc9Ol%ZSkSgbXh4i1d3IV~oek#^M&5rhUZy3k5C;*@-1M*X2BVGLs*gwMdFa39*
z`fvX|O69cb>0!dBQVAyq`DfPnSKu(Q{Y$BE0M8Tt*nedMO2s+rtJEkk1C#?>@l&ZR
z{MqOqE%>*4>VR(I_(>}IKp^9GseLpU06>HGXQ|-P{E7V^K);ttz)vubQX#<`Qyd36
z%;ry0$zc5z%-@yD81O{rOf+TF1<-c)pQJMP;#c;6FO`L)r?p}WMA5j)m<(eC0J1<p
zev%3g$FETSvs4IwLV6UXxXj3;9<VH#C_hVu+u~P9e@iMqj%puuxd<$lu#kIwB^LmI
z{QPIBAlm%~?DtYR`Jq&gQlW17T~=W#ehOr2@t0C@F#fmx{y(dn-Jpd4vx+g?&r*5&
zXQO|#;Qu6*pR>vqFsqnETH)RRL1I~dmWo^XpV<Ea^n0nu{Y6$`(O2x*2Rh8_Pf}TH
z`W4LIl?rLoj`ngR@WDu6R&oE6R9IVnW&ih5$<u#YE6-bZv{id`c#`M=0OhTpvr5^g
zU!nYGsc@S<MIr~5Cz&ln1Qys23I&c<o@SMXqhBHYEvXd!RIGfz9ql%+hi`XcKro@7
zrNRLWKmQma{43Z4TkyZy01)i=QlWbI_hibWR4_jNPAd7pF2NHZ$G?=ycg?4+dhCGR
zhaX7|0HreWrw-WJpN;;}g8y5o;56=QyK<*x$pb+oIe(T4gV3MY{{i%Ssnq_3RG2Gv
zMsI))i~W;S4&{CY^LM3E35-`Sz?|ptfKq`6Hm|20FnNVv+5f#%>`b24N+)o1BQbK;
z&p-zNc%S|(l{uwfq5Nm5AWlC;ss@$^-o?QI99R}&^q-~j+WS{Xe@iNkKNZWVZby3y
z!i-l*6aXmD`B^GwfxiL!y;S-&o|ft{SAw#H+7AM2X#v>aFrIWP>wy3MQ7XT$n;%o-
zqYQn3!R7JukFTelyX}#uw(Xt&QijR~PYFNDFwHO{vK1&pyFba0W%N%*|4_$&E5jE+
z8H$;xv1S8%kYr3h%g}J@mq5Rl;m%JojBeb~o|E>AJ^*^@^`B(uwE8QUU&%05@2S5Y
z?Hdf6r~p$rU<c^4r!wqW`<4CQSM|>**+3M8w}(QJ)Bu3cm!D<0vhgdF|187GpUP7M
zL_&g^W^x2(U%o$e?$!{%o-|lsqxyFeu`)5Yvo`+af*-JhKlu~bW3hg`1?A~Tq8IHq
zV855)&!u|2ROQFBVNXZHC?-#V{<GH}uUPqUNc1T49}gToe<E`e=co4nR>=BM?T=l_
z$5G0Ur&^xQ8vtJlcv3O{%IW{%922lgeje99mgL8++GI~kV(a$TF#l7D9`}C#xTO4a
z4hr!0FQI-tcks9q{O3CPaoG*!Nl7}x{$>96tJFXb{j(w<fN2Q;5C(o%1E(49BY|UI
G!2bcIMC%Cv


From d47d417dcece17c7c65c1989b7e2db21f33428a6 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Wed, 15 Jul 2026 09:34:45 +0300
Subject: [PATCH 10/12] cleaning up package dependencies and duplicate station
 steps

---
 bin/method-cli.js                             | 803 +++++++++++++++++-
 .../bin/create-apiops-project.js              |  25 +-
 packages/create-apiops/bin/method-cli.js      | 802 -----------------
 packages/create-apiops/package.json           |   6 +-
 packages/create-apiops/template/package.json  |   2 +-
 scripts/check-package-contents.mjs            |  11 +-
 scripts/test-create-apiops-scaffold.mjs       |   2 +-
 src/data/method/de/labels.stations.json       |   6 -
 src/data/method/en/labels.stations.json       |   6 -
 src/data/method/fi/labels.stations.json       |   6 -
 src/data/method/fr/labels.stations.json       |   6 -
 src/data/method/pt/labels.stations.json       |   6 -
 src/data/method/stations.json                 |  24 -
 13 files changed, 833 insertions(+), 872 deletions(-)
 delete mode 100644 packages/create-apiops/bin/method-cli.js

diff --git a/bin/method-cli.js b/bin/method-cli.js
index a34b73f..d9fb646 100644
--- a/bin/method-cli.js
+++ b/bin/method-cli.js
@@ -1,7 +1,802 @@
 #!/usr/bin/env node
-import { main } from "../packages/create-apiops/bin/method-cli.js";
+import fs from "node:fs";
+import path from "node:path";
+import { spawnSync } from "node:child_process";
+import readline from "node:readline/promises";
+import { fileURLToPath } from "node:url";
+import * as methodEngine from "../src/lib/method-engine.js";
 
-main().catch((error) => {
-  console.error(error instanceof Error ? error.message : error);
+const currentFilePath = fileURLToPath(import.meta.url);
+
+const STATION_SCRIPT_HINTS = {
+  "api-product-strategy": {
+    resources: "npm run method:resources:strategy",
+    canvases: "npm run method:canvases:new-api"
+  },
+  "api-design": {
+    resources: "npm run method -- resources --station api-design --style \"REST\"",
+    canvases: "npm run method -- generate-canvases --station api-design --style \"REST\" --output ./specs/canvases"
+  }
+};
+
+function printUsage() {
+  console.log(`Usage:
+  node ./bin/method-cli.js start [--cycle <cycle-id>] [--locale <locale>] [--default-locale <locale>] [--json] [--list] [--answers <yes,no,...>] [--next-action <resources|canvases|exit>]
+  node ./bin/method-cli.js resources --station <station-id> [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--json] [--list] [--step-actions <details,next,...>]
+  node ./bin/method-cli.js generate-canvases [--station <station-id> | --stations <ids> | --preset new-api] [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--output <dir>] [--force] [--json]
+
+Examples:
+  node ./bin/method-cli.js start --locale en
+  node ./bin/method-cli.js start --cycle api-productization-cycle --locale en
+  node ./bin/method-cli.js start --default-locale en
+  node ./bin/method-cli.js start --locale en --answers yes,no,yes --next-action resources
+  node ./bin/method-cli.js resources --station api-product-strategy --cycle api-productization-cycle --locale en
+  node ./bin/method-cli.js generate-canvases --preset new-api --cycle api-productization-cycle --style REST --output ./specs/canvases
+`);
+}
+
+function fail(message) {
+  console.error(message);
   process.exit(1);
-});
+}
+
+function parseArgs(argv) {
+  if (argv.length === 0 || argv.includes("--help") || argv.includes("-h")) {
+    return { command: "help", options: {} };
+  }
+
+  const [command, ...rest] = argv;
+  const options = {};
+
+  for (let index = 0; index < rest.length; index += 1) {
+    const current = rest[index];
+    if (!current.startsWith("--")) {
+      fail(`Unexpected argument: ${current}`);
+    }
+
+    const key = current.slice(2);
+    if (key === "json" || key === "force" || key === "list") {
+      options[key] = true;
+      continue;
+    }
+
+    const value = rest[index + 1];
+    if (!value || value.startsWith("--")) {
+      fail(`Missing value for --${key}`);
+    }
+
+    options[key] = value;
+    index += 1;
+  }
+
+  return { command, options };
+}
+
+function readJson(filePath) {
+  return JSON.parse(fs.readFileSync(filePath, "utf8"));
+}
+
+function runCommand(command, args, options = {}) {
+  return spawnSync(command, args, {
+    encoding: "utf8",
+    shell: false,
+    ...options
+  });
+}
+
+function getNextStepHints(stationId) {
+  const hints = STATION_SCRIPT_HINTS[stationId];
+  if (hints) {
+    return hints;
+  }
+
+  return {
+    resources: `npm run method -- resources --station ${stationId}`,
+    canvases: `npm run method -- generate-canvases --station ${stationId} --output ./specs/canvases`
+  };
+}
+
+function getCycleId(options = {}) {
+  return options.cycle || methodEngine.DEFAULT_CYCLE_ID;
+}
+
+function loadCanvasJson(filePath, canvasId, locale) {
+  if (fs.existsSync(filePath)) {
+    return readJson(filePath);
+  }
+  return methodEngine.buildCanvasTemplate(canvasId, locale);
+}
+
+function formatPaletteHelp() {
+  return Object.entries(methodEngine.getNoteColorPalette())
+    .map(([intent, color]) => `${intent}=${color}`)
+    .join(", ");
+}
+
+async function fillCanvasSectionsInteractive(stationId, step, locale, output, rl) {
+  const outPath = methodEngine.generateCanvasForStationResource(stationId, step.resourceId, locale, output);
+  const canvasJson = loadCanvasJson(outPath, step.canvasId, locale);
+  const canvasMetadata = methodEngine.buildCanvasMetadata(step.canvasId, locale);
+  const starterFileName = path.basename(outPath);
+  const suggestedFileSlug = starterFileName.endsWith(".empty.json")
+    ? step.resourceId
+    : starterFileName.replace(/\.json$/i, "");
+  const requestedFileSlug = await rl.question(`Save filled canvas as file name (${suggestedFileSlug}): `);
+  const finalFileSlug = methodEngine.sanitizeFileSlug(requestedFileSlug, suggestedFileSlug);
+  const finalPath = path.join(path.dirname(outPath), `${finalFileSlug}.json`);
+
+  console.log("");
+  console.log(`Filling ${canvasMetadata.title} section by section.`);
+  console.log("Use `|` to create multiple notes in one section. Leave blank to keep existing notes. Type !clear to remove notes in a section.\n");
+  console.log("Prefix any note with `[benefit]`, `[neutral]`, `[negative]`, `[task]`, `[default]`, or `[color=#RRGGBB]` to set its color explicitly.");
+  console.log(`Palette: ${formatPaletteHelp()}\n`);
+
+  for (const section of canvasMetadata.sections) {
+    const existingSection = canvasJson.sections.find((entry) => entry.sectionId === section.id);
+    const existingNotes = existingSection?.stickyNotes || [];
+    console.log(`${section.title}`);
+    console.log(section.description);
+    console.log(`Default note color here: ${section.defaultNoteIntent} (${section.defaultNoteColor})`);
+    if (existingNotes.length > 0) {
+      console.log(`Current notes: ${existingNotes.map((note) => `${note.content} (${note.color})`).join(" | ")}`);
+    }
+
+    const answer = (await rl.question("Notes: ")).trim();
+    if (!answer) {
+      console.log("");
+      continue;
+    }
+
+    if (answer === "!clear") {
+      existingSection.stickyNotes = [];
+      console.log("");
+      continue;
+    }
+
+    const notes = answer
+      .split("|")
+      .map((entry) => entry.trim())
+      .filter(Boolean)
+      .map((content) => methodEngine.parseStickyNoteInput(content, {
+        canvasId: step.canvasId,
+        sectionId: section.id,
+        defaultIntent: section.defaultNoteIntent
+      }));
+
+    existingSection.stickyNotes = notes;
+    console.log("");
+  }
+
+  fs.writeFileSync(finalPath, `${JSON.stringify(canvasJson, null, 2)}\n`);
+  return finalPath;
+}
+
+function resolveCanvasExportCommand() {
+  const packageRoot = path.resolve(process.cwd(), "node_modules", "canvascreator");
+  if (!fs.existsSync(packageRoot)) {
+    return {
+      ok: false,
+      reason: "SVG export requires CanvasCreator export support, which is not installed in this project.",
+      help: "Run `npm install` to install project dependencies, or `npm install canvascreator` to add CanvasCreator manually."
+    };
+  }
+
+  const packageJsonPath = path.join(packageRoot, "package.json");
+  if (fs.existsSync(packageJsonPath)) {
+    const packageJson = readJson(packageJsonPath);
+    const binEntry = typeof packageJson.bin === "string"
+      ? packageJson.bin
+      : packageJson.bin?.["canvascreator-export"];
+
+    if (binEntry) {
+      const binPath = path.resolve(packageRoot, binEntry);
+      if (fs.existsSync(binPath)) {
+        return {
+          ok: true,
+          command: process.execPath,
+          args: [binPath]
+        };
+      }
+    }
+  }
+
+  const scriptPath = path.resolve(packageRoot, "scripts", "export.js");
+  if (fs.existsSync(scriptPath)) {
+    return {
+      ok: true,
+      command: process.execPath,
+      args: [scriptPath]
+    };
+  }
+
+  return {
+    ok: false,
+    reason: "CanvasCreator is installed, but its export CLI could not be found.",
+    help: "Reinstall `canvascreator` or use the CanvasCreator web app to export SVG from the JSON file."
+  };
+}
+
+function resolveStartLocale(options = {}) {
+  const explicitLocale = options.locale;
+  const defaultLocale = options["default-locale"] || methodEngine.DEFAULT_LOCALE;
+  if (explicitLocale) {
+    return explicitLocale;
+  }
+
+  return methodEngine.getSupportedMethodLocales().includes(defaultLocale)
+    ? defaultLocale
+    : methodEngine.DEFAULT_LOCALE;
+}
+
+async function maybePromptForStartLocale(options = {}) {
+  const selectedLocale = resolveStartLocale(options);
+  if (
+    options.locale ||
+    options.json ||
+    options.list ||
+    options.answers ||
+    !process.stdin.isTTY
+  ) {
+    return selectedLocale;
+  }
+
+  const supportedLocales = methodEngine.getSupportedMethodLocales();
+  const rl = readline.createInterface({
+    input: process.stdin,
+    output: process.stdout
+  });
+
+  try {
+    console.log(`Default method language: ${selectedLocale}`);
+    console.log(`Available languages: ${supportedLocales.join(", ")}`);
+    const answer = (await rl.question("Press Enter to keep the default, or type another locale for this run: "))
+      .trim()
+      .toLowerCase();
+    if (!answer) {
+      console.log("");
+      return selectedLocale;
+    }
+
+    if (supportedLocales.includes(answer)) {
+      console.log("");
+      return answer;
+    }
+
+    console.log(`Unknown locale "${answer}", using ${selectedLocale}.`);
+    console.log("");
+    return selectedLocale;
+  } finally {
+    rl.close();
+  }
+}
+
+function formatCommandFailure(result) {
+  if (result.error?.message) {
+    return result.error.message;
+  }
+
+  const stderr = String(result.stderr || "").trim();
+  if (stderr) {
+    return stderr;
+  }
+
+  const stdout = String(result.stdout || "").trim();
+  if (stdout) {
+    return stdout;
+  }
+
+  return "Canvas export failed.";
+}
+
+function exportCanvasSvgForResource(stationId, step, locale, output) {
+  const jsonPath = methodEngine.generateCanvasForStationResource(stationId, step.resourceId, locale, output);
+  const exportCommand = resolveCanvasExportCommand();
+  if (!exportCommand.ok) {
+    return {
+      ok: false,
+      reason: exportCommand.reason,
+      help: exportCommand.help,
+      jsonPath
+    };
+  }
+
+  const outputDir = path.dirname(jsonPath);
+  const outputFile = path.join(outputDir, `${step.resourceId}.svg`);
+  const result = runCommand(
+    exportCommand.command,
+    [
+      ...exportCommand.args,
+      "--input", jsonPath,
+      "--format", "svg",
+      "--output", outputFile
+    ],
+    {
+      cwd: process.cwd()
+    }
+  );
+
+  if (result.status !== 0) {
+    return {
+      ok: false,
+      reason: formatCommandFailure(result),
+      jsonPath
+    };
+  }
+
+  return {
+    ok: true,
+    jsonPath,
+    outputFile
+  };
+}
+
+function printStartText(data) {
+  console.log(`APIOps starting station check (${data.length} core stations)\n`);
+  for (const station of data) {
+    console.log(`${station.order}. ${station.title} (${station.id})`);
+    console.log(`   ${station.description}`);
+    if (station.suggestedForNewApi) {
+      console.log("   Suggested default for a new API unless later-station criteria are already clearly met.");
+    }
+    console.log("   Criteria to check:");
+    for (const criterion of station.criteria) {
+      console.log(`   - ${criterion.label}`);
+    }
+    console.log("");
+  }
+}
+
+function printMenuOptions(options) {
+  for (const option of options) {
+    console.log(`${option.key}. ${option.label}`);
+  }
+}
+
+async function askMenuChoice(rl, prompt, options, providedChoice) {
+  const validKeys = new Set(options.map((option) => option.key));
+  if (providedChoice) {
+    if (!validKeys.has(providedChoice)) {
+      fail(`Unsupported menu choice: ${providedChoice}`);
+    }
+    console.log(`${prompt} ${providedChoice}`);
+    return providedChoice;
+  }
+
+  while (true) {
+    const answer = (await rl.question(prompt)).trim();
+    if (validKeys.has(answer)) {
+      return answer;
+    }
+    console.log(`Choose one of: ${options.map((option) => option.key).join(", ")}`);
+  }
+}
+
+function printResourceDetails(metadata) {
+  console.log("");
+  console.log(`${metadata.title} (${metadata.id})`);
+  console.log(`Type: ${metadata.category}`);
+  console.log(metadata.description);
+  if (metadata.steps.length > 0) {
+    console.log("How it works:");
+    for (const step of metadata.steps) {
+      console.log(`- ${step}`);
+    }
+  }
+  if (metadata.tips.length > 0) {
+    console.log("Tips:");
+    for (const tip of metadata.tips) {
+      console.log(`- ${tip}`);
+    }
+  }
+  if (metadata.canvasId) {
+    console.log(`Canvas template: ${metadata.canvasId}`);
+  }
+  if (metadata.snippet) {
+    console.log(`Snippet: ${metadata.snippet}`);
+  }
+}
+
+function printCanvasDetails(metadata) {
+  console.log("");
+  console.log(`${metadata.title} (${metadata.id})`);
+  if (metadata.purpose) {
+    console.log(`Purpose: ${metadata.purpose}`);
+  }
+  if (metadata.howToUse) {
+    console.log(`How to use: ${metadata.howToUse}`);
+  }
+  if (metadata.sections.length > 0) {
+    console.log("Sections:");
+    for (const section of metadata.sections) {
+      console.log(`- ${section.title}: ${section.description}`);
+    }
+  }
+}
+
+async function runInteractiveStart(data, options) {
+  const answers = {};
+  const providedAnswers = (options.answers || "")
+    .split(",")
+    .map((entry) => entry.trim())
+    .filter(Boolean);
+  const useProvidedAnswers = providedAnswers.length > 0;
+  const rl = !useProvidedAnswers
+    ? readline.createInterface({
+      input: process.stdin,
+      output: process.stdout
+    })
+    : null;
+  let answerIndex = 0;
+  let recommendedStation = null;
+  let stoppingCriterion = null;
+
+  console.log(`APIOps guided station check (${data.length} core stations)`);
+  console.log("Answer each criterion with yes, no, or skip.");
+  console.log("The guide stops at the first `no` and recommends that station immediately.\n");
+
+  try {
+    for (const station of data) {
+      console.log(`${station.order}. ${station.title} (${station.id})`);
+      console.log(`   ${station.description}`);
+
+      for (const criterion of station.criteria) {
+        let normalized;
+        const promptPrefix = `   - ${criterion.label}`;
+
+        if (useProvidedAnswers) {
+          const providedAnswer = providedAnswers[answerIndex];
+          if (!providedAnswer) {
+            fail(`Not enough answers in --answers. Stopped at station ${station.id}, criterion ${criterion.id}.`);
+          }
+          normalized = methodEngine.normalizeAnswer(providedAnswer);
+          if (!normalized) {
+            fail(`Unsupported answer in --answers at position ${answerIndex + 1}: ${providedAnswer}`);
+          }
+          console.log(`${promptPrefix} -> ${providedAnswer}`);
+        } else {
+          while (!normalized) {
+            const answer = await rl.question(`${promptPrefix} (yes/no/skip): `);
+            normalized = methodEngine.normalizeAnswer(answer);
+            if (!normalized) {
+              console.log("Please answer yes, no, or skip.");
+            }
+          }
+        }
+
+        answerIndex += 1;
+        answers[criterion.id] = normalized;
+
+        if (normalized === "not-met") {
+          recommendedStation = station;
+          stoppingCriterion = criterion;
+          break;
+        }
+      }
+
+      console.log("");
+
+      if (recommendedStation) {
+        break;
+      }
+    }
+  } finally {
+    rl?.close();
+  }
+
+  const result = recommendedStation
+    ? {
+      recommendedStation: {
+        id: recommendedStation.id,
+        title: recommendedStation.title,
+        unmetCriteria: [stoppingCriterion]
+      }
+    }
+    : methodEngine.evaluateStartRecommendation(data, answers);
+
+  console.log("");
+  console.log(`Recommended start station: ${result.recommendedStation.title} (${result.recommendedStation.id})`);
+  console.log(recommendedStation
+    ? "Reason: this is the first station where a required criterion was marked as not met."
+    : "Reason: all checked core-station criteria were marked as met.");
+
+  if (result.recommendedStation.unmetCriteria.length > 0) {
+    console.log("Criteria still to address here:");
+    for (const criterion of result.recommendedStation.unmetCriteria) {
+      console.log(`- ${criterion.label}`);
+    }
+  }
+
+  const actionOptions = [
+    { key: "1", label: "Review station resources" },
+    { key: "2", label: "Generate empty starter canvases for this station" },
+    { key: "3", label: "Exit" }
+  ];
+  const mappedActions = {
+    resources: "1",
+    canvases: "2",
+    exit: "3"
+  };
+  const providedAction = options["next-action"] ? mappedActions[options["next-action"]] : null;
+  const actionRl = !providedAction
+    ? readline.createInterface({
+      input: process.stdin,
+      output: process.stdout
+    })
+    : null;
+
+  console.log("");
+  console.log("Next step options:");
+  printMenuOptions(actionOptions);
+
+  const actionChoice = await askMenuChoice(actionRl, "Choose next step (1/2/3): ", actionOptions, providedAction);
+  actionRl?.close();
+
+  if (actionChoice === "1") {
+    await runInteractiveResources({
+      station: result.recommendedStation.id,
+      locale: options.locale || methodEngine.DEFAULT_LOCALE,
+      style: options.style || methodEngine.DEFAULT_STYLE,
+      cycle: getCycleId(options)
+    });
+    return;
+  }
+
+  if (actionChoice === "2") {
+    const generateResult = methodEngine.generateCanvases({
+      station: result.recommendedStation.id,
+      locale: options.locale || methodEngine.DEFAULT_LOCALE,
+      style: options.style || methodEngine.DEFAULT_STYLE,
+      cycle: getCycleId(options),
+      output: methodEngine.DEFAULT_OUTPUT_DIR
+    });
+    printGeneratedCanvasText(generateResult);
+    return;
+  }
+
+  const nextHints = getNextStepHints(result.recommendedStation.id);
+  console.log("");
+  console.log("You can continue later with:");
+  console.log(`- ${nextHints.resources}`);
+  console.log(`- ${nextHints.canvases}`);
+}
+
+function printResourceText(data) {
+  console.log(`${data.stationTitle} (${data.stationId})`);
+  console.log(`${data.stationDescription}\n`);
+  for (const step of data.steps) {
+    console.log(`${step.order}. ${step.step}`);
+    if (step.missing) {
+      console.log(`   Missing resource mapping for ${step.resourceId}`);
+      continue;
+    }
+    console.log(`   Resource: ${step.resourceTitle} (${step.resourceId})`);
+    console.log(`   Type: ${step.category}`);
+    if (step.canvasId) {
+      console.log(`   Canvas template: ${step.canvasId}`);
+    }
+    if (step.snippet) {
+      console.log(`   Snippet: ${step.snippet}`);
+    }
+    console.log(`   ${step.resourceDescription}`);
+  }
+}
+
+async function runInteractiveResources(options) {
+  const locale = options.locale || methodEngine.DEFAULT_LOCALE;
+  const style = methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE);
+  const output = options.output || methodEngine.DEFAULT_OUTPUT_DIR;
+  const data = methodEngine.buildStationResourceData(options.station, locale, style, getCycleId(options));
+  const scriptedActions = (options["step-actions"] || "")
+    .split(",")
+    .map((entry) => entry.trim())
+    .filter(Boolean);
+  let scriptedIndex = 0;
+  const useScriptedActions = scriptedActions.length > 0;
+  const rl = readline.createInterface({
+    input: process.stdin,
+    output: process.stdout
+  });
+
+  console.log(`${data.stationTitle} (${data.stationId})`);
+  console.log(`${data.stationDescription}\n`);
+
+  try {
+    for (const step of data.steps) {
+      console.log(`${step.order}. ${step.step}`);
+      if (step.missing) {
+        console.log(`Missing resource mapping for ${step.resourceId}\n`);
+        continue;
+      }
+
+      console.log(`Resource: ${step.resourceTitle} (${step.resourceId})`);
+      console.log(`Type: ${step.category}`);
+
+      while (true) {
+        const menuOptions = [
+          { key: "1", label: "View resource details" },
+          ...(step.canvasId ? [{ key: "2", label: "View related canvas details" }] : []),
+          ...(step.canvasId ? [{ key: "3", label: "Fill the canvas section by section and save JSON" }] : []),
+          ...(step.canvasId ? [{ key: "4", label: "Show CanvasCreator edit URL" }] : []),
+          ...(step.canvasId ? [{ key: "5", label: "Export current canvas JSON to SVG" }] : []),
+          ...(step.canvasId ? [{ key: "6", label: "Create or show starter canvas JSON" }] : []),
+          { key: step.canvasId ? "7" : "2", label: "Continue to next step" },
+          { key: step.canvasId ? "8" : "3", label: "Exit" }
+        ];
+
+        printMenuOptions(menuOptions);
+        const scriptedAction = useScriptedActions ? scriptedActions[scriptedIndex] : null;
+        const choice = await askMenuChoice(
+          rl,
+          `Choose action for step ${step.order}: `,
+          menuOptions,
+          scriptedAction
+        );
+        if (useScriptedActions) {
+          scriptedIndex += 1;
+        }
+
+        if (choice === "1") {
+          printResourceDetails(methodEngine.buildResourceMetadata(step.resourceId, locale));
+          console.log("");
+          continue;
+        }
+
+        if (choice === "2" && step.canvasId) {
+          printCanvasDetails(methodEngine.buildCanvasMetadata(step.canvasId, locale));
+          console.log("");
+          continue;
+        }
+
+        if (choice === "3" && step.canvasId) {
+          const outPath = await fillCanvasSectionsInteractive(data.stationId, step, locale, output, rl);
+          console.log(`Saved canvas JSON: ${outPath}`);
+          console.log("");
+          continue;
+        }
+
+        if (choice === "4" && step.canvasId) {
+          const outPath = methodEngine.generateCanvasForStationResource(data.stationId, step.resourceId, locale, output);
+          console.log("");
+          console.log(`CanvasCreator URL: ${methodEngine.getCanvasCreatorUrl(step.canvasId, locale)}`);
+          console.log(`Import or edit JSON from: ${outPath}`);
+          console.log("After editing in CanvasCreator, export JSON/SVG/PDF/PNG there and copy the files back into this repo.");
+          console.log("");
+          continue;
+        }
+
+        if (choice === "5" && step.canvasId) {
+          const exportResult = exportCanvasSvgForResource(data.stationId, step, locale, output);
+          console.log("");
+          if (exportResult.ok) {
+            console.log(`SVG export: ${exportResult.outputFile}`);
+            console.log(`Source JSON: ${exportResult.jsonPath}`);
+          } else {
+            console.log(`SVG export unavailable: ${exportResult.reason}`);
+            if (exportResult.help) {
+              console.log(exportResult.help);
+            }
+            console.log(`Canvas JSON is still available at: ${exportResult.jsonPath}`);
+            console.log(`CanvasCreator URL: ${methodEngine.getCanvasCreatorUrl(step.canvasId, locale)}`);
+          }
+          console.log("");
+          continue;
+        }
+
+        if (choice === "6" && step.canvasId) {
+          const outPath = methodEngine.generateCanvasForStationResource(data.stationId, step.resourceId, locale, output);
+          console.log("");
+          console.log(`Starter canvas JSON: ${outPath}`);
+          console.log("");
+          continue;
+        }
+
+        const continueKey = step.canvasId ? "7" : "2";
+        const exitKey = step.canvasId ? "8" : "3";
+
+        if (choice === continueKey) {
+          console.log("");
+          break;
+        }
+
+        if (choice === exitKey) {
+          console.log("");
+          console.log("Stopped resource walkthrough.");
+          return;
+        }
+      }
+    }
+  } finally {
+    rl.close();
+  }
+
+  console.log("Reached the end of the station steps.");
+}
+
+function printGeneratedCanvasText(result) {
+  console.log(`Generated empty canvases in ${result.outputRoot}`);
+  if (result.generated.length > 0) {
+    console.log("");
+    for (const entry of result.generated) {
+      console.log(`- ${entry.resourceId} -> ${entry.file}`);
+    }
+  }
+
+  if (result.skipped.length > 0) {
+    console.log("");
+    console.log("Skipped existing files:");
+    for (const entry of result.skipped) {
+      console.log(`- ${entry.resourceId} -> ${entry.file}`);
+    }
+    console.log("\nUse --force to overwrite existing starter files.");
+  }
+}
+
+export async function main() {
+  const { command, options } = parseArgs(process.argv.slice(2));
+
+  if (command === "help") {
+    printUsage();
+    return;
+  }
+
+  if (command === "start") {
+    const locale = await maybePromptForStartLocale(options);
+    const data = methodEngine.buildStartData(locale, getCycleId(options));
+    if (options.json) {
+      console.log(JSON.stringify(data, null, 2));
+      return;
+    }
+
+    if (options.list || (!process.stdin.isTTY && !options.answers)) {
+      printStartText(data);
+      return;
+    }
+
+    await runInteractiveStart(data, { ...options, locale });
+    return;
+  }
+
+  if (command === "resources") {
+    if (!options.station) {
+      fail("resources requires --station <station-id>");
+    }
+
+    const data = methodEngine.buildStationResourceData(
+      options.station,
+      options.locale || methodEngine.DEFAULT_LOCALE,
+      methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE),
+      getCycleId(options)
+    );
+    if (options.json) {
+      console.log(JSON.stringify(data, null, 2));
+      return;
+    }
+
+    if (!options.list && (process.stdin.isTTY || options["step-actions"])) {
+      await runInteractiveResources(options);
+      return;
+    }
+
+    printResourceText(data);
+    return;
+  }
+
+  if (command === "generate-canvases") {
+    const result = methodEngine.generateCanvases(options);
+    if (options.json) {
+      console.log(JSON.stringify(result, null, 2));
+      return;
+    }
+    printGeneratedCanvasText(result);
+    return;
+  }
+
+  fail(`Unknown command: ${command}`);
+}
+
+if (process.argv[1] && path.resolve(process.argv[1]) === currentFilePath) {
+  main().catch((error) => {
+    console.error(error instanceof Error ? error.message : error);
+    process.exit(1);
+  });
+}
diff --git a/packages/create-apiops/bin/create-apiops-project.js b/packages/create-apiops/bin/create-apiops-project.js
index 67c1fc4..2844c66 100644
--- a/packages/create-apiops/bin/create-apiops-project.js
+++ b/packages/create-apiops/bin/create-apiops-project.js
@@ -8,7 +8,6 @@ import { spawnSync } from "node:child_process";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 const templateDir = path.resolve(__dirname, "..", "template");
-const methodDataRoot = path.resolve(__dirname, "..", "..", "..", "src", "data", "method");
 
 const DEFAULTS = {
   name: "my-api-project",
@@ -211,14 +210,24 @@ function hasCompleteNonInteractiveConfig(args) {
   return args.name && args.locale && args.cycle && args.style && args.install !== undefined;
 }
 
-function getSupportedCycleIds() {
-  const cyclesPath = path.join(methodDataRoot, "cycles.json");
-  const cyclesJson = JSON.parse(fs.readFileSync(cyclesPath, "utf8"));
-  return (cyclesJson.cycles?.items || []).flatMap((cycle) => [cycle.id, cycle.slug].filter(Boolean));
+async function loadMethodEngine() {
+  try {
+    return await import("apiops-cycles-method-data/method-engine");
+  } catch (error) {
+    if (error?.code !== "ERR_MODULE_NOT_FOUND") {
+      throw error;
+    }
+    return import("../../../src/lib/method-engine.js");
+  }
+}
+
+async function getSupportedCycleIds() {
+  const { getCycles } = await loadMethodEngine();
+  return getCycles().flatMap((cycle) => [cycle.id, cycle.slug].filter(Boolean));
 }
 
-function validateCycle(cycle) {
-  const supportedCycleIds = getSupportedCycleIds();
+async function validateCycle(cycle) {
+  const supportedCycleIds = await getSupportedCycleIds();
   if (supportedCycleIds.includes(cycle)) {
     return;
   }
@@ -291,7 +300,7 @@ async function getScaffoldConfig() {
 
 async function main() {
   const { projectName, locale, cycle, apiStyle, installNow } = await getScaffoldConfig();
-  validateCycle(cycle);
+  await validateCycle(cycle);
 
   const targetDir = path.resolve(process.cwd(), projectName);
   if (fs.existsSync(targetDir)) {
diff --git a/packages/create-apiops/bin/method-cli.js b/packages/create-apiops/bin/method-cli.js
deleted file mode 100644
index c3e74fc..0000000
--- a/packages/create-apiops/bin/method-cli.js
+++ /dev/null
@@ -1,802 +0,0 @@
-#!/usr/bin/env node
-import fs from "node:fs";
-import path from "node:path";
-import { spawnSync } from "node:child_process";
-import readline from "node:readline/promises";
-import { fileURLToPath } from "node:url";
-import * as methodEngine from "../../../src/lib/method-engine.js";
-
-const currentFilePath = fileURLToPath(import.meta.url);
-
-const STATION_SCRIPT_HINTS = {
-  "api-product-strategy": {
-    resources: "npm run method:resources:strategy",
-    canvases: "npm run method:canvases:new-api"
-  },
-  "api-design": {
-    resources: "npm run method -- resources --station api-design --style \"REST\"",
-    canvases: "npm run method -- generate-canvases --station api-design --style \"REST\" --output ./specs/canvases"
-  }
-};
-
-function printUsage() {
-  console.log(`Usage:
-  node packages/create-apiops/bin/method-cli.js start [--cycle <cycle-id>] [--locale <locale>] [--default-locale <locale>] [--json] [--list] [--answers <yes,no,...>] [--next-action <resources|canvases|exit>]
-  node packages/create-apiops/bin/method-cli.js resources --station <station-id> [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--json] [--list] [--step-actions <details,next,...>]
-  node packages/create-apiops/bin/method-cli.js generate-canvases [--station <station-id> | --stations <ids> | --preset new-api] [--cycle <cycle-id>] [--locale <locale>] [--style <style>] [--output <dir>] [--force] [--json]
-
-Examples:
-  node packages/create-apiops/bin/method-cli.js start --locale en
-  node packages/create-apiops/bin/method-cli.js start --cycle api-productization-cycle --locale en
-  node packages/create-apiops/bin/method-cli.js start --default-locale en
-  node packages/create-apiops/bin/method-cli.js start --locale en --answers yes,no,yes --next-action resources
-  node packages/create-apiops/bin/method-cli.js resources --station api-product-strategy --cycle api-productization-cycle --locale en
-  node packages/create-apiops/bin/method-cli.js generate-canvases --preset new-api --cycle api-productization-cycle --style REST --output ./specs/canvases
-`);
-}
-
-function fail(message) {
-  console.error(message);
-  process.exit(1);
-}
-
-function parseArgs(argv) {
-  if (argv.length === 0 || argv.includes("--help") || argv.includes("-h")) {
-    return { command: "help", options: {} };
-  }
-
-  const [command, ...rest] = argv;
-  const options = {};
-
-  for (let index = 0; index < rest.length; index += 1) {
-    const current = rest[index];
-    if (!current.startsWith("--")) {
-      fail(`Unexpected argument: ${current}`);
-    }
-
-    const key = current.slice(2);
-    if (key === "json" || key === "force" || key === "list") {
-      options[key] = true;
-      continue;
-    }
-
-    const value = rest[index + 1];
-    if (!value || value.startsWith("--")) {
-      fail(`Missing value for --${key}`);
-    }
-
-    options[key] = value;
-    index += 1;
-  }
-
-  return { command, options };
-}
-
-function readJson(filePath) {
-  return JSON.parse(fs.readFileSync(filePath, "utf8"));
-}
-
-function runCommand(command, args, options = {}) {
-  return spawnSync(command, args, {
-    encoding: "utf8",
-    shell: false,
-    ...options
-  });
-}
-
-function getNextStepHints(stationId) {
-  const hints = STATION_SCRIPT_HINTS[stationId];
-  if (hints) {
-    return hints;
-  }
-
-  return {
-    resources: `npm run method -- resources --station ${stationId}`,
-    canvases: `npm run method -- generate-canvases --station ${stationId} --output ./specs/canvases`
-  };
-}
-
-function getCycleId(options = {}) {
-  return options.cycle || methodEngine.DEFAULT_CYCLE_ID;
-}
-
-function loadCanvasJson(filePath, canvasId, locale) {
-  if (fs.existsSync(filePath)) {
-    return readJson(filePath);
-  }
-  return methodEngine.buildCanvasTemplate(canvasId, locale);
-}
-
-function formatPaletteHelp() {
-  return Object.entries(methodEngine.getNoteColorPalette())
-    .map(([intent, color]) => `${intent}=${color}`)
-    .join(", ");
-}
-
-async function fillCanvasSectionsInteractive(stationId, step, locale, output, rl) {
-  const outPath = methodEngine.generateCanvasForStationResource(stationId, step.resourceId, locale, output);
-  const canvasJson = loadCanvasJson(outPath, step.canvasId, locale);
-  const canvasMetadata = methodEngine.buildCanvasMetadata(step.canvasId, locale);
-  const starterFileName = path.basename(outPath);
-  const suggestedFileSlug = starterFileName.endsWith(".empty.json")
-    ? step.resourceId
-    : starterFileName.replace(/\.json$/i, "");
-  const requestedFileSlug = await rl.question(`Save filled canvas as file name (${suggestedFileSlug}): `);
-  const finalFileSlug = methodEngine.sanitizeFileSlug(requestedFileSlug, suggestedFileSlug);
-  const finalPath = path.join(path.dirname(outPath), `${finalFileSlug}.json`);
-
-  console.log("");
-  console.log(`Filling ${canvasMetadata.title} section by section.`);
-  console.log("Use `|` to create multiple notes in one section. Leave blank to keep existing notes. Type !clear to remove notes in a section.\n");
-  console.log("Prefix any note with `[benefit]`, `[neutral]`, `[negative]`, `[task]`, `[default]`, or `[color=#RRGGBB]` to set its color explicitly.");
-  console.log(`Palette: ${formatPaletteHelp()}\n`);
-
-  for (const section of canvasMetadata.sections) {
-    const existingSection = canvasJson.sections.find((entry) => entry.sectionId === section.id);
-    const existingNotes = existingSection?.stickyNotes || [];
-    console.log(`${section.title}`);
-    console.log(section.description);
-    console.log(`Default note color here: ${section.defaultNoteIntent} (${section.defaultNoteColor})`);
-    if (existingNotes.length > 0) {
-      console.log(`Current notes: ${existingNotes.map((note) => `${note.content} (${note.color})`).join(" | ")}`);
-    }
-
-    const answer = (await rl.question("Notes: ")).trim();
-    if (!answer) {
-      console.log("");
-      continue;
-    }
-
-    if (answer === "!clear") {
-      existingSection.stickyNotes = [];
-      console.log("");
-      continue;
-    }
-
-    const notes = answer
-      .split("|")
-      .map((entry) => entry.trim())
-      .filter(Boolean)
-      .map((content) => methodEngine.parseStickyNoteInput(content, {
-        canvasId: step.canvasId,
-        sectionId: section.id,
-        defaultIntent: section.defaultNoteIntent
-      }));
-
-    existingSection.stickyNotes = notes;
-    console.log("");
-  }
-
-  fs.writeFileSync(finalPath, `${JSON.stringify(canvasJson, null, 2)}\n`);
-  return finalPath;
-}
-
-function resolveCanvasExportCommand() {
-  const packageRoot = path.resolve(process.cwd(), "node_modules", "canvascreator");
-  if (!fs.existsSync(packageRoot)) {
-    return {
-      ok: false,
-      reason: "SVG export requires CanvasCreator export support, which is not installed in this project.",
-      help: "Run `npm install` to install project dependencies, or `npm install canvascreator` to add CanvasCreator manually."
-    };
-  }
-
-  const packageJsonPath = path.join(packageRoot, "package.json");
-  if (fs.existsSync(packageJsonPath)) {
-    const packageJson = readJson(packageJsonPath);
-    const binEntry = typeof packageJson.bin === "string"
-      ? packageJson.bin
-      : packageJson.bin?.["canvascreator-export"];
-
-    if (binEntry) {
-      const binPath = path.resolve(packageRoot, binEntry);
-      if (fs.existsSync(binPath)) {
-        return {
-          ok: true,
-          command: process.execPath,
-          args: [binPath]
-        };
-      }
-    }
-  }
-
-  const scriptPath = path.resolve(packageRoot, "scripts", "export.js");
-  if (fs.existsSync(scriptPath)) {
-    return {
-      ok: true,
-      command: process.execPath,
-      args: [scriptPath]
-    };
-  }
-
-  return {
-    ok: false,
-    reason: "CanvasCreator is installed, but its export CLI could not be found.",
-    help: "Reinstall `canvascreator` or use the CanvasCreator web app to export SVG from the JSON file."
-  };
-}
-
-function resolveStartLocale(options = {}) {
-  const explicitLocale = options.locale;
-  const defaultLocale = options["default-locale"] || methodEngine.DEFAULT_LOCALE;
-  if (explicitLocale) {
-    return explicitLocale;
-  }
-
-  return methodEngine.getSupportedMethodLocales().includes(defaultLocale)
-    ? defaultLocale
-    : methodEngine.DEFAULT_LOCALE;
-}
-
-async function maybePromptForStartLocale(options = {}) {
-  const selectedLocale = resolveStartLocale(options);
-  if (
-    options.locale ||
-    options.json ||
-    options.list ||
-    options.answers ||
-    !process.stdin.isTTY
-  ) {
-    return selectedLocale;
-  }
-
-  const supportedLocales = methodEngine.getSupportedMethodLocales();
-  const rl = readline.createInterface({
-    input: process.stdin,
-    output: process.stdout
-  });
-
-  try {
-    console.log(`Default method language: ${selectedLocale}`);
-    console.log(`Available languages: ${supportedLocales.join(", ")}`);
-    const answer = (await rl.question("Press Enter to keep the default, or type another locale for this run: "))
-      .trim()
-      .toLowerCase();
-    if (!answer) {
-      console.log("");
-      return selectedLocale;
-    }
-
-    if (supportedLocales.includes(answer)) {
-      console.log("");
-      return answer;
-    }
-
-    console.log(`Unknown locale "${answer}", using ${selectedLocale}.`);
-    console.log("");
-    return selectedLocale;
-  } finally {
-    rl.close();
-  }
-}
-
-function formatCommandFailure(result) {
-  if (result.error?.message) {
-    return result.error.message;
-  }
-
-  const stderr = String(result.stderr || "").trim();
-  if (stderr) {
-    return stderr;
-  }
-
-  const stdout = String(result.stdout || "").trim();
-  if (stdout) {
-    return stdout;
-  }
-
-  return "Canvas export failed.";
-}
-
-function exportCanvasSvgForResource(stationId, step, locale, output) {
-  const jsonPath = methodEngine.generateCanvasForStationResource(stationId, step.resourceId, locale, output);
-  const exportCommand = resolveCanvasExportCommand();
-  if (!exportCommand.ok) {
-    return {
-      ok: false,
-      reason: exportCommand.reason,
-      help: exportCommand.help,
-      jsonPath
-    };
-  }
-
-  const outputDir = path.dirname(jsonPath);
-  const outputFile = path.join(outputDir, `${step.resourceId}.svg`);
-  const result = runCommand(
-    exportCommand.command,
-    [
-      ...exportCommand.args,
-      "--input", jsonPath,
-      "--format", "svg",
-      "--output", outputFile
-    ],
-    {
-      cwd: process.cwd()
-    }
-  );
-
-  if (result.status !== 0) {
-    return {
-      ok: false,
-      reason: formatCommandFailure(result),
-      jsonPath
-    };
-  }
-
-  return {
-    ok: true,
-    jsonPath,
-    outputFile
-  };
-}
-
-function printStartText(data) {
-  console.log(`APIOps starting station check (${data.length} core stations)\n`);
-  for (const station of data) {
-    console.log(`${station.order}. ${station.title} (${station.id})`);
-    console.log(`   ${station.description}`);
-    if (station.suggestedForNewApi) {
-      console.log("   Suggested default for a new API unless later-station criteria are already clearly met.");
-    }
-    console.log("   Criteria to check:");
-    for (const criterion of station.criteria) {
-      console.log(`   - ${criterion.label}`);
-    }
-    console.log("");
-  }
-}
-
-function printMenuOptions(options) {
-  for (const option of options) {
-    console.log(`${option.key}. ${option.label}`);
-  }
-}
-
-async function askMenuChoice(rl, prompt, options, providedChoice) {
-  const validKeys = new Set(options.map((option) => option.key));
-  if (providedChoice) {
-    if (!validKeys.has(providedChoice)) {
-      fail(`Unsupported menu choice: ${providedChoice}`);
-    }
-    console.log(`${prompt} ${providedChoice}`);
-    return providedChoice;
-  }
-
-  while (true) {
-    const answer = (await rl.question(prompt)).trim();
-    if (validKeys.has(answer)) {
-      return answer;
-    }
-    console.log(`Choose one of: ${options.map((option) => option.key).join(", ")}`);
-  }
-}
-
-function printResourceDetails(metadata) {
-  console.log("");
-  console.log(`${metadata.title} (${metadata.id})`);
-  console.log(`Type: ${metadata.category}`);
-  console.log(metadata.description);
-  if (metadata.steps.length > 0) {
-    console.log("How it works:");
-    for (const step of metadata.steps) {
-      console.log(`- ${step}`);
-    }
-  }
-  if (metadata.tips.length > 0) {
-    console.log("Tips:");
-    for (const tip of metadata.tips) {
-      console.log(`- ${tip}`);
-    }
-  }
-  if (metadata.canvasId) {
-    console.log(`Canvas template: ${metadata.canvasId}`);
-  }
-  if (metadata.snippet) {
-    console.log(`Snippet: ${metadata.snippet}`);
-  }
-}
-
-function printCanvasDetails(metadata) {
-  console.log("");
-  console.log(`${metadata.title} (${metadata.id})`);
-  if (metadata.purpose) {
-    console.log(`Purpose: ${metadata.purpose}`);
-  }
-  if (metadata.howToUse) {
-    console.log(`How to use: ${metadata.howToUse}`);
-  }
-  if (metadata.sections.length > 0) {
-    console.log("Sections:");
-    for (const section of metadata.sections) {
-      console.log(`- ${section.title}: ${section.description}`);
-    }
-  }
-}
-
-async function runInteractiveStart(data, options) {
-  const answers = {};
-  const providedAnswers = (options.answers || "")
-    .split(",")
-    .map((entry) => entry.trim())
-    .filter(Boolean);
-  const useProvidedAnswers = providedAnswers.length > 0;
-  const rl = !useProvidedAnswers
-    ? readline.createInterface({
-      input: process.stdin,
-      output: process.stdout
-    })
-    : null;
-  let answerIndex = 0;
-  let recommendedStation = null;
-  let stoppingCriterion = null;
-
-  console.log(`APIOps guided station check (${data.length} core stations)`);
-  console.log("Answer each criterion with yes, no, or skip.");
-  console.log("The guide stops at the first `no` and recommends that station immediately.\n");
-
-  try {
-    for (const station of data) {
-      console.log(`${station.order}. ${station.title} (${station.id})`);
-      console.log(`   ${station.description}`);
-
-      for (const criterion of station.criteria) {
-        let normalized;
-        const promptPrefix = `   - ${criterion.label}`;
-
-        if (useProvidedAnswers) {
-          const providedAnswer = providedAnswers[answerIndex];
-          if (!providedAnswer) {
-            fail(`Not enough answers in --answers. Stopped at station ${station.id}, criterion ${criterion.id}.`);
-          }
-          normalized = methodEngine.normalizeAnswer(providedAnswer);
-          if (!normalized) {
-            fail(`Unsupported answer in --answers at position ${answerIndex + 1}: ${providedAnswer}`);
-          }
-          console.log(`${promptPrefix} -> ${providedAnswer}`);
-        } else {
-          while (!normalized) {
-            const answer = await rl.question(`${promptPrefix} (yes/no/skip): `);
-            normalized = methodEngine.normalizeAnswer(answer);
-            if (!normalized) {
-              console.log("Please answer yes, no, or skip.");
-            }
-          }
-        }
-
-        answerIndex += 1;
-        answers[criterion.id] = normalized;
-
-        if (normalized === "not-met") {
-          recommendedStation = station;
-          stoppingCriterion = criterion;
-          break;
-        }
-      }
-
-      console.log("");
-
-      if (recommendedStation) {
-        break;
-      }
-    }
-  } finally {
-    rl?.close();
-  }
-
-  const result = recommendedStation
-    ? {
-      recommendedStation: {
-        id: recommendedStation.id,
-        title: recommendedStation.title,
-        unmetCriteria: [stoppingCriterion]
-      }
-    }
-    : methodEngine.evaluateStartRecommendation(data, answers);
-
-  console.log("");
-  console.log(`Recommended start station: ${result.recommendedStation.title} (${result.recommendedStation.id})`);
-  console.log(recommendedStation
-    ? "Reason: this is the first station where a required criterion was marked as not met."
-    : "Reason: all checked core-station criteria were marked as met.");
-
-  if (result.recommendedStation.unmetCriteria.length > 0) {
-    console.log("Criteria still to address here:");
-    for (const criterion of result.recommendedStation.unmetCriteria) {
-      console.log(`- ${criterion.label}`);
-    }
-  }
-
-  const actionOptions = [
-    { key: "1", label: "Review station resources" },
-    { key: "2", label: "Generate empty starter canvases for this station" },
-    { key: "3", label: "Exit" }
-  ];
-  const mappedActions = {
-    resources: "1",
-    canvases: "2",
-    exit: "3"
-  };
-  const providedAction = options["next-action"] ? mappedActions[options["next-action"]] : null;
-  const actionRl = !providedAction
-    ? readline.createInterface({
-      input: process.stdin,
-      output: process.stdout
-    })
-    : null;
-
-  console.log("");
-  console.log("Next step options:");
-  printMenuOptions(actionOptions);
-
-  const actionChoice = await askMenuChoice(actionRl, "Choose next step (1/2/3): ", actionOptions, providedAction);
-  actionRl?.close();
-
-  if (actionChoice === "1") {
-    await runInteractiveResources({
-      station: result.recommendedStation.id,
-      locale: options.locale || methodEngine.DEFAULT_LOCALE,
-      style: options.style || methodEngine.DEFAULT_STYLE,
-      cycle: getCycleId(options)
-    });
-    return;
-  }
-
-  if (actionChoice === "2") {
-    const generateResult = methodEngine.generateCanvases({
-      station: result.recommendedStation.id,
-      locale: options.locale || methodEngine.DEFAULT_LOCALE,
-      style: options.style || methodEngine.DEFAULT_STYLE,
-      cycle: getCycleId(options),
-      output: methodEngine.DEFAULT_OUTPUT_DIR
-    });
-    printGeneratedCanvasText(generateResult);
-    return;
-  }
-
-  const nextHints = getNextStepHints(result.recommendedStation.id);
-  console.log("");
-  console.log("You can continue later with:");
-  console.log(`- ${nextHints.resources}`);
-  console.log(`- ${nextHints.canvases}`);
-}
-
-function printResourceText(data) {
-  console.log(`${data.stationTitle} (${data.stationId})`);
-  console.log(`${data.stationDescription}\n`);
-  for (const step of data.steps) {
-    console.log(`${step.order}. ${step.step}`);
-    if (step.missing) {
-      console.log(`   Missing resource mapping for ${step.resourceId}`);
-      continue;
-    }
-    console.log(`   Resource: ${step.resourceTitle} (${step.resourceId})`);
-    console.log(`   Type: ${step.category}`);
-    if (step.canvasId) {
-      console.log(`   Canvas template: ${step.canvasId}`);
-    }
-    if (step.snippet) {
-      console.log(`   Snippet: ${step.snippet}`);
-    }
-    console.log(`   ${step.resourceDescription}`);
-  }
-}
-
-async function runInteractiveResources(options) {
-  const locale = options.locale || methodEngine.DEFAULT_LOCALE;
-  const style = methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE);
-  const output = options.output || methodEngine.DEFAULT_OUTPUT_DIR;
-  const data = methodEngine.buildStationResourceData(options.station, locale, style, getCycleId(options));
-  const scriptedActions = (options["step-actions"] || "")
-    .split(",")
-    .map((entry) => entry.trim())
-    .filter(Boolean);
-  let scriptedIndex = 0;
-  const useScriptedActions = scriptedActions.length > 0;
-  const rl = readline.createInterface({
-    input: process.stdin,
-    output: process.stdout
-  });
-
-  console.log(`${data.stationTitle} (${data.stationId})`);
-  console.log(`${data.stationDescription}\n`);
-
-  try {
-    for (const step of data.steps) {
-      console.log(`${step.order}. ${step.step}`);
-      if (step.missing) {
-        console.log(`Missing resource mapping for ${step.resourceId}\n`);
-        continue;
-      }
-
-      console.log(`Resource: ${step.resourceTitle} (${step.resourceId})`);
-      console.log(`Type: ${step.category}`);
-
-      while (true) {
-        const menuOptions = [
-          { key: "1", label: "View resource details" },
-          ...(step.canvasId ? [{ key: "2", label: "View related canvas details" }] : []),
-          ...(step.canvasId ? [{ key: "3", label: "Fill the canvas section by section and save JSON" }] : []),
-          ...(step.canvasId ? [{ key: "4", label: "Show CanvasCreator edit URL" }] : []),
-          ...(step.canvasId ? [{ key: "5", label: "Export current canvas JSON to SVG" }] : []),
-          ...(step.canvasId ? [{ key: "6", label: "Create or show starter canvas JSON" }] : []),
-          { key: step.canvasId ? "7" : "2", label: "Continue to next step" },
-          { key: step.canvasId ? "8" : "3", label: "Exit" }
-        ];
-
-        printMenuOptions(menuOptions);
-        const scriptedAction = useScriptedActions ? scriptedActions[scriptedIndex] : null;
-        const choice = await askMenuChoice(
-          rl,
-          `Choose action for step ${step.order}: `,
-          menuOptions,
-          scriptedAction
-        );
-        if (useScriptedActions) {
-          scriptedIndex += 1;
-        }
-
-        if (choice === "1") {
-          printResourceDetails(methodEngine.buildResourceMetadata(step.resourceId, locale));
-          console.log("");
-          continue;
-        }
-
-        if (choice === "2" && step.canvasId) {
-          printCanvasDetails(methodEngine.buildCanvasMetadata(step.canvasId, locale));
-          console.log("");
-          continue;
-        }
-
-        if (choice === "3" && step.canvasId) {
-          const outPath = await fillCanvasSectionsInteractive(data.stationId, step, locale, output, rl);
-          console.log(`Saved canvas JSON: ${outPath}`);
-          console.log("");
-          continue;
-        }
-
-        if (choice === "4" && step.canvasId) {
-          const outPath = methodEngine.generateCanvasForStationResource(data.stationId, step.resourceId, locale, output);
-          console.log("");
-          console.log(`CanvasCreator URL: ${methodEngine.getCanvasCreatorUrl(step.canvasId, locale)}`);
-          console.log(`Import or edit JSON from: ${outPath}`);
-          console.log("After editing in CanvasCreator, export JSON/SVG/PDF/PNG there and copy the files back into this repo.");
-          console.log("");
-          continue;
-        }
-
-        if (choice === "5" && step.canvasId) {
-          const exportResult = exportCanvasSvgForResource(data.stationId, step, locale, output);
-          console.log("");
-          if (exportResult.ok) {
-            console.log(`SVG export: ${exportResult.outputFile}`);
-            console.log(`Source JSON: ${exportResult.jsonPath}`);
-          } else {
-            console.log(`SVG export unavailable: ${exportResult.reason}`);
-            if (exportResult.help) {
-              console.log(exportResult.help);
-            }
-            console.log(`Canvas JSON is still available at: ${exportResult.jsonPath}`);
-            console.log(`CanvasCreator URL: ${methodEngine.getCanvasCreatorUrl(step.canvasId, locale)}`);
-          }
-          console.log("");
-          continue;
-        }
-
-        if (choice === "6" && step.canvasId) {
-          const outPath = methodEngine.generateCanvasForStationResource(data.stationId, step.resourceId, locale, output);
-          console.log("");
-          console.log(`Starter canvas JSON: ${outPath}`);
-          console.log("");
-          continue;
-        }
-
-        const continueKey = step.canvasId ? "7" : "2";
-        const exitKey = step.canvasId ? "8" : "3";
-
-        if (choice === continueKey) {
-          console.log("");
-          break;
-        }
-
-        if (choice === exitKey) {
-          console.log("");
-          console.log("Stopped resource walkthrough.");
-          return;
-        }
-      }
-    }
-  } finally {
-    rl.close();
-  }
-
-  console.log("Reached the end of the station steps.");
-}
-
-function printGeneratedCanvasText(result) {
-  console.log(`Generated empty canvases in ${result.outputRoot}`);
-  if (result.generated.length > 0) {
-    console.log("");
-    for (const entry of result.generated) {
-      console.log(`- ${entry.resourceId} -> ${entry.file}`);
-    }
-  }
-
-  if (result.skipped.length > 0) {
-    console.log("");
-    console.log("Skipped existing files:");
-    for (const entry of result.skipped) {
-      console.log(`- ${entry.resourceId} -> ${entry.file}`);
-    }
-    console.log("\nUse --force to overwrite existing starter files.");
-  }
-}
-
-export async function main() {
-  const { command, options } = parseArgs(process.argv.slice(2));
-
-  if (command === "help") {
-    printUsage();
-    return;
-  }
-
-  if (command === "start") {
-    const locale = await maybePromptForStartLocale(options);
-    const data = methodEngine.buildStartData(locale, getCycleId(options));
-    if (options.json) {
-      console.log(JSON.stringify(data, null, 2));
-      return;
-    }
-
-    if (options.list || (!process.stdin.isTTY && !options.answers)) {
-      printStartText(data);
-      return;
-    }
-
-    await runInteractiveStart(data, { ...options, locale });
-    return;
-  }
-
-  if (command === "resources") {
-    if (!options.station) {
-      fail("resources requires --station <station-id>");
-    }
-
-    const data = methodEngine.buildStationResourceData(
-      options.station,
-      options.locale || methodEngine.DEFAULT_LOCALE,
-      methodEngine.normalizeStyle(options.style || methodEngine.DEFAULT_STYLE),
-      getCycleId(options)
-    );
-    if (options.json) {
-      console.log(JSON.stringify(data, null, 2));
-      return;
-    }
-
-    if (!options.list && (process.stdin.isTTY || options["step-actions"])) {
-      await runInteractiveResources(options);
-      return;
-    }
-
-    printResourceText(data);
-    return;
-  }
-
-  if (command === "generate-canvases") {
-    const result = methodEngine.generateCanvases(options);
-    if (options.json) {
-      console.log(JSON.stringify(result, null, 2));
-      return;
-    }
-    printGeneratedCanvasText(result);
-    return;
-  }
-
-  fail(`Unknown command: ${command}`);
-}
-
-if (process.argv[1] && path.resolve(process.argv[1]) === currentFilePath) {
-  main().catch((error) => {
-    console.error(error instanceof Error ? error.message : error);
-    process.exit(1);
-  });
-}
diff --git a/packages/create-apiops/package.json b/packages/create-apiops/package.json
index eca1388..bef6395 100644
--- a/packages/create-apiops/package.json
+++ b/packages/create-apiops/package.json
@@ -8,9 +8,13 @@
     "create-apiops": "./bin/create-apiops-project.js"
   },
   "files": [
-    "bin",
+    "bin/check-node-version.js",
+    "bin/create-apiops-project.js",
     "template"
   ],
+  "optionalDependencies": {
+    "apiops-cycles-method-data": "^4.0.0"
+  },
   "keywords": [
     "apiops",
     "openapi",
diff --git a/packages/create-apiops/template/package.json b/packages/create-apiops/template/package.json
index 31383a6..0b4183b 100644
--- a/packages/create-apiops/template/package.json
+++ b/packages/create-apiops/template/package.json
@@ -6,7 +6,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "apiops-cycles-method-data": "^3.4.4",
+    "apiops-cycles-method-data": "^4.0.0",
     "canvascreator": "^1.7.3"
   },
   "devDependencies": {
diff --git a/scripts/check-package-contents.mjs b/scripts/check-package-contents.mjs
index 62b7aa8..19514a2 100644
--- a/scripts/check-package-contents.mjs
+++ b/scripts/check-package-contents.mjs
@@ -45,6 +45,15 @@ function assertHasFiles(fileSet, requiredFiles, label) {
   }
 }
 
+function assertDoesNotHaveFiles(fileSet, forbiddenFiles, label) {
+  for (const file of forbiddenFiles) {
+    if (fileSet.has(file)) {
+      console.error(`[${label}] Unexpected packaged file: ${file}`);
+      process.exit(1);
+    }
+  }
+}
+
 const pkg = JSON.parse(readFileSync("package.json", "utf8"));
 if (!Array.isArray(pkg.files) || !pkg.files.includes("src/schemas/")) {
   console.error('package.json files must include "src/schemas/".');
@@ -101,7 +110,6 @@ assertHasFiles(
   createApiopsFiles,
   [
     "bin/create-apiops-project.js",
-    "bin/method-cli.js",
     "bin/check-node-version.js",
     "template/AGENTS.md",
     "template/README.md",
@@ -110,5 +118,6 @@ assertHasFiles(
   ],
   "create-apiops"
 );
+assertDoesNotHaveFiles(createApiopsFiles, ["bin/method-cli.js"], "create-apiops");
 
 console.log("Root and create-apiops package content inspection passed.");
diff --git a/scripts/test-create-apiops-scaffold.mjs b/scripts/test-create-apiops-scaffold.mjs
index f30d16c..65a6c3c 100644
--- a/scripts/test-create-apiops-scaffold.mjs
+++ b/scripts/test-create-apiops-scaffold.mjs
@@ -273,7 +273,7 @@ try {
     }
   );
   assert(
-    guidedStartOutput.includes("Recommended start station: API Product Strategy - Turn APIs Into Strategic Products (api-product-strategy)"),
+    guidedStartOutput.includes("Recommended start station: API Product Strategy (api-product-strategy)"),
     "Expected guided start flow to recommend API Product Strategy when all answers are no."
   );
   assert(
diff --git a/src/data/method/de/labels.stations.json b/src/data/method/de/labels.stations.json
index b875124..4136edb 100644
--- a/src/data/method/de/labels.stations.json
+++ b/src/data/method/de/labels.stations.json
@@ -357,8 +357,6 @@
   "station.upskilling.outcomes.1": "Erhöhte Kompetenz bei der Konzeption, Entwicklung und Verwaltung von APIs",
   "station.upskilling.outcomes.2": "Verbesserte Fähigkeit zur Übernahme neuer Technologien und Verfahren",
   "station.upskilling.outcomes.3": "Befähigte Teams zur Förderung von API-Innovation und -Qualität",
-  "station.upskilling.how_it_works.1": "Bereitstellung von Schulungsprogrammen, Workshops und Ressourcen, um Teams bei der Verbesserung ihrer API-Fähigkeiten und -Kenntnisse zu unterstützen.",
-  "station.upskilling.how_it_works.2": "Fördern Sie kontinuierliches Lernen durch Online-Kurse, Zertifizierungen und Engagement in der Gemeinschaft.",
   "station.operating-guidelines.outcomes.1": "Konsistente API-Verwaltung und -Qualität im gesamten Unternehmen",
   "station.operating-guidelines.outcomes.2": "Einhaltung von Organisationsstandards und bewährten Verfahren",
   "station.operating-guidelines.outcomes.3": "Verbesserte Sichtbarkeit und Kontrolle über API-Initiativen",
@@ -367,13 +365,9 @@
   "station.portfolio-management.outcomes.1": "APIs im Einklang mit Unternehmenszielen und strategischen Initiativen",
   "station.portfolio-management.outcomes.2": "Priorisierung und Optimierung von APIs auf der Grundlage von Wert und Wirkung",
   "station.portfolio-management.outcomes.3": "Verbesserte Sichtbarkeit und Kontrolle über das API-Portfolio",
-  "station.portfolio-management.how_it_works.1": "Festlegung von Kriterien für die Bewertung und Priorisierung von APIs auf der Grundlage des Geschäftswerts, der Auswirkungen und der Ausrichtung auf strategische Initiativen.",
-  "station.portfolio-management.how_it_works.2": "Überwachen Sie das API-Portfolio, um sicherzustellen, dass die APIs einen Mehrwert liefern, die Leistungserwartungen erfüllen und mit den Geschäftszielen übereinstimmen.",
   "station.budget-and-resource-management.outcomes.1": "Effiziente Zuweisung von Ressourcen für API-Initiativen",
   "station.budget-and-resource-management.outcomes.2": "Optimierte Investitionen in die API-Entwicklung und -Verwaltung",
   "station.budget-and-resource-management.outcomes.3": "Verbesserte finanzielle Transparenz und Kontrolle über API-Initiativen",
-  "station.budget-and-resource-management.how_it_works.1": "Festlegung von Kriterien für die Bewertung und Priorisierung von Budgetzuweisungen auf der Grundlage des Geschäftswerts, der Auswirkungen und der Ausrichtung auf strategische Initiativen.",
-  "station.budget-and-resource-management.how_it_works.2": "Überwachung des Budgets und der Ressourcennutzung, um effektive Investitionen und Ressourcenzuweisung für API-Initiativen sicherzustellen.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "API-Produktstrategie - APIs in strategische Produkte verwandeln",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Bevor Sie etwas bauen, sollten Sie von Anfang an den Wert, die Benutzer und die Geschäftsziele Ihrer API definieren.",
   "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Viele Unternehmen betrachten APIs als technische Projekte und nicht als Produkte. Das Ergebnis? Verwirrte Kunden, schlechte Akzeptanz und verschwendeter Aufwand.\n\nDiese Station hilft Ihnen, den Zweck Ihrer API, die Zielgruppe und die Erfolgskriterien zu definieren, damit Teams APIs bereitstellen können, die echte Probleme lösen.",
diff --git a/src/data/method/en/labels.stations.json b/src/data/method/en/labels.stations.json
index 021d5c7..451db99 100644
--- a/src/data/method/en/labels.stations.json
+++ b/src/data/method/en/labels.stations.json
@@ -339,8 +339,6 @@
   "station.upskilling.outcomes.2": "Improved ability to adopt new technologies and practices",
   "station.upskilling.outcomes.3": "Empowered teams to drive API innovation and quality",
   "station.upskilling.how_it_works": "Identify key API skills and knowledge areas that need enhancement, such as API design, security, and performance.",
-  "station.upskilling.how_it_works.1": "Provide training programs, workshops, and resources to help teams enhance their API skills and knowledge.",
-  "station.upskilling.how_it_works.2": "Encourage continuous learning through online courses, certifications, and community engagement.",
   "station.operating-guidelines.title": "Operating Guidelines - Establish API Governance",
   "station.operating-guidelines.description": "Establish operating guidelines and governance practices to ensure consistent API management and quality.",
   "station.operating-guidelines.why_it_matters": "Effective API governance is essential for ensuring consistent API management, quality, and compliance. This station provides operating guidelines and governance practices that help teams manage APIs effectively, ensuring they align with organizational standards and best practices.",
@@ -361,8 +359,6 @@
   "station.portfolio-management.outcomes.2": "Prioritization and optimization of APIs based on value and impact",
   "station.portfolio-management.outcomes.3": "Improved visibility and control over the API portfolio",
   "station.portfolio-management.how_it_works": "Define portfolio management practices that outline the processes for managing the API portfolio, including prioritization, monitoring, and optimization.",
-  "station.portfolio-management.how_it_works.1": "Establish criteria for evaluating and prioritizing APIs based on business value, impact, and alignment with strategic initiatives.",
-  "station.portfolio-management.how_it_works.2": "Monitor the API portfolio to ensure APIs are delivering value, meeting performance expectations, and aligning with business goals.",
   "station.budget-and-resource-management.title": "Budget and Resource Management - Optimize API Investments",
   "station.budget-and-resource-management.description": "Optimize budget and resource management for API initiatives to ensure effective investments and resource allocation.",
   "station.budget-and-resource-management.why_it_matters": "Effective budget and resource management is essential for ensuring that API initiatives are well-funded and resourced. This station provides guidelines for optimizing budget and resource management, ensuring that API initiatives are aligned with business goals and deliver maximum value.",
@@ -372,8 +368,6 @@
   "station.budget-and-resource-management.outcomes.2": "Optimized investments in API development and management",
   "station.budget-and-resource-management.outcomes.3": "Improved financial visibility and control over API initiatives",
   "station.budget-and-resource-management.how_it_works": "Define budget and resource management practices that outline the processes for managing budgets and resources for API initiatives.",
-  "station.budget-and-resource-management.how_it_works.1": "Establish criteria for evaluating and prioritizing budget allocations based on business value, impact, and alignment with strategic initiatives.",
-  "station.budget-and-resource-management.how_it_works.2": "Monitor budget and resource utilization to ensure effective investments and resource allocation for API initiatives.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "API Product Strategy - Turn APIs Into Strategic Products",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Before building anything, define your API's value, users, and business goals from day one.",
   "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Many organizations think of APIs as tech projects, not products. The result? Confused consumers, poor adoption, and wasted effort.\n\nThis station helps you define your API’s purpose, target audience, and success criteria, so teams can deliver APIs that solve real problems.",
diff --git a/src/data/method/fi/labels.stations.json b/src/data/method/fi/labels.stations.json
index c35a04a..6d334b3 100644
--- a/src/data/method/fi/labels.stations.json
+++ b/src/data/method/fi/labels.stations.json
@@ -357,8 +357,6 @@
   "station.upskilling.outcomes.1": "API-suunnittelun, -kehityksen ja -hallinnan lisääntynyt osaaminen.",
   "station.upskilling.outcomes.2": "Parempi kyky omaksua uutta teknologiaa ja uusia käytäntöjä",
   "station.upskilling.outcomes.3": "Valtuutetaan tiimit edistämään API-innovaatioita ja laatua.",
-  "station.upskilling.how_it_works.1": "Tarjotaan koulutusohjelmia, työpajoja ja resursseja, joiden avulla tiimit voivat parantaa API-taitojaan ja -tietämystään.",
-  "station.upskilling.how_it_works.2": "Kannustetaan jatkuvaan oppimiseen verkkokurssien, sertifikaattien ja yhteisöllisen sitoutumisen avulla.",
   "station.operating-guidelines.outcomes.1": "Yhdenmukainen API-hallinta ja laatu koko organisaatiossa",
   "station.operating-guidelines.outcomes.2": "organisaation standardien ja parhaiden käytäntöjen noudattaminen",
   "station.operating-guidelines.outcomes.3": "Parempi näkyvyys ja API-aloitteiden hallinta",
@@ -367,13 +365,9 @@
   "station.portfolio-management.outcomes.1": "APIt linjassa liiketoiminnan tavoitteiden ja strategisten aloitteiden kanssa.",
   "station.portfolio-management.outcomes.2": "APIen priorisointi ja optimointi arvon ja vaikutusten perusteella.",
   "station.portfolio-management.outcomes.3": "Parempi näkyvyys ja API-portfolion hallinta",
-  "station.portfolio-management.how_it_works.1": "Laaditaan kriteerit rajapintojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden kanssa yhteensopivuuden perusteella.",
-  "station.portfolio-management.how_it_works.2": "Seuraa API-portfoliota varmistaaksesi, että APIt tuottavat arvoa, täyttävät suorituskykyodotukset ja ovat linjassa liiketoiminnan tavoitteiden kanssa.",
   "station.budget-and-resource-management.outcomes.1": "Resurssien tehokas kohdentaminen API-aloitteisiin",
   "station.budget-and-resource-management.outcomes.2": "Optimoidut investoinnit API-kehitykseen ja -hallintaan",
   "station.budget-and-resource-management.outcomes.3": "Parempi taloudellinen näkyvyys ja API-aloitteiden valvonta.",
-  "station.budget-and-resource-management.how_it_works.1": "Laaditaan kriteerit budjettimäärärahojen arvioimiseksi ja priorisoimiseksi liiketoiminta-arvon, vaikutusten ja strategisten aloitteiden mukaisuuden perusteella.",
-  "station.budget-and-resource-management.how_it_works.2": "Seuraa budjettia ja resurssien käyttöä varmistaaksesi tehokkaat investoinnit ja resurssien jakamisen API-aloitteisiin.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "API-tuotestrategia - Tee rajapinnoista strategisia tuotteita",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Ennen kuin rakennat mitään, määrittele APIn arvo, hyödyntäjät ja liiketoiminnalliset tavoitteet heti alusta alkaen.",
   "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Monet organisaatiot pitävät rajapintoja teknisinä projekteina, eivät tuotteina. Tulos? Hämmentyneitä hyödyntäjiä, heikkoa käyttöönottoa ja turhaa työtä. Tämä asema auttaa määrittelemään APIn tarkoituksen, kohderyhmän ja menestyskriteerit, jotta tiimit voivat tuottaa rajapintoja, jotka ratkaisevat todellisia ongelmia.",
diff --git a/src/data/method/fr/labels.stations.json b/src/data/method/fr/labels.stations.json
index 30b6cd2..c8ea246 100644
--- a/src/data/method/fr/labels.stations.json
+++ b/src/data/method/fr/labels.stations.json
@@ -357,8 +357,6 @@
   "station.upskilling.outcomes.1": "Compétences accrues en matière de conception, de développement et de gestion des API",
   "station.upskilling.outcomes.2": "Amélioration de la capacité à adopter de nouvelles technologies et pratiques",
   "station.upskilling.outcomes.3": "Des équipes responsabilisées pour favoriser l'innovation et la qualité de l'API",
-  "station.upskilling.how_it_works.1": "Fournir des programmes de formation, des ateliers et des ressources pour aider les équipes à améliorer leurs compétences et leurs connaissances en matière d'API.",
-  "station.upskilling.how_it_works.2": "Encourager la formation continue par des cours en ligne, des certifications et l'engagement communautaire.",
   "station.operating-guidelines.outcomes.1": "Gestion et qualité cohérentes de l'API dans l'ensemble de l'organisation",
   "station.operating-guidelines.outcomes.2": "Respect des normes et des meilleures pratiques de l'organisation",
   "station.operating-guidelines.outcomes.3": "Amélioration de la visibilité et du contrôle des initiatives en matière d'API",
@@ -367,13 +365,9 @@
   "station.portfolio-management.outcomes.1": "Des API alignées sur les objectifs de l'entreprise et les initiatives stratégiques",
   "station.portfolio-management.outcomes.2": "Hiérarchisation et optimisation des API en fonction de leur valeur et de leur impact",
   "station.portfolio-management.outcomes.3": "Amélioration de la visibilité et du contrôle du portefeuille d'API",
-  "station.portfolio-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des API en fonction de la valeur métier, de l'impact et de l'alignement sur les initiatives stratégiques.",
-  "station.portfolio-management.how_it_works.2": "Contrôler le portefeuille d'API pour s'assurer que les API apportent de la valeur, répondent aux attentes en matière de performances et s'alignent sur les objectifs de l'entreprise.",
   "station.budget-and-resource-management.outcomes.1": "Affectation efficace des ressources aux initiatives de l'API",
   "station.budget-and-resource-management.outcomes.2": "Optimisation des investissements dans le développement et la gestion des API",
   "station.budget-and-resource-management.outcomes.3": "Amélioration de la visibilité financière et du contrôle des initiatives API",
-  "station.budget-and-resource-management.how_it_works.1": "Établir des critères d'évaluation et de hiérarchisation des affectations budgétaires en fonction de la valeur métier, de l'impact et de l'alignement sur les initiatives stratégiques.",
-  "station.budget-and-resource-management.how_it_works.2": "Contrôler le budget et l'utilisation des ressources afin de garantir l'efficacité des investissements et de l'affectation des ressources pour les initiatives de l'API.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "Stratégie produit API - Transformer les API en produits stratégiques",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Avant de construire quoi que ce soit, définissez dès le départ la valeur de votre API, ses utilisateurs et ses objectifs métier.",
   "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "De nombreuses organisations considèrent les API comme des projets technologiques et non comme des produits. Le résultat ? Des utilisateurs désorientés, une adoption médiocre et un gaspillage d'efforts.\n\nCette station vous aide à définir l'objectif, le public cible et les critères de réussite de votre API, afin que les équipes puissent fournir des API qui résolvent des problèmes réels.",
diff --git a/src/data/method/pt/labels.stations.json b/src/data/method/pt/labels.stations.json
index fef1321..1264a33 100644
--- a/src/data/method/pt/labels.stations.json
+++ b/src/data/method/pt/labels.stations.json
@@ -339,8 +339,6 @@
   "station.upskilling.outcomes.2": "Melhoria da capacidade de adoção de novas tecnologias e práticas",
   "station.upskilling.outcomes.3": "Equipas capacitadas para impulsionar a inovação e a qualidade da API",
   "station.upskilling.how_it_works": "Identificar as principais competências e áreas de conhecimento da API que precisam de ser melhoradas, como a conceção, a segurança e o desempenho da API.",
-  "station.upskilling.how_it_works.1": "Fornecer programas de formação, workshops e recursos para ajudar as equipas a melhorar as suas competências e conhecimentos em matéria de API.",
-  "station.upskilling.how_it_works.2": "Incentivar a aprendizagem contínua através de cursos em linha, certificações e envolvimento da comunidade.",
   "station.operating-guidelines.title": "Diretrizes operacionais - Estabelecer a governação da API",
   "station.operating-guidelines.description": "Estabelecer diretrizes operacionais e práticas de governação para garantir uma gestão e qualidade consistentes da API.",
   "station.operating-guidelines.why_it_matters": "A governação eficaz da API é essencial para garantir uma gestão, qualidade e conformidade consistentes da API. Esta estação fornece diretrizes operacionais e práticas de governação que ajudam as equipas a gerir as APIs de forma eficaz, assegurando o seu alinhamento com as normas organizacionais e as boas práticas.",
@@ -361,8 +359,6 @@
   "station.portfolio-management.outcomes.2": "Priorização e otimização de APIs com base no valor e no impacto",
   "station.portfolio-management.outcomes.3": "Melhoria da visibilidade e do controlo da carteira de API",
   "station.portfolio-management.how_it_works": "Definir práticas de gestão da carteira que descrevam os processos de gestão da carteira de API, incluindo a definição de prioridades, a monitorização e a otimização.",
-  "station.portfolio-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às APIs com base no valor de negócio, no impacto e no alinhamento com iniciativas estratégicas.",
-  "station.portfolio-management.how_it_works.2": "Monitorizar a carteira de APIs para garantir que as APIs estão a fornecer valor, a cumprir as expectativas de desempenho e a alinhar-se com os objetivos de negócio.",
   "station.budget-and-resource-management.title": "Orçamento e gestão de recursos - Otimizar os investimentos em API",
   "station.budget-and-resource-management.description": "Otimizar o orçamento e a gestão de recursos para as iniciativas API, a fim de garantir investimentos e atribuição de recursos eficazes.",
   "station.budget-and-resource-management.why_it_matters": "A gestão eficaz do orçamento e dos recursos é essencial para garantir que as iniciativas de API sejam bem financiadas e dotadas de recursos. Esta estação fornece diretrizes para otimizar a gestão do orçamento e dos recursos, assegurando que as iniciativas de API estão alinhadas com os objetivos de negócio e proporcionam o máximo valor.",
@@ -372,8 +368,6 @@
   "station.budget-and-resource-management.outcomes.2": "Investimentos optimizados no desenvolvimento e gestão de API",
   "station.budget-and-resource-management.outcomes.3": "Melhoria da visibilidade financeira e do controlo das iniciativas API",
   "station.budget-and-resource-management.how_it_works": "Definir práticas de gestão orçamental e de recursos que descrevam os processos de gestão de orçamentos e recursos para iniciativas de API.",
-  "station.budget-and-resource-management.how_it_works.1": "Estabelecer critérios para avaliar e dar prioridade às dotações orçamentais com base no valor de negócio, no impacto e no alinhamento com as iniciativas estratégicas.",
-  "station.budget-and-resource-management.how_it_works.2": "Controlar o orçamento e a utilização dos recursos para garantir investimentos eficazes e a afetação de recursos às iniciativas da API.",
   "cycle.api-productization-cycle.station.api-product-strategy.title": "Estratégia de produtos API - Transforme APIs em produtos estratégicos",
   "cycle.api-productization-cycle.station.api-product-strategy.description": "Antes de construir qualquer coisa, defina o valor da sua API, os utilizadores e os objetivos de negócio desde o primeiro dia.",
   "cycle.api-productization-cycle.station.api-product-strategy.why_it_matters": "Muitas organizações pensam nas APIs como projetos tecnológicos e não como produtos. O resultado? Consumidores confusos, fraca adoção e esforço desperdiçado.\n\nEsta estação ajuda-o a definir o objetivo da sua API, o público-alvo e os critérios de sucesso, para que as equipas possam fornecer APIs que resolvam problemas reais.",
diff --git a/src/data/method/stations.json b/src/data/method/stations.json
index 51bd44b..90409c4 100644
--- a/src/data/method/stations.json
+++ b/src/data/method/stations.json
@@ -1046,14 +1046,6 @@
           {
             "step": "station.upskilling.how_it_works",
             "resource": "api-training-programs"
-          },
-          {
-            "step": "station.upskilling.how_it_works.1",
-            "resource": "api-training-programs"
-          },
-          {
-            "step": "station.upskilling.how_it_works.2",
-            "resource": "api-training-programs"
           }
         ],
         "apply_in_work": "station.upskilling.apply_in_work"
@@ -1106,14 +1098,6 @@
           {
             "step": "station.portfolio-management.how_it_works",
             "resource": "api-portfolio-management-guidelines"
-          },
-          {
-            "step": "station.portfolio-management.how_it_works.1",
-            "resource": "api-portfolio-management-guidelines"
-          },
-          {
-            "step": "station.portfolio-management.how_it_works.2",
-            "resource": "api-portfolio-management-guidelines"
           }
         ],
         "apply_in_work": "station.portfolio-management.apply_in_work"
@@ -1136,14 +1120,6 @@
           {
             "step": "station.budget-and-resource-management.how_it_works",
             "resource": "api-portfolio-management-guidelines"
-          },
-          {
-            "step": "station.budget-and-resource-management.how_it_works.1",
-            "resource": "api-portfolio-management-guidelines"
-          },
-          {
-            "step": "station.budget-and-resource-management.how_it_works.2",
-            "resource": "api-portfolio-management-guidelines"
           }
         ],
         "apply_in_work": "station.budget-and-resource-management.apply_in_work"

From 71a7da35571666c8bb4e784a53fc0a0e779a4510 Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Wed, 15 Jul 2026 09:39:12 +0300
Subject: [PATCH 11/12] update dependencies

---
 package-lock.json | 28 ++++++++++++++++++++++------
 1 file changed, 22 insertions(+), 6 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index 21a0a8d..4868ae1 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -802,10 +802,20 @@
       "license": "ISC"
     },
     "node_modules/js-yaml": {
-      "version": "4.1.1",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz",
-      "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==",
+      "version": "4.3.0",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.3.0.tgz",
+      "integrity": "sha512-1td788aAnnZ5qs7V2QIRl1owjtYpbKt749Y3xauqQgwIIGF/xXWz1wMTEBx5O3LK3lXLVuqXPdPxj2BoFHaW9Q==",
       "dev": true,
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/puzrin"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/nodeca"
+        }
+      ],
       "license": "MIT",
       "dependencies": {
         "argparse": "^2.0.1"
@@ -1105,9 +1115,9 @@
       }
     },
     "node_modules/read-yaml-file/node_modules/js-yaml": {
-      "version": "3.14.2",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.2.tgz",
-      "integrity": "sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==",
+      "version": "3.15.0",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.15.0.tgz",
+      "integrity": "sha512-ttBQIIQPDeLjpPOohtUdXuXUVoA2uIB6fEH9HyJ7234s5mBJ5wTx20njxplLZQgLaOfpmPQA7X2t5AX6tIPbog==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -1341,7 +1351,13 @@
       },
       "engines": {
         "node": ">=22"
+      },
+      "optionalDependencies": {
+        "apiops-cycles-method-data": "^4.0.0"
       }
+    },
+    "packages/create-apiops/node_modules/apiops-cycles-method-data": {
+      "optional": true
     }
   }
 }

From e5d50c4ff90ae60f9da9bdb27b1eca061e18dedb Mon Sep 17 00:00:00 2001
From: Marjukka Niinioja <mniinio@users.noreply.github.com>
Date: Wed, 15 Jul 2026 09:39:34 +0300
Subject: [PATCH 12/12] 4.0.0

---
 package-lock.json | 4 ++--
 package.json      | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index 4868ae1..fc71509 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "apiops-cycles-method-data",
-  "version": "3.4.4",
+  "version": "4.0.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "apiops-cycles-method-data",
-      "version": "3.4.4",
+      "version": "4.0.0",
       "license": "Apache-2.0",
       "workspaces": [
         "packages/*"
diff --git a/package.json b/package.json
index 9475e85..7e1b508 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "apiops-cycles-method-data",
-  "version": "3.4.4",
+  "version": "4.0.0",
   "description": "APIOps Cycles Method data and canvases",
   "license": "Apache-2.0",
   "type": "module",