Skip to content
QL
Traceability

Requirement to release, in one unbroken chain

Hover any node to light up its full lineage in both directions. This is the graph that makes change impact a traversal rather than a search.

0%
Lineage coverage
35/37
Trace
REQ-1042

Daily transaction limit

17 artifacts · 19 relationships

artifactrequirementruletestautomationprci
SourceRequirementBusiness ruleTest casesAutomationPull requestCI
ART-001 — Page 12 · Section 4.3ART-001REQ-1042 — Daily transaction limitREQ-1042BR-22 — Daily transaction limit enforcementBR-22TC-094 — Daily transaction limit is satisfied on the primary pathTC-094TC-095 — Daily transaction limit with the amount split across two transactions inside the same windowTC-095TC-096 — Daily transaction limit submitted through the claims API rather than the portalTC-096TC-097 — Rolling 24-hour transaction total exactly at the limit (₹50,000)TC-097TC-098 — Rolling 24-hour transaction total just above the limit (₹50,001)TC-098TC-099 — A transaction taking the rolling total above the limit must be refusedTC-099TC-100 — The rolling window must expire contributions older than 24 hoursTC-100TC-101 — The limit must be enforced server-side, not only by the on-screen headroom displayTC-101AUTO-001 — Transaction exactly at the daily limit is acceptedAUTO-001AUTO-002 — Transaction above the daily limit is refusedAUTO-002AUTO-003 — Rolling window expires contributions older than 24 hoursAUTO-003AUTO-004 — Limit is enforced server-side across split transactionsAUTO-004PR-184 — salc/automation/REQ-1042PR-184CI RUN #291 — Awaiting engineer reviewCI RUN #291
Hover a node to isolate its lineage.
Why this exists

Traceability is not documentation

The value is not in any single generation step. It is in the connected, versioned context that survives between steps — so a requirement change can be traced forward to the tests it invalidates, and a generated test can be traced backward to the sentence in the PRD that justifies it.

Two different questions are being answered here, and both must hold. Citation asks where a piece of generated text came from — enforced by the gateway. Traceability asks which requirement a test covers — enforced by QP-01. Citation is provenance; traceability is completeness.

Because citations are stored as relationships rather than text, “is there any uncited output?” is a query. That is what makes it machine-enforceable rather than a review checklist.

Coverage

What the number means

94%
Requirements in scope
37
With an unbroken, trusted chain
35
Blocked by an open contradiction
2
Test cases linked
147 / 147
Citation relationships
214

A chain is only counted as trusted when the requirement has test coverage and no open contradiction sits on its path. REQ-1042 and REQ-1026 are covered by tests but disputed at source, so SALC refuses to call them complete.

REQ-1042 is blocked by C-014

Interactive product demonstrator. This experience illustrates the designed SALC workflow using simulated project data. Production integrations and capabilities are being developed.