Project Detail
A focused project view for environment, webhook targets, serving keys, usage concentration, and promotion readiness.
The project detail should make the environment boundary obvious before anyone touches the serving key.
Keys and endpoints should stay visible from the project lane that owns them.
The operator should know whether the project is still experimental or ready to move forward.
That keeps project ownership understandable as usage grows and more keys or reports get attached to the same lane.
When one of those assets drifts, the project page should make the problem visible without sending the operator through three different settings pages.
That gives technical and compliance owners one shared answer when they ask whether the lane is ready to move forward.
{
"project_id": "proj_sandbox_workforce_review",
"environment": "sandbox",
"serving_keys": 2,
"webhook_targets": 3,
"threshold_alerts": 1,
"promotion_state": "ready_for_review"
}Project detail should keep environment, serving assets, and promotion readiness visible in one lane.
The detail lane should show environment before the operator reaches for any live key or webhook.
Endpoint count should be visible alongside usage and serving assets.
Project health should remain visible before the project goes to production review.
Key count belongs on the project detail page so rotation and promotion remain tied together.
Operators should know whether the sandbox lane is still light or nearing production-like load.
This is the operational answer the workspace needs before moving the project forward.
A project detail page should open on the actual environment boundary, current workload, and traffic shape so teams know whether they are looking at sandbox experimentation or production behavior.
That keeps project ownership understandable as usage grows and more keys or reports get attached to the same lane.
Webhook targets, serving keys, threshold alerts, and report jobs all belong to the project detail surface because they are what make the project operational.
When one of those assets drifts, the project page should make the problem visible without sending the operator through three different settings pages.
The project page should show whether the project is still being validated, ready for production review, or already carrying live protected usage.
That gives technical and compliance owners one shared answer when they ask whether the lane is ready to move forward.