Document the user-facing /image flow, hosted-provider setup, local GPU setup, supported model/backend recipes, troubleshooting, resource requirements, and security/cost implications.
Provide concise code/config examples an agent can use to help users call both hosted and local paths. Examples must show how to inspect hardware/backend availability, choose a tested model, submit a generation/edit request, and collect the resulting image.
Acceptance criteria
Documentation explicitly says mechanism selection happens first by default.
Hosted API baseline fields and provider deviations are documented.
Every local model recipe names its tested backend/version, model source, VRAM/RAM expectations, supported sizes/operations, and failure modes.
Examples are runnable or tested in CI with mocked services; no secrets or huge weights are included.
Docs distinguish tested support from illustrative/untested possibilities.
Close reason
Closed
Imported from beads archie-core-1786748942296-8-260e931d · GitHub #502 · type task · priority P2 · created 2026-08-14 · closed 2026-10-05
## Scope
Document the user-facing `/image` flow, hosted-provider setup, local GPU setup, supported model/backend recipes, troubleshooting, resource requirements, and security/cost implications.
Provide concise code/config examples an agent can use to help users call both hosted and local paths. Examples must show how to inspect hardware/backend availability, choose a tested model, submit a generation/edit request, and collect the resulting image.
## Acceptance criteria
- Documentation explicitly says mechanism selection happens first by default.
- Hosted API baseline fields and provider deviations are documented.
- Every local model recipe names its tested backend/version, model source, VRAM/RAM expectations, supported sizes/operations, and failure modes.
- Examples are runnable or tested in CI with mocked services; no secrets or huge weights are included.
- Docs distinguish tested support from illustrative/untested possibilities.
### Close reason
Closed
---
_Imported from beads `archie-core-1786748942296-8-260e931d` · GitHub #502 · type task · priority P2 · created 2026-08-14 · closed 2026-10-05_
sam
added the mediumtask labels 2026-10-27 13:34:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Scope
Document the user-facing
/imageflow, hosted-provider setup, local GPU setup, supported model/backend recipes, troubleshooting, resource requirements, and security/cost implications.Provide concise code/config examples an agent can use to help users call both hosted and local paths. Examples must show how to inspect hardware/backend availability, choose a tested model, submit a generation/edit request, and collect the resulting image.
Acceptance criteria
Close reason
Closed
Imported from beads
archie-core-1786748942296-8-260e931d· GitHub #502 · type task · priority P2 · created 2026-08-14 · closed 2026-10-05