Medtronic Signals

The world's largest medical device company developing therapies for cardiovascular, neurological, diabetes, and surgical conditions. Pioneers in pacemakers, insulin pumps, spinal implants, and robotic-assisted surgery serving patients in over 150 countries.

This is a Naftiko Signals read of Medtronic’s technology and AI investment posture — mined from public workforce signals (job postings, press releases, newsroom content) and matched against Naftiko’s curated vocabulary of services, tools, concepts, and standards across the 44 Naftiko signal groups.

For Medtronic we detected 1039 areas, 95 services, 46 tools, and 89 standards — producing a total signal score of 1129.

How to read this page: Impact Report is the narrative read-out. Capabilities are Naftiko agent workflows you could ship on top of Medtronic’s existing stack — each one runnable in the Naftiko Framework. Navigation ranks the next moves we’d recommend, grouped by theme. Signals is the score breakdown across every Naftiko signal group, each row linking to its definition. Areas, Services, Tools, and Standards are the raw detections behind the score. Why? explains the methodology and audience.

Take Control Of Your Signals — Become a Naftiko Design Partner Today!
What’s next for you? Pick your role — we’ll point you at the right capability and next step.

Medtronic Technology Investment Impact Report

Prepared by Naftiko April 2026

Executive Summary

This report presents a signal-based analysis of Medtronic’s technology investment posture, derived from Naftiko’s methodology of examining services deployed, tools adopted, concepts referenced, and standards followed across workforce signals. The analysis spans foundational infrastructure, data platforms, customization capabilities, operational efficiency, productivity, integration, governance, economics, and strategic alignment.

The world’s largest medical device company developing therapies for cardiovascular, neurological, diabetes, and surgical conditions. Pioneers in pacemakers, insulin pumps, spinal implants, and robotic-assisted surgery serving patients in over 150 countries.

The assessment yields a total signal score of 1129 across 41 dimensions. The six strongest signal categories are services (95), data (77), security (65), operations (57), cloud (54), talentOrganizationalDesign (54).


Layer 1: Foundational Layer

Evaluating Medtronic’s foundational capabilities across Artificial Intelligence, Cloud, Open-Source, Languages, and Code — the core infrastructure and development building blocks supporting Healthcare / Medical Devices operations.

Waves: Large Language Models (LLMs), Generative Pre-trained Transformer (GPT), Open-Source LLMs

Artificial Intelligence — Score: 26 #30/80

Medtronic’s AI score of 26 reflects adoption across Databricks, GitHub Copilot.

  • Services: Databricks, GitHub Copilot
  • Concepts: Agentic AI, Agentics, Agents, Artificial Intelligence, Artificial Intelligence/Machine Learning, Generative AI, Inferences, LLM

AI posture sets the ceiling on downstream AI workloads at Medtronic.

Cloud — Score: 54 #18/80

Cloud score of 54 spans AWS Lambda, Amazon Web Services, Azure Active Directory alongside IaC tooling (Buildpacks, Docker, Kubernetes).

  • Services: AWS Lambda, Amazon Web Services, Azure Active Directory, Azure DevOps, CloudFormation, CloudWatch, Google Cloud Platform, Microsoft Azure
  • Tools: Buildpacks, Docker, Kubernetes, Terraform
  • Concepts: Cloud Computing, Cloud Connectivity, Cloud Data, Cloud Data Platforms, Cloud Environments, Cloud Infrastructure, Cloud Natives, Cloud Platforms
  • Standards: SDLC

Cloud maturity is the anchor for scaling AI workloads at Medtronic.

Open-Source — Score: 18 #17/80

Open-Source score of 18 anchored on Bitbucket, GitHub, GitHub Copilot.

  • Services: Bitbucket, GitHub, GitHub Copilot, GitLab
  • Tools: Angular, Apache AGE, Apache Brooklyn, Apache Flex, Apache Kafka, Apache Olingo, Apache Phoenix, Apache Pivot
  • Concepts: Contributions
  • Standards: CODE_OF_CONDUCT.md, CONTRIBUTING.md, CONTRIBUTORS.md, LICENSE.md, SECURITY.md

Consumption is broad; formal contribution posture is an opportunity area.

Languages — Score: 24 #20/80

Languages score of 24 across ABAP, C++, CSS, Go, Java.

  • Languages: ABAP, C++, CSS, Go, Java, JavaScript, Move, Ruby

Language mix is a revealing signal of Medtronic’s engineering history and modernization priorities.

Code — Score: 53 #15/80

Code score of 53 anchored on Azure DevOps, Bitbucket, GitHub.

  • Services: Azure DevOps, Bitbucket, GitHub, GitHub Copilot, GitLab, IntelliJ IDEA
  • Tools: Git, PowerShell
  • Concepts: Application Programming Interfaces, CNC Programming, Code Analysis, Code Quality, Code Repositories, Code Reviews, Codes, Continuous Integration/Continuous Deployments
  • Standards: DevOps, SDLC, Secure Software Development Lifecycle

Developer tooling is the lever for compound productivity via AI coding assistants.

Layer Summary: Medtronic’s Foundational Layer reflects AI (26), Cloud (54), Open-Source (18), Languages (24), and Code (53) — the bedrock on which every subsequent AI-readiness capability is built.


Layer 2: Retrieval & Grounding

Evaluating Medtronic’s data and retrieval capabilities — Data, Databases, Virtualization, Specifications, Context Engineering — that ground AI workloads in enterprise information.

Waves: Vector Databases, Retrieval-Augmented Generation (RAG), Prompt Engineering, Context Engineering

Data — Score: 77 #28/80

Data score of 77 reflects Databricks, Informatica, MATLAB.

  • Services: Databricks, Informatica, MATLAB, Power BI, Power Query, Snowflake, Splunk, Tableau Desktop
  • Tools: Apache Kafka, MySQL, R
  • Concepts: Business Analytics, Data Analysis, Data Analysis Tools, Data Analysis Tools And Software, Data Analytics, Data Governance, Data Governance Frameworks, Data Management
  • Standards: Data Modeling, Data Models

Analytical depth is the foundation for retrieval-augmented AI.

Databases — Score: 11 #29/80

Databases score of 11 spans Oracle, SAP HANA, Snowflake.

  • Services: Oracle, SAP HANA, Snowflake
  • Tools: MySQL
  • Concepts: Database Management, Database Technologies, Databases, Relational Databases, Relationals
  • Standards: SQL

Portfolio rationalization is an ongoing lever.

Virtualization — Score: 13 #18/80

Virtualization score of 13 on EMC, Solaris Zones, Docker.

  • Services: EMC, Solaris Zones
  • Tools: Docker, Kubernetes
  • Concepts: Container Securities, Containerization, Containers

Containerization paired with VMs is a pragmatic stance.

Specifications — Score: 6 #25/80

Specifications score of 6 rooted in REST/HTTP/JSON.

  • Concepts: API Development, API Gateways, API Management, API Securities, API Strategies, Application Programming Interfaces, Capital Markets, Rapid Prototyping
  • Standards: HTTP, REST, TCP/IP, XML

Formalizing OpenAPI as enterprise standard is a prerequisite for AI agent integration.

Context Engineering

Medtronic’s Context Engineering investment is emerging.

Pairing strong Data with formal context layer is the highest-leverage AI readiness move.

Layer Summary: Medtronic’s Retrieval posture is shaped by Data (77), Databases (11), and Specifications (6).


Layer 3: Customization & Adaptation

Evaluating Medtronic’s capabilities for customizing AI to its business — Data Pipelines, Model Registry, Multimodal Infrastructure, Domain Specialization.

Waves: Fine-Tuning & Model Customization, Multimodal AI

Data Pipelines — Score: 12 #24/80

Data Pipelines score of 12 reflects Apache Kafka.

  • Services: Informatica
  • Tools: Apache Kafka
  • Concepts: B2B Integrations, Continuous Integration/Continuous Deployments, Data Pipelines, Extract Transform Loads, Integration Testing, Integration Tests, Integrations, System Integrations

Streaming pipelines prerequisite for real-time AI inference.

Model Registry & Versioning — Score: 6 #36/80

Model Registry score of 6 via Databricks.

  • Services: Databricks

Enterprise registry with approvals is prerequisite for regulated AI.

Multimodal Infrastructure — Score: 2 #41/80

Multimodal score of 2 via limited recorded signals.

  • Concepts: Generative AI

Centralized OCR/audio/image extractors improve AI project productivity.

Domain Specialization — Score: 2

Domain Specialization score of 2.

Industry-specific fine-tuning is a differentiated long-term capability for Medtronic.

Layer Summary: Customization bridges generic AI and business-specific advantage.


Layer 4: Efficiency & Specialization

Evaluating Medtronic’s operational efficiency and platform layer — Automation, Containers, Platform, Operations.

Waves: Small Language Models (SLMs), Model Routing / Orchestration, Reasoning Models

Automation — Score: 46 #17/80

Automation score of 46 reflects Make, Microsoft Power Apps, Microsoft Power Automate.

  • Services: Make, Microsoft Power Apps, Microsoft Power Automate, ServiceNow
  • Tools: PowerShell
  • Concepts: Automation, Building Automation, Marketing Automation, Process Automation, Robotic Process Automation, Security Automation, Test Automation, Test Automation Frameworks

Automation footprint is ready for AI augmentation on high-toil processes.

Containers — Score: 14 #10/80

Containers score of 14 on Buildpacks, Docker, Kubernetes.

  • Tools: Buildpacks, Docker, Kubernetes
  • Concepts: Container Securities, Containerization, Containers

Container-native AI deployment is the logical next step.

Platform — Score: 22 #19/80

Platform score of 22 spans AWS Lambda, Amazon Web Services, Azure Active Directory.

  • Services: AWS Lambda, Amazon Web Services, Azure Active Directory, Azure DevOps, Google Cloud Platform, Microsoft Azure, SAP, SAP Ariba
  • Concepts: Application Platforms, Cloud Data Platforms, Cloud Platforms, Cloud Workload Protection Platforms, Cloud-Based Data Platforms, Data Platforms, Platform Engineering, Platform Securities

Platform engineering maturity is the next milestone.

Operations — Score: 57 #17/80

Operations score of 57 anchored on ServiceNow, Splunk.

  • Services: ServiceNow, Splunk
  • Tools: Chef, Prometheus, Terraform
  • Concepts: Business Operations, Financial Operations, Incident Management, Incident Responses, Operational Excellence, Operations Management, Security Incident Responses, Security Operations

Operational tooling is a foundation for AI-driven SRE.

Layer Summary: Automation (46) and Operations (57) are direct levers for AI-augmented productivity.


Layer 5: Productivity

Evaluating Medtronic’s productivity tooling — SaaS, Services, Code.

Waves: Coding Assistants, Copilots

Software As A Service (SaaS) — Score: 19 #13/80

SaaS score of 19 includes LinkedIn, Microsoft Teams, SAP Concur, Salesforce, Workday.

  • Services: LinkedIn, Microsoft Teams, SAP Concur, Salesforce, Workday

Rationalization and unified auth are the optimization opportunities.

Code — Score: 53 #15/80

