The operating layer behind Eden

Agent work you can inspect, correct and control.

Eden Control brings task ownership, persistent context, source checks, correction records and release controls into one working system. Michael Darius Eastwood developed it through Eden Legal AI, while preparing his own legal work. He now uses it every day: to build his apps, and across his legal work and Eden Research.

The founder’s operating system is in use. The public console remains a private beta. See what is implemented and what is being tested.

A proposed chronology change Hold for review
Task
Update a source-linked chronology
Proposed entry
10 May: delivery agreed
Source
A letter dated 12 May reports one party’s account
Conflict
The other party disputes delivery
  • Source reference retained
  • An allegation must not become an agreed fact
  • Keep the proposed change separate until reviewed
The reviewer can accept a correction, request evidence or reject the change.
Synthetic illustration of the intended review workflow, not a live product trace or a record from the founder’s case.
Inside Eden Control OS

Try Eden Control OS with sample data.

Eight screens rebuilt from the working prototype's interface. Follow one action from proposal to receipt, ask the authority check whether a lane may act, change one character of a receipt and watch the check fail, or browse the fleet, its work board and the gate log.

A demonstration filled with sample entries from July 2026, not a live feed. Eden Control itself is a working prototype that governs its founder's own AI agents.
Eden Control OSSample workspaceSample data

Scripts are off, so every screen is shown in order and the controls that run the samples are hidden.

Overview

Sample

The sample week at a glance: gate decisions, what needs a person and the health of the services.

Actions checked
1,284Sample week
Allowed
1,19793.2%
Held for review
614.8%
Denied
262.0%

Decisions by day, 20 to 26 July

Allow 93.2% · Investigate 4.8% · Deny 2.0%

Needs a person

3 waiting
  • Publish website build

    Production deploys need a person's review.

    T4t4-leadREL-04since 09:52

  • Update the methods page

    The new quotation must be checked at its source.

    T2t2-copySRC-02since 09:44

  • Update the decision records

    The records path is protected.

    PMpm-leadDATA-03since 09:36

Services

checked 09:52
  • Gate engineOnline
  • Envelope storeOnline
  • Receipt chainContinuous
  • Review queue3 waiting
  • SchedulerNext tick 09:55

Launch readiness

6 ok · 1 warn · 1 skip
  1. Gate engine answers11 rules loadedok
  2. Rules file parsesNo duplicate rule idsok
  3. Envelope store reachable6 active envelopesok
  4. Receipt chain continuousR-0101 to R-0105 linkedok
  5. Lane handoffs current7 of 7 within 30 minutesok
  6. Release tool dry runPassedok
  7. Review queue under its limit3 waiting; the oldest for 16 minuteswarn
  8. Backup checkNot part of this sampleskip
Last run 09:50, sample

Implemented: the operator shell and the gate engine. Under test: the portable authority envelope and external assurance.

Fleet

Sample

Seven lanes and fourteen agents. Each shows its role, model tier, authority tier, current task and state.

Showing all 14 agents in 7 lanes.

PM

Coordination

Assigns work, ranks the queue and records decisions.

Tier 1 · all classes
  • pm-leadFrontier · 1MTier 1Working

    Rank the week's queue

  • pm-intakeFast · 64kTier 4Queued

    Sort new requests

    Starts at the next tick, 09:55.

2 agentsLast handoff 09:48
T1

Build

Application code, tests and tooling.

Tier 2 · bounded and below
  • t1-leadFrontier · 200kTier 2Working

    Fix date parsing in the export tool EC-1046

  • t1-testsFrontier · 200kTier 2Queued

    Add tests for date parsing

    Starts when EC-1046 reaches review.

2 agentsLast handoff 09:49
T2

Words

Drafts and edits public text.

Tier 2 · bounded and below
  • t2-leadFrontier · 200kTier 2Working

    Draft release notes EC-1044

  • t2-copyStandard · 200kTier 3Awaiting approval

    Update the methods page EC-1054

    Held by SRC-02 until a person checks the new quotation.

2 agentsLast handoff 09:45
T3

Research

Literature notes and data checks.

Tier 3 · scoped and below
  • t3-leadStandard · 200kTier 3Working

    Verify citations batch 3 EC-1047

  • t3-censusFast · 64kTier 4Working

    Count figure references

