01Decide
Your teams answer the open question before any agent starts.
Assent is designed to bring each open question to the teams that own the code, with the evidence. Their approval would bind to the exact version they read.
Concept UI · illustrative data
What this shows
- Decide: A decision from both teams, before any agent starts.
The usual way
Our hypothesisThe agent guesses. The owners find out in review.
When the answer belongs to another team, an agent can pick one anyway, and the owners first see it in a pull request.
What this shows
- Without Assent: The agent guesses, Owners find out in review, Reworking
- With Assent: Owners decide first, The agent works inside that decision, A pull request that says what wasn’t checked
Our working hypothesis: teams explain the same architectural constraints again and again, reconstruct earlier decisions, and discover consequential choices only after an agent has implemented them.
- Constraints explained again and again
- Earlier decisions rebuilt from memory
- Consequential choices found after the code
- Owners reached through the developer
- Approval given to a paraphrase
Step by step
Synthetic exampleOwners see the evidence, then approve the exact version.
In Assent’s design, settled questions are cited, not asked again. The open question would go to both owners, and a later policy change would send it back to them.
What is already decided, what the code does and what is still open, each with its source. Then the approval, bound to the exact revision and the versions it was given under.
State the intent
A developer would describe the change and the expected behavior, from the workspace, the command line or a tracker item. Nobody would write an agent prompt.
Gather the evidence
Assent would collect the decisions that apply, what the code and contracts actually do, conflicts and unknowns. Recommendations would be labelled as proposals.
Ask only what matters
Concerns the evidence can settle would be closed and cited. A choice that materially affects the outcome would go to its confirmed owners.
Approve the exact revision
Owners would see the proposed content, the alternatives, the affected scopes and what approval will start. Approval would bind to that revision.
What this shows
- Expose reservation expiry to Checkout
- Accepted: Reservations owns reservation expiry. DEC-0007 · rev 3
- Accepted: Existing clients must tolerate additive response fields. API standard §2.3
- Observed: Expiry is computed when a reservation is created. services/reservations @ a41f9
- Observed: Checkout reads reservation status through the public API. services/checkout @ a41f9
- Open choice: Duration or absolute timestamp? Provider and consumer owners
- Unknown: Clock behavior on restart. Exploration proposed
- Consumers outside this repository are outside verified coverage, and say so.
Evidence packet Accepted, observed, open and unknown, each kept apart with its source.
What this shows
- Reservation expiry in the public API
- Open question raised: Duration or absolute timestamp? Routed to both owners.
- Revision 2 proposed: Optional absolute expiry timestamp, serialized in UTC.
- Provider owner assented: To rev 2, under policy v14.
- Consumer owner assented: To rev 2, under policy v14.
- Grant GR-7f3a issued: After publication, scoped to the accepted revision.
- Consumer compatibility policy changed: v14 to v15. The code did not change.
- The approval no longer applies: Merge eligibility withdrawn; both owners asked to revalidate.
Approval history If a policy changed after approval, the approval would stop applying.
The design
First buildall six capabilities
Past decisions are cited. Open questions go to their owners.
In Assent’s design, owners approve the exact content on screen, and they see what their approval will start before they give it.
Existing decisions, found and cited
Assent is designed to gather the decisions and constraints that already govern a change and cite the exact source versions. Search ranking would never confer authority.
Evidence sorted by kind
Observed behavior, accepted constraints, options, recommendations and unknowns would stay apart, each with its source version, strength and freshness.
Open questions reach their owners
An unresolved choice would go to the confirmed owners’ attention lists, with the evidence and the alternatives. The developer wouldn’t chase anyone.
Approval binds to the exact revision
Approving would accept the precise content on screen. If that content changes, the approval would not carry over.
See what approval will start
Before approving, owners would see the task package and the stage it will start.
Explore before committing
An exploration grant would let an agent run a reversible spike to answer a question. Its evidence would inform the decision; it would never authorize adoption or merge.
Limits
Assent may recommend. Only your owners decide.
In Assent’s design, agents and AI representatives can’t approve. Owners would come from the assignments your organization confirms.
Laterall three capabilities
- Consultation without approvalAsk a confirmed owner or opt-in expert for a second opinion. The answer would be evidence; it would never count as approval.
- Impact preview before approvalWho is affected (known, possibly affected, unknown), estimated cost and reversibility, shown before anyone approves.
- Decisions that ask to be reviewedSuccess criteria and review-by dates recorded with a decision. Expiry or failed criteria would raise a flag for its owner; nothing would change on its own.
Code describes how the system behaves; accepted decisions describe what was intended.
Neither would silently replace the other.
Owners would come from assignments your organization confirms.
Code owners files and service catalogs suggest candidates; they don’t prove delegation.
A missing policy classification would never permit silently deciding a consequential unknown.
Model confidence would never be a credential.
Only trusted identity, policy and approval records would establish authorization.
Decide04
Does Assent make decisions for us?
No. It is designed to gather evidence and recommend options, labelled as proposals. Accepting a decision would take the authority your organization has confirmed. Agents and AI representatives would never approve.
What if a decision was never written down?
Then the packet would say so. A missing decision that materially affects the change would become a question for its owner; one the evidence can settle would be closed and cited, never invented.
Who counts as an owner?
The people your organization confirms for each concern. Code owners files and service catalogs supply candidates, not proof of who may decide.
Can a decision be approved in chat or by voice?
Not by a message or a spoken yes alone. On every surface, binding approval would need the exact revision on screen and an authenticated, deliberate action. Voice is a later surface, for reading, drafting and consulting.
Design partners
Bring one recent cross-team change.
We reconstruct it with you before showing a solution.
Each stage earned by the one before
Concept diagram
- 01Conversation
- 02Assisted comparison
- 03Shadow analysis
- 04Bounded evaluation
The program ends with a dated decision to continue, revise or stop.
Will it merge or deploy on its own? Not in the first evaluation: people approve decisions and merge. FAQ