Repo Scanning
Live can link one or more local git repositories into the traceability graph. Scanning turns requirement IDs from your spreadsheet into implementation evidence — surfacing which files, tests, and commits relate to which requirements.
What it reads
Live reads from the local repository only. It does not call GitHub, GitLab, or any remote API.
Working tree
Current source and test files, scanned for @req annotations. Respects .gitignore.
Git history
Local commit log, scanned for commits whose messages reference requirement IDs.
Blame data
Git blame on annotated lines, capturing author, email, and commit timestamp.
Annotation syntax
Add @req comments to your source and test files. Live scans for them on every repo-scan cycle and links the annotated file to the referenced requirement in the graph.
Implementation file — marks the requirement as implemented here
// @req REQ-042 Validate input before processing
function validatePayload(data) {
// ...
} Test file — marks both the requirement and the test group
// @req REQ-042 @test TG-007
test('rejects malformed payload', () => {
// ...
}); Multiple requirements on one line
// @req REQ-010 REQ-011 Shared implementation for both requirements
function sharedHandler() { ... } Live recognizes structured IDs made of two or more hyphen-separated alphanumeric or underscore segments. Examples: REQ-042, REQ-OQ-001, Foo-1AF5-Bar-Q5, and ABC_DEF-01_A.
Adding repositories
From the dashboard
Open the Code group and use the repo-management surface to add, list, and remove registered repositories. Changes take effect on the next scan cycle.
From the CLI
Pass --repo at startup. The flag is repeatable for multiple repos:
rtmify-live --repo /path/to/firmware --repo /path/to/tests
CLI-registered repos are stored in the database and persist across restarts.
What gets added to the graph
Each scan pass creates or updates graph nodes for everything it finds, then links them to the relevant requirements:
| Node type | Created from | Linked to |
|---|---|---|
| SourceFile | A source file containing one or more @req annotations | Requirement via IMPLEMENTED_IN edge |
| TestFile | A test file containing @req + @test annotations | Requirement via VERIFIED_BY_CODE edge |
| CodeAnnotation | Each individual @req comment in a file | SourceFile or TestFile; stores context, author, timestamp |
| Commit | A commit whose message mentions a traced requirement ID | Requirement; stores author email and timestamp |
Where repo data appears
- Code dashboard group — repo list, scan status, file-level traceability tables, unimplemented requirements, untested source files, and recent commits
- Requirement drill-down — shows which source files implement the requirement and which test files verify it
- RTM report — Source File, Test File, and Last Commit columns are populated from repo data
- DHR report — code annotations, commits, and source/test evidence appear in the design-history view
- Code coverage report — Markdown summary of which requirements have code evidence and which gaps exist
- MCP — code traceability tools and resources expose file annotations, commit history per requirement, and untested-source-file queries to AI assistants