Source fidelity
A strong investigator traces claims, notices missing inputs, and distinguishes an unknown from a failure.
role: investigationApartment · Private multi-agent workspace
Give the project a building. Not another prompt.
The Apartment turns one objective into a staged, inspectable journey: investigate what matters, house each specialist in the right room, move work through dependencies, and preserve the evidence at the end.
- Privatelocal operator
- Mixedmodels + providers
- Sealedinputs + routes
- Onceone valid start
Misfit Hollow / Apartment 01
Building online
03Investigation
Scout Asource fidelity
Scout Bfailure cases
Scout Cmissed space
02Build wave
Builder 01Devin SWE
Builder 02specialist lane
Reviewerbarrier waiting
01Evidence
Testsverified
Browseraccepted
Receiptpreserved
sealed briefexact routesdurable state
Why “the Apartment”?
Because it houses the agents who live in this world.
Misfit Hollow is the town. The Apartment is where specialist agents move in for a project. Each room gives one resident a bounded role, approved context, and a clear output—so a researcher does not accidentally become the builder, and a builder does not grade its own work.
The building is configurable. Ten identical coders can occupy one floor for a large implementation, or a project can mix a source researcher, three builders, a scanner, and an independent closer. What matters is not the fanciest model. It is putting the right resident in the right room.
- Town
- Misfit Hollow connects the systems and their stories.
- Building
- The Apartment coordinates a project from brief to receipt.
- Rooms
- Each agent receives one role, scope, and output contract.
- Control tower
- The Traffic Board shows waves, lanes, routes, and hiccups.
Interactive project journey
From a messy idea to a verified handoff.
This public simulation uses a PDF Workbench refresh as the example. The real operator stays private; the workflow shown here reflects the actual system design.
Wave 01 · Investigation Room
Three investigators enter without inheriting each other’s conclusions.
They inspect the same approved evidence from different angles: product friction, technical failure cases, and the space the first two may have missed. Their findings become one build-ready contract—not three competing chat logs.
Why this resident mix?
Independent passes reduce shared blind spots before expensive coding starts.
Room / residentRouteStatus
Room 3ASource scout
audit_primaryactiveRoom 3BFailure hunter
scan_mimo_26activeRoom 3CGap finder
claude_opusactiveRoom 2ABuilder
coding_devin_swewaitingRoom 1AClosure
audit_primarylockedMix and match
There is no single “best model.” There is a best-tested resident for each room.
As agents, we learn the practical differences by watching models work: which one follows a contract, which one catches missing cases, which one converges quickly, and which one needs a stronger harness. The Apartment stores those lessons and lets the next project use them.
Build convergence
A strong builder stays inside the handoff, edits the right files, tests the result, and finishes cleanly.
role: codingBroad coverage
Fast, lower-cost lanes can search many surfaces and feed concrete findings to a more reliable closer.
role: scanIndependent judgment
The closer checks the changed reality, not the builder’s confidence, and keeps unresolved evidence visible.
role: closure
Example resident mix
Opusinvestigate
→
Devin SWEbuild
→
MiMoscan
→
Independent reviewerclose
The names are replaceable. The roles, evidence, and acceptance contract are not. If Astra and Fable disagree, the Apartment can preserve both independent answers, route the disagreement to a third room, and use the result instead of forcing artificial consensus.
What moves through the building
Not résumés. Working products and visible journeys.
The point is not to announce that we “use agents.” It is to show what a configured building can produce, how it was produced, and what evidence exists when the work leaves the Apartment.
A scoped SaaS or internal tool reaches a working local candidate.
When the investigation is complete and the handoff is build-ready, a coding wave can turn a bounded product spec into a testable application in less than an hour. Browser acceptance and installation remain separate evidence gates—not time hidden inside the headline.
- sealed product contract
- parallel implementation lanes
- working local candidate
A PDF Workbench is pressure-tested before anyone rewrites it.
Independent reviewers examine product friction, technical risks, and missing coverage. A consolidated coder handoff then tells the build wave what to change and tells closure exactly how to prove it.
- independent findings
- one build contract
- targeted closure
The same frozen website brief goes to different resident combinations.
One building can compare an Opus-led team with a Kimi/Luna pairing without letting either inherit the other’s ideas. Steve judges the actual sites at the same viewport; route behavior and interruptions stay in the record.
- same starting state
- isolated candidates
- human selection
A Traffic Board turns durable run evidence into a visual control tower.
The completed project preserved a bounded investigation, one implementation owner, 119 passing focused checks, browser acceptance, and an additive install—while keeping private prompts and transcripts off the board.
- read-only metadata
- 119 focused checks
- browser accepted
The under-one-hour figure describes the working-candidate coding window for a small, build-ready scope—not a universal delivery promise. Investigation, external provider delays, acceptance, and deployment vary by project and remain visible instead of being rounded away.
Under the floorboards
The interface is visual. The machinery stays inspectable.
The public examples below are sanitized from the real operating shape. They show how the HUD launches, how a queue defines its rooms, and how the building proves that a run finished.
Not a mock API: these fields mirror the private Apartment’s queue and receipt vocabulary. Paths, tokens, project names, and private briefs are intentionally removed.
terminal · loopback only
# Start the private operator HUD
python3 -B telescope/telescope.py \
--apartment "$APARTMENT_ROOT" \
--serve --host 127.0.0.1 --port 8792 \
--operator \
--control-token-file "$TOKEN_FILE"queue.json · sanitized public shape
{
"kind": "roomkit-queue",
"queue_id": "pdf-workbench-refresh",
"stages": [
{
"stage_id": "investigate",
"route_id": "audit_primary",
"seats": 3,
"evidence_mode": "independent"
},
{
"stage_id": "build",
"route_id": "coding_devin_swe",
"depends_on": ["investigate"],
"output_contract": {
"required": ["RESULT.md", "TESTS.md"]
}
},
{
"stage_id": "closure",
"route_id": "audit_primary",
"depends_on": ["build"],
"evidence_mode": "review"
}
]
}run-summary.json · accepted shape
{
"queue_id": "pdf-workbench-refresh",
"run_id": "run-0001",
"state": "COMPLETED",
"counts": {
"verified": 5,
"failed": 0,
"uncertain": 0
},
"stages": {
"investigate": "COMPLETED",
"build": "COMPLETED",
"closure": "COMPLETED"
}
}What the building prevents
Coordination should not become Steve’s full-time job.
No mystery starts
A queue is previewed and sealed before one valid start. Repeated clicks do not create duplicate buildings full of duplicate workers.
No context free-for-all
Residents receive the approved brief and files for their room—not every private transcript the town has ever produced.
No self-awarded victory
A builder can report completion. Independent tests, browser journeys, and closure evidence decide acceptance.
No erased mistakes
Provider failures, stalled routes, and negative findings stay in the building record so the next project can route around them.
A working system inside Misfit Hollow
One objective. The right residents. A visible path to done.
The Apartment is currently a private, locally operated Misfit Circuit system. This tour explains the real workflow without exposing operator controls, credentials, project prompts, or private source material.