AgilePlus

Appearance

Tracera FR/NFR Catalog — Backfilled Requirements ​

Version: 1.0.0 Date: 2026-05-29 Status: Active

Meta — Dog-fooding note: Tracera IS the traceability tool. This catalog is designed to be ingested into Tracera's own Requirement / Artifact / TraceLink model, making it a self-referential demonstration of the platform's value. Every FR listed here corresponds to a Requirement node, every PR/test reference becomes an Artifact, and every (FR→PR) / (FR→test) pair becomes a TraceLink with VERIFIES or IMPLEMENTS semantics. This is the canonical seed dataset for Tracera's own dog-food project in AgilePlus.

Functional Requirements ​

Title: Canonical Requirement / Artifact / TraceLink value objects with ISO-29148-aligned vocabulary

Description: The system shall expose a canonical domain layer (tracertm.models.trace_link) that defines TraceLinkType (SATISFIES, VERIFIES, IMPLEMENTS, DERIVES_FROM, REFINES, CONFLICTS_WITH, DUPLICATES), ArtifactKind (REQUIREMENT, DESIGN, CODE, TEST, EVIDENCE, RISK, RATIONALE), and lightweight Pydantic value objects (TraceLink, Requirement, Artifact) used at API, RAG, and pipeline boundaries.

Acceptance Criteria:

  • TraceLinkType enum values match Neo4j relationship labels exactly (SCREAMING_SNAKE).
  • ArtifactKind partitions Items into ISO 29148 / DO-178C traceability roles.
  • Pydantic models are wire-format-clean (JSON-serialisable, no ORM dependencies).
  • Neo4jSchema provides declarative Cypher constraints and index declarations.

Traceability:

  • PR: #458 (feat(trace-link): canonical domain + Neo4j schema)
  • Source: src/tracertm/models/trace_link.py
  • Alembic: 062_add_trace_link_fields.py

Title: Persist and query trace links with miner confidence score and natural-language rationale

Description: Every trace link shall carry a confidence float in [0.0, 1.0] (default 1.0 for human-curated links) and an optional rationale text field. The repository shall expose a list_with_confidence query supporting filter-by-confidence thresholds for downstream RAG and explainability layers.

Acceptance Criteria:

  • links.confidence column has DB-level CHECK constraint [0.0, 1.0].
  • links.rationale is nullable TEXT.
  • LinkRepository.create() rejects out-of-range confidence with ValueError.
  • list_with_confidence query is exposed and tested.
  • Indexes: idx_links_confidence, idx_links_project_type_confidence.

Traceability:

  • PR: #460 (feat(link-repository): persist confidence + rationale + list_with_confidence)
  • Source: src/tracertm/repositories/link_repository.py
  • Tests: tests/unit/repositories/test_link_repository.py, tests/unit/repositories/test_link_repository_comprehensive.py
  • Alembic: 062_add_trace_link_fields.py

FR-TRC-003 — Neo4j Trace-Graph Projection Writer ​

Title: Idempotent Neo4j writer for Requirement / Artifact / TraceLink graph projection

Description: The system shall provide tracertm.storage.neo4j_trace_link_writer with idempotent MERGE-based writers (write_requirement, write_artifact, write_link) and an apply_schema bootstrap that creates Neo4j constraints and indexes. Writers must be safe to call multiple times without creating duplicates.

Acceptance Criteria:

  • All writes use MERGE (idempotent) not CREATE.
  • apply_schema creates uniqueness constraints and indexes declared in Neo4jSchema.
  • Integration tests pass against a real Neo4j 5 instance via testcontainers.
  • Module is skipped gracefully when neo4j driver or testcontainers is absent.

Traceability:

  • PR: #461 (feat(neo4j): idempotent TraceLink projection writer)
  • Source: src/tracertm/storage/neo4j_trace_link_writer.py (inferred)
  • Tests: tests/integration/storage/test_neo4j_trace_link_writer.py

FR-TRC-004 — Forward and Reverse Impact Analysis via Cypher ​

Title: REST endpoints for Cypher-powered forward/reverse artifact impact traversal

