01Policy
Define what needs approval.
Rules can vary by project, transition, work type, or agent without slowing down the entire flow.
Product7.0 Gates and OversightPilot
Decide where an AI action should stop.
The pilot validates how a supported transition can pause, expose its context, and request a human decision inside the work.
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 capabilitiesControl by design
Autonomy ends where you decide.
The gates model places review at the moment of a supported action. It is in pilot while we expand the transitions, agents, and policies it can cover.
02Decision
Review where the work happens.
The proposal and its context appear together, avoiding blind approvals or separate conversations.
03Record
Sign-off leaves evidence.
Who decided, when, and over which result remains connected to the work history.
Control appears before the action becomes irreversible.
In the pilot, a supported rule can pause a transition. The accountable person sees the proposal inside the work, and the decision can leave reviewable activity.
- 01Define the rule
- 02Pause the change
- 03Decide with context
- 04Keep the evidence
7.1
Configurable approval workflows
Pilot
We are validating approval rules by project and transition. A supported action can wait for a decision; exact coverage depends on the enabled flow.
7.2Human decision point
The decision happens inside the work
Pilot
When a supported transition activates a gate, the work item can show the rule, available context, and approve or reject actions inside the same system.
7.3
Reviewable activity trail
Preview
Supported decisions can record who approved, when, and which output was reviewed. Retention, export, and API coverage remain in development.
7.4
Roles and permissions
Alpha
Initial roles distinguish basic responsibilities. Inheritance, groups, and uniform coverage across people and agents remain under validation before we present them as complete RBAC.
Visible governance
Transparency and oversight by design
Preview
BIKLABS is designing provenance, human review, and activity as parts of the same flow. Availability varies by capability, and these mechanisms do not replace each organization's governance or legal assessment.
- Context visible for review
- Human review on supported capabilities
- Available activity for investigation
Frequently asked questions
The important details, plainly.
Direct answers about how this capability fits into the work system.
01Does a gate apply only to AI agents?
No. Gates are part of the work flow and can supervise human or automated actions. The rule depends on the transition and the level of control the project requires.
02What does the approver see?
The proposal arrives with available context, the result being reviewed, and related activity. The decision happens inside the same system.
03Can controls differ by project?
The model supports project-specific controls, but exact rule, permission, and action coverage depends on the capabilities enabled during the pilot.
04Do gates guarantee legal compliance on their own?
No. They provide supervision, provenance, and records that support AI governance, but compliance also depends on configuration, process, and how each organization uses the system.
From work to review, with context
Stop managing AI.Start managing with AI.
Projects, knowledge, and AI capabilities sharing the same operating context.