tambo 0.6.3

Install and prove the whole AI knowledge-tool kit
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
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

# Crew capability contracts

Tambo installs the selected crew runtime, but it does not take ownership of
the runtime's security or admission policy. Shantytown is a host executable, so
its adapter reads back the installed `st` version. Creel's decisive facts exist
inside the browser; verification therefore consumes two browser-produced JSON
documents:

```console
tambo verify \
  --creel-doctor creel-doctor.json \
  --creel-admission creel-admission.json
```

Both schemas are version 1 and reject unknown fields. A new producer field
cannot silently become evidence an older Tambo claims to understand.

## Doctor

```json
{
  "schema_version": 1,
  "overall": "pass",
  "checks": [{
    "id": "secure-context",
    "status": "pass",
    "severity": "required",
    "evidence": "browser reported a secure context",
    "remediation": "serve Creel over HTTPS",
    "redacted": true
  }]
}
```

Check IDs must be non-empty and unique. Status is `pass`, `fail`, or
`unknown`; severity is `required` or `advisory`. Every check carries non-empty
redacted evidence and remediation. Every required check and the aggregate must
be `pass`.

The Creel doctor workstream owns which checks it emits, including secure
context, persistence, popup/bridge permissions, provider credential presence,
Quipu WASM, state-repository health, service-worker freshness, and leases.
Tambo validates the contract; it does not reproduce those probes.

## Admission

```json
{
  "schema_version": 1,
  "verdict": "admit",
  "provider_window": {"status":"pass", "evidence":"below ceiling"},
  "device_tab_cap": {"status":"pass", "evidence":"one slot available"},
  "signal_freshness": {"status":"pass", "evidence":"observed now"},
  "reason": "launch is within the redacted policy limits",
  "redacted": true
}
```

The verdict is `admit`, `refuse`, or `unknown`. Tambo proceeds only when all
three signals are measured passes and the verdict is `admit`. It never prints
credentials, accepts an unredacted reason, rounds unknown to zero, or converts
a policy refusal into an installer warning.

Until Creel publishes both producer interfaces, its bundle can be applied but
cannot be marked verified. That refusal is the intended boundary, not a
Tambo installation failure to bypass.