The marketplace
What this build of MiCyte contains — the packages an instance can install and the extensions that fill its ports — alongside the open channel Fruitful Network Development hosts. To find an entity rather than read one, use Explore, or read the directory.
A channel is a session an instance publishes for the outside world, and an open one is engaged by any browser that asks, account or not. This page reads the hosting instance's catalog, opens the session over the network, and renders it — the view an instance gets after arriving from the network browser through the host's msn profile. Nothing below is stored here; every reading comes from the instance at the address shown, including the taxonomy tab, the txa phylogenic tree the market's products resolve through. That tree used to be a tab of this page drawn from a file published to this site; it now belongs to the channel that holds the products, so there is one tree rather than two that could disagree. The calendar and the farm-plan calculator are features of this channel view.
A package is a decision about what ships together, not one tool per entry: quiar is six tools and the documents they need, and a catalogue that offered them separately would let an instance install a jobs table with no contact list to book against. Every card below is written from the build's own declaration — what a package requires and writes is taken from its tools rather than restated — so this page cannot describe a package the software would not install.
Installing grants nothing. It makes an instance SHOW a tool and provisions the blank documents that tool needs. What a tool may write is decided separately, and denies on an empty grant set. An adapter that arrives able to act because it was merely installed is the shape of a supply-chain problem, and a marketplace is exactly where that goes wrong.
Package · v1.0.0
Products, supply, sales and the standing offer, for an instance that sells goods. The commerce seam is DECLARED here and bound — and granted — by the operator on Ports, never by installing.
Package · v0.1.0
The operator's side of the hosting relationship: what each service is priced at, what each alias has been charged, and what has been credited back. Prices are set here; the cost they are measured against is projected from the operator tolling ledger. FND only.
Package · v1.1.0
Notes, the domain sheet, and the instance's automation and AI seams. The AI providers are DECLARED here and bound — and granted — by the operator on Ports, never by installing.
Package · v0.1.0
The client's own record of their provider-service relationship, held as datum documents in an isolated sandbox and fed through the ports their own service key permits. The home tab says what the sandbox keeps and whether the FND seam is bound and permitted; Design shows the client's own site and publishes their writing to it. Analytics, Contacts, Newsletters and Email are planned tabs with no tool behind them yet, so this package does not offer them.
Package · v2.2.0
Book work, group it into projects, keep the people you book it for, and see the week. Nothing in it is trade-specific: a job's kind is a node the instance mints for itself.
An extension installs no tools. It fills a port — a named seam the software declares and something else implements — so the instance gains a capability rather than a screen. The distinction is the build's own: an extension is declared with the port it fills and ships an empty tool list.
Extension · v1.0.0
Send text to Anthropic's models and read the reply. The key is yours and stays on this instance; what the call discloses is the text itself.
Extension · v1.3.0
Connect this instance to what FND already runs for it: the mail — read what arrived, administer the addresses on its domains, answer from one of them, or hand a message to a person — and the served site, where pages can be read and edited, writing published or taken down, assets uploaded, and the month's traffic counted. FND holds the accounts; this instance holds no credential.
Nothing on this site needs an account today: the channel is open, and it is engaged by any browser that asks. An account will be for holding an instance of your own — the address, and what it publishes to the network — rather than for reading what is already public here.
MiCyte runs on your own machine and holds its data there. The current release is 0.2.0, published under AGPL-3.0 with its source. There is no hosted tier to sign up for first, and no key to ask us for.
The desktop application — the same software without a terminal — is still being built. Until it lands, Get carries the wheel, the repository and the install steps.
The network's recurring events (farm stands, farmers markets, CSA pickups) on a month, week, or year view. Events are not map nodes: each belongs to a host entity and lives in the registrar's qc_log / hc_log event-log datums, shipped raw inside the same served micyte-<msn>.bin the map reads. Your browser derives every occurrence itself (weekly stamps minus off-season closures), so the calendar is correct for any month you open. Filter by who hosts and by what it is.
It will model a season before a bed is committed to it (the plantings, the beds they sit in, and the cadence of what follows what), then export the whole plan as records the software can hold and the season can be run against, and as a spreadsheet you can keep: plots, labels, and timing.
Until then, the serves the same classification datum the calculator will plan against, on its taxonomy tab, so a lookup there is a lookup the software recognizes.