RTMX

Keep AI On Task

AI writes code fast—but does it meet your requirements? RTMX connects every change to a spec and its tests, so your AI always knows what you're shipping and why.

Star on GitHub Try RTMX

RTMX closed-loop workflow: AI Agent creates requirements, links to tests, reports status, agent queries via MCP

See It In Action

rtmx status

$ ▋

=============================== RTM Status Check ===============================

Requirements: 74.0%

[████████████████████████████████████████████████████████████████████████████]

✓ 54 COMPLETE △ 0 PARTIAL ✗ 19 MISSING (73 total)

================================= Phase Status =================================

Phase 1 (Foundation): 100.0% ✓ Complete (8✓ 0⚠ 0✗)

Phase 2 (Core Features): 100.0% ✓ Complete (6✓ 0⚠ 0✗)

Phase 3 (Testing): 100.0% ✓ Complete (3✓ 0⚠ 0✗)

Phase 4 (Developer Exp): 100.0% ✓ Complete (11✓ 0⚠ 0✗)

Phase 5 (CLI UX): 100.0% ✓ Complete (7✓ 0⚠ 0✗)

Phase 6 (Web UI): 100.0% ✓ Complete (8✓ 0⚠ 0✗)

Phase 7 (Real-Time): 100.0% ✓ Complete (6✓ 0⚠ 0✗)

Phase 8 (Website): 83.3% ⚠ In Progress (5✓ 0⚠ 1✗)

Phase 9 (CRDT): 0.0% ✗ Not Started (0✓ 0⚠ 6✗)

Phase 10 (Collaboration): 0.0% ✗ Not Started (0✓ 0⚠ 6✗)

Phase 11 (IDE): 0.0% ✗ Not Started (0✓ 0⚠ 5✗)

Phase 12 (Distribution): 0.0% ✗ Not Started (0✓ 0⚠ 1✗)

==================== 54 complete, 0 partial, 19 missing (74.0%) ====================

See your progress at a glance.

rtmx backlog

$ ▋

============================= Prioritized Backlog =============================

Total Requirements: 73

✗ MISSING: 19 (26.0%)

△ PARTIAL: 0 (0.0%)

Estimated Effort: 35.0 weeks

CRITICAL PATH ITEMS (TOP 10)

+-----+----------+----------------+--------------------------------------+----------+----------+

+=====+==========+================+======================================+==========+==========+

| 1 | ✗ | REQ-CRDT-001 | CRDT layer shall use y-py library | 1.0w | 11 (0) |

+-----+----------+----------------+--------------------------------------+----------+----------+

| 2 | ✗ | REQ-COLLAB-001 | CRDT sync server shall use y-web... | 2.0w | 5 (0) |

+-----+----------+----------------+--------------------------------------+----------+----------+

| 3 | ✗ | REQ-COLLAB-002 | Server shall track connected use... | 1.5w | 3 (0) |

+-----+----------+----------------+--------------------------------------+----------+----------+

| 4 | ✗ | REQ-CRDT-002 | Requirements shall be represente... | 2.0w | 2 (0) |

+-----+----------+----------------+--------------------------------------+----------+----------+

| 5 | ✗ | REQ-IDE-001 | VSCode extension shall display R... | 3.0w | 2 (0) |

+-----+----------+----------------+--------------------------------------+----------+----------+

Know exactly what to build next.

rtmx health

$ ▋

============================== RTMX Health Check ==============================

[PASS] config_valid: Config valid: rtmx.yaml

[PASS] rtm_exists: RTM database found: docs/rtm_database.csv

[PASS] rtm_loads: RTM database loaded: 73 requirements

[PASS] schema_valid: Schema validation passed

[WARN] reciprocity: Reciprocity violations: 53

[PASS] cycles: No circular dependencies

[WARN] test_markers: Test coverage: 46.6% (39 requirements without tests)

[WARN] agent_configs: Agent configs without RTMX: CLAUDE.md

============================================================

Status: DEGRADED (warnings present)

Summary: 5 passed, 3 warnings, 0 failed, 0 skipped

Catch issues before they become problems.

rtmx deps

$ ▋

================================= Dependencies =================================

ID Deps Blocks Description

-------------------------------------------------------------------------------------

REQ-WEB-001 0 23 rtmx serve command shall start FastAPI...

REQ-WEB-007 1 12 Server shall support WebSocket connections

REQ-CRDT-001 0 11 CRDT layer shall use y-py library

REQ-WEB-002 1 8 REST API shall expose /api/status endpoint

REQ-RT-001 1 6 Server shall watch RTM database for changes

