Modules
Ten capability domains. Type to filter, arrows to navigate, enter to expand. Same shape as the console people work inside.
Ten capability pillars cover what a team actually does day to day. Each pillar is opinionated about permissions, real-time, and tenancy from the inside. Users see consistent behavior across the surface instead of ten different mental models stapled together.
The browser below uses the same shape as Gealo's internal command palette. Type, navigate, expand. Capability bullets describe what users do, not how the table looks. Tech chips name families, not versions.
Pillars are individually useful and collectively reinforce each other. A few of the seams that get the most attention:
- [01]
tasks ↔ chat
Mentioning a task in chat resolves to the task entity and renders an inline card with status, assignee, and due date. Comments and task activity feed into the same notification fabric.
- [02]
meetings ↔ calendar
Meetings live inside projects, surface on a tenant-wide calendar, and export as ICS. Attendees are workforce-aware: only members the policy allows can be invited.
- [03]
documents ↔ chat
Files shared in chat open in the document preview sidebar without leaving the channel. Permissions resolve once. The chat view does not get its own document grant model.
- [04]
github ↔ tasks
Commits and PRs that mention a task code update the task only inside the tenant that owns the GitHub installation. Webhooks verify and resolve tenant before touching state.
- [05]
hr ↔ tasks
Approved leave shrinks effective capacity in sprint planning views. Capacity is a tenant policy answer, not a per-project guess.