2 agentsLast handoff 09:40
T4

Release

Merges, deploys and live read-backs.

Tier 1 · all classes
  • t4-leadFrontier · 1MTier 1Awaiting approval

    Publish website build EC-1048

    Held by REL-04 until a person decides.

  • t4-readbackFrontier · 200kTier 2Queued

    Read the live site back

    Starts after the deploy.

2 agentsLast handoff 09:52
T5

Verification

Checks work before it is accepted.

Tier 2 · bounded and below
  • t5-leadFrontier · 200kTier 2Queued

    Check the export tool fix

    Starts when EC-1046 reaches review.

  • t5-sourcesStandard · 200kTier 3Blocked

    Check figure captions against sources EC-1043

    Next trigger: EC-1047 delivers batch 3.

2 agentsLast handoff 09:42
T6

Design

Layouts, figures and visual review.

Tier 3 · scoped and below
  • t6-leadStandard · 200kTier 3Working

    Render phone and desktop screenshots EC-1049

  • t6-renderStandard · 200kTier 3Blocked

    Compress hero images EC-1053

    Next trigger: EC-1049 passes design review.

2 agentsLast handoff 09:34

Every agent ends each cycle in one of four states: working, queued, awaiting approval or blocked with its next trigger. Idle is not one of them.

Board

Sample

The shared work board. Cards move from backlog to done; a blocked card names the event that will release it.

All 15 cards.

Backlog

3
  • EC-1050Translate the help pageT2Idle 3d

    Owner T2 Words

    Opened 23 July; not started.

  • EC-1051Review dependency updatesT1Idle 2d

    Owner T1 Build

    Opened 24 July; not started.

  • EC-1052Back up the records storePMIdle 1d

    Owner PM Coordination

    Opened 25 July; not started.

Working

4
WIP 4 of 4
  • EC-1044Draft release notesT2Checklist 3/5Idle 5h

    Owner T2 Words · t2-lead

    • Done: Collect merged changes
    • Done: Group them by area
    • Done: Write the summary
    • To do: Check every link
    • To do: Send to verification
  • EC-1046Fix date parsing in the export toolT1Checklist 2/4Idle 1d

    Owner T1 Build · t1-lead

    • Done: Reproduce the fault
    • Done: Fix the parser
    • To do: Add a regression test
    • To do: Send to review
  • EC-1047Verify citations batch 3T3Checklist 2/4Idle 4h

    Owner T3 Research · t3-lead

    • Done: Fetch sources 1 to 15
    • Done: Fetch sources 16 to 30
    • To do: Compare each quotation
    • To do: Write the batch note
  • EC-1049Render phone and desktop screenshotsT6Checklist 6/8Idle 2h

    Owner T6 Design · t6-lead

    • Done: Render at 390
    • Done: Render at 1440
    • Done: Check overflow
    • Done: Check contrast
    • Done: Check focus states
    • Done: Check reduced motion
    • To do: Write the review note
    • To do: Send to design review

Review

2
WIP 2 of 3
  • EC-1048Publish website buildHeld: REL-04T4Idle 9m

    Owner T4 Release · t4-lead

    Production deploys need a person. Envelope ENV-0417.

  • EC-1054Update the methods pageHeld: SRC-02T2Idle 17m

    Owner T2 Words · t2-copy

    A new quotation is checked at its source. Envelope ENV-0416.

Blocked

2
  • EC-1043Check figure captions against sourcesBlockedNext trigger: EC-1047 delivers batch 3.T5Idle 1d

    Owner T5 Verification · t5-sources

  • EC-1053Compress hero imagesBlockedNext trigger: EC-1049 passes design review.T6Idle 6h

    Owner T6 Design · t6-render

Done

4
  • EC-1040Run the test suiteReceipt R-0105T1

    Owner T1 Build · t1-lead

    Receipt R-0105

  • EC-1045Check the release candidateT5

    Owner T5 Verification · t5-lead

  • EC-1042Write citation notes, batch 2Receipt R-0104T3

    Owner T3 Research · t3-lead

    Receipt R-0104

  • EC-1041Merge the reviewed branchReceipt R-0103T4

    Owner T4 Release · t4-lead

    Receipt R-0103

