How to sign in, upload sources, run the pipeline and review what it produces. Written for the people using the workspace, not for the teams deploying it.
Avcel helps teams turn business intent into governed delivery artifacts, briefs, requirements, blueprints and evaluation evidence, inside your organization workspace.
Use the paperclip or attach control in project chat, or drag files into the chat area.
Use any of these.
Avcel runs a staged delivery flow. Exact timing and available artifacts vary by project. This is the shape every user sees.
Captures intent in business language: what you need and why it matters. Appears first after Start when the brief is empty.
Turns constraints and goals into structured, reviewable requirements that later stages can rely on.
Expands the plan into delivery-oriented specifications and supporting design material. Application runtime affordances appear when blueprint work is ready.
Closes the loop with evaluation outputs, so reviewers see evidence before treating work as complete.
Visual relationships and diagrams drawn from project outputs. Open Context Graph in the right pane when you want the map. It is not required to start a run.
The center pane is the working conversation for the project: uploads, Start and commands, and system status notes as the run progresses. Helpful chips appear when relevant, including Upload documents, Start, /help and /status.
Primary deliverables open in the Documents tab so you can read them beside chat.
Available from the right pane tabs and from Canvas-related controls.
Stages and files appear here as they become available, and counts update as artifacts are produced. Use the play controls only when a stage invites generate, regenerate or Start.
Between major stages Avcel asks you to confirm before moving on. That keeps review in the loop: read what was produced, then continue or stop.
When the prompt appears:
Choose Stop here to end the run after the current stage. You can start again later with updated uploads.
Once a stage has output, the play control offers regenerate instead of Start. Use it when you intend to redo that stage, not for the first empty Business Brief run.
Short capability notes for operators and stakeholders. No deployment, security internals or vendor implementation detail.
Work moves through clear stages, brief to requirements to blueprint to evaluation, so intent, design and evidence stay connected.
Artifacts are first class: upload sources, generate deliverables, and read them in the Documents pane without leaving the project.
Stage continue prompts keep people in control between major phases. You decide when the next stage starts.
When diagrams exist in project outputs, Context Graph surfaces a small set of key views so architecture relationships are easier to navigate.
Avcel is designed for environments where code, data and models stay inside your perimeter. Agents and generation run under organizational controls.
Runs are staged and reviewable. Prefer clear inputs and deliberate Start and Continue actions over open-ended generation sessions.
These belong in private architecture and operations material, not in this help set.
Infrastructure topology, secrets and deployment runbooks
Internal APIs, worker schedules and model routing
Compliance evidence packs and examiner-facing detail