Spectro — Multi-Model Cognitive Spectrograph
Split the beam. Read the spectrum. The convergences are the coastline. The divergences are the interesting water.
What
Spectro sends your prompt to N different AI models in parallel, then analyzes what they agree on (convergences) and where they diverge (divergences). The output isn't any single model's answer — it's the pattern across all of them.
This is not model routing (picking the best model). This is not ensemble voting (averaging answers). This is spectral analysis of model cognition — treating the differences between models as signal, not noise.
Why
Every paradigm essay in the SuperInstance corpus points at the same truth: different models are different perspectives, not different quality. The convergences between independent models reveal high-confidence territory. The divergences reveal the interesting edges — the places where the question is genuinely uncertain, or where a model sees something the others miss.
- A question where all 5 models agree → high confidence, low exploration value
- A question where models disagree → genuinely uncertain, needs human judgment
- A question where one model is unique → either a blind spot or a breakthrough
Spectro makes this visible.
Install
pip install spectro-spectrograph
Quick Start
# Set your DeepInfra API key (or any OpenAI-compatible provider)
export DEEPINFRA_API_KEY=...
# Run a spectral analysis across 5 models
spectro "What is the most important quality in a senior engineer?"
How It Works
Your Prompt
│
▼
┌─────────────────────────────────┐
│ Spectro Engine (parallel) │
│ │
│ Model A ──→ Response A │
│ Model B ──→ Response B │
│ Model C ──→ Response C │
│ Model D ──→ Response D │
│ Model E ──→ Response E │
│ │
└─────────────┬───────────────────┘
│
▼
┌─────────────────────────────────┐
│ Analysis Layer │
│ │
│ 1. Extract key concepts │
│ 2. Find convergences (shared) │
│ 3. Find divergences (unique) │
│ 4. Map the agreement space │
│ │
└─────────────┬───────────────────┘
│
▼
┌─────────────────────────────────┐
│ Spectrum Report │
│ │
│ ████ CONVERGENCE (high conf) │
│ ██░░ PARTIAL AGREEMENT │
│ ░░░░ DIVERGENCE (explore here) │
│ █░█░ UNIQUE INSIGHTS │
│ │
└─────────────────────────────────┘
CLI
# Default ensemble (5 models)
spectro "Should we use microservices?"
# Choose specific models
spectro "What causes bad code?" \
--models deepseek,seed-pro,ornith,nemotron
# Focus on a specific analysis type
spectro "Is this architecture sound?" \
--focus divergence
# Output as JSON
spectro "Best practices for API design" \
--format json
# Verbose mode (show full responses + analysis)
spectro "What is consciousness?" \
--verbose
Python API
from spectro import Spectrograph
spec = Spectrograph(api_key="...")
result = spec.analyze(
prompt="What's the biggest risk in microservices?",
models=[
"deepseek-ai/DeepSeek-V4-Flash",
"ByteDance/Seed-2.0-pro",
"deepreinforce-ai/Ornith-1.0-35B",
],
)
print(result.convergences) # concepts all models share
print(result.divergences) # where models disagree
print(result.unique_insights) # what each model saw alone
print(result.confidence) # 0.0-1.0 agreement score
The Theory
Spectro is built on the paradigm documented across 1,600+ essays in the SuperInstance/AI-Writings corpus:
- The Spectrograph: Every model output is a composite beam. Splitting it reveals composition.
- The Ensemble Is the Experiment: The intelligence is in the relationship, not the individual.
- Charts Not Maps: Each model is a different chart of the same territory.
- Two Charts Same Ocean: Convergences show the ocean floor. Divergences show the interesting water.
- Cast Thin First: Cheap models discover the territory. Expensive models synthesize.
License
MIT
Metadata
Release files for spectro-spectrograph 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spectro_spectrograph-0.1.0.tar.gz | 14.8 kB | Without provenance | Details for spectro_spectrograph-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spectro_spectrograph-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for spectro_spectrograph-0.1.0-py3-none-any.whl |
Total release size: 27.4 kB
Release files / spectro_spectrograph-0.1.0.tar.gz
| Download URL | spectro_spectrograph-0.1.0.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fef5cdfe289cdda61b64f34f2a8341c7436a54594e3562296bc26f1c70cf485
|
|
BLAKE2b-256 checksum How to use checksums |
c0c00fe95f8e74031efd5e50d6fe254b1e6cf5f88e4b86f4c975b881642eb0ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / spectro_spectrograph-0.1.0-py3-none-any.whl
| Download URL | spectro_spectrograph-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f8b25d6420b88c778fa8000fb37258efb3681f977663f46f8345bc6dbc36237
|
|
BLAKE2b-256 checksum How to use checksums |
18398200e16e3005574ba4679a9a66d8607f3b725895d615142e32928a57154f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for spectro-spectrograph 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.