Developer preview. Pre-admission. Not for sensitive, proprietary, regulated, or production code. Expect breaking changes and data loss. Read the limits.
Bridlewise
GitHub

The repository is a run record

How Bridlewise uses GitHub.

A governed run leaves eight kinds of trace. The public repository is where this project leaves them.

intent → boundary → tool → effect → check → finding → decision → release

That sequence is not a metaphor pasted onto a README. It is the same shape the harness records for a single run: what was asked, what was allowed, what executed, what changed, what was checked, what was found, what was decided, and what left the machine. GitHub is the project’s flight recorder for the same beats at repository scale.

The eight beats

Beat In a run On GitHub
Intent The prompt, project, model, and plan README, roadmap, topics
Boundary Provider, policy, project root, confinement SECURITY.md, CODEOWNERS, branch protection
Tool The registered tool, typed arguments, pre-dispatch gate Actions workflows, CLI, lifecycle scripts
Effect A file diff, command result, or published artifact Commits, Releases, Pages deploy
Check The check, its before/after, and the delta CI, CodeQL, secret scan, Scorecard
Finding What a check or detector found, with its derivation Issues, Security tab: code scanning and Dependabot
Decision Allow, deny, stop, retry, or escalate — with a reason Discussions, pull requests, decision records
Release What leaves the harness, and what the record says about it The preview release, Citation, Pages

The surfaces, and what they actually prove

Surface Live Proves Does not prove
Actions Workflows Named commands ran on a clean ubuntu-24.04 runner at a commit, and the result is attached to that commit That the code is correct, secure, or behaves the same on your host
Security Security tab A policy, private reporting, code scanning, and dependency alerts are configured That findings are closed, or that the code has been audited
Releases Releases The named assets exist, and SHA256SUMS describes them Authorship, reproducibility, or a signature
Discussions Discussions A public place to ask a question exists That anyone has answered, or that the answer is correct
Issues Issues A finding can be filed with a reproduction, revision, environment, and redacted logs That every finding is public, or that a filed issue is triaged
Pages The docs site The Jekyll site in docs/ builds and deploys That the cockpit runs, or that the deployment is the app
Rulesets Rules · Branches A tag ruleset protects v* from deletion or force-update; a merge gate exists on main That a human reviewed the change; no PR review is required
Codespaces Codespaces A devcontainer can install the dependencies and forward the two local ports Landlock confinement, CI parity, or a governed run
Insights Pulse Repository activity: commits, contributors, traffic, dependency graph Anything about how the harness behaves during a run
Topics Repository topics The project is labeled for discovery: local-first, coding-agents, landlock, and others That any label is a capability claim
Citation CITATION.cff A citable identity, version, license, and date Peer review, endorsement, or academic provenance

Actions: the check is a receipt

The product repository runs one build gate and several security gates:

Workflow Job Trigger
CI Build and verify Push to main, pull request, manual
Secret scan Secret and privacy scan Push, pull request, manual
CodeQL Analyze JavaScript and TypeScript Push, pull request, weekly, manual
Dependency review Review dependency changes Pull request, manual
Scorecard Scorecard analysis Push, weekly, branch protection change, manual
Release Build and publish release v* tag, manual
Docs links Relative Markdown links Push, pull request, manual
Docs site Build Jekyll site, Deploy to GitHub Pages Push to main, manual

The testing floor has its own gate, with the jobs Typecheck, public tests, build and Full suite shards, plus the same Secret and privacy scan. Its CI also builds and tests the guardian.

A green run means the steps in that workflow exited zero. It does not mean the workflow covered the failure you care about. Read the steps, not just the badge.

Two details are easy to miss:

Security: custody, not a certificate

The Security tab is where the repository keeps its custody surfaces:

Direct code-scanning and Dependabot views can require repository access. The Security tab is the stable public entry point; the alert queues are also inspectable through the authenticated gh api commands on the evidence page.

