2
Upgrade actions
1 urgent review + 1 planned upgrade
Sample deliverable · 5 November 2026
Your lifecycle review.
From evidence to action.
Illustrative report only. All products, dates, assets, support evidence and customer decisions below are fictional. These examples demonstrate the reporting rules; they are not verified vendor lifecycle statements or actual customer findings.
Example organisation · Inventory snapshot: 4 November 2026 · Support review: 5 November 2026. Counts below refer to six grouped findings, not unique assets.
2
Evidence gaps
1 entitlement + 1 missing policy
2
Other dispositions
1 monitored + 1 accepted exception
Actions and supporting evidence
| Action / component | Support status / deadline | Affected systems / owner | Next step / evidence |
|---|---|---|---|
| Urgent review Example Runtime 4.2 | Upstream ended; no alternate support evidenced 2026-10-01 | portal-base:v7 + 12 deployments Platform | Confirm exposure; update base image and redeploy within an owner-agreed window. DEMO-01: simulated upstream policy; checked 2026-11-05 |
| Plan upgrade Example Database 8 | Applicable support ending 2027-01-31 | 3 database instances Data team | Test supported release; schedule migration before support ends. DEMO-02: simulated vendor policy; checked 2026-11-05 |
| Monitor Example Package 2.0 on Example Linux 8 | Upstream ended; distribution support verified in this scenario 2028-05-31 | 8 internal servers IT | Continue distribution updates; retain package/channel evidence. DEMO-03: simulated distribution policy and entitlement |
| Review evidence Example OS 2012 | Standard support ended; claimed third-party support unverified Unknown | 2 legacy servers IT | Obtain contract scope and covered build before treating as supported. DEMO-04: fictional customer statement; no supporting contract Not accepted as verified support |
| Review evidence @example/internal-utils 1.8 | Support status unknown; no published policy Unknown | 6 application inventories App team | Ask maintainer for support policy; do not invent an expiry date. DEMO-05: fictional package with no lifecycle evidence |
| Accepted exception Example Engine 3 | Support ended; risk accepted until review 2026-06-30 | 1 internal worker Operations | Review isolation and migration progress before exception expiry. DEMO-06: simulated vendor policy and customer decision EX-001; approver: fictional service owner; review/expiry 2026-12-01; controls: isolated network, restricted access |
Image relationship
In this fictional scenario, the inventory links portal-base:v7 to 12 deployments. Upgrade the image and the existing deployments: changing the image alone does not update running systems. Without those customer-supplied relationships, the report would show the affected image and mark deployment reach unknown.
Exception register
EX-001 keeps the underlying unsupported status visible. Fictional service owner approved temporary acceptance, Operations owns remediation, and isolated networking plus restricted access are recorded as customer-declared controls. Review and expiry: 1 December 2026. Acceptance is not evidence of vendor support.
Coverage and freshness
This sample presents six deliberately selected scenarios, not a complete inventory. A live report will reconcile all supplied rows into confirmed, unknown and excluded records, and show stale inventories separately. No deployment changes after the snapshot are assumed known.
Source register
DEMO-01 through DEMO-06 are simulated evidence references for this sample only. Live reports replace them with retrievable vendor/distribution URLs or customer evidence references, verified release scope, date checked and matching confidence. Customer assertions remain distinguishable from reviewed evidence.