Description: The API shall expose two endpoints (GET /impact/forward/{artifact_id} and GET /impact/reverse/{artifact_id}) that traverse the Neo4j trace-link graph using multi-hop Cypher queries. Forward impact returns all downstream artifacts affected by a change; reverse impact returns all upstream artifacts (requirements, specs) that led to a given artifact.

Acceptance Criteria:

  • Forward traversal: MATCH (src)-[l*1..]->(affected) collects all reachable downstream nodes.
  • Reverse traversal: MATCH (affected)-[l*1..]->(src) collects upstream chain.
  • Response includes id, project_id, kind, title, external_id, link_types.
  • Endpoints are wired into FastAPI router with proper async Neo4j driver dependency injection.
  • Handler correctly closes driver after each request.

Traceability:

  • PR: #462 (feat(impact-api): Cypher forward/reverse impact analysis endpoints)
  • Source: src/tracertm/api/handlers/impact.py
  • Tests: tests/integration/graph/test_cypher_impact_api.py

FR-TRC-005 — Authentication with DB Account Lookup ​

Title: Auth handler resolves authenticated identities against the accounts database table

Description: Upon successful OAuth/device-code authentication, the system shall look up the authenticated user's account record in the PostgreSQL accounts table via AccountRepository, rather than relying solely on the identity provider's token claims. System admin privileges are determined by matching the email against the TRACERTM_SYSTEM_ADMIN_EMAILS environment variable (comma-separated).

Acceptance Criteria:

  • AccountRepository is called post-token-verification to resolve the local account record.
  • Missing account records result in a well-formed 401/403 (not a 500).
  • System admin cache (_admin_emails_cache) is populated from env var at startup.
  • Device Authorization Flow (RFC 8628) is supported alongside standard OAuth.

Traceability:

  • PR: #463 (feat(auth): implement DB account lookup, closes #223)
  • Source: src/tracertm/api/handlers/auth.py, src/tracertm/repositories/account_repository.py
  • Tests: tests/unit/repositories/test_account_repository.py, tests/unit/api/test_authentication.py

FR-TRC-006 — Spatial GiST Index for Graph Viewport Queries ​

Title: PostgreSQL GIST index on item (position_x, position_y) for O(log n) viewport range queries

Description: Graph items with positional coordinates shall be indexed using a PostgreSQL GIST index (idx_items_spatial) over a box(point(position_x, position_y), ...) expression, enabling sub-linear rectangular range queries for graph viewport/frustum culling without full-table scans.

Acceptance Criteria:

  • items.position_x and items.position_y columns exist (NUMERIC 10,2, default 0).
  • GIST index idx_items_spatial is created with a WHERE deleted_at IS NULL partial filter.
  • Migration is idempotent (uses CREATE INDEX IF NOT EXISTS and ADD COLUMN IF NOT EXISTS).
  • Index is used by the query planner for bbox queries (verified via EXPLAIN ANALYZE).

Traceability:

  • PR: #464 (perf: spatial index for edge midpoint distance queries)
  • Source: alembic/versions/054_add_spatial_gist_index.py

FR-TRC-007 — UICodeTracePanel Live API Integration ​

Title: UICodeTracePanel React component wired to live traceability chain API

Description: The UICodeTracePanel component shall fetch live traceability chain data from the backend API (not mock/stub data), displaying the full UI→code→requirement linkage for any selected artifact. The panel shall show loading states, support CanonicalConcept, CanonicalProjection, CodeReference, and EquivalenceStrategy typed data from @tracertm/types.

Acceptance Criteria:

  • Component imports from @tracertm/types (not local stubs).
  • API fetch uses the project's shared API client (no raw fetch with hardcoded URLs).
  • Loading, error, and empty states are handled.
  • Integration test (UICodeTracePanel.integration.tsx) exercises the live API path.

Traceability:

  • PR: #465 (feat: wire UICodeTracePanel to live API, closes #226)
  • Source: frontend/apps/web/src/components/graph/UICodeTracePanel.tsx
  • Tests: frontend/apps/web/src/components/graph/UICodeTracePanel.integration.tsx

FR-TRC-008 — MCP Auth / Config / DB Contract Tests ​

