shared-resource-model

What problem does it solve?

It prevents inconsistent Kubernetes resource identity, status, facts, links, and projections across Luxury Yacht surfaces, so users don’t see mismatched views of the same object.

Core Features & Use Cases

• Canonical Kubernetes identity: Establishes consistent group/version/kind scoping and cluster-aware references for concrete and event involved-object identities.
• Single-source status presentation: Computes primary status once in the backend and projects it through status/state/presentation fields for consistent UI styling and messaging.
• ResourceLink relationship integrity: Uses safe, display-ready links when sources are incomplete, avoiding unsafe navigation while keeping relationship rendering coherent.
• Parity across consumers: Keeps table rows, stream rows, object panel details, events, and object-map nodes/edges aligned for the same resource family.

Quick Start

Use this shared-resource-model guidance to update identity and presentation logic end-to-end by following the listed backend and frontend entry points and ensuring the projections and tests remain consistent.