SylvieSI reference
Definitions of the terms, items, roles and states used across SylvieSI and this website.
From the first message to the result
Message, Customer, Evidence, Case, Investigation, Work, Change, Approval, Release, Outcome, then the update to the sender. Each step is linked to the one before it.
What SylvieSI keeps track of
Message (SIG)
A user message or event from a channel. The product also calls it a signal.
Customer (CUS)
The person or account a message comes from, with an explicit trust level.
Evidence (EV)
A cited observation that supports or contradicts a conclusion.
Idea (IDEA)
A feature request, with the arguments for and against building it.
Case (CASE)
A confirmed or suspected bug that can link several messages.
Investigation
An analysis that produces a root cause assessment (RCA).
Work (WORK)
The steps and owners needed to resolve a Case.
Change (CHG, CAP)
A proposed change: a native engineering change (CHG) or an approved component (CAP).
Approval (APR)
A person’s decision on the exact change.
Release
A change delivered to an environment after approval.
Outcome (OUT)
The measured result, confirmed or not.
Objective (OBJ)
A goal set in Sylvie, linked to the items above.
Schedule (SCH)
A recurring task.
The four results of an investigation
Verified
A passed reproduction or a direct trace match, confirmed by a person.
Probable
The evidence points to a cause but does not establish it. A model’s conclusion can reach this state at most.
Insufficient evidence
There is not enough to judge. The Case lists what is missing.
Unable to determine
The cause could not be established with the information and permissions available.
The six states of an outcome
Awaiting
The change exists and measuring has not started.
Measuring
SylvieSI is collecting the checks and measurements.
Verified
Every configured check passed and a person confirmed.
Not achieved
The checks ran and the goal was not met.
Inconclusive
There was not enough data to decide.
Regressed
The bug returned after the outcome was verified.
Roles
Owner
Full access to the workspace.
Admin
Manages sources, policies and access.
Product
Works with messages, Ideas, evidence and experiments.
Engineering
Works with Cases, Work and Changes.
Support
Works with messages and drafts of replies.
Reviewer
Decides approvals in their area.
Viewer
Read-only access.
Parts and terms
SylvieSI
The product from THE SHRIKS, formerly called SylvieAI. It has three parts: Sylvie, Mobius and Ouroboros.
Sylvie (the ship)
The workspace where your team sets goals, investigates and reviews running work.
Mobius (the observatory)
The part that reads and sorts what users send. Its product name is Customer Intelligence.
Ouroboros, O.B. (the chamber)
The part that finds causes, prepares changes, gets approval and checks results. Its product name is Product Operations.
THE SHRIKS
The technology company that makes SylvieSI. Laukik Rajput is its founder.
Customer Intelligence (Mobius)
The part that collects user messages and sorts them into bugs and feature requests.
Product Operations (Ouroboros, O.B.)
The part that investigates, prepares changes, gets approval and checks results.
Sylvie
The workspace where goals, investigations and running work live.
Approved component
A versioned web component, shipped by SylvieSI, that can be shown on your page.
LiveLayer
Our name for the delivery path for approved components.
Product Graph
What SylvieSI knows about your product: routes, components, APIs, roles and processes.
Resolution Graph
The links between a bug, its cause, the work, the change and the outcome, used to start new investigations from past Cases.
Where to read more
The six permanent boundaries are on the Trust and control page.
Trust and control