@brik64/cli 0.1.0-beta.1 → 0.1.0-beta.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,97 @@
1
+ # GitHub Repository Governance
2
+
3
+ This repository is public so developers can inspect BRIK64 CLI beta releases,
4
+ read package metadata, download artifacts, and open issues.
5
+
6
+ It is not an external contribution repository.
7
+
8
+ ## Ownership
9
+
10
+ - Organization: `brik64`
11
+ - Repository: `brik64/brik64-cli`
12
+ - Maintainer team: `brik64/brik64-cli-maintainers`
13
+ - Initial maintainers: `brik64-admin`, `carlosjperez`
14
+
15
+ `CODEOWNERS` assigns the full repository to the maintainer team.
16
+
17
+ ## Public Interaction Policy
18
+
19
+ Allowed:
20
+
21
+ - Open issues.
22
+ - Report reproducible CLI beta bugs.
23
+ - Report docs, release, npm, checksum, or install metadata mismatches.
24
+ - Report security concerns through the security policy.
25
+
26
+ Not accepted:
27
+
28
+ - External pull requests.
29
+ - External direct commits.
30
+ - Public changes to release evidence, license text, package metadata, or docs
31
+ claim surfaces.
32
+
33
+ BRIK64 lands changes through authorized maintainers so release evidence,
34
+ package metadata, public claims, licenses, checksums, and docs stay aligned.
35
+
36
+ ## Required Repository Settings
37
+
38
+ Recommended public repo settings:
39
+
40
+ - Issues: enabled.
41
+ - Wiki: enabled.
42
+ - Projects: disabled unless used for public release tracking.
43
+ - Merge commit, squash merge, and rebase merge: disabled for public PR paths.
44
+ - Auto merge: disabled.
45
+ - Delete branch on merge: enabled.
46
+ - Web commit signoff: enabled.
47
+ - Homepage: `https://brik64.com`.
48
+ - Repository topics: `brik64`, `brik`, `cli`, `pcd`, `evidence`,
49
+ `software-trust`, `developer-tools`, `public-beta`, `macos`, `command-line`.
50
+
51
+ Recommended `main` branch protection:
52
+
53
+ - Restrict pushes to `brik64-cli-maintainers`.
54
+ - Require signed commits.
55
+ - Require linear history.
56
+ - Block force pushes.
57
+ - Block deletions.
58
+ - Require conversation resolution.
59
+
60
+ ## Security And Code Quality
61
+
62
+ Repository security should include:
63
+
64
+ - Secret scanning enabled.
65
+ - Secret scanning push protection enabled.
66
+ - Dependabot security updates enabled.
67
+ - Dependabot version update config for npm and GitHub Actions.
68
+ - CodeQL default setup for JavaScript analysis.
69
+ - CI smoke and package checks.
70
+
71
+ Dependabot PRs should be reviewed by `brik64-cli-maintainers` and merged only
72
+ after protected branch checks pass. Dependency update PRs are maintenance
73
+ signals, not release promotion evidence.
74
+
75
+ Do not add a custom CodeQL advanced workflow while GitHub CodeQL default setup is
76
+ enabled for this repository. GitHub rejects SARIF from advanced configuration
77
+ when default setup is active.
78
+
79
+ ## Docs And Mintlify Changelog
80
+
81
+ The publish workflow dispatches `brik64-cli-release` to
82
+ `brik64/brik64-docs-site` when `BRIK64_DOCS_REPO_DISPATCH_TOKEN` is configured.
83
+
84
+ Required secret:
85
+
86
+ ```text
87
+ BRIK64_DOCS_REPO_DISPATCH_TOKEN
88
+ ```
89
+
90
+ The token should be fine-grained and scoped to trigger repository dispatch or
91
+ workflow dispatch in `brik64/brik64-docs-site`. The receiving docs repository
92
+ should update `releases/changelog.mdx`, rebuild Mintlify output, and deploy docs.
93
+
94
+ The GitHub App installation token rollout announced in May 2026 means any app or
95
+ automation that creates installation tokens must treat `ghs_` tokens as opaque
96
+ and avoid fixed-length token assumptions. This repo's workflows do not parse
97
+ GitHub App installation tokens.
@@ -1,27 +1,31 @@
1
1
  # Linux Hetzner Testing
2
2
 
