@grainulation/silo 1.0.0

package/packs/frontend.json

@@ -0,0 +1,175 @@
+{
+  "name": "Frontend Engineering",
+  "description": "Performance budgets, Core Web Vitals targets, accessibility (WCAG 2.1), state management patterns, bundle optimization, and SSR vs CSR tradeoffs.",
+  "version": "1.0.0",
+  "claims": [
+    {
+      "id": "fe-001",
+      "type": "constraint",
+      "topic": "Core Web Vitals thresholds",
+      "content": "Google Core Web Vitals targets for good UX: LCP (Largest Contentful Paint) under 2.5s, INP (Interaction to Next Paint) under 200ms, CLS (Cumulative Layout Shift) under 0.1. These directly affect search ranking. Measure with field data (CrUX, RUM) not just lab data (Lighthouse), since field p75 is what Google uses.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "performance", "core-web-vitals", "seo"]
+    },
+    {
+      "id": "fe-002",
+      "type": "recommendation",
+      "topic": "JavaScript bundle size budget",
+      "content": "Initial JavaScript bundle should be under 150 KB compressed (gzip) for mobile-first applications. Total page weight including images should be under 1.5 MB. Every 100 KB of JavaScript adds approximately 350ms parse/compile time on median mobile devices. Use bundle analyzer (webpack-bundle-analyzer, source-map-explorer) in CI to enforce budgets.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "tested",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "performance", "bundle-size", "mobile"]
+    },
+    {
+      "id": "fe-003",
+      "type": "constraint",
+      "topic": "WCAG 2.1 AA compliance",
+      "content": "WCAG 2.1 Level AA is the legal standard in the US (ADA), EU (EAA 2025), and Canada (AODA). Key requirements: color contrast ratio 4.5:1 for normal text and 3:1 for large text, all interactive elements keyboard-accessible, form inputs have visible labels, images have alt text, focus indicators visible, no content reliant solely on color.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "accessibility", "wcag", "compliance"]
+    },
+    {
+      "id": "fe-004",
+      "type": "factual",
+      "topic": "SSR vs CSR tradeoffs",
+      "content": "Server-Side Rendering (SSR) provides faster First Contentful Paint and better SEO but increases server load and Time to Interactive (hydration cost). Client-Side Rendering (CSR) has faster subsequent navigations but a blank page until JS loads. Use SSR/SSG for content-heavy, SEO-critical pages; CSR for authenticated app-like interfaces behind login.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "ssr", "csr", "architecture"]
+    },
+    {
+      "id": "fe-005",
+      "type": "risk",
+      "topic": "third-party script performance",
+      "content": "Third-party scripts (analytics, ads, chat widgets) are the leading cause of performance regression. A single poorly-written third-party script can add 500ms-2s to page load. Load all third-party scripts with async or defer. Set performance budgets that include third-party weight. Use a tag manager with server-side option to control loading.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "production",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "performance", "third-party", "scripts"]
+    },
+    {
+      "id": "fe-006",
+      "type": "recommendation",
+      "topic": "image optimization pipeline",
+      "content": "Serve images in WebP or AVIF format (30-50% smaller than JPEG). Use srcset with 2-4 size variants for responsive images. Lazy-load images below the fold with loading='lazy'. Set explicit width and height attributes to prevent CLS. Automate optimization in the build pipeline or use an image CDN (Cloudinary, imgix, Cloudflare Images).",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "tested",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "images", "performance", "webp"]
+    },
+    {
+      "id": "fe-007",
+      "type": "recommendation",
+      "topic": "state management selection criteria",
+      "content": "Use local component state (useState/signals) for UI-only state. Use URL state (query params, path) for shareable/bookmarkable state. Use server state libraries (TanStack Query, SWR) for API data with caching. Use global state (Zustand, Redux, or context) only for truly cross-cutting client state (auth, theme, feature flags). Most applications over-use global state.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "state-management", "react", "architecture"]
+    },
+    {
+      "id": "fe-008",
+      "type": "risk",
+      "topic": "layout shift from web fonts",
+      "content": "Custom web fonts cause either FOIT (Flash of Invisible Text) or FOUT (Flash of Unstyled Text), both contributing to CLS. Mitigate with font-display: swap, preload critical fonts with <link rel='preload'>, subset fonts to used character ranges (Latin subset is ~30 KB vs 200 KB for full Unicode), and use size-adjust to match fallback metrics.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "tested",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "fonts", "cls", "performance"]
+    },
+    {
+      "id": "fe-009",
+      "type": "factual",
+      "topic": "code splitting impact",
+      "content": "Route-based code splitting typically reduces initial bundle size by 40-60%. Dynamic import() splits a module into a separate chunk loaded on demand. For React, use React.lazy() with Suspense boundaries. Split at route boundaries first, then heavy component boundaries (charts, editors, maps). Avoid splitting components under 30 KB as the HTTP overhead negates the benefit.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "tested",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "code-splitting", "bundle-size", "lazy-loading"]
+    },
+    {
+      "id": "fe-010",
+      "type": "constraint",
+      "topic": "keyboard navigation requirements",
+      "content": "Every interactive element must be reachable and operable via keyboard alone. Tab order must follow visual reading order. Focus must be visible (minimum 2px outline, 3:1 contrast ratio against adjacent colors). Custom components (dropdowns, modals, tabs) must implement ARIA roles and keyboard patterns from WAI-ARIA Authoring Practices. Test by unplugging the mouse.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "accessibility", "keyboard", "aria"]
+    },
+    {
+      "id": "fe-011",
+      "type": "estimate",
+      "topic": "mobile performance gap",
+      "content": "Median mobile devices (Moto G Power class) process JavaScript 3-5x slower than desktop. A page that loads in 1.5s on desktop takes 4-6s on median mobile hardware over 4G. Always test on throttled connections (Slow 3G: 400 Kbps, 400ms RTT) and CPU throttled 4x in DevTools. Real user monitoring shows median mobile LCP is 2x desktop LCP.",
+      "source": { "origin": "industry", "artifact": null, "connector": null },
+      "evidence": "web",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "mobile", "performance", "testing"]
+    },
+    {
+      "id": "fe-012",
+      "type": "recommendation",
+      "topic": "error boundaries and fallbacks",
+      "content": "Wrap major UI sections in error boundaries that catch render errors and display a fallback UI instead of a white screen. Log caught errors to your observability stack. Provide a retry mechanism in the fallback. Without error boundaries, a single failing component crashes the entire page. Test error boundaries by deliberately throwing in development.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["frontend", "error-handling", "resilience", "react"]
+    }
+  ]
+}

