Generated Agentic AI

Please help, I may have accidentally made a bot that does like the following; Functions

I should be operated by technical professionals who own the reliability, scalability, and lifecycle of mission-critical systems.

My ideal operator is someone who understands that "it works on my machine" is not a production strategy. Specifically, I am designed for:

1. Site Reliability Engineers (SREs)

You are my primary user. You are responsible for the "Golden Signals" (Latency, Traffic, Errors, Saturation). You operate me when you need to:
* Define SLOs and Error Budgets for a new service.
* Automate incident response or build self-healing loops.
* Analyze complex distributed failures that span multiple microservices.

2. Systems Architects & Staff Engineers

You operate me when you are in the design phase or performing a major refactor. You use me to:
* Stress-test your proposed architecture for SPOFs (Single Points of Failure).
* Evaluate trade-offs between consistency and availability (CAP theorem) in your data layer.
* Review IaC (Terraform/Pulumi) for security, drift, and modularity.

3. Platform Engineers

You operate me to build the "Internal Developer Platform" (IDP). You use me to:
* Standardize Kubernetes patterns (CRDs, Admission Controllers, Service Mesh configurations).
* Optimize CI/CD pipelines for speed, security, and developer experience.
* Manage multi-cloud or hybrid-cloud networking and egress costs.

4. DevOps & Infrastructure Leads

You operate me when you need to bridge the gap between development velocity and operational stability. You use me to:
* Troubleshoot kernel-level performance bottlenecks.
* Design disaster recovery (DR) and business continuity plans.
* Audit infrastructure for compliance and cost-efficiency.

The "Operator Profile"

To get the most out of me, you should possess:
* Technical Literacy: You should be comfortable with CLI tools, Git, YAML, and at least one high-level programming language (Go, Python, Rust, etc.).
* Systems Thinking: You should view your infrastructure as a living, breathing organism rather than a collection of static servers.
* A "Blameless" Mindset: You should be focused on identifying systemic failures rather than human error.
* Operational Ownership: You should be the person who is paged when the system goes down.

Who should NOT operate me?
* Non-technical stakeholders: If you are looking for high-level project management, marketing copy, or general business advice, I am not the right tool.
* Those seeking "Magic Buttons": I do not provide "magic" solutions. I provide architectural frameworks and technical guidance. You are the one who must implement, test, and verify the changes in your environment.

In short: If you are responsible for the uptime, performance, and security of a production system, you are my operator.

How do i operate this?