3
- Hetzner is the Linux test surface for the CLI beta.
3
+ Hetzner is the Linux validation surface for BRIK64 CLI beta packaging.
4
4
 
5
- Scope:
6
- - Debian x64 native artifact execution.
7
- - Ubuntu x64 native artifact execution.
8
- - Fedora x64 native artifact execution.
9
- - Alpine x64 musl only with a separate musl artifact or explicit unsupported
5
+ ## Scope
6
+
7
+ - Debian x64 package and install checks.
8
+ - Ubuntu x64 package and install checks.
9
+ - Fedora x64 package and install checks when that lane opens.
10
+ - Alpine x64 musl only with a musl-specific artifact or an explicit scope
10
11
  decision.
11
12
 
12
- Required evidence per supported distro:
13
+ ## Required Evidence Per Distro
14
+
13
15
  - distro identity (`/etc/os-release`);
14
16
  - architecture (`uname -m`);
15
17
  - native binary path;
16
- - no wrapper evidence;
17
18
  - `brik --version` output;
18
19
  - BRIK64 ASCII startup output;
19
20
  - command-contract smoke;
20
21
  - PCD/certify/emit workflow smoke;
21
22
  - behavior PASS report.
22
23
 
23
- Boundary:
24
- - No universal Linux claim.
25
- - No public release authorization.
26
- - No N5, fixpoint or release-readiness claim from a distro smoke alone.
27
- - Windows remains waiting for a real PC/runner.
24
+ ## Promotion Path
25
+
26
+ Each distro lane should publish its own artifact, checksum, install smoke, and
27
+ release manifest before it is promoted through GitHub Releases, curl/GCP, docs,
28
+ or brik64.com. Linux wording should name the validated distro lane instead of
29
+ collapsing all Linux distributions into one status.
30
+
31
+ Windows remains a separate validation lane with its own runner and install smoke.
@@ -6,19 +6,22 @@ Current local platform:
6
6
  - OS: macOS / Darwin
7
7
  - Architecture: arm64
8
8
 
9
- Scope:
10
- - local CLI execution;
11
- - local install path checks;
12
- - local command-contract checks;
13
- - no public release authorization.
14
-
15
- Out of scope:
16
- - macOS x64 runner evidence;
17
- - Windows evidence;
18
- - universal macOS artifact claims;
19
- - fixpoint, N5 or release claims.
20
-
21
- Required evidence before marking macOS local ready:
9
+ ## Scope
10
+
11
+ - Local CLI execution.
12
+ - Local install path checks.
13
+ - Local command-contract checks.
14
+ - Apple Silicon package smoke for the current beta lane.
15
+
16
+ ## Evidence Still Needed For Broader Promotion
17
+
18
+ - macOS Intel runner or host evidence.
19
+ - Windows evidence.
20
+ - Per-artifact checksum and release manifest binding.
21
+ - Release authorization from the active BRIK64 evidence process.
22
+
23
+ ## Required Evidence Before Marking macOS Local Ready
24
+
22
25
  - local binary path;
23
26
  - `brik --version` output;
24
27
  - BRIK64 ASCII startup output;
@@ -2,11 +2,16 @@
2
2
 
3
3
  | Platform | Status | Required Evidence |
4
4
  | --- | --- | --- |
5
- | macOS arm64 local | pending | local binary execution report |
6
- | Linux Debian x64 | pending | native binary, no wrapper, behavior PASS |
7
- | Linux Ubuntu x64 | pending | native binary, no wrapper, behavior PASS |
8
- | Linux Fedora x64 | pending | native binary, no wrapper, behavior PASS |
9
- | Linux Alpine x64 musl | pending | separate musl artifact or explicit unsupported decision |
10
- | Windows x64 | waiting | real PC/runner metadata and execution report |
5
+ | macOS Apple Silicon | current beta lane | package smoke, checksum, release manifest |
6
+ | macOS Intel | planned | Intel host or runner install smoke, checksum, release manifest |
7
+ | Debian Linux x64 | planned | Debian package/install smoke, checksum, release manifest |
8
+ | Ubuntu Linux x64 | planned | Ubuntu package/install smoke, checksum, release manifest |
9
+ | Fedora Linux x64 | future lane | Fedora package/install smoke or explicit scope decision |
10
+ | Alpine Linux x64 musl | future lane | musl-specific artifact or explicit scope decision |
11
+ | Windows x64 | planned | Windows runner smoke, checksum, release manifest |
11
12
 
