The three labels do not stack into one claim
The portal keeps three maturity labels, and they are different claims. Available for POC means an evaluation can exercise the capability now, inside the limits written beside it. Coming next means the capability is specified and is not that evaluation’s current surface. Design-partner roadmap means a direction held until evidence and an owner decision promote it. A sentence may mention all three. It may not treat them as one status.
Polish is not a fourth label. A careful page can make a roadmap direction look as finished as an available one. The label remains the claim, and the finish of the page does not promote it. This explainer is safe to bring into a design-partner conversation because the conversation cannot move a label by sounding decided. The label moves when the evidence and the owner decision say so.
Available for POC is Platform Core and GenAI Prompt DLP
The capabilities marked available for a POC evaluation are Platform Core and GenAI Prompt DLP. The crew view names them Core and Sentry. An evaluation can exercise policy, a verdict, and the evidence and audit records around a decision, and it can judge prompt text before submit. Those are the two surfaces. The rest of the crew is not quietly included.
Available still wears the stand-ins. A console session in the evaluation comes from a local password hash, while directory single sign-on remains the identity model this phase does not run. Evidence unwrap uses software officer keys, with hardware tokens absent from the build. Machine certificates come from a software development CA, while the header actor is resolved from the development roster and is not bound to the certificate. Endpoint inventory is a simulated fleet. Evidence at rest for a captured body is AES-256-GCM ciphertext, and a checkpoint is an Ed25519 signature over a record naming the chain head. The available label does not erase any of those limits.
Coming next is AI usage observability, still on metadata
AI usage observability is the capability marked coming next. The crew view names it Cartographer. The specified input is proxy and DNS metadata the estate already has, not the text of a prompt. Any volume shown from this plane in the current build comes from a synthetic log generator, and a real query over those rows still reports a simulated source.
The label carries no date. Coming next is not a quarter and not a month. The page places this capability after the available pair because that is the label, not because a schedule assigned it a slot. An evaluation that needs a live metadata feed does not have one yet. The honest session reads the specification, names the generator, and leaves the capability in the coming-next column until a promotion actually happens.
Roadmap directions wait on evidence and an owner decision
The other named crew directions stay on the design-partner roadmap. They can be discussed as directions, with the workflows and acceptance criteria a partner cares about. They are not demonstrated as Platform Core, and they do not inherit the available-for-POC label by sharing a navigation bar. A sketch that looks complete remains a roadmap item while the label says roadmap.
Promotion is an owner decision taken against evidence. A demonstration that merely looks finished leaves the label where it was. A design-partner discussion can clarify which evidence would matter, and it can clarify who would own the outcome. The discussion is not itself the decision, and it is not a delivery. This explainer can sit in that meeting without being mistaken for the minutes of a commitment.
Reading order is not a calendar
The sequence on the page is a way to keep the three labels from blending. Available work is placed first so an evaluation has a place to start. Coming next follows so it is not mistaken for the start. The roadmap follows both so it is not mistaken for either. A visitor can retell that order without the table: two capabilities to evaluate now, one metadata plane specified next, and the remaining directions held for a partner conversation.
The margin next to that order stays blank. This product does not publish a delivery quarter on these rows. Typing a quarter into a summary, so the page feels planned, creates a date the source never had. Reports copy the label. Where a date would have been an invention, the report leaves the space empty, and the empty space is part of the accuracy.
How to read this
| Read it as | Which means | Do not read it as |
|---|---|---|
| Available for POC | Platform Core and GenAI Prompt DLP | The rest of the crew |
| Coming next | AI usage observability | A delivery quarter |
| Design-partner roadmap | The other directions, until evidence promotes them | A schedule |