add_progress_note
shallowio.applayer/tango · Verify this server
Step 4 of the Tango working agreement (work in the open). Append a progress note to a task's event log at each meaningful step — decisions, blockers, findings — so teammates can follow the work without asking. Attribution is required: hold an active lease, or pass an `acting_worker_id` you own — a human assignee or org owner may also act without a worker identity. Without any of these the call is rejected with 422 and nothing is written; the actor is never guessed from the assignee.
1 trials · measured 2 days ago
add_progress_note scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.applayer/tango, measured 31 Aug 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-08-31 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/27dfb89d-d99e-4842-aeb4-e5ed0e303c61)