01Capture
Decisions with sources and owners.
Pages bring the decision, its sources, and references together so a conclusion never loses its origin.
Product9.0 WikiPreview
Documentation that follows the work.
Rich editor, page hierarchy, and links to the work that provides context.
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.
05 core capabilitiesMore than documentation
Team memory participates in the work.
A wiki creates value when it preserves the why, connects to what gets executed, and can be used again. BIKLABS connects all three moments.
02Connection
The document knows the work it drives.
Work items and pages link in both directions. The specification and its execution stop drifting apart.
03Reuse
BIA consults knowledge, not fragments.
Answers start from permitted workspace context. Supported actions depend on the scope enabled during the preview.
Write once. Connect what happens next.
BIKLABS structures pages and exposes related work so the team can keep the why available. Use of that knowledge by BIA or agents is communicated according to status.
9.1
Rich editor (Tiptap)
Headings, code blocks, tables, checklists, embeds, and mentions for documenting decisions without leaving the workspace.
9.2
Page hierarchy
Organize knowledge as a tree. Parent pages, child pages. Navigable sidebar. Drag to reorganize. Search by title or content. Structure, not a flat list.
9.3
Linked to work items
Mention MER-1 from a page to retain the relationship between documentation and execution and return to the work from its context.
9.4
Templates
Coming soon
Onboarding, postmortem, technical spec, retrospective. Create pages from a template in one click. Recurring structures solved once.
- Onboarding and runbooks
- Postmortems and retrospectives
- Reusable specifications
9.5
Simultaneous collaboration
In development
Multi-user editing and real-time synchronization are in development. Until validation is complete, we do not present conflict-free editing as a product guarantee.
- Multi-user synchronization in development
- Conflict handling and recovery under validation
- Availability separated from the current editor
Frequently asked questions
The important details, plainly.
Direct answers about how this capability fits into the work system.
01How is this different from a separate wiki?
Pages live in the same system as projects and work items. Connect a decision to the work it creates and consult both through BIA without rebuilding context.
02Can BIA use every page?
BIA only uses knowledge within its access scope. Page visibility and workspace permissions continue to apply.
03Does linked work stay synchronized?
Links and mentions retain the relationship between a page and its work item. Advanced synchronization and real-time collaboration are communicated separately while they remain in development.
04Can I preserve the context of a decision?
Yes. The page, its references, and its links to work keep the context together so the team can return to the decision.
From work to review, with context
Stop managing AI.Start managing with AI.
Projects, knowledge, and AI capabilities sharing the same operating context.