Title: FastMCP server auth, config, and database tool functions verified by contract tests

Description: The MCP tool layer (tracertm.mcp.tools.auth_config_db) shall be covered by contract tests verifying auth_status, auth_logout, config_get, config_set, config_list, config_unset, and db_init functions in isolation, using a lightweight stub for tracertm.mcp.core to avoid triggering the full MCP boot sequence during test collection.

Acceptance Criteria:

  • All seven tool functions have at least one test assertion.
  • Core MCP bootstrap is fully stubbed (@mcp.tool() becomes a pass-through decorator).
  • Tests are importable and runnable in unit-test context (no network/DB required).
  • Tests are collected under tests/mcp/test_auth_config_db.py.

Traceability:

  • PR: #466 (fix(mcp): implement auth/config/db contract tests, closes #232)
  • Source: src/tracertm/mcp/tools/auth_config_db.py (inferred), src/tracertm/mcp/auth.py
  • Tests: tests/mcp/test_auth_config_db.py

FR-TRC-009 — Live Comment Submission in CommentsTab ​

Title: CommentsTab UI component submits comments to the live backend API

Description: The CommentsTab component shall POST new comments to the backend item_comments REST endpoint and optimistically update the UI on success. The item_comments table shall persist item_id, author_id, author_name, content, edited, created_at, and updated_at.

Acceptance Criteria:

  • POST to /api/items/{item_id}/comments creates a persisted record.
  • Comment appears in the thread without a full page reload.
  • item_comments table created by alembic revision 063_add_item_comments.
  • Author attribution uses the authenticated session's identity.

Traceability:

  • PR: #469 (feat(comments): live comment submission in CommentsTab, closes #225)
  • Source: frontend/apps/web/src/ (CommentsTab component), src/tracertm/api/routers/comments.py
  • Alembic: 063_add_item_comments.py

FR-TRC-010 — E2E Project Lifecycle Test Against Real Backend ​

Title: End-to-end project lifecycle test exercises real FastAPI app via HTTPX ASGI transport

Description: The E2E test suite shall include a test_project_lifecycle_roundtrip test that exercises a full create→list→item→update→link→delete→404 cycle against a real in-process FastAPI application wired to the test database engine via HTTPX ASGI transport (no mocks for business logic).

Acceptance Criteria:

  • Test uses test_db_engine fixture with real SQLAlchemy repositories.
  • HTTP transport is HTTPX ASGI (real HTTP semantics, no mock client).
  • Auth guard is a fixed-identity stub (not real WorkOS).
  • All lifecycle steps assert correct HTTP status codes and response bodies.
  • Test is marked @pytest.mark.integration @pytest.mark.slow.
  • Passes in under 30 seconds on local hardware.

Traceability:

  • PR: #470 (feat(e2e): real backend fixture in project lifecycle test, closes #230)
  • Source: tests/e2e/test_project_lifecycle.py

FR-TRC-011 — Requirement Miner: Extract Candidate Requirements from Source Artifacts ​

Title: Heuristic requirement miner with confidence scoring and embedding hook

Description: The system shall provide a requirement_miner service that, given source text and/or file paths, extracts candidate Requirement statements by detecting (a) requirement-language modal verbs (shall/must → 0.90, should/will → 0.70, may/can → 0.50), (b) explicit FR/NFR/REQ/SYS/SRS identifier tags (→ 0.95), and (c) TODO/SPEC/FIXME/@requirement code-comment markers (→ 0.60). Candidates are emitted as CandidateRequirement records carrying id, text, confidence, source_ref, and tags. The service is a pure function (no DB access); an embedding hook (_embedding_hook) is stubbed for future RAG integration. The API shall expose a read-only POST endpoint: POST /api/v1/mine/requirements.

