Start here
Set up a workspace, choose the right operating profile, and understand what Analyst owns.
Workspace setupSolo vs team workspacesRole modesDomain and delivery model defaults
Product documentation
Learn the Analyst evidence workflow.
Analyst is built for the full BA lifecycle: intake, discovery, requirements, stories, UAT, releases, decisions, retained artifacts, and signatures. These docs explain how to work calmly inside the workspace without turning evidence management into another ticket queue.
Guides
How to use the workspace
This hub starts with the workflows that are already live. Deeper article pages can be added as the product hardens.
Run the BA lifecycle
Move from intake and discovery into signed, traceable evidence without losing the thread.
Intake inboxDiscovery questionsRequirements reviewStories and acceptance criteria
Prove readiness
Use UAT, defects, traceability, releases, and decisions to defend go/no-go posture.
UAT test evidenceDefect triageTraceability mapRelease readiness
Retain official artifacts
Review drafts, accept official documents, request signatures, and store signed copies.
Draft review queueLibrary artifactsSignature linksEvidence pack exports
Use Analyst AI safely
Let AI propose, summarize, and audit while people keep control of official evidence.
Agent modesProposal reviewAI usage budgetsHuman approval boundaries
Admin and security
Prepare workspaces for real customers, teams, pilots, and enterprise review.
Members and permissionsAudit logsStorage setupDomain launch checklist
Product reference
What a buyer, BA, PO, or security reviewer needs to understand.
These are the core docs themes Analyst must make clear before a serious pilot or production rollout.
How Analyst works
Analyst is a lifecycle workspace for BA and PO evidence. Work starts as intake, discovery, requirements, stories, UAT, defects, release decisions, and retained artifacts, then becomes defensible through traceability, review, audit, and signatures.
Workspace and project evidence graphReview-first drafts and proposalsOfficial Library retention
BA lifecycle
Run the path from stakeholder signal to signed evidence without losing context. Analyst keeps elicitation, process artifacts, requirements, stories, acceptance criteria, UAT, defects, releases, and evaluation connected.
Discovery and elicitationRequirements and typed backlogUAT, defects, release readiness
Product Owner usage
Use Analyst for outcome framing, stakeholder requests, prioritization, SAFe/PO planning, PI objectives, feature hypotheses, roadmap vision, and release confidence without turning it into a sprint execution board.
Outcomes → features → releasesWSJF/RICE prioritizationPI readiness and dependency pressure
AI guardrails
Analyst AI is proposal-first. It can draft, summarize, audit, explain, and prepare follow-up packets, but it cannot approve, sign, validate, release, delete, baseline, or overwrite official evidence.
Coach, Builder, Auditor, Explainer, OperatorCited evidence linksHuman acceptance before official records
Evidence chain
Every important artifact should answer where it came from, what it supports, who reviewed it, what changed, and why it is safe to rely on. Analyst makes that chain visible across requirements, stories, UAT, releases, and Library.
Trace map and gap queueValidation and signaturesTimeline and audit posture
Security posture
Analyst is designed around authenticated workspaces, role permissions, RLS-backed data, audit logs, server-backed downloads, AI budget controls, and review-only external intake. Hosted rollout still requires provider-specific DNS, storage, and email checks.
Roles and permissionsAudit exportsPilot exceptions tracked explicitly
Exports and packets
Use exports when a BA or PO needs to defend work outside the app: evidence packs, trace maps, compliance summaries, audit CSVs, analytics reports, retained files, and signature packets.
Evidence pack markdownTrace map CSVCompliance and audit exports
Signatures and storage
Accepted artifacts can move into Library, route for stakeholder signature, and retain signed files. Local/private storage is smoke-tested; hosted production still needs mirrored S3-compatible configuration and verified email/domain delivery.
Signature routingRetained Library filesS3-compatible storage readiness
Practical how-tos
Start with the jobs users actually need to finish.
These short paths keep Analyst oriented around evidence outcomes instead of turning the docs into a feature inventory.
Set up a first workspace
- 1Choose solo or team mode
- 2Name the workspace
- 3Create or import the first project
Make a baseline defensible
- 1Review requirements
- 2Resolve missing validation
- 3Connect stories, AC, and UAT
Prepare a release decision
- 1Check failed UAT and defects
- 2Review release confidence
- 3Record the decision rationale
Retain signed evidence
- 1Accept a reviewed draft
- 2Send or copy a signature link
- 3Attach the signed copy to Library
Common questions
Is Analyst replacing Jira, Linear, Miro, or Confluence?
No. Analyst owns BA evidence, readiness, stakeholder signal, traceability, and retained decisions. Execution tools and visual collaboration tools can still exist around it.
Can AI approve requirements or sign documents?
No. AI can propose, summarize, draft, and audit. It cannot silently approve, sign, validate, release, delete, baseline, or overwrite official evidence.
What should a new BA do first?
Create or import a project brief, answer discovery questions, and use the Overview to see what is blocked, stale, missing, ready, or waiting on a stakeholder.