rapp-playwright/history/2026-10-13-2142-intent-scope-assessment.md

INTENT against SCOPE — 2026-10-13 21:42 Europe/Berlin

There is substantial new progress since the previous assessment. The release is now deployed as a Railiance pilot, and discovery publishes the verified local provider. The largest remaining gap has narrowed from deployment/admission to real self-service consumer access. Full INTENT is still not met.

Verified progress

• Fresh cluster readback: playwright Deployment 1/1 Ready on the published immutable 0.1.0 image; artifact PVC Bound at 2Gi; playwright-consumers bound to the namespace Role.
• Platform runtime evidence: 14 responsive/keyboard steps passed, four PNGs, six negative/health checks, and same-image restart. Recomputed all four retained PNG hashes and matched both original and post-restart download receipts.
• Thirteen native RBAC checks are recorded by platform. The access path used administrator impersonation, so these prove permission/runtime behavior and do not prove a real consumer can authenticate.
• Live federation now publishes one browser capability at D3/A5/C2/R2 with immutable client/contract/release links and executable local instructions. REUSE-WP-0024 is finished; its recorded relevance fix returns browser first with a reuse recommendation. The former source-only discovery gap is resolved.

The retained readback contains current cluster/federation observations and reviewed platform receipts. Platform source is commit d303c99e3be993ffa989bc9ba3d7b471903858ce; reuse source is a6da9f2c5c0cb8a69ddf4ea2386e79699a90c2e1. Older assessments remain dated evidence.

Most important gaps

1. Human and coding-agent onboarding is not operational. Group eligibility is decided and the binding exists, but dedicated registrations, native JWT authentication, per-caller API transport and governed credential delivery remain pending. Platform prepared a setup/verification helper and owner handoffs. RPF-WP-0056-T03 owns actual identity integration and live receipts; T06 awaits Custodian coordination. No further membership choice is needed. Completion requires real human and agent trials without administrator impersonation, plus renewal/revocation and native authentication negatives.
2. Managed acceptance and operational proof remain incomplete. The running pilot passes operator tests and completed-artifact recovery. It has no real consumer-network acceptance, abrupt-interruption recovery evidence or actual cross-version rollback. Only one release exists; same-image restart must not be called version rollback. These stay in RAPP-PLAYWRIGHT-WP-0004-T01.
3. Discovery needs the final managed-availability update. A5 local-provider publication is verified. Its summary still says admission is pending even though the pilot is now admitted; it should distinguish deployed pilot from incomplete consumer access. T03 awaits accepted native consumer receipts before any general managed-availability promotion.
4. Consumer-specific acceptance remains with content-explorer. The pinned OnCo home/skip-link smoke is demonstrated locally. Broader routes, graph/search behavior and visual acceptance remain outside that evidence. Provider progress does not close CONTENT-WP-0000-T04.

Workplan and scope disposition

WP-0001–0003 remain finished. WP-0004-T02 is done; T01 and T03 retain explicit waits for the narrower remaining owner outcomes. SCOPE.md, README, the declaration note and workplan records now reflect the deployed pilot and published A5 capability. The declaration remains draft pending full managed consumer acceptance. No browser implementation or running workload was changed in this reconciliation, and no additional browser tests were necessary to verify these documentation changes.