Skip to content

cmanfre4/wardlock

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Summary

This is a thought exercise, on what a good product specification might look like, and the iterative process one can take to shape it into a form that agents can then reliably act upon.

Warning

This README.md is the only human written file. The rest of the documents are generated and contain many hallucinations that are not yet ironed out. The maturity of the various sections depends on where I've last been working and there will be inconsistencies.

Goals

I want to show what a solution to delivering just-in-time credentials to agents running in isolated environments might look like, and what sort of internal machinery would be required for it to function well at scale. I think this sort of underlaying infrastructure is required to safely orchestrate agents working together on very large tasks.

This is also my nascent opinion on how to practice writing good product specification. I'd like this to come across in the progression of commits in the git history, and I hope it helps someone else out who's struggling with the same.

Usage

If I ever end up trying to actually build this I would want to open source it, so I figure just putting the docs out there is really the same thing. You're free to use any of this as you like. Just do me a courtesy; put me in the credits and show me what you've built.

About

A framework for isolating agents and providing scoped, time-limited permissions to external resources so they can work autonomously with bounded blast radius. Named for the ward — the internal mechanism of a lock that determines which key fits. Wardlock determines what level of access each agent request gets.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors