Forticia research infrastructure: A lean core.
Governed at
every edge.
Governance, reproducibility, and controlled access are the baseline, not an add-on. Research runs in isolated workspaces, reaches data only through scoped contracts, and writes only after a human approves.
- Research WorkspacesIsolated containers. Tools load when the domain needs them.
- Helper PlaneThe layer between apps and data. Scoped read and write contracts keep apps off raw disk.
- Governed AIDrafts by default. Lead approval to write. Full audit trail.
- Knowledge ArchivePacks and records that compound across projects.
- Secure CommunicationsChannels, voice, and mail scoped to the research space.
- Controlled GovernanceInvite-only. Role-gated. Compliance before credentials.
The lean kernel
Small enough to inspect.
Sign-in, permissions and storage make up the kernel, the always-loaded core. It stays small and everything else attaches on demand. This is what happens to a single request.
- Lean coreSign-in, permissions and storage form the always-loaded core, the kernel. It stays small.
- Modular loadCapabilities attach on demand, per workspace.
- Accountable AIHuman-in-the-loop. Versioned prompts. Full audit trail.
- Honest limitsFindings are written up with their limits, and every run is logged and replayable.
- Sessionwaiting
- Workspace permissionwaiting
- Rolewaiting
- Typed actionwaiting
- Recordwaiting
Session
A signed-in session in an HTTP-only cookie that expires after seven days, or a scoped API key. Sign-in is rate limited, repeated failures lock the account, and two-factor codes are supported.
Research Workspaces
Every project gets its own room.
Isolated containers. Tools load when the domain needs them, so a biology programme never carries a trading toolchain, and the reverse.
- Access policy: members, roles, visibility
- Tools: loaded per domain, on demand
- Mounts: storage reached by contract only
- Runtime: isolated container, small kernel
Helper Plane
Applications never touch raw disk.
Import, export, and data access are contracts between workspace apps and storage. An app asks for a named contract. If none names the request, there is no path.
- request importPOST /contracts/drive.import
- evaluateapp, role, workspace, target
- allowrule: drive.import
- scoped writedrive/imports
- stored
- append eventworkspace_events
- 202 queued
Importer queues a reading list into the workspace drive.
Governed AI
Drafts by default. Lead approval to write.
Agents propose, people decide. Prompts are versioned, outputs stay drafts, and every step is attributable in the audit trail.
- v12
············ - v13
············ - v14
············ - v15
············
Each fingerprint covers the revision text and the one before it, computed here in your browser from the lines shown.
research-agent drafted v15. Held for a lead.
Knowledge Archive
Work that compounds instead of resetting.
Packs and records that compound across projects. Everything a workspace learns is indexed, versioned, and reachable by the next project through a contract.
Literature summary pack
Sources, extracted claims and open questions for a field, indexed once and cited by record id.
- type
- Knowledge pack
- lane
- Knowledge
- status
- Indexed
- visibility
- Workspace members
- v3Lead approved a refreshed draft
- v2Two sources added
- v1Pack indexed
Cited by
| Workspace A | Cited |
|---|---|
| Workspace B | Cited |
| Workspace C | Cited |
3 of 3 workspaces cite this record, each through a read contract.
- Indexed on arrivalImports and drive files are queued, then indexed with a lane, a type and a visibility.
- Every change leaves a versionEach accepted action adds an entry, so a record can be traced from first index to latest.
- Reused by contractA later project reads what a contract names. It does not copy a folder or inherit a login.
Secure Communications
Conversation stays
inside the space.
Channels, voice, and mail scoped to the research space. Who can see a thread is decided by who is assigned to the workspace, not by who has the link.
- Channels
- Messages carry their author and time and reach members live over the workspace stream.
- Voice and video
- Meeting rooms and live rooms are created inside a workspace, named for it, and listed with host and policy.
- Workspace mail is sent from the space, and every person keeps a real mailbox of their own.
Assigned to both spaces. The spaces below are what that person can see.
- #general
- #method-notes
- #reviews
Mail to the space reaches its members
- #general
- #field-data
Mail to the space reaches its members
Controlled Governance
Compliance before credentials.
Invite-only and role-gated. Nobody arrives with access. It is granted by a person, to a person, for a workspace, and it can be withdrawn the same way.
Invitation
- The link is single-use and expires after seven days.
- Only a hash of the token is stored, so a database reader cannot reuse an invitation.
- for
- A. Researcher
- role
- Researcher · Collaborator
- workspace
- Biology programme
- expires
- Seven days after issue
- token
- Shown once. Stored as a hash.
invite · Manager invited A. Researcher.
PolarisLink™
The protocol that
lets agents coordinate.
Sovereign multi-agent coordination, execution, and real-time telemetry, open-sourced under Apache-2.0. The same scoped keys and audit discipline as the workspaces, available as a protocol you can read.
1GET /api/polarislink/status2Authorization: Bearer <key>34HTTP/1.1 200 OK5X-PolarisLink-Protocol: Forticia PolarisLink™Latest papers
Infrastructure
First papers are in preparation.
Each piece states what it claims and what it does not. See what the institute has published so far in Papers.
Request access to the infrastructure.
Access is invite-only. Tell us what you are working on and an administrator will review it.