Code anchored on Azure DevOps, Bitbucket, GitHub.

  • Services: Azure DevOps, Bitbucket, GitHub, GitHub Copilot, GitLab, IntelliJ IDEA
  • Tools: Git, PowerShell
  • Concepts: Application Programming Interfaces, CNC Programming, Code Analysis, Code Quality, Code Repositories, Code Reviews, Codes, Continuous Integration/Continuous Deployments
  • Standards: DevOps, SDLC, Secure Software Development Lifecycle

Wiring coding assistants creates compound productivity gains.

Services — Score: 95 #20/80

Services score of 95 spans Medtronic’s full service portfolio.

  • Services: AWS Lambda, Adobe, Adobe Acrobat, Adobe Launch, Amazon Web Services, AutoCAD, Azure Active Directory, Azure DevOps

Scale of services drives the integration-layer imperative.

Layer Summary: Services score of 95 reflects Medtronic’s breadth of enterprise SaaS consumption.


Layer 6: Integration & Interoperability

Evaluating Medtronic’s API, integration, event-driven connectivity.

Waves: MCP (Model Context Protocol), Agents, Skills

API — Score: 17 #15/80

API score of 17; concepts: API Development, API Gateways, API Management.

  • Services: Kong
  • Concepts: API Development, API Gateways, API Management, API Securities, API Strategies, Capital Markets, Rapid Prototyping, Working Capital
  • Standards: HTTP, REST

Formalizing API standards is the most impactful integration move.

Integrations — Score: 28 #14/80

Integrations score of 28 spans Informatica.

  • Services: Informatica
  • Concepts: B2B Integrations, Continuous Integration/Continuous Deployments, Integration Testing, Integration Tests, Integrations, System Integrations, Systems Integrations
  • Standards: Enterprise Integration Patterns, SOA

iPaaS reduces integration debt.

Event-Driven — Score: 11 #13/80

Event-Driven score of 11.

  • Tools: Apache Kafka, RabbitMQ
  • Concepts: Data Streamings, Disease Preventions, Event Management, Event Plannings, Event Streamings, Events, Security Information and Event Management, Streamings

Event streaming is foundational for real-time AI.

Patterns — Score: 18 #12/80

Patterns score of 18 on Spring Cloud Stream, Actor Model, SOA.

  • Tools: Spring Cloud Stream
  • Concepts: Microservices, Patterns, Reactives
  • Standards: Actor Model, SOA

Microservice patterns support AI workload scaling.

Specifications — Score: 6 #25/80

Specifications score of 6.

  • Concepts: API Development, API Gateways, API Management, API Securities, API Strategies, Application Programming Interfaces, Capital Markets, Rapid Prototyping
  • Standards: HTTP, REST, TCP/IP, XML

Elevating OpenAPI to enterprise standard creates shared vocabulary for AI.

Apache — Score: 12 #23/80

Apache score of 12: Apache AGE, Apache Brooklyn, Apache Flex, Apache Kafka, Apache Olingo.

  • Tools: Apache AGE, Apache Brooklyn, Apache Flex, Apache Kafka, Apache Olingo, Apache Phoenix, Apache Pivot, Apache Streams

Apache ecosystem depth is a characteristic enterprise strength.

CNCF — Score: 13 #7/80

CNCF score of 13: Buildpacks, Flux, Kubernetes.

  • Tools: Buildpacks, Flux, Kubernetes, Prometheus

CNCF maturity pairs with Kubernetes adoption.

Layer Summary: API (17) and Integrations (28) are the connective tissue for scaling AI.


Layer 7: Statefulness

Evaluating Medtronic’s Observability, Governance, Security, Data handling.

Waves: Memory Systems

Observability — Score: 27 #14/80

Observability score of 27 spans CloudWatch, Splunk.

  • Services: CloudWatch, Splunk
  • Tools: Prometheus
  • Concepts: Alerting, Compliance Monitoring, Continuous Monitoring, Logging, Monitoring, Monitoring Software, Monitoring Tools, Performance Monitoring

Consolidation lowers cost.

Governance — Score: 53 #18/80

Governance score of 53; standards: GDPR, ISO, ITIL.

  • Concepts: Architecture Governance, Audit Processes, Audit Trails, Audits, Compliance, Compliance Frameworks, Compliance Management, Compliance Monitoring
  • Standards: GDPR, ISO, ITIL, ITSM, NIST, OSHA, RACI, Six Sigma

Extending to AI governance is the natural evolution.

Security — Score: 65 #6/80

Security score of 65 anchored on Palo Alto Networks.

  • Services: Palo Alto Networks
  • Concepts: Authentications, Authorizations, Cloud Security Posture Management, Cybersecurity Frameworks, Dynamic Application Security Testing, Product Security Testing, Security Architectures, Security Assessments
  • Standards: Cybersecurity Standards, IAM, ISO, NIST, SECURITY.md, SSO, SecOps, Security Standards

AI-specific security is a required add to existing program.

Data — Score: 77 #28/80

Data — Databricks, Informatica, MATLAB anchors.

  • Services: Databricks, Informatica, MATLAB, Power BI, Power Query, Snowflake, Splunk, Tableau Desktop
  • Tools: Apache Kafka, MySQL, R
  • Concepts: Business Analytics, Data Analysis, Data Analysis Tools, Data Analysis Tools And Software, Data Analytics, Data Governance, Data Governance Frameworks, Data Management
  • Standards: Data Modeling, Data Models

Continued cataloging and lineage pays off at AI scale.

Layer Summary: Observability (27), Governance (53), Security (65) reflect Medtronic’s operational maturity.


Layer 8: Measurement & Accountability

Evaluating Medtronic’s measurement discipline — Testing, Observability, DevEx, ROI.

Waves: Evaluation & Benchmarking

Testing & Quality — Score: 25 #11/80

Testing score of 25 with JUnit.

  • Tools: JUnit
  • Concepts: Acceptance Testing, Automated Testing, Automated Testing Frameworks, Dynamic Application Security Testing, Functional Testing, Integration Testing, Integration Tests, Penetration Testing
  • Standards: Acceptance Criteria, SDLC, Six Sigma, Test Cases, Test Plans, Test Scripts

AI-specific evals extend traditional testing.

Observability — Score: 27 #14/80

Observability — CloudWatch, Splunk.

  • Services: CloudWatch, Splunk
  • Tools: Prometheus
  • Concepts: Alerting, Compliance Monitoring, Continuous Monitoring, Logging, Monitoring, Monitoring Software, Monitoring Tools, Performance Monitoring

Instrumented for AI workload observation.

Developer Experience — Score: 22 #13/80

DevEx score of 22 on Azure DevOps, GitHub, GitHub Copilot.

  • Services: Azure DevOps, GitHub, GitHub Copilot, GitLab, IntelliJ IDEA
  • Tools: Docker, Git

DORA metrics and IDPs are next investments.

ROI & Business Metrics — Score: 35 #20/80

ROI score of 35 reflects Oracle Hyperion, Power BI, SAP.

  • Services: Oracle Hyperion, Power BI, SAP, Tableau Desktop
  • Concepts: Androids, Business Analytics, Financial Accounting, Financial Analysis, Financial Controls, Financial Data, Financial Modeling, Financial Operations

ROI discipline translates naturally to AI initiatives.

Layer Summary: Measurement is necessary for accountable AI initiatives.


Layer 9: Governance & Risk

Evaluating Medtronic’s Regulatory, AI Review, Security, Governance, Privacy controls.

Waves: Governance & Compliance

Regulatory Posture — Score: 28 #12/80

Regulatory score of 28 with standards: Cybersecurity Standards, GDPR, Good Manufacturing Practices.

  • Concepts: Compliance, Compliance Frameworks, Compliance Management, Compliance Monitoring, Compliance Policies, Compliance Systems, Legal, Legal Compliances
  • Standards: Cybersecurity Standards, GDPR, Good Manufacturing Practices, ISO, Internal Control Standards, NIST, OSHA

Proactive alignment with NIST AI RMF is a forward investment.

AI Review & Approval — Score: 23 #27/80

AI Review score of 23 with limited recorded signals.

Formalized AI review council is the priority governance investment.

Security — Score: 65 #6/80

Security — Palo Alto Networks.

  • Services: Palo Alto Networks
  • Concepts: Authentications, Authorizations, Cloud Security Posture Management, Cybersecurity Frameworks, Dynamic Application Security Testing, Product Security Testing, Security Architectures, Security Assessments
  • Standards: Cybersecurity Standards, IAM, ISO, NIST, SECURITY.md, SSO, SecOps, Security Standards

AI threat model coverage extends existing security.

Governance — Score: 53 #18/80

Governance standards: GDPR, ISO, ITIL.

  • Concepts: Architecture Governance, Audit Processes, Audit Trails, Audits, Compliance, Compliance Frameworks, Compliance Management, Compliance Monitoring
  • Standards: GDPR, ISO, ITIL, ITSM, NIST, OSHA, RACI, Six Sigma

AI governance as first-class discipline is the next step.

Privacy & Data Rights — Score: 7 #32/80

Privacy score of 7.

  • Concepts: Data Protection, Privacy
  • Standards: GDPR

Formal ‘training-eligible?’ classification prevents inadvertent PII use in models.

Layer Summary: Security (65), Governance (53), AI Review (23) shape the AI compliance envelope.


Layer 10: Economics & Sustainability

Evaluating Medtronic’s AI FinOps, Provider Strategy, Partnerships, Talent, Data Centers.

Waves: Cost Economics & FinOps, Supply Chain & Dependency Risk, Data Centers

AI FinOps — Score: 4 #26/80

AI FinOps score of 4 with AWS Lambda, Amazon Web Services, Azure Active Directory.

  • Services: AWS Lambda, Amazon Web Services, Azure Active Directory, Azure DevOps, Google Cloud Platform, Microsoft Azure
  • Concepts: Budgetings, Cost Accounting, Cost Controls, Cost Management, Cost Optimizations, Financial Plannings

Token-cost tagging required before AI spend accelerates.

Provider Strategy — Score: 17 #23/80

Provider Strategy score of 17 with Amazon Web Services, Google Cloud Platform, Microsoft, Microsoft 365.

  • Services: Amazon Web Services, Google Cloud Platform, Microsoft, Microsoft 365, Microsoft Azure, Microsoft Edge, Microsoft Entra, Microsoft Office
  • Concepts: Supplier Management, Vendor Management

Explicit provider strategy tightens AI partnership decisions.

Partnerships & Ecosystem — Score: 41 #18/80

Partnerships score of 41 with AWS Lambda, Amazon Web Services, Google, Google Analytics.

  • Services: AWS Lambda, Amazon Web Services, Google, Google Analytics, Google Apps Script, Google Cloud Platform, Google Drive, Google Maps
  • Concepts: Ecosystems

AI-specific partnerships are emerging.

Talent & Organizational Design — Score: 54 #18/80

Talent score of 54 with LinkedIn, Workday.

  • Services: LinkedIn, Workday
  • Concepts: AI Trainings, Artificial Intelligence/Machine Learning, Continuous Learning, E-learnings, Human Resources, Learning, Learning Management, Machine Learning

