Milestone 1: Planning & Design

Planning & Design

Sprint 1 focuses on the planning and design work that gates implementation. We map out the migration path from the existing single-feature Cache Manager UI to a modular Stylus Manager platform, the architecture for the Activation module across smart contracts, backend, and frontend, and a fully interactive V0 prototype of the upgraded experience.

EPICS

Build Development Plan

This is the project's game plan. It breaks down what we are building, how, and when each piece is ready. It is the roadmap for the whole grant.

Tasks

• Define project scope in terms of user stories and user journey for the Activation module.
• Define the rebrand and migration path from "Cache Manager" to "Stylus Manager" (in-place refactor, same domain, no DB migration required).
• Technical feasibility analysis for each user story (smart contracts, backend, frontend).
• Define tech stack for accomplishing each user story.
• Define high-level architecture for each user story.
• Sprints organization and milestone alignment with the proposal deadlines.

Architecture Design

This is where we lay out the foundation for the Activation module across the three layers (smart contracts, backend, frontend) and explain how they evolve from the Cache Manager codebase without breaking caching.

Tasks

• Smart contract architecture design.
  • Map the placeActivations / _shouldActivate / _activate / _doActivation flow.
  • Document new per-contract config (autoActivate, maxActivationCost) and the global maxActivationsPerIteration parameter.
  • Describe the shared BiddingEscrow integration and value-refund safety.
• Backend architecture design.
  • Define the new Activation pipeline (event capture, state checks, automation worker, alerts).
  • Map onto the existing modular NestJS structure (reuse event-fetcher, state-fetcher, alerts, notifications, cma).
  • Define DB schema additions for activation state, history, and per-user activation alert subscriptions.
  • Define the activations automation strategy: how placeActivations is triggered when conditions are met, how it batches, how it integrates with the existing CMA automation loop, and the iteration cap aligned with maxActivationsPerIteration
• Frontend architecture design.
  • Document the rebrand from "Cache Manager" to "Stylus Manager" (metadata, header, copy, docs).
  • Define the contract-centric UX: activation lives inside the contract detail view alongside caching actions.
  • Define inline status indicators for activation state in contract tables (active, expiring soon, inactive).
  • Define the full-responsiveness plan and target breakpoints.
  • Define the alerts UI extension for activation events (reuse existing alert settings pattern).

V0 Prototype