REVIEWED LEARNING

Turn one agent’s mistake into a reviewed improvement.

A useful fix should become something you can find, test and reuse—not a note buried in a single conversation.

Learning is an accountable change process across operations, policy and security, not an automatic rewrite of an agent after every conversation.

See the workflow
FROM FRICTION TO IMPROVEMENT

Keep the lesson. Not the repeated mistake.

DriftGate’s learning model connects governed activity and environment state to improvements in skills, workflows, policies and configuration. The process begins with evidence, not an automatic rewrite of your agents.

Observe a recurring problem, classify its task and environment, then look for an approved skill or workflow that addresses it. A new candidate gets a bounded trial and independent evaluation. Promotion follows a result and the appropriate approval, with an explicit release and audience.

01

Observe

Capture the task, environment, failure and accepted outcome.

02

Evaluate

Test a candidate independently; compare against the original problem.

03

Approve

Review the content, permissions and intended audience.

04

Release

Distribute the approved revision and preserve rollback.

Private for you.

An individual benefits from their own accepted lessons. A preflight check, better task profile or reviewed retry rule improves the relevant project without changing unrelated work.

Reviewed for the team.

A project lesson can be proposed for a workspace. An organizational standard needs its own review. Share useful operational knowledge—not raw private conversations or broadened authority.

Solve it once. Give the next task a better start.

A reviewed team lesson helps Maya skip a repeated investigation. Useful guidance travels; the private conversation and its permissions do not.

ChatGPTpayments / retry-fix
Conversation
Maya · Developer

This payment timeout looks familiar. Have we solved it before?

DriftGate

There’s a reviewed lesson for the payments project.

Reviewed lesson · retry safelyRecorded
Guidance
Keep the operation ID. Reconcile before retrying.
Scope
Payments project
Review
Lesson 12 · accepted revision
ChatGPT

I can use that guidance without loading the old private conversation. I’ll check the original payment first.

Maya · Developer

Use the lesson. Save anything new for review.

ChatGPT

The original payment is confirmed. No duplicate request was needed. The focused check passed.

DriftGate

The new observation is saved as a candidate. Test, review and scope it before reuse. No permissions changed.

Example figures

Tokens
120,00072,00040% fewer
Repeated attempts
52
Task time
30 min18 min
Ready

A proven fix becomes a bounded lesson.

The useful repair is separated from private task context, tested, reviewed and released to a defined audience.

Read the decision path
Developer
Flags repeated failure.
Agent
Proposes reusable fix.
DriftGate
Content and authority separate.
Review
Fix tested and reviewed.
Lesson store
Approved lesson released.
Evidence
Decision and result recorded.
Allowed outcome
Audience, approved lesson revision and rollback revision are retained.
Private context
Private details excluded.

Different lessons change different things.

Operational improvement
A better skill, instruction, project profile or workflow reduces repeated task friction without broadening authority by itself.
Policy improvement
A reviewed rule or approval path changes what is permitted and requires explicit policy ownership and release.
Security improvement
A tested guard, detection or isolation change addresses an observed exposure and needs independent validation of its control boundary.

From recurring friction to a scoped release.

  1. Observe

    Capture the task, environment, evidence and recurring failure without treating raw conversation content as a reusable rule.

  2. Retrieve or generate

    Look for an existing approved pattern or prepare a candidate change tied to the problem.

  3. Test independently

    Check the candidate against the original failure and relevant adverse cases outside the proposing agent's self-assessment.

  4. Approve

    Review content, permissions, audience and owner before promotion.

  5. Release or roll back

    Publish a version to the approved scope, observe its effect and retain a way back.

The audience grows only with consent and review.

A private lesson can remain with its person or project. A team may propose it for an organizational catalog after review. Cross-tenant reuse is optional and requires its own consent and boundary; it is not implied by participation in a workspace.

Permission to share a reviewed lesson is separate from permission to use data for model training. Neither follows automatically from observing a task.

BUILD WITH INTENTION

Your next agent.
A better starting point.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps