Start with existing records
In this design, composable data means connecting the events, jobs, evidence and user-selected preferences already needed by the product. Each record keeps its own owner and purpose. The public article catalog contains editorial content and declared links; it does not need a customer identity graph.
One identity, several reading surfaces
An article has one stable ID and canonical URL. English and Russian companions share that identity. Mirrors may present the same content within Tvijo, DSH and the platform, while relation edges point to real article links. Backlinks are derived from incoming links rather than invented similarity scores.
Keep source verification dates separate from release publication and job completion. Fetch current extension metadata from its release endpoint; do not stamp today onto unchanged evidence. A failed or absent receipt remains visibly unverified.
Consent remains explicit
This graph adds no tracking and changes no data-consent default. Private jobs, terminal paths, credentials and personal preferences do not belong in a public catalog. Use separate access-controlled evidence when a handoff requires private details. The SSP reference inspired linked reading and backlinks; this article and graph are an original implementation.