mirror of
https://github.com/boshu2/agentops.git
synced 2026-09-14 15:08:13 +08:00
Boden Fuller
1e073d8363
Olympus (ol) was the power-user daemon predecessor to AgentOps, archived in strategic-direction.md. The bridge contracts (SPEC_ONLY, never enforced), MemRL policy surface, OL quarantine constraints collector, and supporting scripts/tests all referenced a now-dead integration. Purging them removes ~2400 lines of stale surface area. ## Deleted files - docs/ol-bridge-contracts.md - docs/architecture/ao-olympus-ownership-matrix.md - docs/plans/2026-02-13-ao-olympus-bridge-next-steps.md - docs/contracts/memrl-policy-integration.md - docs/contracts/memrl-policy.schema.json - docs/contracts/memrl-policy.profile.example.json - cli/cmd/ao/inject_ol_test.go - skills/vibe/scripts/ol-validate.sh + codex mirror - skills-codex/swarm/scripts/ol-ratchet.sh, ol-wave-loader.sh - tests/ol-integration/ (entire directory) ## CLI code stripped - internal/search/types.go: OLConstraint struct + InjectedKnowledge.OLConstraints field - internal/search/inject_run.go: CollectOLConstraints, WriteConstraintsSection, quarantineRelPath const, all related trim/render logic - cmd/ao/inject.go: gatherOLConstraints, collectOLConstraints wrapper, olConstraint type alias, init-time call site - Package comments in provenance/storage/types/formatter updated "olympus" → "agentops" - formatter/markdown.go: session tag "olympus" → "agentops" (+ test update) - Tests: deleted TestCollectOLConstraints + TestInject_collectOLConstraints, stripped OL subtests from TestFormatKnowledgeMarkdown and TestInject_*, renamed "olympus" literal test data to "other-repo" - rpi_phased_context.go: stripped "matches Olympus DefaultTimeout" and "Modeled on Olympus internal/git/worktree.go" comments ## Docs + skills stripped - mkdocs.yml nav: 3 entries removed (AO-Olympus Matrix, MemRL Policy, OL-AO Bridge) - docs/INDEX.md, contracts/index.md, architecture/index.md, index.md: cross-refs removed - strategic-direction.md: retirement rationale compressed to one paragraph - docs/context-packet.md, positioning/devops-for-vibe-coding.md, plans/README.md: OL-specific content removed - skills/vibe/SKILL.md + codex mirror, swarm/SKILL.md: OL script refs removed - skills/vibe/references/deep-checks.md, plan/references/planning-rules.md (+ codex), pre-mortem/references/council-fail-patterns.md (+ codex): OL rule/pattern entries removed - skills-codex hashes regenerated (plan, pre-mortem, swarm, vibe) ## Precommit hook fix - hooks/go-test-precommit.sh: prefer ~/.local/go/bin/go when present. Hooks don't inherit interactive-shell PATH, so apt-provided go-1.22 would otherwise override a user-local 1.26 install. Mirrors the zshrc pattern. ## Retained (historical / useful) - strategic-direction.md: 1-paragraph archival note - Historical release notes (docs/releases/*.md) — immutable past-release record - cli/testdata/transcripts/real-2.4mb.jsonl — captured test fixture - docs/brownian-ratchet.md ol-rg3p bead-ID refs — internal bead prefix, not Olympus ## Verification - go build ./... && go vet ./... clean - go test ./... clean except pre-existing TestGCBridgeVersion_Live panic - scripts/docs-build.sh --check (mkdocs strict) clean - scripts/check-contract-compatibility.sh passes - scripts/regen-codex-hashes.sh run — 4 skills updated
Role-Based Profiles
Purpose: Organize 12 domain skills into 3 discoverable profiles for different work contexts.
Version: 4.0.0 (Updated for skills-based approach)
How to Use Profiles
Profiles are documentation groupings, not executable configs. They organize AgentOps skills by domain so you can quickly find which skills are relevant to your work.
To use a profile:
- Find your domain in the table below
- Open the profile YAML (e.g.,
docs/profiles/roles/software-dev.yaml) to see which skills it groups together - Use those skills directly via slash commands (
/research,/plan,/implement) or by reading the SKILL.md files listed in the profile
You do not "load" or "activate" a profile — you read it to discover which skills apply to your workflow, then invoke those skills individually.
Quick Start
| You're doing... | Profile | Key Skills |
|---|---|---|
| Building apps (APIs, frontends, features) | software-dev | languages, development, code-quality |
| Operations (incidents, monitoring, deploys) | platform-ops | operations, monitoring, security |
| Writing (docs, research, patterns) | content-creation | documentation, research, meta |
The 3 Profiles
1. Software Development (software-dev)
What you do:
- Build applications (backend APIs, frontends, full-stack)
- Write code in Python, Go, Rust, TypeScript, Java
- Review code and generate tests
- Deploy with CI/CD pipelines
Skills included:
| Skill | Knowledge Areas |
|---|---|
| languages | Python, Go, Rust, Java, TypeScript, Shell (6) |
| development | Backend, frontend, fullstack, mobile, iOS, deployment, AI, prompts (8) |
| code-quality | Review, improve, test generation (3) |
| validation | Assumptions, continuous, planning, tracer bullets (4) |
| data | Engineering, science, ML, MLOps (4) |
Example workflow:
1. /research "API design for user auth"
2. Load languages skill for Python patterns
3. Load development skill for backend architecture
4. Load code-quality skill before commit
2. Platform Operations (platform-ops)
What you do:
- Respond to production incidents
- Monitor system health and performance
- Debug errors and analyze logs
- Manage deployments and infrastructure
Skills included:
| Skill | Knowledge Areas |
|---|---|
| operations | Incident response, triage, postmortems, error detection (4) |
| monitoring | Alerts/runbooks, performance engineering (2) |
| security | Penetration testing, network engineering (2) |
| validation | Assumptions, tracer bullets (4) |
| meta | Context, execution, autonomous work (6) |
Example workflow:
1. Alert fires → Load operations skill
2. Check metrics → Load monitoring skill
3. After resolution → Load meta skill for postmortem
3. Content Creation (content-creation)
What you do:
- Write documentation (technical and non-technical)
- Extract patterns from completed work
- Conduct research and analysis
- Create tutorials and examples
Skills included:
| Skill | Knowledge Areas |
|---|---|
| documentation | Create, optimize, Diátaxis audit, API docs (4) |
| research | Code, docs, history, archive, structure, specs (6) |
| meta | Context, observer, memory, retro analysis (6) |
| specialized | Accessibility, support, UX (6) |
Example workflow:
1. /research "authentication patterns in our codebase"
2. Load research skill for exploration
3. Load documentation skill for writing
4. Load meta skill for retrospective
Skills by Profile
| Skill | software-dev | platform-ops | content-creation |
|---|---|---|---|
| languages | ✅ | ||
| development | ✅ | ||
| documentation | ✅ | ||
| code-quality | ✅ | ||
| research | ✅ | ||
| validation | ✅ | ✅ | |
| operations | ✅ | ||
| monitoring | ✅ | ||
| security | ✅ | ||
| data | ✅ | ||
| meta | ✅ | ✅ | |
| specialized | ✅ |
Loading Skills
Skills load into main context with full tool access:
# Read a skill directly
Read skills/languages/SKILL.md
# Or let triggers auto-load
"I need help with Python async patterns"
# → languages skill auto-activates
Profile Files
profiles/
├── README.md # This file
├── roles/
│ ├── software-dev.yaml # Software development profile
│ ├── platform-ops.yaml # Platform operations profile
│ └── content-creation.yaml # Content creation profile
└── examples/
├── software-dev-session.md # Example dev session
├── platform-ops-session.md # Example ops session
└── content-creation-session.md # Example writing session