Engineering resilient software systems.
Micrantha is an engineering studio and software ecosystem focused on secure, observable platforms and disciplined AI-assisted development. The work explores how software can remain understandable, operable, composable, and secure as systems evolve over time.
Core areas include platform engineering, mobile systems, infrastructure automation, developer tooling, and governed agentic development, with an emphasis on data sovereignty and user-controlled systems.
🌐 micrantha.com · Collaborate · Projects · Integration map · Engineering standards · Contributing
Micrantha is actively looking for people and organizations that can help turn the ecosystem into durable, useful, independently sustainable software.
- Project contributors — engineering, security review, testing, documentation, design, accessibility, packaging, integrations, and field testing across the public projects.
- A strategic partner — an organization or individual interested in product direction, open-source sustainability, distribution, applied research, commercialization, or bringing the technology into real operating environments.
- A co-founder or long-term operating partner — someone interested in helping shape Micrantha beyond individual repositories, with complementary product, business, research, community, or engineering strengths.
- Hardware and infrastructure resources — GPU-capable systems, accelerators, storage, networking equipment, hosted compute/CI capacity, or other resources that can expand local AI, conformance, build, and systems-testing capability.
- Project adoption and practical feedback — teams willing to try individual tools, challenge assumptions, contribute real-world requirements, or help validate where the projects are and are not useful.
Current Anthesis trial need: Anthesis is specifically looking for existing agentic systems—coding agents, supervisor/specialist systems, MCP/tool workflows, automation platforms, and similar runtimes—for bounded trial runs around one consequential action. The goal is to gather integration, bypass-resistance, policy-model, evidence, approval-UX, and operational feedback, including negative results. See the Anthesis collaboration section.
Support can take the form of time, expertise, equipment, infrastructure, sponsorship, introductions, or direct project work. Collaboration does not bypass project governance, security review, or repository trust boundaries.
For public project work, start with the relevant repository and the organization contributing guide.
Micrantha treats software as a living ecosystem: systems evolve through design, implementation, observation, review, and refinement rather than a one-time construction effort.
flowchart LR
P[Plan] --> W[Work]
W --> R[Review]
R --> C[Compound]
C --> P
A few principles recur across the projects:
- Composable by default. Command-line tools should work cleanly through process boundaries, structured stdin/stdout, meaningful exit semantics, and documented man pages.
- Explicit authority. Identity, policy, evidence, execution, provenance, and observation are different concepts; one must not silently mint another.
- Reproducible where practical. Environments, inputs, plans, artifacts, and important decisions should be attributable and replayable.
- Local-first where practical. Local execution and user-controlled infrastructure are preferred when they materially improve privacy, operability, or resilience.
- Evidence over assertion. Logs, signatures, receipts, model output, test results, and observations are evidence inputs, not automatic authorization or product truth.
- Small durable controls. Repeated findings should become the weakest reliable control that prevents recurrence: tests, schemas, invariants, safer defaults, CI, policy, or bounded guidance.
- Trust domains are explicit. Public/private repositories, mirrors, agent workspaces, recovery stores, and canonical endpoints are modeled as deliberate topology rather than inferred from provider names.
Shared standards, architecture guidance, and the public responsibility map live in hackelia-micrantha/.github. A separate internal meta repository maintains the machine-readable ecosystem registry and aggregate status model.
The ecosystem has several independently useful families, with specific, declared links rather than one required stack. This condensed view highlights registered relationships in the governed-engineering group; arrows do not establish released or operational integrations. Explore the full integration map for mobile/edge, infrastructure, standalone projects, component responsibilities, and drill-down links.
flowchart LR
Cal["Calathea<br/>prioritization"] -->|"integrates with"| Dub["Dubnium<br/>execution"]
Mod["Modolia<br/>model selection"] -->|"integrates with"| Dub
Mod -->|"integrates with"| Anth["Anthesis<br/>governance"]
Inv["Invokrum<br/>context identity"] -->|"integrates with"| Anth
Test["Testule<br/>verification"] -->|"integrates with"| Dub
Test -->|"integrates with"| Anth
Sand["Sandcastle<br/>checkpoints"] -->|"integrates with"| Dub
Sand -->|"integrates with"| Anth
Lab["Governance Lab"] -->|"tests"| Anth
- Dubnium — personal, self-hosted engineering environment and reference use case for local AI and bounded automation. Public contracts and conformance material are incubating; a generally available workstation/runtime distribution is not yet released.
- Anthesis — portable, self-hostable governance for data sovereignty in agentic AI: deterministic policy decisions, capabilities, approvals, evidence, and provenance for consequential effects. Enforcement depends on the integrating tool or runtime controlling bypass paths; Anthesis alone does not guarantee data residency.
- Invokrum — deterministic prompt/context composition, manifests, locks, and exact context identity.
- Modolia — deterministic model-surface eligibility and routing decisions; runtime provider execution remains separate.
- Keylix — sender-constrained OAuth/DPoP and proof-of-possession primitives.
- Sandcastle — persistent checkpoint identity and mutable-workspace lineage for disposable execution environments.
- Testule — portable testability contracts, native-tool adapters, verification requirements, and normalized testing evidence.
Start with the bounded Try Anthesis walkthrough. Testule currently publishes an incubating specification; a public binary release is still pending.
Context identity, sender proof, verification results, and historical memory each provide bounded evidence. None independently grants execution or promotion authority.
- Repora /
repoctl— explicit repository topology, observation, exact plans, stale-safe reconciliation, managed artifacts, posture collection, and execution evidence. - Calathea — deterministic portfolio/workflow orientation and prioritization, with reusable public contracts separated from private portfolio data and dogfood composition.
Micrantha CLI tools follow the shared CLI interoperability standard: machine-readable interfaces should remain usable through ordinary Unix composition as well as higher-level orchestration.
- Dubnium — personal workstation/runtime composition and bounded execution integration, with public conceptual documentation and experimental contracts.
- Hyperion — reproducible provisioned infrastructure, K3s, and GitOps workload convergence.
These scopes complement each other: Dubnium owns the workstation/runtime environment; Hyperion owns provisioned service infrastructure.
- Amaryllis — React Native foundation for on-device multimodal inference and governed AI-enabled UI.
- Achillea — platform/SDK for guided outdoor experiences, with Asterwild as its first product consumer.
- Bluebell — Kotlin Multiplatform SDK/application foundation.
- Digitalis — mobile attestation and backend-authoritative secure-configuration experiments.
- Envuscator — build-time mobile configuration obfuscation and delivery tooling.
- Myosotis — governed field-operated AI tool protocols and SDK architecture.
- Morifolium — versioned mobile platform-engineering golden path and reference distribution.
These are parallel and composable capabilities rather than one mandatory mobile stack.
- Phyllotaxis — shared, themeable design-system/UI substrate for Micrantha project sites. Current contract work starts with Venation layout/primitives; related concerns include Chroma themes/tokens, Lamina surfaces/cards, and Cambium migration/generation tooling. The implementation repository remains private; the linked community repository owns the reviewed public design contracts and documentation.
- Organization standards and prompts — shared engineering, security, testing, release, documentation, review, and Compound-engineering conventions in
.github.
A shared substrate defines reusable contracts; consuming projects retain their own content, product behavior, information architecture, deployment, and brand decisions.
Laboratories challenge product and architecture contracts. Their evidence does not independently establish production readiness or change a product contract.
- Anthesis Governance Lab — executable public scenarios and adversarial fixtures for deterministic governance evaluation. Evaluating declared effects does not prove enforcement in an external runtime.
- MUSICPKG — experimental owner-bound digital music format aimed at durable offline ownership and purchaser-controlled recovery. The public v0.2 Working Draft includes specifications, test vectors, and a bounded Rust reference conformance harness; complete package verification and end-to-end playback remain future work.
- Entanglement of Ages — the multi-book creative project, presented through its separately reviewed public marketing surface.
The shared standards define expectations according to project maturity, risk, and supported surfaces. They are engineering requirements, not a blanket certification of every project.
- Testing — a risk-shaped test pyramid, validation at the lowest trustworthy layer, and explicit gaps. Testule supplies portable contracts and normalized evidence where adopted; native tools execute the tests.
- CI/CD — exact-revision evidence, least-privilege workflows, explicit runner trust, and bounded concurrency. Workflow review targets redundant computation while preserving independent evidence.
- Releases — attributable artifacts, integrity verification, supported installation paths, compatibility, and rollback.
- Security and tool-result trust — explicit trust boundaries and evidence that cannot silently become permission.
- CLI interoperability — composable process interfaces, machine output, meaningful exit semantics, and man pages.
- Documentation — evidence-backed public claims, clear maturity, and reviewed publication boundaries.
- Community UI — Phyllotaxis-aligned, content-first Utility interfaces with modern accessibility; Editorial styling where the publishing task warrants it.
AI-assisted SDLC uses bounded work, explicit handoffs, verification, and risk-appropriate human review. Operational skills remain project-local by default; shared skills and engineering prompts are reusable guidance. Model selection is risk-adaptive: frontier models are an escalation option, not a universal requirement.
Provider and visibility are not authority models.
A logical repository may have several endpoints. Each endpoint needs an explicit role and trust domain, with directed mirror, projection, promotion, import, or archive relationships.
A common private/public pattern is a projection, not informal bidirectional synchronization:
flowchart LR
P[Private canonical] -->|reviewed projection| C[Public/community]
P -->|build + attest| R[Release artifact]
C -. docs / examples .-> R
canonical, private, public, agent, mirror, and recovery describe topology or policy context. None grants read, write, publish, merge, or promotion authority by itself.
See repository topology and trust-domain patterns.
- Micrantha website — public project and engineering material
- Organization defaults — governance, engineering standards, prompts, templates, and shared automation
- Repository responsibility catalogue — public organization-level responsibility map