---
title: Scope test
order: 1
description: "The question every proposed capability has to answer: does it read the model magus already had to build, or does it make magus learn something new about the world? Reads stay small; acquisitions are where a tool loses its shape."
tags: [glossary, design-and-scope]
---

# Scope test

The question every proposed capability has to answer: does it read the model
magus already had to build, or does it make magus learn something new about the
world? Reads stay small; acquisitions are where a tool loses its shape.

## Example

`magus explain` reads the model magus already built; it is the shape of a capability that
passes.

```sh
magus explain internal/httpx
```

## Used in

<!-- BEGIN GLOSSARY USAGE (generated by glossary-usage-generate from the knowledge graph; edit the generator, not this list) -->

The knowledge graph holds no docs section or code type by this name outside the glossary.

<!-- END GLOSSARY USAGE -->

## See also

- [One-vocabulary rule](one-vocabulary-rule.md)
- [Scope](../scope.md)