California Synthetic Contact

Concord / Research workbench

Keep scientific work coherent as models, tools, and compute change.

Concord gives a research campaign one durable record: what was intended, what was inspected, what was allowed, what ran, and why the work moved forward.

Starting point
Your existing work
Control
Explicit permissions and limits
Execution
Local and remote
Record
Durable and attributable
One campaign record across changing toolsFiles, models, and tools connect to one campaign record. Planning and approval precede the external effect boundary; execution receipts and review follow it.FILESMODELSTOOLSEFFECT BOUNDARYEXPLICIT APPROVAL01PLAN02APPROVAL03RECEIPT04REVIEWONE CAMPAIGN HISTORY
Campaign perspectiveSystem diagram / 01
FilesModelsTools

One campaign record

PlanApprovalReceiptReview
Effects require permission and approval.

The research loop

One campaign from intent to review.

Concord connects the work across chats, terminals, files, and compute environments.

The Concord research loopA campaign proceeds from intent through planning, approval, execution, and review while every stage remains joined to one durable record.01INTENT02PLAN03APPROVAL04EXECUTION05REVIEWDURABLE CAMPAIGN RECORD
Bounded research loopSystem diagram / 02
  1. 01

    Begin with the work

    Open a project, repository, dataset, or campaign and state the scientific objective.

  2. 02

    Inspect the plan

    Review the relevant files, tools, prior results, and inputs before execution.

  3. 03

    Set the boundaries

    Define permissions, approvals, resource limits, and budgets for the work.

  4. 04

    Run and observe

    Local and remote work returns artifacts, receipts, costs, and failures to the campaign.

  5. 05

    Review and continue

    Accept, correct, or reject the result. Keep the decision and its basis with the work.

System architecture

The record beneath the workbench.

Epact defines the program, authority, and evidence requirements. Concord connects that program to models, capabilities, execution, and campaign history.

Concord operating systemSemantic, authority, and effect topology
PrincipalHuman operatorIntent · approval · judgment
Delegated actorsAgent populationPlans · proposals · reviews
SurfaceWorkbenchAuthor · inspect · intervene
ReplaceableModelsBounded context in · proposals out
QualifiedCapabilitiesTools · adapters · domain methods
Effect surfacesCompute · data · instrumentsReceipts return to the record
EpactOntological plane
One admissible world for every actor
CompilerProgram → ImageNormalize · validate · hash
Canonical centerProgram ImageContent-addressed · deterministic · signable
RuntimeState → EligibilityEvaluate · replay · explain
PrincipalsObjectsCapabilitiesAuthorityObligationsGatesResourcesEvidenceTerminal
Public compositionConcord HarnessContext composition · model loop · capability binding
Public authority runtimeConcord KernelEvaluate · permit · budget · receiptDispatchAllocator enforces lifecycle
Integrated public runtimeConcord CoreCampaigns · artifacts · source gates · review · supervision
Durable planeCampaign historyAccepted events · receipts · artifacts
IndependentVerifier / compatible runtimeSame image · same projection
Public semantic or runtime contract Product surface or deployment adapter

Epact compiles a campaign’s objects, obligations, permitted actions, and evidence rules into a program image.

Concord records the work performed under that program, including proposals, approvals, artifacts, reviews, and execution receipts.

Campaign records

The result keeps its history.

Inspect the inputs, execution, and decisions behind a result as the campaign develops.

01

Inputs

Files, sources, model context, and constraints used for a run.

02

Actions

Proposals, approvals, tools, remote jobs, interruptions, and retries.

03

Results

Artifacts, observations, evidence, costs, and execution receipts.

04

Judgment

Reviews, corrections, rejected paths, and decisions about what to do next.

California Synthetic

We build Concord.

California Synthetic develops the research workbench and the runtime beneath it. The system is built around durable scientific records, replaceable models, and explicit authority over execution.

LanguageEpactPrograms · authority · replay
RuntimeConcordCampaigns · records · effects
ApplicationWorkbenchResearch · execution · review

Concord / In development

Bring an active research campaign.

Get in touch about research, collaboration, or the company.

Request preview