Portfolio Dashboard
Frontend demonstration
Risk / Hosted demo unavailable
Next: Resolve data-boundary scope
Loading
05 / Engineering control room
Portfolio Dashboard / Engineering experience
Enter a decision environment where confirmed evidence, synthetic run fixtures, unresolved risk, and the next responsible action stay visible together.
Frontend demonstration — previously published demo unavailable.
The source repository uses local mock data. This exhibit does not represent live trading, project telemetry, customer activity, or financial performance.
Attention register
Representative portfolio evidenceFrontend demonstration
Risk / Hosted demo unavailable
Next: Resolve data-boundary scope
Architecture case study
Risk / Provider verification
Next: Durable worker design
Code showcase
Risk / No durable alert retry
Next: Recovery boundary
Derived from published exhibit status and repository limitations. No score, polling, or live feed is implied.
01 / 08
Control room overview
Filter the portfolio and commit a system selection to inspect what is confirmed, what remains risky, what changed, and what deserves attention next.
System portfolio
Confirmed project evidence · no live telemetry
02 / 08
Project health
Inspect the actual Portfolio Dashboard repository boundary. Confirmed routes and release scripts coexist with session-only data, an unavailable deployment, and intentionally absent integrations.
03 / 08
Run inspector
Filter and inspect authentic synthetic fixtures from the repository. The interface separates evidence, configuration, and engineering interpretation without presenting any value as a real trading outcome.
Repository run fixtures
Authentic synthetic records from mockData.ts · never live trading activity
04 selected fixtures / 12 total
04 / 08
Engineering decision log
Each decision links a repository problem to the chosen boundary, its reason, its accepted cost, and the evidence that would trigger reconsideration.
05 / 08
Risk + limitation register
Select every limitation to inspect what is known, why it matters, the current mitigation, and the next reasonable engineering action.
06 / 08
Improvement queue
The queue combines open items from the repository ship-readiness audit with explicitly labeled architectural recommendations from completed exhibits.
Now · Proposed
Portfolio Dashboard
Evidence
Ship audit lists browser-level route coverage as incomplete.
Outcome: Verify critical routes and filters without random mock failures.
Dependency
Stable public fixtures
Now · Decision required
Portfolio Dashboard
Evidence
Ship audit leaves mock-only versus API-adapter scope unresolved.
Outcome: Align buyer expectations with the shipped architecture.
Dependency
Product positioning
Next · Architectural recommendation
AI Content Automation
Evidence
Generation currently runs inside the request lifecycle.
Outcome: Recover work independently from request duration.
Dependency
Queue + worker hosting
Next · Architectural recommendation
Webhook Dashboard
Evidence
Delivery failure is recorded but not retried durably.
Outcome: Separate accepted ingestion from recoverable notification work.
Dependency
Job persistence
Later · Backlog
Portfolio Dashboard
Evidence
Both remain open in the ship-readiness audit.
Outcome: Set expectations for template updates and support boundaries.
Dependency
Commercial/legal review
07 / 08
Technology evidence
The stack is presented through concrete repository responsibility rather than logos or generic capability claims.
Route-level dashboard, list, creation, detail, loading, error, and not-found interfaces.
Why: Client navigation fits the current static frontend boundary.
Accepted limitation
No server rendering or authenticated route boundary.
src/app/router.tsx · src/pages/
Run, query, creation, list-result, and component contracts.
Why: A replaceable data adapter needs stable shapes.
Accepted limitation
Runtime trust still depends on validation at external boundaries.
src/features/runs/types.ts
Manual sorting and pagination over URL-synchronized query state.
Why: Column behavior stays declarative while the mock service owns data operations.
Accepted limitation
The table instance triggers a documented React Compiler lint suppression.
src/pages/RunsPage.tsx
Preset-backed form state and cross-field run validation.
Why: Input errors remain explicit before mock creation.
Accepted limitation
Client validation is not a server authorization boundary.
src/pages/NewRunPage.tsx
Lazy-loaded equity and drawdown views derived from fixture metrics.
Why: The detail route can communicate the charting integration surface.
Accepted limitation
Every plotted value is synthetic and must remain labeled.
RunDetailCharts.tsx
Static production build, SPA fallback, behavior tests, and output smoke checks.
Why: The frontend demonstration has no required server runtime.
Accepted limitation
The previously published demo is unavailable.
vite.config.ts · scripts/
08 / 08
Operating reflection
Portfolio Dashboard proves a thoughtful frontend architecture: explicit URL state, typed adapters, validated inputs, route isolation, and visible failure states. It does not prove a trading system or live operating environment.
A real release would require an explicit API contract, durable run state, provenance for results, deterministic public fixtures, browser-level route tests, and a deployment decision aligned with the template’s commercial and legal position.
Deployment reality
Application
React/Vite frontend demo
Data
Synthetic + in-memory
Hosted demo
Unavailable
Local release checks
Scripted
No live broker, market feed, worker, backend API, database, authentication, telemetry, or financial result is represented.
Evidence standard