1.9 KiB
1.9 KiB
AstrBot ImageStudio
AstrBot ImageStudio is an AstrBot role asset production and image-generation workspace plugin.
It provides two UI surfaces:
- AstrBot Plugin Page UI for lightweight status, queue, recent jobs, and quick entry points.
- Standalone Web UI mounted under AstrBot's plugin extension route for the full workspace.
Both UIs share one backend API, database, queue model, VFS media layer, material library, wardrobe system, and audit trail.
Development Baseline
Use the v3 documents as the source of truth:
imagestudio_full_plugin_dev_doc_v3_ui_adjusted.mdimagestudio_api_contract_v3_ui_adjusted.mdimagestudio_codex_hermes_dev_flow_v3.md
Older v0.1 planning is superseded by v3. In v3, the central fact chain is:
character_profiles
-> profile_workflows
-> workflow_nodes
-> generation_tasks
-> generation_images
Current Stage
This repository is aligned to S0-1: v3 directory and configuration baseline.
Next tasks:
S0-2common response DTO.S0-3request id and audit logger foundation.S1-1character_profilestable, repository, and service.S1-2profile_workflowsandworkflow_nodes.S1-3generation_images.
Repository Layout
main.py
metadata.yaml
_conf_schema.json
config.yaml
adapters/
core/
engines/
backend/
database/
assets_builtin/
pages/imagestudio/
web/
frontend/
data/
The root directory is the plugin repository root. Do not introduce a second backend service or a standalone web port.
Non-Negotiable Rules
- Standalone Web UI must be served by AstrBot plugin extension routes.
- Plugin Page UI and Standalone Web UI must call the same backend API.
- Frontend code must not read or construct real disk paths.
- API keys and tokens must not be returned to the frontend in plain text.
- Every write operation must record
audit_logs. - Generated images must have
generation_imagesrecords. - Media access must go through signed media APIs.