What the labels mean
| Label | What it establishes | What it does not establish |
|---|---|---|
| Code present | A concrete implementation, command path, or adapter was inspected. | A successful installation or exercised integration. |
| Catalog configured | Catalog, Compose, or adapter wiring describes the component. | A running service, populated index, usable credentials, or current client access. |
| Experimental | A support concept or partial mechanism exists with material qualification limits. | Reliable sensing, clinical benefit, or measured effectiveness. |
| Unresolved | Inspected declarations disagree or a connection contract remains uncertain. | A supported recipe or a silently chosen interpretation. |
These labels are evidence vocabulary for this website. They are not a real-time status monitor. A page can have Code present and still document unresolved subpaths.
The source snapshot behind the site
The source review references commit 93050d135ffc2592000c1d0edef82b2912935525 of the public Dopemux repository. Optional Source evidence panels link to that pinned revision; primary setup and documentation links may point to the current main branch.
Source research was performed on 29 October 2026. Runtime code and configuration were preferred over stale descriptions and generated summaries. This website’s research did not start application services, run provider calls, or execute application tests.
Material limits worth knowing first
- Saved context: recent-file hints and notes are implemented; exact editor recovery and timed autosave are not implemented in the inspected path.
- Cockpit: the separate terminal UI is a static demo. Main startup is a different flow.
- Attention support: live input collection into the inspected monitor is not established. No clinical or productivity claim is supported.
- Task Orchestrator: the MCP integration and Python coordination API are distinct surfaces with different ports.
- Serena: advertised HTTP and active SSE transport descriptions conflict.
- PAL: HTTP is health/lifecycle only; reasoning tools have a separate stdio declaration.
- Evidence facade: current source exposes six local tools, narrower than older catalog descriptions.
- PM sync: a bridge acknowledgment does not perform autonomous bidirectional synchronization.
- Shared state: local worktree separation does not establish external service or event-stream isolation.
What remains unqualified
Installation success, all-service health, client handshakes, provider access, actual model identity, current prices or quota, retention enforcement, backup/recovery, cross-project isolation, and end-to-end workflow behavior remain unverified by this website’s research.
No uptime, SLA, performance benchmark, security certification, complete compatibility list, or roadmap delivery date is claimed. A configured health endpoint is not a health result; a source-level test is not an executed test result.
Inspect and contribute through the repository
Use the repository, current documentation, and issue tracker to investigate a specific question. Include the source revision, selected component, expected behavior, observed result, and relevant local configuration without sharing secrets.
Start with a bounded evaluation rather than assuming the entire configured stack is ready. The detailed feature and component pages make those evaluation boundaries explicit.
Source evidence
Inspected source at the pinned reference revision. Source presence does not establish runtime health.