Acceptance Criteria:

  • mine_text(text) returns CandidateRequirement list sorted descending by confidence.
  • mine_files(paths) reads real files and merges results; missing files are silently skipped.
  • Requirement-language sentence extracted as candidate; non-requirement prose not flagged.
  • FR/NFR-pattern detected at confidence 0.95; tags populated in CandidateRequirement.tags.
  • Confidence ordering: explicit tag (0.95) > shall/must (0.90) > should/will (0.70) > may/can (0.50) > marker (0.60).
  • Empty input returns empty list.
  • MinerConfig.deduplicate de-duplicates by normalised text when True.
  • MinerConfig.min_confidence filters candidates below threshold.
  • POST /api/v1/mine/requirements accepts {text, paths, min_confidence, include_markers, deduplicate} and returns {total, candidates[]}.
  • 26 unit tests pass with no live DB or graph required.

Traceability:

  • Branch: feat/requirement-miner
  • Source: src/tracertm/services/requirement_miner.py, src/tracertm/api/routers/mine.py
  • Tests: tests/unit/services/test_requirement_miner.py (26 tests)
  • Closes: FR-TRC-011

Title: Detect near-duplicate requirements and mutually-exclusive TraceLinks

Description: The system shall provide a dup_conflict_detector service that, given an in-memory collection of Artifact/Requirement objects and TraceLink objects, identifies (a) near-duplicate requirements using token-Jaccard similarity (stdlib difflib-compatible, no external NLP dependency) above a configurable threshold (default 0.75), and (b) conflicting TraceLinks where the same ordered (source, target) artifact pair carries mutually-exclusive link types (e.g. CONFLICTS_WITH co-existing with SATISFIES, VERIFIES, IMPLEMENTS, DERIVES_FROM, or REFINES). Both detectors are pure functions over in-memory collections (no live DB access required). The API shall expose two read-only POST endpoints: POST /api/v1/quality/duplicates and POST /api/v1/quality/conflicts.

Acceptance Criteria:

  • detect_duplicate_requirements(artifacts, threshold) returns DuplicateFinding list sorted descending by similarity.
  • detect_conflicting_links(links) returns ConflictFinding list for all (source, target) pairs with cooperative + CONFLICTS_WITH link types.
  • Threshold outside (0.0, 1.0] raises ValueError.
  • POST /api/v1/quality/duplicates and POST /api/v1/quality/conflicts accept JSON bodies and return findings with confidence.
  • 22 unit tests pass with no live DB or graph required.

Traceability:

  • Branch: feat/dup-conflict-detector
  • Source: src/tracertm/services/dup_conflict_detector.py, src/tracertm/api/routers/dup_conflict.py
  • Tests: src/tracertm/services/test_dup_conflict_detector.py (22 tests)
  • Closes: FR-TRC-012

FR-TRC-018 — Canonical Typed-Graph Schema Contract ​

Title: Single canonical node/edge-kind schema contract; GraphPort is the sole graph writer

Description: The platform shall define one canonical typed-graph schema (node kinds: Requirement, Spec, ADR, Code, Test, PR, Commit, Release, Repo, Team, Portfolio, OKR, Roadmap, Evidence, Journey, Keyframe; edges: TRACES_TO, VERIFIES, IMPACTS, DEPENDS_ON, DUPLICATES, IMPLEMENTS, COVERS, EVIDENCES, BELONGS_TO, RELEASES) and route all Neo4j writes through a single GraphPort. No service may write Neo4j directly. Epic: EPIC-TRC-A-SPINE.

Acceptance Criteria:

  • Node/edge kinds are enumerated in one shared contract (HexaKit canonical ports + Python mirror).
  • All existing trace/impact services write via GraphPort.
  • Schema drift is impossible: writes outside the contract are rejected.

Traceability:

  • Epic: EPIC-TRC-PLATFORM / EPIC-TRC-A-SPINE
  • Blueprint: docs/TRACERA_PLATFORM_RND.md §3.3
  • Status: PLANNED (Phase 0)

FR-TRC-019 — Pluggable Agreement Scorer Port ​

Title: ScorerPort with Jaccard / SentenceTransformer / SigLIP / VLM strategies

Description: The platform shall expose a ScorerPort strategy interface for requirement↔artifact agreement scoring, with interchangeable implementations: lexical (Jaccard), text-embedding (SentenceTransformer), visual-embedding (SigLIP), and blind-vs-intent VLM. Pillars A and C consume the same port.

