aprender 0.70.1

Next-generation ML framework in pure Rust — `cargo install aprender` for the `apr` CLI
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

<!-- PCU: cli-capability | contract: contracts/apr-page-cli-capability-v1.yaml -->

# apr capability

What this build can and cannot do, and why. The answer is read from the model-capability contract.

**Category**: Inspection

## Synopsis

```text
apr capability [--json]
```

## What it prints

The model-capability registry that this binary was **built** from. The contract `contracts/apr-model-capability-v1.yaml` is embedded at compile time through its packaged mirror, `crates/apr-cli/contracts/apr-model-capability-v1.yaml`. So a published binary reports its own facts, not a file that happens to be on the host. Every unsupported operation prints the reason it is unsupported. `--json` emits the contract's own sections verbatim, so a consumer reads the same field names the contract declares.

## Example

<!-- example-cost: trivial -->
```bash
apr capability
apr capability --json | jq 'keys'
```

## Full help

Run `apr capability --help` for the complete option list.

## See also

- Source: [`crates/apr-cli/src/commands/capability.rs`](https://github.com/paiml/aprender/blob/main/crates/apr-cli/src/commands/capability.rs)
- Contract: [`contracts/apr-model-capability-v1.yaml`](https://github.com/paiml/aprender/blob/main/contracts/apr-model-capability-v1.yaml)
- Page contract: [`contracts/apr-page-cli-capability-v1.yaml`](https://github.com/paiml/aprender/blob/main/contracts/apr-page-cli-capability-v1.yaml)