Continuous Agentic Development (CAD) requires that TELOS — the intention substrate — is loaded at session start regardless of which harness is running. Currently TELOS exists in brain/wiki/telos/ but is not wired into any harness config. A session that doesn't load TELOS has no intention context and cannot trace decisions back to goals.
Scope: telos-load/SKILL.md
A skill that documents the standard convention for loading TELOS from brain at session start, for each supported harness.
In .crush/instructions.md or equivalent project config:
## Intention context
Load TELOS: query brain MCP with wing=telos, limit=8 at session start.
Antigravity
Equivalent @brain_context directive in project-level Antigravity config.
PRINCIPAL_TELOS.md (fallback)
For sessions without brain MCP access: a pre-assembled PRINCIPAL_TELOS.md generated by concatenating all telos wing files. Cron job or on-demand. Located at ~/.local/share/telos/PRINCIPAL_TELOS.md, @-importable.
When TELOS is not loaded — detection
A session without TELOS context should self-identify: harnesses that support it can check for the telos wing in brain at session start and warn if empty.
Acceptance criteria
telos-load/SKILL.md exists with per-harness instructions
CLAUDE.md snippet documented and tested on koala (Claude Code session loads TELOS)
Crush equivalent documented
PRINCIPAL_TELOS.md assembly script or cron documented
SKILLS_INDEX.md updated
Smoke test: brain_answer "what am I optimizing toward?" returns TELOS content in a wired session
Risk
LOW — config files and markdown only.
## Context — CAD harness-agnostic methodology
Continuous Agentic Development (CAD) requires that TELOS — the intention substrate — is loaded at session start regardless of which harness is running. Currently TELOS exists in `brain/wiki/telos/` but is not wired into any harness config. A session that doesn't load TELOS has no intention context and cannot trace decisions back to goals.
## Scope: `telos-load/SKILL.md`
A skill that documents the standard convention for loading TELOS from brain at session start, for each supported harness.
### Claude Code
In the project's `CLAUDE.md`:
```markdown
## Intention context (TELOS)
> brain_context wing=telos limit=8
```
### Crush
In `.crush/instructions.md` or equivalent project config:
```markdown
## Intention context
Load TELOS: query brain MCP with wing=telos, limit=8 at session start.
```
### Antigravity
Equivalent `@brain_context` directive in project-level Antigravity config.
### PRINCIPAL_TELOS.md (fallback)
For sessions without brain MCP access: a pre-assembled `PRINCIPAL_TELOS.md` generated by concatenating all telos wing files. Cron job or on-demand. Located at `~/.local/share/telos/PRINCIPAL_TELOS.md`, @-importable.
### When TELOS is not loaded — detection
A session without TELOS context should self-identify: harnesses that support it can check for the `telos` wing in brain at session start and warn if empty.
## Acceptance criteria
- [ ] `telos-load/SKILL.md` exists with per-harness instructions
- [ ] CLAUDE.md snippet documented and tested on koala (Claude Code session loads TELOS)
- [ ] Crush equivalent documented
- [ ] PRINCIPAL_TELOS.md assembly script or cron documented
- [ ] SKILLS_INDEX.md updated
- [ ] Smoke test: `brain_answer "what am I optimizing toward?"` returns TELOS content in a wired session
## Risk
**LOW** — config files and markdown only.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context — CAD harness-agnostic methodology
Continuous Agentic Development (CAD) requires that TELOS — the intention substrate — is loaded at session start regardless of which harness is running. Currently TELOS exists in
brain/wiki/telos/but is not wired into any harness config. A session that doesn't load TELOS has no intention context and cannot trace decisions back to goals.Scope:
telos-load/SKILL.mdA skill that documents the standard convention for loading TELOS from brain at session start, for each supported harness.
Claude Code
In the project's
CLAUDE.md:Crush
In
.crush/instructions.mdor equivalent project config:Antigravity
Equivalent
@brain_contextdirective in project-level Antigravity config.PRINCIPAL_TELOS.md (fallback)
For sessions without brain MCP access: a pre-assembled
PRINCIPAL_TELOS.mdgenerated by concatenating all telos wing files. Cron job or on-demand. Located at~/.local/share/telos/PRINCIPAL_TELOS.md, @-importable.When TELOS is not loaded — detection
A session without TELOS context should self-identify: harnesses that support it can check for the
teloswing in brain at session start and warn if empty.Acceptance criteria
telos-load/SKILL.mdexists with per-harness instructionsbrain_answer "what am I optimizing toward?"returns TELOS content in a wired sessionRisk
LOW — config files and markdown only.