Skip to content

Draft: build microkernel-inspired core contracts #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
jsoneaday wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Draft: build microkernel-inspired core contracts #52

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0461641
docs
jsoneaday Sep 27, 2026
908d2eb
Define core redesign protocol contracts
jsoneaday Sep 27, 2026
dc0a146
Rename process supervision contract folder
jsoneaday Sep 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/Design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,34 @@ Derrick does not provide many tools to agents. Instead Derrick provides a small
## Structure
This application is Protocol first. All major features must have a Protocol and internally use GoF Design Patterns. No exceptions. The Protocols can be found in the Structure spm.

## Core redesign vocabulary

The core redesign uses these terms consistently:

- **Module** — functionality running inside an existing process.
- **Service** — a standalone process with its own lifecycle and IPC boundary.
- **Actor** — anything attempting a capability, including an operator, UI, agent, plugin guest, module, or service.
- **SideEffect** — a host-mediated operation with an external consequence, such as network access, UI presentation, container execution, persistence mutation, or message delivery.
- **Command** — a typed request asking an endpoint to perform work.
- **Event** — a typed notification that something happened; it does not expect a response.
- **Model message** — model conversation data such as system, user, assistant, and tool messages.
- **Service message** — internal module/service communication.
- **Plugin SideEffect message** — a guest-to-host request such as `http.request` or `ui.present`.
- Concrete in-process implementations end in `Module`; standalone process implementations end in `Service`.
- Behavioral protocols use suffixes such as `Serving`, `Checking`, `Evaluating`, `Applying`, `Executing`, and `Storing`.

The core boundary is:

1. Validate the message contract.
2. Identify the Actor.
3. Check the Actor's capabilities.
4. Evaluate Guardrail Policy.
5. Apply the decision.
6. Execute the approved SideEffect.
7. Return a typed result and audit event.

The kernel authority owns lifecycle, capabilities, secrets, SideEffects, and Guardrail enforcement. Modules provide replaceable in-process functionality. Services provide standalone process boundaries. Plugins remain user-space programs and never authorize their own SideEffects.

## Guardrail
Guardrail is Derrick's control plane in Structure (`Sources/Guardrail`).

Expand Down
Loading
Loading