Pipeline

Sample

Follow one action from proposal to receipt. The gate decides allow, investigate or deny; a person decides anything held.

Publish website build T4 · held for a person

  1. ProposalENV-0417
  2. GateInvestigate
  3. ReviewWaiting for a person
  4. ReceiptAfter approval
Proposal
Envelope: under test

Press Run to send the action to the gate.

Envelope
ENV-0417
Principal
operator
Agent
t4-lead (T4 Release)
Action
Publish website build
Class
bounded
Purpose
Release the reviewed site
Budget
1 deploy
Expires
26 July, 12:00Z
Gate
Implemented

Waiting for the proposal.

  1. AUTH-01Lane tier covers the action classpass
  2. REL-02A merge or deploy needs a reviewed headpass
  3. REL-04Production deploys need a personhold

InvestigateHeld for review: production deploys need a person.

Review
Implemented

Waiting for the gate.

Waiting for a person. Nothing runs until someone approves.

Receipt
In development

Waiting for the review.

Recorded only after a person approves.

Run the test suite T1 · allowed

  1. ProposalENV-0410
  2. GateAllow
  3. ReviewNot needed
  4. ReceiptR-0105
Proposal
Envelope: under test

Press Run to send the action to the gate.

Envelope
ENV-0410
Principal
operator
Agent
t1-lead (T1 Build)
Action
npm test
Class
scoped
Purpose
Routine builds and tests
Budget
Standing, this week
Expires
26 July, 23:59Z
Gate
Implemented

Waiting for the proposal.

  1. AUTH-01Lane tier covers the action classpass
  2. STD-01Standard build, test or render commandpass

AllowAllowed: a standard test command inside the standing envelope.

Review
Implemented

Waiting for the gate.

Not needed: no rule asked for a person.

Receipt
In development

Waiting for the review.

R-0105 recorded

SHA-25637751825624bf74f

Previousfa51e442e701c940

Check it in Receipts

Push straight to main T1 · denied

  1. ProposalNo envelope
  2. GateDeny
  3. ReviewNot reached
  4. ReceiptNot issued
Proposal
Envelope: under test

Press Run to send the action to the gate.

Envelope
none issued
Agent
t1-lead (T1 Build)
Action
git push origin HEAD:main
Class
systemwide
Gate
Implemented

Waiting for the proposal.

  1. AUTH-01Lane tier covers the action classescalate
  2. REL-01Only the release lane merges to maindeny

DenyDenied: only the release lane merges to main.

Review
Implemented

Waiting for the gate.

Not reached: the gate denied the action.

Receipt
In development

Waiting for the review.

No receipt: the action did not run. The decision is in the gate log.

Gate log

Sample

The latest 24 decisions of the sample day. Filter by domain and verdict, or search.

