SET IT UP
Four steps to an agent on a leash.
A few minutes, most of them spent deciding what the agent may touch.
- 1Create a bundleOne folder of memory for one subject. Start free, go Plus when you want tables and files.Platform architecturebundle · plus · fra.korpus.cloud
- 2Create an agent, set its leashName it and give it the paths and rights it needs. Nothing else. You are the person it answers to.agent/archivistworks for you
- adr/*C R U
- diagrams/*C R U
- sources/*R
- security/*none
- 3Connect Claude twiceOnce as admin, with you in the loop. Once as the agent, for the work that runs without you.
# you, to set things up $ claude mcp add --transport http \ korpus-admin https://mcp.fra.korpus.cloud/mcp/admin # the agent, for the daily work $ claude mcp add --transport http \ korpus-archivist https://mcp.fra.korpus.cloud/mcp/archivist
- 4Ask for the jobTalk to the admin connection. It sets up the agent’s rules; your AI app runs the schedule.you → korpus-admin
Schedule a routine for every morning at 7. Compare the CDK files in
sources/withdiagrams/overview, fix what drifted, and draft an ADR when a decision changed. Run it askorpus-archivist, not as admin.routine drift-check · daily 07:00 · as korpus-archivist
That's it. Every morning your agent does the work, inside its leash, and each change reads @you via archivist.
Give your agents a memory your team can read.
Korpus is coming soon. For early access, a demo or running it in your own AWS account, write to us.
Get in touch