DURANDISSEINDUSTRIES

Concurrent workstreams · executive review

Unified command-center roadmap

Refine the ten existing workspaces while designing the eight new capabilities, on a shared responsive design system.

Preview · proposed architecture · no live integrations

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

A + B · concurrent design and refinement

Current frontend states: in-progress refinements are separated from proposed prototypes and architecture dependencies.

Executive OverviewA · Refine existing pagesGroup financial summary slots, executive priorities, entity drill-downs, and ELOHM briefing signals.Prototype rebuilt · interactions tested

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

Interactive Corporate Portfolio HierarchyA + B · Shared portfolio workspacesClickable visual hierarchy groups current records, planned businesses, initiative and separate nonprofit workspaces with status distinctions.Prototype rebuilt · hierarchy / filters

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

Actions & Executive CommunicationsA + B · Shared workflowAssignments, deadlines, escalation, approvals, correspondence, delivery and follow-up.Prototype design

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

Governance & Corporate RecordsA + B · Shared evidence layerFilings, board records, policies, agreements, official document references, approval evidence.Prototype design

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

Treasury & Capital AllocationA + B · Shared finance modelInteractive treasury flow prototype for cash, reserves, commitments, distributions, matched intercompany transfers, and investment deployment.Prototype rebuilt · interactive flow

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

DIT Industry Operations & Portfolio PerformanceA + B · Shared KPI modelDIT operations prototype built; planned industry workspaces for development, capital, media, aviation and future enterprises.Prototype built · DIT 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

Strategy & InvestmentA · Existing page refinementObjectives, opportunities, diligence, investment decisions and milestone follow-through.In progress · preview built

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

ELOHM Intelligence & Executive DecisionsA + B · Governed ELOHMELOHM conversational prototype with selectable simulated prompts, evidence-boundary responses, and Observe → Understand → Predict → Recommend → Act. Decision history remains read-only.Prototype rebuilt · prompts simulated

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

Alerts, Risk & ReportingA + B · Shared monitoringDeadline/failure alerts, risk register, scenario views and weekly/monthly/quarterly/annual packs.Prototype design

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

Access, Security & AuditA · Foundation for all workspacesAuthentication, entity-scoped roles, least privilege, audit trails, data controls, privacy.In progress · preview built

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

Workstream B · new capabilities and navigation

Eight capabilities are being placed into the shared command-center navigation; current pages are read-only design prototypes.

Phased roadmap

Calendar-week ranges are planning estimates after prerequisites; phases may overlap only once shared foundations are approved.

00

0 · Unified design baseline

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.

01

1 · Secure application foundation

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.

02

2 · Verified data-source pilot

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.

03

3 · Decision / record workflows

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.

04

4 · Intelligence, risk and reporting

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.

Shared components & design standards

  • Approved Durandisse logo, navy / blue / teal palette, typography and clean card structure.
  • Compact responsive navigation: command-center core actions plus Workspace menu; keyboard, focus, escape and phone behavior tested.
  • Reusable entity selector, period selector, KPI tile, evidence-aware status, source-health cue, risk row, drill-down and empty state.
  • Numbers and statuses carry source, entity, period, freshness, unit/currency and confidence; color is paired with labels.
  • This prototype uses blank values and status placeholders; it does not present illustrative company performance as actuals.

Dependencies & executive decisions

  • Confirm legal entity / affiliate map from official records; relationship may not be inferred.
  • Select authorized accounting, banking/treasury, operations, identity, records, and communications systems.
  • Approve consolidation rules, FX policy, chart / KPI definitions, reporting calendar, and data owners.
  • Approve role matrix, delegated approval thresholds, privacy/retention policy, and security review.
  • Define ELOHM data scope, evaluation, source citation and mandatory authorization boundaries.

Acceptance & demonstration cadence

Design review

Clickable page prototypes, navigation placement, responsive breakpoints, source-state and illustration labeling.

Platform acceptance

Auth / RBAC tests, persistent approval and audit history, secure secrets, and source-failure recovery.

Data & intelligence acceptance

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.