MiCyte

The build

Gadgets

A gadget is a decision about what ships together. quiar is six tools and the documents they need — a catalogue that offered them separately would let an instance install a jobs table with no contact list to book against. Everything below is written from the build's own declaration, so this page cannot describe a gadget the software would not install.

Brevat Enchir Oveure PIM Quiar – Freelancer Claude FND Service

Before you install anything

Installing grants nothing.

It makes an instance show a tool, and creates the blank documents that tool needs. What a tool may write is decided separately and denies on an empty grant set; what a seam may call outward is a second decision after that. 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.

So the download here is the declaration, digest-verified — the same one an instance pulls over its own network door. It enables tools; it never adds code. Every tool it names is already in the MiCyte package you installed, so a declaration cannot introduce a tool your build does not have. There is no package archive, deliberately: a file an instance unpacks and runs is a way to ship code, and shipping code without a signing story is the half that cannot be made safe on its own.

Apps

A hub, and a sandbox of its own.

An app is a gadget with a hub — a tabbed surface over its own tools — and its own sandbox to keep its records in.

App · v1.3.0

Brevat

brevat

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.

  • Toolsbrevat, product_catalog, stock_log, supply_ledger, sales_ledger, offer_ledger
  • Hubbrevat
  • Declarescommerce_offering
  • Creates on install6 blank documents
  • Its tools may write5 declared writes
  • Sandboxits own, numbering farm
  • Needs these archetypesinvoice, offer, offering_record, stock_entry

Declaration · brevat 1.3.0

sha256 sha256:5c3be99bdb9fb8b26f0e15632c7dbdec636ef2786f8b1ce41460e6a56fa7af26

App · v1.2.0

Enchir

enchir

The projects, commissions and pieces of work an instance keeps, grouped by what they are — and, when a website is connected, the profiles that site offers them up through: which photograph stands for each, the order of the rest, and the short and long description.

  • Toolsenchir
  • Hubenchir
  • Declaressite_hosting

Declaration · enchir 1.2.0

sha256 sha256:179181be9dd35b64cd77b874ac3e92f9fc1902c2085e97555018bb3fdd3f976f

App · v1.3.0

Oveure

oveure

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.

  • Toolsoveure, lcl_editor
  • Huboveure
  • Declaresai_provider, email_provider, sms_provider
  • Creates on install1 blank document
  • Its tools may write18 declared writes
  • Sandboxits own, numbering inherited from your instance's anchor
  • Needs these archetypeslocal_domain_log

Declaration · oveure 1.3.0

sha256 sha256:1b0958316b89300d2192c2167af23ed55a21ee436695fb19cdb29584f488ec81

App · v0.1.0

PIM

pim

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. Home says what the sandbox keeps and what the client pays; Authoring and Design are their site and the writing published to it; Analytics, Email, Resources, Storage, Payment and Domain each light when the seam that feeds them is bound and say why when it is not.

  • Toolspim_overview, pim_design
  • Hubpim_overview
  • Declaresemail_provider, site_hosting
  • Creates on install1 blank document
  • Sandboxits own, numbering inherited from your instance's anchor

Declaration · pim 0.1.0

sha256 sha256:d9e4228ec0b2afbde6415507cf35c97c5c78998f8b2d0d1ea5ce66d8122984d4

App · v2.4.0

Quiar – Freelancer

quiar

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.

  • Toolsquiar, quiar_overview, job_manager, project_manager, contacts_manager, calendar
  • Hubquiar
  • Creates on install5 blank documents
  • Its tools may write5 declared writes
  • Sandboxits own, numbering registrar
  • Needs these archetypescanvass_visit, job_event, local_domain_log, natural_entity_profile, project_profile

Declaration · quiar 2.4.0

sha256 sha256:431edb00eebd6f64c75d2413556745dc3199004b7eddad59b216e5c3eb3aca5c

Extensions

What stands in a seam.

An extension fills a port an app employs. It ships no tools and no screen: selecting one connects a seam, and the seam is refused everything until a grant names it.

Extension · v1.0.0

Claude

claude

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.

  • Fillsai_provider

Declaration · claude 1.0.0

sha256 sha256:ae5b2a30cc01a822305592fcc62fb973c24d46a52b3e2c3a35f44011e8db0e84

Extension · v1.6.0

FND Service

fnd_service

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, sent to the people who subscribed, or taken down, assets uploaded, and the month's traffic counted. FND holds the accounts; this instance holds no credential.

  • Fillsemail_provider, site_hosting

Declaration · fnd_service 1.6.0

sha256 sha256:b1082446db81fdf1fdc8b088bca3946d37d62960542e19ccc5ee601e161d078c

MiCyte 0.4.1, 5 app(s) and 2 extension(s). Source: the package manifest. Get MiCyte · what else is published.