Neptune Vibes

How this studio is built

How one task runs, and how work is handed over

Workflow & Collaboration

Every unit of work runs the same loop, so any Agent can pick up another's state from three files: what happened, what's in flight, and what shipped.

Workflow & Collaboration: how it runs, as a flowchart1A task beginsa request, to the Agent that owns the folderThe Owner or an Agent2Progress logged as it happensa dated work-log entry with every commitThe working Agent3State kept in one short filea current-state file the next session reads firstThe working Agent4Milestone written oncea milestone entry, to the devlogThe working Agent5Publishedthe post, to the public site once the Owner deploysDevlog Sync routineWorkflow & Collaboration: how it runs, as a flowchart1A task beginsBy The Owner or an Agenta request, to the Agent that owns thefolder2Progress logged as it happensBy The working Agenta dated work-log entry with every commit3State kept in one short fileBy The working Agenta current-state file the next sessionreads first4Milestone written onceBy The working Agenta milestone entry, to the devlog5PublishedBy Devlog Sync routinethe post, to the public site once theOwner deploys

The pieces

What happened
An append-only log. Corrections are new entries, never rewrites.
What's in flight
A short working file a fresh session reads cold, so every line has to still be true. A line cap is what forces someone to read it.
What shipped
The public milestone entries this site is built from.

Where this was worked out