Skip to content

The question

Engineering teams should decide how their software behaves, and Assent should run the coding agents that implement those decisions.

The question it is designed to answer for a team is short:
  1. was what we decided implemented correctly,
  2. what was verified and what was not,
  3. and does anything need my decision?

Authority still bounds the agents

Autonomy would grow one step at a time, per kind of change, only when you switch it on and only with evidence.

  1. Watch onlyFirst build
  2. Write codeFirst build
  3. Merge when your policy allowsLater
  4. Release when your policy allowsLater
Stage labels are targets, not availability. Nothing is available yet.Concept diagram

How we work

Working direction · commercial thesis unvalidated

Status of this direction

This direction was adopted on 2026-10-06, replacing an earlier governance-only thesis.

  1. 2026-10-06

    A change of direction

    Assent will run the coding agents rather than only govern the agents a team already uses.

    Decision
  2. 2026-09-10

    Named Assent

    The working name, Engineering Decision Plane, gave way to Assent and the domain useassent.com (decision D15).

    Decision
  3. External evidence

    None yet

    No external willingness-to-pay or pilot outcome evidence exists yet.

  4. Next tests

    Defined in advance, with stop criteria

    The stop conditions are written down before results exist, each with the decision it would put on the table.

Claims reconciled with the product documents on 2026-10-09

Build log

Design partners

Bring one recent cross-team change.

We reconstruct it with you before showing a solution: the decisions, their owners and the effort, agent operation included.