Acceptance Criteria:

  • Scoring strategy is selectable at call site without changing callers.
  • Each scorer returns a normalized confidence in [0.0, 1.0] + rationale.

Traceability:

  • Epic: EPIC-TRC-A-SPINE
  • Blueprint: docs/TRACERA_PLATFORM_RND.md §3.2
  • Status: PLANNED (Phase 1)

FR-TRC-020 — Blind-vs-Intent Visual Verification ​

Title: VLM proof that running code matches the requirement, with keyframe evidence

Description: The Evidence & Verification engine shall capture journey keyframes/recordings (via phenotype-journeys behind EvidenceRunnerPort), store them in MinIO as Evidence/Keyframe graph nodes, and produce a blind-vs-intent VLM verdict asserting whether the running code satisfies the requirement. Verdicts attach to the graph via VERIFIES edges.

Acceptance Criteria:

  • Evidence artifacts are content-addressed in MinIO and linked from graph nodes.
  • A verdict (pass/fail + rationale + confidence) is recorded per requirement under test.
  • phenotype-journeys is wrapped, not re-implemented.

Traceability:

  • Epic: EPIC-TRC-C-VERIFY
  • Blueprint: docs/TRACERA_PLATFORM_RND.md §4 (Phase 2)
  • Status: PLANNED (Phase 2)

FR-TRC-021 — Program Management via AgilePlus PmEnginePort ​

Title: Portfolios / OKRs / roadmaps / releases as first-class graph nodes via AgilePlus

Description: Pillar B shall promote agileplus_adapter into a PmEnginePort backed by AgilePlus (Rust), projecting portfolios, OKRs, roadmaps, and releases as canonical graph nodes with a PG-backed compliance/audit trail. AgilePlus is wrapped as the PM engine, not duplicated.

Acceptance Criteria:

  • Portfolio/OKR/Roadmap/Release exist as graph node kinds with TraceLinks to requirements.
  • AgilePlus is consumed via a contract port (gRPC/HTTP), not re-implemented in Python.

Traceability:

  • Epic: EPIC-TRC-B-PM
  • Blueprint: docs/TRACERA_PLATFORM_RND.md §4 (Phase 3)
  • Status: PLANNED (Phase 3)

FR-TRC-022 — Multi-Repo Org Intelligence via RegistryPort ​

Title: Org-wide repo/ecosystem graph + dependency/dup rationalization view

Description: Pillar D shall wrap phenotype-registry (ECOSYSTEM_MAP / RATIONALIZATION_PLAN) behind a RegistryPort, ingesting the org repo graph and surfacing cross-repo dependency and duplication rationalization as a Tracera SPA view.

Acceptance Criteria:

  • Repo / Team nodes and DEPENDS_ON / DUPLICATES edges populate the org graph.
  • Rationalization findings render in the SPA org-map workspace.
  • phenotype-registry is wrapped, not re-implemented.

Traceability:

  • Epic: EPIC-TRC-D-ORG
  • Blueprint: docs/TRACERA_PLATFORM_RND.md §4 (Phase 4)
  • Status: PLANNED (Phase 4)

Non-Functional Requirements ​

NFR-TRC-001 — Spatial Index Query Performance ​

Title: Graph viewport queries execute in O(log n) via GIST index

Description: Rectangular range queries over item positions (graph viewport panning/zooming) shall use the idx_items_spatial GIST index and must not degrade to sequential scans on datasets of 10,000+ items.

Evidence:

  • GIST index created in alembic/versions/054_add_spatial_gist_index.py.
  • WHERE deleted_at IS NULL partial filter reduces index size by excluding soft-deleted items.
  • PR #464 description: "spatial index for edge midpoint distance queries".

NFR-TRC-002 — Auth Contract Correctness (Fail-Safe Defaults) ​

Title: Authentication layer has no silent failure modes; missing accounts produce explicit errors

Description: Auth failures (missing account record, invalid token, revoked device code) shall produce deterministic HTTP error responses (401/403), never 500 errors or silent pass-throughs.

