Repository navigation
Foundation's T3 Code / Claude Code reference recipe now defaults to telemetry opt-out (#108).
- Setting: set
T3CODE_TELEMETRY_ENABLED=falsein the T3 server environment before start, and a nonemptyDISABLE_TELEMETRYin the Claude process environment, for the lead and worker sandboxes, through the native environment mechanism. A project can record an authorized exception that names the egress it allows. - Verification: after a restart and a turn, Claude reports
analytics_disabled: true, and the T3 trace showsAnalyticsService.recordspans but nosendBatchoringest.t3.codesrequest, ideally compared with a pre-change trace. - Scope: model and permission mode stay explicit. Operator clients (desktop app, phone) are outside the recipe and unverified.
- Limits: not zero egress, not OpenTelemetry, not provider data retention. The Claude 2.1.306 effects are unverified, and T3 relay diagnostics are lost. Re-verify after upgrades.
- Lab evidence: a dated 30 October entry is added to the qualification record.
Source and review:
- The canonical Notion Foundation skill was updated through the Skills API before the Git export; its supporting files read back byte-exact.
- Two fresh independent Opus 5.5 reviewers accepted the exact patch after one repair round.
- After Claude Code Auto refused the merge, the owner gave an explicit decision for this PR and the operator merged it (PR #112). That refusal is recorded, not resolved.
- Checks: 9 skills, 0 errors; 16 tests passed; Method checks passed.
Only foundation changed (Foundation SKILL.md and references/setup.md). factory.yaml and the other skills are unchanged. This is a package and source release: it applies nothing to any installation and is not an installation claim.