Riveta Labs Glossary
Agent: A workflow that uses AI plus business rules to perform tasks and produce outcomes.
AI-resolution: Percent of conversations or tickets fully resolved by AI without human help.
Alpha: The first working version you can click or run. Target 48-60 hours from intake.
Avatar: A lightweight profile of your role, industry, tools, and KPIs used to tailor solutions.
Book rate: Percent of visitors or leads who schedule a call.
Change log: A dated list of what changed, why, and the observed result.
Close rate: Percent of shows that buy.
Conditional guarantee: If the KPI window is missed by Day 14, we extend up to 14 days within scope, assuming success actions are completed.
Day 0: Intake complete and access granted. Sprint clock starts.
Day 14: Deadline for KPI proof and handoff. Extensions apply only per SLA.
Feedback: Your scored response to an alpha or iteration that sets the next priority.
Fit Check: 15-minute call to validate KPI, scope, access, and timeline before we start.
Gross margin: Price minus variable cost. Used to plan profit targets.
HMAC: Cryptographic signature on Shopify webhooks used to verify authenticity.
Idempotency: Designing automations so the same webhook processed twice does not duplicate work.
Intake: The form and handoff that provide KPI, baseline, access, and constraints.
Instrumentation: Events and metrics added to measure performance and outcomes.
Iteration: A 24-36 hour change cycle where we ship, test, and measure.
KPI: Key Performance Indicator. The metric we agree to move in this sprint.
KPI baseline: Your starting measurement before we build. Used to verify the delta.
KPI delta: The measured change from baseline to current value.
KPI window: The result range and time frame that defines success for the sprint.
Lead routing: Rules that send new leads to the right person or agent in real time.
Line item properties: Extra fields collected on add to cart or checkout for that specific item.
Managed environment: Hosting we provision when your infra is not used. Includes observability and rollback.
Metafields: Custom data fields on products or the store used for dynamic content and links.
Observability: Tools that show system health and behavior such as logs, metrics, traces, and alerts.
PIF: Pay in full. Single payment for the sprint.
2-pay: Split payment across two charges for the same sprint.
Repository: Version-controlled code base where changes are tracked.
Rollback: Revert to a previous version if a change causes issues.
Scope: The agreed set of features, systems, and outcomes included in the sprint.
Scope creep: New tasks or features outside scope that slow delivery and dilute results.
SLA: Service Level Agreement. Our time and delivery commitments for the sprint.
SLO: Service Level Objective. Reliability targets such as uptime or latency.
Speed-to-lead: Time from lead submission to first human or agent contact.
Sprint: A 14-day build focused on one outcome with daily iteration and measurement.
Staging: A safe environment to test changes before production.
Success actions: Buyer-side tasks required for outcomes such as access, approvals, and feedback windows.
Throughput: Units of work completed per time period, for example tickets per hour.
UTM parameters: URL tags that track traffic source, medium, and campaign.
Logs and evals: Run logs plus evaluation scores that show quality and accuracy over time.
