Skip to content

Global Portal Vision by Roles, Profiles, and Audiences

Purpose

Define a single MkDocs portal experience where each collaborator sees routes, language, and tools aligned with their organizational role, knowledge level, and device context.

Canonical visual source

For layered flow, HILT decision graph, and audience mindmap use docs/portal/operating-visual-canon.en.md first.

Design principles

  1. context before menu: identify profile first, then show actions.
  2. role-based minimum: each audience gets only what is needed for the current task.
  3. cognitive progression: layered content (basic, operational, expert).
  4. mandatory human decision: critical actions require HILT gates.
  5. digital sovereignty: sensitive business core and data remain internal.

6D experience segmentation

Dimension Core question Portal usage example
Organizational role What accountability do I own CEO, Finance, Legal, DevOps, Sales
Operational profile How do I execute daily work builder, auditor, operator, communicator
Audience type How should content be framed technical, executive, institutional, junior
Behavior style How do I interact explorer, executor, verifier, approver
Knowledge depth How deep do I need to go 101, operational, advanced
Main concern Which risk do I want to reduce security, cost, speed, compliance

Experience architecture (portal)

flowchart TD
  A[Portal entry] --> B[Identity + Role + Onboarding status]
  B --> C[Experience router]
  C --> D1[Technical view]
  C --> D2[Executive view]
  C --> D3[Legal/Compliance view]
  C --> D4[Sales/Media view]
  D1 --> E1[Runbooks, GitOps, MicroK8s, Proxmox]
  D2 --> E2[KPIs, roadmap, risks, HILT decisions]
  D3 --> E3[Controls, evidence, policies, audits]
  D4 --> E4[One-pagers, narrative, trust pack]
  E1 --> F[Tools by device]
  E2 --> F
  E3 --> F
  E4 --> F

Tool matrix by role and device

Role Primary outcome Desktop/Laptop Mobile CLI/Bastion
CEO / Leadership decide priorities, risk, and focus portal overview, scorecards, roadmap executive alerts, status HILT approvals and evidence review
Finance / Tax financial control and traceability Odoo, reports, compliance evidence milestone approvals signed exports and audits
Legal / Compliance regulatory controls and proof policies, RoPA, DPIA, incident response risk alerts control validation and logs
DevOps / Platform deploy and operate stack Proxmox+MicroK8s runbooks, dashboards operational status FSM/HILT scripts, kubectl, qm
Data / AI run cognitive pipelines Open Notebook, ML scorecards job tracking pipeline execution and verification
Sales / Media market narrative and assets trust pack, one-pagers, sales hub asset sharing versioned marketing artifacts

Knowledge-level routes

  • 101: portal/quickstart/, institutional onboarding, quiz wizard.
  • Operational: domain runbooks, QA checklists, HILT protocols.
  • Expert: onion runtime architecture, multi-forge governance, layered risk control.

Expected behaviors by profile

Profile Expected behavior Minimum evidence
Explorer understands context and scope onboarding quiz + guided reading
Executor follows procedure without skipping gates execution report + logs
Verifier contrasts outputs with controls checklist + technical validation
Approver decides on risk and impact HILT record + decision memo

Secure exposure model (onion)

  1. Internal Core layer: secrets, sensitive logic, runtime governance.
  2. Internal Operations layer: ops panels, runbooks, ML scorecards.
  3. Controlled Collaboration layer: authenticated portal, GitHub App, workflows.
  4. Public layer: sanitized docs and artifacts.

Governance rules for personalization

  1. no role access without onboarding and explicit accountability signal.
  2. third-party connections off by default until INTERNAL_SERVICES_READY_FOR_THIRD_PARTY=true.
  3. each critical flow defines explicit, reversible HILT points.
  4. every action writes traceable evidence in outputs/ and/or docs/internal/.
  1. dynamic role/profile landing (adaptive menu and CTAs).
  2. audience selector for narrative mode (technical, executive, legal).
  3. tool panel by device and context (office, field, bastion).
  4. onboarding maturity score per person/team.
  5. FSM-aware next-step recommender with HILT gate when required.