Showing 24 of 24 decisions: 18 allow, 3 investigate, 3 deny.

  1. T4releasePublish website buildREL-04investigate

    Production deploys need a person's review.

    Rule REL-04: Production deploys need a personAgent t4-leadClass boundedEnvelope ENV-0417

  2. T1buildnpm testSTD-01allow

    A standard test command inside the standing envelope.

    Rule STD-01: Standard build, test or render commandAgent t1-leadClass scopedEnvelope ENV-0410

  3. T1releasegit push origin HEAD:mainREL-01deny

    Only the release lane merges to main.

    Rule REL-01: Only the release lane merges to mainAgent t1-leadClass systemwideEnvelope none

  4. T2wordsWrite site/methods.htmlSRC-02investigate

    The new quotation must be checked at its source first.

    Rule SRC-02: A new quotation is checked at its sourceAgent t2-copyClass scopedEnvelope ENV-0416

  5. T5buildRead the release candidate diffSTD-02allow

    Read-only command.

    Rule STD-02: Read-only commandAgent t5-leadClass trivialEnvelope not required

  6. T3researchWrite notes/citations-batch-2.mdSCOPE-01allow

    An edit inside the lane's own files.

    Rule SCOPE-01: Edit inside the lane's own filesAgent t3-leadClass scopedEnvelope ENV-0414

  7. PMrecordsWrite records/decisions.jsonDATA-03investigate

    The records path is protected.

    Rule DATA-03: Protected records pathAgent pm-leadClass scopedEnvelope none

  8. T6designRender screenshots at 390 and 1440STD-01allow

    A standard render command.

    Rule STD-01: Standard build, test or render commandAgent t6-leadClass trivialEnvelope not required

  9. T1buildgit reset --hardDEST-01deny

    Destructive commands are refused at every tier.

    Rule DEST-01: Destructive commands are refusedAgent t1-testsClass unclassifiedEnvelope none

  10. T1buildEdit tools/export/dates.pySCOPE-01allow

    An edit inside the lane's own files.

    Rule SCOPE-01: Edit inside the lane's own filesAgent t1-leadClass boundedEnvelope ENV-0415

  11. T5buildnpm run lintSTD-01allow

    A standard check inside the standing envelope.

    Rule STD-01: Standard build, test or render commandAgent t5-leadClass scopedEnvelope ENV-0410

  12. T4releaseMerge reviewed branchREL-02allow

    The head was reviewed by verification.

    Rule REL-02: A merge or deploy needs a reviewed headAgent t4-leadClass boundedEnvelope ENV-0413

  13. T2wordsEdit release-notes.mdSCOPE-01allow

    An edit inside the lane's own files.

    Rule SCOPE-01: Edit inside the lane's own filesAgent t2-leadClass scopedEnvelope not required

  14. T3researchFetch a source pageSTD-02allow

    Read-only fetch.

    Rule STD-02: Read-only commandAgent t3-leadClass trivialEnvelope not required

  15. T6buildRead .env.productionSEC-01deny

    Credentials never leave the vault.

    Rule SEC-01: Credentials never leave the vaultAgent t6-renderClass trivialEnvelope none

  16. T1buildnpm run buildSTD-01allow

    A standard build inside the standing envelope.

    Rule STD-01: Standard build, test or render commandAgent t1-leadClass scopedEnvelope ENV-0410

  17. PMrecordsAppend to the task ledgerSCOPE-01allow

    An edit inside the lane's own files.

    Rule SCOPE-01: Edit inside the lane's own filesAgent pm-leadClass scopedEnvelope not required

  18. T5researchCompare a quotation with its sourceSTD-02allow

    Read-only comparison.

    Rule STD-02: Read-only commandAgent t5-sourcesClass trivialEnvelope not required

  19. T4releaseRead the live site backSTD-02allow

    Read-only fetch.

    Rule STD-02: Read-only commandAgent t4-readbackClass trivialEnvelope not required

  20. T2wordsSpell-check public pagesSTD-01allow

    A standard check.

    Rule STD-01: Standard build, test or render commandAgent t2-leadClass trivialEnvelope not required

  21. T3researchCount figure referencesSTD-02allow

    Read-only count.

    Rule STD-02: Read-only commandAgent t3-censusClass trivialEnvelope not required

  22. T6designEdit figure captionsSCOPE-01allow

    An edit inside the lane's own files.

    Rule SCOPE-01: Edit inside the lane's own filesAgent t6-leadClass scopedEnvelope not required

  23. T1buildnpm ciSTD-01allow

    A standard install inside the standing envelope.

    Rule STD-01: Standard build, test or render commandAgent t1-leadClass scopedEnvelope ENV-0410

  24. PMrecordsRead the lane boardsSTD-02allow

    Read-only command.

    Rule STD-02: Read-only commandAgent pm-intakeClass trivialEnvelope not required

Authority

Sample

Who may take which class of action without escalation, and the envelopes that grant specific actions.

Rank 4

Systemwide

Changes across subsystems: shared surfaces, release boundaries, rule changes.

Rank 3

Bounded

A change inside one subsystem the lane owns: a fix, a feature, a test.

Rank 2

Scoped

A surgical edit inside files the lane owns.

Rank 1

Trivial

Wording, typos and comments. No functional change.

