Configure Auxillaries for wallet, externals, profile, and interfaces

Auxillaries hold wallet, externals, profile, and interface readiness

Auxillaries is the configuration shell beside the product routes: Bitcoin wallet identity, GitHub and future source providers, optional profile metadata, interface defaults, and BTD posture.

Opening Auxillaries should feel adjacent to Packs, Deposit, and Read — not a separate product. It changes readiness and defaults while activity you selected on a product route remains recoverable. Connect Wallet is the guest entry; after identity is bound, Auxillaries opens from signed-in chrome.

• Wallet is the first identity step: a Bitcoin wallet proof that can back a session and fee readiness.
• Externals owns GitHub App install and repository scope after wallet identity exists.
• Profile owns optional email, display identity, roles, and organization metadata.
• Interfaces owns defaults for how product detail, conversations, and proofs open.
• Wallet also surfaces BTD balances and related share posture without inventing a second ledger.

Wallet, Externals, Profile, and Interfaces are readiness surfaces

Wallet identity, repository scope, profile roles, interface defaults, and BTD controls determine which writes can leave review and enter signed or connected execution.

You can still learn the product with incomplete readiness, but live deposit, read settlement, and delivery must keep blockers visible. Production execution fails closed until required wallet and source posture is complete.

1. 01Connect and sign with a Bitcoin wallet first (testnet lane for commercial testnet).
2. 02Install the Bitcode GitHub App and authorize repositories second.
3. 03Add optional email and profile settings after wallet and source readiness are clear.
4. 04Set interface defaults for how Packs detail, conversations, and proofs open.
5. 05Review BTD and wallet-adjacent controls before settlement-sensitive work.

Externals is source-bearing ingress — not a buried account setting

Externals owns GitHub (and future providers) because repository scope becomes permitted source for measurement, AssetPack synthesis, proof follow-through, and settlement readiness.

A healthy connection read shows pending, connected, reconnect-required, or inventory-only posture. Wallet identity stays in Wallet; repository attachment and provider scope stay in Externals. Read-space knowledge sharing is a separate opt-in after repositories are approved.

• GitHub scope defines which repositories Bitcode may read as permitted source.
• Stored inventory can support reread; live write admission fails closed until the provider is healthy.
• Bitcoin wallet plus authorized GitHub repositories are the minimum live prerequisites for source-bearing work.

Interface defaults shape how product detail, chat, and proofs open

Interfaces owns detail density, conversation return behavior, proof read mode, and related product posture — not a second protocol.

These preferences change how much detail opens by default, how conversations re-enter the product, and whether proof readers see visual, mixed, or raw evidence first. Ledgerized Reading still keeps protocol-owned model configuration.

• Packs detail density controls how much selected activity detail opens by default.
• Conversation launch controls overlay vs focused continuity when chat re-enters.
• Proof mode controls visual, mixed, or raw-first evidence presentation.

Public docs expose guidance and proof posture, not protected source

Public Bitcode docs derive from the active Protocol, package-owned catalogs, route contracts, and source-safe generated artifacts. They can explain usage, measurements, event ids, proof roots, docs links, runbook links, redaction posture, testnet rollout readiness, fee boundaries, and settlement posture.

They must not reveal protected source payloads, raw protected prompts, secret values, provider tokens, wallet private material, or unpaid AssetPack source. Source-bearing AssetPack contents cross to the reader only after settlement and rights transfer.

• Allowed: usage guidance, route links, state labels, source-safe measurements, proof roots, dashboard/runbook ids, redacted incident posture, testnet rollout readiness, LocalStagingTelemetryDocumentationRehearsal evidence, and fee/right boundaries.
• Interface docs may surface event ids, proof roots, docs links, runbook links, and redaction posture from TelemetryDocumentationInterfaceIntegration without revealing source-bearing payloads.
• Local and staging-testnet rehearsal docs may surface documentation discovery, telemetry event emission, dashboard/runbook lookup, docs QA, incident drill, source-safe proof-root review, and blocked value-bearing mainnet posture.
• Blocked: secrets, provider tokens, wallet private material, raw protected prompts, protected source payloads, and unpaid AssetPack source.
• Docs QA fails closed when public docs, internal docs, route docs, interface docs, generated artifacts, proof posture, or workflow checks drift.
• Compatibility boundaries stay explicit: /exchange redirects to /packs and does not create a parallel current product surface.