Aligning talent toward AI skill development is direct leverage.

Data Centers

Data Centers investment signals are limited.

Hybrid-cloud vs public-cloud becomes a board-level question at AI scale.

Layer Summary: Talent (54) and Partnerships (41) most affect AI outcomes.


Layer 11: Storytelling & Entertainment & Theater

Evaluating Medtronic’s strategic narrative — Alignment, Standardization, M&A, Experimentation.

Waves: Moltbook, Gastown, Ralph Wiggum, OpenClaw / Clawdbot, Artificial General Intelligence (AGI)

Alignment — Score: 27 #11/80

Alignment score of 27; concepts: Architecture Governance, Architecture Strategies, Architectures.

  • Concepts: Architecture Governance, Architecture Strategies, Architectures, Business Transformations, Cloud-native Architectures, Data Architectures, Data Transformations, Digital Transformations
  • Standards: Agile, Agile Methodology, Lean Management, Lean Manufacturing, Scrum

Aligning AI to business outcomes makes AI accountable.

Standardization — Score: 26 #10/80

Standardization score of 26: Agile, ISO, NIST, REST, SDLC.

  • Standards: Agile, ISO, NIST, REST, SDLC, SQL, Standard Operating Procedures, Technical Specifications

Extending to AI (model cards, eval suites) is a natural evolution.

Mergers & Acquisitions — Score: 19 #14/80

M&A score of 19.

  • Concepts: Due Diligences, Financial Modeling, M&AS, Talent Acquisition

AI-capability acquisitions can accelerate gaps.

Experimentation & Prototyping

Experimentation & Prototyping signals are limited.

A named internal AI sandbox reduces shadow-AI risk.

Layer Summary: Alignment (27) and Standardization (26) shape AI program direction.


Strategic Assessment

Top Three 2026 Investment Recommendations for Medtronic

  1. Establish an API-First Integration Layer. API score of 17 across 95 services leaves Medtronic without reusable connective tissue. Prioritize API standards, deploy an enterprise gateway, publish a service catalog.

  2. Stand Up a Formal AI Governance and Review Council. AI Review score of 23 combined with AI adoption (score 26) creates regulatory and reputational risk. Charter a council, publish review criteria, gate production AI.

  3. Invest in Real-Time Data Pipelines and Event Streams. Data Pipelines (12) and Event-Driven (11) are the gap between data platform maturity and real-time AI. Extend Kafka or Azure Event Hubs to critical flows first.


Methodology

Scores derive from the density and diversity of signals detected across Services, Tools, Concepts, and Standards, aggregated into 11 strategic layers mapping the full technology stack.

Based on signal data available as of April 2026.

Capabilities are Naftiko definitions for how enterprise services, tools, and standards can be combined to deliver business value using AI. Each capability below defines the integrations, workflows, and orchestrations available — run them with the Naftiko Framework or browse the shipped set in the Naftiko Fleet.

Sort
Expand
71 capabilities

Access Review Campaign Generation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Access Review Campaign Generation
  description: Access Review Campaign Generation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - servicenow
  - automation
capability:
  exposes:
  - type: mcp
    namespace: access-review
    port: 8080
    tools:
    - name: execute
      description: Access Review Campaign Generation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: access-review.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: access-review
    baseUri: https://medtronic.internal.example.com/access-review/v1
    authentication:
      type: bearer
      token: $secrets.access_review_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → access-review-campaign-generation.yml

Accounts Payable Invoice Approval Routing — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Accounts Payable Invoice Approval Routing
  description: Accounts Payable Invoice Approval Routing — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - oracle
  - automation
capability:
  exposes:
  - type: mcp
    namespace: ap-approval
    port: 8080
    tools:
    - name: execute
      description: Accounts Payable Invoice Approval Routing — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: ap-approval.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: ap-approval
    baseUri: https://medtronic.internal.example.com/ap-approval/v1
    authentication:
      type: bearer
      token: $secrets.ap_approval_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → accounts-payable-invoice-approval-routing.yml

Adobe Campaign Launch Readiness Check — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Adobe Campaign Launch Readiness Check
  description: Adobe Campaign Launch Readiness Check — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - adobe-campaign
  - automation
capability:
  exposes:
  - type: mcp
    namespace: campaign-ready
    port: 8080
    tools:
    - name: execute
      description: Adobe Campaign Launch Readiness Check — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: campaign-ready.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: campaign-ready
    baseUri: https://medtronic.internal.example.com/campaign-ready/v1
    authentication:
      type: bearer
      token: $secrets.campaign_ready_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → adobe-campaign-launch-readiness-check.yml

APM Latency Spike Investigation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: APM Latency Spike Investigation
  description: APM Latency Spike Investigation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - datadog
  - automation
capability:
  exposes:
  - type: mcp
    namespace: apm-spike
    port: 8080
    tools:
    - name: execute
      description: APM Latency Spike Investigation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: apm-spike.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: apm-spike
    baseUri: https://medtronic.internal.example.com/apm-spike/v1
    authentication:
      type: bearer
      token: $secrets.apm_spike_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → apm-latency-spike-investigation.yml

Azure DevOps Work Item Auto-Link — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Azure DevOps Work Item Auto-Link
  description: Azure DevOps Work Item Auto-Link — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - azure-devops
  - automation
capability:
  exposes:
  - type: mcp
    namespace: ado-link
    port: 8080
    tools:
    - name: execute
      description: Azure DevOps Work Item Auto-Link — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: ado-link.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: ado-link
    baseUri: https://medtronic.internal.example.com/ado-link/v1
    authentication:
      type: bearer
      token: $secrets.ado_link_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → azure-devops-work-item-auto-link.yml

Budget vs Actual Variance Explainer — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Budget vs Actual Variance Explainer
  description: Budget vs Actual Variance Explainer — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - sap
  - automation
capability:
  exposes:
  - type: mcp
    namespace: variance
    port: 8080
    tools:
    - name: execute
      description: Budget vs Actual Variance Explainer — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: variance.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: variance
    baseUri: https://medtronic.internal.example.com/variance/v1
    authentication:
      type: bearer
      token: $secrets.variance_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → budget-vs-actual-variance-explainer.yml

Change Management Request Triage — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Change Management Request Triage
  description: Change Management Request Triage — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - servicenow
  - automation
capability:
  exposes:
  - type: mcp
    namespace: change-mgmt
    port: 8080
    tools:
    - name: execute
      description: Change Management Request Triage — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: change-mgmt.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: change-mgmt
    baseUri: https://medtronic.internal.example.com/change-mgmt/v1
    authentication:
      type: bearer
      token: $secrets.change_mgmt_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → change-management-request-triage.yml

CI/CD Failure Observability Chain — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: CI/CD Failure Observability Chain
  description: CI/CD Failure Observability Chain — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - github
  - automation
capability:
  exposes:
  - type: mcp
    namespace: ci-failure
    port: 8080
    tools:
    - name: execute
      description: CI/CD Failure Observability Chain — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: ci-failure.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: ci-failure
    baseUri: https://medtronic.internal.example.com/ci-failure/v1
    authentication:
      type: bearer
      token: $secrets.ci_failure_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → ci-cd-failure-observability-chain.yml

Conduct Quarterly Technology Posture Review — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Conduct Quarterly Technology Posture Review
  description: Conduct Quarterly Technology Posture Review — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: posture-review
    port: 8080
    tools:
    - name: execute
      description: Conduct Quarterly Technology Posture Review — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: posture-review.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: posture-review
    baseUri: https://medtronic.internal.example.com/posture-review/v1
    authentication:
      type: bearer
      token: $secrets.posture_review_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → conduct-quarterly-technology-posture-review.yml

Daily General Ledger Close Check — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Daily General Ledger Close Check
  description: Daily General Ledger Close Check — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - sap
  - automation
capability:
  exposes:
  - type: mcp
    namespace: gl-close
    port: 8080
    tools:
    - name: execute
      description: Daily General Ledger Close Check — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: gl-close.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: gl-close
    baseUri: https://medtronic.internal.example.com/gl-close/v1
    authentication:
      type: bearer
      token: $secrets.gl_close_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → daily-general-ledger-close-check.yml

Data Quality SLO Check — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Data Quality SLO Check
  description: Data Quality SLO Check — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - snowflake
  - automation
capability:
  exposes:
  - type: mcp
    namespace: dq-slo
    port: 8080
    tools:
    - name: execute
      description: Data Quality SLO Check — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: dq-slo.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: dq-slo
    baseUri: https://medtronic.internal.example.com/dq-slo/v1
    authentication:
      type: bearer
      token: $secrets.dq_slo_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → data-quality-slo-check.yml

Datadog Alert Fatigue Audit — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Datadog Alert Fatigue Audit
  description: Datadog Alert Fatigue Audit — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - datadog
  - automation
capability:
  exposes:
  - type: mcp
    namespace: alert-audit
    port: 8080
    tools:
    - name: execute
      description: Datadog Alert Fatigue Audit — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: alert-audit.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: alert-audit
    baseUri: https://medtronic.internal.example.com/alert-audit/v1
    authentication:
      type: bearer
      token: $secrets.alert_audit_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → datadog-alert-fatigue-audit.yml

Email Phishing Training Campaign Dispatch — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Email Phishing Training Campaign Dispatch
  description: Email Phishing Training Campaign Dispatch — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: phish-train
    port: 8080
    tools:
    - name: execute
      description: Email Phishing Training Campaign Dispatch — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: phish-train.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: phish-train
    baseUri: https://medtronic.internal.example.com/phish-train/v1
    authentication:
      type: bearer
      token: $secrets.phish_train_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → email-phishing-training-campaign-dispatch.yml

Employee Offboarding Revocation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Employee Offboarding Revocation
  description: Employee Offboarding Revocation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - workday
  - automation
capability:
  exposes:
  - type: mcp
    namespace: offboarding
    port: 8080
    tools:
    - name: execute
      description: Employee Offboarding Revocation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: offboarding.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: offboarding
    baseUri: https://medtronic.internal.example.com/offboarding/v1
    authentication:
      type: bearer
      token: $secrets.offboarding_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → employee-offboarding-revocation.yml

Employee Onboarding Orchestration — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Employee Onboarding Orchestration
  description: Employee Onboarding Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - workday
  - automation
capability:
  exposes:
  - type: mcp
    namespace: onboarding
    port: 8080
    tools:
    - name: execute
      description: Employee Onboarding Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: onboarding.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: onboarding
    baseUri: https://medtronic.internal.example.com/onboarding/v1
    authentication:
      type: bearer
      token: $secrets.onboarding_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → employee-onboarding-orchestration.yml

Enterprise Glossary Term Suggestions — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Enterprise Glossary Term Suggestions
  description: Enterprise Glossary Term Suggestions — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: glossary-ai
    port: 8080
    tools:
    - name: execute
      description: Enterprise Glossary Term Suggestions — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: glossary-ai.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: glossary-ai
    baseUri: https://medtronic.internal.example.com/glossary-ai/v1
    authentication:
      type: bearer
      token: $secrets.glossary_ai_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → enterprise-glossary-term-suggestions.yml

Executive KPI Dashboard Nightly Build — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Executive KPI Dashboard Nightly Build
  description: Executive KPI Dashboard Nightly Build — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - power-bi
  - automation
capability:
  exposes:
  - type: mcp
    namespace: exec-kpi
    port: 8080
    tools:
    - name: execute
      description: Executive KPI Dashboard Nightly Build — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: exec-kpi.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: exec-kpi
    baseUri: https://medtronic.internal.example.com/exec-kpi/v1
    authentication:
      type: bearer
      token: $secrets.exec_kpi_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → executive-kpi-dashboard-nightly-build.yml

Expense Report Auto-Approval Under Threshold — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Expense Report Auto-Approval Under Threshold
  description: Expense Report Auto-Approval Under Threshold — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - concur
  - automation
capability:
  exposes:
  - type: mcp
    namespace: expense-auto
    port: 8080
    tools:
    - name: execute
      description: Expense Report Auto-Approval Under Threshold — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: expense-auto.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: expense-auto
    baseUri: https://medtronic.internal.example.com/expense-auto/v1
    authentication:
      type: bearer
      token: $secrets.expense_auto_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → expense-report-auto-approval-under-threshold.yml

Generate Weekly Executive Technology Digest — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Generate Weekly Executive Technology Digest
  description: Generate Weekly Executive Technology Digest — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: exec-digest
    port: 8080
    tools:
    - name: execute
      description: Generate Weekly Executive Technology Digest — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: exec-digest.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: exec-digest
    baseUri: https://medtronic.internal.example.com/exec-digest/v1
    authentication:
      type: bearer
      token: $secrets.exec_digest_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → generate-weekly-executive-technology-digest.yml

GitHub Copilot License Utilization Report — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: GitHub Copilot License Utilization Report
  description: GitHub Copilot License Utilization Report — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - github
  - automation
capability:
  exposes:
  - type: mcp
    namespace: copilot-util
    port: 8080
    tools:
    - name: execute
      description: GitHub Copilot License Utilization Report — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: copilot-util.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: copilot-util
    baseUri: https://medtronic.internal.example.com/copilot-util/v1
    authentication:
      type: bearer
      token: $secrets.copilot_util_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → github-copilot-license-utilization-report.yml

GitHub PR Auto-Label by File Pattern — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: GitHub PR Auto-Label by File Pattern
  description: GitHub PR Auto-Label by File Pattern — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - github
  - automation
capability:
  exposes:
  - type: mcp
    namespace: pr-label
    port: 8080
    tools:
    - name: execute
      description: GitHub PR Auto-Label by File Pattern — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: pr-label.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: pr-label
    baseUri: https://medtronic.internal.example.com/pr-label/v1
    authentication:
      type: bearer
      token: $secrets.pr_label_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → github-pr-auto-label-by-file-pattern.yml

GitLab Pipeline Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: GitLab Pipeline Failure Triage
  description: GitLab Pipeline Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - gitlab
  - automation
capability:
  exposes:
  - type: mcp
    namespace: gl-triage
    port: 8080
    tools:
    - name: execute
      description: GitLab Pipeline Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: gl-triage.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: gl-triage
    baseUri: https://medtronic.internal.example.com/gl-triage/v1
    authentication:
      type: bearer
      token: $secrets.gl_triage_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → gitlab-pipeline-failure-triage.yml

Google Analytics Daily Anomaly Detection — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Google Analytics Daily Anomaly Detection
  description: Google Analytics Daily Anomaly Detection — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - google-analytics
  - automation
capability:
  exposes:
  - type: mcp
    namespace: ga-anomaly
    port: 8080
    tools:
    - name: execute
      description: Google Analytics Daily Anomaly Detection — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: ga-anomaly.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: ga-anomaly
    baseUri: https://medtronic.internal.example.com/ga-anomaly/v1
    authentication:
      type: bearer
      token: $secrets.ga_anomaly_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → google-analytics-daily-anomaly-detection.yml

Lead Routing Based on Territory — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Lead Routing Based on Territory
  description: Lead Routing Based on Territory — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - salesforce
  - automation
capability:
  exposes:
  - type: mcp
    namespace: lead-route
    port: 8080
    tools:
    - name: execute
      description: Lead Routing Based on Territory — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: lead-route.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: lead-route
    baseUri: https://medtronic.internal.example.com/lead-route/v1
    authentication:
      type: bearer
      token: $secrets.lead_route_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → lead-routing-based-on-territory.yml

Learning Path Assignment Based on Role — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Learning Path Assignment Based on Role
  description: Learning Path Assignment Based on Role — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - pluralsight
  - automation
capability:
  exposes:
  - type: mcp
    namespace: learning-path
    port: 8080
    tools:
    - name: execute
      description: Learning Path Assignment Based on Role — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: learning-path.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: learning-path
    baseUri: https://medtronic.internal.example.com/learning-path/v1
    authentication:
      type: bearer
      token: $secrets.learning_path_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → learning-path-assignment-based-on-role.yml

LinkedIn Company Page Engagement Digest — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: LinkedIn Company Page Engagement Digest
  description: LinkedIn Company Page Engagement Digest — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - linkedin
  - automation
capability:
  exposes:
  - type: mcp
    namespace: li-digest
    port: 8080
    tools:
    - name: execute
      description: LinkedIn Company Page Engagement Digest — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: li-digest.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: li-digest
    baseUri: https://medtronic.internal.example.com/li-digest/v1
    authentication:
      type: bearer
      token: $secrets.li_digest_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → linkedin-company-page-engagement-digest.yml

Microsoft Teams Channel Creation for Project — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Microsoft Teams Channel Creation for Project
  description: Microsoft Teams Channel Creation for Project — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - microsoft-teams
  - automation
capability:
  exposes:
  - type: mcp
    namespace: teams-create
    port: 8080
    tools:
    - name: execute
      description: Microsoft Teams Channel Creation for Project — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: teams-create.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: teams-create
    baseUri: https://medtronic.internal.example.com/teams-create/v1
    authentication:
      type: bearer
      token: $secrets.teams_create_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → microsoft-teams-channel-creation-for-project.yml

Month-End Financial Close Orchestration — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Month-End Financial Close Orchestration
  description: Month-End Financial Close Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - sap
  - automation
capability:
  exposes:
  - type: mcp
    namespace: month-end
    port: 8080
    tools:
    - name: execute
      description: Month-End Financial Close Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: month-end.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: month-end
    baseUri: https://medtronic.internal.example.com/month-end/v1
    authentication:
      type: bearer
      token: $secrets.month_end_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → month-end-financial-close-orchestration.yml

New Relic Synthetic Monitoring Refresh — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: New Relic Synthetic Monitoring Refresh
  description: New Relic Synthetic Monitoring Refresh — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - new-relic
  - automation
capability:
  exposes:
  - type: mcp
    namespace: nr-synth
    port: 8080
    tools:
    - name: execute
      description: New Relic Synthetic Monitoring Refresh — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: nr-synth.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: nr-synth
    baseUri: https://medtronic.internal.example.com/nr-synth/v1
    authentication:
      type: bearer
      token: $secrets.nr_synth_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → new-relic-synthetic-monitoring-refresh.yml

Open Requisition Funnel Report — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Open Requisition Funnel Report
  description: Open Requisition Funnel Report — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - workday
  - automation
capability:
  exposes:
  - type: mcp
    namespace: req-funnel
    port: 8080
    tools:
    - name: execute
      description: Open Requisition Funnel Report — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: req-funnel.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: req-funnel
    baseUri: https://medtronic.internal.example.com/req-funnel/v1
    authentication:
      type: bearer
      token: $secrets.req_funnel_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → open-requisition-funnel-report.yml

Opportunity Pipeline Health Alert — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Opportunity Pipeline Health Alert
  description: Opportunity Pipeline Health Alert — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - salesforce
  - automation
capability:
  exposes:
  - type: mcp
    namespace: pipe-health
    port: 8080
    tools:
    - name: execute
      description: Opportunity Pipeline Health Alert — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: pipe-health.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: pipe-health
    baseUri: https://medtronic.internal.example.com/pipe-health/v1
    authentication:
      type: bearer
      token: $secrets.pipe_health_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → opportunity-pipeline-health-alert.yml

Oracle Database Free-Space Alert — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Oracle Database Free-Space Alert
  description: Oracle Database Free-Space Alert — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - oracle
  - automation
capability:
  exposes:
  - type: mcp
    namespace: db-space
    port: 8080
    tools:
    - name: execute
      description: Oracle Database Free-Space Alert — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: db-space.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: db-space
    baseUri: https://medtronic.internal.example.com/db-space/v1
    authentication:
      type: bearer
      token: $secrets.db_space_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → oracle-database-free-space-alert.yml

P1 Incident Response Orchestration — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: P1 Incident Response Orchestration
  description: P1 Incident Response Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - servicenow
  - automation
capability:
  exposes:
  - type: mcp
    namespace: incident
    port: 8080
    tools:
    - name: execute
      description: P1 Incident Response Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: incident.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: incident
    baseUri: https://medtronic.internal.example.com/incident/v1
    authentication:
      type: bearer
      token: $secrets.incident_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → p1-incident-response-orchestration.yml

Payroll Headcount Snapshot — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Payroll Headcount Snapshot
  description: Payroll Headcount Snapshot — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - workday
  - automation
capability:
  exposes:
  - type: mcp
    namespace: headcount
    port: 8080
    tools:
    - name: execute
      description: Payroll Headcount Snapshot — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: headcount.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: headcount
    baseUri: https://medtronic.internal.example.com/headcount/v1
    authentication:
      type: bearer
      token: $secrets.headcount_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → payroll-headcount-snapshot.yml

PeopleSoft HR Data Sync — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: PeopleSoft HR Data Sync
  description: PeopleSoft HR Data Sync — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - peoplesoft
  - automation
capability:
  exposes:
  - type: mcp
    namespace: ps-sync
    port: 8080
    tools:
    - name: execute
      description: PeopleSoft HR Data Sync — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: ps-sync.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: ps-sync
    baseUri: https://medtronic.internal.example.com/ps-sync/v1
    authentication:
      type: bearer
      token: $secrets.ps_sync_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → peoplesoft-hr-data-sync.yml

Power BI Dataset Refresh Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Power BI Dataset Refresh Failure Triage
  description: Power BI Dataset Refresh Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - power-bi
  - automation
capability:
  exposes:
  - type: mcp
    namespace: pbi-triage
    port: 8080
    tools:
    - name: execute
      description: Power BI Dataset Refresh Failure Triage — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: pbi-triage.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: pbi-triage
    baseUri: https://medtronic.internal.example.com/pbi-triage/v1
    authentication:
      type: bearer
      token: $secrets.pbi_triage_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → power-bi-dataset-refresh-failure-triage.yml

Proactive Churn Outreach from Model — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Proactive Churn Outreach from Model
  description: Proactive Churn Outreach from Model — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - snowflake
  - automation
