Implementation roadmap
This page turns the remaining final-pitch features into an in-app build plan. It follows the current architecture: dashboard for mission control, ETL for attack-vector context, modules for 0G execution posture, and settings for runtime trust plus future settlement visibility.
Live now
Features already reflected in the app and safe to emphasize in the demo.
Operators can authenticate from the CLI, sync the session to the web app, and keep the control plane tied to the same wallet identity.
The ETL page shows Rekt and Solodit-derived context so fresh findings can seed the next red-team prompt without leaving the app.
The modules and settings surfaces already expose inference readiness, authenticated compute, storage, and fine-tuning prerequisites.
Next up
The smallest changes that unlock the remaining pitch promises.
Expose round number, variant id, lifecycle state, and active role set directly in the dashboard run table and mission-control panels.
Turn common red-team strategies into reusable templates so a user can move from ETL finding to scenario launch in one workflow.
Add payment references, transaction hashes, settlement status, and inference-cost visibility to the same mission-control surface used for run status. Wallet context: 0x0fcD0338a468cE855D7da7ea1fE945CC5457fDd2.
Roadmap
Longer-horizon work aligned with 0G inference, storage, fine-tuning, and governed agent operations.
Use retained vector memory, ETL fragments, and judged run traces to build structured datasets for long-horizon policy improvement.
Map operator approval, alignment-node concepts, and escalations into a human-governed multi-agent workflow.
Prompt-template rollout
Use these templates to demonstrate user-defined red-team strategy today, then promote them into first-class CLI or UI scenario controls.
Pressure the protocol with delayed price updates, manipulated feeds, and time-sensitive liquidation windows while the defense side preserves user funds.
Simulate voter coordination, treasury pressure, and emergency controls so the ciso/cto role can prove whether governance can be contained.
Model cross-chain delay, compromised relayers, and liquidity fragmentation to test both exploit detection and operator coordination.
Stress the response organization with incomplete signals, noisy alerts, and social-engineering-style uncertainty so the operator layer must escalate cleanly.