Reusable tools for AI work that survives the chat.
I'm Brandon Ducar. I'm building toward a shared operating system for digital and physical businesses. These public projects tackle practical pieces: keeping useful context, bounding agent work, and making results inspectable.
Explore the project directory | Ecosystem map | DreamNet
Independent products. Optional connections. Private operations. Start with one project's documented setup; you do not need access to DreamNet's private monorepo. Each product keeps its own requirements, license, data boundaries and release lifecycle. Integrations use explicit interfaces, not shared credentials.
Darkhalo's actual public interface. Its built-in sample is explicitly synthetic; the screenshot is not a receipt for real-world work.
| I need to... | Try | What it provides |
|---|---|---|
| Preserve and resume bounded agent work | DreamLoops | Versioned operating loops, capability Capsules, execution records |
| Inspect a repo before running it | Cerberus | Offline static inspection and digest-bound findings, not a safety guarantee |
| Review agent-run context | Darkhalo | Local-first inspection and review capsules, no automatic authority |
| Prepare source-linked knowledge | Memory Weaver | Portable context with provenance |
| Hand work to someone else | Warper Keeper | Source-first Trapper context bundles |
| Package evidence for a build | Proof Drop | Local evidence-file hashing and exported receipts |
The independently operated ZOL project merged a DreamLoops persistent-agent integration and a Bonfire memory adapter. The pull requests show the contributions. They are not a claim about ZOL's current runtime, an endorsement, or DreamNet ownership.
- Public Core: shared agent contracts.
- ToolGym: agent workouts; practice is not independent qualification.
- LaunchCast: repository-to-storyboard and local video rendering; uploads are not implemented.
- Dreamnetiopi: merchant-operations rehearsal, not production telemetry.
- All 32 public repositories: apps, libraries, research, prototypes, and attributed forks.
| What brings you here? | Next step |
|---|---|
| I need help or found a bug | Open a product help request |
| I want to connect two tools | Propose an integration |
| A link, screenshot or description is wrong | Report a directory correction |
| I have a broader question | Join the public-core discussion |
| I want to contribute code or docs | Read the contribution guide |
Not sure which repository owns a problem? Start here with the product name and a small, non-sensitive example. We can identify the right repository before you invest in a patch. These are public conversations, not private support tickets.
Support and privacy boundaries
DreamNet is early. Each repo has its own implementation boundaries and license. A receipt is not proof that every claim inside it is true, and a capability is not permission to act. Private credentials, customer data, and operating context do not belong in public examples.