MiCyte

← The wiki

99 — What is not built

BuiltRendered from 99-roadmap.md in the public repository. Edits belong there.

This page lists what MiCyte does not do yet, grouped by area. Each item links to the page that states the built part. When an item is built, it is removed here and described on its page.

Core and storage

  • One materialization for reading and writing. Writes go through WORKBOOK-YAML; the workbench reads a SQL projection (10).
  • An authority backend other than SQLite (20).
  • Shell types defined once. shell.py and shell_state.py both define the shell's scope, chrome, state and request types (30).
  • micyte/state_machine/mediation_surface/ is an empty package.

Tools, lenses and hyphae flags

  • Hyphae flags. The registry type exists and is empty; nothing raises a flag; tool eligibility does not read flags; the lens registry's flag_lens_id is never passed (60).
  • Binding a tool to a hyphae value. applies_to_hyphae_value exists; no tool sets it (80).
  • A surface for lens toggles. The toggle API works; no surface mounts its panel (81).

Applications

  • Payment capture for Brevat. commerce_offering has no filling extension (Brevat).
  • SMS for Oveure. sms_provider has no filling extension (Oveure).
  • Scheduled routines. No routine runs on a schedule; each is run by hand (40).

Network

  • Discovery without a contract, resolving a magnet reference on a remote instance, a key rotation policy, and joining from an open channel (90).
  • Delivery between instances on different machines has not happened.
  • Channel app posts: the four channel types are declared and enforced, but no channel records posts of the declared post types (sell and buy orders becoming transactions, feed posts), and whether the Subject Network type is kept is undecided (91).

Marketplace

  • The catalogue address on the package_source binding, a GitHub fill, and offline package installation (93).

Accounts and hosting

  • Self-serve account creation, the hosted adapters as a catalogue extension, a host setting for the registrar, person-level network accounts, and base-plan allowance enforcement (96).
  • Serving an instance from the published package. The package has no host; an archive loads into a store, not a running instance (98).

Desktop and mobile

  • A desktop application with a local database. Not built. The design is to run the existing portal host on a loopback port inside a desktop shell (pywebview first) with one local SQLite store per install. connect_sqlite() creates the file and schema on first use, so a new install needs no migration step. It depends on the host being distributable, which it is not today.
  • Local sync of a hosted instance, and a mobile app (96).