● named after Pando — one aspen, 47,000 stems, one root system
Pandoscope
/ˈpæn.doʊ.skoʊp/ · noun
Pandoscope: a nice decision-driven orchestrator —
self-catalyzing, -observing, -pruning & -explaining.
In plain words: the agentic factory that builds itself. Pandoscope observes its own behaviour and learns from it — and uses what it learns to bootstrap new agentic projects and orchestrate the agents working inside them.
● field note — what the -scope stands for
Four habits, one organism
- Self-catalyzing
- The factory builds the factory. Skills author skills, the template bootstraps the repos that improve the template.
- Self-observing
- Every decision leaves a trace: ADRs, decision markers in diffs, tickets reconciled to what was actually built.
- Self-pruning
- Nothing load-bearing ships unquestioned. Grilling sessions interrogate plans; a brevity rule cuts every artifact to its shortest precise form.
- Self-explaining
- Tickets are self-contained by rule: replay the issue stream in order and you rebuild the same system — no tribal knowledge required.
● field note — dogfood
It eats its own dogfood
Every rule here was produced by following the rules. The ticket that introduced grilling was grilled. The skill that demands reproducible tickets rewrote its own ticket when reality diverged from the plan. The brevity rule cut the very pages that state it.
Nothing in the system is exempt from the system — that is what self-catalyzing means in practice.
● root system — how it is set up
One root system, many stems
Like its namesake, Pandoscope is one organism with many visible stems. Everything shares the same roots:
-
skillsroot system
The canonical skill library: original disciplines (decision documenting, ADR writing) and condensed derivations of vendored skills (TDD, tickets, specs, caveman brevity), each pinned to its upstream commit. Synced into every project — projects never edit their local copies.
-
agentic-engineering-templatecambium
The growth layer. Bootstraps a new agentic project: agent guidelines, hooks, skill lockfiles, tracker conventions — everything a fresh stem needs to sprout.
-
project reposstems
Each project grows from the template and feeds observations back — as tickets, decision records, and skill improvements. The organism learns; every stem benefits.