Evidence:

  • WORKOS_HANDLER_ERRORS and TOKEN_EXTRACTION_ERRORS tuples in auth.py enumerate all swallowed exception types explicitly.
  • Contract tests in tests/mcp/test_auth_config_db.py verify auth tool behavior under error conditions.
  • Unit tests: tests/unit/api/test_authentication.py, tests/unit/api/test_authorization_scenarios.py.

NFR-TRC-003 — E2E Tests Exercise Real Backend (No Mock Bypass) ​

Title: Integration-marked E2E tests must use real repositories, not mock client stubs

Description: Tests marked @pytest.mark.integration shall exercise the real SQLAlchemy repository layer and real HTTP semantics. MSW / mock-client patterns are acceptable only in frontend unit tests.

Evidence:

  • tests/e2e/test_project_lifecycle.py uses HTTPX ASGI transport with test_db_engine (PR #470).
  • tests/integration/storage/test_neo4j_trace_link_writer.py uses testcontainers-neo4j for real Neo4j (PR #461).
  • tests/integration/graph/test_cypher_impact_api.py is marked integration + slow with live Neo4j requirement.

NFR-TRC-004 — Neo4j Projection Idempotency ​

Title: All Neo4j writes are idempotent (MERGE semantics)

Description: The Neo4j trace-link writer shall use MERGE for all node and relationship creation, ensuring that replaying the ingestion pipeline does not create duplicate nodes or relationships.

Evidence:

  • write_requirement, write_artifact, write_link in tracertm.storage.neo4j_trace_link_writer use MERGE (confirmed in tests/integration/storage/test_neo4j_trace_link_writer.py).
  • apply_schema uses CREATE CONSTRAINT IF NOT EXISTS and CREATE INDEX IF NOT EXISTS.

NFR-TRC-005 — Confidence Column DB Integrity Constraint ​

Title: links.confidence enforced at DB level; application-layer validation is redundant defence

Description: The confidence column on the links table shall have a CHECK (confidence >= 0.0 AND confidence <= 1.0) constraint so out-of-range values are rejected even if application code is bypassed.

Evidence:

  • Alembic: ALTER TABLE links ADD CONSTRAINT links_confidence_range CHECK (...) in 062_add_trace_link_fields.py.
  • LinkRepository.create() also validates before INSERT (defence-in-depth).

NFR-TRC-006 — MCP Server Boot Isolation in Unit Tests ​

Title: MCP tool unit tests must not trigger the full FastMCP server boot sequence

Description: Contract tests for MCP tool functions shall stub tracertm.mcp.core before any import of tool modules, ensuring test collection completes in under 5 seconds without network access.

Evidence:

  • _stub_mcp_core() pattern in tests/mcp/test_auth_config_db.py inserts a ModuleType stub into sys.modules before tool module import.

NFR-TRC-007 — Traceability Model Compliance (ISO 29148 / DO-178C Alignment) ​

Title: TraceLinkType vocabulary is aligned with ISO 29148 §5.2.6 and DO-178C Table A-3

Description: The canonical link-type vocabulary shall be documented with its ISO/DO-178C semantic mapping, enabling future compliance audits against aerospace and safety-critical standards.

Evidence:

  • Docstring in TraceLinkType class (src/tracertm/models/trace_link.py) provides per-value ISO 29148 §5.2.6 + DO-178C Table A-3 mapping.
  • ArtifactKind docstring references ISO 29148 / DO-178C / IEC 62304 style traces.

Gap Analysis / PLANNED Forward Requirements ​

IDTitleStatusNotes
FR-TRC-011RAG-layer traceability query / requirement minerSHIPPEDHeuristic miner (modal verbs, FR/NFR tags, spec markers) + confidence scoring; requirement_miner.py; endpoint POST /api/v1/mine/requirements; PR: feat/requirement-miner
FR-TRC-012Automated duplicate / conflict detection via TraceLink minerSHIPPEDToken-Jaccard duplicate detector + structural conflict detector; dup_conflict_detector.py; endpoints POST /api/v1/quality/duplicates + /conflicts; PR: feat/dup-conflict-detector
FR-TRC-013Bulk TraceLink ingestion from external sources (Jira, GitHub Issues)SHIPPEDBranch feat/trc013-bulk-tracelink-ingestion; sources: src/tracertm/services/github_import_service.py, src/tracertm/services/jira_import_service.py, src/tracertm/api/routers/ingest.py; validated with 28 unit tests; uv run python -c "import tracertm"
FR-TRC-014Traceability coverage matrix export (CSV/JSON/PDF)SHIPPEDPure-function coverage_matrix_service.py; rows=requirements, cols=impl/test + ArtifactKind buckets; endpoint GET /api/v1/coverage/matrix?format=csv|json; CSV RFC 4180 + pipe-separated multi-artifact cells; PDF deferred (heavy dep); 25 unit tests; PR: feat/coverage-matrix-export
FR-TRC-015Graph-level impact blast-radius scoring (risk-weighted path analysis)SHIPPEDPure-function blast_radius_service.py; BFS over Requirement/Artifact/TraceLink graph with per-ArtifactKind risk weights + link-confidence multipliers; score 0–100 with LOW/MEDIUM/HIGH/CRITICAL tiers; endpoint GET /api/v1/impact/blast-radius/{artifact_id}; 20 unit tests; PR: feat/trc015-blast-radius-scoring
FR-TRC-016AgilePlus integration — push Requirements / TraceLinks to AgilePlus projectSHIPPEDbranch feat/trc016-agileplus-push; tests/unit/services/test_agileplus_adapter.py (17 tests); src/tracertm/adapters/agileplus_adapter.py; endpoint POST /api/v1/integrations/agileplus/push; .env.example AgilePlus config
FR-TRC-017Traceability coverage / health scoring over Requirement-Artifact-TraceLink graphSHIPPEDPure-function traceability_score_service.py; metrics: impl_coverage, test_coverage, orphan_req_pct, orphan_art_pct, avg_confidence, composite 0-100; endpoint GET /api/v1/quality/score; 19 unit tests; PR: feat/quality-scoring
NFR-TRC-008Link confidence index selectivity target ≥ 90% for miner-generated linksPLANNEDBaseline TBD once miner ships
NFR-TRC-009Neo4j projection sync latency < 500 ms p99 for single-link writesPLANNEDNo SLA defined yet
NFR-TRC-010All graph writes go through exactly one contract; no service writes Neo4j directlyPLANNEDBlueprint §3.2; EPIC-TRC-A-SPINE
NFR-TRC-011Wrap-over-handroll: Authvault/AgilePlus/phenotype-journeys/phenotype-registry/HexaKit consumed via ports, never re-implementedPLANNEDBlueprint §2
NFR-TRC-012Self-hosting: every shipped capability traces Requirement→Code→Test→PR in Tracera's own graphPLANNEDBlueprint §7

Requirement → PR Traceability Map (Summary) ​

RequirementShipped PRsKey Tests
FR-TRC-001#458test_neo4j_trace_link_writer.py
FR-TRC-002#460test_link_repository*.py
FR-TRC-003#461test_neo4j_trace_link_writer.py
FR-TRC-004#462test_cypher_impact_api.py
FR-TRC-005#463test_account_repository.py, test_authentication.py
FR-TRC-006#464alembic 054
FR-TRC-007#465UICodeTracePanel.integration.tsx
FR-TRC-008#466test_auth_config_db.py
FR-TRC-009#469alembic 063
FR-TRC-010#470test_project_lifecycle.py
FR-TRC-011feat/requirement-minertest_requirement_miner.py (26 tests)
FR-TRC-012feat/dup-conflict-detectortest_dup_conflict_detector.py (22 tests)
FR-TRC-014feat/coverage-matrix-exporttest_coverage_matrix_service.py (25 tests)
FR-TRC-015feat/trc015-blast-radius-scoringtest_blast_radius_scoring.py (20 tests)
FR-TRC-016feat/trc016-agileplus-pushtest_agileplus_adapter.py (17 tests)
FR-TRC-017feat/quality-scoringtest_traceability_score_service.py (19 tests)
NFR-TRC-001..007#458–#470(see individual evidences above)

Released under the MIT License.

Copyright © 2026 Phenotype