Turn an AI idea into a controlled delivery
A customer reference for understanding who owns each decision, what information makes a phase priceable, how funding aligns with work, and which evidence closes a phase.
The published delivery model at a glance
Business, Advisor, Project Manager, and Rovvi each have a defined role.
The published sequence runs from a defined outcome through signed close.
A bounded phase records outcome, boundary, owner, inputs, evidence, safety, timing, and change rules.
Scope, evidence, safety, and written sign-off must all be visible.
01 · Role map
Four roles with separate decision rights
The Business, AI Advisor, and Project Manager form the operating team. Rovvi supplies the platform, matching, and payment administration.
Choose
Business
Owns: Outcome, priorities, budget, acceptance
Must prove: The result solves the real business need
Build
AI Advisor
Owns: Technical design, implementation, testing, evidence
Must prove: The deliverable works as agreed
Coordinate
Project Manager
Owns: Definition of done, plan, cadence, risks, sign-off
Must prove: Decisions are clear and the phase stays controlled
Protect
Rovvi
Owns: Platform, matching, and payment administration
Must prove: The agreed workflow and payment controls are available
| Decision | Business | Advisor | PM |
|---|---|---|---|
| Business priority | Decides | Advises | Clarifies |
| Technical method | Informed | Decides | Challenges assumptions |
| Definition of done | Approves | Confirms feasibility | Drafts and maintains |
| Acceptance | Decides | Supplies evidence | Records sign-off |
02 · Protected delivery sequence
Money and work move through the same six gates
Under Rovvi’s published engagement structure, each funded phase is bounded enough to understand and meaningful enough to verify.
- 01
Define
One observable outcome and its boundary are recorded.
- 02
Agree
Owners, evidence, price, timing, and change rules are documented.
- 03
Fund
The bounded phase is funded before implementation begins.
- 04
Build
The Advisor works in increments and shares delivery evidence.
- 05
Verify
Evidence is compared with the agreed definition of done.
- 06
Close
Both sides sign off; funds release and the change is recorded.
03 · Phase record
Eight facts make a phase understandable and priceable
These are the data fields a customer should expect to see in a bounded phase record. Missing information signals that the phase needs clarification before pricing.
Outcome
The observable capability a real user receives at the end of the phase.
Boundary
The work and behavior explicitly excluded from the phase price.
Owner
The person authorized to make the final business decision.
Inputs
The data, systems, access, and people required for delivery.
Evidence
The artifact used to demonstrate that the outcome is complete.
Safety
The approvals required before external or irreversible actions.
Timing
The dates and dependencies that control delivery.
Change
The method used to estimate and approve requests outside the boundary.
04 · Phase close data
Four visible gates replace a vague percentage complete
The project agreement model makes close readiness inspectable. This is a process definition—not a Rovvi-generated performance rating.
Scope
The delivered result fits the agreed boundary.
Evidence
The named proof exists and can be inspected.
Safety
Approvals, access, privacy, and rollback were handled.
Sign-off
Open issues are resolved, deferred, or accepted in writing.
05 · Governance comparison
Human approval is essential—but approval without validation has blind spots
This chart compares a common human-only approval model with the AuthorityGate KeyStone reference architecture. It does not claim that every current governance program lacks validation. It isolates the specific case where a person is the only control between changing vendors, changing AI behavior, and an external action.
A person interprets the request and decides whether to approve.
The human owns purpose, acceptable risk, exceptions, and consequential approval.
The reviewer must notice the change in documentation or changed behavior.
Connector identity, declared capability, schema, scope, and expected contract are checked before action.
The person judges the output they can see; hidden behavior changes may appear after approval.
Approved model/configuration, required fields, policy rules, and acceptance tests must still match.
Permission is often implied by tool access or a broad “go ahead.”
Actor, target, action, data boundary, amount, duration, and expiry are evaluated as explicit constraints.
The result depends on whether the reviewer notices uncertainty and stops.
Missing evidence, changed contracts, stale approval, or an out-of-bound action blocks execution and requests a new decision.
Approval may exist as a message or memory without the exact inputs, version, and resulting state.
The request, policy/version, validation result, human decision, execution identity, and read-back are linked.
Human-only governance
AuthorityGate KeyStone
Scope note: This is the proposed AuthorityGate KeyStone governance architecture supplied for this manual. No public product specification or independent benchmark was available to verify implementation or performance, so the chart makes no certification, coverage-percentage, or risk-reduction claim.
06 · Risk response
Approval strength rises with impact and irreversibility
This map shows the response a customer should expect as a proposed change becomes harder to reverse or more consequential.
What happens when a phase drifts
- New work pauses.
- The original outcome is restated.
- Defects are separated from new scope.
- The change becomes a separately estimated decision.
- The approved boundary and decision owner are recorded.
07 · Answer desk
Frequently asked delivery questions
Who owns the business outcome?
The business owns priorities, budget, acceptance, and the final business decision. The Advisor owns the technical approach and evidence. The Project Manager keeps the engagement clear and moving.
What should a good phase contain?
One observable outcome, an explicit definition of done, a bounded price and schedule, named evidence, and a sign-off decision.
When should work begin?
Begin a phase after its scope is agreed, the agreement is signed, and that phase is funded. This keeps expectations and payment protection aligned.
What counts as delivery evidence?
Use proof appropriate to the outcome: a working link, test result, screen recording, before-and-after report, repository change, runbook, or customer acceptance note.
What does AuthorityGate KeyStone add to human approval?
In the reference architecture shown here, KeyStone adds machine-enforced validation before execution: a declared authority boundary, vendor and model conformance checks, policy tests, fail-closed handling, and an evidence receipt. The human still owns intent, exceptions, and the final consequential decision.