We are looking for design partners, grant support, and early collaborators who already face hard problems around historical texts, commentary traditions, archival stewardship, or durable reference corpora. Support now helps finish the narrow first-client core: verification, replay, rebuildable storage, and profile-governed accepted reading for long-lived cultural materials.
Archives, stewards, or teams with real historical-text workflows who can shape the first practical profile and client path.
Open-infrastructure, cultural-heritage, or public-interest funders who care about durable and auditable knowledge systems.
Researchers, maintainers, archivists, or institutions who want to pressure-test Mycel with concrete preservation use cases.
Shared typed parsing, canonicalization, and clearer profile boundaries for long-lived texts and reference corpora.
Replay verification, accepted-head selection, negative coverage, and fixture-backed checks for preservation workflows.
Rebuildable local storage, simulator-backed workflows, and a narrower interoperable client target for cultural-text stewardship.
Mycel is still early enough that partner input can shape the right first profile and the right first client. It is also concrete enough that support funds real engineering work for cultural preservation infrastructure rather than abstract protocol exploration.
For grants, design-partner conversations, or research collaboration, contact us at ctf2090 [at] gmail [dot] com.
Mycel is built in public on Twitch. If you want to watch live coding, implementation tradeoffs, and ongoing protocol or client work as it happens, follow the stream here.