d6521923fe
Apply stellaopsGlossaryTooltip directive on vex-hub dashboard, trust-admin, and policy-decisioning overview with auto-detect mode for security terms (VEX, CVE, SBOM, DSSE, etc.). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Feature Catalog
Structured inventory of all Stella Ops features, organized for verification tracking.
Updated: 2026-02-25
Summary
| Directory | Meaning | Count |
|---|---|---|
checked/ |
Features verified by code review + tests | 1,118 |
unimplemented/ |
Partially implemented / planned features | 35 |
dropped/ |
Features not found in source code | 22 |
| Total | 1,175 |
Note: Verification evidence (QA run artifacts) is archived in
docs-archived/qa/feature-checks/runs/. The canonical feature summary is indocs/FEATURE_MATRIX.md.
How to Use
- To understand a feature: Read the file in
checked/<module>/— it contains implementation details, key files, classes, and services. - To understand what was dropped: Read files in
dropped/for context on features that were planned but not implemented. - To see unfinished work: Check
unimplemented/<module>/for features with partial scaffolding.
File Format
Each feature file follows a standard template:
Checked (VERIFIED)
# Feature Name
## Module / ## Status / ## Description
## Implementation Details (key files, classes, services)
## E2E Test Plan (setup, action, verification steps)
## Verification (tier results, timestamps)
Dropped (NOT_FOUND)
# Feature Name
## Status / ## Description
## Why Not Implemented / ## Source / ## Notes
Source Data
This catalog was built from:
- 270 product advisories (Phase 1)
- 1,343 sprint archives (Phase 2)
- CLI + Web source code scan (Phase 3)
- Two deduplication passes reducing 1,600 entries to 1,185
- 73 SPRINT_20260208 sprints completing all PARTIALLY_IMPLEMENTED features
- Full QA verification pipeline (Feb 2026) moving all features to checked/