12
- Do not collapse these into "all Linux" or "all platforms" claims.
13
+ ## Public Wording Rule
14
+
15
+ Describe each platform only at the evidence level it has reached. Linux package
16
+ language should name the distro lane, and macOS language should distinguish
17
+ Apple Silicon from Intel until both lanes have passed their own checks.
@@ -8,11 +8,11 @@ and aligned with BRIK64 evidence boundaries.
8
8
  ## Authority
9
9
 
10
10
  - Product surface: BRIK64 CLI.
11
- - Current public beta: `0.1.0-beta.1`.
12
- - Public web surface: https://brik64.com/home-cli
11
+ - Current public beta: `0.1.0-beta.3`.
12
+ - Public web surface: https://brik64.com
13
13
  - Docs: https://docs.brik64.com/cli/install
14
14
  - Package: https://www.npmjs.com/package/@brik64/cli
15
- - Release: https://github.com/brik64/brik64-cli/releases/tag/v0.1.0-beta.1
15
+ - Release: https://github.com/brik64/brik64-cli/releases/tag/v0.1.0-beta.3
16
16
  - Evidence authority: `brik64-prod` gates, manifests, checksums, and release
17
17
  reports.
18
18
  - Implementation surface: `brik64-cli` source, package metadata, tests, PCD seed
@@ -160,7 +160,7 @@ brik --version
160
160
  brik help
