Overview - RFQX Security Architecture Package

Engineering Workflow Dashboard

Customer PDF -> Parsed Markdown -> Customer Requirement Analysis -> System Requirements -> Architecture / Design -> Traceability Matrix -> Estimation -> Jira Import.

Source PDFs8uploaded/source documents Parsed Documents8Markdown conversion success Customer Requirements9071789 total customer items System Requirements73supplier/internal Architecture Items8linked design allocations Traceability Links9161789 end-to-end rows Estimation Items1789requirement-based Open Clarification Questions472P1: 6 P1 Decisions6current decision-control gate Auto-Closed by Additional PDFs0NO AUTO CLOSURE Customer Decision RequiredYESdownstream baseline gate Security Weak AreasOPENsecurity review status Validation Warnings2783coverage and quality checks

Decision-Control Gate

Downstream engineering artifacts remain provisional until customer clarification closure evidence is complete.

BLOCKED BY CUSTOMER DECISIONP1 OPENSECURITY REVIEW OPENNO AUTO CLOSURE

472open clarification questions

6P1 decisions

0answered by additional PDFs

6security weak areas

Open Customer Decisions & Clarifications

Workflow Navigation

Source Documents & ParsingPDF inputs, parse status, markdown previews, extracted sections, and diagnostics.Customer RequirementsCustomer asks, meaning, assumptions, proposed solution and implementation notes.Customer Decisions & ClarificationsP1 decisions, closure evidence, security weak areas, and customer-decision blockers.Per-Document ViewDocument-specific structure, requirements, analysis, warnings, and cross-links.System RequirementsInternal testable supplier requirements with coverage and quality checks.Architecture & DesignDesign items, decisions, diagrams, and links back to system requirements.Traceability MatrixCustomer requirement to system requirement to design, estimation, and Jira.EstimationImplementation complexity and effort hours per requirement.Jira ImportDry-run issue candidates, field mappings, validation errors, and import status.Additional DocumentsRaw intermediate outputs, orphan evidence, debug reports, and appendix material.

Coverage Status

Status	Rows	Action
COMPLETE	916	Review rows
SECURITY REVIEW OPEN	442	Review rows
TOO BROAD SYSTEM REQUIREMENT	220	Review rows
BLOCKED BY CUSTOMER DECISION	208	Review rows
MISSING SYSTEM REQUIREMENT	2	Review rows
MISSING JIRA LINK	1	Review rows

Validation Results

Severity	Rule	Count	Engineering Meaning	Page
FAIL	customer requirements without system requirement coverage	2	Customer requirements need supplier system requirement derivation.	Open
FAIL	system requirements covering more than 10 customer requirements	18	SSR covers too many customer requirements without justification.	Open
WARN	system requirements without acceptance criteria	73	Renderer derives provisional acceptance criteria; baseline criteria should be authored.	Open
FAIL	traceability rows with missing links	873	Traceability row is incomplete or needs review.	Open
FAIL	open customer decisions block downstream artifacts	472	Customer clarification decisions remain open and must gate downstream baselines.	Open
FAIL	clarifications without complete closure evidence	472	Closure is blocked unless customer answer, Source document, requirement IDs, evidence, and rationale all exist.	Open
FAIL	security weak areas unresolved	6	Security weak areas remain review items until customer confirmation.	Open
FAIL	traceability blocked by customer decisions	208	Traceability rows depend on unresolved customer decisions.	Open
WARN	traceability security review open	442	Traceability rows depend on unresolved security weak areas.	Open
WARN	duplicate customer requirements	215	Potential duplicate customer requirement statements were detected.	Open
WARN	duplicate or overlapping system requirements	1	Structured SSR analysis found duplicate/overlapping SSR groups.	Open
WARN	customer requirements without Jira link	1	Customer requirement has no Jira issue candidate.	Open