Syclient Research / Technical Notes

Status beforespectacle.

A working record of what Mosaic implements now, what we are testing next, and what remains a longer-term research direction.

ImplementedRuntime + verification

In developmentMemory Plane

RoadmapAgent-focused models

Start with the runtime

Note 01 / Implemented in Close Beta

Inside the current Mosaic Agent runtime.

The first Mosaic release runs locally with Qwen 3.5 9B through Ollama. The runtime turns an objective into a task tree, matches tools to steps, executes work, and keeps logs and artifacts attached to the task.

Operating loopThink → Plan → Act → Verify

Local executionMulti-step planningTool useTask isolationExecution evidenceRecovery

note 01 / runtimeClose Beta

Current boundaryA local beta runtime—not a released foundation model.

Plan + routeworking

Verify + repairworking

✓ Qwen 3.5 9B via Ollama

✓ Logs and artifacts persisted

→ Reliability hardening in progress

Note 02 / Implemented runtime primitive

Completion requires evidence.

Mosaic treats execution and verification as one workflow. Acceptance contracts define the requested deliverables; the runtime captures stdout, stderr, exit codes, source evidence, and artifact checks before work can be accepted.

When a check fails, Mosaic can make a bounded repair attempt using the failure evidence. “Done” is a verified state, not just a generated sentence.

Acceptance contractsExact deliverablesArtifact validationSource evidenceBounded repair

note 02 / verificationImplemented

01Execute requested workdone

02Validate exact deliverablesdone

03Repair failed checksbounded

› run task --isolated

› verify artifacts evidence saved

› repair failed acceptance check

15 stdout: artifact created16 exit_code: 0 · accepted

Note 03 / In development

Memory needs a permission model.

Long-term memory is only useful when the agent knows what it may retain, where it may reuse it, how the information was produced, and when it should be revoked. The Mosaic Memory Plane is being designed around explicit scope and provenance rather than unlimited recall.

Design constraintMemory must be useful, inspectable, scoped, and revocable.

Project scopeSource provenancePermission boundariesRevocationVerified reuse

note 03 / memory planeIn development

May this result be reused in Project B?

SCOPEProject A only

Reuse is blocked outside its original boundary.

PROVENANCEVerified task evidence

The source, run, and acceptance state remain attached.

CONTROLRevocable memory

Stored context can be inspected and withdrawn.

Note 04 / Public evidence + roadmap

Small model work before large model claims.

Syclient’s current public checkpoint is SPM-70M-Vertigo: a ~71M-parameter English decoder-only, Llama-style foundation-model experiment trained from scratch. It is an early research artifact, not evidence of a frontier-model program.

The next credible steps are documented agent-task fine-tunes, reproducible evaluations, and small hybrid/MoE routing experiments. Mosaic Two remains in development with no public checkpoint today.

SPM-70M · publicAgent fine-tunes · plannedHybrid/MoE · plannedMosaic Two · in development

Open the public checkpoint ↗Read the Model Lab plan ↗

note 04 / model evidenceStaged

Publishing ruleNo scale claim without a checkpoint, model card, and evaluation.

PublicSPM-70M

PlannedFine-tunes

PlannedEval suites

PlannedHybrid/MoE

In developmentMosaic Two

Software before silicon. Hardware remains a long-term research possibility.

Syclient Research

We publish the boundary
with the result.