161
161
  ```
162
162
 
163
- Public web surface: https://brik64.com/home-cli
163
+ Public web surface: https://brik64.com
164
164
 
165
165
  Docs: https://docs.brik64.com/cli/install
166
166
 
@@ -296,3 +296,63 @@ Copyright (c) 2026 BRIK64 INC. All rights reserved.
296
296
 
297
297
  Use this footer in package README, release notes, NOTICE, docs cards, and public
298
298
  repo descriptions where space allows.
299
+
300
+
301
+ ## License Standard
302
+
303
+ BRIK64 CLI public beta releases use the `BRIK64 CLI Public Beta Evaluation License`.
304
+ This is proprietary evaluation software from BRIK64 INC. Public package metadata
305
+ should use:
306
+
307
+ ```json
308
+ "license": "SEE LICENSE IN LICENSE"
309
+ ```
310
+
311
+ Every beta package should include:
312
+
313
+ - `LICENSE` with the full BRIK64 CLI Public Beta Evaluation License;
314
+ - `NOTICE` with copyright, public links, and beta licensing summary;
315
+ - README copyright section pointing to both files;
316
+ - package metadata with `author.name` set to `BRIK64 INC`.
317
+
318
+ Use positive scope language for maturity and support boundaries. Commercial,
319
+ hosted, redistribution, partner, enterprise, regulated, or certification-oriented
320
+ use should route to written commercial terms from BRIK64 INC.
321
+
322
+
323
+ ## ASCII Banner Standard
324
+
325
+ Use this provisional ASCII banner in CLI README and release surfaces until the
326
+ final cross-repo visual identity asset is ready:
327
+
328
+ ```text
329
+ ╔══════════════════════════════════════════════════════╗
330
+ ║ ║
331
+ ║ ██████╗ ██████╗ ██╗██╗ ██╗ ██████╗ ██╗ ██╗ ║
332
+ ║ ██╔══██╗██╔══██╗ ██║██║ ██╔╝██╔════╝ ██║ ██║ ║
333
+ ║ ██████╔╝██████╔╝ ██║█████╔╝ ███████╗ ███████║ ║
334
+ ║ ██╔══██╗██╔══██╗ ██║██╔═██╗ ██╔═══██╗╚════██║ ║
335
+ ║ ██████╔╝██║ ██║ ██║██║ ██╗╚██████╔╝ ██║ ║
336
+ ║ ╚═════╝ ╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═════╝ ╚═╝ ║
337
+ ║ ║
338
+ ║ BRIK64 SYSTEM BOOT ║
339
+ ║ SOFTWARE LOGIC COMPILER ║
340
+ ║ MAKE SOFTWARE REVIEWABLE AGAIN ║
341
+ ║ ║
342
+ ╚══════════════════════════════════════════════════════╝
343
+ ```
344
+
345
+ For beta copy, keep the claim-safe scope paragraph directly after the banner so
346
+ the visual language stays anchored to current release evidence.
347
+
348
+ ## Release Asset Matrix Wording
349
+
350
+ Use this wording for current and future platform packages:
351
+
352
+ ```text
353
+ Current beta asset: macOS Apple Silicon package.
354
+ Planned release lanes: macOS Intel, Debian/Ubuntu Linux packages, and Windows PC packages after platform-specific build and smoke gates pass.
355
+ ```
356
+
357
+ Avoid presenting planned platform lanes as current support until the matching
358
+ artifact, checksum, install smoke, and release gate exist.
@@ -0,0 +1,100 @@
1
+ # BRIK64 CLI Repository Map
2
+
3
+ This map describes the public files and folders in `brik64/brik64-cli`.
4
+ It is intended for package reviewers, beta users, security reporters, and
5
+ maintainers who need to understand what each path is for.
6
+
7
+ ## Root Files
8
+
9
+ | Path | Description |
10
+ | --- | --- |
11
+ | `README.md` | Primary public entry point for BRIK64 CLI install instructions, beta scope, official channels, repository map, release assets, and license summary. |
12
+ | `package.json` | npm package manifest for `@brik64/cli`, including package version, description, binary mapping, scripts, keywords, publish config, and package file allowlist. |
13
+ | `LICENSE` | Proprietary beta license for BRIK64 CLI. The package is public for evaluation and inspection, not open source redistribution. |
14
+ | `NOTICE` | Copyright notice and third-party notice surface for the public beta package. |
15
+ | `SECURITY.md` | Security reporting policy, supported beta version scope, and private reporting route. |
16
+ | `CONTRIBUTING.md` | Public interaction policy. Issues are accepted for reproducible beta bugs and metadata mismatches; external pull requests are not accepted. |
17
+ | `.gitignore` | Local Git ignore rules for generated files, dependency directories, package outputs, logs, and temporary artifacts. |
18
+ | `.npmignore` | npm packaging exclusions for repository-only files that should not ship in the published package. |
19
+
20
+ ## Executable CLI
21
+
22
+ | Path | Description |
23
+ | --- | --- |
24
+ | `src/` | Executable CLI source directory for the current beta. |
25
+ | `src/brik.js` | Node.js command entry point exposed as `brik` by npm. It implements the current public beta command behavior. |
26
+
27
+ ## Tests
28
+
29
+ | Path | Description |
30
+ | --- | --- |
31
+ | `tests/` | Local test directory for current beta smoke checks. |
32
+ | `tests/smoke.sh` | Shell smoke test covering basic CLI execution, help/version output, project initialization behavior, `AGENTS.md` non-mutation policy, certify/emit behavior, target generation, and fail-closed unsupported targets. |
33
+
34
+ ## PCD Seed Material
35
+
36
+ | Path | Description |
37
+ | --- | --- |
38
+ | `pcd/` | Candidate PCD seed material for moving CLI behavior toward a PCD-first BRIK64 methodology. These files are review material, not release certificates. |
39
+ | `pcd/README.md` | Folder-level explanation of current PCD seed role, promotion path, and authority boundary. |
40
+ | `pcd/cli_core.pcd` | Candidate command contract seed for core CLI behavior. |
41
+ | `pcd/cli_init_policy.pcd` | Candidate command contract seed for initialization and agent-file consent policy. |
42
+ | `pcd/cli_certify_emit.pcd` | Candidate command contract seed for bounded certification-output behavior. |
43
+ | `pcd/cli_polymer.pcd` | Candidate composition contract that binds the CLI command PCD seeds before a future compile route. |
44
+
45
+ ## Evidence And Packaging
46
+
47
+ | Path | Description |
48
+ | --- | --- |
49
+ | `evidence/` | Public beta evidence area for package inspection and generated-review material. |
50
+ | `evidence/pcd-seed/` | Generated PCD seed review material used to keep methodology work inspectable without presenting it as certification. |
51
+ | `evidence/pcd-seed/README.md` | Explanation of how seed evidence should be read and what must happen before stronger release language is allowed. |
52
+ | `packaging/` | Packaging notes and release-lane material for platform-specific package work. |
53
+ | `packaging/macos-local/` | macOS local package review material for the current beta lane. |
54
+ | `packaging/macos-local/README.md` | macOS local packaging scope, package review expectations, and promotion requirements. |
55
+
56
+ ## Documentation
57
+
58
+ | Path | Description |
59
+ | --- | --- |
60
+ | `docs/REPOSITORY_MAP.md` | This file-by-file public repository map. |
61
+ | `docs/BRIK_METHODOLOGY_TRANSITION.md` | Methodology transition plan for moving the CLI from executable beta source toward PCD-first implementation and evidence-backed promotion. |
62
+ | `docs/DISTRIBUTION_ROADMAP.md` | Distribution roadmap for npm, GitHub Releases, GitHub Packages, curl/GCP, Homebrew, macOS Intel, Linux, and Windows lanes. |
63
+ | `docs/GITHUB_NPM_PUBLISHING.md` | npm publishing workflow notes for the public beta package. |
64
+ | `docs/GITHUB_PACKAGES_PUBLISHING.md` | GitHub Packages mirror workflow notes and verification boundary. |
65
+ | `docs/GITHUB_REPO_GOVERNANCE.md` | Repository governance policy for branch protection, maintainer ownership, issue flow, package publication, and public interaction controls. |
66
+ | `docs/LINUX_HETZNER_TESTING.md` | Linux test plan and operator guidance for Debian/Ubuntu lanes using remote execution infrastructure. |
67
+ | `docs/MACOS_LOCAL_TESTING.md` | macOS local test plan and operator guidance for current Apple Silicon package validation. |
68
+ | `docs/PLATFORM_MATRIX.md` | Platform support matrix for current beta support and planned release lanes. |
69
+ | `docs/RELEASE_COPY_MANUAL.md` | Standardized release-copy guide for npm, GitHub Releases, package descriptions, changelog entries, and public keywords. |
70
+ | `docs/REPO_BOUNDARY.md` | Public repository boundary: what this repo owns, what `brik64-prod` owns, and what must not be claimed from this repo alone. |
71
+ | `docs/WIKI_HOME.md` | Versioned wiki-home content while GitHub Wiki remote access remains under operational review. |
72
+
73
+ ## GitHub Governance
74
+
75
+ | Path | Description |
76
+ | --- | --- |
77
+ | `.github/CODEOWNERS` | Maintainer ownership rules for protected files and review-required changes. |
78
+ | `.github/PULL_REQUEST_TEMPLATE.md` | Internal maintainer checklist for protected changes, claim-safety review, package impact, and evidence updates. |
79
+ | `.github/dependabot.yml` | Dependabot grouping and review configuration for GitHub Actions and npm ecosystem updates. |
80
+ | `.github/ISSUE_TEMPLATE/` | Public issue templates for beta bugs, docs/package metadata mismatches, and security-report routing. |
81
+ | `.github/workflows/ci.yml` | Main CI workflow for smoke tests and package-content checks. |
82
+ | `.github/workflows/codeql.yml` | CodeQL workflow configuration where custom analysis is needed. |
83
+ | `.github/workflows/publish-npm-beta.yml` | Manual npm beta publication workflow for authorized maintainers. |
84
+ | `.github/workflows/publish-github-packages-beta.yml` | Manual GitHub Packages beta mirror workflow for authorized maintainers. |
85
+
86
+ ## BRIK64 Traceability
87
+
88
+ | Path | Description |
89
+ | --- | --- |
90
+ | `.brik/` | BRIK64 local project metadata directory. |
91
+ | `.brik/manifest.json` | Local traceability manifest for the CLI repo. It is operational metadata and is not a formal certificate. |
92
+
93
+ ## Authority Boundary
94
+
95
+ This repository owns the public CLI package surface, local beta source, package
96
+ metadata, package smoke checks, public repo governance, and beta documentation.
97
+
98
+ `brik64-prod` remains the authority for release gates, certificate boundaries,
99
+ compiler evidence, promotion decisions, and any stronger public claim
100
+ authorization.
@@ -2,29 +2,28 @@
2
2
 
3
3
  ## Lives Here
4
4
 
5
- - CLI source code.
6
- - CLI tests and fixtures.
7
- - Platform packaging scripts.
8
- - Local beta artifacts.
9
- - Per-version changelogs.
5
+ - Public beta CLI source code.
6
+ - CLI smoke tests and fixtures.
7
+ - Platform packaging scripts and wrappers.
8
+ - Local beta artifacts and package metadata.
9
+ - Per-version release notes, runbooks, and distribution docs.
10
10
 
11
- ## Does Not Live Here
11
+ ## Authority Boundary
12
12
 
13
- - Private engines.
14
- - Claim-bearing certification authority.
15
- - Public release authorization.
16
- - N-level claims.
17
- - Prod evidence source of truth.
13
+ - `brik64-cli` owns implementation, public package metadata, distribution
14
+ workflows, issue templates, and release-surface documentation for the CLI beta.
15
+ - `brik64-prod` owns methodology gates, evidence authority, release decision,
16
+ compiler evidence, certificate boundaries, and public claim authorization.
18
17
 
19
- ## Authority Split
18
+ ## Public Surface Rule
20
19
 
21
- - `brik64-cli`: implementation and packaging iteration.
22
- - `brik64-prod`: gates, evidence, methodology, release decision and claim
23
- boundary.
20
+ The public repository should help developers inspect, install, and report on the
21
+ CLI beta without exposing private engines, internal gates, private evidence
22
+ stores, raw credentials, or unsupported certification language.
24
23
 
25
24
  ## Platform Scope
26
25
 
27
26
  - macOS local testing can run on the current development machine.
28
27
  - Linux testing should run on the Hetzner runner and must be split by distro
29
- family rather than claimed as universal Linux support.
28
+ family.
30
29
  - Windows testing remains pending until a real Windows PC/runner is available.
@@ -0,0 +1,50 @@
1
+ # BRIK64 CLI Public Beta
2
+
3
+ BRIK64 CLI is the public beta command-line surface for local BRIK64 project
4
+ workflows, PCD-oriented structure, bounded evidence review, and claim-safe
5
+ project scaffolding.
6
+
7
+ ## Official Links
8
+
9
+ - Website: https://brik64.com
10
+ - Docs: https://docs.brik64.com
11
+ - npm: https://www.npmjs.com/package/@brik64/cli
12
+ - GitHub release: https://github.com/brik64/brik64-cli/releases
13
+
14
+ ## Public Interaction
15
+
16
+ This repository is public for inspection, installation, issue reporting, release
17
+ review, and package transparency.
18
+
19
+ Allowed:
20
+
21
+ - Open issues for reproducible CLI beta bugs.
22
+ - Open issues for docs, npm, release, checksum, or install metadata mismatches.
23
+ - Report security concerns using the repository security policy.
24
+
25
+ Not accepted:
26
+
27
+ - External pull requests.
28
+ - External direct commits.
29
+ - Public edits to release evidence, license text, package metadata, or public
30
+ claim surfaces.
31
+
32
+ BRIK64 lands changes through authorized maintainers.
33
+
34
+ ## Current Beta
35
+
36
+ Current beta: `0.1.0-beta.3`
37
+
38
+ Install:
39
+
40
+ ```sh
41
+ npm install -g @brik64/cli@beta
42
+ brik --version
43
+ brik help
44
+ ```
45
+
46
+ ## Evidence Boundary
47
+
48
+ `brik64-prod` remains the authority for methodology, release gates, evidence
49
+ contracts, certification boundaries, compiler claim authorization, and release
50
+ approval.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": "brik64.cli_local_candidate_certificate.v1",
3
- "generatedAt": "2026-06-03T05:06:50Z",
3
+ "generatedAt": "2026-06-03T20:12:17Z",
4
4
  "pcd": {
5
5
  "path": "pcd/cli_certify_emit.pcd",
6
6
  "sha256": "1d73245ebee8592a4eeacdb4b99398baf7c5ddfa3c88c5927f924a871eee7147"
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schemaVersion": "brik64.cli_local_candidate_certificate.v1",
3
- "generatedAt": "2026-06-03T05:06:50Z",
3
+ "generatedAt": "2026-06-03T20:12:17Z",
4
4
  "pcd": {
5
5
  "path": "pcd/cli_core.pcd",
6
- "sha256": "c1d3167109d842c5b321ed541604bdcff2c7be7865b2aac8116f1db03b557944"
6
+ "sha256": "a2337d9d359061d5c655320ad5fb64c2acbea0ed077840bc61c049dbf387419e"
7
7
  },
8
8
  "certificate": {
9
9
  "kind": "local_candidate_certificate",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": "brik64.cli_local_candidate_certificate.v1",
3
- "generatedAt": "2026-06-03T05:06:50Z",
3
+ "generatedAt": "2026-06-03T20:12:17Z",
4
4
  "pcd": {
5
5
  "path": "pcd/cli_init_policy.pcd",
6
6
  "sha256": "fae8cf2f18ba00b337236a46ee7d212b1437c7b4eae812ca1e3506651ffdb31d"
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schemaVersion": "brik64.cli_local_candidate_certificate.v1",
3
- "generatedAt": "2026-06-03T05:06:50Z",
3
+ "generatedAt": "2026-06-03T20:12:17Z",
4
4
  "pcd": {
5
5
  "path": "pcd/cli_polymer.pcd",
6
- "sha256": "776bbd5a15357bf47350a81011f1d12bdf4a04fb843cd035c39f9b3985cb9196"
6
+ "sha256": "db285a12918a9fe4d50f80054e66d240d71d4ff0dd3031e495201a7dee936f71"
7
7
  },
8
8
  "certificate": {
9
9
  "kind": "local_candidate_certificate",
@@ -1,7 +1,18 @@
1
- # PCD Seed Evidence Boundary
1
+ # PCD Seed Evidence
2
2
 
3
- This directory is reserved for future reports generated from the candidate PCD
4
- source in `pcd/`.
3
+ This directory is reserved for reports generated from the candidate PCD source
4
+ in `pcd/`.
5
5
 
6
- No report in this directory currently authorizes a public beta, fixpoint claim,
7
- N5 claim, formal certification claim, or Rust-independence claim.
6
+ ## Current Role
7
+
8
+ - Holds future evidence generated from PCD seed review.
9
+ - Keeps PCD methodology evidence separate from executable CLI source.
10
+ - Provides a stable location for future gate outputs, manifests, and review
11
+ notes tied to the PCD seed material.
12
+
13
+ ## Evidence Boundary
14
+
15
+ Public beta install and package metadata are supported by the release artifacts
16
+ and workflows documented in this repository. Stronger compiler, fixpoint,
17
+ platform, or certification language belongs to fresh evidence from the relevant
18
+ BRIK64 gates before it is promoted publicly.
package/package.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "name": "@brik64/cli",
3
- "version": "0.1.0-beta.1",
3
+ "version": "0.1.0-beta.3",
4
4
  "private": false,
5
5
  "description": "BRIK64 CLI public beta for local PCD workflows, bounded evidence review, and claim-safe project scaffolding.",
6
- "homepage": "https://brik64.com/home-cli",
6
+ "homepage": "https://brik64.com",
7
7
  "repository": {
8
8
  "type": "git",
9
9
  "url": "git+https://github.com/brik64/brik64-cli.git"
@@ -49,6 +49,8 @@
49
49
  "README.md",
50
50
  "LICENSE",
51
51
  "NOTICE",
52
+ "SECURITY.md",
53
+ "CONTRIBUTING.md",
52
54
  ".brik/manifest.json"
53
55
  ]
54
56
  }
@@ -1,15 +1,22 @@
1
1
  # macOS Local Bootstrap Wrapper
2
2
 
3
- This directory contains a local macOS bootstrap wrapper for testing:
3
+ This directory contains the local macOS wrapper used to exercise the public beta
4
+ CLI during package and command smoke testing.
4
5
 
5
6
  ```bash
6
7
  export PATH="/Users/carlosjperez/Documents/GitHub/brik64-cli/packaging/macos-local:$PATH"
7
8
  brik --version
8
9
  ```
9
10
 
10
- Boundary:
11
- - bootstrap wrapper only;
12
- - depends on local Node.js;
13
- - not a native final artifact;
14
- - not public release evidence;
15
- - not post-beta `.brik`/PCD semantic source.
11
+ ## Current Role
12
+
13
+ - Provides a local `brik` command wrapper for macOS testing.
14
+ - Depends on the local Node.js runtime.
15
+ - Supports install-path and command-contract checks before platform packages are
16
+ promoted.
17
+
18
+ ## Promotion Path
19
+
20
+ Native macOS release assets should ship with platform-specific checksum,
21
+ install-smoke, and release-manifest evidence before they are promoted through
22
+ GitHub Releases, curl/GCP, Homebrew, docs, or brik64.com.