Describe the environment
Use declared platform and project inputs so development environments can be reproduced, inspected, and changed deliberately.
A Micrantha project
Reproducible engineering. Bounded automation.
Dubnium is an engineering environment built around a practical question: how can a workstation, local AI runtime, developer tools, and automation fit together while staying rebuildable, observable, and governed?
It brings Nix-based system configuration and operator tooling together with public contracts for capabilities and interoperability. Models may propose work; explicit policy and bounded execution remain in control.
Incubating
Canary implementation
Experimental contracts
Design approach
Keep the important boundaries visible.
Reproducibility is useful when systems can be rebuilt and reviewed. Governance is useful when an automation request does not silently become authority. Dubnium is designed to make those distinctions explicit.
Separate intent from effect
AI can help interpret and propose work. Identity, authorization, policy, and execution still need explicit system boundaries.
Test the public promises
Versioned contracts, synthetic adversarial fixtures, and implementation-neutral conformance checks make integration assumptions testable.
Current state
Built in slices. Still being proven.
The project combines a personal canary implementation with a public community surface for contracts, validation, documentation, and safe reference assets.
Operator and system tooling
Public materials describe the NixOS platform and the dubctl, modectl, and configctl operator surfaces.
Capability contract slice
An experimental gateway contract has schemas, canonicalization and error semantics, synthetic fixtures, conformance checks, and a no-effect reference.
Browse public specificationsVerifiable public artifacts
Release tooling is designed to produce deterministic bundles and let consumers verify their contents and provenance independently.
Explore conformance assetsOne public source of truth
The community repository owns the public website, condensed Technical Overview, contracts, and bounded public roadmap.
Visit dubnium-community
Incubating; no stable consumer baseline yet.
Public APIs and contract slices are experimental or alpha. No protected contract-v* release has yet been accepted as a consumer baseline.
Goals and outcomes
Prove the contracts with real consumers.
The roadmap prioritizes dependable public interfaces and useful adoption evidence before broader promises about deployment forms or compatibility.
Now
Complete the first release and publication gates.
- Close correctness questions in the capability contract.
- Verify protected release and consumer checks.
- Keep generated public documentation reviewed and bounded.
Next
Improve integration and expand only where reuse is clear.
- Test contracts against independent and downstream implementations.
- Develop event and resource-budget interoperability contracts.
- Refine compatibility guidance from adopter feedback.
Find your entry point
Bring a build, a question, or a constraint.
Dubnium benefits from people who want to run the public slice, challenge its assumptions, or help work out what a sustainable ecosystem could look like.
Developers
Review schemas and compatibility rules, run conformance checks, improve validators, or build an independent implementation against the public contracts.
Contribution guideHobbyists and workstation builders
Explore reproducible Nix environments, local-first AI architecture, operator tooling, and the no-effect reference assets. The public repository is a safe slice, not a packaged production workstation.
Start with the Technical OverviewDesign partners and adopters
Bring constraints from local or private AI, self-hosted builds, secure developer environments, or governed automation. Use them to test whether the contracts match real work.
Design partner guideStrategic and investment conversations
Discuss sustainability, infrastructure, distribution, integrations, and independent implementations. The project is incubating, and these conversations can help test its direction.
Micrantha collaboration overviewA deliberately condensed public manual
Understand the promises. Keep deployment details private.
The Technical Overview is generated from reviewed community sources. It explains project concepts, public contracts, and observable behavior while omitting private topology, prompts, production policy, privileged procedures, and operational evidence.