> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_37/session_02_g4_status_equipment.md). # Session 02: G4 Status Equipment **Session ID**: `phase37-session02-g4-status-equipment` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Finish the remaining G4 status, equipment, and reward/loadout icon work without disturbing the already-wired system-object frames. *** ## Scope ### In Scope (MVP) * Select and crop G4 status pips, equipment icons, and tier-language icons. * Wire icons into runtime HUD and React surfaces that expose statuses, equipment, rewards, loadout, ledger, or settings state. * Add tests for new status/equipment frame expectations and UI mapping behavior. * Document accepted and rejected G4 candidates. * Prove the icons render in the actual product surfaces that use them. ### Out of Scope * Reworking already-wired G4 system-object frames. * Adding new equipment or status mechanics that are not already exposed. * Replacing familiar standard controls with themed icons when clarity drops. *** ## Prerequisites * [ ] Session 01 completed or no unresolved atlas-contract changes remain from G8 work. * [ ] G4 source and alpha derivative are available under the generated visual asset directory. * [ ] Existing system-object frame tests are passing before edits. *** ## Source Inputs | Asset | Path | | ---------------- | ------------------------------------------------------------------------------------------------------------------ | | Source sheet | `docs/ongoing-projects/generated/ai-rogue-visual-audio-assets/source/ai-rogue-status-equipment-systems-source.png` | | Alpha derivative | `docs/ongoing-projects/generated/ai-rogue-visual-audio-assets/alpha/ai-rogue-status-equipment-systems-alpha.png` | | Crop manifest | `docs/ongoing-projects/generated/ai-rogue-visual-audio-assets/crop-manifest.json` | System-object frames are already wired; only status/equipment/icon candidates remain. Review abstract cross/lock motifs before accepting them. *** ## Detailed Work Use the accepted G4 source only for the unclaimed status/equipment subset: * UI pips for active statuses. * Equipment icons for `kernel`, `guard`, and `payload`. * Tier language for patched, compiled, vectorized, and kernel-grade equipment that does not rely only on hue. * Optional equipment reward/pickup visuals if the simulation exposes those items on the board. * Preserve the first G4 runtime pass; only the unclaimed status/equipment/icon subset is in scope. *** ## Likely Code Touchpoints * `src/extensions/ai-rogue/runtime/equipment.ts` * `src/extensions/ai-rogue/runtime/status.ts` * `src/extensions/ai-rogue/runtime/render-hud.ts` * `src/extensions/ai-rogue/views/reward-icon.tsx` * `src/extensions/ai-rogue/views/loadout-view.tsx` * `src/extensions/ai-rogue/views/ledger-view.tsx` * `src/extensions/ai-rogue/views/settings-view.tsx` * `src/extensions/ai-rogue/runtime/__tests__/equipment.test.ts` * `src/extensions/ai-rogue/runtime/__tests__/status-expanded.test.ts` *** ## Required Validation * `scripts/extensions/ai-rogue/pack-visual-assets.py` * `bun run typecheck` * `bash scripts/check-asset-sizes.sh` * Focused equipment/status tests and relevant React view tests. * `bunx playwright test tests/e2e/ai-rogue-runtime.spec.ts` * `bunx playwright test tests/e2e/ai-rogue-mobile.spec.ts` * Browser evidence that the HUD and relevant React surfaces render icons without relying only on hue. *** ## Deliverables 1. Updated G4 crop manifest entries and refreshed atlas outputs. 2. Status/equipment icon mappings in runtime and relevant React views. 3. Focused equipment/status/view tests. 4. Updated visual asset documentation with accepted and rejected candidates. *** ## Success Criteria * [ ] Existing system-object frame tests still pass. * [ ] New equipment and status mappings resolve to stable typed frame names. * [ ] UI surfaces render recognizable icons without relying only on hue. * [ ] The product outcome is proven end to end: status/equipment visuals appear in live AI Rogue HUD and React surfaces, recover through normal fallback paths, and are covered by focused tests. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_37/session_02_g4_status_equipment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.