think-wide.
The component workshop

A space to think across projects

Find the connection.
Keep the context.

Evidence side by side. Your judgment in the loop.
A clearer next step for the person or agent doing the work.

Explore the components
Synthetic workshop

Authored sample evidence and local interactions. Repository access, durable decisions, and live reasoning are not connected.

06 components 02 themes

01 / Look at the evidence

Source ASynthetic

atlas-api

src/commands/receipt.ts

Commit aaaaaaaLines 1–5
const previous = await receipts.find(key);
if (previous) return previous.result;

const result = await execute(command);
await receipts.save(key, result);
Source identity
Fixture ID
source-a
Fixture commit
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Blob
90f1e1ce84cc57b8cc0380430388d424b41af5af
Byte range
[0, 154)
SHA-256
092b7a541ba30913a69aa1735b30815d254da83ed42f92b12eb36ba26610df58
Provenance
Authored workshop sample. Exact Git bytes and hashes are not connected.
Source BSynthetic

orbit-worker

src/jobs/deduplicate.ts

Commit bbbbbbbLines 1–5
const receipt = await store.lookup(job.key);
if (receipt) return receipt.output;

const output = await processJob(job);
await store.record(job.key, output);
Source identity
Fixture ID
source-b
Fixture commit
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Blob
dd40f7e12395e4d077a608fdfed38382dd2282cf
Byte range
[0, 156)
SHA-256
c034feecd14b4886289e878c834074ed615a4246f5b61c13bf5629dda17158c5
Provenance
Authored workshop sample. Exact Git bytes and hashes are not connected.
A possible connectionHypothesis

A shared contract for repeated commands

Both samples look up a receipt before doing work. A common request-key contract could make retry behavior easier to reason about across projects.

Still unknown: concurrent requests, changed payloads, and atomic writes. Similar syntax does not prove equivalent behavior.

Based on 2 synthetic sources · not verified

02 / Shape the next step

Human direction

Your judgment belongs here

Suggested by the agent Does the contract apply without the persistent worker?

You know the constraints. Give the next comparison a better starting point.

Local preview only. Drafts stay while switching workshop views; reloading clears them.

From insight to implementationSample brief

Make the contract reusable

# Implementation brief · synthetic sample

Scope
Define a shared command-receipt interface.

Constraints
• Keep execution inside each project.
• Do not introduce a persistent worker.

Evidence
• source-a: atlas-api / receipt.ts (1–5)
• source-b: orbit-worker / deduplicate.ts (1–5)
Authored samples; exact Git references pending.

Acceptance
Same key + same arguments reuses the result.
Same key + changed arguments is a conflict.
Test concurrent requests before adoption.

Exports this synthetic text. No issue is created and no agent is dispatched.

Composition inspector Contract 0.1.0

Edit the JSON, then apply it to change the component layout above. Invalid layouts leave your current view and decision draft intact. This only changes the local preview; it does not save a decision.

Only the six registered components and their reviewed properties are accepted. Maximum 16 nodes, depth 4, and 32 KiB. This is a UI workshop using the public contract with synthetic data.