Business outcome, CMS scope, data sensitivity, owner role, risk tier, and approval depth.
MarketLink CMS EDE requirements traceability
From requirement to disposition.
A program-facing view that connects every CMS/EDE requirement source to its Agile plan, controlled delivery lane, test case, and evidence disposition — with human-owned gates the whole way.
-
01
CMS source
Requirement, toolkit, control, FIT row, or change request.
-
02
Agile plan
Epic, sprint lane, backlog item, owner role, acceptance criteria.
-
03
Controlled delivery
Screen, API, workflow, control, data, notice, or integration behavior.
-
04
Proof and release
Test kit, case ID, security gate, readiness state, open gap, and disposition.
Governed metadata view
Loading current traceability position...
Canonical AI SDLC lifecycle
One seven-phase lifecycle connects Agile artifacts, agentic execution, and release controls.
The traceability matrix is aligned to the WHPS AI SDLC, an Agile framework adapted for agentic delivery. The method keeps product ownership, architecture review, security validation, test evidence, and release authority visible at the right review altitude.
Epics, backlog items, sprint lanes, acceptance criteria, dependencies, and Definition of Done.
Data flow, integration path, trust boundary, threat model, design review, and control alignment.
Platform functions, APIs, UI behavior, notices, controls, and controlled delivery lanes.
FIT cases, UAT capture, regression checks, accessibility, security scans, and remediation evidence.
Evidence index, control mapping, integrity state, open gaps, and reviewer disposition.
Named approvals, export readiness, rollback path, archive discipline, monitoring, and change control.
Traceability coverage
Every visible row maps to a CMS source, Agile backlog lane, AI SDLC gate, test kit, and evidence reference.
This is intentionally a traceability view, not an evidence repository. The matrix keeps the assurance chain visible while raw evidence remains in the controlled repository for authorized review and archival control.
--%
Traceability link coverage
Rows with source, backlog, test, and evidence references.
Disclosure boundary
Requirements, Agile artifacts, controls, tests, functions, and evidence only.
This view is limited to requirement sources, Agile backlog, platform functions, test coverage, evidence references, audit disposition, and open gaps.
Evidence posture
Reference controlled evidence. Do not publish raw evidence.
The matrix shows readiness metadata and reviewer state; source artifacts remain in the controlled evidence repository under the named evidence owner and release authority.
Evidence completion
Traceability is complete; auditor evidence readiness is a separate status.
The toolkit-driven traceability matrix can be complete while final evidence remains in capture and review. Evidence completion below reflects export-ready auditor evidence, not mapped rows or supporting material held in the controlled repository.
--%
Auditor evidence completion
Export-ready evidence disposition.
Current posture
Loading evidence readiness...
Evidence readiness will separate current review candidates, pending UAT capture, and source-pending scope.
Enrollment evidence
Pending full enrollment capture
The final packet still needs a current full enrollment walkthrough and independent reviewer disposition before the evidence package can be marked export-ready.
| Evidence area | Required | Export-ready | In review | Pending capture | Source pending | Completion |
|---|---|---|---|---|---|---|
| Loading evidence readiness... | ||||||
Program management status view
A familiar Agile status layout without losing requirement-to-proof traceability.
This gives project management, product, QA, and program leadership the table view they expect: requirement area, backlog status, testing posture, evidence status, dependencies, risks, and next actions.
Coverage reflects traceability references, not final auditor evidence completion.
Metadata references held against the controlled evidence record.
Current review candidate still subject to independent disposition and export-readiness approval.
Items requiring source or scope confirmation before export.
Development status by domain
| Domain | Total | Done | In progress | Pending | At risk | Rate |
|---|---|---|---|---|---|---|
| Loading development status... | ||||||
Evidence status by requirement area
| Requirement area | Evidence references | In review | Pending capture | Source pending | Access |
|---|---|---|---|---|---|
| Loading evidence status... | |||||
Requirements traceability matrix
Search from requirement source to function, test case, and evidence disposition.
Each row is built for review: CMS source, Agile epic, sprint lane, backlog item, AI SDLC gate, acceptance criteria, platform function, test kit, case ID, evidence reference, audit disposition, and open gap.
| Trace ID | Requirement source | Agile backlog | AI SDLC gate | Function | Test kit / case | Evidence | Status |
|---|---|---|---|---|---|---|---|
| Loading traceability matrix... | |||||||
Evidence reference model
The matrix shows readiness. The controlled repository preserves the proof.
This prevents duplicate artifact copies, avoids version confusion, and keeps reviewers aligned to the current evidence state, open gaps, named ownership, and AI SDLC release controls.
Current readiness
F001-F013 evidence state
One review candidate, eleven pending captures, one source-pending case, and zero export-ready.
Traceability matrix Requirement-to-disposition mapMapped source, owned delivery work, control gate, test state, and evidence disposition.
Delivery controls WHPS AI SDLCSeven phases, thirteen control gates, independent verification, and retained human authority.
Executive view MarketLink evidence chainPresent the production position, CMS UAT result, and open evidence-completion boundary.
Actions, dependencies, and risks
Traceability is established; remaining work is evidence capture, source confirmation, and final disposition.
Traceability readiness and final evidence completion are separate review states. The matrix shows the path; the open items show what remains before export-ready auditor submission.
- Loading next steps...
- Loading dependencies...
- Loading risks...