[OpenSpec] operations-technology-components #1129

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• ✅ Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

Stackiq records applications, their versions, suites and the connections between them. It cannot record what they run on: the database server, the virtual machine, the laptop fleet, the network switch. A municipal information manager who hears that PostgreSQL 13 is out of support cannot find which of their applications depend on it. This change adds technology components owned by an organisation, with a class, a lifecycle and relations to each other, links an application in use to the components it runs on, and gives each component its end of support date, copied from the end-of-life feed when the component is a known software version. Stackiq records these; it does not discover them.

Specs

• 📄 technology-components

Tasks

• Implement
• Test (PHPUnit tests/Unit/Settings/TechnologyComponentDeclarationTest.php)
• Implement
• Test (Playwright tests/e2e/spec-coverage/technology-components.spec.ts)
• Implement
• Test (vitest tests/vitest/technologyLifecycle.spec.js and Playwright tests/e2e/spec-coverage/technology-components.spec.ts)
• Implement
• Test (PHPUnit tests/Unit/Service/EolSyncServiceTest.php)
• Implement
• Test (Playwright tests/e2e/spec-coverage/technology-components.spec.ts against the demo data)

Design

See design.md for technical design details.

Synced from openspec/changes/operations-technology-components by OpenSpec workflow
App: stackiq