Live

Live Overview

RTMify Live is a local-first traceability runtime. It runs on your machine, connects to your spreadsheet, watches your codebase, and keeps the full traceability graph current — continuously, in the background.

Architecture

Live uses a three-layer model: a native OS shell, a local runtime, and a browser dashboard. The browser dashboard is the main operator surface. The native shell is a thin OS-integration wrapper.

1
Native shell

A menu-bar app (macOS) or system tray app (Windows) that manages the runtime process: start/stop, launch-at-login, crash restart, and license gate. It is not the product UI.

2
Local runtime (rtmify-live)

The core process. Owns SQLite graph persistence, workbook sync, status write-back, repo scanning, test-results ingestion, report generation, and MCP. Binds exclusively to 127.0.0.1.

3
Browser dashboard

The operator UI, served by the local runtime and opened in your default browser at http://127.0.0.1:8000. Shows graph views, analysis, code traceability, reports, and operator tooling.

What Live owns

Workbook sync

Polls your Google Sheets or Excel Online workbook every 30 seconds. Detects changes via a change token and ingests only when needed.

Graph persistence

Stores the full traceability graph in a local SQLite database. Survives restarts. Supports historical tracking and suspect propagation.

Status write-back

After each sync, writes RTMify status codes and row formatting back into the connected workbook. Writes the RTMify Verification column after test results are ingested.

Repo scanning

Scans local git repositories for requirement annotations in source and test files, commit references, and blame data.

Test results ingestion

Accepts test execution evidence via HTTP POST or inbox file-drop. Computes verification rollups per requirement.

Report generation

Generates RTM (PDF, Word, Markdown), DHR (PDF, Markdown), code coverage (Markdown), product-scoped Design BOM (PDF, Word, Markdown), and SOUP Register (PDF, Word, Markdown) reports from the live graph on demand.

MCP

Exposes a Model Context Protocol server on the same loopback address. AI assistants can query requirements, tests, risks, gaps, code, Design BOMs, and SOUP/software inventory without screen-scraping.

Dashboard

The browser UI providing tabular graph views, impact analysis, gap review, code traceability, and report launch — all driven by the SQLite graph.

Dedicated ingest guides

Design BOM Ingestion

Hardware BOM CSV, grouped workbook, read-only Design BOM Sync, graph shape, replacement semantics, and template download path.

ATE / ATP Results

Production-test and acceptance-test evidence through the JSON test-results API, with serial-number and product-scoped unit history.

SOUP Ingestion

Dedicated SOUP JSON and workbook ingest, SOUP Sync, anomaly fields, software graph shape, and the downloadable SOUP template.

Local-first, always

Live is not a hosted service and not a team-shared server. The HTTP server binds 127.0.0.1 only. Remote access is unsupported by design. Foreign Host headers and cross-origin requests from external origins are rejected at the server level.

The MCP endpoint is equally local — it is not a public internet MCP server. Only processes on the same machine can reach it.

What Live is not

  • —A remote multi-user SaaS or team-shared server
  • —A spreadsheet editor — it reads and writes status cells but does not edit requirement content
  • —A GitHub or GitLab integration — it reads local git history, not remote APIs
  • —A public MCP endpoint — MCP is loopback-only, same-machine
  • —A replacement for Trace — Trace is a single-run report generator; Live is a continuous runtime