Role/Actor Trends by Surface¶
Purpose
Show the latest operational reading of the private portal by role/actor and by surface: services, apps, and applications.
Signal sources¶
This view combines:
docs/internal/runtime-applications-catalog.mddocs/portal/global-vision-role-based-experience.en.mddocs/portal/private-apps-hub.en.mddocs/portal/metrics.en.md
Quick read¶
| Role / actor | Recent trend | Services | Apps | Applications |
|---|---|---|---|---|
Kabehz |
consolidating the private hub and purpose-based navigation | portal, oauth2-proxy, tech-radar | private-apps-hub, enter, govern | atlantyqa-portal, atlantyqa-tech-radar |
L0KY |
gate, review, and merge-evidence priority | github-app-bot, oauth2-proxy, portal | collaborate, govern, measure | atlantyqa-portal, github-app-bot |
AJCG131281 |
guided onboarding, quickstart, and small verifiable execution | portal, tech-radar, open-notebook | enter, learn, measure | atlantyqa-portal, open-notebook |
Trend by surface¶
Services
The most visible signal now is the segmentation of the private portal and the decoupling of auth/ops/radar.
Apps
The portal is now read by purpose: enter, collaborate, govern, operate, learn, trust, and measure.
Applications
The most useful trend is converting every surface into an actionable route with evidence and validation.
What to look at next¶
- Open
portal/private-apps-hub/as the main router. - Enter via
portal/enter/when the actor needs orientation. - Go to
portal/collaborate/orportal/govern/when the actor needs to work or decide. - Review
portal/measure/to validate UX, metrics, and evidence.