feat(dashboard): ground enterprise-facing surfaces in HR/IAM vocab (#124)#125
Merged
Conversation
) Three-renderings rule: only the ENTERPRISE/admin-facing surfaces are grounded in enterprise vocabulary; operator/work surfaces keep their "substrate console" skin untouched. Preserve-then-ground (per Hadi's order of operations): 1. docs/vocab-operator-artifact.md snapshots the operator/admin label strings as they existed before grounding (kept by design). 2. The enterprise surfaces are then grounded per ENTERPRISE-VOCAB.md. Grounded surfaces (enterprise): /admin/members → "People & Access" / "Directory" / "Onboard a person"; capability→Entitlement; Grant capability→Grant entitlement /admin/divisions→ "Organization"; squad→team; head=owner (lead+ entitlement) /members → "Access Tokens"; member→person; Mint→Provision /admin/keys → person/team vocab; Mint key→Provision key (Scopes kept — OAuth/API context) /admin/connectors → Connector Credentials; Add→Provision credential; pot/squad/agent scope → Organization-wide/Team/AI Agent grantLabel + scope selectors → squad→team, org→organization (display only; API scope-type values unchanged) role-presets prose → team/person/organization (allow/deny permission identifiers kept verbatim — they are the API contract) nav → Members→People, Divisions→Organization Untouched (operator): Overview, Send, Approvals, Loops, Brain, Flights, Fleet, Agents, /squads/:id, Setup wizard. Verification: tsc --noEmit clean; 865/865 tests pass; all 5 enterprise surfaces screenshotted at 1440+390 and read — no game/operator words leak into enterprise views (mupot dashboard is single-theme dark). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #124. Do not merge — Kasra gates.
Grounds the enterprise-facing dashboard surfaces in the HR/IAM vocabulary from
agents/kasra/designs/ENTERPRISE-VOCAB.md, following the three-renderings rule: operator/work surfaces keep their "substrate console" skin and are not touched.Order of operations (preserve, then ground)
docs/vocab-operator-artifact.mdsnapshots the operator/admin label strings as they were before grounding, so the operator rendering's wording is never lost (kept by design).Surfaces classified ENTERPRISE (grounded)
/admin/members/admin/divisions· squad→ · team; "head … capability" → "owner … lead entitlement"/members/admin/keys/admin/connectorssquad→team,org→organization (option values unchanged — API contract preserved)role-presetsprosesquads:write,cross-squadkept verbatim — they are the API contract, not prose)Surfaces classified OPERATOR (untouched — keep the skin)
Overview swimlane, Send, Approvals, Loops, Brain, Flights, Fleet, Agents,
/squads/:id,/agents/:id, Setup wizard. The shared nav keeps its operator items (Send/Loops/Brain/Flights/Fleet/Agents).Banned words check
The mupot dashboard never contained creature/hatch/gym/badge/battle/qNFT. Remaining
squad/networkgame-vocab in enterprise views was mapped to Team / Organization. Final HTML sweep across all 5 enterprise surfaces: no game/operator word leaks into the rendered enterprise text.Verification
tsc --noEmit— cleanvitest run— 865/865 pass (49 files)var(--…)tokens used.Files
docs/vocab-operator-artifact.md(new)src/dashboard/index.ts,src/dashboard/keys.ts,src/connectors/dashboard.ts,src/auth/role-presets.ts🤖 Generated with Claude Code