Customer Reliability Detail
A full single-subject drill-down with HRS trajectory, consent history, event explanations, export shortcuts, and audit-safe operational context.
The subject page opens on trajectory first so operators can explain the score before they act on it.
Consent timing stays visible on the detail page so operators do not overrun the approved view window.
Recoveries, declines, and consent changes stay in one operator-grade event lane.
The detail lane should explain how the current score formed instead of leaving the operator with one flat number.
Keep identity-backed visibility, scope timing, and audit state visible from the same customer page.
Operators need to see whether the current score is stabilizing, sliding, or recovering, then move straight into the events that explain why.
That is what makes the page useful during underwriting, qualification, or trust review instead of turning it into a decorative analytics chart.
Every export, share, and operator action remains tied to the same approved scope so the page never turns into an unrestricted people-search surface.
That keeps the platform workspace operational instead of forcing teams to rebuild trust decisions from disconnected screens.
{
"subject_id": "subj_1184",
"display_label": "Sovereign Node #1184",
"hrs": {
"current": 812,
"trend": "recovering",
"last_material_change_at": "2026-03-05T14:20:00Z"
},
"trajectory": {
"rise_windows": 4,
"plateau_windows": 2,
"recovery_windows": 1,
"decline_windows": 1
},
"consent": {
"scope": "hrs.lookup.identity.extended",
"granted_at": "2026-01-14T11:08:00Z",
"expiring_at": "2026-04-01T00:00:00Z"
},
"recent_events": [
{ "type": "verified_completion", "at": "2026-03-05T14:20:00Z", "impact": "+14" },
{ "type": "early_release", "at": "2026-02-22T09:11:00Z", "impact": "-8" }
]
}A serious customer page needs trajectory, scope, and event context together so operators can explain the score instead of merely reading it.
Recent verified completions are offsetting one earlier early-release event.
The score held steady before the latest recovery cycle began.
The most recent verified completion is the event currently shaping the rise.
Identity-backed detail remains bounded by the active consent scope.
The timestamp remains visible so operators can explain why the record is available.
Upcoming expiry stays visible before the enterprise loses access unexpectedly.
The subject page should make the safest next export obvious instead of forcing another routing step.
The current cohort context should stay visible so the operator can explain why this subject is open.
Single-subject review needs a named owner before the record turns into a cross-team blind spot.
Most recent movement is still being driven by verified follow-through rather than passive age or decay.
The subject is recovering, but the slope is still softer than the strongest portfolio lane.
Current scope still has strong runway before the portfolio loses access to the identity-backed view.
A clean proof-backed finish raised the subject out of the earlier plateau.
One abandoned commitment still explains the brief downward section in the trend line.
Expanded visibility made the deeper trajectory and event view available to the workspace.
The detail view should open with the current HRS, the active trend, the last material change, and a graph that makes rises, declines, plateaus, and recoveries obvious without flattening the subject into one number.
Operators need to see whether the current score is stabilizing, sliding, or recovering, then move straight into the events that explain why.
The timeline keeps verified completions, early releases, missed commitments, consent changes, and scope-limited reliability events in time order with date filters and operator notes.
That is what makes the page useful during underwriting, qualification, or trust review instead of turning it into a decorative analytics chart.
The subject page keeps the consent timestamp, active scope, identity-matching status, and any upcoming scope expiry visible at all times.
Every export, share, and operator action remains tied to the same approved scope so the page never turns into an unrestricted people-search surface.
The detail view should make the next action obvious: open a scoped export, compare the subject to a saved cohort, review audit history, or return to the wider portfolio.
That keeps the platform workspace operational instead of forcing teams to rebuild trust decisions from disconnected screens.
A single-customer page should still show the subject's current cohort, why the subject is in that lane, and how the current trajectory compares with the surrounding portfolio. That gives teams enough context to explain whether the record is exceptional or representative.
Without that surrounding context, even a detailed graph turns into an isolated story that is harder to operationalize.