GLOSSARY
Every term on the map, defined
Every term on the Cinderpath map in one place: the twelve topics and the thirty services, each with the definition its own page gives.
INDEX
All 42 terms
- Access and identity
- AI agents
- AI assistants and agents
- AI Integration & Automation
- AI Search Visibility
- Answer engine content
- Audit evidence
- Automation
- B2B SaaS
- Change management
- Cloud & Modernization
- Cloud and DevOps
- Cloud native
- Conversion and landing
- Demand Generation
- DORA
- Entity and structured data
- EU AI Act
- Evaluation and guardrails
- Fintech
- GDPR
- Integrations and data
- Legacy modernization
- Managed Services
- Measurement and attribution
- Monitoring and on call
- NIS2
- NIS2 and DORA readiness
- Observability
- Paid performance
- Patching and backups
- Process automation
- RAG
- Reconciliation reporting
- Retrieval over your documents
- Schema
- Schema implementation
- Security & Compliance Readiness
- Technical foundation
- The evaluation set
- The event schema
- The evidence pack
TOPICS
By axis
Practice
- AI agents
- An AI agent is software that uses a model to select and perform actions toward a defined goal. Its useful boundary comes from the tools it may call, the information it may retrieve and the conditions that stop or escalate its work.
- RAG
- Retrieval augmented generation, or RAG, gives a language model selected source material at request time before it writes an answer. The retrieval layer determines what can be found, while citations and evaluation show whether the answer remains grounded in that material.
- Automation
- Automation turns a repeatable process into explicit triggers, actions, checks and exception paths. A reliable automation records what happened, preserves ownership and sends ambiguous cases to a person instead of hiding them.
- Cloud native
- Cloud native describes systems built to use programmable infrastructure, managed services and repeatable deployment practices. It is an operating model rather than a requirement to split every application into small services.
- Observability
- Observability is the ability to understand a system's internal condition from traces, metrics, logs and other outputs. It connects technical signals to user journeys and operating decisions so a team can explain failures rather than only detect them.
- Schema
- A schema defines the structure, meaning and allowed relationships of data. It gives producers and consumers a shared contract, whether the data describes an API payload, an analytics event or an entity on a web page.
Regulation
- EU AI Act
- The EU AI Act is a risk-based legal framework for artificial intelligence systems placed on the EU market or used in the European Union. It assigns duties according to the system, its use and the organisation's role. The legal obligations belong to the client; Cinderpath builds and operates technical controls that can support compliance work.
- NIS2
- NIS2 is a European Union directive that sets cybersecurity risk-management, governance and incident-reporting duties for covered essential and important entities. National law determines the exact duties and enforcement route in each member state. The legal obligations belong to the client; Cinderpath builds and operates technical controls that can support compliance work.
- DORA
- The Digital Operational Resilience Act, or DORA, sets a common European Union framework for managing information and communication technology risk in financial entities and certain technology providers. It covers governance, incidents, resilience testing and third-party risk. The legal obligations belong to the client; Cinderpath builds and operates technical controls that can support compliance work.
- GDPR
- The General Data Protection Regulation, or GDPR, governs how personal data is processed and protected in the European Union and European Economic Area. It sets principles, individual rights and duties for controllers and processors. The legal obligations belong to the client; Cinderpath builds and operates technical controls that can support compliance work.
Context
- B2B SaaS
- B2B SaaS is software sold to organisations through a subscription or recurring commercial relationship and operated as an ongoing service. Product access, tenant boundaries, billing, releases and support all meet in the same operating model.
- Fintech
- Fintech is the use of software and data systems to deliver or support financial products, payments and financial operations. Its technical work often depends on accurate state changes, controlled access, reconciliation and evidence that can explain an event after it happened.
SERVICES
By line
AI Integration & Automation
- AI Integration & Automation
- AI integration is the work of connecting language models to a defined business process, its source material, permissions, tools and review points so the resulting system can operate under named human ownership.
- AI assistants and agents
- AI assistants and agents are software interfaces that retrieve approved information, use permitted tools and prepare or execute bounded actions while preserving identity, access and human review rules.
- Retrieval over your documents
- Retrieval over your documents is a pipeline that ingests approved material, divides it into searchable units, applies access rules and supplies cited source passages to a model at answer time.
- Process automation
- Process automation converts a repeated workflow into explicit triggers, rules, system actions, audit records and escalation points while keeping exceptions with a named human owner.
- Evaluation and guardrails
- Evaluation and guardrails define the cases, scoring rules, operating limits, logs and human checkpoints used to measure model behaviour before a change reaches normal operation.
- The evaluation set
- An evaluation set is a versioned collection of representative inputs, expected outcomes and scoring instructions used to compare an AI system before and after a model, prompt or data change.
Cloud & Modernization
- Cloud & Modernization
- Cloud modernization is the controlled replacement of fragile infrastructure, deployment paths and system boundaries with repeatable environments, observable services and documented operating ownership.
- Cloud and DevOps
- Cloud and DevOps work creates repeatable accounts, environments, infrastructure definitions and deployment controls so application changes follow the same tested path into production.
- Legacy modernization
- Legacy modernization replaces a constrained system in bounded increments by mapping dependencies, isolating change boundaries and moving one capability at a time without requiring a full rewrite.
- Integrations and data
- Integration and data work connects systems through explicit contracts, event definitions, retries, identity rules and reconciliation so records can move without hiding failures or duplication.
- Reconciliation reporting
- Reconciliation reporting compares records held by two systems, identifies missing or conflicting values and records the age and ownership of each unresolved difference.
Security & Compliance Readiness
- Security & Compliance Readiness
- Security and compliance readiness turns obligations into technical controls, evidence records and named operating responsibilities that can be inspected without reconstructing months of activity.
- Access and identity
- Access and identity work defines who can enter each system, what they may do, how secrets are handled and how access is approved, reviewed and removed.
- Audit evidence
- Audit evidence is the collection of logs, approvals, review records and supplier information that demonstrates a control operated during a stated period.
- The evidence pack
- An evidence pack is a dated, indexed collection of control records that links each audit request to its source, owner, period and supporting artefact.
- NIS2 and DORA readiness
- NIS2 and DORA readiness maps applicable operational resilience duties to current technical controls, evidence sources, accountable owners and a sequenced remediation plan.
Managed Services
- Managed Services
- Managed services assigns named ownership to monitoring, incidents, changes, patches, backups and operating records for systems that must keep working after delivery.
- Monitoring and on call
- Monitoring and on call work connects service signals to actionable alerts, a named rota, documented authority and an escalation path for incidents outside working hours.
- Patching and backups
- Patching and backup operations set a tested cadence for software updates, data copies, retention, restore exercises and documented exceptions across managed systems.
- Change management
- Change management records the reason, owner, review, release path and rollback method for production changes so responsibility remains visible before and after deployment.
AI Search Visibility
- AI Search Visibility
- AI search visibility makes a company and its services readable as consistent, citable entities through accessible rendering, explicit page definitions and structured data tied to visible content.
- Technical foundation
- The technical foundation for AI search visibility is server-readable HTML, stable routing, clear information architecture and crawl controls that expose the same content visitors receive.
- Entity and structured data
- Entity and structured data work aligns names, identifiers, relationships and page markup so the company, its services and its published facts describe one consistent subject.
- Schema implementation
- Schema implementation generates machine-readable entities and relationships from the same approved content records used by the visible page, preventing markup from drifting away from published facts.
- Answer engine content
- Answer engine content gives each page a self-contained definition, explicit supporting facts and a clear subject hierarchy that can be quoted without relying on hidden context.
Demand Generation
- Demand Generation
- Demand generation connects a defined offer, paid distribution, landing experience and consent-aware measurement so each inbound lead has a traceable path from source to commercial response.
- Paid performance
- Paid performance work connects account structure, audience rules, creative, spend controls and landing destinations to a named offer and an inspectable commercial objective.
- Conversion and landing
- Conversion and landing work builds a focused page and response path around one defined visitor action, with message continuity from the traffic source through confirmation.
- Measurement and attribution
- Measurement and attribution records the events, identifiers, consent states and ownership needed to connect an inbound visit to a lead response without pretending uncertain links are exact.
- The event schema
- An event schema is the agreed catalogue of user and system actions, their properties, consent conditions, owners and downstream uses before tracking code is implemented.