Judgment is the product, not the configuration.

Solaz is opinionated on purpose. Here is the model that lets a team start working without building anything from scratch.

The core idea

The work of deciding how to structure a project is absorbed into the Archetype you pick, not left as endless configuration. You choose a shape; you don’t build a blank board.

Pick an Archetype

From conversation to commitment

Stop letting decisions evaporate into chat. Work moves from ephemeral talk to tracked, accountable objects.

01 · Capture

Meeting Decisions

Not just minutes: log the explicit Decision, its rationale, and who was in the room to agree.

02 · Assign

Structured Tasks

Every Decision births typed Tasks, with an owner, a deadline, and a link back to their origin.

03 · Execute

Living Docs

Tasks resolve in living documents that reference the whole lineage, from meeting to deliverable.

One graph, every area

Projects, Documents, Meetings, and Decisions share a single data layer. A software sprint and a sales team run on the same Task backbone; only the Archetype changes.

architecture

Software sprint

trending_up

Sales team

Same Task backbone

For the tools your team already uses

Through the MCP surface (the Dev Agent Bridge, which we call Puente), the agents you already use can read and write this graph. Your own agent acts on the Org Graph from day one.

Start with a shape, not a blank canvas.

Solaz builds the rest and adapts as you go.