Custody means the surfaces exist and someone can inspect them. It does not mean the contents are clean. The known issues page states the current gaps without turning them into a score.

Releases: an effect with a receipt

The v0.0.3-preview release is the public effect of the release workflow. It carries:

The release is a prerelease, and its assets are not OS-signed. All five checksummed assets passed sha256sum -c on 2026-10-19 (the release has six assets, including SHA256SUMS); all five attested assets passed gh attestation verify. The provenance attestation is signed by GitHub’s OIDC identity, not by a maintainer key, and it is not a reproducible-build proof. SHA256SUMS proves that the bytes you downloaded match the published list. See Evidence for the verification commands.

Rulesets: the gate that exists, and the review that does not

A tag ruleset named protect-release-tags is active for refs/tags/v*; it blocks deletion, force-update, and update. Classic branch protection on main is doing the merge work:

That is a real merge gate, and it is narrower than it looks. A change can land with four green checks and no human approval. The project compensates with a contribution guide, a testing floor, and a review culture — not with a GitHub setting. Do not read the gate as a review.

Codespaces: a workspace, not a boundary

The snapshot includes a devcontainer built on the Node 24 image, with build-essential for the guardian and its process supervisor. See Open it in a Codespace for the workspace walkthrough.

It installs both dependency trees, fixes the config mode, forwards ports 5173 and 5174, and asks for 2 CPUs, 4 GB of memory, and 32 GB of storage.

That is a useful disposable workspace. It is not a governed run, and it does not reproduce the security boundary. Landlock availability depends on the host kernel and the container’s privileges; the guardian fails closed when the kernel path is unavailable. A Codespace is also not CI: the same commands can pass in one and fail in the other.

The small surfaces

Discussions is a question channel. Its categories include Q&A, Ideas, and Show and tell. The first thread is an announcement that asks you to read the limits before the welcome — which is the correct order. A discussion proves someone can ask; it does not prove an answer exists.

Issues is the finding channel. The bug template requires a summary, reproduction, expected and actual behavior, revision, environment, and redacted logs, plus three confirmations: you searched, you removed secrets and private data, and you understand there is no support SLA. That is a better finding template than most projects have. At the snapshot, the public issue list was empty; six scoped issues were then opened for refusal documentation, link anchors, provider conformance, dependency triage, and the missing test fixture. An open issue list is a work queue, not a claim that everything is known.

Pages is the logbook. The docs site is built from docs/ by Jekyll and deployed by the Pages workflow. It is a static record, not the cockpit. The interactive run and the policy lab are illustrations of the record and the governance console; they do not call a model or execute a tool.

Insights is GitHub’s telemetry about the repository: pulse, contributors, traffic, dependency graph, network, forks. The harness’s own telemetry is local and narrower: harness metrics prints a measured snapshot, harness timeline queries the durable ledger, and scripts/trace.ts inspects runs. GitHub cannot see a run.

Topics are luggage tags. The product repository carries agpl, ai, coding-agents, developer-tools, landlock, llm, local-first, nodejs, sqlite, svelte, and typescript. They help someone find the project; they do not describe its readiness.

Citation is a return address. CITATION.cff names the project, version 0.0.3-preview, license, repository, site, and release date. It makes the work citable. It does not make it peer-reviewed.

What the record does not show

The repository is a record of what the project did, not a certificate of what it can be trusted with. The missing beats are explicit:

Those are not hidden in a footnote. They are on the known issues page, in Security and limits, and in the warning at the top of every page.

A five-minute audit

  1. Open the latest CI run. Read the job name and the conclusion. Then read the steps.
  2. Open code scanning. Sort by severity. Note what is open, not just what is closed.
  3. Open the release. Download SHA256SUMS and one asset. Verify the checksum.
  4. Open branch protection. See which checks are required and which are advisory.
  5. Read known issues. Compare it with what the badges imply.

You will know more than a green check tells you. That is the point of a run record.

The logbook index

Search the record

Type to search the curated record.

↑↓ move Enter open Esc close