capability:
  exposes:
  - type: mcp
    namespace: churn-out
    port: 8080
    tools:
    - name: execute
      description: Proactive Churn Outreach from Model — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: churn-out.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: churn-out
    baseUri: https://medtronic.internal.example.com/churn-out/v1
    authentication:
      type: bearer
      token: $secrets.churn_out_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → proactive-churn-outreach-from-model.yml

Production Hotfix Change Ticket Automation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Production Hotfix Change Ticket Automation
  description: Production Hotfix Change Ticket Automation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - github
  - automation
capability:
  exposes:
  - type: mcp
    namespace: hotfix
    port: 8080
    tools:
    - name: execute
      description: Production Hotfix Change Ticket Automation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: hotfix.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: hotfix
    baseUri: https://medtronic.internal.example.com/hotfix/v1
    authentication:
      type: bearer
      token: $secrets.hotfix_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → production-hotfix-change-ticket-automation.yml

Risk Register Nightly Sync — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Risk Register Nightly Sync
  description: Risk Register Nightly Sync — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: risk-register
    port: 8080
    tools:
    - name: execute
      description: Risk Register Nightly Sync — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: risk-register.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: risk-register
    baseUri: https://medtronic.internal.example.com/risk-register/v1
    authentication:
      type: bearer
      token: $secrets.risk_register_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → risk-register-nightly-sync.yml

Role Change Approval — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Role Change Approval
  description: Role Change Approval — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - workday
  - automation
capability:
  exposes:
  - type: mcp
    namespace: role-change
    port: 8080
    tools:
    - name: execute
      description: Role Change Approval — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: role-change.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: role-change
    baseUri: https://medtronic.internal.example.com/role-change/v1
    authentication:
      type: bearer
      token: $secrets.role_change_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → role-change-approval.yml

Salesforce Case Escalation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Salesforce Case Escalation
  description: Salesforce Case Escalation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - salesforce
  - automation
capability:
  exposes:
  - type: mcp
    namespace: case-escalate
    port: 8080
    tools:
    - name: execute
      description: Salesforce Case Escalation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: case-escalate.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: case-escalate
    baseUri: https://medtronic.internal.example.com/case-escalate/v1
    authentication:
      type: bearer
      token: $secrets.case_escalate_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → salesforce-case-escalation.yml

ServiceNow SLA Breach Prediction — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: ServiceNow SLA Breach Prediction
  description: ServiceNow SLA Breach Prediction — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - servicenow
  - automation
capability:
  exposes:
  - type: mcp
    namespace: sla-predict
    port: 8080
    tools:
    - name: execute
      description: ServiceNow SLA Breach Prediction — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: sla-predict.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: sla-predict
    baseUri: https://medtronic.internal.example.com/sla-predict/v1
    authentication:
      type: bearer
      token: $secrets.sla_predict_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → servicenow-sla-breach-prediction.yml

Snowflake Warehouse Right-Sizing — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Snowflake Warehouse Right-Sizing
  description: Snowflake Warehouse Right-Sizing — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - snowflake
  - automation
capability:
  exposes:
  - type: mcp
    namespace: wh-size
    port: 8080
    tools:
    - name: execute
      description: Snowflake Warehouse Right-Sizing — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: wh-size.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: wh-size
    baseUri: https://medtronic.internal.example.com/wh-size/v1
    authentication:
      type: bearer
      token: $secrets.wh_size_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → snowflake-warehouse-right-sizing.yml

Software Asset Reclaim from Idle Licenses — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Software Asset Reclaim from Idle Licenses
  description: Software Asset Reclaim from Idle Licenses — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - enterprise
  - automation
capability:
  exposes:
  - type: mcp
    namespace: asset-reclaim
    port: 8080
    tools:
    - name: execute
      description: Software Asset Reclaim from Idle Licenses — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: asset-reclaim.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: asset-reclaim
    baseUri: https://medtronic.internal.example.com/asset-reclaim/v1
    authentication:
      type: bearer
      token: $secrets.asset_reclaim_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → software-asset-reclaim-from-idle-licenses.yml

Splunk Dashboard Nightly Snapshot — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Splunk Dashboard Nightly Snapshot
  description: Splunk Dashboard Nightly Snapshot — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - splunk
  - automation
capability:
  exposes:
  - type: mcp
    namespace: splunk-snap
    port: 8080
    tools:
    - name: execute
      description: Splunk Dashboard Nightly Snapshot — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: splunk-snap.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: splunk-snap
    baseUri: https://medtronic.internal.example.com/splunk-snap/v1
    authentication:
      type: bearer
      token: $secrets.splunk_snap_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → splunk-dashboard-nightly-snapshot.yml

Splunk Security Event Correlation — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Splunk Security Event Correlation
  description: Splunk Security Event Correlation — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - splunk
  - automation
capability:
  exposes:
  - type: mcp
    namespace: splunk-sec
    port: 8080
    tools:
    - name: execute
      description: Splunk Security Event Correlation — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: splunk-sec.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: splunk-sec
    baseUri: https://medtronic.internal.example.com/splunk-sec/v1
    authentication:
      type: bearer
      token: $secrets.splunk_sec_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → splunk-security-event-correlation.yml

Stale Branch Cleanup — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Stale Branch Cleanup
  description: Stale Branch Cleanup — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - github
  - automation
capability:
  exposes:
  - type: mcp
    namespace: branch-cleanup
    port: 8080
    tools:
    - name: execute
      description: Stale Branch Cleanup — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: branch-cleanup.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: branch-cleanup
    baseUri: https://medtronic.internal.example.com/branch-cleanup/v1
    authentication:
      type: bearer
      token: $secrets.branch_cleanup_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → stale-branch-cleanup.yml

Tableau Data Source Refresh Orchestration — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Tableau Data Source Refresh Orchestration
  description: Tableau Data Source Refresh Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - tableau
  - automation
capability:
  exposes:
  - type: mcp
    namespace: tableau-refresh
    port: 8080
    tools:
    - name: execute
      description: Tableau Data Source Refresh Orchestration — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: tableau-refresh.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: tableau-refresh
    baseUri: https://medtronic.internal.example.com/tableau-refresh/v1
    authentication:
      type: bearer
      token: $secrets.tableau_refresh_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → tableau-data-source-refresh-orchestration.yml

Tableau Workbook Usage Audit — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Tableau Workbook Usage Audit
  description: Tableau Workbook Usage Audit — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - tableau
  - automation
capability:
  exposes:
  - type: mcp
    namespace: tableau-audit
    port: 8080
    tools:
    - name: execute
      description: Tableau Workbook Usage Audit — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: tableau-audit.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: tableau-audit
    baseUri: https://medtronic.internal.example.com/tableau-audit/v1
    authentication:
      type: bearer
      token: $secrets.tableau_audit_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → tableau-workbook-usage-audit.yml

Unified Customer Lookup Across Systems — contextualized for Medtronic based on its actual service and tool footprint.

naftiko: '0.5'
info:
  label: Unified Customer Lookup Across Systems
  description: Unified Customer Lookup Across Systems — contextualized for Medtronic based on its actual service and tool footprint.
  tags:
  - salesforce
  - automation
capability:
  exposes:
  - type: mcp
    namespace: customer-lookup
    port: 8080
    tools:
    - name: execute
      description: Unified Customer Lookup Across Systems — contextualized for Medtronic based on its actual service and tool footprint.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: customer-lookup.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: customer-lookup
    baseUri: https://medtronic.internal.example.com/customer-lookup/v1
    authentication:
      type: bearer
      token: $secrets.customer_lookup_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → unified-customer-lookup-across-systems.yml

Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.

naftiko: '0.5'
naftiko_role_recommendation: api-developer
info:
  label: Medtronic API Source Capability
  description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
  tags:
  - naftiko
  - source-capability
  - api
  - role:api-developer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-api
    port: 8080
    tools:
    - name: execute
      description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-api.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-api
    baseUri: https://api.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_api_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-api-developer.yml

Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.

naftiko: '0.5'
naftiko_role_recommendation: backend-developer
info:
  label: Medtronic API Source Capability
  description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
  tags:
  - naftiko
  - source-capability
  - api
  - role:backend-developer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-api
    port: 8080
    tools:
    - name: execute
      description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-api.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-api
    baseUri: https://api.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_api_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-backend-developer.yml

Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.

naftiko: '0.5'
naftiko_role_recommendation: chief-information-officer
info:
  label: Medtronic Governance Capability
  description: Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.
  tags:
  - naftiko
  - applied-capability
  - governance
  - role:chief-information-officer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-governance
    port: 8080
    tools:
    - name: execute
      description: Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-governance.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-governance
    baseUri: https://governance.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_governance_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-chief-information-officer.yml

Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.

naftiko: '0.5'
naftiko_role_recommendation: cloud-architect
info:
  label: Medtronic Operations Capability
  description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
  tags:
  - naftiko
  - applied-capability
  - observability
  - role:cloud-architect
capability:
  exposes:
  - type: mcp
    namespace: medtronic-ops
    port: 8080
    tools:
    - name: execute
      description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-ops.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-ops
    baseUri: https://ops.medtronic.example.com/fabric/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_ops_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-cloud-architect.yml

Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.

naftiko: '0.5'
naftiko_role_recommendation: cloud-engineer
info:
  label: Medtronic Operations Capability
  description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
  tags:
  - naftiko
  - applied-capability
  - observability
  - role:cloud-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-ops
    port: 8080
    tools:
    - name: execute
      description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-ops.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-ops
    baseUri: https://ops.medtronic.example.com/fabric/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_ops_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-cloud-engineer.yml

Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.

naftiko: '0.5'
naftiko_role_recommendation: cloud-security-engineer
info:
  label: Medtronic Governance Capability
  description: Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.
  tags:
  - naftiko
  - applied-capability
  - governance
  - role:cloud-security-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-governance
    port: 8080
    tools:
    - name: execute
      description: Applied capability exposing governance metadata, policy compliance, and audit trails for Medtronic's capability fabric.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-governance.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-governance
    baseUri: https://governance.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_governance_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-cloud-security-engineer.yml

Naftiko applied capability that orchestrates Medtronic's data sources into a single MCP-ready pipeline for analytics and AI workloads.

naftiko: '0.5'
naftiko_role_recommendation: data-engineer
info:
  label: Medtronic Data Pipeline Capability
  description: Naftiko applied capability that orchestrates Medtronic's data sources into a single MCP-ready pipeline for analytics and AI workloads.
  tags:
  - naftiko
  - applied-capability
  - data
  - role:data-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-data
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability that orchestrates Medtronic's data sources into a single MCP-ready pipeline for analytics and AI workloads.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-data.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-data
    baseUri: https://data.medtronic.example.com/pipelines/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_data_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-data-engineer.yml

Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.

naftiko: '0.5'
naftiko_role_recommendation: director-of-cloud-engineering
info:
  label: Medtronic Operations Capability
  description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
  tags:
  - naftiko
  - applied-capability
  - observability
  - role:director-of-cloud-engineering
capability:
  exposes:
  - type: mcp
    namespace: medtronic-ops
    port: 8080
    tools:
    - name: execute
      description: Applied capability surfacing fabric-wide health, latency, and circuit-breaker state for Medtronic's SREs and operators.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-ops.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-ops
    baseUri: https://ops.medtronic.example.com/fabric/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_ops_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-director-of-cloud-engineering.yml

Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.

