memories/ai-operations-portfolio-and-roadmap-3a7ec0a5.md

memory

A centralized view of active and recently active AI Operations initiatives, maintained as a navigation aid. Delivery state is tracked in the APMT Jira board.

Current Active Initiatives (as of Aug 26, 2026)

  • AI Portal: Portal, catalog, and governance development (APMT-184).
  • AI Ops Leadership Visibility Project: Roadmap and reporting implementation (APMT-311).
  • [[AI Ops Portfolio Ledger]]: Tracking methodology, telemetry, and ROI (APMT-302 / APMT-303). (In Backlog)
  • [[Citizen-developer infrastructure]]: Intake, GitLab templates, and self-service deployment
  • [[ai-ops-run]]: Platform for webhook and scheduled workflows.
  • Docebo Wrapped: Personalized account-level customer summaries; Snowflake → DynamoDB → app architecture, currently on mock/seed data with real Snowflake cutover targeted mid-September 2026; Okta auth not yet added (APMT-298, parent; APMT-299, APMT-301, APMT-300, APMT-313 children).
  • Claude Tag Rollout: Slack integration with shared Anthropic sessions, currently in pilot.
  • K2M Engine: Proof of Concept deployment and EC2 architecture.
  • AI Operations Team#Operating Model: Phased rollout of the hub-and-spoke strategy.
  • Contracts Assistant Agent: AI agent suggesting accept/reject/counter positions on legal contract redlines via clause library + historical MSA precedent, with a Word plugin workflow; targeting deals ≤$75k. Owner: [[Samuel Adams]]. Standalone-first, LinkSquares integration deferred to Phase 2. (APMT-270, In Development, due 2026-08-28; superseding [[APMT-187]] (Cancelled)).

Governance & Hygiene

  • Jira (APMT board) is the authoritative source for status, assignment, and delivery dates.
  • Production blockers must be recorded separately from administrative/reporting milestones.

Asset Registry / Telemetry Store (as of 2026-09-09)

  • Registry Structure: Interim telemetry/portfolio store implemented as an asset registry (one YAML file per custom build). Captures metadata, support level, expiration date, BPO, KPI/value estimate, effort (estimated/actual), and review logs. Designed as a portfolio management tool rather than technical documentation.
  • Rules: The registry is the enforcement mechanism for the Custom Build engagement model rules: mandatory expiration dates and telemetry requirements (Ref: AIPM Playbook AI Ops Custom Build Engagement Model).
  • Target State: Migration toward an aggregator fed by OpenTelemetry endpoints per application, using scoped tokens. Aggregation targets events rather than unified metrics, acknowledging that KPIs are unique to each app.
  • Risk: Potential telemetry data flow failure. [[Preet Patel]] is currently investigating for errors.
  • Sources: Jira APMT-302, APMT-303; "Preet / Samuel — Glean Agent Audit + Sync" (2026-09-09).