REQ-UX-001 0 5 rtmx status shall display rich progress bars

REQ-RT-002 1 5 Server shall push updates to WebSocket...

REQ-SITE-001 0 5 Website shall use Astro with Starlight theme

REQ-COLLAB-001 2 5 CRDT sync server shall use y-websocket...

REQ-DX-001 0 4 All rtmx artifacts shall be in .rtmx/...

-------------------------------------------------------------------------------------

✓ No circular dependencies detected

Find what's blocking your progress.

Why RTMX Matters

Software Engineering is Fragmenting

The centralized era of "one company, one repo, one CI server" is ending. We're entering a fundamentally different world.

Gig Developers

Engineers spanning multiple organizations simultaneously. Your requirements can't live in one company's Jira.

AI Across Trust Boundaries

Agents generating code for projects they don't own. How do you verify work when you can't trust the worker?

Mathematical Proof

Regulated industries requiring cryptographic evidence of access control. "Trust me" isn't compliance.

Offline-First

Network is optional, not guaranteed. Air-gapped facilities, field deployments, unreliable connections.

The Old Model

GitHub / GitLab / Jira

Centralized servers
Corporate trust boundaries
Network-dependent workflows
Single organization scope

The New Model

RTMX

Git-native, fully distributed
Zero-trust verification
Offline-first architecture
Cross-organization federation

$199B Agentic AI market by 2034 Precedence Research

66% of developers frustrated with "almost right" AI code Stack Overflow 2025

39% of project failures due to requirements issues Zipdo Statistics

48% of AI-generated code contains security vulnerabilities Qodo 2025

One Command to See Everything

Know exactly where your project stands. rtmx status shows what's done, what's blocked, and what needs tests.

Proof, Not Promises

Every feature links to a test that proves it works. No more "I think it's covered."

AI That Knows Your Project

Claude, GPT, and other agents can query your requirements in real-time. They know what to build next.

Works With Your Tools

Sync to GitHub Issues, Jira, or keep everything local in version control. Your data, your choice.

See What's Blocking You

Visualize dependencies and find the critical path to done. Stop guessing what to work on next.

Catch Mistakes Before They Ship

Validate requirements against your team's standards automatically. Extensible for aerospace, medical, and defense.

Your Data Stays Yours

No cloud required. Open source and auditable. Git-native audit trail for compliance.

Programmable Requirements

Full Python API. Query, filter, and automate from any script or notebook. Build custom workflows.

Coming Soon

Team Sync

CRDT-based collaboration with automatic conflict resolution. Multiple users, one source of truth.

AI writes code fast. But does it match your requirements?

Most tools track tasks. RTMX tracks whether the code actually does what you asked.

Feature	RTMX	GitHub	GitLab	Jira	Linear
Test traceability	Built-in	No	Basic	Plugin	No
pytest markers	Native	No	No	No	No
AI agent support	MCP	Copilot	Duo	API only	API only
Requirements spec	CSV + Markdown	Issues only	Epics	Yes	No
Git-native storage	Yes	Database	Database	SaaS	SaaS
Self-hosted	Free	Enterprise	Free	$$$	No
Open source	MIT	No	Core only	No	No
CLI-first workflow	Yes	gh CLI	glab CLI	No	No

DON'T Use RTMX

Seriously. It's not for everyone. Here's why you should probably stay away:

You already have a spreadsheet.

And you definitely don't spend 2 hours every sprint reconciling it with what actually shipped. That's just part of the process, right?

AI-generated code always works.

Your agent never confidently implements the wrong feature or quietly breaks something three files away. No need to trace what it changed back to what you actually asked for.

You love Jira.

RTMX is distributed and version-controlled with your code. Way worse than managing requirements in a GUI that's definitely not loading right now.

You don't want to pay $9.

You'd rather spend 9 hours every week fixing the tech debt slop that AI creates for your team. Time is money, but it's your time.

Tests prove nothing.

You trust your test suite, even if nobody can remember which features it actually covers. "I think auth is tested somewhere" is basically the same as traceability.

Dependencies are obvious.

Your team instinctively knows that REQ-47 blocks REQ-12 which blocks REQ-89. Why would you need a graph for that?

Your AI knows the codebase.

Context windows are unlimited now. Your agent never forgets the requirement it was working on or what tests need to pass. Refresh the chat? No problem.

Audits are fine.

"Show me every requirement and its test" is a reasonable ask and you can answer it in 5 minutes. You've definitely done the drill and it went great.

Still reading? Sounds like you might actually need RTMX.

Get Started