Workstream A
10 existing pages
Refine without needless rebuilds
Command center
OverviewRoadmapPortfolioActionsTreasury & CapitalDIT OperationsStrategyELOHMWorkspace
Entity directoryEnterprise OperationsStrategy & objectivesGovernanceDecisionsAlerts & RiskEnterprise RiskExecutive CommunicationsDocuments & RecordsReports & AnalyticsFinance statementsPerformanceAccess & SecurityConcurrent workstreams · executive review
Refine the ten existing workspaces while designing the eight new capabilities, on a shared responsive design system.
Design / capability boundary: page prototypes and interaction patterns can be refined now. Authentication, persistent workflows, API sync, consolidated financials, and ELOHM action execution are not active in this static prototype and depend on the approved secure platform foundation.
Workstream A
10 existing pages
Refine without needless rebuilds
Workstream B
8 capabilities
Introduce prototypes concurrently
Shared components
One design system
Navigation, state cues, cards, lists, filters
Backend readiness
Foundation needed
Auth, storage, sources, audit, governance
Current frontend states: in-progress refinements are separated from proposed prototypes and architecture dependencies.
Scope: Group financial summary slots, executive priorities, entity drill-downs, and ELOHM briefing signals.
Dependency: Verified accounting and operating feeds; approved ELOHM data boundary.
Acceptance: Each KPI shows entity, period, currency, source, and verification state; unsupported totals blank.
Open workspace
Scope: Clickable visual hierarchy groups current records, planned businesses, initiative and separate nonprofit workspaces with status distinctions.
Dependency: Formation/ownership records, jurisdictions, affiliate evidence, executive owners.
Acceptance: Every connector visibly denotes workspace grouping only; ownership is not inferred without dated source evidence.
Open workspace
Scope: Assignments, deadlines, escalation, approvals, correspondence, delivery and follow-up.
Dependency: Identity / RBAC, durable action store, approved email source and write scopes.
Acceptance: Assignment / approval changes persist with authorization and audit history; mail is not sent without authorized review.
Open workspace
Scope: Filings, board records, policies, agreements, official document references, approval evidence.
Dependency: Permission-controlled document repository, retention policy, legal source records.
Acceptance: Prepared, submitted, accepted, confirmed are distinct; records have entity, owner, effective date, access scope and evidence.
Open workspace
Scope: Interactive treasury flow prototype for cash, reserves, commitments, distributions, matched intercompany transfers, and investment deployment.
Dependency: Finance system(s), bank/treasury source, controller-approved consolidation and FX policies.
Acceptance: Every flow identifies both ledger sides; test matching and elimination policy without double-counting; personal / nonprofit books remain separate.
Open workspace
Scope: DIT operations prototype built; planned industry workspaces for development, capital, media, aviation and future enterprises.
Dependency: Verified operating systems, accountable metric owners and KPI definitions.
Acceptance: Each metric has definition, units, period, target/owner where approved, source, trend and last-verified marker.
Open workspace
Scope: Objectives, opportunities, diligence, investment decisions and milestone follow-through.
Dependency: Approved corporate thesis, deal owner, evidence, capital mandates.
Acceptance: Pipeline stage and investment status separate; committed capital requires explicit authorization and source.
Open workspace
Scope: ELOHM conversational prototype with selectable simulated prompts, evidence-boundary responses, and Observe → Understand → Predict → Recommend → Act. Decision history remains read-only.
Dependency: Authenticated roles, audit event service, verified datasets, evaluation corpus and human approval matrix.
Acceptance: Recommendations cite evidence / uncertainty; no consequential action executes without a permitted approval and audit record.
Open workspace
Scope: Deadline/failure alerts, risk register, scenario views and weekly/monthly/quarterly/annual packs.
Dependency: Current source sync, approved risk taxonomy, threshold owners, close/report calendar.
Acceptance: Stale or failed sources flagged; alerts link to evidence and owner; reports disclose basis, period, status, assumptions.
Open workspace
Scope: Authentication, entity-scoped roles, least privilege, audit trails, data controls, privacy.
Dependency: Identity provider choice, user/role matrix, access review owner, security and retention policies.
Acceptance: RBAC negative/positive tests pass; all sensitive reads/writes authorized and attributable; secrets remain server-side.
Open workspace
Eight capabilities are being placed into the shared command-center navigation; current pages are read-only design prototypes.
Placement: Top-level Portfolio
Placement: Treasury & Capital
Placement: Workspace menu · industry portfolio
Placement: Top-level ELOHM
Placement: Workspace menu
Placement: Workspace menu · Governance
Placement: Alerts & Reporting
Placement: Alerts & Risk
Calendar-week ranges are planning estimates after prerequisites; phases may overlap only once shared foundations are approved.
A + B concurrently · Prototype refinement underway
1–2 weeks · active
Depends on: Architecture / navigation review; existing page inventory; approved visual tokens.
Deliverable: Shared navigation, responsive review, homepage + added workspace prototypes, reusable interaction patterns.
Shared platform · Critical dependency
3–5 weeks · after design decisions
Depends on: Approved identity and database/service selection, RBAC roles, record retention, security owner.
Deliverable: Secure auth, entity-scoped permissions, durable data model, audit events, backend API patterns.
Finance + Operations · High
4–8 weeks
Depends on: Source owners, API access, mapping, controller reconciliation and KPI approvals.
Deliverable: One finance and one operations source integrated with lineage, health monitoring, and verified KPI read models.
Actions + Governance + Decisions + Communications · High
3–6 weeks
Depends on: Phase 1; approval matrix, document repository, authoritative records, outbound message authorization.
Deliverable: Persistent workflow states, evidence links, access policy checks, append-only decision/action history.
ELOHM + Risk + Reporting · After reliable data
4–8 weeks
Depends on: Verified history and baseline; approved risk scales, report calendar, ELOHM evaluation / human-gate policy.
Deliverable: Briefing and scenario prototypes backed by measured data; recommendations remain human-approved.
Indicative only. Schedule may expand for procurement, security assessment, legal review, source cleanup, and provider/API lead time.
Clickable page prototypes, navigation placement, responsive breakpoints, source-state and illustration labeling.
Auth / RBAC tests, persistent approval and audit history, secure secrets, and source-failure recovery.
Reconciled entity/group figures, intercompany elimination tests, risk threshold validation, ELOHM evidence and authorization gates.
Demonstrate the integrated preview after each concurrent design increment; mark each capability proposed, designed, implemented, tested, or approved in its own release note.