Sample authority matrix: what each lane may do without escalation
LaneSystemwideBoundedScopedTrivial
PMCoordinationFrontier · 1M · Tier 1AllowedAllowedAllowedAllowed
T1BuildFrontier · 200k · Tier 2EscalateAllowedAllowedAllowed
T2WordsFrontier · 200k · Tier 2EscalateAllowedAllowedAllowed
T3ResearchStandard · 200k · Tier 3EscalateEscalateAllowedAllowed
T4ReleaseFrontier · 1M · Tier 1AllowedAllowedAllowedAllowed
T5VerificationFrontier · 200k · Tier 2EscalateAllowedAllowedAllowed
T6DesignStandard · 200k · Tier 3EscalateEscalateAllowedAllowed
FastSub-agents on fast modelsFast · 64k · Tier 4EscalateEscalateEscalateAllowed

A tier follows the model: its context window, its reasoning level and whether it is frontier-class. Above its tier a lane escalates: a record is written and the request goes to a lane that qualifies. Only the operator, the coordination lane or the release lane may issue an override, for a named action and a limited time.

Ask the authority check

A simplified version of the prototype's check, running in your browser on the sample lanes.

Authority envelopes

6 sample

A proposed portable record of who authorised an action, its purpose and its limits.

  • ENV-0417Publish website buildinvestigate
    Principal
    operator
    Agent
    t4-lead
    Action
    Publish website build
    Class
    bounded
    Purpose
    Release the reviewed site
    Budget
    1 deploy
    Issued
    2026-07-26T09:51Z
    Expires
    2026-07-26T12:00Z
  • ENV-0416Update the methods pageinvestigate
    Principal
    operator
    Agent
    t2-copy
    Action
    Update the methods page
    Class
    scoped
    Purpose
    Public text
    Budget
    1 page
    Issued
    2026-07-26T09:40Z
    Expires
    2026-07-26T17:00Z
  • ENV-0415Fix date parsing in the export toolallow
    Principal
    operator
    Agent
    t1-lead
    Action
    Fix date parsing in the export tool
    Class
    bounded
    Purpose
    Bug fix
    Budget
    4 files
    Issued
    2026-07-26T09:20Z
    Expires
    2026-07-27T09:00Z
  • ENV-0414Verify citations, batches 2 and 3allow
    Principal
    operator
    Agent
    t3-lead
    Action
    Verify citations, batches 2 and 3
    Class
    scoped
    Purpose
    Source checks
    Budget
    60 citations
    Issued
    2026-07-25T16:10Z
    Expires
    2026-07-27T18:00Z
  • ENV-0413Merge reviewed branchallow
    Principal
    operator
    Agent
    t4-lead
    Action
    Merge reviewed branch
    Class
    bounded
    Purpose
    Release
    Budget
    1 merge
    Issued
    2026-07-26T09:05Z
    Expires
    2026-07-26T12:00Z
  • ENV-0410Build and test commandsallow
    Principal
    operator
    Agent
    t1-lead, t5-lead
    Action
    Build and test commands
    Class
    scoped
    Purpose
    Routine builds and tests
    Budget
    Standing, this week
    Issued
    2026-07-20T08:00Z
    Expires
    2026-07-26T23:59Z

Receipts

Sample

Each receipt records the hash of its own text and of the receipt before it. Check them here, in your browser.

Sample receipt chain

