One customer journey, with the current evidence, dependencies and proof needed before Sales treats a capability as ready.
This PR builds the enterprise web experience, local prototypes, documentation skin and verification gates. It does not implement or deploy platform, authentication, CRM, Minerva, Spaces or job services.
Enterprise story and a credible starting point
The right personal, evaluation or organisation workspace
Upload, connect or watch an approved source
Table → chart → changed chart → report, dashboard or app
Save, rerun, schedule or respond when data arrives
Organisation ownership, people, permissions and continuity
Isolation, evidence, safe failure and support
“Partly available” is intentional: the platform may already do much of the work, while the complete supported user journey or enterprise contract is not yet proven.
I can understand what Novem does, see a credible workflow and decide what to explore next.
I can explore personally, evaluate for my organisation or enter an invited organisation without ending up in the wrong workspace.
I can start from an uploaded file or an approved live folder and use the latest data without rebuilding the work.
I can inspect data, create and adjust charts, add narrative, combine views and produce a report, dashboard or factsheet.
I can turn useful work into a standalone job, run it again, schedule it or trigger it when approved data arrives.
My organisation keeps its reports, jobs and schedules when people change roles or leave, with understandable access controls.
Minerva uses only my organisation's approved context, creates work in the intended scope and stops rather than falling back elsewhere.
This is a customer-proof chain, not a mandated technical architecture. Several workstreams can progress in parallel, but the final enterprise proof needs all of them to meet their acceptance gates.
Enterprise story, trustworthy public pages, entry prototype and launch register.
The working product surface where sources, outputs, jobs, reviews and evidence can be seen.
Live files, data tables, charts, changes, themes and report-grade outputs.
Create, approve, test, run and schedule bounded work—including when approved data arrives.
Use approved context, act in the intended organisation and fail closed without leakage.
One repeatable Sales journey with observable evidence and an agreed safe failure.
Capability status, workspace journey, pricing scope and which previews remain private.
Route ownership, integrations, runtime configuration, observability and rollback.
Identity, isolation, headers, data handling, execution and safe-failure evidence.
Policies, processors, analytics wording, customer marks and public claims.
Golden journey, qualification form, assets, proof language and handoff.
Canonical /docs ownership, draft visibility and first-class component behaviour.
