01Vocabulary
The system speaks like your team.
Define types and properties that reflect your domain without losing a shared structure.
Product1.0 Work ItemsAvailable
One task with its working context.
Objective, properties, relationships, conversation, activity, and approval stay together, using the vocabulary your team actually works with.
Shared context Visible status Scoped MCP
Each capability starts from the same work and retains recognizable references to its context. AI, permission, and activity coverage is stated by status.
07 core capabilitiesA connected unit of work
The task fits in a list. Its context does not.
BIKLABS brings the objective, owners, relationships, conversation, and activity around the same work item so the team does not have to rebuild its context.
02Structure
Large work can be broken down.
Hierarchies, checklists, and relationships turn an intention into coordinated work.
03History
Every change leaves context.
Comments, states, and activity stay attached to the work; approvals are added where the pilot is enabled.
What needs doing, and everything required to finish it.
A work item brings definition, structure, ownership, conversation, and activity together. Approval is added to transitions where the pilot is enabled.
1.1
Flexible types
Epic, Issue, Work Package, Task, and Subtask share one model. Types and properties let projects adapt their vocabulary to the team domain.
Checklists and subtasks
Alpha
Checklists and relationships help break down and connect work. Deep hierarchy and placement rules remain in development and are validated separately.
- Checklists inside the item
- Typed relationships between work items
- Advanced hierarchy in development
Detail panel
Status, priority, assignee, cycle, module, dates, estimate, labels, custom fields. Everything visible in the side panel without losing the overview. Configurable per project.
- Important properties visible at a glance
- Editing without leaving the project view
- Consistent configuration for the whole team
1.4
Custom fields
Text, number, date, select, and URL describe work with domain-specific data. Availability in filters and views depends on the enabled capability.
1.5
Relations and assignees
Alpha
Link work items with typed relations. Agent assignment and returned activity are in alpha and depend on the supported operations of the connected agent.
- Human assignment available
- Visible blockers and dependencies
- Agent assignment in alpha
1.6
Activity feed
Chronological feed: threaded comments, reactions, state changes, logged time, file attachments. No need to ask "who changed this?" — it is all there.
- Contextual conversations and reactions
- State changes and logged time
- Attachments and decisions in chronological order
1.7
Approval gates on transitions
Pilot
The gates pilot can require approval on supported transitions. Coverage depends on the project and enabled capability; it does not apply automatically to all work.
Frequently asked questions
The important details, plainly.
Direct answers about how this capability fits into the work system.
01Do I have to use software terminology?
No. Each project can use types and vocabulary adapted to its domain while keeping the same structured BIKLABS model underneath.
02What happens when one task depends on another?
Typed relationships make blockers, blocked work, and connected items visible. That information follows the views and the context available to agents.
03Can I assign work to an agent?
Agent assignment is part of the alpha. Availability depends on the agent, enabled tools, and current identity and permission coverage.
04Is history lost when work moves between cycles?
No. The work item keeps comments, subtasks, relationships, attachments, and activity when its cycle, state, or owner changes.
From work to review, with context
Stop managing AI.Start managing with AI.
Projects, knowledge, and AI capabilities sharing the same operating context.