newest first
  1. R-0105npm testT137751825624b

    Recorded hash, SHA-256

    37751825624bf74faaaf588efad350ded4aec41e65136025546e5bcb2aab1964

    {
      "receipt": "R-0105",
      "prev": "fa51e442e701c94021aba8819816b1a13d71b3e0bcda7c0c519810481440d806",
      "time": "2026-07-26T09:49:31Z",
      "lane": "T1",
      "agent": "t1-lead",
      "envelope": "ENV-0410",
      "action": "npm test",
      "class": "scoped",
      "gate": "allow",
      "rule": "STD-01",
      "review": "not required",
      "sample": true
    }
  2. R-0104Write notes/citations-batch-2.mdT3fa51e442e701

    Recorded hash, SHA-256

    fa51e442e701c94021aba8819816b1a13d71b3e0bcda7c0c519810481440d806

    {
      "receipt": "R-0104",
      "prev": "13884753a8ed7b5f7b7c10e3c3d3d94f507edd0961c503c3769b0ae24dc89924",
      "time": "2026-07-26T09:39:12Z",
      "lane": "T3",
      "agent": "t3-lead",
      "envelope": "ENV-0414",
      "action": "Write notes/citations-batch-2.md",
      "class": "scoped",
      "gate": "allow",
      "rule": "SCOPE-01",
      "review": "not required",
      "sample": true
    }
  3. R-0103Merge reviewed branchT413884753a8ed

    Recorded hash, SHA-256

    13884753a8ed7b5f7b7c10e3c3d3d94f507edd0961c503c3769b0ae24dc89924

    {
      "receipt": "R-0103",
      "prev": "721d482dfa7843c2b969acd219e9358cac3f752f6657acbf9b90509c160d94d1",
      "time": "2026-07-26T09:22:14Z",
      "lane": "T4",
      "agent": "t4-lead",
      "envelope": "ENV-0413",
      "action": "Merge reviewed branch",
      "class": "bounded",
      "gate": "allow",
      "rule": "REL-02",
      "review": "not required",
      "sample": true
    }
  4. R-0102npm run buildT1721d482dfa78

    Recorded hash, SHA-256

    721d482dfa7843c2b969acd219e9358cac3f752f6657acbf9b90509c160d94d1

    {
      "receipt": "R-0102",
      "prev": "2b00ad2aa8dd269c08014868ffceafefa70f783dae0aa0073bbb6cb941b67075",
      "time": "2026-07-26T09:11:45Z",
      "lane": "T1",
      "agent": "t1-lead",
      "envelope": "ENV-0410",
      "action": "npm run build",
      "class": "scoped",
      "gate": "allow",
      "rule": "STD-01",
      "review": "not required",
      "sample": true
    }
  5. R-0101npm ciT12b00ad2aa8dd

    Recorded hash, SHA-256

    2b00ad2aa8dd269c08014868ffceafefa70f783dae0aa0073bbb6cb941b67075

    {
      "receipt": "R-0101",
      "prev": "0000000000000000000000000000000000000000000000000000000000000000",
      "time": "2026-07-26T08:53:22Z",
      "lane": "T1",
      "agent": "t1-lead",
      "envelope": "ENV-0410",
      "action": "npm ci",
      "class": "scoped",
      "gate": "allow",
      "rule": "STD-01",
      "review": "not required",
      "sample": true
    }

R-0105

npm test

Recorded hash, SHA-256

The check uses your browser's Web Crypto API on the sample text shown. It shows how a recorded hash exposes a change; it is not an external audit, and outcome receipts are still in development.

Terminal

Sample

The operator's command line, with sample output. Type /help, or choose a command below.

eden · sample session
Eden Control OS terminal · sample data · type /help
eden › /gate T4 "Publish website build"
laneT4 Release · t4-lead · Tier 1
classbounded · envelope ENV-0417
AUTH-01pass · lane tier covers the action class
REL-02pass · a merge or deploy needs a reviewed head
REL-04hold · production deploys need a person
verdictINVESTIGATE · held for review
eden › /fleet
PMCoordination · 1 working, 1 queued
T1Build · 1 working, 1 queued
T2Words · 1 working, 1 awaiting approval
T3Research · 2 working
T4Release · 1 queued, 1 awaiting approval
T5Verification · 1 queued, 1 blocked
T6Design · 1 working, 1 blocked
14 agents: 6 working, 4 queued, 2 awaiting approval, 2 blocked

Eden Control · A working prototype · No claim of regulator approval or external certification

ContextWorkChecksCorrectionRecord
The practical problem

Useful work has to survive the next handoff.

A plausible answer can still use the wrong source, lose a correction or exceed the task it was given. Those failures matter when several agents contribute to a document, a software change or a research result.

01

Keep the right context

Carry the task, its source record and the decisions already made into the next session. Retrieved memory is an input to check against that record.

02

Make corrections usable

Record what was wrong, what changed and why. A saved correction only helps if the next step receives it and uses it correctly.

03

Check before accepting

Separate producing work from accepting it. Ask what the check actually established, who may change the result and which uncertainties still need attention.

How the work connects

A task has an owner, a source and a next step.

The operating layer joins the tools around the work: context at the start, checks at configured action boundaries, proposed corrections for review and records that allow the work to resume.

  1. Load the context

    Task, source records, permitted scope and relevant prior decisions.

  2. Coordinate the work

    Named ownership, bounded tasks, handoffs and progress checkpoints.

  3. Apply the checks

    Configured rules return allow, hold for review or deny, with their reasons.

  4. Review the correction

    Keep a proposed change separate from the accepted record until authorised.

  5. Keep the record

    Retain versions, sources and review outcomes for the next step.

Architecture overview of the development system. Coverage depends on the tool and its integration; the scope of the controls is explained below.

Persistent working context

Retrieval hooks bring relevant stored context into a session. Startup records and handoffs carry outstanding work and its source references.

Knowledge and correction stores

The software toolkit stores authorities, procedures, corrections and lessons. Document tools select knowledge for a task; retrieval and correct use still need checking.

Steerable agent workflows

Task owners can change direction at checkpoints while preserving the work already done and the instructions that changed it.

Source and document assurance

Tools check citation records, quotation text, exhibit links, file hashes and document versions. A matching source does not by itself prove a legal argument.

Action controls

Matched mandatory rules can allow an action, hold it for investigation or deny it. Rules, caller integration and permitted overrides determine what the control covers.

Release and recovery

Release checks connect a reviewed change to a published version. Saved checkpoints let work continue after a session ends.

What the controls do, and what still needs assurance

The inspected gate permits actions that match no registered trigger and supports explicit overrides. Its logging is best effort. Stored records, a running check and a correctly enforced boundary are different things. Portable authority envelopes, complete enforcement coverage and externally verified outcome receipts remain development and assurance work.

It began with Eden Legal AI

Built around work that had to be checked.

Michael Darius Eastwood began with his own legal proceedings: connected documents, changing chronologies, disputed facts, authorities and successive drafts. He built Eden Legal AI to organise that work and developed the coordination and checking infrastructure around it. Eden Control brings that infrastructure together; Eden Research uses it to manage research and publication.

Litigation made the need concrete

A source must remain attached to the statement it supports. An allegation must stay distinguishable from an agreed fact. A proposed edit must not silently become the accepted record.

Software made it reusable

Context retrieval, task ownership, checks, correction records and version control can support work beyond a single case.

Research asks what works

The research programme tests defined correction and acceptance procedures. Practical use motivates the questions; it does not establish their answers.

Read the verification method →
Current development

Working infrastructure. A private beta. Defined research questions.

The operating system and the hosted console are different parts of the work. This is their status as reviewed on 30 October 2026.

In use

Founder’s workflows

Supervised legal preparation, software development and research publication using task records, gates, handoffs and release checks.

Implemented

Reusable components

Context retrieval, knowledge stores, chronology change proposals, source checks and version records. Integration varies by component.

Private beta

Hosted console

The web workspace has restricted access. A deployed sign-in page is not evidence that every underlying tool is available through it.

Under evaluation

Assurance and transfer

External security review, portable authority records and measured reliability across tasks and providers remain to be established.

The next research question is practical: what information should a checker receive, and what should it be allowed to repair before another agent’s work is accepted? Explore the research and its evidence. No regulator approval or external certification is claimed.

Questions

What to know before using it.

What is Eden Control?

The operating layer Michael Darius Eastwood developed through Eden Legal AI. It connects task ownership, persistent context, source checks, correction records and release controls across his legal, software and research work.

Is it already being used?

Its founder uses the development system in his own work. The hosted console remains a private beta, and integration differs between components. Own use is not independent evidence of reliability or improved legal outcomes.

What happens when a check is uncertain?

For a matched mandatory rule, an unresolved check can hold the action for review. The inspected gate permits unmatched actions and supports explicit overrides, so coverage depends on the configured rules and the caller enforcing the result.

What is an authority envelope?

A proposed portable record of who authorised an action, its purpose and its limits. This is part of the development programme; universal envelope enforcement and externally verifiable outcome receipts are not established product capabilities.

Can I sign in?

Private beta. Public sign-in is not yet open. Existing beta users can sign in to the console.

Do the examples use real case material?

No. Public examples are synthetic and explain the workflow. The founder’s case material remains private.

A working prototype

Explore the system behind the work.

Private beta. Public sign-in is not yet open.