Centra
CENTRA · WORKFORCE · IN DEVELOPMENT

Set the direction.
Let the organization
keep moving.

Workforce is being built for company-scale work that spans departments, deadlines, and handoffs. You set the mandate; the organization carries the work forward; consequential decisions still come back to you.

Concept command centerWorkforce organization
In development
Mission

Make reliable AI operations practical for small teams.

Illustrative work graph · development preview

DiscoverValidateDecideBuildLaunchMeasureLearn
Work graph

Illustrative initiatives

3 / 5 funded
Research workspace

12 interviews · demand threshold met

Validate
Team reporting tool

4 of 6 acceptance checks verified

Build
Finance assistant

Revenue observed · retention still open

Measure
Founder decisionRaise the portfolio capital ceiling?

Two initiatives qualify. This change remains reserved for you.

7 departments3 durable seats each1 fenced effect gatewayOpen 1.0 qualification

Company work needs owners, handoffs, and a shared record.

Project timeline with written work, approvals, and progress
THE WORK OUTLIVES THE WORKERPlans, mandates, evidence, dependencies, and decisions remain part of the organization even when the process doing one task is replaced.
01

Developer

Carries software projects from specification through changes, tests, and verified project knowledge.

02

Executive

Keeps priorities, operating decisions, and cross-department work aligned with the direction set by the owner.

03

Research and Development

Gathers evidence, tests hypotheses, runs experiments, and turns findings into work the organization can use.

04

Marketing and Social

Develops positioning, campaigns, publishing, and audience work within the channels and approvals you define.

05

Legal

Reviews the work, applies jurisdictional constraints, keeps records, and escalates when a decision exceeds its mandate.

06

Accounting

Maintains financial records, reconciles activity, follows budgets, and applies stricter controls wherever money is involved.

07

Back Office

Carries vendor work, schedules, support, and the recurring operations that keep a company from falling behind.

The work is planned, carried, and checked by different hands.

Each department separates direction, execution, and review. The role and its mandate persist; the agent process assigned to one piece of work starts fresh.

01

Lead

Turns the department's assignment into clear work: what the mandate permits, what needs to happen, and which decisions belong with the owner.

02

Executor

Carries one bounded task with the tools, data, budget, deadline, and authority provided for that piece of work.

03

Auditor

Reviews the evidence independently. The worker cannot approve its own result, and disagreement can trigger another review.

The company remembers. Each worker starts clean.

01

Fresh process on every wake

Each Lead or Executor wake starts a new isolated process. No transcript, scratchpad, or episodic persona memory survives between wakes.

02

Durable organization, stateless worker

Continuity lives in the signed organizational ledger, global work graph, typed mail, policies, receipts, schedules, and verified project knowledge not inside a long-lived agent identity.

03

Typed WorkPackets

Every wake receives a bounded packet containing the mandate, goal slice, tools, model binding, policy, lease, budget, and deadline required for that assignment.

04

Deterministic execution loop

The kernel owns leases, dependency resolution, scheduling, reconciliation, verification, commit, yield, and sleep so interrupted work can be reconstructed from durable state.

For a persistent named teammate who learns your routines and works across your apps, meet Workmates.

Meet Workmates

The organization can move. Your authority does not.

SIGNED

The owner keeps root authority

Autonomy and approval policies are compiled from signed, non-delegable authority. A seat cannot expand its mandate or promote itself into the owner role.

FENCED

One gateway owns real-world effects

Seat processes never hold effect credentials. External actions pass through a single fenced gateway with policy, lease, budget, and reconciliation checks.

RECONCILED

Ambiguity stops blind retries

If an external effect is uncertain, probes and circuit breakers reconcile against the authoritative system before another attempt can create a duplicate effect.

AUDITED

Completion requires evidence

Receipts and independent review keep activity separate from verified completion. In-flight work is never presented as success.

The foundation is built. The release is not finished.

The public changelog separates what already exists from the qualification still required. Workforce remains in development until those gates close.

01

What exists

The separate Go runtime, seven departments, durable seats and mandates, stateless wake workers, WorkPackets, control plane, mail protocol, scheduler, fenced effects, department skill packs, and initial owner APIs and client surfaces are documented in the current milestone.

02

What remains

The full client surface set, encrypted backup and recovery, retention and cryptographic erasure, enforced resource budgets, overload qualification, and the complete seven-department adversarial release gate remain before Workforce 1.0.

03

What that means here

Workforce is in development. This page explains the intended and partially implemented architecture; it does not claim a finished public product or a completed 1.0 qualification.

Read the source milestone for the exact architecture, completed work, and outstanding 1.0 qualification.

Open the changelog
Set the mandate.Keep the handoffs moving.Hold the authority.

Workforce is in development for people who want company-scale autonomy without giving the company away.