package/packs/migration.json

@@ -0,0 +1,147 @@
+{
+  "name": "Migration Research Templates",
+  "description": "Common research patterns for technology migrations -- database migrations, cloud migrations, language/framework migrations. Seed claims capture recurring risks and constraints.",
+  "version": "1.0.0",
+  "claims": [
+    {
+      "id": "mig-001",
+      "type": "constraint",
+      "topic": "migration rollback safety",
+      "content": "Production migrations must be reversible. Every schema change, data transform, or infrastructure swap needs a tested rollback procedure with a maximum rollback time SLA.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "rollback", "safety"]
+    },
+    {
+      "id": "mig-002",
+      "type": "risk",
+      "topic": "dual-write consistency risk",
+      "content": "Dual-write periods introduce data consistency risks. During cutover, writes must go to both old and new systems, and a reconciliation process must detect drift.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "dual-write", "consistency"]
+    },
+    {
+      "id": "mig-003",
+      "type": "risk",
+      "topic": "migration window overrun",
+      "content": "Data migrations that run longer than the maintenance window force a choice between extended downtime and incremental migration. Estimate data volume transfer rates early.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "downtime", "planning"]
+    },
+    {
+      "id": "mig-004",
+      "type": "constraint",
+      "topic": "minimum viable migration scope",
+      "content": "Feature parity with the legacy system is rarely achievable on day one. Define a 'minimum viable migration' scope that covers the critical path and defer edge cases.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "stated",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "scope", "mvp"]
+    },
+    {
+      "id": "mig-005",
+      "type": "recommendation",
+      "topic": "strangler fig migration pattern",
+      "content": "Use the strangler fig pattern for large migrations: route traffic incrementally to the new system while the old system continues to serve unmodified paths.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "strangler-fig", "pattern"]
+    },
+    {
+      "id": "mig-006",
+      "type": "risk",
+      "topic": "character encoding corruption",
+      "content": "Character encoding mismatches (UTF-8 vs Latin-1, collation differences) are the most common silent data corruption source in database migrations. Test with production-representative data.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "database", "encoding"]
+    },
+    {
+      "id": "mig-007",
+      "type": "estimate",
+      "topic": "cloud migration timeline",
+      "content": "Cloud-to-cloud migrations typically take 2-4x longer than initial estimates due to undocumented dependencies, permission differences, and networking surprises.",
+      "source": { "origin": "industry", "artifact": null, "connector": null },
+      "evidence": "web",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "cloud", "estimation"]
+    },
+    {
+      "id": "mig-008",
+      "type": "constraint",
+      "topic": "API versioning during migration",
+      "content": "API contract changes during migration require versioned endpoints. Clients must be able to continue using the old API for a deprecation period (minimum 3 months is standard).",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "api", "versioning"]
+    },
+    {
+      "id": "mig-009",
+      "type": "recommendation",
+      "topic": "shadow traffic validation",
+      "content": "Run shadow traffic (replay production reads against the new system without serving responses) for at least 2 weeks before cutover. Compare results for correctness and latency.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "shadow-traffic", "validation"]
+    },
+    {
+      "id": "mig-010",
+      "type": "risk",
+      "topic": "legacy knowledge decay",
+      "content": "Team knowledge of the legacy system degrades over time. If migration stalls, institutional knowledge may be lost before it completes. Document as you migrate, not after.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "stated",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["migration", "knowledge", "documentation"]
+    }
+  ]
+}

