Synthesis WorkSynthesis EngineeringSynthesis CodingSynthesis Writing

The synthesis movement · the public door

Your work should outlive the chat window.

The synthesis work system gives human-AI work a durable home: shared methods, project memory, safeguards, coordination, and evidence you can inspect. It is open, vendor-neutral, and designed to keep working when you change tools.

01 / the rule

Complete, or visibly partial.

One door must account for every layer. A partial setup is legitimate when it is deliberate. A silent gap is not. Each layer should read as installed, declined, or missing, and a check that cannot run must never look like a pass.

02 / the system

More than a skill pack.

The plugin is the public core. The working system includes every layer below. This map shows what the current bootstrap reaches and where the one-door work is still incomplete.

Reached today Exists through separate setup One-door completion work
  1. 01

    Skills

    Portable methods for coding, writing, project management, governance, and operations.

    Reached today
  2. 02

    Session context

    Verified time, active project state, and recovery at the beginning of a session.

    Reached today
  3. 03

    Hooks and gates

    Fail-closed checks for commits, messages, coordination, publishing, and task completion.

    Separate setup
  4. 04

    Agent kernel

    A thin instruction core that carries identity, invariants, routing, and enforcement across clients.

    Completion work
  5. 05

    Runtime engines

    Durable machinery for receipts, safeguards, daily operations, and repository health.

    Separate setup
  6. 06

    Coordination

    Claims, handoffs, and shared project state when several agents work at once.

    Separate setup
  7. 07

    Doctors and conformance

    Checks that distinguish a working system from a system that merely has files installed.

    Separate setup
  8. 08

    Personal policy

    Your voice, preferences, disclosure boundaries, and agent identities in files you own.

    Completion work
  9. 09

    Organization and knowledge

    Personal and shared knowledge bases, plus organization configuration without installer forks.

    Separate setup
  10. 10

    Lifecycle

    Update notices, safe convergence, and receipts that show every installed machine is current.

    Completion work

03 / start

Install the public core.

The current bootstrap installs the native public plugin into supported local clients, activates verified session context, and runs its onboarding doctor. It can also scaffold a personal project workspace. It does not yet claim to produce every layer in the system map.

Path A

Work with an agent

Give this page to a capable local coding agent. Ask it to inspect the public bootstrap, install the synthesis core, run the doctor, and report anything it could not verify.

Installation should be the task's last action before the client restarts.

Path B

Use the terminal

Close active agent sessions, then run the bootstrap on a Mac with command-line tools installed.

curl -fsSL https://raw.githubusercontent.com/synthesisengineering/synthesis-skills/main/onboard.sh | sh

Read the script before running it. Re-running converges or repairs the public core without overwriting files you changed.

Read the result literally

  • Installed means the doctor verified the component it names.
  • Needs you means the installer reached an auth or identity boundary.
  • Missing or unverifiable is work to resolve, not a pass.

04 / where this leads

A system you can leave, and return to.

Native agent memory helps inside one product. Synthesis keeps the work itself in durable, versioned records that different tools and people can read. The harness becomes an adapter. Your project remains yours.