Skip to content

feat(addie): add private smoke live composition - #7331

Draft
bokelley wants to merge 2 commits into
mainfrom
conductor/6842-private-live-smoke-launcher
Draft

feat(addie): add private smoke live composition#7331
bokelley wants to merge 2 commits into
mainfrom
conductor/6842-private-live-smoke-launcher

Conversation

@bokelley

@bokelley bokelley commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Replaces the prior pre-live composition wiring with a pure JSON-text declarative contract for the frozen stage-1 authority. This is not a live coordinator.

  • It derives 192 unique, non-secret provider accounting-slot declarations from the immutable 8-probe / 21-cell / 168-assignment authority.
  • Every slot fail-closes as not_provisioned: ordinal 1 requires the exact reviewed request-tool replay binding and semantic request fingerprint; ordinal 2 additionally requires exact provider continuation binding.
  • Production remains hard-null and default-off. The module exposes no provider transport, adapter, coordinator execution, authority/grant path, ledger handle, generic dispatcher, route, job, cron, or ambient enablement.
  • The transparent slot key binds the pinned admission fingerprint, assignment, probe, cell, provider, model, effort, and ordinal. It is explicitly not an HMAC or substitute for future keyed custody.

Safety and scope

  • Provider calls: 0. New evaluation spend: $0.
  • No provider/API call, credential, grant, private key, nonce, raw prompt, raw response, or provider error body was created, stored, logged, or used.
  • The public trust-root registry and actual dispatch remain unprovisioned. They require a separate reviewed custody/transport/provisioning slice; raw outputs for later judging likewise require a separately reviewed encrypted-artifact slice.
  • The PR remains draft and is not ready for live use.

Validation

  • Sanitized dedicated corrected-contract tests: 8/8 passed.
  • Sanitized aggregate focused authority/runtime/authorization/ledger tests: 68/68 passed.
  • npm run typecheck, migration validation (3/3), and diff checks passed.
  • Fresh PostgreSQL 15 database: all 566 migrations through 582 applied; private-ledger migration integration: 34/34 passed.
  • The initial fresh-PostgreSQL attempt stopped at migration 156 because this VM lacked the pg_trgm contrib prerequisite. After installing that prerequisite, a recreated fresh database completed the clean migration/integration rerun.
  • The normal sanitized commit hook passed its preliminary phases but its full server-unit phase reached the repository fixed 600-second timeout. Root then authorized exactly one HUSKY=0 commit only for the unchanged two-file staged correction in commit dce6dce29b4d8933b8cdf908e37d90c121d29038; no other bypass was used.

No protocol release surface changed, so no changeset is required.

Related to #6842.


Open workspace in Conductor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant