Skip to content

architecture.md

Latest commit

 

History

History
48 lines (35 loc) · 2.93 KB

architecture.md

File metadata and controls

48 lines (35 loc) · 2.93 KB
Raw

FlyBot Architecture

FlyBot is a team of long-lived Bots built on DeepSeek Harness (DSH). Two parts ship: the ds-bot plugin (patched upstream) and the desktop app.

Layout

Path What it is
ds-bot/ Pristine upstream pin (Fei2411/DeepSeek-Bot). Never edit.
patches/ds-bot/ Ordered FlyBot patches on the pin.
core/ ds-bot/ + patches. Ships; all tests run here.
plugins/social/ @flybot/social — social posting plugin.
plugins/tree/ @flybot/tree — knowledge-tree plugin.
plugins/timeline/ @flybot/timeline — where time goes across the local Bot team (swimlanes, communication map, utilization).
app/ Desktop app (Windows/macOS) for the DSH + plugin.

Subsystems

Each subsystem has a detail page under docs/subsystems/ with owned paths, invariants and tests:

  • ds-bot-core — pin, patch format and dev tooling of the patched core; core-host and core-client — its server and browser code
  • plugin-runtime — FlyBot plugin hooks
  • tree — @flybot/tree
  • timeline — @flybot/timeline
  • social — @flybot/social
  • install — scripts and install doctor
  • team — planned human/Chief/specialist authority contract (not shipped); #47–#50 are data/auth/room-membership foundations only

Team authority (planned, not shipped)

Multi-human ownership is planned, not shipped. The proposed contract — human owner ↔ designated Chief ↔ specialists, owner-scoped management, Chief-only cross-owner traffic, approval authority and the routing matrix — lives in docs/subsystems/team.md. Schema (#47), member sign-in (#48), owner-scoped access (#49) and typed room membership (#50) are foundations on that page; team mode stays disabled until that page's authorization gates pass. Issue #16 is resolved: tree Bots may create children under themselves (Option B; see tree).

Integrating

See docs/integrating.md for how to add a plugin or integrate with DSH.

Cross-runtime collaboration is proposed in #198. The room participant contract scopes the same-room DSH + DSH baseline and DSH + OpenCode target. Its current implementation extracts the DSH execution boundary only. The earlier OpenCode pilot contract and offline harness cover a Bot Social transport experiment with independent owner identities; they preserve its same-owner friendship restriction and do not satisfy the room target. No OpenCode adapter or additional team-mode gate is enabled.

Reference

See docs/reference.md for API and CLI reference material.