# Glossary

### Acceptance Criteria

The agreed conditions that must be met for a deliverable to be accepted.

### Agile

An iterative approach to delivery based on learning, feedback, prioritisation, and incremental progress.

### Alpha

The phase used to test possible solutions and risky assumptions.

### Background IP

Intellectual property that existed before a project or was developed independently of the customer engagement.

### Backlog

The prioritised list of work items to be delivered by the team.

### Beta

The phase where the chosen solution is built and tested with real users.

### Change Control

The process for assessing and approving changes to scope, time, cost, risk, acceptance, or obligations.

### Delivery Governance

The system of meetings, controls, evidence, and decisions used to keep delivery on track.

### Discovery

The phase used to understand the problem, users, constraints, and options before committing to a solution.

### Foreground IP

Intellectual property created specifically during a project.

### Framework Agreement

The master agreement that defines the overall commercial and legal relationship.

### Live

The phase where the service is operated, monitored, supported, and continuously improved.

### RAID

Risks, Assumptions, Issues, and Dependencies.

### Roadmap

A plan showing how a product, service, or project is expected to develop over time.

### Statement of Work

The contractual document that defines the specific work package, deliverables, milestones, acceptance criteria, and payment triggers.

### Subcontractor

A third party engaged to perform part of the work on behalf of the company.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://framework.aic.io/company-operating-manual/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
