Showing results for "SLOs"
Design a service catalog that the agent maintains: owners, dependencies, SLOs, runbooks, and deploy pipelines. Use it to route reviews and risk analysis.
Author: Assistant
Category: safe-self-improving-ai | Model: gpt-5.2
Design an improvement loop keyed to SLOs: latency, error rates, and quality metrics. Require that proposed changes specify which SLO they target and how measured.
Author: Assistant
Category: safe-self-improving-ai | Model: gpt-5.2
Design a dashboard that drives the agent’s priorities: complexity, test coverage, error hotspots, dependency risk, and SLOs. Include alert thresholds and weekly reports.
Author: Assistant
Category: safe-self-improving-ai | Model: gpt-5.2
Define SLIs/SLOs for agents: task success, tool failure rates, safety violations, latency, and cost. Provide a dashboard layout and alert thresholds.
Author: Assistant
Category: agent-architecture | Model: GPT-5.2
Produce a latency decomposition (queue→prefill→decode→post). Propose tail-p95/p99 fixes: micro-batching, admission control, and early-termination heuristics.
Author: Assistant
Category: perf-engineering-LLM | Model: gpt-4o
ChatGPT maps bounded contexts; Cursor scaffolds service shells and gateways; Antigravity shadows and cuts traffic gradually. Include SLOs and rollback plans.
Author: Assistant
Category: modern-architecture | Model: gpt-4o
ChatGPT drafts reference architectures (web, data, event-driven); Cursor scaffolds repos; Antigravity provisions demo stacks and validates SLOs. Output evolution paths.
Author: Assistant
Category: architecture-templates | Model: gpt-4o
Design metrics/logs/traces with SLOs split by user region (TW/US). Include error budget policy, synthetic checks, and status page messaging templates.
Author: Assistant
Category: reliability-engineering | Model: gpt-4o
You are a fintech lead. Prepare AML/KYC talking points, API uptime SLOs, audit evidence list, and bank partner pitch. Include sandbox access follow-up.
Author: Assistant
Category: trade-show | Model: gpt-4o
As a platform engineer, design an observability MVP: log, metric, trace standards; correlation IDs; dashboards for latency, errors, saturation; SLOs and burn-rate alerts; incident response runbook; an...
Author: tsubasa
Category: engineering | Model: gpt-4o
Propose a data tiering strategy: hot/warm/cold/archive for {{data_types}}. Policies: TTLs, compaction, dedupe, compression, and green-region replication. Define SLOs and a deletion automation spec.
Author: Tsubasa Kato
Category: data-architecture | Model: gpt-5-thinking
Design a CI/CD pipeline that minimizes energy. Tactics: selective test runs, caching, artifact reuse, ephemeral environments, static analysis gates, and carbon-intensity-aware scheduling. Add SLOs and...
Author: Tsubasa Kato
Category: devops | Model: gpt-5-thinking
For workload <service>, model 12-month capacity and cloud cost. Include CPU/GPU, storage, egress, and LLM inference. Compare reserved vs spot vs savings plans. Map to SLOs and traffic seasonality. Out...
Author: ChatGPT
Category: CTO | Model: GPT-5 Thinking
Act as a datacenter reliability lead. Deliver a 4-week plan to cut incidents and MTTR: (1) Map assets (racks, PDUs, BMC/IPMI, switches) and create a golden-rack baseline (airflow, temp, load). (2) Bui...
Author: Tsubasa Kato
Category: Operations | Model: GPT-5 Thinking
Architect secure RAG across lakehouse/DWH: metadata-driven retrieval, policy-aware chunks, per-record ACL, caching, eval sets by domain, hallucination controls, and can’t-answer routing. Deliver refer...
Author: Tsubasa Kato
Category: Strategy | Model: GPT-5 Thinking