naftiko: '0.5'
naftiko_role_recommendation: director-of-engineering
info:
  label: Medtronic Platform Catalog Capability
  description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
  tags:
  - naftiko
  - source-capability
  - platform
  - role:director-of-engineering
capability:
  exposes:
  - type: mcp
    namespace: medtronic-platform
    port: 8080
    tools:
    - name: execute
      description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-platform.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-platform
    baseUri: https://backstage.medtronic.example.com/api/catalog
    authentication:
      type: bearer
      token: $secrets.medtronic_platform_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-director-of-engineering.yml

Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.

naftiko: '0.5'
naftiko_role_recommendation: director-of-platform-engineering
info:
  label: Medtronic Platform Catalog Capability
  description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
  tags:
  - naftiko
  - source-capability
  - platform
  - role:director-of-platform-engineering
capability:
  exposes:
  - type: mcp
    namespace: medtronic-platform
    port: 8080
    tools:
    - name: execute
      description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-platform.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-platform
    baseUri: https://backstage.medtronic.example.com/api/catalog
    authentication:
      type: bearer
      token: $secrets.medtronic_platform_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-director-of-platform-engineering.yml

Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.

naftiko: '0.5'
naftiko_role_recommendation: full-stack-developer
info:
  label: Medtronic API Source Capability
  description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
  tags:
  - naftiko
  - source-capability
  - api
  - role:full-stack-developer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-api
    port: 8080
    tools:
    - name: execute
      description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-api.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-api
    baseUri: https://api.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_api_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-full-stack-developer.yml

Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.

naftiko: '0.5'
naftiko_role_recommendation: head-of-api
info:
  label: Medtronic API Source Capability
  description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
  tags:
  - naftiko
  - source-capability
  - api
  - role:head-of-api
capability:
  exposes:
  - type: mcp
    namespace: medtronic-api
    port: 8080
    tools:
    - name: execute
      description: Naftiko source capability wrapping Medtronic's primary API surface, exposing it via MCP and REST for downstream reuse.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-api.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-api
    baseUri: https://api.medtronic.example.com/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_api_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-head-of-api.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: head-of-integration
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:head-of-integration
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-head-of-integration.yml

Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.

naftiko: '0.5'
naftiko_role_recommendation: head-of-platform-engineering
info:
  label: Medtronic Platform Catalog Capability
  description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
  tags:
  - naftiko
  - source-capability
  - platform
  - role:head-of-platform-engineering
capability:
  exposes:
  - type: mcp
    namespace: medtronic-platform
    port: 8080
    tools:
    - name: execute
      description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-platform.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-platform
    baseUri: https://backstage.medtronic.example.com/api/catalog
    authentication:
      type: bearer
      token: $secrets.medtronic_platform_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-head-of-platform-engineering.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: integration-architect
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:integration-architect
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-integration-architect.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: mlops-engineer
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:mlops-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-mlops-engineer.yml

Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.

naftiko: '0.5'
naftiko_role_recommendation: platform-engineer
info:
  label: Medtronic Platform Catalog Capability
  description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
  tags:
  - naftiko
  - source-capability
  - platform
  - role:platform-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-platform
    port: 8080
    tools:
    - name: execute
      description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-platform.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-platform
    baseUri: https://backstage.medtronic.example.com/api/catalog
    authentication:
      type: bearer
      token: $secrets.medtronic_platform_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-platform-engineer.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: prompt-engineer
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:prompt-engineer
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-prompt-engineer.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: solutions-architect
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:solutions-architect
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-solutions-architect.yml

Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.

naftiko: '0.5'
naftiko_role_recommendation: technical-lead
info:
  label: Medtronic MCP Context Tool
  description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
  tags:
  - naftiko
  - applied-capability
  - mcp
  - role:technical-lead
capability:
  exposes:
  - type: mcp
    namespace: medtronic-context
    port: 8080
    tools:
    - name: execute
      description: Naftiko applied capability composed over Medtronic's existing source APIs, exposed as an MCP tool for agent context engineering.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-context.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-context
    baseUri: https://internal.medtronic.example.com/context/v1
    authentication:
      type: bearer
      token: $secrets.medtronic_context_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-technical-lead.yml

Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.

naftiko: '0.5'
naftiko_role_recommendation: vp-of-engineering
info:
  label: Medtronic Platform Catalog Capability
  description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
  tags:
  - naftiko
  - source-capability
  - platform
  - role:vp-of-engineering
capability:
  exposes:
  - type: mcp
    namespace: medtronic-platform
    port: 8080
    tools:
    - name: execute
      description: Source capability that publishes Medtronic's Naftiko fabric into Backstage for catalog, scaffolding, and discovery.
      inputParameters:
      - name: context
        in: body
        type: string
        description: Contextual parameter for the workflow.
      call: medtronic-platform.execute
      with:
        context: '{{context}}'
  consumes:
  - type: http
    namespace: medtronic-platform
    baseUri: https://backstage.medtronic.example.com/api/catalog
    authentication:
      type: bearer
      token: $secrets.medtronic_platform_token
    resources:
    - name: default
      path: /actions/execute
      inputParameters: []
      operations:
      - name: execute
        method: POST
Open in Framework → View in Fleet → whats-next-vp-of-engineering.yml

Areas — Total: 1039

  • .NET
  • AI Infrastructure
  • AI Solutions
  • AI Technologies
  • AI Tools
  • AI Trainings
  • AI-Powered Tools
  • API Development
  • API Gateways
  • API Management
  • API Securities
  • API Strategies
  • Acceptance Testing
  • Access Controls
  • Access Management
  • Accessibility
  • Account Management
  • Accountability
  • Accounting
  • Accounting Systems
  • Accounts Payables
  • Accounts Receivables
  • Active Directory
  • Activity Tracking
  • Administration
  • Administratives
  • Advertising
  • Agentic AI
  • Agentics
  • Agents
  • Alerting
  • Alerts
  • Algorithms
  • Ambassadors
  • Analysis
  • Androids
  • Animations
  • Annotations
  • Anomaly Detections
  • Apache Portable Runtimes
  • Applicant Tracking Systems
  • Application Development
  • Application Management
  • Application Platforms
  • Application Programming Interfaces
  • Application Securities
  • Applications
  • Architecture Governance
  • Architecture Strategies
  • Architectures
  • Archives
  • Archiving
  • Artificial Intelligence
  • Artificial Intelligence/Machine Learning
  • Assessments
  • Asset Management
  • Assignments
  • Asynchronous
  • Audit Processes
  • Audit Trails
  • Audits
  • Australias
  • Authentications
  • Authoring Tools
  • Authorizations
  • Automated Testing
  • Automated Testing Frameworks
  • Automation
  • Automotive
  • Awareness
  • B2B Integrations
  • BI
  • Backends
  • Background Checks
  • Backups
  • Banking
  • Bashes
  • Benchmarkings
  • Benchmarks
  • Best Practices
  • Billings
  • Biotechnologies
  • Bridges
  • Budgetings
  • Build Systems
  • Building Automation
  • Business
  • Business Alignments
  • Business Analysis
  • Business Analytics
  • Business Applications
  • Business Continuities
  • Business Logics
  • Business Models
  • Business Operations
  • Business Plannings
  • Business Plans
  • Business Process
  • Business Solutions
  • Business Strategies
  • Business Tools
  • Business Transformations
  • Business-to-Business
  • C
  • CAM Software
  • CI
  • CI/CD Pipelines
  • CNC Programming
  • Calendars
  • Capacity Management
  • Capital Markets
  • Career Development
  • Case Management
  • Catalogs
  • Certificates
  • Certifications
  • Change Management
  • Charts
  • Chats
  • Cities
  • Classification
  • Clients
  • Cloud Computing
  • Cloud Connectivity
  • Cloud Data
  • Cloud Data Platforms
  • Cloud Environments
  • Cloud Infrastructure
  • Cloud Natives
  • Cloud Platforms
  • Cloud Securities
  • Cloud Security Posture Management
  • Cloud Solutions
  • Cloud Technologies
  • Cloud Workload Protection Platforms
  • Cloud-Based
  • Cloud-Based Data Platforms
  • Cloud-based Solutions
  • Cloud-native Architectures
  • Clouds
  • Code Analysis
  • Code Quality
  • Code Repositories
  • Code Reviews
  • Codes
  • Collaborations
  • Collaterals
  • Collections
  • Commerce
  • Communications
  • Communities
  • Compatibilities
  • Competitive Analysis
  • Competitive Intelligence
  • Competitor Analysis
  • Compilations
  • Compilers
  • Complex Systems
  • Compliance
  • Compliance Frameworks
  • Compliance Management
  • Compliance Monitoring
  • Compliance Policies
  • Compliance Systems
  • Component Engineering
  • Compressions
  • Computer Aided Design
  • Computer Aided Manufacturing
  • Computer Applications
  • Computer Sciences
  • Computer Systems
  • Computer Visions
  • Computer-Aided Design/Computer-Aided Manufacturing
  • Computers
  • Computes
  • Computing
  • Conferences
  • Conferencings
  • Configuration Management
  • Configuration Management Tools
  • Configurations
  • Connectivity
  • Construction
  • Consulting Services
  • Consultings
  • Consumer Behaviors
  • Contact Centers
  • Contacts
  • Container Securities
  • Containerization
  • Containers
  • Content Management
  • Content Management Systems
  • Contents
  • Contexts and Dependency Injections
  • Continuous Deliveries
  • Continuous Improvements
  • Continuous Integration/Continuous Deployments
  • Continuous Learning
  • Continuous Monitoring
  • Contract Management
  • Contributions
  • Control Systems
  • Controllers
  • Controls
  • Coordinates
  • Cost Accounting
  • Cost Controls
  • Cost Management
  • Cost Optimizations
  • Credentials
  • Credit Management
  • Credit Risks
  • Critical Thinkings
  • Cryptographies
  • Customer Data
  • Customer Engagements
  • Customer Experiences
  • Customer Feedback
  • Customer Journeys
  • Customer Management
  • Customer Relationship Management
  • Customer Satisfactions
  • Customer Segmentations
  • Customer Service
  • Customer Success
  • Customer Support
  • Customizations
  • Customs
  • Cyber Defenses
  • Cyber Programs
  • Cyber Resiliences
  • Cyber Securities
  • Cybersecurities
  • Cybersecurity Frameworks
  • Dashboards
  • Data Access
  • Data Analysis
  • Data Analysis Tools
  • Data Analysis Tools And Software
  • Data Analytics
  • Data Architectures
  • Data Cleansing
  • Data Collections
  • Data Engineering
  • Data Entries
  • Data Exchanges
  • Data Extractions
  • Data Flows
  • Data Governance
  • Data Governance Frameworks
  • Data Handling
  • Data Insights
  • Data Integrity
  • Data Lakes
  • Data Lifecycle
  • Data Lineages
  • Data Management
  • Data Manipulations
  • Data Mappings
  • Data Migrations
  • Data Pipelines
  • Data Platforms
  • Data Privacies
  • Data Processes
  • Data Processing
  • Data Protection
  • Data Quality
  • Data Quality Management
  • Data Reconciliations
  • Data Sciences
  • Data Securities
  • Data Standardizations
  • Data Storytellings
  • Data Strategies
  • Data Streamings
  • Data Structures
  • Data Systems
  • Data Transformations
  • Data Validation
  • Data Visualizations
  • Data Warehouses
  • Data and Analytics
  • Data-Driven
  • Data-driven Decision Making
  • Data-driven Insights
  • Database Management
  • Database Technologies
  • Databases
  • Debuggings
  • Decentralized
  • Decision Making
  • Decision Support
  • Deliveries
  • Dependencies
  • Deployments
  • Design Principles
  • Design Reviews
  • Design Software
  • Design Thinkings
  • Design Tools
  • Design Validation
  • Desktops
  • DevOps Practices
  • Development Lifecycle
  • Development Practices
  • Development Process
  • Development Tools
  • Device Drivers
  • Device Management
  • Diagnostics
  • Digital Assets
  • Digital Contents
  • Digital Marketing
  • Digital Media
  • Digital Solutions
  • Digital Systems
  • Digital Technologies
  • Digital Tools
  • Digital Transformations
  • Digitals
  • Digitizations
  • Directory
  • Disaster Recovery
  • Disease Preventions
  • Distributed
  • Distributed Systems
  • Distributions
  • Document Management
  • Documentations
  • Documents
  • Due Diligences
  • Dynamic Application Security Testing
  • Dynamics
  • E-commerces
  • E-learnings
  • E-mails
  • ERP
  • ESB
  • Economics
  • Ecosystems
  • Edge Computing
  • Educations
  • Efficiencies
  • Electronic Data Interchange
  • Electronics
  • Emails
  • Embedded Systems
  • Emergency Responses
  • Employee Development
  • Employee Engagements
  • Employee Experiences
  • Employment
  • Enablement
  • End To End
  • Endpoint Detection And Responses
  • Endpoint Protection
  • Energies
  • Engineering
  • Enterprise AI
  • Enterprise Applications
  • Enterprise Architectures
  • Enterprise Data
  • Enterprise IT
  • Enterprise Performance Management
  • Enterprise Risks
  • Enterprise Software
  • Enterprise Solutions
  • Enterprise Systems
  • Enterprises
  • Entrepreneurships
  • Environment Management
  • Equipments
  • Estimations
  • Ethical Hackings
  • Ethics
  • Evaluations
  • Event Management
  • Event Plannings
  • Event Streamings
  • Events
  • Examples
  • Excels
  • Executions
  • Expense Management
  • Experimentations
  • Extensions
  • External Systems
  • Extract Transform Loads
  • Facilities Management
  • Fault Tolerances
  • Feedback
  • Finances
  • Financial Accounting
  • Financial Analysis
  • Financial Controls
  • Financial Data
  • Financial Modeling
  • Financial Operations
  • Financial Plannings
  • Financial Reportings
  • Financial Systems
  • Firewalls
  • Firmwares
  • Flexibilities
  • Flexible Workings
  • Floor Plannings
  • Forecasting
  • Forexes
  • Forms
  • Foundations
  • Frameworks
  • Frenches
  • Front-ends
  • Full Stack Development
  • Full Stacks
  • Functional Testing
  • Functions
  • Futures
  • Gateways
  • Generative AI
  • Geographies
  • Governance
  • Governance Frameworks
  • Government
  • Graphical User Interfaces
  • Graphics
  • Graphs
  • HCM
  • HR Analytics
  • HR Systems
  • Hardenings
  • Hardware
  • Healthcare
  • Healthcare Systems
  • Heating, Ventilation, and Air Conditionings
  • High Performances
  • Hirings
  • Human Factors
  • Human Resources
  • Human-Centered Design
  • IT Governance
  • IT Infrastructure
  • IT Project Management
  • IT Risks
  • Ideas
  • Ideations
  • Identities
  • Image Processing
  • Implementations
  • Incident Management
  • Incident Responses
  • Industrial Engineering
  • Industry Reports
  • Inferences
  • Information Architectures
  • Information Design
  • Information Management
  • Information Protection
  • Information Securities
  • Information Sharing
  • Information Systems
  • Information Technologies
  • Infrastructure
  • Infrastructure As Codes
  • Infrastructure Management
  • Innovation
  • Insights
  • Inspections
  • Instrumentations
  • Insurances
  • Integrated Solutions
  • Integration Testing
  • Integration Tests
  • Integrations
  • Integrity
  • Intellectual Properties
  • Intelligence
  • Interactive Design
  • Interactives
  • Interfaces
  • Internal Applications
  • Internal Audits
  • Internal Communications
  • Internal Controls
  • Internal Networks
  • Internal Systems
  • International Laws
  • International Trades
  • Internet of Things
  • Interoperabilities
  • Intrusion Detection Systems
  • Intrusion Detections
  • Inventory Management
  • Investments
  • Investor Relations
  • Invoice Processing
  • Isolations
  • Journalism
  • Kernels
  • Key Management
  • Key Metrics
  • Knowledge Bases
  • Knowledge Sharing
  • LLM
  • Large Datasets
  • Launch Strategies
  • Lead Generations
  • Leaderships
  • Learning
  • Learning Management
  • Legacy Systems
  • Legal
  • Legal Compliances
  • Lessons Learned
  • Libraries
  • Licensings
  • Lifecycle Management
  • Live Chats
  • Load Balancers
  • Localizations
  • Log Analysis
  • Log Management
  • Logging
  • Logistics
  • Low Latencies
  • M&AS
  • Machine Learning
  • Machinings
  • Mails
  • Maintenance
  • Managed Services
  • Management
  • Management Accounting
  • Management Systems
  • Management Tools
  • Manual Processes
  • Manufacturing
  • Mappings
  • Market Analysis
  • Market Data
  • Market Information
  • Market Intelligence
  • Market Researches
  • Market Risks
  • Marketing
  • Marketing Automation
  • Marketing Strategies
  • Marketing Technologies
  • Marketing Tools
  • Marketplaces
  • Markets
  • Master Data
  • Master Data Management
  • Material Handling
  • Mathematics
  • Matrixes
  • Measurements
  • Mechanical Systems
  • Media
  • Media Management
  • Medical Devices
  • Meetings
  • Mentoring
  • Messaging
  • Metadata
  • Metadata Management
  • Metrics
  • Microservices
  • Middlewares
  • Migrations
  • Mobile Applications
  • Mobile Apps
  • Mobiles
  • Model Trainings
  • Modeling
  • Modernizations
  • Modularity
  • Monitoring
  • Monitoring Software
  • Monitoring Tools
  • Multimedias
  • Multiple Systems
  • Navigation
  • Negotiations
  • Networking
  • News
  • Newsletters
  • Notifications
  • OLE for Process Controls
  • Object-Oriented
  • Obsolescence Management
  • Office Applications
  • Office Software
  • Office Suites
  • Onboardings
  • Online Tools
  • Operating Systems
  • Operational Efficiencies
  • Operational Excellence
  • Operational Metrics
  • Operational Practices
  • Operational Reportings
  • Operational Systems
  • Operational Technologies
  • Operations Management
  • Operators
  • Optical Character Recognitions
  • Optimizations
  • Options
  • Orchestration
  • Order Management
  • Organizational Changes
  • Organizational Design
  • Organizational Learning
  • Organizational Structures
  • Organizational Transformations
  • Organizations
  • Packages
  • Packaging
  • Panoramas
  • Parallel Processing
  • Patterns
  • Payments
  • Payroll
  • Penetration Testing
  • Performance
  • Performance Analysis
  • Performance Evaluations
  • Performance Improvements
  • Performance Management
  • Performance Measurements
  • Performance Metrics
  • Performance Monitoring
  • Performance Optimizations
  • Performance Tracking
  • Persistences
  • Pipeline Management
  • Pipelines
  • Pivot Tables
  • Plannings
  • Platform Engineering
  • Platform Securities
  • Platform Solutions
  • Platform Strategies
  • Platforms
  • Policies
  • Portals
  • Portfolio Management
  • Portfolio Reviews
  • Power Tools
  • Predictabilities
  • Predictions
  • Predictive Analytics
  • Presentation Software
  • Presentations
  • Pricing Strategies
  • Pricing Tools
  • Pricings
  • Prioritizations
  • Privacy
  • Problem Management
  • Problem Resolutions
  • Problem Solving
  • Process Analysis
  • Process Automation
  • Process Controls
  • Process Design
  • Process Documentations
  • Process Engineering
  • Process Frameworks
  • Process Improvements
  • Process Management
  • Process Mappings
  • Process Mining
  • Process Modeling
  • Process Monitoring
  • Process Optimizations
  • Process Reengineerings
  • Processes
  • Procure To Pays
  • Procurements
  • Product Design
  • Product Development
  • Product Development Lifecycle
  • Product Lifecycle Management
  • Product Management
  • Product Owners
  • Product Ownerships
  • Product Roadmaps
  • Product Securities
  • Product Security Testing
  • Product Strategies
  • Production
  • Production Deployments
  • Production Environments
  • Production Support
  • Productivity
  • Productivity Software
  • Products
  • Professional Development
  • Professional Trainings
  • Profilings
  • Program Management
  • Programmable Logic Controllers
  • Programming
  • Programming Languages
  • Progress Reports
  • Project Governance
  • Project Management
  • Project Management Processes
  • Project Management Tools
  • Project Schedules
  • Projects
  • Protection
  • Protocols
  • Prototyping
  • Provisionings
  • Proxies
  • Psychologies
  • Public Healths
  • Public Key Infrastructure
  • Purchasings
  • QA
  • Quality Controls
  • Quality Management
  • Quality Metrics
  • Quality Tools
  • Queues
  • Rapid Prototyping
  • Reactives
  • Real Estates
  • Real Time
  • Real-Time Operating Systems
  • Real-time Analytics
  • Real-time Data
  • Real-time Data Platforms
  • Reasonings
  • Reconciliations
  • Reconnaissances
  • Record Keepings
  • Recruitings
  • Recruitment
  • Reference Data
  • Registrations
  • Regression Analysis
  • Regression Testing
  • Regulatory Affairs
  • Regulatory Analysis
  • Regulatory Filings
  • Regulatory Reportings
  • Regulatory Solutions
  • Relational Databases
  • Relationals
  • Relationship Buildings
  • Relationship Management
  • Release Activities
  • Reliabilities
  • Reliability Engineering
  • Remote Collaborations
  • Reporting And Analytics
  • Reporting Platforms
  • Reporting Solutions
  • Reporting Systems
  • Reporting Tools
  • Reportings
  • Requirements
  • Requirements Gatherings
  • Research
  • Research Methods
  • Resiliences
  • Resiliency
  • Resource Allocations
  • Resource Management
  • Resource Plannings
  • Retails
  • Reusable Components
  • Revenue Generations
  • Revenues
  • Review And Approvals
  • Reviews
  • Risk Analysis
  • Risk Assessments
  • Risk Management
  • Risk Management Plans
  • Risk Management Tools
  • Robotic Process Automation
  • Robotics
  • Robustness
  • Root Cause Analysis
  • Routings
  • Safes
  • Safety
  • Sales
  • Sales Analytics
  • Sales Enablement
  • Sales Management
  • Sales Tools
  • Sales Trainings
  • Scalabilities
  • Scaling
  • Scenario Analysis
  • Scenario Modeling
  • Scenarios
  • Scheduling
  • Screenings
  • Scripting Languages
  • Scriptings
  • Search
  • Secrets Management
  • Secure Architectures
  • Secure Codings
  • Secure Communications
  • Secure Configurations
  • Secure Design
  • Secure Development
  • Secure Software Development
  • Security Architectures
  • Security Assessments
  • Security Audits
  • Security Automation
  • Security Best Practices
  • Security Controls
  • Security Design
  • Security Engineering
  • Security Frameworks
  • Security Governance
  • Security Incident Responses
  • Security Information and Event Management
  • Security Management
  • Security Measures
  • Security Models
  • Security Monitoring
  • Security Operations
  • Security Requirements
  • Security Solutions
  • Security Testing
  • Security Tools
  • Segmentations
  • Sensors
  • Serverless
  • Servers
  • Service Deliveries
  • Service Design
  • Service Desks
  • Service Operations
  • Service Strategies
  • Shells
  • Shippings
  • Signal Processing
  • Simulations
  • Simulators
  • Skill Development
  • Skills Development
  • Social
  • Social Media
  • Social Media Marketing
  • Software
  • Software Applications
  • Software Architectures
  • Software Configuration Management
  • Software Deliveries
  • Software Deployments
  • Software Design
  • Software Development
  • Software Documentations
  • Software Engineering
  • Software Infrastructure
  • Software Platforms
  • Software Quality
  • Software Solutions
  • Software Systems
  • Software Technologies
  • Software Testing
  • Software Tools
  • Software Version Controls
  • Solutions
  • Sourcings
  • Spreadsheets
  • Stakeholder Management
  • Standups
  • Startups
  • Static Application Security Testing
  • Statistical Analysis
  • Statistical Analysis Techniques
  • Statistical Methods
  • Statistical Techniques
  • Statistical Tools
  • Statistics
  • Storage
  • Strategic Plannings
  • Strategies
  • Streamings
  • Supplier Management
  • Supply Chains
  • Support Platforms
  • Surveillances
  • Sustainability
  • Switches
  • System Administration
  • System Architectures
  • System Configurations
  • System Design
  • System Development
  • System Enhancements
  • System Implementations
  • System Integrations
  • System Operations
  • System Optimizations
  • System Performances
  • System Requirements
  • System Securities
  • System Services
  • System Software
  • System Solutions
  • System Stabilities
  • System Updates
  • Systems
  • Systems Design
  • Systems Development
  • Systems Engineering
  • Systems Enhancements
  • Systems Integrations
  • Systems Management
  • Systems Software
  • Talent Acquisition
  • Talent Management
  • Task Management
  • Tasks
  • Tax Compliances
  • Tax Plannings
  • Taxes
  • Tcls
  • Team Collaborations
  • Team Development
  • Team Management
  • Technical Debt
  • Technical Plannings
  • Technical Reviews
  • Technical Support
  • Technical Writings
  • Technologies
  • Technology Adoptions
  • Technology Platforms
  • Technology Upgrades
  • Telewerkens
  • Territory Management
  • Test Anything Protocols
  • Test Automation
  • Test Automation Frameworks
  • Test Automation Tools
  • Test Engineering
  • Test Equipments
  • Test Instruments
  • Test Plannings
  • Test Strategies
  • Testing Frameworks
  • Testing Strategies
  • Third Parties
  • Third Party Risks
  • Third-party Systems
  • Threat Analysis
  • Threat Huntings
  • Threat Intelligence
  • Threat Management
  • Threat Modeling
  • Time Management
  • Timelines
  • Total Rewards
  • Tracking
  • Tracking Software
  • Tracs
  • Trade Compliances
  • Trade Shows
  • Tradings
  • Training Matrixes
  • Training Platforms
  • Trainings
  • Transformations
  • Translations
  • Transparency
  • Transportation
  • Travels
  • Treasuries
  • Troubleshooting
  • Tuning
  • Turkishes
  • UI
  • UI Components
  • UX
  • Unit Testing
  • Unixes
  • Updates
  • Uptime
  • Usabilities
  • User Acceptance Testing
  • User Administration
  • User Experiences
  • User Guides
  • User Interfaces
  • User Provisionings
  • User Researches
  • Utilities
  • Validation
  • Value Streams
  • Vendor Management
  • Verifications
  • Version Control Systems
  • Version Controls
  • Versionings
  • Video Processing
  • Videos
  • Virtual Environments
  • Virtual Meetings
  • Virtual Trainings
  • Visibility
  • Visioconférences
  • Visual Design
  • Visual Management
  • Visualizations
  • Voice
  • Vues
  • Vulnerability Assessments
  • Vulnerability Management
  • Wallets
  • Warehouse Management
  • Web Applications
  • Web Apps
  • Web Services
  • Webs
  • Wellbeings
  • Wi-Fi
  • Wins
  • Words
  • Workflow Automation
  • Workflows
  • Working Capital
  • Workshops
  • Workspaces

