01
Identity
Alpha surfaces show a recognizable actor.
Security and trust
Control you can see. Evidence you can review.
BIKLABS documents its infrastructure and shows the actual status of tokens, roles, gates, and activity. Security is not a row of logos: every control should be explainable and verifiable.
Core infrastructure in AWS ParisTLS 1.2+ and AES-256 encryption on AWS9 MCP tools · 4 scopesDPA draft available
Control pattern in pilot
Control travels with the work. It does not arrive later.
In a supported transition, identity, scope, and decision can share one timeline. Coverage expands in stages and is not presented as universal.
02
Scope
The MCP token limits the available tools.
03
Policy
A pilot gate can hold a supported transition.
04
Decision
A person reviews the proposal, actor, and available context.
05
Activity
Emitted events can remain linked to the work.
Four layers that make risk legible.
Residency and subprocessors
Documented
Core infrastructure operates in AWS eu-west-3, Paris. The DPA identifies subprocessors and applicable safeguards, including transfers where relevant.
Identity and least access
Alpha
Initial roles and scoped MCP tokens let teams evaluate access by project and operation. Complete inheritance and isolation at scale remain under validation.
Human oversight
Pilot
In supported transitions, a gate can show the proposal, context, and actor before continuing. Action coverage continues to expand.
Provenance and activity
Preview
Supported surfaces can show provenance, actor, state, and outcome. Exhaustive coverage, immutability, and universal export remain in development.
BIKLABS is designed to support transparency and oversight obligations. Final legal suitability depends on the use case, configuration, and responsible organization.