Skip to content

explore: credential relay as product (deferred to strategy meeting)#248

Merged
klappy merged 1 commit into
mainfrom
explore/credential-relay-product
Jun 10, 2026
Merged

explore: credential relay as product (deferred to strategy meeting)#248
klappy merged 1 commit into
mainfrom
explore/credential-relay-product

Conversation

@klappy

@klappy klappy commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Exploration capture per mode discipline — no build decision made at midnight. Reusable: yes regardless. Billable/MIT: routed to the strategy meeting with the ODD license question. 6B gate declared.


Note

Low Risk
Documentation-only internal exploration with no runtime, auth, or licensing changes.

Overview
Adds a new internal exploration doc docs/explorations/credential-relay-as-product.md (E0010) that records product/strategy thinking on the GitHub App credential relay—no implementation or governance change.

Decisions captured: build the relay reusable either way; defer billable hosted service, MIT vs protective licensing, and ODD license tie-in to a strategy meeting. The write-up argues minting is likely commodity (6B Borrow) while differentiation sits in charter-scoped agent identity / governance; flags hosted custody of App private keys as high liability for a one-person-maintainable system and favors self-host-first with paid value in governance/support/panel.

Strategy meeting agenda: five explicit questions (moat placement, custody acceptability, license split, 6B borrow table vs Actions/Octokit/managed-auth/Vault-class tools, smallest test via self-host template adoption). Explicitly gates any build on a real 6B table and governs nothing yet.

Reviewed by Cursor Bugbot for commit 00a18cb. Bugbot is set up for automated code reviews on this repo. Configure here.

Genericize the relay regardless (free). Commercial/licensing questions
routed to the strategy meeting with the ODD license decision. Honest
priors recorded: plumbing is commodity, moat is charter-scoped agent
identity, custody collides with maintainability-one-person, MIT is
compatible with license-never-assign but placement matters.
@klappy klappy merged commit c503504 into main Jun 10, 2026
@github-actions

Copy link
Copy Markdown

Canon Quality — P0010 Retrieval-Readiness ⚠️

Soft report for klappy://canon/constraints/retrieval-disclosure-contract. 668 files scanned. Never blocks — informational until the corpus is ready to enforce.

  • Blocking-class findings: 12 (structural fields the contract would filter on)
  • Warnings: 0 (kind resolves to unknown)
  • Informational: 13 (exempt templates/archive/drafts)

Kind distribution: {'essays': 48, 'canon': 223, 'apocrypha': 38, 'docs': 296, 'journals': 57, 'unknown': 6}
Kind source: {'path': 541, 'frontmatter': 121, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 567 visible, 101 hidden (journals/apocrypha/unknown)

By rule: {'audience-invalid': 2, 'exposure-missing': 5, 'tier-missing': 5, 'tier-invalid': 7, 'kind-unresolvable': 6}

These are not schema violations (see the Frontmatter Schema job for those on writings/). They are corpus-readiness signals for the retrieval contract: invalid/missing audience, exposure, tier, and docs whose kind cannot be resolved. Fix in a corpus-cleanup PR before the contract flips to enforcing. See the retrieval-readiness-findings artifact for the full list.

Validator: scripts/audit-retrieval-readiness.py · Constraint: klappy://canon/constraints/retrieval-disclosure-contract · Run: #248

@github-actions

Copy link
Copy Markdown

Canon Quality — Frontmatter Schema ✅

All 46 file(s) in writings/ conform to klappy://canon/meta/frontmatter-schema.

Validator: scripts/validate-frontmatter.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge · Run: #248

@github-actions

Copy link
Copy Markdown

Canon Quality — Homepage Surfacing ✅

46 essay(s) scanned. Soft report — never blocks; the hard field gate is the Frontmatter Schema job.

All published essays resolve to the homepage feed.

Report: scripts/surfacing-report.py · Canon: klappy://canon/constraints/frontmatter-validation-before-merge

@github-actions

Copy link
Copy Markdown

Canon Quality — oddkit_audit

No dead klappy:// references or legacy link patterns found in writings/. 48 files scanned.

Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #248

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant