September 2026 Summaries

Network change procedures often span multiple vendors, owners, documents, approvals, scripts, and rollback plans, creating coordination challenges when these resources become outdated or disconnected. The text presents a Method of Procedure application built on Harper as a way to centralize procedure storage, dependency context, approvals, staged execution, validation, recovery, and audit records while integrating with existing ticketing, inventory, and automation systems. It describes a telecom customer that developed a prototype in three days using AI coding tools after a major outage, illustrating an iterative approach that begins with a specific operational workflow. Compared with assembling separate databases, caches, messaging systems, search tools, and APIs, Harper is positioned as a unified runtime that reduces infrastructure integration work and supports searchable procedure data through semantic, text, and structured retrieval. Teams are encouraged to begin with one frequent, well-defined change type, validate workflows through simulated execution and limited pilots, track operational outcomes, and expand reusable patterns over time.