Working draft

PRO-02 Agent Promotion Procedure

How an agent moves up one trust level at a time, with an evidence pack, a cooling-off review and a signed Release Certificate.

Working draft, published openly. This is the version Temei works to. You may read it in full, adapt it and use it in your own organisation. If you would like help fitting it to your tenant, book a call.

FieldValue
OwnerFounder, FIDEVO/AI LABS LIMITED (trading as Temei)
StatusWorking draft, published for open use
Version0.1 draft, 22 November 2026
Reviewyearly, and after every promotion that went wrong
Applies toevery request to raise an agent's Trust Level, including its first use on live data
Sits underPOL-01 Agent Autonomy Policy (sections 5 and 6) · STD-01 Agent Build Standard

An agent moves up one level at a time, only with evidence, and only with a signed Release Certificate. This procedure says how. Demotion and suspension follow POL-01 section 6 and need no procedure: anyone may do them at once.

1. The key idea: the level lives in the write workflow

Agents built to STD-01 never write directly. That lets one agent climb the levels without being rebuilt: only its write workflow changes.

LevelWhere the agent readsWhat its write workflow does
L1 Sandboxtest listswrites to test lists
L2 Read-only, supervisedlive listsshadow mode: records what it would have written in a shadow list (or only answers the agent); nothing live changes
L3 Write, per-action approvallive listsadds an approval step (Human review or Standard approvals) before the write; a person approves each one
L4 Autonomous within boundarieslive listswrites directly, with the duplicate check, and alerts the owner on every failure
L5 Full autonomy in domainlive listsas L4, plus exception rules the agent may apply itself

Changing the level is therefore a small, testable change to one workflow, and going back down is just as small.

2. Roles

RoleDoes
Agent ownerasks for the promotion, builds the evidence pack, runs the hypercare period
Reviewerchecks the pack against the criteria; must not be the builder once Temei has a second person (until then: the founder, after a full cooling-off day)
Approversigns the Release Certificate: the founder for Temei agents; the client's accountable owner for client agents
Platform adminapplies connector or data policy changes the new level needs

3. Steps

  1. Ask. The owner writes a promotion request in Logos: agent, current level, target level, and the live lists or systems it will touch.
  2. Check the data. Compare the live sources with POL-02 section 3. If personal data is involved, record the lawful basis; for L4 and above, complete a DPIA. If special-category data could appear, stop here.
  3. Build the evidence pack (section 4).
  4. Cool off. At least one full day between finishing the pack and reviewing it.
  5. Review. The reviewer scores the pack against the table in section 5 and writes Pass, Pass with conditions or Fail with reasons. A fail returns to step 3; nothing changes.
  6. Prepare the change in the sandbox. Copy the write workflow, apply the level change from section 1, point read tools at the live site only in the copy, and run STD-01 tests T1 to T6 where they apply. Record results.
  7. Apply data policy changes, if any, the day before go-live .
  8. Sign. The approver signs the Release Certificate (section 7).
  9. Go live. Switch the agent and its workflows to the live configuration. Update the register: AutonomyLevel, AgentStatus, Reads, Writes, ReviewDue (no more than 90 days ahead).
  10. Log. Write the decision in Logos with the certificate reference.
  11. Hypercare (section 6).

4. Evidence pack

ItemWhat it contains
Quality Ledgerthe scored sessions at the current level and the R×U average, as ENGRAM requires
Decision logevery decision the agent made in the period, each marked Correct, Wrong or Unclear by a person, with at least 20 marked Correct for L1 → L2
Scope checkproof that nothing was written outside the agent's lists and fields (queries, not screenshots)
Incidentsevery failed run, odd output or stop, with what was done
Test resultsSTD-01 T1 to T6 for the prepared live change
Data checkthe POL-02 class of every live source, lawful basis, DPIA if needed
Stop routehow to stop the agent at the new level, and (L3 and above) how long it took in a test
CostCopilot Credits used per day at the current level and expected at the new one

5. Criteria

From → toPass when
L1 → L23 scored sessions, R×U ≥ 0.75; 20 decisions marked Correct and none Wrong in the last 10; no scope breach; owner confirmed; live sources classed
L2 → L35 scored sessions at L2, R×U ≥ 0.80; shadow writes would have been right in at least 95% of cases; scope re-signed; architecture review; no incidents at L2
L3 → L410 scored sessions at L3, R×U ≥ 0.85; approvers changed or rejected fewer than 5% of proposed writes; no scope breach; data policy review; security and architecture sign-off; failure alerts and incident plan tested; stop route timed under 15 minutes
L4 → L520 scored sessions at L4, R×U ≥ 0.90; external audit or red-team; board sign-off; legal and compliance review

The 95% and 5% figures are Temei additions. They may be raised for a client, never lowered.

6. Hypercare

For 14 days after go-live (30 days for L4 and above):

  • the owner reads every output or every escalation the agent raises, each working day;
  • any Wrong decision, scope breach or failed run is logged the same day;
  • one Wrong decision that changed live data, or any scope breach, triggers demotion under POL-01 section 6;
  • at the end, the owner writes a short close note in Logos: decisions, errors, cost, and whether the review date stands.

7. Release Certificate

One page, kept with the gate. A promotion without it did not happen.

FieldEntry
Agentname and register ID
Ownername
From → toL_ → L_
Scopelive lists and fields read; live lists and fields written; write workflow name
Evidence packlocation and date
Review resultPass / Pass with conditions (list them)
Dataclasses involved; lawful basis; DPIA reference if any
Stop routewhat to switch off, and by whom
Hypercarestart and end dates
Review dateDD Month YYYY (no more than 90 days)
Reviewername, signature, date
Approvername, signature, date

9. Approval

When you adopt this document, record who approved it, their role and the date, and keep that record with your other governance records.