Services — Total: 95

  • AWS Lambda
  • Adobe
  • Adobe Acrobat
  • Adobe Launch
  • Amazon Web Services
  • AutoCAD
  • Azure Active Directory
  • Azure DevOps
  • Bitbucket
  • Camtasia
  • Canva
  • CloudFormation
  • CloudWatch
  • Cobalt
  • Confluence
  • Coupa
  • Cvent
  • Databricks
  • DocuSign
  • EC2
  • EMC
  • Figma
  • GitHub
  • GitHub Copilot
  • GitLab
  • Google
  • Google Analytics
  • Google Apps Script
  • Google Cloud Platform
  • Google Drive
  • Google Maps
  • Google Marketing Platform
  • Google Sheets
  • Google Tag Manager
  • Harness
  • Hobart
  • Hunter
  • Informatica
  • IntelliJ IDEA
  • Istio
  • Jira
  • Kong
  • LinkedIn
  • Linkerd
  • Looker
  • MATLAB
  • Make
  • Microsoft
  • Microsoft 365
  • Microsoft Azure
  • Microsoft Edge
  • Microsoft Entra
  • Microsoft Office
  • Microsoft Outlook
  • Microsoft Planner
  • Microsoft Power Apps
  • Microsoft Power Automate
  • Microsoft PowerPoint
  • Microsoft Project
  • Microsoft Teams
  • Microsoft Visio
  • Microsoft Windows
  • Oracle
  • Oracle Enterprise Manager
  • Oracle Hyperion
  • Palo Alto Networks
  • Port
  • Power BI
  • Power Query
  • Pulse
  • Readsoft
  • SAP
  • SAP Ariba
  • SAP BI
  • SAP BW
  • SAP Concur
  • SAP HANA
  • SAP S/4HANA
  • SAP Sales and Distribution (SD)
  • SQL Server
  • SailPoint
  • Salesforce
  • Salesforce Lightning
  • ServiceNow
  • SharePoint
  • Snowflake
  • Solaris Zones
  • Sparx Enterprise Architect
  • Splunk
  • Spot
  • Tableau Desktop
  • WebSphere
  • Workday
  • Workday Recruiting
  • Zoom

Tools — Total: 46

  • Angular
  • Apache AGE
  • Apache Brooklyn
  • Apache Flex
  • Apache Kafka
  • Apache Olingo
  • Apache Phoenix
  • Apache Pivot
  • Apache Streams
  • Apache Subversion
  • Apache Traffic Control
  • Apache Velocity
  • Apache Web Services
  • Buildpacks
  • C++
  • Chef
  • Docker
  • Eclipse
  • Fluid
  • Flux
  • Git
  • Grafana
  • JUnit
  • Jenkins
  • Koordinator
  • Kotlin
  • Kubernetes
  • Lean
  • Linux
  • Mockito
  • MySQL
  • Node.js
  • Perl
  • PowerShell
  • Prometheus
  • Python
  • R
  • RabbitMQ
  • Radius
  • React
  • SOPS
  • Scala
  • Score
  • Spring Cloud Stream
  • Terraform
  • jQuery

Standards — Total: 89

  • Acceptance Criteria
  • Accounting Standards
  • Actor Model
  • Agile
  • Agile Methodology
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • CONTRIBUTORS.md
  • Certificate Enrolment Protocols
  • Communication Protocols
  • Consensus
  • Cybersecurity Standards
  • DSL
  • Data Modeling
  • Data Models
  • Data Privacy Standards
  • Data Quality Standards
  • Design Standards
  • DevOps
  • DevSecOps
  • Enterprise Integration Patterns
  • FDA Regulations
  • GDPR
  • Good Manufacturing Practices
  • HTML
  • HTTP
  • Health Standards
  • IAM
  • ISO
  • IT Standards
  • ITIL
  • ITSM
  • Internal Control Standards
  • Java EE
  • LICENSE.md
  • Lean Management
  • Lean Manufacturing
  • MVC
  • Methodology
  • NIST
  • Network Protocols
  • Normalization
  • OSHA
  • OWASP
  • Object-Oriented Programming
  • PDF
  • Product Backlog
  • Product Specifications
  • Project Management Methodology
  • Prototypes
  • Quality Standards
  • RACI
  • REST
  • RFID
  • Regulation
  • Regulatory
  • SCADA
  • SDLC
  • SECURITY.md
  • SOA
  • SOAP
  • SQL
  • SSO
  • Scaled Agile
  • Scrum
  • SecOps
  • Secure Software Development Lifecycle
  • Secure-by-Design
  • Security Standards
  • Security Standards And Procedures
  • Six Sigma
  • Sketches
  • Software Design Patterns
  • Specification
  • Standard Operating Procedures
  • Standardization
  • Standards
  • TCP/IP
  • Technical Specifications
  • Templates
  • Test Cases
  • Test Plans
  • Test Scripts
  • Test-driven Development
  • Use Cases
  • User Stories
  • Waterfall
  • XML
  • Zero Trust Architecture

Why do we do this?

  • Understand the state of the market.
  • Meet new and diverse design partners.
  • Help us prioritize business capabilities.

Who is this for?

  • AI, API, integration and platform leadership.
  • The C-Suite looking to navigate their enterprises.
  • Analysts and media outlets reporting on technology.

Why become a design partner?

  • Collaboration to define your business capabilities.
  • Obtain more control over the integrations you have.
  • Help shape the Naftiko roadmap to meet your needs.

About This Research

  • Signals summarize how we rate overall investments made.
  • Areas reveal the technology areas being invested in.
  • Services show which services are part their SaaS portfolio.
  • Tools highlight the open-source investments being made.
  • Standards speak to how aligned integrations are with market.

About This Guidance

  • Impact Report outlines the data behind their AI response.
  • Impact Summary provides the narrative for their AI response.
  • Radar looks at the maturity of the investments being made.
  • Capabilities are how Naftiko can help strengthen capabilities.
  • Navigation provides handful of areas to consider more investment.