The intended team
A concept for a different kind of software development.
Synq, an intelligentversion control system.
scroll to trace the idea
Synchronous development for small teams: partial work stays local until push; the moving codebase stays legible.
01 / Who it is for
Start with the operating conditions.
Synq is not a universal replacement for Git. It is a concept for a specific phase: the messy, high-context period before a team has become a release machine.
Small enough to talk.
01 / Trust
No formal code-review queue. Contributors own the quality of the work they push.
02 / Presence
People and agents disclose what they are changing before collision becomes a merge problem.
03 / Stable workspaces
A teammate’s in-progress edits never stream into your workspace. You keep the last pushed state: runnable, testable, and deployable.
04 / Scope
A bounded product surface, shared conventions, and willingness to sequence work deliberately.
A premise, not a promise: Synq trades some parallel independence for tighter coordination and immediate awareness.
02 / One directional model
Three environments. Two verbs.
Work begins locally, then pushes into dev. A ship is a release promotion: dev → beta, then beta → prod. There are no feature branches, release branches, or review gates in the basic model.
Interactive model / click through the promotion pathstate 00
synq / project: northstarenvironment topology
prod
Always behind or caught up with beta. The live, trusted surface.
waiting for a ship
ship / checkout tax flowfrom beta · verified
beta
Always behind or caught up with dev. The proving ground.
waiting for a ship
ship / checkout tax flowfrom dev · release candidate
dev
The shared development environment. Local work enters here through a push, which synchronizes changes and resolves their freeze.
local change frozen
local / checkout tax flowapi/tax.ts · 42 lines · frozen
push / checkout tax flowlocal → dev · synced + unfrozen
Push synchronizes a local change into dev and unfreezes its affected logic. Ship names a release promotion: dev → beta or beta → prod. The environments remain directional: prod is always behind or caught up with beta; beta is always behind or caught up with dev.
03 / The Synq method
Synchronous coordination. Stable local workspaces.
Git makes it easy for people to work apart, then reconcile later. Synq asks a different question: what if active work made its dependency surface visible to the team without streaming partial edits into everyone else’s workspace?
A change freezes the part of the system that depends on the change.
As code is edited, Synq continuously infers the affected logic surface. A file may be frozen, but so may a logic chain, a contract, a test surface, or a generated output. The aim is not to control people. It is to make simultaneous change visible before it creates an untestable or ambiguous state.
api/tax.ts
cart total
checkout UI
auth session
pricing spec
The edit stream is idle. Synq is ready to map the next change as it happens.
04 / A methodological fork
Not Git with different words.
Synq changes the point at which a team sees and resolves coupling. It is a coordination model, not merely another version-control interface.
Question
Git methodology
Synq methodology
Coordination
People work independently, then merge their histories.
People surface overlapping work first; the affected logic is frozen while one path moves.
Unit of motion
Commits, branches, pull requests, releases.
A local push into dev, its dependency chain, and a one-way ship through beta and prod.
Conflict signal
Usually appears at merge, test, review, or production time.
Appears as an edit evolves: Synq maps the affected paths and freezes them in real time.
Working copy
Each branch and merge base can diverge independently.
A teammate’s partial edit stays local. Everyone else remains on the last pushed, runnable state until the change enters dev.
Interface
CLI-first, with many surrounding services.
Desktop-first: a shared, living map of environments, freezes, agents, tests, and current work.
05 / The operating contract
Adapt the team before adopting the tool.
Synq works when the workflow is designed around its assumptions. These are not features to bolt on later; they are the small-team habits that make the model useful.
Make dev the honest shared source of motion.
Work locally, then push to dev. Do not maintain hidden branches or side channels that create a second truth.
Let Synq observe the edit surface.
As humans and agents edit, Synq maps the dependency surface and freezes affected paths in real time.
Treat a push as a synchronization event.
A push releases a local frozen chain into dev, syncs the work to the team, and announces what changed, why, and which tests now matter.
Keep every workspace runnable.
A freeze stops overlapping changes from entering the shared path; it does not make a teammate’s working copy partial, broken, or undeployable.
Ship deliberately, one step at a time.
Ship is the release verb: dev ships to beta, then beta ships to prod. This keeps the three environments ordered without inventing a release bureaucracy.
Graduate when the team outgrows it.
For large, low-context, regulated, or globally distributed teams, Git-style asynchronous coordination may be the better fit.
06 / The primary surface
A desktop app, not a command tucked into the terminal.
Synq centers the desktop app as the place where team state becomes visible and actionable: environments, live dependency surfaces, active freezes, tests, and release decisions.
northstar / devall systems legible
Active logic surface
A map of the code that is moving, blocked, or ready to travel.
checkout / tax calculationfrozen · Maya + agent-2
test / pricing regressionqueued · beta
auth / sessionsavailable
catalog / cache strategyavailable
07 / Intelligent PM
Create an issue once. Let the work move the board.
Synq already gathers edit context to understand dependency paths and manage freezes. The same AI layer can connect that live context to an issue, so the project board follows the work instead of asking contributors to narrate it twice.
ISS-42 / tax-correct checkoutissue created once · context follows automatically
to do01
issue existsTax-correct checkout
No active edit or mapped dependency surface yet.
in progress02
edit observedapi/tax.ts
Freeze opened. Three dependent paths are now visible on the project map.
done03
ship observedrelease confirmed
The configured ship or deployment has reached its intended environment.
The board remains a compact view of the real work: issue intent + edit context + dependency map + deployment evidence.
08 / Open questions
Work left to do.
This concept should earn its model through experiments with real teams—not through a promise to eliminate conflict everywhere.