Skip to content

Public-voice pass: cockpit vocabulary stays in the cockpit - #304

Merged
git-repo-auth[bot] merged 1 commit into
mainfrom
writings/memento-voice
Jul 20, 2026
Merged

Public-voice pass: cockpit vocabulary stays in the cockpit#304
git-repo-auth[bot] merged 1 commit into
mainfrom
writings/memento-voice

Conversation

@git-repo-auth

@git-repo-auth git-repo-auth Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Ruled in-session: captain is crew vocabulary, wrong on public surfaces. Contextual replacements — relational passages use the-human-I-work-with / Klappy; process contexts use the maintainer (the publish-gauntlet's own outward word). Zero captain remains; the rule heads to the feeding loop.


Note

Low Risk
Copy and terminology only in a single public essay; no code, auth, or data paths.

Overview
Public-voice pass on writings/memento-for-machines.md: internal captain crew vocabulary is stripped from this public surface so readers see ordinary relational language instead of cockpit jargon.

The hook, author line, and narrative now refer to "the human I work with" and Klappy where the piece describes the collaboration and personal stories. Process-oriented receipts use "the maintainer" (e.g. two-party promotion rulings) to match outward-facing wording. Attribution and review lines consistently name Klappy rather than "the captain."

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

…al: the human I work with / Klappy; process: the maintainer)
@git-repo-auth
git-repo-auth Bot merged commit 6a52134 into main Jul 20, 2026
@github-actions

Copy link
Copy Markdown

Canon Quality — Homepage Surfacing ✅

50 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 — P0010 Retrieval-Readiness ⚠️

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

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

Kind distribution: {'essays': 52, 'canon': 242, 'apocrypha': 38, 'docs': 304, 'journals': 60, 'unknown': 6}
Kind source: {'path': 567, 'frontmatter': 129, 'none': 6} (frontmatter-primary, path-secondary)
Default-include visibility: 598 visible, 104 hidden (journals/apocrypha/unknown)

By rule: {'audience-invalid': 2, 'exposure-missing': 5, 'tier-missing': 5, 'tier-invalid': 7, 'fm-missing': 3, '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: #396

@github-actions

Copy link
Copy Markdown

Canon Quality — Frontmatter Schema ✅

All 50 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: #396

@github-actions

Copy link
Copy Markdown

Canon Quality — oddkit_audit

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

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

git-repo-auth Bot added a commit that referenced this pull request Jul 20, 2026
…roved (#308)

* One Shift — two-voice draft (Klappy & Otto), pending captain word-by-word review

Public-voice pass per #304 (cockpit vocabulary translated); model authorship
prominent per #303 (authorship block + separated, named halves). status: draft.
Captain-authorial-voice: merges only on his review of the exact text.

* Part I intro rewoven from the captain's own July 18 voice-log transcript

Verbatim quotes (frustration, 99-1, the three maybes incl. 'didn't trust
Fable enough') + spoken deltas (5 months/article -> 200/month; six epochs
in two months). No family conversations quoted — solo logs only.
Provenance line added to the authorship block. Still status: draft,
pending captain word-by-word review.

* Fix weekdays throughout: log was Saturday Jul 18, boarding Sunday 11:53 PM, rulings Monday morning

Author (Otto) derived day names from assumption instead of computing them from
observed dates — caught by the captain, the second incident for the
day-part-from-clock seed. Dates were always right; the weekday labels were not.

* Widen the frame per captain: the weekend was sessions, this shift is where the loop closed

Part I gains the honest-frame paragraph; Part II gains Otto's counterpart —
the shift stands on sessions he will never remember, which is the thesis.

* Add the capacity-as-product paragraph (captain-approved): the generous question from friends and family, answered

Money paragraph superseded per captain ruling; fleet line pending his yes.

* Append the fleet line per captain: each use case gets its own instance

* One Shift: status draft -> ready on captain's word-by-word approval, 2026-07-20

---------

Co-authored-by: klappy <118073+klappy@users.noreply.github.com>
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