# Self Context Standard

> A portable `self/` folder standard for agent runtime context, designed around progressive disclosure.

Self defines a small local folder structure that lets agents discover runtime context without loading everything at once. The proposal site is a static HTML/CSS/JavaScript page that works from disk.

## Links

- Proposal: https://selfmd.pages.dev/
- Setup wizard: https://selfmd.pages.dev/setup/
- Source repository: https://github.com/thealialexander/self
- Starter example: ./examples/self/
- Manifest: ./examples/self/manifest.json
- Validator: ./scripts/validate-self.js
- License: ./LICENSE

## Notes for agents

- Start with `examples/self/SELF.md`.
- Use `examples/self/manifest.json` to discover slots.
- Treat `examples/self/model.md` as model identity facts only. Put the access app, CLI, desktop client, or service surface in `examples/self/harness.md`.
- Use `examples/self/harness.md` for the actual access interface, exposed surfaces, APIs, tool or script routes, permissions, and app/runtime limits.
- Use `examples/self/orch.md` for workflow coordination: routing, context loading, tool mediation, model or subagent selection, private context, adaptation notes, fallbacks, and repeated high-level harness routes.
- Treat `examples/self/user.md` as private, consent-gated personal context for user-stated biography, professional context, preferences, beliefs, habits, routines, decision preferences, workflows, and communication defaults.
- Treat `examples/self/metadata.json` as a minimal Self system stamp for troubleshooting, debugging, or diagnostics. Do not put routing rules, model details, or private user facts there.
- Keep private slots such as `examples/self/user.md` and `examples/self/chrono/` out of model context unless the user asks for them.
- If files under `examples/` change, keep the embedded `starterFiles` object in `app.js` aligned.