delivery workspace· 2026
Stackx Track
A delivery workspace that connects project planning, calendar-based time logging, reporting, and shared knowledge. Teammates and AI agents work through the same validation and permission rules.
Fullstack development · Product engineering
Technology
- Rails 8.1
- Ruby
- PostgreSQL
- Phlex
- Hotwire
- Turbo
- Stimulus
- Tailwind CSS
- Trailblazer
- Pundit
- MCP
- Kamal
The problem
Planning work is only one part of running a delivery team. Tasks need owners, recorded time needs project context, and reports need to explain where effort went. When those records live in separate tools, even a simple question about a project can require manual reconciliation. Adding AI agents creates another challenge: a tool that can create tasks or log time must respect the same access boundaries and validation as a teammate using the application.
The solution
Stackx Track brings projects, epics, shared sprints, assignments, time entries, and reporting into one Rails application. Calendar interactions make it practical to record effort, while filtered reports connect that effort to projects, clients, members, and cost. Knowledge articles keep working context alongside delivery. The web interface and MCP tools share domain operations. Task changes and time logging follow ordinary validation and authorization, including all-or-nothing batch time entry creation. A server-rendered interface built with Phlex, Turbo, and Stimulus keeps the product centered on these connected workflows.
Inside the product
One connected workspace.
Generated product illustrations explain the workflows below. They are not screenshots or live workspace data.
01 / Stackx Track
Plan the work together
Move from a cross-project backlog into shared sprints, with epics, assignments, checklists, and comments keeping the work understandable. Closing a sprint preserves completed cards in read-only sprint history and removes unfinished tasks from that sprint for future planning.
02 / Stackx Track
Record time in context
Create a time entry from a selected calendar range, then move or resize it as the record changes. Project and task context stay attached to the entry, with calendar and list views for reviewing logged work.
03 / Stackx Track
Make delivery visible
Administrators can review recorded hours, cost, and team allocation across week, month, quarter, or year, filter by project, client, or member, and export reports to CSV.
04 / Stackx Track
Let agents work through the product
MCP tools let an assistant find projects, create and update tasks, read and maintain knowledge, log time, and produce factual work recaps. These tools reuse the application’s domain operations; batch time logging either succeeds in full or creates no entries.
05 / Stackx Track
Keep the working knowledge close
Write Markdown knowledge articles, attach images, and search the collection using PostgreSQL-backed search. Signed-in authoring, trash, and published public manuals support both internal working notes and intentionally shared guidance.
06 / Stackx Track
Review invoices with their context
Administrators organize uploaded documents and shared Gmail attachments for structured invoice review. Vendor, category, VAT, and line-item fields support expense reporting, with human review kept explicit rather than assuming every extracted field is correct.
07 / Stackx Track
Account for team availability
Members can request leave, administrators can approve it, and calendars make availability visible. Annual balances support planning while leave remains separate from project effort and cost hours.
08 / Stackx Track
Carry permissions across every surface
Admin and member roles combine with viewer and contributor project memberships. Personal API keys retain their owner’s permissions, so agent actions follow the same access boundaries as the web application. Authorization stays part of each workflow.