package/packs/observability.json

@@ -0,0 +1,175 @@
+{
+  "name": "Observability and Incident Response",
+  "description": "Structured logging, metrics, distributed tracing, SLO definitions, alerting hygiene, and incident response patterns for production systems.",
+  "version": "1.0.0",
+  "claims": [
+    {
+      "id": "obs-001",
+      "type": "constraint",
+      "topic": "structured logging format",
+      "content": "All application logs must be structured JSON with mandatory fields: timestamp (ISO 8601), level (debug/info/warn/error/fatal), message, service, and trace_id. Unstructured string logs break log aggregation queries and make correlation impossible at scale.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "production",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "logging", "structured-logging"]
+    },
+    {
+      "id": "obs-002",
+      "type": "recommendation",
+      "topic": "RED method for services",
+      "content": "Every service should expose the RED metrics: Rate (requests per second), Errors (failed requests per second), and Duration (latency histogram). These three metrics cover 80% of service-level debugging. Use histograms with buckets at 5ms, 10ms, 25ms, 50ms, 100ms, 250ms, 500ms, 1s, 2.5s, 5s, 10s.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "metrics", "red-method", "monitoring"]
+    },
+    {
+      "id": "obs-003",
+      "type": "factual",
+      "topic": "SLO error budget calculation",
+      "content": "An SLO of 99.9% availability allows 43.2 minutes of downtime per 30-day window (0.1% error budget). An SLO of 99.95% allows 21.6 minutes. Error budget = total time * (1 - SLO target). When budget is exhausted, freeze feature work and focus on reliability.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "slo", "error-budget", "reliability"]
+    },
+    {
+      "id": "obs-004",
+      "type": "risk",
+      "topic": "alert fatigue",
+      "content": "Alert fatigue occurs when on-call engineers receive more than 2-3 actionable alerts per shift. Non-actionable alerts must be demoted to dashboards or deleted. Every alert should have a runbook link, a clear threshold, and an expected action. Pages without runbooks erode trust in the alerting system.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "production",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "alerting", "on-call", "alert-fatigue"]
+    },
+    {
+      "id": "obs-005",
+      "type": "recommendation",
+      "topic": "distributed trace propagation",
+      "content": "Propagate W3C Trace Context headers (traceparent, tracestate) across all service boundaries including HTTP, gRPC, and message queues. Without trace propagation, latency debugging in distributed systems requires manual log correlation which takes 10-50x longer.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "tracing", "distributed-systems", "opentelemetry"]
+    },
+    {
+      "id": "obs-006",
+      "type": "constraint",
+      "topic": "no PII in logs",
+      "content": "Logs must never contain PII (emails, names, IP addresses, session tokens, passwords). Use hashed or tokenized identifiers for correlation. Accidental PII in logs creates GDPR/CCPA compliance risk and makes log retention policies complex. Enforce with automated log scrubbing or allowlist-based field serialization.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "logging", "pii", "compliance"]
+    },
+    {
+      "id": "obs-007",
+      "type": "recommendation",
+      "topic": "USE method for infrastructure",
+      "content": "For infrastructure resources (CPU, memory, disk, network), track the USE metrics: Utilization (% of capacity used), Saturation (queue depth or wait time), and Errors (error count). Alert when utilization exceeds 80% sustained over 5 minutes or saturation is non-zero.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "metrics", "use-method", "infrastructure"]
+    },
+    {
+      "id": "obs-008",
+      "type": "factual",
+      "topic": "log retention cost model",
+      "content": "Log storage costs scale linearly with volume and retention. At 100 GB/day ingestion, 30-day retention costs roughly $3,000-6,000/month on major cloud log platforms (Datadog, Splunk, CloudWatch). Reduce costs by sampling debug logs (keep 10%), archiving to cold storage after 7 days, and dropping health check logs.",
+      "source": { "origin": "industry", "artifact": null, "connector": null },
+      "evidence": "web",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "logging", "cost", "retention"]
+    },
+    {
+      "id": "obs-009",
+      "type": "recommendation",
+      "topic": "incident severity definitions",
+      "content": "Define incident severity levels with quantitative criteria: SEV1 (total service outage or data loss, all hands, 15-min response), SEV2 (degraded for >50% of users, team response, 30-min), SEV3 (degraded for <50% or non-critical feature down, next business day), SEV4 (cosmetic or minor, backlog). Ambiguous severity wastes escalation time.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "incident-response", "severity", "on-call"]
+    },
+    {
+      "id": "obs-010",
+      "type": "risk",
+      "topic": "cardinality explosion in metrics",
+      "content": "High-cardinality labels (user IDs, request IDs, full URLs) on metrics cause cardinality explosion, which degrades query performance and inflates storage costs exponentially. Prometheus recommends keeping total time series under 10 million. Use logs or traces for high-cardinality data, not metrics.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "production",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "metrics", "cardinality", "prometheus"]
+    },
+    {
+      "id": "obs-011",
+      "type": "recommendation",
+      "topic": "postmortem blamelessness",
+      "content": "Postmortems must be blameless and focus on systemic causes, not individual actions. Required sections: timeline, impact (users affected, duration, revenue impact), root cause, contributing factors, action items with owners and due dates. Publish postmortems within 48 hours of incident resolution.",
+      "source": { "origin": "best-practice", "artifact": null, "connector": null },
+      "evidence": "documented",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "incident-response", "postmortem", "culture"]
+    },
+    {
+      "id": "obs-012",
+      "type": "estimate",
+      "topic": "OpenTelemetry migration effort",
+      "content": "Migrating from vendor-specific instrumentation (Datadog agent, New Relic APM) to OpenTelemetry SDK typically takes 2-4 weeks per service for auto-instrumentation, plus 1-2 additional weeks for custom spans and metrics migration. The payoff is vendor portability and 30-50% reduction in long-term instrumentation costs.",
+      "source": { "origin": "industry", "artifact": null, "connector": null },
+      "evidence": "web",
+      "status": "active",
+      "phase_added": "define",
+      "timestamp": "2025-01-01T00:00:00.000Z",
+      "conflicts_with": [],
+      "resolved_by": null,
+      "tags": ["observability", "opentelemetry", "migration", "cost"]
+    }
+  ]
+}