The words that appear in the product, in one place. Where a term has a page of its own, the heading links to it.
Some words you may see in older material have been retired. See Words we do not use.
Organisation model
The organisation model is what intelligent.page builds first: your people, customers, projects, metrics and what matters right now, read from your website and the systems you connect. Every request is answered from it, and every finished piece of work writes back into it.
Company audit
The company audit reads your organisation stage by stage — market, customers, product, pricing, channels, operations, outcomes — and records what it visibly decided, what it has not decided, and in what order. It runs with every organisation-model build and is written into the directory’s audit.
Memory
Memory is everything the work has touched — every doc, decision, task and source — kept per directory and queryable in plain language. Ask a question and it answers from the memory, citing the records it used.
Scope
Scope is how far a task is allowed to run. It is chosen per task in the composer at send time, and the last choice sticks for the next one — so a quick question stays quick and a real build gets the whole model behind it.
Interfaces and surfaces
An interface is the surface a piece of work comes back as. intelligent.page picks the one the work needs rather than the one tool it has, and the page keeps updating as the model underneath it changes.
Dossier
A dossier is the finished deliverable for one request: every interface the work needed, the sources it drew on and the assumptions it made, kept together on one shareable page. One problem returns one dossier.
Projects, drivers and milestones
A project is a bet on one driver — a metric the organisation wants to move — inside one stage of the organisation, such as pricing or channels. The tasks that serve that driver roll up into it, and its milestones are metric targets rather than to-do lists.
Driver
A driver is a metric the organisation wants to move — repeat rate, contribution per channel, activation. Drivers come out of the model’s problem-state and metrics-model stages, and each project is a bet on exactly one of them.
Milestone
A milestone is a checkpoint inside a project, shown as a diamond on the directory timeline when it has a date. Metric milestones state the value the driver should reach, such as 22% repeat rate; deliverable milestones are the interfaces the project has to ship; planned milestones are the ones a task placed on its Timeline, with the tasks that lead to them; manual milestones are anything you add yourself.
Directories
A directory is one modelled organisation with its own memory, members and boundaries. Run one for your own company, and more for the competitors or stakeholders you want to study alongside it — the same analysis pointed both ways.
Issues
An issue is one open item the work could not close on its own. Everything a task leaves unresolved lands here as one list, each item carrying a label that knows how it closes — answer, choose, attach, accept or mark done — and the answer writes straight back into the interface that asked for it.
Data request
A data request is an issue the work raises when it needs a value it could not find — a price, a conversion rate, a headcount. It shows the placeholder it used so the work can finish, and your answer writes straight back into the cell that asked.
Claims
Claims are the taste, insights, assumptions and judgments the work must align with. Each is a statement the model proposes or you record; approve it and it becomes a boundary every later task in that directory respects, reject it and it never applies.
Benchmark
Benchmarking runs the brands you compete with as directories beside your own and points the same analysis both ways — pricing, channels, positioning — so you see where you stand rather than guessing.