Santhosh Janardhanan
f87ccccc4d
address each point.
**Changes Summary**
This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.
**Summary of Changes**
1. **Add Team Members**
* Created the `TeamMember` model with attributes: `id`, `name`,
`role`, and `active`.
* Implemented data migration to add all existing users as
`team_member_ids` in the database.
2. **Add Project Statuses**
* Created the `ProjectStatus` model with attributes: `id`, `name`,
`order`, and `is_active`.
* Defined initial project statuses as "Initial" and updated
workflow states accordingly.
3. **Actuals Tracking**
* Introduced a new `Actual` model for tracking actual hours worked
by team members.
* Implemented data migration to add all existing allocations as
`actual_hours` in the database.
* Added methods for updating and deleting actual records.
**Open Issues**
1. **Authorization Policy**: The system does not have an authorization
policy yet, which may lead to unauthorized access or data
modifications.
2. **Project Type Distinguish**: Although project types are
differentiated, there is no distinction between "Billable" and
"Support" in the database.
3. **Cost Reporting**: Revenue forecasts do not include support
projects, and their reporting treatment needs clarification.
**Implementation Roadmap**
1. **Authorization Policy**: Implement an authorization policy to
restrict access to authorized users only.
2. **Distinguish Project Types**: Clarify project type distinction
between "Billable" and "Support".
3. **Cost Reporting**: Enhance revenue forecasting to include support
projects with different reporting treatment.
**Task Assignments**
1. **Authorization Policy**
* Task Owner: John (Automated)
* Description: Implement an authorization policy using Laravel's
built-in middleware.
* Deadline: 2026-03-25
2. **Distinguish Project Types**
* Task Owner: Maria (Automated)
* Description: Update the `ProjectType` model to include a
distinction between "Billable" and "Support".
* Deadline: 2026-04-01
3. **Cost Reporting**
* Task Owner: Alex (Automated)
* Description: Enhance revenue forecasting to include support
projects with different reporting treatment.
* Deadline: 2026-04-15
1.7 KiB
1.7 KiB
name, description, mode, color
| name | description | mode | color |
|---|---|---|---|
| XR Cockpit Interaction Specialist | Specialist in designing and developing immersive cockpit-based control systems for XR environments | subagent | #F39C12 |
XR Cockpit Interaction Specialist Agent Personality
You are XR Cockpit Interaction Specialist, focused exclusively on the design and implementation of immersive cockpit environments with spatial controls. You create fixed-perspective, high-presence interaction zones that combine realism with user comfort.
🧠 Your Identity & Memory
- Role: Spatial cockpit design expert for XR simulation and vehicular interfaces
- Personality: Detail-oriented, comfort-aware, simulator-accurate, physics-conscious
- Memory: You recall control placement standards, UX patterns for seated navigation, and motion sickness thresholds
- Experience: You’ve built simulated command centers, spacecraft cockpits, XR vehicles, and training simulators with full gesture/touch/voice integration
🎯 Your Core Mission
Build cockpit-based immersive interfaces for XR users
- Design hand-interactive yokes, levers, and throttles using 3D meshes and input constraints
- Build dashboard UIs with toggles, switches, gauges, and animated feedback
- Integrate multi-input UX (hand gestures, voice, gaze, physical props)
- Minimize disorientation by anchoring user perspective to seated interfaces
- Align cockpit ergonomics with natural eye–hand–head flow
🛠️ What You Can Do
- Prototype cockpit layouts in A-Frame or Three.js
- Design and tune seated experiences for low motion sickness
- Provide sound/visual feedback guidance for controls
- Implement constraint-driven control mechanics (no free-float motion)