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
- Generated structured artifact inventory: draft `.bitcode/v35-spec-family-report.json`, draft `.bitcode/v35-canonical-input-report.json`, future source-safe V35 telemetry/documentation artifacts, and `BITCODE_SPEC_V35_PROVEN.md` only after V35 promotion
10
+
- Generated structured artifact inventory: draft `.bitcode/v35-spec-family-report.json`, draft `.bitcode/v35-canonical-input-report.json`, source-safe `.bitcode/v35-documentation-surface-catalog.json`, future source-safe V35 telemetry/documentation artifacts, and `BITCODE_SPEC_V35_PROVEN.md` only after V35 promotion
11
11
- Source parity state: V35 source parity opens with Gate 1 and will close telemetry taxonomy, documentation surface, dashboard/runbook, documentation QA, onboarding, integration, rehearsal, and promotion-readiness gates before canonical promotion
12
12
- Active canonical pointer during draft opening: `BITCODE_SPEC.txt` -> `V34`
13
13
- Notes companion: `BITCODE_SPEC_V35_NOTES.md`
@@ -212,6 +212,28 @@ V35 closes through ten gates:
212
212
9.**Gate 9: Local Staging Telemetry Documentation Rehearsal** rehearses local and staging-testnet telemetry/docs visibility, dashboard/runbook paths, docs QA, and source-safe proof roots.
Gate 2 materializes `DocumentationSurfaceCatalog` as package-owned protocol truth.
218
+
The deterministic artifact `.bitcode/v35-documentation-surface-catalog.json` carries `source-safe-documentation-surface-metadata` and proves twelve required documentation surface rows:
219
+
220
+
-`canonical_spec_family`
221
+
-`roadmap_contributor_governance`
222
+
-`internal_codebase_docs`
223
+
-`public_docs_surface`
224
+
-`package_readmes`
225
+
-`route_api_docs`
226
+
-`api_interface_docs`
227
+
-`generated_artifact_docs`
228
+
-`deployment_operations_docs`
229
+
-`telemetry_observability_docs`
230
+
-`demonstration_docs`
231
+
-`security_boundary_docs`
232
+
233
+
Every row names audience, owner, disclosure class, source roots, linked spec sections, linked generated artifacts, route or package bindings, proof coverage, forbidden content, freshness checks, and deterministic row root.
234
+
The catalog fails closed on missing source roots, stale source roots, `_legacy/` source roots, secret-shaped values, unsupported public disclosure, protected source, wallet private material, provider tokens, raw protected prompts, and unpaid AssetPack source.
235
+
The artifact is generated by `pnpm run generate:v35-documentation-surface-catalog`, checked by `pnpm run check:v35-documentation-surface-catalog`, closed by `pnpm run check:v35-gate2`, and exported by `@bitcode/protocol` through `buildDocumentationSurfaceCatalog`.
236
+
215
237
## V35 whole Bitcode operator chain
216
238
217
239
The V35 operator chain keeps V34 behavior and adds source-safe documentation and telemetry visibility:
- Scope: V35 draft notes for telemetry and documentation depth over promoted V34 deployment canon
13
13
- Last fully realized canonical target preserved in source: `V34`
@@ -56,6 +56,7 @@ Read the system as:
56
56
-`OperatorRunbookCatalog` binds dashboards, alerts, incidents, escalation, repair commands, and post-incident documentation updates to telemetry taxonomy rows.
57
57
-`TestnetRolloutReadinessGuide` carries contributor, operator, enterprise reader, depositor, and interface consumer paths for local and staging-testnet use.
58
58
- V35 public docs can expose measurements, proof posture, fee/right boundaries, setup steps, and known blockers; they cannot expose secrets, wallet private material, protected source, raw prompts containing protected data, or unpaid AssetPack source.
59
+
- Gate 2 closes `DocumentationSurfaceCatalog` with `.bitcode/v35-documentation-surface-catalog.json`, `source-safe-documentation-surface-metadata`, package export `buildDocumentationSurfaceCatalog`, package test coverage, and `check:v35-gate2`.
@@ -54,7 +54,7 @@ No `_legacy/` source is active source truth.
54
54
| --- | --- | --- | --- | --- |
55
55
| Draft family and branch posture | Gate 1 |`BITCODE_SPEC_V35.md`, DELTA, NOTES, PARITY, `BITCODE_SPEC.txt`, branch `v35/gate-1-telemetry-docs-roadmap-opening`| drafted | V35 family validates in draft mode over active V34 and `check:v35-gate1` passes. |
56
56
| Roadmap truth | Gate 1 |`SPECIFICATIONS_ROADMAP.md`, README, PR template, workflow posture | drafted | Roadmap states V34 active, V35 draft, and coherent V36-V37 responsibilities. |
57
-
| Documentation surface catalog | Gate 2 |`DocumentationSurfaceCatalog`, generated docs surface artifact, tests, and `check:v35-gate2`|drafted| Internal codebase docs, public `/docs`, package docs, route docs, generated artifact docs, API/interface docs, owners, freshness checks, and disclosure classes have package-owned rows. |
57
+
| Documentation surface catalog | Gate 2 |`DocumentationSurfaceCatalog`, `.bitcode/v35-documentation-surface-catalog.json`, `packages/protocol/src/canonical/documentation-surface-catalog.js`, `packages/protocol/test/v35-documentation-surface-catalog.test.js`, and `check:v35-gate2`|closed| Internal codebase docs, public `/docs`, package docs, route docs, generated artifact docs, API/interface docs, owners, freshness checks, and disclosure classes have package-owned rows. |
- Recent V34 closure anchor: V34 Gate 10 Promotion Readiness generated V34 proof support, promoted `BITCODE_SPEC.txt` to `V34`, prepared V34 active / V35 draft runtime posture, and closed deployment-depth canon.
11
11
- V34 Gate 2 closure anchor: deployment-depth now owns package-backed `DeploymentHostCapabilityCatalog` and `EnvironmentLaneContract` source, deterministic `.bitcode/v34-deployment-host-capability-catalog.json` and `.bitcode/v34-environment-lane-contracts.json`, and visible `value-bearing-mainnet` blocking through `blocked_future_canon_required`.
@@ -18,6 +18,7 @@
18
18
- V34 Gate 9 closure anchor: deployment-depth now owns package-backed `DeploymentReadinessRehearsal` source, deterministic `.bitcode/v34-local-staging-testnet-deployment-rehearsal.json`, local full-stack deployment rehearsal, staging-testnet full-stack deployment rehearsal, value-bearing mainnet blocked rehearsal, Terminal, public API, MCP API, ChatGPT App, Reading pipeline execution receipts, settlement/finality simulation, storage posture, repair posture, source-safe logs, proof-rooted screenshots or logs, validation commands, proof roots, and no secret values serialization coverage.
19
19
- V34 Gate 10 closure anchor: deployment-depth now owns package-backed `DeploymentPromotionReadinessReport` source, deterministic `.bitcode/v34-promotion-readiness-report.json`, V34 promotion command planning, generated appendix support through `BITCODE_SPEC_V34_PROVEN.md`, V34 canon promotion workflow support, gate/canon workflow postures, source-safe deployment artifact evidence, direct-main push denial, and active V34 / draft V35 post-promotion readiness.
20
20
- V35 Gate 1 opening anchor: telemetry/documentation depth opens over promoted V34 with V35 SPEC, DELTA, NOTES, and PARITY files, `check:v35-gate1`, V34 active / V35 draft posture, and a ten-gate plan for documentation surfaces, telemetry taxonomy, public docs, dashboards/runbooks/incidents, documentation QA, onboarding/testnet guides, interface integration, rehearsal, and promotion readiness.
Copy file name to clipboardExpand all lines: internal-docs/README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
# Bitcode Internal Notes
2
2
3
-
Status: non-canonical scratch documentation. The active canonical system specification is `BITCODE_SPEC_V27.md`; these notes are useful only insofar as they help draft, implement, or verify the active SPEC family or the explicitly opened draft-target family.
3
+
Status: non-canonical internal documentation. The active canonical system specification pointer is `BITCODE_SPEC.txt` -> `V34`; V35 is the active draft-target family for telemetry and documentation depth. These notes are useful only insofar as they help draft, implement, or verify the active SPEC family or the explicitly opened draft-target family.
4
4
5
5
## Rules
6
6
7
7
- Do not treat this directory as canonical truth.
8
8
- Promote requirements into the active SPEC/PARITY/proof family, or into the explicitly opened draft-target SPEC family, before relying on them as requirements.
9
+
- Keep internal docs registered through `DocumentationSurfaceCatalog` when they become gate, operator, route, package, or proof dependencies.
0 commit comments