Working definitions for the terms used throughout CodeSaudi. Follow each one into the guide that puts it into practice.
API
Application programming interface
A defined way for software components to request information or actions from one another. When reviewing an integration, ask what data it receives, which permissions it needs, and how failures are handled.
The existing or simpler process used to evaluate a proposed change. For an AI pilot, it might be manual review, keyword search, or a rules-based workflow. Write it down before testing.
A capitalization table summarizes ownership and the instruments that may affect it. A spreadsheet should be checked against the relevant signed records; neat formatting does not establish its accuracy.
A structured review of evidence, documents, counterparties, and unresolved risks. Its purpose is to support an informed decision, not to guarantee a result or remove uncertainty.
A limited product used to test a specific business or user assumption. Define what it needs to demonstrate and what remains outside scope rather than using the term to excuse a broken experience.
A scoped experiment with agreed participants, duration, data, support, and success questions. A positive pilot can inform the next decision without proving the product is ready for every customer.
The Saudi personal data protection framework discussed in our developer checklist. Engineers should provide accurate data-flow and control evidence; qualified reviewers should determine applicable legal obligations.
A pattern in which an application retrieves relevant material to support a generated answer. Retrieval does not by itself ensure that a response is correct or that a user is authorized to see the source.
A base reading direction used for Arabic and other scripts. Language and direction are separate settings; a bilingual interface also needs deliberate handling of mixed-script text and layout.
Software delivered as an ongoing service. A SaaS product includes onboarding, access, billing, support, and exit arrangements as well as the interface users interact with.
A clear description of what a project includes and excludes. Scope helps a team make reliable commitments and decide whether a new request belongs in the current test or a later phase.
The authoritative reference for a defined purpose, such as a signed contract or current official requirement. Different questions may have different sources; a promotional summary is not always sufficient.