Menu

Individual skill

ApertureOscillation

3-pass scope oscillation that holds a question constant while shifting zoom — narrow/tactical, wide/strategic, then synthesis — to surface design tensions, scope recommendations, and coherence assessments invisible at any single zoom level. USE WHEN aperture oscillation, oscillate scope, zoom in and out, tactical vs strategic, scope framing, design tension, system coherence check, local vs global design, wrong scope, scope negotiation. NOT FOR lens rotation across angles (use IterativeDepth).

LifeOS/install/skills/ApertureOscillation/SKILL.md

Read pinned source

Source commit b7efec97d8c3885feee285bee468c35602fb0606

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
19,758
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# ApertureOscillation

Holds one question constant and answers it at two zoom levels: narrow (what the component wants to be on its own) and wide (what the system needs it to be). A third pass names where the two answers disagree, and that gap is the output. The point is to catch a component that works on its own but fights the system before the build commits to it. IterativeDepth varies the analytical lens instead of the scope; when both apply, run IterativeDepth first (understand the problem), then ApertureOscillation (understand where the solution fits).

## Ideal State

- The principal gets a coherence verdict that changes or confirms a design decision before the build commits to it: a component that works alone but fights the system is caught at scoping, not after it ships.
- Scope questions land here and angle questions land in IterativeDepth, so the two skills never run the same analysis twice.

## Intent Routing

| Intent | Trigger | File |
|--------|---------|------|
| **Oscillate** | "aperture oscillation", "oscillate scope", "zoom in/out", "tactical vs strategic"; an Algorithm run selects the ApertureOscillation capability while scoping | `Intents/Oscillate.md` |