You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V31.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -243,6 +243,9 @@ Gate 4 Connects precision:
243
243
- Provider readiness records name provider id, installation/account state, token presence class, scopes class, last readback status, blocker, and repair action.
244
244
- Secrets and raw provider tokens are never stored in telemetry, UI metadata, or proof hooks.
245
245
- Recovery attempts produce before/after readiness roots and never silently downgrade provider policy.
246
+
-`AuxillariesConnectionReadiness` is the canonical provider-readiness object for Connects and VCS routes. It carries `providerId`, `providerName`, `credentialPosture`, `tokenPresenceClass`, `scopesClass`, `lastReadbackStatus`, `blocker`, `repairAction`, source-safe metadata, and `providerReadinessRoot`.
247
+
- Provider connection routes may store or validate private provider credentials at the route boundary, but responses, telemetry, proof hooks, and UI metadata can only expose classified token/scope/readback posture and source-safe account labels.
248
+
-`AuxillariesRecoveryRun` records provider recovery as before-readiness root, after-readiness root, repair action, execution id, outcome, and source-safety class; it never serializes the provider credential that made the repair possible.
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V31_DELTA.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,6 +127,13 @@ Closure acceptance:
127
127
- GitHub and provider connection routes emit source-safe readiness/recovery evidence;
128
128
- recovery runs record before/after readiness roots and never leak tokens.
129
129
130
+
Gate 4 implementation centers:
131
+
132
+
-`AuxillariesConnectionReadiness` now names provider id/name, token presence class, scopes class, readback state, blocker, repair action, source-safe metadata, and `providerReadinessRoot`.
133
+
- VCS connection and GitHub Auxillaries routes emit `providerReadiness` and source-safe `recoveryRun` evidence while keeping access tokens out of responses.
134
+
- The Externals pane consumes `connectionReadiness` and `recoveryRuns` from `/api/auxillaries/data`, rendering classified provider posture and compact proof roots without local readiness rederivation.
135
+
- Focused package, route, and pane tests prove classified provider readiness, before/after recovery roots, UI projection, and response redaction.
136
+
130
137
### Gate 5: Wallet And BTD Pane Readiness
131
138
132
139
Gate 5 connects Wallet and BTD panes to V30 wallet/BTD primitives.
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V31_NOTES.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,3 +87,10 @@ Gate 3 is closed only when Profile/account state is not just a form payload.
87
87
It must be a package-owned support state that binds account identity, profile completeness issues, repair routes, wallet binding posture, model/template preference posture, notification posture, data-sharing posture, and proof roots.
88
88
The Profile pane may present and link repairs, but it must consume the package contract and must not locally rederive account readiness or completeness law.
89
89
Route hydration must include template preference and notification readback where available, while missing storage rows degrade into explicit repair posture rather than generic missing data.
90
+
91
+
## Gate 4 closure note
92
+
93
+
Gate 4 is closed only when Connects provider state is a source-safe readiness contract rather than a raw OAuth/VCS status blob.
94
+
Provider readiness must name provider id/name, installation state, credential posture, token presence class, scopes class, last readback status, blocker, repair action, and proof root without exposing raw provider credentials.
95
+
VCS and GitHub Auxillaries routes may use credentials internally to validate or repair a connection, but responses, UI metadata, telemetry, and recovery proof hooks must carry only classified posture and before/after readiness roots.
96
+
The Externals pane can display compact provider proof detail, but it must consume `connectionReadiness` and `recoveryRuns` from the package-owned Auxillaries contract instead of locally deciding provider law.
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V31_PARITY_MATRIX.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,9 +113,9 @@ No `_legacy/` source is active source truth.
113
113
114
114
| Requirement | Source evidence | Current V31 judgment |
115
115
| --- | --- | --- |
116
-
| Provider readiness is source-safe | provider connection contracts and tests|pending|
117
-
| Recovery runs record before/after readiness roots |recovery route and execution tests| pending|
118
-
| Tokens and credentials never enter telemetry/UI metadata |source-safety testsand scans | pending|
116
+
| Provider readiness is source-safe |`AuxillariesConnectionReadiness` in `packages/api/src/routes/auxillaries-contract.ts` carries provider id/name, token presence class, scopes class, last readback, blocker, repair action, source-safe metadata, and `providerReadinessRoot`|drafted|
117
+
| Recovery runs record before/after readiness roots |`uapi/app/api/vcs/[provider]/connection/route.ts`, `uapi/app/api/auxillaries/connections/github/route.ts`, and `uapi/tests/api/auxillariesGithubConnectionRoute.test.ts` emit and test before/after readiness roots | drafted|
118
+
| Tokens and credentials never enter telemetry/UI metadata |`packages/api/src/routes/__tests__/auxillaries-contract.test.ts`, `uapi/tests/api/vcsRoutes.test.ts`, `uapi/tests/api/auxillariesGithubConnectionRoute.test.ts`, and `uapi/tests/auxillariesExternalsPane.test.tsx` cover response/UI redaction and source-safe projection | drafted|
Copy file name to clipboardExpand all lines: SPECIFICATIONS_ROADMAP.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
- Current active canonical pointer: `BITCODE_SPEC.txt` -> `V30`
6
6
- Current active canon: `BITCODE_SPEC_V30.md`
7
7
- Current draft target: `BITCODE_SPEC_V31.md`
8
-
- Current working gate: V31 Gate 3 Profile and account state, which deepens the package-owned Auxillaries Profile contract with account identity, wallet binding posture, model/template preferences, notifications, data-sharing posture, explicit blockers, and repair routes over the V30 Protocol/BTD substrate.
8
+
- Current working gate: V31 Gate 4 Connects provider readiness and recovery, which deepens source-safe provider connection posture with provider id/name, installation state, token presence class, scopes class, last readback status, blocker, repair action, readiness roots, and before/after recovery evidence over the V30 Protocol/BTD substrate.
9
9
- Purpose: concise running index of Bitcode/ENGI specification history, current work, and planned work.
10
10
11
11
This roadmap is not an active system specification.
0 commit comments