Where do you answer"is the agent allowed to do this?"–one place,orevery adapter?

yogisotho1 pts0 comments

GitHub - YogiSotho/warden: Rust-purist unified agent substrate — a scaffold composing the best-at containment/governance pattern per subsystem from a 64-repo teardown. Hub & spokes; warden-daemon is the single spawn chokepoint. · GitHub

/" data-turbo-transient="true" />

Skip to content

Search or jump to...

Search code, repositories, users, issues, pull requests...

-->

Search

Clear

Search syntax tips

Provide feedback

--><br>We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Cancel

Submit feedback

Saved searches

Use saved searches to filter your results more quickly

-->

Name

Query

To see all available qualifiers, see our documentation.

Cancel

Create saved search

Sign in

/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up

Appearance settings

Resetting focus

You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

{{ message }}

YogiSotho

warden

Public

Notifications<br>You must be signed in to change notification settings

Fork

Star

main

BranchesTags

Go to file

CodeOpen more actions menu

Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit

History<br>2 Commits<br>2 Commits

spokes

spokes

.gitignore

.gitignore

ARCHITECTURE.md

ARCHITECTURE.md

Cargo.lock

Cargo.lock

Cargo.toml

Cargo.toml

README.md

README.md

ROADMAP.md

ROADMAP.md

View all files

Repository files navigation

warden

A Rust-purist unified agent substrate — a SCAFFOLD (shape, not implementation).

It composes the best-at pattern per subsystem from the june/29 teardown of 64+ repos<br>(governance ← omnigent/coven, memory ← resonant-lattice, egress/ANN/gateway/sandbox ← coder org,<br>orchestration ← windmill, spend ← the hackathon "clamp-the-model" pattern). It does not rewrite<br>200 repos — it finds the one chokepoint and attaches containment once.

Hub & spokes: warden-daemon = the hub (the one spawn chokepoint); every subsystem = a spoke under spokes/.

The shape / visual map: ARCHITECTURE.md

The manifest = table of contents: Cargo.toml

Materialized now ([✓ stub]): warden-core, warden-daemon (★ the chokepoint), warden-policy, warden-egress, warden-memory — each has real traits/types + todo!() bodies + // PORT FROM: cites.

Expansion roster ([· roster]): identity, ledger, sandbox, runtime, harness, gateway, ann, orchestrator, spend, acp, cli — specified in the Cargo.toml comments + ARCHITECTURE table.

Northstar: everything Rust. Go/TS winners are translated in crate-by-crate; the port-from<br>file:line sits in each stub's module doc comment, so translation is a lookup, not a redesign.

--lib ; copy an anchor's stub pattern ; add to members">cargo build # builds the 5 anchor stubs (todo!() bodies compile)<br># to expand: cargo new spokes/warden- --lib ; copy an anchor's stub pattern ; add to members

About

Rust-purist unified agent substrate — a scaffold composing the best-at containment/governance pattern per subsystem from a 64-repo teardown. Hub & spokes; warden-daemon is the single spawn chokepoint.

Resources

Readme

Uh oh!

There was an error while loading. Please reload this page.

Activity

Stars

stars

Watchers

watching

Forks

fork

Report repository

Releases

No releases published

Packages

Uh oh!

There was an error while loading. Please reload this page.

Contributors

Uh oh!

There was an error while loading. Please reload this page.

Languages

Rust<br>100.0%

You can’t perform that action at this time.

warden cargo spokes pattern reload rust

Related Articles