The principles behind it

• Agents are first-class. Every capability is designed for the API and MCP as much as for the screen. Agent tools are workflow-oriented: one call does what a person would do in one step, and every refusal explains the rule that refused it.
• Everything is recorded, and by whom. Each change is attributed to the person whose key or session made it, and Quasar marks when an agent acted on that person's behalf. Event logs keep the history of issues, documents and sprints.
• Retries are safe. Every write accepts an idempotency key, so a repeated call replays instead of duplicating. Every entity carries a version, so two concurrent edits conflict instead of one silently winning.
• Nothing is hidden. An action that cannot run is shown disabled, with the reason. A figure Quasar could not compute says so instead of showing zero.
• Isolation is enforced by the database. Tenant separation relies on PostgreSQL row-level security, not on a filter someone might forget.
• Built with itself. Quasar is planned, built and documented in Quasar, by AI agents working under the workflow it offers, with an architect who supervises and accepts. See Crucial points and objections.