CAPABILITY 18 / 30

One place everyone works

A shared spine, a five-stage work zone per person, and an approval route with a record.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

The alternative to emailing files is not a tidier inbox, it is one place where the team and the system both work. A shared spine holds what is settled, each person gets the same five-stage pipeline, and anything heading outward passes a review that leaves a record. It works on a shared drive, a document library, an object store, or a repository.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

One place, not five copies

The shared workspace

One place the whole team and the assistant both work, so nobody emails a file around and nobody has to ask which copy is current. A shared spine everyone reads, a work zone per person with the same five stages in each, and an approval route that is written down as data rather than remembered.

Loading the workspace.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON

The folder scheme, 59 nodesData · The shared spine (facts, approved, templates, knowledge, plans) with 23 child folders, plus five per person work zones each holding the same five stages, 25 stage folders in all. Every node carries read roles, write roles, what belongs, what does not, and one sentence on why the boundary exists. Also the four providers this shape runs on, the ten role names, and the five stage definitions.Open the file ↗

JSON

Two weeks of activity, 120 eventsData · August 24 to September 6, 2026, across 22 documents and six actors including the assistant. Eight actions: the six named in the brief plus moved to work and returned, which the five stage pipeline needs. Every one of the ten working days has traffic on it. Includes the Meridian Pro one pager going through all five stages, five returns from review each with a reason, and 12 folder plus day pairs where two people were in the same folder.Open the file ↗

JSON

The approval route as dataData · Six triggers, twelve reviewer rules keyed on the kind of piece, the clock in working days, the rejection path, the timeout path with its refusal to approve by silence, and the eight fields an approval record leaves behind.Open the file ↗

MJS

Data builderData · Node ESM. The spine, the stage rules, the documents, and one table of 120 event tuples are all in this file, and the three JSON files are derived from them, so the tree, the feed, and the route cannot drift apart. Run from rebuild/ with node systems/shared-workspace/build-data.mjs.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is

01Settle the spine
Facts, approved work, templates and plans live in one place with stated rules.
02Give everyone the same shape
Intake, in progress, for review, approved, archived. The same five stages for every person.
03Work in the open
Two people in the same folder can see each other, and an agent reads the same path a person does.
04Route the review
What goes outward is reviewed, and a rejection comes back with a reason.
05Leave the record
Every approval writes who, when, and against what version.

WHAT IT READS

A folder scheme with read and write rules
A five-stage pipeline per person
An approval route and its timeout behaviour

WHAT IT CHECKS BEFORE IT SHIPS

Every folder states who may read and who may write
A rejected piece returns with a reason attached
An approval names a person and a version
Nothing outward-facing skips the route

In production: a canonical shared store with per-person work zones and an approval step, in both company systems.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it produces What is being built next