Glossary
Glossary
The product uses these words on every screen, and this site uses them the same way.
- Organization
- The space a team works in. Every document, artifact, key, and cost belongs to one organization, and a person can belong to several and switch between them.
- Source
- A place documents come from, such as a Confluence space, a website, a watched folder, uploads, or manual entries, reached through a connector.
- Connector
- A plugin that knows how to read one kind of source and notice what is new, changed, or removed there.
- Sync
- A scheduled run of a connector that brings in new, changed, and removed items for a source.
- Document
- The unit of knowledge and of approval. It has versions, a trust state, and a record of where it came from.
- Trust state
- Where a document stands - ingested, pending review, approved, rejected, superseded, or archived. Only approved documents reach search and the workbench.
- Pending re-review
- An approved document whose source changed. The approved version stays in use, with a flag, until a reviewer decides on the new one.
- Refinement
- A reviewer's annotation, correction, tag, or context attached to a document without changing its source text.
- Restricted
- Content that must not be sent to a model provider outside your control. The product refuses to send it and says what it left out.
- Reviewer mode
- A clearly labeled search for reviewers that includes unapproved content. Nothing found in it can be cited.
- Initiative
- The unit of product work. One owner, a lifecycle (draft, active, on hold, handed off, archived), and the artifacts made for it.
- Stage
- A step in an initiative, from framing to handoff. Stages have a default order but never block you.
- Artifact
- What a stage produces, such as a problem framing, a requirement set, a flow, a design, a mockup, or a bundle. Every change makes a new version.
- Workflow
- The agent procedure that does a stage's work. A run of it asks its questions, streams its progress, and can be steered, edited, cancelled, and resumed.
- Stage interview
- The short questions a stage asks before it drafts, one to three at a time, only about what the approved knowledge and the earlier artifacts do not answer. Each answer is recorded on the version as your input.
- Citation
- A link from a statement in an artifact to an approved document version and passage, with where it sits, who approved it, and a short excerpt.
- Assumption
- A statement no approved passage supports, marked as such with a reason instead of a citation.
- Open question
- Something the agent could not resolve, such as a conflict between documents, a gap, restricted content it could not use, or a product decision. You decide each one.
- Stale
- An artifact whose inputs changed after it was made, either an earlier artifact or a cited document.
- The three responses
- What you can do with a stale artifact - regenerate it, keep it as is with a recorded note, or merge the new version with your edits.
- Ready mark
- A record that a stage's checks were confirmed, either by a reviewer or by the owner as a self-check. The two are shown as different kinds.
- Design system
- Your organization's tokens and components, registered so designs and mockups are built from them. It never changes how the workbench itself looks.
- Token
- A design value, such as a color, a type size, or a spacing step.
- Mockup
- A clickable, multi-screen HTML proof of concept rendered from the design system and shown in a sandbox.
- Walkthrough
- An ordered, annotated path through a mockup, each step pointing at one element with the requirement and flow step it shows.
- Handoff bundle
- The versioned export for engineering - the mockup, designs, flows, epics and stories with Given, When, Then scenarios, citations, and open questions.
- Export profile
- A layout the handoff bundle can be written in at export, matching the folder shape a spec-driven engineering method reads. Every profile carries the same content and citations.
- Planning prompts
- The prompts in a bundle's prompts folder for the planning engineering does itself - the architecture document, the task breakdown, and the test plan - each pointing at the bundle files it draws on.
- Local embedding service
- An optional container that runs a small open embedding model beside the database, so search can match meaning as well as words without sending passages to a provider.
- Reference initiative
- A test initiative with known documents and a rubric, run end to end to compare output as prompts and models change.