Skip to content

Documentation

Alex Miarsky edited this page Nov 10, 2026 · 1 revision

TACTIC Stream documentation

GitHub Wiki: English · Русский.

This is the entry point for maintained TS documentation. Stream owns the server, core data model, transports and browser UI. Handler is an independent desktop client; its Python objects and local execution are not server APIs.

Need Start here
Visual presentation English · Русский
Product, workflow, docks and administration Full product tour · Русский
Built-in project assistant Presentation · Русский
Custom dashboards and page authoring Presentation · Русский
Built-in Help Presentation · Русский
Project Knowledge Base Presentation · Русский
Install and run Stream Application README
Understand source ownership Architecture
Configure projects through an external administrator agent Agent start, MCP connection and implemented tools, task-specific source references
Server API and core structures TS API map, core model
Compatibility with original TACTIC Compatibility and verification
Shared QML/Vue descriptions and controls Frame contracts
Install, package, upgrade or restore Delivery guides
Use the web application Product Help catalogue
Work with Handler's native API TH API, TH documentation

Source and generated files

  • src/pyasm, src/tactic: native TACTIC core, domain operations and compatibility.
  • src/tactic_stream/server: server transports, application services and lifecycle.
  • frontend/src: editable web UI; frontend/public/help: web Help sources.
  • src/tactic_stream/web: versioned built resources shipped in wheels. Rebuild them through the frontend build; they are not an expendable cache.
  • src/tactic_stream/shared_ui: Stream's portable Frame source. Handler ships its own checked copy; neither installation imports the other checkout.
  • tests, tools, benchmarks: maintained checks and drivers. Checked-in fixtures belong beside their consumer; generated tools/*/output and temporary results are ignored.
  • data, .venv, frontend dependencies and installed browser caches are local runtime/development state. Do not sweep them up as unused source.

Write engineering documentation in English. Keep EN/RU product Help and localization with their owning product. A new document must have a clear audience and a link from this index or its domain index. Update an existing contract before adding another. Keep engineering rules in AGENTS and administrator instructions in admin_agent. Backlog, handoffs, dated audits and acceptance results belong in the workspace's local agent-work/ archive, outside both Git repositories and release bundles.

Clone this wiki locally